[Gen-art] RE: Gen ART review of draft-ietf-avt-compact-bundled-evrc-09.txt
Black_David@emc.com Thu, 12 October 2006 14:42 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY1lV-0000i9-Km; Thu, 12 Oct 2006 10:42:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY1lT-0000fd-Ov for gen-art@ietf.org; Thu, 12 Oct 2006 10:42:27 -0400
Received: from mexforward.lss.emc.com ([128.222.32.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY1h3-0008Hs-Gd for gen-art@ietf.org; Thu, 12 Oct 2006 10:37:57 -0400
Received: from mailhub.lss.emc.com (nirah.lss.emc.com [10.254.144.13]) by mexforward.lss.emc.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k9CEbf7k008456; Thu, 12 Oct 2006 10:37:41 -0400 (EDT)
Received: from corpussmtp4.corp.emc.com (corpussmtp4.corp.emc.com [10.254.64.54]) by mailhub.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k9CEb8k0004208; Thu, 12 Oct 2006 10:37:34 -0400 (EDT)
From: Black_David@emc.com
Received: from CORPUSMX20A.corp.emc.com ([128.221.62.13]) by corpussmtp4.corp.emc.com with Microsoft SMTPSVC(6.0.3790.0); Thu, 12 Oct 2006 10:37:15 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 12 Oct 2006 10:37:19 -0400
Message-ID: <F222151D3323874393F83102D614E05502B6750D@CORPUSMX20A.corp.emc.com>
In-Reply-To: <452DD37E.40308@motorola.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Gen ART review of draft-ietf-avt-compact-bundled-evrc-09.txt
Thread-Index: AcbtwAeC57fakiHySlKGSOTHrVrMPAAS3mMA
To: Qiaobing.Xie@motorola.com, csp@csperkins.org
X-OriginalArrivalTime: 12 Oct 2006 14:37:15.0892 (UTC) FILETIME=[E9A9FB40:01C6EE0B]
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.4.0.264935, Antispam-Data: 2006.10.12.71443
X-PerlMx-Spam: Gauge=, SPAM=2%, Reason='EMC_FROM_0+ -2, NO_REAL_NAME 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __FRAUD_419_TINHORN 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: fluffy@cisco.com, gen-art@ietf.org, roni.even@polycom.co.il, rkapoor@qualcomm.com, Black_David@emc.com
Subject: [Gen-art] RE: Gen ART review of draft-ietf-avt-compact-bundled-evrc-09.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Errors-To: gen-art-bounces@ietf.org
"default change requires new RFC" is fine with me, and Qiaobing's proposal to just remove the notes about possible 3GPP2 changes to defaults is a reasonable way to get there. Thanks, --David > -----Original Message----- > From: Qiaobing Xie [mailto:Qiaobing.Xie@motorola.com] > Sent: Thursday, October 12, 2006 1:33 AM > To: Colin Perkins > Cc: Black, David; gen-art@ietf.org; rkapoor@qualcomm.com; > fluffy@cisco.com; taylor@nortel.com; roni.even@polycom.co.il > Subject: Re: Gen ART review of > draft-ietf-avt-compact-bundled-evrc-09.txt > > Hi, David, Colin, > > ... > >> > >> I don't like that idea - if there are interoperability issues here, they > >> need to be documented, but if there aren't interoperability issues here, > >> the MUST was probably wrong. I would advise consulting your WG chairs > >> (and possibly the responsible AD) about the importance and potential > >> impact of this issue, as I'm not sufficiently expert to make the call. > > > > Qiaobing is the expert on this codec. As working group chair, I'm happy > > to go with his opinion on this issue. This seems like a minor issue, > > with no impact on the larger protocol design choices. > > > > I agree with Colin. There is no impact on the protocol design here. > > In the rather unlikely event (I can't still think of a reason for it to > happen) that someone wants to change the defaults, a new RFC (or a new > 3GPP2 spec) probably will have to be created to not only specify the > exact changes, but also give meaningful analysis and address on any > potential inter-op issues. Those discussions seems out of scope of this > RFC. That's the reason I propose to remove the misleading note. > > regards, > -Qiaobing > > > Colin _______________________________________________ Gen-art mailing list Gen-art@ietf.org https://www1.ietf.org/mailman/listinfo/gen-art
- [Gen-art] Gen ART review of draft-ietf-avt-compac… Black_David
- [Gen-art] RE: Gen ART review of draft-ietf-avt-co… Black_David
- [Gen-art] Re: Gen ART review of draft-ietf-avt-co… Colin Perkins
- [Gen-art] Re: Gen ART review of draft-ietf-avt-co… Qiaobing Xie
- [Gen-art] RE: Gen ART review of draft-ietf-avt-co… Black_David
- [Gen-art] Re: Gen ART review of draft-ietf-avt-co… Colin Perkins
- [Gen-art] RE: draft-ietf-avt-compact-bundled-evrc… Qiaobing Xie
- [Gen-art] RE: draft-ietf-avt-compact-bundled-evrc… Kapoor, Rohit
- [Gen-art] RE: Gen ART review of draft-ietf-avt-co… Black_David