Tim Wicinski <tjw.i...@gmail.com> writes: > >I think only a document that is Standards Track is needed to change the > >SHOULD or RECOMMENDED values as a group - eg talking about all the
The good news is that I think everyone is generally aligned on standards track being required for higher level SHOULD/RECOMMENDED/MUSTs (and likely the equivalent inverses SHOULD NOT, MUST NOT, NOT RECOMMENDED). > One thing I've not seen mentioned in this discussion on IETF standards > track documents is Implementations and Interoperability. I think we likely mean for both. If the IETF wants people to strongly encourage implementing a particular algorithm, it would be IETF standards action only (Implement for DNSSEC Signing, Implement for DNSSEC Validation, Implement for DNSSEC Delegation, Implement for DNSSEC Validation). If the IETF wants to encourage the usage deployment, it should also be standards action only (Use for DNSSEC Signing, Use for DNSSEC Delegation, Use for DNSSEC Validation, Use for DNSSEC Validation). You're right we didn't explicitly spell that out and probably should. But I suspect we are aligned at that level (or to put it another way: does anyone disagree that anything higher than an initial MAY should require standards actions for any of those columns?) -- Wes Hardaker USC/ISI _______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
