Re: [Bier] BIER OAM Document Status

gregory.mirsky@ztetx.com Wed, 28 July 2021 21:15 UTC

Return-Path: <gregory.mirsky@ztetx.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20CF73A20DE; Wed, 28 Jul 2021 14:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.874
X-Spam-Level:
X-Spam-Status: No, score=-0.874 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, OBFU_TEXT_ATTACH=1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_HTML_ATTACH=0.01, T_OBFU_HTML_ATTACH=0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 894_7duZ_iDA; Wed, 28 Jul 2021 14:15:05 -0700 (PDT)
Received: from mxus.zteusa.com (mxus.zteusa.com [4.14.134.162]) (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 48E903A11FE; Wed, 28 Jul 2021 14:15:04 -0700 (PDT)
Received: from mse-us.zte.com.cn (unknown [10.36.11.29]) by Forcepoint Email with ESMTPS id 869977D3EC7A0B81FBAC; Thu, 29 Jul 2021 05:15:03 +0800 (CST)
Received: from mgapp01.zte.com.cn ([10.36.9.142]) by mse-us.zte.com.cn with SMTP id 16SLF0pD095181; Thu, 29 Jul 2021 05:15:00 +0800 (GMT-8) (envelope-from gregory.mirsky@ztetx.com)
Received: from mapi (mgapp02[null]) by mapi (Zmail) with MAPI id mid81; Thu, 29 Jul 2021 05:14:59 +0800 (CST)
Date: Thu, 29 Jul 2021 05:14:59 +0800
X-Zmail-TransId: 2afa6101c8d3fea43caa
X-Mailer: Zmail v1.0
Message-ID: <202107290514598856512@zte.com.cn>
Mime-Version: 1.0
From: gregory.mirsky@ztetx.com
To: aretana.ietf@gmail.com
Cc: bier@ietf.org, bier-chairs@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-us.zte.com.cn 16SLF0pD095181
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/5zk9w25pFCOVs-27CQ7SZYY4vMs>
Subject: Re: [Bier] BIER OAM Document Status
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2021 21:15:10 -0000

Hi Alvaro,


thank you very much for pointing it to me. Will wait for the WG discussion of the questions to the WG you've raised. I've copied them below. Please find my notes tagged by GIM>>:

Status.  This documents depends Normatively on rfc8321, which is an Experimental RFC.  In general, downward references are possible, but I don't think this is one of those cases.  The Shepherd writeup for rfc8321 [2] states that "the measurement utility of this extension still is to be demonstrated at a variety of scales in a plurality of network conditions."  As far as I can tell, that hasn't been demonstrated, nor specific information about the completion of the experiment was included in the RFC text.  I didn't see the topic of the document status discussed in the WG -- nor am I aware of discussions about the maturity of rfc8321 in the ippm WG.  The result is then that this document should be either Informational or Experimental.

GIM>> Though the BIER WG doesn't have to copy what other groups decide, I would refer to draft-ietf-6man-ipv6-alt-mark that is on the Standards track by 6man WG and in the IESG Evaluation. I know that the 6man WG also discussed the appropriate status for the document, and Giuseppe can give us more detail on what was done to have the draft on the Standards track.

Applicability.  The applicability to p2p/p2mp traffic is not explicitly discussed in rfc8321.  The specific applicability of PNPM to BIER should be clearly considered.


GIM>> Yes, Alternate mariking method in multipoint network is discussed in RFC 8889. Will add the reference.


Relationship to other WG items, e.g., draft-ietf-ippm-oam-requirements. 


GIM>> To the best of my understanding, the WG decided not to publish that informational document.


The attached diff between -05 and the current version -10 reflects all the updates made to address the AD review comments.







Regards,


Greg Mirsky






Sr. Standardization Expert
预研标准部/有线研究院/有线产品经营部 Standard Preresearch Dept./Wireline Product R&D Institute/Wireline Product Operation Division









E: gregory.mirsky@ztetx.com 
www.zte.com.cn






Original Mail



Sender: AlvaroRetana
To: gregory mirsky10211915;
CC: bier@ietf.org;bier-chairs@ietf.org;
Date: 2021/07/27 15:44
Subject: Re: [Bier] BIER OAM Document Status


_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier


Greg:


I know you didn’t ask me, but the intent of sending the document back to the WG is for the WG to discuss the updates (see the link below to the specific issues I want the WG to consider).


Thanks!


Alvaro.


On July 27, 2021 at 5:32:07 PM, gregory.mirsky@ztetx.com (gregory.mirsky@ztetx.com) wrote:





Hi Alvaro,

many thanks for clarifying the status of the draft.




Hi Tony and Greg,

the draft was updated to address AD review comments. Do you feel these changes need a formal presentation to the WG, or can the draft be moved to the second WG LC?








Regards,


Greg Mirsky






Sr. Standardization Expert
预研标准部/有线研究院/有线产品经营部 Standard Preresearch Dept./Wireline Product R&D Institute/Wireline Product Operation Division









E: gregory.mirsky@ztetx.com 
www.zte.com.cn















Sender: AlvaroRetana
To: bier-chairs@ietf.org;gregory mirsky10211915;bier@ietf.org;
Date: 2021/07/26 18:05
Subject: Re: [Bier] BIER OAM Document Status


On July 26, 2021 at 7:23:57 PM, gregory.mirsky@ztetx.com wrote:


Hi!


> draft-ietf-bier-pmm-oam - it appears to be marked as "Dead". The authors
> addressed AD review comments, and the updated version is available (not
> expired).

This shows up as "Dead" from the IESG point of view because -06 (which
was the version I returned to the WG) expired: the system then marks
the document as "Dead" (again, from the IESG point of view, not the
WG).

What is needed if for the WG to revisit the document: I returned it
because it needs more WG input, and so that I am not the gating
factor.  I will look at the changes after the document goes back
through the process (WGLC, etc) and is sent back for publication.

Take a look at my comments from 2019-07-02:
https://datatracker.ietf.org/doc/draft-ietf-bier-pmmm-oam/history/


Thanks!

Alvaro.

_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier