Comcast route server not reflecting their reality

• Subject: Comcast route server not reflecting their reality
• From: ross at tajvar.io (Ross Tajvar)
• Date: Wed, 11 Sep 2019 13:05:11 -0400
• In-reply-to: <[email protected]>
• References: <[email protected]> <MN2PR17MB40293[email protected]> <[email protected]> <CA[email protected]> <[email protected]>

>
> IIRC, Comcast uses "local-as 7922" path rewriting for all enterprise EDI
> customers
> running BGP off of regional CRANs, unless I'm mistaken.  So if your
> regional CRAN
> is as7015 (for New England), even if your physical circuit and BGP session
> land
> on a local SUR in your area, you have to use remote-as 7922 to setup the
> session
> with Comcast ENS, regardless of the fact that actual peer's router is
> using as7015.
>

This totally makes sense, thanks for the explanation!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190911/41593a03/attachment.html>

• References:
  • Comcast route server not reflecting their reality
    • From: will at loopfree.net (Will Orton)
  • Comcast route server not reflecting their reality
    • From: martijnschmidt at i3d.net (Martijn Schmidt)
  • Comcast route server not reflecting their reality
    • From: will at loopfree.net (Will Orton)
  • Comcast route server not reflecting their reality
    • From: ross at tajvar.io (Ross Tajvar)
  • Comcast route server not reflecting their reality
    • From: james.jun at towardex.com (James Jun)

• Prev by Date: Comcast route server not reflecting their reality
• Next by Date: Geolocation\VPN Assistance
• Previous by thread: Comcast route server not reflecting their reality
• Next by thread: Bahamas: Hurricane Dorian recovery status
• Index(es):
  • Date
  • Thread