This highlights an interesting issue as an RFC goes from PS to IS. I would offer that most SHOULDs in a document will, if there are real implementations out there, migrate to MUST or MUST NOT. On Aug 31, 2011, at 9:57 AM, hector wrote: > I think you are speaking of long term operations where an SHOULD is so widely adopted, it inherently because a MUST have in all new implementations. So that vain, sure, eventually the better options naturally become part of the protocol to the extent the options might be even remove to simplify things. We also have the opposite where a SHOULD is implemented but no one users it so eventually, it may be remove as an option.
<<attachment: smime.p7s>>
_______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf