Re: Nits in current drafts

[Chris Lonvick <clonvick%cisco.com@localhost>]

Hi,

On Sun, 20 Feb 2005, Ben Harris wrote:

> I've mentioned some of these before,

Sorry, I must have missed them.

> but all of them still apply to the
> set of drafts released on Friday.
>
> draft-ietf-secsh-transport-23.txt:
>
> Section 6.4: replace "The hash algorithms are described in [SCHNEIER]."
> with "The SHA-1 hash algorithm is described in [FIPS-180-2].  The MD5 hash
> algorithm is described in [RFC1321]."

OK.

>
> Section 6.6: replace each occurrence of "the SHA-1 hash" with "the SHA-1
> hash, as defined in [FIPS-180-2],".

Like Sam says, the first occurance should be sufficient.

>
> Section 6.6: replace "according to [SCHNEIER] and [RFC3447]" with
> "according to the RSASSA-PKCS1-v1_5 scheme of [RFC3447]".

OK.

>
> Sections 8.1, 8.2: replace each occurrence of "SHA-1" with "SHA-1, as
> defined in [FIPS-180-2],".
>
> Section 15.1: delete references [RFC2693] and [RFC3280].

Good catch.

>
> Section 15.1: add references:
>
>     <reference anchor="RFC1321">
>      <front>
>       <title>The MD5 Message-Digest Algorithm</title>
>       <author initials='R.' surname='Rivest' fullname='Ronald L. Rivest'>
>        <organization/>
>       </author>
>       <date month="April" year="1992"/>
>      </front>
>      <seriesInfo name='RFC' value='1321'>
>     </reference>

The references for RFCs are already done.
  http://xml.resource.org/public/rfc/bibxml/
I just have to pull that (actually just the tar) and then give an
"include" in the document.
  <?rfc include="./references/reference.RFC.1321.xml"?>

>
>     <reference anchor="FIPS-180-2">
>      <front>
>       <title>Secure Hash Standard (SHS)</title>
>       <author>
>        <organization>National Institute of Standards and Technology
>        (NIST)</organization>
>       </author>
>       <date month="August" year="2002"/>
>      </front>
>      <seriesInfo name="FIPS PUB" value="180-2"/>
>     </reference>

Unlike the RFCs, there are not too many FIPS pubs in the repository
  http://xml.resource.org/public/rfc/bibxml2/

>
> The references to other FIPS PUBs could do with all having the same
> format and being in numerical order.  I'd suggest replacing them with:

OK.

>
>     <reference anchor="FIPS-46-3">
>      <front>
>       <title>Data Encryption Standard (DES)</title>
>       <author>
>        <organization>National Institute of Standards and Technology
>        (NIST)</organization>
>       </author>
>       <date month="October" year="1999"/>
>      </front>
>      <seriesInfo name="FIPS PUB" value="46-3"/>
>     </reference>

I think the seriesInfo should be spelled out:

<reference anchor='FIPS-46-3'>
<front>
<title>Data Encryption Standard (DES)</title>
<author>
<organization>National Institute of Standards and
Technology</organization>
</author>
<date month='October' year='1999'/>
</front>
<seriesInfo name='Federal Information Processing Standards Publication'
value='46-3' />
</reference>

and I'll make them all consistent.

>
>     <reference anchor="FIPS-186-2">
>      <front>
>       <title>Digital Signature Standard (DSS)</title>
>       <author>
>        <organization>National Institute of Standards and Technology
>        (NIST)</organization>
>       </author>
>       <date month="January" year="2000"/>
>      </front>
>      <seriesInfo name="FIPS PUB" value="186-2"/>
>     </reference>
>
>     <reference anchor="FIPS-197">
>      <front>
>       <title>Advanced Encryption Standard (AES)</title>
>       <author>
>        <organization>National Institute of Standards and Technology
>        (NIST)</organization>
>       </author>
>       <date month="November" year="2001"/>
>      </front>
>      <seriesInfo name="FIPS PUB" value="197"/>
>     </reference>
>
> draft-ietf-secsh-connect-24.txt:
>
> Section 5.2: replace second paragraph with:
>
>     After receiving this message, the recipient MAY send the given number
>     of bytes more than it was previously allowed to send; the window size
>     is incremented.  Implementations MUST correctly handle window sizes of
>     up to 2^32 - 1 bytes.  The window MUST NOT be increased above 2^32 - 1
>     bytes.
>

OK.

Thanks,
Chris