Subject: [eap] EAP Keying Framework Editorial nits

From: Nick Petroni <[email-masked]>
Date: Wed, 15 Oct 2003 09:56:55 -0400 (EDT)

Typos/grammar errors in draft-ietf-eap-keying-00
Submitter name: Nick Petroni
Submitter email address: [email-masked]
Date first submitted: October 15, 2003
Reference:
Document: Keying Framework
Comment type: E
Priority: S
Section: 2.1.2, 3.1
Rationale/Explanation of issue:

Incorrect language, simple changes enclosed.

Requested change:
In section 2.1.2, second paragraph, change "cannot" to "can"

   In fact, the
   authenticator is not required to implement any EAP methods at all,
   nor cannot it be assumed to implement code specific to any EAP
   method.

to

   In fact, the
   authenticator is not required to implement any EAP methods at all,
   nor can it be assumed to implement code specific to any EAP
   method.

Requested change:
In section 3.1, second full paragraph, change "may be" to "may"

   Some methods may be
   support "fast resume" by caching EAP SA state on the EAP peer and
   server.

to

   Some methods may
   support "fast resume" by caching EAP SA state on the EAP peer and
   server.

_______________________________________________
eap mailing list
[email-masked]
http://mail.frascone.com/mailman/listinfo/eap