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]/
Operational Contacts
- Previous message (by thread): Operational Contacts
- Next message (by thread): Operational Contacts
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Karrenberg
Daniel.Karrenberg at ripe.net
Thu Oct 22 17:45:45 CET 1992
> Arnold Nipper <nipper at ira.uka.de> writes: > > We should soon introduce this new NOC object. If for example a service > provider wants to give support to all his customer networks, all three > attributes have to be added to a lot of networks. And then the phone > number changes ... Don't waste time. This sounds like re-opening the discussion. Questions: - Do more people feel strongly about this? - Might they even feel strongly enough to circulate a proposal for the NOC object? - Shall we come back on the interim soloution? If there is consensus on the list discussion that (contrary to the Paris consensus) we should proceed immediately and quickly with the NOC object, I am very reluctant to put an interim soloution into place. Please comment on this, even if it is just Yes, reopen the discussion. No, proceed as agreed in Paris. The NCC needs to know what the DB WG wants quickly. Daniel PS: My personal preference is to go ahead quickly with the NOC object but I think this was not the consensus in Paris.
- Previous message (by thread): Operational Contacts
- Next message (by thread): Operational Contacts
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]