1 / 23

Simplified Extension of LSP Space for IS-IS

draft-ietf-isis-wg-extlsp-01.txt Danny McPherson (Ed.) Les Ginsberg Stefano Previdi Mike Shand. Simplified Extension of LSP Space for IS-IS. draft-ietf-isis-wg-extlsp-0 2 .txt Danny McPherson (Ed.) Les Ginsberg Stefano Previdi Mike Shand. Simplified Extension of LSP Space for IS-IS.

nell-morse
Download Presentation

Simplified Extension of LSP Space for IS-IS

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. draft-ietf-isis-wg-extlsp-01.txt Danny McPherson (Ed.) Les Ginsberg Stefano Previdi Mike Shand Simplified Extension of LSP Space for IS-IS

  2. draft-ietf-isis-wg-extlsp-02.txt Danny McPherson (Ed.) Les Ginsberg Stefano Previdi Mike Shand Simplified Extension of LSP Space for IS-IS

  3. Changes since previous version • Resubmitted for standards track • TLV 22/TLV23 metric conflict

  4. TLV22/TLV23 Conflict “In cases where information about the same neighbor/link appears in both TLV 22 and TLV 23 (or TLV 222 and TLV 223 for the same MTID) then the information in TLV 22 (or TLV 222) MUST be used and the information in TLV 23 (or TLV 223) MUST be ignored.”

  5. Questions?

  6. draft-ietf-isis-genapp-00.txt Les Ginsberg Stefano Previdi Mike Shand Advertising Generic Information in IS-IS

  7. Changes since previous version • Now a WG document • Standards track • Applicability statement

  8. Applicability Statement “The GENINFO TLV supports the advertisement of application specific information in IS-IS LSPs which is not directly related to the operation of the IS-IS protocol. Information which is not directly used by the IS-IS Decision process falls into this category. The Decision Process is defined by [ISO10589] and extended by [RFC1195] and [RFC3906].”

  9. Applicability Statement • May be interpreted to cover existing information • Migration to use of GENAPP is seen as desirable • WG is the authority

  10. Questions?

  11. draft-chopps-isis-bfd-tlv-01.txt Chris Hopps Les Ginsberg IS-IS and BFD

  12. Problem Statement • BFD used to detect IPv4/IPv6 forwarding failures • IS-IS PDUs do not always share fate with IP packets • Adjacencies may be established even when IP forwarding problems are detectable

  13. B A IP IS-IS • IS-IS PDUs exchanged • Adjacency UP • BFD session requested (neighbor IP address) • If BFD session doesn’t come up could be: • IP forwarding failure • No BFD Config/Support

  14. Advertise support for BFD in IIHs Type 139 (proposed) Length # of octets in the value field (1 to 255) Value: No. of octets +-----------------------------+ | NLPID | 1 +-----------------------------+ : : +-----------------------------+ | NLPID | 1 +-----------------------------+

  15. When BFD is supported by both neighbors… • Hold adjacency in Init state until BFD session is UP • Bring adjacency down when BFD session goes down • P2P – 3 way state is DOWN when BFD is down • LAN – omit neighbor MAC address when BFD is down

  16. Determining when new rules apply For each topology/NLPID shared by the neighbors, if BFD support is configured for both neighbors, BFD session must be UP to use that topology At least one topology must be “useable” in order for adjacency to come up

  17. B A IP IS-IS MTID: 0 (IPv4), 2 (IPv6) BFD: IPv4, IPv6 MTID: 0 (IPv4) BFD: IPv4 IPv4 BFD Session MUST be UP before adjacency comes up.

  18. B A IP IS-IS MTID: 0 (IPv4), 2 (IPv6) BFD: IPv4, IPv6 MTID: 0 (IPv4), 2 (IPv6) BFD: IPv4 Normal adjacency establishment rules. IPv4 BFD Session MUST be UP for MTID #0 to be useable.

  19. Transition – enable BFD Detected by addition of NLPID in BFD-TLV For existing adjacencies, do not update hold time on receipt of IIH until BFD session is UP

  20. B A IP IS-IS MTID: 0 (IPv4) BFD: IPv4 MTID: 0 (IPv4) BFD: IPv4 • Adjacency is Up • B configures IPv4 BFD support • IIH from B includes BFD-TLV for IPv4 – hold time not updated • BFD session comes up • Normal hold time update resumes

  21. Transition – disable BFD Detected by transition of BFD session state to admin down For existing adjacencies, do not update hold time on receipt of IIH until corresponding NLPID is no longer advertised in BFD-TLV

  22. B A IP IS-IS MTID: 0 (IPv4) BFD: IPv4 MTID: 0 (IPv4) BFD: IPv4 • Adjacency is Up/BFD session Up • B deconfigures IPv4 BFD support • IPv4 BFD session admin down on A • IIH from B has no BFD-TLV for IPv4 • Normal hold time update resumes

  23. Questions? WG Document?

More Related