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

"Frank Brockners (fbrockne)" <fbrockne@cisco.com> Tue, 29 September 2020 18:25 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 2EAF83A1419; Tue, 29 Sep 2020 11:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level:
X-Spam-Status: No, score=-9.598 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.001, RCVD_IN_MSPIKE_WL=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 header.b=V2lOQ6+m; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=E9j7WdsM
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 R1BUPVkfzGci; Tue, 29 Sep 2020 11:25:04 -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 D36253A1416; Tue, 29 Sep 2020 11:25:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4730; q=dns/txt; s=iport; t=1601403904; x=1602613504; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=UsEDNERCgMcdb+2qqf4ZaPfv5LeGDfR/mnqctkRw0z0=; b=V2lOQ6+mxA529KEzYvd0g01kByQBu/MxRGIu+mrEYSc0KKa51Ns8fUcb HoySKlFLrkdqfOK6V/Q3jJpYc8nbMxrQtcSIh/mzC4jwjyLEDsBgT7QmE 6l7r8AdGkBSjCWDHrQwypPIZlXdAfR1YXa3W7NmgzPoh6H6H5Qtf6TKKH 0=;
IronPort-PHdr: 9a23:BDei3xGd3moK51gx4KsIz51GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e401QObVJ3D7/8CgO3T4OjsWm0FtJCGtn1KMJlBTAQMhshemQs8SNWEBkv2IL+PDWQ6Ec1OWUUj8yS9Nk5YS8/mf1nf5Ha16G1aFhD2LwEgIOPzF8bbhNi20Obn/ZrVbk1IiTOxbKk0Ig+xqFDat9Idhs1pLaNixw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B1AADFe3Nf/4kNJK1gHAEBAQEBAQcBARIBAQQEAQFAgTwGAQELAYFRUQdwWS8sCoQzg0YDjX+KD45ogS4UgREDVQsBAQENAQEnBgIEAQGEB0QCF4IYAiU1CA4CAwEBCwEBBQEBAQIBBgRthVwMhXIBAQEBAgESEREMAQE3AQsEAgEIDgIBBAEBAQICJgICAh8RFQgIAgQOBQgagwWCSwMOIAEOqjUCgTmIYXaBMoMBAQEFhRENC4IQAwaBDioBgnGDaYZTG4FBP4ERQ4IfLj6CGkICgUUcgxUzggsiknwBPKM8UQqCZ4h7hlWFfoUrgw2JfpQIlQGIc4JqkjkCBAIEBQIOAQEFgVYBN4FXcBU7gmlQFwINjh+DcYpWdAI1AgYBCQEBAwl8jC0BgRABAQ
X-IronPort-AV: E=Sophos;i="5.77,319,1596499200"; d="scan'208";a="570228306"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 Sep 2020 18:24:57 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by alln-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 08TIOvQK023233 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 29 Sep 2020 18:24:57 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 29 Sep 2020 13:24:56 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 29 Sep 2020 14:24:55 -0400
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 29 Sep 2020 13:24:55 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PEC2vdjRuNNY1xGhx33eqlFJ17A4Wd4VcwH8nHFlpXyyxQL+OCGAwRdpDVAMcIIhLOxkSQSWzvYi+g2j9VgGsDhY6gQRCH2k2P+3tv5G49Z85AdovhY+LmiBj80JGFl+c4KfQcuAsrIKkALDkLcvTypleFi9CINC+NuYzPHIDCfxDG+hXY5iCPq+9y77JrBeXVLiwOjem0eOlVE96Xc6/kxnzQQppKkP/w6h3LyHtN5QfSpUFMOLsx2080Pb9ipoDE8ybZ7TpSg7NJi66Yb2DN26mdt0vWwX+OXwS9dgd0SHL+H22QrAmYO/pqfRz2ncaj4uFFKzES/sfmmhCI69Rg==
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=UsEDNERCgMcdb+2qqf4ZaPfv5LeGDfR/mnqctkRw0z0=; b=YPiFpotd67ZoTDotn90+MyiFqN94IIZk5OHMKq55tID9RRGzUtx8hRsS+QzRwCAGVUfgW5JLs8r1PU6DSIkNuW+npIEO5Tst3qiy2P5X+VP16TRvpGovBYN9xN6LliQfvb+10BaZpeh4+u9rkrwnjOWsWMKwkQBgVXXk4EZUZPGz7/HunWWfjc9BzoKJzfQyZga1jFiCbkJFaI4cPv9kSAWrbFAo7oYYgBbtKJkdlmvMtqXA0q7uJjpjNU+zMJpKU6qDOS+DI+AzyPIP/8TSdHcKyoXz14/qkpJC1W/8Aj0hWW9A1nRn8x6towxdxdz3o25qQkjo4pB9zqBVw3IyOw==
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=UsEDNERCgMcdb+2qqf4ZaPfv5LeGDfR/mnqctkRw0z0=; b=E9j7WdsM82vBcT9iiwettRwujiJ0Zz3U4+kpS+YJ4JPHHyxC9utV8zKt31mXFtm1dW5ALpUcuAKDdIDDr4aB46tmUn6SAfgEmmjlaYMrKRr8iaJcLRa/6d4LtzgZf0s0CZ+7LMmJfDY61ON4wekVx9lzXucpZkcbSCQirVJ1m58=
Received: from BYAPR11MB2584.namprd11.prod.outlook.com (2603:10b6:a02:c8::31) by BYAPR11MB3543.namprd11.prod.outlook.com (2603:10b6:a03:b1::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.32; Tue, 29 Sep 2020 18:24:53 +0000
Received: from BYAPR11MB2584.namprd11.prod.outlook.com ([fe80::61db:d07f:1813:af8d]) by BYAPR11MB2584.namprd11.prod.outlook.com ([fe80::61db:d07f:1813:af8d%6]) with mapi id 15.20.3412.029; Tue, 29 Sep 2020 18:24:53 +0000
From: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
To: Tommy Pauly <tpauly@apple.com>
CC: "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>, 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+tehkJP0ZMgkKNO88gp8Y0RKluSaBQgBHrXQCAAAECQA==
Date: Tue, 29 Sep 2020 18:24:53 +0000
Message-ID: <BYAPR11MB2584406116E1874719B74538DA320@BYAPR11MB2584.namprd11.prod.outlook.com>
References: <SN6PR11MB2589632C6BAE9DF09633323DDA3F0@SN6PR11MB2589.namprd11.prod.outlook.com> <BA5345AC-A344-40F8-A371-CBFBB7D5870B@apple.com>
In-Reply-To: <BA5345AC-A344-40F8-A371-CBFBB7D5870B@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: 152aa8aa-6cc7-4a24-5495-08d864a4f60a
x-ms-traffictypediagnostic: BYAPR11MB3543:
x-microsoft-antispam-prvs: <BYAPR11MB35432693A6CD6EA4866278C1DA320@BYAPR11MB3543.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: JWnpnFAVzNuMTPrgb+qPZMgKZBx2zJPhH8yECXSICwDREfcj2vvLh/ohcQxTFPQHkgNk39TYx0seoWdelBWYeM+zojIQPPMdZYfoGBQUgJtXisGbQNf0r2wJGamwzshGfpzT9r9bYP/YrJ0IJWjNmzvtv6pY1TBPN7xNQLG+hB26eHKnEThMyf0PlVZSnREwY3GdRMh/0AgKzBWM7vp2v5ZVzSsU4BN5s3SFSfu2i/C0/cyJ3vZiJLBT0KoTURBaIGOJKr3USGF7plrOvngRPZYYSAckPDdrryfOiKhvqAuQl76Pubu38EuyWJyfNRPxEf3RH4i3OioYjGEMMCfFZBupwSzlLPHLwZTG5h4L7ZIIjD1QDljwA417D1CucaW+bfECwZ8dTTvG9agXFw/t9Q==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR11MB2584.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(136003)(396003)(376002)(346002)(366004)(39860400002)(5660300002)(83080400001)(33656002)(76116006)(8936002)(71200400001)(55016002)(2906002)(6506007)(53546011)(9686003)(52536014)(7696005)(186003)(966005)(86362001)(6916009)(478600001)(26005)(83380400001)(4326008)(8676002)(66446008)(66476007)(66556008)(64756008)(66946007)(316002)(54906003); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: Rq5erUSc0oPkZ0bZitAlzMayLfe3PKPwpCdxSG/yRB8QgcEdy6HvuJS6Tr6fNHSO7falMSeOURA3KAEamPmh1s/q573z9iuXvaWM46z94tl3zmj/i6YCV8Xnjexu6l4bkzNCSNBxzV03mc8+2Wsu/Nco/s4aBlRdlzMFqB8Gm083EwQWp1PtXJiN6jTWM3KcO9ybxlzpHVKjY2LyOp5VJfvQdK1t4bqyKeDad40h5mbGL/nYmLsskP1W1IC1R3C08R5LGHW+vxE6CoDV1xF0MweyLZlPs7K29VkhPcqtGWjv/vdSvBzjxkfzTuNuAD+Lk0qZfbPDu2yZ2BAqOTZfv1cEgxcvq9oYVurPvOl5mTrUPXQY85rDdgUrHKA3K90uX/dCIk7yxQf9SqR5K7ogNuL/W0zv/aUkvcFGGjsKhPuuIMsiIm50eLN3OgcsmYFIQPKFbrM0BXheNf3SLsbU+v7gv7PXiaPua3EdUNxGyF6/pBt7pNB6phNSLSk9Dy5hCK31cB+HDzkOZERTwF1rPlzON74yb8VJpCiLtiI4zH0pB7fCftEhJhKUa4YAvqZAhvL1o8Hd3cS9lLMu3wDyaiWzToP6M0cZUFk0cghnGlKE36CNjHuQhh1QnAuS+LKd9B2u/7w5mfuksEHFHZKahQ==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR11MB2584.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 152aa8aa-6cc7-4a24-5495-08d864a4f60a
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Sep 2020 18:24:53.6762 (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: xyFRVkXMPdVHwzlPAqCQwki+53F4ncNokm4pBbuz+FWN4UHg6cJx1dM9eO+PhJ31T1j6N2Ns00a8tIaECcOp7g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3543
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/U193EHfk19gJM2mDaEhhCQOkKOE>
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: Tue, 29 Sep 2020 18:25:06 -0000

Hi Tommy,

Thanks for your feedback. Here's the git link:
https://github.com/inband-oam/ietf/blob/master/drafts/draft-ietf-ippm-ioam-ipv6-options.xml
Text version is here: https://github.com/inband-oam/ietf/blob/master/drafts/versions/03/draft-ietf-ippm-ioam-ipv6-options-03.txt

Looking forward to your comments.

Thanks, Frank

> -----Original Message-----
> From: Tommy Pauly <tpauly@apple.com>
> Sent: Dienstag, 29. September 2020 20:19
> To: Frank Brockners (fbrockne) <fbrockne@cisco.com>
> Cc: draft-ietf-ippm-ioam-ipv6-options@ietf.org; draft-ioametal-ippm-6man-
> ioam-ipv6-deployment@ietf.org; IPPM Chairs <ippm-chairs@ietf.org>; Martin
> Duke <martin.h.duke@gmail.com>; IETF IPPM WG (ippm@ietf.org)
> <ippm@ietf.org>
> Subject: Re: Merging deployment considerations into IPv6 IOAM document
> 
> Hi Frank, all,
> 
> Thanks for providing this update. The combined document makes sense and, I
> believe, will provide a more useful resource to implementors.
> 
> Looking through the new text, I had a few textual/editorial nits. Is this available
> on a GitHub for comments or a PR?
> 
> Thanks,
> Tommy
> 
> > On Sep 18, 2020, at 1:56 AM, Frank Brockners (fbrockne)
> <fbrockne@cisco.com> wrote:
> >
> > 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