5.2. Traffic Classification Sub-Data Item Type Values

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

Original RFC Text

5.2.  Traffic Classification Sub-Data Item Type Values

   IANA has created a new DLEP registry named "Traffic Classification
   Sub-Data Item Type Values".

   Table 2 shows the registration policies [RFC8126] for the registry:

                 +=============+=========================+
                 | Range       | Registration Procedures |
                 +=============+=========================+
                 | 1-65407     | Specification Required  |
                 +-------------+-------------------------+
                 | 65408-65534 | Private Use             |
                 +-------------+-------------------------+

                       Table 2: Registration Policies

   Table 3 shows the initial contents of the registry:

      +=============+=================================+=============+
      | Type Code   | Description                     | Reference   |
      +=============+=================================+=============+
      | 0           | Reserved                        | RFC 9892    |
      +-------------+---------------------------------+-------------+
      | 1           | Diffserv Traffic Classification | [RFC2474]   |
      +-------------+---------------------------------+-------------+
      | 2           | Ethernet Traffic Classification | [IEEE8021Q] |
      +-------------+---------------------------------+-------------+
      | 3-65407     | Unassigned                      |             |
      +-------------+---------------------------------+-------------+
      | 65408-65534 | Reserved for Private Use        | RFC 9892    |
      +-------------+---------------------------------+-------------+
      | 65535       | Reserved                        | RFC 9892    |
      +-------------+---------------------------------+-------------+

                     Table 3: Initial Registry Contents

   This registry encompasses packet traffic classification, where
   standard packet header identifiers in packets or data frames indicate
   Quality of Service (QoS) treatment.  It includes two specific entries
   for widely recognized identifiers used in QoS management for IP and
   Ethernet networks.  Reserved values are set aside for similar future
   identifiers that may emerge to denote QoS treatment.  However,
   requests for new entries are not expected to be frequent.

   Allocations within the registry are subject to the following
   requirements:

   1.  Documentation of the intended use of the requested value, in
       compliance with the "Specification Required" policy defined in
       [RFC8126].

   2.  Approval by the designated expert (DE) appointed by the IESG.
       The DE must do the following:

       *  Verify that the requested value is clearly documented and its
          purpose and usage are unambiguous.

       *  Ensure that the proposed value does not conflict with existing
          work or ongoing efforts within the IETF.

       *  Confirm that any specification requesting a code point has
          undergone review by the MANET Working Group (or a successor
          mailing list designated by the IESG).

       *  Validate that external specifications requesting code points
          are publicly available, are permanently archived, and do not
          conflict with active or published IETF work.

       *  Ensure that the review process is conducted in a timely
          manner, with any disputes resolved through consultation with
          the appropriate working groups.