1 / 8

Flooding Scope PDUs draft-ietf-isis-fs-lsp-01.txt

Flooding Scope PDUs draft-ietf-isis-fs-lsp-01.txt. Les Ginsberg ( ginsberg@cisco.com ) Stefano Previdi (sprevidi@cisco.com) Yi Yang (yiya @cisco.com ). V1 Changes. Only covering changes since V00 - more details at: http :// tools.ietf.org/agenda/86/slides/slides-86-isis-0.pdf

zenda
Download Presentation

Flooding Scope PDUs draft-ietf-isis-fs-lsp-01.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. Flooding Scope PDUsdraft-ietf-isis-fs-lsp-01.txt Les Ginsberg (ginsberg@cisco.com) Stefano Previdi (sprevidi@cisco.com) Yi Yang (yiya@cisco.com) 88th IETF, Vancouver, November 2013

  2. V1 Changes Only covering changes since V00 - more details at: http://tools.ietf.org/agenda/86/slides/slides-86-isis-0.pdf 16 bit TLV support introduced 88th IETF, Vancouver, November 2013

  3. Overview Introduce a new LSP with flooding scope encoded in the LSP header (also new CSNP/PSNP) Minimize the use of limited PDU type space Define new flooding scopes LSPs for each scope are kept in a scope specific LSDB Not backwards compatible 88th IETF, Vancouver, November 2013

  4. Standard TLV Limitations Limited to 255 octets/TLV Increasing sub-TLV use means a single object (e.g. a link) could require more than 255 octets to describe it This requires repetition of base object identifier in multiple TLVs Receivers must treat the multiple TLVs as additive. 88th IETF, Vancouver, November 2013

  5. Extended TLVs (and sub-TLVs) Extended-TLV Format # octets +---------------------------+ | Type | 2 +---------------------------+ | Length | 2 +---------------------------+ | Data | 1 - 65535 +---------------------------+ Type and Length encoded in network byte order Maximum Length limited by LSP-MTU No change to LSP-MTU support Not an excuse to bloat TLV Types Not backwards compatible 88th IETF, Vancouver, November 2013

  6. Extended TLVs Rules Extended TLVs and extended sub-TLVs are permitted only in Flooding Scoped PDUs which have a flooding scope designated for their use Extended TLVs and extended sub-TLVs MUST be used together Standard TLV code points/formats supported • The eight bit type is encoded as an unsigned 16 bit integer • The eight bit length field is replaced by the 16 bit length field • The length MAY take on values greater than 255 88th IETF, Vancouver, November 2013

  7. Extended TLV and Flooding Scope X| Scope (1 – 127) “X” is Priority (LSP) Reserved(CSNP) Unsupported(PSNP) Scopes 1 – 63 use Standard TLVs Scope (64 – 127) use Extended TLVs Mixing of Standard/Extended TLVs forbidden 88th IETF, Vancouver, November 2013

  8. Questions? 88th IETF, Vancouver, November 2013

More Related