Re: NetConf over SOAP normative reference issue

["Randy Presuhn" <randy_presuhn@mindspring.com>]

Hi -

> From: "Andy Bierman" <ietf@andybierman.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: <netconf@psg.com>; <netconf@ops.ietf.org>
> Sent: Tuesday, March 15, 2005 12:24 PM
> Subject: Re: NetConf over SOAP normative reference issue
...
> >Are you suggesting we re-cast the document in terms of SOAP 1.2,
> >and drop the BEEP dependency?
> >
> >
> what do you mean "drop the BEEP dependency"?

Ira's note said there was a normative reference to RFC 3288.

Randy

> >>From: "McDonald, Ira" <imcdonald@sharplabs.com>
> >>To: <netconf@psg.com>
> >>Sent: Tuesday, March 15, 2005 9:53 AM
> >>Subject: NetConf over SOAP normative reference issue
> >>
> >>Hi,
> >>
> >>[Bert Wijnen asked me to pass on this comment.]
> >>
> >>The latest NetConf over SOAP <draft-ietf-netconf-soap-04.txt>
> >>has a serious problem for advancement on the IETF "standards
> >>track", to whit, these two normative references:
> >>
> >>   [3]   Box, D., Ehnebuske, D., Kakivaya, G., Layman, A., Mendelsohn,
> >>         N., Nielsen, H., Thatte, S. and D. Winer, "Simple Object Access
> >>         Protocol (SOAP) 1.1", W3C Note NOTE-SOAP-20000508, May 2000,
> >>         <http://www.w3.org/TR/2000/NOTE-SOAP-20000508>.
> >>
> >>   [16]  O'Tuathail, E. and M. Rose, "Using the Simple Object Access
> >>         Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)",
> >>         RFC 3288, June 2002, <http://www.ietf.org/rfc/rfc3288.txt>.
...



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