1 / 10

Proposal-061: 32-bit ASNs for documentation purposes

Proposal-061: 32-bit ASNs for documentation purposes. Gaurab Raj Upadhaya & Philip Smith Policy SIG @ APNIC 26 28th August 2008 Christchurch, New Zealand. Introduction. Proposal to reserve four 32-bit ASNs exclusively for documentation purposes. Current Problem.

wynn
Télécharger la présentation

Proposal-061: 32-bit ASNs for documentation purposes

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. Proposal-061: 32-bit ASNs for documentation purposes Gaurab Raj Upadhaya & Philip Smith Policy SIG @ APNIC 26 28th August 2008 Christchurch, New Zealand

  2. Introduction • Proposal to reserve four 32-bit ASNs exclusively for documentation purposes

  3. Current Problem • There is no ASN space above 65535 which is usable for documentation purposes • Documentation writers: • Transition and interworking cases studies • Private ASNs 64512 to 65534 aren’t examples from the extended 32-bit ASN range • Shouldn’t use real life operational ASNs in documentation • Shouldn’t use currently unallocated resources as they will be required in the future

  4. Situation in other RIRs • The RIRs have no formal common policy for making a 32-bit ASN allocation exclusively for documentation

  5. Details of the Proposal • APNIC set aside a common block of 32-bit ASNs to be used solely for the purpose of documentation • The 32-bit ASN block for documentation should include minimum four ASNs • This is sufficient for a small network topology to include either exclusive 32-bit ASN or a mixture of 16-bit or 32-bit ASNs for purposes of documenting relationships between ASNs.

  6. Advantages • Authors of documentation and Internet books no longer have to use • 32-bit ASNs which belong to their employer (and risk causing disruption to their employer’s business) • 32-bit ASNs allocated to other organisations around the Internet (and risk causing disruption to a multitude of organisations)

  7. Disadvantages • Will mean that four 32-bit ASNs will be added to the non-routable ASN space of the Internet • Might make some people believe that this ASN block is effectively private ASN space as it is not routable

  8. Other considerations • Rejection of this proposal: • Means that authors will have to carry on with the practice highlighted in the Background section of this proposal, with the associated risks to the integrity of the commercial Internet • APNIC and other training documentation will have to use ad-hoc representations, specially at the time when education and training are important • Even with prop-64 approved, during transition it will be essential for 4 byte ASNs for documentation/training.

  9. Impact on APNIC members and NIRs • This proposal has no impact on APNIC members or NIRs

  10. Questions?

More Related