Re: [Bier] Prague Agenda

[Michael Menth <[e-mail]>]

Hi Greg,

my presentation on BIER-FRR is missing. Details are in the attached
email. Can you add that talk, please?

Kind Regards,

Michael

Am 24.03.2019 um 10:33 schrieb Greg Shepherd:
> Here's the latest agenda just published:
> 
> BIER WG Agenda
> 
> IETF 104, Prague
> Monday, 25 March 2019 09:00-12:20
> Karlin 3
> 
> Welcome, Notewell, Agenda bash5minChairs
> draft-ietf-bier-mtud10min
> draft-ietf-bier-mld5minStig Venaas
> draft-dhanaraj-bier-lsr-ethernet-extensions10minSenthil Dhanaraj
> draft-purkayastha-bier-multicast-http-response15minPurkayastha
> ietf-bier-bgp-ls-bier-ext-04
> draft-ietf-bier-bier-yang-04
> draft-chen-pce-bier-0420minRan Chen
> draft-mcbride-bier-ipv6-problem-statement
> ietf104-slides-bier-ipv6-encapsulation10minMike McBride
> draft-xie-bier-6man-encapsulation10minJingrong Xie
> draft-xie-bier-ipv6-mvpn-0010minJingrong Xie
> draft-ietf-bier-te-0110minToerless Eckert
> 
> Anything else?
> 
> -Shep
> (Chairs)
> 
> On Sun, Mar 24, 2019 at 2:17 AM Greg Shepherd <[e-mail]
> <mailto:[e-mail]>> wrote:
> 
>     ..and more updates. I've added two agenda items as I received slides
>     for them (to the wrong email address...) but no actual agenda
>     request. Following instructions is hard. :)
> 
>     I'm going to publish this version. I'll check email later for any
>     updates. Still some slides missing too (you know who you are). We
>     are on deck tomorrow at 0900 so there's not much time left. I won't
>     take slides in the room.
> 
>     BIER WG Agenda
> 
>     IETF 104, Prague
>     Monday, 25 March 2019 09:00-12:20
>     Karlin 3
> 
>     Welcome, Notewell, Agenda bash5minChairs
>     draft-ietf-bier-mtud10min
>     draft-ietf-bier-mld5minStig Venaas
>     draft-dhanaraj-bier-lsr-ethernet-extensions10minSenthil Dhanaraj
>     ietf-bier-bgp-ls-bier-ext-04
>     draft-ietf-bier-bier-yang-04
>     draft-chen-pce-bier-0420minRan Chen
>     ietf104-slides-bier-ipv6-encapsulation
>     draft-mcbride-bier-ipv6-problem-statement10minMike McBride
>     draft-xie-bier-6man-encapsulation10minJingrong Xie
>     draft-xie-bier-ipv6-mvpn-0010minJingrong Xie
>     draft-ietf-bier-te-0110minToerless Eckert
> 
>     -Shep
>     (Chairs)
> 
>     On Sun, Mar 24, 2019 at 1:42 AM Greg Shepherd <[e-mail]
>     <mailto:[e-mail]>> wrote:
> 
>         Already an update:
> 
>         BIER WG Agenda
> 
>         IETF 104, Prague
>         Monday, 25 March 2019 09:00-12:20
>         Karlin 3
> 
>         Welcome, Notewell, Agenda bash5minChairs
>         draft-ietf-bier-mtud10min
>         draft-ietf-bier-mld5minStig Venaas
>         draft-dhanaraj-bier-lsr-ethernet-extensions10minSenthil Dhanaraj
>         ietf-bier-bgp-ls-bier-ext-04
>         draft-ietf-bier-bier-yang-04
>         draft-chen-pce-bier-0420minRan Chen
>         draft-xie-bier-ipv6-mvpn-0010minJingrong Xie
>         draft-ietf-bier-te-0110minToerless Eckert
> 
> 
> 
>         On Sun, Mar 24, 2019 at 1:34 AM Greg Shepherd <[e-mail]
>         <mailto:[e-mail]>> wrote:
> 
>             Unlike meetings past, our agenda for this week is quite
>             light. I did however find an email that slipped my agenda
>             filter, so maybe others failed to follow directions and
>             respond to the request thread directly. So, here is what we
>             have so far. If something is missing please let me know ASAP
>             so we can make correction.
> 
>             BIER WG Agenda
> 
>             IETF 104, Prague
>             Monday, 25 March 2019 09:00-12:20
>             Karlin 3
> 
>             Welcome, Notewell, Agenda bash5minChairs
>             draft-xie-bier-ipv6-mvpn-0010minJingrong Xie
>             draft-ietf-bier-mtud10min
>             draft-ietf-bier-mld5minStig Venaas
>             ietf-bier-bgp-ls-bier-ext-04
>             draft-ietf-bier-bier-yang-04
>             draft-chen-pce-bier-0420minRan Chen
>             draft-ietf-bier-te-0110minToerless Eckert
> 
>             Thanks,
>             Shep
>             (Chairs)
> 
> 
> _______________________________________________
> BIER mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/bier
> 

