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

Michael Welzl <michawe@ifi.uio.no> Tue, 05 November 2013 00:02 UTC

Return-Path: <michawe@ifi.uio.no>
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 01B2321E8318; Mon, 4 Nov 2013 16:02:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.652
X-Spam-Level:
X-Spam-Status: No, score=-101.652 tagged_above=-999 required=5 tests=[AWL=-0.947, BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_HTML_USL_OBFU=1.666, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 G-3it9XUWY6O; Mon, 4 Nov 2013 16:02:49 -0800 (PST)
Received: from mail-out5.uio.no (mail-out5.uio.no [IPv6:2001:700:100:10::17]) by ietfa.amsl.com (Postfix) with ESMTP id 6F02B21E833A; Mon, 4 Nov 2013 16:02:44 -0800 (PST)
Received: from mail-mx4.uio.no ([129.240.10.45]) by mail-out5.uio.no with esmtp (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1VdU6S-0001CB-W1; Tue, 05 Nov 2013 01:02:40 +0100
Received: from dhcp-9c73.meeting.ietf.org ([31.133.156.115]) by mail-mx4.uio.no with esmtpsa (TLSv1:AES128-SHA:128) user michawe (Exim 4.80) (envelope-from <michawe@ifi.uio.no>) id 1VdU6R-0004gn-NB; Tue, 05 Nov 2013 01:02:40 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_CDB986EB-EC31-41E4-8F39-FF55DFD9A5CD"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <CAH56bmDfOxi2FBvg1P-UH-ds_WveZP4NvOyqopKdEcy5WX3XnQ@mail.gmail.com>
Date: Mon, 04 Nov 2013 16:02:32 -0800
Message-Id: <0D37F652-8259-4A03-AA1F-4889221D84BD@ifi.uio.no>
References: <201311042203.rA4M3lo0026458@bagheera.jungle.bt.co.uk> <CAH56bmDfOxi2FBvg1P-UH-ds_WveZP4NvOyqopKdEcy5WX3XnQ@mail.gmail.com>
To: Bob Briscoe <bob.briscoe@bt.com>
X-Mailer: Apple Mail (2.1510)
X-UiO-SPF-Received:
X-UiO-Ratelimit-Test: rcpts/h 4 msgs/h 1 sum rcpts/h 9 sum msgs/h 5 total rcpts 9380 max rcpts/h 40 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, HTML_MESSAGE=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: F87095E641CC2FDC768DC1C3634DD0D2BDEA6645
X-UiO-SPAM-Test: remote_host: 31.133.156.115 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 1 total 21 max/h 8 blacklist 0 greylist 0 ratelimit 0
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: Tue, 05 Nov 2013 00:02:54 -0000

+1


On 4. nov. 2013, at 15:16, Matt Mathis <mattmathis@google.com> wrote:

> 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
> 
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm