Vijay, Please see inline.
On Tue, Jul 5, 2016 at 1:04 PM, Vijay K. Gurbani <[email protected]> wrote: > On Monday, Jul 4, 2016 "Y. Richard Yang" <[email protected]> wrote: > > Vijay, Jan, all, >> >> I am replying this email publicly so that all of us can engage more >> in shaping the agenda in about three weeks. >> >> A key item that the WG needs to discuss, in the potentially more >> productive f2f-meeting setting in Berlin, is how the WG should move >> forward. Can we allocate a slot, say at least 20 min, for this >> discussion? >> > > Richard: ACK. More inline. > > Besides the general discussions, here are some comments on specific >> agenda items and the mission of the WG: >> >> - Despite the substantial change of the networking landscape, I still >> believe that the foundational services of ALTO are sound: providing >> abstract network information to applications. I believe that this is >> also what many others see ALTO; for example see [1]. The key is what >> we do to go beyond the initial network abstractions. >> > > - The first I see is Endpoint Cost Service (ECS), which is the >> foundation. It provides an interface to allow applications to know >> the routing costs. However, current ALTO is defined pre-SDN, and the >> emerging trend of SDN is going beyond simple destination routing, to >> be more application dependent. Hence, I see that we need to go beyond >> Endpoint Cost Service, to say Flow Cost Service. There is an >> extension draft [2], and I suggest that the WG finishes this to make >> the ALTO protocol complete. Make sense? >> > > The ecs-flow draft has been around for a couple of months. I don't > think it has attracted WG attention, despite being headed in the right > direction with respect to the abstraction that involves application- > constraints during routing decisions. > > - The next I see is network graph (path vector) abstraction. The >> more I think about it, the more I am convinced that this is the way >> we go. I am an author of the draft and multiple versions are evolving >> [3, 4, 5], but we are relatively slow in convergence. I suggest that >> the WG gets a set of active participants to finish this draft, so >> that we have a relatively complete set of ALTO services. >> > > The above will be imperative, I believe. I may well be wrong and it may > just be me, but I still sense a bit of bewilderment as the convergence > occurs. Most of the time, these drafts gets discussed around a pending > meeting. I think it is necessary to crisply define and finish this > work as soon as possible. > > OK. We should target posting a spec by this Friday so that we can discuss the spec before the meeting, to remove any confusion/bewilderment. Since the key piece is encoding specification of (1) graph; and (2) path vector associated w/ a graph. We will target posting those spec, precisely first. Thanks, Richard > [1] >> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.opendaylight.org_file_odl-2Dberyllium-2Ddiagram02&d=CwICaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=adhagbZSLa5CB30jrM471w53fmh23nxWmJzt3jJW07c&s=ECAY29NKpa-pzUFGnbFKc14RscT_yWXOudwbFTF_JOA&e= >> [2] >> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dwang-2Dalto-2Decs-2Dflows_&d=CwICaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=adhagbZSLa5CB30jrM471w53fmh23nxWmJzt3jJW07c&s=KoT7ZAqiWhT9v8F789UjuxAXfsWYGhVHJ8ky_4a1iYA&e= >> [3] >> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dgao-2Dalto-2Drouting-2Dstate-2Dabstraction_&d=CwICaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=adhagbZSLa5CB30jrM471w53fmh23nxWmJzt3jJW07c&s=SQw1tvpbmAAef8M7j2zUxUpRDNjT962ij0EwRRAwTe8&e= >> [4] >> https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dyang-2Dalto-2Dtopology-2D06&d=CwICaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=adhagbZSLa5CB30jrM471w53fmh23nxWmJzt3jJW07c&s=iHLFCmBP0BOPkNSlv7GTtgbIKJOsJC3QVv5vYEGDp1s&e= >> [5] >> https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dscharf-2Dalto-2Dtopology-2D00&d=CwICaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=adhagbZSLa5CB30jrM471w53fmh23nxWmJzt3jJW07c&s=I7IDwEnKJY80JCz52SuKsoi4Fj6eedjJuwWkNGYsFOM&e= >> > > Thanks, > > - vijay > -- > Vijay K. Gurbani, Bell Laboratories, Nokia Networks > 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA) > Email: [email protected] / [email protected] > Web: > https://urldefense.proofpoint.com/v2/url?u=http-3A__ect.bell-2Dlabs.com_who_vkg_&d=CwICaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=adhagbZSLa5CB30jrM471w53fmh23nxWmJzt3jJW07c&s=CVBjaDcXsvH5d3XzEDkwYshYN1iFjR4RHwwPFmxfPIY&e= > | Calendar: > https://urldefense.proofpoint.com/v2/url?u=http-3A__goo.gl_x3Ogq&d=CwICaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=adhagbZSLa5CB30jrM471w53fmh23nxWmJzt3jJW07c&s=enw4lznI8SylO_dz-KCbJLBPlXhKyWdRXHMGDAg--Zw&e= -- -- ===================================== | Y. Richard Yang <[email protected]> | | Professor of Computer Science | | http://www.cs.yale.edu/~yry/ | =====================================
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
