Subject: [bess] FW: New Version Notification for draft-snr-bess-pbb-evpn-isid-cmacflush-06.txt

From: "Rabadan, Jorge (Nokia - US/Mountain View)" <[email-masked]>
Date: Fri, 26 Jul 2019 12:53:30 +0000

We just updated this draft with the security considerations.
As discussed by the WG chairs this week, it's ready for WG adoption call.

Comments are welcome.

Thanks.
Jorge 

    A new version of I-D, draft-snr-bess-pbb-evpn-isid-cmacflush-06.txt
    has been successfully submitted by Jorge Rabadan and posted to the
    IETF repository.
    
    Name:		draft-snr-bess-pbb-evpn-isid-cmacflush
    Revision:	06
    Title:		PBB-EVPN ISID-based CMAC-Flush
    Document date:	2019-07-26
    Group:		Individual Submission
    Pages:		10
    URL:            https://www.ietf.org/internet-drafts/draft-snr-bess-pbb-evpn-isid-cmacflush-06.txt
    Status:         https://datatracker.ietf.org/doc/draft-snr-bess-pbb-evpn-isid-cmacflush/
    Htmlized:       https://tools.ietf.org/html/draft-snr-bess-pbb-evpn-isid-cmacflush-06
    Htmlized:       https://datatracker.ietf.org/doc/html/draft-snr-bess-pbb-evpn-isid-cmacflush
    Diff:           https://www.ietf.org/rfcdiff?url2=draft-snr-bess-pbb-evpn-isid-cmacflush-06
    
    Abstract:
       Provider Backbone Bridging (PBB) can be combined with Ethernet VPN
       (EVPN) to deploy ELAN services in very large MPLS networks (PBB-
       EVPN). Single-Active Multi-homing and per-ISID Load-Balancing can be
       provided to access devices and aggregation networks. In order to
       speed up the network convergence in case of failures on Single-Active
       Multi-Homed Ethernet Segments, PBB-EVPN defines a CMAC-Flush
       mechanism that works for different Ethernet Segment BMAC address
       allocation models. This document complements those CMAC-Flush
       procedures for cases in which no PBB-EVPN Ethernet Segments are
       defined (ESI 0) and an ISID-based CMAC-Flush granularity is desired.

    
    Please note that it may take a couple of minutes from the time of submission
    until the htmlized version and diff are available at tools.ietf.org.
    
    The IETF Secretariat