[Sipping] P-headers in 3GPP
krisztian.kiss@nokia.com Fri, 08 March 2002 15:28 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09942 for <sipping-archive@odin.ietf.org>; Fri, 8 Mar 2002 10:28:18 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA09070 for sipping-archive@odin.ietf.org; Fri, 8 Mar 2002 10:28:19 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA05948; Fri, 8 Mar 2002 09:34:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA05921 for <sipping@optimus.ietf.org>; Fri, 8 Mar 2002 09:34:53 -0500 (EST)
Received: from mgw-x3.nokia.com (mgw-x3.nokia.com [131.228.20.26]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06986 for <sipping@ietf.org>; Fri, 8 Mar 2002 09:34:48 -0500 (EST)
From: krisztian.kiss@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x3.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g28EZSi08297 for <sipping@ietf.org>; Fri, 8 Mar 2002 16:35:28 +0200 (EET)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T598333a404ac158f21081@esvir01nok.ntc.nokia.com> for <sipping@ietf.org>; Fri, 8 Mar 2002 16:34:48 +0200
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779); Fri, 8 Mar 2002 16:34:48 +0200
Received: from trebe003.NOE.Nokia.com ([172.22.232.175]) by esebe013.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966); Fri, 8 Mar 2002 16:34:48 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Fri, 08 Mar 2002 16:34:48 +0200
Message-ID: <DED1F2C6CE07FA498D7AD0CCAC03401B0C2A01@trebe003.NOE.Nokia.com>
Thread-Topic: P-headers in 3GPP
Thread-Index: AcHGrm/QfQRqYDKXEdaaNwAQpJJIjw==
To: sipping@ietf.org
X-OriginalArrivalTime: 08 Mar 2002 14:34:48.0820 (UTC) FILETIME=[666E5340:01C1C6AE]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id JAA05922
Subject: [Sipping] P-headers in 3GPP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit
Hi, As I understood from draft-tsvarea-sipchange-01, the process to define P-headers is the following: - an individual I-D shall be written to describe the actual P-header, syntax, usage, etc. - a designated expert will review the I-D and check whether it meets the requirements described in the sipchange draft. - if the requirements are met, the reviewer informs IESG about the decision, and the I-D can become an (individual or WG) informational RFC. - the P-headers shall be also registered with IANA. (is this the final step?) My question is about the duration of this process. If 3GPP starts to define now couple of P-3GPP-... headers by publishing an I-D, what is the chance that 3GPP can include and reference them in its specifications in June? Thanks and Regards, Krisztian _______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP
- [Sipping] P-headers in 3GPP krisztian.kiss
- Re: [Sipping] P-headers in 3GPP Dean Willis