Re: [Ioam] [ippm] IOAM in IPPM
<nalini.elkins@insidethestack.com> Thu, 16 February 2017 19:15 UTC
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ioam@ietfa.amsl.com
Delivered-To: ioam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6C681295A5 for <ioam@ietfa.amsl.com>; Thu, 16 Feb 2017 11:15:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.287
X-Spam-Level:
X-Spam-Status: No, score=-3.287 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 1ihu6tqhJ0fm for <ioam@ietfa.amsl.com>; Thu, 16 Feb 2017 11:15:13 -0800 (PST)
Received: from nm8-vm1.bullet.mail.gq1.yahoo.com (nm8-vm1.bullet.mail.gq1.yahoo.com [98.136.218.224]) (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 7FE6D12955E for <ioam@ietf.org>; Thu, 16 Feb 2017 11:15:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1487272512; bh=y9jfA9riuuziSaMfkHm4gHSJeWb9Ugo6E74JkdkfsyA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=bBtyhsEEBgBnp1cgui9mwHmRNvvPx6nyuANoicggkUef9sjG9HwV/qAy6UaTK6mpLFZu71x+ICVJ4SsRT9aQ/T6fQGmO+unlM/8Pk2gendRxxVG6OymadM3HgUqVeRgp1nnU1ITeCwHWjgB17xkeKJAHOtCYm30HEyfKf953Wu+SuWez+i5pVR9Gn2JaVsTkJx9yJ/2TBrr+A5wa3NE3t6Faa4DM/m0eaWgoLg3ykc51AzgVQAxGK4sU1Lz53lF4Eh5nNEukmPEpITNG2JFlpM4r4zyGDAEuNLxWdPnKTwjFnk8UKjI5i+dLn1pr9zACtFjaEF5MqGpREaFbm4bR0Q==
Received: from [216.39.60.184] by nm8.bullet.mail.gq1.yahoo.com with NNFMP; 16 Feb 2017 19:15:12 -0000
Received: from [98.137.12.202] by tm20.bullet.mail.gq1.yahoo.com with NNFMP; 16 Feb 2017 19:15:12 -0000
Received: from [127.0.0.1] by omp1010.mail.gq1.yahoo.com with NNFMP; 16 Feb 2017 19:15:12 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 584108.17433.bm@omp1010.mail.gq1.yahoo.com
X-YMail-OSG: l6NqxnUVM1lqeqXfiML8ti9zsfkI.pZVRrYPUJnaF_YDIB.oOnV7EZDaZ8qUW83 ZuUidFa9crdW6IJVJtDW18lVKYHNyTjXvJfMJBvkxJUO8I6WVuud3KZp9KC.W0M5Xp6_slALRLxU Ne7fclnJBYdTFi1RYKJKsO7pPnvSyWP4.Q5hwcaNOFVfULicr.KYEXVNTsrwR02nB.HDBrcKkg8K BikFmDsBbv7YT7mrCr.BGX6YPgElxpTqLfKWYddFIbg_HOZB7isdb_Pk3IqGqABifoxa_XyXRy9W 34J0cpyQ.plEEMerougge8kcbW8lFaBTSQSzudBTnZl66eTdjMaj5mgxzNfuJjUiCTNfid26Y.Xe gMugPpNtX0D4fQm4g.B.nALt263p9jO2EmolhZRYGTdaXXK4ooI1scPQFP6yoGQXF.WR.5IAsaQM Gh9vcmCz_KWNNBijBrXJm1rsKyD2f._u8lO8MlM2Pi4dOc.aYRx7rtC07KZbaKUsYjxdJ8tBE6Pv 2Q7KR7Lm3NWW1f20eILNSkS9oxTYrjYyjW5X9WwiLJO.7s6jT3UTcxlemjJ5j_kw-
Received: from jws300069.mail.gq1.yahoo.com by sendmailws101b.mail.gq1.yahoo.com; Thu, 16 Feb 2017 19:15:12 +0000; 1487272512.206
Date: Thu, 16 Feb 2017 19:15:11 +0000
From: nalini.elkins@insidethestack.com
To: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>, "ippm@ietf.org" <ippm@ietf.org>
Message-ID: <91884089.975471.1487272511971@mail.yahoo.com>
In-Reply-To: <c50156b882bb4df0aab600d4b23f0ab1@XCH-RCD-008.cisco.com>
References: <202517D0-A6CE-40D3-98BE-A2AFA8F83A19@trammell.ch> <c50156b882bb4df0aab600d4b23f0ab1@XCH-RCD-008.cisco.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_975470_640265054.1487272511971"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ioam/GzLz45V0yCw2V0X9SBX0yAtyHf8>
Cc: Robert Hamilton <rhamilton@cas.org>, "ioam@ietf.org" <ioam@ietf.org>, Michael Ackermann <mackermann@bcbsm.com>
Subject: Re: [Ioam] [ippm] IOAM in IPPM
X-BeenThere: ioam@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: Discussion on In-Situ OAM <ioam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ioam>, <mailto:ioam-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ioam/>
List-Post: <mailto:ioam@ietf.org>
List-Help: <mailto:ioam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ioam>, <mailto:ioam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 19:15:15 -0000
Frank, As one of the authors of the PDM draft (draft-ietf-ippm-6man-pdm-option) that you discussed below. I find your work extremely interesting, as you know! I hope to see your work in IPPM. I can see that we may be able to collaborate and do quite interesting work in the future. Thanks, Nalini Elkins Inside Products, Inc. www.insidethestack.com (831) 659-8360 ----- Original Message ----- From: Frank Brockners (fbrockne) <fbrockne@cisco.com> To: "ippm@ietf.org" <ippm@ietf.org> Cc: "ioam@ietf.org" <ioam@ietf.org> Sent: Thursday, February 16, 2017 9:06 AM Subject: [ippm] IOAM in IPPM Dear IPPM WG, following the recommendation from the IPPM chairs (see also Brian's email below) as well as ADs involved (see also Alvaro's email below) the discussions on in-situ OAM (IOAM), we'd like the IPPM WG to consider adopting the IOAM work, especially the definition of formats and associated procedures for in-situ OAM, including mechanisms for capturing path and path-traversal related information as well as procedures to employ, configure, trigger, and export the embedded telemetry information. For this we'd suggest to adopt https://tools.ietf.org/html/draft-brockners-inband-oam-data-02 as a starting point for the work of IPPM on IOAM. Like Brian noted, IPPM WG already focusses on hybrid measurements (e.g. those enabled by the similar draft-ietf-ippm-6man-pdm-option), hence IOAM would be a natural complement and addition to that work and would benefit from all earlier work on metrics etc. Background on In-situ OAM: In-situ OAM provides real-time telemetry of individual data packets and flows. It is based on telemetry information which is embedded within live user traffic, where "live user traffic" means packets originated and terminated at the application layer. For more information on in-situ OAM, you could refer to the requirements draft we posted (draft-brockners-inband-oam-requirements-02), or check out the presentations we gave at IETF 96 and 97: https://www.ietf.org/proceedings/96/slides/slides-96-opsawg-8.pdf and https://www.ietf.org/proceedings/97/slides/slides-97-opsawg-in-situ-oam-00.PDF Appreciate your thoughts and support :-). Thanks, Frank -----Original Message----- From: Brian Trammell (IETF) [mailto:ietf@trammell.ch] Sent: Donnerstag, 16. Februar 2017 16:13 To: Frank Brockners (fbrockne) <fbrockne@cisco.com> Subject: IOAM in IPPM Hi, Frank, As we discussed today, please do introduce your draft (draft-brockners-inband-oam-data-00) to the IPPM mailing list. Given our recent focus on hybrid measurements (e.g. those enabled by the similar draft-ietf-ippm-6man-pdm-option), I'd like to start a discussion there about considering the draft for adoption within IPPM. Thanks, cheers, Brian -----Original Message----- From: Ioam [mailto:ioam-bounces@ietf.org] On Behalf Of Alvaro Retana (aretana) Sent: Donnerstag, 16. Februar 2017 17:58 To: ioam@ietf.org Subject: [Ioam] IOAM Work Moving Forward Hi! First of all, thank you all for the interest expressed in this topic and the discussions about the charter. As you know, one of the discussions resulting from the Internal Review of the proposed IOAM charter was whether the work was already within the ippm WG scope or not. Over the last couple of days, I have dug deeper into that question with the Transport ADs and the ippm WG Chairs, and our conclusion is that there is significant overlap between the current ippm Charter and the proposed IOAM work. Enough to justify moving the work forward in the ippm WG and not splintering a related effort into a new WG. I have then stopped the chartering effort for a new WG. The proponents will start discussions on the ippm list soon - please join if you're not there already. I will keep this list open for a couple more days. Clearly there is interest in developing this cross-area work in the IETF. I hope that you will continue to participate as the topic progresses on the ippm WG. It is important that this type of cross-area efforts be properly discussed and that we don't create more silos. I realize it took us a couple of tries to find what I think is a stable home for the IOAM work - I know that the open discussion has only helped the overall process. Thanks! Alvaro. _______________________________________________ ippm mailing list ippm@ietf.org https://www.ietf.org/mailman/listinfo/ippm
- [Ioam] IOAM in IPPM Frank Brockners (fbrockne)
- Re: [Ioam] [ippm] IOAM in IPPM nalini.elkins
- Re: [Ioam] IOAM in IPPM MORTON, ALFRED C (AL)
- Re: [Ioam] IOAM in IPPM Frank Brockners (fbrockne)
- Re: [Ioam] [ippm] IOAM in IPPM Frank Brockners (fbrockne)
- Re: [Ioam] IOAM in IPPM MORTON, ALFRED C (AL)