[Idr] Barry Leiba's No Objection on draft-ietf-idr-bgpls-segment-routing-epe-18: (with COMMENT)

[Barry Leiba via Datatracker <[e-mail]>]

Barry Leiba has entered the following ballot position for
draft-ietf-idr-bgpls-segment-routing-epe-18: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-segment-routing-epe/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Just editorial stuff...

Throughout: “i.e.” needs a comma after it.  So does “e.g.”.

— Section 1 —

   SR can be directly applied to either an MPLS dataplane (SR/MPLS) with
   no change on the forwarding plane or to a modified IPv6 forwarding

Make it “either to” so it’s parallel with the “or to” that comes later.

   centralized controller based BGP Egress Peer Engineering solution
   involving SR path computation using the BGP Peering Segments.  This
   use-case comprises of a centralized controller that learns the BGP

“Centralized-controller-based” is a compound adjective that needs to be
hyphenated.  “Use case” is a noun, and should not be hyphenated.  And
“comprises” should not have “of” after it (“consists of” would, though).