Hi GROW (and cc TEAS, authors),

I’ve just requested IETF Last Call [1] for draft-ietf-teas-rfc3272bis-24 
("Overview and Principles of Internet Traffic Engineering”). In my AD review 
[2] I had several questions about Section 7, “Inter-Domain Considerations”. In 
particular, this one remains unresolved (this is a quote from the draft, 
followed by my comment, in case it’s unclear):

```
   When considering inter-domain TE with BGP, note that the outbound
   traffic exit point is controllable, whereas the interconnection point
   where inbound traffic is received typically is not.  Therefore, it is
   up to each individual network to implement TE strategies that deal
   with the efficient delivery of outbound traffic from its customers to
   its peering points.  The vast majority of TE policy is based on a
   "closest exit" strategy, which offloads inter-domain traffic at the
   nearest outbound peering point towards the destination AS.  Most
   methods of manipulating the point at which inbound traffic enters a
   are either ineffective, or not accepted in the peering community.
--
jgs: the last two sentences above seem to be [citation needed]. In 
particular, I had thought AS_PATH prepending was a pretty common 
practice. A very brief web search turned up a 2020 CAIDA paper that
seems to confirm this 
(https://www.caida.org/catalog/papers/2020_aspath_prepending/aspath_prepending.pdf)

At this point it occurs to me to ask whether the GROW WG was prompted
to review this section?
—
```

Adrian (the editor) suggested [3] that we solicit this input during IETF Last 
Call, which makes sense to me. So, please consider this your invitation to have 
a look at Section 7 and provide any feedback you may have.

Thanks in advance!

—John

[1] https://mailarchive.ietf.org/arch/msg/teas/agv93XBdaAcpONX6-AB42vROqF4/
[2] https://mailarchive.ietf.org/arch/msg/teas/rHvxm7Jv5j_btcNED5waqFgnKao/
[3] https://mailarchive.ietf.org/arch/msg/teas/fJrMWX0ZalySZjEiV8kNbr9wr60/
_______________________________________________
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow

Reply via email to