Re: [Iasa20] Odd deprecations in draft-ietf-iasa2-consolidated-upd-05

I started my AD review of this doc but it seems like the issues Robert raised need to get sorted out before I can do it properly. My take is below.

In terms of the document header, it doesn’t seem like this document should be obsoleting any other documents. The Obsoletes: header indicates a replacement version of the document being obsoleted [1]. The point of collecting together a set of updates here was precisely that these updates were not substantive enough to warrant obsoleting individual documents — otherwise that could have been done on a document-by-document basis, as with 4071 and 7437. So I would expect this document to have only an Updates: header, not an Obsoletes: header.

The updates as already explained in the document for 2028, 2418, 3005, 3710, and 6702 make sense to me. 

3979 and 4879 do not need to be touched by this document because they have been obsoleted by 8179 already. If people want to mention that in an appendix, that seems fine but not strictly necessary.

3929 seems like it should have the same treatment as 2028, 2418, 3710, and 6702 in Section 2, namely s/IETF Executive Director/Managing Director, Secretariat/. I agree with Ted’s logic there.

3716 and 4633 seem like they can be left alone without consequence. 4633’s incidence of “Executive Director" actually just quotes 2418, which this document is updating. And as Russ noted regarding 3716, it’s a historical record from a committe that existed at the time. If people wanted to move both of these to historic I don’t think that would be wrong, but I also doubt it’s worth the effort and would require a separate document.

Alissa
[1] https://www.ietf.org/blog/iesg-statement-designating-rfcs-historic/

> On Feb 12, 2019, at 3:23 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
> 
> I realize this is a bit late (since the document has been pubreq'ed), but I wanted to call this out before IETF Last Call. A re-review of some of the documents going through the IAB stream caused me to read this one more closely this week. Apologies for not being active on the list when this was discussed.
> 
> I was surprised that this document was obsoleting things like RFC3929 ( Alternative Decision Making Processes for Consensus-Blocked Decisions in the IETF ) and RFC 4633 ( Experiment in Long-Term Suspensions From Internet Engineering Task Force (IETF) Mailing Lists ).
> 
> It seems outside the remit of this working group to deprecate/obsolete these (or perhaps any) RFCs (whether they should be or not).
> 
> I also note that the body had five RFCs that it asks to deprecate and move to historic, but only three of those listed as obsoleted.
> 
> RjS
> 
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20