Re: XMLCONF Proposal

[Harrie Hazewinkel <harrie@jumpy.it>]

On Monday, February 17, 2003, at 04:13 PM, Margaret Wasserman wrote:

> Hi All,
>
> We have a proposal available for a new configuration protocol
> that may be of interest to folks on these lists.  The proposal
> has been published an an I-D, and can be found at:
>
> http://www.ietf.org/internet-drafts/draft-enns-xmlconf-spec-00.txt
>
> We believe that this proposal addresses many of the operator
> and vendor requirements for a configuration protocol that have
> been gathered and analyzed over the past couple of years.
I have read the draft and have some comments or questions.
These are just general and some, I believe, discussed
various times.

1)
Why using RPC and not for instance SOAP over HTTP??
Maybe it is wise to seperate that layer from the
XMLCONF protocol so various mappings can exist.

(Yes, I understand that for during the start it is
wiser to have it all in a single draft).


2)
As a transport you mantion various protocols in a figure in
section 1.1. Later you use the concept of channels.
Why adding RPC between the operations layer and transport
layer if you could use BEEP directly and providing you the
channels??

3)
Section 2.2 speaks about authentication and privacy.
However, the use of privacy is not explained. They are
left out of this document, but I am interested in seeing
this somehow. Also because the rest of this section
speaks a lot on authentication, but not which kind
of mecahnisms must be used. I beleive to have this deployed
from various vendors this must be aligned/standardized
somehow.

NOTE: I am not a vendor, so maybe I lack the knowledge of this.

4) With respect to 'kill-session' I could not figure
out on how to know the session from the protocol
operations defined in section 5. Or are the sessions the
channels defined in section 2.4. I believe so.


As a general comment, this could be a reasonable start,
but it is also far from complete, I believe.
However, I am not a vendor.


cheers,
Harrie


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