Re: [ippm] RFC 8321 and 8889 Tue, 24 August 2021 00:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C40553A0FB6 for <>; Mon, 23 Aug 2021 17:41:56 -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 XeBGUlBjmo2K for <>; Mon, 23 Aug 2021 17:41:50 -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 B2FDE3A0FB5 for <>; Mon, 23 Aug 2021 17:41:50 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTPS id 5E2454A7B65972E203DF; Tue, 24 Aug 2021 08:41:47 +0800 (CST)
Received: from ([]) by with SMTP id 17O0ff3I034998; Tue, 24 Aug 2021 08:41:41 +0800 (GMT-8) (envelope-from
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid201; Tue, 24 Aug 2021 08:41:41 +0800 (CST)
Date: Tue, 24 Aug 2021 08:41:41 +0800 (CST)
X-Zmail-TransId: 2afb61244045bb27f854
X-Mailer: Zmail v1.0
Message-ID: <>
In-Reply-To: <>
References:, d392b3339899499590e0d1c9e7a761a0@M10-HQ-ML02.hq.cnc.intra,,,
Mime-Version: 1.0
From: <>
To: <>
Cc: <>, <>, <>
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: 17O0ff3I034998
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: Tue, 24 Aug 2021 00:41:57 -0000

Hi Martin,

I'd like to work on this, as an author or a contributor.

Best Regards,
Xiao Min
抄送人:Ran Pang(联通集团中国联通研究院-本部);IETF IPPM WG;
日 期 :2021年08月24日 03:35
主 题 :Re: [ippm] RFC 8321 and 8889
ippm mailing list

Hi Al, this is my impression as well. In a perfect world I would ask the WG to do a bis draft to inventory what is mature and to deprecate the bits that haven't seen real deployment. If it turns out that it's all deployed, then we could do a simpler document action.

Is this work that anyone is interested in taking on?

On Fri, Aug 20, 2021 at 9:41 AM MORTON JR., AL <> wrote:
Hi Martin,
While I don’t have a serious concern, I’d prefer to elevate the parts of 8321 that *were implemented* to PS.  I think I read that some parts were not implemented and I look to those who reported on their implementations to say what they did.
This thinning-out of non-implemented capabilities was a feature of Standards Track Advancement processes in the past, so it makes sense to apply it here as well.  I realize this means a new draft, but the processing could be accelerated to match the need.
If the entire RFC 8321 was implemented, then this point is a non-issue.
hope this helps,
From: ippm <> On Behalf Of Martin Duke
Sent: Friday, August 20, 2021 12:31 PM
To: Ran Pang(联通集团中国联通研究院-本部)  <>
Subject: Re: [ippm] RFC 8321 and 8889

Thanks all,
I'm hearing strong consensus that 8321 should be a PS and somewhat weaker support for 8889, but no dissents.
If anyone has serious concerns, this would be a good time to say so.

On Fri, Aug 20, 2021 at 3:02 AM Ran Pang(联通集团中国联通研究院-本部)  <> wrote:
Hi Martin and WG,
The alt-mk described in RFC8321/8889 has been deployed in some of our networks.
It works well.
So I would like the WG consider elevate them to proposed standard.
Best regards,
Pang Ran.
From: Martin  Duke
Date: 2021-08-13 02:26
Subject: [ippm]  RFC 8321 and 8889
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?)
如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。  If you have received this email in error please notify us immediately by e-mail. Please reply to ,you can unsubscribe from this mail. We will immediately remove your information  from send catalogue of our.