draft-ietf-dime-qos-attributes-13.txt   draft-ietf-dime-qos-attributes-14.txt 
Diameter Maintenance and J. Korhonen Diameter Maintenance and J. Korhonen
Extensions (DIME) H. Tschofenig Extensions (DIME) H. Tschofenig
Internet-Draft Nokia Siemens Networks Internet-Draft Nokia Siemens Networks
Intended status: Standards Track M. Arumaithurai Intended status: Standards Track M. Arumaithurai
Expires: January 14, 2010 University of Goettingen Expires: April 26, 2010 University of Goettingen
M. Jones, Ed. M. Jones, Ed.
A. Lior A. Lior
Bridgewater Systems Bridgewater Systems
July 13, 2009 October 23, 2009
Quality of Service Attributes for Diameter Quality of Service Attributes for Diameter
draft-ietf-dime-qos-attributes-13.txt draft-ietf-dime-qos-attributes-14.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from IETF Standards Process. Without obtaining an adequate license from
skipping to change at page 1, line 47 skipping to change at page 1, line 47
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 14, 2010. This Internet-Draft will expire on April 26, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. and restrictions with respect to this document.
Abstract Abstract
This document extends the IPFilterRule AVP functionality of the This document defines a number of Diameter Quality of Service (QoS)
Diameter Base protocol and the functionality of the QoS-Filter-Rule related attribute-value pairs (AVP) that can be used in existing and
AVP defined in RFC 4005. The ability to convey Quality of Service future Diameter applications where permitted by the Augmented Backus-
information using the AVPs defined in this document is available to Naur Form (ABNF) specification of the command.
existing and future Diameter applications where permitted by the
command ABNF.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Rule Sets and Rules . . . . . . . . . . . . . . . . . . . . . 5 3. Rule Sets and Rules . . . . . . . . . . . . . . . . . . . . . 5
3.1. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 5 3.1. QoS-Resources AVP . . . . . . . . . . . . . . . . . . . . 5
3.2. QoS-Rule AVP . . . . . . . . . . . . . . . . . . . . . . . 6 3.2. QoS-Rule AVP . . . . . . . . . . . . . . . . . . . . . . . 5
3.3. QoS-Rule-Precedence AVP . . . . . . . . . . . . . . . . . 7 3.3. QoS-Rule-Precedence AVP . . . . . . . . . . . . . . . . . 6
4. Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4. Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Traffic Classifiers . . . . . . . . . . . . . . . . . . . 7 4.1. Traffic Classifiers . . . . . . . . . . . . . . . . . . . 6
4.1.1. Classifier AVP . . . . . . . . . . . . . . . . . . . . 9 4.1.1. Classifier AVP . . . . . . . . . . . . . . . . . . . . 8
4.1.2. Classifier-ID AVP . . . . . . . . . . . . . . . . . . 10 4.1.2. Classifier-ID AVP . . . . . . . . . . . . . . . . . . 9
4.1.3. Protocol AVP . . . . . . . . . . . . . . . . . . . . . 10 4.1.3. Protocol AVP . . . . . . . . . . . . . . . . . . . . . 9
4.1.4. Direction AVP . . . . . . . . . . . . . . . . . . . . 10 4.1.4. Direction AVP . . . . . . . . . . . . . . . . . . . . 9
4.1.5. From-Spec AVP . . . . . . . . . . . . . . . . . . . . 10 4.1.5. From-Spec AVP . . . . . . . . . . . . . . . . . . . . 9
4.1.6. To-Spec AVP . . . . . . . . . . . . . . . . . . . . . 11 4.1.6. To-Spec AVP . . . . . . . . . . . . . . . . . . . . . 10
4.1.7. Source and Destination AVPs . . . . . . . . . . . . . 12 4.1.7. Source and Destination AVPs . . . . . . . . . . . . . 11
4.1.8. Header Option AVPs . . . . . . . . . . . . . . . . . . 16 4.1.8. Header Option AVPs . . . . . . . . . . . . . . . . . . 15
4.2. Time Of Day AVPs . . . . . . . . . . . . . . . . . . . . . 23 4.2. Time Of Day AVPs . . . . . . . . . . . . . . . . . . . . . 22
4.2.1. Time-Of-Day-Condition AVP . . . . . . . . . . . . . . 23 4.2.1. Time-Of-Day-Condition AVP . . . . . . . . . . . . . . 22
4.2.2. Time-Of-Day-Start AVP . . . . . . . . . . . . . . . . 23 4.2.2. Time-Of-Day-Start AVP . . . . . . . . . . . . . . . . 23
4.2.3. Time-Of-Day-End AVP . . . . . . . . . . . . . . . . . 24 4.2.3. Time-Of-Day-End AVP . . . . . . . . . . . . . . . . . 23
4.2.4. Day-Of-Week-Mask AVP . . . . . . . . . . . . . . . . . 24 4.2.4. Day-Of-Week-Mask AVP . . . . . . . . . . . . . . . . . 23
4.2.5. Day-Of-Month-Mask AVP . . . . . . . . . . . . . . . . 24 4.2.5. Day-Of-Month-Mask AVP . . . . . . . . . . . . . . . . 23
4.2.6. Month-Of-Year-Mask AVP . . . . . . . . . . . . . . . . 24 4.2.6. Month-Of-Year-Mask AVP . . . . . . . . . . . . . . . . 24
4.2.7. Absolute-Start-Time AVP . . . . . . . . . . . . . . . 25 4.2.7. Absolute-Start-Time AVP . . . . . . . . . . . . . . . 24
4.2.8. Absolute-Start-Fractional-Seconds AVP . . . . . . . . 25 4.2.8. Absolute-Start-Fractional-Seconds AVP . . . . . . . . 24
4.2.9. Absolute-End-Time AVP . . . . . . . . . . . . . . . . 25 4.2.9. Absolute-End-Time AVP . . . . . . . . . . . . . . . . 24
4.2.10. Absolute-End-Fractional-Seconds AVP . . . . . . . . . 25 4.2.10. Absolute-End-Fractional-Seconds AVP . . . . . . . . . 25
4.2.11. Timezone-Flag AVP . . . . . . . . . . . . . . . . . . 26 4.2.11. Timezone-Flag AVP . . . . . . . . . . . . . . . . . . 25
4.2.12. Timezone-Offset AVP . . . . . . . . . . . . . . . . . 26 4.2.12. Timezone-Offset AVP . . . . . . . . . . . . . . . . . 25
5. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.1. QoS-Action AVP . . . . . . . . . . . . . . . . . . . . . . 26 5. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.2. QoS-Profile-Id AVP . . . . . . . . . . . . . . . . . . . . 27 5.1. QoS-Action AVP . . . . . . . . . . . . . . . . . . . . . . 25
5.2. QoS-Profile-Id AVP . . . . . . . . . . . . . . . . . . . . 26
5.3. QoS-Profile-Template AVP . . . . . . . . . . . . . . . . . 27 5.3. QoS-Profile-Template AVP . . . . . . . . . . . . . . . . . 27
5.4. QoS-Semantics . . . . . . . . . . . . . . . . . . . . . . 28 5.4. QoS-Semantics . . . . . . . . . . . . . . . . . . . . . . 27
5.5. QoS-Parameters AVP . . . . . . . . . . . . . . . . . . . . 29 5.5. QoS-Parameters AVP . . . . . . . . . . . . . . . . . . . . 28
5.6. Excess-Treatment AVP . . . . . . . . . . . . . . . . . . . 29 5.6. Excess-Treatment AVP . . . . . . . . . . . . . . . . . . . 29
6. QoS Capability Indication . . . . . . . . . . . . . . . . . . 30 6. QoS Capability Indication . . . . . . . . . . . . . . . . . . 29
7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.1. Diameter EAP with QoS Information . . . . . . . . . . . . 30 7.1. Diameter EAP with QoS Information . . . . . . . . . . . . 30
7.2. Diameter NASREQ with QoS Information . . . . . . . . . . . 31 7.2. Diameter NASREQ with QoS Information . . . . . . . . . . . 31
7.3. QoS Authorization . . . . . . . . . . . . . . . . . . . . 32 7.3. QoS Authorization . . . . . . . . . . . . . . . . . . . . 32
7.4. Diameter Server Initiated Re-authorization of QoS . . . . 33 7.4. Diameter Server Initiated Re-authorization of QoS . . . . 32
7.5. Diameter Credit Control with QoS Information . . . . . . . 34 7.5. Diameter Credit Control with QoS Information . . . . . . . 33
7.6. Classifier Examples . . . . . . . . . . . . . . . . . . . 35 7.6. Classifier Examples . . . . . . . . . . . . . . . . . . . 34
7.7. QoS Examples . . . . . . . . . . . . . . . . . . . . . . . 36 7.7. QoS Examples . . . . . . . . . . . . . . . . . . . . . . . 36
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 37 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 36
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 37 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 36
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
11. Security Considerations . . . . . . . . . . . . . . . . . . . 39 11. Security Considerations . . . . . . . . . . . . . . . . . . . 39
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 40 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39
12.1. Normative References . . . . . . . . . . . . . . . . . . . 40 12.1. Normative References . . . . . . . . . . . . . . . . . . . 39
12.2. Informative References . . . . . . . . . . . . . . . . . . 41 12.2. Informative References . . . . . . . . . . . . . . . . . . 40
Appendix A. MAC and EUI64 Address Mask Usage Considerations . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 41 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 41
1. Introduction 1. Introduction
This document defines a number of Diameter Quality of Service (QoS) This document defines a number of Diameter Quality of Service (QoS)
related AVPs that can be used in existing and future Diameter related AVPs that can be used in existing and future Diameter
applications where permitted by the ABNF of a command. The applications where permitted by the ABNF of a command. The
IPFilterRule AVP, defined in RFC 3588 [RFC3588], and the QoS-Filter- IPFilterRule AVP, defined in RFC 3588 [RFC3588], and the QoS-Filter-
Rule AVP, defined in RFC 4005 [RFC4005], provide basic support for Rule AVP, defined in RFC 4005 [RFC4005], provide basic support for
classification and QoS already. The classification rule syntax is a classification and QoS already. The classification rule syntax is a
modified subset of FreeBSD ipfw packet filter implementation. The modified subset of FreeBSD ipfw packet filter implementation. The
QoS functionality provided by the IPFilterRule AVP was updated by the QoS functionality provided by the IPFilterRule AVP was updated by the
QoS-Filter-Rule AVP. The QoS-Rule AVP offers an extended way of QoS-Filter-Rule AVP. The QoS-Rule AVP offers an extended way of
expressing classification and QoS capabilities. expressing classification and QoS capabilities.
The QoS-Resources AVP represents a complete rule set with each rule The QoS-Resources AVP represents a complete rule set with each rule
represented by a QoS-Rule AVP. Each rule consists of a conditions represented by a QoS-Rule AVP. Each rule consists of a conditions
part and the corresponding actions to be performed if the conditions part and the corresponding actions to be performed if the conditions
are satisfied. The AVPs responsible for expressing a condition are are satisfied. The AVPs responsible for expressing a condition are
defined in Section 4. The capability to match all or a subset of the defined in Section 4. The capability to match all or a subset of the
data traffic is provided and this includes the ability to match on data traffic is provided. This includes the ability to match on
Ethernet specific attributes which was not possible with the QoS- Ethernet specific attributes which was not possible with the QoS-
Filter-Rule AVP. Additionally, time-based conditions can be Filter-Rule AVP. Service differentiation may be based on Ethernet
expressed based on the functionality offered in Section 4.2. The priority bits, a single layer of VLAN-IDs or stacked VLAN-IDs, LLC
action part of a rule contains information for handling conflict attributes, MAC addresses or any combination thereof. The header
fields used for Ethernet classification are defined in the IEEE802
series of specifications: [IEEE802.2], [IEEE802.1ad], [IEEE802.1Q]
and [IEEE802.1D]. Additionally, time-based conditions can be
expressed based on the functionality offered by the attributes in
Section 4.2.
The action part of a rule contains information for handling conflict
resolution, such as a priority value for each individual rule within resolution, such as a priority value for each individual rule within
a rule set, and further description regarding QoS related actions. a rule set, and further description regarding QoS related actions.
The QoS policy rules are defined as Diameter encoded Attribute Value The QoS policy rules are defined as Diameter encoded Attribute Value
Pairs (AVPs) described using a modified version of the Augmented Pairs (AVPs) described using a modified version of the Augmented
Backus-Naur Form (ABNF), see [RFC3588]. The AVP datatypes are also Backus-Naur Form (ABNF), see [RFC3588]. The AVP datatypes are also
taken from [RFC3588]. taken from [RFC3588].
2. Terminology 2. Terminology
skipping to change at page 14, line 40 skipping to change at page 13, line 40
4.1.7.9. MAC-Address-Mask AVP 4.1.7.9. MAC-Address-Mask AVP
The MAC-Address-Mask AVP (AVP Code TBD) is of type Grouped and 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 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 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 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-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 00-00 will match all MAC addresses from 00-10-A4-23-00-00 up to and
including 00-10-A4-23-FF-FF. including 00-10-A4-23-FF-FF.
Appendix A describes the considerations that should be given to the
use of MAC address masks in constructing Classifiers.
MAC-Address-Mask ::= < AVP Header: XXX > MAC-Address-Mask ::= < AVP Header: XXX >
{ MAC-Address } { MAC-Address }
{ MAC-Address-Mask-Pattern } { MAC-Address-Mask-Pattern }
* [ AVP ] * [ AVP ]
4.1.7.10. MAC-Address-Mask-Pattern AVP 4.1.7.10. MAC-Address-Mask-Pattern AVP
The MAC-Address-Mask-Pattern AVP (AVP Code TBD) is of type The MAC-Address-Mask-Pattern AVP (AVP Code TBD) is of type
OctetString. The value is a 6 octets specifying the bit positions of OctetString. The value is a 6 octets specifying the bit positions of
a MAC address, that are taken for matching. a MAC address, that are taken for matching.
skipping to change at page 15, line 23 skipping to change at page 14, line 24
The EUI64-Address-Mask AVP (AVP Code TBD) is of type Grouped and 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 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 bits of the EUI64 addresses which must fit to the specified EUI64
address attribute. For example, a EUI64-Address-Mask with the 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- 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 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- from 00-10-A4-FF-FE-23-00-00 up to and including 00-10-A4-FF-FE-23-
FF-FF. FF-FF.
Appendix A describes the considerations that should be given to the
use of EUI64 address masks in constructing Classifiers.
EUI64-Address-Mask ::= < AVP Header: XXX > EUI64-Address-Mask ::= < AVP Header: XXX >
{ EUI64-Address } { EUI64-Address }
{ EUI64-Address-Mask-Pattern } { EUI64-Address-Mask-Pattern }
* [ AVP ] * [ AVP ]
4.1.7.13. EUI64-Address-Mask-Pattern AVP 4.1.7.13. EUI64-Address-Mask-Pattern AVP
The EUI64-Address-Mask-Pattern AVP (AVP Code TBD) is of type The EUI64-Address-Mask-Pattern AVP (AVP Code TBD) is of type
OctetString. The value is a 8 octets specifying the bit positions of OctetString. The value is a 8 octets specifying the bit positions of
a EUI64 address, that are taken for matching. a EUI64 address, that are taken for matching.
skipping to change at page 24, line 30 skipping to change at page 23, line 38
------+------------ ------+------------
0 | SUNDAY 0 | SUNDAY
1 | MONDAY 1 | MONDAY
2 | TUESDAY 2 | TUESDAY
3 | WEDNESDAY 3 | WEDNESDAY
4 | THURSDAY 4 | THURSDAY
5 | FRIDAY 5 | FRIDAY
6 | SATURDAY 6 | SATURDAY
The bit MUST be set for the time window to match on the corresponding The bit MUST be set for the time window to match on the corresponding
day of the week. Bit 0 is the most significant bit and unused bits day of the week. Bit 0 is the least significant bit and unused bits
MUST be cleared. If this AVP is absent from the Time-Of-Day- MUST be cleared. If this AVP is absent from the Time-Of-Day-
Condition AVP, the time windows match on all days of the week. Condition AVP, the time windows match on all days of the week.
4.2.5. Day-Of-Month-Mask AVP 4.2.5. Day-Of-Month-Mask AVP
The Day-Of-Month AVP (AVP Code TBD) is of type Unsigned32. The value The Day-Of-Month AVP (AVP Code TBD) is of type Unsigned32. The value
MUST be in the range from 0 to 2147483647. The value is a bitmask MUST be in the range from 0 to 2147483647. The value is a bitmask
which specifies the days of the month where bit 0 represents the which specifies the days of the month where bit 0 represents the
first day of the month through to bit 30 which represents the last first day of the month through to bit 30 which represents the last
day of the month. The bit MUST be set for the time window to match day of the month. The bit MUST be set for the time window to match
on the corresponding day of the month. Bit 0 is the most significant on the corresponding day of the month. Bit 0 is the least
bit and unused bits MUST be cleared. If this AVP is absent from the significant bit and unused bits MUST be cleared. If this AVP is
Time-Of-Day-Condition AVP, the time windows match on all days of the absent from the Time-Of-Day-Condition AVP, the time windows match on
month. all days of the month.
4.2.6. Month-Of-Year-Mask AVP 4.2.6. Month-Of-Year-Mask AVP
The Month-Of-Year-Mask AVP (AVP Code TBD) is of type Unsigned32. The The Month-Of-Year-Mask AVP (AVP Code TBD) is of type Unsigned32. The
value is a bitmask which specifies the months of the year for the value is a bitmask which specifies the months of the year for the
time window to match. This document specifies the following bits: time window to match. This document specifies the following bits:
Bit | Name Bit | Name
------+----------- ------+-----------
0 | JANUARY 0 | JANUARY
skipping to change at page 25, line 21 skipping to change at page 24, line 27
4 | MAY 4 | MAY
5 | JUNE 5 | JUNE
6 | JULY 6 | JULY
7 | AUGUST 7 | AUGUST
8 | SEPTEMBER 8 | SEPTEMBER
9 | OCTOBER 9 | OCTOBER
10 | NOVEMBER 10 | NOVEMBER
11 | DECEMBER 11 | DECEMBER
The bit MUST be set for the time window to match on the corresponding The bit MUST be set for the time window to match on the corresponding
month of the year. Bit 0 is the most significant bit and unused bits month of the year. Bit 0 is the least significant bit and unused
MUST be cleared. If this AVP is absent from the Time-Of-Day- bits MUST be cleared. If this AVP is absent from the Time-Of-Day-
Condition AVP, the time windows match during all months of the year. Condition AVP, the time windows match during all months of the year.
4.2.7. Absolute-Start-Time AVP 4.2.7. Absolute-Start-Time AVP
The Absolute-Start-Time AVP (AVP Code TBD) is of type Time. The The Absolute-Start-Time AVP (AVP Code TBD) is of type Time. The
value of this AVP specifies the time in seconds since January 1, value of this AVP specifies the time in seconds since January 1,
1900, 00:00 UTC when the time window starts. If this AVP is absent 1900, 00:00 UTC when the time window starts. If this AVP is absent
from the Time-Of-Day-Condition AVP, the time window starts on January from the Time-Of-Day-Condition AVP, the time window starts on January
1, 1900, 00:00 UTC. 1, 1900, 00:00 UTC.
skipping to change at page 27, line 8 skipping to change at page 26, line 12
actions that are associated with the condition part of a rule. The actions that are associated with the condition part of a rule. The
following actions are defined in this document: following actions are defined in this document:
0: drop 0: drop
1: shape 1: shape
2: mark 2: mark
drop: drop:
All traffic that is met by the condition part of a rule MUST be All traffic that is met by the condition part of a rule MUST be
dropped. This action implements firewalling functionality. dropped.
shape: shape:
[RFC2475] describes shaping as "the process of delaying packets [RFC2475] describes shaping as "the process of delaying packets
within a traffic stream to cause it to conform to some defined within a traffic stream to cause it to conform to some defined
traffic profile". When the action is set to 'shape', it is traffic profile". When the action is set to 'shape', the QoS-
expected that the QoS-Parameters AVP carries QoS information to Parameters AVP SHALL contain QoS information AVPS that indicate
indicate how to shape the traffic indicated in the condition part how to shape the traffic described by the condition part of the
of the rule. rule.
mark: mark:
[RFC2475] describes marking as "the process of setting the DS [RFC2475] describes marking as "the process of setting the DS
codepoint in a packet based on defined rules". When the action is codepoint in a packet based on defined rules". When the action is
set to 'mark', it is expected that the QoS-Parameters AVP carries set to 'mark', the QoS-Parameters AVP SHALL contain QoS
information about the DiffServ marking. information AVPS that indicate the DiffServ marking to be applied
to the traffic described by the condition part of the rule.
Further action values can be registered, as described in
Section 10.3.
[RFC2475] also describes an action called "policing" as "the process [RFC2475] also describes an action called "policing" as "the process
of discarding packets (by a dropper) within a traffic stream in of discarding packets (by a dropper) within a traffic stream in
accordance with the state of a corresponding meter enforcing a accordance with the state of a corresponding meter enforcing a
traffic profile". This behavior in modeled in the QoS-Rule through traffic profile". This behavior in modeled in the QoS-Rule through
the inclusion of the Excess-Treatment AVP containing a QoS-Action AVP the inclusion of the Excess-Treatment AVP containing a QoS-Action AVP
set to "drop". set to "drop".
Further action values can be registered, as described in
Section 10.3.
5.2. QoS-Profile-Id AVP 5.2. QoS-Profile-Id AVP
The QoS-Profile-Id AVP (AVP Code TBD) is of type Unsigned32 and The QoS-Profile-Id AVP (AVP Code TBD) is of type Unsigned32 and
contains a QoS profile template identifier. An initial QoS profile contains a QoS profile template identifier. An initial QoS profile
template is defined with value of 0 and can be found in template is defined with value of 0 and can be found in
[I-D.ietf-dime-qos-parameters]. The registry for the QoS profile [I-D.ietf-dime-qos-parameters]. The registry for the QoS profile
templates is created with the same document. templates is created with the same document.
5.3. QoS-Profile-Template AVP 5.3. QoS-Profile-Template AVP
skipping to change at page 28, line 22 skipping to change at page 27, line 31
5.4. QoS-Semantics 5.4. QoS-Semantics
The QoS-Semantics AVP (AVP Code TBD) is of type Enumerated and The QoS-Semantics AVP (AVP Code TBD) is of type Enumerated and
provides the semantics for the QoS-Profile-Template and QoS- provides the semantics for the QoS-Profile-Template and QoS-
Parameters AVPs in the QoS-Rule AVP. Parameters AVPs in the QoS-Rule AVP.
This document defines the following values: This document defines the following values:
(0): QoS-Desired (0): QoS-Desired
(1): QoS-Available (1): QoS-Available
(2): QoS-Reserved (2): QoS-Delivered
(3): Minimum-QoS (3): Minimum-QoS
(4): QoS-Authorized (4): QoS-Authorized
The semantic of the QoS parameters depend on the information provided The semantic of the QoS parameters depend on the information provided
in the list above. The semantics of the different values are as in the list above. The semantics of the different values are as
follows: follows:
Object Type Direction Semantic Object Type Direction Semantic
--------------------------------------------------------------------- ---------------------------------------------------------------------
QoS-Desired C->S Please authorize the indicated QoS QoS-Desired C->S Client requests authorization of the
indicated QoS.
QoS-Desired C<-S NA QoS-Desired C<-S NA
QoS-Available C->S Admission Control at interface indicates QoS-Available C->S Admission Control at client indicates
that this QoS is available. (note 1) that this QoS is available. (note 1)
QoS-Available C<-S Indicated QoS is available. (note 2) QoS-Available C<-S Admission Control at server indicates
QoS-Reserved C->S Used for reporting during accounting. that this QoS is available. (note 2)
QoS-Reserved C<-S NA QoS-Delivered C->S Client is reporting the actual QoS
Minimum-QoS C->S Indicates that the client is not delivered to the terminal.
interested in authorizing QoS that is QoS-Delivered C<-S NA
lower than Min. QoS. Minimum-QoS C->S Client is not interested in authorizing
Minimum-QoS C<-S The client must not provide QoS QoS that is lower than the indicated QoS.
guarantees lower than Min. QoS. Minimum-QoS C<-S Client must not provide QoS guarantees
lower than the indicated QoS.
QoS-Authorized C->S NA QoS-Authorized C->S NA
QoS-Authorized C<-S Indicated QoS authorized QoS-Authorized C<-S Server authorizes the indicated QoS.
Legend: Legend:
C: Diameter client C: Diameter client
S: Diameter server S: Diameter server
NA: Not applicable to this document; NA: Not applicable to this document;
no semantic defined in this specification no semantic defined in this specification
Notes: Notes:
(1) QoS-Available is only useful in relationship with QoS-Desired (1) QoS-Available in this direction indicates to the server that
(and optionally with Minimum-QoS). any QoS-Authorized or Minimum-QoS must be less than this
(2) QoS-Available is only useful when the AAA server performs indicated QoS.
admission control and knows about the resources in the network.
(2) QoS-Available in this direction is only useful when the AAA
server performs admission control and knows about the resources
in the network.
5.5. QoS-Parameters AVP 5.5. QoS-Parameters AVP
The QoS-Parameters AVP (AVP Code TBD) is of type grouped and contains The QoS-Parameters AVP (AVP Code TBD) is of type grouped and contains
Quality of Service parameters. These parameters are defined in Quality of Service parameters. These parameters are defined in
separate documents and depend on the indicated QoS profile template separate documents and depend on the indicated QoS profile template
of the QoS-Profile-Template AVP. For an initial QoS parameter of the QoS-Profile-Template AVP. For an initial QoS parameter
specification see [I-D.ietf-dime-qos-parameters]. specification see [I-D.ietf-dime-qos-parameters].
QoS-Parameters ::= < AVP Header: XXX > QoS-Parameters ::= < AVP Header: XXX >
skipping to change at page 34, line 38 skipping to change at page 33, line 38
| | Result-Code=DIAMETER_SUCCESS| | | Result-Code=DIAMETER_SUCCESS|
| | (authorization AVPs)| | | (authorization AVPs)|
| | QoS-Resources(QoS-Authorized)| | | QoS-Resources(QoS-Authorized)|
| |<-----------------------------+ | |<-----------------------------+
| | | | | |
Figure 5: Example of a Server-initiated Re-Authorization Procedure Figure 5: Example of a Server-initiated Re-Authorization Procedure
7.5. Diameter Credit Control with QoS Information 7.5. Diameter Credit Control with QoS Information
In this case the User is charged as soon as the Service Element (CC In this example, the CC client includes a QoS authorization request
client) receives the service request. In this case the client uses (QoS-Semantics=QoS-Desired) in the initial Credit Control
the "QoS-Desired" QoS-Semantics parameter in the QoS-Resources AVP Request(CCR). The CC server responds with a Credit Control Answer
that it sends to the Accounitng server. The server responds with a (CCA) which includes the granted resources with an authorized QoS
"QoS-Available" QoS-Semantics parameter in the QoS-Resources AVP definition (QoS-Semantics=QoS-Authorized) and the CC client proceeds
Service Element to deliver service with the specified QoS.
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 | | |
|<------------------------------------>| |
| | | |
. . . .
. . . .
Figure 6: Example for a One-Time Diameter Credit Control Charging At the end of service, the CC client reports the units used and the
Event QoS level at which those units were delivered (QoS-Semantics=QoS-
Delivered). The end of service could occur because the credit
resources granted to the user were exhausted or the service was been
successfully delivered or the service was terminated, e.g. because
the Service Element could not deliver the service at the authorized
QoS level.
Service Element
End User (CC Client) CC Server
| | |
|(1) Service Request | |
|-------------------->| |
| |(2) CCR (Initial, |
| | QoS-Resources(QoS-Desired)) |
| |--------------------------------->|
| |(3) CCA (Granted-Units, |
| | QoS-Resources(QoS-Authorized))|
| |<---------------------------------|
|(4) Service Delivery | |
|<------------------->| |
| | |
|(5) End of Service | |
|-------------------->| |
| |(6) CCR (Termination, Used-Units,|
| | QoS-Rsources(QoS-Delivered)) |
| |--------------------------------->|
| |(7) CCA |
| |<---------------------------------|
Figure 6: Example for a Diameter Credit Control with QoS Information
7.6. Classifier Examples 7.6. Classifier Examples
Example: Classify all packets from hosts on subnet 192.0.2.0/24 to Example: Classify all packets from hosts on subnet 192.0.2.0/24 to
ports 80, 8090 or 443 on web servers 192.0.2.123, 192.0.2.124, ports 80, 8090 or 443 on web servers 192.0.2.123, 192.0.2.124,
192.0.2.125. 192.0.2.125.
Classifier = { Classifier = {
Classifier-Id = "web_svr_example"; Classifier-Id = "web_svr_example";
Protocol = TCP; Protocol = TCP;
skipping to change at page 37, line 16 skipping to change at page 36, line 39
Mbit/sec, and the PHB-Class AVP is set to class "X". Then, the Mbit/sec, and the PHB-Class AVP is set to class "X". Then, the
Excess-Treatment AVP has to be included with the QoS-Action AVP set Excess-Treatment AVP has to be included with the QoS-Action AVP set
to 'mark' and the QoS-Parameters AVP to carry another PHB-Class AVP to 'mark' and the QoS-Parameters AVP to carry another PHB-Class AVP
indicating PHB-Class AVP setting to class "Y". indicating PHB-Class AVP setting to class "Y".
8. Acknowledgments 8. Acknowledgments
We would like to thank Victor Fajardo, Tseno Tsenov, Robert Hancock, We would like to thank Victor Fajardo, Tseno Tsenov, Robert Hancock,
Jukka Manner, Cornelia Kappler, Xiaoming Fu, Frank Alfano, Tolga Jukka Manner, Cornelia Kappler, Xiaoming Fu, Frank Alfano, Tolga
Asveren, Mike Montemurro, Glen Zorn, Avri Doria, Dong Sun, Tina Tsou, Asveren, Mike Montemurro, Glen Zorn, Avri Doria, Dong Sun, Tina Tsou,
Pete McCann, Georgios Karagiannis, Elwyn Davies, Max Riegel and Yong Pete McCann, Georgios Karagiannis, Elwyn Davies, Max Riegel, Yong Li
Li for their comments. We thank Victor Fajardo for his job as PROTO and Eric Gray for their comments. We thank Victor Fajardo for his
document shepherd. job as PROTO document shepherd.
9. Contributors 9. Contributors
Max Riegel contributed the VLAN sections. Max Riegel contributed the VLAN sections.
10. IANA Considerations 10. IANA Considerations
10.1. AVP Codes 10.1. AVP Codes
IANA is requested to allocate codes from the "AVP Codes" registry IANA is requested to allocate codes from the "AVP Codes" registry
under Authentication, Authorization, and Accounting (AAA) Parameters under Authentication, Authorization, and Accounting (AAA) Parameters
for the following AVPs that are defined in this document. for the following AVPs that are defined in this document.
+--------------------------------------------------------------------+ +-------------------------------------------------------------------+
| AVP Section | | AVP Section |
| Attribute Name Code Defined Data Type | | Attribute Name Code Defined Data Type |
+--------------------------------------------------------------------+ +-------------------------------------------------------------------+
|QoS-Resources TBD 3.1 Grouped | |QoS-Resources TBD 3.1 Grouped |
|QoS-Rule TBD 3.2 Grouped | |QoS-Rule TBD 3.2 Grouped |
|QoS-Rule-Precedence TBD 3.3 Unsigned32 | |QoS-Rule-Precedence TBD 3.3 Unsigned32 |
|Classifier TBD 4.1.1 Grouped | |Classifier TBD 4.1.1 Grouped |
|Classifier-ID TBD 4.1.2 OctetString | |Classifier-ID TBD 4.1.2 OctetString |
|Protocol TBD 4.1.3 Enumerated | |Protocol TBD 4.1.3 Enumerated |
|Direction TBD 4.1.4 Enumerated | |Direction TBD 4.1.4 Enumerated |
|From-Spec TBD 4.1.5 Grouped | |From-Spec TBD 4.1.5 Grouped |
|To-Spec TBD 4.1.6 Grouped | |To-Spec TBD 4.1.6 Grouped |
|Negated TBD 4.1.7.1 Enumerated | |Negated TBD 4.1.7.1 Enumerated |
|IP-Address TBD 4.1.7.2 Address | |IP-Address TBD 4.1.7.2 Address |
|IP-Address-Range TBD 4.1.7.3 Grouped | |IP-Address-Range TBD 4.1.7.3 Grouped |
|IP-Address-Start TBD 4.1.7.4 Address | |IP-Address-Start TBD 4.1.7.4 Address |
|IP-Address-End TBD 4.1.7.5 Address | |IP-Address-End TBD 4.1.7.5 Address |
|IP-Address-Mask TBD 4.1.7.6 Grouped | |IP-Address-Mask TBD 4.1.7.6 Grouped |
|IP-Mask-Bit-Mask-Width TBD 4.1.7.7 Unsigned32 | |IP-Mask-Bit-Mask-Width TBD 4.1.7.7 Unsigned32 |
|MAC-Address TBD 4.1.7.8 OctetString | |MAC-Address TBD 4.1.7.8 OctetString |
|MAC-Address-Mask TBD 4.1.7.9 Grouped | |MAC-Address-Mask TBD 4.1.7.9 Grouped |
|MAC-Address-Mask-Pattern TBD 4.1.7.10 OctetString | |MAC-Address-Mask-Pattern TBD 4.1.7.10 OctetString |
|EUI64-Address TBD 4.1.7.11 OctetString | |EUI64-Address TBD 4.1.7.11 OctetString |
|EUI64-Address-Mask TBD 4.1.7.12 Grouped | |EUI64-Address-Mask TBD 4.1.7.12 Grouped |
|EUI64-Address-Mask-Pattern TBD 4.1.7.13 OctetString | |EUI64-Address-Mask-Pattern TBD 4.1.7.13 OctetString |
|Port TBD 4.1.7.14 Integer32 | |Port TBD 4.1.7.14 Integer32 |
|Port-Range TBD 4.1.7.15 Grouped | |Port-Range TBD 4.1.7.15 Grouped |
|Port-Start TBD 4.1.7.16 Integer32 | |Port-Start TBD 4.1.7.16 Integer32 |
|Port-End TBD 4.1.7.17 Integer32 | |Port-End TBD 4.1.7.17 Integer32 |
|Use-Assigned-Address TBD 4.1.7.18 Enumerated | |Use-Assigned-Address TBD 4.1.7.18 Enumerated |
|Diffserv-Code-Point TBD 4.1.8.1 Enumerated | |Diffserv-Code-Point TBD 4.1.8.1 Enumerated |
|Fragmentation-Flag TBD 4.1.8.2 Enumerated | |Fragmentation-Flag TBD 4.1.8.2 Enumerated |
|IP-Option TBD 4.1.8.3 Grouped | |IP-Option TBD 4.1.8.3 Grouped |
|IP-Option-Type TBD 4.1.8.4 Enumerated | |IP-Option-Type TBD 4.1.8.4 Enumerated |
|IP-Option-Value TBD 4.1.8.5 OctetString | |IP-Option-Value TBD 4.1.8.5 OctetString |
|TCP-Option TBD 4.1.8.6 Grouped | |TCP-Option TBD 4.1.8.6 Grouped |
|TCP-Option-Type TBD 4.1.8.7 Enumerated | |TCP-Option-Type TBD 4.1.8.7 Enumerated |
|TCP-Option-Value TBD 4.1.8.8 OctetString | |TCP-Option-Value TBD 4.1.8.8 OctetString |
|TCP-Flags TBD 4.1.8.9 Grouped | |TCP-Flags TBD 4.1.8.9 Grouped |
|TCP-Flag-Type TBD 4.1.8.10 Unsigned32 | |TCP-Flag-Type TBD 4.1.8.10 Unsigned32 |
|ICMP-Type TBD 4.1.8.11 Grouped | |ICMP-Type TBD 4.1.8.11 Grouped |
|ICMP-Type-Number TBD 4.1.8.12 Enumerated | |ICMP-Type-Number TBD 4.1.8.12 Enumerated |
|ICMP-Code TBD 4.1.8.13 Enumerated | |ICMP-Code TBD 4.1.8.13 Enumerated |
|ETH-Option TBD 4.1.8.14 Grouped | |ETH-Option TBD 4.1.8.14 Grouped |
|ETH-Proto-Type TBD 4.1.8.15 Grouped | |ETH-Proto-Type TBD 4.1.8.15 Grouped |
|ETH-Ether-Type TBD 4.1.8.16 OctetString | |ETH-Ether-Type TBD 4.1.8.16 OctetString |
|ETH-SAP TBD 4.1.8.17 OctetString | |ETH-SAP TBD 4.1.8.17 OctetString |
|VLAN-ID-Range TBD 4.1.8.18 Grouped | |VLAN-ID-Range TBD 4.1.8.18 Grouped |
|S-VID-Start TBD 4.1.8.19 Unsigned32 | |S-VID-Start TBD 4.1.8.19 Unsigned32 |
|S-VID-End TBD 4.1.8.20 Unsigned32 | |S-VID-End TBD 4.1.8.20 Unsigned32 |
|C-VID-Start TBD 4.1.8.21 Unsigned32 | |C-VID-Start TBD 4.1.8.21 Unsigned32 |
|C-VID-End TBD 4.1.8.22 Unsigned32 | |C-VID-End TBD 4.1.8.22 Unsigned32 |
|User-Priority-Range TBD 4.1.8.23 Grouped | |User-Priority-Range TBD 4.1.8.23 Grouped |
|Low-User-Priority TBD 4.1.8.24 Unsigned32 | |Low-User-Priority TBD 4.1.8.24 Unsigned32 |
|High-User-Priority TBD 4.1.8.25 Unsigned32 | |High-User-Priority TBD 4.1.8.25 Unsigned32 |
|Time-Of-Day-Condition TBD 4.2.1 Grouped | |Time-Of-Day-Condition TBD 4.2.1 Grouped |
|Time-Of-Day-Start TBD 4.2.2 Unsigned32 | |Time-Of-Day-Start TBD 4.2.2 Unsigned32 |
|Time-Of-Day-End TBD 4.2.3 Unsigned32 | |Time-Of-Day-End TBD 4.2.3 Unsigned32 |
|Day-Of-Week-Mask TBD 4.2.4 Unsigned32 | |Day-Of-Week-Mask TBD 4.2.4 Unsigned32 |
|Day-Of-Month-Mask TBD 4.2.5 Unsigned32 | |Day-Of-Month-Mask TBD 4.2.5 Unsigned32 |
|Month-Of-Year-Mask TBD 4.2.6 Unsigned32 | |Month-Of-Year-Mask TBD 4.2.6 Unsigned32 |
|Absolute-Start-Time TBD 4.2.7 Time | |Absolute-Start-Time TBD 4.2.7 Time |
|Absolute-Start-Fractional-Seconds TBD 4.2.8 Unsigned32 | |Absolute-Start-Fractional-Seconds TBD 4.2.8 Unsigned32 |
|Absolute-End-Time TBD 4.2.9 Time | |Absolute-End-Time TBD 4.2.9 Time |
|Absolute-End-Fractional-Seconds TBD 4.2.10 Unsigned32 | |Absolute-End-Fractional-Seconds TBD 4.2.10 Unsigned32 |
|Timezone-Flag TBD 4.2.11 Enumerated | |Timezone-Flag TBD 4.2.11 Enumerated |
|Timezone-Offset TBD 4.2.12 Integer32 | |Timezone-Offset TBD 4.2.12 Integer32 |
|QoS-Action TBD 5.1 Grouped | |QoS-Action TBD 5.1 Grouped |
|QoS-Profile-Id TBD 5.2 Unsigned32 | |QoS-Profile-Id TBD 5.2 Unsigned32 |
|QoS-Profile-Template TBD 5.3 Grouped | |QoS-Profile-Template TBD 5.3 Grouped |
|QoS-Semantics TBD 5.4 Enumerated | |QoS-Semantics TBD 5.4 Enumerated |
|QoS-Parameters TBD 5.5 Grouped | |QoS-Parameters TBD 5.5 Grouped |
|Excess-Treatment TBD 5.6 Grouped | |Excess-Treatment TBD 5.6 Grouped |
|QoS-Capability TBD 6 Grouped | |QoS-Capability TBD 6 Grouped |
+--------------------------------------------------------------------+ +-------------------------------------------------------------------+
10.2. QoS-Semantics IANA Registry 10.2. QoS-Semantics IANA Registry
IANA is also requested to allocate a new registry under IANA is also requested to allocate a new registry under
Authentication, Authorization, and Accounting (AAA) Parameters for Authentication, Authorization, and Accounting (AAA) Parameters for
the QoS-Semantics AVP. The following values are allocated by this the QoS-Semantics AVP. The following values are allocated by this
specification: specification:
(0): QoS-Desired (0): QoS-Desired
(1): QoS-Available (1): QoS-Available
(2): QoS-Reserved (2): QoS-Delivered
(3): Minimum-QoS (3): Minimum-QoS
(4): QoS-Authorized (4): QoS-Authorized
The definition of new values is subject to the Specification Required The definition of new values is subject to the Specification Required
policy [RFC5226]. policy [RFC5226].
10.3. Action 10.3. Action
IANA is also requested to allocate a new registry under IANA is also requested to allocate a new registry under
Authentication, Authorization, and Accounting (AAA) Parameters for Authentication, Authorization, and Accounting (AAA) Parameters for
skipping to change at page 41, line 12 skipping to change at page 40, line 33
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
12.2. Informative References 12.2. Informative References
[I-D.ietf-dime-diameter-qos] [I-D.ietf-dime-diameter-qos]
Sun, D., McCann, P., Tschofenig, H., Tsou, T., Doria, A., Sun, D., McCann, P., Tschofenig, H., ZOU), T., Doria, A.,
and G. Zorn, "Diameter Quality of Service Application", and G. Zorn, "Diameter Quality of Service Application",
draft-ietf-dime-diameter-qos-09 (work in progress), draft-ietf-dime-diameter-qos-12 (work in progress),
July 2009. October 2009.
[I-D.ietf-dime-qos-parameters] [I-D.ietf-dime-qos-parameters]
Korhonen, J., Tschofenig, H., and E. Davies, "Quality of Korhonen, J., Tschofenig, H., and E. Davies, "Quality of
Service Parameters for Usage with Diameter", Service Parameters for Usage with Diameter",
draft-ietf-dime-qos-parameters-11 (work in progress), draft-ietf-dime-qos-parameters-11 (work in progress),
May 2009. May 2009.
[RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z., [RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z.,
and W. Weiss, "An Architecture for Differentiated and W. Weiss, "An Architecture for Differentiated
Services", RFC 2475, December 1998. Services", RFC 2475, December 1998.
[RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton, [RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton,
"Diameter Network Access Server Application", RFC 4005, "Diameter Network Access Server Application", RFC 4005,
August 2005. August 2005.
Appendix A. MAC and EUI64 Address Mask Usage Considerations
The MAC and EUI64 address bit masks are generally used in classifying
devices according to OUI and/or address blocks specific to the OUI
assignee. The bit masks are not intended to introduce a structure
into the MAC or EUI64 address space that was not intended by the
IEEE.
The MAC address bit mask should be defined as a contiguous series of
"N" set bits followed by a contiguous series of "48 - N" clear bits,
e.g. the MAC address bit mask of 0xFF00FF000000 would not be valid.
Similarly the EUI64 address bit mask should be defined as a
contiguous series of "N" set bits followed by a contiguous series of
"64 - N" clear bits.
It should also be noted that some OUIs are assigned for use in
applications that require number space management at the organization
level (e.g. - LLC/SNAP encoding), and are not commonly used for MAC
addresses.
Authors' Addresses Authors' Addresses
Jouni Korhonen Jouni Korhonen
Nokia Siemens Networks Nokia Siemens Networks
Linnoitustie 6 Linnoitustie 6
Espoo 02600 Espoo 02600
Finland Finland
Email: jouni.korhonen@nsn.com Email: jouni.korhonen@nsn.com
 End of changes. 41 change blocks. 
196 lines changed or deleted 246 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/