[sfc] IETF 104 Side Meeting: Operational Aspects of IOAM

Tal Mizrahi <tal.mizrahi.phd@gmail.com> Thu, 21 March 2019 14:18 UTC

Return-Path: <tal.mizrahi.phd@gmail.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93E9712798E; Thu, 21 Mar 2019 07:18:07 -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=ham 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 WdxTYhnHO_JG; Thu, 21 Mar 2019 07:18:06 -0700 (PDT)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (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 D244B1277C9; Thu, 21 Mar 2019 07:18:05 -0700 (PDT)
Received: by mail-qt1-x82d.google.com with SMTP id w5so1518811qtb.11; Thu, 21 Mar 2019 07:18:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=EOly4+0y3aI+uZAkeKYfrv4ndyCGyBjabGI3/rV9BHo=; b=lFWcevfp/FCnfVPFRSyfU7Z62vY2WcKBJ2O9RIzeY0vR1/ehxKbvtY2JLYWukkGU6B SpZqOL4AW59WeahbIgakAXKpuMiZ0kqHFnePbGRZAS5DbatIaSpWOeCWuRxQIEX8nXG3 sh1W00MV9bS0Wcv83yxkfQYcRW2ZPjpf5IOuJALucsK1BoqIOV60OXZoCjXNAjGtPzcO A7TSU58hx3CKTXsdPTjj3HRGRryIAtWAPCWFWTQVECXpc0rdXzSYG76T6AYYCrZ6CoL/ X0rF2vXgVzK+Wf5jxIqXDNtaKHY+J/iZt+LSOawr80My3NPsExZmZ74IPDOV6iWDPDb0 tFjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=EOly4+0y3aI+uZAkeKYfrv4ndyCGyBjabGI3/rV9BHo=; b=n+3vOXG/TwiU2I6v+TlXmaNToEjgr8xoNWfY9TfKLOvglAwzX/eT894n2uf5JG15Qw /b7NgMYMZITvXtbm38AQtznJsnHuZVkOkiIMhuJqwI1Fjz2QQWx84QMWevpkPBdJXy2a c8NWqBFFkqDCmW0Y6BPWyx8qgXclUfSg2et/ItgO4AekPNcBE+bO5u5juqUutE6RPZmd RmfHI4c8qjIMCq3CqZELXbgSWht6N76yu1D08GX6vYrCuAlhHdme81dBiK8BlWj+jrwd OO77iGhrFZjHmmD4FEc2ig11GuYyCDpS5yPmuismVKdiOPDI4T3fNVhyqZaL77531AKa wlIg==
X-Gm-Message-State: APjAAAXTRs+xcBSdbA8QVIbO/BfVPr0TDuwJxDegHUx+dhXuk+dN3zES ucr0d7In+7e77dtwHcKdqryXhZCm9cAGoBqhdtriPk9t0Z0=
X-Google-Smtp-Source: APXvYqwV+6iFqyS3+MBXY+3m4tAPF7ouOPbnqL+h5QueALkPLbrnYe07s8psww89JFMR126r4dyFKT0iCPlkErVUtDU=
X-Received: by 2002:ac8:3f62:: with SMTP id w31mr3331578qtk.342.1553177884783; Thu, 21 Mar 2019 07:18:04 -0700 (PDT)
MIME-Version: 1.0
From: Tal Mizrahi <tal.mizrahi.phd@gmail.com>
Date: Thu, 21 Mar 2019 16:17:53 +0200
Message-ID: <CABUE3XmPbY_K7=tQMi12ZUukRf3rmdpQH7pYMeuUMUxX_cZsag@mail.gmail.com>
To: IETF IPPM WG <ippm@ietf.org>
Cc: ipv6@ietf.org, sfc@ietf.org, v6ops@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001878fc05849b68fd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/k-vFb-bR-phZ7gThGlfAuYMKOAQ>
Subject: [sfc] IETF 104 Side Meeting: Operational Aspects of IOAM
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2019 14:18:08 -0000

Time: Tuesday, 18:30.
Place: Tyrolka.
Details:
In this side meeting we will discuss some of the operational aspects of In
situ OAM (IOAM). While the specification of IOAM is in progress in the IPPM
working group, including a wide set of features and encapsulation types, it
is likely that in practice IOAM will be used in a few common deployment
scenarios, potentially using a subset of the IOAM capabilities that have
been defined. The goal of this meeting is to stir up discussion about the
deployment aspects of IOAM, including potential use cases and deployment
challenges.

We would like to solicit operators to come and share their thoughts. If you
would like to present some slides - please reply to me off-list.
Other interested parties are also welcome, of course.

Cheers,
Tal.