Re: [Pce] I-D Action: draft-ietf-pce-association-bidir-07.txt

Hi Rakesh,

In Figures 2 and 4 of the latest update, the addition of the PLSP-ID
corresponding to the PCInitiate message is misleading. As per RFC
8281, the PCInitiate message carries PLSP-ID as 0 and it is the PCC
that allocates the PLSP-ID.

One option would be to show the PLSP-ID as part of the LSPDB inside
the box rather than on the flight (i.e. move the PLSP-ID part
corresponding to the node A and D instead of the arrow). Or break it
into two figures - first a PCInitiate message with PLSP-ID 0 and then
a PCC reporting with the PLSP-ID.

Thanks!
Dhruv

On Wed, Sep 9, 2020 at 11:36 PM <internet-drafts@ietf.org> wrote:
>
>
> 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 Extensions for Associated Bidirectional Label Switched Paths (LSPs)
>         Authors         : Rakesh Gandhi
>                           Colby Barth
>                           Bin Wen
>         Filename        : draft-ietf-pce-association-bidir-07.txt
>         Pages           : 19
>         Date            : 2020-09-09
>
> Abstract:
>    The Path Computation Element Communication Protocol (PCEP) provides
>    mechanisms for Path Computation Elements (PCEs) to perform path
>    computations in response to Path Computation Clients (PCCs) requests.
>    The Stateful PCE extensions allow stateful control of Multiprotocol
>    Label Switching (MPLS) Traffic Engineering (TE) Label Switched Paths
>    (LSPs) using PCEP.
>
>    This document defines PCEP extensions for grouping two unidirectional
>    MPLS TE LSPs (one in each direction in the network) into an
>    Associated Bidirectional LSP.  The mechanisms defined in this
>    document can be applied using a Stateful PCE for both PCE-Initiated
>    and PCC-Initiated LSPs, as well as when using a Stateless PCE.  The
>    procedures defined are applicable to the LSPs using Resource
>    Reservation Protocol (RSVP) for signaling.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-pce-association-bidir/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-pce-association-bidir-07
> https://datatracker.ietf.org/doc/html/draft-ietf-pce-association-bidir-07
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-association-bidir-07
>
>
> 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