1 / 8

aut-num object

aut-num object. Denis Walker Business Analyst RIPE NCC Database Team. “ via ” attributes. Draft RFC from Job Snijders http://tools.ietf.org/html/draft-snijders-rpsl-via-02 Two new optional attributes "import-via:" and "export-via:"

adonica
Download Presentation

aut-num object

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. aut-num object • Denis Walker • Business Analyst • RIPE NCC Database Team

  2. “via” attributes • Draft RFC from Job Snijders • http://tools.ietf.org/html/draft-snijders-rpsl-via-02 • Two new optional attributes • "import-via:" and "export-via:" • “Used in RPSL policy specifications to publish desired routing policy regarding non-adjacent networks.”

  3. Open source software • Job modified the RIPE Database software • Provided a patch to the RIPE NCC • Ready to implement this change in a test environment

  4. Change to aut-num - ALERT!!!! • The aut-num object is important to routing • This feature adds 2 new optional attributes • RFC2622 says tools should transparently handle unknown attributes • Will this break your tools?

  5. Communication • The syntax of the aut-num object does not change often • When it does, how should we contact all those who really need to know this?

  6. Pending route authorisation • Simplify the complex authorisation for route creation • One user submits route object with some auth • Second user submits same object with missing auth tokens • When both objects received, RIPE Database software creates object if combined auth tokens all pass • Available on TEST soon after RIPE 67

  7. aut-num management • Very big objects • Composed of many peering detail sets • Updated often, small changes • Sometimes auto generated by scripts • Can we manage it better? • With new software, management of data can be de-coupled from presentation of information… • Manage as simple data sets, present as RPSL?

  8. Questions?

More Related