Re: [ippm] Draft agenda for IETF 104

"Brian Trammell (IETF)" <ietf@trammell.ch> Sun, 24 March 2019 20:06 UTC

Return-Path: <ietf@trammell.ch>
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 5649F1200A3 for <ippm@ietfa.amsl.com>; Sun, 24 Mar 2019 13:06:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 UPhjc_qaaLh5 for <ippm@ietfa.amsl.com>; Sun, 24 Mar 2019 13:06:31 -0700 (PDT)
Received: from smtp-sh.infomaniak.ch (smtp-sh.infomaniak.ch [128.65.195.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13A0712009E for <ippm@ietf.org>; Sun, 24 Mar 2019 13:06:30 -0700 (PDT)
Received: from smtp8.infomaniak.ch (smtp8.infomaniak.ch [83.166.132.38]) by smtp-sh.infomaniak.ch (8.14.5/8.14.5) with ESMTP id x2OK6MKa027313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sun, 24 Mar 2019 21:06:23 +0100
Received: from [192.168.21.127] ([80.250.3.147]) (authenticated bits=0) by smtp8.infomaniak.ch (8.14.5/8.14.5) with ESMTP id x2OK6Kl8110732 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 24 Mar 2019 21:06:21 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
In-Reply-To: <CY4PR11MB1335695F04CABF482D0D6234DA470@CY4PR11MB1335.namprd11.prod.outlook.com>
Date: Sun, 24 Mar 2019 21:06:20 +0100
Cc: Greg Mirsky <gregimirsky@gmail.com>, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>, IETF IPPM WG <ippm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E3E422E-4D0B-4FC8-B608-2FF57CB593CB@trammell.ch>
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> <CA+RyBmVKqiX2v_880FM+k4JfA8r__9uY_MH0sKqTUTHMv7zF1A@mail.gmail.com> <CY4PR11MB1335695F04CABF482D0D6234DA470@CY4PR11MB1335.namprd11.prod.outlook.com>
To: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
X-Mailer: Apple Mail (2.3445.102.3)
X-Antivirus: Dr.Web (R) for Unix mail servers drweb plugin ver.6.0.2.8
X-Antivirus-Code: 0x100000
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/QnaHlh1ZUPUueP6OQ2G9EfliMuU>
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: Sun, 24 Mar 2019 20:06:33 -0000

hi Frank, all,

Apologies that I'm just now getting to this...

> On 18 Mar 2019, at 11:14, Frank Brockners (fbrockne) <fbrockne@cisco.com> wrote:
> 
> Hi Greg,
>  
> From what I understand, it is chair’s objective to address the question you raise below (i.e. what categories should IPPM WG consider for adoption?) as part of the planned WG discussion.

There's an action item still on the chairs' list post-Bangkok that we should follow up on this week -- figuring out one of the following three cases for each proposed encapsulation:

(1) Send the encapsulation draft to the relevant working group for the encapsulating protocol for adoption.

(2) Send the encapsulation draft to the a working group relevant to the area defining the encapsulating protocol, in case the encapsulating protocol does not have a most-relevant working group (RTGWG? INTAREA?)

(3) Adopt the encapsulating protocol in IPPM. For example, this is already clearly the correct thing to do for IPv6 encapsulation in an option, since 6man doesn't want to be in the business of defining options.

In cases 1 or 2, the document might come back to IPPM if the relevant WG is okay with it, but the discussion does need to have happened there first.

In cases where documents clearly require coordination with external standards organizations (Ethertype and Packet-Optical seem to be in this class), we need to liaise with the relevant organization before an adoption call can be made.

> In order to have a meaningful discussion – and given the fact that quite a few of the drafts are new/revised, it makes sense to get everyone on the same page, hence the superbrief lightening talks.

This seems reasonable, but during the meeting tomorrow morning, I'd like the discussion on encaps to focus on addressing the questions above. We need to be very clear on the answers before we can move to adopt any of them.

Cheers,

Brian (as co-chair IPPM)


>  
> Frank
>  
> From: Greg Mirsky <gregimirsky@gmail.com> 
> Sent: Montag, 18. März 2019 10:42
> To: Frank Brockners (fbrockne) <fbrockne@cisco.com>
> Cc: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>; IETF IPPM WG <ippm@ietf.org>
> Subject: Re: [ippm] Draft agenda for IETF 104
>  
> 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
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm