Re: [Last-Call] Last Call: RFC 8321 (Alternate-Marking Method for Passive and Hybrid Performance Monitoring) and RFC 8889 (Multipoint Alternate-Marking Method for Passive and Hybrid Performance Monitoring)to Proposed Standard

["touch@xxxxxxxxxxxxxx" <touch@xxxxxxxxxxxxxx>]

FWIW, I would also expect a summary report on the “experiment”, i.e., what is known now that wasn’t known then.

For RFCs issued under 6 months ago, it seems unlikely things would change that much.

Joe

On Aug 29, 2021, at 9:51 AM, Barry Leiba <barryleiba@xxxxxxxxxxxx> wrote:

I don't understand how we can reclassify Experimental RFCs to Proposed
Standard without re-issuing them with a new RFC number, as the
boilerplate is incompatible.  Specifically, the "Status of This Memo"
section says:

  This document is not an Internet Standards Track specification; it is
  published for examination, experimental implementation, and
  evaluation.

  This document defines an Experimental Protocol for the Internet
  community.

The status-change reclassification is for reclassification in place
(as when we move from Proposed Standard to Internet Standard, or from
any status to Historical).  But to move Experimental to Proposed
Standard, it seems to me that we need a new Internet Draft that
Obsoletes the Experimental RFC, with normal processing of that draft
and publication as a new RFC.

Barry

On Fri, Aug 27, 2021 at 5:08 PM The IESG <iesg-secretary@xxxxxxxx> wrote:

The IESG has received a request from an Area Director to make the
following status changes:

- RFC8321 from Experimental to Proposed Standard
   (Alternate-Marking Method for Passive and Hybrid Performance Monitoring)

- RFC8889 from Experimental to Proposed Standard
   (Multipoint Alternate-Marking Method for Passive and Hybrid Performance
   Monitoring)

The supporting document for this request can be found here:

https://datatracker.ietf.org/doc/status-change-rfc8321-rfc8889-alt-mark-to-ps/

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@xxxxxxxx mailing lists by 2021-09-24. Exceptionally, comments may
be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

The affected documents can be obtained via
https://datatracker.ietf.org/doc/rfc8321/
https://datatracker.ietf.org/doc/rfc8889/

IESG discussion of this request can be tracked via
https://datatracker.ietf.org/doc/status-change-rfc8321-rfc8889-alt-mark-to-ps/ballot/



_______________________________________________
IETF-Announce mailing list
IETF-Announce@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf-announce

--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call

-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call