Sorry for late reply, please see my reply inline below. -----邮件原件----- 发件人: Vijay K. Gurbani [mailto:[email protected]] 发送时间: 2016年3月22日 1:52 收件人: Qin Wu; IETF ALTO 抄送: Y. Richard Yang; RANDRIAMASY, SABINE (SABINE) 主题: Re: [alto] Rebooting ALTO (or how to avoid the "low energy" label)
Qin Wu writes: > Hi, Vijay: > Thank for raising discussion on this. Qin: Thanks for starting a discussion on this. I was wondering why no one had picked up on the mail to start a thread. > Socializing multi-cost and alto-calendar is a good idea, I also think > we should socialize ALTO cost metric draft since this draft is a > companion document of alto-calendar draft and it interacts with many > routing area WGs on how to use measurement data provided by routing > system data source and RFC7471 and RFC7752 even provide a clear ALTO > use case. Great. I would think that you'd want to be in a position by the Berlin IETF to make a short presentation to RTG area to intimate the WGs there on the draft. [Qin]: Sure, if we can proceed alto-calendar and alto te metrics more quickly, I can give a presentation to RTG area. > We authors plan to revive alto te metric draft and keep on proceeding > it in the upcoming IETF meeting. Good. [Qin]: It looks there is no F2F meeting for ALTO in BA. However we authors believe this draft is ready for WG adoption together with alto-calendar draft since this draft has got aligned with RFC7471,RFC7752 and ISIS-TE metric WG draft and ALTO-cost has been discussed several time and both draft are stable now. [Qin]: I am wondering if we can have a timeslot in > Regarding developing policy using ALTO or JSON, I am afraid this has > potential overlapping with SUPA since YANG defined policy can be > translated into either XML format or JSON format and YANG is used to > generate API, it could be RESTful API or PlugRestful API. Do we think > ALTO is another modeling language besides YANG? Is ALTO a modeling language? I don't think so. But I will be the first to admit that my YANG knowledge is not up to par with that of others in the working group, who I hope will hold a more insightful discussion on this topic, and in the process educate me. [Qin]: I hope not, I think ALTO is a just query protocol, but it follows RESTFUL approach and design, Use JSON to encode request and response, JSON provides encoding format. yes we can use JSON to represent policy, but how JSON based policy is different from YANG based policy? I think YANG serves as both information model and data model therefore, when we model policy using YANG, it can be automatically generated into JSON based policy using some tool. Clearly, the emergence of YANG has stymied the efforts of certain work items in ALTO. [Qin]: I think the big difference between them is ALTO separates schema from data model while YANG integrates schema into data model. YANG based model can be translated into JSON format, but for ALTO, given their difference, ALTO doesn't need to rely on YANG to generate JSON format, instead, it can generate JSON format directly. It will be an excellent start for someone (Richard Y?) to provide a summary on the relevant issues we need to discuss here to move some of the work forward and indeed, to formulate a response [Qin]: There is a draft in NETMOD to discuss JSON Encoding of Data Modeled with YANG https://tools.ietf.org/html/draft-ietf-netmod-yang-json-09 However I believe this JSON encoding rule defined in draft-ietf-netmod-yang-json-09 may not sufficient to support ALTO data. It will be great for us to find gap between JSON encoding rule in draft-ietf-netmod-yang-json-09 and JSON encoding rule used in ALTO and document them. --- if one is needed --- on the use of YANG in ALTO. Cheers, - vijay -- Vijay K. Gurbani, Bell Laboratories, Nokia Networks 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA) Email: vkg@{bell-labs.com,acm.org} / [email protected] Web: http://ect.bell-labs.com/who/vkg/ | Calendar: http://goo.gl/x3Ogq _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
