Okay, I am find with the Y->N change. Nick, Yoav?
___
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
On Fri, Sep 18, 2020 at 10:28 AM Sean Turner wrote:
> Also, should we be adding “_legacy” to the names of the code points as was
> done for rsa_pkcs1_sha256_legacy by:
> https://www.ietf.org/archive/id/draft-davidben-tls13-pkcs1-00.txt?
>
My inclination is no. We didn't go about renaming the
Rich,
Just to close the loop on this, there are three values: Y, N, and blank. I tend
to think we should mark is as “N”:
If an item is not marked as "Recommended" (i.e., "N"), it does not
necessarily mean that it is flawed; rather, it indicates that the
item either has not been through
Looks good to me.
On Thursday, June 25, 2020 15:32 +04, Kathleen Moriarty
wrote:
> Thank you, Joe.
>
> Sent from my mobile device
>
> > On Jun 25, 2020, at 1:10 AM, Joseph Salowey wrote:
> >
> >
> > Hi All,
> >
> > I submitted a PR [1] for draft-ietf-tls-md5-sha1-deprecate to move
* I submitted a PR [1] for draft-ietf-tls-md5-sha1-deprecate to move the
recommended IANA registry entries for rsa_pkcs1_sha1 and ecdsa_sha1 in the
Signature Scheme registry from Y to N. This change can be incorporated with
any updates from the AD review.
Yes yes yes.
Or no no no?
I
Thank you, Joe.
Sent from my mobile device
> On Jun 25, 2020, at 1:10 AM, Joseph Salowey wrote:
>
>
> Hi All,
>
> I submitted a PR [1] for draft-ietf-tls-md5-sha1-deprecate to move the
> recommended IANA registry entries for rsa_pkcs1_sha1 and ecdsa_sha1 in the
> Signature Scheme
Hi All,
I submitted a PR [1] for draft-ietf-tls-md5-sha1-deprecate to move the
recommended IANA registry entries for rsa_pkcs1_sha1 and ecdsa_sha1 in the
Signature Scheme registry from Y to N. This change can be incorporated
with any updates from the AD review.
Please post to this thread if
