IETF Logo Mail Archive

Re: [Tsv-art] Tsvart early review of draft-ietf-trill-over-ip-10 - ECN & DSCP considerations

Joe Touch <touch@isi.edu> Thu, 13 July 2017 16:05 UTC

Return-Path: <touch@isi.edu>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B68E1316ED for <tsv-art@ietfa.amsl.com>; Thu, 13 Jul 2017 09:05:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
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 BHUhM-Zudehd for <tsv-art@ietfa.amsl.com>; Thu, 13 Jul 2017 09:05:37 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EC4113144E for <tsv-art@ietf.org>; Thu, 13 Jul 2017 09:05:37 -0700 (PDT)
Received: from [10.31.59.150] (ip-64-134-100-23.public.wayport.net [64.134.100.23]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id v6DG5Q4s012372 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 13 Jul 2017 09:05:28 -0700 (PDT)
To: "Black, David" <David.Black@dell.com>, Wesley Eddy <wes@mti-systems.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>
References: <CE03DB3D7B45C245BCA0D243277949362FB4DF88@MX307CL04.corp.emc.com> <CAF4+nEFUmB=eMO6rvK6-YiL+3Adp_t1QVqgMDBHZFn73_JxEfw@mail.gmail.com> <CE03DB3D7B45C245BCA0D243277949362FB59E00@MX307CL04.corp.emc.com> <CAF4+nEEdv8XRSKmpffe1fU+4wRpikeixzX-49g1ocQSJBaqgSg@mail.gmail.com> <67476ec5-2e50-bd27-de97-16aaabc9c078@mti-systems.com> <1dcb8ba7-5403-435f-9637-1b2cdf2f5247@isi.edu> <bffd51e8-7bc0-5e7d-319a-f13a0058f606@isi.edu> <52bbffe7-0f6d-dfc0-dcc0-b0eb491f9aa9@mti-systems.com> <CE03DB3D7B45C245BCA0D243277949362FB71972@MX307CL04.corp.emc.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <70c1492c-58ea-3cbc-752c-170f3bf9707a@isi.edu>
Date: Thu, 13 Jul 2017 09:05:23 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362FB71972@MX307CL04.corp.emc.com>
Content-Type: multipart/alternative; boundary="------------62EA9FCDF3C92891B6DDB004"
Content-Language: en-US
X-MailScanner-ID: v6DG5Q4s012372
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/_DvPJQv0Sm7e91iD5v44vgXrrZA>
Subject: Re: [Tsv-art] Tsvart early review of draft-ietf-trill-over-ip-10 - ECN & DSCP considerations
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jul 2017 16:05:39 -0000


On 7/13/2017 8:47 AM, Black, David wrote:
>> I agree on all points, and with the absurdity of trying to change DSCP
>> on a TCP connection per encapsulated packet.  If the DSCP values used
>> for a TCP connection change over time, it should be "coarse grained"
>> (e.g. with say hundreds or thousands of segments in between changes) and
>> not anywhere near per-segment.
>>
>> But while obvious to us, I don't think this is in any RFC to be quoted.
> [David>] RFC 7657 - this is discussed in sections 5.1 & 5.3 and summarized as a bullet point in section 6.
Those sections reinforce the idea that it SHOULD NOT be changed, but
don't explain (AFAICT) the conditions under which it might be safe or
appropriate to change it (e.g., over longer timescales).

Joe

v2.23.0 | Report a Bug | By Email