Re: [ippm] Merging deployment considerations into IPv6 IOAM document

"Frank Brockners (fbrockne)" <fbrockne@cisco.com> Fri, 18 September 2020 08:56 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 E64B53A0AD6; Fri, 18 Sep 2020 01:56:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.62
X-Spam-Level:
X-Spam-Status: No, score=-9.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 header.b=babuMUxD; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=cex/0uo+
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 sgLzvGZAJxAw; Fri, 18 Sep 2020 01:56:40 -0700 (PDT)
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 201F73A08BB; Fri, 18 Sep 2020 01:56:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2116; q=dns/txt; s=iport; t=1600419400; x=1601629000; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=hpeNX1pZcQt2NQMKbwosXQjWYo/s+q1LZIZrZRdCRNY=; b=babuMUxD9v/VqdKSwbeUIFuL/YKmk0WzmL+pJa+UhXdfuW/Ax3nrYER2 Hs++MwRuTkbJ98LszXT79QfKw0Bz9P21K8qa7vd9Mqpb4Nq4E1OBIQKZd JgV2XVE4cedHhsRH6HUtY6Ztbh0DMuO5AEfLv/VgVxGZrmJNovmjHaKur o=;
IronPort-PHdr: 9a23:WF61kR9QQJZ45f9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+7ZRCN7O11iFKPVoLeuLpIiOvT5qbnX2FIoZOMq2sLf5EEURgZwd4XkAotDI/gawX7IffmYjZ8EJFEU1lorHijKUxYXs35Yg6arni79zVHHBL5OEJ8Lfj0HYiHicOx2qiy9pTfbh8OiiC6ZOZ5LQ69qkPascxFjA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B0AAD7dWRf/51dJa1fHAEBAQEBAQcBARIBAQQEAQFAgTwGAQELAYFRIy4HgUkvLAqHdQONdYoOjmaBLhSBEQNVCwEBAQ0BAS0CBAEBhEsCgikCJDUIDgIDAQELAQEFAQEBAgEGBG2FXAyFcgEBAQEDEigGAQE3AQsEAgEIDgIBBAEBHxAhER0IAgQBDQUIGoVQAy4BqkkCgTmIYXSBNIMBAQEFhSMNC4IQCYE4AYJwijsbgUE/gRFDgh8uPoIaggkcg0iCCyKSdKNrUQqCZ49IhXyFKYMMiXqTfJJ6gXeLVJIxAgQCBAUCDgEBBYFWAzWBV3AVO4JpUBcCDY4fg3GKVnQCNQIGCgEBAwl8jFIBgRABAQ
X-IronPort-AV: E=Sophos;i="5.77,274,1596499200"; d="scan'208";a="563882742"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 18 Sep 2020 08:56:34 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 08I8uYdF011285 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 18 Sep 2020 08:56:34 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 18 Sep 2020 03:56:33 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 18 Sep 2020 03:56:33 -0500
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Fri, 18 Sep 2020 04:56:32 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=X/AloXEf+yxkJBX+yLLf098A5zhsdEK55roCEn3vIBR17lfm7+dbnbrfKnw3ONQdcOo/ovVHMkKTCJEiC1cgMVFR9uZAWWOlnc5q3IWaq/HT0egPfkDzZGq7pyMCfktwfQ8AX1P7Sd1yeqn4kITFRqFd/QNDwaMnTxScdrNW4xowUposl9DPtmK23p3Gba27FX3vYIxBs3z+Hl1pPQM1QwNcGQrVRZisnWu3tAyRLYmP42yotD78ShDHpbFNDtBHlwrYmGXtob+Q1vLzzqThezy+HCm1PZJ6WqOO9JwQI91GRG7EAx8yw6Mst7xLjaivXFbsDz2hIoqat7zges+BRg==
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=4HBx/91SL6/ZTQS4lbqRCCGD5fsZvs4+0RqKZQrx6aA=; b=MXHbzPKpswpiDWq4Ome+q25Ag6wINpimsTluGuA/iTrwy6R2uyfbG1pWfkPavQqgR49bScAFSYLeTy1OpR//ltSvnalsqDUibw7xEjq/+1Ouzky5wPgqUN+JV5zqX7dCAob+OXFmZ7RDWNTaAhUeYDsMglBjE9sNYZldPp3RVFYu3rQTfijO+4bc9iGsHdjrZB2zF+RB51JsFLi9fBoc5EgUoldGfi5Cq7ZciOEhBNuSJR1RPDEv5GLJ89oluIFbGdcrBrfU7NgyhqsxnVNypB33SvPcu3PqlIOFCUbjdzcbsWzzuJgtICYapPTVf4CUUoJGt6qqSsnjm/qf9mdJYg==
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=4HBx/91SL6/ZTQS4lbqRCCGD5fsZvs4+0RqKZQrx6aA=; b=cex/0uo+njLUfI9cQBeO8ydbOidbvMV5uxmFFXgteoNyPBaMi0lN6Tv8XCRpPAhcCpQ8cUa3J5pi0dRoJU4vgfV6dntHdHZytugQLNi6YM0Pdkxx7izfmBOtLvRWOblwMZ90HInlYeTubei1S/42NWiOeYdJv+g/AIXbOBMemT0=
Received: from SN6PR11MB2589.namprd11.prod.outlook.com (2603:10b6:805:53::12) by SN6PR11MB3181.namprd11.prod.outlook.com (2603:10b6:805:c3::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3391.15; Fri, 18 Sep 2020 08:56:32 +0000
Received: from SN6PR11MB2589.namprd11.prod.outlook.com ([fe80::cd9e:cf16:e204:215e]) by SN6PR11MB2589.namprd11.prod.outlook.com ([fe80::cd9e:cf16:e204:215e%3]) with mapi id 15.20.3391.011; Fri, 18 Sep 2020 08:56:32 +0000
From: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
To: Tommy Pauly <tpauly@apple.com>, "draft-ietf-ippm-ioam-ipv6-options@ietf.org" <draft-ietf-ippm-ioam-ipv6-options@ietf.org>, "draft-ioametal-ippm-6man-ioam-ipv6-deployment@ietf.org" <draft-ioametal-ippm-6man-ioam-ipv6-deployment@ietf.org>
CC: IPPM Chairs <ippm-chairs@ietf.org>, Martin Duke <martin.h.duke@gmail.com>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>
Thread-Topic: Merging deployment considerations into IPv6 IOAM document
Thread-Index: AQHWcn+tehkJP0ZMgkKNO88gp8Y0RKluSaBQ
Date: Fri, 18 Sep 2020 08:56:32 +0000
Message-ID: <SN6PR11MB2589632C6BAE9DF09633323DDA3F0@SN6PR11MB2589.namprd11.prod.outlook.com>
References: <CAA85DDF-E1DA-4FE3-B4F3-96C00550F9FE@apple.com>
In-Reply-To: <CAA85DDF-E1DA-4FE3-B4F3-96C00550F9FE@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: apple.com; dkim=none (message not signed) header.d=none;apple.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [173.38.220.48]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c815dd29-cd63-4d9a-b6bd-08d85bb0bd6d
x-ms-traffictypediagnostic: SN6PR11MB3181:
x-microsoft-antispam-prvs: <SN6PR11MB318122175C1898C9F07193CBDA3F0@SN6PR11MB3181.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: DBtC13r4y6Zr5pAxeiw8qMF0Ahs6exBxUioWsuOT2BYkm5/EmbLxh2GZx46sArXBdk+NxWq7jBs0H8BP8N3z1d186RRxccZF8lhh3An6oS/pv9x3IUf81zfTuL1G/SPDoofzBnPdZNeH1LoE+RvY8CJstrk1U1RnyIEnbro4nocVMBrVfiTUz0R39BA0PKgF0NVDcfCxexG+4DFYVPSld063p21EtzUeoiAev3PNgQEOhrzK0ZNNzh9mn4G4kfHOL8NpIxqGmB9CmIo0TPS5yg1LIII4ziOqKHqsnsZcvt+f0R6mlYctIUXlmBCWllan4X2TAto8nBAi6jcKo/5gdQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:SN6PR11MB2589.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(346002)(376002)(366004)(396003)(136003)(39860400002)(8676002)(66476007)(66446008)(66946007)(66556008)(86362001)(64756008)(52536014)(6506007)(8936002)(76116006)(186003)(4326008)(53546011)(33656002)(7696005)(9686003)(26005)(55016002)(110136005)(316002)(478600001)(54906003)(5660300002)(2906002)(83380400001)(71200400001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: xrOkfoVbn5dnN1OZQnwfqcRwBjvPYo9jO9MVBTTJde4tQpkReg48fFeiWD2xy7F2PYtrUoDE6NO9byTxgM92WDmI9fCPxA7TEhSoQPbJoYGy3lAaVDKPivlB5LIGF4vs1LolZGxlW83d2mA+ls5tbNHMJ8DmYqD4nGiBZjUKXUC/Ds39/UaISfSjUX+0Sq7pJciC91f4mkrb8z234QeVjAQ5+hOWton8wjlpRs6o4o1lXyep9u7lmkLKCA6a8+Vdd0wh+jmF5EYjcTEq+Qi/XZZREpDW5nOHCVErxawtMiL0q/UhNtyXEBxFJQwUjWN8O1EDimGTorTbtpXtlzLCpVbu7DgJXSGB1uE50xTdDttp6jfsVyC7D3HZ0MK4ZhMSkqSpgC/UBVXbLQ/usOSTpfh40rixEdZX6kaGk8aeXbQPx6DBPYsbOsH6U1jb+U2dhNQKkDfQwOS87SOkFEmZcX2XlFo3z3iD7nEo0BquVwaqm+nanox4ly2yRqQ8wyZwu2bmvnWQSJvoUzoATomzoADWQIStCWDY3mSKWHtDP250BD6a73WEnxHdj5hXzvL1e4dFU1Ep22gwO5iG1MUWfeJOIqcQgVdW6YdbE7EGRL+kR6svoiIsr7336rKecBHL5lUvQsr/7qqbLYvl5lPpJw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: SN6PR11MB2589.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c815dd29-cd63-4d9a-b6bd-08d85bb0bd6d
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Sep 2020 08:56:32.2161 (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: ibLedh/+eLDdoTVvvMG4zsJ0Ve6T+Ty/Jt78opFclGtBasu7482+A5VHS18b91WflgR2y7r6RX8jY17rd1RcYA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR11MB3181
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/wlKQY9yjmUOkxM6AiuHOBWsEzZI>
Subject: Re: [ippm] Merging deployment considerations into IPv6 IOAM document
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: Fri, 18 Sep 2020 08:56:42 -0000

Hi Tommy, IPPM WG,

we just posted an updated draft-ietf-ippm-ioam-ipv6-options-03 which merges draft-ioametal-ippm-6man-ioam-ipv6-deployment into draft-ietf-ippm-ioam-ipv6-options plus it reflects the WG discussion of the last IPPM meeting.

The updates to draft-ietf-ippm-ioam-ipv6-options-03 are

* implement the guidance from the WG chairs: Merge in draft-ioametal-ippm-6man-ioam-ipv6-deployment "as is", i.e. only editorial changes were made (e.g. resolve references which would have been circular).
* implement the result of discussion in the last WG meeting: Removed the paragraph that started with " In order for IOAM to work in IPv6 networks.." which included deployment considerations.

Moving forward, we'll need to further evolve the deployment section (now section 4). 
There were already comments raised in the IOAM DT wrt/ what is now section 4.4.1 by Haoyu. I asked  Haoyu to take those to the IPPM list. 

Cheers, Frank

> -----Original Message-----
> From: Tommy Pauly <tpauly@apple.com>
> Sent: Freitag, 14. August 2020 23:12
> To: draft-ietf-ippm-ioam-ipv6-options@ietf.org; draft-ioametal-ippm-6man-
> ioam-ipv6-deployment@ietf.org
> Cc: IPPM Chairs <ippm-chairs@ietf.org>; Martin Duke
> <martin.h.duke@gmail.com>
> Subject: Merging deployment considerations into IPv6 IOAM document
> 
> Hi IOAM IPv6 authors,
> 
> At IETF 108, we discussed draft-ietf-ippm-ioam-ipv6-options and draft-ioametal-
> ippm-6man-ioam-ipv6-deployment, and how to progress with the deployment
> considerations. Since the hums showed no strong opinions one way or the other
> in the WG, Ian and I have discussed and would prefer to see the deployment
> considerations merged into the existing and adopted IPv6 options document.
> Both documents are short, and readers will benefit from any discussion of
> deployment being available in the same document that defines the extension
> header.
> 
> Please post an update for draft-ietf-ippm-ioam-ipv6-options with this content
> added when you have a chance!
> 
> Thanks,
> Tommy