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
Kommentare zu diesen Handbüchern