Hi WG,

Chairs requested me to review draft-dhody-pce-pceps-tls13.
Here are couple of comments regarding the draft, I'm not an expert in this 
area, so my comments may sometimes be inaccurate:

Intro:

  *   As RFC8253 is already making TLS 1.2 as required (Section 3.4 of 
RFC8253), why does this draft cares about "address support requirements for TLS 
1.2" ? What is missing in RFC8253 ?



Section 4:

  *   The two first paragraph related to TLS1.2 are already covered by RFC8253 
section 3.4, what is changing ?



  *   Regarding: "Implementations that support TLS 1.3 
[I-D.ietf-tls-rfc8446bis<https://datatracker.ietf.org/doc/html/draft-ietf-tls-rfc8446bis-05>]
 are REQUIRED to support the mandatory-to-implement cipher suites listed in 
Section 
9.1<https://datatracker.ietf.org/doc/html/draft-ietf-tls-rfc8446bis-05#section-9.1>
 of 
[I-D.ietf-tls-rfc8446bis<https://datatracker.ietf.org/doc/html/draft-ietf-tls-rfc8446bis-05>].ΒΆ<https://datatracker.ietf.org/doc/html/draft-dhody-pce-pceps-tls13#section-4-4>
     *   This is already mandated as per TLS1.3 draft (Section 9.1), so is the 
purpose of defining specific requirement for PCEP app ?

Security considerations:

  *   I don't see Security considerations of RFC8253 referred in the section ? 
shouldn't the draft build on top of it ? Is  there any new consideration 
compared to RFC8253 brought by TLS1.3?


Brgds,

Stephane

_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

Reply via email to