1 / 5

draft-ietf-dhc-dhcpv6-stateful-issues

draft-ietf-dhc-dhcpv6-stateful-issues. IETF 87 DHC WG Berlin, Germany Thursday, 1 August, 2013. ‘Recent’ Activity. WG LC issues in December/January 2013 Several issues raised Some addressed in 04 (published May 2013) Some still outstanding Rebind issue (sent to ML but no feedback)

sereno
Download Presentation

draft-ietf-dhc-dhcpv6-stateful-issues

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. draft-ietf-dhc-dhcpv6-stateful-issues IETF 87 DHC WG Berlin, Germany Thursday, 1 August, 2013

  2. ‘Recent’ Activity • WG LC issues in December/January 2013 • Several issues raised • Some addressed in 04 (published May 2013) • Some still outstanding • Rebind issue (sent to ML but no feedback) • Karl Auer raised Rebind issue on ipv6 mailing list (6/26) • A few others (mostly just digging through the comments and trying to resolve them)

  3. Rebind Issues • RFC 3315, 18.2.4. Receipt of Rebind Messages • Doesn’t mention use of NoBinding Status (as is discussed in 18.1.8. Receipt of Reply Messages) • Covers only some cases: • IA is found & addresses OK • IA is found and addresses not OK (not on link) • IA is not found and addresses not OK (not on link) • Missing other cases: • IA not found & addresses OK • Other conflicts than “not on link” (in use by another client/binding or not available) • Can new addresses be given? Note Solicit w/Rapid Commit concern (multiple servers responding)

  4. My Rebind Recommendations • Keep it simple – use 0 lifetimes for any requested address that is not usable (not on link, in use, etc.) • Don’t allocate new addresses except if Rapid Commit allowed • Server can assign address(es) if no conflict (client is already using it) • Assume client will return to Request (or Solicit) if no usable addresses result for binding • Allow NoBinding status if server wants to use it (forces client back to Request) but no reason to require it • Server can also elect to send no response if it believes it can not determine on-link status of addresses

  5. Next Steps • Comments on Rebind Recommendations • Resolve other prior comments • New comments? Please review 04! • Publish 05 (hopefully by early September) • Last Call (in September)

More Related