Re: [Sip] Need for RPH in SIP Responses

Jeroen van Bemmel <jbemmel@zonnet.nl> Wed, 21 November 2007 21:14 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 1Iuwtu-0003bL-7P; Wed, 21 Nov 2007 16:14:26 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Iuwtr-0003Cw-Fq for sip-confirm+ok@megatron.ietf.org; Wed, 21 Nov 2007 16:14:23 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iuwtq-00038b-Vp for sip@ietf.org; Wed, 21 Nov 2007 16:14:23 -0500
Received: from smtp1.versatel.nl ([62.58.50.88]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iuwtq-0001Ot-Hq for sip@ietf.org; Wed, 21 Nov 2007 16:14:22 -0500
Received: (qmail 23613 invoked by uid 0); 21 Nov 2007 21:15:23 -0000
Received: from ip198-11-212-87.adsl2.versatel.nl (HELO [192.168.1.6]) ([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>) by smtp1.versatel.nl (qmail-ldap-1.03) with SMTP for < >; 21 Nov 2007 21:15:23 -0000
Message-ID: <47449FA0.6050904@zonnet.nl>
Date: Wed, 21 Nov 2007 22:14:08 +0100
From: Jeroen van Bemmel <jbemmel@zonnet.nl>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: "Sandesara, Niranjan B" <nsandesa@telcordia.com>
Subject: Re: [Sip] Need for RPH in SIP Responses
References: <A09345776B6C7A4985573569C0F3004318E7A558@rrc-dte-exs01.dte.telcordia.com>
In-Reply-To: <A09345776B6C7A4985573569C0F3004318E7A558@rrc-dte-exs01.dte.telcordia.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
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>
Errors-To: sip-bounces@ietf.org

Niranjan,

> As has been pointed out earlier, possible security risk of permitting 
> RPH in SIP responses is minimal in managed IP networks where this 
> capability is generally expected to be used.
>
For this argument to apply, the element sending the RPH header in a 
response and the element acting on it should both be in the same domain. 
In other words you are talking about a closed system, a very specific 
environment. The use of this header in this way then clearly does not 
apply to the Internet; the proper way to standardize this is as a 
P-header (instead of taking a header which is already defined in a 
"approved-for-the-Internet" RFC, and modifying its allowed use to 
accommodate for a non-Internet use)

Regards,
Jeroen


_______________________________________________
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