Hi Richard and all, for the last few years I've been teaching and
working in the SDN space and mostly agree with Richard's assessment. The
only disagreement is with his assessment of "slow" convergence of the
network graph/(path vector) drafts. These drafts are basically in
conceptual agreement and have been for quite some time (2012 Vancouver
meeting). The exact encoding details were not worked out at the time,
but could be quickly converged based on examples that have been given in
the more recent drafts.
The applicability of such a feature to SDN virtualized networks
hopefully should be clear but we can easily add it as another
application/motivation.
On 7/4/2016 4:06 PM, Y. Richard Yang 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?
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 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.
Cheers,
Richard
[1] https://www.opendaylight.org/file/odl-beryllium-diagram02
[2] https://datatracker.ietf.org/doc/draft-wang-alto-ecs-flows/
[3]
https://datatracker.ietf.org/doc/draft-gao-alto-routing-state-abstraction/
[4] https://tools.ietf.org/html/draft-yang-alto-topology-06
[5] https://tools.ietf.org/html/draft-scharf-alto-topology-00
On Wednesday, June 29, 2016, Vijay K. Gurbani <[email protected]
<mailto:[email protected]>> wrote:
Folks: Please send me and Jan agenda requests for the ALTO WG meeting
in IETF. We have a 2 hour slot on Thu afternoon (July 21).
Specifically:
- Presenter name
- Time requested (in minutes)
- Internet-Draft to be discussed
As usual, drafts that have seen list discussions will be given
precedence when scheduling the agenda.
As you are all aware, the deployment draft is now with the IESG.
As per our last meeting (virtual interm [1]), we need to move two
drafts ahead: (1) draft-ietf-alto-multi-cost-01 needs to be scheduled
for a WGLC, and (2) draft-randriamasy-alto-cost-calendar-05 needs
to be
open up to being adopted as a WG item. Jan and I will like to start
proceeding on this perhaps as early as next week.
[1]
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_proceedings_interim_2015_10_27_alto_minutes_minutes-2Dinterim-2D2015-2Dalto-2D1&d=CwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=ASHRozEgZvFCzydTsT-P7fLIy1RVC6ciNuTtWDmqNtM&s=ghe2Ca7B5zd4u_ZWbLeZZ5oexLFxV07x-MYfkipmAk4&e=
Thank you,
- 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=CwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=ASHRozEgZvFCzydTsT-P7fLIy1RVC6ciNuTtWDmqNtM&s=TgjoQbo9aR1PTVWRY6Ydlw_khODlDN6l8OaFh4fS1ZA&e=
| Calendar:
https://urldefense.proofpoint.com/v2/url?u=http-3A__goo.gl_x3Ogq&d=CwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=ASHRozEgZvFCzydTsT-P7fLIy1RVC6ciNuTtWDmqNtM&s=1Q7R5p_enzJxoGM_E41qNrEhCWmfOrjLsuv6jL-Sw64&e=
_______________________________________________
alto mailing list
[email protected]
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_alto&d=CwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=4G36iiEVb2m_v-0RnP2gx9KZJjYQgfvrOCE3789JGIA&m=ASHRozEgZvFCzydTsT-P7fLIy1RVC6ciNuTtWDmqNtM&s=M5Nv0WdiAJeh_iGLcglzHuJQVxMDz5gxGw32JXEFCf8&e=
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
