RE: How does XML help Network Operators

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

OK, I have gone through the draft and have these comments:

- In the intro, you differentiate between configuration and
  provisioning. Later in the document, I get confused again 
  as to when you use the term provisioning and when you use
  configuration. Is it just me?
- I wish operators would also read this and express their
  agreement or disagreement with what you have written down
- I am missing any discussion on "network-wide-configuration",
  while I have seen that as THE BIG REQUIREMENT through all
  of the discussions we have had
- I am not clear that the authorization aspects have been
  discussed well enough. This is the "who is who" and "who
  can do what". I understand the "who is who" is authentication,
  but once you have authenticated someone, you want that person
  to be mapped into some sort of "group" and then you want to
  control access to various portions of the configuration and/or
  provioning data based on the group to which the person is
  mapped. Or at least that is what I understand from some 
  of the operator input I have heard.

Well, those are my intial remarks.. more comments from others please

Bert 

> -----Original Message-----
> From: Eliot Lear [mailto:lear@cisco.com]
> Sent: donderdag 26 september 2002 0:43
> To: Wijnen, Bert (Bert)
> Cc: xmlconf
> Subject: Re: How does XML help Network Operators
> 
> 
> Bert,
> 
> Along the lines of wanting things written down, I've done a little 
> writing of my own, with a WHOLE lot of input from many different 
> sources.  The following is provided merely for discussion purposes, 
> based on our world tours together and other customer interactions.  I 
> hope you find it useful.  This is a draft -00.  Your comments and 
> suggestions are welcome.  I have donned my flame retardant 
> glasses and 
> gloves ;-)
> 
> Eliot
> 
> file saved as: draft-lear-config-issues-00.txt
> 

--
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/>