[nvo3] Paul Wouters' Abstain on draft-ietf-nvo3-encap-11: (with COMMENT)

Paul Wouters via Datatracker <noreply@ietf.org> Wed, 14 February 2024 21:08 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: nvo3@ietf.org
Delivered-To: nvo3@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D8E89C14CEE3; Wed, 14 Feb 2024 13:08:52 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Paul Wouters via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-nvo3-encap@ietf.org, nvo3-chairs@ietf.org, nvo3@ietf.org, Matthew Bocci <matthew.bocci@nokia.com>, matthew.bocci@nokia.com
X-Test-IDTracker: no
X-IETF-IDTracker: 12.5.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Paul Wouters <paul.wouters@aiven.io>
Message-ID: <170794493287.51625.2714628190839223841@ietfa.amsl.com>
Date: Wed, 14 Feb 2024 13:08:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/mBGsAqBk9xynDgDZx11lY_Ugfbg>
Subject: [nvo3] Paul Wouters' Abstain on draft-ietf-nvo3-encap-11: (with COMMENT)
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Feb 2024 21:08:52 -0000

Paul Wouters has entered the following ballot position for
draft-ietf-nvo3-encap-11: Abstain

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.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-nvo3-encap/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I also believe that a Design Team's output consists of only input to the WG. So
I would be okay if the document mentions that work was done via a design team,
but that the text should be updated to replace all current tense occurrences of
the DT to either "WG" or some other kind of generalized phrasing. The shepherds
review states there was strong WG consensus on this document, so why not make
this WG document come from the WG properly, and perhaps have a single section
mentioning/crediting the work(flow) of the Design Team?

I believe the content is worth publishing, but I feel this is a slippery slope
to have design teams write RFCs