Re: [Ioam] [ippm] IOAM in IPPM

"Frank Brockners (fbrockne)" <fbrockne@cisco.com> Fri, 17 February 2017 11:45 UTC

Return-Path: <fbrockne@cisco.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 BA459129418; Fri, 17 Feb 2017 03:45:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 eSjOv7XitFee; Fri, 17 Feb 2017 03:45:15 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 991A112998C; Fri, 17 Feb 2017 03:45:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6672; q=dns/txt; s=iport; t=1487331915; x=1488541515; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=43kx1g25j/76xVGFqtcvYU+4O4AhyQF0RNfyIK6fdQk=; b=feGXsWzYwC8Rvoof0KpgyfEVUOFRv65rtxug4T3V8JkYdpSZS/99iu1h kGJ0z9/H5DxcTs/Qj80yVR8gzmdPejRml7y7ZFYpwOPteNwdCApviSDcO x7bGo+SW9OggLo9Q1fiZ9JKPLARQ5F2rMev14c3bb/aaXmXRgsYA15Q7b Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CcAQCZ4aZY/4ENJK1bAxkBAQEBAQEBAQEBAQcBAQEBAYNRYYEJB4NSigiSEJU0ggwfDYV2AhqBfz8YAQIBAQEBAQEBYiiEcAEBAQICAQEhERUlCwwEAgEIEQQBAQMCIwMCAgIlCxQBCAgCBAENBQiJZA6wJoIli1gBAQEBAQEBAQEBAQEBAQEBAQEBAQEdgQuFQYRvhCYRATMKJoI/gl8FlV2GIwGGcIJaiEWCBIUXiXaTGwEfOHgIURU9hkR1AYg8gSGBDQEBAQ
X-IronPort-AV: E=Sophos;i="5.35,171,1484006400"; d="scan'208";a="209736824"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 17 Feb 2017 11:45:14 +0000
Received: from XCH-ALN-008.cisco.com (xch-aln-008.cisco.com [173.36.7.18]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v1HBjEdE030017 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 17 Feb 2017 11:45:14 GMT
Received: from xch-rcd-008.cisco.com (173.37.102.18) by XCH-ALN-008.cisco.com (173.36.7.18) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 17 Feb 2017 05:45:13 -0600
Received: from xch-rcd-008.cisco.com ([173.37.102.18]) by XCH-RCD-008.cisco.com ([173.37.102.18]) with mapi id 15.00.1210.000; Fri, 17 Feb 2017 05:45:13 -0600
From: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
To: "nalini.elkins@insidethestack.com" <nalini.elkins@insidethestack.com>, "ippm@ietf.org" <ippm@ietf.org>
Thread-Topic: [Ioam] [ippm] IOAM in IPPM
Thread-Index: AQHSiGc9cXzuyNyh40uXrix8UqmsmqFryByAgACdp4CAAK/YMA==
Date: Fri, 17 Feb 2017 11:45:13 +0000
Message-ID: <b867dbe778fd42bf9e21e17b85eb235b@XCH-RCD-008.cisco.com>
References: <202517D0-A6CE-40D3-98BE-A2AFA8F83A19@trammell.ch> <c50156b882bb4df0aab600d4b23f0ab1@XCH-RCD-008.cisco.com> <91884089.975471.1487272511971@mail.yahoo.com>
In-Reply-To: <91884089.975471.1487272511971@mail.yahoo.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.190.229]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ioam/-wZW3HIVTAmSRyYTKzo_rsDG80I>
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
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: Fri, 17 Feb 2017 11:45:18 -0000

Thanks Nalini. Looking forward to the IOAM work in IPPM. Frank

-----Original Message-----
From: Ioam [mailto:ioam-bounces@ietf.org] On Behalf Of nalini.elkins@insidethestack.com
Sent: Donnerstag, 16. Februar 2017 20:15
To: Frank Brockners (fbrockne) <fbrockne@cisco.com>; ippm@ietf.org
Cc: Robert Hamilton <rhamilton@cas.org>; ioam@ietf.org; Michael Ackermann <mackermann@bcbsm.com>
Subject: Re: [Ioam] [ippm] IOAM in IPPM

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