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

Joe Touch <touch@isi.edu> Tue, 05 November 2013 18:39 UTC

Return-Path: <touch@isi.edu>
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 75FE321E809E for <aqm@ietfa.amsl.com>; Tue, 5 Nov 2013 10:39:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.199
X-Spam-Level:
X-Spam-Status: No, score=-103.199 tagged_above=-999 required=5 tests=[AWL=-0.827, BAYES_00=-2.599, 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 SpELT1V7FLUq for <aqm@ietfa.amsl.com>; Tue, 5 Nov 2013 10:38:56 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id D45A111E80DE for <aqm@ietf.org>; Tue, 5 Nov 2013 10:38:39 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id rA5IcAAZ011239 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 5 Nov 2013 10:38:10 -0800 (PST)
Message-ID: <52793B87.4040102@isi.edu>
Date: Tue, 05 Nov 2013 10:40:07 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Michael Menth <menth@uni-tuebingen.de>, aqm@ietf.org
References: <201311042203.rA4M3lo0026458@bagheera.jungle.bt.co.uk> <CAH56bmDfOxi2FBvg1P-UH-ds_WveZP4NvOyqopKdEcy5WX3XnQ@mail.gmail.com> <52789FF5.3030907@uni-tuebingen.de>
In-Reply-To: <52789FF5.3030907@uni-tuebingen.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
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 18:39:00 -0000

IMO, these guidelines ought to come out in a single recommendation for 
tunnels; we had a draft of that in INTAREA but insufficient momentum.

Piecemeal recommendations are likely to be ignored/lost.

Joe

On 11/4/2013 11:36 PM, Michael Menth wrote:
> +1
>
> We need such guidelines for consistent congestion management.
>
> Best wishes,
>
> Michael
>
> Am 05.11.2013 00:16, schrieb Matt Mathis:
>> 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
>> <mailto: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 <mailto:aqm@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/aqm
>>
>>
>>
>>
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
>
> --
> Prof. Dr. habil. Michael Menth
> University of Tuebingen
> Faculty of Science
> Department of Computer Science
> Chair of Communication Networks
> Sand 13, 72076 Tuebingen, Germany
> phone: (+49)-7071/29-70505
> fax: (+49)-7071/29-5220
> mailto:menth@uni-tuebingen.de
> http://kn.inf.uni-tuebingen.de
>
>
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>