Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4) (RFC3925)

IP.com Disclosure Number: IPCOM000032249D
Original Publication Date: 2004-Oct-01
Included in the Prior Art Database: 2004-Oct-27
Document File: 10 page(s) / 18K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Littlefield: AUTHOR

Abstract

The Dynamic Host Configuration Protocol (DHCP) options for Vendor Class and Vendor-Specific Information can be limiting or ambiguous when a DHCP client represents multiple vendors. This document defines two new options, modeled on the IPv6 options for vendor class and vendor-specific information, that contain Enterprise Numbers to remove ambiguity.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 15% of the total text.

Network Working Group                                     J. Littlefield

Request for Comments: 3925                           Cisco Systems, Inc.

Category: Standards Track                                   October 2004

                 Vendor-Identifying Vendor Options for

         Dynamic Host Configuration Protocol version 4 (DHCPv4)

Status of this Memo

   This document specifies an Internet standards track protocol for the

   Internet community, and requests discussion and suggestions for

   improvements.  Please refer to the current edition of the "Internet

   Official Protocol Standards" (STD 1) for the standardization state

   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   The Dynamic Host Configuration Protocol (DHCP) options for Vendor

   Class and Vendor-Specific Information can be limiting or ambiguous

   when a DHCP client represents multiple vendors.  This document

   defines two new options, modeled on the IPv6 options for vendor class

   and vendor-specific information, that contain Enterprise Numbers to

   remove ambiguity.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2

       1.1.  Conventions Used in This Document. . . . . . . . . . . .  2

   2.  Supporting Multiple Vendor Instances . . . . . . . . . . . . .  3

   3.  Vendor-Identifying Vendor Class Option . . . . . . . . . . . .  3

   4.  Vendor-Identifying Vendor-Specific Information Option  . . . .  5

   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  7

   6.  Security Considerations  . . . . . . . . . . . . . . . . . . .  7

   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  8

       7.1.  Normative References . . . . . . . . . . . . . . . . . .  8

       7.2.  Informative References . . . . . . . . . . . . . . . . .  8

   8.  Author's Address . . . . . . . . . . . . . . . . . . . . . . .  8

   9.  Full Copyright Statement . . . . . . . . . . . . . . . . . . .  9

Littlefield                 Standards Track                     [Page 1]

RFC 3925           Vendor-Identifying Vendor Options        October 2004

1.  Introduction

   The DHCP protocol for IPv4, RFC 2131 [2], defines options that allow

   a client to indicate its vendor type (option 60), and the DHCP client

   and server to exchange vendor-specific information (option 43) [5].

   Although there is no prohibition against passing multiple copies of

   these options in a single packet, doing so would introduce ambiguity

   of interpretation, particularly if conveying vendor-specific

   information for multiple vendors.  The vendor identified by option 60

   define...