This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
Suggestion from Piet Beertema
- Previous message (by thread): Suggestion from Piet Beertema
- Next message (by thread): Suggestion from Piet Beertema
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Karrenberg
Daniel.Karrenberg at ripe.net
Thu Jul 23 11:16:15 CEST 1992
I am still not clear what is really needed. I read: - information about service provider(s) for a domain But i assume what is meant is: - information about *e-mail* service provider(s) for a domain We have information about IP service providers in the database and while the currenct "connect" field is not very well defined we will have the more clearly defined fields soon. Questions: Do we need information about mail service providers separately? My answer: Don't know. Who will maintain the information? My answer: This is the key question. I think the providers should. This raises similar problems as the routing-privilege one. Is the RIPE database the right place? My answer: maybe. How to code it in the RIPE database (object, attribute)? My answer: Piet is right that it should go with the domain object. I would propose a new attribute "mail-provider" or some similar name. This should probably be an *ordered* list of tags much like the new routing privilege. It should definitely not be named just "connect". Daniel
- Previous message (by thread): Suggestion from Piet Beertema
- Next message (by thread): Suggestion from Piet Beertema
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]