Re: [ippm] Draft agenda for IETF 104

"Frank Brockners (fbrockne)" <fbrockne@cisco.com> Tue, 19 March 2019 14:41 UTC

Return-Path: <fbrockne@cisco.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 162B013134E for <ippm@ietfa.amsl.com>; Tue, 19 Mar 2019 07:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=UDo8u8kT; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=dd7ipQ2+
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 Z834gqUSPMOW for <ippm@ietfa.amsl.com>; Tue, 19 Mar 2019 07:41:04 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98605131354 for <ippm@ietf.org>; Tue, 19 Mar 2019 07:40:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=41983; q=dns/txt; s=iport; t=1553006457; x=1554216057; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=n9VealxwKHb7Y9RD/B98BVssONWGDNVTCMsVTpLJpKc=; b=UDo8u8kTJdoqAkNjM/0bC3HxEDokLHJkJRB2x9SKxxaSIDyXTrWN+7DT QtqoOGCPBSuXQ2M7GOYvfn10el0OYazvpU09DTU5pqm1dd0Xt3fj1QG1J LbPZXsusoIv4B+C82vWw/XJe7xoFVihuZ/6WOegBP/GV7cD5+VcjeaqyH k=;
IronPort-PHdr: 9a23:K2l1XxbSFj1OCmwtU+ESMW3/LSx94ef9IxIV55w7irlHbqWk+dH4MVfC4el20gabRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn1NksAKh0olCc+BB1f8KavkZTY9F8dEWXdu/mqwNg5eH8OtL1A=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAAA6/5Bc/5tdJa1jGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQ4vUANodAQLJwqHSAOEUopggleJM41RgS4UgRADUAQLAQEYAQwHhEAChGsiNAkNAQEDAQEJAQMCbRwMhUoBAQEBAwEBKxMBASwLAQ8CAQgQAQQBASEBBgchBgsUCQgCBAENBQiDG4ERTAMVAQ4DnnACihSCIIJ4AQEFgTEBAwICDEGDCQ0LggwDBYEvAYRbhlUXgUA/gRABRoJMgUGBFkcBAQIBAYEqARIBISQHCYMFgiaQeWmGU4wBNgkCh1uEB4QJg1iBfIVyi3CLDIEXhGSBNotSAgQCBAUCDgEBBYFHODUwcXAVGiGCOAEzggoMF4NLhRSBZYNacgGBJ4ZPgR8BgR4BAQ
X-IronPort-AV: E=Sophos;i="5.58,498,1544486400"; d="scan'208,217";a="247164397"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Mar 2019 14:40:35 +0000
Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x2JEeZLV031921 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 19 Mar 2019 14:40:35 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 19 Mar 2019 09:40:35 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 19 Mar 2019 09:40:33 -0500
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 19 Mar 2019 09:40:33 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=BQphqp1cANLvpR9WYmZblshxDB7z1NNxa3JZOq7wzy8=; b=dd7ipQ2+459ZkXtNh4hOMml60D4WOEABFfgrqCVVN/KH+zHGlqKN55wvzR6s5KiZ1uNz8IiA5Jxej7hurLmYGd8LciGTIENcwBy5trJBd0vsM8QQK5THxIYR5WYMybfjoAn+OPjqTK0m1GVWDA039BXyKXCjVhaNW8Jb9OjKZbQ=
Received: from CY4PR11MB1335.namprd11.prod.outlook.com (10.169.252.143) by CY4PR11MB1336.namprd11.prod.outlook.com (10.173.17.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1709.14; Tue, 19 Mar 2019 14:40:32 +0000
Received: from CY4PR11MB1335.namprd11.prod.outlook.com ([fe80::1b2:a8de:1872:456c]) by CY4PR11MB1335.namprd11.prod.outlook.com ([fe80::1b2:a8de:1872:456c%5]) with mapi id 15.20.1709.015; Tue, 19 Mar 2019 14:40:32 +0000
From: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
To: Haoyu song <haoyu.song@huawei.com>, Tianran Zhou <zhoutianran@huawei.com>, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
CC: IETF IPPM WG <ippm@ietf.org>
Thread-Topic: [ippm] Draft agenda for IETF 104
Thread-Index: AQHU2Pn/ZjFQb8wgMUG0R4ypWuDc2KYITHmAgABnvQCACHCdMIAABsuAgAAHlBCAAHrIAIABYwXA
Date: Tue, 19 Mar 2019 14:40:32 +0000
Message-ID: <CY4PR11MB13359C67202D1090A2CF264BDA400@CY4PR11MB1335.namprd11.prod.outlook.com>
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> <BBA82579FD347748BEADC4C445EA0F21B582E9CD@NKGEML515-MBX.china.huawei.com> <CY4PR11MB133513B0A5CD4C96885C7636DA470@CY4PR11MB1335.namprd11.prod.outlook.com> <78A2745BE9B57D4F9D27F86655EB87F93766DC45@sjceml521-mbs.china.huawei.com>
In-Reply-To: <78A2745BE9B57D4F9D27F86655EB87F93766DC45@sjceml521-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=fbrockne@cisco.com;
x-originating-ip: [173.38.220.53]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a57d2250-1227-4ee8-41bb-08d6ac78d75c
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:CY4PR11MB1336;
x-ms-traffictypediagnostic: CY4PR11MB1336:
x-ms-exchange-purlcount: 5
x-microsoft-antispam-prvs: <CY4PR11MB13363BE9DAB195D0326092DEDA400@CY4PR11MB1336.namprd11.prod.outlook.com>
x-forefront-prvs: 0981815F2F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(39860400002)(366004)(136003)(396003)(189003)(199004)(11346002)(446003)(6506007)(53546011)(25786009)(5660300002)(3846002)(256004)(14444005)(8936002)(105586002)(106356001)(790700001)(410100003)(81166006)(110136005)(316002)(7696005)(4326008)(99286004)(6116002)(26005)(8676002)(33656002)(76176011)(102836004)(186003)(2906002)(93886005)(68736007)(81156014)(6436002)(9686003)(229853002)(476003)(606006)(7736002)(66066001)(86362001)(6246003)(66574012)(478600001)(74316002)(14454004)(53946003)(55016002)(54896002)(486006)(966005)(71200400001)(236005)(6306002)(53936002)(71190400001)(97736004)(52536014)(15940465004); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR11MB1336; H:CY4PR11MB1335.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: Sg17JOeTIg5joO7E+l9EevJkYDx/IQz+YpGU6Gtm7QPKhevy0qzVj4m1Z+nPJrqqqasLKlZl2ktpbqqwrCFi79F5V9feOB/nFWr76JRrl/rJuerqj3O4ZujgUjBr9YafCzrCRrmXYxPE6NNH4KW/G/APZPqh8CrPpJiVhY4QsC+tvoMP2JABONC8BOF/XjKHOJYLyYQvhhpGwn8dKTUFGIUueFP/QDluxWb4M18Gkw9Zi8sEbHHgvPFME41K282zGc3Eec3iNgYUKPvYX0uxZE8M6NtW/P30+GeU2u2yL86ckD5xkDf5pccKPYE6vWW9Jo9RHn0GLTbl6Sv2Fegfm70dIMEoOZW7q4LJiMlI+QwkfZd7cKxZZolNXhnkcd/er0kiq4rj1l/3HIHJ/6FiMT6hlXfMPiojlJOea7mBxYI=
Content-Type: multipart/alternative; boundary="_000_CY4PR11MB13359C67202D1090A2CF264BDA400CY4PR11MB1335namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: a57d2250-1227-4ee8-41bb-08d6ac78d75c
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Mar 2019 14:40:32.7013 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR11MB1336
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.22, xch-rcd-012.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/nj05pOqBOCrFvWEOnNKwg7cMnxY>
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: Tue, 19 Mar 2019 14:41:07 -0000

Haoyu,

Thanks - per my other email, I've added a new category "IOAM additional options" and also added draft-song-mpls-extension-header-02 to the set of encap options which are covered by a lightening talk.

See: https://docs.google.com/presentation/d/1P1Kp9mXA0eKkws78p1tldFn8zqx0YPQ5TK5fnq6Vyz4/

Frank

From: Haoyu song <haoyu.song@huawei.com>
Sent: Montag, 18. März 2019 18:28
To: Frank Brockners (fbrockne) <fbrockne@cisco.com>; Tianran Zhou <zhoutianran@huawei.com>; Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
Cc: IETF IPPM WG <ippm@ietf.org>
Subject: RE: [ippm] Draft agenda for IETF 104

We currently positioned a part of the draft (PBT-I) a mode of IOAM so it could fit in the IOAM data session.

We also have another draft https://tools.ietf.org/html/draft-song-mpls-extension-header-02 for IOAM encapsulation in MPLS networks. We can also use 1 min 1 slide to mention it.
Thanks!

Haoyu

From: ippm [mailto:ippm-bounces@ietf.org] On Behalf Of Frank Brockners (fbrockne)
Sent: Monday, March 18, 2019 3:11 AM
To: Tianran Zhou <zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>>; Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org<mailto:tpauly=40apple.com@dmarc.ietf.org>>
Cc: IETF IPPM WG <ippm@ietf.org<mailto:ippm@ietf.org>>
Subject: Re: [ippm] Draft agenda for IETF 104

Hi Tianran,

in which category would the draft fit?

Thanks, Frank

From: Tianran Zhou <zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>>
Sent: Montag, 18. März 2019 10:42
To: Frank Brockners (fbrockne) <fbrockne@cisco.com<mailto:fbrockne@cisco.com>>; Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org<mailto:tpauly=40apple.com@dmarc.ietf.org>>
Cc: IETF IPPM WG <ippm@ietf.org<mailto:ippm@ietf.org>>
Subject: RE: [ippm] Draft agenda for IETF 104

Hi Frank and Tommy,

I just want to know where the draft-song-ippm-postcard-based-telemetry-02 fit into the agenda?
https://datatracker.ietf.org/doc/draft-song-ippm-postcard-based-telemetry/
Personally, I want to be included in the IOAM slot.

Best,
Tianran


From: ippm [mailto:ippm-bounces@ietf.org] On Behalf Of Frank Brockners (fbrockne)
Sent: Monday, March 18, 2019 5:28 PM
To: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org<mailto:tpauly=40apple.com@dmarc.ietf.org>>
Cc: IETF IPPM WG <ippm@ietf.org<mailto:ippm@ietf.org>>
Subject: Re: [ippm] Draft agenda for IETF 104


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<mailto:ippm-bounces@ietf.org>> On Behalf Of Tommy Pauly
Sent: Mittwoch, 13. März 2019 01:24
To: Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>>
Cc: IETF IPPM WG <ippm@ietf.org<mailto: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<mailto: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<mailto: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<mailto:ippm@ietf.org>
https://www.ietf.org/mailman/listinfo/ippm