Re: [ippm] Adoption call for draft-mizrahi-ippm-ioam-flags Re: Regarding draft-mizrahi-ippm-ioam-flags

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Mon, 29 July 2019 04:09 UTC

Return-Path: <cpignata@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 BD61E120115; Sun, 28 Jul 2019 21:09:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 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, 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 header.b=cBEiNAst; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=yOxq41p+
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 LDbarprsvf98; Sun, 28 Jul 2019 21:09:39 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB1D31200F6; Sun, 28 Jul 2019 21:09:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2666; q=dns/txt; s=iport; t=1564373378; x=1565582978; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=RfuOU2HYGBjMDsZCkSR3m3DKgv3f0/sJ4EjAViW846k=; b=cBEiNAsturQWd2pBOIUi+eCdOecVQAyK9Dp7X1exVafKEZb3exrsOvLz J7OKvy3shU3xERkSuhkESsAAmAxdr4u/AFDaNQQWFnVUc6AouY5H2g2TR ++z80TAsdGWLElASlX/E2ETcwSbeam134MJrfTgfqf1ti8qYFg+MBkqVL s=;
IronPort-PHdr: 9a23:8TR84Bxpmf8kyFPXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YhWN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZuOEUz0Kvf2ZgQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AGAADXcD5d/5NdJa1mGQEBAQEBAQEBAQEBAQcBAQEBAQGBUwQBAQEBAQsBgUMkLANtVSAECyoKhBSDRwOEUogugjYliVSNf4EuFIEQA1QJAQEBDAEBGAsKAgEBhEACF4JLIzQJDgEDAQEEAQECAQZthR4MhUoBAQEBAgEBARALBhEMAQEsCwEECwIBCBgCAh8HAgICHwYLFRACBA4FIoMAAYFqAw4PAQIMoCcCgTiIYHGBMoJ6AQEFhQMNC4ITAwaBDCgBi18XgUA/gREnDBOCTD6CGkcBAYEpNwGDCzKCJo5+jW2NUEAJAoIakB2DdxuCLocljjuMXAmCB4gOiwyDCwIEAgQFAg4BAQWBUDiBWHAVOyoBgkE+ggQ3gzqFFIU/coEpjAQBgSABAQ
X-IronPort-AV: E=Sophos;i="5.64,321,1559520000"; d="scan'208";a="302121418"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 Jul 2019 04:09:36 +0000
Received: from XCH-ALN-018.cisco.com (xch-aln-018.cisco.com [173.36.7.28]) by rcdn-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id x6T49aQh003960 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 29 Jul 2019 04:09:36 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-018.cisco.com (173.36.7.28) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 28 Jul 2019 23:09:35 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 29 Jul 2019 00:09:35 -0400
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 29 Jul 2019 00:09:35 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=UJQfTMSziWdphKoOoJPh00qrC5137iLa7+7sJ3bLwmnB9pWh8GjijQcKUiPmli2MGhXjDsDg4PIfpw26/WoVTzQk/8WQCiy+Qn7TRl0vx/mZk/cVR5TeckHEnfnyVXh4ReDIKEsTQsU/pp0zQElPPDGUsuDhn8p3Czc9lfvEz/CzV4AW1+7Vwr5FZoHE5X5YN92aLHn545dg+aqQdjJit8tFuDnB7x4ZNEXvIzkwiXJpfp3SX6nx1mod8K/mGFEFVF/efpxMv/h8LPXHcZZd6y1ibCkYtkEgZUBdDi97JgTuoZq5s3enDPbFOQed9zZeVOHJRH2RK7okD5Wq7dqnqQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RfuOU2HYGBjMDsZCkSR3m3DKgv3f0/sJ4EjAViW846k=; b=DPsFke+7pLm7q42Kyzs2ua/hrZBb0EoaRYe27EO/UpiQN6uspSs7AISamevBX0szENr2p7l6r8btuu+WR/nba/79/Ip0UIvMoRWXmSFj0o4D9x5KVx5+wrF7n060+YKwNj2oGMJH5h2SDoS1imAYbMZ00dCMTp4tXNdlWkQXDFrHBfWdaJWEbsPfLnZNFuvXXWOlmfV3qawmpJAMVGUnaRMx42dWpDiiyiGIVOZtr6NFWu9y1WfVpgha/ill3dK2I33LX85mebR8eZBFlfH/zUetGUtbmpz4Pw5+5iksgwuNZVjBc1q4+oc0JIyWp/52Xrgm3XMM3ob0NArWivuxdw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=cisco.com;dmarc=pass action=none header.from=cisco.com;dkim=pass header.d=cisco.com;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RfuOU2HYGBjMDsZCkSR3m3DKgv3f0/sJ4EjAViW846k=; b=yOxq41p+UJ188QYVAe9ygg3lpVjNbBaJrRgcjTg70FujcT9NHAkIh+j0mrRlYDYet3zjycPxTctVkOB+SjtF9qZUgrg/IHHn6vMgf9iTEU7Hni+XVjQEgQ2gvhZPrJAZG2cPdxjgLAM9dgFVx37FvewKrk1HktPPM5rq9Eb8Fko=
Received: from BL0PR11MB3028.namprd11.prod.outlook.com (20.177.204.138) by BL0PR11MB3457.namprd11.prod.outlook.com (10.167.234.88) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.15; Mon, 29 Jul 2019 04:09:33 +0000
Received: from BL0PR11MB3028.namprd11.prod.outlook.com ([fe80::28e3:f8a3:596:b998]) by BL0PR11MB3028.namprd11.prod.outlook.com ([fe80::28e3:f8a3:596:b998%3]) with mapi id 15.20.2115.005; Mon, 29 Jul 2019 04:09:33 +0000
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "Brian Trammell (IETF)" <ietf@trammell.ch>
CC: Greg Mirsky <gregimirsky@gmail.com>, IPPM Chairs <ippm-chairs@ietf.org>, IETF IPPM WG <ippm@ietf.org>
Thread-Topic: [ippm] Adoption call for draft-mizrahi-ippm-ioam-flags Re: Regarding draft-mizrahi-ippm-ioam-flags
Thread-Index: AQHVQxPhrKSfRYTYWk6hrIGjowkMKqbhALEA
Date: Mon, 29 Jul 2019 04:09:33 +0000
Message-ID: <4AC4BE58-D387-4230-974F-1E313AA49E45@cisco.com>
References: <CA+RyBmVnkMFEQv=Hr3y9OD09+_vocHRgnGQnLwEVO=yuTcptEQ@mail.gmail.com> <EAB5C70D-A160-423E-84FE-3CE7AC079168@trammell.ch>
In-Reply-To: <EAB5C70D-A160-423E-84FE-3CE7AC079168@trammell.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3445.104.11)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=cpignata@cisco.com;
x-originating-ip: [173.38.117.88]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7ceb7295-57c7-47d6-a64b-08d713da9013
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BL0PR11MB3457;
x-ms-traffictypediagnostic: BL0PR11MB3457:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BL0PR11MB3457A83754680271606BED2EC7DD0@BL0PR11MB3457.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01136D2D90
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(396003)(376002)(366004)(346002)(136003)(51914003)(189003)(199004)(81156014)(81166006)(8676002)(8936002)(102836004)(53546011)(6506007)(66946007)(76116006)(25786009)(6306002)(3846002)(6512007)(50226002)(53936002)(54906003)(6116002)(6486002)(256004)(66556008)(64756008)(66446008)(71190400001)(71200400001)(86362001)(76176011)(2906002)(66476007)(68736007)(229853002)(6436002)(7736002)(14444005)(99286004)(186003)(486006)(5660300002)(316002)(11346002)(305945005)(36756003)(33656002)(4326008)(476003)(2616005)(26005)(66066001)(6916009)(478600001)(966005)(14454004)(6246003)(57306001)(446003); DIR:OUT; SFP:1101; SCL:1; SRVR:BL0PR11MB3457; H:BL0PR11MB3028.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: SIsIFZS9C1wUGk6OWrx3pIFv6s/AR4fK/ELB0ywaCoUW0fb6uzQeyL7Tighhzaf83LDftW+RnJ7w//rt7K8ZSBXhtHKSwauzO6/XgjZ4MGdBlFRDqg0PKhnU8nlgDP3CoPIGfxxp4EUyk0HsK7S0jX2Uqv7jV6ACabzML+ZPmin5yl249O+ZrzYI/pKvFWOBrfdpylFG5L+oXjwAKjo/nHHsMr50qpBvOoXBXEIoYxEK92gc8EyGPYk1g9OP3JmwAUsdulBvFgVcqR77/8g3JyaLzY05pojanivlhmNahcnyC4gaUs7fuFDMB0rlPSoox+ngUNR3zEnQJayADQe+sebScxfr7CJVrHFTnhXNBe3s6r5CIJziNNPiV7WfarwzeEKfvmbXX/ZxtoU6pOrigEtSI0ukPXTb5Qc01YiyAuY=
Content-Type: text/plain; charset="utf-8"
Content-ID: <E8CD00E2BD8F4542BA71DBC694B35FAE@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 7ceb7295-57c7-47d6-a64b-08d713da9013
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jul 2019 04:09:33.4761 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: cpignata@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR11MB3457
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.28, xch-aln-018.cisco.com
X-Outbound-Node: rcdn-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/hyb2GRFITIzi444tQF6ZTb2G8Vk>
Subject: Re: [ippm] Adoption call for draft-mizrahi-ippm-ioam-flags Re: Regarding draft-mizrahi-ippm-ioam-flags
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 Jul 2019 04:09:41 -0000

