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

"Black, David" <David.Black@dell.com> Thu, 25 July 2019 20:00 UTC

Return-Path: <David.Black@dell.com>
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 274B21201EF for <detnet@ietfa.amsl.com>; Thu, 25 Jul 2019 13:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.689
X-Spam-Level:
X-Spam-Status: No, score=-2.689 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dell.com header.b=naTQ5oQi; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=Ay8MhJU9
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 4WM86YNzjYvQ for <detnet@ietfa.amsl.com>; Thu, 25 Jul 2019 13:00:42 -0700 (PDT)
Received: from mx0a-00154904.pphosted.com (mx0a-00154904.pphosted.com [148.163.133.20]) (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 DAFC612029D for <detnet@ietf.org>; Thu, 25 Jul 2019 13:00:42 -0700 (PDT)
Received: from pps.filterd (m0170392.ppops.net [127.0.0.1]) by mx0a-00154904.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x6PJxs1L022217; Thu, 25 Jul 2019 16:00:42 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dell.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=smtpout1; bh=JV3P+IPrwzDUPNd+WdRJ52SXGiMZr3R9IxnU22YrcRQ=; b=naTQ5oQi1bwaQSfpkLJX8h/NH+YYdl0puSc55KUUyhGwGN+0Cnm8yY416reH/dGgKw1h gzuWysVDmvb0OhiOz1CR6SAinLr3h7A3f+5qQUWglo18JeYqDS4a1/Df1Dq6CLnIn1LP PZeymIeVjbsfkQDwtLEsmCsee9xrd0borDKLweKsHOTb4/A7xa2Z4S3n5xFRdr3ULCnW aiiIhb1RS0FWTPfhLjFN29fSC1wH6+5iugoflo9htsbkHGIWlDH8cL8Qtz4SAiL4C1ZV kPPrJyw3v5sSOU90wAaBlq4UJUU+AAoC24nwSDEDWfNsIYYdbiCKoxo9ge1AzCYr0Hlw RQ==
Received: from mx0b-00154901.pphosted.com (mx0b-00154901.pphosted.com [67.231.157.37]) by mx0a-00154904.pphosted.com with ESMTP id 2ty9yvtrh4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 25 Jul 2019 16:00:42 -0400
Received: from pps.filterd (m0144102.ppops.net [127.0.0.1]) by mx0b-00154901.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x6PJw7IC071298; Thu, 25 Jul 2019 16:00:41 -0400
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by mx0b-00154901.pphosted.com with ESMTP id 2tyh009wbh-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 25 Jul 2019 16:00:41 -0400
Received: from maildlpprd52.lss.emc.com (maildlpprd52.lss.emc.com [10.106.48.156]) by mailuogwprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id x6PK0NYq014722 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 25 Jul 2019 16:00:40 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com x6PK0NYq014722
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1564084840; bh=B5iAHTUvYvkbv+l0mphXcYJQHFw=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=Ay8MhJU9mTVa98Vf1aN1mTjkwLUKK4uv/dP9zrMu1hXXTiPGOZSxF2/oPNv0BP3oP z6UIfqgF9fT9R9RdDPOwM3xDT4oj9MOmY95b2ct5nEPrrBf0EU2t7KBluXEo1UlG0Z xGu38IL/PxInv1p4eIpwcXlejk8ZOk4Ny2fInS+M=
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd52.lss.emc.com (RSA Interceptor); Thu, 25 Jul 2019 15:59:15 -0400
Received: from MXHUB316.corp.emc.com (MXHUB316.corp.emc.com [10.146.3.94]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id x6PJxE1G030021 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Thu, 25 Jul 2019 15:59:15 -0400
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB316.corp.emc.com ([10.146.3.94]) with mapi id 14.03.0439.000; Thu, 25 Jul 2019 15:59:14 -0400
From: "Black, David" <David.Black@dell.com>
To: Lou Berger <lberger@labn.net>, "detnet@ietf.org" <detnet@ietf.org>
Thread-Topic: [Detnet] IP Data plane: 5-tuple vs. 6-tuple - proposed text
Thread-Index: AdVCXpIhBtev3ygsR5aNJnOm9N0jWgAvTkaAAAHBfxA=
Date: Thu, 25 Jul 2019 19:59:13 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949363063BC8A@MX307CL04.corp.emc.com>
References: <CE03DB3D7B45C245BCA0D2432779493630637620@MX307CL04.corp.emc.com> <9694ecf4-7f0f-feec-7e1f-b97b441362fa@labn.net>
In-Reply-To: <9694ecf4-7f0f-feec-7e1f-b97b441362fa@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_Enabled=True; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_SiteId=945c199a-83a2-4e80-9f8c-5a91be5752dd; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_Owner=david.black@emc.com; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_SetDate=2019-07-25T19:59:10.6845518Z; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_Name=External Public; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_Application=Microsoft Azure Information Protection; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_Extended_MSFT_Method=Manual; aiplabel=External Public
x-originating-ip: [10.105.8.135]
Content-Type: multipart/alternative; boundary="_000_CE03DB3D7B45C245BCA0D243277949363063BC8AMX307CL04corpem_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-25_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1907250238
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1907250238
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/ykpI6gbH2L705BBjmHbnsZraxig>
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 20:00:50 -0000

> Are you okay with dropping "While 5-tuples suffice to identify DetNet flows,"
Not by itself - if that text is dropped, I'd want to add a couple of sentences (perhaps not in Section 3) to explain how DetNet flows differ from Diffserv flows, i.e., "microflows" in defined in RFC 2475 (Diffserv Architecture).

If that's ok, I can go write some proposed text ...

Thanks, --David

From: Lou Berger <lberger@labn.net>
Sent: Thursday, July 25, 2019 11:05 AM
To: Black, David; detnet@ietf.org
Subject: Re: [Detnet] IP Data plane: 5-tuple vs. 6-tuple - proposed text


[EXTERNAL EMAIL]

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<mailto:detnet@ietf.org>

https://www.ietf.org/mailman/listinfo/detnet