draft-ietf-netconf-soap-06.txt   draft-ietf-netconf-soap-07.txt 
Network Working Group T. Goddard Network Working Group T. Goddard
Internet-Draft ICEsoft Technologies Inc. Internet-Draft ICEsoft Technologies Inc.
Expires: March 20, 2006 September 16, 2005 Expires: June 9, 2006 December 6, 2005
Using the Network Configuration Protocol (NETCONF) Over the Simple Using the Network Configuration Protocol (NETCONF) Over the Simple
Object Access Protocol (SOAP) Object Access Protocol (SOAP)
draft-ietf-netconf-soap-06 draft-ietf-netconf-soap-07
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 20, 2006. This Internet-Draft will expire on June 9, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
Abstract Abstract
The Network Configuration Protocol (NETCONF) is applicable to a wide The Network Configuration Protocol (NETCONF) is applicable to a wide
range of devices in a variety of environments. The emergence of Web range of devices in a variety of environments. The emergence of Web
Services gives one such environment, and is presently characterized Services gives one such environment, and is presently characterized
skipping to change at page 6, line 26 skipping to change at page 6, line 26
o HTTP may be more complex than is necessary for the application o HTTP may be more complex than is necessary for the application
o The use of HTTP may mask the application from some firewalls o The use of HTTP may mask the application from some firewalls
o A substantially new service should not re-use port 80 as assigned o A substantially new service should not re-use port 80 as assigned
to HTTP to HTTP
o HTTP caching may mask connection state o HTTP caching may mask connection state
Fundamentally, these concerns lie directly with SOAP over HTTP, Fundamentally, these concerns lie directly with common usage of SOAP
rather than the application of SOAP over HTTP to NETCONF. As BCP 56 over HTTP, rather than the application of SOAP over HTTP to NETCONF.
indicates, it is debatable whether HTTP is an appropriate protocol As BCP 56 indicates, it is debatable whether HTTP is an appropriate
for SOAP at all, and it is likely that BEEP would be a superior protocol for SOAP at all, and it is likely that BEEP would be a
protocol for most SOAP applications. Unfortunately, SOAP over HTTP superior protocol for most SOAP applications. Unfortunately, SOAP
is in common use and must be supported if the practical benefits of over HTTP is in common use and must be supported if the practical
SOAP are to be realized. Note that the verbose nature of SOAP benefits of SOAP are to be realized. Note that the verbose nature of
actually makes it more readily processed by firewalls, albeit SOAP actually makes it more readily processed by firewalls, albeit
firewalls designed to process SOAP messages. firewalls designed to process SOAP messages.
HTTP caches SHOULD NOT be inserted between NETCONF managers and HTTP caches SHOULD NOT be inserted between NETCONF managers and
agents as NETCONF session state is tied to the state of the agents as NETCONF session state is tied to the state of the
underlying transport connection. Three defensive actions can be underlying transport connection. Three defensive actions can be
taken: taken:
o Caching MUST be prohibited through the use of HTTP headers Cache- o Caching MUST be prohibited through the use of HTTP headers Cache-
Control and Pragma: no-cache Control and Pragma: no-cache
o HTTP proxies SHOULD NOT be deployed within the management network o HTTP proxies SHOULD NOT be deployed within the management network
o Use HTTPS o Use HTTPS
It is also possible to respond to the concern on the re-use of port It is also possible to respond to the concern on the re-use of port
80. A NETCONF SOAP service SHOULD be offered over a new standard 80. Any NETCONF SOAP service MUST always be supported over the new
port for NETCONF over SOAP (over HTTP) to be defined as requested in standard port for NETCONF over SOAP and all conforming
the IANA considerations of this document. implementations MUST default to attempting connections over this new
standard port for NETCONF. A standard port for NETCONF over SOAP
(over HTTP) is requested in the IANA considerations of this document.
2.5 Important HTTP 1.1 Features 2.5 Important HTTP 1.1 Features
HTTP 1.1 [5] includes two important features that provide for HTTP 1.1 [5] includes two important features that provide for
relatively efficient transport of SOAP messages. These features are relatively efficient transport of SOAP messages. These features are
"persistent connections" and "chunked transfer-coding". "persistent connections" and "chunked transfer-coding".
Persistent connections allow a single TCP connection to be used Persistent connections allow a single TCP connection to be used
across multiple HTTP requests. This permits multiple SOAP request/ across multiple HTTP requests. This permits multiple SOAP request/
response message pairs to be exchanged without the overhead of response message pairs to be exchanged without the overhead of
 End of changes. 5 change blocks. 
14 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.27, available from http://www.levkowetz.com/ietf/tools/rfcdiff/