Hi Alan,
thanks for the answers... aligned with what I thought and they do make
sense... :D Further considerations inline...
On 2/12/19 11:26 AM, Alan DeKok wrote:
On Feb 12, 2019, at 12:36 PM, Dr. Pala wrote:
[...]
This, led me to my first question: is there a de-facto "standard" way to ad
Hi,
I have reviewed this draft multiple times, I think this draft is very
well-written and ready to be published. A few minor comments:
- "3rd Generation Authentication and Key Agreement"
I see that this exact term was used in RFC 5448, but I find it quite strange. I
think the terminology is
Hi Oleg,
You are warmly welcome.
Not all methods use a TLS outer tunnel. For example: EAP-pwd has the following
text:
EAP-pwd fragmentation support is provided through the addition of
flags within the EAP-Response and EAP-Request packets, as well as a
Total-Length field of two octets. Fl
Hi all,
These are my first steps in this group so please correct me if I don't
follow the rules.
Per my experience the existing fragmentation method described in EAP-TLS
RFC 5216 serves good for all fragmentation needs. The method is reused by
PEAP, EAP-FAST, TEAP and EAP-TTLS. There's an ambiguit
Dear Dr. Pala,
On 2/12/19 7:36 PM, Dr. Pala wrote:
Hi all,
I am working on a draft for credentials management via EAP. When looking at the
different specifications, it seems a bit weird that EAP does not provide
Fragmentation control and requires each method to define their own way.
This, led
