RFC 7083: Modification to Default Values of SOL_MAX_RT and INF_MAX_RT
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8415.
Current document in this lineage: RFC 9915 — Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
In plain English — editorial summary, not part of the RFC
This document updates RFC 3315 by redefining the default values for SOL_MAX_RT and INF_MAX_RT and defining options through which a DHCPv6 server can override the client's default value for SOL_MAX_RT and INF_MAX_RT with new values.
Document record
- Document ID
- RFC7083
- Published
- November 2013
- Authors
- R. Droms
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
Standards lineage
This document is one revision in a chain of 9 RFCs, each formally replacing the one before it.
- RFC 3315 (2003)
- RFC 3633 (2003)
- RFC 3736 (2004)
- RFC 4242 (2005)
- RFC 7083 (2013)
- RFC 7283 (2014)
- RFC 7550 (2015)
- RFC 8415 (2018)
- RFC 9915 (2026) ✓
Read the full history of Dynamic Host Configuration Protocol for IPv6 (DHCPv6) →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7086Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD)Current
January 2014
- RFC 7078Distributing Address Selection Policy Using DHCPv6Current
January 2014
- RFC 7077Update Notifications for Proxy Mobile IPv6Current
November 2013
- RFC 7098Using the IPv6 Flow Label for Load Balancing in Server FarmsCurrent
January 2014
- RFC 7112Implications of Oversized IPv6 Header ChainsCurrent
January 2014
- RFC 7048Neighbor Unreachability Detection Is Too ImpatientCurrent
January 2014
- RFC 7045Transmission and Processing of IPv6 Extension HeadersCurrent
December 2013
- RFC 7040Public IPv4-over-IPv6 Access NetworkCurrent
November 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?