rfc-3993

Subscriber-ID Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option

R. Johnson, T. Palaniappan, M. Stapp
date2005-03 streamIETF areaint wgdhc statusPROPOSED STANDARD pages7 canonicalhttps://www.rfc-editor.org/rfc/rfc3993 doi10.17487/RFC3993
This memo defines a new Subscriber-ID suboption for the Dynamic Host Configuration Protocol's (DHCP) relay agent information option. The suboption allows a DHCP relay agent to associate a stable "Subscriber-ID" with DHCP client messages in a way that is independent of the client and of the underlying physical network infrastructure. [STANDARDS-TRACK]

Extracted elements (12)

design-rationale §1

Existing relay agent suboptions (Remote-ID, Circuit-ID) are based on physical network resources like IP addresses or ATM virtual circuit identifiers, making them path-dependent. The Subscriber-ID suboption was designed to carry a stable, provider-assigned value independent of the physical connection path, so clients connecting through different paths receive consistent identification.

interoperability-note §3

The Subscriber-ID suboption complements rather than replaces existing network-based relay agent suboptions (Remote-ID, Circuit-ID defined in RFC 3046), and both may be used together in the same relay agent information option.

normative-requirement §6 SHOULD

A deeper defense using authentication for relay agent options via the Authentication Suboption or IPSec SHOULD be deployed in addition to perimeter defenses that block untrusted relay agent options.

security

normative-requirement §4 MAY

DHCP relay agents MAY be configured to include a Subscriber-ID suboption when they include a relay agent information option in relayed DHCP messages.

normative-requirement §3.1 MUST NOT

The Subscriber-ID string MUST NOT be NULL terminated; the length is specified in the Len field.

privacy-consideration §6

The Subscriber-ID suboption may convey information that identifies a specific host or user. If DHCP messages travel outside the service provider's network or suboption values become visible to other users, this may raise privacy concerns. Administrators should use identifiers appropriate to the network type.

privacy

protocol-element §3

The semantic contents of the Subscriber-ID string are provider-specific; this specification establishes no semantic requirements on the string data. The assignment and configuration of subscriber-id strings are outside the scope of this memo.

protocol-element §3

The Subscriber-ID suboption allows a DHCP relay agent to associate a stable, provider-assigned identifier with DHCP client messages, independent of the physical network infrastructure through which the subscriber connects.

registry §7

IANA assigned suboption code 6 from the DHCP Relay Agent Information Option suboption codes registry for the Subscriber-ID Suboption defined in this document.

registry

security-consideration §6

The DHCP relay agent option depends on a trusted relationship between the relay agent and server. Fraudulent relay agent option data could lead to theft-of-service, exhaustion of IP addresses, denial of service to legitimate hosts, or assignment of inappropriate configuration parameters.

security

security-consideration §6

While perimeter defenses can block fraudulent relay agent options from untrusted agents, authentication via the Authentication Suboption or IPSec should also be deployed as a deeper defense.

security, crypto

wire-format §3.1

The Subscriber-ID suboption has a 1-octet Code field (value 6), a 1-octet Len field indicating the length of the ID string in octets, and a variable-length NVT ASCII Subscriber-ID string with a minimum length of 1 octet.