[nvo3] Last Call: <draft-ietf-nvo3-encap-09.txt> (Network Virtualization Overlays (NVO3) Encapsulation Considerations) to Informational RFC

The IESG <iesg-secretary@ietf.org> Sat, 04 November 2023 07:44 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
CC: Matthew Bocci <matthew.bocci@nokia.com>, andrew-ietf@liquid.tech, draft-ietf-nvo3-encap@ietf.org, matthew.bocci@nokia.com, nvo3-chairs@ietf.org, nvo3@ietf.org
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <169908385909.64170.16765433988215757299@ietfa.amsl.com>
Date: Sat, 04 Nov 2023 00:44:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/zQyRmSLordwIpYEzrmN6FHUuM5k>
Subject: [nvo3] Last Call: <draft-ietf-nvo3-encap-09.txt> (Network Virtualization Overlays (NVO3) Encapsulation Considerations) to Informational RFC

The IESG has received a request from the Network Virtualization Overlays WG
(nvo3) to consider the following document: - 'Network Virtualization Overlays
(NVO3) Encapsulation Considerations'
  <draft-ietf-nvo3-encap-09.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2023-11-18. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   The IETF Network Virtualization Overlays (NVO3) Working Group Chairs
   and Routing Area Director chartered a design team to take forward the
   encapsulation discussion and see if there was potential to design a
   common encapsulation that addresses the various technical concerns.
   This document provides a record, for the benefit of the IETF
   community, of the considerations arrived at by the NVO3 encapsulation
   design team, which may be helpful with future deliberations by
   working groups over the choice of encapsulation formats.

   There are implications of having different encapsulations in real
   environments consisting of both software and hardware implementations
   and within and spanning multiple data centers.  For example, OAM
   functions such as path MTU discovery become challenging with multiple
   encapsulations along the data path.

   The design team recommended Geneve with a few modifications as the
   common encapsulation. This document provides more details,
   particularly in Section 7.





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-nvo3-encap/



No IPR declarations have been submitted directly on this I-D.

[nvo3] Last Call: <draft-ietf-nvo3-encap-09.txt> … The IESG