Re: [sipcore] A new SIP header fields with "P-" name
Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 01 December 2015 14:35 UTC
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C718D1A8F3E for <sipcore@ietfa.amsl.com>; Tue, 1 Dec 2015 06:35:08 -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 px5UCckyOvXM for <sipcore@ietfa.amsl.com>; Tue, 1 Dec 2015 06:35:07 -0800 (PST)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C2241A0127 for <sipcore@ietf.org>; Tue, 1 Dec 2015 06:35:07 -0800 (PST)
Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by resqmta-ch2-08v.sys.comcast.net with comcast id oEb51r0022XD5SV01Eb6PM; Tue, 01 Dec 2015 14:35:06 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-20v.sys.comcast.net with comcast id oEb51r00U3KdFy101Eb6aG; Tue, 01 Dec 2015 14:35:06 +0000
To: sipcore@ietf.org
References: <39B5E4D390E9BD4890E2B3107900610112AEC437@ESESSMB301.ericsson.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <565DB018.3000900@alum.mit.edu>
Date: Tue, 01 Dec 2015 09:35:04 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <39B5E4D390E9BD4890E2B3107900610112AEC437@ESESSMB301.ericsson.se>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1448980506; bh=qbT1YgkicXYK+BydM5md9aY/6d7oKAbLTlsZ96spYj8=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=wDi3W5Y9kXYmTeREEmK22T8m4JbyjJuFbE6HzaPir5UdbW4dKhdRlFcRxGVu7olD3 xpGdfCQUukgHu6h6z6Nu4NwFddDrVsvy66vzy8VB1Cy+Ikhci4ZTwBHmr0QIGP0608 0RrC/HHCSnpaSyGSzcXoexCrmdqqyTzuxKAB0oO7G0jwNsSQxKGJbNgxnwN9gP5Qn+ EQ5Lheetlqpr85ZYOlM4F04FiWGx0ZqkzQS1HrIz/cYbRtjkvaLRwKpK9LJzQXSPrI 38gnWjXmS7JUXdMviMwi2jnZNo5WtBpT5c+1nDPeNeB432trQn+Z2j4LGlDVz81X/7 kzA/x5He8R3dQ==
Archived-At: <http://mailarchive.ietf.org/arch/msg/sipcore/5v06B0BwInOo0nx-e_ewLmTsIEI>
Subject: Re: [sipcore] A new SIP header fields with "P-" name
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 01 Dec 2015 14:35:09 -0000
On 12/1/15 2:00 AM, Ivo Sedlacek wrote: > Hello, > > in the last 3GPP CT1 WG meeting, 3GPP CT1 WG was unable to conclude > whether it is possible to define and to use a new "P-"header field. > > Some believed that IANA registration of a new "P-" header field is not > possible any more due to RFC5727. Others believed that IANA registration > of a new "P-" header field is possible as long as someone already > implemented and deployed such header field (even if it was done recently). My understanding of 5727 is that when it refers to "existing", it means those existing prior to the publication of 5727. Anybody starting to use a new P- header after that time should have known they were doing something wrong. Thanks, Paul > Can you please provide guidance whether IANA registration of a new "P-" > header field is likely? Thanks. > > RFC5727 states: > > --------------------------- > > New > > proposals to document SIP header fields of an experimental or private > > nature, however, shall not use the "P-" prefix (unless existing > > deployments or standards use the prefix already, in which case they > > may be admitted as grandfathered cases at the discretion of the > > Designated Expert). > > --------------------------- > > Kind regards > > Ivo Sedlacek > > > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore >
- [sipcore] A new SIP header fields with "P-" name Ivo Sedlacek
- Re: [sipcore] A new SIP header fields with "P-" n… Paul Kyzivat
- Re: [sipcore] A new SIP header fields with "P-" n… Adam Roach
- Re: [sipcore] A new SIP header fields with "P-" n… Christer Holmberg
- Re: [sipcore] A new SIP header fields with "P-" n… Ben Campbell
- Re: [sipcore] A new SIP header fields with "P-" n… Ivo Sedlacek
- Re: [sipcore] A new SIP header fields with "P-" n… James Cloos
- Re: [sipcore] A new SIP header fields with "P-" n… Paul Kyzivat
- Re: [sipcore] A new SIP header fields with "P-" n… Adam Roach
- Re: [sipcore] A new SIP header fields with "P-" n… Mary Barnes
- Re: [sipcore] A new SIP header fields with "P-" n… Ivo Sedlacek
- Re: [sipcore] A new SIP header fields with "P-" n… Paul Kyzivat
- Re: [sipcore] A new SIP header fields with "P-" n… Ben Campbell
- Re: [sipcore] A new SIP header fields with "P-" n… DRAGE, Keith (Keith)
- Re: [sipcore] A new SIP header fields with "P-" n… Ivo Sedlacek
- Re: [sipcore] A new SIP header fields with "P-" n… Mary Barnes