Re: [Ioam] Internal WG Review: In-situ OAM (ioam)

"Frank Brockners (fbrockne)" <fbrockne@cisco.com> Fri, 10 February 2017 13:38 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 5061B129976; Fri, 10 Feb 2017 05:38:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 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, 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 8SIW-6WTtZyw; Fri, 10 Feb 2017 05:38:57 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 811EE129975; Fri, 10 Feb 2017 05:38:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4882; q=dns/txt; s=iport; t=1486733937; x=1487943537; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=L9JvbFxGwGAfkGmcVDLTLGpBOKLUi6/0R7ICo8/Lyf8=; b=FegzUaNefPC3Jwn/xXL4I9xN0uiBkMcME0ZW7IkSzW1KmRlQkXm7eQ/D bWzoIiOBniZD7Hvz74rk55JybIyOHBsMu+BVZEQVDa9d9pRiKgNXyUMXU DOLlH/3Xz3m/B6GiELlUgsj8+16oC5DQTYuwHZhpaDJeMaPHtR+3lEMqS k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CIAQAkwZ1Y/4cNJK1eGQEBAQEBAQEBAQEBBwEBAQEBgygqYYEJB4NSigiSDIgMjSqCDR8LhXgCGoJcPxgBAgEBAQEBAQFiKIRpAQEBAwEBASERNwMEBwUHBAIBCBEEAQEDAiMDAgICHwYLFAEICAIEAQ0FCIlYAw0IDq9VgiWHOA2EDgEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgQuFQYRvglGBVIM1gl8Fmzg6AY16hBCCBIhnhiOKNYhfAR84fk8VPIREHYFhdYkSgQwBAQE
X-IronPort-AV: E=Sophos;i="5.35,141,1484006400"; d="scan'208";a="382476382"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Feb 2017 13:38:56 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v1ADcuSZ030162 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 10 Feb 2017 13:38:56 GMT
Received: from xch-rcd-008.cisco.com (173.37.102.18) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 10 Feb 2017 07:38:56 -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, 10 Feb 2017 07:38:55 -0600
From: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>
Thread-Topic: [Ioam] Internal WG Review: In-situ OAM (ioam)
Thread-Index: AQHSgjmziLYbR6WLQk6B61NU2m1JJqFf5E4AgAECTQCAAFm/gIABTQoA//+ulhA=
Date: Fri, 10 Feb 2017 13:38:55 +0000
Message-ID: <0bdcfd0be2c84ffa81b1658af60f084d@XCH-RCD-008.cisco.com>
References: <148657872835.4362.4208222446069276322.idtracker@ietfa.amsl.com> <CAKKJt-cwinU_f+Kgb+PuUfufZdAL788ZyYjd_2o3UCLwE5FJmQ@mail.gmail.com> <5EADB2FC-9112-4C6F-956D-C9B0A7FA405F@cisco.com> <6F7EEE4C-2D31-438E-B672-49FEED30C1A4@cisco.com> <58201ECE-F536-4ADC-98DE-95BCDAC28D31@kuehlewind.net>
In-Reply-To: <58201ECE-F536-4ADC-98DE-95BCDAC28D31@kuehlewind.net>
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.236]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ioam/EVJcLkre0tV1SWle0p6oWbos2_s>
Cc: The IAB <iab@iab.org>, "ioam@ietf.org" <ioam@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Subject: Re: [Ioam] Internal WG Review: In-situ OAM (ioam)
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, 10 Feb 2017 13:38:59 -0000

Hi Mirja,

you raise an interesting point. The IPPM charter states  " Specifying network or lower layer OAM mechanisms is out of scope of the IPPM charter.", whereas the WG has " Submit a draft on the IPv6 Performance and Diagnostic Metrics (PDM) Destination Option as Proposed Standard 
draft-ietf-ippm-6man-pdm-option" as a milestone. I'd assume that we'd likely qualify IPv6 as a transport protocol... 

So far I understood the main focus of the new IOAM WG to be network-layer focused, i.e. piggyback OAM-meta-data onto network-layer protocols - but that does not necessarily need to be always the case as you implicitly highlight by drawing the link to IPPM. One could also do so using e.g. TCP options. I did not read the statement on IPPM in the draft charter as "not cooperating with IPPM" - I read it in a way that methods that do not piggyback information on live traffic are not considered in IOAM. That said, especially when it comes to export and interpretation of in-situ OAM data, there might indeed be common ground between IOAM and IPPM.

How about we add another sentence to the charter that underlines the fact that IOAM would actively seek cooperation with other related efforts? We could add something like: 

"The IOAM WG seeks cooperation with other appropriate standards bodies and forums to promote consistent approaches, as well as definition and interpretation of in-situ OAM data."

This would naturally capture IETF WGs like IPPM - but also efforts like INT in P4, hence we'd even cast the net a little wider.

Thoughts?

Thanks, Frank

-----Original Message-----
From: Ioam [mailto:ioam-bounces@ietf.org] On Behalf Of Mirja Kuehlewind (IETF)
Sent: Freitag, 10. Februar 2017 13:10
To: Carlos Pignataro (cpignata) <cpignata@cisco.com>; Alvaro Retana (aretana) <aretana@cisco.com>
Cc: iesg@ietf.org; The IAB <iab@iab.org>; Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>; ioam@ietf.org
Subject: Re: [Ioam] Internal WG Review: In-situ OAM (ioam)

Hi all,

also one more comment on this point:

> Am 09.02.2017 um 18:18 schrieb Carlos Pignataro (cpignata) <cpignata@cisco.com>:
> 
>>> Is there any connection with IPPM?
> 
> Yes, there is, as already mentioned above.


The charter currently says:

"Other ongoing OAM-related efforts in working groups(s) such as MPLS and IPPM that do not piggyback information onto the live user data traffic are out of scope of the IOAM WG.“

which indictates that cooperation with IPPM is not planned.

To me in general the relation between this work and other ongoing work in the IETF is not very clear and IPPM has several documents and milestones that are in scope for this work:

- Submit a draft on the IPv6 Performance and Diagnostic Metrics (PDM) Destination Option as Proposed Standard: draft-ietf-ippm-6man-pdm-option (this draft is mainly done and silenter the publication process soon to my understanding)

- Submit an Experimental draft on coloring-based hybrid measurement methodologies for loss and delay to the IESG: draft-ietf-ippm-alt-mark-03

I don’t think that the assessment in the charter that IPPM's scope does not include piggybacked information is correct. Looking at draft-brockners-inband-oam-transport-02, I think that any work on IPV6 and IPv6 in this scope should be done in IPPM because that’s were this work is already on-going and where the measurement expertise is.

Mirja




_______________________________________________
Ioam mailing list
Ioam@ietf.org
https://www.ietf.org/mailman/listinfo/ioam