Re: [RTG-DIR] Rtgdir last call review of draft-ietf-detnet-problem-statement-06

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 01 October 2018 07:26 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44FDF130DE7; Mon, 1 Oct 2018 00:26:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 bGBsoXpOBY_Y; Mon, 1 Oct 2018 00:26:54 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A80A130DE3; Mon, 1 Oct 2018 00:26:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4044; q=dns/txt; s=iport; t=1538378814; x=1539588414; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=rmOdOMWUaDP5HuWWePU27saF3ipiCo1VRZ26aDtnbA0=; b=cZ8v4KqYZYRaQ4iQSGtTlJ+nlnfKhqKN6Rtvo0Gu/ceUkDmSCzNgBuHh Ft7D+Ba6hlcH7xLPgTuzZuS9wC8TcrM8jkXgYl7F6VqZAAODg10hZaWsa 3msQkVxbNsEcqHPP/12jkABYvCqayMoViFNQVvBfpkdVvLzUC5EBf7mSH U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AXAADFy7Fb/51dJa1aGQEBAQEBAQEBAQEBAQcBAQEBAQGBUYIOgWUyg2qIFYwwgg14gkWTHYF6C4RsAheDbCE0GAEDAQECAQECbSiFOAEBAQECASMRMxIFCwIBCA4ECAImAgICMBUCDgIEAQ0NhRMIo0GBLooIgQuJdxeBQT+BEoJdNYRYgyeCVwKIe5NiTAkCkCofgUeEW4Zegk+VCgIRFIElHTiBVXAVgyiQU4wLgS2BHwEB
X-IronPort-AV: E=Sophos;i="5.54,327,1534809600"; d="scan'208";a="241667048"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Oct 2018 07:26:53 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id w917QrhL009627 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 1 Oct 2018 07:26:53 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 1 Oct 2018 02:26:52 -0500
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1395.000; Mon, 1 Oct 2018 02:26:52 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Ines Robles <mariainesrobles@googlemail.com>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
CC: "detnet@ietf.org" <detnet@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-detnet-problem-statement.all@ietf.org" <draft-ietf-detnet-problem-statement.all@ietf.org>
Thread-Topic: Rtgdir last call review of draft-ietf-detnet-problem-statement-06
Thread-Index: AQHUWPtHUK6sOqQa+0Kg+dXUUubEVKUJ6N6g
Date: Mon, 01 Oct 2018 07:26:36 +0000
Deferred-Delivery: Mon, 1 Oct 2018 07:26:17 +0000
Message-ID: <bf03cc0dbee34971adcdfc4f68566b25@XCH-RCD-001.cisco.com>
References: <153833893256.13335.17089954204593908870@ietfa.amsl.com>
In-Reply-To: <153833893256.13335.17089954204593908870@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.22.4]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/t2TgYsqfFUElMUyP-3Ad7SJPBlg>
Subject: Re: [RTG-DIR] Rtgdir last call review of draft-ietf-detnet-problem-statement-06
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Oct 2018 07:26:57 -0000

Hello Ines

Many thanks for your review. 

I see this recurring point of adding references to the other detnet documents; I'm happy to follow this advice, noting though that these are forward pointers since the problem statement comes first. 

Please see below:
 
> I believe the draft is technically good. This document is well written and clear to
> understand.
> 
> The document describes the needs in various industries to establish multi-hop
> paths for characterized flows with deterministic properties.
> 
> This document is basically ready for publication, but I have some minor
> questions that should be considered prior to being submitted to the IESG.
> 
> Comments:
> 
> 1)- In section 1 you mention: "....a new model must be proposed to integrate
> determinism in IT technology..." Do you think it is useful to mention draft-ietf-
> detnet-architecture as a starting point for the model?
> 
[PT>] what about:
"
      Forward note: The <xref target='I-D.ietf-detnet-architecture'>
      DetNet Architecture</xref> is the document produced by the DetNet WG to 
      describe that model.
"

> 2)- In Section 1: "the model should not compromise the ability of a network to
> keep carrying the sorts of traffic that is already carried today in conjunction
> with new, more deterministic flows.", and in Section 2 "The goals of
> Deterministic Networking (DetNet) are .... and to support both these new
> applications, and existing packet network applications, over the same physical
> network." Those sentences seems to be related with Interoperability, but
> Interoperability is not explicitly mentioned in the document. Do you think that it
> should be?
[PT>] Can we add after the latter sentence:

"
In other words, a Deterministic Network is backwards compatible with - capable
of transporting - statistically multiplexed traffic while preserving the
properties of the accepted deterministic flows.
"

> 
> 3)- In Section 2: "Multiple methods to schedule, shape, limit, and otherwise
> control the transmission of critical packets at each hop through the network
> data plane;" Do you think that it would be good to add something like: "Detnet
> is working on IP Data Plane Encapsulation [ref.] and on MPLS Data Plane
> Encapsulation [ref]?"
[PT>] I'm not too inclined because this sentence is about a lot more than DP 
encoding, ad because this is really fast forwarding a lot.

> 
> 4)- In Section 2: "Robust defenses against misbehaving hosts, routers, or
> bridges,both in the data and control planes...." Do you think that it would be
> good to add here or in the security considerations section (maybe better) a
> reference to draft-ietf-detnet-security?
> 
[PT>] You're right, that fit in both places.

> Nits:
> 
> It would be nice to expand DetNet in Section 1, since it is the first time that it is
> mentioned.
> 
[PT>] done

Many Thanks, Ines : )

Pascal