eap Mailing List: Re: sm-02 nits

[Nick Petroni (npetroni]

Jari et al.,

I have created a -03b to address these issues. Please take a look and
provide feedback so we can produce a -03. 03b can be found at
http://www.cs.umd.edu/~npetroni/EAP/.

Thanks to Pasi, we now have an appendix with an ASCII table of the
state machine.

Please *do* note format issues, but I will likely not fix them all until
we get closer to a final version -- it's a pain to do. I do want to keep
a list though so we get them all.

Thanks,
nick

Nick L. Petroni, Jr.
Graduate Student, Computer Science
Maryland Information Systems Security Lab
University of Maryland
http://www.cs.umd.edu/~npetroni

On Thu, 18 Mar 2004, Jari Arkko wrote:

> Thanks for your quick response Nick. Inline some
> answers to your questions:
>
> >>- Move the second last paragraph after the text
> >>   that talks about the switch.
> >
> > I don't quite understand this request. Which paragraph moved where?
>
>     This document describes a state machine based on an EAP "Switch"
>     model. This model includes  events and actions for the interaction
>     between the EAP Switch and EAP methods. The State Machine and
>     associated model are informative only. Implementations may achieve
>     the same results using different methods.
>
>     A brief description of the EAP "Switch" model is given in the
>     Introduction section.
>
> =>
>
>     This document describes a state machine based on an EAP "Switch"
>     model. This model includes  events and actions for the interaction
>     between the EAP Switch and EAP methods. A brief description of
>     the EAP "Switch" model is given in the Introduction section.
>
>     The State Machine and associated model are informative only.
>     Implementations may achieve the same results using different
>     methods.
>
> >>- For some reason, the bottom page heading is right on
> >>   the next line after text ends. E.g. Section 4.1.
> >>   I find this a bit confusing, it takes a moment to
> >>   realize that your eyes have read into the heading and
> >>   not a continuation of the paragraph. If you can change
> >>   this easily, please do. If not, don't worry about it...
> >
> > This is a LaTeX-ism, worst case I will fix it by hand.
>
> Ok. Don't worry about it.
>
> >>- Inconsistent capitalization of the sentences explaining
> >>   variables, see e.g. Sections 4.1.1 vs 4.1.2.
> >
> > Which do you prefer? start with caps or no?
>
> Caps, and I think you have it everywhere else except
> 4.1.1.
>
> >>- In Section 5.2, I think it would be useful to add
> >>   the following just before "m.init": "In the following
> >>   we will discuss procedure calls that the state machine
> >>   can make to methods."
> >
> > done with slight word smithing.  "The following describes the interaction
> > between the state machine and EAP methods."
> >
> > Also made this change in 4.2. Furthermore, I made the order of "IN",
> > "OUT", and "IN/OUT" consistent between these two sections.
>
> Very good.
>
> >>- As discussed with the RFC editor and in IETF-59,
> >>   we need a .txt version with the state machine
> >>   as a table.
> >
> > Working on that now... should have something to show tonight or tomorrow.
>
> Great, thanks!
>
> --Jari
>
>