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]/
[address-policy-wg] 2006-01 IPv6 PI implementation
- Previous message (by thread): [address-policy-wg] 2006-01 IPv6 PI implementation
- Next message (by thread): [address-policy-wg] 2006-01 IPv6 PI implementation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Wed Dec 9 19:06:54 CET 2009
Hi,
On Wed, Dec 09, 2009 at 05:58:58PM +0100, Sergey Myasoedov wrote:
> can anyone explain me is there a restriction in policy for assigning /48 PI IPv6 to ISP
> which will use /64-/128 prefixes to connect broadband customers?
IPv6 PI is for *your* network.
IPv6 PI space is not to be used for assigning prefixes to customers - and
this is very clear from the policy documents. If you want to assign prefixes
to customers, become a LIR and get a /32 IPv6 PA (or larger).
(Yes, this is different from the way one could run an "ISP" in IPv4 land,
assigning single IPv4 addresses to customers, and declaring those to be
"ISP infrastructure" - this is permitted by the current IPv4 policy, but
this loop hole does not make any sense in IPv6 where you are supposed to
assign whole /64 or /56 networks to customers)
Gert Doering
-- APWG chair
--
Total number of prefixes smaller than registry allocations: 144438
SpaceNet AG Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279
- Previous message (by thread): [address-policy-wg] 2006-01 IPv6 PI implementation
- Next message (by thread): [address-policy-wg] 2006-01 IPv6 PI implementation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]