Hi Linda, See my responses inline.
- Larry From: Linda Dunbar <[email protected]<mailto:[email protected]>> Date: Thursday, October 24, 2013 11:19 AM To: Larry Kreeger <[email protected]<mailto:[email protected]>>, Linda Dunbar <[email protected]<mailto:[email protected]>>, Thomas Narten <[email protected]<mailto:[email protected]>>, David Black <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: RE: Suggested additional requirement to be added to "draft-ietf-nvo3-nve-nva-cp-req-00" Larry, Please see my comments inserted below: LK> I'm pretty sure this is covered in the architecture document, but we could do some repeating here. Regarding "each holding the mapping information for a subset of VNs", part, this gets into federation of NVAs. I think we can leave that part in the architecture document since it will probably open more questions, than provide answers. Also, it is not relevant to the NVA to NVE protocol since a single NVE only uses a single NVA. [Linda] “a single NVE only uses a single NVA”? What if the NVE is disconnected from its “only” NVA? Or its only “NVA” has failure or is going through software restart? LK> As described in the architecture document, the NVA is "logically centralized". It is expected to support fault tolerance, and be made up of more than a single entity for this reason. There is some more discussion of this in sections 6.2 and 6.3 of draft-narten-nvo3-arch-01 (recently updated). For the distributed case, each NVA only has mapping for a subset of VNs. It is very possible that the VNs being participated by one NVE are carried by multiple NVAs LK> Even if an NVA is distributed, it is still logically a single NVA. Section 6.3 has some discussion on how NVEs might use multiple IP addresses to access a single logical NVA. It is currently left very open for discussion. Linda
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
