[routing-wg] [address-policy-wg] Re-issue of reclaimed 16bit ASNs and modifications to references in routing policy to these resources

On Jun 9, 2014, at 9:09 AM, Job Snijders <job at instituut.net> wrote:

> On Mon, Jun 09, 2014 at 02:49:33PM +0200, João Damas wrote:
>> at the recent RIPE 68 meeting there was a discussion about issues
>> concerning the re-issue of recovered 16-bit ASNs by the RIPE NCC and
>> possible modifications to the content of routing-related attributes in
>> RIPE Database objects, namely the routing policy attributes of autnum
>> and as-set objects.
>> 
>> The observed consensus during the meeting was that:
>> 
>> - the RIPE NCC should not to remove references to recovered ASNs from
>> import and export lines, and neither from as-set objects; routing
>> policies are the realm of the object owner and are not related to
>> allocation data.
>> - the RIPE NCC will inform the maintainer of the object containing the
>> obsolete reference about this reference. The RIPE NCC will also offer
>> support to the maintainer to delete the reference;
>> - the RIPE NCC will start re-assigning referenced AS numbers once the
>> unreferenced pool of 16-bit AS numbers has been exhausted.
>> 
>> We would like to close the issue and be able to provide clear guidance
>> to the RIPE NCC so we would like to get confirmation for this outcome
>> also from the working group mailing lists. This is not a policy issue:
>> the re-allocation of recovered ASNs was dealt with by the APWG, the
>> current issue is related to alterations to RIPE Database objects that
>> reference the resources subject to re-allocation.  We propose a 15 day
>> comment period, ending June 24th 2014.
> 
> 


Same, this works.

Best,

-M<




-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: </ripe/mail/archives/routing-wg/attachments/20140609/799a988f/attachment.sig>