| 1/base.txt | 2/issue37.txt | |
|---|---|---|
| Skipping to change at page 3, line 4: | ||
| 7.1.1 Sending Secure Neighbor Solicitations . . . .37 | 7.1.1 Sending Secure Neighbor Solicitations . . . .37 | |
| 7.1.2 Receiving Secure Neighbor Solicitations . . .37 | 7.1.2 Receiving Secure Neighbor Solicitations . . .37 | |
| 7.2 Neighbor Advertisement Messages . . . . . . . . . . 37 | 7.2 Neighbor Advertisement Messages . . . . . . . . . . 37 | |
| 7.2.1 Sending Secure Neighbor Advertisements . . . .37 | 7.2.1 Sending Secure Neighbor Advertisements . . . .37 | |
| 7.2.2 Receiving Secure Neighbor Advertisements . . .38 | 7.2.2 Receiving Secure Neighbor Advertisements . . .38 | |
| 7.3 Other Requirements . . . . . . . . . . . . . . . . . 38 | 7.3 Other Requirements . . . . . . . . . . . . . . . . . 38 | |
| 8. Securing Router Discovery with SEND . . . . . . . . . . . 40 | 8. Securing Router Discovery with SEND . . . . . . . . . . . 40 | |
| 8.1 Router Solicitation Messages . . . . . . . . . . . . 40 | 8.1 Router Solicitation Messages . . . . . . . . . . . . 40 | |
| 8.1.1 Sending Secure Router Solicitations . . . . .40 | 8.1.1 Sending Secure Router Solicitations . . . . .40 | |
| 8.1.2 Receiving Secure Router Solicitations . . . .40 | 8.1.2 Receiving Secure Router Solicitations . . . .40 | |
| 8.2 Router Advertisement Messages . . . . . . . . . . . 41 | 8.2 Router Advertisement Messages . . . . . . . . . . . 40 | |
| 8.2.1 Sending Secure Router Advertisements . . . . .41 | 8.2.1 Sending Secure Router Advertisements . . . . .41 | |
| 8.2.2 Receiving Secure Router Advertisements . . . .41 | 8.2.2 Receiving Secure Router Advertisements . . . .41 | |
| 8.3 Redirect Messages . . . . . . . . . . . . . . . . . 41 | 8.3 Redirect Messages . . . . . . . . . . . . . . . . . 41 | |
| 8.3.1 Sending Redirects . . . . . . . . . . . . . .41 | 8.3.1 Sending Redirects . . . . . . . . . . . . . .41 | |
| 8.3.2 Receiving Redirects . . . . . . . . . . . . .42 | 8.3.2 Receiving Redirects . . . . . . . . . . . . .42 | |
| 8.4 Other Requirements . . . . . . . . . . . . . . . . . 42 | 8.4 Other Requirements . . . . . . . . . . . . . . . . . 42 | |
| 9. Co-Existence of SEND and non-SEND nodes . . . . . . . . . 43 | 9. Co-Existence of SEND and non-SEND nodes . . . . . . . . . 43 | |
| 10. Performance Considerations . . . . . . . . . . . . . . . . 45 | 10. Performance Considerations . . . . . . . . . . . . . . . . 45 | |
| 11. Security Considerations . . . . . . . . . . . . . . . . . 46 | 11. Security Considerations . . . . . . . . . . . . . . . . . 46 | |
| 11.1 Threats to the Local Link Not Covered by SEND . . . 46 | 11.1 Threats to the Local Link Not Covered by SEND . . . 46 | |
| Skipping to change at page 40, line 47: | ||
| Router Solicitation messages received with another type of source | Router Solicitation messages received with another type of source | |
| address but without the Nonce, Timestamp, or Signature options | address but without the Nonce, Timestamp, or Signature options | |
| MUST be silently discarded. | MUST be silently discarded. | |
| The Signature option MUST be constructed with the configured | The Signature option MUST be constructed with the configured | |
| authorization method(s), the used key being within the configured | authorization method(s), the used key being within the configured | |
| minimum (and maximum) allowable key size, and if applicable, using | minimum (and maximum) allowable key size, and if applicable, using | |
| an acceptable trust anchor and/or minSec value. | an acceptable trust anchor and/or minSec value. | |
| The configured authorization methods MUST include the trust anchor | ||
| authorization method, and MAY be additionally configured to | ||
| require CGA authorization. | ||
| 8.2 Router Advertisement Messages | 8.2 Router Advertisement Messages | |
| All Router Advertisement messages are protected with SEND. | All Router Advertisement messages are protected with SEND. | |
| 8.2.1 Sending Secure Router Advertisements | 8.2.1 Sending Secure Router Advertisements | |
| Secure Router Advertisement messages are sent as described in RFC | Secure Router Advertisement messages are sent as described in RFC | |
| 2461, with the additional requirements as listed in the following: | 2461, with the additional requirements as listed in the following: | |
| All Router Advertisement messages sent MUST contain a Timestamp | All Router Advertisement messages sent MUST contain a Timestamp |