Re: [Spud] Additional SPUD use-cases

gorry@erg.abdn.ac.uk Wed, 18 March 2015 17:13 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: spud@ietfa.amsl.com
Delivered-To: spud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49E381A8771 for <spud@ietfa.amsl.com>; Wed, 18 Mar 2015 10:13:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 IMMavV-Zlty6 for <spud@ietfa.amsl.com>; Wed, 18 Mar 2015 10:13:47 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 3AB641A8769 for <spud@ietf.org>; Wed, 18 Mar 2015 10:13:47 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id BDC3B1B00510; Wed, 18 Mar 2015 17:14:00 +0000 (GMT)
Received: from 139.133.204.3 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Wed, 18 Mar 2015 17:13:17 -0000
Message-ID: <9b0c6afc92491c6dfe1b1401c02aa162.squirrel@erg.abdn.ac.uk>
In-Reply-To: <CAD62q9WRVazAO5QNGbaLwVuesSHrASYVwY5W7A+UACY9x0G1BQ@mail.gmail.com>
References: <B57E4F68-A0C6-44D8-A729-47B1BED309C9@cisco.com> <CA+9kkMB4kfmMuR61aAhHLzrhEK37dEqy9cpdaqdtzpuyoCbBfg@mail.gmail.com> <CE03DB3D7B45C245BCA0D24327794936412E51@MX104CL02.corp.emc.com> <CAD62q9WRVazAO5QNGbaLwVuesSHrASYVwY5W7A+UACY9x0G1BQ@mail.gmail.com>
Date: Wed, 18 Mar 2015 17:13:17 -0000
From: gorry@erg.abdn.ac.uk
To: "Aaron Falk" <aaron.falk@gmail.com>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/jP53QczILWlcVs0m06wm9eGnvkM>
Cc: "Pal Martinsen \(palmarti\)" <palmarti@cisco.com>, "Black, David" <david.black@emc.com>, Ted Hardie <ted.ietf@gmail.com>, "spud@ietf.org" <spud@ietf.org>
Subject: Re: [Spud] Additional SPUD use-cases
X-BeenThere: spud@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 18 Mar 2015 17:13:49 -0000

David & I  approved the talk as a presentation of current research.

My own hopes are that this talk focusses on:

- the existing experiments and running code, showing how this handles
congestion-control.
- Actual gains of a L2-enhanced approach, such as this, compared to a
mechanism such as ECN.
- How to handle speed-increases, previous attempts at explicit signals for
speed increases at the IETF have all failed to progress. I am dubious that
this signal is useful for a shared capacity bearer.
- Explain the security requirements and model (which I do not understand).
- Help understand if this useful outside of a single-bottleneck radio
network.

To avoid any confusion: This is an individual submission expected to start
a discussion, this draft will not be considered as a candidate for
adoption at this meeting.

Gorry

> On Mon, Mar 16, 2015 at 5:02 PM, Black, David <david.black@emc.com> wrote:
>
>>  Here are four potentially related drafts:
>>
>>
>>
>> -- Rate Adaptation based on network feedback, and (to some extent) FCFS
>> (weak) admission control:
>>
>>
>>
>> This work is TCP based, but with similar goals:
>>
>>
>>
>>
>> https://datatracker.ietf.org/doc/draft-sprecher-mobile-tg-exposure-req-arch/
>>
>> https://datatracker.ietf.org/doc/draft-flinck-mobile-throughput-guidance/
>>
>>
>>
>> The latter draft is (IMHO) better viewed as a proof-of-concept
>> demonstration that this can work, as opposed to a specific protocol
>> design
>> for how to do it.  Design concerns have been raised about what was done
>> there (e.g., aggressive use of TCP options).
>>
>
> Hi David-
>
> Are the congestion control concerns being discussed within a working
> group?
>
> --aaron
> _______________________________________________
> Spud mailing list
> Spud@ietf.org
> https://www.ietf.org/mailman/listinfo/spud
>