dhc WGDRAFT

IETF 82

2011-11-17

1

2

NOTE WELLAny submission to the IETF intended by the Contributor for publication as all or part of

an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:

• the IETF plenary session, • any IETF working group or portion thereof, • the IESG, or any member thereof on behalf of the IESG, • the IAB or any member thereof on behalf of the IAB, • any IETF mailing list, including the IETF list itself, any working group or design team

list, or any other list functioning under IETF auspices, • the RFC Editor or the Internet-Drafts functionAll IETF Contributions are subject to the rules of RFC 3978 (updated by RFC 4748) and

RFC 3979(updated by RFC 4879).Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice.

Please consult RFC 3978 (and RFC 4748) for details. A participant in any IETF activity is deemed to accept all IETF rules of process, as

documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of

meetings may be made and may be available to the public.

3

AgendaThursday, 0900-1130, November 17, 2011, Room 102

Introduction, Agenda Bashing, Document Status, Chairs, 10 min.Client Hardware Address Option in DHCPv6, Wojciech Dec, 5 MinutesDHCPv6 class based prefix, Shwetha Bhandari, 15 minutesRelay Agent Encapsulation for DHCPv4, Ted Lemon, 5 minutesPost-WGLC status of Redundancy Considerations draft, Tomasz Mrugalski, 5 minutesDHCPv6 suboptions clarification draft, Tomasz Mrugalski, 5 minutesDHCPv6 route options draft, 5 minutesClient Identifier Option in DHCP Server Replies, Shwetha Bhandari, 5 minutesModification to Default Value of MAX_SOL_RT, Ralph Droms, 10mPort Set Extension for DHCPv4 (Lightweight 4over6), Qiong Sun, 10 minutesDHCPv6 and Multihoming Problem Statement, Ted Lemon, 10 minutesExplicit DHCPv6 hint for IPv6 Prefix Delegation, John Jason Brzozowski, 10mDHCPv4 option exhaustion, Ted Lemon, 5mDHCPv6 option formats, Ted Lemon, 5m

4

Adminisitrivia

• Meeting materials at– https://datatracker.ietf.org/meeting/82/materials.html

• Meeting, jabber scribes?

• Jabber info– dhc@jabber.ietf.org

• Other dhc WG info– tools.ietf.org/wg/dhc

5

dhc WG I-D status• Submitted to IESG

draft-ietf-dhc-subnet-alloc-12draft-ietf-dhc-vpn-option-14draft-ietf-dhc-pd-exclude-03draft-ietf-dhc-dhcpv6-relay-supplied-options-

09• Ready for submission to IESG

draft-ietf-dhc-dhcpv6-redundancy-consider-00draft-ietf-dhc-forcerenew-nonce-01

• In WG last call• Ready for WG last call• Review required

draft-ietf-dhc-l2ra-05draft-ietf-dhc-relay-id-suboption-09draft-ietf-dhc-host-gen-id-00draft-ietf-dhc-secure-dhcpv6-03

dhc WG I-D status• Mailing list discussion required• Requires update

draft-ietf-dhc-cga-config-dhcpv6-00• Status update

draft-ietf-dhc-option-guidelines-07draft-ietf-dhc-dhcpinform-clarify-06draft-ietf-dhc-dhcpv6-reconfigure-rebind-08draft-ietf-dhc-dhcpv4-relay-encapsulation-01draft-ietf-dhc-client-id-01

2009/03/25 IETF 74 - dhc WG 6