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

"Frank Brockners (fbrockne)" <fbrockne@cisco.com> Mon, 12 October 2020 16:51 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 D28493A159B; Mon, 12 Oct 2020 09:51:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.597
X-Spam-Level:
X-Spam-Status: No, score=-9.597 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, HTML_MESSAGE=0.001, 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=kV6RFbWv; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=HKY7ri9u
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 X9Ft4IrmNOc2; Mon, 12 Oct 2020 09:51:38 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EEEA3A151D; Mon, 12 Oct 2020 09:51:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20420; q=dns/txt; s=iport; t=1602521498; x=1603731098; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=+/qwosLWTC9KG5/sDzV/opxNsfPWbBNGLZHuKDKDxQE=; b=kV6RFbWvFtK63+tEBesuydWThfkD+oliVYsWYsBacuu9FpWlApqz1WA+ uK/ebBAM5UULF+MrKc0+eTbyKrOt/6AnzV+xH1fFw/3pCYmOdHMtZK4kt jkhVelOqUlTi3OtWHNwCuIj1fuJu/aUiCg+ylJB/I2hggU/0CaYTV5ewA k=;
IronPort-PHdr: 9a23:KQQmRhMUnUrZ7EcmCMsl6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEvKwx3lbRRYHWrflDjrmev6PhXDkG5pCM+DAHfYdXXhAIwcMRg0Q7AcGDBEG6SZyibyEzEMlYElMw+Xa9PBtcAN76ahvZpXjhpTIXEw/0YAxyIOm9E4XOjsOxgua1/ZCbYwhBiDenJ71oKxDjpgTKvc5Qioxneas=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C5BQBkiIRf/4QNJK1gHAEBAQEBAQcBARIBAQQEAQGCD4EjL1EHcFkvLAqEM4NGA41RihGJe4RvgUKBEQNVCwEBAQ0BAScGAgQBAYQGRAIXgX8CJTgTAgMBAQsBAQUBAQECAQYEbYVcDIVyAQEBBBIRChMBATcBCwQCAQgOAgEEAQEoAwICAh8RFAkIAgQOBQgagwWBfk0DLgEDC5xQAoE5iGF2gTKDAQEBBYEzAYNYDQuCEAMGgTiCcoNugQaFUBuBQT+BEUOBT1AuPoIaQgKBRRwrCYJhM4ILIpMNATyHBpxCUgqCaIkBhlqGA4UtgxWKCJQdlR2IdoJskkgCBAIEBQIOAQEFgWsjgVdwFTuCaVAXAg2OH4NxilZ0AjUCBgEJAQEDCXyMOwGBEAEB
X-IronPort-AV: E=Sophos;i="5.77,367,1596499200"; d="scan'208,217";a="560480525"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 12 Oct 2020 16:51:37 +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 09CGpaWP002636 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 12 Oct 2020 16:51:36 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 12 Oct 2020 11:51:36 -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; Mon, 12 Oct 2020 12:51:35 -0400
Received: from NAM10-DM6-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; Mon, 12 Oct 2020 11:51:35 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=LA8BCcdzEH7W9G4RFCVcttoyS1sOMgXU9pdbi1xOE+v89I2K89+KuaYHZTMet4YlUI1Ma4Hvxh+2lDXj2K3Dj1kmHbsos6Sn1I78xhXtqiOOzOKeIn8IOJqEaLZbH86PS1Pd9Nf0rV4fDzM+2h26JflTCSl9MahCqABFdrx2Odls/kl1CEe7IuugnbPrYWukr3GY2dE+5UNzUqiWnzfInu+YolUyL0/4XVOgZUjs2k0ZHwCmIYh9FXY9p76He/pbRQfVH19KeCGh4Z+DzlGjyVE4DyyIgOwMU38sDJlk9d2rO7B0VdZPIqSxsWKV0yAHKlPppdZ4olv5efUfP1rM/w==
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=+/qwosLWTC9KG5/sDzV/opxNsfPWbBNGLZHuKDKDxQE=; b=IeBQ8MYYBk+d7Uxr1XJSYyQ3WbpHU89D68pvTwyFWS1oL1AN60YLMViTjDKVj2xAopIh3qsZeXdv0L4fr6/J2VnRYZoDTm9PeVtD9pWk2PlOalAvcmiY2BzIDOe5FsDBncz255FiijNmVbMAugpivrZo9WfZ5MAHRKzkvqHl4dT9FHvWfDAnK05K8FR99YuBPdS3m9XFlQ0ayE8KPXG004LI3By+NuRL8LLoGIp289amFT6uI+tGH4iakTocoXHfC+1nTNzviMQNsjHUqsRxARZh5oxfFZFcaICBaygnOGjfwxbHvbeKzN1CycncTXUXKhi3m/705I8XvzCZV6gPMQ==
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=+/qwosLWTC9KG5/sDzV/opxNsfPWbBNGLZHuKDKDxQE=; b=HKY7ri9uFoctXimzeDs0QD5mQXuq7tUGeqJVlJLggRuozCoCdL2Ay52U201s2jtm7C/clLJqW5tXFwmuWB9JpER9ME7+0NMmqa91rFl9JPPfWGUWU45TVMFEwYV9VEUj8M4yJovwNTaL7S6R0N8XdZ38XRht1VPL6lPd8cJLnCE=
Received: from BYAPR11MB2584.namprd11.prod.outlook.com (2603:10b6:a02:c8::31) by BYAPR11MB2710.namprd11.prod.outlook.com (2603:10b6:a02:c7::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.25; Mon, 12 Oct 2020 16:51:34 +0000
Received: from BYAPR11MB2584.namprd11.prod.outlook.com ([fe80::546d:44a0:ffc2:ebe7]) by BYAPR11MB2584.namprd11.prod.outlook.com ([fe80::546d:44a0:ffc2:ebe7%7]) with mapi id 15.20.3455.029; Mon, 12 Oct 2020 16:51:34 +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+tehkJP0ZMgkKNO88gp8Y0RKluSaBQgBHrXQCAAAECQIAUS1gAgAAJIjA=
Date: Mon, 12 Oct 2020 16:51:34 +0000
Message-ID: <BYAPR11MB258460175365BE45F83069F4DA070@BYAPR11MB2584.namprd11.prod.outlook.com>
References: <SN6PR11MB2589632C6BAE9DF09633323DDA3F0@SN6PR11MB2589.namprd11.prod.outlook.com> <BA5345AC-A344-40F8-A371-CBFBB7D5870B@apple.com> <BYAPR11MB2584406116E1874719B74538DA320@BYAPR11MB2584.namprd11.prod.outlook.com> <AF6D3FB0-B3B7-4F79-B861-483A9B1EB4CB@apple.com>
In-Reply-To: <AF6D3FB0-B3B7-4F79-B861-483A9B1EB4CB@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: [5.146.24.90]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: bb9aed0b-977a-4891-24ff-08d86ecf13e7
x-ms-traffictypediagnostic: BYAPR11MB2710:
x-microsoft-antispam-prvs: <BYAPR11MB271045739D9547D8708CC1D1DA070@BYAPR11MB2710.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: vDi6I/z2FlFpq7whKrqtWbcV37m770LSgz73fbHcHqjzvmP2TTDsmScEXdYz5q7DYv3qU+paWCSOFzWPiQ3UAYjmWWZIuwcBZNt1t/l+pBh2BSKJeimeDhoBbJ3VUrCWJRyuZVRJCSUL4WRcIjhuLLskqlUKmEnOpnRqPwOTeWQXuyWwa/EN+njhxLqSpU22i9bsG41Ni1xpSwIbTMdrQxbKuitJSXajLHJ+KHOFbwzgW7gTsGV1mp1Q8woLt0OBWAzyo93qZqU/Y6XSZB7xt0KUAnuxj6Rd9EqEJzedPX0LZ1ujOIHun5L2J+RdjkYaX8yjUslZS1d/9ML8fUe1xKYymsjXx62LolXc+V6oFew=
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:(346002)(376002)(136003)(366004)(39860400002)(396003)(66946007)(316002)(76116006)(66476007)(64756008)(52536014)(86362001)(66556008)(66446008)(5660300002)(7696005)(4326008)(55016002)(54906003)(71200400001)(83380400001)(166002)(33656002)(186003)(9686003)(26005)(6506007)(53546011)(6916009)(2906002)(8676002)(478600001)(966005)(9326002)(8936002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: lC+yDd906+ktT4OL8VHGQh3G8R3lkzlN9znKwnCVknB4+BYx6D+IglKhXo5sANnd2GJtGJpCWwxGqWdXt9egHilER1dxMA7hmzXYodMmnqEF4nyPUh6OaU4opckr5bKDfB2DHr5PNXSy4cgUPMKpcIo7eplURFdGVJW8bnGA9zhy7J3jOs1S3QI5o/pE0BdulzIcjdSlMADpM1Ix2XnMfsKNDc6vYK+SAelLuwHQLBYLBu7xgkhvxoKI6UKpeJYKuJ2ZhGgGDXHOncUKJxYeHZd67aSBDiw6vpFd4X3SXffTioLvYPH70Y7iK96tm90seSoZPCPL1vAlUTVqcSuyRuuPrGCB3Mla1FqFNVhIXbu/go0HOVEz942AnM9SJ7idkAdvky7dToJLlb40RfwemsFIYozrDu+1FIP7kFWapWn9x2W8CutAwI36hJgCE6in2cldZmT2NlvZ+FsxrO2jeSB8+2PbHkU7XEz0IAuKB0NrwiYPLCY9GxMt2hG1yhukv/R8cZT2POncZUK73eDqWD90cDxcpfs891jmm0sKbElFmavmV1SZEX+UaBDY0BZQ3jpgB+twQXVS15Meblt9tp2lrERofHdA+TwHj9bH4G0JYor4vJOsBJJuUa6wd0SMe+A6LkCrX/HbvJ5Hu/xL8g==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB258460175365BE45F83069F4DA070BYAPR11MB2584namp_"
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: bb9aed0b-977a-4891-24ff-08d86ecf13e7
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Oct 2020 16:51:34.1927 (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: hoSJODu7do35Fu1cWpVE4mRwnzHn+nqUA8HHgpCkE2qt4JW2Kob9QByIr7Avb6qM3bJdWd0JTtsufrFMt/pC/Q==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2710
X-OriginatorOrg: cisco.com
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/smRTC7JnMT46fvTgcK-dLzo0E2Q>
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: Mon, 12 Oct 2020 16:51:41 -0000

Hi Tommy,

Thanks much. The too long author list is a common – and not easily addressable issue as we all know.

Cheers, Frank

From: Tommy Pauly <tpauly@apple.com>
Sent: Montag, 12. Oktober 2020 18:17
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,

I’ve provided some editorial suggestions here:

https://github.com/inband-oam/ietf/pull/198

Also, we should clean up the long author list on this document:

https://github.com/inband-oam/ietf/issues/197

Best,
Tommy


On Sep 29, 2020, at 11:24 AM, Frank Brockners (fbrockne) <fbrockne@cisco.com<mailto:fbrockne@cisco.com>> wrote:

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<mailto:tpauly@apple.com>>
Sent: Dienstag, 29. September 2020 20:19
To: Frank Brockners (fbrockne) <fbrockne@cisco.com<mailto:fbrockne@cisco.com>>
Cc: draft-ietf-ippm-ioam-ipv6-options@ietf.org<mailto:draft-ietf-ippm-ioam-ipv6-options@ietf.org>; draft-ioametal-ippm-6man-
ioam-ipv6-deployment@ietf.org<mailto:ioam-ipv6-deployment@ietf.org>; IPPM Chairs <ippm-chairs@ietf.org<mailto:ippm-chairs@ietf.org>>; Martin
Duke <martin.h.duke@gmail.com<mailto:martin.h.duke@gmail.com>>; IETF IPPM WG (ippm@ietf.org<mailto:ippm@ietf.org>)
<ippm@ietf.org<mailto: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<mailto: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<mailto:tpauly@apple.com>>
Sent: Freitag, 14. August 2020 23:12
To: draft-ietf-ippm-ioam-ipv6-options@ietf.org<mailto:draft-ietf-ippm-ioam-ipv6-options@ietf.org>;
draft-ioametal-ippm-6man- ioam-ipv6-deployment@ietf.org<mailto:ioam-ipv6-deployment@ietf.org>
Cc: IPPM Chairs <ippm-chairs@ietf.org<mailto:ippm-chairs@ietf.org>>; Martin Duke
<martin.h.duke@gmail.com<mailto: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