Hi Roman,
Thanks for the update. We adopt the nits and propose the following text in Sec
9:
Additionally, operators of the ALTO servers MUST follow the guidelines in
[RFC9325]
to avoid new TLS vulnerabilities discovered after [RFC7285] was published.
Please let us know if that makes sense.
Thanks Zahed, these comments are very helpful. I just submitted the new
revision -20.
Best,
Kai
> -Original Messages-
> From: "Zaheduzzaman Sarker"
> Send time:Thursday, 11/30/2023 17:32:14
> To: kai...@scu.edu.cn
> Cc: "Kai GAO" , "The IESG" ,
> alto@ietf.org, alto-cha...@ietf.org,
Hi Zahed,
Please see inline for the new text. If it works, I will submit a new revision
with the proposed changes. Thanks for the helpful review!
Best,
Kai
-Original Messages-
From:"Zaheduzzaman Sarker"
Send time:Wednesday, 11/29/2023 20:01:10
To: kai...@scu.edu.cn
Cc: "Kai GAO"
Hi Zahed,
Thanks for the comments! Please see the responses inline. I already have the
updates in place but would like to submit a new revision after you review the
proposed texts.
Best,
Kai
-Original Messages-
From:"Zaheduzzaman Sarker"
Send time:Tuesday, 11/28/2023 20:02:44
To:
Hi Martin,
The paragraph is in -19 which I just submitted. Thanks for the reminder.
Best,
Kai
-Original Messages-
From:"Martin Duke"
Send time:Tuesday, 11/28/2023 05:29:06
To: "Kai GAO"
Cc: "Zaheduzzaman Sarker" , "The IESG"
, alto-cha...@ietf.org,
Hi Francesca,
We have uploaded a new revision (-18) of the document
draft-ietf-alto-new-transport
(https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/). Could you
please take a look and see if the proposed changes address your DISCUSS points?
Thanks!
Best,
Kai
> -Original
Hi Francesca,
Thanks for the review. Please see our responses to the "other points" below.
Best,
Kai
> -Original Messages-
> From: "Francesca Palombini via Datatracker"
> Send time:Wednesday, 10/25/2023 14:29:19
> To: "The IESG"
> Cc: alto-cha...@ietf.org,
Hi Bob,
Thanks for the review. Please see inline.
Best,
Kai
> -Original Messages-
> From: "Bob Halley via Datatracker"
> Send time:Thursday, 10/19/2023 22:11:44
> To: int-...@ietf.org
> Cc: alto@ietf.org, draft-ietf-alto-new-transport@ietf.org,
> last-c...@ietf.org
> Subject:
Hi Wesley,
Sorry for the delay. Here are the follow-up updates of your telechat review.
Regarding the relationship between TIPS and ALTO/SSE, we think that they can
both transport incremental updates but offer different and complementary
capabilities: TIPS is optimizing for throughput and
Hi Roman,
I hope you are OK with our responses to your DISCUSS points. This is the
follow-up update regarding your comments.
First, for the comment on Digest authentication, we agree that this is a fair
request as RFC 7285 says Digest authentication is mandatory. An example using
Digest
Hi Roman,
Thanks for the review. Please see inline.
Best,
Kai
> -Original Messages-
> From: "Roman Danyliw via Datatracker"
> Send time:Tuesday, 10/24/2023 10:40:46
> To: "The IESG"
> Cc: alto-cha...@ietf.org, draft-ietf-alto-new-transp...@ietf.org,
> alto@ietf.org
> Subject: [alto]
Hi Med and Wesley,
Thanks for the comments! I already fix nits 1 & 3 and we will propose some new
texts for Issue 1) and Nits 2) as soon as possible.
Best,
Kai
> -Original Messages-
> From: mohamed.boucad...@orange.com
> Send time:Tuesday, 10/24/2023 13:40:02
> To: "Wesley Eddy" ,
Hi Martin,
I'm holding the revision -17 as there is a GENART LC review. I will submit once
the proposed change is acked or there is no respond before Saturday night.
Best,
Kai
-Original Messages-
From:"Martin Duke"
Send time:Thursday, 10/19/2023 21:20:47
To: kai...@scu.edu.cn
Cc:
Hi Linda,
Different clients can request different incremental updates and the load
balancing is applied to all requests. However, here the issue is mainly for a
single user whose requests may be distributed through different HTTP
connections (and eventually different TCP connections). The
Hi Martin,
I would like to change the wording a bit to make sure they guidelines are
interpreted as applicable only when the resources are sufficient:
OLD:
If resources allow, servers SHOULD avoid closing TIPS views that have active
polling edge requests. Servers also SHOULD avoid closing
-Original Messages-
From:"Martin Duke"
Send time:Tuesday, 10/17/2023 22:45:05
To: kai...@scu.edu.cn
Cc: draft-ietf-alto-new-transport@ietf.org, "Martin Thomson"
, "IETF ALTO"
Subject: Re: Re: Re: AD comments on draft-ietf-alto-new-transport-15
On Sat, Oct 14, 2023 at 8:15
Hi Martin,
Thanks for the comments. Please see inline.
Best,
Kai
-Original Messages-
From:"Martin Duke"
Send time:Saturday, 10/14/2023 04:04:43
To: kai...@scu.edu.cn
Cc: draft-ietf-alto-new-transport@ietf.org, "Martin Thomson"
, "IETF ALTO"
Subject: Re: Re: AD comments on
Hi Martin,
Thanks for the summary. I like the simplicity of approach 2 but here are some
concerns.
The previous service model is more like First-Come First-Serve, so that the
server keeps the resources for views that already exist and reject requests if
the resources are constrained. Approach
eview of
> draft-ietf-alto-new-transport-14
>
>
>
>
> > -Original Messages-
> > From: "Martin Thomson"
> > Send time:Thursday, 10/05/2023 11:26:32
> > To: kaigao
> > Cc: ietf-http...@w3.org, alto@ietf.org,
> > draft-ietf-a
> -Original Messages-
> From: "Martin Thomson"
> Send time:Thursday, 10/05/2023 11:26:32
> To: kaigao
> Cc: ietf-http...@w3.org, alto@ietf.org,
> draft-ietf-alto-new-transport@ietf.org, last-c...@ietf.org
> Subject: Re: Httpdir last call review o
Hi Martin,
Thanks for the review. Sorry it took us a while to read related documents and
discuss internally. Please see our proposed changes below.
Best,
Kai
> -Original Messages-
> From: "Martin Thomson via Datatracker"
> Send time:Wednesday, 09/27/2023 13:00:00
> To:
Dear all,
We have prepared a new revision of the new transport document (version -12) [1]
based on the AD review and follow-up discussions. The major changes include
- Add a paragraph to discuss why this extension should coexist with RFC 8895
- Move the server push feature to the
Dear all,
The meeting minutes of today's meeting are attached below. You may also check
the github page to follow up previous meetings.
Best,
Kai
Meeting minutes:
https://github.com/ietf-wg-alto/wg-materials/blob/main/meetings-ietf-alto/ietf-alto-2023.md
==
Hi Spencer,
Thanks for the reply! The reviews really help to make the draft in a better
shape!
Thanks a lot and stay well!
Best,
Kai
-Original Messages-
From: "Spencer Dawkins at IETF"
Sent Time: 2023-06-06 04:23:04 (Tuesday)
To: kai...@scu.edu.cn
Cc: "alto@ietf.org" ,
Hi Med and all,
Sure! We will prepare a new revision shortly based on the comments.
We would also like to thanks the reviewers for the wonderful comments.
Best,
Kai
-Original Messages-
From:mohamed.boucad...@orange.com
Sent Time:2023-06-01 22:35:59 (Thursday)
To: "IETF ALTO
Hi Qiufang,
Thanks for the review! It is very helpful. Please see the responses inline.
Best,
Kai
-Original Messages-
From: "maqiufang (A)"
Sent Time: 2023-05-19 15:59:03 (Friday)
To: "draft-ietf-alto-new-transp...@ietf.org"
Cc: "IETF ALTO"
Subject: [alto] Comments on
Hi Adrian,
Thanks for the review. We will fix the unused reference issue.
Best,
Kai
-Original Messages-
From:"Adrian Farrel"
Sent Time:2023-05-22 06:09:42 (Monday)
To: "'Jordi Ros Giralt'" , alto@ietf.org
Cc:
Subject: [alto] draft-ietf-alto-new-transport : Call for volunteers
Hi Spencer,
We have prepared a pre-release of the new transport document. You can see the
diffs with the link below, and the details are inline.
Please let us know if the updates address your comments. We look forward to
your feedback!
Diff with -07:
Hi Bernard,
We have made a pre-release of the new transport document based on your review
and some others'. You can see the updates using the link below and here is a
short summary:
- Requirements for the document are summarized in Section 2.1 Transport
Requirements. The requirements are
Hi Luis and all,
Thanks for the effort. The information is really useful and comprehensive. I
think it lays a very good foundation to discuss and proceed with potential ALTO
extensions.
With the rationale that, in my opinion, sets the expectations for each data
source, I am wondering
Hi Martin and all,
Thanks a lot for these wonderful comments! We are sorry for the late response
but it took us a while to digest the comments and discuss internally. The
responses will arrive in multiple emails, focusing on different aspects.
Before going to the technical and editorial
Hi Bernard,
Thanks for the enlightening review. Please see the responses inline.
Best,
Kai
-Original Messages-
From: "Bernard Aboba via Datatracker"
Sent Time: 2023-03-16 04:49:06 (Thursday)
To: tsv-...@ietf.org
Cc: alto@ietf.org, draft-ietf-alto-new-transport@ietf.org
Hi Spencer,
Thanks for the review. Please see our responses below
-Original Messages-
From:mohamed.boucad...@orange.com
Sent Time:2023-03-18 03:35:29 (Saturday)
To: "Spencer Dawkins at IETF" , "alto@ietf.org"
, "draft-ietf-alto-new-transp...@ietf.org"
Cc: "a...@ietf.org"
Hi Med,
Got it. We will respond to the mailing list. Thanks!
Best,
Kai
-Original Messages-
From:mohamed.boucad...@orange.com
Sent Time:2023-03-21 23:45:09 (Tuesday)
To: "kai...@scu.edu.cn"
Cc: "IETF ALTO" , "draft-ietf-alto-new-transp...@ietf.org"
, "ALTO Working Group"
Hi Med,
Thanks for the reminder and organization. Yes, we are preparing to address the
comments and will post in the next 2 days.
One quick question, what is the best way to do this? Should we resolve the WGLC
issues on github or respond to the mailing list likely we did in the past?
Hi Med and all,
I am not aware of any IPR related to draft-ietf-alto-new-transport.
Best,
Kai
-Original Messages-
From:"Y. Richard Yang"
Sent Time:2023-02-28 03:04:29 (Tuesday)
To: roland.sch...@telekom.de
Cc: draft-ietf-alto-new-transp...@ietf.org, alto@ietf.org
Subject: Re:
Hi everyone,
I am not aware of any IPR applied to this document.
Best,
Kai
-Original Messages-
From:"maqiufang (A)"
Sent Time:2023-02-28 09:21:18 (Tuesday)
To: "mohamed.boucad...@orange.com" ,
"draft-ietf-alto-oam-y...@ietf.org"
Cc: "'alto@ietf.org'"
Subject: RE: IPR poll:
Dear ALTOers,
My student Jie is helping with the Wiki transition and he has submitted a pull
request [1] to the wiki.ietf.org repository. Please feel free to review the
pages and see if there is any problem with the transition.
Best,
Kai
[1] https://github.com/ietf/wiki.ietf.org/pull/16
Hi all,
For anyone who is interested in playing around or participating in the
development/deployment of the openalto project, here is a brief introduction to
the code base. We will post further information such as the architecture and
how to install/deploy the server to the mailing list as
Hi Jensen, Qin and all,
Thanks for the discussion. Please see my comments inline.
Best,
Kai
-Original Messages-
From:"Jensen Zhang"
Sent Time:2022-09-06 21:13:01 (Tuesday)
To: "Qin Wu"
Cc: "IETF ALTO"
Subject: Re: [alto] Open discussions of ALTO O data model
Hi Qin,
Sorry
Dear all,
I had a back surgery today and will take a rest for the next coming days. In
that case, I will not be able to attend the meeting today. I will read the
meeting notes once I get better. My apologies.
Best,
Kai
___
alto mailing list
Hi all,
I am not aware of any IPR related to this document.
Best,
Kai
-Original Messages-
From:"王巍"
Sent Time:2022-06-13 10:31:11 (Monday)
To: "Qin Wu" , "alto@ietf.org"
Cc:
Subject: Re: [alto] WG adoption call for draft-schott-alto-new-transport-01
Hi all,
I have
Hi Qin, Danny and all,
Sorry I did not get the email from Danny and just saw this discussion. Please
see my comments inline.
Best,
Kai
-Original Messages-
From:"Qin Wu"
Sent Time:2022-05-18 13:07:36 (Wednesday)
To: "Danny Lachos" , "Jordi Ros Giralt"
, "kai...@scu.edu.cn" ,
Hi Med,
Sounds good to me. Then I believe all comments are already addressed and the
draft is ready for publication.
Thanks for all the work!
Best,
Kai
-Original Messages-
From: mohamed.boucad...@orange.com
Sent Time: 2022-04-19 13:21:47 (Tuesday)
To: "kai...@scu.edu.cn"
Cc:
Hi Med,
Thanks for the quick update but I have one additional comment on the registry
specification:
I suggest adding the following paragraphs after the registry table:
NEW:
Requests to add a new value to the registry MUST include the
following information:
o Identifier: The name of
Dear WG and authors of draft-ietf-alto-cost-mode,
I am posting this review of draft-ietf-alto-cost-mode-01 to the mailing list, as
part of my shepherd write-up. Any comments and feedback are more than welcome!
Best,
Kai
===
This draft extends the base ALTO protocol (RFC 7285)
Dear authors,
Please reply to this email (with the WG mailing list cc'ed) indicating whether
you are aware of any IPR related to draft-ietf-alto-cost-mode.
If you are aware of any, can you please confirm that all appropriate IPR
disclosures required for full conformance with the provisions
Hi Med and all,
Sounds good to me. In that case, I think we can end the WGLC for
draft-ietf-alto-cost-mode-00.
Three individual reviews were posted to the mailing list by Peng [1], Jordi [2]
and Qiao [3]. No objections have been raised and I believe a new version has
already been
Hi Qin, Qiao and all,
I searched for a few documents and it seems that many documents are referring
to U+002D as hyphen-minus. It seems to me that we should use hyphen-minus.
https://datatracker.ietf.org/doc/html/rfc3490
https://datatracker.ietf.org/doc/html/rfc5890
Hi Qiao and all,
Thanks for reviewing the document.
In RFC 7285, "hyphen" is used when defining PID, cost metric, etc. One option
is to use the term consistently with existing RFCs.
Best,
Kai
-Original Messages-
From:"Qiao Xiang"
Sent Time:2022-04-09 18:04:36 (Saturday)
Hi Jordi,
Thanks for reviewing the document!
Best,
Kai
-Original Messages-
From:"Jordi Ros Giralt"
Sent Time:2022-04-08 13:03:03 (Friday)
To: "kai...@scu.edu.cn" , "alto@ietf.org"
Cc:
Subject: Re: [alto] WGLC for draft-ietf-alto-cost-mode-00
Hi Kai,
I read this document
Hi Jordi,
Sounds good. I will put this in the agenda.
Best,
Kai
-Original Messages-
From:"Jordi Ros Giralt"
Sent Time:2022-04-04 18:30:48 (Monday)
To: "alto@ietf.org" , "kai...@scu.edu.cn" ,
"Qin Wu"
Cc:
Subject: Re: ALTO WG Project Dashboards
Correction:
s/previous
Hi WG,
I am not aware of any IPR related to this document.
Best,
Kai
-Original Messages-
From:"Wei Wang"
Sent Time:2022-03-30 14:37:41 (Wednesday)
To: "mohamed.boucadair" ,
"draft-zhang-alto-oam-y...@ietf.org"
Cc: "alto@ietf.org"
Subject: Re:[alto] IPR Poll for
Hi all,
As discussed during the ALTO session in IETF 113, the ALTO cost mode document
is now adopted as a working group document. A new WG version
(draft-ietf-alto-cost-mode-00) [1] has been submitted to replace the individual
draft and address comments from the Call for Adoption.
To move
Dear all,
The Call for Adoption for draft-bw-alto-cost-mode-01 is taken on the mailing
list [1] from March 7 to March 21 to determine if the WG should adopt
draft-bw-alto-cost-mode-01 as a working group document to fulfill the
deliverable regarding "protocol maintenance".
As the mailing list
Hi Ben,
Thanks for the feedback. Please see inline for the response.
Best,
Kai
-Original Messages-
From: "Benjamin Kaduk via Datatracker"
Sent Time: 2022-03-20 01:41:31 (Sunday)
To: "The IESG"
Cc: alto-cha...@ietf.org, draft-ietf-alto-path-vec...@ietf.org,
alto@ietf.org
Hi Ben,
How are you doing?
We are wondering if you can take a look at the proposed changes of Path Vector
and see whether they address the DISCUSS and COMMENT.
Thanks a lot!
Best,
Kai
-Original Messages-
From: kai...@scu.edu.cn
Sent Time: 2022-03-06 01:17:37 (Sunday)
To:
Dear all,
This is a friendly reminder that the time of the ALTO weekly meeting is 9:00 am
US EST (2:00 pm CET and 9:00 pm Beijing Time) now.
Best,
Kai
-Original Messages-
From:"ALTO Working Group"
Sent Time:2022-03-15 13:51:19 (Tuesday)
To: kai...@scu.edu.cn
Cc:
Subject:
Dear all,
I have been appointed to run the Call for Adoption of
draft-bw-alto-cost-mode-01.
Following up with what has been proposed and agreed during the IESG review on
draft-ietf-alto-path-vector [1], we are starting a call for adoption of the
ALTO cost mode [2] document as a charter
Hi Samuel,
Sorry to bother you again but we have just submitted a new version of the path
vector document. See the diff in [1].
[1]
https://www.ietf.org/rfcdiff?url1=draft-ietf-alto-path-vector-22url2=draft-ietf-alto-path-vector-23
Ben gave some suggestions on the security consideration part.
Hi Ben,
We have just submitted a new revision of path vector. Please see the diff in
[1].
[1]
https://www.ietf.org/rfcdiff?url1=draft-ietf-alto-path-vector-22url2=draft-ietf-alto-path-vector-23
There are two parts that are slightly different from the previously proposed
text:
Section 6.2.4:
Hi Martin and Ben,
I think ideally making an update to RFC 7285 probably is the best way to solve
the issue. In RFC 7285, the definition for the cost services actually leave
space for non-numerical/ordinal cost values:
Section 11.2.3.6:
... An implementation of the protocol in
Hi Jordi and all,
Sextant is EPL v1.0 (inherited from OpenDaylight). The license is put in the
front of each source file.
Best,
Kai
-Original Messages-
From:"Jordi Ros Giralt"
Sent Time:2022-03-04 06:35:30 (Friday)
To: "Charles Eckel (eckelcu)" , "Christian
Esteve
Hi Ben,
Thanks a lot for the review. The comments are really helpful. We have proposed
texts for most of the comments except for calculating content-lengths and the
security-related comments, which we will come up with some proposal tomorrow.
Please see our feedback inline.
Best,
Kai
Hi Samuel,
Thanks for the feedback. Please see our replies inline.
Best,
Kai
-Original Messages-
From: "Samuel Weiler via Datatracker"
Sent Time: 2022-02-26 05:38:53 (Saturday)
To: sec...@ietf.org
Cc: alto@ietf.org, draft-ietf-alto-path-vector@ietf.org,
last-c...@ietf.org
Hi Reinaldo and all,
There are some projects where the hackathon can be based on. If you are
developing something on top of these projects, I would recommend using the same
or compatible licenses.
https://github.com/openalto/sextant (EPL v1.0)
Dear all,
This is a friendly reminder that we will have the weekly meeting of the ALTO
design team at 9:00 am US EST (3:00 pm CET and 10:00 pm Beijing Time) on
Tuesday, February 15, 2022.
To help refresh our memory, below is a short summary of the discussion we had
last week.
1. Luis led the
Dear all,
This is a friendly reminder that we will have the ALTO weekly meeting at 9:00
am US EST (3:00 pm CET and 10:00 pm Beijing Time) on Tuesday, February 8, 2022.
Below is a brief summary of the discussions in the last meeting just to help
refresh our memory:
1. Richard and Roland
Hi Roman,
That is really great! Thanks a lot!
Best,
Kai
-Original Messages-
From:"Roman Danyliw"
Sent Time:2022-02-03 08:55:17 (Thursday)
To: "kai...@scu.edu.cn"
Cc: "alto@ietf.org" , "alto-cha...@ietf.org"
, "draft-ietf-alto-path-vec...@ietf.org"
, "The IESG" , "Qin Wu"
Hi Roman,
We have just submitted a new version of path vector which uses the proposed
text in our discussion. We hope this addresses your comments well. Thanks a lot
for the guidance and suggestions!
Hi Roman,
Thanks a lot! We will revise the draft and submit a new version soon.
Best,
Kai
-Original Messages-
From:"Roman Danyliw"
Sent Time:2022-01-28 22:40:51 (Friday)
To: "kai...@scu.edu.cn"
Cc: "draft-ietf-alto-path-vec...@ietf.org"
, "alto@ietf.org" , "The
IESG" ,
Hi Roman,
Thanks for the comment.
Regarding the DRM issue, we are mostly following the guidance of RFC 7971 and
7285.
RFC 7971 (ALTO deployment considerations) has discussed the issue of
information leak and RFC 7285 suggests that encryption only protects the
end-to-end
Dear all,
This is a friendly reminder that we will have the ALTO weekly meeting at 9:00
am US EST (3:00 pm CET and 10:00 pm Beijing Time) on Tuesday, January 25, 2022.
To refresh our memory, here is a brief summary of the discussion we had last
week.
1. Richard and Roland presented their
Dear all,
This is a friendly reminder that the ALTO weekly meeting will be held at 9:00
am US EST (3:00 pm CET and 10:00 pm Beijing Time) on Tuesday, January 18, 2022.
To help us refresh our memories, below are some topics discussed in the last
meeting:
1. Richard and Roland are leading the
Dear all,
This is a friendly reminder that we will have the ALTO weekly meeting at 9:00
am US EST (3:00 pm CET and 10:00 pm Beijing Time) on Tuesday, January 11, 2022.
Here are a few points that we have discussed last week to help us all refresh
our memory:
- For IETF 113, the main focus
Hi Roman and all,
Happy New Year!
We have submitted a new version of the Path Vector draft (-20) [1]. The
proposed texts are integrated in Section 11. Please let us know if they address
you comments.
Best,
Kai
[1]
Dear all,
Happy New Year!
This is a friendly reminder that we will have the ALTO weekly meeting at 9:00
am US EST (3:00 pm CET and 10:00 pm Beijing Time) on Tuesday, Jan 4, 2022.
Agenda:
- Follow-ups of IESG reviews on WG documents
- Planning for IETF 113
Bridge:
Dear all,
This is a friendly reminder that we will have the ALTO weekly meeting at 9:00
am EST (3:00 pm CET and 10:00 pm Beijing Time) on Tuesday, Dec 21, 2021.
Agenda:
- GradientGraph and its applications (G2 team)
- IETF WG drafts and new charter items
Bridge:
Hi Francesca,
Thanks for the review and we are sorry for the late response. Somehow
it went into the spams.
We have changed the reference to RFC 7540 to draft-ietf-httpbis-http2bis
as suggested. Thanks for the comment!
Best,
Kai
-Original Messages-
From: "Francesca Palombini via
Hi Roman,
Please find below for the proposed text for Sec 11. Please let us know if it
makes sense and any further comments or suggestions are welcomed!
Best,
Kai
-Original Messages-
From:kai...@scu.edu.cn
Sent Time:2021-12-06 22:53:04 (Monday)
To: "Roman Danyliw"
Cc: "The
Dear all,
This is a friendly reminder that we will have the ALTO weekly meeting at 9:00
am UST (3:00 pm CET and 10:00 pm Beijing Time) on Tuesday, Dec 14, 2021.
Agenda:
- Editorial sessions for WG drafts (Resolve DISCUSS)
Bridge:
https://yale.zoom.us/my/yryang
Feel free to let
Welcome Med! Looking forward to working with you!
Thanks Jan!
Best,
Kai
-Original Messages-
From:"LUIS MIGUEL CONTRERAS MURILLO"
Sent Time:2021-12-07 21:31:06 (Tuesday)
To: "Qin Wu" , "Martin Duke"
, "IETF ALTO"
Cc:
Subject: Re: [alto] New chair!
Congrats Med!
and
Hi Roman,
Thanks for the review and please see the replies inline.
> -Original Messages-
> From: "Roman Danyliw via Datatracker"
> Sent Time: 2021-11-30 23:33:54 (Tuesday)
> To: "The IESG"
> Cc: alto-cha...@ietf.org, draft-ietf-alto-path-vec...@ietf.org, alto@ietf.org
> Subject:
Dear all,
This is a friendly reminder that we will have the ALTO weekly meeting at 9:00
am US EST (3:00 pm CET and 10:00 pm Beijing Time) on Tuesday, December 7, 2021.
Agenda:
- OpenNetLab & BWE Challenge (Zhixiong Niu)
- IESG telechat DISCUSS issues
Bridge:
Hi Murray,
Thanks for the review and please see the replies inline.
Best,
Kai
> -Original Messages-
> From: "Murray Kucherawy via Datatracker"
> Sent Time: 2021-12-06 13:46:28 (Monday)
> To: "The IESG"
> Cc: alto-cha...@ietf.org, draft-ietf-alto-path-vec...@ietf.org, alto@ietf.org
>
Hi Erik,
Thanks for the comments and please see the replies inline.
Best,
Kai
> -Original Messages-
> From: "Erik Kline via Datatracker"
> Sent Time: 2021-12-02 13:30:33 (Thursday)
> To: "The IESG"
> Cc: alto-cha...@ietf.org, draft-ietf-alto-path-vec...@ietf.org, alto@ietf.org
>
Hi Éric,
Thanks for the comments and please see the replies inline.
Best,
Kai
> -Original Messages-
> From: "Eric Vyncke (evyncke)"
> Sent Time: 2021-12-01 23:34:50 (Wednesday)
> To: "kai...@scu.edu.cn"
> Cc: "The IESG" , "draft-ietf-alto-path-vec...@ietf.org"
> ,
Hi Tim,
Thanks for the review and please see the responses inline.
Best,
Kai
> -Original Messages-
> From: "Tim Chown via Datatracker"
> Sent Time: 2021-12-01 19:44:33 (Wednesday)
> To: ops-...@ietf.org
> Cc: draft-ietf-alto-path-vector@ietf.org, last-c...@ietf.org,
>
Hi Éric,
Thanks for the review and please see the responses inline.
Best,
Kai
-Original Messages-
From: "Éric Vyncke via Datatracker"
Sent Time: 2021-11-29 18:59:54 (Monday)
To: "The IESG"
Cc: draft-ietf-alto-path-vec...@ietf.org, alto-cha...@ietf.org,
alto@ietf.org,
Dear all,
This is a friendly reminder that the ALTO weekly meeting will be held at 9:00
am US EST (3:00 pm CET and 10:00 pm Beijing Time) on Tuesday, November 30, 2021.
Agenda:
- Design session for new transport
- Collaboration discussion (G2/PANRG/...)
Bridge:
Hi Sabine,
OK. Below is the updated agenda:
- Discuss the review of Eric on Unified properties and Performance metrics
- Design sessions for new charter items:
- ALTO new transport
- ALTO OAM
Best,
Kai
-Original Messages-
From:"Randriamasy, Sabine (Nokia -
Dear all,
This is a friendly reminder that we will have the ALTO weekly meeting at 9:00
am US EST (3:00 pm CET and 10:00 pm Beijing Time) on Tuesday, November 23, 2021.
Agenda:
- Design sessions for new charter items:
- ALTO new transport
- ALTO OAM
Bridge:
Dear all,
This is a friendly reminder that we will have the ALTO weekly meeting at 9:00
am US EST (3:00 pm CET and 10:00 pm Beijing Time) on Tuesday, November 16, 2021.
Agenda:
- Planning for new charter items (deployment, OAM, transport, etc.)
Bridge:
Hi Luis,
Yes, it should be 2:00 pm CET. Sorry for the confusion.
Best,
Kai
2021-11-02 16:21:25"LUIS MIGUEL CONTRERAS MURILLO"
wrote:
Hi Kao,
Last weekend we had in Europe the time adjustment, so I guess that the new time
for the meeting in Europe is 14:00 CET instead of 15:00
Dear all,
This is a friendly reminder that we will have the ALTO weekly meeting at 9:00
am US EST (3:00 pm CET and 9:00 pm Beijing Time) on Tuesday, November 2, 2021.
Agenda:
- Preparation for IETF 112
Bridge:
https://yale.zoom.us/my/yryang
If you want to put a new topic to the
Hi Tim,
I'm really sorry about the wrong spelling. My apologies.
Best,
Kai
-Original Messages-
From: kai...@scu.edu.cn
Sent Time: 2021-10-27 11:40:01 (Wednesday)
To: "Tim Chown"
Cc: "draft-ietf-alto-path-vector@ietf.org"
, "last-c...@ietf.org"
, "ops-...@ietf.org" ,
Dear Time,
We have just submitted a revision of the Path Vector draft (-19). Below
are the links to the latest revision and the diffs. Please see inline
the pointers to the proposed changes to the comments, in brief:
1. More detailed examples are given in Sec 4.2:
a. what is the role of ALTO
Dear Suresh,
Please see below our latest revision of the Path Vector draft (-19). We have
added IPv6 examples for each endpoint-based example. We hope this addresses
your comments.
Draft:
https://www.ietf.org/archive/id/draft-ietf-alto-path-vector-19.html
Diffs:
Dear WG members and reviewers,
We have just submitted a new version of the Path Vector draft. This revision
addresses the comments in the Last Call reviews, most notably:
1. Add IPv6 examples
2. Change the "content-id" format in multipart messages to conform to RFC 2387
5322
3. Add
Hi Martin,
Sorry for the late response. I had a discussion with Qin yesterday on the
responsibility of designated experts. I think I can do it.
Best,
Kai
2021-10-27 03:18:35"Martin Duke" wrote:
Kai, does this work for you?
Any other nominations?
On Mon, Oct 25, 2021 at 10:57 PM Qin Wu
1 - 100 of 192 matches
Mail list logo
