Re: [Detnet] Alvaro Retana's Yes on draft-ietf-detnet-problem-statement-07: (with COMMENT)

Alvaro Retana <aretana.ietf@gmail.com> Wed, 19 December 2018 21:06 UTC

Return-Path: <aretana.ietf@gmail.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 5E145130EC9; Wed, 19 Dec 2018 13:06:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ab_fOkIaAudV; Wed, 19 Dec 2018 13:06:02 -0800 (PST)
Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) (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 C1E58130E86; Wed, 19 Dec 2018 13:06:01 -0800 (PST)
Received: by mail-oi1-x231.google.com with SMTP id v6so2803123oif.2; Wed, 19 Dec 2018 13:06:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=s1YrYL2gNnFQkNJhz2ycPABm9zkiVMakjpIC1mwb2bE=; b=AfAL23h0QfFCCkkO3Mrze+oeiv8PdBD4FlbfKRL9RypmMxY5Jluq/Ilx5KchNs9YpD +pm0QhYPvgR9YydfXQnvXIvsPyQhIq8ADNpZFYC/uAx/rS+upnKqCCr15ywkmacu1y50 DESuMM9aCiXXlbGMi0rh6FSAzfY4Z33MqxVYjdgJtBRhSGii/mOQgNzlNbz7OyOzi0BR SdH6v67AxAWvHEJ3JaNiqW8dsYIY7S8Ok0MpY/NMq0fjvx0Vf2zYDzt3jTjdE8RPKEoy B+P0xgCfQ3v1fVq/gr+mVHJi5kCFMITQ4RI3244FHyvV15GjadGFiI8By0Hf+cnBKJWh n0DA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=s1YrYL2gNnFQkNJhz2ycPABm9zkiVMakjpIC1mwb2bE=; b=GtbcWJfFoF6K/vnxvYdPpyY5r14ILeDGTt881vIvJ5J271TexlnJ4WTs1Nz+w54gFm jXHOOyz9qJ6PgSwC8+EF2m7y4FetXP/f1PHFPeGHS8sKAX/nX2d/g3v84z6lyz6Ofafp YK2ekpu9oBSeoB8+dVBpp/dVMqA3wjbxTorwaAd+YyC46Od1vzqn4j6ZA+MOjkZHZ9d0 fJSIlqs+eL90M0oxAJQgstSYNAEKYQFBnLNfFsbMlkhuxSF2hqVhkZ69oh/CFeELqtii sUB0jmICdogEh975V6vEzbLm7RxHxtXLx2rjIoFuWyOnjVW57W744D6ac6ieoAK62B2F b9ZA==
X-Gm-Message-State: AA+aEWapOxYDA/udNkq8r7dxRraIVaCpXfd6+9Ne/490l1vKibvQKvSD yqjiQ7Sh3Y4kBJsaLLTWjMUUD/grlZ9RnyfS6is=
X-Google-Smtp-Source: AFSGD/VfjcQBMoucAPJbT9Qrqrf3deyaNlyC+lLjCECsh9a8ZI7AULUpncn9wqa3VECx27tBleRjeakZPQ3UfUL6Bzw=
X-Received: by 2002:aca:b6c3:: with SMTP id g186mr288842oif.289.1545253561136; Wed, 19 Dec 2018 13:06:01 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 19 Dec 2018 13:06:00 -0800
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <70f06a054a6c4fa4881ad54d61a0bc2a@XCH-RCD-001.cisco.com>
References: <70f06a054a6c4fa4881ad54d61a0bc2a@XCH-RCD-001.cisco.com>
X-Mailer: Airmail (528)
MIME-Version: 1.0
Date: Wed, 19 Dec 2018 13:06:00 -0800
Message-ID: <CAMMESswwtODOPgpeGUsVgznV97LX6LqwXc+firnwiNbOUUwMHQ@mail.gmail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Cc: Lou Berger <lberger@labn.net>, "detnet-chairs@ietf.org" <detnet-chairs@ietf.org>, "draft-ietf-detnet-problem-statement@ietf.org" <draft-ietf-detnet-problem-statement@ietf.org>, IESG <iesg@ietf.org>, "detnet@ietf.org" <detnet@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000997c09057d6661b8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/wckeUdIxUaQqKViczxPPmzmwGRk>
Subject: Re: [Detnet] Alvaro Retana's Yes on draft-ietf-detnet-problem-statement-07: (with COMMENT)
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: Wed, 19 Dec 2018 21:06:03 -0000

Pascal:

Hi!

The document is fine with me…this was just a non-blocking comment to say
that I would have preferred one document instead of two…but no change is
needed.

Thanks for following up.

Alvaro.

On December 19, 2018 at 11:39:07 AM, Pascal Thubert (pthubert) (
pthubert@cisco.com) wrote:

Hello Alvaro :



I was digging the datatracker and found the following comment from you:

“

Given the close relationship between this document and
draft-ietf-detnet-use-cases, I think that it would have been beneficial to
produce a single document.  As it stands neither one normatively references
the other.



draft-ietf-detnet-architecture-09 says it better:



   The Deterministic Networking Problem Statement

   [I-D.ietf-detnet-problem-statement] introduces Deterministic

   Networking, and Deterministic Networking Use Cases

   [I-D.ietf-detnet-use-cases] summarizes the need for it.

I’m sorry I cannot remember seeing this comment before, and I could not dig
it in my mail client, so I do not know what happened with it.



As it goes, the problem statement precedes the architecture document and
cannot really reference it normatively.

On the other hand the problem statement is a consequence of the use case
draft so it is heavily based on it.



Still there is a forward note that references it, so we do have a reference.

                 Forward note: The DetNet Architecture

   [I-D.ietf-detnet-architecture] is the document produced by the DetNet

   WG to describe that model.





But in general when we mention a DetNet architecture we present it as an
abstract architecture to be defined as opposed to work already done, so we
abstained to have a reference to the architecture draft.



More than that seems artificial and I’m tempted to leave things as is. If
you think it is important then I’m OK add a sentence or modify the one
quoted above in the next editions.



Please let us know if that’s OK?



Pascal