draft-ietf-fecframe-rtp-raptor-00.txt   draft-ietf-fecframe-rtp-raptor-01.txt 
FEC Framework Working Group M. Watson FEC Framework Working Group M. Watson
Internet-Draft Qualcomm Inc. Internet-Draft Qualcomm Inc.
Intended status: Standards Track March 4, 2009 Intended status: Standards Track March 6, 2009
Expires: September 5, 2009 Expires: September 7, 2009
RTP Payload Format for Raptor FEC RTP Payload Format for Raptor FEC
draft-ietf-fecframe-rtp-raptor-00 draft-ietf-fecframe-rtp-raptor-01
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. 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), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
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 September 5, 2009. This Internet-Draft will expire on September 7, 2009.
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
skipping to change at page 2, line 31 skipping to change at page 2, line 31
4.2. Payload Header . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Payload Header . . . . . . . . . . . . . . . . . . . . . . 6
4.3. Payload Data . . . . . . . . . . . . . . . . . . . . . . . 6 4.3. Payload Data . . . . . . . . . . . . . . . . . . . . . . . 6
5. Congestion Control Considerations . . . . . . . . . . . . . . 7 5. Congestion Control Considerations . . . . . . . . . . . . . . 7
6. Media Types . . . . . . . . . . . . . . . . . . . . . . . . . 8 6. Media Types . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.1. Registration of the application/raptorfec media type . . . 8 6.1. Registration of the application/raptorfec media type . . . 8
6.1.1. Media Type Definition . . . . . . . . . . . . . . . . 8 6.1.1. Media Type Definition . . . . . . . . . . . . . . . . 8
6.2. Registration of the video/raptorfec media type . . . . . . 9 6.2. Registration of the video/raptorfec media type . . . . . . 9
6.2.1. Media Type Definition . . . . . . . . . . . . . . . . 9 6.2.1. Media Type Definition . . . . . . . . . . . . . . . . 9
6.3. Registration of the audio/raptorfec media type . . . . . . 10 6.3. Registration of the audio/raptorfec media type . . . . . . 10
6.3.1. Media Type Definition . . . . . . . . . . . . . . . . 10 6.3.1. Media Type Definition . . . . . . . . . . . . . . . . 10
6.4. Registration of the text/raptorfec media type . . . . . . 11 6.4. Registration of the text/raptorfec media type . . . . . . 12
6.4.1. Media Type Definition . . . . . . . . . . . . . . . . 11 6.4.1. Media Type Definition . . . . . . . . . . . . . . . . 12
7. Mapping to SDP . . . . . . . . . . . . . . . . . . . . . . . . 13 7. Mapping to SDP . . . . . . . . . . . . . . . . . . . . . . . . 14
8. Offer/Answer considerations . . . . . . . . . . . . . . . . . 14 8. Offer/Answer considerations . . . . . . . . . . . . . . . . . 15
9. Declarative SDP Considerations . . . . . . . . . . . . . . . . 15 9. Declarative SDP Considerations . . . . . . . . . . . . . . . . 16
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
11. Security Considerations . . . . . . . . . . . . . . . . . . . 17 11. Security Considerations . . . . . . . . . . . . . . . . . . . 18
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 19 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
The FEC Framework [I-D.ietf-fecframe-framework] defines a general The FEC Framework [I-D.ietf-fecframe-framework] defines a general
framework for the use of Forward Error Correction in association with framework for the use of Forward Error Correction in association with
arbitrary packet flows, including flows over UDP and RTP. Forward arbitrary packet flows, including flows over UDP and RTP. Forward
Error Corrections operates by generating redundant data packets Error Corrections operates by generating redundant data packets
("repair data") which can be sent independently from the original ("repair data") which can be sent independently from the original
flow. At a receiver the original flow can be reconstructed provided flow. At a receiver the original flow can be reconstructed provided
a sufficient set of redundant data packets and possibly original data a sufficient set of redundant data packets and possibly original data
skipping to change at page 3, line 26 skipping to change at page 3, line 26
The FEC Framework provides for independence between application The FEC Framework provides for independence between application
protocols and FEC codes. The use of a particular FEC code within the protocols and FEC codes. The use of a particular FEC code within the
framework is defined by means of an FEC Scheme which may then be used framework is defined by means of an FEC Scheme which may then be used
with any application protocol compliant to the framework. with any application protocol compliant to the framework.
Repair data flows may be sent directly over a transport protocol such Repair data flows may be sent directly over a transport protocol such
as UDP, or they may be encapsulated within RTP. In the latter case, as UDP, or they may be encapsulated within RTP. In the latter case,
an RTP Payload Format must be defined for each FEC Scheme. an RTP Payload Format must be defined for each FEC Scheme.
This document defines the RTP Payload Format for the Raptor FEC This document defines the RTP Payload Format for the Raptor FEC
Schemes defined in [I-D.watson-fecframe-raptor]. Schemes defined in [I-D.ietf-fecframe-raptor].
2. Conventions, Definitions and Acronyms 2. Conventions, Definitions and Acronyms
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Media Format Background 3. Media Format Background
The Raptor code is an efficient XOR-based block-based fountain code, The Raptor code is an efficient XOR-based block-based fountain code,
meaning that from any group of source packets an arbitrary number of meaning that from any group of source packets (or 'source block') an
repair packets may be generated. The Raptor code has the property arbitrary number of repair packets may be generated. The Raptor code
that the original group of source packets can be recovered with very has the property that the original group of source packets can be
high probability from any set of packets (source and repair) only recovered with very high probability from any set of packets (source
slightly greater in number than the original number of source and repair) only slightly greater in number than the original number
packets. of source packets.
[I-D.watson-fecframe-raptor] defines three FEC Schemes for the use of [I-D.ietf-fecframe-raptor] defines three FEC Schemes for the use of
the Raptor code with arbitary packet flows: the first scheme is fully the Raptor code with arbitary packet flows: the first scheme is fully
applicable to arbitary packet flows. The second scheme is a slightly applicable to arbitary packet flows. The second scheme is a slightly
optimised version of the first scheme which is applicable in optimised version of the first scheme which is applicable in
applications with relatively small block sizes. The third scheme is applications with relatively small block sizes. The third scheme is
a variant of the second scheme which is applicable to a single source a variant of the second scheme which is applicable to a single source
flow which already has some kind of identifiable sequence number. flow which already has some kind of identifiable sequence number.
The presence of a sequence number in the source flow allows for The presence of a sequence number in the source flow allows for
backwards compatible operation (the source flows do not need to be backwards compatible operation (the source flows do not need to be
modified in order to apply FEC). In this case in the language of the modified in order to apply FEC). In this case, in the language of
FEC Framework, there is no explicit FEC Source Payload Id. the FEC Framework, there is no explicit FEC Source Payload Id.
4. Payload Format 4. Payload Format
The RTP Payload contains a FEC Repair Payload as defined in The RTP Payload contains a FEC Repair Payload as defined in
[I-D.watson-fecframe-raptor]. [I-D.ietf-fecframe-raptor].
4.1. RTP Header Usage 4.1. RTP Header Usage
The rules SHALL be followed for the RTP header used with FEC repair The rules SHALL be followed for the RTP header used with FEC repair
packets: packets:
o Marker bit: The marker bit shall be set 1 for the last protection o Marker bit: The marker bit shall be set 1 for the last protection
RTP packet sent for each source block, and otherwise set to 0 RTP packet sent for each source block, and otherwise set to 0
o Timestamp: The timestamp SHALL be set to a time corresponding to o Timestamp: The timestamp SHALL be set to a time corresponding to
skipping to change at page 6, line 30 skipping to change at page 6, line 30
the actual FEC protection process. It may be used for packet the actual FEC protection process. It may be used for packet
arrival timing and jitter calculations. arrival timing and jitter calculations.
4.2. Payload Header 4.2. Payload Header
There is no Payload Header in this Payload Format There is no Payload Header in this Payload Format
4.3. Payload Data 4.3. Payload Data
The RTP Payload contains a FEC Repair Payload as defined in The RTP Payload contains a FEC Repair Payload as defined in
[I-D.ietf-fecframe-framework] and [I-D.watson-fecframe-raptor]. [I-D.ietf-fecframe-framework] and [I-D.ietf-fecframe-raptor].
5. Congestion Control Considerations 5. Congestion Control Considerations
See [I-D.ietf-fecframe-framework]. See [I-D.ietf-fecframe-framework].
6. Media Types 6. Media Types
6.1. Registration of the application/raptorfec media type 6.1. Registration of the application/raptorfec media type
This RTP payload format is identified using the application/raptorfec This RTP payload format is identified using the application/raptorfec
skipping to change at page 8, line 23 skipping to change at page 8, line 23
6.1.1. Media Type Definition 6.1.1. Media Type Definition
Type name: application Type name: application
Subtype name: raptorfec Subtype name: raptorfec
Required parameters: Required parameters:
raptor-scheme-id: The value of this parameter is the FEC Scheme Id raptor-scheme-id: The value of this parameter is the FEC Scheme Id
for the specific Raptor FEC Scheme that will be used as defined in for the specific Raptor FEC Scheme that will be used as defined in
[I-D.watson-fecframe-raptor] [I-D.ietf-fecframe-raptor].
max-sbl: The value of this parameter is the FEC Object
Transmission Information element "Maximum Source Block Length" as
defined in [I-D.ietf-fecframe-raptor] encoded as a decimal
integer.
symbol-size: The value of this parameter is the FEC Object
Transmission Information element "Encoding Symbol Size" as
definedf in [I-D.ietf-fecframe-raptor] encoded as a decimal
integer.
Optional parameters: none Optional parameters: none
Encoding considerations: This media type is framed and binary, see Encoding considerations: This media type is framed and binary, see
section 4.8 in [RFC4288] section 4.8 in [RFC4288]
Security considerations: Please see security consideration in Security considerations: Please see security consideration in
[I-D.ietf-fecframe-framework] [I-D.ietf-fecframe-framework]
Interoperability considerations: Interoperability considerations:
Published specification: [I-D.watson-fecframe-raptor] Published specification: [I-D.ietf-fecframe-raptor]
Applications that use this media type: Applications that use this media type:
Additional information: Additional information:
Magic number(s): <none defined> Magic number(s): <none defined>
File extension(s): <none defined> File extension(s): <none defined>
Macintosh file type code(s): <none defined> Macintosh file type code(s): <none defined>
Person & email address to contact for further information: Mark Person & email address to contact for further information: Mark
Watson, mark@digitalfountain.com Watson, watson@qualcomm.com
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: This media type depends on RTP framing, and Restrictions on usage: This media type depends on RTP framing, and
hence is only defined for transfer via RTP [[RFC3550]]. Transport hence is only defined for transfer via RTP [[RFC3550]]. Transport
within other framing protocols is not defined at this time. within other framing protocols is not defined at this time.
Author: Mark Watson, Digital Fountain Author: Mark Watson, Qualcomm Inc.
Change controller: IETF Audio/Video Transport working group delegated Change controller: IETF Audio/Video Transport working group delegated
from the IESG. from the IESG.
6.2. Registration of the video/raptorfec media type 6.2. Registration of the video/raptorfec media type
This RTP payload format is identified using the video/raptorfec media This RTP payload format is identified using the video/raptorfec media
type which is registered in accordance with [RFC4855] and using the type which is registered in accordance with [RFC4855] and using the
template of [RFC4288]. template of [RFC4288].
6.2.1. Media Type Definition 6.2.1. Media Type Definition
Type name: video Type name: video
Subtype name: raptorfec Subtype name: raptorfec
Required parameters: Required parameters:
raptor-scheme-id: The value of this parameter is the FEC Scheme Id raptor-scheme-id: The value of this parameter is the FEC Scheme Id
for the specific Raptor FEC Scheme that will be used as defined in for the specific Raptor FEC Scheme that will be used as defined in
[I-D.watson-fecframe-raptor] [I-D.ietf-fecframe-raptor]
Optional parameters: none max-sbl: The value of this parameter is the FEC Object
Transmission Information element "Maximum Source Block Length" as
defined in [I-D.ietf-fecframe-raptor] encoded as a decimal
integer.
symbol-size: The value of this parameter is the FEC Object
Transmission Information element "Encoding Symbol Size" as
definedf in [I-D.ietf-fecframe-raptor] encoded as a decimal
integer.
Optional parameters: none
Encoding considerations: This media type is framed and binary, see Encoding considerations: This media type is framed and binary, see
section 4.8 in [RFC4288] section 4.8 in [RFC4288]
Security considerations: Please see security consideration in Security considerations: Please see security consideration in
[I-D.ietf-fecframe-framework] [I-D.ietf-fecframe-framework]
Interoperability considerations: Interoperability considerations:
Published specification: [I-D.watson-fecframe-raptor] Published specification: [I-D.ietf-fecframe-raptor]
Applications that use this media type: Applications that use this media type:
Additional information: Additional information:
Magic number(s): <none defined> Magic number(s): <none defined>
File extension(s): <none defined> File extension(s): <none defined>
Macintosh file type code(s): <none defined> Macintosh file type code(s): <none defined>
skipping to change at page 10, line 4 skipping to change at page 10, line 23
Applications that use this media type: Applications that use this media type:
Additional information: Additional information:
Magic number(s): <none defined> Magic number(s): <none defined>
File extension(s): <none defined> File extension(s): <none defined>
Macintosh file type code(s): <none defined> Macintosh file type code(s): <none defined>
Person & email address to contact for further information: Mark Person & email address to contact for further information: Mark
Watson, mark@digitalfountain.com Watson, watson@qualcomm.com
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: This media type depends on RTP framing, and Restrictions on usage: This media type depends on RTP framing, and
hence is only defined for transfer via RTP [[RFC3550]]. Transport hence is only defined for transfer via RTP [[RFC3550]]. Transport
within other framing protocols is not defined at this time. within other framing protocols is not defined at this time.
Author: Mark Watson, Digital Fountain Author: Mark Watson, Qualcomm Inc.
Change controller: IETF Audio/Video Transport working group delegated Change controller: IETF Audio/Video Transport working group delegated
from the IESG. from the IESG.
6.3. Registration of the audio/raptorfec media type 6.3. Registration of the audio/raptorfec media type
This RTP payload format is identified using the audio/raptorfec media This RTP payload format is identified using the audio/raptorfec media
type which is registered in accordance with [RFC4855] and using the type which is registered in accordance with [RFC4855] and using the
template of [RFC4288]. template of [RFC4288].
6.3.1. Media Type Definition 6.3.1. Media Type Definition
Type name: audio Type name: audio
Subtype name: raptorfec Subtype name: raptorfec
Required parameters: Required parameters:
raptor-scheme-id: The value of this parameter is the FEC Scheme Id raptor-scheme-id: The value of this parameter is the FEC Scheme Id
for the specific Raptor FEC Scheme that will be used as defined in for the specific Raptor FEC Scheme that will be used as defined in
[I-D.watson-fecframe-raptor] [I-D.ietf-fecframe-raptor]
max-sbl: The value of this parameter is the FEC Object
Transmission Information element "Maximum Source Block Length" as
defined in [I-D.ietf-fecframe-raptor] encoded as a decimal
integer.
symbol-size: The value of this parameter is the FEC Object
Transmission Information element "Encoding Symbol Size" as
definedf in [I-D.ietf-fecframe-raptor] encoded as a decimal
integer.
Optional parameters: none Optional parameters: none
Encoding considerations: This media type is framed and binary, see Encoding considerations: This media type is framed and binary, see
section 4.8 in [RFC4288] section 4.8 in [RFC4288]
Security considerations: Please see security consideration in Security considerations: Please see security consideration in
[I-D.ietf-fecframe-framework] [I-D.ietf-fecframe-framework]
Interoperability considerations: Interoperability considerations:
Published specification: [I-D.watson-fecframe-raptor] Published specification: [I-D.ietf-fecframe-raptor]
Applications that use this media type: Applications that use this media type:
Additional information: Additional information:
Magic number(s): <none defined> Magic number(s): <none defined>
File extension(s): <none defined> File extension(s): <none defined>
Macintosh file type code(s): <none defined> Macintosh file type code(s): <none defined>
Person & email address to contact for further information: Mark Person & email address to contact for further information: Mark
Watson, mark@digitalfountain.com Watson, watson@qualcomm.com
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: This media type depends on RTP framing, and Restrictions on usage: This media type depends on RTP framing, and
hence is only defined for transfer via RTP [[RFC3550]]. Transport hence is only defined for transfer via RTP [[RFC3550]]. Transport
within other framing protocols is not defined at this time. within other framing protocols is not defined at this time.
Author: Mark Watson, Digital Fountain Author: Mark Watson, Qualcomm Inc.
Change controller: IETF Audio/Video Transport working group delegated Change controller: IETF Audio/Video Transport working group delegated
from the IESG. from the IESG.
6.4. Registration of the text/raptorfec media type 6.4. Registration of the text/raptorfec media type
This RTP payload format is identified using the text/raptorfec media This RTP payload format is identified using the text/raptorfec media
type which is registered in accordance with [RFC4855] and using the type which is registered in accordance with [RFC4855] and using the
template of [RFC4288]. template of [RFC4288].
6.4.1. Media Type Definition 6.4.1. Media Type Definition
Type name: text Type name: text
Subtype name: raptorfec Subtype name: raptorfec
Required parameters: Required parameters:
raptor-scheme-id: The value of this parameter is the FEC Scheme Id raptor-scheme-id: The value of this parameter is the FEC Scheme Id
for the specific Raptor FEC Scheme that will be used as defined in for the specific Raptor FEC Scheme that will be used as defined in
[I-D.watson-fecframe-raptor] [I-D.ietf-fecframe-raptor]
max-sbl: The value of this parameter is the FEC Object
Transmission Information element "Maximum Source Block Length" as
defined in [I-D.ietf-fecframe-raptor] encoded as a decimal
integer.
symbol-size: The value of this parameter is the FEC Object
Transmission Information element "Encoding Symbol Size" as
definedf in [I-D.ietf-fecframe-raptor] encoded as a decimal
integer.
Optional parameters: none Optional parameters: none
Encoding considerations: This media type is framed and binary, see Encoding considerations: This media type is framed and binary, see
section 4.8 in [RFC4288] section 4.8 in [RFC4288]
Security considerations: Please see security consideration in Security considerations: Please see security consideration in
[I-D.ietf-fecframe-framework] [I-D.ietf-fecframe-framework]
Interoperability considerations: Interoperability considerations:
Published specification: [I-D.watson-fecframe-raptor] Published specification: [I-D.ietf-fecframe-raptor]
Applications that use this media type: Applications that use this media type:
Additional information: Additional information:
Magic number(s): <none defined> Magic number(s): <none defined>
File extension(s): <none defined> File extension(s): <none defined>
Macintosh file type code(s): <none defined> Macintosh file type code(s): <none defined>
Person & email address to contact for further information: Mark Person & email address to contact for further information: Mark
Watson, mark@digitalfountain.com Watson, watson@qualcomm.com
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: This media type depends on RTP framing, and Restrictions on usage: This media type depends on RTP framing, and
hence is only defined for transfer via RTP [[RFC3550]]. Transport hence is only defined for transfer via RTP [[RFC3550]]. Transport
within other framing protocols is not defined at this time. within other framing protocols is not defined at this time.
Author: Mark Watson, Digital Fountain Author: Mark Watson, Qualcomm Inc.
Change controller: IETF Audio/Video Transport working group delegated Change controller: IETF Audio/Video Transport working group delegated
from the IESG. from the IESG.
7. Mapping to SDP 7. Mapping to SDP
The mapping of the above defined payload format media type and its The mapping of the above defined payload format media type and its
parameters SHALL be done according to Section 3 of [RFC4855] parameters SHALL be done according to Section 3 of [RFC4855]
When the RTP Payload Formats defined in this document are used, the
Media Type Parameters defined above SHALL be used to specify the FEC
Object Transmission Information in preference to the SDP attributes
specified in [I-D.ietf-fecframe-sdp-elements]
8. Offer/Answer considerations 8. Offer/Answer considerations
None. None.
9. Declarative SDP Considerations 9. Declarative SDP Considerations
None. None.
10. IANA Considerations 10. IANA Considerations
skipping to change at page 18, line 25 skipping to change at page 19, line 25
Registration Procedures", BCP 13, RFC 4288, December 2005. Registration Procedures", BCP 13, RFC 4288, December 2005.
[RFC4855] Casner, S., "Media Type Registration of RTP Payload [RFC4855] Casner, S., "Media Type Registration of RTP Payload
Formats", RFC 4855, February 2007. Formats", RFC 4855, February 2007.
[I-D.ietf-fecframe-framework] [I-D.ietf-fecframe-framework]
Watson, M., "Forward Error Correction (FEC) Framework", Watson, M., "Forward Error Correction (FEC) Framework",
draft-ietf-fecframe-framework-03 (work in progress), draft-ietf-fecframe-framework-03 (work in progress),
October 2008. October 2008.
[I-D.watson-fecframe-raptor] [I-D.ietf-fecframe-sdp-elements]
Begen, A., "SDP Elements for FEC Framework",
draft-ietf-fecframe-sdp-elements-02 (work in progress),
November 2008.
[I-D.ietf-fecframe-raptor]
Watson, M., "Raptor FEC Schemes for FECFRAME", Watson, M., "Raptor FEC Schemes for FECFRAME",
draft-watson-fecframe-raptor-00 (work in progress), draft-ietf-fecframe-raptor-00 (work in progress),
July 2008. October 2008.
Author's Address Author's Address
Mark Watson Mark Watson
Qualcomm Inc. Qualcomm Inc.
3165 Kifer Rd. 3165 Kifer Rd.
Santa Clara, CA 95051 Santa Clara, CA 95051
U.S.A. U.S.A.
Email: watson@qualcomm.com Email: watson@qualcomm.com
 End of changes. 34 change blocks. 
47 lines changed or deleted 95 lines changed or added

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