| Previous |
|
|
|
|
||
|
2.0.- Some other considerations |
||
| Element of procedure | ||
| Routers shall originate TELSAs whenever the LSA content changes, and whenever otherwise required by OSPF (a refresh, for example). Changes have not to be flooded immediately; thresholds may be set that trigger immediate flooding and initiate flooding of changes after a short time interval. In any case, TELSA should be rate-limited to at most one every MinLSInterval. | ||
| Upon receipt of a changed TELSA, the router should update its TED. No SPF or other calculations are necessary. | ||
| Compatibility | ||
| There should be no interoperability issues with routers not implementing these extensions, since Opaque LSAs not being understood are silently ignored. | ||
| Security | ||
| Contents specify in this document are Opaque LSAs in OSPFv2. Then, it is suggested that any mechanisms used for securing the transmission of normal OSPF LSAs be applied equally to all Opaque LSAs, including TELSAs specified here. | ||
|
IANA |
||
| There are guidelines for the assignment of TELSA types. Please, refer to the original RFC for more information. | ||
|
|
||