Re: [Gen-art] Genart last call review of draft-ietf-detnet-data-plane-framework-04

Balázs Varga A <balazs.a.varga@ericsson.com> Thu, 16 April 2020 11:28 UTC

Return-Path: <balazs.a.varga@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB1D43A14DB; Thu, 16 Apr 2020 04:28:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.268
X-Spam-Level:
X-Spam-Status: No, score=-2.268 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.168, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 PDhbkyKZODNV; Thu, 16 Apr 2020 04:28:14 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80052.outbound.protection.outlook.com [40.107.8.52]) (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 2AC423A14DA; Thu, 16 Apr 2020 04:28:13 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TcmMzfuTOi6K5DSkv+h0B6At2QgR3KcfBxDYquoUU5zscYEphEjlsSeY8JIaFuvz0VkZOUXRNZAW7PgRrlAPLpqS61TEp+ijsPGzbXVuC4Rt5UxVb+YSHfqdziL23e0NAsWpAAtzca773/f55dLVCeLbyJyk8uWePvg1RtSEuH2627Wxb1hS6SRLzQOoFiU5c3Zcqa3gHlwwJcmiJiDF5Lq7MP/NSzx7mkFHN49JzBdZbXnHPFOAvq/oAKp6ACLAhIMt7dahxzhXBAu/hSj11hEp36wJRyU3z59pO6aDq/rzZL7Nvc3WarWZSeHa7iir6ys4YOwv/HyGYPznJxELbQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yXw1NCKSMT7EkQTW8LfFnOd3NvGPlphYOZiavEa5+g4=; b=fIGx4zGP3OiZm9kzFDXmlmp/RGDI3WM5zYL3RwExtL9ysCTAXqOmqcUlM3CLfbpJtZ31bRJ/b+DIHm+wMK3a6olLGDZfTMzwZ2M5vrouZ+A3Y6Mj72WXqDRHRxiG9xK6NhxeHrVk8pf8GMQ+t5vctZY5UUvjQfqVuC3klKfp6ZPs7evQN+7WszEjkrQgB0awNtxZNhJ+bvyHTzNwyQqyjVjjSF9CdMY+NfRATRNcpCn0vUxnfxy3ESOVs3ygGFDhrImqF7igho6t619qUTqaEYQKUOgCa3Khz+FR7HY9O+d+pf/nsgn3bvzTrRIjBPkzBoZB84LhT+KvO05voN+7Uw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yXw1NCKSMT7EkQTW8LfFnOd3NvGPlphYOZiavEa5+g4=; b=KZpTIb7acoClTxVWhGvhJNVvQ5U5x7MAibXXt5mXz0C9DVh0ALVCzarOpXBJX2aB+AjRdN/HDGnsvO9e/EcFZQeOHKEIXKRBE+4PbvbMizQc2fW+tBSloaIoc/2NXUmVorqLAJ5FHHbBi2dii8hC/eU/qFcvp8Tx1peDoGyUEok=
Received: from AM0PR0702MB3603.eurprd07.prod.outlook.com (2603:10a6:208:22::25) by AM0PR0702MB3588.eurprd07.prod.outlook.com (2603:10a6:208:21::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2921.23; Thu, 16 Apr 2020 11:28:11 +0000
Received: from AM0PR0702MB3603.eurprd07.prod.outlook.com ([fe80::9c11:1589:8e18:5209]) by AM0PR0702MB3603.eurprd07.prod.outlook.com ([fe80::9c11:1589:8e18:5209%3]) with mapi id 15.20.2921.027; Thu, 16 Apr 2020 11:28:11 +0000
From: Balázs Varga A <balazs.a.varga@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "last-call@ietf.org" <last-call@ietf.org>, "draft-ietf-detnet-data-plane-framework.all@ietf.org" <draft-ietf-detnet-data-plane-framework.all@ietf.org>, "detnet@ietf.org" <detnet@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-detnet-data-plane-framework-04
Thread-Index: AQHV+rSDVYEcYqs1/EilCY14wjzHyah6a0vAgAB2SQCAAOqqYA==
Date: Thu, 16 Apr 2020 11:28:11 +0000
Message-ID: <AM0PR0702MB3603E1B3E20B83D1404A94A9ACD80@AM0PR0702MB3603.eurprd07.prod.outlook.com>
References: <158426811560.18081.13105223593760493382@ietfa.amsl.com> <AM0PR0702MB36039AEF0508BB9DC50EE2D5ACDB0@AM0PR0702MB3603.eurprd07.prod.outlook.com> <B5E1FC7E-166A-465D-B9EF-0DF2A08BDC8F@ericsson.com>
In-Reply-To: <B5E1FC7E-166A-465D-B9EF-0DF2A08BDC8F@ericsson.com>
Accept-Language: hu-HU, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=balazs.a.varga@ericsson.com;
x-originating-ip: [188.143.71.76]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 194206ca-5c1f-49d5-2a07-08d7e1f93f1b
x-ms-traffictypediagnostic: AM0PR0702MB3588:|AM0PR0702MB3588:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <AM0PR0702MB3588635032608986AB720FC1ACD80@AM0PR0702MB3588.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0375972289
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR0702MB3603.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(10009020)(4636009)(136003)(366004)(376002)(396003)(346002)(39860400002)(186003)(81156014)(54906003)(33656002)(85182001)(8936002)(8676002)(86362001)(71200400001)(53546011)(2906002)(478600001)(26005)(6506007)(55016002)(9686003)(7696005)(66476007)(4326008)(450100002)(85202003)(76116006)(52536014)(110136005)(66946007)(316002)(66446008)(66556008)(5660300002)(64756008); DIR:OUT; SFP:1101;
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: bFAvt7tTARA6FSNcvrvxA58nnKIfOTQPb8rCnsFVr/rJjNudmtsQBNnEsMXxsIjVI8jWhUF5nylXc+JjYYwsChYMBIhcUSFRW9DZ36n0lOQD596fPlaPI0r3SS+ns8aN6n147QbzBjcIk3FGvFzxTH0VwYVVlwAWol5KEiwe1kLqzMoj8E9KoWUOJclFeFLjqlWsxZF13OxF3v2IZvxC7axDtRx7cMpLYQCWJSm9tBchTDfZYAnEpIBOirS5VdrPjSDYzCzu2Y4GFx40kzaMuRezSU/6D5wofic4uVr0bvPvaUsTZSXRx7BB9z2JHUAmX3vyyix+BUqBIoUO/CW9DJauSIi+C5MG7fi+0sm88dvmocgEH59szOKZq15iRkkeaB1TOg6Q+2t5L2cgVxqnDU4b9DPAA1v0DLahaLXNX5ZWssy6xZHKqPlthHkdd16t
x-ms-exchange-antispam-messagedata: Ds+VZzLz5kuyxnYx4EYSduSkN+Ks/B7rRTMqjSEVCCzeHx3SJPdAhIrWRqWAK2dm1YApk3iSvd2ISGw92FuxmSgXL4mUplNpi5+ZAt5gZAgnukS5mw1yUPULi6d3JXc0PtAH0POEkDfFr71rB644rA==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 194206ca-5c1f-49d5-2a07-08d7e1f93f1b
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Apr 2020 11:28:11.7106 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: PPu+MzVFHYnk/9uOxuIj0Y+h8OTnzI5lWjxrNfDnNrsCZo3ow3Q1GeF99wwhVFeR6g1Kgb/W4gpFd/wBQFJ5SpdBX8C1HmRrx4Hy1iBb57U=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR0702MB3588
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/2yTSqqThoQXVYJ9HD5oJhEgv6Ag>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-detnet-data-plane-framework-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Apr 2020 11:28:16 -0000

Hi Christer,

No, data plane specification does not cover what protocols are used by service sub-layer and forwarding sub-layer functions.
A data plane specification specifies what headers fields are there in the packet and how to use these header fields for a specific 
purpose. For instance, in case of DetNet, what fields are used to recognize a DetNet flow (flow ID) and how is the sequence number 
encoded and used.

A possible clarification is below (text added in brackets to firs sentence). Does it solves your concern?
OLD:
   This document describes the concepts needed by any DetNet data plane
   specification and provides considerations for any corresponding
   implementation.  It covers the building blocks that provide the
   DetNet service, the DetNet service sub-layer and the DetNet
   forwarding sub-layer functions as described in the DetNet
   Architecture.

NEW:
   This document describes the concepts needed by any DetNet data plane
   specification (i.e., the DetNet-specific use of packet header fields) and 
   provides considerations for any corresponding
   implementation.  It covers the building blocks that provide the
   DetNet service, the DetNet service sub-layer and the DetNet
   forwarding sub-layer functions as described in the DetNet
   Architecture.

Thanks
Bala'zs

-----Original Message-----
From: Christer Holmberg <christer.holmberg@ericsson.com> 
Sent: Wednesday, April 15, 2020 11:19 PM
To: Balázs Varga A <balazs.a.varga@ericsson.com>; gen-art@ietf.org
Cc: last-call@ietf.org; draft-ietf-detnet-data-plane-framework.all@ietf.org; detnet@ietf.org
Subject: Re: Genart last call review of draft-ietf-detnet-data-plane-framework-04

Hi Bala'zs,

Thank you for the reply and clarifications. I still have a question on Q2.

...
    
    Q2:
    
    >> The first line of the 2nd paragraph of the Introduction says:
    >>
    >> “This document describes the concepts needed by any DetNet data plane specification…”
    >>
    >> What is meant by DetNet data plane specification? The definition of DetNet flows over a specific network technology? Please clarify, or reference if already defined elsewhere.
    >
    > <BV> Data plane documents focuses how DetNet packets are recognized and served according to DetNet service and forwarding sub-layer functions. 
    >The next sentence is intended to clarify that.

    The next sentence is fine. It is just a little unclear to me what the definition of DetNet data plane specification actually is. Is it a specification that 
    defines the combination of service sub-layer using protocol X and forwarding sub-layer using protocol Y?


Regards,

Christer