[writing as individual RG member and not as chair] Dear all, Here is a brief review of draft-shin-virtualization-meta-arch-01.txt. - Section 1, 1st paragraph: this describes abstraction but not virtualization. - Section 1, page 3, bullet list: how does this related to VNs? - Section 1.1: too narrow for VN and it mixes VNs with programmable networks. - Section 2: First para: de-ossification may be one motivation but is in IMHO not the motiviation. - Section 2: VNs are not necessarily programmable networks. - Section 3: The requirements are too high-level. It would be good to get more detailed requirements and where (from what system) these requirements are. - Section 4: It's too high-level. A good use case would describe a VN use case and the resulting challenges and requirements I personally do not yet see this document to be the RG problem statement draft at this point of time. The draft misses some important points: - what are some use cases you have in mind (system and what it does) - e.g., testbed virtualization, operator-scale, Internet-scale, etc? - what components are you using - how do these components interact - what about the existing work, e.g., VPNs, L2 link bundling technologies, virtual routers - what are the problems? In general: I do not yet see that this draft is really a problem statement. It makes a start and its worth keep working on it, but needs more thoughts and discussions. Martin martin.stiemerling at neclab.eu NEC Laboratories Europe - Network Research Division NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England 2832014
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.