Re: [Detnet] Benjamin Kaduk's No Objection on charter-ietf-detnet-01-00: (with COMMENT)

Benjamin Kaduk <kaduk@mit.edu> Thu, 09 April 2020 22:30 UTC

Return-Path: <kaduk@mit.edu>
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 517A93A10CD; Thu, 9 Apr 2020 15:30:21 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 icAZG5g9CUsB; Thu, 9 Apr 2020 15:30:19 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 62BC43A10C8; Thu, 9 Apr 2020 15:30:18 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 039MUCBW024256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 9 Apr 2020 18:30:14 -0400
Date: Thu, 09 Apr 2020 15:30:12 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Janos Farkas <Janos.Farkas@ericsson.com>
Cc: The IESG <iesg@ietf.org>, "detnet@ietf.org" <detnet@ietf.org>, "detnet-chairs@ietf.org" <detnet-chairs@ietf.org>
Message-ID: <20200409223012.GK88064@kduck.mit.edu>
References: <158641436125.2478.11784850947087112876@ietfa.amsl.com> <VI1PR07MB44151A52DB1DD05DF799E738F2C10@VI1PR07MB4415.eurprd07.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <VI1PR07MB44151A52DB1DD05DF799E738F2C10@VI1PR07MB4415.eurprd07.prod.outlook.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/ylRQ-Q1U43UUH5RIyVHkiIQTs38>
Subject: Re: [Detnet] Benjamin Kaduk's No Objection on charter-ietf-detnet-01-00: (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: Thu, 09 Apr 2020 22:30:21 -0000

On Thu, Apr 09, 2020 at 12:31:17PM +0000, Janos Farkas wrote:
> Hi Benjamin,
> 
> Thank you for your review!
> 
> Please see in line.
> 
> -----Original Message-----
> From: detnet <detnet-bounces@ietf.org> On Behalf Of Benjamin Kaduk via Datatracker
> Sent: Thursday, April 9, 2020 8:39 AM
> To: The IESG <iesg@ietf.org>
> Cc: detnet@ietf.org; detnet-chairs@ietf.org
> Subject: [Detnet] Benjamin Kaduk's No Objection on charter-ietf-detnet-01-00: (with COMMENT)
> 
> Benjamin Kaduk has entered the following ballot position for
> charter-ietf-detnet-01-00: No Objection
> 
> When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)
> 
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/charter-ietf-detnet/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> I don't particularly mind the "vertical requirements" bit; "cannot be supported using defined DetNet solutions" does serve to limit scope.
> 
> I do think that clarity around "identify the appropriate WG" would be good, though.
> 
> [Janos Farkas] 
> I hope the updated text is clearer:
> https://mailarchive.ietf.org/arch/msg/detnet/IfEJfMaLP79ar0Cc0d6hzL75HlA/ 

It is; thanks!

> A couple nits:
> 
>      Data plane: This work will document how to use IP and/or MPLS, and
>      related OAM, to support a data plane method of flow identification
>      and packet forwarding over Layer 3. Other IETF defined data plane
>      technologies may also be used.
> 
> nit: "IP and/or MPLS, and related OAM, [...] Other IETF defined data plane technologies" is a somewhat awkward construction.
> 
> [Janos Farkas] 
> To be honest, I have not idea how to improve, what change to make.

I don't have a good idea, either.  The most promising approach is to try to
make a single list, "how to use IP, MPLS, other IETF-defined data plane
technologies, and/or related OAM, to support [...]" but I suspect that
loses some of the intended emphasis on which methods are preferred.  It's
okay to just leave this as-is, I think.

>      Controller Plane: This work will document how to use IETF control
>      plane solutions to support DetNet. This work includes identification
>      of any gaps in existing solutions and identifying the appropriate
>      Working Group for any needed extensions.
> 
> nit: maybe "for developing"?
> 
> This part has been updated:
> https://mailarchive.ietf.org/arch/msg/detnet/IfEJfMaLP79ar0Cc0d6hzL75HlA/

Indeed, this comment is overtaken by events.

Thanks,

Ben