Re: [ippm] Adoption call for draft-ioametal-ippm-6man-ioam-ipv6-options

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 12 September 2019 02:15 UTC

Return-Path: <jmh@joelhalpern.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 22D52120232; Wed, 11 Sep 2019 19:15:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 gCIfymxRMHxZ; Wed, 11 Sep 2019 19:15:00 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 A77F81200B7; Wed, 11 Sep 2019 19:15:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 46TMmN4BJmz1bF53; Wed, 11 Sep 2019 19:15:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1568254500; bh=w/SX+Yp9ydokxSUcnBBzrMveWAjsTEvLccMiE73YGtE=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=c8yq9D7WLKswcpqomcoiRAdpcEaloueB/hFhLK99KMP6JoU/9ad4+kdAMKOBK2HZp 3BXCbeiSg6j0653eQVcR+qFt8ZhgdoLAdPgjDj2wXpWIdlTK7s+g43rIEcBMBwyK+l Kpvowbaf/e1oVo9hut4Om4TfQc0aWZH3ecgxCm4A=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [172.20.7.244] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 46TMmL0mFfz1bF4t; Wed, 11 Sep 2019 19:14:57 -0700 (PDT)
To: Lizhenbin <lizhenbin@huawei.com>, Anoop Ghanwani <anoop@alumni.duke.edu>, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
Cc: "draft-ioametal-ippm-6man-ioam-ipv6-options@ietf.org" <draft-ioametal-ippm-6man-ioam-ipv6-options@ietf.org>, IPv6 List <ipv6@ietf.org>, IETF IPPM WG <ippm@ietf.org>
References: <EF8A9ED8-171F-42E4-9E69-82EB25F5D294@apple.com> <CA+-tSzwFBLdFgm=Veb9JpK3Up8BgJp=sW24RdvYX5v3F0Z13KA@mail.gmail.com> <5A5B4DE12C0DAC44AF501CD9A2B01A8D934AD23E@DGGEMM532-MBX.china.huawei.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <af5be46c-3a42-415f-e7c1-9d4a46c5989b@joelhalpern.com>
Date: Wed, 11 Sep 2019 22:14:56 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <5A5B4DE12C0DAC44AF501CD9A2B01A8D934AD23E@DGGEMM532-MBX.china.huawei.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/QqCF5L6GWEePK59NTjHnaBT6mco>
Subject: Re: [ippm] Adoption call for draft-ioametal-ippm-6man-ioam-ipv6-options
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: Thu, 12 Sep 2019 02:15:03 -0000

No, please.
That draft proposes recoding the information from SFC's NSH into some 
other format.  This removes the entire interoperability premise of teh 
NSH work.

Yours,
Joel

On 9/11/2019 9:14 PM, Lizhenbin wrote:
> Agree very much. We also proposed the challenges and the optimization 
> considering when IOAM and SRH are used together in the following draft.
> 
> https://datatracker.ietf.org/doc/draft-li-6man-ipv6-sfc-ifit/
> 
> That is the reason why we do not think the solution proposed by 
> draft-ioametal-ippm-6man-ioam-ipv6-options is reasonable.
> 
> In order for better understanding and discussion, 6MAN WG is copied.
> 
> Best Regards,
> 
> Zhenbin (Robin)
> 
> *From:*ippm [mailto:ippm-bounces@ietf.org] *On Behalf Of *Anoop Ghanwani
> *Sent:* Thursday, September 12, 2019 8:31 AM
> *To:* Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
> *Cc:* draft-ioametal-ippm-6man-ioam-ipv6-options@ietf.org; IETF IPPM WG 
> <ippm@ietf.org>
> *Subject:* Re: [ippm] Adoption call for 
> draft-ioametal-ippm-6man-ioam-ipv6-options
> 
> How would the headers look when IOAM is used in conjunction with IPv6 
> segment routing?  Does the IOAM header and metadata precede or 
> follow the segment routing header?
> 
> Thanks,
> 
> Anoop
> 
> On Wed, Sep 11, 2019 at 9:11 AM Tommy Pauly 
> <tpauly=40apple.com@dmarc.ietf.org <mailto:40apple.com@dmarc.ietf.org>> 
> wrote:
> 
>     Hello IPPM,
> 
>     This email starts a working group adoption call for
>     draft-ioametal-ippm-6man-ioam-ipv6-options. This document defines
>     the IPv6 option encapsulation for IOAM data. This document was
>     discussed with the 6man WG, which advised that the work be done in
>     ippm, with review by 6man.
> 
>     The documents are available here:
> 
>     https://datatracker.ietf..org/doc/draft-ioametal-ippm-6man-ioam-ipv6-options/
>     <https://datatracker.ietf.org/doc/draft-ioametal-ippm-6man-ioam-ipv6-options/>
>     https://tools.ietf.org/html/draft-ioametal-ippm-6man-ioam-ipv6-options-02
> 
>     Please reply to this email by Wednesday, September 25, with your
>     input on whether or not the WG should adopt this document.
> 
>     Best,
>     Tommy (as IPPM co-chair)
>     _______________________________________________
>     ippm mailing list
>     ippm@ietf.org <mailto:ippm@ietf.org>
>     https://www.ietf.org/mailman/listinfo/ippm
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>