From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id F178D201A69 for ; Mon, 16 May 2011 08:00:46 -0700 (PDT) Received: from hydrogene.pps.jussieu.fr (hydrogene.pps.jussieu.fr [134.157.168.1]) by shiva.jussieu.fr (8.14.4/jtpda-5.4) with ESMTP id p4GF9pu5029642 ; Mon, 16 May 2011 17:10:04 +0200 (CEST) X-Ids: 168 Received: from lanthane.pps.jussieu.fr (lanthane.pps.jussieu.fr [134.157.168.57]) by hydrogene.pps.jussieu.fr (Postfix) with ESMTPS id 5ED22C337F; Mon, 16 May 2011 17:09:50 +0200 (CEST) Received: from jch by lanthane.pps.jussieu.fr with local (Exim 4.76) (envelope-from ) id 1QLzQc-0000w3-5t; Mon, 16 May 2011 17:09:50 +0200 From: Juliusz Chroboczek To: Dave Taht References: <4DA67BBE.9050606@taht.net> <1303145028.24248.1442482225@webmail.messagingengine.com> <1304695674.3066.57.camel@edumazet-laptop> Date: Mon, 16 May 2011 17:09:50 +0200 In-Reply-To: (Dave Taht's message of "Fri, 6 May 2011 12:14:23 -0600") Message-ID: <7i4o4uhebl.fsf@lanthane.pps.jussieu.fr> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Miltered: at jchkmail.jussieu.fr with ID 4DD13E3F.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 4DD13E3F.002/134.157.168.1/hydrogene.pps.jussieu.fr/hydrogene.pps.jussieu.fr/ Cc: Bufferbloat Mainlinglist Subject: Re: [Bloat] No ECN marking in IPv6 linux X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 May 2011 15:00:47 -0000 > I am curious as to what the correct behavior here should be for encapsulated > (6in4, 6to4, teredo) packets, RFC 3168 sections 9.1 and 9.2 (which I've read), but I fear it may have been updated by RFC 6040 (which I haven't). -- Juliusz