[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nanog
Subject:    Re: BGP - Traffic Management
From:       Ross Tajvar <ross () tajvar ! io>
Date:       2021-08-20 3:58:34
Message-ID: CA+FDdDQjnba8ciCHxWEnU-i0+=JSevGgsbCW_iZNX-oPo0QO9g () mail ! gmail ! com
[Download RAW message or body]

Atlantic Metro (now 365 Datacenters) AS29838 allows more specifics on our
backbone. We filter outbound to transit and peering obviously, but we allow
e.g. granular steering if you have more than one port with us.

On Thu, Aug 19, 2021, 1:23 PM Ryan Hamel <administrator@rkhtech.org> wrote:

> Hello,
>
>
>
> Does anyone know of any US carriers that will accept more specific routes
> other than what's required for the DFZ, like "le 31" or "upto /31" (junos
> speak) ? I know Zayo supports this internally but would like to know of
> other carriers for redundancy.
>
>
>
> I am currently dealing with a network that has per region assigned public
> IP blocks. I would like to see about moving to announcing aggregates to the
> carriers across the MPLS network and redistributing more specifics from
> iBGP to the carriers to get the traffic where it needs to be. In a failover
> situation these more specifics are also visible on an MPLS backbone where
> other transit routers will prepend the AS path upstream based on specific
> communities to prevent anycast routing.
>
>
>
> Thanks,
>
>
>
> Ryan
>

[Attachment #3 (text/html)]

<div dir="auto">Atlantic Metro (now 365 Datacenters) AS29838 allows more specifics on \
our backbone. We filter outbound to transit and peering obviously, but we allow e.g. \
granular steering if you have more than one port with us.</div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Aug 19, 2021, 1:23 PM \
Ryan Hamel &lt;<a href="mailto:administrator@rkhtech.org">administrator@rkhtech.org</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="#0563C1" \
vlink="#954F72" style="word-wrap:break-word"><div \
class="m_-3747963294620653837WordSection1"><p class="MsoNormal"><span \
style="font-family:&quot;Open \
Sans&quot;,sans-serif">Hello,<u></u><u></u></span></p><p class="MsoNormal"><span \
style="font-family:&quot;Open Sans&quot;,sans-serif"><u></u>  <u></u></span></p><p \
class="MsoNormal"><span style="font-family:&quot;Open Sans&quot;,sans-serif">Does \
anyone know of any US carriers that will accept more specific routes other than \
what's required for the DFZ, like "le 31" or "upto /31" (junos speak) ? I know Zayo \
supports this internally but would like to know of other carriers for \
redundancy.<u></u><u></u></span></p><p class="MsoNormal"><span \
style="font-family:&quot;Open Sans&quot;,sans-serif"><u></u>  <u></u></span></p><p \
class="MsoNormal"><span style="font-family:&quot;Open Sans&quot;,sans-serif">I am \
currently dealing with a network that has per region assigned public IP blocks. I \
would like to see about moving to announcing aggregates to the carriers across the \
MPLS network and redistributing more specifics from iBGP to the carriers to get the \
traffic where it needs to be. In a failover situation these more specifics are also \
visible on an MPLS backbone where other transit routers will prepend the AS path \
upstream based on specific communities to prevent anycast \
routing.<u></u><u></u></span></p><p class="MsoNormal"><span \
style="font-family:&quot;Open Sans&quot;,sans-serif"><u></u>  <u></u></span></p><p \
class="MsoNormal"><span style="font-family:&quot;Open \
Sans&quot;,sans-serif">Thanks,<u></u><u></u></span></p><p class="MsoNormal"><span \
style="font-family:&quot;Open Sans&quot;,sans-serif"><u></u>  <u></u></span></p><p \
class="MsoNormal"><span style="font-family:&quot;Open \
Sans&quot;,sans-serif">Ryan<u></u><u></u></span></p></div></div></blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread]