RFC 8253 on PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)

rfc-editor@rfc-editor.org Fri, 20 October 2017 23:42 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E08D134452; Fri, 20 Oct 2017 16:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 qIl8Nv5guZct; Fri, 20 Oct 2017 16:42:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B4D3134322; Fri, 20 Oct 2017 16:42:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 71863B80D5A; Fri, 20 Oct 2017 16:42:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8253 on PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, pce@ietf.org
Message-Id: <20171020234222.71863B80D5A@rfc-editor.org>
Date: Fri, 20 Oct 2017 16:42:22 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/0eOtcuTTe8g4G_bsgSnwwe2ipl4>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 20 Oct 2017 23:42:50 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8253

        Title:      PCEPS: Usage of TLS to 
                    Provide a Secure Transport for the 
                    Path Computation Element Communication Protocol (PCEP) 
        Author:     D. Lopez, 
                    O. Gonzalez de Dios,
                    Q. Wu, 
                    D. Dhody
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2017
        Mailbox:    diego.r.lopez@telefonica.com, 
                    oscar.gonzalezdedios@telefonica.com, 
                    sunseawq@huawei.com,  
                    dhruv.ietf@gmail.com
        Pages:      26
        Characters: 56767
        Updates:    RFC 5440

        I-D Tag:    draft-ietf-pce-pceps-18.txt

        URL:        https://www.rfc-editor.org/info/rfc8253

        DOI:        10.17487/RFC8253

The Path Computation Element Communication Protocol (PCEP) defines
the mechanisms for the communication between a Path Computation
Client (PCC) and a Path Computation Element (PCE), or among PCEs.
This document describes PCEPS -- the usage of Transport Layer
Security (TLS) to provide a secure transport for PCEP.  The
additional security mechanisms are provided by the transport protocol
supporting PCEP; therefore, they do not affect the flexibility and
extensibility of PCEP.

This document updates RFC 5440 in regards to the PCEP initialization
phase procedures.

This document is a product of the Path Computation Element 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/retrieve/bulk

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