draft-ietf-xrblock-rtcp-xr-loss-conceal-00.txt   draft-ietf-xrblock-rtcp-xr-loss-conceal-01.txt 
Audio/Video Transport Working Group G. Hunt Network Working Group C. Bi
Internet-Draft Unaffiliated Internet-Draft STTRI
Intended status: Standards Track A. Clark Intended status: Standards Track A. Clark
Expires: December 14, 2012 Telchemy Expires: December 24, 2012 Telchemy
G. Zorn G. Hunt
Network Zen Unaffiliated
C. Bi
STTRI
Q. Wu Q. Wu
Huawei Huawei
June 12, 2012 G. Zorn, Ed.
Network Zen
June 22, 2012
RTCP XR Report Block for Loss Concealment metric Reporting RTCP XR Report Block for Loss Concealment Metric Reporting
draft-ietf-xrblock-rtcp-xr-loss-conceal-00.txt draft-ietf-xrblock-rtcp-xr-loss-conceal-01.txt
Abstract Abstract
This document defines an RTCP XR Report Block that allows the This document defines an RTCP XR Report Block that allows the
reporting of Loss Concealment metrics primarily for audio reporting of Loss Concealment metrics primarily for audio
applications of RTP. applications of RTP.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on December 14, 2012. This Internet-Draft will expire on December 24, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Loss Concealment Report Block . . . . . . . . . . . . . . 3 1.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 1.2. Loss Concealment Report Block . . . . . . . . . . . . . . . 3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 4 1.3. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 4 1.4. Performance Metrics Framework . . . . . . . . . . . . . . . 4
2. Loss Concealment Block . . . . . . . . . . . . . . . . . . . . 5 1.5. Applicability . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Report Block Structure . . . . . . . . . . . . . . . . . . 5 2. Loss Concealment Block . . . . . . . . . . . . . . . . . . . . 4
2.2. Definition of Fields in Loss Concealment Report Block . . 5 2.1. Report Block Structure . . . . . . . . . . . . . . . . . . 4
3. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 9 2.2. Definition of Fields in Loss Concealment Report Block . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 3. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 10 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
4.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . 10 4.1. New RTCP XR Block Type value . . . . . . . . . . . . . . . 8
4.3. Contact information for registrations . . . . . . . . . . 10 4.2. New RTCP XR SDP Parameter . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 4.3. Contact Information for Registrations . . . . . . . . . . . 8
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . . 13 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . . 13 7.1. Normative References . . . . . . . . . . . . . . . . . . . 9
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 14 7.2. Informative References . . . . . . . . . . . . . . . . . . 9
A.1. draft-ietf-xrblock-rtcp-xr-loss-conceal-00 . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
1.1. Loss Concealment Report Block 1.1. Standards Language
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 [RFC2119].
1.2. Loss Concealment Report Block
This draft defines a new block type to augment those defined in This draft defines a new block type to augment those defined in
[RFC3611], for use in a range of RTP applications. Friedman, et al. [RFC3611] for use in a range of RTP applications.
At any instant, the audio output at a receiver may be classified as At any instant, the audio output at a receiver may be classified as
either 'normal' or 'concealed'. 'Normal' refers to playout of audio either 'normal' or 'concealed'. 'Normal' refers to playout of audio
payload received from the remote end, and also includes locally payload received from the remote end, and also includes locally
generated signals such as announcements, tones and comfort noise. generated signals such as announcements, tones and comfort noise.
Concealment refers to playout of locally-generated signals used to Concealment refers to playout of locally-generated signals used to
mask the impact of network impairments or to reduce the audibility of mask the impact of network impairments or to reduce the audibility of
jitter buffer adaptations. jitter buffer adaptations.
The new block type provides metrics for actions taken by the receiver The new block type provides metrics for actions taken by the receiver
skipping to change at page 3, line 41 skipping to change at page 3, line 47
Further metrics (Playout Interrupt Count and Mean Playout Interrupt Further metrics (Playout Interrupt Count and Mean Playout Interrupt
Size) report the number of times normal playout was interrupted, and Size) report the number of times normal playout was interrupted, and
the mean duration of these interruptions. the mean duration of these interruptions.
Loss Concealment Duration and Buffer Adjustment Concealment Duration Loss Concealment Duration and Buffer Adjustment Concealment Duration
are reported separately because buffer adjustment is typically are reported separately because buffer adjustment is typically
arranged to occur in silence periods so may have very little impact arranged to occur in silence periods so may have very little impact
on user experience, whilst loss concealment may occur at any time. on user experience, whilst loss concealment may occur at any time.
The metric belongs to the class of transport-related terminal metrics The metric belongs to the class of transport-related terminal metrics
defined in [MONARCH] (work in progress). defined in Wu, et al. [I-D.ietf-avtcore-monarch].
1.2. RTCP and RTCP XR Reports 1.3. RTCP and RTCP XR Reports
The use of RTCP for reporting is defined in [RFC3550]. [RFC3611] The use of RTCP for reporting is defined in Schulzrinne, et
defined an extensible structure for reporting using an RTCP Extended al. [RFC3550]. Friedman, Cacares & Clark [RFC3611] define an
Report (XR). This draft defines a new Extended Report block that extensible structure for reporting using an RTCP Extended Report
MUST be used as defined in [RFC3550] and [RFC3611]. (XR). This draft defines a new Extended Report block that MUST be
used as defined in RFC 3550 and RFC 3611.
1.3. Performance Metrics Framework 1.4. Performance Metrics Framework
The Performance Metrics Framework [RFC6390] provides guidance on the Clark & Claise [RFC6390] provides guidance on the definition and
definition and specification of performance metrics. The RTP specification of performance metrics. Wu, et
Monitoring Architectures [MONARCH] provides guideline for reporting al. [I-D.ietf-avtcore-monarch] provides guidelines for RTCP XR report
block format using RTCP XR. The Metrics Block described in this block formats. The report block defined in this document is in
document are in accordance with the guidelines in [RFC6390] and accordance with those guidelines.
[MONARCH].
1.4. Applicability 1.5. Applicability
This metric is primarily applicable to audio applications of RTP. This metric is primarily applicable to audio applications of RTP.
EDITOR'S NOTE: are there metrics for concealment of transport errors EDITOR'S NOTE: are there metrics for concealment of transport errors
for video? for video?
2. Loss Concealment Block 2. Loss Concealment Block
2.1. Report Block Structure 2.1. Report Block Structure
Loss Concealment metrics block 0 1 2 3
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
0 1 2 3 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 | BT=NLC | I |plc| rsv. | block length=5 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=NLC | I |plc| rsv. | block length=5 | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | On-time Playout Duration |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| On-time Playout Duration | | Loss Concealment Duration |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Loss Concealment Duration | | Buffer Adjustment Concealment Duration |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Buffer Adjustment Concealment Duration | | Playout Interrupt Count | Mean Playout Interrupt Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Playout Interrupt Count | Mean Playout Interrupt Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Report Block Structure Figure 1: Structure of the Loss Concealment Metrics Block
2.2. Definition of Fields in Loss Concealment Report Block 2.2. Definition of Fields in Loss Concealment Report Block
Block type (BT): 8 bits Block type (BT): 8 bits
A Loss Concealment Metrics Report Block is identified by the A Loss Concealment Metrics Report Block is identified by the
constant NLC. constant <NLC>.
[Note to RFC Editor: please replace NLC with the IANA provided [Note to RFC Editor: please replace <NLC> with the IANA provided
RTCP XR block type for this block.] RTCP XR block type for this block.]
Interval Metric flag (I): 2 bit Interval Metric flag (I): 2 bit
This field is used to indicate whether the Delay metrics are This field is used to indicate whether the Delay metrics are
Sampled, Interval or Cumulative metrics, that is, whether the Sampled, Interval or Cumulative metrics, that is, whether the
reported values applies to the most recent measurement interval reported values applies to the most recent measurement interval
duration between successive metrics reports (I=10) (the Interval duration between successive metrics reports (I=10) (the Interval
Duration) or to the accumulation period characteristic of Duration) or to the accumulation period characteristic of
cumulative measurements (I=11) (the Cumulative Duration) or is a cumulative measurements (I=11) (the Cumulative Duration) or is a
skipping to change at page 6, line 34 skipping to change at page 6, line 7
These bits are reserved. They SHOULD be set to zero by senders These bits are reserved. They SHOULD be set to zero by senders
and MUST be ignored by receivers. and MUST be ignored by receivers.
block length: 16 bits block length: 16 bits
The length of this report block in 32-bit words, minus one. For The length of this report block in 32-bit words, minus one. For
the Delay block, the block length is equal to 5. the Delay block, the block length is equal to 5.
SSRC of source: 32 bits SSRC of source: 32 bits
As defined in Section 4.1 of [RFC3611]. As defined in Section 4.1 of RFC 3611.
On-time Playout Duration (ms): 32 bits On-time Playout Duration (ms): 32 bits
'On-time' playout is the uninterrupted, in-sequence playout of 'On-time' playout is the uninterrupted, in-sequence playout of
valid decoded audio information originating from the remote valid decoded audio information originating from the remote
endpoint. This includes comfort noise during periods of remote endpoint. This includes comfort noise during periods of remote
talker silence, if VAD is used, and locally generated or talker silence, if voice activity detection (VAD) is in use, and
regenerated tones and announcements. locally generated or regenerated tones and announcements.
An equivalent definition is that on-time playout is playout of any An equivalent definition is that on-time playout is playout of any
signal other than those used for concealment. signal other than those used for concealment.
On-time playout duration MUST include both speech and silence On-time playout duration MUST include both speech and silence
intervals, whether VAD is used or not. This duration is reported intervals, whether VAD is used or not. This duration is reported
in millisecond units. in millisecond units.
If the measured value exceeds 0xFFFFFFFD, the value 0xFFFFFFFE If the measured value exceeds 0xFFFFFFFD, the value 0xFFFFFFFE
SHOULD be reported to indicate an over-range measurement. If the SHOULD be reported to indicate an over-range measurement. If the
skipping to change at page 9, line 7 skipping to change at page 8, line 7
The mean duration, in ms, of interruptions to normal playout which The mean duration, in ms, of interruptions to normal playout which
occurred during the reporting period. occurred during the reporting period.
If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be
reported to indicate an over-range measurement. If the reported to indicate an over-range measurement. If the
measurement is unavailable, the value 0xFFFF SHOULD be reported. measurement is unavailable, the value 0xFFFF SHOULD be reported.
3. SDP Signaling 3. SDP Signaling
[RFC3611] defines the use of SDP (Session Description Protocol) The use of the Session Description Protocol (SDP) [RFC4566] for
[RFC4566] for signaling the use of XR blocks. XR blocks MAY be used signaling the use of XR blocks is described in RFC 3611. XR blocks
without prior signaling. MAY be used without prior signaling.
This section augments the SDP [RFC4566] attribute "rtcp-xr" defined This section augments the SDP attribute "rtcp-xr" [RFC3611] by
in [RFC3611] by providing an additional value of "xr-format" to providing an additional value of "xr-format" to signal the use of the
signal the use of the report block defined in this document. report block defined in this document.
rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF
(defined in [RFC3611]) (defined in [RFC3611])
xr-format =/ xr-conceal-block xr-format =/ xr-conceal-block
xr-conceal-block = "loss-conceal" xr-conceal-block = "loss-conceal"
4. IANA Considerations 4. IANA Considerations
New block types for RTCP XR are subject to IANA registration. For New block types for RTCP XR are subject to IANA registration. For
general guidelines on IANA considerations for RTCP XR, refer to general guidelines on IANA considerations for RTCP XR, refer to RFC
[RFC3611]. 3611.
4.1. New RTCP XR Block Type value 4.1. New RTCP XR Block Type value
This document assigns the block type value NJB in the IANA "RTCP XR This document assigns the block type value NJB in the IANA "RTCP XR
Block Type Registry" to the "Loss Concealment Metrics Block". Block Type Registry" to the "Loss Concealment Metrics Block".
[Note to RFC Editor: please replace NLC with the IANA provided RTCP [Note to RFC Editor: please replace <NLC> with the RTCP XR block type
XR block type for this block.] assigned by IANA for this block.]
4.2. New RTCP XR SDP Parameter 4.2. New RTCP XR SDP Parameter
This document also registers a new parameter "loss-conceal" in the This document also registers a new parameter "loss-conceal" in the
"RTCP XR SDP Parameters Registry". "RTCP XR SDP Parameters Registry".
4.3. Contact information for registrations 4.3. Contact Information for Registrations
The contact information for the registrations is: The contact information for the registrations is:
Alan Clark (alan.d.clark@telchemy.com) Alan Clark (alan.d.clark@telchemy.com)
2905 Premiere Parkway, Suite 280 2905 Premiere Parkway, Suite 280
Duluth, GA 30097 Duluth, GA 30097
USA USA
5. Security Considerations 5. Security Considerations
It is believed that this proposed RTCP XR report block introduces no It is believed that this proposed RTCP XR report block introduces no
new security considerations beyond those described in [RFC3611]. new security considerations beyond those described in RFC 3611. This
This block does not provide per-packet statistics so the risk to block does not provide per-packet statistics so the risk to
confidentiality documented in Section 7, paragraph 3 of [RFC3611] confidentiality documented in Section 7, paragraph 3 of RFC 3611 does
does not apply. not apply.
6. Acknowledgements 6. Acknowledgements
The authors gratefully acknowledge the comments and contributions The authors gratefully acknowledge the comments and suggestions made
made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin Connor,
Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert Higashi,
Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith Lantz,
Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi
Ravi Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada. Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs
Requirement Levels", March 1997. to Indicate Requirement Levels", BCP 14,
RFC 2119, March 1997.
[RFC3550] Schulzrinne, H., "RTP: A Transport Protocol for Real-Time [RFC3550] Schulzrinne, H., Casner, S., Frederick,
Applications", RFC 3550, July 2003. R., and V. Jacobson, "RTP: A Transport
Protocol for Real-Time Applications",
STD 64, RFC 3550, July 2003.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control [RFC3611] Friedman, T., Caceres, R., and A. Clark,
Protocol Extended Reports (RTCP XR)", November 2003. "RTP Control Protocol Extended Reports
(RTCP XR)", RFC 3611, November 2003.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C.
Description Protocol", July 2006. Perkins, "SDP: Session Description
Protocol", RFC 4566, July 2006.
7.2. Informative References 7.2. Informative References
[MONARCH] Hunt, G., "Monitoring Architectures for RTP", [I-D.ietf-avtcore-monarch] Wu, W., Hunt, G., and P. Arden,
ID draft-ietf-avtcore-monarch-04, August 2011. "Guidelines for Use of the RTP Monitoring
Framework", draft-ietf-avtcore-monarch-16
[RFC6390] Clark, A. and B. Claise, "Framework for Performance Metric (work in progress), June 2012.
Development", RFC 6390, October 2011.
Appendix A. Change Log
Note to the RFC-Editor: please remove this section prior to
publication as an RFC.
A.1. draft-ietf-xrblock-rtcp-xr-loss-conceal-00
The following are the major changes to previous version :
o Changed BNF for SDP following Christian Groves' and Tom Taylor's
comments (4th and 5th May 2009).
o Updated references. [RFC6390] Clark, A. and B. Claise, "Guidelines for
Considering New Performance Metric
Development", BCP 170, RFC 6390,
October 2011.
Authors' Addresses Authors' Addresses
Geoff Hunt Claire Bi
Unaffiliated Shanghai Research Institure of China Telecom Corporation Limited
No.1835,South Pudong Road
Shanghai 200122
China
Email: r.geoff.hunt@gmail.com EMail: bijy@sttri.com.cn
Alan Clark Alan Clark
Telchemy Incorporated Telchemy Incorporated
2905 Premiere Parkway, Suite 280 2905 Premiere Parkway, Suite 280
Duluth, GA 30097 Duluth, GA 30097
USA USA
Email: alan.d.clark@telchemy.com EMail: alan.d.clark@telchemy.com
Glen Zorn
Network Zen
77/440 Soi Phoomjit, Rama IV Road
Phra Khanong, Khlong Toie
Bangkok 10110
Thailand
Phone: +66 (0) 87 502 4274
Email: gwz@net-zen.net
Claire Bi Geoff Hunt
Shanghai Research Institure of China Telecom Corporation Limited Unaffiliated
No.1835,South Pudong Road
Shanghai 200122
China
Email: bijy@sttri.com.cn EMail: r.geoff.hunt@gmail.com
Qin Wu Qin Wu
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Email: sunseawq@huawei.com EMail: sunseawq@huawei.com
Glen Zorn (editor)
Network Zen
227/358 Thanon Sanphawut
Bang Na, Bangkok 10260
Thailand
Phone: +66 (0) 90 920 1060
EMail: glenzorn@gmail.com
 End of changes. 40 change blocks. 
139 lines changed or deleted 126 lines changed or added

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