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] Any-cast or uni-cast solutions
- Previous message (by thread): [address-policy-wg] Any-cast or uni-cast solutions
- Next message (by thread): [address-policy-wg] Any-cast or uni-cast solutions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ingrid Wijte
ingrid at ripe.net
Wed May 23 11:13:15 CEST 2012
I would like to give some further clarification on this. The RIPE NCC allocates/assigns address space to organisations who have a need in the RIPE NCC service region. The address space must be originated from the RIPE NCC service region. Due to the diverse nature of businesses, in addition to this there can be announcements from other regions. To respond to Randy, also having BGP-speaking customers outside of the region is no problem. Regards, Ingrid Wijte Registration Services Assistant Manager RIPE NCC On 5/23/12 10:54 AM, Wilfried Woeber, UniVie/ACOnet wrote: > Tore Anderson wrote: > >> * Lu Heng >> >> >>> but if there is no policy for that, is that means people can announce >>> their address in us or region outside ripe region(as i know some >>> people do for their us cdn network for example)., is this also >>> accepted in the policy? >> >> You can announce them anywhere you like. But you cannot assign them to >> end users outside outside of the region. > I am not aware of such a limitation in the RIPE Region's policies. > Wilfried. > >
- Previous message (by thread): [address-policy-wg] Any-cast or uni-cast solutions
- Next message (by thread): [address-policy-wg] Any-cast or uni-cast solutions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]