Re: RFC 8253 on PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)
Ranga Sam <ranga.sam@me.com> Sat, 21 October 2017 03:06 UTC
Return-Path: <ranga.sam@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 08DEE134215
for <ietf@ietfa.amsl.com>; Fri, 20 Oct 2017 20:06:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7,
RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=me.com
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 ldnN7NUAbXzT for <ietf@ietfa.amsl.com>;
Fri, 20 Oct 2017 20:06:34 -0700 (PDT)
Received: from pv33p03im-asmtp001.me.com (pv33p03im-asmtp001.me.com
[17.143.180.10])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 76FED13420B
for <ietf@ietf.org>; Fri, 20 Oct 2017 20:06:34 -0700 (PDT)
Received: from process-dkim-sign-daemon.pv33p03im-asmtp001.me.com by
pv33p03im-asmtp001.me.com
(Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7
2017)) id <0OY500500K3YF200@pv33p03im-asmtp001.me.com> for ietf@ietf.org; Sat,
21 Oct 2017 03:06:34 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017;
t=1508555194; bh=pbglt7Frnojm7NOOjQsrt0kowvZvyv6jyMxuwj6SN60=;
h=Content-type:MIME-version:Subject:From:Date:Message-id:To;
b=OM2ID07lHrPkjpKmmO97x5v6do6Vfsz2fvk1Rg/+WURzfmpFxTMVAMBHRVWExLU85
gydgjixM4oizLdRGbW5HbV1ToYrADWidGDIBQILKPfIoSRvZp02OgZFYJNZXv4Icwj
Ezv7sZvHk57NtOgQnF5vhCekXlwV4kLoea67+9HcMvlcU33MWvOnkq1aUj2qWXbWXK
ek0P1njJ3Y0f5E0b9p7/qX4XQ5+/vy4lEX6yWcCE8+8Gbv82hNApBtiMPHQnOyp3xw
rianZb35XFY4WO7QEjPk+w84nOEpvcEiEPq7Hw3Uyxuddp9sd26PBjqGtOcW8PlK73
NZuprcERkZ/5A==
Received: from icloud.com ([127.0.0.1]) by pv33p03im-asmtp001.me.com
(Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7
2017)) with ESMTPSA id <0OY5003YBKMWAQ00@pv33p03im-asmtp001.me.com> for
ietf@ietf.org; Sat, 21 Oct 2017 03:06:33 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,,
definitions=2017-10-20_11:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0
clxscore=1011 suspectscore=3 malwarescore=0 phishscore=0 adultscore=0
bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1
engine=8.0.1-1707230000 definitions=main-1710210045
Content-type: text/plain; charset=us-ascii
MIME-version: 1.0 (1.0)
Subject: Re: RFC 8253 on PCEPS: Usage of TLS to Provide a Secure Transport for
the Path Computation Element Communication Protocol (PCEP)
From: Ranga Sam <ranga.sam@me.com>
X-Mailer: iPhone Mail (15A432)
In-reply-to: <20171020234222.71863B80D5A@rfc-editor.org>
Date: Fri, 20 Oct 2017 23:06:31 -0400
Content-transfer-encoding: quoted-printable
Message-id: <BC94FD5A-2D8F-40C5-97F7-AB51C991CB37@me.com>
References: <20171020234222.71863B80D5A@rfc-editor.org>
To: ietf@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZQ20XoOp-AfCwxbwRNTD694zwPs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>,
<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>,
<mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Oct 2017 03:06:36 -0000
Unsubscribe Sent from my iPhone > On Oct 20, 2017, at 7:42 PM, rfc-editor@rfc-editor.org wrote: > > 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 > >