Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication
RFC 7589
| Document | Type |
RFC - Proposed Standard
(June 2015; No errata)
Obsoletes RFC 5539
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-badra-netconf-rfc5539bis | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Mehmet Ersue | ||
| Shepherd write-up | Show (last changed 2015-02-19) | ||
| IESG | IESG state | RFC 7589 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Benoît Claise | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) M. Badra
Request for Comments: 7589 Zayed University
Obsoletes: 5539 A. Luchuk
Category: Standards Track SNMP Research, Inc.
ISSN: 2070-1721 J. Schoenwaelder
Jacobs University Bremen
June 2015
Using the NETCONF Protocol over Transport Layer Security (TLS)
with Mutual X.509 Authentication
Abstract
The Network Configuration Protocol (NETCONF) provides mechanisms to
install, manipulate, and delete the configuration of network devices.
This document describes how to use the Transport Layer Security (TLS)
protocol with mutual X.509 authentication to secure the exchange of
NETCONF messages. This revision of RFC 5539 documents the new
message framing used by NETCONF 1.1 and it obsoletes RFC 5539.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7589.
Badra, et al. Standards Track [Page 1]
RFC 7589 NETCONF over TLS June 2015
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Connection Initiation . . . . . . . . . . . . . . . . . . . . 3
3. Message Framing . . . . . . . . . . . . . . . . . . . . . . . 3
4. Connection Closure . . . . . . . . . . . . . . . . . . . . . 4
5. Certificate Validation . . . . . . . . . . . . . . . . . . . 4
6. Server Identity . . . . . . . . . . . . . . . . . . . . . . . 4
7. Client Identity . . . . . . . . . . . . . . . . . . . . . . . 4
8. Cipher Suites . . . . . . . . . . . . . . . . . . . . . . . . 6
9. Security Considerations . . . . . . . . . . . . . . . . . . . 7
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
11.1. Normative References . . . . . . . . . . . . . . . . . . 8
11.2. Informative References . . . . . . . . . . . . . . . . . 9
Appendix A. Changes from RFC 5539 . . . . . . . . . . . . . . . 10
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
Badra, et al. Standards Track [Page 2]
RFC 7589 NETCONF over TLS June 2015
1. Introduction
The NETCONF protocol [RFC6241] defines a mechanism through which a
network device can be managed. NETCONF is connection-oriented,
requiring a persistent connection between peers. This connection
must provide integrity, confidentiality, peer authentication, and
reliable, sequenced data delivery.
This document defines how NETCONF messages can be exchanged over
Transport Layer Security (TLS) [RFC5246]. Implementations MUST
support mutual TLS certificate-based authentication [RFC5246]. This
assures the NETCONF server of the identity of the principal who
wishes to manipulate the management information. It also assures the
NETCONF client of the identity of the server for which it wishes to
manipulate the management information.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. Connection Initiation
The peer acting as the NETCONF client MUST act as the TLS client.
The TLS client actively opens the TLS connection and the TLS server
Show full document text