Re: [Sipping] draft-elwell-sipping-update-pai-02
Cullen Jennings <fluffy@cisco.com> Mon, 03 December 2007 06:00 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 1Iz4MA-0001q5-H0; Mon, 03 Dec 2007 01:00:38 -0500
Received: from sipping by megatron.ietf.org with local (Exim 4.43) id 1Iz4M8-0001pN-HT for sipping-confirm+ok@megatron.ietf.org; Mon, 03 Dec 2007 01:00:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iz4M8-0001pF-6n for sipping@ietf.org; Mon, 03 Dec 2007 01:00:36 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iz4M6-0005Cq-0i for sipping@ietf.org; Mon, 03 Dec 2007 01:00:36 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 02 Dec 2007 22:00:33 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id lB360XRF000500; Sun, 2 Dec 2007 22:00:33 -0800
Received: from [130.129.86.243] (sjc-vpn3-316.cisco.com [10.21.65.60]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id lB360X75014188; Mon, 3 Dec 2007 06:00:33 GMT
In-Reply-To: <CA8EB93B28BD0F4C88392699600BD65502E83048@xmb-rtp-211.amer.cisco.com>
References: <CA8EB93B28BD0F4C88392699600BD65502E83048@xmb-rtp-211.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <C5DB3565-5575-42F9-80E7-8399FB43BC52@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sipping] draft-elwell-sipping-update-pai-02
Date: Sun, 02 Dec 2007 21:39:24 -0800
To: Jonathan Rosenberg <jdrosen@cisco.com>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1764; t=1196661633; x=1197525633; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Re=3A=20[Sipping]=20draft-elwell-sipping-update-pai-02 |Sender:=20; bh=dcaJ1gYVAA3qzWnkbXwjbKfOigl+gGe4TY/dvyxpT1U=; b=g3zQJH7ufXHXYWeWmfKMIcni7IZBOzXjbO6DDgo/kfzA68nyDhBdnxllLuCOL4olRTpzDkx8 52jtZ0ZfXsLA92ElxFvG13ac0NQwMJMCB+sdlLSk92CEdcct7ePxINMG;
Authentication-Results: sj-dkim-3; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: sipping <sipping@ietf.org>, "Elwell, John" <john.elwell@siemens.com>
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>
Errors-To: sipping-bounces@ietf.org
Ok, I just went and read hitchhiker again and saw it defines Core: The essential SIP specifications that are expected to be utilized for every session or registration. well I find this really scary in the same way that I find sipping-16 scary. If we view that we are going to start seeing RFP that ask for all of "core SIP" as defined in hitchhikers, then this document is getting very much the wrong level of review and would probably would better be a BCP. I was under the impression these were more arranged in a way of just grouping into logical categories to help find them without making a value judgement about what RFC were needed and what was not. On Dec 2, 2007, at 3:54 PM, Jonathan Rosenberg (jdrosen) wrote: > 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
- [Sipping] draft-elwell-sipping-update-pai-02 Cullen Jennings
- RE: [Sipping] draft-elwell-sipping-update-pai-02 Elwell, John
- Re: [Sipping] draft-elwell-sipping-update-pai-02 Cullen Jennings
- RE: [Sipping] draft-elwell-sipping-update-pai-02 DRAGE, Keith (Keith)
- Re: [Sipping] draft-elwell-sipping-update-pai-02 Jonathan Rosenberg (jdrosen)
- Re: [Sipping] draft-elwell-sipping-update-pai-02 Cullen Jennings