IETF Logo Mail Archive

Re: [Detnet] IP Data plane: 5-tuple vs. 6-tuple - proposed text

Lou Berger <lberger@labn.net> Thu, 25 July 2019 15:13 UTC

Return-Path: <lberger@labn.net>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AFD3120370 for <detnet@ietfa.amsl.com>; Thu, 25 Jul 2019 08:13:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.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 w9bmigcr-2ow for <detnet@ietfa.amsl.com>; Thu, 25 Jul 2019 08:13:36 -0700 (PDT)
Received: from gproxy3-pub.mail.unifiedlayer.com (gproxy3-pub.mail.unifiedlayer.com [69.89.30.42]) (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 2781612033D for <detnet@ietf.org>; Thu, 25 Jul 2019 08:13:33 -0700 (PDT)
Received: from cmgw11.unifiedlayer.com (unknown [10.9.0.11]) by gproxy3.mail.unifiedlayer.com (Postfix) with ESMTP id 395CE42A72 for <detnet@ietf.org>; Thu, 25 Jul 2019 09:04:35 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id qfIIhBdqmdgLtqfIJhXhYN; Thu, 25 Jul 2019 09:04:35 -0600
X-Authority-Reason: nr=8
X-Authority-Analysis: $(_cmae_reason
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From: References:To:Subject:Sender:Reply-To:Cc:Content-Transfer-Encoding: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=3On0Jvm+2TheTYSdOoDsYPuFnBfBo9lVWbkEkPaBYH4=; b=zD8zbwD5HdBo7l6j7mgkp5kv0/ QoCJTHk/Sk2iulB5+UaazixtW4h5nc83J1r23SP7XL1CVA6fhLa0VseMuZL00CAULoLbdRd0IeBfz ZTD5FEyLBVmv0Cf9drn08ZEzD;
Received: from [127.0.0.1] (port=39147 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <lberger@labn.net>) id 1hqfII-000MZU-Kp; Thu, 25 Jul 2019 09:04:34 -0600
To: "Black, David" <David.Black@dell.com>, "detnet@ietf.org" <detnet@ietf.org>
References: <CE03DB3D7B45C245BCA0D2432779493630637620@MX307CL04.corp.emc.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <9694ecf4-7f0f-feec-7e1f-b97b441362fa@labn.net>
Date: Thu, 25 Jul 2019 11:04:33 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1
MIME-Version: 1.0
In-Reply-To: <CE03DB3D7B45C245BCA0D2432779493630637620@MX307CL04.corp.emc.com>
Content-Type: multipart/alternative; boundary="------------D38B3C38A9D30157B18B6BAE"
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 127.0.0.1
X-Source-L: Yes
X-Exim-ID: 1hqfII-000MZU-Kp
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: ([IPv6:::1]) [127.0.0.1]:39147
X-Source-Auth: lberger@labn.net
X-Email-Count: 2
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Org: HG=bhcustomer;ORG=bluehost;
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/8iXiEBTWWHsEQHVajGkPiLqU2b0>
Subject: Re: [Detnet] IP Data plane: 5-tuple vs. 6-tuple - proposed text
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jul 2019 15:13:44 -0000

Hi David,

Thank you for the text. See below.

On 7/24/2019 4:30 PM, Black, David wrote:
> I think I found a way out of the rathole that I caused on this topic 
> in the meeting ....
> Here’s the second paragraph in Section 3 of the IP Data Plane draft 
> (https://tools.ietf.org/html/draft-ietf-detnet-ip-01#section-3):
>     The DetNet IP data plane uses "6-tuple" based flow identification,
>     where 6-tuple refers to information carried in IP and higher layer
>     protocol headers.  The 6-tuple referred to in this document is the
>     same as that defined in [RFC3290  <https://tools.ietf.org/html/rfc3290>].  Specifically 6-tuple is
>     (destination address, source address, IP protocol, source port,
>     destination port, and differentiated services (DiffServ) code point
>     (DSCP).  General background on the use of IP headers, and 5-tuples,
>     to identify flows and support Quality of Service (QoS) can be found
>     in [RFC3670  <https://tools.ietf.org/html/rfc3670>].  [RFC7657  <https://tools.ietf.org/html/rfc7657>] also provides useful background on the
>     delivery of DiffServ and "tuple" based flow identification.
>     Referring to a 6-tuple allows DetNet nodes to forward packets with
>     the 6-tuple as is or remap the DSCP where required by the DetNet
>     service.
>
> The following small change suffices to address the roles of 5-tuples 
> vs. 6-tuples:
>
> OLD
>
>     Referring to a 6-tuple allows DetNet nodes to forward packets with
>     the 6-tuple as is or remap the DSCP where required by the DetNet
>     service.
>
> NEW
>
>     While 5-tuples suffice to identify DetNet flows, using 6-tuples
>     enables DetNet nodes to forward packets with an unchanged 6-tuple
>     or with a changed DSCP where required by the DetNet service.
>
Are you okay with dropping "While 5-tuples suffice to identify DetNet 
flows,"

Thanks,

Lou


> Thanks, --David
>
> ----------------------------------------------------------------
>
> David L. Black, Senior Distinguished Engineer
>
> Dell EMC, 176 South St., Hopkinton, MA 01748
>
> +1 (774) 350-9323 *New *   Mobile: +1 (978) 394-7754
>
> David.Black@dell.com <mailto:David.Black@dell.com>
>
> ----------------------------------------------------------------
>
>
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet

v2.23.0 | Report a Bug | By Email