Hi Jon, Thanks for the update. One comment regarding this paragraph: "If the peer has sent no PATH-SETUP-TYPE-CAPABILITY TLV, then the PCEP speaker MUST infer that the peer supports path setup using at least RSVP-TE. The PCEP speaker MAY also infer that the peer supports other path setup types, but the means of inference are outside the scope of this document."
Why not enforcing here ? I mean if a PCEP speaker uses a PST that was not advertised in the capability TLV, the PST is rejected by a PCError. During the OPEN message, peers may agree on the PST to be used on the session based on the common subset. What's your opinion on that ? Brgds, Stephane -----Original Message----- From: Jonathan Hardwick [mailto:jonathan.hardw...@metaswitch.com] Sent: Monday, November 20, 2017 16:07 To: pce@ietf.org Cc: MEURIC Julien IMT/OLN; LITKOWSKI Stephane OBS/OINIS Subject: FW: [Pce] I-D Action: draft-ietf-pce-lsp-setup-type-06.txt Dear PCE WG This new revision of the LSP setup type draft makes the following changes. 1) Added a capability TLV for the OPEN object and rules for processing it, as discussed in the attached thread. This is to address Julien's WGLC comment that there was no way for a PCEP speaker to express that it doesn't support RSVP-TE as a path setup type. 2) Made the path setup type explicit for anything other than RSVP-TE paths (where absence of TLV implies RSVP-TE). This is to address Stephane's recent comment to the list. 3) Updated the IANA / code point text to reflect that we have had an early allocation. 4) Made some editorial fixes and clarifications. Best regards Jon -----Original Message----- From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of internet-dra...@ietf.org Sent: 20 November 2017 14:59 To: i-d-annou...@ietf.org Cc: pce@ietf.org Subject: [Pce] I-D Action: draft-ietf-pce-lsp-setup-type-06.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Path Computation Element WG of the IETF. Title : Conveying path setup type in PCEP messages Authors : Siva Sivabalan Jeff Tantsura Ina Minei Robert Varga Jon Hardwick Filename : draft-ietf-pce-lsp-setup-type-06.txt Pages : 10 Date : 2017-11-20 Abstract: A Path Computation Element can compute traffic engineering paths (TE paths) through a network that are subject to various constraints. Currently, TE paths are label switched paths (LSPs) which are set up using the RSVP-TE signaling protocol. However, other TE path setup methods are possible within the PCE architecture. This document proposes an extension to PCEP to allow support for different path setup methods over a given PCEP session. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-pce-lsp-setup-type/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-pce-lsp-setup-type-06 https://datatracker.ietf.org/doc/html/draft-ietf-pce-lsp-setup-type-06 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-lsp-setup-type-06 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce
