Hi Jordi,

Will we use email thread for each topic as well? I am writing up a document
for some aspects of Topic A and am eager to post :-)

Richard

On Wed, Jun 21, 2023 at 7:34 AM Jordi Ros Giralt <j...@qti.qualcomm.com>
wrote:

> Hi all,
>
> Many thanks Richard for the great notes and summary of our call yesterday.
>
> Following up on the below plan, I initiated the conversation for topic A
> under this thread:
> https://mailarchive.ietf.org/arch/msg/alto/nSBb2fJwwEEEeZ-Xxw-OmHhJdTs/
>
> Please use this thread to directly express your opinions on topic A. Other
> group members will be initiating similar threads for the other topics.
>
> I have also updated the root document on ALTO future work to include the
> latest conversations about each of the topics:
> https://docs.google.com/document/d/1rpziU7NZEE8f84XkJSjMhEIHUA5G7rXkGB5c_7UFxUY/edit?usp=sharing
>
> Thanks,
> Jordi
> ------------------------------
> *From:* alto <alto-boun...@ietf.org> on behalf of Y. Richard Yang <
> y...@cs.yale.edu>
> *Sent:* Wednesday, June 21, 2023 1:47
> *To:* IETF ALTO <alto@ietf.org>
> *Subject:* [alto] June 20, 2023 meeting minutes and discussion working
> links
>
>
> *WARNING:* This email originated from outside of Qualcomm. Please be wary
> of any links or attachments, and do not enable macros.
> Hi all,
>
> As suggested by Ayoub, Jordi and others during the weekly meeting today,
> starting from today, the note taker will not only update the meeting
> minutes page (
> https://github.com/ietf-wg-alto/wg-materials/blob/main/meetings-ietf-alto/ietf-alto-2023.md),
> but also provide a text summary and comments, if appropriate, on the
> meeting. So below are my quick comments and the full meeting minutes are
> below; the archive is at the link above.
>
> Regarding comments, the most important item that I, as a note taker, take
> away is the wonderful discussion about how to organize future work
> discussions. In particular, the participants divided the potential work
> into 4 areas, and created 4 github issues. We also created a common Google
> doc to allow systematic write up. The links to them are below.
>
> In particular, the four areas and their coordinators are:
> - A: Integration of data sources and their exposures; coordinator: Jordi,
> Luis and Kai
> - B: Maintenance of ALTO protocol; coordinator: Luis, Richard
> - C: Security and trust; coordinators: Ayoub, Junichi, Motoyoshi
> - D: New architectural extensions; coordinators: Roland and Sabine
>
> We sure can adjust the coordinators. So so, please let me know, and we can
> adjust the page. The plan is that the coordinators will closely with the
> chairs (Qin and Med) to make concrete progress. The coordinators will kick
> off the discussions.
>
> Richard as note taker on June 20, 2023
>
> ==== Meeting Minutes Text ====
>
> *IETF, ALTO Meeting: June 20, 2023*
>
> *Agenda:*
>
>    - Transport and OAM documents
>       - Transport:
>       https://github.com/ietf-wg-alto/draft-ietf-alto-new-transport/issues
>    - OAM: https://github.com/ietf-wg-alto/draft-ietf-alto-oam-yang/issues
>    - ALTO Future Work:
>    https://mailarchive.ietf.org/arch/msg/alto/uIFD6Dhikfu4J4PYcpJTbsiXbnE/
>
>    
> https://github.com/ietf-wg-alto/wg-materials/blob/main/FutureALTO/alto-direction-of-work.md
>    - Preps for IETF 117:
>       - Drafts and presentations that the ALTO group plans to work on
>       - Agenda
>    - New revision of Green Networking Metrics draft in opsawg:
>    https://datatracker.ietf.org/doc/draft-cx-opsawg-green-metrics/
>
> *Minutes*
>
> *Note taker: Richard
>
>    -
>
>    Charter documents: transport and OAM updates
>    - OAM: Jensen and Med had a discussion on the draft and submit the
>       revision to IESG. The document is now waiting for AD review.
>       - Transport: Richard sent a note to Martin Thompson, to provide the
>       justification on introducing server push using PUSH PROMISE. It includes
>       two basic reasonings: lower load, and the feature is optional; Kai 
> updated
>       that Med sent two pull requests and sent the latest version for AD 
> review,
>       and wait for updates.
>    -
>
>    Updates on future work on ALTO
>    -
>
>       Overview: Jordi started with an update on the planning: Please
>       follow the ongoing conversation on the WG mailing list initiated by 
> Sabine,
>       engaged by Jordi and Luis; the WG welcomes conversations by all; please
>       socialize the ideas; leadership is important and please take ownership;
>       this WG meets each week, and we do not know any other IETF WG that meets
>       each week, but because we meet each week, we do not use the mailing 
> list,
>       which may appear to be inactive by those not attending the weekly 
> meeting.
>       -
>
>       Individual topics:
>       - Jordi summarized that from the mailing list, item 3 appears to be
>          the most preferred; please do discussions, propose a charter item 
> and then
>          write documents; The goal is to go to 117 and should be prepared.
>          - Richard commented that one of his focus points will be on data
>          sources, which can be more informational than standard. Luis advised 
> that
>          there can be two types of approaches: bottom-up (individuals propose
>          ideas), and top-down (chairs/AD guidance).
>          - Luis suggests that we should take a look at chair-mentioned
>          items such as BGP communities, and security; mid-term: such as data
>          sources, please go to the mailing list.
>       -
>
>    Work organization: Meeting notes work plan: Ayoub gave the suggestion
>    that note taker shares the note to the mailing list, some kind of annotated
>    meeting minutes. Roland clarified that the sharing notes can be double
>    sent, or summary/highlights, or up to note taker. Organizing discussions:
>    Luis/Jordi: email as record, GitHub tickets to organize; Jordi creates 4
>    tickets, and puts links to doc.
>    -
>
>    Issues, leads, and working documents:
>    -
>
>       Topic A:
>       - GitHub issue: #48
>          <https://github.com/ietf-wg-alto/wg-materials/issues/48>
>          - Topic coordinator: Jordi, Kai
>       -
>
>       Topic B:
>       - GitHub: #49
>          <https://github.com/ietf-wg-alto/wg-materials/issues/49>
>          - Topic coordinator: Roland, Sabine
>       -
>
>       Topic C:
>       - GitHub: #50
>          <https://github.com/ietf-wg-alto/wg-materials/issues/50>
>          - Topic coordinator: Ayoub, Junichi, Motoyoshi
>       -
>
>       Topic D:
>       - GitHub: #51
>          <https://github.com/ietf-wg-alto/wg-materials/issues/51>
>          - Coordinator: Luis, Jordi
>       -
>
>       Discussion Google doc:
>       -
>          
> https://docs.google.com/document/d/1rpziU7NZEE8f84XkJSjMhEIHUA5G7rXkGB5c_7UFxUY/edit?usp=sharing
>       -
>
>       Goals: Enabling conversations and concrete documents (compute, edge
>       service, etc), need to focus; real good way to make progress is
>       internet-draft (ID) as ground truth, from dynamic to stable, with focus 
> on
>       writing drafts for concrete results).
>
>
_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

Reply via email to