> Just FYI I and Enke Chen have discussed in the past an > algorithmic way to convert 4 byte AS number into the locator. > Naturally such locator would be an anycast and one could most > likely enter given AS via any peering ASBR.
In the draft of "Simple Tunnel Endpoint Signalling in BGP"[ http://tools.ietf.org/id/draft-xu-tunnel-00.txt ] , an IP address specific extended community is used for carring the tunnel endpoint (RLOC), which is associated with the NLRI (EID prefix). In fact, as long as the tunnel endpoint address is an anycast address within the originator AS , it is just AS-based inter-domain routing. Xiaohu > The scheme is very simple. > > We take 4 byte AS number, assume that we will use 3 last > octets while first octet would be all zeros and do normal > byte by byte bin to dec conversion. > > The resulting special IPv4 address would be 0.A.B.C. > > For IPv6 this is even simpler :). > > At that time some folks voiced their opinion that making AS > part of a locator is a bad thing. Along the same lines they > were against tunneling to AS/IP address. Perhaps those folks > could comment now why this is a bad choice ? > > I never understood why we can not make first baby step and > introduce some of the hierarchy just by doing this. We pretty > much already know today the originator AS from AS_PATH (AS > SET is sporadic) as well as number of potentially injected > new entires equal to number of ASes would be noise for current BGP. > > Cheers, > R. > > > How can locator have default association with its > containing autonomous system? > > Easy. Autonomous system number shall be incorporated into > locator. Universally recognizable locator shall start with it. > > > > On Tuesday 5 May 2009 12:35:41 Toni Stoev sent: > >> Intra-domain routing can be considered as a general > solution. This general solution is the provision of > reachability throughout an autonomous system. > >> Node locators can be considered intra-domain locators. > Every locator shall have default association with its > containing autonomous system in order to be universally recognizable. > >> Utilizing these approaches inter-domain routing can be > separated from intra-domain routing. Inter-domain routing > shall be based on autonomous system paths and not on IP > addresses and prefixes. Thus inter-domain routing tables will > be substantially unloaded and more easily managed. > >> This will provide significant improvement to inter-domain > routing scalability. > > _______________________________________________ > rrg mailing list > [email protected] > http://www.irtf.org/mailman/listinfo/rrg _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
