From internet-drafts@ietf.org Tue Nov 5 06:51:26 2013 Return-Path: X-Original-To: payload@ietfa.amsl.com Delivered-To: payload@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18F1F21E8262; Tue, 5 Nov 2013 06:51:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.57 X-Spam-Level: X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eFDxyBQmtLFc; Tue, 5 Nov 2013 06:51:25 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EFECF21E8311; Tue, 5 Nov 2013 06:50:56 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.82 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131105145056.29536.71799.idtracker@ietfa.amsl.com> Date: Tue, 05 Nov 2013 06:50:56 -0800 Cc: payload@ietf.org Subject: [payload] I-D Action: draft-ietf-payload-rtp-aptx-04.txt X-BeenThere: payload@ietf.org X-Mailman-Version: 2.1.12 List-Id: Audio/Video Transport Payloads working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 14:51:26 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Audio/Video Transport Payloads Working Gr= oup of the IETF. Title : RTP Payload Format for Standard apt-X and Enhanced apt-X= Codecs Author(s) : John Lindsay Hartmut Foerster Filename : draft-ietf-payload-rtp-aptx-04.txt Pages : 22 Date : 2013-11-05 Abstract: This document specifies a scheme for packetizing Standard apt-X, or Enhanced apt-X, encoded audio data into Real-time Transport Protocol (RTP) packets. The document describes a payload format that permits transmission of multiple related audio channels in a single RTP payload, and a means of establishing Standard apt-X and Enhanced apt-X connections through the Session Description Protocol (SDP). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-payload-rtp-aptx There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-payload-rtp-aptx-04 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-payload-rtp-aptx-04 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From Lindsay@worldcastsystems.com Tue Nov 5 07:10:18 2013 Return-Path: X-Original-To: payload@ietfa.amsl.com Delivered-To: payload@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9E5511E8118 for ; Tue, 5 Nov 2013 07:10:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ESpRTTRaQBFd for ; Tue, 5 Nov 2013 07:10:14 -0800 (PST) Received: from mailgate.aptcodecs.com (mailgate.aptcodecs.com [217.33.179.85]) by ietfa.amsl.com (Postfix) with ESMTP id 8D0D511E8112 for ; Tue, 5 Nov 2013 07:09:52 -0800 (PST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Tue, 5 Nov 2013 15:09:47 -0000 Message-ID: <8C4E0C2409735E4FBC22D754A238F94D02FDEEFF@APTSBS.apt.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-ietf-payload-rtp-aptx-04 Thread-Index: Ac7aORDUwMKSCqAkR7aPOGzr60UXeg== From: "John Lindsay" To: "Ali C. Begen (abegen)" Cc: payload@ietf.org, draft-ietf-payload-rtp-aptx@tools.ietf.org Subject: [payload] draft-ietf-payload-rtp-aptx-04 X-BeenThere: payload@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Payloads working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 15:10:19 -0000 Hi=20 A new doc has been submitted which address the issues raised below. https://datatracker.ietf.org/doc/draft-ietf-payload-rtp-aptx/ If you spot any other issues please let me know. Regards John -----Original Message----- From: payload-bounces@ietf.org [mailto:payload-bounces@ietf.org] On Behalf Of Ali C. Begen (abegen) Sent: 22 October 2013 18:31 To: John Lindsay Cc: ; Subject: Re: [payload] Review of draft-ietf-payload-rtp-aptx-02 John, A few errors still exist (I dont think these are showstoppers but IESG tends to be picky about these when the document is shipped w/o fixing them). > 1) The registration in Section 6.1 uses the old template.=20 > The current template is here: > http://tools.ietf.org/html/rfc6838#section-5.6 >> Updated please ensure you agree You forgot the following item (insert it based on the template): Fragment identifier considerations: None > 5) Regarding the encoding considerations: This should say "framed".=20 >>>> Don't understand issue? Can you give further explanation? Encoding considerations: This media type is framed in RTP and contains binary data; see Section 4.8 of [RFC6838]. > 6) "Restrictions on usage" field can say "RTP applications only". >> Not sure what is meant by this? >> Changed Intended usage: RTP applications only at the bottom of page 14? > Can you ensure you agree? Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP [RFC3550]. >=20 > 7) Person & email address to contact for further information: This=20 > should be "John Lindsay email:lindsay@worldcastsystems.com" >> Again cannot see the issue? Is this supposed to be in quotes? >> Changed to quotes but not 100% sure this was the issue? >> Person & email address to contact for further information: "John=20 >> Lindsay email:lindsay@worldcastsystems.com" I am sorry. Please remove the quotes. I thought the email was missing. The submission is now closed but will open in two weeks. Please update the draft at that time. Thanks, -acbegen _______________________________________________ payload mailing list payload@ietf.org https://www.ietf.org/mailman/listinfo/payload From abegen@cisco.com Tue Nov 5 10:57:11 2013 Return-Path: X-Original-To: payload@ietfa.amsl.com Delivered-To: payload@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9038C21F96CA for ; Tue, 5 Nov 2013 10:57:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WQqcpS4QNnyd for ; Tue, 5 Nov 2013 10:57:06 -0800 (PST) Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id D752221E809F for ; Tue, 5 Nov 2013 10:57:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2767; q=dns/txt; s=iport; t=1383677824; x=1384887424; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ETe/PWP+KfIxDWFI4DkMkhIBFWVSmY5m/5XlQYckWxY=; b=DuVoszwKKpExkGfgTWbfix3MiuE1/lqBxj5fkS2LJEMgvh8KKq/vG15d 0cKkarRDlHHNs6uo45ie0VAx04coFrAwHVwaf4Cwj9Qtr4/TPthcvZngh yIxWzIxqBARtyiE6zvmuoPvt0q9v6R5AKooq6Pz0nWFzR/BXie3ej7C74 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhgFAFY+eVKtJXG+/2dsb2JhbABZgmYhOFO+bUuBLBZ0giUBAQEDAQEBATc0CwUHBAIBCBEEAQEfCQcnCxQJCAEBBAoEBYd7BgEMvwOOEIEWCCsHAgSDGoEPA5gKgS+QWoMmgXE5 X-IronPort-AV: E=Sophos;i="4.93,640,1378857600"; d="scan'208";a="281027973" Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-7.cisco.com with ESMTP; 05 Nov 2013 18:57:03 +0000 Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id rA5Iv3Sq005217 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Nov 2013 18:57:03 GMT Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0123.003; Tue, 5 Nov 2013 12:57:03 -0600 From: "Ali C. Begen (abegen)" To: John Lindsay Thread-Topic: draft-ietf-payload-rtp-aptx-04 Thread-Index: Ac7aORDUwMKSCqAkR7aPOGzr60UXegAUgrYA Date: Tue, 5 Nov 2013 18:57:02 +0000 Message-ID: <2EFA45FA-9AD7-4B00-93CA-1DEC3978D29F@cisco.com> References: <8C4E0C2409735E4FBC22D754A238F94D02FDEEFF@APTSBS.apt.local> In-Reply-To: <8C4E0C2409735E4FBC22D754A238F94D02FDEEFF@APTSBS.apt.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.21.68.93] Content-Type: text/plain; charset="us-ascii" Content-ID: <1C64D3EF2CBBA447B9F124095E76EC37@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "" , "" Subject: Re: [payload] draft-ietf-payload-rtp-aptx-04 X-BeenThere: payload@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Audio/Video Transport Payloads working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 18:57:11 -0000 The revision looks good, I submitted the write-up to the IESG. Please wait = for the IESG review and a green light before the AD before submitting a new= version. Thanks. On Nov 5, 2013, at 7:09 AM, John Lindsay wro= te: > Hi=20 >=20 > A new doc has been submitted which address the issues raised below. >=20 > https://datatracker.ietf.org/doc/draft-ietf-payload-rtp-aptx/ >=20 > If you spot any other issues please let me know. >=20 > Regards >=20 > John >=20 >=20 >=20 > -----Original Message----- > From: payload-bounces@ietf.org [mailto:payload-bounces@ietf.org] On > Behalf Of Ali C. Begen (abegen) > Sent: 22 October 2013 18:31 > To: John Lindsay > Cc: ; > Subject: Re: [payload] Review of draft-ietf-payload-rtp-aptx-02 >=20 > John, >=20 > A few errors still exist (I dont think these are showstoppers but IESG > tends to be picky about these when the document is shipped w/o fixing > them). >=20 >> 1) The registration in Section 6.1 uses the old template.=20 >> The current template is here: >> http://tools.ietf.org/html/rfc6838#section-5.6 >>> Updated please ensure you agree >=20 > You forgot the following item (insert it based on the template): > Fragment identifier considerations: None >=20 >> 5) Regarding the encoding considerations: This should say "framed".=20 >>>>> Don't understand issue? Can you give further explanation? >=20 > Encoding considerations: This media type is framed in RTP and contains > binary data; see Section 4.8 of [RFC6838]. >=20 >> 6) "Restrictions on usage" field can say "RTP applications only". >>> Not sure what is meant by this? >>> Changed Intended usage: RTP applications only at the bottom of page > 14? >> Can you ensure you agree? >=20 > Intended usage: COMMON > Restrictions on usage: This media type depends on RTP framing, and hence > is only defined for transfer via RTP [RFC3550]. >=20 >>=20 >> 7) Person & email address to contact for further information: This=20 >> should be "John Lindsay email:lindsay@worldcastsystems.com" >>> Again cannot see the issue? Is this supposed to be in quotes? >>> Changed to quotes but not 100% sure this was the issue? >>> Person & email address to contact for further information: "John=20 >>> Lindsay email:lindsay@worldcastsystems.com" >=20 > I am sorry. Please remove the quotes. I thought the email was missing. >=20 > The submission is now closed but will open in two weeks. Please update > the draft at that time. >=20 > Thanks, > -acbegen >=20 > _______________________________________________ > payload mailing list > payload@ietf.org > https://www.ietf.org/mailman/listinfo/payload From iesg-secretary@ietf.org Fri Nov 22 13:18:09 2013 Return-Path: X-Original-To: payload@ietfa.amsl.com Delivered-To: payload@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEB481AE278; Fri, 22 Nov 2013 13:18:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6CeWyz-JBWmb; Fri, 22 Nov 2013 13:18:07 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AE3181AE232; Fri, 22 Nov 2013 13:18:07 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Sender: Message-ID: <20131122211807.31080.10150.idtracker@ietfa.amsl.com> Date: Fri, 22 Nov 2013 13:18:07 -0800 Cc: payload@ietf.org Subject: [payload] Last Call: (How to Write an RTP Payload Format) to Informational RFC X-BeenThere: payload@ietf.org X-Mailman-Version: 2.1.15 Reply-To: ietf@ietf.org List-Id: Audio/Video Transport Payloads working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Nov 2013 21:18:09 -0000 The IESG has received a request from the Audio/Video Transport Payloads WG (payload) to consider the following document: - 'How to Write an RTP Payload Format' as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2013-12-06. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document contains information on how to best write an RTP payload format specification. It provides reading tips, design practices, and practical tips on how to produce an RTP payload format specification quickly and with good results. A template is also included with instructions. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-payload-rtp-howto/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-payload-rtp-howto/ballot/ No IPR declarations have been submitted directly on this I-D. From rlb@ipv.sx Fri Nov 22 13:48:16 2013 Return-Path: X-Original-To: payload@ietfa.amsl.com Delivered-To: payload@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DE791AE301 for ; Fri, 22 Nov 2013 13:48:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.977 X-Spam-Level: X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S9gWkqK3QDEk for ; Fri, 22 Nov 2013 13:48:15 -0800 (PST) Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) by ietfa.amsl.com (Postfix) with ESMTP id 25FCA1AE300 for ; Fri, 22 Nov 2013 13:48:15 -0800 (PST) Received: by mail-oa0-f45.google.com with SMTP id o6so2044585oag.32 for ; Fri, 22 Nov 2013 13:48:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=AHH6DoEIxZXvoDPh9JsbfGJO7EwGfKh0T3NiPERzFAM=; b=O2hayFzdkfrdKUSnVEyjSgkbVoS/GRaUT6ypeDGqyv5Qx1HLb0myS9s/RhzQKnk4tx 6iCAP+89Zx4tyDxgA2k5itDtuRLHHHnU8u2+3UySRrb0qeqbeX6eWGM+qYxKwetLfrec pnOwG32ARH0uC4u6DQoo60m/z4wCzx53j3BNa/hWTbkFUEJ7AclWrXXA1mgb8Jike6/o sJ9i8O4VVp7v8GBisg9JKJ3aOUGSK9Bx8Mui9mez5uGd+tuHIJ6Gj/s6WANz06z9pWEw 3gBig3UoIoGGrl4rFpn+6AyK3pmJl1BHYCtnukiSyFlN/BAHFnWYGQeJ1ATQ6EjIEqhe cncg== X-Gm-Message-State: ALoCoQn82tY5Pjjv8bNm8L0n/4KRCUOj4a4jZvFro+r9hQ8cWeYOCJJb5JXk51Hd17PlLVECq+bd MIME-Version: 1.0 X-Received: by 10.60.98.168 with SMTP id ej8mr12380949oeb.45.1385156887868; Fri, 22 Nov 2013 13:48:07 -0800 (PST) Received: by 10.60.31.74 with HTTP; Fri, 22 Nov 2013 13:48:07 -0800 (PST) Date: Fri, 22 Nov 2013 16:48:07 -0500 Message-ID: From: Richard Barnes To: draft-ietf-payload-rtp-aptx@tools.ietf.org, payload-chairs@tools.ietf.org, "payload@ietf.org" Content-Type: multipart/alternative; boundary=089e0115f928428b4904ebcaf830 Subject: [payload] AD review: draft-ietf-payload-rtp-aptx-04 X-BeenThere: payload@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Audio/Video Transport Payloads working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Nov 2013 21:48:16 -0000 --089e0115f928428b4904ebcaf830 Content-Type: text/plain; charset=ISO-8859-1 I have reviewed this document in preparation for IETF LC, and think it's ready to go. Thanks to the authors for a clear, readable spec. --Richard --089e0115f928428b4904ebcaf830 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I have reviewed this document in preparation for IETF= LC, and think it's ready to go.=A0 Thanks to the authors for a clear, = readable spec.

--Richard
--089e0115f928428b4904ebcaf830-- From iesg-secretary@ietf.org Fri Nov 22 14:08:32 2013 Return-Path: X-Original-To: payload@ietfa.amsl.com Delivered-To: payload@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C6671AE19F; Fri, 22 Nov 2013 14:08:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6bxpdqJMmwW5; Fri, 22 Nov 2013 14:08:31 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BC5FE1AE34D; Fri, 22 Nov 2013 14:08:27 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Sender: Message-ID: <20131122220827.31098.15162.idtracker@ietfa.amsl.com> Date: Fri, 22 Nov 2013 14:08:27 -0800 Cc: payload@ietf.org Subject: [payload] Last Call: (RTP Payload Format for Standard apt-X and Enhanced apt-X Codecs) to Proposed Standard X-BeenThere: payload@ietf.org X-Mailman-Version: 2.1.15 Reply-To: ietf@ietf.org List-Id: Audio/Video Transport Payloads working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Nov 2013 22:08:32 -0000 The IESG has received a request from the Audio/Video Transport Payloads WG (payload) to consider the following document: - 'RTP Payload Format for Standard apt-X and Enhanced apt-X Codecs' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2013-12-06. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document specifies a scheme for packetizing Standard apt-X, or Enhanced apt-X, encoded audio data into Real-time Transport Protocol (RTP) packets. The document describes a payload format that permits transmission of multiple related audio channels in a single RTP payload, and a means of establishing Standard apt-X and Enhanced apt-X connections through the Session Description Protocol (SDP). The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-payload-rtp-aptx/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-payload-rtp-aptx/ballot/ No IPR declarations have been submitted directly on this I-D.