Re: [mpls] Comments on draft-andersson-mpls-mna-fwk-01

Tony Li <> Thu, 26 May 2022 17:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1785CC185B23; Thu, 26 May 2022 10:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.481
X-Spam-Status: No, score=-1.481 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_FREEMAIL_DOC_PDF=0.01, T_FREEMAIL_RVW_ATTCH=0.01] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id xrBbPHxB9C5v; Thu, 26 May 2022 10:50:20 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id 67AC3C15EB53; Thu, 26 May 2022 10:50:20 -0700 (PDT)
Received: by with SMTP id 137so1893863pgb.5; Thu, 26 May 2022 10:50:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=sender:from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=XhprSriKFKq+oVS7aCdfVaDeHjTja1KhV4mqPdZHirc=; b=NYyDTqyROvEizh8KJsUAR4JXwZYYjYsnmCSz9Lk5bRLl411NuDXVcIs9QE39wCfl6K jKf3kzWIE2/9vYq+/SZjn3QoDZv0aGGqkkiwAjrfFt6HiunFTqk3sXkhCVRc7fhBM+1+ j/ctUG9xLfbPDEPa0mGTBXeIosgBSToff4Vv7KNrw8lere2WPgECsE5NaRJr0TnW9sYB LWDsyghwgYPlb8DZMwpwGBVcx+p/2IVq4IfkLfDT+IkKhvwUS8SsY5N3ong/cVzHTTzC PCEi6zO7eqX+JIIoabDcDpiDamR37cOj+udOGKs9yw1lUmEKXR/Cof5bTuE6a9WdJgAD awFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:sender:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=XhprSriKFKq+oVS7aCdfVaDeHjTja1KhV4mqPdZHirc=; b=VRTNaOiMPT17RZ4DnoHytxnzO/SLm4/M5lfFg9Yyt+Xqj+f+XV0/SX8Y3tnc9FYHD3 Vg1LQI+0Jv6ZRd1WuPm7YG29pmt1enUO2yg7Bc3Kbpx+JprmbSpxTSiWronORY8iss4Y W5Ly4GqLhxc0DK/bvUErizhSXw+QG8kCBw2mH38tLDWQE7udrwdmRBzQNW6zwYBFjA8K Ui0bq2MZAlnYt1aaggCqlDMvM4YHxfeckxQfHvVM7GwCNl+40X3banAdr/FA3RWwMvSC kp/VA2oj27tHgg2+uoFz7VOpfFaaMr14o1OfGjERjBlAvjavlS+8RVNFxAw/xw21wHix EEbg==
X-Gm-Message-State: AOAM530aRPoLVxkIiJe0ZrOVb2r2Y4wWqAhJaYTWWKXtVKkjynwum7eh sT1kZRYk5RXoSG5Ir+D3OJxyEchrmgY=
X-Google-Smtp-Source: ABdhPJzFf7lMWGDAah8/bS6VlK5EDMW+7C1OJ3z8bNTqdiwPxJ8ne9i0azhhWXg9uB9yxEK/xS0tJQ==
X-Received: by 2002:a63:eb47:0:b0:3fb:10da:6699 with SMTP id b7-20020a63eb47000000b003fb10da6699mr3983175pgk.618.1653587418512; Thu, 26 May 2022 10:50:18 -0700 (PDT)
Received: from ( []) by with ESMTPSA id h6-20020a636c06000000b003c619f3d086sm1840252pgc.2.2022. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 May 2022 10:50:17 -0700 (PDT)
Sender: Tony Li <>
From: Tony Li <>
Message-Id: <>
Content-Type: multipart/mixed; boundary="Apple-Mail=_B5AEE6AF-8C7C-422D-9DAF-17622B1F5858"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.\))
Date: Thu, 26 May 2022 10:50:16 -0700
In-Reply-To: <>
Cc: "" <>, "" <>
To: "Dongjie (Jimmy)" <>
References: <>
X-Mailer: Apple Mail (2.3693.
Archived-At: <>
Subject: Re: [mpls] Comments on draft-andersson-mpls-mna-fwk-01
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 26 May 2022 17:50:26 -0000

Hi Jimmy,

Thank you for your comments.  I’ve replied to each and every one of them.  As you commented inside of a Word document, I’ve replied in kind.  Please see the attached document.

I have made a number of the changes that you’ve suggested.  I will send a separate post to the list with the updated document and a diff.

Many of the changes that you suggested hinge on a single question which you did not raise directly.  That question should have the input of the broader group, so I’ll raise it explicitly now:

	Currently the framework document implicitly precludes some of the mechanisms found in draft-song-mpls-eh-indicator.  
	Should the framework draft be broadened to encompass this draft?

Speaking personally (co-author hat off), I don’t see an architectural reason to disagree. Please don’t take this as support of the draft.  I still believe that this is a sub-optimal approach, but could it work architecturally?  I have to say that yes, it could, and thus the framework draft could and should be broadened to encompass this.  

If the group agrees with this, the changes to implement this are minimal and straightforward.

Could I please get input from the group?


> On May 25, 2022, at 7:34 AM, Dongjie (Jimmy) <> wrote:
> Dear authors, 
> Thanks for the effort in organizing and updating this document. I've reviewed the current version and have a number of comments and suggestions. 
> In my view, the most important thing for this framework document is to describe the possible changes introduced to the MPLS architecture, the MPLS data plane encoding, and the processing behaviors of the LSRs. 
> Please find the attached file for the details of my review notes. 
> Hope it helps and looking forward to your feedback. 
> Best regards,
> Jie
> <draft-andersson-mpls-mna-fwk-01_Jie Dong_0525.docx>