IETF Logo Mail Archive

[mpls] Comment on draft-gandhi-mpls-ioam-sr-05

xiao.min2@zte.com.cn Tue, 12 January 2021 01:49 UTC

Return-Path: <xiao.min2@zte.com.cn>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 638AC3A0964 for <mpls@ietfa.amsl.com>; Mon, 11 Jan 2021 17:49:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level:
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 fab2VBapFhbe for <mpls@ietfa.amsl.com>; Mon, 11 Jan 2021 17:49:27 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 3E2F43A0957 for <mpls@ietf.org>; Mon, 11 Jan 2021 17:49:25 -0800 (PST)
Received: from mxct.zte.com.cn (unknown [192.168.164.215]) by Forcepoint Email with ESMTPS id CBD14887A25A43FD35CE for <mpls@ietf.org>; Tue, 12 Jan 2021 09:49:23 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id B91E7E2F28FB41244F99 for <mpls@ietf.org>; Tue, 12 Jan 2021 09:49:22 +0800 (CST)
Received: from njxapp03.zte.com.cn ([10.41.132.202]) by mse-fl2.zte.com.cn with SMTP id 10C1n9x6099364 for <mpls@ietf.org>; Tue, 12 Jan 2021 09:49:09 +0800 (GMT-8) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njxapp02[null]) by mapi (Zmail) with MAPI id mid201; Tue, 12 Jan 2021 09:49:09 +0800 (CST)
Date: Tue, 12 Jan 2021 09:49:09 +0800
X-Zmail-TransId: 2afa5ffd0015e8d22b6e
X-Mailer: Zmail v1.0
Message-ID: <202101120949094647407@zte.com.cn>
In-Reply-To: <161020726794.17530.11589439685950388453@ietfa.amsl.com>
References: 161020726794.17530.11589439685950388453@ietfa.amsl.com
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: mpls@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 10C1n9x6099364
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/57E1DP_Xxb7x1_itec4tuO-FfRE>
Subject: [mpls] Comment on draft-gandhi-mpls-ioam-sr-05
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jan 2021 01:49:29 -0000

Hi authors,

While looking through the updated -05 version of this draft, a question emerged in my mind, with the separated Edge-to-Edge IOAM Indicator Label and Hop-by-Hop IOAM Indicator Label, how can the network operator achieve both the Edge-to-Edge IOAM and Hop-by-Hop IOAM simultaneously?
I think there are two ways to achieve that, one way is to define the third IOAM Indicator Label which indicates the existence of both Edge-to-Edge IOAM and Hop-by-Hop IOAM, another way is to merge the current two IOAM Indicator Labels and let the IOAM Option-Type to tell the difference between Edge-to-Edge IOAM and Hop-by-Hop IOAM.

Best Regards,
Xiao Min



原始邮件



发件人：internet-drafts@ietf.org
收件人：i-d-announce@ietf.org ;
抄送人：mpls@ietf.org;
日 期 ：2021年01月09日 23:49
主 题 ：[mpls] I-D Action: draft-gandhi-mpls-ioam-sr-05.txt



A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiprotocol Label Switching WG of the IETF.
 
        Title           : MPLS Data Plane Encapsulation for In-situ OAM Dataloo
        Authors         : Rakesh Gandhi
                          Zafar Ali
                          Clarence Filsfils
                          Frank Brockners
                          Bin Wen
                          Voitek Kozak
    Filename        : draft-gandhi-mpls-ioam-sr-05.txt
    Pages           : 14
    Date            : 2021-01-09
 
Abstract:
   In-situ Operations, Administration, and Maintenance (IOAM) records
   operational and telemetry information in the data packet while the
   packet traverses a path between two nodes in the network.  This
   document defines how IOAM data fields are transported with MPLS data
   plane encapsulation using new Generic Associated Channel (G-ACh),
   including Segment Routing (SR) with MPLS data plane (SR-MPLS).
 
 
The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-gandhi-mpls-ioam-sr/
 
There are also htmlized versions available at:
https://tools.ietf.org/html/draft-gandhi-mpls-ioam-sr-05
https://datatracker.ietf.org/doc/html/draft-gandhi-mpls-ioam-sr-05
 
A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-gandhi-mpls-ioam-sr-05
 
 
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
 
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
 
 
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

v2.23.0 | Report a Bug | By Email