![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Martin Rex wrote: > I have _never_ disputed this motivation. And I certainly do not > want to take this freedom away from the customer. However, I clearly > want to deny the vendor a compliance tag for not providing a fully > functional option to the customer. Martin: That is exactly what mandatory to implement means. The vendor must implement it to be considered in compliance. However, you can't mandate in an IETF standard what is deployed by the users of the implementation. My requirement is that TLS be deployable without certificates if an alternative mechanism for managing keys distribution is available. I have that today with RFC 2712. Jeffrey Altman
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ TLS mailing list TLS at lists.ietf.org https://www1.ietf.org/mailman/listinfo/tls