Looking at the minutes, I think there wasn't enough time left for the draft-hao-bess-inter-nvo3-vpn that a discussion could take place.
I will explain the answer to the question that was asked. In option C the ASBR-W will have to establish EBGP will each NVE in the DC. NVE in some cases could be a ToR and in most cases will be a software gateway in the hypervisor. In any case the number of NVEs can run in thousands. This would mean the other service provider will need to establish EBGP sessions possibly in thousands which is not practical. In this scenario Option-B will provide the architecture to address the scaling issue. I would like to request additional comments and call for adoption. Regards, Osama From: BESS [mailto:[email protected]] On Behalf Of Susan Hares Sent: Wednesday, April 8, 2015 2:29 PM To: [email protected] Subject: [bess] Minutes for IETF 92 BESS meeting The BESS minutes for IETF 92 session are attached (html, pdf). Should you want to make changes to the minutes, you may edit the etherpad location. The minutes have been upload to the etherpad for BESS 92 which is at: http://etherpad.tools.ietf.org:9000/p/notes-ietf-92-bess?useMonospaceFont=true Sue Hares
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
