About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: Operational Contacts

  • From: Duncan Rogerson < >
  • Date: Fri, 23 Oct 1992 17:59:28 +0100 (BST)

> POC for the network. But if <customer> has problems, and <service_provider>
> wants to contact <customer>, the appropriate information can be stored
> in the general contact information as well. Pls keep in mind, that this
> contact information doesn't supersede the named [at]c's in the objects,
> but will provider general contact point if the specific poeple are not

What I read from this is that we have to distinguish between
the service provider's NOC and the customers own NOC.  So we
should have operational contact details for both the end site and
their service provider ?

So, assuming we still go with the NOC object idea, that means
a NOC object is created for the service provider, and one for
the end site's own NOC.  Each network the end site registers
then has a pointer to their NOC, and also to their service
provider's.

Does this make sense, or am I falling asleep already seeing as 
the weekend is here ? :)  I just don't think we gain anything
having information spread all over the database, that could be
maintained much more easily in one object.

Dunc



  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | © RIPE Community. All rights reserved.
RIPE.NET Homepage LIR Portal RIPE Community