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] Re: RIPE Access Policy Change Request to allow allocations to critical infrastructure
- Previous message (by thread): [address-policy-wg] Re: RIPE Access Policy Change Request to allow allocations to critical infrastructure
- Next message (by thread): [address-policy-wg] Re: RIPE Access Policy Change Request to allow allocations to critical infrastructure
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Fri Jan 9 11:57:33 CET 2004
Hi,
On Fri, Jan 09, 2004 at 11:44:45AM +0100, Gert Doering wrote:
> So it could look like this:
>
> Criteria:
> - Anycast
> - technical requirements (UDP record full)
> - ccTLD or gTLD operator
>
> Assignment:
> - /24 "status: ASSIGNED ANYCAST" out of well-known range
> - all anycast blocks (in RIPE land) come from the same range
People just pointed out to me that it's a "IPv4/IPv6 Policy", so
the whole thing should be formulated accordingly.
For IPv6, it could be done in analogy to the IPv6 root server policy.
Gert Doering
-- NetMaster
--
Total number of prefixes smaller than registry allocations: 57882 (57753)
SpaceNet AG Mail: netmaster at Space.Net
Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0
80807 Muenchen Fax : +49-89-32356-299
- Previous message (by thread): [address-policy-wg] Re: RIPE Access Policy Change Request to allow allocations to critical infrastructure
- Next message (by thread): [address-policy-wg] Re: RIPE Access Policy Change Request to allow allocations to critical infrastructure
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]