1 / 8

Policy Proposal 2006-3

This proposal outlines ARIN's approach to collecting and displaying Autonomous System Numbers (ASNs) permitted to originate IPv4 and IPv6 prefixes in all number transactions. It emphasizes significant changes required in templates, registration software, directory services, guidelines, and staff training. While there are no major legal risks identified, some concerns about increased legal responsibilities and verification processes are discussed. The proposal seeks to enhance the routing registry while ensuring authorized submission from vetted organizations.

allan
Télécharger la présentation

Policy Proposal 2006-3

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. Policy Proposal 2006-3 Capturing Originations in Templates

  2. Policy Proposal 2006-3Description • ARIN would, in all IPv4 and IPv6 number transactions, collect and display the ASN(s) which are permitted to originate a prefix. **************************************** AC Shepherds • Mark Kosters • Suzanne Woolf

  3. Policy Proposal 2006-3History Proposal Text In Meeting Packet http://www.arin.net/policy/2006_3.html

  4. Policy Proposal 2006-3Implementation Assessment – March 2006 Resource Impact: Significant Implementation Requirements: • Template Change • Registration Software Change • Directory Services Change • Guidelines Change • Staff Training

  5. Policy Proposal 2006-3Legal Assessment – March 2006 Legal Risks: None* *However, the third staff comment indicates a potential issue by increasing ARIN legal responsibility> As ARIN agrees to “verify” anything it may create a legal liability if it is done badly…

  6. Policy Proposal 2006-3Staff Comment Comments: • Could be addressed by alternatively enhancing the ARIN Internet Routing Registry. • Network Modification template omitted from proposal. • Reminder: ARIN can verify that the request was submitted by an authorized POC representing a vetted organization. ARIN can not verify specifically “the list of the ASes that the user permits to originate address prefixes within the address block”.

  7. Policy Proposal 2006-3PPML Discussion • 2 for, 1 for as long as info is also put in IRR, 2 said to use the IRR, 1 said use RPSL • Comments: • "…effort would be better spent in revitalizing the RR…" • “This [is] a simple method to allow folks doing prefix-list building to verify that sprint (sic) has the block owners authority to originate said block."

  8. Policy Proposal 2006-3 http://www.arin.net/policy/2006_3.html

More Related