Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0
  • Category: (replace this text with one of the following categories: Administration/Budget, Board, ccTLD, gTLD, IP, ICANN Structure, International Agreement, Root Zone) Internet Protocols
  • Topic: ASN Global PolicyTopic: (replace this text with a keywords from title)
  • Board meeting date: 31 July 2008
  • Resolution number: __.2008, __.2008
  • URL for Board minutes/resolution: http://www.icann.org/en/minutes/minutes-31jul08.htm
  • Status: (replace this text with: Completed, Ongoing, Suspended)

Summary ASN

Board ratifies the Global Addressing Policy for Proposal on Autonomous System Numbers (Board Action) – Olof Nordling – Paper 69-2008

Text

Olof Nordling advised that An Autonomous System (AS) is a network operated with a single, clearly defined routing policy. When exchanging exterior routing information a unique number identifies each AS. This means ASNs are needed by networks connecting to multiple independently operated networks. These networks are normally run by ISPs and large enterprises. When a network connects to just one other network it can only route traffic via one external link and so cannot define its own routing policy.

Olof noted that the RIRs have been assigning 4-byte numbers in addition to 2- byte numbers since 2007 and will default to assigning 4-byte numbers in 2009. In 2010 they will cease to distinguish between the two number spaces. This global policy formalizes the process and sets a date for transition when all two byte numbers will be considered to be of four-byte length.

Olof indicated that Staff recommends the ratification of the proposals, since the need for longer AS Numbers has long been recognized and longer numbers have already been introduced in practice. The Proposal adds a timeline for the handling which has the support of all stakeholders, and that there appear to be no diverging positions on any of its provisions within the Regional Internet Registries, and that the proposals are fully in line with the practices within IANA. The consideration of the policy by the Board is timely, in that it is in the middle of the sixty-day period the MOU identifies for Board ratification of proposals---this window expires on 12 August.

Raimundo Beca suggested a small change to the proposed resolution before the Board that accurately reflects the date the ASO forwarded the policy from IANA to the RIRs.

The following motion was moved by Raimundo Beca and seconded by Dave Wodelet.

as a Global Policy and instructs ICANN Staff to implement its provisions. 

Text

Whereas, on 12 June 2008, the ASO Address Council forwarded a Global Policy Proposal for the Allocation of Autonomous System Numbers from IANA to the RIRs to be ratified by the ICANN Board.

...

It is hereby resolved (__.2008) that the Board requests the ICANN staff to develop and implement, in cooperation with the NRO and the RIRs, timely announcement arrangements concerning the allocation of Autonomous System Numbers.

A voice vote was taken of all Board Members present, and the motion was approved by a vote of 13 to 0, with no abstentions.

Implementation Actions

Implementation Actions

  • Develop and implement announcements concerning the allocation. (replace this text with specific Action Item)
    • Responsible entity: (replace this text with the responsible entity: ICANN department, ICANN Community Structure, Board, U.S. Department of Commerce)ICANN Staff. NRO, RIRs
    • Due date: (replace this text with Due Date)None provided
    • Completion date: (replace this text with Date action was implemented)
  • (replace this text with specific Action Item)
    • Responsible entity: (replace this text with the responsible entity: ICANN department, ICANN Community Structure, Board, U.S. Department of Commerce)
    • Due date: (replace this text with Due Date)
    • Completion date: (replace this text with Date action was implemented)

Other Related Resolutions

  • (replace this text with links to related resolutions)

Additional Information

...

    • 22 April 2010

Other Related Resolutions


Additional Information

Explanatory text does not modify or override Resolutions.  See Board Resolutions Page for more information.

Note: The "Add Comment" box below is for sharing information about implementation of this resolution. Off-topic comments will be removed.