[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[dhcwg] Add WG item: draft-hunt-dhcpv6-clarify-mrc-00

To: dhc WG <dhcwg at ietf.org>
Subject: [dhcwg] Add WG item: draft-hunt-dhcpv6-clarify-mrc-00
From: Ted Lemon <Ted.Lemon at nominum.com>
Date: Thu, 25 Jun 2009 00:27:17 -0700
Delivered-to: dhcwg at core3.amsl.com
List-archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-help: <mailto:dhcwg-request@ietf.org?subject=help>
List-id: <dhcwg.ietf.org>
List-post: <mailto:dhcwg@ietf.org>
List-subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>

This was discussed at the San Francisco IETF, and the consensus in theroom was to adopt it as a working group item. The draft clarifies anambiguity in the handling of the Maximum Retry Count (MRC) constant.This draft will become a working group item if no objections are heardprior to Thursday, 7/2/2009, by 5:00 pm.

Follow-Ups:
- Re: [dhcwg] Add WG item: draft-hunt-dhcpv6-clarify-mrc-00
  - From: Bernie Volz (volz)

Prev by Date: Re: [dhcwg] draft-miles-dhc-dhcpv5-ldra-02.txt: adopt as a working group item?
Next by Date: Re: [dhcwg] Add WG item: draft-hunt-dhcpv6-clarify-mrc-00
Previous by thread: [dhcwg] I-D Action:draft-ietf-dhc-forcerenew-nonce-00.txt
Next by thread: Re: [dhcwg] Add WG item: draft-hunt-dhcpv6-clarify-mrc-00
Index(es):
- Date
- Thread