1 / 8

Utilizing 240.0.0.0/4 Address Space: Paving the Way for Future Innovations

Delve into the potential of 240.0.0.0/4 address space for both public and private uses while considering implementation, impacts on existing systems, and suggestions for moving forward. Explore the running code and its compatibility with various operating systems. Share your feedback to shape the future use of this address space.

samuru
Download Presentation

Utilizing 240.0.0.0/4 Address Space: Paving the Way for Future Innovations

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. 240.0.0.0/4: The Future Begins Now Vince Fuller Eliot Lear David Meyer

  2. What’s this all about? 240.0.0.0/4 Source: IANA (20 Sep 2007)

  3. Options for 240.0.0.0/4 • Make Space Unicast Public • Makes it potentially available sometime down the line • Make Space Unicast Private • Lets “consenting adults” use space(draft-wilson-classe-01.txt) • Split space up in some way • Do Nothing

  4. Our Approach • We don’t yet know or agree on how address space should be used, except… • Someone should use it • “future use” doesn’t make much sense any more • Make code changes NOW and figure out whether it’s public or private in the next year or so • Draft-fuller-240space-00.txt

  5. There is some running code • Coming soon to a Linux kernel near you • 5 files, removing a few lines each (submitted) • Kernel developers have done a simpler version • FreeBSD and OSX (mostly) works • One minor change if system is a router • Has been added to latest Solaris • More code needed (in many places); this will take time • If you want this, tell your vendors

  6. Possible issues • Will this slow down ipv6 implementations? • Seems unlikely given how simple this is • What about router support? • Surprisingly few “martian” checks for 240/4 • Cisco DCOS done; IOS, XR bug fixes opened • Don’t know about Juniper, others • Microsoft and 6to4 tunneling • Application knows if address is public/private • But should this prevent kernel changes?

  7. Last words • 240/4 is not a panacea but it may help • No consensus yet on public/private… • …code changes are simple • …and status can be decided later • “Let’s Do It”

  8. Questions? Comments?

More Related