Attached is a doc that builds on the framework Guy provided last week. I think this reflects our discussion so far. I note that the Path part is one which I think needs lots more discussion. I can work on that next week -- maybe others can as well? I think other issues to be clarified for the architecture part include the role of topology and path finding in NSI, and perhaps some limitation on what sort of services can be included in NSI. What issues do others think need to be addressed? John
Hi, I've given some comments into the doc. Most of them will are for discussion, rather than just for accept/decline. I apology but I can't join the call today. Best regards Radek ________________________________________________________________________ Radoslaw Krzywania Network Research and Development Poznan Supercomputing and radek.krzywania@man.poznan.pl Networking Center +48 61 850 25 26 http://www.man.poznan.pl ________________________________________________________________________
-----Original Message----- From: nsi-wg-bounces@ogf.org [mailto:nsi-wg-bounces@ogf.org] On Behalf Of John Vollbrecht Sent: Tuesday, September 07, 2010 11:49 PM To: NSI WG Subject: [Nsi-wg] NSI CS Message (ConnReq)
Attached is a doc that builds on the framework Guy provided last week. I think this reflects our discussion so far. I note that the Path part is one which I think needs lots more discussion. I can work on that next week -- maybe others can as well?
I think other issues to be clarified for the architecture part include the role of topology and path finding in NSI, and perhaps some limitation on what sort of services can be included in NSI. What issues do others think need to be addressed?
John
participants (2)
-
John Vollbrecht -
Radek Krzywania