Hi, Authors of Database-based Open Resource Service drafts: Thank for proposing your idea to ALTO WG, there are two relevant drafts https://datatracker.ietf.org/doc/draft-zhou-alto-dbors-framework/ https://datatracker.ietf.org/doc/draft-zhou-alto-dbors-requirement-usecase/ These two drafts aim at network and cloud integration scenarios, I am more interested in how you implement data based open Resource service using ETCD, a few questions and comments on these two drafts: 1. Can you provide details about network information and cloud information exposure? you can provide parameters or attributes list for network information and cloud information? 2. what schema description file do you use to collect network information and cloud information? what format looks like? Can you provide a JSON example for schema description file format? 3. How do you make sure the path can be managed in response to the scale down or up of the cloud resource? How do you correlate network information with cloud information in your case? 4. Is the network resource is allocated dedicated for a specific cloud service? what about network resource sharing by multiple cloud service? 5. what ALTO protocol extension you are looking for to support cloud and network integration in your cases such as Cloud Access, DCI? I am under impression is that endpoint identified by IPv4/IPv6 address is not sufficient to address your use cases, you might need to extend endpoint address?
-Qin
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
