IETF Logo Mail Archive

Re: [sipcore] Tracker Etiquette

Paul Kyzivat <pkyzivat@cisco.com> Thu, 02 September 2010 20:23 UTC

Return-Path: <pkyzivat@cisco.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6EBBA3A6998 for <sipcore@core3.amsl.com>; Thu, 2 Sep 2010 13:23:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.512
X-Spam-Level:
X-Spam-Status: No, score=-110.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JJo2GGlinJBk for <sipcore@core3.amsl.com>; Thu, 2 Sep 2010 13:23:41 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 6B16E3A688C for <sipcore@ietf.org>; Thu, 2 Sep 2010 13:23:41 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPqkf0ytJV2Z/2dsb2JhbAChC3GiZJwlhTsEihk
X-IronPort-AV: E=Sophos;i="4.56,309,1280707200"; d="scan'208";a="154709460"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rtp-iport-1.cisco.com with ESMTP; 02 Sep 2010 20:24:10 +0000
Received: from [161.44.174.142] (dhcp-161-44-174-142.cisco.com [161.44.174.142]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id o82KOA1N026906; Thu, 2 Sep 2010 20:24:10 GMT
Message-ID: <4C8007EC.6050707@cisco.com>
Date: Thu, 02 Sep 2010 16:24:12 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
References: <4C7D5E9C.9090908@nostrum.com> <CD5674C3CD99574EBA7432465FC13C1B21FFC79C04@DC-US1MBEX4.global.avaya.com>, <4C7E5785.6080008@cisco.com> <CD5674C3CD99574EBA7432465FC13C1B21FFC79C0D@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B21FFC79C0D@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: SIPCORE <sipcore@ietf.org>
Subject: Re: [sipcore] Tracker Etiquette
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 20:23:42 -0000

Worley, Dale R (Dale) wrote:
> ________________________________________
> From: Paul Kyzivat [pkyzivat@cisco.com]
> 
> I think there will be no problem if the creator of a ticket closes it.
> But if the editor of the subject document closes the ticket without
> acting on it, and without explaining why, and without permission of the
> creator, then there will probably be complaints.
> _______________________________________________
> 
> OTOH, when WGLC time comes around, I will do the appropriate search on the tracker (category == "4244bis" && submitter == "dworley") to find all the issues that I have raised and will compare each issue with the document to verify that it has been taken care of.  So though there is no security block against closing an issue "arbitrarily", if the submitter is paying attention, there will be no adverse practical consequence.

If people find that sufficient, then it is certainly simple.

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email