You have to be specific on where you made those points and changes needs to be applied. As none of the note takes captured, unless provided exact locations you made those comments, they cannot be automagically integrated/merged.
Having said that, couldn’t parse one of the sentences. could you clarify? See below. > On May 26, 2015, at 7:50 AM, Lucy yong <[email protected]> wrote: > > Here are the points I made at the last in the NVO3 interim meeting. > · NVO3 architecture decouples control plane and data plane, but NVE > and NVA functions integrate VN layer and VN transport layer together. NVA > does inner/outer mapping and NVEs perform the lookup and tunnel functions. > This has difference from traditional VPNs technology where control plane and > data plane couples but VN layer and VN transport layer are separated at the > architecture. What does it mean by, CP and DP couples but VN layer and VN transport are separated at the architecture? > · In NVO3, there are tunnel trace and underlay path trace. Tunnel > trace is the tunnel endpoint trace including tunnel stitching case. Underlay > path trace is the path from ingress NVE to egress NVE including each underlay > intermediate hops. The end-to-end path in overlay relates to tunnel trace > only. We need separate two traces clearly. > > Lucy > From: nvo3 [mailto:[email protected]] On Behalf Of Sam Aldrin > Sent: Monday, May 25, 2015 1:49 AM > To: [email protected] > Cc: NVO3 Working Group > Subject: [nvo3] NVo3 May 22 2015 interim meeting minutes uploaded > > Minutes are now uploaded. > They could be found at > <https://www.ietf.org/proceedings/interim/2015/05/22/nvo3/minutes/minutes-interim-2015-nvo3-9 > > <https://www.ietf.org/proceedings/interim/2015/05/22/nvo3/minutes/minutes-interim-2015-nvo3-9>> > > Thanks to Sue and Matt for taking notes. > > Do let me know if there need any changes or corrections. > > cheers > -sam
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
