draft-ietf-dime-qos-parameters-00.txt   draft-ietf-dime-qos-parameters-01.txt 
Diameter Maintenance and J. Korhonen, Ed. Diameter Maintenance and J. Korhonen, Ed.
Extensions (DIME) TeliaSonera Extensions (DIME) TeliaSonera
Internet-Draft H. Tschofenig Internet-Draft H. Tschofenig
Intended status: Standards Track Nokia Siemens Networks Intended status: Standards Track Nokia Siemens Networks
Expires: December 11, 2007 June 9, 2007 Expires: April 1, 2008 September 29, 2007
Quality of Service Parameters for Usage with the AAA Framework Quality of Service Parameters for Usage with the AAA Framework
draft-ietf-dime-qos-parameters-00.txt draft-ietf-dime-qos-parameters-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 December 11, 2007. This Internet-Draft will expire on April 1, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document defines a number of Quality of Service (QoS) parameters This document defines a number of Quality of Service (QoS) parameters
that can be reused for conveying QoS information within RADIUS and that can be reused for conveying QoS information within RADIUS and
Diameter. Diameter.
skipping to change at page 2, line 15 skipping to change at page 2, line 15
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 3 2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 3
3. Parameter Overview . . . . . . . . . . . . . . . . . . . . . . 3 3. Parameter Overview . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Traffic Model Parameter . . . . . . . . . . . . . . . . . 3 3.1. Traffic Model Parameter . . . . . . . . . . . . . . . . . 3
3.2. Constraints Parameters . . . . . . . . . . . . . . . . . . 3 3.2. Constraints Parameters . . . . . . . . . . . . . . . . . . 3
3.3. Traffic Handling Directives . . . . . . . . . . . . . . . 5 3.3. Traffic Handling Directives . . . . . . . . . . . . . . . 5
3.4. Traffic Classifiers . . . . . . . . . . . . . . . . . . . 5 3.4. Traffic Classifiers . . . . . . . . . . . . . . . . . . . 5
4. Parameter Encoding . . . . . . . . . . . . . . . . . . . . . . 5 4. Parameter Encoding . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Header . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.1. Parameter Header . . . . . . . . . . . . . . . . . . . . . 5
4.2. TMOD-1 Parameter . . . . . . . . . . . . . . . . . . . . . 5 4.2. TMOD-1 Parameter . . . . . . . . . . . . . . . . . . . . . 5
4.3. TMOD-2 Parameter . . . . . . . . . . . . . . . . . . . . . 6 4.3. TMOD-2 Parameter . . . . . . . . . . . . . . . . . . . . . 6
4.4. Path Latency Parameter . . . . . . . . . . . . . . . . . . 7 4.4. Path Latency Parameter . . . . . . . . . . . . . . . . . . 7
4.5. Path Jitter Parameter . . . . . . . . . . . . . . . . . . 7 4.5. Path Jitter Parameter . . . . . . . . . . . . . . . . . . 7
4.6. Path PLR Parameter . . . . . . . . . . . . . . . . . . . . 8 4.6. Path PLR Parameter . . . . . . . . . . . . . . . . . . . . 8
4.7. Path PER Parameter . . . . . . . . . . . . . . . . . . . . 8 4.7. Path PER Parameter . . . . . . . . . . . . . . . . . . . . 8
4.8. Slack Term> Parameter . . . . . . . . . . . . . . . . . . 9 4.8. Slack Term Parameter . . . . . . . . . . . . . . . . . . . 9
4.9. Preemption Priority amp; Defending Priority Parameters . . 9 4.9. Preemption Priority amp; Defending Priority Parameters . . 9
4.10. Admission Priority Parameter . . . . . . . . . . . . . . . 10 4.10. Admission Priority Parameter . . . . . . . . . . . . . . . 10
4.11. RPH Priority Parameter . . . . . . . . . . . . . . . . . . 10 4.11. RPH Priority Parameter . . . . . . . . . . . . . . . . . . 10
4.12. Excess Treatment Parameter . . . . . . . . . . . . . . . . 12 4.12. Excess Treatment Parameter . . . . . . . . . . . . . . . . 12
4.13. PHB Class Parameter . . . . . . . . . . . . . . . . . . . 13 4.13. PHB Class Parameter . . . . . . . . . . . . . . . . . . . 13
4.14. DSTE Class Type Parameter . . . . . . . . . . . . . . . . 14 4.14. DSTE Class Type Parameter . . . . . . . . . . . . . . . . 14
4.15. Y.1541 QoS Class Parameter . . . . . . . . . . . . . . . . 14 4.15. Y.1541 QoS Class Parameter . . . . . . . . . . . . . . . . 14
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 5. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 16
6. Security Considerations . . . . . . . . . . . . . . . . . . . 16 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 6.1. QoS Profile . . . . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 6.2. Parameter ID . . . . . . . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . . 16 7. Security Considerations . . . . . . . . . . . . . . . . . . . 18
8.2. Informative References . . . . . . . . . . . . . . . . . . 17 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Intellectual Property and Copyright Statements . . . . . . . . . . 19 9.1. Normative References . . . . . . . . . . . . . . . . . . . 18
9.2. Informative References . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20
Intellectual Property and Copyright Statements . . . . . . . . . . 21
1. Introduction 1. Introduction
This document defines a number of Quality of Service (QoS) parameters This document defines a number of Quality of Service (QoS) parameters
that can be reused for conveying QoS information within RADIUS and that can be reused for conveying QoS information within RADIUS and
Diameter. Diameter.
The payloads used to carry these QoS parameters are opaque for the The payloads used to carry these QoS parameters are opaque for the
AAA client and the AAA server itself and interpreted by the AAA client and the AAA server itself and interpreted by the
respective Resource Management Function. respective Resource Management Function.
skipping to change at page 5, line 20 skipping to change at page 5, line 20
3.4. Traffic Classifiers 3.4. Traffic Classifiers
Resource reservations might refer to a packet processing with a Resource reservations might refer to a packet processing with a
particular DiffServ per-hop behavior (PHB) [RFC2475] or to a particular DiffServ per-hop behavior (PHB) [RFC2475] or to a
particular QoS class, e.g., Y.1541 QoS class or DiffServ-aware MPLS particular QoS class, e.g., Y.1541 QoS class or DiffServ-aware MPLS
traffic engineering (DSTE) class type [RFC3564], [RFC4124]. traffic engineering (DSTE) class type [RFC3564], [RFC4124].
4. Parameter Encoding 4. Parameter Encoding
4.1. Header 4.1. Parameter Header
Each QoS parameter is encoded in TLV format using a similar parameter Each QoS parameter is encoded in TLV format.
header:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|M|r|r|r| Parameter ID |r|r|r|r| Length | |M|r|r|r| Parameter ID |r|r|r|r| Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
M Flag: When set indicates the subsequent parameter MUST be M Flag: When set indicates the subsequent parameter MUST be
interpreted. Otherwise the parameter can be ignored if not interpreted. If the M flag is set and the parameter is not
understood. understood then it leads to an error. If the M flag is not
set and then not understood then it can be ignored.
The r bits are reserved. The r bits are reserved.
Parameter ID: Assigned to each parameter (see below) Parameter ID: Assigned to each individual QoS parameter
4.2. TMOD-1 Parameter 4.2. TMOD-1 Parameter
<TMOD-1> = <r> <b> <p> <m> [RFC2210] , [RFC2215] <TMOD-1> = <r> <b> <p> <m> [RFC2210] , [RFC2215]
The above notation means that the 4 <TMOD-1> sub-parameters must be The above notation means that the 4 <TMOD-1> sub-parameters must be
carried in the <TMOD-1> parameter. The coding for the <TMOD-1> carried in the <TMOD-1> parameter. The coding for the <TMOD-1>
parameter is as follows: parameter is as follows:
0 1 2 3 0 1 2 3
skipping to change at page 9, line 5 skipping to change at page 9, line 5
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
| Path Packet Error Ratio (32-bit floating point) | | Path Packet Error Ratio (32-bit floating point) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Path PER is a single 32-bit single precision IEEE floating point The Path PER is a single 32-bit single precision IEEE floating point
number in network byte order. The PERs are reported in units of number in network byte order. The PERs are reported in units of
10^-11. A system with resolution less than one microsecond MUST set 10^-11. A system with resolution less than one microsecond MUST set
unused digits to zero. The total PER added across all QoS aware unused digits to zero. The total PER added across all QoS aware
nodes can range as high as 10^-1. nodes can range as high as 10^-1.
4.8. Slack Term> Parameter 4.8. Slack Term Parameter
A description of the semantic of the parameter values can be found in A description of the semantic of the parameter values can be found in
[RFC2212], [RFC2215]. The coding for the <Path PLR> parameter is as [RFC2212], [RFC2215]. The coding for the <Path PLR> parameter is as
follows: follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|M|r|r|r| 7 |r|r|r|r| 1 | |M|r|r|r| 7 |r|r|r|r| 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 15, line 13 skipping to change at page 15, line 13
+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
Y.1541 QoS Class: Indicates the Y.1541 QoS Class. Values currently Y.1541 QoS Class: Indicates the Y.1541 QoS Class. Values currently
allowed are 0, 1, 2, 3, 4, 5, 6, 7. A value of 255 (all 1's) means allowed are 0, 1, 2, 3, 4, 5, 6, 7. A value of 255 (all 1's) means
that the <Y.1541 QoS Class> parameter is not used. that the <Y.1541 QoS Class> parameter is not used.
Class 0: Class 0:
Mean delay <= 100 ms, delay variation <= 50 ms, loss ratio <= Mean delay <= 100 ms, delay variation <= 50 ms, loss ratio <=
10^-3. Real-time, highly interactive applications, sensitive to 10^-3. Real-time, highly interactive applications, sensitive to
jitter. Application examples include VoIP, Video Teleconference. jitter. Application examples include VoIP, Video Teleconference.
Class 1: Class 1:
Mean delay <= 400 ms, delay variation <= 50 ms, loss ratio <= Mean delay <= 400 ms, delay variation <= 50 ms, loss ratio <=
10^-3. Real-time, interactive applications, sensitive to jitter. 10^-3. Real-time, interactive applications, sensitive to jitter.
Application examples include VoIP, Video Teleconference. Application examples include VoIP, Video Teleconference.
Class 2: Class 2:
Mean delay <= 100 ms, delay variation unspecified, loss ratio <= Mean delay <= 100 ms, delay variation unspecified, loss ratio <=
10^-3. Highly interactive transaction data. Application examples 10^-3. Highly interactive transaction data. Application examples
include signaling. include signaling.
Class 3: Class 3:
Mean delay <= 400 ms, delay variation unspecified, loss ratio <= Mean delay <= 400 ms, delay variation unspecified, loss ratio <=
10^-3. Interactive transaction data. Application examples 10^-3. Interactive transaction data. Application examples
include signaling. include signaling.
Class 4: Class 4:
Mean delay <= 1 sec, delay variation unspecified, loss ratio <= Mean delay <= 1 sec, delay variation unspecified, loss ratio <=
10^-3. Low Loss Only applications. Application examples include 10^-3. Low Loss Only applications. Application examples include
short transactions, bulk data, video streaming. short transactions, bulk data, video streaming.
Class 5: Class 5:
Mean delay unspecified, delay variation unspecified, loss ratio Mean delay unspecified, delay variation unspecified, loss ratio
unspecified. Unspecified applications. Application examples unspecified. Unspecified applications. Application examples
include traditional applications of default IP networks. include traditional applications of default IP networks.
Class 6: Class 6:
Mean delay <= 100 ms, delay variation <= 50 ms, loss ratio <= Mean delay <= 100 ms, delay variation <= 50 ms, loss ratio <=
10^-5. Applications that are highly sensitive to loss, such as 10^-5. Applications that are highly sensitive to loss, such as
television transport, high-capacity TCP transfers, and TDM circuit television transport, high-capacity TCP transfers, and TDM circuit
emulation. emulation.
Class 7: Class 7:
Mean delay <= 400 ms, delay variation <= 50 ms, loss ratio <= Mean delay <= 400 ms, delay variation <= 50 ms, loss ratio <=
10^-5. Applications that are highly sensitive to loss, such as 10^-5. Applications that are highly sensitive to loss, such as
television transport, high-capacity TCP transfers, and TDM circuit television transport, high-capacity TCP transfers, and TDM circuit
emulation. emulation.
5. IANA Considerations 5. Extensibility
This document reuses the namespace created in [I-D.ietf-nsis-qspec]. This document is designed with extensibility in mind given that
different organizations and groups are used to define their own
Quality of Service parameters. This document provides an initial QoS
profile with common set of parameters. Ideally, these parameters
should be used whenever possible but there are cases where additional
parameters might be needed, or where the parameters specified in this
document are used with a different semantic. In this case it is
advisable to define a new QoS profile that may consist of new
parameters in addition to parameters defined in this document or an
entirely different set of parameters.
No actions are required by IANA. To enable the definition of new QoS profiles a 8 octet registry is
defined field that is represented by a 4-octet vendor and 4-octet
specifier field. The vendor field indicates the type as either
standards-specified or vendor-specific. If the four octets of the
vendor field are 0x00000000, then the value is standards-specified
and the registry is maintained by IANA, and any other value
represents a vendor-specific Object Identifier (OID). IANA created
registry is split into two value ranges; one range uses the
"Standards Action" and the second range uses "Specification Required"
allocation policy. The latter range is meant to be used by
organizations outside the IETF.
6. Security Considerations 6. IANA Considerations
This document reuses the namespace created in [I-D.ietf-nsis-qspec]
for
1. Admission Priority Parameter
2. RPH Namespace Parameter
3. RPH Priority Parameter
4. Excess Treatment Parameter
5. DSTE Class Type Parameter
6. Y.1541 QoS Class Parameter
IANA is requested to create the following registries: QoS Profile (32
bits), and Parameter ID (12 bits)
6.1. QoS Profile
The QoS Profile refers to a 64 bit long field that is represented by
a 4-octet vendor and 4-octet specifier field. The vendor field
indicates the type as either standards-specified or vendor-specific.
If the four octets of the vendor field are 0x00000000, then the value
is standards-specified and the registry is maintained by IANA, and
any other value represents a vendor-specific Object Identifier (OID).
The specifier field indicates the actual QoS profile. The vendor
field 0x00000000 is reserved to indicate that the values in the
specifier field are maintained by IANA. This document requests IANA
to create such a registry and to allocate the value zero (0) for the
QoS profile defined in this document.
For any other vendor field, the specifier field is maintained by the
vendor.
For the IANA maintained QoS profiles the following allocation policy
is defined:
1 to 511: Standards Action
512 to 4095: Specification Required
Standards action is required to depreciate, delete, or modify
existing QoS profile values in the range of 0-511 and a specification
is required to depreciate, delete, or modify existing QoS profile
values in the range of 512-4095.
6.2. Parameter ID
The Parameter ID refers to a 12 bit long field.
The following values are allocated by this specification.
(0): <TMOD-1>
(1): <TMOD-2>
(2): <Path Latency>
(3): <Path Jitter>
(4): <Path PLR>
(5): <Path PER>
(6): <Slack Term>
(7): <Preemption Priority> & <Defending Priority>
(8): <Admission Priority>
(9): <RPH Priority>
(10): <Excess Treatment>
(11): <PHB Class>
(12): <DSTE Class Type>
(13): <Y.1541 QoS Class>
The allocation policies for further values are as follows:
14-127: Standards Action
128-255: Private/Experimental Use
255-4095: Specification Required
A standards track document is required to depreciate, delete, or
modify existing Parameter IDs.
7. Security Considerations
This document does not raise any security concerns as it only defines This document does not raise any security concerns as it only defines
QoS parameters. QoS parameters.
7. Acknowledgements 8. Acknowledgements
The authors would like to thank the NSIS QSPEC [I-D.ietf-nsis-qspec] The authors would like to thank the NSIS QSPEC [I-D.ietf-nsis-qspec]
authors (Cornelia Kappler, Jerry Ash, Attila Bader, Dave Oran), the authors (Cornelia Kappler, Jerry Ash, Attila Bader, Dave Oran), the
NSIS working group chairs (John Loughney and Martin Stiemerling) and NSIS working group chairs (John Loughney and Martin Stiemerling) and
the former Transport Area Directors (Allison Manking, Jon Peterson) the former Transport Area Directors (Allison Manking, Jon Peterson)
for their help. for their help.
8. References 9. References
8.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated [RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated
Services", RFC 2210, September 1997. Services", RFC 2210, September 1997.
[RFC2212] Shenker, S., Partridge, C., and R. Guerin, "Specification [RFC2212] Shenker, S., Partridge, C., and R. Guerin, "Specification
of Guaranteed Quality of Service", RFC 2212, of Guaranteed Quality of Service", RFC 2212,
September 1997. September 1997.
skipping to change at page 17, line 38 skipping to change at page 20, line 9
Diffserv-aware MPLS Traffic Engineering", RFC 4124, Diffserv-aware MPLS Traffic Engineering", RFC 4124,
June 2005. June 2005.
[RFC4412] Schulzrinne, H. and J. Polk, "Communications Resource [RFC4412] Schulzrinne, H. and J. Polk, "Communications Resource
Priority for the Session Initiation Protocol (SIP)", Priority for the Session Initiation Protocol (SIP)",
RFC 4412, February 2006. RFC 4412, February 2006.
[Y.1541] "Network Performance Objectives for IP-Based Services", , [Y.1541] "Network Performance Objectives for IP-Based Services", ,
2006. 2006.
8.2. Informative References 9.2. Informative References
[I-D.ietf-nsis-qspec] [I-D.ietf-nsis-qspec]
Ash, J., "QoS NSLP QSPEC Template", Ash, J., "QoS NSLP QSPEC Template",
draft-ietf-nsis-qspec-16 (work in progress), March 2007. draft-ietf-nsis-qspec-17 (work in progress), July 2007.
[Y.1540] "Internet Protocol Data Communication Service - IP Packet [Y.1540] "Internet Protocol Data Communication Service - IP Packet
Transfer and Availability Performance Parameters", , Transfer and Availability Performance Parameters", ,
December 2002. December 2002.
Authors' Addresses Authors' Addresses
Jouni Korhonen (editor) Jouni Korhonen (editor)
TeliaSonera TeliaSonera
Teollisuuskatu 13 Teollisuuskatu 13
skipping to change at page 18, line 21 skipping to change at page 20, line 35
Finland Finland
Email: jouni.korhonen@teliasonera.com Email: jouni.korhonen@teliasonera.com
Hannes Tschofenig Hannes Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
Otto-Hahn-Ring 6 Otto-Hahn-Ring 6
Munich, Bavaria 81739 Munich, Bavaria 81739
Germany Germany
Email: Hannes.Tschofenig@siemens.com Email: Hannes.Tschofenig@nsn.com
URI: http://www.tschofenig.com URI: http://www.tschofenig.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
 End of changes. 28 change blocks. 
30 lines changed or deleted 135 lines changed or added

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