RFC 7150 on Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol
rfc-editor@rfc-editor.org Tue, 04 March 2014 11:23 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 B16681A0722; Tue, 4 Mar 2014 03:23:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 xGmGqCYUJ0Mj; Tue, 4 Mar 2014 03:23:41 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 016D11A070A; Tue, 4 Mar 2014 03:23:41 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DFC927FC3AC; Tue, 4 Mar 2014 03:23:37 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7150 on Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol
From: rfc-editor@rfc-editor.org
Message-Id: <20140304112337.DFC927FC3AC@rfc-editor.org>
Date: Tue, 04 Mar 2014 03:23:37 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/tENLSFs7IvWz2v2piuMYn4P0OhQ
Cc: drafts-update-ref@iana.org, pce@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: Tue, 04 Mar 2014 11:23:48 -0000
A new Request for Comments is now available in online RFC libraries. RFC 7150 Title: Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol Author: F. Zhang, A. Farrel Status: Standards Track Stream: IETF Date: March 2014 Mailbox: zhangfatai@huawei.com, adrian@olddog.co.uk Pages: 12 Characters: 24156 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pce-vendor-constraints-11.txt URL: http://www.rfc-editor.org/rfc/rfc7150.txt The Path Computation Element Communication Protocol (PCEP) is used to convey path computation requests and responses both between Path Computation Clients (PCCs) and Path Computation Elements (PCEs) and between cooperating PCEs. In PCEP, the path computation requests carry details of the constraints and objective functions that the PCC wishes the PCE to apply in its computation. This document defines a facility to carry vendor-specific information in PCEP using a dedicated object and a new Type-Length-Variable that can be carried in any existing PCEP object. 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 Internet Official Protocol Standards (STD 1) 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 http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/search For downloading RFCs, see http://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