IETF Logo Mail Archive

[payload] Review of draft-ietf-payload-rtp-aptx-02

"Ali C. Begen (abegen)" <abegen@cisco.com> Sun, 20 October 2013 20:57 UTC

Return-Path: <abegen@cisco.com>
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 96BD111E8447 for <payload@ietfa.amsl.com>; Sun, 20 Oct 2013 13:57:17 -0700 (PDT)
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 Csy+3apPMgkD for <payload@ietfa.amsl.com>; Sun, 20 Oct 2013 13:57:12 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 3633311E8444 for <payload@ietf.org>; Sun, 20 Oct 2013 13:57:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1815; q=dns/txt; s=iport; t=1382302629; x=1383512229; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=OQSukhimunEX0rsq6xs13HoNZZ7MhMuNvYJneWYiNxA=; b=aol57W54BEwLGw5SpAfx5tJz2nAzDpCd0QdX2aPCRNScjjkXBl5cOils s/ndnknDpZpFRcEYEXUOyyx7Omh5X+plwYM+233n2dqqTn3LYcz95qGc4 E9XEZKe7XG5RmS963IZkquPqB5WovXK/OFssDoHkw7t8GuPXu/sFdz1KG Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AngGAC1DZFKtJXHB/2dsb2JhbABagmYhOFS+MoEkFm0HgicBBDo/EgEqFEInBA4FCId+AQy9QY4TgRgxgyaBCgOZOJBYgySBcTk
X-IronPort-AV: E=Sophos;i="4.93,534,1378857600"; d="scan'208";a="274365386"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-7.cisco.com with ESMTP; 20 Oct 2013 20:57:09 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r9KKv8i2019111 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 20 Oct 2013 20:57:08 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.02.0318.004; Sun, 20 Oct 2013 15:57:08 -0500
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "payload@ietf.org" <payload@ietf.org>
Thread-Topic: Review of draft-ietf-payload-rtp-aptx-02
Thread-Index: AQHOzdbw2vjQftbAz0q6DC+dHfSdjw==
Date: Sun, 20 Oct 2013 20:57:08 +0000
Message-ID: <C15918F2FCDA0243A7C919DA7C4BE9940E71F203@xmb-aln-x01.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.107.190]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F9D31C7741BBE248B0F592E9B8F75C59@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-ietf-payload-rtp-aptx@tools.ietf.org" <draft-ietf-payload-rtp-aptx@tools.ietf.org>
Subject: [payload] Review of draft-ietf-payload-rtp-aptx-02
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/payload>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Oct 2013 20:57:18 -0000

The WGLC has ended a few weeks ago and I just completed my review. Everything looks good except a few typos. In general, I would avoid using "ms" until it is defined "milliseconds (ms)".

Authors, if you can submit a revision by tomorrow (21st of Oct.), we can ship this right away.

Thanks,
-acbegen

Other comments regarding media subtype registration (Thanks to Bjoern Hoehrmann):

1) The registration in Section 6.1 uses the old template. 
The current template is here: http://tools.ietf.org/html/rfc6838#section-5.6

2) Regarding ptime: It might be better to say "Defaults to 4 (milliseconds)", otherwise some might be confused whether the `ms` is part of the value.

3) Regarding stereo channels: If the value includes characters like `{` then in protocols like HTTP the value would have to be enclosed in double quotes since `{` is not allowed as a bare token in that protocol. The situation may be similar in RTP, and if so, that's not sufficiently clear from the text above. The same goes for some other parameters and other characters like `,`.

Is there some other way that we can use to avoid this potential problem?

4) Regarding embedded-autosync-channels: This should be rephrased to avoid combining "MUST" and "only"; it is not clear whether specifying more than the first channel is optional or forbidden. Same for the `embedded-aux-channels` parameter.

5) Regarding the encoding considerations: This should say "framed". 

6) "Restrictions on usage" field can say "RTP applications only".

7) Person & email address to contact for further information: This should be "John Lindsay email:lindsay@worldcastsystems.com"

8) Author/Change controller: This should say "IETF Payload Working Group delegated from the IESG"

v2.23.0 | Report a Bug | By Email