1 / 9

DHCPv6 refresh RFC3315bis

DHCPv6 refresh RFC3315bis. Vancouver, 2013-11-05 Tomek Mrugalski < tomasz.mrugalski@gmail.com >. IETF-88 DHC WG. 1. Motivation. DHCPv6 is a hugely successful protocol Over 10 years old, aged nicely Some things were deprecated Advancing along standards track

ariane
Download Presentation

DHCPv6 refresh RFC3315bis

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. DHCPv6 refresh RFC3315bis Vancouver, 2013-11-05 Tomek Mrugalski <tomasz.mrugalski@gmail.com> IETF-88 DHC WG 1

  2. Motivation • DHCPv6 is a hugely successful protocol • Over 10 years old, aged nicely • Some things were deprecated • Advancing along standards track • Addrsand prefixes are handled slightly differently • Clarifications • Corrections • Minor updates (e.g. solmaxrt) • No new features IETF-88 DHC WG 2

  3. The plan Assemble editors/”design” team Convert 3315, 3633 to xml Pick a list of RFCs/drafts to include Produce I-D that includes results from #2 Follow the usual WG path + extras Use issue tracker to manage changes IETF-88 DHC WG 3

  4. 1. Editors team • Call for volunteers • Tomek volunteered to organize this work • Similar to design teams, but nothing to design • Lots of editorial work • Preferred size: 5-6 people • Need weekly/bi-weekly calls? (No?) • Everything over mails? (Yes?) IETF-88 DHC WG 4

  5. 2. Convert to XML • xml2rfc was not used in 2003 • We have rfc3315.txt and rfc3315.nroff • RFC Editor keeps nroff files for published RFCs • Possibly useful tools: • rfc2xml1 • nroff2xml2 • 1) http://sourceforge.net/projects/rfc2xml/ • 2) https://github.com/tomaszmrugalski/nroff2xml IETF-88 DHC WG 5

  6. 3. RFCs/I-Ds to merge • Possible candidates to merge: • RFC3315 (you should recognize this :) • RFC3633 (PD) • RFC3736 (stateless DHCPv6) • Pick pieces from/add references to: • dhc-stateful-issues • dhc-dhcpv6-solmaxrt-update • RFC6355 (DUID-UUID) • RFC6644 (rebind in reconfigure) • RFC6422 (relay supplied options) • ... • Pick a minimal # of documents for merge/reference others • No decision today, that's a job for editors team IETF-88 DHC WG 6

  7. 4. Dealing with changes • Erratas, corrections, minor improvements • Need to manage those changes (issue tracker?) • Examples: • Must not interpret DUID content • Obsolete site-local addrs (e.g. ff05::1:3) • Requesting nested options • Handle unknown messages • Clarify: relay agents not modify relayed message • … IETF-88 DHC WG 7

  8. 5. Work Organization • Need a place to keep intermediate drafts • Proposal: github • https://github.com/dhcwg/rfc3315bis • Free, ads free, public, git, history • No need for separate list, stick to DHC list • Need to manage list of issuesProposal: DHC issue trackerhttp://trac.tools.ietf.org/wg/dhc/trac/report/1 IETF-88 DHC WG 8

  9. 6. Schedule • We have milestones defined! • Oct 2013: Appoint editor, assemble design team for 3315bis work • Nov 2013: Decide which RFCs/drafts to merge • Mar 2014: Adopt 3315bis draft • Nov 2014: WG last call on 331bis draft • Apr 2015: Submit 3315bis draft to IESG • Need to adjust them a bit… IETF-88 DHC WG 9

More Related