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/address-policy-wg@ripe.net/
[address-policy-wg] draft-hain-ipv6-pi*
- Previous message (by thread): [address-policy-wg] Additional supporting document for IANA->RIR IPv6 policy proposal
- Next message (by thread): [address-policy-wg] Fwd: [Apnic-announce] Privacy of customer assignment records - implementation update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tony Hain
alh-ietf at tndh.net
Wed Sep 22 18:38:05 CEST 2004
Per request, the pointers to the current PI drafts are: http://www.ietf.org/internet-drafts/draft-hain-ipv6-pi-addr-07.txt http://www.ietf.org/internet-drafts/draft-hain-ipv6-pi-addr-use-07.txt As the USE draft discusses, the exchange points are likely to have a more prominent role than they do in the PA deployment model. For the obvious discussion about how this is impacted by natural impediments, there is an example for exception prefixes at: http://www.tndh.net/~tony/ietf/GrandCanyon.htm Depending on where these prefixes aggregate, there may or may not be any need for distributing these exception prefixes beyond one exchange point. In any case the only entities that need to know the detail are the ones directly involved in sorting it out. Tony
- Previous message (by thread): [address-policy-wg] Additional supporting document for IANA->RIR IPv6 policy proposal
- Next message (by thread): [address-policy-wg] Fwd: [Apnic-announce] Privacy of customer assignment records - implementation update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]