From nobody Mon Feb 8 17:44:41 2021 Return-Path: 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 2DDA33A1797; Mon, 8 Feb 2021 17:44:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EfXXmd63HJer; Mon, 8 Feb 2021 17:44:36 -0800 (PST) Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B06E43A1796; Mon, 8 Feb 2021 17:44:35 -0800 (PST) Received: from fraeml707-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DZQYS32qnz67m5J; Tue, 9 Feb 2021 09:39:40 +0800 (CST) Received: from nkgeml708-chm.china.huawei.com (10.98.57.160) by fraeml707-chm.china.huawei.com (10.206.15.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Tue, 9 Feb 2021 02:44:32 +0100 Received: from nkgeml707-chm.china.huawei.com (10.98.57.157) by nkgeml708-chm.china.huawei.com (10.98.57.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Tue, 9 Feb 2021 09:44:30 +0800 Received: from nkgeml707-chm.china.huawei.com ([10.98.57.157]) by nkgeml707-chm.china.huawei.com ([10.98.57.157]) with mapi id 15.01.2106.006; Tue, 9 Feb 2021 09:44:30 +0800 From: Liyizhou To: "nvo3@ietf.org" CC: "nvo3-chairs@ietf.org" Thread-Topic: call for NVO3 agenda items for IETF110 Thread-Index: Adb+hDlHIESbdSXxRHSlopMFx1qa0A== Date: Tue, 9 Feb 2021 01:44:30 +0000 Message-ID: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.136.98.176] Content-Type: multipart/alternative; boundary="_000_f0b45d2c68f44f0382ced3bc87966b2fhuaweicom_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: [nvo3] call for NVO3 agenda items for IETF110 X-BeenThere: nvo3@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Feb 2021 01:44:40 -0000 --_000_f0b45d2c68f44f0382ced3bc87966b2fhuaweicom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, NVO3 will meet at 15:30-16:30 on Monday, March 8th in IETF110. If you would like to present, please let the chairs and me know. For more information, please check the IETF 110 Preliminary Agenda at https= ://datatracker.ietf.org/meeting/110/agenda.html Please note the agenda times are listed in CET (UTC +1) by default. Cheers, Yizhou --_000_f0b45d2c68f44f0382ced3bc87966b2fhuaweicom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi all,

NVO3 will meet at 15:30-16:30 on Monday, Ma= rch 8^th in IETF110.

If you would like to present, please let th= e chairs and me know.

For more information, please check the IETF 110 Preliminary Agenda at https://datatracker.ietf.org/meeting/110/agenda.html<= /p>

Please note the agenda times are listed in = CET (UTC +1) by default.

Cheers,

Yizhou

--_000_f0b45d2c68f44f0382ced3bc87966b2fhuaweicom_-- From nobody Fri Feb 12 16:38:14 2021 Return-Path: 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 79D2D3A118B; Fri, 12 Feb 2021 16:33:33 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: martin.vigoureux@nokia.com, nvo3@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.25.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <161317641348.31337.17311838358290275670@ietfa.amsl.com> Date: Fri, 12 Feb 2021 16:33:33 -0800 Archived-At: Subject: [nvo3] nvo3 - Requested session has been scheduled for IETF 110 X-BeenThere: nvo3@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Feb 2021 00:33:42 -0000 Dear Matthew Bocci, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. nvo3 Session 1 (1:00 requested) Monday, 8 March 2021, Session II 1530-1630 Room Name: Room 4 size: 504 --------------------------------------------- iCalendar: https://datatracker.ietf.org/meeting/110/sessions/nvo3.ics Request Information: --------------------------------------------------------- Working Group Name: Network Virtualization Overlays Area Name: Routing Area Session Requester: Matthew Bocci Number of Sessions: 1 Length of Session(s): 1 Hour Number of Attendees: 50 Conflicts to Avoid: Chair Conflict: spring sfc rtgwg bess Technology Overlap: mpls People who must be present: Martin Vigoureux Matthew Bocci Sam Aldrin Resources Requested: Special Requests: --------------------------------------------------------- From nobody Mon Feb 15 21:33:52 2021 Return-Path: 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 E2A003A0DDE for ; Mon, 15 Feb 2021 21:33:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.848 X-Spam-Level: X-Spam-Status: No, score=-6.848 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, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c5ag4IN4zdlm for ; Mon, 15 Feb 2021 21:33:48 -0800 (PST) Received: from mail-il1-x134.google.com (mail-il1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06A133A0DC0 for ; Mon, 15 Feb 2021 21:33:47 -0800 (PST) Received: by mail-il1-x134.google.com with SMTP id a16so7365126ilq.5 for ; Mon, 15 Feb 2021 21:33:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=9/PV5+HpNyB1sEJlRo+FaT9mtEDyNS4CnD29n59Vg08=; b=eXQwYzjxXqFW7p1xqDI+PAyzcgKcKC5P01PJMJ7irIqeYi86gFQ2jtvVjkqwLJLXgK 7VqeviNwQ5UbnVwj8lZ9cunf45ZI8JDx52+IkFX7WuCx+PSBqmQM3eJ8Q/OmHR294V2b G2egS/TnlbyA3J+YFipLZNReI9vNkcBga+wMAnxsihjGjaVY1JU3g62RG0yGrvcu5Tks N1s9PmPMSWlQMbLe6km/UYjZhjTaaPRmCnXj8FmIFwwFUJJodGrmG0HmbSuVsvLaBntq OVlaQNicW1wEvzozYx3vEqri/Cta/0gX1fp5QtyJcKXucAmNXViX90jARCnOyeikG+Q4 itXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=9/PV5+HpNyB1sEJlRo+FaT9mtEDyNS4CnD29n59Vg08=; b=mwHsnqxIecoWKm6fAepNhEYIw//DHKynGdGja2Hk2uUXQi4GyUOnUYrmVzsXMG/SKY +n0/LjmWsl5gBbirLCqsd+HHMTKwlehp6NFNmXF7+3lA9VeULZD79bzJilY7LBXJK8oI HF6nm8mLQ8q+Bz7SzR68LjDIRVyIHaOYa5UAQSZ8E1pMpO08g/i9ikm/NpTOVAdf32Ei C2bMe19fAV1bxtCJWMjhEbVjte1tcHDlzRSioKfUEmedz8m8yrYpFKq7Mx8f7q1qI1GL kiTMa1VVuaZi38adwb8CuDJU9YTSXP6c4C43z43FoAsGM5XWlysuFrnDxJ4bdYM37B0F mg2A== X-Gm-Message-State: AOAM530SvqSs4GlGjImsHJdMV5qqe/eMkEa8busfpn+sVwjII+wxAyrL VGoWTTA/JxjY0MlQAKHSPjqFLk0T4X2XIZgXnT8g60Kb4Lw= X-Google-Smtp-Source: ABdhPJzMGtEpeky0U4RHkRaeDFeH4GIEQnAUbbpPPjcEAjYxZH0yjU81kqc2XTSzOBi1WqGEZQ9VVKox4GN8R1dx5xU= X-Received: by 2002:a92:c24b:: with SMTP id k11mr15831520ilo.276.1613453626866; Mon, 15 Feb 2021 21:33:46 -0800 (PST) MIME-Version: 1.0 From: Donald Eastlake Date: Tue, 16 Feb 2021 00:33:36 -0500 Message-ID: To: NVO3 Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [nvo3] You may wish to support or otherwise comment on draft-ietf-idr-flowspec-nvo3 X-BeenThere: nvo3@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Feb 2021 05:33:51 -0000 Hi, draft-ietf-idr-flowspec-nvo3 is a document in the IDR WG about how to specify, in BGP, certain tunnelled flows and actions to take with packets in those flows. There is an "nvo3" in the file name partly for historic reasons. The call is here https://mailarchive.ietf.org/arch/msg/idr/qZK5UeZnp27ecbIcgA9EhOdEs4g/ The existing draft does not cover Geneve encapsulation. Here, for example, is a supporting comment that requests that be included https://mailarchive.ietf.org/arch/msg/idr/GtuhsKNxWhCQ9PDWwCotvBLGPjs/ and here was my response to that https://mailarchive.ietf.org/arch/msg/idr/y-dNvZdZQHmjHQFlc4KJAYqjPgU/ You might want to comment on the draft or post to support it and encourage the inclusion of Geneve or the like, on the idr@ietf mailing list, ideally with the same subject line as the initial call. Thanks, Donald =============================== Donald E. Eastlake 3rd +1-508-333-2270 (cell) 2386 Panoramic Circle, Apopka, FL 32703 USA d3e3e3@gmail.com From nobody Sat Feb 20 20:47:04 2021 Return-Path: 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 436853A1418 for ; Sat, 20 Feb 2021 20:47:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.847 X-Spam-Level: X-Spam-Status: No, score=-1.847 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X0rx_YNtEy5S for ; Sat, 20 Feb 2021 20:47:00 -0800 (PST) Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BAF13A1415 for ; Sat, 20 Feb 2021 20:47:00 -0800 (PST) Received: by mail-io1-xd31.google.com with SMTP id u8so9895113ior.13 for ; Sat, 20 Feb 2021 20:47:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=9H7WZWrl3Rn2FxDAr7i6Hw0cIO69pLibOE5PDghn904=; b=enYRI2DDzEtQWkT2BO2lNNxrtKEt8Rb6afdEcyknJ6REBpY67ogHVtLC8o+4XVLqx/ AzWEvwTgAoh4rwj1lnN6buhkUwBn1yCNBkMaCA3WVEeMItouFXJbJmyr3O7Tpxy4ZDOV 1s3c66794PI0AdbQPDrsv7uDKiCCqCaudHGtIEPjyMiiJarp0QDBMW/I16LiJfo3bNMA GKwU+LiJrpxpEQ2lRo6CTf720TVzfzkULEcMjx/1fHQBVABQHxptgx/GehFSwOa7DBMP 7sqQqb1y3KKqbeN6l6vcIcYPI+lAuePc0U9OHuWd4YAoVp2ASUC0zVM6lEy7wsiC7Fvy wQmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=9H7WZWrl3Rn2FxDAr7i6Hw0cIO69pLibOE5PDghn904=; b=J91m3LwbQhAiYNVreVr7WC3DI2wKAezTVOKmUjUYwvwfhk4hNUa4aigz3sFE3b9ol+ GDXE55F/aymSiDcrShroeOcopJaqlV0HuOHda4J8HJMqGnS0/RBFDVRUyvv5edSy75mX Lj1SWfQ3SVpwKSN10mkQa1+r2szGWhWzHnXo+UXn638Axh6lO5RdGfIoI6WKGom5Qec3 1UrgOxv6/DpNYYYA8m/THLrStVxk1Hqgvc2+FohGf9HCp5/tLMbTcJ2PINsqPiNa8uXx zNQAMqLPQaL94B50gyby48vgeHPjs1Q6IKoEL4cwzXG3ECqBnlxm9qUYaRxfbNF6TvkH xWfg== X-Gm-Message-State: AOAM5310MzlXC4aWsjU5fvFjol0mzYeJsbWU2W9NWg4kvbz+YUDYpjTS CmwdQ/fiTmm7kaPfqGJcsOAV+wNx9ivk4HwW334nf0qP3T0= X-Google-Smtp-Source: ABdhPJzUzbASj2O6jhncqeGzR+Ky1Rz9vH4khFIxGhINL5eqU0DbSIeOXUGsTLyra9XyGWu+/6VbxNW/nWEilckyh7M= X-Received: by 2002:a5d:8d92:: with SMTP id b18mr10555864ioj.167.1613882819448; Sat, 20 Feb 2021 20:46:59 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Donald Eastlake Date: Sat, 20 Feb 2021 23:46:48 -0500 Message-ID: To: NVO3 Content-Type: multipart/alternative; boundary="00000000000029945b05bbd160b3" Archived-At: Subject: Re: [nvo3] You may wish to support or otherwise comment on draft-ietf-idr-flowspec-nvo3 X-BeenThere: nvo3@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Feb 2021 04:47:02 -0000 --00000000000029945b05bbd160b3 Content-Type: text/plain; charset="UTF-8" FYI, the deadline for the WG Last Call in the IDR WG has been extended by one week so, if you want to respond to that call and have not done so yet, you still have time. Thanks, Donald =============================== Donald E. Eastlake 3rd +1-508-333-2270 (cell) 2386 Panoramic Circle, Apopka, FL 32703 USA d3e3e3@gmail.com On Tue, Feb 16, 2021 at 12:33 AM Donald Eastlake wrote: > Hi, > > draft-ietf-idr-flowspec-nvo3 is a document in the IDR WG about how to > specify, in BGP, certain tunnelled flows and actions to take with > packets in those flows. There is an "nvo3" in the file name partly for > historic reasons. The call is here > https://mailarchive.ietf.org/arch/msg/idr/qZK5UeZnp27ecbIcgA9EhOdEs4g/ > > The existing draft does not cover Geneve encapsulation. Here, for > example, is a supporting comment that requests that be included > https://mailarchive.ietf.org/arch/msg/idr/GtuhsKNxWhCQ9PDWwCotvBLGPjs/ > and here was my response to that > https://mailarchive.ietf.org/arch/msg/idr/y-dNvZdZQHmjHQFlc4KJAYqjPgU/ > > You might want to comment on the draft or post to support it and > encourage the inclusion of Geneve or the like, on the idr@ietf mailing > list, ideally with the same subject line as the initial call. > > Thanks, > Donald > =============================== > Donald E. Eastlake 3rd +1-508-333-2270 (cell) > 2386 Panoramic Circle, Apopka, FL 32703 USA > d3e3e3@gmail.com > --00000000000029945b05bbd160b3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

FYI, the deadline for the WG Last Call in= the IDR WG has been extended by one week so, if you want to respond to tha= t call and have not done so yet, you still have time.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=C2=A0Donald E. Eastlak= e 3rd =C2=A0 +1-508-333-2270 (cell)
=C2=A02386 Panoramic Circle, Apopka,= FL 32703 USA
=C2=A0d3e3e3@gmail.com

On Tue, Feb 16, 2021 at 12:33 AM Do= nald Eastlake <d3e3e3@gmail.com&= gt; wrote:

Hi,
draft-ietf-idr-flowspec-nvo3 is a document in the IDR WG about how to
specify, in BGP, certain tunnelled flows and actions to take with
packets in those flows. There is an "nvo3" in the file name partl= y for
historic reasons. The call is here
https://mailarchive.ietf.org/a= rch/msg/idr/qZK5UeZnp27ecbIcgA9EhOdEs4g/

The existing draft does not cover Geneve encapsulation. Here, for
example, is a supporting comment that requests that be included
https://mailarchive.ietf.org/a= rch/msg/idr/GtuhsKNxWhCQ9PDWwCotvBLGPjs/
and here was my response to that
https://mailarchive.ietf.org/a= rch/msg/idr/y-dNvZdZQHmjHQFlc4KJAYqjPgU/

You might want to comment on the draft or post to support it and
encourage the inclusion of Geneve or the like, on the idr@ietf mailing
list, ideally with the same subject line as the initial call.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D
=C2=A0Donald E. Eastlake 3rd=C2=A0 =C2=A0+1-508-333-2270 (cell)
=C2=A02386 Panoramic Circle, Apopka, FL 32703 USA
=C2=A0d3e3e3@gmail.co= m

--00000000000029945b05bbd160b3-- From nobody Sun Feb 21 18:17:44 2021 Return-Path: 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 D16313A07FC; Sun, 21 Feb 2021 18:17:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3F865n-KQjrF; Sun, 21 Feb 2021 18:17:41 -0800 (PST) Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E682C3A07F7; Sun, 21 Feb 2021 18:17:40 -0800 (PST) Received: from fraeml745-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DkQcz4pltz67rP4; Mon, 22 Feb 2021 10:10:27 +0800 (CST) Received: from nkgeml708-chm.china.huawei.com (10.98.57.160) by fraeml745-chm.china.huawei.com (10.206.15.226) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 22 Feb 2021 03:17:38 +0100 Received: from nkgeml707-chm.china.huawei.com (10.98.57.157) by nkgeml708-chm.china.huawei.com (10.98.57.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 22 Feb 2021 10:17:35 +0800 Received: from nkgeml707-chm.china.huawei.com ([10.98.57.157]) by nkgeml707-chm.china.huawei.com ([10.98.57.157]) with mapi id 15.01.2106.006; Mon, 22 Feb 2021 10:17:35 +0800 From: Liyizhou To: "nvo3@ietf.org" CC: "nvo3-chairs@ietf.org" Thread-Topic: call for NVO3 agenda items for IETF110 Thread-Index: Adb+hDlHIESbdSXxRHSlopMFx1qa0AKPDrGg Date: Mon, 22 Feb 2021 02:17:35 +0000 Message-ID: <93d273202f764e3bae912cc07a44a76f@huawei.com> References: In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.136.98.176] Content-Type: multipart/alternative; boundary="_000_93d273202f764e3bae912cc07a44a76fhuaweicom_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: [nvo3] FW: call for NVO3 agenda items for IETF110 X-BeenThere: nvo3@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Feb 2021 02:17:43 -0000 --_000_93d273202f764e3bae912cc07a44a76fhuaweicom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Folks, If you would like to present your work in NVO3 session in IETF 110, please = send the request to us. Thank you. Cheers, Yizhou From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Liyizhou Sent: Tuesday, February 9, 2021 9:45 AM To: nvo3@ietf.org Cc: nvo3-chairs@ietf.org Subject: [nvo3] call for NVO3 agenda items for IETF110 Hi all, NVO3 will meet at 15:30-16:30 on Monday, March 8th in IETF110. If you would like to present, please let the chairs and me know. For more information, please check the IETF 110 Preliminary Agenda at https= ://datatracker.ietf.org/meeting/110/agenda.html Please note the agenda times are listed in CET (UTC +1) by default. Cheers, Yizhou --_000_93d273202f764e3bae912cc07a44a76fhuaweicom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Folk= s,

&n= bsp;

If you = would like to present your work in NVO3 session in IETF 110, please send th= e request to us.

Thank y= ou.

&n= bsp;

Cheers,=

Yizhou<= o:p>

&n= bsp;

From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Liyizhou
Sent: Tuesday, February 9, 2021 9:45 AM
To: nvo3@ietf.org
Cc: nvo3-chairs@ietf.org
Subject: [nvo3] call for NVO3 agenda items for IETF110

Hi all,

NVO3 will meet at 15:30-16:30 on Monday, Ma= rch 8^th in IETF110.

If you would like to present, please let th= e chairs and me know.

For more information, please check the IETF 110 Preliminary Agenda at https://datatracker.ietf.org/meeting/110/agenda.html<= /p>

Please note the agenda times are listed in = CET (UTC +1) by default.

Cheers,

Yizhou

--_000_93d273202f764e3bae912cc07a44a76fhuaweicom_-- From nobody Sun Feb 21 22:13:47 2021 Return-Path: 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 9DB663A0B72; Sun, 21 Feb 2021 22:13:41 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: nvo3@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.26.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: nvo3@ietf.org Message-ID: <161397442160.19898.15208114364447490338@ietfa.amsl.com> Date: Sun, 21 Feb 2021 22:13:41 -0800 Archived-At: Subject: [nvo3] I-D Action: draft-ietf-nvo3-bfd-geneve-01.txt X-BeenThere: nvo3@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Feb 2021 06:13:42 -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 : BFD for Geneve Authors : Xiao Min Greg Mirsky Santosh Pallagatti Jeff Tantsura Filename : draft-ietf-nvo3-bfd-geneve-01.txt Pages : 11 Date : 2021-02-21 Abstract: This document describes the use of the Bidirectional Forwarding Detection (BFD) protocol in point-to-point Generic Network Virtualization Encapsulation (Geneve) tunnels used to make up an overlay network. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-nvo3-bfd-geneve/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-nvo3-bfd-geneve-01 https://datatracker.ietf.org/doc/html/draft-ietf-nvo3-bfd-geneve-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-nvo3-bfd-geneve-01 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/ From nobody Sun Feb 28 19:21:00 2021 Return-Path: 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 022333A139C; Sun, 28 Feb 2021 19:20:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lrdzGU1A5W7l; Sun, 28 Feb 2021 19:20:56 -0800 (PST) Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AA1E3A139B; Sun, 28 Feb 2021 19:20:56 -0800 (PST) Received: from fraeml714-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DplmC0Z1gz67tbq; Mon, 1 Mar 2021 11:16:43 +0800 (CST) Received: from fraeml714-chm.china.huawei.com (10.206.15.33) by fraeml714-chm.china.huawei.com (10.206.15.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 1 Mar 2021 04:20:52 +0100 Received: from DGGEML423-HUB.china.huawei.com (10.1.199.40) by fraeml714-chm.china.huawei.com (10.206.15.33) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2106.2 via Frontend Transport; Mon, 1 Mar 2021 04:20:52 +0100 Received: from DGGEML532-MBX.china.huawei.com ([169.254.8.50]) by dggeml423-hub.china.huawei.com ([10.1.199.40]) with mapi id 14.03.0509.000; Mon, 1 Mar 2021 11:20:49 +0800 From: "Pengshuping (Peng Shuping)" To: "apn@ietf.org" CC: "nvo3@ietf.org" Thread-Topic: eVXLAN carrying Group information Thread-Index: AdcORo5O2ZyXWAGiSueI62HOGIOv/g== Date: Mon, 1 Mar 2021 03:20:49 +0000 Message-ID: <4278D47A901B3041A737953BAA078ADE1994930E@DGGEML532-MBX.china.huawei.com> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.153.195.12] Content-Type: multipart/alternative; boundary="_000_4278D47A901B3041A737953BAA078ADE1994930EDGGEML532MBXchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: [nvo3] eVXLAN carrying Group information X-BeenThere: nvo3@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Mar 2021 03:20:58 -0000 --_000_4278D47A901B3041A737953BAA078ADE1994930EDGGEML532MBXchi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear all, Anybody knows about using eVXLAN to carry the Group information? What is th= e scenario? How the group is identified? Thank you very much! Best regards, Shuping --_000_4278D47A901B3041A737953BAA078ADE1994930EDGGEML532MBXchi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear all,

Anybody knows about using eVXLA= N to carry the Group information? What is the scenario? How the group is id= entified?

Thank you very much!

Best regards,

Shuping

--_000_4278D47A901B3041A737953BAA078ADE1994930EDGGEML532MBXchi_-- From nobody Sun Feb 28 22:50:32 2021 Return-Path: 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 4296D3A168D; Sun, 28 Feb 2021 22:50:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.187 X-Spam-Level: X-Spam-Status: No, score=-0.187 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Izpc6A-VGwRQ; Sun, 28 Feb 2021 22:50:28 -0800 (PST) Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23B6F3A16CB; Sun, 28 Feb 2021 22:50:22 -0800 (PST) Received: by mail-pj1-x1034.google.com with SMTP id b15so10429940pjb.0; Sun, 28 Feb 2021 22:50:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JhUJJRc+QodQtM6n38bNOGb+i1vUkNFyAELjwr0HhOE=; b=hwrlM/iwhVpPg8jLrL6UuDKEqYd3Gok0bG1OqzMWUXD3w3zyMvO2wIzE3IYqQXp1sc f2/KKzdEaqdkUzTM2382S+0OwFVo4sqKW0wGYGxgvMttFn10irqMuwLakHmSi1QqG6KQ DLpOKF+kg9DYoeAnyYpqIbGJxNZ1me8hZ3GL/dD0fgFp2wvULumUqaspOMOQQdfTarX+ fUnb60oFsqL2KdFFI5hbSGnPWI06i/+Fr+3DjMy4oirUDqKORCpsCx3lplwE0J+HoUq8 OSYMDstdYBz06PcxFVD+CkTH3khNkxI/eIn1BxDI0Xp7wTjfNZu88ZSQbo/6siw3N8XM vbWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JhUJJRc+QodQtM6n38bNOGb+i1vUkNFyAELjwr0HhOE=; b=jb9jqeY/yjl7SlEhP1qWVLsV6Jj0Rr/nppbfGffJn//C2HVfACqY4saGeFltTmLHHB XcT1ZQNic2CYerScBYg25x0/wu1d0OWIKWIE1s6ExFDZAheWDBds5Ev+HwiWfl/zc7B/ U49jtm2eM/mkgqRtoU3UcUDc/NbJYcwhlyYNZXDpH6VhQje/X3lVdaagxCG9P3QJZ2gi NkaD6YfLJLDZfFc9tUrLbdCHQukZ7A6IgipbmK2tF3NYx3k33eMO4J/oBaGy9g40ohI7 T1eSwyaaJzxAivJslvxF9nRCUg99q/16ExBMYPRifulBnETWio3QJzVKrViDNmHv8P4f Xthg== X-Gm-Message-State: AOAM533SIhIN3osWc1HmKFWHCQjMfXt5ZwoZjIq6wvcfK7MtqMNforbA L7VgfHy8WvET0wP1eEeEH7R4ZftXrOMpxEa5OiU= X-Google-Smtp-Source: ABdhPJyz9kZrufWL4Aux7VibXRZZU2qIB9/As5r3BlN9xWgS7Tj0qoF+TGkFzFeAPEhtoA+rQwgdvmWxBN9Cc2TNdos= X-Received: by 2002:a17:90a:4a0a:: with SMTP id e10mr15336768pjh.112.1614581419586; Sun, 28 Feb 2021 22:50:19 -0800 (PST) MIME-Version: 1.0 References: <4278D47A901B3041A737953BAA078ADE1994930E@DGGEML532-MBX.china.huawei.com> In-Reply-To: <4278D47A901B3041A737953BAA078ADE1994930E@DGGEML532-MBX.china.huawei.com> From: Gyan Mishra Date: Mon, 1 Mar 2021 01:50:09 -0500 Message-ID: To: "Pengshuping (Peng Shuping)" Cc: "apn@ietf.org" , "nvo3@ietf.org" Content-Type: multipart/alternative; boundary="000000000000f9b97c05bc740765" Archived-At: Subject: Re: [nvo3] eVXLAN carrying Group information X-BeenThere: nvo3@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Mar 2021 06:50:30 -0000 --000000000000f9b97c05bc740765 Content-Type: text/plain; charset="UTF-8" Shuping I am not sure if you are referring to VXLAN-GPE vxlan Generic protocol extension which has changes in the vxlan header to support multi protocol encapsulation, OAM and BUM. https://tools.ietf.org/html/draft-ietf-nvo3-vxlan-gpe-10 The capabilities of the VXLAN-GPE protocol can be extended by defining next protocol "shim" headers that are used to implement new data plane functions. For example, Group-Based Policy (GBP) or In- situ Operations, Administration, and Maintenance (IOAM) metadata functionalities can be added as specified in [I-D.lemon-vxlan-lisp-gpe-gbp ] and [I-D.brockners-ippm-ioam-vxlan-gpe ]. Kind Regards Gyan On Sun, Feb 28, 2021 at 10:21 PM Pengshuping (Peng Shuping) < pengshuping@huawei.com> wrote: > Dear all, > > > > Anybody knows about using eVXLAN to carry the Group information? What is > the scenario? How the group is identified? > > > > Thank you very much! > > > > Best regards, > > Shuping > > > _______________________________________________ > nvo3 mailing list > nvo3@ietf.org > https://www.ietf.org/mailman/listinfo/nvo3 > -- *Gyan Mishra* *Network Solutions A**rchitect * *M 301 502-134713101 Columbia Pike *Silver Spring, MD --000000000000f9b97c05bc740765 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Shuping=C2=A0

<= /div>

I am not sure if you are referring to VXLAN-GPE vxla= n Generic protocol extension which has changes in the vxlan header to suppo= rt multi protocol encapsulation, OAM and BUM.

https://tools.ietf.org/html/draft-ietf-nvo3-vxlan-gpe-= 10

   The capabilities of t=
he VXLAN-GPE protocol can be extended by
   defining next protocol "shim" headers that are used to impleme=
nt new
   data plane functions.  For example, Group-Based Policy (GBP) or In-
   situ Operations, Administration, and Maintenance (IOAM) metadata
   functionalities can be added as specified in
   [I-D.lemon-vxlan=
-lisp-gpe-gbp] and
   [I-D.brockners-i=
ppm-ioam-vxlan-gpe].

Kind Regards=C2=A0

Gyan

On Sun, Fe= b 28, 2021 at 10:21 PM Pengshuping (Peng Shuping) <pengshuping@huawei.com> wrote:

Dear all, =

=C2=A0

Anybody knows about using eVXLA= N to carry the Group information? What is the scenario? How the group is id= entified?

=C2=A0

Thank you very much! =

=C2=A0

Best regards,

Shuping

=C2=A0

_______________________________________________
nvo3 mailing list
nvo3@ietf.org
https://www.ietf.org/mailman/listinfo/nvo3

Gyan Mishra

Network Solutio= ns Architect= =C2=A0

M 301 502-1347
13101 Colum= bia Pike=C2=A0
Silver Spring, MD

--000000000000f9b97c05bc740765--