draft-ietf-avt-rtp-ipmr-06.txt   draft-ietf-avt-rtp-ipmr-07.txt 
Audio/Video Transport Working Group Y. Morzeev Audio/Video Transport Working Group S. Ikonin
Internet Draft SPIRIT DSP Internet Draft SPIRIT DSP
Intended status: Informational September 2, 2009 Intended status: Informational September 8, 2009
RTP Payload Format for IP-MR Speech Codec draft-ietf-avt-rtp-ipmr-06.txt RTP Payload Format for IP-MR Speech Codec draft-ietf-avt-rtp-ipmr-07.txt
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.
Copyright (c) 2009 IETF Trust and the persons identified as the document Copyright (c) 2009 IETF Trust and the persons identified as the document
authors. All rights reserved. authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions This document is subject to BCP 78 and the IETF Trust's Legal Provisions
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 material time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as "work in progress." 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/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
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 February 18, 2010. This Internet-Draft will expire on March 8, 2010.
Abstract Abstract
This document specifies the payload format for packetization of SPIRIT This document specifies the payload format for packetization of SPIRIT
IP-MR encoded speech signals into the Real-time Transport Protocol IP-MR encoded speech signals into the Real-time Transport Protocol
(RTP). The payload format supports transmission of multiple frames per (RTP). The payload format supports transmission of multiple frames per
payload and introduced redundancy for robustness against packet loss. payload and introduced redundancy for robustness against packet loss.
Table of Contents Table of Contents
skipping to change at page 6, line 34 skipping to change at page 6, line 34
using the table for CR. Values in the range 0-5 indicate bitrates using the table for CR. Values in the range 0-5 indicate bitrates
for core layer, same as for packet SHOULD be discarded. The base for core layer, same as for packet SHOULD be discarded. The base
rate is the lowest rate for scalability, so speech payload can rate is the lowest rate for scalability, so speech payload can
be scaled down not lower than BR value. If a received packet has be scaled down not lower than BR value. If a received packet has
BR > CR then during decoding it will be assumed that BR = CR. BR > CR then during decoding it will be assumed that BR = CR.
o D (1 bit): indicates if the DTX mode is allowed or not. This o D (1 bit): indicates if the DTX mode is allowed or not. This
parameter is only required for a correct payload parsing. The parameter is only required for a correct payload parsing. The
particular decoder implementation must always include DTX mode particular decoder implementation must always include DTX mode
support and update internal states properly. It is prohibited support and update internal states properly. It is prohibited
to decoder to rely this parameter is constantly off during session. to decoder to rely this parameter is constantly off during
session.
o A (1 bit): byte-aligned payload. If A=1 then all speech frames o A (1 bit): byte-aligned payload. If A=1 then all speech frames
MUST be byte-aligned. This mode speeds up speech data access. MUST be byte-aligned. This mode speeds up speech data access.
The A=0 value specifies bandwidth-efficient mode with no byte The A=0 value specifies bandwidth-efficient mode with no byte
alignment(including end of header). alignment(including end of header).
o GR (2 bits): number of frames in packet (grouping size). Actual o GR (2 bits): number of frames in packet (grouping size). Actual
grouping size is GR + 1, thus maximum grouping supported is 4. grouping size is GR + 1, thus maximum grouping supported is 4.
o R (1 bit): redundancy presence bit. If R=1 then the packet o R (1 bit): redundancy presence bit. If R=1 then the packet
skipping to change at page 12, line 20 skipping to change at page 12, line 20
Interoperability considerations: none Interoperability considerations: none
Published specification: RFC XXXX Published specification: RFC XXXX
Applications that use this media type: Real-time audio applications like Applications that use this media type: Real-time audio applications like
voice over IP and teleconference, and multi-media streaming. voice over IP and teleconference, and multi-media streaming.
Additional information: none Additional information: none
Person & email address to contact for further information: Person & email address to contact for further information:
Yuri Morzeev Yury Morzeev
morzeev@spiritdsp.com morzeev@spiritdsp.com
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: This media type depends on RTP framing, and hence Restrictions on usage: This media type depends on RTP framing, and hence
is only defined for transfer via RTP [RFC 3550]. is only defined for transfer via RTP [RFC 3550].
Authors: Authors:
Yury Morzeev <morzeev@spiritdsp.com> Sergey Ikonin <info@spiritdsp.com>
Change controller: IETF Audio/Video Transport working group delegated Change controller: IETF Audio/Video Transport working group delegated
from the IESG. from the IESG.
5.2. Mapping Media Type Parameters into SDP 5.2. Mapping Media Type Parameters into SDP
The information carried in the media type specification has a specific The information carried in the media type specification has a specific
mapping to fields in the Session Description Protocol (SDP) [RFC 4566], mapping to fields in the Session Description Protocol (SDP) [RFC 4566],
which is commonly used to describe RTP sessions. When SDP is used to which is commonly used to describe RTP sessions. When SDP is used to
specify sessions employing the IP-MR codec, the mapping is as follows: specify sessions employing the IP-MR codec, the mapping is as follows:
skipping to change at page 15, line 7 skipping to change at page 15, line 7
[RFC 5246] Dierks, T. and E. Rescorla, "The Transport Layer [RFC 5246] Dierks, T. and E. Rescorla, "The Transport Layer
Security (TLS) Protocol Version 1.2", RFC 5246, Security (TLS) Protocol Version 1.2", RFC 5246,
August 2008. August 2008.
[RFC 4301] Kent, S. and K. Seo, "Security Architecture for the [RFC 4301] Kent, S. and K. Seo, "Security Architecture for the
Internet Protocol", RFC 4301, December 2005. Internet Protocol", RFC 4301, December 2005.
10. Author(s) Information: 10. Author(s) Information:
Sergey Morzeev Sergey Ikonin
email: Morzeev@spiritdsp.com email: info@spiritdsp.com
Russia 109004 Russia 109004
Building 27, A. Solgenizyn street Building 27, A. Solzhenitsyna street
Tel: +7 495 661-2178 Tel: +7 495 661-2178
Fax: +7 495 912-6786 Fax: +7 495 912-6786
11. Disclaimer 11. Disclaimer
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November 10, Contributions published or made publicly available before November 10,
2008. The person(s) controlling the copyright in some of this material 2008. The person(s) controlling the copyright in some of this material
may not have granted the IETF Trust the right to allow modifications of may not have granted the IETF Trust the right to allow modifications of
such material outside the IETF Standards Process. Without obtaining an such material outside the IETF Standards Process. Without obtaining an
skipping to change at page 19, line 43 skipping to change at page 19, line 43
for (i = 0; i < *nLayers; i++) { for (i = 0; i < *nLayers; i++) {
payloadBitCount += pLayerBits[i]; payloadBitCount += pLayerBits[i];
} }
return payloadBitCount; return payloadBitCount;
} }
} }
Authors' Addresses Authors' Addresses
SPIRIT DSP SPIRIT DSP
Building 27, A. Solgenizyn street Building 27, A. Solzhenitsyna street
109004, Moscow, RUSSIA 109004, Moscow, RUSSIA
Tel: +7 495 661-2178 Tel: +7 495 661-2178
Fax: +7 495 912-6786 Fax: +7 495 912-6786
EMail: Morzeev@spiritdsp.com EMail: info@spiritdsp.com
 End of changes. 11 change blocks. 
11 lines changed or deleted 12 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/