search

ietf-wg-idr / draft-ietf-idr-sr-policy-safi

Repository for draft-ietf-idr-sr-policy-safi Issues
0 stars 0 forks source link

### RTG-DIR Issue-13: Section 2.4.2, paragraph 3 - Binding SID + SRv6 Binding SID SubTLVs #15

Closed suehares closed 3 months ago

suehares commented 4 months ago

RTG-DIR Issue-13: Section 2.4.2, paragraph 3 - Binding SID + SRv6 Binding SID SubTLVs

Section 2.4.2, paragraph 3 Text:/ When the Binding SID sub-TLV is used to signal an SRv6 SID, the choice of its SRv6 Endpoint Behavior [RFC8986] to be instantiated is left to the headend node. It is RECOMMENDED that the SRv6 Binding SID sub-TLV defined in Section 2.4.3, that enables the specification of the SRv6 Endpoint Behavior, be used for signaling of an SRv6 Binding SID for an SR Policy candidate path./

Jeffrey: Is there a choice here? Shouldn't the behavior be that traffic with that Binding SID is steered into this policy? The whole paragraph is hard to parse.

KT What is meant by SRv6 Endpoint behavior is specified in RFC8986 - e.g., End.B6.Encaps, End.B6.Encaps.Red, and others could be defined in the future.

Shepherd: Suggested editorial change: / When the Binding SID sub-TLV is used to signal an SRv6 SID, the choice of its SRv6 Endpoint Behavior [RFC8986] to be instantiated is left to the headend node. It is RECOMMENDED that the SRv6 Binding SID sub-TLV (defined in Section 2.4.3) be used to signal an SRv6 Binding SID for an SR Policy candidate path./

Why change: Sentence clarity. Note: Bold indicates change.

suehares commented 3 months ago

-04.txt Status: Closed, added to -04 Shepherd's issue (issue 32) https://github.com/ietf-wg-idr/draft-ietf-idr-sr-policy-safi/issues/32