Hi WG,
draft-ietf-pce-binding-label-sid defines 2 flags in TE-PATH-BINDING TLV -
o S-Flag: This flag encodes the "Specified-BSID-only" behavior. It
is used as described in Section 6.2.3 of
[I-D.ietf-spring-segment-routing-policy].
o I-Flag: This flag encodes the "Drop Upon
Thanks again for your help!
Cheng
-Original Message-
From: Stone, Andrew (Nokia - CA/Ottawa) [mailto:andrew.st...@nokia.com]
Sent: Saturday, March 27, 2021 2:42 AM
To: Chengli (Cheng Li) ; julien.meu...@orange.com; pce@ietf.org
Cc: draft-ietf-pce-binding-label-...@ietf.org
Subject:
Hi Cheng,
Thanks for clarifying the text in the document. Diff content looks good to me,
much clearer. Consider my comments resolved.
Thanks!
Andrew
On 2021-03-25, 10:49 PM, "Pce on behalf of Chengli (Cheng Li)"
wrote:
Hi Andrew,
Thanks for your comments, please see my reply
Hi all,
After discussing with Tom and the authors, we believe that a reasonable
way to progress this early allocation is to postpone the allocation of
the error codes. We'll proceed accordingly.
Enjoy the week-end,
Dhruv & Julien
On 01/02/2021 11:54, julien.meu...@orange.com wrote:
> Hi WG,
>
Hi Tom,
As agreed with the authors, we'll proceed with the early allocation
request by leaving the error codes pending upcoming updates (i.e.
request allocation for PCEP TLV and LSP object flags). This will leave
you some time to find an agreement on the final wording of the error
messages.
Hi Cheng!
This is good progress, thanks.
I have cut down to the points that are still open.
Nothing we need to fight about
Best,
Adrian
>> == Questions / Issues ==
>>
>> 3.
>>
>> o BT = 0: The binding value is an MPLS label carried in the format
>> specified in [RFC5462] where only
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 : PCEP Extension for Native IP Network
Authors : Aijun Wang
Boris Khasanov
Hi Hooman,
With my chair hat off and speaking as a WG participant. Thanks for
explaining your point of view and the history.
The PCEP stateful messages are currently being used for -
- LSP operations (LSP instruction/reports to/from head end i.e. stateful
PCE)
- PCECC operations (generic
To all,
The latest diff of BSID draft is
https://tools.ietf.org/rfcdiff?url1=https://www.ietf.org/archive/id/draft-ietf-pce-binding-label-sid-07.txt=https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-binding-label-sid-08.txt
Sorry for using the wrong diff file.
Thanks,
Hi Tom,
Sorry for sending the error diff.
The latest diff is here
https://tools.ietf.org/rfcdiff?url1=https://www.ietf.org/archive/id/draft-ietf-pce-binding-label-sid-07.txt=https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-binding-label-sid-08.txt
Also, Julien has
Oh, Adrian, all,
some update for comment 4, Regarding multiple TE-PATH-BINDING TLVs, we have
updated the operation rules as follow.
In case of multiple TE-PATH-BINDING TLVs, all
existing instances of TE-PATH-BINDING TLVs MUST always be included in
the LSP object. In case of an error
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 : PCEP Procedures and Protocol Extensions for Using PCE
as a Central Controller (PCECC) for Segment Routing (SR)
12 matches
Mail list logo