Hi,
As there was no objections, I made the following changes to the GitHub version
that will appear in draft-ietf-emu-eap-tls13-04
Section 2.1.1
OLD:
As stated in [RFC5216], the TLS cipher suite shall not be used to
protect application data. This applies also for early application
On Feb 1, 2019, at 7:20 AM, John Mattsson wrote:
> If we cannot come up with a good reason to have the requirement, I think we
> should consider removing it in draft-ietf-emu-eap-tls13.
> draft-ietf-emu-eap-tls13 already has a whole paragraph just trying to
> motivate why the use of an empty ap
Hi Alan
> Alan DeKok ; wrote:
>
>> The mentioned requirement comes from Section 2.4 of RFC 5216, which states
>> that:
>>
>> "Since the ciphersuite negotiated within EAP-TLS applies only to the EAP
>> conversation, TLS ciphersuite negotiation MUST NOT be used to negotiate the
>> ciphersuite
On Jan 31, 2019, at 11:42 AM, John Mattsson wrote:
>
> The mentioned requirement comes from Section 2.4 of RFC 5216, which states
> that:
>
> "Since the ciphersuite negotiated within EAP-TLS applies only to the EAP
> conversation, TLS ciphersuite negotiation MUST NOT be used to negotiate the
Hi Alan,
The mentioned requirement comes from Section 2.4 of RFC 5216, which states
that:
"Since the ciphersuite negotiated within EAP-TLS applies only to the EAP
conversation, TLS ciphersuite negotiation MUST NOT be used to negotiate the
ciphersuites used to secure data."
However, I do not
Section 2.1.1 says:
As stated in [RFC5216], the TLS cipher suite shall not be used to
protect application data. This applies also for early application
data. When EAP-TLS is used with TLS 1.3, early application data
SHALL NOT be used.
I can't find any such statement in RFC 5216.
