IETF Logo Mail Archive

Re: [Spud] endpoint control

"Fossati, Thomas (Nokia - GB)" <thomas.fossati@nokia.com> Tue, 28 June 2016 10:59 UTC

Return-Path: <thomas.fossati@nokia.com>
X-Original-To: spud@ietfa.amsl.com
Delivered-To: spud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9089612D0DB for <spud@ietfa.amsl.com>; Tue, 28 Jun 2016 03:59:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RTNyLOn04h40 for <spud@ietfa.amsl.com>; Tue, 28 Jun 2016 03:59:45 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE90C12DC8E for <spud@ietf.org>; Tue, 28 Jun 2016 03:59:43 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id C4BADEB7C98B5; Tue, 28 Jun 2016 10:59:39 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u5SAxeOB009905 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 28 Jun 2016 10:59:41 GMT
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u5SAxJFR015252 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 Jun 2016 12:59:39 +0200
Received: from FR711WXCHMBA08.zeu.alcatel-lucent.com ([169.254.4.136]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Tue, 28 Jun 2016 12:59:33 +0200
From: "Fossati, Thomas (Nokia - GB)" <thomas.fossati@nokia.com>
To: "Smith, Kevin, (R&D) Vodafone Group" <Kevin.Smith@vodafone.com>, "Brian Trammell (ietf@trammell.ch)" <ietf@trammell.ch>
Thread-Topic: [Spud] endpoint control
Thread-Index: AdHRKB6Rk1yBi0AtT2GnUMPMbLGi+v//90kA
Date: Tue, 28 Jun 2016 10:59:33 +0000
Message-ID: <D3981609.6AF91%thomas.fossati@alcatel-lucent.com>
References: <A4BAAB326B17CE40B45830B745F70F10EE37ACAE@VOEXM17W.internal.vodafone.com>
In-Reply-To: <A4BAAB326B17CE40B45830B745F70F10EE37ACAE@VOEXM17W.internal.vodafone.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.5.160527
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <236B7823AD8FCC49A93ED588383335E0@exchange.lucent.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spud/FV17GYTWrhcjTW8JS46_d99FtEI>
Cc: "spud@ietf.org" <spud@ietf.org>
Subject: Re: [Spud] endpoint control
X-BeenThere: spud@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Session Protocol Underneath Datagrams <spud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spud>, <mailto:spud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spud/>
List-Post: <mailto:spud@ietf.org>
List-Help: <mailto:spud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spud>, <mailto:spud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jun 2016 10:59:50 -0000

Hi Kevin,

On 28/06/2016 11:41, "Spud on behalf of Smith, Kevin, (R&D) Vodafone
Group" <spud-bounces@ietf.org on behalf of Kevin.Smith@vodafone.com> wrote:
>>(1) For forward signaling, the sending endpoint must place "scratch
>>space" in the packet with a label on it stating that it's okay to
>>modify; this okay-to-modify state is enforced by a MAC which only
>>verifies the length but not the content of the scratch space.
>
>...may not provide the guarantee that (1) the MTG information was indeed
>injected by the cellular network and (2) that it has not been modified by
>another node. Have I got that right?

Yes, you are right.  See also section 5.2 of [1].

Cheers, t

[1] https://www.iab.org/wp-content/IAB-uploads/2015/08/MaRNEW_1_paper_4.pdf

v2.23.0 | Report a Bug | By Email