Comments on draft-ietf-bfd-hmac-sha

["Nobo Akiya (nobo)" <[e-mail]>]

Hi Authors,

I have reviewed your draft (draft-ietf-bfd-hmac-sha), comments below.
Since document is nearing expiration, perhaps you can address some of these comments and re-publish?


(1) Section 3, couple of places

s/avaliable/available/g


(2) Section 2, 3, 4

I see that most texts from sections 3 & 4 overlaps with texts in draft-ietf-bfd-generic-crypto-auth. Are texts in section 2 something required for BFD to use HMAC-SHA (i.e. required to interop)?  I'm just wondering why this is a standard-track document, i.e. with draft-ietf-bfd-generic-crypto-auth available, whether or not we need to write standard-track draft for every authentication that BFD need to use going forward. Maybe I over-looked something ...


(3) Section 2

Missing '.' chars.

[old]
   B is the block size of H, measured in octets rather than bits.  Note
   that B is the internal block size, not the hash size.  For SHA-1 and
   SHA-256: B == 64 For SHA-384 and SHA-512: B == 128 L is the length of
   the hash, measured in octets rather than bits.
[new]
   B is the block size of H, measured in octets rather than bits.  Note
   that B is the internal block size, not the hash size.  For SHA-1 and
   SHA-256: B == 64. For SHA-384 and SHA-512: B == 128. L is the length
   of the hash, measured in octets rather than bits.
[snip]


-Nobo