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] PI vs PA in routing table
- Previous message (by thread): [address-policy-wg] PI vs PA in routing table
- Next message (by thread): [address-policy-wg] PI vs PA in routing table
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber, UniVie/ACOnet
Woeber at CC.UniVie.ac.at
Thu Sep 28 14:55:44 CEST 2006
Iljitsch van Beijnum wrote: [...] > - there is no easy way to distinguish between a PI and a PA prefix I presume the RIPE NCC would assign those blocks from a "separate" address range, much like it is the habit for IPv4 PI. And of coure include that informtion in the *usual* reports and places. Maybe this should go into the proposal? Wilfried.
- Previous message (by thread): [address-policy-wg] PI vs PA in routing table
- Next message (by thread): [address-policy-wg] PI vs PA in routing table
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]