1 / 11

Support of Address-family in OSPFv3 draft-mirtorabi-ospfv3-af-00.txt

Support of Address-family in OSPFv3 draft-mirtorabi-ospfv3-af-00.txt. Agenda. What do we have today in OSPFv3 What does this draft propose What does this draft introduce Interaction with non-AF capable router Conclusion. What do we have today in OSPFv3.

infinity
Download Presentation

Support of Address-family in OSPFv3 draft-mirtorabi-ospfv3-af-00.txt

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Support of Address-familyin OSPFv3draft-mirtorabi-ospfv3-af-00.txt

  2. Agenda • What do we have today in OSPFv3 • What does this draft propose • What does this draft introduce • Interaction with non-AF capable router • Conclusion

  3. What do we have today in OSPFv3 • OSPFv3 is defined with a network protocol independent core • Router and Network LSAs carry only topology information • Only IPv6 address family is currently defined • V6-bit is defined in Options field, which can be used to include or exclude a node in IPv6 address-family

  4. What does this draft propose • Enhance the per node support of address-family to per link support • This will allow a link to be included or excluded explicitly in a given address-family • This will be used during SPF in order to have incongruent address-family topologies

  5. What does this draft introduce (I) • A New bit (AF) is defined in the Options field in order to convey the support of address-family as specified in this draft • Routers supporting this draft MUST set this bit

  6. What does this draft introduce (II) • An unused field in Router-LSA is used to define per link AddressFamilies field (shown as AF below)

  7. What does this draft introduce (contd.) AddressFamiles field is defined as: • Each bit corresponds to an address-family • V6-AF bit MUST be set when a link participates in IPv6 topology otherwise it MUST be cleared • When a link participate in more than one AF, all of the corresponding bits will be set

  8. What does this draft introduce (III) • A new LSA called AF-Functionality-LSA is defined to carry [Nt|W|V|E|B] bits for each AF, it has area flooding scope and the U bit is set. The type is 0xA00A • This is NOT needed for IPv6 AF (which uses these bits from the router-lsa header)

  9. Interaction with non-AF capable router • Current routers participating in IPv6 do not set the V6-AF bit • All routers need to understand the AddressFamilies field, before enabling AF capability in an Area. • A new AFCapability parameter is introduced in the area data structure, which could be set to Enabled or Disabled • The Default value (when area data structure is created) is Disabled

  10. Interaction with non-AF capable router (contd.) • Router supporting this draft MUST always set the AF bit in the Options field and V6-AF bit on the links that participate in IPv6 topology • When AFCapability is set to Enabled the router will further do 1) while doing SPF for an address-family only links that are part of the AF will be considered 2) Accept the Hello only if the AF bit is set in the Options field of Hello packet

  11. Conclusion • This draft enhances OSPFv3 address-family support from per node to per link • It enables incongruent topologies for different address-families

More Related