This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] IPv6 Routing Recommendations
- Previous message (by thread): [routing-wg] IPv6 Routing Recommendations
- Next message (by thread): [routing-wg] IPv6 Routing Recommendations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Smith
pfs at cisco.com
Tue Apr 27 04:18:31 CEST 2010
Nick Hilliard said the following on 27/04/10 07:57 : > On 26/04/2010 13:32, Randy Bush wrote: >> we tell people ipv6 allows multi-homing. > > Do we? Which particular vapour are you referring to here? I suppose the question Rob and I are trying to address is, do we want to encourage ISPs to take their /32 and announce all 65536 /48s in an effort to do some kind of amazing traffic engineering act by juggling all 65k prefixes at once? Or do we want to encourage ISPs to think aggregation, and only leak the subprefixes that they need to leak to support their multihoming customers and traffic engineering requirements? Anyway, the doc would just be recommendations, along the lines of RIPE-399 being no more than recommendations. If folks think we are wasting our time putting together an IPv6 equivalent, let us know, and we can stop here. ;-) philip --
- Previous message (by thread): [routing-wg] IPv6 Routing Recommendations
- Next message (by thread): [routing-wg] IPv6 Routing Recommendations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]