Re: [secdir] secdir review of draft-ietf-simple-msrp-sessmatch

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 09 September 2010 07:12 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B3313A6848; Thu, 9 Sep 2010 00:12:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.57
X-Spam-Level:
X-Spam-Status: No, score=-5.57 tagged_above=-999 required=5 tests=[AWL=1.029, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4yg-KzNDyfAT; Thu, 9 Sep 2010 00:12:54 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 770E23A67CC; Thu, 9 Sep 2010 00:12:53 -0700 (PDT)
X-AuditID: c1b4fb3d-b7b90ae00000278d-b0-4c888910c9ff
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id EE.EC.10125.019888C4; Thu, 9 Sep 2010 09:13:20 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.78]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Thu, 9 Sep 2010 09:13:19 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@estacado.net>, Cullen Jennings <fluffy@cisco.com>
Date: Thu, 9 Sep 2010 09:13:18 +0200
Thread-Topic: secdir review of draft-ietf-simple-msrp-sessmatch
Thread-Index: ActPo1ki8jw9pVdrTjKfKNpVEucoawASmCuw
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05850169444B@ESESSCMS0356.eemea.ericsson.se>
References: <7F2072F1E0DE894DA4B517B93C6A0585015BCA1D@ESESSCMS0356.eemea.ericsson.se> <AANLkTikqkX4iY2nUF1eRYEcpR80pw8A2wXnV1kpfwAZk@mail.gmail.com>, <C3918F74-44C6-4332-9A16-6FDEF6F9A130@cisco.com> <7F2072F1E0DE894DA4B517B93C6A0585015BCA41@ESESSCMS0356.eemea.ericsson.se> <7DA8DA86-792B-44A4-A1AD-8DD6DF3FA985@estacado.net>
In-Reply-To: <7DA8DA86-792B-44A4-A1AD-8DD6DF3FA985@estacado.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "draft-ietf-simple-msrp-sessmatch@tools.ietf.org" <draft-ietf-simple-msrp-sessmatch@tools.ietf.org>, Ted Hardie <ted.ietf@gmail.com>, "secdir@ietf.org" <secdir@ietf.org>, IESG IESG <iesg@ietf.org>, The IETF <ietf@ietf.org>
Subject: Re: [secdir] secdir review of draft-ietf-simple-msrp-sessmatch
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 07:12:56 -0000

Hi,

I think Ben gave my clarification :)

Regards,

Christer



 

> -----Original Message-----
> From: Ben Campbell [mailto:ben@estacado.net] 
> Sent: 9. syyskuuta 2010 1:15
> To: Christer Holmberg; Cullen Jennings
> Cc: draft-ietf-simple-msrp-sessmatch@tools.ietf.org; Ted 
> Hardie; IESG IESG; The IETF; secdir@ietf.org
> Subject: Re: secdir review of draft-ietf-simple-msrp-sessmatch
> 
> (as individual)
> 
> On Sep 2, 2010, at 8:37 AM, Christer Holmberg wrote:
> 
> > Hi Cullen,
> > 
> >> Do these changes allow an SBC on the signaling path to change the 
> >> contents of the MSRP messages without the end points being able to 
> >> detect that? I'm sure it will be easier to answer this 
> once we have a new draft.
> > 
> > Sessmatch does not make it any easier for an SBC in the 
> signalling path to change the content of the MSRP messages. 
> > 
> > For an SBC to do MSRP message modification it will have to 
> implement MSRP B2BUA functionality - no matter if sessmatch 
> is supported by the endpionts or not.
> 
> I'm going to have to push on this one a little bit:
> 
> I think it _does_ make it easier for an SBC to change MSRP 
> messages because it makes it easier for the SBC to put itself 
> into the media path in the first place. This is no different 
> than for any other sort of media.
> 
> The need to implement MSRP b2bUA functionality exists if the 
> SBC changes the To-Path and From-Path headers. It may or may 
> not be required if it wants to change _bodies_, depending on 
> whether that change requires chunk-reassembly or changes the 
> length of the body. And assuming, of course, there is no 
> end-to-end protection on the MSRP messages in the first 
> place--and we all know that in practice there probably won't be.
> 
> I think what Christer is talking about is, if sessmatch did 
> not exist, then if an SBC were to insert itself into the MSRP 
> media path, it would be _forced_ then to rewrite the To-Path 
> and From-Path in each MSRP request to match the change it 
> made in the SDP. If it did not do so, the endpoints would 
> detect the change and treat it as an error. That is, 
> sessmatch does not enable the insertion in the first 
> place--it just makes things cheaper from a processing perspective.
> 
> Note that any end-to-end integrity protection on the SDP, 
> such as RFC4474 or s/mime, will prevent SBC insertion, with 
> or without sessmatch. Just like for any other media.
> 
> 
> > 
> > Regards,
> > 
> > Christer
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> 
>