Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option
RFC 4580

 
Document Type RFC - Proposed Standard (June 2006; No errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 4580 (Proposed Standard)
Telechat date
Responsible AD Margaret Wasserman
Send notices to rdroms@cisco.com, sv@ecs.soton.ac.uk
Network Working Group                                            B. Volz
Request for Comments: 4580                           Cisco Systems, Inc.
Category: Standards Track                                      June 2006

         Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
                    Relay Agent Subscriber-ID Option

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 (2006).

Abstract

   This memo defines a new Relay Agent Subscriber-ID option for the
   Dynamic Host Configuration Protocol for IPv6 (DHCPv6).  The option
   allows a DHCPv6 relay agent to associate a stable "Subscriber-ID"
   with DHCPv6 client messages in a way that is independent of the
   client and of the underlying physical network infrastructure.

Table of Contents

   1. Introduction ....................................................2
   2. The Relay Agent Subscriber-ID Option ............................2
   3. DHCPv6 Relay Agent Behavior .....................................3
   4. DHCPv6 Server Behavior ..........................................3
   5. Security Considerations .........................................4
   6. IANA Considerations .............................................4
   7. Acknowledgements ................................................4
   8. References ......................................................4
      8.1. Normative References .......................................4
      8.2. Informative References .....................................4

Volz                        Standards Track                     [Page 1]
RFC 4580               Relay Agent Subscriber-ID               June 2006

1.  Introduction

   DHCPv6 [1] provides IP addresses and configuration information for
   IPv6 clients.  It includes a relay agent capability, in which
   processes within the network infrastructure receive multicast
   messages from clients and relay them to DHCPv6 servers.  In some
   network environments, it will be useful for the relay agent to add
   information to the DHCPv6 message before relaying it.

   The information that relay agents supply can also be used in the
   server's decision-making about the addresses, delegated prefixes [2],
   and configuration parameters that the client is to receive.

   In many service-provider environments, it is believed to be desirable
   to associate some provider-specific information with clients' DHCPv6
   messages that is independent of the physical network configuration
   and that the relay agent has learned through some means that is
   outside the scope of this memo.

2.  The Relay Agent Subscriber-ID Option

   In complex service provider environments, there is a need to connect
   a customer's DHCPv6 configuration with the customer's administrative
   information.  The Relay Agent Subscriber-ID option carries a value
   that can be independent of the physical network configuration through
   which the subscriber is connected.  This value complements, and might
   well be used in addition to, the network-based information.  The
   "subscriber-id" assigned by the provider is intended to be stable as
   customers connect through different paths, and as network changes
   occur.

   The subscriber-id information allows the service provider to assign/
   activate subscriber-specific actions; e.g., assignment of specific IP
   addresses, prefixes, DNS configuration, trigger accounting, etc.
   This option is de-coupled from the access network's physical
   structure, so a subscriber that moves from one access-point to
   another, for example, would not require reconfiguration at the
   service provider's DHCPv6 servers.

   The subscriber-id information is only intended for use within a
   single administrative domain and is only exchanged between the relay
   agents and DHCPv6 servers within that domain.  Therefore, the format
   and encoding of the data in the option is not standardized, and this
   specification does not establish any semantic requirements on the
   data.  This specification only defines the option for conveying this
   information from relay agents to DHCPv6 servers.

Volz                        Standards Track                     [Page 2]
RFC 4580               Relay Agent Subscriber-ID               June 2006

   However, as the DHCPv4 Subscriber-ID suboption [3] specifies Network
Show full document text