Re: [ippm] Draft agenda for IETF 104

Greg Mirsky <gregimirsky@gmail.com> Mon, 18 March 2019 09:42 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 865DD128CE4 for <ippm@ietfa.amsl.com>; Mon, 18 Mar 2019 02:42:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable 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 Ud4612TS8IMy for <ippm@ietfa.amsl.com>; Mon, 18 Mar 2019 02:42:33 -0700 (PDT)
Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (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 38D04128D0B for <ippm@ietf.org>; Mon, 18 Mar 2019 02:42:31 -0700 (PDT)
Received: by mail-lf1-x132.google.com with SMTP id u68so11177082lff.7 for <ippm@ietf.org>; Mon, 18 Mar 2019 02:42:31 -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=jSlqWzDIi2gzHH0tGxBVxVZRrV4GlGAojlF5F8GHas0=; b=EBvBMkha4gQnrUK6juqPMMcsn4LdIn1Uc9mZfkZk2HKtk1c5rRTt1NEk1WNgzXm98L sVu/ZzyyCzc7oOuNzbpmohVmubiAdD8yRnxzKhdsvmffPZGQ+x7g8KS/8k/ml0qRRqqm aeBpAlrTeMg+iJk/rbdMVz7DZ0lH2cnV0crL5np6+DpHD+RGOFa396UjGUKLK10XXUFf AtUWFl5b0xi1rLcE4X3COssvCk3zRA/CLtLzEXoRFD737z2/MQC0rIpl1owd5kB4ZlEv h3F6m8CSJTmO9twpOMSh2Xm2FiFnlhEmCI2EzgcVTwX4sFJgdm0qtgxaWQvBqePWu3WU llXA==
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=jSlqWzDIi2gzHH0tGxBVxVZRrV4GlGAojlF5F8GHas0=; b=fuqbKwFOPZsVYZsndEUtERk61qloICs9Rlmtq0LPWSszm8wGpLDwDmnc1KK0Uwqv1H ZrBtqBpUW9lRoniiqcLtwRWlD1fKQyaWEtzw5uq4sJ7fmHvA21Ck55iGoLL8aqiu+KbE ZuyTEq/fRvC26M3TVEcPinl36w6VXVlhKdYs2+WyWt77CKzFQcXf9XDvKIc0FtrBV23Z LYnXUdAQXtKaM8jVyP3uUWBtxAmwfA0h1psIQj5S9YzGh/4ESAxNtYwfjFstDcgwK3+G IXbT3PIU+3q8kDHXL5T3NWdz6u8dFk4NkVg8THnywFNl7JSMQprUIIAbNm9czfOOHj04 TUSw==
X-Gm-Message-State: APjAAAWRc4VyW4hL8/j8O3wzfd2BoLcY5EaFHduLcgTOCTlteCH4uZ7m lJ7GFLHDzRdjWU0JAwVnzFevqoNXGgFn275UNBY=
X-Google-Smtp-Source: APXvYqy1i8QIk0V1CPB8IZY4jvrTNB7+Ize1ZvsCfjo0uRIXpRl0RG2KedrqjTs60lyhH6lRlGgl/ejRc1SPrkvgceM=
X-Received: by 2002:a19:ee18:: with SMTP id g24mr9629489lfb.158.1552902149104; Mon, 18 Mar 2019 02:42:29 -0700 (PDT)
MIME-Version: 1.0
References: <F2ABDB31-380C-43B1-9B3D-BB5C5E309DD8@apple.com> <CA+RyBmWS58i3qNgit1P9YZSZn5Op+J4+caWGe8kORJpwXJb-fA@mail.gmail.com> <B6815E8D-48F3-45E8-B71C-C6F3EEBBF7EF@apple.com> <CY4PR11MB13356537CD317FF3AA5925C0DA470@CY4PR11MB1335.namprd11.prod.outlook.com>
In-Reply-To: <CY4PR11MB13356537CD317FF3AA5925C0DA470@CY4PR11MB1335.namprd11.prod.outlook.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 18 Mar 2019 10:42:18 +0100
Message-ID: <CA+RyBmVKqiX2v_880FM+k4JfA8r__9uY_MH0sKqTUTHMv7zF1A@mail.gmail.com>
To: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
Cc: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>, IETF IPPM WG <ippm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f7e85205845b3431"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/ZK-vwpxPMPeJpBmeKOxIctCZ9C4>
Subject: Re: [ippm] Draft agenda for IETF 104
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2019 09:42:38 -0000

Hi Frank,
thank you for taking the proactive step to have a productive discussion in
Prague. I think that we have a pretty good understanding of the iOAM
related drafts presented to IPPM WG, some several times, before. Thus, I
cannot see another 13+ minutes being spent on re-representing them as
efficient use of everyone time. The scope of the draft-ietf-ippm-ioam-data
is declared as "the data fields and associated data types for in-situ OAM".
Based on that, I suggest that authors of the iOAM encapsulations drafts,
e.g., Ethernet, IPv6, Optical, etc., work with the Responsible AD to help
them find WGs to work on their respective documents. The rest is what we
could discuss. How many non-encapsulation iOAM drafts that will be?

Regards,
Greg

On Mon, Mar 18, 2019 at 10:28 AM Frank Brockners (fbrockne) <
fbrockne@cisco.com> wrote:

> Hi IPPM WG,
>
>
>
> Tommy asked me to facilitate the IOAM discussion. Per Tommy’s note below,
> we want to discuss the entire set of IOAM related documents and decide on
> next steps.
>
>
>
> Given that we have a pretty large set of IOAM related individual drafts
> (currently 13 drafts, if I counted things correctly), I suggest that we do
> a very brief lightening talk (< 1 min – hard policed) on each document and
> then have a discussion on which categories and documents IPPM WG should
> consider for adoption.  In order to ease the “lightening talk” section –
> I’ve created a template
> https://docs.google.com/presentation/d/1P1Kp9mXA0eKkws78p1tldFn8zqx0YPQ5TK5fnq6Vyz4
> - where each draft is listed with title and abstract. An author of each
> draft should present the key points of the drafts – as well as answer the
> question, whether IPPM should consider WG adoption.
> If you’re an author, please feel free to update the particular slide of
> your draft according to what you think is required.
>
>
>
> Here’s a draft agenda for the 40min IOAM slot:
>
>
>
> ·        IOAM data draft  / WG document (10min)
>
> ·        draft-ietf-ippm-ioam-data-05 – 10min
>
> ·        Review of individual IOAM drafts by category  (13min, 1min each
> max)
>
> ·        *IOAM encapsulation (9min)*
>
> ·        Draft-weis-ippm-ioam-eth-01 (new)
>
> ·        Draft-ioametal-ippm-6man-ioam-ipv6-options-01
>
> ·        Draft-ioametal-ippm-6man-ioam-ipv6-deployment-00 (new)
>
> ·        Draft-brockners-ippm-ioam-geneve-02 (new)
>
> ·        Draft-gafni-ippm-ioam-ipv4-options-00 (new)
>
> ·        Draft-ali-6man-spring-srv6-oam-00 (new)
>
> ·        Draft-anand-ippm-po-ioam-02 (new)
>
> ·        Draft-gandhi-spring-ioam-sr-mpls-00
>
> ·        Draft-ali-spring-ioam-srv6-00
>
> ·        *IOAM data export (1min)*
>
> ·        Draft-spiegel-ippm-ioam-rawexport-01
>
> ·        *IOAM YANG models/operations (2 min)*
>
> ·        Draft-zhou-ippm-ioam-yang-03 (new)
>
> ·        Draft-mizrahi-ippm-ioam-profile-00 (new)
>
> ·        IOAM tools (1min)
>
> ·        Draft-xiao-ippm-ioam-conf-state-03 (new)
>
> ·        Discussion and Hums (15min)
>
> ·        Which categories of IOAM documents make sense for IPPM to adopt?
>
> ·        WG adoption of certain drafts (for those categories and drafts
> which apply)?
>
>
>
> Did I miss any document that should be added to the list above? If so,
> please let us know – and add another slide to the google slide deck.
> The deck should be editable by anyone.
>
>
>
> Thanks, Frank
>
>
>
> *From:* ippm <ippm-bounces@ietf.org> *On Behalf Of * Tommy Pauly
> *Sent:* Mittwoch, 13. März 2019 01:24
> *To:* Greg Mirsky <gregimirsky@gmail.com>
> *Cc:* IETF IPPM WG <ippm@ietf.org>
> *Subject:* Re: [ippm] Draft agenda for IETF 104
>
>
>
> To clarify, the time allocated for IOAM is not allocated just to
> discuss draft-ietf-ippm-ioam-data. That currently is the one IOAM document
> that is a WG document, but there is a list of many other documents that
> have been submitted as "-ippm" individual drafts. We want to use this time
> to figure out collectively as a group how we want to approach this work
> going forward, and where the documents best belong. The goal of this
> discussion is to come out with a clear picture of what work we think makes
> sense for IPPM. This will hopefully be more fruitful than having many
> individual lightning talks for these topics.
>
>
>
> Best,
>
> Tommy
>
>
>
> On Mar 12, 2019, at 11:12 AM, Greg Mirsky <gregimirsky@gmail.com> wrote:
>
>
>
> Hi Tommy,
>
> given how dense is our agenda for Prague, allotting 40 minutes for one
> draft seems as overgenerous. If there are updates to IOAM individual
> drafts, then should these be explicitly listed among other individual
> drafts that have allocated 5 minutes each?
>
>
>
> Kind regards,
>
> Greg
>
>
>
> On Tue, Mar 12, 2019 at 10:35 AM Tommy Pauly <tpauly=
> 40apple.com@dmarc.ietf.org> wrote:
>
> Hello IPPM,
>
> We've posted our draft agent for IETF 104 here:
> https://datatracker.ietf.org/meeting/104/materials/agenda-104-ippm-00
>
> We have a two-hour slot, and are pretty full! The chairs have discussed
> and would like to have two more extended discussions this time about:
> - Finalizing the metrics and initial registries, so we can get those out
> the door
> - How we should progress with IOAM and the large cluster of related
> documents. We'll ask that instead of having any lightning talks on related
> IOAM documents, we have a broader discussion about what we're doing for
> these.
>
> After that, the agenda is made up of 5 minute lightning talks, with a
> group of related alt-mark documents at the start. Apologies that we can't
> have longer time for these!
>
> Suggestions or bashing welcome!
>
> Best,
> Tommy
>
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm
>
>
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm
>