[Idr] draft-li-idr-bgpls-sr-policy-composite-path-09.txt

[Susan Hares <[e-mail]>]

The question at the microphone related to the discussion
on draft-jiang-idr-sr-policy-composite-path.


The draft-jiang-idr-sr-policy-composite-path does not specify
how the Color precedence works between the setting of
color in the BGP Update by three things:
1) Color extended community attribute
2) Color TLV
3) Segment list's Constituent SR Policy TLV - Color Sub-TLV

If I were an operator, I would like to BGP-LS
a) What color set by policy on the composite candidate path,
b) Where this color came from (Color Ext. Community,
   Color TLV in Tunnel Attribute, Segment List's
    Constituent SR Policy TLV).

Does your draft assume BGP and/or the SRPM saves this information?
If so, how does it query for this information?

Cheerily, Sue



Relevant text sections for reference:


draft-jiang-idr-sr-policy-composite-path text that applies:

      SR Policy SAFI NLRI: <Distinguisher, Policy-Color, Endpoint>
          Attributes:
              Tunnel Encaps Attribute (23)
                  Tunnel Type: SR Policy
                      Binding SID
                      SRv6 Binding SID
                      Preference
                      Priority
                      Policy Name
                      Policy Candidate Path Name
                      Explicit NULL Label Policy (ENLP)
                      Segment List
                          Weight
                          Segment
                          Segment
                          ...
                      Constituent SR Policy
                          Color
                          Weight
                          Fowarding Class
                      ...




   The Constituent SR Policy sub-TLV has the following format:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |      Type     |         Length              |     RESERVED    |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                             Color                             |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                             Weight                            |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                            sub-TLVs                           |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


                   Figure 1:  Constituent SR Policy sub-TLV format



draft-li-idr-bgpls-sr-policy-composite-path-09.txt

The Composite Candidate Path TLV is used to report the constituent SR
   policy(s) of a composite candidate path.  It is carried in the
   optional non-transitive BGP- LS Attribute defined in [RFC9552] and is
   associated with the SR Policy Candidate Path NLRI type.  Only a
   single instance of this TLV is advertised for a given candidate path.
   If multiple instances are present, then the first valid (i.e., not
   determined to be malformed as per section 8.2.2 of [RFC9552]) one is
   used and the rest are ignored. The TLV has following format:


   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |              Type             |             Length            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                            RESERVED                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                             Color                             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                             Weight                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                       Sub-TLVs (variable)                     //
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+