Ipng addressing document status
This presentation is the property of its rightful owner.
Sponsored Links
1 / 5

IPng Addressing Document Status PowerPoint PPT Presentation


  • 79 Views
  • Uploaded on
  • Presentation posted in: General

IPng Addressing Document Status. Thomas Narten [email protected] March, 2001. Addressing Architecture. Currently under IESG discussion Make clear that implementations must treat all "non-special" addresses as global unicast Downplay reference to RFC2374 (Unicast Aggregatable)

Download Presentation

IPng Addressing Document Status

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Ipng addressing document status

IPng Addressing Document Status

Thomas Narten

[email protected]

March, 2001


Addressing architecture

Addressing Architecture

  • Currently under IESG discussion

    • Make clear that implementations must treat all "non-special" addresses as global unicast

    • Downplay reference to RFC2374 (Unicast Aggregatable)

    • Other editorial edits (no impact on implementations)

  • -04 ID addresses some issues, another rev needed

  • Approval as Draft Expected


Rfc2374 global unicast aggregatable addresses

RFC2374: "Global Unicast Aggregatable Addresses"

  • IESG unwilling to advance in current from

    • Not really appropriate for Standards Track

    • Topic of document has few implications for implementations

    • Size of TLAs, NLAs, etc. may change in future

    • Address assignment policy is the domain of RIRs

  • IPv6 architecture defines /64 boundary

  • /48 boundary not required by architecture, though good technical arguments for having it

  • Other boundaries in routing part managed by RIRs


Rfc 2374 cont

RFC 2374 (cont.)

  • Recommendation:

    • Engage the RIRs on topics covered in 2374

    • Cooperative effort:

      • IETF provides input on technical issues

      • RIRs develop and adopt allocation policies

      • Separate documents (with different focus) may result

  • No change to existing allocations expected

  • No change in policy without extensive public review (both in IETF & RIRs)

  • May result in evolution of future policy


Met with rirs

Met With RIRs

  • IPng Chairs and ADs met with RIRs this week

  • Initial discussion positive


  • Login