Fw: [Sip] draft-gunn-sip-req-for-rph-in-responses-00: What is impact on response?

Janet P Gunn <jgunn6@csc.com> Fri, 23 November 2007 00:28 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 1IvMPE-0000IM-PC; Thu, 22 Nov 2007 19:28:28 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IvMPC-0008Ti-Jz for sip-confirm+ok@megatron.ietf.org; Thu, 22 Nov 2007 19:28:26 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvMPC-0008R6-5t for sip@ietf.org; Thu, 22 Nov 2007 19:28:26 -0500
Received: from mail145.messagelabs.com ([216.82.245.115]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IvMPB-0004e9-JE for sip@ietf.org; Thu, 22 Nov 2007 19:28:26 -0500
X-VirusChecked: Checked
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-10.tower-145.messagelabs.com!1195777704!16015002!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [20.137.2.88]
Received: (qmail 24994 invoked from network); 23 Nov 2007 00:28:24 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-10.tower-145.messagelabs.com with AES256-SHA encrypted SMTP; 23 Nov 2007 00:28:24 -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 lAN0SStl008405 for <sip@ietf.org>; Thu, 22 Nov 2007 19:28:28 -0500
To: sip@ietf.org
Subject: Fw: [Sip] draft-gunn-sip-req-for-rph-in-responses-00: What is impact on response?
MIME-Version: 1.0
X-Mailer: Lotus Notes 652HF83 November 04, 2004
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OFF807CD80.CE569034-ON8525739C.000285D5-8525739C.00029837@csc.com>
Date: Thu, 22 Nov 2007 19:28:20 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 7.0.2FP1 HF180|March 29, 2007) at 11/22/2007 07:26:48 PM, Serialize complete at 11/22/2007 07:26:48 PM
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
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="===============1296902671=="
Errors-To: sip-bounces@ietf.org

Janet P Gunn/FED/CSC wrote on 11/22/2007 03:14:07 PM:

> I just want to point out that, for the use case presented in draft-
> gunn-sip-req-for-rph-in-responses-00, 
> the "priority status of the call target" is not relevant.  Priority 
> treatment is dependant
> entirely on the priority status of the calling party.
> 
> There might be other use case/scenarios which do depend on the 
> priority status of the call target- but not this one.
> 
> Janet

> 
> Dean Willis <dean.willis@softarmor.com> wrote on 11/21/2007 03:14:24 PM:
> 
> > 
> > I'm still struggling with the rph-in-response question. I was hoping 
> > to get some insight from draft-gunn-sip-req-for-rph-in-responses-00, 
> > but I'm still left unclear on a few points.
> > 
> > For the record, this draft adds supporting rationale for draft-polk- 
> > sip-rph-in-responses-00.txt.
> > 
> > I understand from this draft that a node making a call that would 
> > need RPH information might not know what RPH value would apply at the 
> > time the call is launched by sending INVITE. This is because the 
> > priority granted will depend on external factors, including 
> > potentially the priority status of the call target. So we need a way 
> > to inform the network elements along the path (including the UAC) as 
> > to what priority they should grant the call.
> > 
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > 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
_______________________________________________
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