IETF Logo Mail Archive

Re: [tsvwg] Status of ECN encapsulation drafts (i.e., stuck)

Bob Briscoe <ietf@bobbriscoe.net> Fri, 13 March 2020 17:45 UTC

Return-Path: <ietf@bobbriscoe.net>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F3663A0405 for <tsvwg@ietfa.amsl.com>; Fri, 13 Mar 2020 10:45:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.433
X-Spam-Level:
X-Spam-Status: No, score=-1.433 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bobbriscoe.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ORW6ITgZdwTY for <tsvwg@ietfa.amsl.com>; Fri, 13 Mar 2020 10:45:37 -0700 (PDT)
Received: from cl3.bcs-hosting.net (cl3.bcs-hosting.net [3.11.37.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67B963A0402 for <tsvwg@ietf.org>; Fri, 13 Mar 2020 10:45:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=QTptdLm4pjHtRdLSHAjOmr3jf14/lp/I4Epc2aCW4vo=; b=MZiOl5LbHmknrlPUGm1QecGqyC NN2QDi8a0PE+wsfhApDySSq7PzYQHKUhXd0afi0hf6iiSZB8kdmq/EnbFEyw0E7MwZEvyDc9KC0W0 MEJb09PAIbWlymcNgAN3WBcRKd2WxMEAiMrITg24zrIcZWJ9U6ebukRt/qsjvu4BWPougPXgJ2sYd pVfKTiPwgNMEQLS9Z2D/FheSj1PWW8NMeSmNw16asymT6CLJ+nKqZURFcmZ/znKttQylN7RikIZcg nHe4g46HxvCLnUMGyq6YodWnGmZm3Uqf87V9vxtyjAykpJ4Ot5Y2B6JD9umht+vBm5BhvTUc0ez8d 9akmD9Dg==;
Received: from [31.185.135.141] (port=39298 helo=[192.168.0.4]) by cl3.bcs-hosting.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from <ietf@bobbriscoe.net>) id 1jCoNL-00FQ7H-Gl; Fri, 13 Mar 2020 17:45:35 +0000
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "Black, David" <David.Black@dell.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
References: <CE03DB3D7B45C245BCA0D24327794936306F8925@MX307CL04.corp.emc.com> <2873ab79-19ad-0541-e3a4-d1d28dbc7ba0@bobbriscoe.net> <B6D58310-41E0-4172-B555-D28E7926A0B5@gmail.com> <3ee6e427-9dc9-e885-21a9-df9e35d99006@bobbriscoe.net> <C1696430-D2D2-48BB-AB17-EFB77EE474DE@gmail.com> <5d8f11f3-9def-14b1-4923-4eb02caf51eb@bobbriscoe.net> <50B14177-EB29-4273-839C-D22CCC47511E@gmail.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <4f66ba3e-9eed-03cd-7f45-a1d7d10ec697@bobbriscoe.net>
Date: Fri, 13 Mar 2020 17:45:34 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <50B14177-EB29-4273-839C-D22CCC47511E@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cl3.bcs-hosting.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: cl3.bcs-hosting.net: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: cl3.bcs-hosting.net: in@bobbriscoe.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/F3b8q8Oer_Fo1W3L3KkhRELCKzo>
Subject: Re: [tsvwg] Status of ECN encapsulation drafts (i.e., stuck)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2020 17:45:39 -0000

Jonathan,

No, you have to read the email. The doubling comes at fragmentation, 
then the reassembly is meant to compensate for it.




Bob

On 13/03/2020 17:23, Jonathan Morton wrote:
>> On 13 Mar, 2020, at 6:42 pm, Bob Briscoe <ietf@bobbriscoe.net> wrote:
>>
>>> What am I missing from the context of your objections?
>> Well, I don't know, 'cos I don't know how you came to that interpretation (you'll need to point to the sentence that made you think that, if it's still not clear).
> I'm referring specifically to your claim that the existing specifications can result in a doubling of CE marks in the reassembled and decapsulated packets, relative to the number present in the encapsulated, fragmented packets arriving at the decapsulator.  I cannot at present identify any mechanism which permits this to occur, but it seems to form the basis of your justification for modified language.
>
> So *one* of us has clearly misread the specs in question.  I just want to figure out which of us it is.  You could do so by quoting chapter and verse for such a mechanism, and we can work from there.
>
>   - Jonathan Morton

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/

v2.23.0 | Report a Bug | By Email