-- 
Prof. Dr. habil. Michael Menth
University of Tuebingen
Faculty of Science
Department of Computer Science
Chair of Communication Networks
Sand 13, 72076 Tuebingen, Germany
phone: [phone]
fax: [phone]
mailto:[e-mail]
http://kn.inf.uni-tuebingen.de

--- Begin Message ---

Dear WG,

please find attached a new draft for BIER-FRR. We would like to present
it in Prague and are happy to receive feedback.

Kind regards,

Michael

Am 05.03.2019 um 11:22 schrieb [e-mail]:
> 
> A new version of I-D, draft-merling-bier-frr-00.txt
> has been successfully submitted by Daniel Merling and posted to the
> IETF repository.
> 
> Name:		draft-merling-bier-frr
> Revision:	00
> Title:		BIER Fast Reroute
> Document date:	2019-03-05
> Group:		Individual Submission
> Pages:		15
> URL:            https://www.ietf.org/internet-drafts/draft-merling-bier-frr-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-merling-bier-frr/
> Htmlized:       https://tools.ietf.org/html/draft-merling-bier-frr-00
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-merling-bier-frr
> 
> 
> Abstract:
>    BIER is a scalable multicast overlay [RFC8279] that utilizes some
>    routing underlay, e.g., IP, to build up its Bit Index Forwarding
>    Tables (BIFTs).  This document proposes a Fast Reroute Extension for
>    BIER (BIER-FRR).  In case of a link or node failure, the routing
>    underlay may first utilize FRR techniques to restore connectivity and
>    then its forwarding tables converge.  After that, BIER can update its
>    BIFTs, which requires time.  BIER packets may not be delivered until
>    the last procedure has finished.  With BIER-FRR, a BIER Forwarding
>    Router (BFR) can deliver BIER packets again after a link or node
>    failures as soon as the connectivity within the routing underlay is
>    restored and the BFR is informed about a next-hop (NH) that is
>    unreachable on a lower layer.  BIER-FRR provides a mode for link
>    protection and node protection.  For link protection, it tunnels
>    traffic to the next-hop using the underlying routing.  For node
>    protection, it forwards BIER packets to their specific next-hop and
>    next-next-hops using tunnels in the underlying routing after applying
>    a suitable backup bitmask to the bitstring in the BIER header of each
>    packet.  This procedure prevents duplicates.  If topology allows,
>    BIER-FRR achieves full protection against any single component
>    failure.  For link protection, BIER-FRR requires only a minor change
>    to the forwarding logic.  For node protection, BIER-FRR also requires
>    backup entries in the BIFT.
> 
>    This document describes the concept and operating principles of BIER-
>    FRR.  It defines the necessary modifications to the BIER forwarding
>    Procedure and the BIFT, and explains how backup entries are computed.
> 
>                                                                                   
> 
> 
> 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
> 

-- 
Prof. Dr. habil. Michael Menth
University of Tuebingen
Faculty of Science
Department of Computer Science
Chair of Communication Networks
Sand 13, 72076 Tuebingen, Germany
phone: [phone]
fax: [phone]
mailto:[e-mail]
http://kn.inf.uni-tuebingen.de

--- End Message ---