draft-ietf-netconf-4741bis-05.txt   draft-ietf-netconf-4741bis-06.txt 
Network Working Group R. Enns, Ed. Network Working Group R. Enns, Ed.
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Obsoletes: RFC4741 M. Bjorklund, Ed. Obsoletes: RFC4741 M. Bjorklund, Ed.
(if approved) Tail-f Systems (if approved) Tail-f Systems
Intended status: Standards Track J. Schoenwaelder, Ed. Intended status: Standards Track J. Schoenwaelder, Ed.
Expires: April 23, 2011 Jacobs University Expires: April 28, 2011 Jacobs University
A. Bierman, Ed. A. Bierman, Ed.
Brocade Brocade
October 20, 2010 October 25, 2010
Network Configuration Protocol (NETCONF) Network Configuration Protocol (NETCONF)
draft-ietf-netconf-4741bis-05 draft-ietf-netconf-4741bis-06
Abstract Abstract
The Network Configuration Protocol (NETCONF) defined in this document The Network Configuration Protocol (NETCONF) defined in this document
provides mechanisms to install, manipulate, and delete the provides mechanisms to install, manipulate, and delete the
configuration of network devices. It uses an Extensible Markup configuration of network devices. It uses an Extensible Markup
Language (XML)-based data encoding for the configuration data as well Language (XML)-based data encoding for the configuration data as well
as the protocol messages. The NETCONF protocol operations are as the protocol messages. The NETCONF protocol operations are
realized as Remote Procedure Calls (RPC). realized as Remote Procedure Calls (RPC).
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on April 23, 2011. This Internet-Draft will expire on April 28, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 77, line 7 skipping to change at page 77, line 7
<id>2</id> <id>2</id>
</company-info> </company-info>
</user> </user>
</users> </users>
</top> </top>
</data> </data>
</rpc-reply> </rpc-reply>
9. Security Considerations 9. Security Considerations
This section provides security considerations for the base NETCONF
message layer and the base operations of the NETCONF protocol.
Security considerations for the NETCONF transports are provided in
the transport documents and security considerations for the content
manipulated by NETCONF can be found in the documents defining data
models.
This document does not specify an authorization scheme, as such a This document does not specify an authorization scheme, as such a
scheme should be tied to a meta-data model or a data model. scheme should be tied to a meta-data model or a data model.
Implementors SHOULD provide a comprehensive authorization scheme with Implementors SHOULD provide a comprehensive authorization scheme with
NETCONF. NETCONF.
Authorization of individual users via the NETCONF server may or may Authorization of individual users via the NETCONF server may or may
not map 1:1 to other interfaces. First, the data models may be not map 1:1 to other interfaces. First, the data models may be
incompatible. Second, it may be desirable to authorize based on incompatible. Second, it may be desirable to authorize based on
mechanisms available in the secure transport layer (SSH, BEEP, etc). mechanisms available in the secure transport layer (SSH, BEEP, etc).
skipping to change at page 82, line 9 skipping to change at page 82, line 9
for his persistence and patience in assisting us with security for his persistence and patience in assisting us with security
considerations. We would also like to thank Randy Presuhn, Sharon considerations. We would also like to thank Randy Presuhn, Sharon
Chisholm, Juergen Schoenwalder, Glenn Waters, David Perkins, Weijing Chisholm, Juergen Schoenwalder, Glenn Waters, David Perkins, Weijing
Chen, Simon Leinen, Keith Allen, and Dave Harrington for all of their Chen, Simon Leinen, Keith Allen, and Dave Harrington for all of their
valuable advice. valuable advice.
12. References 12. References
12.1. Normative References 12.1. Normative References
[1] Sperberg-McQueen, C., Paoli, J., Maler, E., and T. Bray, [1] Sperberg-McQueen, C., Bray, T., Paoli, J., and E. Maler,
"Extensible Markup Language (XML) 1.0 (Second Edition)", World "Extensible Markup Language (XML) 1.0 (Second Edition)", World
Wide Web Consortium FirstEdition REC-xml-20001006, Wide Web Consortium FirstEdition REC-xml-20001006,
October 2000, <http://www.w3.org/TR/2000/REC-xml-20001006>. October 2000, <http://www.w3.org/TR/2000/REC-xml-20001006>.
[2] DeRose, S. and J. Clark, "XML Path Language (XPath) Version [2] DeRose, S. and J. Clark, "XML Path Language (XPath) Version
1.0", World Wide Web Consortium Recommendation REC-xpath- 1.0", World Wide Web Consortium Recommendation REC-xpath-
19991116, November 1999, 19991116, November 1999,
<http://www.w3.org/TR/1999/REC-xpath-19991116>. <http://www.w3.org/TR/1999/REC-xpath-19991116>.
[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement
 End of changes. 6 change blocks. 
5 lines changed or deleted 12 lines changed or added

This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/