SourceForge : View Wiki Page: NETCONF

Search Wiki Pages Project: scrm-wg Wiki > NETCONF > View Wiki Page

wiki1509: NETCONF

Standard

1. The name of the specification

Network Configuration Protocol (NETCONF)

2. A short statement (<100 words) of the purpose and function of the specification

The NETCONF configuration protocol provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML) based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized on top of a simple Remote Procedure Call (RPC) layer.

The NETCONF protocol defines a simple mechanism through which a network device can be managed, configuration data information can be retrieved, and new configuration data can be uploaded and manipulated. The protocol allows the device to expose a full, formal, application programming interface (API). Applications can use this straight-forward API to send and receive full and partial configuration data sets.

The protocol requires that the mapping over SSH is mandatory to implement while the mapping over BEEP and SOAP are optional.

3. The version number (or other distinct identifier) and date of the most recently approved version of the specification.

Approval of the Netconf protocol and the mapping over SSH:

http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg02342.html

Approval of the mapping over BEEP:

http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg02355.html

Approval of the mappong over SOAP:

http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg02343.html

4. If the specification is part of a group of explicitly related specifications from the same source, the name of the group of specifications.

Network Configuration (NETCONF) Working Group in the IETF: http://www.ietf.org/html.charters/netconf-charter.html

5. URI for the normative text of the specification

NETCONF Configuration Protocol (187259 bytes) http://www.ietf.org/internet-drafts/draft-ietf-netconf-prot-12.txt

Using the NETCONF Configuration Protocol over Secure Shell (SSH) http://www.ietf.org/internet-drafts/draft-ietf-netconf-ssh-06.txt

Using the NETCONF Protocol over Blocks Extensible Exchange Protocol (BEEP) http://www.ietf.org/internet-drafts/draft-ietf-netconf-beep-10

Using the Network Configuration Protocol (NETCONF) Over the Simple Object Access Protocol (SOAP) http://www.ietf.org/internet-drafts/draft-ietf-netconf-soap-08

SOURCE

6. The name of the SDO that generated/authored/hosted the specification.

Internet Engineering Task Force (IETF)

7. URI for the SDO

http://www.ietf.org

8. The level of approval that the SDO has conferred on the specification as described by the SDO's process.

Approved as a Proposed Standard. In RFC-Editor queue for publication as RFC.

9. The language or languages in which the specification is available.

US English

SUBJECT

10. Which of the ITU-T TMN FCAPS model layers does the specification's functionality address?

(http://en.wikipedia.org/wiki/FCAPS, http://www.futsoft.com/pdf/fcapswp.pdf) Fault Management: Fixing broken resources. Configuration Management: Controlling a resource's operational parameters. Accounting Management: Recording and analyzing resource use. Performance Management: Controlling speed and efficiency of resource use. Security Management: Controlling access to resources.

12. Where does the specification directly operate, as among the layers defined in the ISO Open System Interconnect (OSI) model?

(http://www.looselycoupled.com/opinion/2003/saruk-osi-infr0905.html )

The protocol allows for configuration at any layer: Physical layer Data link layer Network layer Transport layer Session layer Presentation layer Application layer.

13. Which of the following (CIM based) functional areas does the model of the specification address?

(http://www.dmtf.org/standards/cim/)

Policy Management Infrastructure Physical Networks Logical Networks Physical Systems Logical Systems Physical Devices Logical Devices Physical Storage Logical Storage Operating Systems Databases Application Servers Applications Users Security Support

OPTIONAL

14. The level of approval of the specification in this generic lifecycle taxonomy:

IESG Approved as Proposed Standard in the IETF.

15. URI for the applicable SDO's patent and copyright rules, if any, applicable to development and use of the specification.

http://www.ietf.org/rfc/rfc3978.txt and http://www.ietf.org/rfc/rfc3979.txt

16. URI for the SDO's posting location, (if any) for notices from participants or individuals regarding claims under the rules stated under number 15.

https://datatracker.ietf.org/public/ipr_disclosure.cgi

17. Interoperability, conformance, or certification test activity for the specification (by owner name or URI).

18. Known implementations of the specification (by owner name or URI).

19. A list (or URI pointer to same) of the other specifications* that are normatively referenced in the specification.

20. A list (or URI pointer to same) of the other specifications* that are referenced in the specification (except the ones listed under number 19).

21. A list (or URI pointer to same) of other specifications* with which the specification may (speculatively) interoperate or act in complementary, compatible fashion.

22. A list (or URI pointer to same) of other specifications* similar to this specification. (Whether or not substitutable.)

Show Details