RFC 3697: IPv6 Flow Label Specification
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6437.
Current version: RFC 6437 — IPv6 Flow Label Specification
In plain English — editorial summary, not part of the RFC
This document specifies the IPv6 Flow Label field and the minimum requirements for IPv6 source nodes labeling flows, IPv6 nodes forwarding labeled packets, and flow state establishment methods. Even when mentioned as examples of possible uses of the flow labeling, more detailed requirements for specific use cases are out of scope for this document. The usage of the Flow Label field enables efficient IPv6 flow classification based only on IPv6 main header fields in fixed positions. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3697
- Published
- March 2004
- Authors
- J. Rajahalme; A. Conta; B. Carpenter; S. Deering
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 9
- Also known as
- —
- Obsoleted by:
- RFC 6437
Topics
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 6275Mobility Support in IPv6Current
July 2011
- RFC 8200Internet Protocol, Version 6 (IPv6) SpecificationUpdated
July 2017
- RFC 3736Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6Obsoleted
April 2004
- RFC 3775Mobility Support in IPv6Obsoleted
June 2004
- RFC 3590Source Address Selection for the Multicast Listener Discovery (MLD) ProtocolCurrent
September 2003
- RFC 3879Deprecating Site Local AddressesCurrent
September 2004
- RFC 3484Default Address Selection for Internet Protocol version 6 (IPv6)Obsoleted
March 2003
- RFC 3336PPP Over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2)Current
December 2002
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?