Re: [nvo3] IETF105 NVO3 Agenda
Greg Mirsky <gregimirsky@gmail.com> Thu, 01 August 2019 16:14 UTC
Return-Path: <gregimirsky@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 6CEB712018F; Thu, 1 Aug 2019 09:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.997
X-Spam-Level:
X-Spam-Status: No, score=-0.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 sj1I87Jvkur5; Thu, 1 Aug 2019 09:14:17 -0700 (PDT)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 319531200E0; Thu, 1 Aug 2019 09:14:17 -0700 (PDT)
Received: by mail-lj1-x231.google.com with SMTP id m23so69898371lje.12; Thu, 01 Aug 2019 09:14:17 -0700 (PDT)
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=7kdY7eyH7JwOMEN5tqsqDZAqnR0UckuAafRCEbbO3Ds=; b=T9qS2ShGuN7/1YqNeGBJdSbyxxJdqQMtlLieYkTdL1t3MIM/IHurSUUWSPwPjANlnI 8q/k9DtCkUTL65wliYJPEtWf6O5cBLaJtF52q8GsRxJP7K3L8NYsRNj0BtnzWfobr0xy GJb4wtKHBmH9jcUcFjcz+TIIPDfjnIrLa4PLQsuy6EMxrWG0SJSitIRoEtq7yjCVWwKK 7Tz64ZwY8ovrH3nNZz+opRvTVTkm+8igb7YsTczKNG2TfpOOMSACVA7cgRNjHhXmSqCv oK2fxiGziCLU3wsBZ3JvbH1bReIAXJbgQsbVftY/LrhWf4M/wtzwjudUaVXlo0X2BC5E Mfxw==
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=7kdY7eyH7JwOMEN5tqsqDZAqnR0UckuAafRCEbbO3Ds=; b=VhGlwFRtFtDzZdX3qW0UMU+NefJ985k0QTMPEzBI1kQ4qvcfjeaWYtt/LBmnPI7Hzf /XOAD8rKM86leKDXpw8YdYknEnzITyJAE862JHtEntzE2KD61MaLaEURulmqCPf8BM8Y /27Bx3uQUrmoNbDGwcDomIHoe5rzA4Jo48kFTYDSARd7K+IryZG3Jlk2Q3YSDc9WoH6t /0UD5zSFWQSvpQMKvU6mrYdUhwZZwS1bvCL2hfXgiO9EvMu1+aYJdAA0vA/m4PDa2m8q qWms3Oo7LazK8Pd0A+gKuNRuZXUtHau3X775CWzqWby7hvi8NMhiF/AwWZ8XdL4JGDVb wVQQ==
X-Gm-Message-State: APjAAAXw5YjdP3RuBLmubu/RHI3VcJ/eHrnwgvrpVg+IW9zKyXIzjr+6 M9OCXq13WyRJ+mJHz+zQiodnqu8xY2lgkQjHpaM=
X-Google-Smtp-Source: APXvYqy+vjuWJVs3CdlU4lTMmyNKXweidDBrh/O3DWZ6nRRGUXnsYGCzvZ9qklyE/LUBSryOp32BggUyUrdaHaAxl0g=
X-Received: by 2002:a2e:7d0c:: with SMTP id y12mr18885794ljc.36.1564676055189; Thu, 01 Aug 2019 09:14:15 -0700 (PDT)
MIME-Version: 1.0
References: <D408889639FC5E4FADB4E00A3E01FA8FC212F4DA@nkgeml513-mbs.china.huawei.com> <CANtnpwgDqgE0OoQvwAgsU_4q-vnFe1aRzscZkdDYy8MoL5fxgw@mail.gmail.com>
In-Reply-To: <CANtnpwgDqgE0OoQvwAgsU_4q-vnFe1aRzscZkdDYy8MoL5fxgw@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 01 Aug 2019 12:14:03 -0400
Message-ID: <CA+RyBmX54L-DCwf=QvtCumHT93fOA7fg6nvAQUvf59VbfGoonw@mail.gmail.com>
To: "B. Khasnabish" <vumip1@gmail.com>
Cc: Liyizhou <liyizhou@huawei.com>, NVO3 <nvo3@ietf.org>, "nvo3-chairs@ietf.org" <nvo3-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000754b77058f10889b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/fEqbgxwJUm3O-Uw6g_YJu9gEBnk>
Subject: Re: [nvo3] IETF105 NVO3 Agenda
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 01 Aug 2019 16:14:19 -0000
Hi Bhumip, much appreciate your kind words and thoughtful suggestions. All actionable are accepted and I'll share the updated version shortly. Also, I agree with your proposal to collect requirements for active OAM in Geneve in this document. Dear All, please consider contributing to the Requirements for Active OAM in Geneve section. Regards, Greg On Wed, Jul 31, 2019 at 11:29 AM B. Khasnabish <vumip1@gmail.com> wrote: > > Hi Greg, > > Thanks for the wonderful presentation and followup discussion on the OAM > for use in Geneve during IETF-105. > > Below pls find a few minor comments/suggestions re . the draft-mmbb-nvo3- > geneve-oam-00 > (OAM for use in GENEVE, https://datatracker.ietf.org/doc/draft-mmbb-nvo3- > geneve-oam/). > > (1) Do you think that a title "Active OAM for use in GENEVE" would better > reflect the intention of the draft & the contents ? If yes, may be you > can consider updating the Title in the next revision, if everyone agrees .. > > (2) The Abstract may be updated as follows..added "OAM" & "...for fault > monitoring .. " > This document defines encapsulation for active Operations, Administration, > and Maintenance (OAM) protocols in Geneve protocol. Also, the format and > operation of the Echo Request and Echo Reply mechanism for fault monitoring > in Geneve are defined. > > (3) At the end of the 1st sentence of Introduction Section (Sec.1), may > need to add the word "encapsulation" > > (4) The last line of the 2nd para of Introduction Section (Sec.1) needs > to be completed.. > > (5) May be you can consider adding Sec.2.1 in order to collect & show all > the Requirements . > > ........ > > Once again, many Thanks in advance. > > Best > > Bhumip > > [Bhumip Khasnabish] > +1-781-752-8003 | vumip1@gmail.com > > <http://turing.acm.org/~bhumip/pub.html> > > > > > On Wed, Jul 17, 2019 at 11:30 PM Liyizhou <liyizhou@huawei.com> wrote: > >> Hi folks, >> >> >> >> Please find the IETF 105 NVO3 agenda. >> >> https://datatracker.ietf.org/meeting/105/materials/agenda-105-nvo3-00 >> >> >> >> Presenters: Please send your slides by Thursday 6pm (July 25). >> >> >> >> See you in Montreal. Travel safe. >> >> >> >> Thanks, >> >> Yizhou >> >> >> >> IETF105 NVO3 WG agenda >> >> ---------------------- >> >> Network Virtualisation Overlays WG >> >> >> >> Friday Afternoon session I - 12:20-13:50 – Duluth >> >> >> >> 1. WG Status update >> >> (WG Chairs, 10mins) >> >> >> >> 2. Security update >> >> (Daniel Migault,20 mins) >> >> draft-mglt-nvo3-geneve-security-requirements-06 >> >> draft-mglt-nvo3-geneve-security-architecture-00 >> >> >> >> 3. Base YANG Data Model for NVO3 Protocols >> >> (Remy Liu, 10 mins) >> >> draft-zhang-nvo3-yang-cfg-06 >> >> >> >> 4. MAC move over Geneve encapsulation >> >> (Sami Boutros, 10 mins) >> >> draft-boutros-nvo3-mac-move-over-geneve-01 >> >> >> >> 5. OAM for use in Geneve >> >> (Greg Mirsky, 15 mins) >> >> draft-mmbb-nvo3-geneve-oam-00 >> _______________________________________________ >> nvo3 mailing list >> nvo3@ietf.org >> https://www.ietf.org/mailman/listinfo/nvo3 >> > _______________________________________________ > nvo3 mailing list > nvo3@ietf.org > https://www.ietf.org/mailman/listinfo/nvo3 >
- [nvo3] IETF105 NVO3 Agenda Liyizhou
- Re: [nvo3] IETF105 NVO3 Agenda B. Khasnabish
- Re: [nvo3] IETF105 NVO3 Agenda Greg Mirsky