> This one's for Barry: Can a Standards Track document contradict another > one on the basis of an accepted erratum? Or should we do a quick update > to RFC5965 (not a "bis", just a standards-track correction)?
The second (contradicting) S-T document can be the one to do the "quick update" (you don't need a separate document to do it). Just make it "Updates 5965", include text in the introduction that says it updates 5965 to change XYZ, and then in the normative text where you make the contradiction, add a sentence that says "This updates the requirement [or whatever] in RFC 5965." b _______________________________________________ marf mailing list [email protected] https://www.ietf.org/mailman/listinfo/marf
