Re: [44net] directly routed subnets

Not as a whole, of course, but pieces of it. I thought we were talking about announcing bits and pieces elsewhere at the globe than at UCSD and SF Bay Area to avoid as much global tunneling as possible, or? On 2012-03-16 19:27, Tim Pozar wrote: > (Please trim inclusions from previous messages) > _______________________________________________ > Ok... Pardon my confusion here. Why would 44/8 as a whole need to show up any other location? If that is needed, then some backhaul would need to happen between additional peering locations. Not saying that can be done the usual way ($$$) or via GRE tunnels (less $$$). > > I thought we were talking about: > > * One 44/8 BGP announcement at USD > > * One or more specific peers for address space that would be used for a region. Ie. /16 for SF Bay Area that could be announced at one or more locations in the SF Bay Area. Or, say multiple /18s announced in different locations in the SF Bay Area used for those "sub-regions". ie. A /18 for the South Bay, a /18 for SF, a /18 for the East Bay, etc... > > Tim > > On Mar 16, 2012, at 11:16 AM, Bjorn Pehrson wrote: > >> (Please trim inclusions from previous messages) >> _______________________________________________ >> Well, right now it seems as if 44/8 is announced out of AS7377, belonging to UCSD, together with several other prefixes. >> >> To facilitate interdomain peering at several sites on the globe, I guess there is a need for a separate public AS number for 44/8. There shouldn't be a problem getting that.