Re: [aqm] Updated draft-ietf-aqm-ecn-benefits - comments still welcome

Dave Taht <dave.taht@gmail.com> Wed, 18 March 2015 17:45 UTC

Return-Path: <dave.taht@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82A001A8776 for <aqm@ietfa.amsl.com>; Wed, 18 Mar 2015 10:45:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 MHvKo1VeYRYD for <aqm@ietfa.amsl.com>; Wed, 18 Mar 2015 10:45:32 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (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 512321A1B5E for <aqm@ietf.org>; Wed, 18 Mar 2015 10:45:32 -0700 (PDT)
Received: by oier21 with SMTP id r21so42959333oie.1 for <aqm@ietf.org>; Wed, 18 Mar 2015 10:45:31 -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=S0ECA1aP57dSVPeFUpwqZfRBup7GiZvm6mwo92IxIS8=; b=KxJj68GwqgBWStNf11rQh7+X7TXv9EAx4u+1/x60u2S21/wLhGcZQ7XHvV1CccCARl KteoXaFxyGdAv4eZ2PrXQEbfTnkQijjzbHZUsZIqdpVL4uENbin208xQdetDJlVCSWxR +D9Nkd6D9EVk27Jko+TD3SHOT0XP62bfJsZXwhZ9QRqDNwQbZEJFXMdC5SVqpyafeQC0 agorga1xOJvE55fV1XHt5/Rss4+4d9V+335TNeqicmYk+01EmJntjm6sbIjgXqAWnymR mkyzS+iuR4D6cYE5lAFYRV/Ubn5G98kKPkshzxwjRrEhSKk/FY9ppMO/CPUseVDzRCO7 C6Gg==
MIME-Version: 1.0
X-Received: by 10.202.62.70 with SMTP id l67mr55667254oia.59.1426700731862; Wed, 18 Mar 2015 10:45:31 -0700 (PDT)
Received: by 10.202.51.66 with HTTP; Wed, 18 Mar 2015 10:45:31 -0700 (PDT)
In-Reply-To: <a4dc09801ccd09db5350c2eb8a31f216.squirrel@erg.abdn.ac.uk>
References: <a4dc09801ccd09db5350c2eb8a31f216.squirrel@erg.abdn.ac.uk>
Date: Wed, 18 Mar 2015 10:45:31 -0700
Message-ID: <CAA93jw74Vr3bhzJcm7WHD2DSFPiMCqQoP5Eimr2due4GJUNPdQ@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Content-Type: multipart/alternative; boundary=001a113ce09a52d5ba051193a6f8
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/b5Q-FAA6wFfE2bTf7aVkWsocOKg>
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] Updated draft-ietf-aqm-ecn-benefits - comments still welcome
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Mar 2015 17:45:34 -0000

section 6 addition. (could use more verbiage)

6.3 "An AQM that is ECN aware MUST have overload protection.

It is trivial for a malbehaved application/worm/bot to mark all it's
packets with ECN and thus gain priority over other traffic not ecn marked.

6.4  Enabling ECN at the application layer requires access to the IP header
fields, which are usually
       abstracted out completely at the tcp layer, and hard to access from
udp with multiple non-portable
       methods to do so. ECN over UDP in new applications such as webrtc
and Quic has great potential for
       many other applications, however the same care of design that went
into ECN on TCP needs to go
       into future UDP based protocols.

Some other section that may end up here?

ECN marking other sorts of flows (example routing packets) that have a
higher priority than other flows on link-local packets may be of benefit
with wider availability of aqm technologies that are ecn aware...




On Wed, Mar 18, 2015 at 8:49 AM, <gorry@erg.abdn.ac.uk> wrote:

> Chairs, WG,
>
> Thanks for all people who emailed me on and off list.
>
> Apologies to be editing when we supposed to be in reading mode prior to
> the IETF (!!). However, since this seems to me to be useful, I continue.
>
> I have updated the "unpublished" current version - this is ready for
> upload (including minor corrections):
>
> www.erg.abdn.ac.uk/users/gorry/ietf/AQM/draft-ietf-aqm-ecn-benefits-01.txt
> www.erg.abdn.ac.uk/users/gorry/ietf/AQM/draft-ietf-aqm-ecn-benefits-01.xml
>
> Since some people have already shown an interest in Wes's proposal to
> restructure the thinking on deployment pitfalls, I've also started a
> second new version that rolls all the previous corrections together and
> also starts to apply this change. This version is still being updated, and
> is here:
>
> www.erg.abdn.ac.uk/users/gorry/ietf/AQM/draft-ietf-aqm-ecn-benefits-02.txt
> www.erg.abdn.ac.uk/users/gorry/ietf/AQM/draft-ietf-aqm-ecn-benefits-02.xml
>
> If you wish to add comments - please do send. I still plan to roll more
> corrections into rev -02, and then upload both revisions as soon as the ID
> archives open again.
>
> Best wishes,
>
> Gorry (& MIchael)
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>



-- 
Dave Täht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb