IETF Logo Mail Archive

Re: [nvo3] I-D Action: draft-ietf-nvo3-encap-10.txt

Donald Eastlake <d3e3e3@gmail.com> Mon, 06 November 2023 10:21 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5481C1B0323 for <nvo3@ietfa.amsl.com>; Mon, 6 Nov 2023 02:21:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.855
X-Spam-Level:
X-Spam-Status: No, score=-6.855 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GFc2earEeWZX for <nvo3@ietfa.amsl.com>; Mon, 6 Nov 2023 02:21:44 -0800 (PST)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4963EC1519B2 for <nvo3@ietf.org>; Mon, 6 Nov 2023 02:21:44 -0800 (PST)
Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-53e70b0a218so7305497a12.2 for <nvo3@ietf.org>; Mon, 06 Nov 2023 02:21:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699266102; x=1699870902; darn=ietf.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=28s/QMAgk2RQQASnccNgM2syK+O/6CV0biLxhyekaOg=; b=hjiYnFWzw8Hs0or3+QWOkTJh5zL+c3SColDJa2+CdSVIPh8huL8Z3zYUjIpXUAMHZv 2aLfTQGuOS368D787C4O4UKDKCdp7OPfNrxJAfBu6mTX3NUEaIqglDwp6/X5R9xX50Hv Dl2yIGV9Ar9Y21KLzk/WfAgh8bizb6m9KSh8sc/FYMnKJ+oy0sj4FTZhkEyYniK57Ysp 56fqI6UpG6oBWeTukBofzDkTRI5b09hShmTrg2adeiCdsSAFA40oeNwKsPBQ77r8XFiF exd7ZKaDrg0Yn+kX2lC1tRSru4U2zGFNvFYztZTTQbDHMO956dXO8IKTydHG5yqbYuvx t5DQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699266102; x=1699870902; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=28s/QMAgk2RQQASnccNgM2syK+O/6CV0biLxhyekaOg=; b=r0ahGY7iX0Mqebt/5W0YR1IB2fq3j91HgXOgJAioZ+1P/+ms6hK3SMBqceojMa3HC4 e62igqbvrgxo3JVS2leXapAgb2UXkWQduJ5IDjJnqvl+a4pzjCuUMP4B5OCFRNy+d32A hfdbuiLXxHLooxvDJzVn17uscZU9aW8o2G4GHgEVVA4u2yp6LAdxNF5wgK/76TzEkB+e 4u8fqnWBn5eAG3UVV8UORaE/cdCmS+hlyw9ZxJelJKeG4oJNSlasaGUwqCydTVtd86/h EBM4KlxQtfPd4egObNILBu+6ZFpJSz6v1+koXdo2tBS9/hn2HwX16bZ0XGJvq0vQ4GyN EUpg==
X-Gm-Message-State: AOJu0YzBFWozFEhRHjmqk9AXc6qQh/CUe62NnQ9iV5fDnzC9+oNNCm4v hlN50Yuaasn8GPd+kHRYOjEDirw/Qw5SzFcbOgr5kb3wnGM=
X-Google-Smtp-Source: AGHT+IFc2m9lnKTxYlrI6fasBa2FMQirILXOrUOLW8M/e/pFUAh/HnPjqOUIHWSEwqryVKXZa7Pk3F0YrI85a8raBxQ=
X-Received: by 2002:a50:fc01:0:b0:541:2476:d23e with SMTP id i1-20020a50fc01000000b005412476d23emr22161401edr.28.1699266102195; Mon, 06 Nov 2023 02:21:42 -0800 (PST)
MIME-Version: 1.0
References: <169926592443.1177.1951893515679823277@ietfa.amsl.com>
In-Reply-To: <169926592443.1177.1951893515679823277@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 06 Nov 2023 05:21:31 -0500
Message-ID: <CAF4+nEEf5pxqQHsSWd0B=cssNCsx4pJuFZqyNJ_pxyo=o63Y=g@mail.gmail.com>
To: nvo3@ietf.org
Content-Type: multipart/alternative; boundary="000000000000667a080609793842"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/3mG-sZkOS7pyoVlCSGYAE5EW8yc>
Subject: Re: [nvo3] I-D Action: draft-ietf-nvo3-encap-10.txt
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
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: Mon, 06 Nov 2023 10:21:45 -0000

There are no technical changes in this revision. It fixes an incorrect text
reference to the IDR WG 🙂 as where to send comments and has a number of
formatting changes due to converting from nroff source to XMLv3 source
which should make things easier going forward.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com


On Mon, Nov 6, 2023 at 5:18 AM <internet-drafts@ietf.org> wrote:

> Internet-Draft draft-ietf-nvo3-encap-10.txt is now available. It is a work
> item of the Network Virtualization Overlays (NVO3) WG of the IETF.
>
>    Title:   Network Virtualization Overlays (NVO3) Encapsulation
> Considerations
>    Authors: Sami Boutros
>             Donald E. Eastlake 3rd
>    Name:    draft-ietf-nvo3-encap-10.txt
>    Pages:   25
>    Dates:   2023-11-06
>
> 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 IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-nvo3-encap/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-nvo3-encap-10.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-nvo3-encap-10
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3
>

v2.23.0 | Report a Bug | By Email