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

Inline:

On 2/12/19 3:14 PM, Brian E Carpenter wrote:
> Hi Robert,
> On 2019-02-13 09:23, Robert Sparks 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).
> Clearly, directly relevant RFCs may need to be obsoleted, but I agree
> that these two in particular are essentially "collateral damage".
> 3716, on the other hand, is just an old Informational on how we used
> to administer the IETF, so it needs to go.
>
> 4633 is explicitly time limited, so obsoleting it seems like routine
> book keeping that the IESG could do at any time. All the same, it needs
> to be called out during Last Call.
>
> 3929 has no explicit time limit, which these days is considered bad
> practice for procedural experiments. So yes, it isn't this WG's
> job to decide. But the IETF can of course decide. If it's clear
> that this is subject to Last Call comments, is there really a problem?
>
>> 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.
> You are quite right about those other two. They should be in a separate
> list which is essentially FYI. They don't need any status change.
>
> 3979 is not out of date. Its bullet point correctly says:
>
> o  RFC 3979 [RFC3979], that is updated by [RFC8179], which corrects
>     mentions of the IETF Executive Director to the IETF Secretariat
>
> so it should not be deprecated.
>
> 4879 is already obsoleted by 8179. So its bullet point should say:
>
> o  RFC 4879 [RFC4879], that is obsoleted by [RFC8179], which corrects
>     mentions of the IETF Executive Director to the IETF Secretariat.
>
> Regards
>     Brian
There's also a call at the end of section 4 to move all 5 of the docs it 
calls out to historic...
>> RjS
>>
>> _______________________________________________
>> iasa20 mailing list
>> iasa20@ietf.org
>> https://www.ietf.org/mailman/listinfo/iasa20
>>