Re: [dhcwg] Options in base doc for DHCPv6
Jim Bound <seamus@bit-net.com> Wed, 23 January 2002 19:28 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21614 for <dhcwg-archive@odin.ietf.org>; Wed, 23 Jan 2002 14:28:35 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id OAA12997 for dhcwg-archive@odin.ietf.org; Wed, 23 Jan 2002 14:28:37 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11361; Wed, 23 Jan 2002 13:53:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11334 for <dhcwg@optimus.ietf.org>; Wed, 23 Jan 2002 13:53:22 -0500 (EST)
Received: from mail.users.bit-net.com (www.bit-net.com [208.146.132.4]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA20467 for <dhcwg@ietf.org>; Wed, 23 Jan 2002 13:53:19 -0500 (EST)
Received: from localhost by mail.users.bit-net.com; (5.65v3.2/1.1.8.2/30Jul96-0143PM) id AB02088; Wed, 23 Jan 2002 13:53:11 -0500
Date: Wed, 23 Jan 2002 13:53:11 -0500
From: Jim Bound <seamus@bit-net.com>
Reply-To: Jim Bound <seamus@bit-net.com>
To: Martin Stiemerling <Martin.Stiemerling@ccrle.nec.de>
Cc: Ralph Droms <rdroms@cisco.com>, dhcwg@ietf.org
Subject: Re: [dhcwg] Options in base doc for DHCPv6
In-Reply-To: <5890000.1011774024@elgar>
Message-Id: <Pine.OSF.3.95.1020123134222.8303B-100000@www.bit-net.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Martin, Exactly why we need these options now. IPv6 is being deployed. It will take at least 3 IETF meetings to get a specific options draft after dhc6. We cannot wait. Also these options will not hold up the processs. They are pretty basic. /jim On Wed, 23 Jan 2002, Martin Stiemerling wrote: > I totally agree with this. Escpecially the point of slowing down the > acceptance process is worth to mention. A lot of IPv6 networks are in the > deployment process or will be deployed in the near future and DHCPv6 is > needed for this deployment, i.e. there should be a standard. > > Martin > > > > --On Dienstag, Januar 22, 2002 14:55:41 -0500 Ralph Droms > <rdroms@cisco.com> wrote: > > > We've recently experienced a proliferation of proposed and defined > > options for DHCPv6. Initially, the WG agreed to publish all options that > > were defined at the time the base spec was completed in the same doc. > > I'm having second thoughts about that decision. Here's what I'm thinking: > > > > * The new options are adding more weight to > > an already hefty document > > * Keeping all the options in one doc make > > updating any one option more complicated > > * Reviewing all of these options will slow > > down the acceptance process > > > > I propose that we put a moratorium on adding any new options to > > draft-ietf-dhc-dhcpv6-22.txt, and move any non-essential options out of > > draft-ietf-dhc-dhcpv6-22.txt into individual drafts. The definition of > > "essential" is open to discussion; here's a first pass at a list of the > > options to retain in draft-ietf-dhc-dhcpv6-22.txt: > > > > * DHCP unique identifier option > > * Identity association option > > * IA Address option > > * Requested Temporary Addresses (RTA) Option > > * Option request option > > * Preference option > > * Elapsed Time > > * Client message option > > * Server message option > > * Authentication option > > * Server unicast option > > * Domain Search Option > > * Domain Name Server Option > > * Status Code Option > > > > - Ralph > > > > > > _______________________________________________ > > dhcwg mailing list > > dhcwg@ietf.org > > https://www1.ietf.org/mailman/listinfo/dhcwg > > > > > > Martin Stiemerling > > NEC Europe Ltd. -- Network Laboratories Martin.Stiemerling@ccrle.nec.de > IPv4: http://www.ccrle.nec.de IPv6: http://www.ipv6.ccrle.nec.de > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Options in base doc for DHCPv6 Ralph Droms
- Re: [dhcwg] Options in base doc for DHCPv6 Mark Stapp
- Re: [dhcwg] Options in base doc for DHCPv6 Jim Bound
- RE: [dhcwg] Options in base doc for DHCPv6 Bernie Volz (EUD)
- RE: [dhcwg] Options in base doc for DHCPv6 Jim Bound
- Re: [dhcwg] Options in base doc for DHCPv6 Jitesh N Verma
- RE: [dhcwg] Options in base doc for DHCPv6 Bernie Volz (EUD)
- Re: [dhcwg] Options in base doc for DHCPv6 Martin Stiemerling
- Re: [dhcwg] Options in base doc for DHCPv6 Ralph Droms
- Re: [dhcwg] Options in base doc for DHCPv6 Vijay Bhaskar A K
- Re: [dhcwg] Options in base doc for DHCPv6 Ted Lemon
- RE: [dhcwg] Options in base doc for DHCPv6 Jim Bound
- Re: [dhcwg] Options in base doc for DHCPv6 Vijay Bhaskar A K
- Re: [dhcwg] Options in base doc for DHCPv6 John Schnizlein
- Re: [dhcwg] Options in base doc for DHCPv6 Jim Bound
- Re: [dhcwg] Options in base doc for DHCPv6 Ted Lemon
- RE: [dhcwg] Options in base doc for DHCPv6 Richard Barr Hibbs
- Re: [dhcwg] Options in base doc for DHCPv6 Jitesh N Verma
- Re: [dhcwg] Options in base doc for DHCPv6 Martin Stiemerling
- RE: [dhcwg] Options in base doc for DHCPv6 Ralph Droms
- RE: [dhcwg] Options in base doc for DHCPv6 Jim Bound
- RE: [dhcwg] Options in base doc for DHCPv6 Bernie Volz (EUD)
- Re: [dhcwg] Options in base doc for DHCPv6 Ted Lemon
- Re: [dhcwg] Options in base doc for DHCPv6 Ted Lemon
- Re: [dhcwg] Options in base doc for DHCPv6 Ralph Droms
- Re: [dhcwg] Options in base doc for DHCPv6 Ted Lemon
- RE: [dhcwg] Options in base doc for DHCPv6 Ralph Droms