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] 2006-02 Last Call for Comments (IPv6 Address Allocation and Assignment Policy)
- Previous message (by thread): [address-policy-wg] 2006-02 Last Call for Comments (IPv6 Address Allocation and Assignment Policy)
- Next message (by thread): [address-policy-wg] IPv6 PI policy implemented
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber, UniVie/ACOnet
Woeber at CC.UniVie.ac.at
Wed Jul 4 19:56:07 CEST 2007
michael.dillon at bt.com wrote: [...] > > But, since an organization with a single external connection is not an > ISP How, why and when did you arrive at that conclusion? And for which definition of ISP? And for which definition of external? > they should not receive a /32. In general, /32s should be for > organizations with steadily growing networks and also a few critical > infrastructure types of organization which needs the operational > characteristics of an ISP allocation. > > --Michael Dillon Wilfried
- Previous message (by thread): [address-policy-wg] 2006-02 Last Call for Comments (IPv6 Address Allocation and Assignment Policy)
- Next message (by thread): [address-policy-wg] IPv6 PI policy implemented
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]