IETF Logo Mail Archive

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

wangyali <wangyali11@huawei.com> Sun, 24 May 2020 11:49 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 598EC3A0A60 for <ippm@ietfa.amsl.com>; Sun, 24 May 2020 04:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-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 3W5jywpFbBoL for <ippm@ietfa.amsl.com>; Sun, 24 May 2020 04:49:46 -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 9AD573A0A5F for <ippm@ietf.org>; Sun, 24 May 2020 04:49:45 -0700 (PDT)
Received: from lhreml709-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id B38FE4BA46952CC3554A for <ippm@ietf.org>; Sun, 24 May 2020 12:49:41 +0100 (IST)
Received: from lhreml709-chm.china.huawei.com (10.201.108.58) by lhreml709-chm.china.huawei.com (10.201.108.58) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Sun, 24 May 2020 12:49:41 +0100
Received: from DGGEML405-HUB.china.huawei.com (10.3.17.49) by lhreml709-chm.china.huawei.com (10.201.108.58) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1913.5 via Frontend Transport; Sun, 24 May 2020 12:49:41 +0100
Received: from DGGEML524-MBX.china.huawei.com ([169.254.1.54]) by dggeml405-hub.china.huawei.com ([10.3.17.49]) with mapi id 14.03.0487.000; Sun, 24 May 2020 19:49:36 +0800
From: wangyali <wangyali11@huawei.com>
To: "ippm@ietf.org" <ippm@ietf.org>
Thread-Topic: Questions about draft-xiao-ippm-ioam-conf-state
Thread-Index: AdYxv7teg1vaP9pKRO+OVDyrWBO9tw==
Date: Sun, 24 May 2020 11:49:35 +0000
Message-ID: <1520992FC97B944A9979C2FC1D7DB0F404E70E53@dggeml524-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.174.162]
Content-Type: multipart/alternative; boundary="_000_1520992FC97B944A9979C2FC1D7DB0F404E70E53dggeml524mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/nVZpvQzVsBur-azTqE_U96CzWCo>
Subject: [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: Sun, 24 May 2020 11:49:49 -0000

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.

Second, could this extension to the echo request/reply mechanisms also be used in ICMP defined for IPv4?

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.

Thanks,
Yali

v2.23.0 | Report a Bug | By Email