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

Tom Herbert <tom@herbertland.com> Thu, 21 July 2016 13:28 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 3C3CE126FDC for <spud@ietfa.amsl.com>; Thu, 21 Jul 2016 06:28:59 -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 tRAPNIdLM4O9 for <spud@ietfa.amsl.com>; Thu, 21 Jul 2016 06:28:58 -0700 (PDT)
Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (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 DD96812B076 for <spud@ietf.org>; Thu, 21 Jul 2016 06:28:57 -0700 (PDT)
Received: by mail-it0-x234.google.com with SMTP id u186so14122127ita.0 for <spud@ietf.org>; Thu, 21 Jul 2016 06:28:57 -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; bh=5Dvjryy1MbyNPyDKSj/eqTjgPfJqw+dzvQcMAjjQecA=; b=0AtAidZfTzwP0gW9Qy7kPaTo7d+PGOGsTHHzG67tbHEKzG34QmxBXnDz3jS61ERrbZ 25LgRAl4Kn5NU1WMBPPPcylYHjrXdGmVFM+yTmYEIR393Z09E7XKG7MvoLxu+Cwa2sis 9bZPZ3Sy8vMRkZTLAlI2wH3JYbq1ijr+g9vi2lM7FCGfRCOSHBuH95CDc4ZlenTRnjj4 bAz85/iAHnhlBRGRYtkj/MEOUqV7M9C5cFELN/LZ+XPYNTUh+o+wTyHt4ut1yg1r2nr9 JikDnymxyuB/hwmz2lijWDPWWxT1sCIk4y/y4QYGC55RpnN80KvmFuTUwnzS0gMGw+vd kLOA==
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; bh=5Dvjryy1MbyNPyDKSj/eqTjgPfJqw+dzvQcMAjjQecA=; b=K39KNTGGsG54djeGEfcNnFLUnTfGgLB6MiqPiHnOBmcBzX3dTh/6JHa6B6hW/5atRY quxEQuN/P7er3BHsZHPIHujCqh7NYsJr4tRjG/5QdVCkgrJAkLt3cYbSW/s7EkdO8QKm oGuiLb2sQIA39u1CH5qruqqWiNUJWrzDhgEPf4bSkKQaXdDqRc0lSnvQXBW9IljlJ0vC 1a61ElnDJNY1IAYa4U4HdrGVbETG3rVO9ipamAkw4t6XSeVoxqd2bLiKmcCM4wJ1swPf gWs3ZAEnAKatsDMaPA8QABIALq4nkYhhWHzyFKoBTb/u+Ytlkmzm+8OxkIrQ4kVgqjmg T/5g==
X-Gm-Message-State: ALyK8tIcw6+8RT5LT9xwjnrPtq97eW4tkZuXg1qnL0Vbq0ZOupVWDC18M1jVU73EAMQkIrcsiLVYAEFKT3/FwQ==
X-Received: by 10.36.14.193 with SMTP id 184mr12680338ite.91.1469107736602; Thu, 21 Jul 2016 06:28:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.31.134 with HTTP; Thu, 21 Jul 2016 06:28:56 -0700 (PDT)
In-Reply-To: <43a39476-9327-87ef-204c-d7c614a80669@tele.no>
References: <43a39476-9327-87ef-204c-d7c614a80669@tele.no>
From: Tom Herbert <tom@herbertland.com>
Date: Thu, 21 Jul 2016 15:28:56 +0200
Message-ID: <CALx6S34edZbOpfeQr0Z5P90AydtFubxvcMBQpDq8r+9-1o1AYQ@mail.gmail.com>
To: Frode Kileng <frodek@tele.no>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/spud/nNicl808vVWpCpzT7rgVrqhk_F8>
Cc: spud <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: Thu, 21 Jul 2016 13:28:59 -0000

> That said, PLUS may be an enabler for mobile network management practices,
> for example a 1-bit latency/throughput prioritization indicator.
>
Doesn't DSCP/TOS already provide that?

Tom