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] ALLOCATED PI / UNSPECIFIED next action
- Previous message (by thread): [address-policy-wg] ALLOCATED PI / UNSPECIFIED next action
- Next message (by thread): [address-policy-wg] Fwd: Re: Update on ALLOCATED PI/UNSPECIFIED
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
fransossen at yahoo.com
fransossen at yahoo.com
Thu Oct 27 17:06:23 CEST 2016
Hi, > On Thursday, October 20, 2016 2:38 PM, Sander Steffann <sander at steffann.nl> wrote: > - increase of the routing table This would be the perfect moment to introduce the possibility to authenticate Route(6) creation for contiguous prefixes belonging to different organisations, this is out of scope for this WG, but the DB WG could pick this up. Many of those Allocated PI and Allocated unspecified are aggregated already, if the more specifics are converted to regular PI assignment rather than PA the aggregation in the IRR will be lost unless a mechanism is put in place to allow for it. Allowing the AS to somehow create a /xx aggregated route for the more specifics would be a nice thing and would also be beneficial to other operators that currently have to create separate entries while having contiguous ranges from various customers. Cheers, David
- Previous message (by thread): [address-policy-wg] ALLOCATED PI / UNSPECIFIED next action
- Next message (by thread): [address-policy-wg] Fwd: Re: Update on ALLOCATED PI/UNSPECIFIED
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]