From: sheherezada@gmail.com
Date: Thu Jan 31 2008 - 07:34:22 ARST
From my point of view, I would go with a public AS. The overlapping
issues seem minor to me when compared to the limitations in future
services: maybe you will want to offer public Internet access to your
customers and you will need to be multi-homed to at least two Internet
upstreams if your are not already.
Or you may see it the other way: getting a public AS has no financial
impact and it bears a negligible administrative effort. I don't see
any reason for using a private AS, especially if you are not a small
organization.
HTH,
Mihai
CCIE #16616
On Jan 30, 2008 4:19 PM, Gabriel Nunes <gabriel.nunes@gmail.com> wrote:
> Hi Experts!
>
> I work for a mobile phone provider which is intending to provide VPN MPLS
> service that require the use of MP-BGP protocol into the backbone MPLS.
>
> The question is regarding the AS number to use in the backbone. I believe
> that they need to configure a public AS instead of a private AS to avoid
> some kind of overlapping issues with the customer, and BGP AS-Path issues as
> well.
> I'd like to hear from your side the key technical points to justify the use
> of a public AS in the backbone for this service. Any?
>
> Thanks,
>
> Gabriel Nunes CCIE#17737
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2008 - 16:54:47 ARST