RE: Operator requirements

["Chen, Weijing" <wchen@tri.sbc.com>]

Bert,

What about us create a management system requirement draft from LAP (Large
and very large Access Provider) point of view? It is a requirement for
management system, not for equipment. I hope that it can translate into more
general management requirement or supplant general one.


What is thought out there?



--
Weijing Chen



-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
Sent: Tuesday, September 24, 2002 3:28 AM
To: Xmlconf (E-mail)
Subject: Operator requirements

I recently (well, a month ago now) tried this on a much 
smaller mailing list. No reaction. So let me try here.

I was wondering if we have any volunteers who are willing
to get the operator requirements documented. Even if such
requirements are not universal, still having them, eben by
separate categories like
  - all operators
  - core operators
  - large isps
  - small isps
  - enterprises
  - ...
would be really helpfull.

I have heard that the document draft-ops-operator-req-mgmt-02.txt
was not it. But we need something to work from. If the doc is
not complete, or if it is not describing the requirements
correctly, or if it is not complete, then we need to work on it.
 
So... which operators want to help to make sure that whatever
we do next will take the proper operator requirements into account?

Thanks,
Bert 

--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>

--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>