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] IPv6 PI request is turned down for my multihomed hosting facility - Why?
- Previous message (by thread): [address-policy-wg] IPv6 PI request is turned down for my multihomed hosting facility - Why?
- Next message (by thread): [address-policy-wg] IPv6 PI request is turned down for my multihomed hosting facility - Why?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tero Toikkanen
Tero.Toikkanen at nebula.fi
Wed Mar 30 12:28:19 CEST 2011
> The IPv4 policy has this sentence: > > http://www.ripe.net/ripe/docs/ripe-509#----network-infrastructure-and- > end-user-networks > > 6.2 Network Infrastructure and End User Networks > > IP addresses used solely for the connection of an End User to a service > provider (e.g. point-to-point links) are considered part of the service > provider's infrastructure. These addresses do not have to be registered with > the End User's contact details but can be registered as part of the service > provider's internal infrastructure. > When an End User has a network using public address space this must be > registered separately with the contact details of the End User. > > ... and this specific clause is not in the IPv6 policy, so "networks used to > number end customers" are considered "part of the assignment to this end > customer". > > (Which makes sense for DSL and cable etc. networks, where you really want > to assign a /56 or /48 anyway, and not start tricking around with single- > address-assignment from PI blocks) Right. Thanks for clearing this up Gert. In any case, this should be clearer in the policies as it is easy to get confused because IPv4 PI != IPv6 PI in terms of what you can do with it. Also, policy interpretation within RIPE NCC should be sorted out (unless it already is), as I distinctly remember getting IPv6 PI for a customer for hosting purposes a year ago. ____________________________________ Tero Toikkanen Nebula Oy
- Previous message (by thread): [address-policy-wg] IPv6 PI request is turned down for my multihomed hosting facility - Why?
- Next message (by thread): [address-policy-wg] IPv6 PI request is turned down for my multihomed hosting facility - Why?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]