Browse Prior Art Database

Textual Conventions for IPv6 Flow Label (RFC3595)

IP.com Disclosure Number: IPCOM000019350D
Original Publication Date: 2003-Sep-01
Included in the Prior Art Database: 2003-Sep-12
Document File: 7 page(s) / 12K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Wijnen: AUTHOR

Abstract

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.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 29% of the total text.

Network Working Group B. Wijnen

Request for Comments: 3595 Lucent Technologies

Category: Standards Track September 2003

Textual Conventions for IPv6 Flow Label

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2003). All Rights Reserved.

Abstract

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.

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2

2. The Internet-Standard Management Framework . . . . . . . . . . 2

3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 2

4. Security Considerations . . . . . . . . . . . . . . . . . . . 4

5. Intellectual Property Statement. . . . . . . . . . . . . . . . 4

6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4

6.1. Normative References . . . . . . . . . . . . . . . . . . 4

6.2. Informative References . . . . . . . . . . . . . . . . . 5

7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5

8. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 5

9. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 6

Wijnen Standards Track [Page 1]

RFC 3595 Textual Conventions for IPv6 Flow Label September 2003

1. Introduction

Several standards-track MIB modules have defined objects to represent

an IPv6 Flow Label (sometimes referred to as Flow ID) [RFC2460]

[FLOWLABEL] and IPv6 Flow Label filters. Unfortunately the result is

a set of different definitions for the same piece of management

information. This may lead to confusion and unnecessary complexity.

This document defines a set of textual conventions (TCs) that can and

should be (re-)used in MIB modules, so that they all represent an

IPv6 Flow Label in the same way. In fact, PIB modules can and should

also use these TCs when they need to represent an IPv6 Flow label.

2. The Internet-Standard Management Framework

For a detailed overview of the documents that describe the current

Internet-Standard Management Framework, please refer to section 7 of

RFC 3410 [RFC3410].

Managed objects are accessed via a virtual information store, termed

the Management Information Base or MIB. MIB objects are generally

accessed through the Simple Network Management Protocol (SNMP).

Objects in the MIB are defined using the mechanisms defined in the

Structure of Management Information (SMI). This memo specifies a MIB

module that is compliant to the SMIv2, which is described in STD 58,

RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580

[RF...