Reclassification of RFC 1142 to Historic
RFC 7142

Note: This ballot was opened for revision 00 and is now closed.

(Stewart Bryant) Yes

(Adrian Farrel) Yes

(Joel Jaeggli) Yes

(Sean Turner) Yes

(Jari Arkko) No Objection

(Gonzalo Camarillo) No Objection

(Benoît Claise) No Objection

(Spencer Dawkins) No Objection

(Stephen Farrell) No Objection

(Brian Haberman) No Objection

Barry Leiba No Objection

Comment (2013-12-30)
No email
send info
Procedurally, I wish this had been done with a status-change document, rather than with an RFC.  But I have no objection -- the action seems correct.

(Ted Lemon) No Objection

(Pete Resnick) No Objection

Comment (2014-01-06)
No email
send info
I've got no problem with reclassifying 1142 as Historic. Normally, moving a document to Historic would require a separate Last Call, but the Last Call for this document was crystal clear in what it intended. And even though I find it a bit weird to move an Informational document to Historic, this document makes it clear that the purpose in doing so is to assure that references no longer get made to 1142, since 1142 is no longer the definitive spec. That said, I'd really prefer if we stopped this practice of *documents* "reclassifying" other documents. A document can't make another document move from Proposed to Standard, and similarly a document shouldn't make another document move to Historic (recent practices notwithstanding). The *IESG* reclassifies documents. So I'd ask that you change the Abstract to say:

   This memo outlines why RFC 1142, OSI IS-IS Intra-domain Routing
   Protocol, should be moved to Historic status.

I'd strike the bit about Obsoletes. This document is not a new version of 1142, which is why you'd use Obsoletes. 1142 will show as Historic in all of the tools, so no need to have Obsoletes as well.

Finally, strike the last paragraph of section 1.

(Note to Adrian: When this document gets approved, make sure you remind the Secretariat to send out a *separate* Document Action to move RFC 1142 to Historic. Without the status change document, that won't get done automatically.)

(Martin Stiemerling) No Objection