rfc-3898

Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)

V. Kalusivalingam
date2004-10 streamIETF areaint wgdhc statusPROPOSED STANDARD pages7 canonicalhttps://www.rfc-editor.org/rfc/rfc3898 doi10.17487/RFC3898
This document describes four options for Network Information Service (NIS) related configuration information in Dynamic Host Configuration Protocol for IPv6 (DHCPv6): NIS Servers, NIS+ Servers, NIS Client Domain Name, NIS+ Client Domain name. [STANDARDS-TRACK]

Extracted elements (15)

interoperability-note §1

The options defined in RFC 3898 can only configure NIS servers reachable via IPv6. IPv4 NIS server configuration is handled by RFC 2132 DHCP options. Mechanisms for configuring IPv4/IPv6 dual-stack applications were not specified in this document.

dns, v6ops

normative-requirement §4 MUST

Clients MUST treat the list of NIS+ servers provided in OPTION_NISP_SERVERS as an ordered list. The server MAY list the NIS+ servers in order of preference.

dns

normative-requirement §5 MUST

The 'nis-domain-name' field MUST be encoded as specified in the section 'Representation and Use of domain names' of the DHCPv6 specification (RFC 3315).

dns

normative-requirement §7 MUST NOT

The NIS servers, NIS+ servers, NIS domain name, and NIS+ domain name options MUST NOT appear in messages other than: Solicit, Advertise, Request, Renew, Rebind, Information-Request, and Reply.

dns

normative-requirement §6 MUST

The 'nisp-domain-name' field MUST be encoded as specified in the section 'Representation and Use of domain names' of the DHCPv6 specification (RFC 3315).

dns

normative-requirement §7 MAY

The option numbers for OPTION_NIS_SERVERS, OPTION_NISP_SERVERS, OPTION_NIS_DOMAIN_NAME, and OPTION_NISP_DOMAIN_NAME MAY appear in the Option Request Option in Solicit, Request, Renew, Rebind, Information-Request, and Reconfigure messages.

dns

normative-requirement §8 SHOULD

To avoid attacks through these options, the DHCPv6 client SHOULD use authenticated DHCP as specified in the 'Authentication of DHCP messages' section of RFC 3315.

security, dns

protocol-element §5

OPTION_NIS_DOMAIN_NAME (option code 29) is used by the DHCPv6 server to convey the client's NIS domain name. The nis-domain-name field is variable length and encoded per DHCPv6 domain name representation rules.

dns, registry

protocol-element §3

OPTION_NIS_SERVERS (option code 27) provides a list of one or more IPv6 addresses of NIS servers available to the client. The option-len field must be a multiple of 16 octets, with each NIS server address encoded as a 128-bit IPv6 address.

dns, registry

protocol-element §6

OPTION_NISP_DOMAIN_NAME (option code 30) is used by the DHCPv6 server to convey the client's NIS+ domain name. The nisp-domain-name field is variable length and encoded per DHCPv6 domain name representation rules.

dns, registry

protocol-element §4

OPTION_NISP_SERVERS (option code 28) provides a list of one or more IPv6 addresses of NIS+ servers available to the client. The option-len field must be a multiple of 16 octets.

dns, registry

registry §9

IANA assigned four option codes from the DHCPv6 option-code space: OPTION_NIS_SERVERS (27), OPTION_NISP_SERVERS (28), OPTION_NIS_DOMAIN_NAME (29), and OPTION_NISP_DOMAIN_NAME (30).

registry, dns

security-consideration §8

A rogue DHCPv6 server may assign invalid NIS parameters via these options, causing clients to be unable to use NIS service or to send queries to an attacker-controlled NIS/NIS+ server, enabling spoofing of NIS/NIS+ names. Invalid domain name options can also redirect searches through attacker-controlled domains.

security, dns

wire-format §6

The NIS+ Domain Name option wire format encodes a 2-octet option-code (OPTION_NISP_DOMAIN_NAME=30), a 2-octet option-len, followed by the nisp-domain-name field encoded per DHCPv6 domain name representation.

dns

wire-format §4

The NIS+ Servers option wire format encodes a 2-octet option-code (OPTION_NISP_SERVERS=28), a 2-octet option-len (multiple of 16), followed by one or more 16-octet IPv6 addresses of NIS+ servers.

dns