IETF Logo Mail Archive

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

Tommy Pauly <tpauly@apple.com> Tue, 29 September 2020 18:19 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 0B34F3A12B3; Tue, 29 Sep 2020 11:19:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.301
X-Spam-Level:
X-Spam-Status: No, score=-3.301 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, 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 6hXpGgyvf-dk; Tue, 29 Sep 2020 11:19:04 -0700 (PDT)
Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) (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 B11123A12B2; Tue, 29 Sep 2020 11:19:01 -0700 (PDT)
Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.42/8.16.0.42) with SMTP id 08TIHvXm053543; Tue, 29 Sep 2020 11:18:59 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=content-type : content-transfer-encoding : from : mime-version : subject : date : message-id : references : cc : in-reply-to : to; s=20180706; bh=sN/E05/tK9XYl+/MSnvFY7v42R/lxYmIpsOXIpBCWoc=; b=uGA7r6aFz8aH/usBdYPwCV35eehfbJxAP7SgY3hvjV7cXaniWhkDmPFNBgX5uiGgUmf/ CwugYGz+noXEk5HGGIyf5TRQxicp1zZvdVU5kf6WR7V+6sRE3lhf+ugDtpYTso39+SHn AqafohS22Nc5CIGSMNyYcYGZeNiq9LKaYAUuLCdwugNSxC3biQ3U/9aR3pMPpSLrEjib Rjdg+xVCArSivU3C6TFZRB+Ll8wPVwLRPvI8lX9KUrLvPFvRU4905JeP4g6oVTP+4ZLT JFascQiPr0q7WzHQBA5/FTBRZ17iJQdRdPNeGbfuRYHsMecGnT9yp16T1mYagaAk/182 NA==
Received: from rn-mailsvcp-mta-lapp03.rno.apple.com (rn-mailsvcp-mta-lapp03.rno.apple.com [10.225.203.151]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 33t2ase37k-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 29 Sep 2020 11:18:59 -0700
Received: from rn-mailsvcp-mmp-lapp03.rno.apple.com (rn-mailsvcp-mmp-lapp03.rno.apple.com [17.179.253.16]) by rn-mailsvcp-mta-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.6.20200729 64bit (built Jul 29 2020)) with ESMTPS id <0QHF00F0KMVM4ID0@rn-mailsvcp-mta-lapp03.rno.apple.com>; Tue, 29 Sep 2020 11:18:58 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp03.rno.apple.com by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.6.20200729 64bit (built Jul 29 2020)) id <0QHF00U00M7EBW00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Tue, 29 Sep 2020 11:18:58 -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: eede592d-700b-4445-bedc-c9882d1bc74a
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: d7c43b2d-8876-4c0e-ac44-292d26ce1997
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-09-29_11:2020-09-29, 2020-09-29 signatures=0
Received: from localhost.localdomain (unknown [10.105.115.216]) by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.6.20200729 64bit (built Jul 29 2020)) with ESMTPSA id <0QHF00Q4MMVLYQ00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Tue, 29 Sep 2020 11:18:57 -0700 (PDT)
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: quoted-printable
From: Tommy Pauly <tpauly@apple.com>
MIME-version: 1.0 (1.0)
Date: Tue, 29 Sep 2020 11:18:56 -0700
Message-id: <BA5345AC-A344-40F8-A371-CBFBB7D5870B@apple.com>
References: <SN6PR11MB2589632C6BAE9DF09633323DDA3F0@SN6PR11MB2589.namprd11.prod.outlook.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>
In-reply-to: <SN6PR11MB2589632C6BAE9DF09633323DDA3F0@SN6PR11MB2589.namprd11.prod.outlook.com>
To: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
X-Mailer: iPhone Mail (18A373)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-09-29_11:2020-09-29, 2020-09-29 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/GX1UxsCxv2UCxlXHchlE16Zk120>
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:19:06 -0000

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

v2.23.0 | Report a Bug | By Email