draft-ietf-netconf-call-home-09.txt   draft-ietf-netconf-call-home-10.txt 
NETCONF Working Group K. Watsen NETCONF Working Group K. Watsen
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Standards Track July 21, 2015 Intended status: Standards Track September 22, 2015
Expires: January 22, 2016 Expires: March 25, 2016
NETCONF Call Home and RESTCONF Call Home NETCONF Call Home and RESTCONF Call Home
draft-ietf-netconf-call-home-09 draft-ietf-netconf-call-home-10
Abstract Abstract
This RFC presents NETCONF Call Home and RESTCONF Call Home, which This RFC presents NETCONF Call Home and RESTCONF Call Home, which
enable a NETCONF or RESTCONF server to initiate a secure connection enable a NETCONF or RESTCONF server to initiate a secure connection
to a NETCONF or RESTCONF client respectively. to a NETCONF or RESTCONF client respectively.
Editorial Note (To be removed by RFC Editor) Editorial Note (To be removed by RFC Editor)
This draft contains many placeholder values that need to be replaced This draft contains many placeholder values that need to be replaced
with finalized values at the time of publication. This note with finalized values at the time of publication. This note
summarizes all of the substitutions that are needed. Please note summarizes all of the substitutions that are needed. Please note
that no other RFC Editor instructions are specified anywhere else in that no other RFC Editor instructions are specified anywhere else in
this document. this document.
Artwork in this document contains placeholder references for this Artwork in this document contains placeholder references for this
draft. Please apply the following replacement: draft. Please apply the following replacement:
o "XXXX" --> the assigned RFC value for this draft o "XXXX" --> the assigned RFC value for this draft
This document contains references to other drafts in progress, both This document contains references to another drafts in progress, both
in the Normative References section, as well as in body text in the Normative References section, as well as in body text
throughout. Please update the following references to reflect their throughout. Please update the following reference to reflect its
final RFC assignments: final RFC assignment:
o draft-ietf-netconf-restconf o draft-ietf-netconf-restconf
o draft-ietf-netconf-server-model
Artwork in this document contains placeholder values for ports Artwork in this document contains placeholder values for ports
pending IANA assignment from "draft-ietf-netconf-call-home". Please pending IANA assignment from "draft-ietf-netconf-call-home". Please
apply the following replacements: apply the following replacements:
o "PORT-X" --> the assigned port value for "netconf-ch-ssh" o "PORT-X" --> the assigned port value for "netconf-ch-ssh"
o "PORT-Y" --> the assigned port value for "netconf-ch-tls" o "PORT-Y" --> the assigned port value for "netconf-ch-tls"
o "PORT-Z" --> the assigned port value for "restconf-ch-tls" o "PORT-Z" --> the assigned port value for "restconf-ch-tls"
The following two Appendix sections are to be removed prior to The following two Appendix sections are to be removed prior to
publication: publication:
o Appendix A. Change Log o Appendix A. Change Log
o Appendix B. Open Issues o Appendix B. Open Issues
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 2, line 26 skipping to change at page 2, line 24
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 January 22, 2016. This Internet-Draft will expire on March 25, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 4, line 43 skipping to change at page 4, line 39
network IP addresses. network IP addresses.
o The network element may be deployed behind a firewall that doesn't o The network element may be deployed behind a firewall that doesn't
allow any management access to the internal network. allow any management access to the internal network.
o The network element may be configured in "stealth mode" and thus o The network element may be configured in "stealth mode" and thus
doesn't have any open ports for the management system to connect doesn't have any open ports for the management system to connect
to. to.
o The operator may prefer to have network elements initiate o The operator may prefer to have network elements initiate
management connections, believing it is easier to secure one open- management connections, believing it is easier to secure one open
port in the data center than to have an open port on each network port in the data center than to have an open port on each network
element in the network. element in the network.
1.2. Requirements Terminology 1.2. Requirements Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
1.3. Applicability Statement 1.3. Applicability Statement
skipping to change at page 6, line 4 skipping to change at page 5, line 48
1.5. The NETCONF/RESTCONF Convention 1.5. The NETCONF/RESTCONF Convention
Throughout the remainder of this document, the term "NETCONF/ Throughout the remainder of this document, the term "NETCONF/
RESTCONF" is used as an abbreviation in place of the text "the RESTCONF" is used as an abbreviation in place of the text "the
NETCONF or the RESTCONF". The NETCONF/RESTCONF abbreviation is not NETCONF or the RESTCONF". The NETCONF/RESTCONF abbreviation is not
intended to require or to imply that a client or server must intended to require or to imply that a client or server must
implement both the NETCONF standard and the RESTCONF standard. implement both the NETCONF standard and the RESTCONF standard.
2. The NETCONF or RESTCONF Client 2. The NETCONF or RESTCONF Client
The term "NETCONF/RESTCONF client" can refer to the [RFC6241],
Section 1.1 "client".
2.1. Protocol Operation 2.1. Protocol Operation
C1 The NETCONF/RESTCONF client listens for TCP connection requests C1 The NETCONF/RESTCONF client listens for TCP connection requests
from NETCONF/RESTCONF servers. The client SHOULD listen for from NETCONF/RESTCONF servers. The client SHOULD listen for
connections on the IANA-assigned ports defined in section connections on the IANA-assigned ports defined in section
Section 5, but MAY be configured to use a non-standard port. Section 5, but MAY be configured to use a non-standard port.
C2 The NETCONF/RESTCONF client accepts an incoming TCP connection C2 The NETCONF/RESTCONF client accepts an incoming TCP connection
request and a TCP connection is established. request and a TCP connection is established.
skipping to change at page 7, line 18 skipping to change at page 7, line 18
2.2. Configuration Data Model 2.2. Configuration Data Model
How a NETCONF or RESTCONF client is configured is outside the scope How a NETCONF or RESTCONF client is configured is outside the scope
of this document. This includes configuration that might be used to of this document. This includes configuration that might be used to
enable listening for call home connections, configuring trust enable listening for call home connections, configuring trust
anchors, or configuring identifiers for expected connections. anchors, or configuring identifiers for expected connections.
3. The NETCONF or RESTCONF Server 3. The NETCONF or RESTCONF Server
The term "NETCONF/RESTCONF server" can refer to the [RFC6241],
Section 1.1 "server".
3.1. Protocol Operation 3.1. Protocol Operation
S1 The NETCONF/RESTCONF server initiates a TCP connection request to S1 The NETCONF/RESTCONF server initiates a TCP connection request to
the NETCONF/RESTCONF client. The server SHOULD connect to one of the NETCONF/RESTCONF client. The server SHOULD connect to one of
the IANA-assigned ports defined in section Section 5, but MAY be the IANA-assigned ports defined in section Section 5, but MAY be
configured to use a non-standard port. Using the IANA-assigned configured to use a non-standard port. Using the IANA-assigned
ports, the server connects to port PORT-X for NETCONF over SSH, ports, the server connects to port PORT-X for NETCONF over SSH,
port PORT-Y for NETCONF over TLS, and port PORT-Z for RESTCONF port PORT-Y for NETCONF over TLS, and port PORT-Z for RESTCONF
over TLS. over TLS.
 End of changes. 10 change blocks. 
10 lines changed or deleted 16 lines changed or added

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