IETF Logo Mail Archive

Re: [sipcore] Tracker Etiquette

"Worley, Dale R (Dale)" <dworley@avaya.com> Thu, 02 September 2010 19:56 UTC

Return-Path: <dworley@avaya.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 5E9373A6781 for <sipcore@core3.amsl.com>; Thu, 2 Sep 2010 12:56:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.429
X-Spam-Level:
X-Spam-Status: No, score=-102.429 tagged_above=-999 required=5 tests=[AWL=0.170, BAYES_00=-2.599, 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 ms3OnZVIDrJl for <sipcore@core3.amsl.com>; Thu, 2 Sep 2010 12:56:02 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 770113A65A5 for <sipcore@ietf.org>; Thu, 2 Sep 2010 12:56:02 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,309,1280721600"; d="scan'208";a="236032374"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 02 Sep 2010 15:56:31 -0400
X-IronPort-AV: E=Sophos;i="4.56,309,1280721600"; d="scan'208";a="505992870"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 02 Sep 2010 15:56:31 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.129]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Thu, 2 Sep 2010 15:56:31 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Date: Thu, 02 Sep 2010 15:53:34 -0400
Thread-Topic: [sipcore] Tracker Etiquette
Thread-Index: ActJ2x31VfoZit2yTaupuMDZCSX/DQA/Wh4y
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FFC79C0D@DC-US1MBEX4.global.avaya.com>
References: <4C7D5E9C.9090908@nostrum.com> <CD5674C3CD99574EBA7432465FC13C1B21FFC79C04@DC-US1MBEX4.global.avaya.com>, <4C7E5785.6080008@cisco.com>
In-Reply-To: <4C7E5785.6080008@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 19:56:03 -0000

________________________________________
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.

Dale

v2.23.0 | Report a Bug | By Email