Re: [Tm-rid] Benjamin Kaduk's Block on charter-ietf-tmrid-00-03: (with BLOCK and COMMENT)

Benjamin Kaduk <kaduk@mit.edu> Fri, 07 February 2020 22:37 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: tm-rid@ietfa.amsl.com
Delivered-To: tm-rid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B989A120103; Fri, 7 Feb 2020 14:37:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 OG0IrJ5AC2US; Fri, 7 Feb 2020 14:37:42 -0800 (PST)
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 ADFA21200FA; Fri, 7 Feb 2020 14:37:42 -0800 (PST)
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 017MbLii002598 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 7 Feb 2020 17:37:24 -0500
Date: Fri, 07 Feb 2020 14:37:21 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Cc: The IESG <iesg@ietf.org>, The IAB <iab@iab.org>, "tm-rid@ietf.org" <tm-rid@ietf.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <20200207223721.GD14382@kduck.mit.edu>
References: <158097042097.30642.12144712233440703137.idtracker@ietfa.amsl.com> <25DC0F80-4881-4576-A42D-A514A32E77D7@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <25DC0F80-4881-4576-A42D-A514A32E77D7@cisco.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/_az_aekn_jsbOhZWwBdk1D89CJk>
Subject: Re: [Tm-rid] Benjamin Kaduk's Block on charter-ietf-tmrid-00-03: (with BLOCK and COMMENT)
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Trustworthy Multipurpose RemoteID <tm-rid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tm-rid>, <mailto:tm-rid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tm-rid/>
List-Post: <mailto:tm-rid@ietf.org>
List-Help: <mailto:tm-rid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tm-rid>, <mailto:tm-rid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2020 22:37:45 -0000

Hi Éric,

On Fri, Feb 07, 2020 at 07:54:01PM +0000, Eric Vyncke (evyncke) wrote:
> As discussed over our IESG telechat of 6th of February, the charter for DRIP (new potential name for TM-RID)  has been updated to take into account all comments received by email or during the telechat.
> 
> https://datatracker.ietf.org/doc/charter-ietf-tmrid/
> 
> Ben, Magnus, if you agree with the improved charter, then can you clear your BLOCK so that the charter could proceed to the external review ?

I like the direction this is going; thanks to all who worked on it!

With respect to:

% * Protocol design: while the primary purpose of DRIP WG is to leverage
% existing protocols, the specificities of the UAS environment are likely to
% require existing protocols to be extended or new protocols to be designed.
% The WG will be focused on standardizing these protocols or extensions.

This could be read as saying that DRIP will extend existing protocols,
including ones that already have a WG to maintain the protocol.  Typically
we say that WGs will coordinate with the protocol-maintenance WGs to get
the work done (i.e., focus on the work and not who is doing it).

So perhaps "The WG will focus on getting these protocols or extensions
standardized, coordinating with other WGs relevant for the protocol(s) in
question on the most appropiate home for any given piece of work."?

-Ben