[AFS3-std] Updated rxgk draft

Steven Jenkins steven.jenkins@gmail.com
Sun, 15 Jan 2012 21:39:32 -0500


--20cf307f32dcda84c004b69c1fbc
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jan 10, 2012 at 5:58 AM, Simon Wilkinson <simon@sxw.org.uk> wrote:

> I have updated the core rxgk draft to incorporate all of the previous
> comments and corrections. The new version is available from
> http://tools.ietf.org/html/draft-wilkinson-afs3-rxgk-02
>


I have read the document and have no objections to the contents.

However, I do have some suggestions:

1- Should RFC 2744  be added to the references, specifically to provide a
source for various gss_* functions (e.g., gss_get_mic)? I also found the
usage of both gss_get_mic and get_mic within this document to be a bit
confusing, and that usage should either be made consistent, or perhaps an
explanation given to the reader to explain why both are used in the
document.
2- An edit might be done to capitalize all 'Requirements language'
elements.  (e.g., 'should' is inconsistently capitalized)

Thank you,
Steven

--20cf307f32dcda84c004b69c1fbc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Tue, Jan 10, 2012 at 5:58 AM, Simon W=
ilkinson <span dir=3D"ltr">&lt;<a href=3D"mailto:simon@sxw.org.uk">simon@sx=
w.org.uk</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
I have updated the core rxgk draft to incorporate all of the previous comme=
nts and corrections. The new version is available from <a href=3D"http://to=
ols.ietf.org/html/draft-wilkinson-afs3-rxgk-02" target=3D"_blank">http://to=
ols.ietf.org/html/draft-wilkinson-afs3-rxgk-02</a><br>
</blockquote></div><br><br>I have read the document and have no objections =
to the contents.=A0 <br><br>However, I do have some suggestions:<br><br>1- =
Should RFC 2744=A0 be added to the references, specifically to provide a so=
urce for various gss_* functions (e.g., gss_get_mic)? I also found the usag=
e of both gss_get_mic and get_mic within this document to be a bit confusin=
g, and that usage should either be made consistent, or perhaps an explanati=
on given to the reader to explain why both are used in the document.<br>
2- An edit might be done to capitalize all &#39;Requirements language&#39; =
elements.=A0 (e.g., &#39;should&#39; is inconsistently capitalized)<br><br>=
Thank you,<br>Steven<br><br>

--20cf307f32dcda84c004b69c1fbc--