draft-ietf-payload-rtp-sbc-03.txt   draft-ietf-payload-rtp-sbc-04.txt 
Working Group PAYLOAD C. Hoene Working Group PAYLOAD C. Hoene
Internet Draft Symonics GmbH Internet Draft Symonics GmbH
Intended status: Standards Track F. de Bont Intended status: Standards Track F. de Bont
Expires: January 2013 Philips Electronics Expires: July 2013 Philips Electronics
July 8, 2012 January 10, 2013
RTP Payload Format for Bluetooth's SBC Audio Codec RTP Payload Format for Bluetooth's SBC Audio Codec
draft-ietf-payload-rtp-sbc-03 draft-ietf-payload-rtp-sbc-04
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), 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
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference 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 January 8, 2009. This Internet-Draft will expire on July 10, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 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 carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
skipping to change at page 2, line 22 skipping to change at page 2, line 22
Profile (A2DP) Specification written by the Bluetooth(r) Special Profile (A2DP) Specification written by the Bluetooth(r) Special
Interest Group (SIG). The payload format is designed to be able to Interest Group (SIG). The payload format is designed to be able to
interoperate with existing Bluetooth A2DP devices, to provide high interoperate with existing Bluetooth A2DP devices, to provide high
streaming audio quality, interactive audio transmission over the streaming audio quality, interactive audio transmission over the
internet, and ultra-low delay coding for jam sessions on the internet, and ultra-low delay coding for jam sessions on the
internet. This document contains also a media type registration internet. This document contains also a media type registration
which specifies the use of the RTP payload format. which specifies the use of the RTP payload format.
Table of Contents Table of Contents
1. Introduction ................................................ 3 1. Introduction ................................................. 3
2. Conventions used in this Document ........................... 3 2. Conventions used in this Document ............................ 3
3. Background .................................................. 3 3. Background ................................................... 3
3.1. SBC Media Payload Format ............................... 5 3.1. SBC Frame Structure ..................................... 5
3.2. SBC Fragmentation ...................................... 5 3.2. Frame Header ............................................ 5
3.3. Media Payload Format Header ............................ 5 3.3. Remaining Frame Part .................................... 8
3.4. SBC Frame Structure .................................... 5 4. Usage Scenarios .............................................. 8
3.5. Frame Header ........................................... 5 4.1. Scenario 1: Interconnection of A2DP Devices ............. 8
3.6. Remaining Frame Part ................................... 8 4.2. Scenario 2: High Quality Interactive Audio Transmissions 9
4. Usage Scenarios ............................................. 8 4.3. Scenario 3: Ensembles performing over a Network ......... 9
4.1. Scenario 1: Interconnection of A2DP Devices ............ 8 5. Header Usage ................................................ 10
4.2. Scenario 2: High Quality Interactive Audio Transmissions 9 6. Payload Format .............................................. 11
4.3. Scenario 3: Ensembles performing over a Network ........ 9 7. Payload Format Parameters ................................... 11
5. Header Usage ............................................... 10 7.1. Media Type Registration for SBC ........................ 11
6. Payload Format ............................................. 11 7.1.1. Capabilities: A2DP Modes .......................... 13
7. Payload Format Parameters .................................. 11 7.1.2. Capabilities: Other Modes ......................... 14
7.1. Media Type Registration for SBC ....................... 11 7.2. Mapping to SDP Parameters .............................. 14
7.1.1. Capabilities: A2DP Modes ......................... 13 7.2.1. Offer-Answer Model Considerations ................. 15
7.1.2. Capabilities: Other Modes ........................ 14 7.2.2. Declarative SDP Considerations .................... 17
7.2. Mapping to SDP Parameters ............................. 14 8. Congestion Control .......................................... 17
7.2.1. Offer-Answer Model Considerations ................ 15 9. Packet Loss Concealment ..................................... 18
7.2.2. Declarative SDP Considerations ................... 17 10. Security Considerations .................................... 18
8. Congestion Control ......................................... 17 11. IANA Considerations......................................... 19
9. Packet Loss Concealment .................................... 18 12. References ................................................. 20
10. Security Considerations ................................... 18 12.1. Normative References .................................. 20
11. IANA Considerations........................................ 19 12.2. Informative References ................................ 20
12. References ................................................ 20 13. Acknowledgments ............................................ 22
12.1. Normative References ................................. 20
12.2. Informative References ............................... 20
13. Acknowledgments ........................................... 22
1. Introduction 1. Introduction
The Bluetooth(r) Special Interest Group (SIG) specifies in the The Bluetooth(r) Special Interest Group (SIG) specifies in the
Advanced Audio Distribution Profile (A2DP) [A2DPV12] a mono and Advanced Audio Distribution Profile (A2DP) [A2DPV12] a mono and
stereo high quality audio subband codec (SBC). This document stereo high quality audio subband codec (SBC). This document
specifies the payload format for the encapsulation of SBC encoded specifies the payload format for the encapsulation of SBC encoded
audio frames into the Real-time Transport Protocol (RTP). audio frames into the Real-time Transport Protocol (RTP).
SBC has a low computational complexity at modest compression rates. SBC has a low computational complexity at modest compression rates.
skipping to change at page 23, line 13 skipping to change at page 23, line 13
This document was prepared using 2-Word-v2.0.template.dot. This document was prepared using 2-Word-v2.0.template.dot.
Authors' Addresses Authors' Addresses
Christian Hoene Christian Hoene
Symonics GmbH Symonics GmbH
Sand 13 Sand 13
72076 Tuebingen 72076 Tuebingen
DE DE
Phone: +49 7071 5681300 Phone: +49 7071 568 1300
Email: christian.hoene@symonics.com Email: Christian.hoene@symonics.com
Frans de Bont Frans de Bont
Philips Electronics Philips Electronics
High Tech Campus 36 High Tech Campus 36
5656 AE Eindhoven 5656 AE Eindhoven
NL NL
Phone: +31 40 2740234 Phone: +31 40 2740234
Email: frans.de.bont@philips.com Email: frans.de.bont@philips.com
 End of changes. 6 change blocks. 
37 lines changed or deleted 34 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/