Re: [MMUSIC] Issue tracker for 4566bis
Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 16 January 2014 22:28 UTC
Return-Path: <pkyzivat@alum.mit.edu>
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 3A7B81A1F78 for <mmusic@ietfa.amsl.com>; Thu, 16 Jan 2014 14:28:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
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 xrMehh-P70Xm for <mmusic@ietfa.amsl.com>; Thu, 16 Jan 2014 14:28:34 -0800 (PST)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:212]) by ietfa.amsl.com (Postfix) with ESMTP id 84FD51A1F62 for <mmusic@ietf.org>; Thu, 16 Jan 2014 14:28:34 -0800 (PST)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta14.westchester.pa.mail.comcast.net with comcast id El061n0031ei1Bg5EmUMwQ; Thu, 16 Jan 2014 22:28:21 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta24.westchester.pa.mail.comcast.net with comcast id EmUM1n00g3ZTu2S3kmUMVN; Thu, 16 Jan 2014 22:28:21 +0000
Message-ID: <52D85D05.5050907@alum.mit.edu>
Date: Thu, 16 Jan 2014 17:28:21 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
References: <55D7A835-54DD-4803-94C3-062D1108E0D6@cisco.com> <52D6D256.3020301@alum.mit.edu> <ACB24DBD-A219-44AB-89D1-A83D47E3B3CE@cisco.com>
In-Reply-To: <ACB24DBD-A219-44AB-89D1-A83D47E3B3CE@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1389911301; bh=3uQsdN8xjJdwTk7JFiGe4A09E72jKvBDOuZtTjfdkTc=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=PkT8XYCf95Zkpc8A9lKwFa4K2gZF7GKw7Xh/U5k/KN2aaJQQXN6i0GRorxg8tcKAn c6zN5N9y2ljF9oObspAhsBg/Ok9SyfMQbaitUlGRce0axH4rjPevC9Y7Khm797SI2Z weewVPtYszkZX7PJmLIiIkqPpyxkwd3bxO4inBT4plXU5xhlCqyaCLcUe4tBRnQ9sU ty2kgcVEschpjPfSTqeJ95dsM2HQqRovpEBRZAXIJkW23agk6lZhNRUgwrv+EWOUL7 PUkL0ZhjZjN7RKPS51O6SKrnxbtfHdUCwAYt29X/WZxEUrcLpDoK2F0UknY6tNVfZG 95PtDio/5SShQ==
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 22:28:36 -0000
Ali, I'll be interested to see the set of issues you post initially. I've raised things from time to time in the past, and you may already have them on your private list. Thanks, Paul On 1/16/14 12:37 PM, Ali C. Begen (abegen) wrote: > > 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 > >
- [MMUSIC] Issue tracker for 4566bis Ali C. Begen (abegen)
- Re: [MMUSIC] Issue tracker for 4566bis Paul Kyzivat
- Re: [MMUSIC] Issue tracker for 4566bis Ali C. Begen (abegen)
- Re: [MMUSIC] Issue tracker for 4566bis Paul Kyzivat