The Flexible Authentication via Secure Tunneling Extensible Authentication Protocol Method (EAP-FAST)
RFC 4851
Yes
No Objection
No Record
Note: This ballot was opened for revision 06 and is now closed.
Lars Eggert No Objection
(Jari Arkko; former steering group member) (was Discuss) Yes
> If an inner EAP method is run, then the Peer-Id is obtained from the > inner method. What if multiple inner methods are run? > EAP-FAST packets contain a three bit version field, following the TLS > Flags field, which All TLS data comes *after* the EAP-FAST version field. Did you mean "following the EAP-FAST Flags field"?
(Russ Housley; former steering group member) Yes
(Brian Carpenter; former steering group member) No Objection
(Dan Romascanu; former steering group member) No Objection
There are a couple of places in this document where the vendor-ID is coded in three octets, although a four octets coding could have been used. Is there a reason for doing this? I would not be too much concerned because this should suffice for all practical reasons (8,288,608 enterprises - right now only 27825 codes are allocated) but maybe a note should indicate that we are placing a limitation and what are the reasons.
(David Kessens; former steering group member) No Objection
(Magnus Westerlund; former steering group member) No Objection
(Ross Callon; former steering group member) No Objection
(Ted Hardie; former steering group member) No Objection
(Cullen Jennings; former steering group member) No Record
Given what is in here and how it is used, I would prefer PS.