[mpls] Question on draft-lm-mpls-sfc-path-verification

Loa Andersson <loa@pi.nu> Thu, 17 September 2020 05:09 UTC

Return-Path: <loa@pi.nu>
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 D59D53A0A84; Wed, 16 Sep 2020 22:09:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 75UDEcTGOQDI; Wed, 16 Sep 2020 22:09:33 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3BF33A0A13; Wed, 16 Sep 2020 22:09:29 -0700 (PDT)
Received: from [192.168.0.14] (unknown [111.125.123.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 81CDC3279BE; Thu, 17 Sep 2020 07:09:26 +0200 (CEST)
To: draft-lm-mpls-sfc-path-verification@ietf.org, "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, liu.yao71@zte.com.cn
From: Loa Andersson <loa@pi.nu>
Message-ID: <3a54d74e-2608-db8b-6879-7f9f79c7e2dd@pi.nu>
Date: Thu, 17 Sep 2020 13:09:18 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/wXHqyXfMOXts9EEMWq5lbSp2o94>
Subject: [mpls] Question on draft-lm-mpls-sfc-path-verification
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: Thu, 17 Sep 2020 05:09:36 -0000

Yao,

This is a follow up from your presentation at the MPLS interim meeting 
September 16, 2020.

Thank you for the draft, I think the the problem you are addressing 
might turn out to be real.

A few early comments though.

You are defining new a new LSP Ping TLV and two  sub-TLVs for this TLV, 
but there are no IANA section in the document. An IANA section would 
probably have made it easier to parse the document.

However mostly my question was because I missed the early slides, 
including the SFC Validation TLV.

So let us see if I got it right after reading the document and go over 
the slides again.

You define a new LSP Ping TLV - the SFC Validation TLV.

You also define two sub-TLVs - the SFC Info Sub-TLV and the SFC Basic 
Unit FEC Sub-TLV.

The SFC Validation TLV may be included in a MPLS echo request or an MPLS 
echo reply.

The SFC Basic Unit FEC Sub-TLV maybe included in a SFC Validation TLV 
carried both in a MPLS echo request and a MPLS echo reply.

The SFC Info Sub-TL mayb be included in a SFC Validation TLV only if the 
TLV is carried in a MPLS echo replay.

Correct?

You need to define which range the TLV and sub-TLVs should be allocated 
from.

/Loa
-- 

Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert                          loa.pi.nu@gmail.com
Bronze Dragon Consulting             phone: +46 739 81 21 64