[address-policy-wg] RIPE 553 & last /8 <-> Anycast assignments
- Previous message (by thread): [address-policy-wg] RIPE 553 & last /8 <-> Anycast assignments
- Next message (by thread): [address-policy-wg] RIPE 553 & last /8 <-> Anycast assignments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carsten Schiefner
ripe-wgs.cs at schiefner.de
Tue Sep 18 13:12:57 CEST 2012
Clarification: my question below only regards IPv4 Anycast assignments, of course. Best, Carsten On 18.09.2012 11:50, Carsten Schiefner wrote: > All - > > as I have just discussed this privately with a colleague: is it the case > that as a side effect of section 5.6 "Use of last /8 for PA Allocations" > of RIPE 553: > > https://www.ripe.net/ripe/docs/ripe-553#-----use-of-last-8-for-pa-allocations > > > there won't be any more Anycast assignments following section 6.9 > "Anycasting TLD and Tier 0/1 ENUM Nameservers" of this policy: > > https://www.ripe.net/ripe/docs/ripe-553#-----anycastying-tld-and-tier-1-enum-nameservers > > > either? > > As such 'Assignments for authoritative TLD or ENUM Tier 0/1 DNS lookup > services are subject to the policies described in the RIPE Document > entitled "Contractual Requirements for Provider Independent Resource > Holders in the RIPE NCC Service Region"' as this section states. > > I tried various ways of interpretation, but failed to come to terms > eventually. > > Any hints, anyone? > > Thanks and best, > > Carsten
- Previous message (by thread): [address-policy-wg] RIPE 553 & last /8 <-> Anycast assignments
- Next message (by thread): [address-policy-wg] RIPE 553 & last /8 <-> Anycast assignments
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]