1 / 7

DHCP Failover Protocol

DHCP Failover Protocol. Report on Current Status December 11, 2000 Kim Kinnear. Failover Conference Calls. Held October 27 and November 14, 2000. Meeting minutes distributed on dhcp-v4 list. Discussed: - Issues surrounding lease ownership and pool allocation for secondary servers.

topaz
Download Presentation

DHCP Failover Protocol

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. DHCP Failover Protocol Report on Current Status December 11, 2000 Kim Kinnear

  2. Failover Conference Calls • Held October 27 and November 14, 2000. • Meeting minutes distributed on dhcp-v4 list. • Discussed: - Issues surrounding lease ownership and pool allocation for secondary servers. - Handling of Dynamic bootp leases and "reservations. - Massive resychronization required when bringing in new secondary server. - Comments derived from implementation experience with 06/07 draft. - What to do to move this draft towards last call? • New draft: draft-ietf-dhc-failover-08.txt.

  3. Ralph Droms (DHC WG/Cisco) Steve Gonczi (Process) Richard Jones (MetaIP) Kim Kinnear (Cisco) Ted Lemon (ISC) Thomas Narten (Area Dir/IBM) Greg Rabil (Lucent) Mark Stapp (Cisco) Sri Hary Vengadasubbu (Cisco) Bernie Volz (Process) Attendees (to at least one call)

  4. Major Changes in -08 draft • New state to synchronize responsiveness with load balancing: CONFLICT-DONE. • Tied in reject reasons to text in draft. • Added information on changing failover partners derived from real world experience • Sent out detailed list on dhcp-v4 list around submission.

  5. Additional Work Required: • Detailed review by authors, other technical people. • Synchronize with load-balancing draft : do we need to move to last call together?

  6. What was next for Failover?(Adelaide slide) • Conference call this spring on -06 draft. • Produce -07 draft prior to Pittsburgh IETF. • Another conference call in late summer. • Produce -08 draft prior to San Diego IETF with the goal of that draft going to WG last call. We are pretty much on track!

  7. What’s next for Failover? • Announce WG Last Call after San Deigo IETF. • Make changes required by comments from list. • Resubmit to IETF prior to Minneapolis. • Goal is last call complete before Minneapolis.

More Related