[radext] suggested charter text wrt FIPS-140

[Stephen Farrell <[e-mail]>]

Hi all,

Based on yesterday's and today's discussion I'd suggest the
following change to the draft charter [1] text on that:

OLD:

    - Defining a secure variant of RADIUS which can be used in
      a FIPS-140 compliant environment.

NEW:

    - Document WG consensus on requirements for RADIUS (not
      necessarily in an RFC) in a FIPS-140 environment and
      subsequently define a secure variant of RADIUS that can
      be used in such a FIPS-140 compliant environment.

The "(not necessarily in an RFC)" phrase is more or less
what we did in the lake WG where the requirements are still
in an I-D [2] but we did a WGLC on that before moving on
to protocol specification.

If that's ok with people then I suggest our AD make that
change to [1] and the FIPS-140 stuff can be figured out
when the WG is chartered, i.e. we'd not need to bottom
out on it beforehand.

Cheers,
S.

[1] https://datatracker.ietf.org/doc/charter-ietf-radext/
[2] https://datatracker.ietf.org/doc/draft-ietf-lake-reqs/