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

"Fred Baker (fred)" <fred@cisco.com> Mon, 04 November 2013 22:39 UTC

Return-Path: <fred@cisco.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 AFAF521E80E1; Mon, 4 Nov 2013 14:39:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.419
X-Spam-Level:
X-Spam-Status: No, score=-110.419 tagged_above=-999 required=5 tests=[AWL=-0.047, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 NiN8pGH+rODs; Mon, 4 Nov 2013 14:39:11 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id DA25821E809F; Mon, 4 Nov 2013 14:39:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2874; q=dns/txt; s=iport; t=1383604751; x=1384814351; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=yR0YuyUT4sViaubdlhZfpFBlglGNt8cLShXpsuI9QUQ=; b=kntTcXNCapxBafXiCWLkp01QzyWlgNnl7qfnBSNicsYj+phl6NE+k/ng x6mZDnbiy9de8UPp7i8zhFUI0wnAcPomu6e898D/n+C6tLM50DpgvidZl qgb6txBGJSj9kfYu5IUdKE1FBNG3Kb0HYIeLOn48h8Lmfazb8aC3/ioq/ E=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiQFAFcheFKtJXG//2dsb2JhbABZgwc4U74tgRKBJxZ0giUBAQEDAQEBASRHCwULAgEIRicLJQIEDgUOh20GDb5Gj1gHgyCBDgOQLoEwhiyBL5BagyaCKg
X-IronPort-AV: E=Sophos; i="4.93,635,1378857600"; d="asc'?scan'208"; a="280408696"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-1.cisco.com with ESMTP; 04 Nov 2013 22:39:10 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id rA4MdADP006852 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 4 Nov 2013 22:39:10 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.122]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Mon, 4 Nov 2013 16:39:10 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Bob Briscoe <bob.briscoe@bt.com>
Thread-Topic: [aqm] Who supports tsvwg adoption of adding ECN to L2 or tunnel protocols?
Thread-Index: AQHO2a6s10fjb0a1UEK5OS95UGUypw==
Date: Mon, 04 Nov 2013 22:39:09 +0000
Message-ID: <AB7A26DF-2432-4320-B048-69070D31C7D6@cisco.com>
References: <201311042203.rA4M3lo0026458@bagheera.jungle.bt.co.uk>
In-Reply-To: <201311042203.rA4M3lo0026458@bagheera.jungle.bt.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.88.9]
Content-Type: multipart/signed; boundary="Apple-Mail=_AD0D3F69-F2EF-4DCE-BA6B-C70B0DDB695C"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
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:39:17 -0000

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?

> 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

------------------------------------------------------
8 issues in virtual infrastructure
http://dcrocker.net/#fallacies