Re: [sipcore] [Ecrit] Establishing a "Priority" header field registry

Janet P Gunn <jgunn6@csc.com> Wed, 07 November 2012 14:07 UTC

Return-Path: <jgunn6@csc.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1B7821F875C; Wed, 7 Nov 2012 06:07:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.952
X-Spam-Level:
X-Spam-Status: No, score=-5.952 tagged_above=-999 required=5 tests=[AWL=0.646, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z13fEEH50r0U; Wed, 7 Nov 2012 06:07:57 -0800 (PST)
Received: from mail85.messagelabs.com (mail85.messagelabs.com [216.82.241.211]) by ietfa.amsl.com (Postfix) with ESMTP id 784CF21F8742; Wed, 7 Nov 2012 06:07:57 -0800 (PST)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-14.tower-85.messagelabs.com!1352297276!36749630!1
X-Originating-IP: [20.137.2.87]
X-StarScan-Received:
X-StarScan-Version: 6.6.1.8; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 595 invoked from network); 7 Nov 2012 14:07:56 -0000
Received: from amer-mta101.csc.com (HELO amer-mta101.csc.com) (20.137.2.87) by server-14.tower-85.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Nov 2012 14:07:56 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta101.csc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qA7E7sc0025836; Wed, 7 Nov 2012 09:07:54 -0500
In-Reply-To: <201211070405.qA745JVS004352@rcdn-core2-2.cisco.com>
References: <50993285.4020408@nostrum.com> <7D126AA8-CCA4-4D88-82FA-796ADC0FFEB0@neustar.biz> <201211070405.qA745JVS004352@rcdn-core2-2.cisco.com>
To: James Polk <jmpolk@cisco.com>
MIME-Version: 1.0
X-KeepSent: B909FEAE:A277906E-85257AAF:004D90C7; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OFB909FEAE.A277906E-ON85257AAF.004D90C7-85257AAF.004DA1B3@csc.com>
Date: Wed, 07 Nov 2012 09:07:50 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 11/07/2012 09:03:22 AM, Serialize complete at 11/07/2012 09:03:22 AM
Content-Type: multipart/alternative; boundary="=_alternative 004DA15685257AAF_="
Cc: "Rosen, Brian" <Brian.Rosen@neustar.biz>, "sipcore@ietf.org" <sipcore@ietf.org>, "ecrit@ietf.org" <ecrit@ietf.org>, ecrit-bounces@ietf.org
Subject: Re: [sipcore] [Ecrit] Establishing a "Priority" header field registry
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 07 Nov 2012 14:07:58 -0000

I also support this work
Janet

This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use of 
e-mail for such purpose.



From:   James Polk <jmpolk@cisco.com>
To:     "Rosen, Brian" <Brian.Rosen@neustar.biz>, "sipcore@ietf.org" 
<sipcore@ietf.org>
Cc:     "ecrit@ietf.org" <ecrit@ietf.org>
Date:   11/06/2012 11:05 PM
Subject:        Re: [Ecrit] [sipcore] Establishing a "Priority" header 
field registry
Sent by:        ecrit-bounces@ietf.org



I support this work

James

At 12:22 PM 11/6/2012, Rosen, Brian wrote:
>I support this work.  I agree with Christer about a registration 
>template.  While it is obvious what is requested, I think it's 
>better to have it.
>
>I am happy with "IETF Review" as the management policy.
>
>Brian
>
>On Nov 6, 2012, at 10:53 AM, Adam Roach <adam@nostrum.com> wrote:
>
> > [as an individual]
> >
> > The document draft-ietf-ecrit-psap-callback has identified a 
> desire to add a new value to the "Priority" header field for SIP. 
> While RFC 3261 clearly intended the values in this header field to 
> be extensible, it did not define a registry of such values.
> >
> > To address this oversight, I have put together a small draft that 
> defines such a registry and populates it with the values defined by 
> RFC 3261. Because this is a correction to the core SIP 
> specification, it is my belief that it falls within the charter of 
> the SIPCORE working group.
> >
> > The only real open issue, in my opinion, is the IANA registration 
> policy that should apply to new "Priority" header field values. To 
> avoid blocking any work in ECRIT, we need to move this work (or 
> something equivalent) forward very quickly. If you have any 
> interest in the topic, please review and comment with some urgency.
> >
> > http://www.ietf.org/id/draft-roach-sipcore-priority-00.txt
> >
> >
> > [The following request is being made in my WG chair role]
> > As this is a SIPCORE matter, please discuss it on the SIPCORE 
> list rather than the ECRIT list.
> >
> > Thanks!
> >
> > /a
> > _______________________________________________
> > sipcore mailing list
> > sipcore@ietf.org
> > https://www.ietf.org/mailman/listinfo/sipcore
>
>_______________________________________________
>Ecrit mailing list
>Ecrit@ietf.org
>https://www.ietf.org/mailman/listinfo/ecrit

_______________________________________________
Ecrit mailing list
Ecrit@ietf.org
https://www.ietf.org/mailman/listinfo/ecrit