Administrivia		Brzozowski/Droms	0:15	3:35 PM
Agenda bashing; blue sheets; scribe; Jabber scribe				
Draft last call and adoption announcements

  Ralph thanked Stig Venaas for his good service a dhc WG co-chair and
  introduced John Brzozowski as the new co-chair.  The WG has pubished
  RFC 5107 and RFC 5071.  There was consensus to accept
  draft-raj-tftp-option as a WG work item and conduct WG last call;
  this consensus will be confirmed on the WG mailing list.

Report from DHCPv6 Bakeoff		A. Durand

  Comcast sponsored a third DHCPv6 bakeoff March 5-7.  The bakeoff
  tested interoperability among several implementations: 8 servers, 8
  clients, 4 relay agents.  Details of the tests and results along
  with some specific identified problems can be found in the slides.
  A minor inconsistency in the leasequery specification aws found; the
  WG will need to publish either an errata or an update RFC.

Virtual Subnet Selection Option
draft-ietf-dhc-vpn-option-08
K. Kinnear

  The authors have combined the client and realy agent subnet
  selection option specifications into a single I-D, and extended the
  specifications for IPv6.  The authors will publish a revision with
  updates from WG comments and review; that revised draft will be
  ready for WG last call and will be reviewed by Volz, Hankins and one
  other reviewer.

DHCPv6 Bulk Leasequery
draft-stapp-dhc-dhcpv6-bulk-leasequery-00
M. Stapp

  This revision of the specification uses TCP and new query types to
  clarify distinction between UDP leasequery and TCP bulk leasequery.
  The revision was accepted as WG work item; this acceptance will be
  confirmed on the WG mailing list.

A relay agent DUID for DHCPv4
draft-stapp-dhc-relay-id-00
M. Stapp

  This is a new I-D proposing a unique identifier for relay agents.
  The use case is certain deployment situations where other
  information like circuit id and IP address may not be sufficient.
  The I-D was accepted as WG work item; this acceptance will be
  confirmed on the WG mailing list.

DHCPv4 Leasequery by relay agent remote ID and circuit ID
draft-kurapati-dhc-leasequery-by-remote-id-00
B. Joshi

  This new I-D propsoes a new index for leasequery requests.  The I-D
  was accepted as WG work item; this acceptance will be confirmed on
  the WG mailing list.

Using DHCPv6 for Prefix Delegation in IEEE 802.16 Networks
draft-sarikaya-16ng-prefix-delegation-02
F. Xia

  This I-D is not a dhc WG work item.  The 16ng WG asked the dhc WG
  about colocating a DHCPv6 relay agent wth a DHCPv6 client as a way
  to allow unicast of DHCPv6 messages from a client to a server.  The
  preliminary advice to 16ng WG is that this architecture should be
  OK; discussion will continue on the WG mailing list.

Operational problems caused by inconsistent RA M/O flags
J. H. Cha

  (No draft) The presenter noted that RFC 4861 and RFC 4862 do not
  have text describing how to interpret M/O bits in a Router
  Advertisement.  Inconsistency in those bits in RAs may lead to
  operational problem.  There was no consensus in WG to confirm that
  R/A flag inconsistency is a real problem, or how it should be
  solved, or if it should go to v6ops.  Thomas Narten noted it is an
  implementation problem, and does not have a reasonable specification
  fix.

Kerberos server option for DHCPv6
draft-sakane-dhc-dhcpv6-kdc-option-00
S. Sakane

  Definition of a new DHCPv6 option for a list of Kerberos servers
  should be managed by the kerberos WG involved, For now, discussion
  will continue on the dhc WG mailing list.

Layer 2 Relay Agent Information
draft-ietf-dhc-l2ra-00
B. Joshi

   This I-D requires a little further discussion on WG mailing list
   before progressing to IESG as Informational.

Extensions to Layer 2 Relay Agent
draft-kurapati-dhc-l2ra-extensions-00
B. Joshi

   Also requires further discussion on WG mailing list; there may be
   an opportunity to improve L3 relay agent behavior as well.  This
   I-D depends on draft-ietf-dhc-l2ra-00 before progressing.

Configuring BFD with DHCP and Other Musings
draft-vinokour-bfd-dhcp-00
V. Vinokour

   The idea in this I-D is to use BFD to monitor L3 connectivity
   between a host and an L3 aggregation router.  The I-D proposes a
   DHCP option to carry BFD initialization information.  It also
   proposes DHCP behavior in case BFD detects loss of L3 connectivity.
   The I-D is proposed as a bfd WG work item so no dhc WG action is
   required at this time