Re: [Sip] Need for RPH in SIP Responses
Janet P Gunn <jgunn6@csc.com> Wed, 28 November 2007 22:01 UTC
Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxUy2-0004h3-Hc; Wed, 28 Nov 2007 17:01:14 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IxUy0-0004gh-Tj for sip-confirm+ok@megatron.ietf.org; Wed, 28 Nov 2007 17:01:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxUy0-0004gZ-Jn for sip@ietf.org; Wed, 28 Nov 2007 17:01:12 -0500
Received: from mail171.messagelabs.com ([216.82.253.243]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IxUxz-0005zi-CI for sip@ietf.org; Wed, 28 Nov 2007 17:01:12 -0500
X-VirusChecked: Checked
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-7.tower-171.messagelabs.com!1196287266!12961543!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [20.137.2.88]
Received: (qmail 22210 invoked from network); 28 Nov 2007 22:01:07 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-7.tower-171.messagelabs.com with AES256-SHA encrypted SMTP; 28 Nov 2007 22:01:07 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (Switch-3.3.0/Switch-3.3.0) with ESMTP id lASM1K6I010952; Wed, 28 Nov 2007 17:01:20 -0500
In-Reply-To: <B1428F6F-3BD5-49B4-8475-47C31399D531@g11.org.uk>
To: ken carlberg <carlberg@g11.org.uk>
Subject: Re: [Sip] Need for RPH in SIP Responses
MIME-Version: 1.0
X-Mailer: Lotus Notes 652HF83 November 04, 2004
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF58AD3FC8.97E806C6-ON852573A1.0078C9EA-852573A1.0078F2BD@csc.com>
Date: Wed, 28 Nov 2007 17:01:03 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 7.0.2FP1 HF180|March 29, 2007) at 11/28/2007 05:01:23 PM, Serialize complete at 11/28/2007 05:01:23 PM
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: sip@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1140227858=="
Errors-To: sip-bounces@ietf.org
Ken, Could you expand on these other use cases, and how they would benefit from RPH in responses? Thanks Janet ken carlberg <carlberg@g11.org.uk> wrote on 11/27/2007 11:04:44 AM: > Janet, > > sorry for the tardy comments on the thread. when I read the draft, a > couple of other use cases outside of the GETS model came to mind that > would seem to prompt a need for an R-P header in a SIP response. In > the land mobile radio arena, we have bridging architectures/ > technologies like the ISSI that use SIP as a foundation to bridge > autonomous subnets of P25 systems. These tend to be resource > constrained systems of multi-level precedence, and so having a > corresponding R-P header in SIP responses would fold in nicely with > what is being built today and planned for the near future. > > outside of that, there are also some efforts to bridge ISSI with Push- > to-talk over Cellular (PoC) with SIP, though this is quite preliminary > so I don't know if I'd list this as another use case. But in any > event, I think it would be helpful if you could broaden the problem > statement in your draft so that it is not strictly focused to just > GETS. Subsequent to this broader statement, you could then provide a > more in-depth discussion of the GETS *example*. > > also, is it your plan to progress your draft in the SIPPING WG given > that it deals with a requirement? I see its on the SIP agenda along > with James' related draft, which is helpful, but I assume that further > progress would be shifted to SIPPING. > > -ken >
_______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- Re: [Sip] Need for RPH in SIP Responses ken carlberg
- [Sip] Need for RPH in SIP Responses Sandesara, Niranjan B
- Re: [Sip] Need for RPH in SIP Responses Jeroen van Bemmel
- RE: [Sip] Need for RPH in SIP Responses DOLLY, MARTIN C, ATTLABS
- Re: [Sip] Need for RPH in SIP Responses Jeroen van Bemmel
- RE: [Sip] Need for RPH in SIP Responses DRAGE, Keith (Keith)
- Re: [Sip] Need for RPH in SIP Responses Joel M. Halpern
- RE: [Sip] Need for RPH in SIP Responses DRAGE, Keith (Keith)
- [Sip] Need for RPH in SIP Responses Sandesara, Niranjan B
- Re: [Sip] Need for RPH in SIP Responses Janet P Gunn
- Re: [Sip] Need for RPH in SIP Responses ken carlberg