### RTG-DIR Issue-14: Section 2.4.2 - Last paragraph:

[suehares]

RTG-DIR Issue-14: Section 2.4.2 - Last paragraph:

Text:/

• Binding SID: If the length is 2, then no Binding SID is present. If the length is 6 then the Binding SID is encoded in 4 octets using the format below. Traffic Class (TC), S, and TTL (Total of 12 bits) are RESERVED and MUST be set to zero and MUST be ignored.

   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
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |          Label                        | TC  |S|       TTL     |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Figure 6: Binding SID Label Encoding

  If the length is 18 then the Binding SID contains a 16-octet SRv6
  SID./ 

Jeffrey: Why do we need the a 16-octet Binding SID since we have the following "SRv6 Binding SID Sub-TLV"?

Ketan (KT2): We put it up front so it is more clear - putting it at the end may result in it being missed. This is an editorial thing and I prefer keeping it as is.

https://mailarchive.ietf.org/arch/msg/rtg-dir/uXLLj_Mpd6_DpvzgnOWBeqq7wvg/

Shepherd: Approved as editorial choice.

[suehares]

-04.txt Status: Closed as complete.