On Fri, Oct 23, 2020 at 9:20 AM Jouni Malinen wrote:
> On Thu, Oct 22, 2020 at 05:44:33PM +0300, Oleg Pekar wrote:
> > The Authority-ID TLV is used by the client to identify the TEAP server it
> > is talking to. If the same client talks to more than one TEAP server - it
> > can keep PACs or cache
On Thu, Oct 22, 2020 at 05:44:33PM +0300, Oleg Pekar wrote:
> The Authority-ID TLV is used by the client to identify the TEAP server it
> is talking to. If the same client talks to more than one TEAP server - it
> can keep PACs or cached data from all of them identified by
> the Authority-ID. If we
The Authority-ID TLV is used by the client to identify the TEAP server it
is talking to. If the same client talks to more than one TEAP server - it
can keep PACs or cached data from all of them identified by
the Authority-ID. If we make it optional in TEAP start message but keep
mandatory in PAC-In
Errata 5765: https://www.rfc-editor.org/errata/eid5765
Proposed Status: Verified
Revision: (unmodified from original posting)
Section 4.2.2 says:
M
Mandatory, set to one (1)
It should say:
M
0 (Optional)
Notes:
Authority-ID TLV is used only as an Outer TLV (in TEAP/Start)