Re: [ippm] draft-weis-ippm-ioam-gre-00 -> draft-weis-ippm-ioam-eth-00

"Frank Brockners (fbrockne)" <fbrockne@cisco.com> Mon, 29 October 2018 18:41 UTC

Return-Path: <fbrockne@cisco.com>
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 87C03131063 for <ippm@ietfa.amsl.com>; Mon, 29 Oct 2018 11:41:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.969
X-Spam-Level:
X-Spam-Status: No, score=-14.969 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 jhIseXVaZhMU for <ippm@ietfa.amsl.com>; Mon, 29 Oct 2018 11:41:48 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 391AE131059 for <ippm@ietf.org>; Mon, 29 Oct 2018 11:41:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9483; q=dns/txt; s=iport; t=1540838508; x=1542048108; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Ayltjd8WEkpZcJJ/fWxnhUMpzG4l3GC8udRu2u4Pi80=; b=ZrUFGzyWC+08aZXYDOOmdllEBzjbCFUM5xNs4/C7YNx8XOLypTmC/a7X Trb1lldPU1SOnaYGxg5hAxKBmpcCo9xXdllI69Q1bAnA2qpCvOu6AP91G HqwJFQACGaMdMAhCaqlhkXMlx0In0sSmO6EKhg9PNeuhdAhf8IUqVSH9K c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AGAAANVNdb/4QNJK1lGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQ1IL2Z/KAqETYc2jBmCDXqQW4VLFIFmCwEBhGwCgy0hNA0NAQMBAQIBAQJtHAyFOgEBAQEDJwZMEAIBCBEEAQEoBzIUCQgBAQQBDQUIgxqBHWSrHjOKFYtnF4FBP4ERgl01hEZuhSUCjkqQPwkCkHoggVKEd4MchmKWdQIRFIEmHTiBVXAVgyeMfoNZb4wGgR8BAQ
X-IronPort-AV: E=Sophos;i="5.54,441,1534809600"; d="scan'208,217";a="473080598"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Oct 2018 18:41:46 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id w9TIfk6X029025 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 29 Oct 2018 18:41:46 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.1395.4; Mon, 29 Oct 2018 13:41:46 -0500
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.1395.000; Mon, 29 Oct 2018 13:41:45 -0500
From: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
To: Haoyu song <haoyu.song@huawei.com>, IETF IPPM WG <ippm@ietf.org>
CC: "Brian Weis (bew)" <bew@cisco.com>
Thread-Topic: draft-weis-ippm-ioam-gre-00 -> draft-weis-ippm-ioam-eth-00
Thread-Index: AdRscK+Hymk1mndDT3qYYjQH+2j5ygDQy83wAACj+yA=
Date: Mon, 29 Oct 2018 18:41:45 +0000
Message-ID: <18855b4555ab47cf92dadd393b7a6bf9@XCH-RCD-008.cisco.com>
References: <c4aabb12a62247ae8b6c3a7970a4ca88@XCH-RCD-008.cisco.com> <78A2745BE9B57D4F9D27F86655EB87F9375920A9@sjceml521-mbs.china.huawei.com>
In-Reply-To: <78A2745BE9B57D4F9D27F86655EB87F9375920A9@sjceml521-mbs.china.huawei.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.117.11]
Content-Type: multipart/alternative; boundary="_000_18855b4555ab47cf92dadd393b7a6bf9XCHRCD008ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/qEQXuN-olU-HhaE6hXRMrfvxqA4>
Subject: Re: [ippm] draft-weis-ippm-ioam-gre-00 -> draft-weis-ippm-ioam-eth-00
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, 29 Oct 2018 18:41:51 -0000

Hi Haoyu,

hmm - the draft is very explicit on that, see section 3: "When the IOAM data fields are included within an encapsulation that identifies the next protocol using an EtherType (e.g., GRE or Geneve) the presence of IOAM data fields are identified with TBD_IOAM." - and the draft gives 2 examples in section 4, showing IOAM encapsulation options for Geneve and GRE. Not sure what else would be needed, i.e. what additional description are you looking for? IOAM data fields are of course defined elsewhere, see draft-ietf-ippm-ioam-data-04.

Cheers, Frank

From: Haoyu song <haoyu.song@huawei.com>
Sent: Montag, 29. Oktober 2018 19:22
To: Frank Brockners (fbrockne) <fbrockne@cisco.com>; IETF IPPM WG <ippm@ietf.org>
Cc: Brian Weis (bew) <bew@cisco.com>
Subject: RE: draft-weis-ippm-ioam-gre-00 -> draft-weis-ippm-ioam-eth-00

Hi Frank and Brian,

I read the draft but couldn't figure out how it is related to Ethertype. It's mentioned in the draft but not explained. Maybe I missed something. Could you please clarify it a little it? Thanks!

Haoyu

From: ippm [mailto:ippm-bounces@ietf.org] On Behalf Of Frank Brockners (fbrockne)
Sent: Thursday, October 25, 2018 7:49 AM
To: IETF IPPM WG <ippm@ietf.org<mailto:ippm@ietf.org>>
Cc: Brian Weis (bew) <bew@cisco.com<mailto:bew@cisco.com>>
Subject: [ippm] draft-weis-ippm-ioam-gre-00 -> draft-weis-ippm-ioam-eth-00

Dear IPPM WG,

given that Brian is currently OOO - I wanted to take the opportunity to point you to draft-weis-ippm-ioam-eth-00: When we reviewed draft-weis-ippm-ioam-gre-00 in our last meeting in Montreal, we concluded that we should treat encapsulations for protocols which use Ethertype and would add IOAM data fields as a header in sequence with other Ethertype-identified header the same (Alia was among those highlighting this point). A very straight forward and obvious ask. As a consequence, Brian took the effort to evolve the draft which was focused on GRE encap - and made it generic to protocols which use Ethertype. We'll discuss the draft as part of the IOAM slot in our meeting in BKK.

Frank