IETF Logo Mail Archive

Re: [sipcore] Tracker Etiquette

"James M. Polk" <jmpolk@cisco.com> Wed, 01 September 2010 04:00 UTC

Return-Path: <jmpolk@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 152133A6A12 for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 21:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.498
X-Spam-Level:
X-Spam-Status: No, score=-110.498 tagged_above=-999 required=5 tests=[AWL=0.101, 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 Dqv9St4J2Uhm for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 21:00:01 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 202C03A6A03 for <sipcore@ietf.org>; Tue, 31 Aug 2010 21:00:01 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACdsfUyrR7Hu/2dsb2JhbACgXXGif5wdhTcEhD0
X-IronPort-AV: E=Sophos;i="4.56,301,1280707200"; d="scan'208";a="179685366"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 01 Sep 2010 04:00:31 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8715.cisco.com [10.99.80.22]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o8140VYa026581; Wed, 1 Sep 2010 04:00:31 GMT
Message-Id: <201009010400.o8140VYa026581@sj-core-5.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 31 Aug 2010 23:00:30 -0500
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, Adam Roach <adam@nostrum.com>, SIPCORE <sipcore@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B21FFC79C04@DC-US1MBEX4.glo bal.avaya.com>
References: <4C7D5E9C.9090908@nostrum.com> <CD5674C3CD99574EBA7432465FC13C1B21FFC79C04@DC-US1MBEX4.global.avaya.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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: Wed, 01 Sep 2010 04:00:02 -0000

At 09:21 PM 8/31/2010, Worley, Dale R (Dale) wrote:

>In regard to putting something in the "ticket name" to indicate the 
>document in question:  I see a data field "Component" for which one 
>can select the value "4244bis".

I don't see "4244bis" in the subject line, which is ideally what I'm 
asking for - so I can track those messages pertinent to my doc, even 
though I care a lot about every SIPCORE doc, the one I'm responsible 
for is more important - right?

If it could show up as

         Subject: [sipcore] 4244bis: ...
or
         Subject: [sipcore] Loc: ...

then it can be tracked by everyone (especially the editors) easier ISTM.

james

>I've been assuming that is how one identifies the tickets that are 
>relevant to 4244bis.  Is this not the correct thing to do?  I do not 
>see a data field named "ticket name".
>
>Dale
>_______________________________________________
>sipcore mailing list
>sipcore@ietf.org
>https://www.ietf.org/mailman/listinfo/sipcore

v2.23.0 | Report a Bug | By Email