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

Bob Briscoe <bob.briscoe@bt.com> Mon, 04 November 2013 22:45 UTC

Return-Path: <bob.briscoe@bt.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 605C121E80E1; Mon, 4 Nov 2013 14:45:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.297
X-Spam-Level:
X-Spam-Status: No, score=-3.297 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 N1XYvv8IamQO; Mon, 4 Nov 2013 14:44:58 -0800 (PST)
Received: from hubrelay-rd.bt.com (hubrelay-rd.bt.com [62.239.224.99]) by ietfa.amsl.com (Postfix) with ESMTP id BE2F921E80AF; Mon, 4 Nov 2013 14:44:56 -0800 (PST)
Received: from EVMHR01-UKBR.domain1.systemhost.net (193.113.108.40) by EVMHR67-UKRD.bt.com (10.187.101.22) with Microsoft SMTP Server (TLS) id 8.3.297.1; Mon, 4 Nov 2013 22:44:54 +0000
Received: from EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) by EVMHR01-UKBR.domain1.systemhost.net (193.113.108.40) with Microsoft SMTP Server (TLS) id 8.3.297.1; Mon, 4 Nov 2013 22:44:52 +0000
Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) with Microsoft SMTP Server id 14.2.347.0; Mon, 4 Nov 2013 22:44:52 +0000
Received: from BTP075694.jungle.bt.co.uk ([10.109.157.6]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id rA4MinXo026739; Mon, 4 Nov 2013 22:44:50 GMT
Message-ID: <201311042244.rA4MinXo026739@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 04 Nov 2013 22:44:48 +0000
To: "Fred Baker (fred)" <fred@cisco.com>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <AB7A26DF-2432-4320-B048-69070D31C7D6@cisco.com>
References: <201311042203.rA4M3lo0026458@bagheera.jungle.bt.co.uk> <AB7A26DF-2432-4320-B048-69070D31C7D6@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
Cc: Pat Thaler <pthaler@broadcom.com>, John Kaippallimalil <John.Kaippallimalil@huawei.com>, "<draft-briscoe-tsvwg-ecn-encap-guidelines@tools.ietf.org>" <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 22:45:08 -0000

Fred,

At 22:39 04/11/2013, Fred Baker (fred) wrote:

>On 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.
>
>And don't respond if we don't support it? :-)
>
>I have a very basic question. For IP/IP tunnels, such as GRE, the 
>ECN flags are defined, and I would imagine that RFC 2983 could be 
>interpreted as saying what one does with flags (when you move the 
>TOS octet, move 8 bits, whether in->out or out->in). For non-IP 
>tunnels, with the exception of MPLS, the IETF doesn't define the header.
>
>How does one add ECN to a protocol we don't maintain? If we maintain 
>it, are we already done?

The idea is to issue liaison statements to make the relevant stds 
bodies aware of this. E.g.:
- to 3GPP for GTP,
- to IEEE for 802.

The IETF maintains a number of the relevant tunnelling protocols it 
mentions, e.g.
L2TP, GRE, PPTP.



________________________________________________________________
Bob Briscoe,                                                  BT