IETF Logo Mail Archive

Re: [MMUSIC] Issue tracker for 4566bis

"Ali C. Begen (abegen)" <abegen@cisco.com> Thu, 16 January 2014 17:37 UTC

Return-Path: <abegen@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFE431AE171 for <mmusic@ietfa.amsl.com>; Thu, 16 Jan 2014 09:37:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level:
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 LaSWD3rMY2zU for <mmusic@ietfa.amsl.com>; Thu, 16 Jan 2014 09:37:42 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id 33C7B1AE116 for <mmusic@ietf.org>; Thu, 16 Jan 2014 09:37:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2016; q=dns/txt; s=iport; t=1389893850; x=1391103450; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=YFZapA/Zb/TcELVqAgQc8jPQBPnn1JtfBuOmFAIduV0=; b=l5bzMErvznyTm7oLDQbQX58BJbKIV8izDknaSo5mWMxGVDkTwzA6gAMB p/9Z0BsS2C8usmSkQahGvRtvhblFyS2ozJo4r48kdIEiC7V+g0FgfdV5c C05belw3iSEBCkSxkAzUUVLIOvU7ytDHHEYjlWJJTauRNPlbteNYMOjR+ 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjMFABQY2FKtJXG+/2dsb2JhbABZDoJcIThWujxPgQ4WdIIlAQEBAwEBAQE3NAsFCwIBCA4KHhAnCyUCBA4FG4dhCAEMxGEXjh0RAQsSMweDJIEUBJghgTGQZoJuP4FxOQ
X-IronPort-AV: E=Sophos;i="4.95,668,1384300800"; d="scan'208";a="13371827"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by alln-iport-6.cisco.com with ESMTP; 16 Jan 2014 17:37:29 +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 s0GHbTBU019662 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 16 Jan 2014 17:37:29 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; Thu, 16 Jan 2014 11:37:29 -0600
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [MMUSIC] Issue tracker for 4566bis
Thread-Index: AQHPEWG8F/foggAQEEyGL+H7582LcJqGf9cAgAGFPwA=
Date: Thu, 16 Jan 2014 17:37:29 +0000
Message-ID: <ACB24DBD-A219-44AB-89D1-A83D47E3B3CE@cisco.com>
References: <55D7A835-54DD-4803-94C3-062D1108E0D6@cisco.com> <52D6D256.3020301@alum.mit.edu>
In-Reply-To: <52D6D256.3020301@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.122.225]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <042D7ECA2E9A0141812F357768D01B19@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<mmusic@ietf.org>" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Issue tracker for 4566bis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 17:37:44 -0000

On Jan 15, 2014, at 10:24 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> On 1/14/14 2:49 PM, Ali C. Begen (abegen) wrote:
>> Hi everyone
>> 
>> Revising 4566 is underway as you know and there have been some issues with 4566 and some folks want them to be fixed in 4566bis. However, due to convoluted discussions, some of these issues go unfixed. To make the process easier, it was suggested to establish an issue tracker.
>> 
>> I have not done this before, but found the link below:
>> http://tools.ietf.org/wg/mmusic/trac/report/1
>> 
>> Is this a good idea to use this or do you have better suggestions?
> 
> This is just a link to a report of active tickets.
> Are you just asking if doing something analogous for 4566bis would be a good thing?
> 
> I think the issue tracker is fine if you, as editor, use it to track the issues with your document.
> 
> But I strongly suggest that you be the only one to open, update, and close tickets for 4566bis. Don't leave it for anybody who thinks they have an issue to open their own ticket, and don't use updates to the tickets as a way to debate an issue. I saw that done once or twice and it created a mess - confusing established mechanisms for discussing issues via email.
> 
> So IMO we should continue to *discuss* proposed changes on the mmusic list. Based on those discussions you can make tickets as you see fit to track the status of identified issues and their incorporation into the draft.

Fine with me. I will try to create and track the issues in that list (so everybody can know where we are) and people should post their comments about the 4566bis in the list. But, please be clear on what the problem is and provide a solution if you can so that we can move faster.

thanks.
-acbegen



> 
> 	Thanks,
> 	Paul
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic

v2.23.0 | Report a Bug | By Email