Re: [ippm] RFC 8321 and 8889 Fri, 13 August 2021 03:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 16D5A3A1AB1 for <>; Thu, 12 Aug 2021 20:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id GnqWIpiENQ6p for <>; Thu, 12 Aug 2021 20:26:20 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1208A3A1AB0 for <>; Thu, 12 Aug 2021 20:26:19 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTPS id EA72DBA6108ACD29CF3F; Fri, 13 Aug 2021 11:26:14 +0800 (CST)
Received: from (unknown []) by Forcepoint Email with ESMTPS id 44009694D9239F834137; Fri, 13 Aug 2021 11:26:13 +0800 (CST)
Received: from ([]) by with SMTP id 17D3Q3wP063063; Fri, 13 Aug 2021 11:26:03 +0800 (GMT-8) (envelope-from
Received: from mapi (njxapp04[null]) by mapi (Zmail) with MAPI id mid201; Fri, 13 Aug 2021 11:26:03 +0800 (CST)
Date: Fri, 13 Aug 2021 11:26:03 +0800 (CST)
X-Zmail-TransId: 2afc6115e64b84c11cfa
X-Mailer: Zmail v1.0
Message-ID: <>
In-Reply-To: <>
Mime-Version: 1.0
From: <>
To: <>
Cc: <>
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: 17D3Q3wP063063
Archived-At: <>
Subject: Re: [ippm] =?utf-8?q?RFC_8321_and_8889?=
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 13 Aug 2021 03:26:25 -0000

Hi Martin,

AFAIK, RFC 8321 has been implemented (by at least three vendors) and deployed (by at least one operator) in MPLS mobile backhaul networks.
Although not all measuring options described in RFC 8321 are implemented, e.g. only fixed-timer block and double-marking methodology are used, I believe it's still reasonable to elevate it to PS.
As to RFC 8889, I have no idea on its maturity level, so I'll let others to comment.
With that said, I tend to support that we take action 1) and elevate RFC 8321 to PS.

Best Regards,
Xiao Min
日 期 :2021年08月13日 02:27
主 题 :[ippm] RFC 8321 and 8889
ippm mailing list

Hello IPPM,

(with AD hat on)

The IESG is currently considering
which is the implementation of RFC 8321 and 8889 techniques in an IPv6 framework. IIUC, this is very much how things are "supposed to work" -- measurement definitions and methodology are done by IPPM, and the protocol-specific instantiations are in the respective working groups.

However, there are complications in that 8321 and 8889 are Experimental RFCs, and the ipv6-alt-mark draft is a Proposed Standard. This has resulted in text from 8321/8889 going into ipv6-alt-mark so that it can be elevated to PS. I'm told that, if the status quo holds, other drafts will reference ipv6-alt-mark to avoid a downref. This seems suboptimal.

I would prefer that we take one of the two following actions:
1) If the WG has consensus that we are comfortable that there is enough experience with 8321 and/or 8889 to elevate them to PS, I can initiate a document action to change their status.

2) If there is no such consensus, ipv6-alt-mark should be Experimental.

In either case, the draft can probably lose some of the duplicate text.

Logically, there is a third option -- that the bits of the RFCs copied in the draft are mature enough to be a standard, but that the others aren't. Though I'm not an expert, I doubt this is the case. But if people believe it to be true, we'll have to come up with new options.

I would be grateful for the working group's thoughts about these documents and the ideas therein. Is it reasonable for people to read and reflect on this by 26 August (2 weeks from today?)