| 1/base.txt | 2/issue36.txt | |
|---|---|---|
| Skipping to change at page 13, line 8: | ||
| CGA, Nonce, Timestamp, Signature. | CGA, Nonce, Timestamp, Signature. | |
| 5.2 CGA Option | 5.2 CGA Option | |
| The CGA option allows the verification of the sender's CGA. The | The CGA option allows the verification of the sender's CGA. The | |
| format of the CGA option is described as follows. | format of the CGA option is described as follows. | |
| 0 1 2 3 | 0 1 2 3 | |
| 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 | 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |
| | Type | Length | Modifier | | | Type | Length | Collision Cnt | Reserved | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |
| | Collision Cnt | Reserved | | | | | |
| | Modifier | | ||
| | | | ||
| | | | ||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |
| | | | | | | |
| . . | . . | |
| . Key Information . | . Key Information . | |
| . . | . . | |
| | | | | | | |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |
| | | | | | | |
| . . | . . | |
| . Padding . | . Padding . | |
| Skipping to change at page 13, line 35: | ||
| The meaning of the fields is described as follows. | The meaning of the fields is described as follows. | |
| Type | Type | |
| TBD <To be assigned by IANA> for CGA. | TBD <To be assigned by IANA> for CGA. | |
| Length | Length | |
| The length of the option, in units of 8 octets. | The length of the option, in units of 8 octets. | |
| Modifier | ||
| A random number used in CGA generation. Its semantics are defined | ||
| in [12]. | ||
| Collision Cnt | Collision Cnt | |
| An 8-bit collision count, which can get values 0, 1 and 2. Its | An 8-bit collision count, which can get values 0, 1 and 2. Its | |
| semantics are defined in [12]. | semantics are defined in [12]. | |
| Reserved | Reserved | |
| A 24-bit field reserved for future use. The value MUST be | An 8-bit field reserved for future use. The value MUST be | |
| initialized to zero by the sender, and MUST be ignored by the | initialized to zero by the sender, and MUST be ignored by the | |
| receiver. | receiver. | |
| Modifier | ||
| A random 128-bit number used in CGA generation. Its semantics are | ||
| defined in [12]. | ||
| Key Information | Key Information | |
| A variable length field containing the public key of the sender, | A variable length field containing the public key of the sender, | |
| represented as an ASN.1 type SubjectPublicKeyInfo [10], encoded as | represented as an ASN.1 type SubjectPublicKeyInfo [10], encoded as | |
| described in Section 4 of [12]. | described in Section 4 of [12]. | |
| This specification requires that if both the CGA option and the | This specification requires that if both the CGA option and the | |
| Signature option are present, then the publicKey field in the | Signature option are present, then the publicKey field in the | |
| former option MUST be the public key referred by the Key Hash | former option MUST be the public key referred by the Key Hash | |
| field in the latter option. Packets received with two different | field in the latter option. Packets received with two different | |
| Skipping to change at page 15, line 27: | ||
| The address MUST be the source address of the message. | The address MUST be the source address of the message. | |
| 5.2.2 Processing Rules for Receivers | 5.2.2 Processing Rules for Receivers | |
| A message containing a CGA option MUST be checked as follows: | A message containing a CGA option MUST be checked as follows: | |
| If the interface has been configued to use CGA, it is REQUIRED | If the interface has been configued to use CGA, it is REQUIRED | |
| that the receiving node verifies the source address of the packet | that the receiving node verifies the source address of the packet | |
| using the algorithm described in Section 5 of [12]. The inputs | using the algorithm described in Section 5 of [12]. The inputs | |
| for the algorithm are the contents of the Modifier, Collision Cnt, | for the algorithm are the contents of the Collision Cnt, Modifier, | |
| and the Key Information fields, the claimed address in the packet | and the Key Information fields, the claimed address in the packet | |
| (as discussed in the previous section), and the minimum acceptable | (as discussed in the previous section), and the minimum acceptable | |
| Sec value. If the CGA verification is successful, the recipient | Sec value. If the CGA verification is successful, the recipient | |
| proceeds with the cryptographically more time consuming check of | proceeds with the cryptographically more time consuming check of | |
| the signature. | the signature. | |
| Note that a receiver which does not support CGA or has not specified | Note that a receiver which does not support CGA or has not specified | |
| its use for a given interface can still verify packets using trust | its use for a given interface can still verify packets using trust | |
| anchors, even if CGA had been used on a packet. In such a case, the | anchors, even if CGA had been used on a packet. In such a case, the | |
| CGA property of the address is simply left unverified. | CGA property of the address is simply left unverified. |