One document matched: draft-ietf-dime-qos-attributes-07.xml
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type='text/xsl' href='./rfc2629.xslt' ?>
<?rfc toc="yes"?>
<?rfc symrefs="no"?>
<?rfc compact="no" ?>
<?rfc sortrefs="yes" ?>
<?rfc strict="yes" ?>
<?rfc linkmailto="yes" ?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
<!ENTITY RFC4005 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4005.xml'>
<!ENTITY I-D.ietf-dime-rfc3588bis PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-dime-rfc3588bis.xml'>
<!ENTITY I-D.ietf-dime-qos-parameters PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-dime-qos-parameters.xml'>
<!ENTITY I-D.ietf-dime-diameter-qos PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-dime-diameter-qos.xml'>
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="no" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="yes" ?>
<rfc ipr="full3978" category="std" docName="draft-ietf-dime-qos-attributes-07.txt">
<front>
<title abbrev="QoS Attributes for Diameter">Quality of Service Attributes for Diameter</title>
<author initials="J" surname="Korhonen" fullname="Jouni Korhonen">
<organization>TeliaSonera</organization>
<address>
<postal>
<street>Teollisuuskatu 13</street>
<city>Sonera</city>
<code>FIN-00051</code>
<country>Finland</country>
</postal>
<email>jouni.korhonen@teliasonera.com</email>
</address>
</author>
<author initials="H." surname="Tschofenig" fullname="Hannes Tschofenig">
<organization>Nokia Siemens Networks</organization>
<address>
<postal>
<street>Linnoitustie 6</street>
<city>Espoo</city>
<code>02600</code>
<country>Finland</country>
</postal>
<phone>+358 (50) 4871445</phone>
<email>Hannes.Tschofenig@gmx.net</email>
<uri>http://www.tschofenig.priv.at</uri>
</address>
</author>
<author initials="M." surname="Arumaithurai" fullname="Mayutan Arumaithurai">
<organization abbrev="University of Goettingen">University of Goettingen</organization>
<address>
<postal>
<street/>
<city> </city>
<region> </region>
<code> </code>
<country> </country>
</postal>
<email>mayutan.arumaithurai@gmail.com</email>
</address>
</author>
<author role="editor" initials="M." surname="Jones" fullname="Mark Jones">
<organization>Bridgewater Systems</organization>
<address>
<postal>
<street>303 Terry Fox Drive</street>
<city>Ottawa</city>
<region>Ontario</region>
<code>K2K 3J1</code>
<country>Canada</country>
</postal>
<email>mark.jones@bridgewatersystems.com</email>
</address>
</author>
<author initials="A" surname="Lior" fullname="Avi Lior">
<organization>Bridgewater Systems</organization>
<address>
<postal>
<street>303 Terry Fox Drive, Suite 500</street>
<city>Ottawa</city>
<region>Ontario</region>
<code/>
<country>Canada K2K 3J1</country>
</postal>
<phone>+1 613-591-6655</phone>
<email>avi@bridgewatersystems.com</email>
</address>
</author>
<date year="2008"/>
<area>Operations and Management</area>
<workgroup>Diameter Maintenance and Extensions (DIME)</workgroup>
<keyword>Internet-Draft</keyword>
<keyword>Diameter</keyword>
<keyword>QoS Attributes</keyword>
<abstract>
<t>This document extends the IPFilterRule AVP functionality of the Diameter Base protocol
and the functionality of the QoS-Filter-Rule AVP defined in RFC 4005. The ability to
convey Quality of Service information using the AVPs defined in this document is
available to existing and future Diameter applications where permitted by the command
ABNF.</t>
</abstract>
</front>
<!-- ====================================================================== -->
<middle>
<!-- ====================================================================== -->
<section anchor="introduction" title="Introduction">
<t>This document defines a number of Diameter Quality of Service (QoS) related AVPs that
can be used in existing and future Diameter applications where permitted by the command
ABNF. The Extended-QoS-Filter-Rule AVP thereby replaces the IPFilterRule, defined in
RFC 3588bis <xref target="I-D.ietf-dime-rfc3588bis"/>, and the QoS-Filter-Rule, defined
in RFC 4005 <xref target="RFC4005"/>. </t>
</section>
<!-- ====================================================================== -->
<section title="Terminology">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD
NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as
described in RFC 2119 <xref target="RFC2119"/>. </t>
</section>
<!-- ====================================================================== -->
<section anchor="qos-new-avps" title="Diameter QoS Defined AVPs">
<section title="QoS-Capability AVP" anchor="capability">
<t>The QoS-Capability AVP (AVP Code TBD) is of type Grouped and contains a list of
supported Quality of Service profile templates (and therefore the support of the
respective parameter AVPs).
</t>
<t>The QoS-Capability AVP may be used for a simple announcement of the QoS capabilities
and QoS profiles supported by a peer. It may also be used to negotiate a mutually
supported set of QoS capabilities and QoS profiles between two peers.</t>
<t>
<figure>
<artwork><![CDATA[
QoS-Capability ::= < AVP Header: XXX >
* [ QoS-Profile-Template ]
* [ Vendor-Specific-QoS-Profile-Template ]
* [ AVP ]
]]></artwork>
</figure>
</t>
</section>
<section title="QoS-Profile-Template AVP" anchor="qos-profile">
<t>The QoS-Profile-Template AVP (AVP Code TBD) is of type Unsigned32 and contains
a QoS profile template identifier. An initial QoS profile template is defined with
value of 0 and is described in <xref target="I-D.ietf-dime-qos-parameters"/>.
The registry for the QoS profile templates is created with the same document.
</t>
</section>
<section title="Vendor-Specific-QoS-Profile-Template AVP" anchor="vendor-qos-profile">
<t>The Vendor-Specific-QoS-Profile-Template AVP (AVP Code TBD) is of type Grouped and
defines a vendor-specific QoS profile template.</t>
<t>The Vendor-Id AVP contains a 32 bit IANA SMI Network Management Private Enterprise
Code and the QoS-Profile-Template AVP contains the template identifier assigned
by the vendor.</t>
<t>
<figure>
<artwork><![CDATA[
Vendor-Specific-QoS-Profile-Template ::= < AVP Header: XXX >
{ Vendor-Id }
{ QoS-Profile-Template }
* [ AVP ]
]]></artwork>
</figure>
</t>
</section>
<section title="QoS-Resources AVP">
<t> The QoS-Resources AVP (AVP Code TBD) is of type Grouped and includes a description of
the Quality of Service resources for policing traffic flows. </t>
<t>
<figure>
<artwork><![CDATA[
QoS-Resources ::= < AVP Header: XXX >
* [ Extended-QoS-Filter-Rule ]
* [ AVP ]
]]></artwork>
</figure>
</t>
</section>
<section title="Extended-QoS-Filter-Rule AVP">
<t>The Extended-QoS-Filter-Rule AVP (AVP Code TBD) is of type Grouped and defines
one or more traffic flows together with a set of QoS parameters that should be
applied to the flow(s) by the Resource Management Function. This AVP uses the
Classifier AVP (see <xref target="classifier"/>) to describe
traffic flows.
</t>
<t>
<figure>
<artwork><![CDATA[
Extended-QoS-Filter-Rule ::= < AVP Header: XXX >
{ QoS-Semantics }
[ QoS-Profile-Template ]
[ Vendor-Specific-QoS-Profile-Template ]
[ QoS-Parameters ]
[ QoS-Rule-Precedence ]
[ Classifier ]
* [ AVP ]
]]></artwork>
</figure>
</t>
<t>Either the QoS-Profile-Template or Vendor-Specific-QoS-Profile-Template AVP MUST
appear in the Extended-QoS-Filter-Rule AVP.</t>
</section>
<section title="QoS-Semantics">
<t>The QoS-Semantics AVP (AVP Code TBD) is of type Enumerated and provides the semantics
for the QoS-Profile-Template and QoS-Parameters AVPs in the Extended-QoS-Filter-Rule AVP. </t>
<t>This document defines the following values: <figure>
<artwork><![CDATA[
(0): QoS-Desired
(1): QoS-Available
(2): QoS-Reserved
(3): Minimum-QoS
(4): QoS-Authorized
]]></artwork>
</figure>
</t>
</section>
<section title="QoS-Parameters AVP">
<t> The QoS-Parameters AVP (AVP Code TBD) is of type OctetString and contains Quality of
Service parameters. These parameters are defined in a separate document, see <xref
target="I-D.ietf-dime-qos-parameters"/>. </t>
</section>
<section title="QoS-Rule-Precedence AVP">
<t> The QoS-Rule-Precedence AVP (AVP Code TBD) is of type Unsigned32 and specifies the
execution order of the rules expressed in the QoS-Resources AVP. Rules with equal
precedence MAY be executed in parallel if supported by the Resource Management Function.
If the QoS-Rule-Precedence AVP is absent from the Extended-QoS-Filter-Rule AVP, the rules
SHOULD be executed in the order in which they appear in the QoS-Resources AVP.
The lower the numerical value of QoS-Rule-Precedence AVP, the higher the rule precedence.
</t>
</section>
</section>
<section title="Semantics of QoS Parameters">
<t>The QoS parameters carried in the QoS-Resources AVP may appear in different messages.
The semantic of the QoS parameters depend on the information provided in the QoS-Semantics
AVP which currently defines 5 values, namely QoS-Desired (0), QoS-Available (1),
QoS-Reserved (2), Minimum-QoS (3), and QoS-Authorized (4). </t>
<t> The semantics of the different values are as follows: <figure>
<artwork><![CDATA[
Object Type Direction Semantic
---------------------------------------------------------------------
QoS-Desired C->S Please authorize the indicated QoS
QoS-Desired C<-S NA
QoS-Available C->S Admission Control at interface indicates
that this QoS is available. (note 1)
QoS-Available C<-S Indicated QoS is available. (note 2)
QoS-Reserved C->S Used for reporting during accounting.
QoS-Reserved C<-S NA
Minimum-QoS C->S Indicates that the client is not
interested in authorizing QoS that is
lower than Min. QoS.
Minimum-QoS C<-S The client must not provide QoS
guarantees lower than Min. QoS.
QoS-Authorized C->S NA
QoS-Authorized C<-S Indicated QoS authorized
Legend:
C: Diameter client
S: Diameter server
NA: Not applicable to this document;
no semantic defined in this specification
Notes:
(1) QoS-Available is only useful in relationship with QoS-Desired
(and optionally with Minimum-QoS).
(2) QoS-Available is only useful when the AAA server performs
admission control and knows about the resources in the network.
]]></artwork>
</figure>
</t>
</section>
<section anchor="classifier" title="Diameter Classifier AVPs">
<t>Classifiers are used in many applications to specify how to classify packets. For example
in a QoS application, if a packet matches a classifier then that packet will be treated in
accordance with a QoS specification associated with that classifier.
</t>
<t>The Classifiers are sent to on on-path element (e.g. a router) which uses the classifier to
match packets. <xref target="classifier-arch"/> shows a typical deployment.</t>
<figure anchor="classifier-arch" title="Example of a Classifier Architecture">
<artwork><![CDATA[
+-----------+
+-----------+|
+--------+ +-------------+ +------------+||
| | IN | | | |||
| +--------->| +------------->| |||
|Managed | | Classifying | | Unmanaged |||
|Terminal| OUT | Entity | | Terminal |||
| |<---------+ |<-------------+ ||+
| | | | | |+
+--------+ +-------------+ +------------+
^
| Classifiers
|
+------+-------+
| |
| AAA |
| |
+--------------+
]]></artwork>
</figure>
<t>The managed terminal, the terminal for which the classifiers are being specified is
located on the left of the Classifying Entity. The unmanaged terminal, the terminal that
receives packets from the Managed terminal or sends packets to the managed terminal is
located to the right side of the Classifying Entity.</t>
<t>The Classifying Entity is responsible for classifying packets that are incoming (IN)
from the Managed Terminal or packets outgoing (OUT) to the Managed Terminal.</t>
<t>A Classifier consists of a group of attributes that specify how to match a packet. Each
set of attributes expresses values about aspects of the packet - typically the packet header.
Different protocols therefore would use different attributes.</t>
<t>In general a Classifier consists of the following:</t>
<t>
<list style="hanging">
<t hangText="Identifier:"> <vspace blankLines="1"/>
The identifier uniquely identifies this classifier and may be used to reference the
classifier from another structure.
<vspace blankLines="1"/></t>
<t hangText="From:"><vspace blankLines="1"/>
Specifies the rule for matching the source part of the packet.
<vspace blankLines="1"/></t>
<t hangText="To:"><vspace blankLines="1"/>
Specifies the rule for matching the destination part of the packet.
<vspace blankLines="1"/></t>
<t hangText="Protocol:"><vspace blankLines="1"/>
Specifies the matching protocol of the packet.
<vspace blankLines="1"/></t>
<t hangText="Direction:"><vspace blankLines="1"/>
Specifies whether the classifier is to apply to packets flowing from the Managed
Terminal (IN) or to packets flowing to the Managed Terminal (OUT), or packets flowing in both direction.
<vspace blankLines="1"/></t>
<t hangText="Options:"><vspace blankLines="1"/>
Associated with each protocol or layer, or various values specific to the header of the protocol or layer.
Options allow matching on those values.
<vspace blankLines="1"/></t>
</list>
</t>
<t>Each protocol type will have a specific set of attributes that can be used to specify a classifier for that protocol. These attributes will be grouped under a grouped AVP called a Classifier AVP.</t>
<!-- ====================================================================== -->
<section title="Classifier AVP">
<t>The Classifier AVP (AVP Code TBD) is a grouped AVP that consists of a set of attributes
that specify how to match a packet.</t>
<t>
<figure>
<artwork><![CDATA[
Classifier ::= < AVP Header: XXX >
{ Classifier-ID }
{ Protocol }
{ Direction }
* [ From-Spec ]
* [ To-Spec ]
* [ Diffserv-Code-Point ]
[ Fragmentation-Flag ]
* [ IP-Option ]
* [ TCP-Option ]
[ TCP-Flags ]
* [ ICMP-Type ]
* [ ETH-Option ]
* [ AVP ]
]]></artwork>
</figure>
</t>
</section>
<!-- ====================================================================== -->
<section title="Classifier-ID AVP">
<t>The Classifier-ID AVP (AVP Code TBD) is of type OctetString and uniquely identifies
the classifier. Each application will define the uniqueness scope of this identifier,
e.g. unique per terminal or globally unique.
Exactly one Classifier-ID AVP MUST be contained within a Classifier AVP.</t>
</section>
<!-- ====================================================================== -->
<section title="Protocol AVP">
<t>The Protocol AVP (AVP Code TBD) is of type Enumerated and specifies the protocol
being matched. The attributes included in the Classifier AVP must be consistent with the
value of the Protocol AVP. Exactly one Protocol AVP MUST be contained within a
Classifier AVP. The values for this AVP are managed by IANA under the Protocol Numbers
registry <xref target="PROTOCOL"/>.</t>
</section>
<!-- ====================================================================== -->
<section title="Direction AVP">
<t>The Direction AVP (AVP Code TBD) is of type Enumerated that specifies in which
direction to apply the Classifier. The values of the enumeration are: "IN","OUT","BOTH".
In the "IN" and "BOTH" directions, the From-Spec refers to the address of the Managed
Terminal and the To-Spec refers to the unmanaged terminal. In the "OUT" direction, the
From-Spec refers to the Unmanaged Terminal whereas the To-Spec refers to the Managed
Terminal. </t>
<t>
<figure>
<artwork><![CDATA[
Value | Name and Semantic
------+--------------------------------------------------
0 | RESERVED
1 | IN - The classifier applies to flows from the
| Managed Terminal.
2 | OUT - The classifier applies to flows to the
| Managed Terminal.
3 | BOTH - The classifier applies to flows both to
| and from the Managed Terminal.
]]></artwork>
</figure>
</t>
</section>
<!-- ====================================================================== -->
<section title="From-Spec AVP">
<t>The From-Spec AVP (AVP Code TBD) is a grouped AVP that specifies the Source
Specification used to match the packet. Zero or more of these AVPs may appear in the
Classifier. If this AVP is absent from the Classifier then all packets are matched
regardless of the source address. If more than one instance of this AVP appears in the
Classifier then the source of the packet can match any From-Spec AVP. The contents of
this AVP are protocol specific.</t>
<t>If more than one instance of the IP address AVPs (IP-Address, IP-Address-Range,
IP-Address-Mask, Use-Assigned-Address) appear in the From-Spec AVP then the source
IP address of the packet must match one of the addresses represented by these AVPs.</t>
<t>If more that one instance of the layer 2 address AVPs (MAC-Address, MAC-Address-Mask,
EUI64-Address, EUI64-Address-Mask) appears in the From-Spec then the the source layer 2
address of the packet must match one of the addresses represented in these AVPs.</t>
<t>If more that one instance of the VLAN-ID AVP appears in the From-Spec then the
VLAN-ID of the packet must match one of the VLAN-IDs represented in these AVPs.</t>
<t>If more that one instance of the port AVPs (Port, Port-Range) appears in the
From-Spec AVP then the source port number must match one of the port numbers represented
in these AVPs.</t>
<t>If the IP address, MAC address and port AVPs appear in the same From-Spec AVP then
the source packet must match all the specifications, i.e. match the IP address AND
MAC address AND port number.</t>
<t>
<figure>
<artwork><![CDATA[
From-Spec ::= < AVP Header: XXX >
* [ IP-Address ]
* [ IP-Address-Range ]
* [ IP-Address-Mask ]
* [ MAC-Address ]
* [ MAC-Address-Mask]
* [ EUI64-Address ]
* [ EUI64-Address-Mask]
* [ VLAN-ID ]
* [ Port ]
* [ Port-Range ]
[ Negated ]
[ Use-Assigned-Address ]
* [ AVP ]
]]></artwork>
</figure>
</t>
</section>
<!-- ====================================================================== -->
<section title="To-Spec AVP">
<t>The To-Spec AVP (AVP Code TBD) is a grouped AVP that specifies the Destination
Specification used to match the packet. Zero or more of these AVPs may appear in the
Classifier. If this AVP is absent from the Classifier then all packets are matched
regardless of the destination address. If more than one instance of this AVP appears in the
Classifier then the destination of the packet can match any To-Spec AVP. The contents of
this AVP are protocol specific.</t>
<t>If more than one instance of the IP address AVPs (IP-Address, IP-Address-Range,
IP-Address-Mask, Use-Assigned-Address) appear in the To-Spec AVP then the destination
IP address of the packet must match one of the addresses represented by these AVPs.</t>
<t>If more that one instance of the layer 2 address AVPs (MAC-Address, MAC-Address-Mask,
EUI64-Address, EUI64-Address-Mask) appears in the To-Spec then the the destination layer 2
address of the packet must match one of the addresses represented in these AVPs.</t>
<t>If more that one instance of the VLAN-ID AVP appears in the From-Spec then the
VLAN-ID of the packet must match one of the VLAN-IDs represented in these AVPs.</t>
<t>If more that one instance of the port AVPs (Port, Port-Range) appears in the
To-Spec AVP then the destination port number must match one of the port numbers
represented in these AVPs.</t>
<t>If the IP address, MAC address and port AVPs appear in the same To-Spec AVP then
the destination packet must match all the specifications, i.e. match the IP address
AND MAC address AND port number.</t>
<t>
<figure>
<artwork><![CDATA[
To-Spec ::= < AVP Header: XXX >
* [ IP-Address ]
* [ IP-Address-Range ]
* [ IP-Address-Mask ]
* [ MAC-Address ]
* [ MAC-Address-Mask]
* [ EUI64-Address ]
* [ EUI64-Address-Mask]
* [ VLAN-ID ]
* [ Port ]
* [ Port-Range ]
[ Negated ]
[ Use-Assigned-Address ]
* [ AVP ]
]]></artwork>
</figure>
</t>
</section>
<!-- ====================================================================== -->
<section title="Source and Destination AVPs">
<t>For packet classification the contents of the From-Spec and To-Spec can contain the
following AVPs.</t>
<t>By combining several of these AVPs within a From-Spec or To-Spec AVP and using
more than one From-Spec or To-Spec AVP in the Classifier AVP, one can express many
different types of address pools.
</t>
<!-- ====================================================================== -->
<section title="Negated AVP">
<t>The Negated AVP (AVP Code TBD) of type Enumerated containing the values of True or
False. Exactly zero or one of these AVPs may appear in the From-Spec or To-Spec
AVP. When set to True the meaning of the match in the To-Spec and From-Spec are
negated, causing all other addresses to be matched instead.</t>
<t>When set to False, or when the AVP is not included in the From-Spec or
To-Spec AVP then the meaning of the match is not inverted, causing only the addresses
specified to be matched.</t>
<t>Note that the negation does not impact the port comparisons.</t>
<t>
<figure>
<artwork><![CDATA[
Value | Name
------+--------
0 | False
1 | True
]]></artwork>
</figure>
</t>
</section>
<!-- ====================================================================== -->
<section title="IP-Address AVP">
<t>The IP-Address AVP (AVP Code TBD) is of type Address and specifies a single
IP address (IPv4 or IPv6) address to match.</t>
</section>
<section title="IP-Address-Range AVP">
<t>The IP-Address-Range AVP (AVP Code TBD) is of type Grouped and specifies an
inclusive IP address range.</t>
<t>
<figure>
<artwork><![CDATA[
IP-Address-Range ::= < AVP Header: XXX >
[ IP-Address-Start ]
[ IP-Address-End ]
* [ AVP ]
]]></artwork>
</figure>
</t>
<t>If the IP-Address-Start AVP is not included then the address range starts from the
first valid IP address up to and including the specified IP-Address-End address.</t>
<t>If the IP-Address-End AVP is not included then the address range starts at the
address specified by the IP-Address-Start AVP and includes all the remaining valid IP
addresses.</t>
<t>For the IP-Address-Range AVP to be valid, the IP-Address-Start AVP MUST contain a
value that is less than that of the IP-Address-End AVP. </t>
</section>
<section title="IP-Address-Start AVP">
<t>The IP-Address-Start AVP (AVP Code TBD) is of type Address and specifies the
first IP address (IPv4 or IPv6) address of an IP address range.
</t>
</section>
<section title="IP-Address-End AVP">
<t>The IP-Address-End AVP (AVP Code TBD) is of type Address and specifies the
last IP address (IPv4 or IPv6) address of an address range.
</t>
</section>
<section title="IP-Address-Mask AVP">
<t>The IP-Address-Mask AVP (AVP Code TBD) is of type Grouped and specifies an IP
address range using a base IP address and the bit-width of the mask. For example, a
range expressed as 1.2.3.0/24 will match all IP addresses from 1.2.3.0 up to and
including 1.2.3.255. The bit-width MUST be valid for the type of IP address.</t>
<t>
<figure>
<artwork><![CDATA[
IP-Address-Mask ::= < AVP Header: XXX >
{ IP-Address }
{ IP-Bit-Mask-Width }
* [ AVP ]
]]></artwork>
</figure>
</t>
</section>
<section title="IP-Mask-Bit-Mask-Width AVP">
<t>The IP-Bit-Mask-Width AVP (AVP Code TBD) is of type OctetString. The value is a
single octet and specifies the width of an IP address bit-mask.</t>
</section>
<section title="MAC-Address AVP">
<t>The MAC-Address AVP (AVP Code TBD) is of type OctetString and specifies a single
layer 2 address in MAC-48 format. The value is a 6 octets encoding of the address as
it would appear in the frame header.</t>
</section>
<section title="MAC-Address-Mask AVP">
<t>The MAC-Address-Mask AVP (AVP Code TBD) is of type Grouped and
specifies a set of MAC addresses using a bit mask to indicate the
bits of the MAC addresses which must fit to the specified MAC
address attribute. For example, a MAC-Address-Mask with the
MAC-Address as 00-10-A4-23-00-00 and with a MAC-Address-Mask-Pattern
of FF-FF-FF-FF-00-00 will match all MAC addresses from
00-10-A4-23-00-00 up to and including 00-10-A4-23-FF-FF. </t>
<t>
<figure>
<artwork><![CDATA[MAC-Address-Mask ::= < AVP Header: XXX >
{ MAC-Address }
{ MAC-Address-Mask-Pattern }
* [ AVP ]]]></artwork>
</figure>
</t>
</section>
<section title="MAC-Address-Mask-Pattern AVP">
<t>The MAC-Address-Mask-Pattern AVP (AVP Code TBD) is of type
OctetString. The value is a 6 octets specifying the bit positions of
a MAC address, that are taken for matching.</t>
</section>
<section title="EUI64-Address AVP">
<t>The EUI64-Address AVP (AVP Code TBD) is of type OctetString and specifies a single
layer 2 address in EUI-64 format. The value is a 8 octets encoding of the address as
it would appear in the frame header.</t>
</section>
<section title="EUI64-Address-Mask AVP">
<t>The EUI64-Address-Mask AVP (AVP Code TBD) is of type Grouped and
specifies a set of EUI64 addresses using a bit mask to indicate the
bits of the EUI64 addresses which must fit to the specified EUI64
address attribute. For example, a EUI64-Address-Mask with the
EUI64-Address as 00-10-A4-FF-FE-23-00-00 and with a EUI64-Address-Mask-Pattern
of FF-FF-FF-FF-FF-FF-00-00 will match all EUI64 addresses from
00-10-A4-FF-FE-23-00-00 up to and including 00-10-A4-FF-FE-23-FF-FF. </t>
<t>
<figure>
<artwork><![CDATA[EUI64-Address-Mask ::= < AVP Header: XXX >
{ EUI64-Address }
{ EUI64-Address-Mask-Pattern }
* [ AVP ]]]></artwork>
</figure>
</t>
</section>
<section title="EUI64-Address-Mask-Pattern AVP">
<t>The EUI64-Address-Mask-Pattern AVP (AVP Code TBD) is of type
OctetString. The value is a 8 octets specifying the bit positions of
a EUI64 address, that are taken for matching.</t>
</section>
<section title="VLAN-ID AVP">
<t>VLAN-ID AVP (AVP Code TBD) is of type OctetString. The value is a
double octet encoded in Network Byte Order. The value of this field
specifies the matching value for the IEEE 802.1Q VLAN-ID bits. Only
the lower (i.e., rightmost) 12 bits of the specified 2 octet VLAN-ID
field are significant; the upper four bits shall be ignored for
comparison. If this field is omitted, then comparison of the IEEE
802.1Q VLAN-ID bits for this entry is irrelevant. If this parameter
is specified for an entry, then Ethernet packets without IEEE 802.1Q
encapsulation shall not match this entry.</t>
</section>
<section title="Port AVP">
<t>The Port AVP (AVP Code TBD) is of type Integer32 in the range of 0 to 65535 and
specifies the TCP or UDP port number to match.
</t>
</section>
<section title="Port-Range AVP">
<t>The Port-Range AVP (AVP Code TBD) is of type Grouped and specifies an inclusive range
of ports.</t>
<t>
<figure>
<artwork><![CDATA[
Port-Range ::= < AVP Header: XXX >
[ Port-Start ]
[ Port-End ]
* [ AVP ]
]]></artwork>
</figure>
</t>
<t>If the Port-Start AVP is omitted then port 0 is assumed. If the Port-End AVP is
omitted then port 65535 is assumed.</t>
</section>
<section title="Port-Start AVP">
<t>The Port-Start AVP (AVP Code TBD) is of type Integer32 and specifies the
first port number of an IP port range.
</t>
</section>
<section title="Port-End AVP">
<t>The Port-End AVP (AVP Code TBD) is of type Integer32 and specifies the
last port number of an IP port range.
</t>
</section>
<section title="Use-Assigned-Address AVP">
<t>In some scenarios, the AAA does not know the IP address assigned to the Managed
Terminal at the time that the Classifier is sent to the Classifying Entity.
The Use-Assigned-Address AVP (AVP Code TBD) is of type Enumerated containing the
values of True or False. When present and set to True, it represents the IP address
assigned to the Managed Terminal.</t>
<t>
<figure>
<artwork><![CDATA[
Value | Name
------+--------
0 | False
1 | True
]]></artwork>
</figure>
</t> </section>
</section>
<!-- ====================================================================== -->
<section title="Header Option AVPs">
<t>The Classifier AVP may contain one or more of the following AVPs to match on
the various possible IP, TCP or ICMP header options.</t>
<section title="Diffserv-Code-Point AVP">
<t>The Diffserv-Code-Point AVP (AVP Code TBD) is of type Enumerated and specifies the
Differentiated Services Field Codepoints to match in the IP header. The values
are managed by IANA under the Differentiated Services Field Codepoints registry
<xref target="DSCP"/>.</t>
</section>
<section title="Fragmentation-Flag AVP">
<t>The Fragmentation-Flag AVP (AVP Code TBD) is of type Enumerated and specifies the
packet fragmentation flags to match in the IP header.</t>
<t>
<figure>
<artwork><![CDATA[
Value | Name and Semantic
------+------------------------------------------------------------
0 | RESERVED
1 | Don't Fragment (DF)
2 | More Fragments (MF)
]]></artwork>
</figure>
</t>
</section>
<section title="IP-Option AVP">
<t>The IP-Option AVP (AVP Code TBD) is of type Grouped and specifies an IP header
option that must be matched.</t>
<t>
<figure>
<artwork><![CDATA[
IP-Option ::= < AVP Header: XXX >
{ IP-Option-Type }
* [ IP-Option-Value ]
[ Negated ]
* [ AVP ]
]]></artwork>
</figure>
</t>
<t>If one or more IP-Option-Value AVPs are present, one of the values MUST match
the value in the IP header option. If the IP-Option-Value AVP is absent, the
option type MUST be present in the IP header but the value is wild carded. </t>
<t>The Negated AVP is used in conjunction with the IP-Option-Value AVPs to specify
IP header options which do not match specific values. The Negated AVP is used
without the IP-Option-Value AVP to specify IP headers which do not contain the
option type.</t>
</section>
<section title="IP-Option-Type AVP">
<t>The IP-Option-Type AVP (AVP Code TBD) is of type Enumerated and the values
are managed by IANA under the IP Option Numbers registry <xref target="IPOPTIONS"/>.
</t>
</section>
<section title="IP-Option-Value AVP">
<t>The IP-Option-Value AVP (AVP Code TBD) is of type OctetString and contains the
option value that must be matched.</t>
</section>
<section title="TCP-Option AVP">
<t>The TCP-Option AVP (AVP Code TBD) is of type Grouped and specifies a TCP header
option that must be matched.</t>
<t>
<figure>
<artwork><![CDATA[
TCP-Option ::= < AVP Header: XXX >
{ TCP-Option-Type }
* [ TCP-Option-Value ]
[ Negated ]
* [ AVP ]
]]></artwork>
</figure>
</t>
<t>If one or more TCP-Option-Value AVPs are present, one of the values MUST match the
value in the TCP header option. If the TCP-Option-Value AVP is absent, the option type
MUST be present in the TCP header but the value is wild carded. </t>
<t>The Negated AVP is used in conjunction which the TCP-Option-Value AVPs to specify
TCP header options which do not match specific values. The Negated AVP is used
without the TCP-Option-Value AVP to specify TCP headers which do not contain the
option type.</t>
</section>
<section title="TCP-Option-Type AVP">
<t>The TCP-Option-Type AVP (AVP Code TBD) is of type Enumerated and the values are
managed by IANA under the TCP Option Numbers registry <xref target="TCPOPTIONS"/>.
</t>
</section>
<section title="TCP-Option-Value AVP">
<t>The TCP-Option-Value AVP (AVP Code TBD) is of type OctetString and contains the
option value that must be matched.</t>
</section>
<section title="TCP-Flags AVP">
<t>The TCP-Flags AVP (AVP Code TBD) is of type Grouped and specifies a set of TCP
control flags that must be matched.</t>
<t>
<figure>
<artwork><![CDATA[
TCP-Flags ::= < AVP Header: XXX >
1* { TCP-Flag-Type }
[ Negated ]
* [ AVP ]
]]></artwork>
</figure>
</t>
<t>If the Negated AVP is not present, the TCP-Flag-Type AVPs specifies which
flags MUST be set. If the Negated AVP is present, the TCP-Flag-Type AVPs
specifies which flags MUST be cleared. </t>
</section>
<section title="TCP-Flag-Type AVP">
<t>The TCP-Flag-Type AVP (AVP Code TBD) is of type Enumerated and specifies a
TCP control flag type that must be matched.</t>
<t>
<figure>
<artwork><![CDATA[
Value | Name and Semantic
------+------------------------------------------------------------
0 | RESERVED
1 | CWR - Congestion Window Reduced.
2 | ECE - ECN-Echo. TCP peer is ECN capable.
3 | URG - URGent pointer field is significant.
4 | ACK - ACKnowledgment field is significant.
5 | PSH - Push function.
6 | RST - Reset the connection.
7 | SYN - Synchronize sequence numbers.
8 | FIN - No more data from sender.
]]></artwork>
</figure>
</t>
</section>
<section title="ICMP-Type">
<t>The ICMP-Type AVP (AVP Code TBD) is of type Grouped and specifies a ICMP
message type that must be matched.</t>
<t>
<figure>
<artwork><![CDATA[
ICMP-Type ::= < AVP Header: XXX >
{ ICMP-Type-Number }
* [ ICMP-Code ]
[ Negated ]
* [ AVP ]
]]></artwork>
</figure>
</t>
<t>If the ICMP-Code AVP is present, the value MUST match that in the ICMP
header. If the ICMP-Code AVP is absent, the ICMP type MUST be present in the
ICMP header but the code is wild carded. </t>
<t>The Negated AVP is used in conjunction which the ICMP-Code AVPs to specify
ICMP codes which do not match specific values. The Negated AVP is used
without the ICMP-Code AVP to specify ICMP headers which do not contain the
ICMP type.
</t>
</section>
<section title="ICMP-Type-Number AVP">
<t>The ICMP-Type-Number AVP (AVP Code TBD) is of type Enumerated and the values are
managed by IANA under the ICMP Type Numbers registry <xref target="ICMPTYPE"/>.</t>
</section>
<section title="ICMP-Code AVP">
<t>The ICMP-Code AVP (AVP Code TBD) is of type Enumerated and the values are
managed by IANA under the ICMP Type Numbers registry <xref target="ICMPTYPE"/>.</t>
</section>
<section title="ETH-Option AVP">
<t>The ETH-Option AVP (AVP Code TBD) is of type Grouped and specifies
Ethernet specific classifiers.</t>
<t>
<figure>
<artwork><![CDATA[
ETH-Option ::= < AVP Header: XXX >
{ ETH-Proto-Type }
* [ ETH-VLAN-ID ]
* [ ETH-Priority-Range ]
* [ AVP ]
]]></artwork>
</figure>
</t>
</section>
<section title="ETH-Proto-Type AVP">
<t>The Eth-Proto-Type AVP (AVP Code TBD) is of type Grouped and specifies
the encapsulated protocol type. ETH-Ether-Type and ETH-SAP are
mutually exclusive.</t>
<t>
<figure>
<artwork><![CDATA[
ETH-Proto-Type ::= < AVP Header: XXX >
* [ ETH-Ether-Type ]
* [ ETH-SAP ]
* [ AVP ]
]]></artwork>
</figure>
</t>
</section>
<section title="ETH-Ether-Type AVP">
<t>The ETH-Ether-Type AVP (AVP Code TBD) is of type OctetString. The
value is a double octet the contains the value of the Ethertype that
the packet shall match in order to match the rule. It might be
present in case of DIX or if SNAP is present at 802.2 (SAP shall not
be present in this case).</t>
</section>
<section title="ETH-SAP AVP">
<t>The ETH-SAP AVP (AVP Code TBD) is of type OctetString. The value is a
double octet representing the 802.2 SAP as specified in "IEEE
Standards for Local Area Networks: Logical Link Control". The first
octet contains the DSAP and the second the SSAP.</t>
</section>
<section title="ETH-Priority-Range AVP">
<t>The ETH-Priority-Range AVP (AVP Code TBD) is of type Grouped and
specifies a valid priority range in between the Low-priority AVP to
the High-priority AVP specified. An Ethernet packet with IEEE 802.1D
user_priority value "priority" matches these parameters if priority
is greater than or equal to pri-low and priority is less than or
equal to pri-high. If this field is omitted, then comparison of the
IEEE 802.1D user_priority bits for this entry is irrelevant.</t>
<t>
<figure>
<artwork><![CDATA[
ETH-Priority-Range ::= < AVP Header: XXX >
* [ ETH-Low-Priority ]
* [ ETH-High-Priority ]
* [ AVP ]
]]></artwork>
</figure>
</t>
</section>
<section title="ETH-Low-Priority AVP">
<t>The ETH-Low-Priority AVP (AVP Code TBD) is of type OctetString. The
value is a single octet with a valid range from 0 to 7.</t>
</section>
<section title="ETH-High-Priority AVP">
<t>The ETH-High-Priority AVP (AVP Code TBD) is of type OctetString. The
value is a single octet with a valid range from 0 to 7.</t>
</section>
</section>
</section>
<!-- =================================================================================== -->
<section title="Examples">
<t>This section shows a number of signaling flows where QoS negotiation and authorization
is part of the conventional NASREQ, EAP or Credit Control applications message
exchanges. The signalling flows for the Diameter QoS Application are described in
<xref target="I-D.ietf-dime-diameter-qos"/>.</t>
<section title="Diameter EAP with QoS Information">
<t><xref target="diameter-eap-message-flow"/> shows a simple signaling flow where a NAS
(Diameter Client) announces its QoS awareness and capabilities included into the DER
message and as part of the access authentication procedure. Upon completion of the
EAP exchange, the Diameter Server provides a pre-provisioned QoS profile with the
QoS-Semantics in the Extended-QoS-Filter-Rule AVP set to "QoS-Authorized", to the
NAS in the final DEA message. <figure
title="Example of a Diameter EAP enhanced with QoS Information"
anchor="diameter-eap-message-flow">
<artwork><![CDATA[
End Diameter Diameter
Host Client Server
| | |
| (initiate EAP) | |
|<----------------------------->| |
| | Diameter-EAP-Request |
| | EAP-Payload(EAP Start) |
| | QoS-Capability |
| |------------------------------->|
| | |
| | Diameter-EAP-Answer |
| Result-Code=DIAMETER_MULTI_ROUND_AUTH |
| | EAP-Payload(EAP Request #1) |
| |<-------------------------------|
| EAP Request(Identity) | |
|<------------------------------| |
: : :
: <<<more message exchanges>>> :
: : :
| | |
| EAP Response #N | |
|------------------------------>| |
| | Diameter-EAP-Request |
| | EAP-Payload(EAP Response #N) |
| |------------------------------->|
| | |
| | Diameter-EAP-Answer |
| | Result-Code=DIAMETER_SUCCESS |
| | EAP-Payload(EAP Success) |
| | [EAP-Master-Session-Key] |
| | (authorization AVPs) |
| | QoS-Resources(QoS-Authorized) |
| |<-------------------------------|
| | |
| EAP Success | |
|<------------------------------| |
| | |
]]></artwork>
</figure>
</t>
</section>
<section title="Diameter NASREQ with QoS Information">
<t><xref target="diameter-nasreq-flow"/> shows a similar pre-provisioned QoS signaling
as in <xref target="diameter-eap-message-flow"/> but using the NASREQ application
instead of EAP application. </t>
<t>
<figure title="Example of a Diameter NASREQ enhanced with QoS Information"
anchor="diameter-nasreq-flow">
<artwork><![CDATA[
End Diameter
Host NAS Server
| | |
| Start Network | |
| Attachment | |
|<---------------->| |
| | |
| |AA-Request |
| |NASREQ-Payload |
| |QoS-Capability |
| +----------------------------->|
| | |
| | AA-Answer|
| Result-Code=DIAMETER_MULTI_ROUND_AUTH|
| NASREQ-Payload(NASREQ Request #1)|
| |<-----------------------------+
| | |
| Request | |
|<-----------------+ |
| | |
: : :
: <<<more message exchanges>>> :
: : :
| Response #N | |
+----------------->| |
| | |
| |AA-Request |
| |NASREQ-Payload ( Response #N )|
| +----------------------------->|
| | |
| | AA-Answer|
| | Result-Code=DIAMETER_SUCCESS|
| | (authorization AVPs)|
| |QoS-Resources(QoS-Authorized) |
| |<-----------------------------+
| | |
| Success | |
|<-----------------+ |
| | |
]]></artwork>
</figure>
</t>
</section>
<section title="QoS Authorization">
<t><xref target="diameter-authz-only-message-flow"/> shows an example of authorization
only QoS signaling as part of the NASREQ message exchange. The NAS provides the
Diameter server with the "QoS-Desired" QoS-Semantics AVP included in the
QoS-Resources AVP. The Diameter server then either authorizes the indicated QoS or
rejects the request and informs the NAS about the result. In this scenario the NAS
does not need to include the QoS-Capability AVP in the AAR message as the
QoS-Resources AVP implicitly does the same and also the NAS is authorizing a specific
QoS profile, not a pre-provisioned one. </t>
<t>
<figure title="Example of an Authorization-Only Message Flow"
anchor="diameter-authz-only-message-flow">
<artwork><![CDATA[
End Diameter
Host NAS Server
| | |
| | |
| QoS Request | |
+----------------->| |
| | |
| |AA-Request |
| |Auth-Request-Type=AUTHORIZE_ONLY
| |NASREQ-Payload |
| |QoS-Resources(QoS-Desired) |
| +----------------------------->|
| | |
| | AA-Answer|
| | NASREQ-Payload(Success)|
| | QoS-Resources(QoS-Authorized)|
| |<-----------------------------+
| Accept | |
|<-----------------+ |
| | |
| | |
| | |
]]></artwork>
</figure>
</t>
</section>
<section title="Diameter Server Initiated Re-authorization of QoS">
<t><xref target="diameter-re-auth-flow"/> shows a message exchange for a Diameter server
initiated QoS re-authorization procedure. The Diameter server sends the NAS a RAR
message requesting re-authorization for an existing session and the NAS acknowledges
it with a RAA message. The NAS is aware of its existing QoS profile and information
for the ongoing session that the Diameter server requested for re-authorization.
Thus, the NAS must initiate re-authorization of the existing QoS profile. The
re-authorization procedure is the same as in <xref
target="diameter-authz-only-message-flow"/>. </t>
<t>
<figure title="Example of a Server-initiated Re-Authorization Procedure"
anchor="diameter-re-auth-flow">
<artwork><![CDATA[
End Diameter
Host NAS Server
| | |
| | |
: : :
: <<<Initial Message Exchanges>>> :
: : :
| | |
| | RA-Request |
| |<-----------------------------+
| | |
| |RA-Answer |
| |Result-Code=DIAMETER_SUCCESS |
| +----------------------------->|
| | |
| | |
| |AA-Request |
| |NASREQ-Payload |
| |Auth-Request-Type=AUTHORIZE_ONLY
| |QoS-Resources(QoS-Desired) |
| +----------------------------->|
| | |
| | AA-Answer|
| | Result-Code=DIAMETER_SUCCESS|
| | (authorization AVPs)|
| | QoS-Resources(QoS-Authorized)|
| |<-----------------------------+
| | |
]]></artwork>
</figure>
</t>
</section>
<section title="Diameter Credit Control with QoS Information">
<t>In this case the User is charged as soon as the Service Element (CC client) receives
the service request. In this case the client uses the "QoS-Desired" QoS-Semantics
parameter in the QoS-Resources AVP that it sends to the Accounitng server. The server
responds with a "QoS-Available" QoS-Semantics parameter in the QoS-Resources AVP
<figure title="Example for a One-Time Diameter Credit Control Charging Event"
anchor="dcc-initial">
<artwork><![CDATA[
Service Element
End User (CC Client) B CC Server
| | | |
|(1) Service Request | | |
|-------------------->| | |
| |(2) CCR (event, DIRECT_DEBITING,|
| | QoS-Resources[QoS-desired]) |
| |-------------------------------->|
| |(3) CCA (Granted-Units, QoS- |
| | Resources[QoS-Authorized]) |
| |<--------------------------------|
|(4) Service Delivery | | |
|<--------------------| | |
|(5) Begin service | | |
|<------------------------------------>| |
| | | |
. . . .
. . . .
]]></artwork>
</figure>
</t>
</section>
<section title="Classifier Examples">
<t>Example: Classify all packets from hosts on subnet 12.34.56.00/24 to ports 80, 8090
or 443 on web servers 23.45.67.123, 23.45.68.124, 23.45.69.125.</t>
<t>
<figure>
<artwork><![CDATA[
Classifer = {
Classifier-Id = "web_svr_example";
Protocol = TCP;
Direction = OUT;
From-Spec = {
IP-Address-Mask = {
IP-Address = 12.34.56.00;
IP-Bit-Mask-Width = 24;
}
}
To-Spec = {
IP-Address = 23.45.67.123;
IP-Address = 23.45.68.124;
IP-Address = 23.45.69.125;
Port = 80;
Port = 8080;
Port = 443;
}
}
]]></artwork>
</figure>
</t>
<t>Example: Any SIP signalling traffic from a device with a MAC address of
01:23:45:67:89:ab to servers with IP addresses in the range 34.56.78.90 to
34.56.78.190.</t>
<t>
<figure>
<artwork><![CDATA[
Classifer = {
Classifier-Id = "web_svr_example";
Protocol = UDP;
Direction = OUT;
From-Spec = {
MAC-Address = 01:23:45:67:89:ab;
}
To-Spec = {
IP-Address-Range = {
IP-Address-Start = 34.56.78.90;
IP-Address-End = 34.56.78.190;
}
Port = 5060;
Port = 3478;
Port-Range = {
Port-Start = 16348;
Port-End = 32768;
}
}
}
]]></artwork>
</figure>
</t>
</section>
</section>
<!-- ====================================================================== -->
<section title="Acknowledgments">
<t>We would like to thank Victor Fajardo, Tseno Tsenov, Robert Hancock, Jukka Manner,
Cornelia Kappler, Xiaoming Fu, Frank Alfano,Tolga Asveren, Mike Montemurro,Glen Zorn,
Avri Doria, Dong Sun, Tina Tsou, Pete McCann, Georgios Karagiannis and Elwyn Davies
for their comments. </t>
</section>
<!-- ====================================================================== -->
<section title="IANA Considerations">
<t>IANA is requested to allocate AVP codes for the following AVPs that are defined in
this document.</t>
<t>
<figure>
<artwork><![CDATA[
+------------------------------------------------------------------+
| AVP Section |
| Attribute Name Code Defined Data Type |
+------------------------------------------------------------------+
|QoS-Capability TBD 3.1 Grouped |
|QoS-Profile-Template TBD 3.2 Unsigned32 |
|Vendor-Specific-QoS-Profile-Template TBD 3.3 Grouped |
|Extended-QoS-Filter-Rule TBD 3.5 Grouped |
|QoS-Semantics TBD 3.6 Enumerated |
|QoS-Parameters TBD 3.7 OctetString |
|QoS-Rule-Precedence TBD 3.8 Unsigned32 |
|Classifier TBD 5.1 Grouped |
|Classifier-ID TBD 5.2 OctetString |
|Protocol TBD 5.3 Enumerated |
|Direction TBD 5.4 Enumerated |
|From-Spec TBD 5.5 Grouped |
|To-Spec TBD 5.6 Grouped |
|Negated TBD 5.7.1 Enumerated |
|IP-Address TBD 5.7.2 Address |
|IP-Address-Range TBD 5.7.3 Grouped |
|IP-Address-Start TBD 5.7.4 Address |
|IP-Address-End TBD 5.7.5 Address |
|IP-Address-Mask TBD 5.7.6 Grouped |
|IP-Mask-Bit-Mask-Width TBD 5.7.7 OctetString |
|MAC-Address TBD 5.7.8 OctetString |
|MAC-Address-Mask TBD 5.7.9 Grouped |
|MAC-Address-Mask-Pattern TBD 5.7.10 OctetString |
|EUI64-Address TBD 5.7.11 OctetString |
|EUI64-Address-Mask TBD 5.7.12 Grouped |
|EUI64-Address-Mask-Pattern TBD 5.7.13 OctetString |
|VLAN-ID TBD 5.7.14 OctetString |
|Port TBD 5.7.15 Integer32 |
|Port-Range TBD 5.7.16 Grouped |
|Port-Start TBD 5.7.17 Integer32 |
|Port-End TBD 5.7.18 Integer32 |
|Use-Assigned-Address TBD 5.7.19 Enumerated |
|Diffserv-Code-Point TBD 5.8.1 Enumerated |
|Fragmentation-Flag TBD 5.8.2 Enumerated |
|IP-Option TBD 5.8.3 Grouped |
|IP-Option-Type TBD 5.8.4 Enumerated |
|IP-Option-Value TBD 5.8.5 OctetString |
|TCP-Option TBD 5.8.6 Grouped |
|TCP-Option-Type TBD 5.8.7 Enumerated |
|TCP-Option-Value TBD 5.8.8 OctetString |
|TCP-Flags TBD 5.8.9 Grouped |
|TCP-Flag-Type TBD 5.8.10 Enumerated |
|ICMP-Type TBD 5.8.11 Grouped |
|ICMP-Type-Number TBD 5.8.12 Enumerated |
|ICMP-Code TBD 5.8.13 Enumerated |
|ETH-Option TBD 5.8.14 Grouped |
|ETH-Proto-Type TBD 5.8.15 Grouped |
|ETH-Ether-Type TBD 5.8.16 OctetString |
|ETH-SAP TBD 5.8.17 OctetString |
|ETH-Priority-Range TBD 5.8.18 Grouped |
|ETH-Low-Priority TBD 5.8.19 OctetString |
|ETH-High-Priority TBD 5.8.20 OctetString |
+------------------------------------------------------------------+
]]></artwork>
</figure>
</t>
<t>IANA is also requested to allocate a registry for the QoS-Semantics. The following values
are allocated by this specification. <figure>
<artwork><![CDATA[
(0): QoS-Desired
(1): QoS-Available
(2): QoS-Reserved
(3): Minimum-QoS
(4): QoS-Authorized
]]></artwork>
</figure>
</t>
<t>A specification is required to add a new value to the registry. A standards track
document is required to depreciate, delete, or modify existing values. </t>
</section>
<!-- ====================================================================== -->
<section title="Security Considerations">
<t> This document describes the extension of Diameter for conveying Quality of Service
information. The security considerations of the Diameter protocol itself have been
discussed in RFC 3588bis <xref target="I-D.ietf-dime-rfc3588bis"/>. Use of the AVPs defined in this document
MUST take into consideration the security issues and requirements of the Diameter Base
protocol. </t>
</section>
<!-- ====================================================================== -->
</middle>
<back>
<references title="Normative References">
&RFC2119;
&RFC4005;
&I-D.ietf-dime-rfc3588bis;
&I-D.ietf-dime-qos-parameters;
<reference anchor="DSCP">
<front>
<title>Differentiated Services Field Codepoints</title>
<author>
<organization abbrev="IANA">IANA,</organization>
</author>
<date month="" year=""/>
</front>
<seriesInfo name="" value="http://www.iana.org/assignments/dscp-registry"/>
</reference>
<reference anchor="PROTOCOL">
<front>
<title>Protocol Types</title>
<author>
<organization abbrev="IANA">IANA,</organization>
</author>
<date month="" year=""/>
</front>
<seriesInfo name="" value="http://www.iana.org/assignments/protocol-numbers"/>
</reference>
<reference anchor="IPOPTIONS">
<front>
<title>IP Option Numbers</title>
<author>
<organization abbrev="IANA">IANA,</organization>
</author>
<date month="" year=""/>
</front>
<seriesInfo name="" value="http://www.iana.org/assignments/ip-parameters"/>
</reference>
<reference anchor="TCPOPTIONS">
<front>
<title>TCP Option Numbers</title>
<author>
<organization abbrev="IANA">IANA,</organization>
</author>
<date month="" year=""/>
</front>
<seriesInfo name="" value="http://www.iana.org/assignments/tcp-parameters"/>
</reference>
<reference anchor="ICMPTYPE">
<front>
<title>ICMP Type Numbers</title>
<author>
<organization abbrev="IANA">IANA,</organization>
</author>
<date month="" year=""/>
</front>
<seriesInfo name="" value="http://www.iana.org/assignments/icmp-parameters"/>
</reference>
</references>
<references title="Informative References">&I-D.ietf-dime-diameter-qos;</references>
</back>
<!-- ====================================================================== -->
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 01:21:49 |