IP addresses for the RIPE NCC
Randy Bush randy at psg.com
Thu May 9 01:21:55 CEST 2002
as my earlier recommendation attests, i agree with you. grab a /48 and do as in v4. except ... rfc 2772 - 6Bone Backbone Routing Guidelines 4. Routing Policies for the 6bone Leaf sites or pNLAs MUST only advertise to an upstream provider the prefixes assigned by that provider. Advertising a prefix assigned by another provider to a provider is not acceptable, and breaks the aggregation model. A site MUST NOT advertise a prefix from another provider to a provider as a way around the multi-homing problem. However, in the interest of testing new solutions, one may break this policy, so long as ALL affected parties are aware of this test, and all agree to support this testing. These policy breaks MUST NOT affect the 6bone routing table globally. ... All 6bone pTLAs MUST NOT advertise prefixes longer than a given pTLA delegation (currently /24 or /28) to other 6bone pTLAs unless special peering arrangements are implemented. When such special peering aggreements are in place between any two or more 6bone pTLAs, care MUST be taken not to leak the more specifics to other 6bone pTLAs not participating in the peering aggreement. 6bone pTLAs which have such agreements in place MUST NOT advertise other 6bone pTLA more specifics to downstream 6bone pNLAs or leaf sites, as this will break the best-path routing decision. cute, eh? will work well in scalable reality, eh? randy, struggling along in 2001:418:1::/48
[ lir-wg Archives ]