search

ietf-wg-idr / draft-ietf-idr-bgp-ct

1 stars 2 forks source link

2nd WG LC draft-ietf-idr-bgp-ct-srv6 - Q3 issues - English Editorial issues in main text. #68

Closed suehares closed 3 months ago

suehares commented 4 months ago

Q3 issues - English Editorial issues in the main draft-ietf-idr-bgp-ct-srv6 text.

Q3-01 - Section 3, paragraph 4 - use And

old text:/ Aspects regarding Interoperability between nodes supporting different forwarding technologies is discussed in Section 6.3, Section 11.3.2 of [BGP-CT]. / New text:/ Aspects regarding Interoperability between nodes supporting different forwarding technologies is discussed in Section 6.3 and Section 11.3.2 of [BGP-CT].

Q3-02 - section 5.1, paragraph begining "Futhermore".

I recommend removing "Furthermore" and starting the paragraph "Any service". Starting two paragraphs "Furthermore" and then "Similarly", IMHO seems to be stilted English.

Old text:/ Furthermore, any service routes received with next hop as PE2-LPBK and Mapping Community as Color:0:100 indicating Gold SLA will use the Resolution Scheme associated with its Mapping Community to resolve over the PE2-LPBK CT route installed in the gold TRDB, and push the SRv6-gold SID stack to reach PE2. /

Q3-04, Section 5.1, 2 line wraps need to be fixed, and spelling error (replace)

old text:/ PE1: Service routes FIB

  [BGP INET] SVC_PFX1, color:0:100
    NH: EncapSID "PE2-SRv6-S1-DT4, ASBR1-SRv6-gold-**Repace**, Gold-SRv6-Tunnel-to-ASBR1(outer)"

  [BGP INET] SVC_PFX2, color:0:200
    NH: EncapSID "PE2-SRv6-S1-DT4, ASBR1-SRv6-bronze-Replace, Bronze-SRv6-Tunnel-to-ASBR1(outer)"

/ New text:/ PE1: Service routes FIB

  [BGP INET] SVC_PFX1, color:0:100
    NH: EncapSID "PE2-SRv6-S1-DT4, ASBR1-SRv6-gold-Replace,
            Gold-SRv6-Tunnel-to-ASBR1(outer)"

  [BGP INET] SVC_PFX2, color:0:200
    NH: EncapSID "PE2-SRv6-S1-DT4, ASBR1-SRv6-bronze-Replace, 
    Bronze-SRv6-Tunnel-to-ASBR1(outer)"

/

suehares commented 3 months ago

closed based on draft-ietf-idr-bgp-ct-27.