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/ipv6-wg@ripe.net/
[ipv6-wg] IPv6 policies & BGP announcements
- Previous message (by thread): [ipv6-wg] IPv6 policies & BGP announcements
- Next message (by thread): [ipv6-wg] IPv6 policies & BGP announcements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Florian Weimer
fw at deneb.enyo.de
Mon Nov 26 20:36:37 CET 2007
* Clement Cavadore: > - Am I allowed to announce a prefix more specific than my LIR's /32 > (originated from my ASN, not the LIR's one) ? This is really the LIR's call because it's within their prefix. There are no other rules regarding prefix announcements. > - If I can announce a more specific prefix, do I have to announce a > couple of /48s, or may I announce a single /47, originated from my AS ? > If I can announce the /47, I assume the LIR has to create a route: object ? Not necessarily. For IPv4, there are some folks who use RIR data to create filters, so having such an object would be beneficial. I don't know about the state of IPv6 filtering. A lot of operators likely discard anything longer than /32 in the RIR allocation space. > - Is there any recommendations I'd need to know for such a situation > (except becoming LIR, which is not possible for us at the moment) ? ARIN offers IPv6 PI space, perhaps you can get a /48 prefix which is supposed to be globally routable from them.
- Previous message (by thread): [ipv6-wg] IPv6 policies & BGP announcements
- Next message (by thread): [ipv6-wg] IPv6 policies & BGP announcements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]