Download
status report n.
Skip this Video
Loading SlideShow in 5 Seconds..
Status Report PowerPoint Presentation
Download Presentation
Status Report

Status Report

116 Views Download Presentation
Download Presentation

Status Report

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Status Report • Drafts are “mostly finished” • Current intention is to last call before IETF71 • Drafts are 95% stable, could really use more review • Still a number of loose ends • Clerical loose ends: • IANA Considerations • Security Considerations IETF 69, L3VPN WG

  2. Technical Loose Ends • Inter-provider C-Bidir Support for non-outsourced RPA • Distributing Designated Forwarder label (upstream assigned) • Identify the Designated Forwarder for C-Bidir when P2MP LSPs are used for MI-PMSI • Distributing Sender PE label (upstream assigned) • Identify the sender PE when MP2MP LSP is used • Carrier’s carrier (maybe this is clerical) • Clarifications on criteria for triggering S-PMSI A-D routes • Control or data driven • Some inter-AS issues still unresolved: • PIM extensions, if any, for unsegmented inter-AS trees in “option B” environment • A few details on segmented inter-AS trees to be clarified IETF 69, L3VPN WG

  3. draft-ietf-l3vpn-2547bis-mcast-bgpChanges from the previous version (1) • Clarification to the procedures for forcing all PEs to switch from RPT to SPT when at least one PE switches • Recommend a configurable timer to trigger RPT to SPT switchover to minimize traffic loss during the switchover • Timer is triggered on receipt of a SA A-D route generated by the PE that receives the first source tree c-multicast route • PEs send a source tree c-multicast route for (C-S, C-G) only if they have (C-S, C-G) state • PEs that have only (C-*, C-G) state receive data on the P-tunnel used (for C-S, C-G) by the originator of the best SA-AD route • Without originating a source tree c-multicast route for (C-S, C-G) IETF 69, L3VPN WG

  4. draft-ietf-l3vpn-2547bis-mcast-bgpChanges from the previous version (2) • Editorial clarifications to the procedures for stitching intra-AS segments (in the source AS) and inter-AS segment of an inter-AS segmented tree • Editorial clarification to the procedures for stitching inter-AS segment to intra-AS segment (in a non-source AS) for inter-AS segmented trees IETF 69, L3VPN WG

  5. draft-ietf-l3vpn-2547bis-mcast-bgpChanges from the previous version (3) • Specify that the default policy for aggregation of intra-AS AD routes into an inter-AS AD route: • ASBR that originates a given inter-AS AD route could aggregate only the intra-AS AD routes that carry exactly the same set of RTs (note that this set may have just one RT) • The default can be modified by configuration IETF 69, L3VPN WG