IESG, The move to Historic seems appropriate given the explanation below, however, while these specs are out of my field of expertise, three mostly-procedural observations/ comments: (1) LISP and the associated details have gotten enough attention in the broader community that a few sentences about the impact of the end of these experiments on the Proposed Standard version of the protocol set (e.g., RFC 9300ff.) and the residual Experimental protocols and maybe Informational documents, i.e., RFC 6831ff would be in order. If it is worth cleaning up some of the early LISP proposals and other documents, why not clean up all of them? Or, if there is a reason why those other documents should be retained as apparently active Experiments it seems to me that it would be worthwhile to put a sentence or two in some prominent location explaining why. (2) For much the same reason as above, this seems to me to deserve a brief RFC, not just a change in status with links into the datatracker that will likely be obscure or invisible to likely readers who are not active and experienced IETF participants. Except for whatever is said about those other documents, I think virtually all of the substantive text for such an RFC is in the Last Call announcement. (3) The Last Call announcement concludes with "IESG discussion of this request can be tracked..." but the link given produces a "page not found" error. Presumably it should either be corrected to refer to the parent page, https://datatracker.ietf.org/doc/status-change-lisp-eid-block-to-historic/ , or someone should fix the datatracker record so that ../ballot/ exists and contains at least placeholder text. thanks, john --On Thursday, August 10, 2023 12:01 -0700 The IESG <iesg-secretary@xxxxxxxx> wrote: > > The IESG has received a request from an individual participant > to make the following status changes: > > - RFC7954 from Experimental to Historic > (Locator/ID Separation Protocol (LISP) Endpoint Identifier > (EID) Block) > > - RFC7955 from Informational to Historic > (Management Guidelines for the Locator/ID Separation > Protocol (LISP) Endpoint Identifier (EID) Block) > > The supporting document for this request can be found here: > > https://datatracker.ietf.org/doc/status-change-lisp-eid-block- > to-historic/ > > 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 2023-09-07. 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/rfc7954/ > https://datatracker.ietf.org/doc/rfc7955/ > > IESG discussion of this request can be tracked via > https://datatracker.ietf.org/doc/status-change-lisp-eid-block- > to-historic/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
