Skip to main content

Reclassification of RFC 1142 to Historic
RFC 7142

Yes

(Adrian Farrel)
(Joel Jaeggli)
(Sean Turner)
(Stewart Bryant)

No Objection

(Benoît Claise)
(Brian Haberman)
(Gonzalo Camarillo)
(Jari Arkko)
(Martin Stiemerling)
(Spencer Dawkins)
(Stephen Farrell)
(Ted Lemon)

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

Adrian Farrel Former IESG member
Yes
Yes ()

                            
Joel Jaeggli Former IESG member
Yes
Yes ()

                            
Sean Turner Former IESG member
Yes
Yes ()

                            
Stewart Bryant Former IESG member
Yes
Yes ()

                            
Barry Leiba Former IESG member
No Objection
No Objection (2013-12-30)
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.
Benoît Claise Former IESG member
No Objection
No Objection ()

                            
Brian Haberman Former IESG member
No Objection
No Objection ()

                            
Gonzalo Camarillo Former IESG member
No Objection
No Objection ()

                            
Jari Arkko Former IESG member
No Objection
No Objection ()

                            
Martin Stiemerling Former IESG member
No Objection
No Objection ()

                            
Pete Resnick Former IESG member
No Objection
No Objection (2014-01-06)
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.)
Spencer Dawkins Former IESG member
No Objection
No Objection ()

                            
Stephen Farrell Former IESG member
No Objection
No Objection ()

                            
Ted Lemon Former IESG member
No Objection
No Objection ()