[nvo3] Robert Wilton's Yes on draft-ietf-nvo3-encap-11: (with COMMENT)

Robert Wilton via Datatracker <noreply@ietf.org> Tue, 13 February 2024 09:22 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 2D427C14F5EC; Tue, 13 Feb 2024 01:22:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton 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: Robert Wilton <rwilton@cisco.com>
Message-ID: <170781615916.62925.4767718644282999845@ietfa.amsl.com>
Date: Tue, 13 Feb 2024 01:22:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/7JtAEJKZeNiwe8JniVHYmXR86B8>
Subject: [nvo3] Robert Wilton's Yes 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: Tue, 13 Feb 2024 09:22:39 -0000

Robert Wilton has entered the following ballot position for
draft-ietf-nvo3-encap-11: Yes

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 think that some questions have been raised as to whether this sort of draft
about a design team's reasoning and discussions should be published as an RFC. 
To me, I read this document as the supporting justification as to the path
taken vs the paths not taken, and I suspect that this reasoning could
potentially be useful for other engineers considering similar issues.  Hence,
writing it down and publishing it somewhere accessible is potentially useful,
and as Informational RFC seems like a reasonable place, and better than, e.g.,
a wiki page that would likely suffer from bit rot.

Thanks for spending the time to write it and run it through the process.

Regards,
Rob