IETF Logo Mail Archive

Re: [Spud] endpoint control

Tom Herbert <tom@herbertland.com> Tue, 28 June 2016 17:37 UTC

Return-Path: <tom@herbertland.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 1742212D616 for <spud@ietfa.amsl.com>; Tue, 28 Jun 2016 10:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
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 W8jPP666noJY for <spud@ietfa.amsl.com>; Tue, 28 Jun 2016 10:37:07 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B44E12D5E9 for <spud@ietf.org>; Tue, 28 Jun 2016 10:37:07 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id g13so23263648ioj.1 for <spud@ietf.org>; Tue, 28 Jun 2016 10:37:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=BzCMREslIbuonXM5WctIL6nD2KK6XjjuHprbh7IECNw=; b=cOvfKOxIUXH3/8SBh9ut2vlUKvLJNCun/HiUbACjwB6igbbVKiw7cMlQLOqfCfMSKp lLb5pKXuFQ3mEQV3VxcdHAE25trO0v3fpGvEj3W7ggPYGF47l9L5O+IjBh91Z/l3wdvb YD0YOS/43EGUOCZFTdqRYOX6Wi+jRao1Sfu4B7N2QQIAclJuiVVKLcEcKDcMdDKUI6zm xeyj+avVZg9l7o5GTCZHYE5h7oGehi7rnklJx1riIvhXENqJ2ZDlXlmxSaASH+Mh3Rlw HAUQm0L1XXxsi1NFfVSpiUD3MbxlvYnayHQ0ZPGY+cTMEgje6YG1vFLny+4hg7K39T/S kryw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=BzCMREslIbuonXM5WctIL6nD2KK6XjjuHprbh7IECNw=; b=Lch9dm2rXIRK7zOplrhZREkIGDbfTDnUdunjQ58vofmO0XdrqLDGmsijPKAYe5Rh5a pv1UPiB3i1PMaGX1/CEAI7nbLwf/l0j2LIAfn2BBziplb3tuUFv6f72OJSnp8FancGcn o4Kl97Aim66niYaJziNxNQLJEpWxUvNdcPNNVeSB4lscRZmjKDg29Nvlcj966F7uOTUS sv8DtwuJOXRO4G6F1a+1/f0kIJ+9pRXK+g6H+SGYFTfIyIIUvcXS10UwMba81ndkzN5t Kf/wE2YTXdgrejOo38S8TgjOkXO6kHJDdLs5znyDVrFHLiue6KkY8OWGTt1zOWjnvLtH OcZg==
X-Gm-Message-State: ALyK8tLrk/11jVRFk7HzYeS/UH5n8naOqq7JpxBsAHGKZQzqesgdaVx7CFF3Wo3bIPIp7+/glrpI07CIHgYtpQ==
X-Received: by 10.107.11.26 with SMTP id v26mr5410022ioi.107.1467135426574; Tue, 28 Jun 2016 10:37:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.31.134 with HTTP; Tue, 28 Jun 2016 10:37:06 -0700 (PDT)
In-Reply-To: <A4BAAB326B17CE40B45830B745F70F10EE37ACAE@VOEXM17W.internal.vodafone.com>
References: <A4BAAB326B17CE40B45830B745F70F10EE37ACAE@VOEXM17W.internal.vodafone.com>
From: Tom Herbert <tom@herbertland.com>
Date: Tue, 28 Jun 2016 10:37:06 -0700
Message-ID: <CALx6S35DbFk5ZXUf0ob+hziPb1d5xjZvGADP_g-rw=EYKbPOvw@mail.gmail.com>
To: "Smith, Kevin, (R&D) Vodafone Group" <Kevin.Smith@vodafone.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/spud/o4Dk3u_YzBlq6TOQO4SRtBN5tiI>
Cc: "Brian Trammell (ietf@trammell.ch)" <ietf@trammell.ch>, "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 17:37:09 -0000

On Tue, Jun 28, 2016 at 3:41 AM, Smith, Kevin, (R&D) Vodafone Group
<Kevin.Smith@vodafone.com> wrote:
> Hi Brian,
>
> I think Mobile Throughput Guidance would be a good candidate for PLUS path-to-endpoint signalling. The latest (albeit expired) MTG draft [1] is bound to TCP Options, and was considering use of TCP-AO for authentication; PLUS could allow MTG for both TCP and UDP-based flows. However it seems that proposed PLUS mechanism:
>
>>(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? Or would such an authentication/integrity check applicable to path data be in scope of PLUS?
>
> Cheers,
> Kevin
> Vodafone R&D
>
> [1] https://www.ietf.org/archive/id/draft-flinck-mobile-throughput-guidance-03.txt , expired
>
Hi Kevin,

That is an interesting use case. Do you see any reason (other than
maybe current deployability) that these can't be done in HBH options
instead of TCP options?

Thanks,
Tom


> _______________________________________________
> Spud mailing list
> Spud@ietf.org
> https://www.ietf.org/mailman/listinfo/spud

v2.23.0 | Report a Bug | By Email