> -----邮件原件----- > 发件人: Robert Raszuk [mailto:[email protected]] > 发送时间: 2012年5月9日 19:01 > 收件人: Ivan Pepelnjak > 抄送: Keshava A K; [email protected]; Xuxiaohu; [email protected]; [email protected] > 主题: Re: [nvo3] Facilitating the load-balancing of L2VPN/L3VPN traffic over IP > PSN using MPLS-in-UDP encapsulation// fwd: New Version Notification for > draft-xu-mpls-in-udp-00.txt > > Hi Ivan, > > > True, but then you need a mechanism to discover all the available > > endpoints, whereas with single VTEP per host you can use existing > > mechanisms (either learning from source IP address or next-hop > > distribution with BGP-like protocols). > > True. > > I see few options: > > - Signal different next hops in BGP for the application which runs across > > - Treat next hop in BGP as prefix indicator not as host route. In > particular next hop resolves in IGP to a prefix which in turn could be > used as set of GRE destination addresses > > - Signal such range explicitly. I think there will be a draft coming up > on just that soon.
Hi all, The draft that Robert mentioned is now available at http://tools.ietf.org/html/draft-xu-idr-tunnel-address-prefix-00. Any comments and suggestions are welcome. BTW, thanks Robert for your pre-announcement of this draft ;) Best regards, Xiaohu
