IETF 101 RIFT Meeting Notes (by Olufemi Komolafe)

+ WG Status Update and charter discussion (Jeff Tantsura)

+ Motivation, Additional Requirements and Use Cases in User Access Networks (Yan Filyurin)
Tony Przygienda: While network slicing merits discussion it is pointless to attempt to redo RFC 2547 VPNs.
Yan Filyurin: Agree.  Not proposing to do so.

Tony Przygienda: How does default routing break tunnelling?
Yan Filyurin: Building the tunnel is easy, knowing how to forward into the tunnel is the challenge.  Aggregation means it can be difficult to know exactly what traffic should be forwarded into the tunnel.
Tony Przygienda: But tunnel destination endpoint more specific than default?
Agree to continue discussion offline.

Tony Przygienda: Is there really a problem handling mobile workloads?  Currently, a TIE will be flooded from each of the old and new locations. This should suffice.
Yan Filyurin: What about the workload moving to a new branch of the tree?
Tony Przygienda: Existing mechanisms handle this fine.
Agree to continue discussion offline.

+ draft-przygienda-rift (Tony Przygienda)
Tony Przygienda: Who has read the draft?  Who has read draft more than once?
??????: Perhaps should be asking who has *understood* the draft?
Tony Przygienda: Will present survey of RIFT, laying out landscape and emphasising areas needing attention and further work.    

+ draft-zhang-rift-yang (Sandy Zhang)
No questions or discussion.

+ draft-zzhang-bier-rift (Sandy Zhang)
Jeffrey Zhang: This work is not currently in charter and so the point is to show how RIFT can easy work with other technologies, such as BIER.

+Wrap up (Jeff Tantsura)
Jeff Tantsura: Thanks for attending.  Goal of today’s session was to give some background and introduction to RIFT.  Next meeting will focus more on the appeal and potential of RIFT.