R: R: R: [Sip] a question about IETF draft location conveyance 09

"daniel grotti" <daniel.grotti@unibo.it> Sat, 24 November 2007 11:38 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 1IvtKq-0001Gt-Is; Sat, 24 Nov 2007 06:38:08 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IvtKp-0001CJ-4G for sip-confirm+ok@megatron.ietf.org; Sat, 24 Nov 2007 06:38:07 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvtKo-0001AW-4U for sip@ietf.org; Sat, 24 Nov 2007 06:38:06 -0500
Received: from poster3.unibo.it ([137.204.24.100]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IvtKn-0001Ka-Jf for sip@ietf.org; Sat, 24 Nov 2007 06:38:06 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by poster3.unibo.it (Postfix) with ESMTP id 58A2A2FE; Sat, 24 Nov 2007 12:38:04 +0100 (CET)
Received: from EXBK03 (unknown [137.204.25.211]) by poster3.unibo.it (Postfix) with ESMTP id EBE49167; Sat, 24 Nov 2007 12:37:55 +0100 (CET)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: R: R: R: [Sip] a question about IETF draft location conveyance 09
Date: Sat, 24 Nov 2007 12:37:55 +0100
Message-ID: <A30B7FF9263D5340AD5DECB88A243C42015FEE69@EXBK03.personale.dir.unibo.it>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: R: R: [Sip] a question about IETF draft location conveyance 09
Thread-Index: AcguOftcpiqOEOUgQ9WPkSnSiLbCzAAU0NU1
References: <4742BDF5.9040302@unibo.it> <XFE-SJC-212qXLFfJNw000012bf@xfe-sjc-212.amer.cisco.com> <p06240607c36a38613297@[67.169.50.136]> <XFE-SJC-211EAOeIiGX000013f8@xfe-sjc-211.amer.cisco.com> <p06240608c36a4849ecf3@[67.169.50.136]> <XFE-SJC-212AOmAfjuU000013bb@xfe-sjc-212.amer.cisco.com> <p0624060ac36a6ec4f1c2@[67.169.50.136]> <A30B7FF9263D5340AD5DECB88A243C42015FEE65@EXBK03.personale.dir.unibo.it> <4745BDC7.30003@gmx.net> <A30B7FF9263D5340AD5DECB88A243C42015FEE67@EXBK03.personale.dir.unibo.it> <A3636D5F-1B88-4C38-8091-F083AD517D47@softarmor.com>
From: daniel grotti <daniel.grotti@unibo.it>
To: Dean Willis <dean.willis@softarmor.com>
X-Virus-Scanned: Cineca AppOs 1.00 at poster3.unibo.it
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: IETF SIP List <sip@ietf.org>, "James M. Polk" <jmpolk@cisco.com>
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

I know. 
May be SHOULD NOT instead MUST NOT could be better.

daniel


----------------------------------
       Daniel  Grotti
D.E.I.S. - University of Bologna
----------------------------------
       Via Venezia, 52
  47023 Cesena (FC) - ITALY
----------------------------------
e-mail: daniel.grotti@unibo.it
---------------------------------- 



-----Messaggio originale-----
Da: Dean Willis [mailto:dean.willis@softarmor.com]
Inviato: sab 24/11/2007 2.32
A: daniel grotti
Cc: Hannes Tschofenig; IETF SIP List; James M. Polk
Oggetto: Re: R: R: [Sip] a question about IETF draft location conveyance 09
 

On Nov 22, 2007, at 12:08 PM, daniel grotti wrote:

> Hi all,
> so why don't emphasize this point in the next draft, saying :  
> "Proxy server MUST not read messages with "recipient=endpoint"  
> paramenter setted".
> This is my point of you.
>
>


because from a security standpoint, this prohibition is meaningless.  
Intermediate nodes can and will read anything that's in plaintext,  
and SOMEBODY will come up with a rationale, in some context or  
another, for doing so.

And has been pointed out, doing so does not appear to create a  
compatibility problem. It doesn't break the protocol. It might defeat  
security-through-obscurity. It might be rude, or otherwise socially  
unacceptable. But those don't qualify for a MUST level protocol  
prohibition.

--
Dean




_______________________________________________
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