draft-ietf-avt-rtp-evrc-wb-08.txt   draft-ietf-avt-rtp-evrc-wb-09.txt 
Network Working Group H. Desineni Network Working Group H. Desineni
Internet-Draft Qualcomm Internet-Draft Qualcomm
Updates: 4788 (if approved) Q. Xie Updates: 4788 (if approved) Q. Xie
Intended status: Standards Track Motorola Intended status: Standards Track Motorola
Expires: May 18, 2008 November 15, 2007 Expires: June 5, 2008 December 3, 2007
RTP payload format for Enhanced Variable Rate Wideband Codec (EVRC-WB) RTP payload format for Enhanced Variable Rate Wideband Codec (EVRC-WB)
and media subtype updates for EVRC-B codec and media subtype updates for EVRC-B codec
draft-ietf-avt-rtp-evrc-wb-08.txt draft-ietf-avt-rtp-evrc-wb-09.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 36 skipping to change at page 1, line 36
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 May 18, 2008. This Internet-Draft will expire on June 5, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document specifies real-time transport protocol (RTP) payload This document specifies real-time transport protocol (RTP) payload
formats to be used for the Enhanced Variable Rate Wideband Codec formats to be used for the Enhanced Variable Rate Wideband Codec
(EVRC-WB) and updates the media type registrations for EVRC-B codec. (EVRC-WB) and updates the media type registrations for EVRC-B codec.
skipping to change at page 2, line 30 skipping to change at page 2, line 30
5. RTP header usage . . . . . . . . . . . . . . . . . . . . . . . 7 5. RTP header usage . . . . . . . . . . . . . . . . . . . . . . . 7
6. Payload format . . . . . . . . . . . . . . . . . . . . . . . . 8 6. Payload format . . . . . . . . . . . . . . . . . . . . . . . . 8
7. Congestion Control Considerations . . . . . . . . . . . . . . 9 7. Congestion Control Considerations . . . . . . . . . . . . . . 9
8. Storage format for the EVRC-WB Codec . . . . . . . . . . . . . 10 8. Storage format for the EVRC-WB Codec . . . . . . . . . . . . . 10
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
9.1. Media Type Registrations . . . . . . . . . . . . . . . . . 11 9.1. Media Type Registrations . . . . . . . . . . . . . . . . . 11
9.1.1. Registration of Media Type audio/EVRCWB . . . . . . . 11 9.1.1. Registration of Media Type audio/EVRCWB . . . . . . . 11
9.1.2. Registration of Media Type audio/EVRCWB0 . . . . . . . 13 9.1.2. Registration of Media Type audio/EVRCWB0 . . . . . . . 13
9.1.3. Registration of Media Type audio/EVRCWB1 . . . . . . . 15 9.1.3. Registration of Media Type audio/EVRCWB1 . . . . . . . 15
9.1.4. Updated Registration of Media Type audio/EVRCB . . . . 17 9.1.4. Updated Registration of Media Type audio/EVRCB . . . . 17
9.1.5. Updated Registration of Media Type audio/EVRCB0 . . . 18 9.1.5. Updated Registration of Media Type audio/EVRCB0 . . . 19
10. SDP mode attributes for EVRC-WB and EVRC-B . . . . . . . . . . 21 10. SDP mode attributes for EVRC-WB and EVRC-B . . . . . . . . . . 21
11. EVRC-B Interoperability with legacy implementations (RFC 11. EVRC-B Interoperability with legacy implementations (RFC
4788) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 4788) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
12. Mapping EVRC-WB media type parameters into SDP . . . . . . . . 23 12. Mapping EVRC-WB media type parameters into SDP . . . . . . . . 23
13. Mapping EVRC-B media type parameters into SDP . . . . . . . . 24 13. Mapping EVRC-B media type parameters into SDP . . . . . . . . 24
14. Offer-Answer Model Considerations for EVRC-WB . . . . . . . . 25 14. Offer-Answer Model Considerations for EVRC-WB . . . . . . . . 25
15. Offer-Answer Model Considerations for EVRC-B . . . . . . . . . 27 15. Offer-Answer Model Considerations for EVRC-B . . . . . . . . . 27
16. Declarative SDP Considerations . . . . . . . . . . . . . . . . 28 16. Declarative SDP Considerations . . . . . . . . . . . . . . . . 28
17. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 17. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
18. Security Considerations . . . . . . . . . . . . . . . . . . . 33 18. Security Considerations . . . . . . . . . . . . . . . . . . . 33
skipping to change at page 8, line 15 skipping to change at page 8, line 15
6. Payload format 6. Payload format
Three RTP packet formats are supported for the EVRC-WB codec - the Three RTP packet formats are supported for the EVRC-WB codec - the
interleaved/bundled packet format, the header-free packet format and interleaved/bundled packet format, the header-free packet format and
the compact bundled packet format. For all these formats, the the compact bundled packet format. For all these formats, the
operational details and capabilities, such as ToC, interleaving, DTX, operational details and capabilities, such as ToC, interleaving, DTX,
and bundling, of EVRC-WB are exactly the same as those of EVRC-B, as and bundling, of EVRC-WB are exactly the same as those of EVRC-B, as
defined in [3], except that the mode change request field in the ToC defined in [3], except that the mode change request field in the ToC
MUST be interpreted according to the definition of the RATE_REDUC MUST be interpreted according to the definition of the RATE_REDUC
parameter as defined in EVRC-WB [5]. The media type audio/EVRCWB parameter as defined in EVRC-WB [5]. The media type audio/EVRCWB
maps to the interleaved/bundled packet format, audio/EVWB0 maps to maps to the interleaved/bundled packet format, audio/EVRCWB0 maps to
the header-free packet format and audio/EVRCWB1 maps to the compact the header-free packet format and audio/EVRCWB1 maps to the compact
bundled packet format. bundled packet format.
7. Congestion Control Considerations 7. Congestion Control Considerations
Congestion control for RTP SHALL be used in accordance with RFC 3550 Congestion control for RTP SHALL be used in accordance with RFC 3550
[6], and with any applicable RTP profile; e.g., RFC 3551 [11]. [6], and with any applicable RTP profile; e.g., RFC 3551 [11].
Due to the header overhead, the number of frames encapsulated in each Due to the header overhead, the number of frames encapsulated in each
RTP packet influences the overall bandwidth of the RTP stream. RTP packet influences the overall bandwidth of the RTP stream.
skipping to change at page 11, line 31 skipping to change at page 11, line 31
9.1.1. Registration of Media Type audio/EVRCWB 9.1.1. Registration of Media Type audio/EVRCWB
Type name: audio Type name: audio
Subtype names: EVRCWB Subtype names: EVRCWB
Required parameters: none Required parameters: none
Optional parameters: Optional parameters:
These parameters apply to RTP transfer only.
mode-set-recv: A subset of EVRC-WB modes. Possible values are a mode-set-recv: A subset of EVRC-WB modes. Possible values are a
comma separated list of modes from the set {0,4,7} (see Table comma separated list of modes from the set {0,4,7} (see Table
2.5.1.2-1 in 3GPP2 C.S0014-C). A decoder can use this attribute to 2.5.1.2-1 in 3GPP2 C.S0014-C). A decoder can use this attribute to
inform an encoder of its preference to operate in a specified subset inform an encoder of its preference to operate in a specified subset
of modes. Absence of this parameter signals the mode set {0,4,7}. of modes. Absence of this parameter signals the mode set {0,4,7}.
sendmode: A mode of the EVRC-WB codec. An encoder can use this to sendmode: A mode of the EVRC-WB codec. An encoder can use this to
signal its current mode of operation. Possible values are 0,4,7 (see signal its current mode of operation. Possible values are 0,4,7 (see
Table 2.5.1.2-1 in 3GPP2 C.S0014-C). Absence of this parameter Table 2.5.1.2-1 in 3GPP2 C.S0014-C). Absence of this parameter
signals mode 0. signals mode 0.
skipping to change at page 12, line 38 skipping to change at page 12, line 40
3GPP2 specifications are publicly accessible at http://www.3gpp2.org 3GPP2 specifications are publicly accessible at http://www.3gpp2.org
Applications that use this media type: Applications that use this media type:
It is expected that many VoIP applications (as well as mobile It is expected that many VoIP applications (as well as mobile
applications) will use this type. applications) will use this type.
Additional information: Additional information:
The following information applies for the storage format only. The following applies to stored-file transfer methods:
Magic number: #!EVCWB\n (see Section 8 of RFC XXXX) Magic number: #!EVCWB\n (see Section 8 of RFC XXXX)
File extensions: evw, EVW File extensions: evw, EVW
Macintosh file type code: none Macintosh file type code: none
Object identifier or OID: none Object identifier or OID: none
EVRC-WB speech frames may also be stored in the file format "3g2" EVRC-WB speech frames may also be stored in the file format "3g2"
skipping to change at page 13, line 11 skipping to change at page 13, line 13
"audio/3gpp2" or "video/3gpp2" registered by RFC 4393. "audio/3gpp2" or "video/3gpp2" registered by RFC 4393.
Person & email address to contact for further information: Person & email address to contact for further information:
Harikishan Desineni <hd@qualcomm.com> Harikishan Desineni <hd@qualcomm.com>
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: Restrictions on usage:
This basic form of this media type depends on RTP framing, and hence When this media type is used in the context of transfer over RTP, the
is only defined for transfer via RTP (RFC 3550). For storage and/or RTP payload format specified in Section 4.1 of RFC 3558 SHALL be
transfer within other protocols, the storage format according to the used. In all other contexts, the file format defined in Section 8 of
Additional Information clause above must be used. RFC XXXX SHALL be used.
Author: Author:
Harikishan Desineni Harikishan Desineni
Change controller: Change controller:
IETF Audio/Video Transport working group delegated from the IESG. IETF Audio/Video Transport working group delegated from the IESG.
9.1.2. Registration of Media Type audio/EVRCWB0 9.1.2. Registration of Media Type audio/EVRCWB0
Type name: audio Type name: audio
Subtype names: EVRCWB0 Subtype names: EVRCWB0
Required parameters: Required parameters:
Optional parameters: Optional parameters:
These parameters apply to RTP transfer only.
mode-set-recv: A subset of EVRC-WB modes. Possible values are a mode-set-recv: A subset of EVRC-WB modes. Possible values are a
comma separated list of modes from the set {0,4,7} (see Table comma separated list of modes from the set {0,4,7} (see Table
2.5.1.2-1 in 3GPP2 C.S0014-C). A decoder can use this attribute to 2.5.1.2-1 in 3GPP2 C.S0014-C). A decoder can use this attribute to
inform an encoder of its preference to operate in a specified subset inform an encoder of its preference to operate in a specified subset
of modes. Absence of this parameter signals the mode set {0,4,7}. of modes. Absence of this parameter signals the mode set {0,4,7}.
sendmode: A mode of the EVRC-WB codec. An encoder can use this to sendmode: A mode of the EVRC-WB codec. An encoder can use this to
signal its current mode of operation. Possible values are 0,4,7 (see signal its current mode of operation. Possible values are 0,4,7 (see
Table 2.5.1.2-1 in 3GPP2 C.S0014-C). Absence of this parameter Table 2.5.1.2-1 in 3GPP2 C.S0014-C). Absence of this parameter
signals mode 0. signals mode 0.
skipping to change at page 14, line 42 skipping to change at page 14, line 46
Additional information: None Additional information: None
Person & email address to contact for further information: Person & email address to contact for further information:
Harikishan Desineni <hd@qualcomm.com> Harikishan Desineni <hd@qualcomm.com>
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: Restrictions on usage:
This basic form of this media type depends on RTP framing, and hence This media type depends on RTP framing, and hence is only defined for
is only defined for transfer via RTP (RFC 3550). Transfer within transfer via RTP [RFC3550], the RTP payload format specified in
other framing protocols is not defined at this time. Section 4.2 of RFC 3558 SHALL be used. This media type SHALL NOT be
used for storage or file transfer using the file format defined in
Section 8 of RFC XXXX, instead audio/EVRCWB SHALL be used.
Author: Author:
Harikishan Desineni Harikishan Desineni
Change controller: Change controller:
IETF Audio/Video Transport working group delegated from the IESG. IETF Audio/Video Transport working group delegated from the IESG.
9.1.3. Registration of Media Type audio/EVRCWB1 9.1.3. Registration of Media Type audio/EVRCWB1
Type name: audio Type name: audio
Subtype names: EVRCWB1 Subtype names: EVRCWB1
Required parameters: Required parameters:
Optional parameters: Optional parameters:
These parameters apply to RTP transfer only.
mode-set-recv: A subset of EVRC-WB modes. Possible values are a mode-set-recv: A subset of EVRC-WB modes. Possible values are a
comma separated list of modes from the set {0,4,7} (see Table comma separated list of modes from the set {0,4,7} (see Table
2.5.1.2-1 in 3GPP2 C.S0014-C). A decoder can use this attribute to 2.5.1.2-1 in 3GPP2 C.S0014-C). A decoder can use this attribute to
inform an encoder of its preference to operate in a specified subset inform an encoder of its preference to operate in a specified subset
of modes. A value of 0 signals the support for wideband fixed rate of modes. A value of 0 signals the support for wideband fixed rate
(full or half rate, depending on the value of 'fixedrate' parameter). (full or half rate, depending on the value of 'fixedrate' parameter).
A value of 4 signals narroband fixed full rate. A value of 7 signals A value of 4 signals narroband fixed full rate. A value of 7 signals
narrowband fixed half rate. Absence of this parameter signals mode narrowband fixed half rate. Absence of this parameter signals mode
0. 0.
sendmode: A mode of the EVRC-WB codec. An encoder can use this to sendmode: A mode of the EVRC-WB codec. An encoder can use this to
signal its current mode of operation. Possible values are 0,4,7 (see signal its current mode of operation. Possible values are 0,4,7 (see
Table 2.5.1.2-1 in 3GPP2 C.S0014-C). 'sendmode' with value 0 signals Table 2.5.1.2-1 in 3GPP2 C.S0014-C). 'sendmode' with value 0 signals
wideband fixed rate operation (full or half rate, depending on the wideband fixed rate operation (full or half rate, depending on the
value of the 'fixedrate' parameter). 'sendmode' with value 4 signals value of the 'fixedrate' parameter). 'sendmode' with value 4 signals
narrowband fixed full rate operation. 'sendmode' with value 7 signals narrowband fixed full rate operation. 'sendmode' with value 7 signals
narrowband fixed half rate operation. The 'fixedrate' parameter MUST narrowband fixed half rate operation. The 'fixedrate' parameter MUST
not be present when the 'sendmode' value is 4 or 7. Absence of this NOT be present when the 'sendmode' value is 4 or 7. Absence of this
parameter signals mode 0. parameter signals mode 0.
ptime: see RFC 4566. ptime: see RFC 4566.
maxptime: see RFC 4566. maxptime: see RFC 4566.
fixedrate: Indicates the EVRC-WB rate of the session while in single fixedrate: Indicates the EVRC-WB rate of the session while in single
rate operation. Valid values include: 0.5 and 1, where a value of rate operation. Valid values include: 0.5 and 1, where a value of
0.5 indicates the 1/2 rate while a value of 1 indicates the full 0.5 indicates the 1/2 rate while a value of 1 indicates the full
rate. If this parameter is not present, 1/2 rate is assumed. rate. If this parameter is not present, 1/2 rate is assumed.
skipping to change at page 16, line 38 skipping to change at page 16, line 46
Additional information: None Additional information: None
Person & email address to contact for further information: Person & email address to contact for further information:
Harikishan Desineni <hd@qualcomm.com> Harikishan Desineni <hd@qualcomm.com>
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: Restrictions on usage:
This basic form of this media type depends on RTP framing, and hence This media type depends on RTP framing, and hence is only defined for
is only defined for transfer via RTP (RFC 3550). Transfer within transfer via RTP [RFC3550], the RTP payload format specified in
other framing protocols is not defined at this time. Section 4 of RFC 4788 SHALL be used. This media type SHALL NOT be
used for storage or file transfer using the file format defined in
Section 8 of RFC XXXX, instead audio/EVRCWB SHALL be used.
Author: Author:
Harikishan Desineni Harikishan Desineni
Change controller: Change controller:
IETF Audio/Video Transport working group delegated from the IESG. IETF Audio/Video Transport working group delegated from the IESG.
9.1.4. Updated Registration of Media Type audio/EVRCB 9.1.4. Updated Registration of Media Type audio/EVRCB
Type name: audio Type name: audio
Subtype names: EVRCB Subtype names: EVRCB
Required parameters: none Required parameters: none
Optional parameters: Optional parameters:
These parameters apply to RTP transfer only.
recvmode: A mode of the EVRC-B codec. A decoder can use this recvmode: A mode of the EVRC-B codec. A decoder can use this
attribute to inform an encoder of its preference to operate in a attribute to inform an encoder of its preference to operate in a
specified mode. Possible values are 0..7 (see the encoder operating specified mode. Possible values are 0..7 (see the encoder operating
point column in Table 2-6 of 3GPP2 C.S0014-B). point column in Table 2-6 of 3GPP2 C.S0014-B).
sendmode: A mode of the EVRC-B codec. An encoder can use this to sendmode: A mode of the EVRC-B codec. An encoder can use this to
signal its current mode of operation. Possible values are 0..7 (see signal its current mode of operation. Possible values are 0..7 (see
encoder operating point column in Table 2-6 of 3GPP2 C.S0014-B). encoder operating point column in Table 2-6 of 3GPP2 C.S0014-B).
ptime: see RFC 4566. ptime: see RFC 4566.
skipping to change at page 18, line 33 skipping to change at page 18, line 41
Object identifier or OID: none Object identifier or OID: none
Person & email address to contact for further information: Person & email address to contact for further information:
Harikishan Desineni <hd@qualcomm.com> Harikishan Desineni <hd@qualcomm.com>
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: Restrictions on usage:
This basic form of this media type depends on RTP framing, and hence When this media type is used in the context of transfer over RTP, the
is only defined for transfer via RTP (RFC 3550). For storage and/or RTP payload format specified in Section 4.1 of RFC 3558 SHALL be
transfer within other protocols, the storage format according to the used. In all other contexts, the file format defined in Section 5 of
Additional Information clause above must be used. RFC 4788 SHALL be used.
Author: Author:
Qiaobing Xie / Harikishan Desineni Qiaobing Xie / Harikishan Desineni
Change controller: Change controller:
IETF Audio/Video Transport working group delegated from the IESG. IETF Audio/Video Transport working group delegated from the IESG.
9.1.5. Updated Registration of Media Type audio/EVRCB0 9.1.5. Updated Registration of Media Type audio/EVRCB0
skipping to change at page 19, line 4 skipping to change at page 19, line 14
IETF Audio/Video Transport working group delegated from the IESG. IETF Audio/Video Transport working group delegated from the IESG.
9.1.5. Updated Registration of Media Type audio/EVRCB0 9.1.5. Updated Registration of Media Type audio/EVRCB0
Type name: audio Type name: audio
Subtype names: EVRCB0 Subtype names: EVRCB0
Required parameters: none Required parameters: none
Optional parameters: Optional parameters:
These parameters apply to RTP transfer only.
recvmode: A mode of the EVRC-B codec. A decoder can use this recvmode: A mode of the EVRC-B codec. A decoder can use this
attribute to inform an encoder of its preference to operate in a attribute to inform an encoder of its preference to operate in a
specified mode. Possible values are 0..7 (see the encoder operating specified mode. Possible values are 0..7 (see the encoder operating
point column in Table 2-6 of 3GPP2 C.S0014-B). point column in Table 2-6 of 3GPP2 C.S0014-B).
sendmode: A mode of the EVRC-B codec. An encoder can use this to sendmode: A mode of the EVRC-B codec. An encoder can use this to
signal its current mode of operation. Possible values are 0..7 (see signal its current mode of operation. Possible values are 0..7 (see
the encoder operating point column in Table 2-6 of 3GPP2 C.S0014-B). the encoder operating point column in Table 2-6 of 3GPP2 C.S0014-B).
silencesupp: see Section 6.1 of RFC 4788 for a definition. If this silencesupp: see Section 6.1 of RFC 4788 for a definition. If this
skipping to change at page 19, line 45 skipping to change at page 20, line 10
The EVRC-B vocoder is specified in 3GPP2 C.S0014-B. The transfer The EVRC-B vocoder is specified in 3GPP2 C.S0014-B. The transfer
method with the Header-Free packet format via RTP is specified in RFC method with the Header-Free packet format via RTP is specified in RFC
3558, RFC 4788 and RFC XXXX. 3558, RFC 4788 and RFC XXXX.
Applications that use this media type: Applications that use this media type:
It is expected that many VoIP applications (as well as mobile It is expected that many VoIP applications (as well as mobile
applications) will use this type. applications) will use this type.
Additional information: none Additional information: None
Person & email address to contact for further information: Person & email address to contact for further information:
Harikishan Desineni <hd@qualcomm.com> Harikishan Desineni <hd@qualcomm.com>
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: Restrictions on usage:
When this media type is used in the context of transfer over RTP, the
RTP payload format specified in Section 4.2 of RFC 3558 SHALL be
used.
This media type depends on RTP framing, and hence is only defined for This media type depends on RTP framing, and hence is only defined for
transfer via RTP (RFC 3550). Transfer within other framing protocols transfer via RTP [RFC3550], the RTP payload format specified in
is not defined at this time. Section 4.2 of RFC 3558 SHALL be used. This media type SHALL NOT be
used for storage or file transfer using the file format defined in
Section 5 of RFC 4788, instead audio/EVRCB SHALL be used.
Author: Author:
Qiaobing Xie / Harikishan Desineni Qiaobing Xie / Harikishan Desineni
Change controller: Change controller:
IETF Audio/Video Transport working group delegated from the IESG. IETF Audio/Video Transport working group delegated from the IESG.
10. SDP mode attributes for EVRC-WB and EVRC-B 10. SDP mode attributes for EVRC-WB and EVRC-B
 End of changes. 21 change blocks. 
24 lines changed or deleted 46 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/