Hi, Lixia,
I received some questions in private, and I think I was not specific enough,
though a short memo. I'm posting a revised text.
A power point material will be distributed within this week. A full text
proposal will be submitted by the due date, Dec. 15.
Can you count my short memo as one item of the list you're going to finish
within a few days?
--
Regards,
Dae Young
http://cnu.kr/~dykim
SCALABLE INTERNET
dykim, 09.11.18
A. Fundamentals:
o Skeletons:
o ID is global, Locator is local(private) to AS.
o Keep use of DNS, with some extension.
o TCP works on ID, IP on Loctor, Gateways(BGP) on AS #.
o Gateways advertises only AS #s, not network prefixes.
o Corollaries:
o Number space of AS is limited to 2^^16(64K) in one tier.
o AS tier recurs hierarchically, downward and upwards(or inwards and
outwards). In each tier, the maximum number of ASs is limited to 2^^16.
o AS(cloud) can float within and across tiers. AS(ISP) can change is
neighbor relation anytime in the course of its existence within and across the
tier architecture.
o Implementation choices:
o Take IPv4 and IPv6 addresses as IDs. That is, IP addresses in the
current Internet infrastructure is to be used as IDs, not anymore as locators.
o Locators are local (private) IP addresses.
o DNS is extended to serve not only name-to-address(ID) mapping but
also ID-to-AS mapping.
o AS to Locator mapping is done by a server within the AS where the
affected host belongs.
B. Scenario of outgoing communication example:
1. DNS returns the remote (glabal) ID as well as the AS number it belongs
to.
2. TCP establishes connections by use of ID.
3. TCP requests, to IP, transmission of segments with the AS number, as a
parameter, of the domain where the destination peer belongs.
4a. If the target AS is local, IP uses a locator(private IP address) to
deliver the packet.
4b. If the target AS is foreign, IP uses a locator to deliver the packet to
the egress gateway(BGP) router.
5. Local gateway relays the packet to one of the next hop gateways that
advertised the target AS #.
C. Scenario of incoming communication example:
(Your homework.)
D. Consequences.
o Gateway routing table doesn't explode, never exceeds 64K(2^^16).
o AS tier can recurs, theoretically, indefinitely. The whole Internet can
scale to infinity.
o NAT is a norm, not an evil.
o The current IP address management infrastructure won't be abandoned. They
operate exactly the same way as it does. Only that the number is now used as
IDs, not for locators.
o The current DNS infrastructure is maintained, only with a bit of
extension. It now has to keep database of (domain name, ID, AS number) tuples.
o Minimal disturbance to the current Internet infrastructure, with a path
out for sustainable scalability.
Your comments are solicited._______________________________________________
rrg mailing list
[email protected]
http://www.irtf.org/mailman/listinfo/rrg
