Passa al contenuto principale

2.1.1. Traffic Classification Sub-Data Item

This page preserves the original RFC text for the section and adds navigation metadata for the documentation site.

Original RFC Text

2.1.1.  Traffic Classification Sub-Data Item

All Traffic Classification Sub-Data Items share a common format that
is patterned after the standard DLEP Data Item format. See
Section 11.3 of [RFC8175]. There is no requirement on, or meaning
to, Sub-Data Item ordering. Any errors or inconsistencies
encountered in parsing Sub-Data Items are handled in the same fashion
as any other Data Item parsing error encountered in DLEP. See
[RFC8175].

The format of the Traffic Classification Sub-Data Item is as follows:

0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Value... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Sub-Data Item Type:
A 16-bit unsigned integer that indicates the type and
corresponding format of the Sub-Data Item's Value field. Sub-Data
Item Types are scoped within the Data Item in which they are
carried, i.e., the Sub-Data Item Type field MUST be used together
with the Traffic Classification Data Item Type to identify the
format of the Sub-Data Item. Traffic Classification Sub-Data Item
Types are managed according to the IANA registry described in
Section 5.2.

Length:
Variable

Per Section 11.3 of [RFC8175], Length is a 16-bit unsigned integer
that is the number of octets in the Sub-Data Item, excluding the
Data Item Type and Length fields. Each Sub-Data Item has its own
Length field.

Value:
A field of <Length> octets that contains data specific to a
particular Data Item.