Re: [smime] HTTP Encrypted Content-Encoding

ietf-smime

Re: [smime] HTTP Encrypted Content-Encoding

2015-04-02 11:22:17

On 2 April 2015 at 08:12, Russ Housley <housley(_at_)vigilsec(_dot_)com> wrote:

I do not understand the desire to avoid crypto agility.


It's not a desire to avoid agility; it's a desire to have the agility
mechanisms align with the extensibility model that is already in
place.

_______________________________________________
smime mailing list
smime(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/smime

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[smime] HTTP Encrypted Content-Encoding, Martin Thomson Re: [smime] HTTP Encrypted Content-Encoding, Paul Hoffman Re: [smime] HTTP Encrypted Content-Encoding, Sean Turner Re: [smime] HTTP Encrypted Content-Encoding, Paul Hoffman Re: [smime] HTTP Encrypted Content-Encoding, Sean Turner Re: [smime] HTTP Encrypted Content-Encoding, Martin Thomson Re: [smime] HTTP Encrypted Content-Encoding, Russ Housley Re: [smime] HTTP Encrypted Content-Encoding, Martin Thomson <=

Previous by Date:	Re: [smime] HTTP Encrypted Content-Encoding, Russ Housley
Next by Date:	[smime] IPR Disclosure Certicom Corp.'s Statement about IPR related to RFC 2631, IETF Secretariat
Previous by Thread:	Re: [smime] HTTP Encrypted Content-Encoding, Russ Housley
Next by Thread:	[smime] IPR Disclosure Certicom Corp.'s Statement about IPR related to RFC 2631, IETF Secretariat
Indexes:	[Date] [Thread] [Top] [All Lists]