draft-ietf-xrblock-rtcp-xr-synchronization-06.txt   draft-ietf-xrblock-rtcp-xr-synchronization-07.txt 
Network Working Group H. Asaeda Network Working Group H. Asaeda
Internet-Draft NICT Internet-Draft NICT
Intended status: Standards Track R. Huang Intended status: Standards Track Q. Wu
Expires: November 30, 2013 Q. Wu Expires: May 23, 2014 R. Huang
Huawei Huawei
May 29, 2013 November 19, 2013
RTP Control Protocol (RTCP) Extended Report (XR) Blocks for RTP Control Protocol (RTCP) Extended Report (XR) Blocks for
Synchronization Delay and Offset Metrics Reporting Synchronization Delay and Offset Metrics Reporting
draft-ietf-xrblock-rtcp-xr-synchronization-06 draft-ietf-xrblock-rtcp-xr-synchronization-07
Abstract Abstract
This document defines two RTP Control Protocol (RTCP) Extended Report This document defines two RTP Control Protocol (RTCP) Extended Report
(XR) Blocks that allow the reporting of synchronization delay and (XR) Blocks that allow the reporting of synchronization delay and
offset metrics for use in a range of RTP applications. offset metrics for use in a range of RTP applications.
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 November 30, 2013. This Internet-Draft will expire on May 23, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Synchronization Delay and Offset Metrics Reporting 1.1. Synchronization Delay and Offset Metrics Reporting Blocks 3
Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . 3
1.2. RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . . 3 1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3
1.3. Performance Metrics Framework . . . . . . . . . . . . . . 3 1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3
1.4. Applicability . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Standards Language . . . . . . . . . . . . . . . . . . . 4
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 4 3. RTP Flows Initial Synchronization Delay Report Block . . . . 5
3. RTP Flows Initial Synchronization Delay Report Block . . . . . 5 3.1. Metric Block Structure . . . . . . . . . . . . . . . . . 5
3.1. Metric Block Structure . . . . . . . . . . . . . . . . . . 5 3.2. Definition of Fields in RTP Flow Initial Synchronization
3.2. Definition of Fields in RTP Flow Initial Delay Metrics Block . . . . . . . . . . . . . . . . . . . 5
Synchronization Delay Metrics Block . . . . . . . . . . . 5 4. RTP Flows Synchronization Offset Metrics Block . . . . . . . 6
4. RTP Flows Synchronization Offset Metrics Block . . . . . . . . 6 4.1. Metric Block Structure . . . . . . . . . . . . . . . . . 7
4.1. Metric Block Structure . . . . . . . . . . . . . . . . . . 7 4.2. Definition of Fields in RTP Flow General Synchronization
4.2. Definition of Fields in RTP Flow General Offset Metrics Block . . . . . . . . . . . . . . . . . . 7
Synchronization Offset Metrics Block . . . . . . . . . . . 7 5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 9
5. SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . . 9 5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . 9
5.1. SDP rtcp-xr-attrib Attribute Extension . . . . . . . . . . 9 5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . 10
5.2. Offer/Answer Usage . . . . . . . . . . . . . . . . . . . . 9 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 9.1. Normative References . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . . 11 9.2. Informative References . . . . . . . . . . . . . . . . . 12
9.2. Informative References . . . . . . . . . . . . . . . . . . 11 Appendix A. Metrics represented using RFC6390 Template . . . . . 12
Appendix A. Metrics represented using RFC6390 Template . . . . . 12 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 13
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 13 B.1. draft-ietf-xrblock-rtcp-xr-syncronization-07 . . . . . . 13
B.1. draft-ietf-xrblock-rtcp-xr-syncronization-06 . . . . . . . 13 B.2. draft-ietf-xrblock-rtcp-xr-syncronization-06 . . . . . . 13
B.2. draft-ietf-xrblock-rtcp-xr-syncronization-05 . . . . . . . 13 B.3. draft-ietf-xrblock-rtcp-xr-syncronization-05 . . . . . . 13
B.3. draft-ietf-xrblock-rtcp-xr-syncronization-04 . . . . . . . 13 B.4. draft-ietf-xrblock-rtcp-xr-syncronization-04 . . . . . . 14
B.4. draft-ietf-xrblock-rtcp-xr-syncronization-03 . . . . . . . 13 B.5. draft-ietf-xrblock-rtcp-xr-syncronization-03 . . . . . . 14
B.5. draft-ietf-xrblock-rtcp-xr-syncronization-02 . . . . . . . 13 B.6. draft-ietf-xrblock-rtcp-xr-syncronization-02 . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
1.1. Synchronization Delay and Offset Metrics Reporting Blocks 1.1. Synchronization Delay and Offset Metrics Reporting Blocks
This document defines two new block types to augment those defined in This document defines two new block types to augment those defined in
[RFC3611], for use in a range of RTP applications. [RFC3611], for use in a range of RTP applications.
The first new block type supports reporting of Initial The first new block type supports reporting of Initial
Synchronization Delay to establish multimedia session. Information Synchronization Delay to establish multimedia session. Information
is recorded about time difference between the start of RTP sessions is recorded about time difference between the start of RTP sessions
and the time the RTP receiver acquires all components of RTP sessions and the time the RTP receiver acquires all components of RTP sessions
in the multimedia session [RFC6051]. in the multimedia session [RFC6051].
skipping to change at page 5, line 31 skipping to change at page 5, line 26
at the receiving end of RTP stream. at the receiving end of RTP stream.
This block needs only be exchanged occasionally, for example sent This block needs only be exchanged occasionally, for example sent
once at the start of RTP session. once at the start of RTP session.
3.1. Metric Block Structure 3.1. Metric Block Structure
The RTP Flows Initial Synchronization Delay Report Block has the The RTP Flows Initial Synchronization Delay Report Block has the
following format: following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=RFISD | Reserved | Block length=2 | | BT=RFISD | Reserved | Block length=2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source | | SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Initial Synchronization Delay | | Initial Synchronization Delay |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.2. Definition of Fields in RTP Flow Initial Synchronization Delay 3.2. Definition of Fields in RTP Flow Initial Synchronization Delay
Metrics Block Metrics Block
Block type (BT): 8 bits Block type (BT): 8 bits
The RTP Flows Initial Synchronization Delay Report Block is The RTP Flows Initial Synchronization Delay Report Block is
identified by the constant <RFISD>. identified by the constant <RFISD>.
[Note to RFC Editor: please replace RFISD with the IANA provided [Note to RFC Editor: please replace RFISD with the IANA provided
skipping to change at page 7, line 30 skipping to change at page 7, line 26
SHOULD be sent in the same compound RTCP packet as the measurement SHOULD be sent in the same compound RTCP packet as the measurement
information block. If the measurement period is not received in the information block. If the measurement period is not received in the
same compound RTCP packet as this Block, this Block MUST be same compound RTCP packet as this Block, this Block MUST be
discarded. discarded.
4.1. Metric Block Structure 4.1. Metric Block Structure
The RTP Flow General Synchronization Offset Report Block has the The RTP Flow General Synchronization Offset Report Block has the
following format: following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=RFSO | I | Reserved | Block length=3 | | BT=RFSO | I | Reserved | Block length=3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of source | | SSRC of source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Synchronization Offset, most significant word | | Synchronization Offset, most significant word |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Synchronization Offset, least significant word | | Synchronization Offset, least significant word |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4.2. Definition of Fields in RTP Flow General Synchronization Offset 4.2. Definition of Fields in RTP Flow General Synchronization Offset
Metrics Block Metrics Block
Block type (BT): 8 bits Block type (BT): 8 bits
The RTP Flow General Synchronization Offset Report Block is The RTP Flow General Synchronization Offset Report Block is
identified by the constant <RFSO>. identified by the constant <RFSO>.
[Note to RFC Editor: please replace RFSO with the IANA provided [Note to RFC Editor: please replace RFSO with the IANA provided
skipping to change at page 8, line 6 skipping to change at page 8, line 4
Block type (BT): 8 bits Block type (BT): 8 bits
The RTP Flow General Synchronization Offset Report Block is The RTP Flow General Synchronization Offset Report Block is
identified by the constant <RFSO>. identified by the constant <RFSO>.
[Note to RFC Editor: please replace RFSO with the IANA provided [Note to RFC Editor: please replace RFSO with the IANA provided
RTCP XR block type for this block.] RTCP XR block type for this block.]
Interval Metric Flag (I): 2 bits Interval Metric Flag (I): 2 bits
This field is used to indicate whether the Burst/Gap Discard This field is used to indicate whether the Burst/Gap Discard
Summary Statistics metrics are Sampled, Interval or Cumulative Summary Statistics metrics are Sampled, Interval or Cumulative
metrics: metrics:
I=10: Interval Duration - the reported value applies to the I=10: Interval Duration - the reported value applies to the
most recent measurement interval duration between successive most recent measurement interval duration between successive
metrics reports. metrics reports.
I=11: Cumulative Duration - the reported value applies to the I=11: Cumulative Duration - the reported value applies to
accumulation period characteristic of cumulative measurements. the accumulation period characteristic of cumulative
I=01: Sampled Value - the reported value is a sampled measurements.
instantaneous value. I=01: Sampled Value - the reported value is a sampled
instantaneous value.
In this document, the value I=00 is the reserved value and MUST In this document, the value I=00 is the reserved value and MUST
NOT be used. NOT be used.
Reserved: 6 bits Reserved: 6 bits
This field is reserved for future definition. In the absence of This field is reserved for future definition. In the absence of
such a definition, the bits in this field MUST be set to zero and such a definition, the bits in this field MUST be set to zero and
MUST be ignored by the receiver. MUST be ignored by the receiver.
skipping to change at page 9, line 4 skipping to change at page 9, line 4
The synchronization offset of the reporting RTP stream relative to The synchronization offset of the reporting RTP stream relative to
the reference stream with the same CNAME. The calculation of the reference stream with the same CNAME. The calculation of
Synchronization Offset is similar to Difference D calculation in Synchronization Offset is similar to Difference D calculation in
the RFC3550. That is to say, if Si is the NTP timestamp from the the RFC3550. That is to say, if Si is the NTP timestamp from the
reporting RTP packet i, and Ri is the time of arrival in NTP reporting RTP packet i, and Ri is the time of arrival in NTP
timestamp units for reporting RTP packet i, Sj is the NTP timestamp units for reporting RTP packet i, Sj is the NTP
timestamp from the reference RTP packet j, and Rj is the time of timestamp from the reference RTP packet j, and Rj is the time of
arrival in NTP timestamp units for reference RTP packet j, then arrival in NTP timestamp units for reference RTP packet j, then
the value of the synchronization offset D may be expressed as the value of the synchronization offset D may be expressed as
D(i,j) = (Rj - Ri) - (Sj - Si) = (Rj - Sj) - (Ri - Si) D(i,j) = (Rj - Ri) - (Sj - Si) = (Rj - Sj) - (Ri - Si)
If in-band delivery of NTP-format timestamps is supported If in-band delivery of NTP-format timestamps is supported
[RFC6051], Si and Sj should be obtained directly from the RTP [RFC6051], Si and Sj should be obtained directly from the RTP
packets where NTP timestamps are available. If not, Si and Sj packets where NTP timestamps are available. If not, Si and Sj
should be calculated from their corresponding RTP timestamps. The should be calculated from their corresponding RTP timestamps. The
value of the synchronization offset is represented using a 64-bit value of the synchronization offset is represented using a 64-bit
signed NTP-format timestamp as defined in [RFC5905], which is 64- signed NTP-format timestamp as defined in [RFC5905], which is
bit signed fixed-point number with the integer part in the first 64-bit signed fixed-point number with the integer part in the
32 bits and the fractional part in the last 32 bits. A positive first 32 bits and the fractional part in the last 32 bits. A
value of the synchronization offset means that the reporting positive value of the synchronization offset means that the
stream leads before the reference stream, while a negative one reporting stream leads before the reference stream, while a
means the reporting stream lags behind the reference stream. The negative one means the reporting stream lags behind the reference
synchronization offset of zero means the stream is the reference stream. The synchronization offset of zero means the stream is
stream. the reference stream.
If the measurement is unavailable, the value of this field with If the measurement is unavailable, the value of this field with
all bits set to 1 MUST be reported. all bits set to 1 MUST be reported.
5. SDP Signaling 5. SDP Signaling
[RFC3611] defines the use of SDP (Session Description Protocol) [RFC3611] defines the use of SDP (Session Description Protocol)
[RFC4566] for signaling the use of XR blocks. XR blocks MAY be used [RFC4566] for signaling the use of XR blocks. XR blocks MAY be used
without prior signaling. without prior signaling.
skipping to change at page 9, line 40 skipping to change at page 9, line 40
Two new parameters are defined for the two report blocks defined in Two new parameters are defined for the two report blocks defined in
this document to be used with Session Description Protocol (SDP) this document to be used with Session Description Protocol (SDP)
[RFC4566] using the Augmented Backus-Naur Form (ABNF) [RFC5234]. [RFC4566] using the Augmented Backus-Naur Form (ABNF) [RFC5234].
They have the following syntax within the "rtcp-xr" attribute They have the following syntax within the "rtcp-xr" attribute
[RFC3611]: [RFC3611]:
xr-format = xr-rfisd-block xr-format = xr-rfisd-block
/ xr-rfso-block / xr-rfso-block
xr-rfisd-block = " rtp-flow-init-syn-delay" xr-rfisd-block = "rtp-flow-init-syn-delay"
xr-rfso-block = " rtp-flow-syn-offset" xr-rfso-block = "rtp-flow-syn-offset"
Refer to Section 5.1 of RFC 3611 [RFC3611] for a detailed description Refer to Section 5.1 of RFC 3611 [RFC3611] for a detailed description
and the full syntax of the "rtcp-xr" attribute. and the full syntax of the "rtcp-xr" attribute.
5.2. Offer/Answer Usage 5.2. Offer/Answer Usage
When SDP is used in offer-answer context, the SDP Offer/Answer usage When SDP is used in offer-answer context, the SDP Offer/Answer usage
defined in [RFC3611] applies. defined in [RFC3611] applies.
6. IANA Considerations 6. IANA Considerations
skipping to change at page 10, line 27 skipping to change at page 10, line 32
Reference: Section 3 Reference: Section 3
Name: RFSO Name: RFSO
Long Name: RTP Flows Synchronization Offset Metrics Block Long Name: RTP Flows Synchronization Offset Metrics Block
Value <RFSO> Value <RFSO>
Reference: Section 4 Reference: Section 4
This document also registers two new SDP [RFC4566] parameters for the This document also registers two new SDP [RFC4566] parameters for the
"rtcp-xr" attribute in the RTCP XR SDP Parameters Registry: "rtcp-xr" attribute in the RTCP XR SDP Parameters Registry:
* "xr-rfisd " * "rtp-flow-init-syn-delay "
* "xr-rfso" * "rtp-flow-syn-offset"
The contact information for the registrations is: The contact information for the registrations is:
Qin Wu Qin Wu
sunseawq@huawei.com sunseawq@huawei.com
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012, China Nanjing, Jiangsu 210012, China
7. Security Considerations 7. Security Considerations
The new RTCP XR report blocks proposed in this document introduces no The new RTCP XR report blocks proposed in this document introduces no
new security considerations beyond those described in [RFC3611]. new security considerations beyond those described in [RFC3611].
8. Acknowledgements 8. Acknowledgements
The authors would like to thank Bill Ver Steeg, David R Oran, Ali The authors would like to thank Bill Ver Steeg, David R Oran, Ali
Begen, Colin Perkins, Roni Even, Kevin Gross, Jing Zhao, Fernando Begen, Colin Perkins, Roni Even, Kevin Gross, Jing Zhao, Fernando
skipping to change at page 11, line 17 skipping to change at page 11, line 25
9.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.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, July 2003. 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, "RTP Control
Protocol Extended Reports (RTCP XR)", RFC 3611, Protocol Extended Reports (RTCP XR)", RFC 3611, November
November 2003. 2003.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, July 2006.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5905] Mills, D., Martin, J., Burbank, J., and W. Kasch, "Network [RFC5905] Mills, D., Martin, J., Burbank, J., and W. Kasch, "Network
Time Protocol Version 4: Protocol and Algorithms Time Protocol Version 4: Protocol and Algorithms
Specification", RFC 5905, June 2010. Specification", RFC 5905, June 2010.
skipping to change at page 13, line 14 skipping to change at page 13, line 31
* Use and applications: See section 1.4 [RFCXXXX]. * Use and applications: See section 1.4 [RFCXXXX].
* Reporting model: See RFC3611. * Reporting model: See RFC3611.
Appendix B. Change Log Appendix B. Change Log
Note to the RFC-Editor: please remove this section prior to Note to the RFC-Editor: please remove this section prior to
publication as an RFC. publication as an RFC.
B.1. draft-ietf-xrblock-rtcp-xr-syncronization-06 B.1. draft-ietf-xrblock-rtcp-xr-syncronization-07
The following are the major changes compared to previous version:
Minor Editorial changes.
B.2. draft-ietf-xrblock-rtcp-xr-syncronization-06
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
Some Editorial changes. Some Editorial changes.
B.2. draft-ietf-xrblock-rtcp-xr-syncronization-05 B.3. draft-ietf-xrblock-rtcp-xr-syncronization-05
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
Editorial changes and typo fixed. Editorial changes and typo fixed.
B.3. draft-ietf-xrblock-rtcp-xr-syncronization-04 B.4. draft-ietf-xrblock-rtcp-xr-syncronization-04
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
Additional text to clarify on how to distinguish report stream Additional text to clarify on how to distinguish report stream
from reference stream. from reference stream.
Other Editorial changes. Other Editorial changes.
B.4. draft-ietf-xrblock-rtcp-xr-syncronization-03 B.5. draft-ietf-xrblock-rtcp-xr-syncronization-03
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
Remove the need to signal the reference source in the Remove the need to signal the reference source in the
synchronisation offset metrics RTCP XR report. synchronisation offset metrics RTCP XR report.
Apply RFC6390 template to metrics in the appendix. Apply RFC6390 template to metrics in the appendix.
Other editorial changes to get inline with other XRBLOCK drafts. Other editorial changes to get inline with other XRBLOCK drafts.
B.5. draft-ietf-xrblock-rtcp-xr-syncronization-02 B.6. draft-ietf-xrblock-rtcp-xr-syncronization-02
The following are the major changes compared to previous version: The following are the major changes compared to previous version:
Editorial change based on comments raised on the list and in the Editorial change based on comments raised on the list and in the
IETF85 meeting IETF85 meeting
Authors' Addresses Authors' Addresses
Hitoshi Asaeda Hitoshi Asaeda
National Institute of Information and Communications Technology National Institute of Information and Communications Technology
4-2-1 Nukui-Kitamachi 4-2-1 Nukui-Kitamachi
Koganei, Tokyo 184-8795 Koganei, Tokyo 184-8795
Japan Japan
Email: asaeda@nict.go.jp Email: asaeda@nict.go.jp
Rachel Huang Qin Wu
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Email: Rachel@huawei.com Email: sunseawq@huawei.com
Rachel Huang
Qin Wu
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Email: sunseawq@huawei.com Email: Rachel@huawei.com
 End of changes. 25 change blocks. 
96 lines changed or deleted 100 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/