RFC 3595: Textual Conventions for IPv6 Flow Label

In plain English — editorial summary, not part of the RFC

This MIB module defines textual conventions to represent the commonly used IPv6 Flow Label. The intent is that these textual conventions (TCs) will be imported and used in MIB modules that would otherwise define their own representations. [STANDARDS-TRACK]

Document record

Document ID

RFC3595

Published

September 2003

Authors

B. Wijnen

Status

PROPOSED STANDARD

Stream

IETF

Area

ops

Pages

6

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC3595

Topics

• mib
• management information base

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 3593Textual Conventions for MIB Modules Using Performance History Based on 15 Minute IntervalsCurrent

  September 2003

• RFC 3592Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface TypeCurrent

  September 2003

• RFC 3591Definitions of Managed Objects for the Optical Interface TypeCurrent

  September 2003

• RFC 3606Definitions of Supplemental Managed Objects for ATM InterfaceCurrent

  November 2003

• RFC 3621Power Ethernet MIBCurrent

  December 2003

• RFC 3635Definitions of Managed Objects for the Ethernet-like Interface TypesCurrent

  October 2003

• RFC 3637Definitions of Managed Objects for the Ethernet WAN Interface SublayerCurrent

  October 2003

• RFC 3498Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) ArchitecturesCurrent

  March 2003

Also filed under

• PROPOSED STANDARD
• 2003
• IETF stream
• ops area