Re: [Spud] No. Operators don't need SPUD for mobile network management

"Fossati, Thomas (Nokia - GB)" <thomas.fossati@nokia.com> Wed, 27 July 2016 06:34 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 6048C12DD45 for <spud@ietfa.amsl.com>; Tue, 26 Jul 2016 23:34:33 -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 1KrczXudQZ-z for <spud@ietfa.amsl.com>; Tue, 26 Jul 2016 23:34:31 -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 7EB4112DCF7 for <spud@ietf.org>; Tue, 26 Jul 2016 23:34:31 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 46BBC2C0C6336; Wed, 27 Jul 2016 06:34:27 +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 u6R6YSBe025606 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 27 Jul 2016 06:34:28 GMT
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u6R6YRlo023552 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 27 Jul 2016 08:34:27 +0200
Received: from FR711WXCHMBA08.zeu.alcatel-lucent.com ([169.254.4.83]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Wed, 27 Jul 2016 08:34:27 +0200
From: "Fossati, Thomas (Nokia - GB)" <thomas.fossati@nokia.com>
To: Tom Herbert <tom@herbertland.com>, "Smith, Kevin, (R&D) Vodafone Group" <Kevin.Smith@vodafone.com>
Thread-Topic: [Spud] No. Operators don't need SPUD for mobile network management
Thread-Index: AQHR59Dr+i1xEn5sN0mq+YBB2mmKsA==
Date: Wed, 27 Jul 2016 06:34:26 +0000
Message-ID: <D3BE1148.6ECDF%thomas.fossati@alcatel-lucent.com>
References: <43a39476-9327-87ef-204c-d7c614a80669@tele.no> <alpine.DEB.2.02.1607211643150.2309@uplift.swm.pp.se> <0f504f66-1df8-e2da-b55a-3e44e67d0912@tele.no> <alpine.DEB.2.02.1607211712500.2309@uplift.swm.pp.se> <3F114FAB-6F70-4908-939C-1DA5661B2113@netapp.com> <alpine.DEB.2.02.1607211724010.2309@uplift.swm.pp.se> <FD62252A-85F2-49A6-ADBF-4F85E9357182@netapp.com> <A4BAAB326B17CE40B45830B745F70F10EE3B01C3@VOEXM17W.internal.vodafone.com> <CALx6S36qGMwaYeE1_2GYnd3sKn1PzBDRtdkcEZN8cmTEJ7BAOA@mail.gmail.com>
In-Reply-To: <CALx6S36qGMwaYeE1_2GYnd3sKn1PzBDRtdkcEZN8cmTEJ7BAOA@mail.gmail.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.6.160626
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0C578D9A3107504B9392E8E441398382@exchange.lucent.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spud/agzVdj3v27RVSA58ornRQ0__zT8>
Cc: Frode Kileng <frodek@tele.no>, Mikael Abrahamsson <swmike@swm.pp.se>, "Eggert, Lars" <lars@netapp.com>, "spud@ietf.org" <spud@ietf.org>
Subject: Re: [Spud] No. Operators don't need SPUD for mobile network management
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: Wed, 27 Jul 2016 06:34:33 -0000

On 27/07/2016 04:05, "Spud on behalf of Tom Herbert"
<spud-bounces@ietf.org on behalf of tom@herbertland.com> wrote:
>On Mon, Jul 25, 2016 at 3:49 AM, Smith, Kevin, (R&D) Vodafone Group
><Kevin.Smith@vodafone.com> wrote:
>> Another operator here:  I like the notion of PLUS being used to hint to
>>the TCP sender regarding network radio cell conditions, i.e. mobile
>>throughput guidance[1].  So network information being sent out to help
>>tune cwnd.
>>
>I am not a big fan of having middleboxes purposely parsing an
>modifying TCP options, but I do like security considerations of mobile
>guidance and hope that PLUS might adopt some of the same concepts.
>Specifically:
>
>"The protocol specified in this document assumes that a trustful
>relationship between the Throughput Guidance Provider and the TCP
>server has been formed"
>
>and
>
>"Throughput guidance is considered confidential information"
>
>and
>
>"The identity of the Mobile Throughput Guidance provider that injects
>the throughput guidance header must be explicitly known to the
>endpoint receiving the information."

These security & privacy considerations are MTG-specific.  If (as I do
wish) MTG is ported to PLUS, MTG will have to define how security &
privacy of its own vocabulary is achieved.

Section 6.3 of draft-trammel-spud-reqs already has text that takes this
scenario into consideration:

   [...] SPUD should support different levels of
   trust than the default ("untrusted, but presumed honest due to
   limitations on the signaling vocabulary") and fully-authenticated;