Re: Question about Vendor option
Ralph Droms <droms@bucknell.edu> Fri, 01 March 1996 04:52 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03685;
29 Feb 96 23:52 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03679;
29 Feb 96 23:52 EST
Received: from coral.bucknell.edu by CNRI.Reston.VA.US id aa00681;
29 Feb 96 23:52 EST
Received: from charcoal-gw.eg.bucknell.edu by coral.bucknell.edu;
(5.65v3.0/1.1.8.2/29Aug94-0956AM)
id AA20399; Thu, 29 Feb 1996 23:38:09 -0500
Received: from reef.bucknell.edu by charcoal (5.x/SMI-SVR4)
id AA01801; Thu, 29 Feb 1996 23:30:19 -0500
Received: from coral.bucknell.edu by reef.bucknell.edu with SMTP
(5.65/IDA-1.2.8) id AA07489; Thu, 29 Feb 1996 23:30:16 -0500
Received: from droms.bucknell.edu by coral.bucknell.edu;
(5.65v3.0/1.1.8.2/29Aug94-0956AM)
id AA18729; Thu, 29 Feb 1996 23:30:13 -0500
Date: Thu, 29 Feb 1996 23:30:13 -0500
X-Sender: droms@mail.bucknell.edu
Message-Id: <v02120d02ad5ab8780f89@[134.82.7.156]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: dhcp-v4@bucknell.edu
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Ralph Droms <droms@bucknell.edu>
Subject: Re: Question about Vendor option
Cc: B Mahesh <mahesh@wipro.wipsys.soft.net>
At 11:21 AM 2/28/96, B Mahesh wrote: >As per RFC 1533, Sec 9.6, each requested parameter is a >valid DHCP option code. >^^^^^^^^^^^^^^^^^^^^^^^ > >What does the term 'valid DHCP option code' refer to ? Can the option >code be any of the numbers specified in RFC1533, that include the RFC1497 >vendor extensionsi also? Yes, the code can be any RFC1533 option or any option defined subsequently in a later DHCP options RFC. - Ralph
- Re: Question about Vendor option Ralph Droms
- Question about Vendor option B Mahesh
- Re: Question about Vendor option KEY