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

Matt Mathis <mattmathis@google.com> Mon, 04 November 2013 23:16 UTC

Return-Path: <mattmathis@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 8117321E8270 for <aqm@ietfa.amsl.com>; Mon, 4 Nov 2013 15:16:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.779
X-Spam-Level:
X-Spam-Status: No, score=-0.779 tagged_above=-999 required=5 tests=[AWL=-0.695, 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 yJ1zoCoOtO5c for <aqm@ietfa.amsl.com>; Mon, 4 Nov 2013 15:16:31 -0800 (PST)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 990C421E824E for <aqm@ietf.org>; Mon, 4 Nov 2013 15:16:31 -0800 (PST)
Received: by mail-ie0-f176.google.com with SMTP id u16so13957570iet.35 for <aqm@ietf.org>; Mon, 04 Nov 2013 15:16:31 -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=K97CLgUclEVmjrZo3fPN6I5oOKAiBcHfb/31J0lsIMk=; b=GEfL50c5gsiTmFf37WJPaxNE3fIS7xzDVdIsYOxh5BO8ugcpAlD+dnhQeyQJyDWUMK xMCByhaKRr+o8vwiLnw78pwi/Po6Isn3IU5W65POZbrdqPTzIFy0h3NnVklGee3cqOCt 2otNmKC52nfZMsPdXOYyMnbikEiUYnuSarNwBboOWuiGy/NcovWEYK2GIVn8y+mI/E8G XKXf+1Z0F6Bu96ZTNP7SaXYBOa7cwN8mJZImnbBtjGaiCLGYEzXkzEkmzY3CDS4nGcKX 3yefHCGA7yHFBb/OKOH1Th0VcRsBxsOt1L+xwd854LX2NuV+auARHF1oIyLDr7ckV4Xh igNQ==
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=K97CLgUclEVmjrZo3fPN6I5oOKAiBcHfb/31J0lsIMk=; b=QLdd0nwXQk4u/YFrcTRqgJzSm5FhfZ3hbO3A2e2meaomtFt141JqAQygbo1ZOS8TTf +c7Lx/LcZPCWMG7fseIVlRhtErOR++x+EHz56vS4yl4fLqCnDUyc7jY6RjVE+c8UzWq8 cfU8Hk7CxMOlBymkuAwW56cDAScnfAjIIepa+eZNKs+dY9q7eenl+PEA/TNmUf7KI5Xg GddhDN/7TKbRz1xixkYX2cWNMl+AXJv7g1v6RLSaR1He+UPgLxt/1T2GDsgPjpDKUDs2 lq/AFe2OpAY8UGg0KlJvcZ4vc3AxVRbWbP+v4CrRYMha7WwUBdLQRhYT7Hiz3Apn2250 7JTg==
X-Gm-Message-State: ALoCoQl+g5AfHnuGP5+3C8V460N85DarfQYeDJBR6gkBWQqbNF3306KDDluR5SuHOz0CMyKfNDxjXWODkroxB0WIElkIoEMwJNnEztn8IPOnb5XqVZ9nGm18r+H26S7XZk6shLt+ka/VcrGyGyazrUPspHTXooBMomR+liKFCV0ALyvjBnPJa60N2TrpbPGZM/ZNA3E7I9NZ
MIME-Version: 1.0
X-Received: by 10.43.158.10 with SMTP id ls10mr11482691icc.20.1383606990999; Mon, 04 Nov 2013 15:16:30 -0800 (PST)
Received: by 10.64.243.66 with HTTP; Mon, 4 Nov 2013 15:16:30 -0800 (PST)
In-Reply-To: <201311042203.rA4M3lo0026458@bagheera.jungle.bt.co.uk>
References: <201311042203.rA4M3lo0026458@bagheera.jungle.bt.co.uk>
Date: Mon, 04 Nov 2013 15:16:30 -0800
Message-ID: <CAH56bmDfOxi2FBvg1P-UH-ds_WveZP4NvOyqopKdEcy5WX3XnQ@mail.gmail.com>
From: Matt Mathis <mattmathis@google.com>
To: Bob Briscoe <bob.briscoe@bt.com>
Content-Type: multipart/alternative; boundary="001a11c1ead6352a2604ea621b57"
Cc: 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:16:32 -0000

I think this is valuable work.  Having a single document that describes the
requirements and general principles will save future tunnel
inventor/implementers from rediscovering the same bugs

Thanks,
--MM--
The best way to predict the future is to create it.  - Alan Kay

Privacy matters!  We know from recent events that people are using our
services to speak in defiance of unjust governments.   We treat privacy and
security as matters of life and death, because for some users, they are.


On Mon, Nov 4, 2013 at 2:03 PM, 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
>