Re: [ippm] Merging deployment considerations into IPv6 IOAM document
Tommy Pauly <tpauly@apple.com> Mon, 12 October 2020 16:17 UTC
Return-Path: <tpauly@apple.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 528B43A0E8B; Mon, 12 Oct 2020 09:17:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.3
X-Spam-Level:
X-Spam-Status: No, score=-3.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.2, 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_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 d_BkpyAAM_WJ; Mon, 12 Oct 2020 09:17:36 -0700 (PDT)
Received: from nwk-aaemail-lapp01.apple.com (nwk-aaemail-lapp01.apple.com [17.151.62.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B3043A0C8B; Mon, 12 Oct 2020 09:17:36 -0700 (PDT)
Received: from pps.filterd (nwk-aaemail-lapp01.apple.com [127.0.0.1]) by nwk-aaemail-lapp01.apple.com (8.16.0.43/8.16.0.42) with SMTP id 09CGAIFL017640; Mon, 12 Oct 2020 09:17:34 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=zNfOZlY+kPYFcr8yNTjCbwBmfVNZdiGgjArzDfFvPYM=; b=nTmXhQmw8mcSgDiPDi2sVOhYgYYj9ohNRLrMeWOmOKCafr6ecGDldtXmJgohNRZe+HLT cf6c7gi7v9nbLXxOfmmmmNUe3Xv/TB8j9/yJeSSOIhn0p+Nf1wFiHZlP6h4Q82RyDcvi JK4CJm7iuJdfEgdFFLxPiv1w4rAWPxK2b2VdIqeErg+tqhnYHdcQwvVf2g180LyyUpfm lt9vKpu5I0ha7islfpVPUjhyNjDo8lqBFurfT+t09PEeee0yQOH9lXmfmZk1yXK+FbAU 1rL2mz8mlGgIRe7VJzgVim9qnWe4zFo2p0SxtDFVOik1u9nHaztUQ7jzyhJXwRa1UuhM uw==
Received: from rn-mailsvcp-mta-lapp02.rno.apple.com (rn-mailsvcp-mta-lapp02.rno.apple.com [10.225.203.150]) by nwk-aaemail-lapp01.apple.com with ESMTP id 344smts152-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 12 Oct 2020 09:17:34 -0700
Received: from rn-mailsvcp-mmp-lapp04.rno.apple.com (rn-mailsvcp-mmp-lapp04.rno.apple.com [17.179.253.17]) by rn-mailsvcp-mta-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.6.20200729 64bit (built Jul 29 2020)) with ESMTPS id <0QI300J8NJXAVJA0@rn-mailsvcp-mta-lapp02.rno.apple.com>; Mon, 12 Oct 2020 09:17:34 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp04.rno.apple.com by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.6.20200729 64bit (built Jul 29 2020)) id <0QI300200JOCUV00@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Mon, 12 Oct 2020 09:17:34 -0700 (PDT)
X-Va-A:
X-Va-T-CD: c1b389506f216bb3aba14cffce0c1559
X-Va-E-CD: 8bf595ab35985b6539caa1f8e396c411
X-Va-R-CD: 9cb08760a38ef3426f7d36a976f60ef5
X-Va-CD: 0
X-Va-ID: 9086f4d9-feae-4eb1-aff8-341239243eaa
X-V-A:
X-V-T-CD: c1b389506f216bb3aba14cffce0c1559
X-V-E-CD: 8bf595ab35985b6539caa1f8e396c411
X-V-R-CD: 9cb08760a38ef3426f7d36a976f60ef5
X-V-CD: 0
X-V-ID: 0c429bcc-dcb4-4034-bb03-348a9738bba9
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-10-12_12:2020-10-12, 2020-10-12 signatures=0
Received: from localhost.localdomain (unknown [17.232.218.59]) by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.6.20200729 64bit (built Jul 29 2020)) with ESMTPSA id <0QI300687JX0WD00@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Mon, 12 Oct 2020 09:17:33 -0700 (PDT)
From: Tommy Pauly <tpauly@apple.com>
Message-id: <AF6D3FB0-B3B7-4F79-B861-483A9B1EB4CB@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_84A07F27-2186-426F-8257-70A2D9006704"
MIME-version: 1.0 (Mac OS X Mail 14.0 \(3654.0.3.2.26\))
Date: Mon, 12 Oct 2020 09:17:24 -0700
In-reply-to: <BYAPR11MB2584406116E1874719B74538DA320@BYAPR11MB2584.namprd11.prod.outlook.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>
To: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
References: <SN6PR11MB2589632C6BAE9DF09633323DDA3F0@SN6PR11MB2589.namprd11.prod.outlook.com> <BA5345AC-A344-40F8-A371-CBFBB7D5870B@apple.com> <BYAPR11MB2584406116E1874719B74538DA320@BYAPR11MB2584.namprd11.prod.outlook.com>
X-Mailer: Apple Mail (2.3654.0.3.2.26)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-10-12_12:2020-10-12, 2020-10-12 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/s_gvV71RT9yEiRcOhsFJbQt4jzU>
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:17:38 -0000
Hi Frank, I’ve provided some editorial suggestions here: https://github.com/inband-oam/ietf/pull/198 <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 <https://github.com/inband-oam/ietf/issues/197> Best, Tommy > On Sep 29, 2020, at 11:24 AM, Frank Brockners (fbrockne) <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> >> 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
- Re: [ippm] Merging deployment considerations into… Frank Brockners (fbrockne)
- Re: [ippm] Merging deployment considerations into… Tommy Pauly
- Re: [ippm] Merging deployment considerations into… Frank Brockners (fbrockne)
- Re: [ippm] Merging deployment considerations into… Tommy Pauly
- Re: [ippm] Merging deployment considerations into… Frank Brockners (fbrockne)
- Re: [ippm] Merging deployment considerations into… Tommy Pauly