Re: [ippm] Questions about draft-xiao-ippm-ioam-conf-state

wangyali <wangyali11@huawei.com> Thu, 28 May 2020 02:55 UTC

Return-Path: <wangyali11@huawei.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 B9D163A0B44 for <ippm@ietfa.amsl.com>; Wed, 27 May 2020 19:55:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 5hf3K90Kf4WP for <ippm@ietfa.amsl.com>; Wed, 27 May 2020 19:54:54 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 4745F3A0B4B for <ippm@ietf.org>; Wed, 27 May 2020 19:54:54 -0700 (PDT)
Received: from lhreml726-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id AB2059CE2C0DE6D89944 for <ippm@ietf.org>; Thu, 28 May 2020 03:54:50 +0100 (IST)
Received: from lhreml726-chm.china.huawei.com (10.201.108.77) by lhreml726-chm.china.huawei.com (10.201.108.77) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 28 May 2020 03:54:50 +0100
Received: from DGGEML424-HUB.china.huawei.com (10.1.199.41) by lhreml726-chm.china.huawei.com (10.201.108.77) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Thu, 28 May 2020 03:54:50 +0100
Received: from DGGEML524-MBX.china.huawei.com ([169.254.1.54]) by dggeml424-hub.china.huawei.com ([10.1.199.41]) with mapi id 14.03.0487.000; Thu, 28 May 2020 10:54:45 +0800
From: wangyali <wangyali11@huawei.com>
To: Tommy Pauly <tpauly@apple.com>, "xiao.min2@zte.com.cn" <xiao.min2@zte.com.cn>
CC: "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>
Thread-Topic: [ippm] Questions about draft-xiao-ippm-ioam-conf-state
Thread-Index: AQHWNJqYr5xvN3MSSUOBKieAvvQg5qi8zPbg
Date: Thu, 28 May 2020 02:54:44 +0000
Message-ID: <1520992FC97B944A9979C2FC1D7DB0F404E7B392@dggeml524-mbx.china.huawei.com>
References: <202005261657347762187@zte.com.cn> <1520992FC97B944A9979C2FC1D7DB0F404E7ADD6@dggeml524-mbx.china.huawei.com> <202005271721263284249@zte.com.cn> <E2910907-2BD1-4069-97CF-459F226ADC77@apple.com>
In-Reply-To: <E2910907-2BD1-4069-97CF-459F226ADC77@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.203.65]
Content-Type: multipart/alternative; boundary="_000_1520992FC97B944A9979C2FC1D7DB0F404E7B392dggeml524mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/mGg-TMdWtwg6x8hzB-b-SgBL26s>
Subject: Re: [ippm] Questions about draft-xiao-ippm-ioam-conf-state
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, 28 May 2020 02:55:02 -0000

Hi Min and Tommy,

Thank you. Significant information.

Yali

From: Tommy Pauly [mailto:tpauly@apple.com]
Sent: Thursday, May 28, 2020 10:49 AM
To: xiao.min2@zte.com.cn; wangyali <wangyali11@huawei.com>
Cc: IETF IPPM WG (ippm@ietf.org) <ippm@ietf.org>
Subject: Re: [ippm] Questions about draft-xiao-ippm-ioam-conf-state

To be clear regarding IPv4, the guidance in previous meetings has been that a standard IPv4 extension is almost certainly not something that would progress as a standard. I would suggest not basing work on the presence of such an IPv4 extension.

Best,
Tommy


On May 27, 2020, at 2:21 AM, xiao.min2@zte.com.cn<mailto:xiao.min2@zte.com.cn> wrote:

Hi Yali,

This draft is a supportive document to IOAM encapsulations, so I believe it's too early to consider concrete ICMPv4 extensions, before there is rough consensus on IOAM over IPv4 encapsulation.

Best Regards,
Xiao Min
原始邮件
发件人:wangyali <wangyali11@huawei.com<mailto:wangyali11@huawei.com>>
收件人:肖敏10093570;
抄送人:ippm@ietf.org<mailto:ippm@ietf.org> <ippm@ietf.org<mailto:ippm@ietf.org>>;
日 期 :2020年05月27日 10:11
主 题 :RE: Re:[ippm] Questions about draft-xiao-ippm-ioam-conf-state
Hi Min,

Thanks for your reply. Please see inline [Yali].

Best regards,
Yali

From: xiao.min2@zte.com.cn<mailto:xiao.min2@zte.com.cn> [mailto:xiao.min2@zte.com.cn]
Sent: Tuesday, May 26, 2020 4:58 PM
To: wangyali <wangyali11@huawei.com<mailto:wangyali11@huawei.com>>
Cc: ippm@ietf.org<mailto:ippm@ietf.org>
Subject: Re:[ippm] Questions about draft-xiao-ippm-ioam-conf-state

Hi Yali,

Many thanks for your review and questions.
Please see my inline reply with <XM>.

Best Regards,
Xiao Min
原始邮件
发件人:wangyali <wangyali11@huawei.com<mailto:wangyali11@huawei.com>>
收件人:ippm@ietf.org<mailto:ippm@ietf.org> <ippm@ietf.org<mailto:ippm@ietf.org>>;
日期:2020年05月24日 19:50
主题:[ippm] Questions about draft-xiao-ippm-ioam-conf-state
_______________________________________________
ippm mailing list
ippm@ietf.org<mailto:ippm@ietf.org>
https://www.ietf.org/mailman/listinfo/ippm
Hi authors,

This is Yali. This is an interesting work. I have following two questions.

First, is the list of Namespace-IDs the subset or all of Namespaces which the IOAM encapsulating node belongs to? If it is, I suggest adding some words to illustrate this.
<XM>  Yes, you're correct. I'll make it more clear in the next revision.
 [Yali] OK. Thanks.
Second, could this extension to the echo request/reply mechanisms also be used in ICMP defined for IPv4?
<XM>  In theory the mechanism described in this draft can also apply to ICMPv4, whereas I believe ICMPv4 needs to be taken into account only after the IOAM over IPv4 is defined. Currently the IOAM over IPv6 has been adopted in IPPM WG as draft-ietf-ippm-ioam-ipv6-options, if you're interested, we can work together on ICMPv6 first.
 [Yali] IOAM over IPv6 is important. While considering a scenario that IOAM applied in the legacy IPv4 network, I think the problem of echo request/reply IOAM node capabilities also needs to be taken account. But it may be discussed in another draft later.
In my opinion, as the Information Request and Reply Type=15 and Type=16 have been obsolete [RFC6918], so it could be used as the IOAM Capability echo request/reply messages to acquire the enabled IOAM capabilities.
 [Yali] Do you think this is a way to request/reply IOAM capabilities?
Thanks,
Yali



_______________________________________________
ippm mailing list
ippm@ietf.org<mailto:ippm@ietf.org>
https://www.ietf.org/mailman/listinfo/ippm