Dear Erik, We intend to follow up on this during the RIPE meeting next week. In short, there are no objections to adding the new attributes and we're aiming to have the attributes available in the TEST Database right after the meeting. This is a change to the aut-num object structure so we need to communicate this properly. There is a chance that we may break user implementations by introducing these attributes, so we need to make sure that the users are aware of the change and have plenty of time to adjust their implementations if necessary. Kind regards, Johan Åhlén Assistant Manager Database RIPE NCC On 9 Oct 2013, at 10:48, "Erik Bais" <ebais@a2b-internet.com> wrote:

Hi Job & Johan,

I think the implementation makes sense and my compliments on the draft. It looks good:

...

http://tools.ietf.org/html/draft-snijders-rpsl-via

Is this already in the new db version or is this still waiting for more community support ?

For me, support +1.

Kind regards, Erik Bais A2B Internet

...

I have submitted the following draft to the IETF:

http://tools.ietf.org/html/draft-snijders-rpsl-via

And I have submitted a patch for the RIPE whois server to support the

feature.

...

https://github.com/job/whois

The extension should be backward compatible with minimal impact on

existing

...

tools and processes, following Section 10.2 of RFC2622. RPSL parsers which do not understand the new attributes are expected to just ignore it.

I am looking for feedback from this community, and especially the community's blessing to allow RIPE NCC to adopt the patch.

Kind regards,

Job