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.

We authors plan to revive alto te metric draft and keep on proceeding
it in the upcoming IETF meeting.

Good.

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.

Clearly, the emergence of YANG has stymied the efforts of certain work
items in ALTO.  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
--- 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

Reply via email to