[Docs] [txt|pdf] [Tracker] [WG] [Email] [Nits]

Versions: 00 01 02 03 04 05 06 07 08 09 RFC 3004

Network Working Group                                   Glenn Stump, IBM
INTERNET DRAFT                          Ralph Droms, Bucknell University
                                                           November 1996
                                                        Expires May 1996


                     The User Class Option for DHCP
                   <draft-ietf-dhc-userclass-00.txt>

Status of this Memo

   This document is an Internet-Draft.  Internet-Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as ``work in progress.''

   To learn the current status of any Internet-Draft, please check the
   ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow
   Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
   munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
   ftp.isi.edu (US West Coast).

1. Abstract

   This option is used by a DHCP client to optionally identify the type
   or category of user or applications it represents.  The information
   contained in this option is an NVT ASCII text object that represents
   the user class of which the client is a member.

2. Definitions

   Throughout this document, the words that are used to define the
   significance of particular requirements are capitalized.  These words
   are:

      o "MUST"

        This word or the adjective "REQUIRED" means that the
        item is an absolute requirement of this specification.







Stump, Droms                                                    [Page 1]


DRAFT                The User Class Option for DHCP           April 1996


      o "MUST NOT"

        This phrase means that the item is an absolute prohibition
        of this specification.

      o "SHOULD"

        This word or the adjective "RECOMMENDED" means that there
        may exist valid reasons in particular circumstances to ignore
        this item, but the full implications should be understood and
        the case carefully weighed before choosing a different course.

      o "SHOULD NOT"

        This phrase means that there may exist valid reasons in
        particular circumstances when the listed behavior is acceptable
        or even useful, but the full implications should be understood
        and the case carefully weighed before implementing any behavior
        described with this label.

      o "MAY"

        This word or the adjective "OPTIONAL" means that this item is
        truly optional.  One vendor may choose to include the item
        because a particular marketplace requires it or because it
        enhances the product, for example; another vendor may omit the
        same item.


   This document also uses the following terms:

      o "DHCP client"

        A DHCP client or "client" is an Internet host using DHCP to obtain
        configuration parameters such as a network address.

      o "DHCP server"

        A DHCP server of "server"is an Internet host that returns
        configuration parameters to DHCP clients.

      o "binding"

        A binding is a collection of configuration parameters, including
        at least an IP address, associated with or "bound to" a DHCP
        client.  Bindings are managed by DHCP servers.





Stump, Droms                                                    [Page 2]


DRAFT                The User Class Option for DHCP           April 1996


3. User Class Information

   This option is used by a DHCP client to optionally identify the type
   or category of user or applications it represents.  The information
   contained in this option is an NVT ASCII text object that represents
   the user class of which the client is a member.

   DHCP administrators may define specific user class identifiers to
   convey information about a client's software configuration or about
   its user's preferences.  For example, an identifier may specify that
   a particular DHCP client is a member of the class "accounting
   auditors", which have special service needs such as a particular
   database server.

   Servers not equipped to interpret the user class specified by a
   client MUST ignore it (although it may be reported).  Otherwise,
   servers SHOULD respond with the set of options corresponding to the
   user class specified by the client.  Further, if the server responds
   with the set of options corresponding to the given user class, it
   MUST return this option (with the given user class value) to the
   client.

   Clients which do not receive information for the user class requested
   SHOULD make an attempt to operate without it, although they may do so
   (and may announce they are doing so) in a degraded mode.

   The code for this option is 77.  The minimum length for this option
   is two.

      Code   Len     text1
     +-----+-----+-----+-----+-----
     | 77  |  N  |  c1 |  c2 | ...
     +-----+-----+-----+-----+-----

Security Considerations

   Security issues are not discussed in this document.

References

   [DHCP] Droms, R., "Dynamic Host Configuration Protocol", RFC1541,
   October 1993

Acknowledgments







Stump, Droms                                                    [Page 3]


DRAFT                The User Class Option for DHCP           April 1996


Author Information


   Glenn Stump
   IBM Networking Software Solutions
   4205 South Miami Blvd.
   RTP, NC 27709
   Phone: (919) 254-5616
   email: glennstump@vnet.ibm.com

   Ralph Droms
   Computer Science Department
   323 Dana Engineering
   Bucknell University
   Lewisburg, PA 17837
   Phone: (717) 524-1145
   email: droms@bucknell.edu


































Stump, Droms                                                    [Page 4]


Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/