[nvo3] I-D Action: draft-ietf-nvo3-encap-04.txt
internet-drafts@ietf.org Thu, 23 January 2020 20:14 UTC
Return-Path: <internet-drafts@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 B6754120BB1; Thu, 23 Jan 2020 12:14:59 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: nvo3@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.116.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: nvo3@ietf.org
Message-ID: <157981049962.22864.2284788970778033924@ietfa.amsl.com>
Date: Thu, 23 Jan 2020 12:14:59 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/xprRwIeBt4a3L_CpbXpvKcyKsJY>
Subject: [nvo3] I-D Action: draft-ietf-nvo3-encap-04.txt
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 23 Jan 2020 20:15:00 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Network Virtualization Overlays WG of the IETF. Title : NVO3 Encapsulation Considerations Author : Sami Boutros Filename : draft-ietf-nvo3-encap-04.txt Pages : 19 Date : 2020-01-23 Abstract: As communicated by WG Chairs, the IETF NVO3 chairs and Routing Area director have chartered a design team to take forward the encapsulation discussion and see if there is potential to design a common encapsulation that addresses the various technical concerns. There are implications of different encapsulations in real environments consisting of both software and hardware implementations 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 recommend Geneve with few modifications as the common encapsulation, more details are described in section 7. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-nvo3-encap/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-nvo3-encap-04 https://datatracker.ietf.org/doc/html/draft-ietf-nvo3-encap-04 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-nvo3-encap-04 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- [nvo3] I-D Action: draft-ietf-nvo3-encap-04.txt internet-drafts