Hi, Brian,

I support adoption of draft-mizrahi-ippm-ioam-flags. This is an important set of definition of flags for real uses based on experience. It fulfills part of the charter milestone below complementing the base ioam-data, realizing specific use cases, as an offspring document from ioam-data.

I’m a co-author.

Thanks,

Carlos.

> On Jul 25, 2019, at 2:07 PM, Brian Trammell (IETF) <ietf@trammell.ch> wrote:
> 
> hi Greg,
> 
> Thanks for the feedback; absolutely, we can do this the normal way. Authors: let's do a normal two-week adoption call for this document before publishing the update.
> 
> This adoption call starts now.
> 
> IPPM, please respond to this message with an indication to the mailing list of your support for adopting draft-mizrahi-ippm-ioam-flags as a working group document, in partial fulfillment of our charter milestone "submit a Standards Track draft on inband OAM based measurement methodologies to the IESG" (obviously, depending on how many documents we end up sending to the IESG, we may have to change the plurality of this milestone). If you do not support this, please send a message to the list explaining why.
> 
> Thanks, cheers,
> 
> Brian (as IPPM co-chair)
> 
> 
>> On 25 Jul 2019, at 13:15, Greg Mirsky <gregimirsky@gmail.com> wrote:
>> 
>> Dear Chairs, et al.,
>> I appreciate that editors of draft-ietf-ippm-ioam-data followed on the decision of the WG reached at the meeting in Prague to extract material not directly related to the definition of iOAM data elements from the document. The new draft was presented earlier this week and generated many comments. I feel that it would be right to discuss the draft and its relevance to the charter of the IPPM WG before starting WG adoption poll.
>> 
>> Regards,
>> Greg
> 
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://www.ietf.org/mailman/listinfo/ippm