Re: [aqm] Who supports tsvwg adoption of adding ECN to L2 or tunnel protocols?

Andrew Mcgregor <andrewmcgr@google.com> Mon, 04 November 2013 23:04 UTC

Return-Path: <andrewmcgr@google.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 615BD21E8217 for <aqm@ietfa.amsl.com>; Mon, 4 Nov 2013 15:04:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.084
X-Spam-Level:
X-Spam-Status: No, score=-0.084 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_HTML_USL_OBFU=1.666, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cyGVCT5s8YVI for <aqm@ietfa.amsl.com>; Mon, 4 Nov 2013 15:04:07 -0800 (PST)
Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 38CA021E81C6 for <aqm@ietf.org>; Mon, 4 Nov 2013 15:04:02 -0800 (PST)
Received: by mail-qa0-f48.google.com with SMTP id w8so634156qac.14 for <aqm@ietf.org>; Mon, 04 Nov 2013 15:04:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UgKzNxyw1zcSX2Bv5kGlsO5Fr76M4Ynb/z4RYYwowjc=; b=ZfZ4b0Pb2aOp/FO6O4173sXLhg9F/sU2FUlOS3WmlMxlwyUqJxKqR5cwhEiJ3B+ANO 1kmzEa1DktpwwyIrwBnRrJXuIvOalInzeQedsh3Ckz2FDr4RocJwVaRnkJPdGf7OCPpS WB1sj2xmPrnaC37SrPh79c4ymOh0hoOo2rm2bcI7uN6lrgVGMF/cyVGtjry5DMcP04d6 /QR5tZy5eSQo6EJiYNb7KxdRkjkyM+CIh0rrA4Zqh1aN7YhbXQJk4EUrXwPsg0lTp83V FnaVEISYzPwufdBmDH9wAz5nzp5hXVXCZMcscdCHISgoCoBBq6VNyqZiS2jH87kBAmDf hCzQ==
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:date :message-id:subject:from:to:cc:content-type; bh=UgKzNxyw1zcSX2Bv5kGlsO5Fr76M4Ynb/z4RYYwowjc=; b=Vkin2uNSdRjYRArQLgJXz+4tsM0KEsugcQM1dGb57TkpcO+qAalqa/ohlKR0xEkRti ooAZQfQYpEJL2J9Vu8vOLWPy7T1RibPJlj+FmYWo6kKJWrp9Yk0jnivpLbY5YGK2if8i BCJzbYnuiox82vO9c+hwKIxdpAtB/frQFq8r5nwAN1bCXbwBWyHyqaq+LRRyULCBqCtG 3Qcs+XKkcdcJpGBoWqGbuayCF0+6swnFIo3vfTiPy+sKhz5raAczUR9fMjeoERxSYQ1E JS8MkfYYvMaLLKKw98YkWlQfxyXmTArtGl6r7M23b5P9MubDn3HtWuaYx/Zkf7fkp6pA XZcg==
X-Gm-Message-State: ALoCoQnou5EGibyNaQarpVePYllOiEb3x7mZaPeGgHKom3a1ilJofQg4pwhVxgc09V3Iz9HGUEa8qGbzz6G9AFOqgkY+KiIoC0gduv+H1XnhVEa+YviyXUt2oTsmz726hoYfFUk/mnqB+44cNJSVsY8ukcXlbbhm6SClt5z5pQAN89ygR3z3mdB2v1P7Q6/bBfmmKRZu1ual
MIME-Version: 1.0
X-Received: by 10.224.22.75 with SMTP id m11mr25705540qab.27.1383606241488; Mon, 04 Nov 2013 15:04:01 -0800 (PST)
Received: by 10.224.197.198 with HTTP; Mon, 4 Nov 2013 15:04:01 -0800 (PST)
In-Reply-To: <201311042203.rA4M3lo0026458@bagheera.jungle.bt.co.uk>
References: <201311042203.rA4M3lo0026458@bagheera.jungle.bt.co.uk>
Date: Tue, 05 Nov 2013 10:04:01 +1100
Message-ID: <CAPRuP3kRsoPP2e9+vBjn1xiZ1UWJpc8Ds5VhsggKWa2suj_19Q@mail.gmail.com>
From: Andrew Mcgregor <andrewmcgr@google.com>
To: Bob Briscoe <bob.briscoe@bt.com>
Content-Type: multipart/alternative; boundary="047d7bdc78cc888b7b04ea61eed3"
Cc: Pat Thaler <pthaler@broadcom.com>, John Kaippallimalil <John.Kaippallimalil@huawei.com>, draft-briscoe-tsvwg-ecn-encap-guidelines@tools.ietf.org, tsvwg IETF list <tsvwg@ietf.org>, AQM IETF list <aqm@ietf.org>
Subject: Re: [aqm] Who supports tsvwg adoption of adding ECN to L2 or tunnel protocols?
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 04 Nov 2013 23:04:08 -0000

This seems like valuable work.  One question is, can we put in scope
notification that losses are NOT due to congestion?

Willing to comment and review, at least.


On 5 November 2013 09:03, Bob Briscoe <bob.briscoe@bt.com> wrote:

> Folks,
>
> Pls respond if you support this being adopted as a work-group item in the
> IETF transport services w-g (tsvwg). The WG chairs need visibility of
> interest.
> Even better, if you're willing to read / comment / review / implement
>
> Guidelines for Adding Congestion Notification to Protocols that
> Encapsulate IP
> <http://tools.ietf.org/html/draft-briscoe-tsvwg-ecn-encap-guidelines>
>
> Abstract
>
>    The purpose of this document is to guide the design of congestion
>    notification in any lower layer or tunnelling protocol that
>    encapsulates IP.  The aim is for explicit congestion signals to
>    propagate consistently from lower layer protocols into IP.  Then the
>    IP internetwork layer can act as a portability layer to carry
>    congestion notification from non-IP-aware congested nodes up to the
>    transport layer (L4).  Following these guidelines should assure
>    interworking between new lower layer congestion notification
>    mechanisms, whether specified by the IETF or other standards bodies.
>
>
> [Cross-posting tsvwg & aqm, just in case]
>
>
> Bob Briscoe,
> also for co-authors Pat Thaler and John Kaippallimalil
>
>
> ________________________________________________________________
> Bob Briscoe,                                                  BT
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>



-- 
Andrew McGregor | SRE | andrewmcgr@google.com | +61 4 8143 7128