Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04543 for ; Wed, 9 Oct 2002 16:58:48 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g99L0U017965 for dhcwg-archive@odin.ietf.org; Wed, 9 Oct 2002 17:00:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99L0Uv17962 for ; Wed, 9 Oct 2002 17:00:30 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04534 for ; Wed, 9 Oct 2002 16:58:16 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Kw2v17543; Wed, 9 Oct 2002 16:58:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Kv1v17510 for ; Wed, 9 Oct 2002 16:57:01 -0400 Received: from imr1.ericy.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04192 for ; Wed, 9 Oct 2002 16:54:48 -0400 (EDT) Received: from mr5.exu.ericsson.se (mr5u3.ericy.com [208.237.135.124]) by imr1.ericy.com (8.11.3/8.11.3) with ESMTP id g99Kusj15658; Wed, 9 Oct 2002 15:56:54 -0500 (CDT) Received: from eamrcnt761.exu.ericsson.se (eamrcnt761.exu.ericsson.se [138.85.133.39]) by mr5.exu.ericsson.se (8.11.3/8.11.3) with ESMTP id g99KusK19309; Wed, 9 Oct 2002 15:56:54 -0500 (CDT) Received: by eamrcnt761.exu.ericsson.se with Internet Mail Service (5.5.2656.59) id <41PAP34R>; Wed, 9 Oct 2002 15:56:54 -0500 Message-ID: From: "Bernie Volz (EUD)" To: "'Ralph Droms'" , dhcwg@ietf.org Subject: RE: [dhcwg] Fwd: RFC-to-be: Date: Wed, 9 Oct 2002 15:56:53 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C26FD6.0EBD0BB0" Sender: dhcwg-admin@ietf.org Errors-To: dhcwg-admin@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C26FD6.0EBD0BB0 Content-Type: text/plain; charset="iso-8859-1" What about adding: 115 Failover N DHCP Failover Protocol That option was probably used in some of the early failover protocol designs? It is not used in DRAFT-IETF-DHC-FAILOVER-10.TXT. - Bernie -----Original Message----- From: Ralph Droms [mailto:rdroms@cisco.com] Sent: Wednesday, October 09, 2002 4:52 PM To: dhcwg@ietf.org Subject: [dhcwg] Fwd: RFC-to-be: Well, considering we're now at option code 121, perhaps I should start the process of resolving the status of some of the unused option codes. Here are some option codes that should be easy to decide on: Option Name code ------ -------- 83, 84 Relay agent options 89 FQDNs in DHCP options 91 VINES TCP/IP server 96 IPv6 Transition 100 Printer name 101-107 Multicast assignment through DHCP 108 Swap path 110 IPX compatibility These option codes were assigned based on requests to IANA, but none of the associated options were ever published as RFCs. I've tried to contact the persons to whom these option codes were assigned, and have either received an ack that the option codes can be returned or no response to my e-mail. As an informal next step, please respond to the mailing list if you know of any implementation or use of any of these option codes. - Ralph >From: "IANA" >To: , , > >Cc: >Subject: RFC-to-be: >Date: Wed, 9 Oct 2002 13:16:48 -0700 >X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) >Importance: Normal > >Authors: > >We are working on the IANA Actions for RFC-to-be: >. > >We have assigned value 121 to the Classless Static >Route Option. Please see the following for the >registration and make sure everything looks OK: > > > >Please reply back with a final OK so that we may >send a message to the RFC Editor indicating that the >IANA Actions are completed. > >Thank you, > >Michelle S. Cotton >IANA Administrator _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg ------_=_NextPart_001_01C26FD6.0EBD0BB0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [dhcwg] Fwd: RFC-to-be: = <draft-ietf-dhc-csr-07.txt>

What about adding:

   115     = Failover          &nbs= p;      N    DHCP Failover = Protocol

That option was probably used in some of the early = failover protocol
designs? It is not used in = DRAFT-IETF-DHC-FAILOVER-10.TXT.

- Bernie

-----Original Message-----
From: Ralph Droms [mailto:rdroms@cisco.com]
Sent: Wednesday, October 09, 2002 4:52 PM
To: dhcwg@ietf.org
Subject: [dhcwg] Fwd: RFC-to-be: = <draft-ietf-dhc-csr-07.txt>


Well, considering we're now at option code 121, = perhaps I should start the
process of resolving the status of some of the = unused option codes.  Here
are some option codes that should be easy to decide = on:

Option  Name
code
------  --------
83, 84   Relay agent options
89       FQDNs in DHCP = options
91       VINES TCP/IP = server
96       IPv6 = Transition
100      Printer = name
101-107 Multicast assignment through DHCP
108      Swap path
110      IPX = compatibility

These option codes were assigned based on requests to = IANA, but none of the
associated options were ever published as = RFCs.  I've tried to contact the
persons to whom these option codes were assigned, = and have either received
an ack that the option codes can be returned or no = response to my
e-mail.  As an informal next step, please = respond to the mailing list if
you know of any implementation or use of any of = these option codes.

- Ralph


>From: "IANA" = <iana@icann.org>
>To: <Ted.Lemon@nominum.com>, = <rfc@stuartcheshire.org>,
>         = <bernie.volz@ericsson.com>
>Cc: <rdroms@cisco.com>
>Subject: RFC-to-be: = <draft-ietf-dhc-csr-07.txt>
>Date: Wed, 9 Oct 2002 13:16:48 -0700
>X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 = (9.0.2911.0)
>Importance: Normal
>
>Authors:
>
>We are working on the IANA Actions for = RFC-to-be:
><draft-ietf-dhc-csr-07.txt>.
>
>We have assigned value 121 to the Classless = Static
>Route Option.  Please see the following for = the
>registration and make sure everything looks = OK:
>
><http://www.iana.org/assignments/bootp-dhcp-parameters<= /A>>
>
>Please reply back with a final OK so that we = may
>send a message to the RFC Editor indicating that = the
>IANA Actions are completed.
>
>Thank you,
>
>Michelle S. Cotton
>IANA Administrator

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

------_=_NextPart_001_01C26FD6.0EBD0BB0-- _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg