Tuomas Aura: I have some minor editorial comments, which I'll post /
mail to the editor as soon as they have been typed in.

---------------

Tuomas Aura:

Section 2: 
"Nonce - A random number generated by..." --> 
"Nonce - An unpredictable random or pseudorandom 
number generated by...";
"non-SEND" --> "Non-SEND" (capitalize)

Figure at the end of Section 2: 
"ND message specific data" --> "ND Message-
Specific Data" (capitalize; hyphen optional 
depending on your style)

Section 4, 2nd bullet: 
"Cryptographically Generated Addresses are used 
to assure that the sender of a Neighbor or 
Router Advertisement..." --> 
"Cryptographically Generated Addresses are used 
to assure that the sender of a Neighbor 
Discovery message..." 
(don't forget solicitations)

Section 5.1, Key Information: 
"the former...the latter" --> 
"the CGA option...the Signature option" 
(reader cannot be sure whether the words 
"former" and "latter" are a reference to the 
order of the options in the text or in the 
packet and may feel confused)

Section 5.1, Padding: 
"has ends" --> "has ended"

Section 5.1.2, last paragraph: 
"Note that a receiver WHICH" --> 
"Note that a receiver that"

Section 5.1.2: 
"The inputs for the algorithm are the contents 
of the Collision Cnt, Modifier, and the Key 
Information fields, the claimed address in the 
packet (as discussed in the previous section), 
and the minimum acceptable Sec value." --> 
"The inputs to the algorithm are the claimed 
address, as defined in the previous section, and 
the concatenation from left to right of the 
following data: the contents of the 8-octet 
Modifier field, the 8-octet subnet-prefix part 
of the claimed address, the content of the 1-
octet Collision Cnt field, and contents of the 
variable-length Key Information Field." (to be 
consistent with [12])

Section 5.1.3, minSec: 
Move the reference "(see Section 2 in [12])" to 
the end of the same paragraph. It is less 
confusing there because [12] does not say 
anything about a minimum acceptable value.

Section 5.2, first paragraph: 
"Both trust anchor authentication and CGAs can 
be used  The format..." --> "Both trust anchor 
authentication and CGAs can be used as the trust 
root. The format..."

Section 5.2 and elsewhere: 
"SHA1" --> "SHA-1" (the FIPS standard uses a 
hyphen in the algorithm name)

Section 5.2, Digital Signature: 
"contains a signature" --> 
"contains a PCKS#1 signature";
"The 128-bit CGA Type Tag [12]" --> 
"The 128-bit CGA Message Type tag" (note 
also that "tag" should not be capitalized);
"...7c08 (generated randomly)." --> "...7c08. 
(The tag value has been generated randomly by 
the editor of this specification.)";
"The signature is constructed using the RSA 
algorithm and MUST be encoded as private key 
encryption in PKCS#1 format [13]. The signature 
value is computed with..." --> 
"The signature is computed with..." 
(it is unnecessary to try to explain how the 
signature is algorithm works, signing is NOT 
encryption with private key, and it is better to 
simply reference the standard); 
"Pad Length Field" --> "Pad Length field" 
(remove capitalization)

Section 5.2.2:
"not exceed the length of the Signature option." 
--> "not exceed the length of the Signature 
option minus the Padding."

Section 5.2.4: 
"a few dozen ONES per second" --> 
"a few dozen per second" 
"precomputed as discussed below" --> 
"precomputed as explained below"

Section 7.1: 
"start the process from Step 4." --> 
"start the process from Step 4 of the generation 
algorithm."  

Section 8 
"This is recovery mechanism" --> 
"This is a recovery mechanism"
"Received secured messages cause an update" --> 
"Received secured messages MUST cause an update" 

---------------

Jari Arkko: Agreed. Edited. Thanks.

---------------