-----BEGIN PGP SIGNED MESSAGE----- Per Gregers Bilse <bilse@EU.net> writes:
What would happen if the customer used private address space and NAT & ALGs to hook this into the two providers' CIDR space?
I think that this is an excellent idea. In fact, Ed Kern at Digex is working with OFRV on making this real, so that other folks can do so when the NAT code is available in IOS. He might have something to say about your note.
Has anybody noticed that the net global routing table has bumped 40k a couple of times recently?
Yes. Fun fun fun. Has anyone else seen SSE microcode size get too big as a result? Ping. More than 2/3 of the way to the point where 7000s+SSPs will not be usable with traffic towards a fair number of destinations, in routers that carry full routing.
Would the registries have problems with this approach?
Would it matter if they did? :-) No, seriously, any concerns about the cases where twice the PA address space will be used should be releived by the reduction in demand (or at least in absolute need) for PI address space. In short, if it works well enough to be a general solution for customer migratability without requiring migratable address allocations, it's obviously a net win for the registries too.
Another issue is that the I-must-be-multihomed-to-different-providers mantra frequently isn't anything else than a funny idea in somebody's head.
Well, I agree with you about market misperception. However, this doesn't seem to be a very popular thing to say (flame wars ahead), and in part this is because few people have been saying it in public, even when they actually agree. Sean. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: PGP Public Key in ftp://ftp.sprintlink.net/engineer/smd/pgpkey iQCVAwUBMhZE7kSWYarrFs6xAQEvegQAjTHWfPO1Kbeuc6TYgFJ16EV6KjTq22AM tcW/VGP7NJ3DDuySlDgHqa2180NKrDlBGbU9kyK9nZJB67eWtvigEJ+V4T+D33aP vlJXNItzbQR7X9hnbAHr386VGDFjdm+CrnvC6fPGUZm754B2AbwCI/4qVJ9PZy2s wU78IyMudiM= =TWtU -----END PGP SIGNATURE-----
Hi,
What would happen if the customer used private address space and NAT & ALGs to hook this into the two providers' CIDR space? I think that this is an excellent idea.
APNIC is in the process of doing something like this. We will be requesting a /27 from the provider blocks of each of our peers at the connection point we're at. Each Internet accessible machine will have mutiple IP addresses per interface (VIF for Suns and ifconfig alias for BSDI boxes). Our internal machines are, of course, behind a firewall (TIS's Gauntlet) and using net 10. Of course, we'll be burning much more address space than we 'need' to, but we'll be adding 0 routing entries, even though we are multiply multi-homed. However, as I'm only a registry person and I "don't run real routers", it is possible I am missing something obvious that will result in this not working. If so, please let me know before I turn APNIC into slag...
Would the registries have problems with this approach?
Clearly APNIC doesn't.
Would it matter if they did? :-)
Only when an ISP went to get more address space from their registry. Regards, -drc P.S.: last I checked the routing tables were at 40853.
In message <199608180412.NAA01392@moonsky.jp.apnic.net>, "David R. Conrad" writ es:
P.S.: last I checked the routing tables were at 40853.
Checking overlaps (39066 routes found) overlaps with same AS path: 3315 Adjacent prefixes with same AS path: 3533 merges merges at /15 length = 200 merges at /16 length = 2 merges at /17 length = 3 merges at /18 length = 11 merges at /19 length = 23 merges at /20 length = 11 merges at /21 length = 31 merges at /22 length = 29 merges at /23 length = 3223 256 merges on AS path 3561 577 3804 157 merges on AS path 174 122 merges on AS path 690 2493 86 merges on AS path 1239 1794 3848 82 merges on AS path 1239 1794 3602 76 merges on AS path 3561 1691 75 merges on AS path 568 73 merges on AS path 1239 1790 58 merges on AS path 1239 1792 2044 55 merges on AS path 568 721 52 merges on AS path 1239 4005 5511 1717 48 merges on AS path 1321 2386 48 merges on AS path 1239 1785 38 merges on AS path 1 86 37 merges on AS path 1239 6174 2711 36 merges on AS path 1800 3215 36 merges on AS path 1239 1791 35 merges on AS path 1239 1791 3354 35 merges on AS path 701 34 merges on AS path 2041 2568 31 merges on AS path 3561 577 549 30 merges on AS path 3561 30 merges on AS path 1 86 225 29 merges on AS path 701 813 27 merges on AS path 3561 3824 447 AS paths used in 3533 merges 83 merges blocked on AS paths 3561 1221 & 3561 4433 80 merges blocked on AS paths 3561 1221 & 3561 2764 4175 76 merges blocked on AS paths 701 286 790 719 & 4000 3336 719 75 merges blocked on AS paths 3561 4433 & 3561 1221 74 merges blocked on AS paths 3561 2764 4175 & 3561 1221 71 merges blocked on AS paths 1665 3493 & 3561 577 376 58 merges blocked on AS paths 286 1270 & 1849 517 54 merges blocked on AS paths 3561 1221 & 4000 2764 4175 51 merges blocked on AS paths 1239 1794 3848 & 3561 577 3804 48 merges blocked on AS paths 690 2493 & 3561 577 549 45 merges blocked on AS paths 286 1899 & 1239 4005 5511 1717 43 merges blocked on AS paths 286 790 719 & 4000 3336 719 40 merges blocked on AS paths 690 2493 & 3561 577 542 35 merges blocked on AS paths 701 & 3561 33 merges blocked on AS paths 701 4474 & 701 33 merges blocked on AS paths 3561 577 271 & 3561 1691 32 merges blocked on AS paths 1239 6177 3602 & 1239 1794 3602 32 merges blocked on AS paths 1 200 681 & 3561 4768 31 merges blocked on AS paths 3561 1221 & 4000 2764 4174 30 merges blocked on AS paths 1239 4005 4230 & 3561 4230 30 merges blocked on AS paths 701 & 2551 29 merges blocked on AS paths 701 2685 2686 & 2685 2686 28 merges blocked on AS paths 1239 1792 2044 & 3561 1221 28 merges blocked on AS paths 690 2493 & 3561 577 591 28 merges blocked on AS paths 1239 1794 3602 & 1239 6177 3602 7811 merges blocked due to 4002 AS path pairs This represents a merge of Sprint NAP, MaeEast, and MaeWest routes (routing dumps taken on 8/13). The AS paths represent our best routes and so are tainted somewhat by our routing policy (not to mention who we peer with). This is probably a reasonable snapshot for the purpose of an order of magnitude estimate. Roughly 40,000 routes. Roughly 3,000 overlap with same AS path. Roughly 3,000 candidates for real easy aggregation. The "7811 merges blocked due to 4002 AS path pairs" is sort of scary, since that says there are a real lot of adjacent prefixes that have different AS paths. Adjacent in this context means differing in only the lowest bit in the prefix. Curtis
participants (3)
-
Curtis Villamizar -
David R. Conrad -
Sean Doran