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/[email protected]/
[ipv6-wg] /127 for point to point links
- Previous message (by thread): [ipv6-wg] /127 for point to point links
- Next message (by thread): [ipv6-wg] /127 for point to point links
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marc Blanchet
marc.blanchet at viagenie.ca
Mon Feb 15 12:58:07 CET 2010
João Damas a écrit : > On 13 Feb 2010, at 13:14, Marco Hogewoning wrote: > >>> What do others think of drafting an IPv6 best practices >>> document in this WG that is specifically for network operators? >> some: - address plan: RFC3531 - special IPv6 prefixes (the ones who usually need to be filtered): RFC5156 Marc. >> Looking forward to a first draft of this. Is it worth joining up with the routing WG who is, I believe, busy with something on filtering recommendations and deaggregation ? >> > > True, ever since AP-wg agreed that routing considerations, such as (de)aggregation, would be better reflected in a routing document than in an address policy one. Work has been headed by Rob Evans and Sander steffann with help. see http://www.ripe.net/ripe/wg/routing/r59-minutes.html, the minutes for RIPE 59. Look at the last item in the minutes > > Joao -- ========= IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca DTN news service: http://reeves.viagenie.ca NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca
- Previous message (by thread): [ipv6-wg] /127 for point to point links
- Next message (by thread): [ipv6-wg] /127 for point to point links
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]