Meeting notes from ALTO WG meeting, IETF 88, Vancouver, Canada.
Monday, November 4, 2013

This report has been distilled from the detailed meeting notes taken
by Young Lee and Sabine Randriamasy.

Chairs: Vijay Gurbani and Enrico Marocco.

Agenda
------

Meeting materials: 
  slides, 
  Meetecho recording (HTML5) 

  Enrico presented the agenda and the status of the WG. WGLC concluded
  for the protocol draft.

    Richard Yang: no major issue; next step to be sent to IESG. Two
    minor issues addressed were cross references and details on how to
    handle errors (addressed with input from Sebastian Kiesel). IP
    longest matching – for single PID or multiple PIDs still needs to
    be resolved. The consensus among the authors seems to lean to
    allowing the client to choose one PID in case multiple PIDs are
    supported.

  The ALTO server discovery draft is in RFC Ed's queue. Two
  complementary drafts were agreed to be adopted in Orlando, but
  little interest shown on the list.

    Wolfgang Beck: 3rd party discovery is needed to be adopted and
    progressed.

    Jan Seedorf: just sent my support on the list.


Deployment considerations
-------------------------

Meeting materials: 
  slides, 
  Meetecho recording (HTML5) 

  Vijay on behalf of Michael Scharf presented the status of the
  deployment considerations draft.

    Richard: language, API dependent? Vijay: no need for standardize
    APIs. Diego Lopez: agreed.

    Richard: on monitoring. We need to define: what are we looking
    for? Then we can understand. Vijay: we let Michael asnswer. This
    is a charter item, so please do react on the list.


Extension: Topology service
---------------------------

Meeting materials: 
  slides, 
  Meetecho recording (HTML5) 

  Richard presented the requirements for an advanced topology
  service. Many networks (e.g. Verizon, Century Link, British Telecom,
  China Telecom) already provide such kind of information, but in
  various funny formats (e.g. PDF, JPG).

    Jan: what is the intention of provider? Isn't it that they not
    want provide info to apps? Richard: well, they end up just making
    it more difficult to apps to access such data, not impossible.

    Diego: client of several providers in multi-home environment would
    be the context? Richard: yes. Security needs to be clarified when
    this happens.

    Jan: for rechartering, specific item needs to be elaborated.

  Comments deferred to the end of the extensions presentations.


Extension: Exporting of LMAP information
----------------------------------------

Meeting materials: 
  slides, 
  Meetecho recording (HTML5) 

  Jan presented a proposal about how to export LMAP information with ALTO.

  Comments deferred to the end of the extensions presentations.


Extension: VPN environments
---------------------------

Meeting materials: 
  slides, 
  Meetecho recording (HTML5) 

  Vijay on behalf of Michael presented a proposal for extending ALTO
  to support VPN enviroments.

  Comments deferred to the end of the extensions presentations.


Extension: Virtualization
-------------------------

Meeting materials: 
  slides, 
  Meetecho recording (HTML5) 

  Zhen Cao presented a proposal for extending ALTO for usage in
  virtualized environments.

    Jan: (clarification) require both ways (2-ways) between client and server
    communication? Zhen: depends on the use-case.

  Comments deferred to the end of the extensions presentations.


Extension: CDNI
---------------

Meeting materials: 
  slides, 
  Meetecho recording (HTML5) 

  Jan presented a proposal for using ALTO for CDNI request routing.

  Comments deferred to the end of the extensions presentations.


Extension: Traffic engineering
------------------------------

Meeting materials: 
  slides, 
  Meetecho recording (HTML5) 

  Qin Wu presented a proposal for using ALTO for exporting TE cost metrics.

  Comments deferred to the end of the extensions presentations.


Extension: Overlay routing
--------------------------

Meeting materials: 
  slides, 
  Meetecho recording (HTML5) 

  Haibin Song presented a proposal for using ALTO for providing
  guidance to overlay routing.

  Comments deferred to the end of the extensions presentations.


Extension: High bandwidth applications
--------------------------------------

Meeting materials: 
  slides, 
  Meetecho recording (HTML5) 

  Yang presented a proposal for using using ALTO in high bandwidth scenarios.

    From Jabber: are IPv4 addresses as EP ID always sufficient? Yang:
    other names will likely need to be supported.

  Comments deferred to the end of the extensions presentations.


Extension: PID properties
-------------------------

Meeting materials: 
  slides, 
  Meetecho recording (HTML5) 

  Richard presented a proposal for extending PID properties.

  Comments deferred to the end of the extensions presentations.


Wrap-up
-------

Meeting materials: 
  Meetecho recording (HTML5) 

  Vijay wraps up. The goal of the extension proposals presentations
  was to identify a taxonomy of proposed extensions, measure the WG
  interest (i.e., is there a real need for IETF standardization?) and
  identify options for moving the work ahead.

  Some use-cases seem quite popular; some can be done here, other in
  other WGs.

  Some basic building blocks (e.g. incremental updates,
  server-initiated notifications) can enable most of the extensions
  proposed incremental.

    Jan: what is the minimum set the WG wants?; Is that enough or not
    for each use-case?

    Wolfgang: there are some use cases where parties could use routing
    protocol and not ALTO. Need to focus on application-oriented use
    cases.

  Spencer Dawkins (responsible AD): focus on identifying building
  blocs. Let us focus on what we do rather than on where/how to do
  it. I recommend to finish base protocol. Thank you all.