Re: [dhcwg] Revised charter

Jinmei-san - thanks for catching the typo, and I will add
a reference to the newly published RFC 3736.

- Ralph

At 11:08 AM 4/9/2004 +0900, JINMEI Tatuya / 
=?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= wrote:
> >>>>> On Wed, 07 Apr 2004 08:53:58 -0400,
> >>>>> Ralph Droms <rdroms@cisco.com> said:
>
> > Here is a draft charter for the WG, based on discussion at the WG 
> meeting in
> > Seoul and discussion on the mailing list.  Please review and respond with
> > comments.
>
>It basically looks good.  A couple of minor comments:
>
> > Standard" and is documented in RFC3315.  Subsequent RFCS document
> > additional options and other enhancements to the specifications.
>
>s/RFCS/RFCs/ ?
>
> > * The DHCPv6 specification in RFC3315 includes a mechanism through
> >    which clients can obtain other configuration information without
> >    obtaining an address or addresses.  This mechanisms is sometimes
> >    called "stateless DHCPv6".  RFC3315 includes no provision for
> >    notifying DHCPv6 clients using stateless DHCPv6 of changes in the
> >    configuration information supplied to the client or any
> >    recommendations as to when a client should obtain possibly updated
> >    information.  The dhc WG will assess the requirements for informing
> >    DHCPv6 clients of changes in configuration information, review
> >    alternative solutions and select a solution, and develop, review and
> >    publish a specification for the chosen solution.
>
>We may want to add RFC3736 as a reference of "stateless DHCPv6".
>
>                                         JINMEI, Tatuya
>                                         Communication Platform Lab.
>                                         Corporate R&D Center, Toshiba Corp.
>                                         jinmei@isl.rdc.toshiba.co.jp

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg