rfc9032v2.txt | rfc9032.txt | |||
---|---|---|---|---|
skipping to change at line 120 ¶ | skipping to change at line 120 ¶ | |||
There are a limited number of timeslots designated as broadcast slots | There are a limited number of timeslots designated as broadcast slots | |||
by each router in the network. Considering 10 ms slots and a | by each router in the network. Considering 10 ms slots and a | |||
slotframe length of 100, these slots are rare and could result in | slotframe length of 100, these slots are rare and could result in | |||
only 1 slot per second for broadcasts, which needs to be used for the | only 1 slot per second for broadcasts, which needs to be used for the | |||
beacon. Additional broadcasts for Router Advertisements (RA) or | beacon. Additional broadcasts for Router Advertisements (RA) or | |||
Neighbor Discovery (ND) could be even more scarce. | Neighbor Discovery (ND) could be even more scarce. | |||
1.3. Layer 3 Synchronization: IPv6 Router Solicitations and | 1.3. Layer 3 Synchronization: IPv6 Router Solicitations and | |||
Advertisements | Advertisements | |||
At layer 3, [RFC4861] defines a mechanism by which nodes learn about | At Layer 3, [RFC4861] defines a mechanism by which nodes learn about | |||
routers by receiving multicast RAs. If no RA is received within a | routers by receiving multicast RAs. If no RA is received within a | |||
set time, then a Router Solicitation (RS) may be transmitted as a | set time, then a Router Solicitation (RS) may be transmitted as a | |||
multicast, to which an RA will be received, usually unicast. | multicast, to which an RA will be received, usually unicast. | |||
Although [RFC6775] reduces the amount of multicast necessary for | Although [RFC6775] reduces the amount of multicast necessary for | |||
address resolution via Neighbor Solicitation (NS) messages, it still | address resolution via Neighbor Solicitation (NS) messages, it still | |||
requires multicast of either RAs or RSes. This is an expensive | requires multicast of either RAs or RSes. This is an expensive | |||
operation for two reasons: there are few multicast timeslots for | operation for two reasons: there are few multicast timeslots for | |||
unsolicited RAs; and if a pledge node does not receive an RA, and | unsolicited RAs; and if a pledge node does not receive an RA, and | |||
decides to transmit an RS, a broadcast Aloha slot (see Appendix A.5 | decides to transmit an RS, a broadcast Aloha slot (see Appendix A.5 | |||
End of changes. 1 change blocks. | ||||
1 lines changed or deleted | 1 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |