Hello,
I have one comment which I have sent in the control plane draft
discussion. But it may have an impact on the architecture draft as well. In
section 7.1, there are two alternatives described. However it shall be possible
for an implementation to use NVE-NVE protocol for inner-outer mapping updating.
Using NVE-NVE protocol may not be the best solution. But as an architecture
document, it may be good to list all the possibilities. And it may be better to
have some analysis text on the pros and cons of each alternatives. I'm not sure
if this is the right place to do this comparison. If yes, I do have some
security considerations text of each alternatives in the security requirements
draft [http://tools.ietf.org/html/draft-zu-nov3-security-requirements-01] .
hope it can give some help for this discussion.
Have a nice day
Zu Qiang
>-----Original Message-----
>From: [email protected] [mailto:[email protected]] On Behalf Of
>Thomas Narten
>Sent: Friday, October 11, 2013 9: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
