[ippm] Summary of Next Steps for IOAM encapsulations

"Brian Trammell (IETF)" <ietf@trammell.ch> Mon, 25 March 2019 11: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 0D31F120395 for <ippm@ietfa.amsl.com>; Mon, 25 Mar 2019 04:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 xetwBJPldvQc for <ippm@ietfa.amsl.com>; Mon, 25 Mar 2019 04:06:16 -0700 (PDT)
Received: from smtp-sh2.infomaniak.ch (smtp-sh2.infomaniak.ch [128.65.195.6]) (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 36EFF120390 for <ippm@ietf.org>; Mon, 25 Mar 2019 04:06:16 -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 x2PB6E4p025961 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <ippm@ietf.org>; Mon, 25 Mar 2019 12:06:14 +0100
Received: from [IPv6:2001:67c:370:128:a186:bdcf:4068:e8f0] ([IPv6:2001:67c:370:128:a186:bdcf:4068:e8f0]) (authenticated bits=0) by smtp8.infomaniak.ch (8.14.5/8.14.5) with ESMTP id x2PB5hvX000477 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ippm@ietf.org>; Mon, 25 Mar 2019 12:06:14 +0100
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Message-Id: <B84318E3-83C0-4FB3-BD00-021A10718711@trammell.ch>
Date: Mon, 25 Mar 2019 12:06:13 +0100
To: IETF IPPM WG <ippm@ietf.org>
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/ntFLqfl_GmLxV49oDhbNqnWA18Y>
Subject: [ippm] Summary of Next Steps for IOAM encapsulations
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, 25 Mar 2019 11:06:19 -0000

Greetings, all,

Here's where I think we are on IOAM encapsulations after today's discussion:

draft-weis-ippm-ioam-eth-01 : I have pinged Donald Eastlake (as IANA Ethertype expert, instead of Erik Nordmark) to determine the right way to get an Ethertype through IANA. Will follow up to determine if there is a better venue than IPPM for the discussion on this draft.

draft-ioametal-ippm-6man-ioam-ipv6-options-01
draft-ioametal-ippm-6man-ioam-ipv6-deployment-00 : to be discussed at 6man on Friday, next steps to be determined there. It is not clear whether this is more like PDM or more like SR as to how much 6man will care about the details of IOAM.

draft-brockners-ippm-ioam-geneve-02 : this is an alternate approach if getting an ethertype doesn't work.

draft-gafni-ippm-ioam-ipv4-options-00 : adding options to IPv4 for IOAM encaps is almost certainly a nonstarter. While the IESG statement in 2016 (https://www.iab.org/2016/11/07/iab-statement-on-ipv6/) does not prohibit work on v4 extensions, v4 options are deprecated de facto. In any case, IPPM is not the appropriate venue.

draft-*-spring: SR drafts belong in spring; authors of different approaches here should collaborate to see if their work can be combined. In any case, these are not for IPPM until spring indicates they're okay with SR encapsulation work happening outside the WG

I (personally) suggest that we focus on encaps that will drive deployment: GRE, Geneve (where ethertype will fix these two), IPv6, and MPLS; the authors probably have a better idea than I do of where to focus first in terms of impact.

Cheers,

Brian