Re: [AVTCORE] WG last call on draft-ietf-avtcore-avp-codecs-01

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Tue, 19 March 2013 17:15 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E77B21F8F00 for <avt@ietfa.amsl.com>; Tue, 19 Mar 2013 10:15:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 7gelovBNPD8U for <avt@ietfa.amsl.com>; Tue, 19 Mar 2013 10:15:37 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 5BE4421F8DD9 for <avt@ietf.org>; Tue, 19 Mar 2013 10:15:37 -0700 (PDT)
Received: from us70uusmtp3.zam.alcatel-lucent.com (h135-5-2-65.lucent.com [135.5.2.65]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r2JHFSlE023012 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 19 Mar 2013 12:15:28 -0500 (CDT)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id r2JHFSZE017059 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Mar 2013 13:15:28 -0400
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (135.239.2.111) by US70UWXCHHUB02.zam.alcatel-lucent.com (135.5.2.49) with Microsoft SMTP Server (TLS) id 14.2.247.3; Tue, 19 Mar 2013 13:15:28 -0400
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.201]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Tue, 19 Mar 2013 18:15:23 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [AVTCORE] WG last call on draft-ietf-avtcore-avp-codecs-01
Thread-Index: AQHOI8LhCA0R1lcTUk2XY0zvQt8uJZitLXpw
Date: Tue, 19 Mar 2013 17:15:22 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B0181CF@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <513F7BDD.8010700@ericsson.com> <949EF20990823C4C85C18D59AA11AD8B0128BD@FR712WXCHMBA11.zeu.alcatel-lucent.com> <1515D7F3-AEC2-4612-829F-41EB3E7A9069@csperkins.org>
In-Reply-To: <1515D7F3-AEC2-4612-829F-41EB3E7A9069@csperkins.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, IETF AVTCore WG <avt@ietf.org>
Subject: Re: [AVTCORE] WG last call on draft-ietf-avtcore-avp-codecs-01
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 17:15:38 -0000

I'm still confused.

Surely PCMU0 was recommended before this update and is recommended now.

DVI4 was recommended before this update and is now optional.

I guess the result of that is that I can be conformant but implement neither, although it will not be a terribly useful implementation.

Regards

Keith



> -----Original Message-----
> From: Colin Perkins [mailto:csp@csperkins.org]
> Sent: 15 March 2013 18:00
> To: DRAGE, Keith (Keith)
> Cc: Magnus Westerlund; IETF AVTCore WG
> Subject: Re: [AVTCORE] WG last call on draft-ietf-avtcore-avp-codecs-01
> 
> On 12 Mar 2013, at 16:40, DRAGE, Keith (Keith) wrote:
> > I'm trying to parse the final sentence of the change made to RFC 3551.
> >
> > Essentially this i-d modifies:
> >
> > "   Audio applications operating under this profile SHOULD, at a minimum,
> >   be able to send and/or receive payload types 0 (PCMU) and 5 (DVI4).
> >   This allows interoperability without format negotiation and ensures
> >   successful negotiation with a conference control protocol."
> >
> > To become:
> >
> > "   Audio applications operating under this profile SHOULD, at a minimum,
> >   be able to send and/or receive payload type 0 (PCMU).
> >   This allows interoperability without format negotiation and ensures
> >   successful negotiation with a conference control protocol. Some
> >   environments MAY make support for PCMU mandatory."
> >
> > What the final sentence currently says is that some environments provide
> an option to make support for PCMU mandatory, which implies that other
> environments do not provide such an option. Neither of those make sense to
> me and there I believe that cannot be the meaning.
> >
> > I suspect we are looking for sentence that looks more like "Some
> environments REQUIRE support for PCMU", but I am not sure if there is an
> "only" floating around in there somewhere.
> 
> 
> I don't think the draft ought to say "only". This sentence looks to be
> addressing the RTCWeb use case, which makes PCMU mandatory to implement
> but also allows other codecs.
> 
> To my reading, "Some environments MAY make support for PCMU mandatory" and
> "Some environments REQUIRE support for PCMU" are equivalent, but I have no
> objection to the change if you think it clearer.
> 
> --
> Colin Perkins
> http://csperkins.org/
> 
>