RTG-DIR Issue 22: Section 2.4.4.2.4 - SRv6 SID Endpoint Behavior vs. RFC9252 "SRv6 SID Structure Sub-Sub-TLV"

[suehares]

RTG-DIR Issue 22: Section 2.4.4.2.4 - SRv6 SID Endpoint Behavior vs. RFC9252 "SRv6 SID Structure Sub-Sub-TLV"

Text:/ 2.4.4.2.4. SRv6 SID Endpoint Behavior and Structure

The Segment Types sub-TLVs described above MAY contain the SRv6 Endpoint Behavior and SID Structure [RFC8986] encoding as described below: 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Endpoint Behavior | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LB Length | LN Length | Fun. Length | Arg. Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Figure 23: SRv6 SID Endpoint Behavior and Structure

where:

  Endpoint Behavior: 2 octets.  It carries the SRv6 Endpoint
  Behavior code point for this SRv6 SID as defined in section 9.2 of
  [RFC8986].  When set with the value 0xFFFF (i.e., Opaque), the
  choice of SRv6 Endpoint Behavior is left to the headend.

  Reserved: 2 octets of reserved bits.  This field MUST be set to
  zero on transmission and MUST be ignored on receipt.

  Locator Block Length: 1 octet.  SRv6 SID Locator Block length in
  bits.

  Locator Node Length: 1 octet.  SRv6 SID Locator Node length in
  bits.

  Function Length: 1 octet.  SRv6 SID Function length in bits.

  Argument Length: 1 octet.  SRv6 SID Arguments length in bits.

/end text

Jeffrey: How is this different from the "SRv6 SID Structure Sub-Sub-TLV" in RFC9252? Why not reuse that one?

Ketan: There is no need for transposition related fields here and this is a different TLV space anyway. https://mailarchive.ietf.org/arch/msg/rtg-dir/v000LQ8UZWJg-IR2-WnJqaki394/

[suehares]

RTG-DIR Issue-22 status in -04.txt: Resolved, Closed