[Idr] Shepherd's report on draft-ietf-idr-bgp-ct-srv6-00

[Susan Hares <[e-mail]>]

Shepherd's report on draft-ietf-idr-bgp-ct-srv6-00
Date: 1/25/2023

Status: 3 technical Issues, 3 editorial issues


Technical issue:

1. End.Replace - in draft-salih-spring-srv6-inter-domain-sids

type End.Replace - is specified in
draft-salih-spring-srv6-03 (which is an individual draft).

At this point, the

2.  I'm missing something in section 5.1

Text:
  EBGP CT routes from ASBR2 to ASBR1

      RD1:PE2-LPBK,
        transport-target:0:100,
        Prefix-SID: ASBR2-SRv6-PE2-gold-Replace,
        NH: ASBR2_InterAS_Link

      RD2:PE2-LPBK,
        transport-target:0:200,
        Prefix-SID: ASBR2-SRv6-PE2-bronze-Replace,
        NH: ASBR2_InterAS_Link
/
Where: Where is the next hop set to ASBR2_InterAS_Link
Is it in this paragraph:

   "The BGP CT routes for RD1:PE2-LPBK is further advertised
   towards ASBR1 via EBGP CT as follows.  During this readvertisement,
   the next hop is set to self, and SID is rewritten to ASBR2-SRv6-gold-
   Replace."

3.  Section 5.2 -

Is there a reason you did not indicate how CPR works with CT?

It seems like it is in the following text:

Current text:/
   CPR achieves strict Intent based forwarding for the service routes.
   Fallback to best effort transport class is achieved by numbering all
   SRv6 Colorful Prefix locators at the egress SN to fall in the same
   subnet as the SRv6 locator that uses best effort transport class.
   Customized intent fallback between different color transport classes
   may be achieved by allocating a CPR prefix for each such intent
   fallback policy, and advertising that CPR prefix with an appropriate
   mapping community, that maps to a customized resolution scheme.
   Alternatively, the intent fallback policy may be provisioned on the
   ingress nodes directly.

/

============================
Editorial:

#1 - section 2, Terminology

Please Alphabetize the abbreviations.
Please Alphabetize the definitions.

#2 - Section 2, Definitions

2a:
Old text:/
   Import processing: Receive side processing of an overlay route,
   including things like import policy application, resolution scheme
   selection and nexthop resolution.
   /

New text/
   Import processing: The receive side processing of an overlay route,
   which includes things like import policy application, resolution scheme
   selection and nexthop resolution.
   /

2b:
Old text:/
   Transport Tunnel : A tunnel over which a service may place traffic.
   Such a tunnel can be provisioned or signaled using a variety of means
   (e.g., Generic Routing Encapsulation (GRE), UDP, LDP, RSVP-TE, IGP
   FLEX-ALGO or SRTE).
/

 New text:/
    Transport Tunnel: A tunnel over which a service may send traffic.
   Such a tunnel can be provisioned or signaled using a variety of means
   (e.g., Generic Routing Encapsulation (GRE), UDP, LDP, RSVP-TE, IGP
   FLEX-ALGO or SRTE).
/


#3 - Section 3,

3a:
Old Text/
   The procedures for encoding a BGP Classful Transport (BGP CT) family
   route are specified in sections 6, section 4 in [BGP-CT].  These are
   followed, with the addition of SRv6 encapsulation information.
   /

New Text: /
   The procedures for encoding a BGP Classful Transport (BGP CT) family
   route are specified in sections 4 and 6 [BGP-CT].  These are
   followed, with the addition of SRv6 encapsulation information.
  /