RFC 7589 on Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication
rfc-editor@rfc-editor.org Sat, 20 June 2015 00:22 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6618A1A9153; Fri, 19 Jun 2015 17:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lqVEGH0IKe2B; Fri, 19 Jun 2015 17:22:39 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 552931A90A1; Fri, 19 Jun 2015 17:22:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C912D180205; Fri, 19 Jun 2015 17:19:44 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7589 on Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150620001944.C912D180205@rfc-editor.org>
Date: Fri, 19 Jun 2015 17:19:44 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/1bXb7ukaO8zaNBLd33BbHv6SzoI>
Cc: drafts-update-ref@iana.org, netconf@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Jun 2015 00:22:41 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7589
Title: Using the NETCONF Protocol over
Transport Layer Security (TLS) with Mutual
X.509 Authentication
Author: M. Badra, A. Luchuk, J. Schoenwaelder
Status: Standards Track
Stream: IETF
Date: June 2015
Mailbox: mohamad.badra@zu.ac.ae,
luchuk@snmp.com,
j.schoenwaelder@jacobs-university.de
Pages: 11
Characters: 22727
Obsoletes: RFC 5539
I-D Tag: draft-ietf-netconf-rfc5539bis-10.txt
URL: https://www.rfc-editor.org/info/rfc7589
DOI: http://dx.doi.org/10.17487/RFC7589
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.
This document is a product of the Network Configuration Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC