Hi Thomas, Here are some comments.
Section 5.3 describes gateways. IMO: it misses an important use case. A Gateway, say overlay gateway, may be used to interconnect two or more overlay VNs. In this case, the traffic traversing between two overlay VNs must go through the gateway where the policy can be enforced. Furthermore, it is possible to implement centralized or distributed overlay gateway. The latter has overlay gateway function implemented on NVEs. Thus, it requests the cross-VN policies to be distributed to NVEs. Current section seems very focus on overlay VN interconnect a non-overlay network, which centralized gateway architecture is practical. But in overlay networks, both centralized or distributed are possible and depend on the applications. The draft barely touches Multicast/broadcast supports in describing NVE state in section 4.3. But it does not describe in section 7 at all. How to obtain the mapping for multicast traffic is much more complex. Simply statement " Since the NVA has current knowledge of which NVE each Tenant System is connected to, the NVA can proactively push updates out to the NVEs when they occur." is not enough for multicast transport. It seems valuable to describe that NVA may send NVE a default route/gateway instead of tenant/location mapping and NVA can perform the route distribution control. Regards, Lucy -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Thomas Narten Sent: Friday, October 11, 2013 8:04 AM To: [email protected] Subject: [nvo3] NVO3 Architecture document draft-narten-nvo3-arch-00.txt is intended to become a WG document, but to date we've received limited feedback with specific actions. If folk have changes/additions/clarifications they'd like to see, or disagree with particular aspects, please speak up. For example, Section's 6-8 talk about NVAs and a federated model. These concepts have been discussed several times over the last year and appear to have general support. That said, some of the sections have "notes" specifically asking for further discussion/feedback. Thanks! Thomas _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
