IETF Logo Mail Archive

Re: [Sipping] draft-elwell-sipping-update-pai-02

"Jonathan Rosenberg (jdrosen)" <jdrosen@cisco.com> Sun, 02 December 2007 23:54 UTC

Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iyydc-0002tT-C0; Sun, 02 Dec 2007 18:54:16 -0500
Received: from sipping by megatron.ietf.org with local (Exim 4.43) id 1Iyyda-0002tG-NW for sipping-confirm+ok@megatron.ietf.org; Sun, 02 Dec 2007 18:54:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iyyda-0002t6-Dp for sipping@ietf.org; Sun, 02 Dec 2007 18:54:14 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IyydZ-0003P1-0J for sipping@ietf.org; Sun, 02 Dec 2007 18:54:14 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 02 Dec 2007 18:54:14 -0500
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id lB2NsC2J030056; Sun, 2 Dec 2007 18:54:12 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id lB2Ns70i026755; Sun, 2 Dec 2007 23:54:12 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 2 Dec 2007 18:54:07 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: Re: [Sipping] draft-elwell-sipping-update-pai-02
Date: Sun, 02 Dec 2007 18:54:06 -0500
Message-ID: <CA8EB93B28BD0F4C88392699600BD65502E83048@xmb-rtp-211.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sipping] draft-elwell-sipping-update-pai-02
Thread-Index: Acg1LMA09DedE4fIS2OZP/EFj6L6LAAEd/en
From: "Jonathan Rosenberg (jdrosen)" <jdrosen@cisco.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "Elwell, John" <john.elwell@siemens.com>
X-OriginalArrivalTime: 02 Dec 2007 23:54:07.0500 (UTC) FILETIME=[A060C4C0:01C8353E]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2765; t=1196639652; x=1197503652; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:=20=22Jonathan=20Rosenberg=20(jdrosen)=22=20<jdrosen@cisco.com> |Subject:=20Re=3A=20[Sipping]=20draft-elwell-sipping-update-pai-02 |Sender:=20 |To:=20=22Cullen=20Jennings=20(fluffy)=22=20<fluffy@cisco.com>, =0A=20=20= 20=20=20=20=20=20=22Elwell,=20John=22=20<john.elwell@siemens.com>; bh=hT3okoM2wKAUThEn9LqQGnhTGh6LwvedwNvXR7a3rA0=; b=QYaDIjsBv+x21V+NHOeiu4tDs3q9SBRhjESwrh/fr0PWxww3cUUpLghlaou/l4Bw1bGe6Bt+ TlWwVStPMGQv9unH1Y7imSg9eDO6DGS/p4JIs/yapZBFzzOkXQ9qX60G;
Authentication-Results: rtp-dkim-2; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1677269463=="
Errors-To: sipping-bounces@ietf.org

3325 is a core spec according to the hitchhikers guide criteria.

Jonathan R




 -----Original Message-----
From: 	Cullen Jennings (fluffy)
Sent:	Sunday, December 02, 2007 04:46 PM Eastern Standard Time
To:	Elwell, John
Cc:	sipping
Subject:	Re: [Sipping] draft-elwell-sipping-update-pai-02


On Nov 30, 2007, at 12:15 AM, Elwell, John wrote:

> On the
> other hand, given that PAI is part of "core SIP", it would make some
> sense for it to be standards track.


Just to keep me on the right path here. When you say "core SIP", how  
would you define that?

Cullen <with my individual hat on>


_______________________________________________
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 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

v2.23.0 | Report a Bug | By Email