Re: [Marnew] RFC 6077

Ca By <cb.list6@gmail.com> Thu, 24 September 2015 13:28 UTC

Return-Path: <cb.list6@gmail.com>
X-Original-To: marnew@ietfa.amsl.com
Delivered-To: marnew@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E67A1ACF5E for <marnew@ietfa.amsl.com>; Thu, 24 Sep 2015 06:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.24
X-Spam-Level:
X-Spam-Status: No, score=0.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, SPF_PASS=-0.001] autolearn=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 IFF3wruB-YYX for <marnew@ietfa.amsl.com>; Thu, 24 Sep 2015 06:28:48 -0700 (PDT)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) (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 E50E21ACF5B for <marnew@iab.org>; Thu, 24 Sep 2015 06:28:47 -0700 (PDT)
Received: by wicfx3 with SMTP id fx3so28108433wic.1 for <marnew@iab.org>; Thu, 24 Sep 2015 06:28:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zdrQ3UNIgFmvfucp5AKbUhdJ8rUc8ILVoGT+20YfxSE=; b=Q7AKHUbV6SABP/VVRav9AtKqsZ4ctb9MXHGMECxINDQ+jGrT9rax+afL/26M98moTc uNiiPFv3mILTv8y8gpoyf4/1Vyp0Kd00YqG7o9HUVgiCYbSiHwfsdG1fi3872fR68/SK biQUUdjdlibNF9lsCDQ8p07OHT46YPjKm8cXO7X/35elDYHvm1YL8iL2wJVcNwj8mLkE GRwwVzyJx7pzaIuK72MG35i38+pR91q7dWOwXmaVmqs5oUneAJQdy0OkwbgZ4SezHBnD YUsD4vr4Ag5UTcK7af2sSKLQUm8aSxb7reqbEz3ggIK9rFlY4M6dDzRILpIn+NzSb5fi QSOQ==
MIME-Version: 1.0
X-Received: by 10.180.8.3 with SMTP id n3mr403608wia.41.1443101326407; Thu, 24 Sep 2015 06:28:46 -0700 (PDT)
Received: by 10.194.192.40 with HTTP; Thu, 24 Sep 2015 06:28:46 -0700 (PDT)
In-Reply-To: <816A185E-0255-46FF-BCBF-6334C43C18B2@fb.com>
References: <655C07320163294895BBADA28372AF5D484CEA55@FR712WXCHMBA15.zeu.alcatel-lucent.com> <1btgnrka8yjoatcenyhh7rj9.1443094482483@email.android.com> <A98526CB-31EA-4CA0-A7CE-F0DA9645AE33@fb.com> <CAD6AjGQdyTRR=19SOTkjq1dm0d+1LRTTLKQNH9S-6wUNgnGZeA@mail.gmail.com> <816A185E-0255-46FF-BCBF-6334C43C18B2@fb.com>
Date: Thu, 24 Sep 2015 06:28:46 -0700
Message-ID: <CAD6AjGSZJfyXfYG=jdHYAzYuNBfppOWybX4BDeov9MJbcQ6sgQ@mail.gmail.com>
From: Ca By <cb.list6@gmail.com>
To: Blake Matheny <bmatheny@fb.com>
Content-Type: multipart/alternative; boundary=f46d04428184ef7d5c05207e35ac
Archived-At: <http://mailarchive.ietf.org/arch/msg/marnew/8PenMEvhvOastI87p6VB3LlDeXQ>
Cc: "marnew@iab.org" <marnew@iab.org>, "Smith, Kevin, \(R&D\) Vodafone Group" <Kevin.Smith@vodafone.com>, "Scharf, Michael \(Michael\)" <michael.scharf@alcatel-lucent.com>
Subject: Re: [Marnew] RFC 6077
X-BeenThere: marnew@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Managing Radio Networks in an Encrypted World <marnew.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/marnew>, <mailto:marnew-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/marnew/>
List-Post: <mailto:marnew@iab.org>
List-Help: <mailto:marnew-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/marnew>, <mailto:marnew-request@iab.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2015 13:28:50 -0000

On Thursday, September 24, 2015, Blake Matheny <bmatheny@fb.com> wrote:

> I don’t think that has to be the case. I’d like to get channel bandwidth,
> allocated channels vs available channels, and a couple of other things from
> the tower. Beyond collecting this
>
>
Why not get it from the ue?

You realize this data will all change before you even receive it? So it
would be no more than a historical record.

Also, there may be privacy concerns here.

Maybe i dont want you to know my location. Everytime the 49ers play at
home, my congestion goes up, you may now infer my location.


> data to better understand global trends, we use similar (less accurate)
> signals for making dynamic decisions (for instance, disable a particular
> feature because conditions look like X).
>
> Just because the signals are ephemeral/dynamic don’t mean they aren’t
> useful. TCP does not provide these hints. Also struct tcp_info is a
> Linuxism and is not widely available across platforms.
>
> -Blake
>
> From: Ca By
> Date: Thursday, September 24, 2015 at 8:49 AM
> To: Blake Matheny
> Cc: "Smith, Kevin, (R&D) Vodafone Group", "Scharf, Michael (Michael)", "
> marnew@iab.org <javascript:_e(%7B%7D,'cvml','marnew@iab.org');>"
> Subject: Re: [Marnew] RFC 6077
>
>
>
> On Thursday, September 24, 2015, Blake Matheny <bmatheny@fb.com
> <javascript:_e(%7B%7D,'cvml','bmatheny@fb.com');>> wrote:
>
>> I’ve asked a couple of vendors for congestion hints in a variety of ways.
>> So far, no luck :) I would really like to see this as well.
>>
>>
>>
> The problem is these hints are too ephemeral and dynamic to be useful.
> Someone turns on a microwave oven and congestion becomes high ....
>
> This just seems to be more signalling without actionable information. I
> belive tcp already provides these hints
>
>
>>
>>
>> On 9/24/15, 7:34 AM, "Marnew on behalf of Smith, Kevin, (R&D) Vodafone
>> Group" <marnew-bounces@iab.org on behalf of Kevin.Smith@vodafone.com>
>> wrote:
>>
>> >Hi Michael,
>> >Thanks for reminding me - Bob Briscoe also recommended 6077, especially
>> when considering the impact of providing congestion hints (namely in the
>> Mobile Throughput Guidance draft). Certainly we need to make sure that such
>> efforts do not merely shift the bottleneck to cause problems elsewhere. So
>> as you say we can review those challenges - if not in detail at the
>> workshop then on the mailing list.
>> >All best
>> >Kevin
>> >
>> >"Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com> wrote:
>> >
>> >
>> >On the MarNew page, I see some ideas related to
>> network-support/network-assisted congestion control. The IRTF has written
>> some time ago RFC 6077, and it could be useful to review the challenges in
>> Section 3.1 therein. Of course, parts of that RFC may be outdated.
>> >
>> >Michael (co-author of RFC 6077)
>> >
>> >_______________________________________________
>> >Marnew mailing list
>> >Marnew@iab.org
>> >
>> https://urldefense.proofpoint.com/v1/url?u=https://www.iab.org/mailman/listinfo/marnew&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=dPSUqzzpoMUu%2B7UN6oQ1DQ%3D%3D%0A&m=sfDv5HORjurZqK2gt%2FlxX1SHIUOTFXmXhNMlEycm9DI%3D%0A&s=287c4a2ca16575e5bb0b89f8a38b2058107aa632016e43ad3d5820b036687265
>> >
>> >_______________________________________________
>> >Marnew mailing list
>> >Marnew@iab.org
>> >
>> https://urldefense.proofpoint.com/v1/url?u=https://www.iab.org/mailman/listinfo/marnew&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=dPSUqzzpoMUu%2B7UN6oQ1DQ%3D%3D%0A&m=sfDv5HORjurZqK2gt%2FlxX1SHIUOTFXmXhNMlEycm9DI%3D%0A&s=287c4a2ca16575e5bb0b89f8a38b2058107aa632016e43ad3d5820b036687265
>> _______________________________________________
>> Marnew mailing list
>> Marnew@iab.org
>> https://www.iab.org/mailman/listinfo/marnew
>> <https://urldefense.proofpoint.com/v1/url?u=https://www.iab.org/mailman/listinfo/marnew&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=dPSUqzzpoMUu%2B7UN6oQ1DQ%3D%3D%0A&m=Jss0283WJ77x215YTlEiFoCnppBsdgDltN16tKkCNn0%3D%0A&s=89899417f5b429204a349b6420a315e537ba5bac6608bfaf44f3af11cc8a1b17>
>>
>