e (of what has been done) such as ALTO and maybe
other services such as control plane verification. Data export is indeed
expensive and hence should be a major consideration in such a route state
(RS) protocol, if designed. Make sense?
Thank you so much!
Richard
>
> Cheers,
>
&g
n/wp-content/uploads/sites/5/2022/12/Telefonica-Third-data-subjects-Privacy-Policy.pdf>
> .
>
> Informamos que o responsável pelo tratamento dos seus dados é a entidade
> do Grupo Telefónica vinculada ao remetente, a fim de manter o contato
> professional e administrar a relação esta
FYI. Any comments or suggestions are greatly appreciated.
-- Forwarded message -
From:
Date: Mon, Jul 10, 2023 at 9:20 PM
Subject: New Version Notification for draft-yang-alto-multi-domain-03.txt
To: Y. Richard Yang , Annie Gu , Danny
Lachos , Ingmar Poese , Jordi Ros
Giralt
>
>
>
> Best regards
>
>
>
> Luis
>
>
>
> *De:* Qin Wu
> *Enviado el:* jueves, 6 de julio de 2023 4:18
> *Para:* Danny Lachos ; LUIS MIGUEL CONTRERAS MURILLO <
> luismiguel.contrerasmuri...@telefonica.com>; Y. Richard Yang <
> y...@cs.yale.edu>;
aracterizing the cost map. I think this can be an interesting work to be
> discussed by the WG in future work.
>
>
>
> Best regards
>
>
>
> Luis
>
>
>
> *De:* Qin Wu
> *Enviado el:* jueves, 6 de julio de 2023 4:52
> *Para:* Y. Richard Yang ; LUIS MIGUEL CONT
On Tue, Jun 27, 2023 at 8:33 AM Y. Richard Yang wrote:
> Hi Luis,
>
> Thank you so much for starting this thread on Topic B. I feel that this is
> a crucial topic for the WG to investigate. Please see below.
>
> On Mon, Jun 26, 2023 at 5:18 PM LUIS MIGUEL
Hi Luis,
On Tue, Jun 27, 2023 at 8:43 AM LUIS MIGUEL CONTRERAS MURILLO <
luismiguel.contrerasmuri...@telefonica.com> wrote:
> Hi Richard,
>
>
>
> Thanks for your comments.
>
>
>
> Just a small comment on security. Certainly we are addressing two
> dimensions in ALTO regarding security, at least
s respect?
>
>
>
> Of course for those interested on the topics above, please comment.
>
>
>
> Thanks in advance
>
>
>
> Best regards
>
>
>
> Luis
>
>
>
> *De:* alto *En nombre de * Y. Richard Yang
> *Enviado el:* miércoles, 21 d
UFxUY/edit?usp=sharing
>
> Thanks,
> Jordi
> ----------
> *From:* alto on behalf of Y. Richard Yang <
> y...@cs.yale.edu>
> *Sent:* Wednesday, June 21, 2023 1:47
> *To:* IETF ALTO
> *Subject:* [alto] June 20, 2023 meeting minutes and discussion working
> links
>
>
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).
--
--
=========
| Y. Richard Yang|
| Professor of Computer Science |
| htt
Hi Jensen, all,
Thank you for authoring the OAM document. It clearly is a massive effort on
an important task that helps with ALTO development. In the first part of
this review, I will focus on early text and structure. I will review the
yang model details soon.
High-level structure: My
Hi Sabine,
On Thu, Mar 23, 2023 at 8:58 AM Sabine Randriamasy (Nokia) <
sabine.randriam...@nokia-bell-labs.com> wrote:
> Hi Med, Qin and ALTO WG
>
>
>
> Thanks a lot for initiating this discussion and your options proposal.
>
>
>
Hi all,
Some of us have made additional updates to the ALTO deployment wiki:
https://wiki.ietf.org/en/group/ALTO/deployment
Any feedback and suggestions will be appreciated.
Thanks,
Richard
___
alto mailing list
alto@ietf.org
Hi Med, Qin,
Thank you for initiating the discussion of this important topic.
At a high level, my understanding of the proposed decision-making
methodology is the following: let's have an assessment (it is called
rational in the email and I will use the same term) of the current state
and
, Mar 13, 2023 at 6:44 PM
Subject: New Version Notification for draft-yang-alto-multi-domain-01.txt
To: Y. Richard Yang , Mario Lassnig
A new version of I-D, draft-yang-alto-multi-domain-01.txt
has been successfully submitted by Y. Richard Yang and posted to the
IETF repository.
Name
Hi All,
With the interim meeting behind us, I was suggested to start the discussion
of the multi-domain use case, which is a use case driven by a real setting.
Details: A motivation use case of multi-domain ALTO is the LHCONE setting,
which is an L3VPN consisting of multiple networks [1]. Given
be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
>
> Thank you.
>
> ___
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
--
--
===
Hi WG, Adrian, Qin, Jordi, all,
Thank you so much for the wonderful reviews of the new alto transport
design. Roland, Lachlan, Kai and I are taking a final pass and will go over
it on Thursday during the interim meeting.
One key issue that we want to discuss, in this specific thread, is a
Hi all,
It turns out that the ALTO session is at the same time as the Rucio session
when we (Mario/Mihai/Jordi/Harvey/Kai) will present the ALTO/TCN update (
https://indico.cern.ch/event/1185600/timetable/#20221110.detailed). For
those who are not familiar with Rucio/FTS, they are the main data
Looks like that webex meeting does not work?
Richard
On Tue, Nov 8, 2022 at 9:11 AM Jordi Ros Giralt
wrote:
> Let's meet at the Ground floor of the hotel's West Wing. We will find a
> place to talk. (The two only available rooms for side meetings are booked).
>
> For online attendees, let's
90fe06a-f028-4de4-b117-379d0c4badb5=98e9ba89-e1a1-4e38-9007-8bdabc25de1d=19_meeting_ZDUyZmNmYWUtNzdmMi00YTRhLTg4M2ItZTQ1NDBkMDNmMTM2@thread.v2=0=en-US>
>
>
> _______
> alto mailing list
> alto@ietf.org
> https://www.iet
t;
> Come by to our table and we look forward to chatting with you.
>
> Jordi
> ___
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
--
--
=
| Y. Richar
Hi all,
Sorry to spam the list with one more work-in-progress update email. But
since it is an important, chartered task of the WG, we would like to hear
your feedback and invite more to be involved to work together.
The openalto.org team has two main objectives: (1) design and implement a
ctures
> Authors : Roland Schott
> Y. Richard Yang
> Kai Gao
> Jingxuan Jensen Zhang
> Filename: draft-ietf-alto-new-transport-02.txt
> Pages : 22
> Date
Hi WG,
Sorry for the spam. Deployment is another topic which we will discuss in
the coming weekly meeting. Below is a quick email update to save update
time so that we can focus on discussions at the meeting.
There were 3 meetings yesterday to push the effort forward: an early
meeting with
Hi WG,
Updating transport mechanisms is an WG item and we are getting close to the
milestone (in September). Hence, the authors are finalizing the updates as
soon they can, and the topic will be a main item for the coming weekly
meeting. It was suggested that we send out some main points for
Hi Qin, all,
This is a good progress indeed. I share with you that many WG members
including both the authors and many others have made contributions in the
process. A big thank you!
Richard
On Fri, Sep 23, 2022 at 9:13 PM Qin Wu
wrote:
> Congratulation to all authors and other people who
ard
On Mon, Sep 12, 2022 at 10:50 PM Y. Richard Yang wrote:
> Hi all,
>
> During the weekly meeting last week, we went over the details when
> deploying ALTO in a multi-domain setting, say the FTS/Rucio setting
> supporting the TCN deployment [1]. Below is the endpoint cost se
Hi all,
Sorry to spam the mailing list with a second email message.
During the weekly meeting last week, we also discussed about the progress
and planning for the testing and deployment of TCN, which uses alto and is
based on our past progress. It was suggested that we post the planning (in
Hi all,
During the weekly meeting last week, we went over the details when
deploying ALTO in a multi-domain setting, say the FTS/Rucio setting
supporting the TCN deployment [1]. Below is the endpoint cost service (ECS)
case, and it was suggested that we post it to the WG mailing list to update
Hi all,
Since many of us are away this week, may I suggest that we cancel the WG
weekly meeting this Tuesday (Aug. 23)?
As a small advertisement for Luis, the SIGCOMM network-application
integration (NAI'22) workshop chaired by Lui is tomorrow (Aug. 22, 2022).
It has an extremely interesting
I was at the presentations by Luis. Excellent presentation and great Q!
We should share the questions and answers back to this mailing list.
Richard
On Fri, Jul 29, 2022 at 11:52 AM wrote:
> Hi all,
>
>
>
> The slides that are presented by Luis can be seen at:
>
Thanks for the update, Jordi. So we just meet at Maggiano's Little Italy at
7:30.
For some of you who want to stop by to see the hackathon demo, Mahdi and
some others will be at the Hackathon Happy Hour from 5:30-6:30 pm. Feel
free to stop by as well.
Richard
On Mon, Jul 25, 2022 at 4:39 AM
ALTO, FTS would find whether it may increase or should
> decrease traffic involving that RSE
>
> This maps directly to what we see in production: FTS can hit some sites
> too hard.
> Any extra knowledge FTS gets on this aspect would allow it to improve.
>
> Best Regards,
> M
On Thu, Jul 21, 2022, 23:00 Mark Nottingham wrote:
>
>> Hi Richard,
>>
>> I'm just going to give some impressions while reading this, FWIW.
>>
>> > On 22 Jul 2022, at 6:20 am, Y. Richard Yang wrote:
>> >
>> > Hi Mark, Martin, Spencer,
>&g
022, at 6:20 am, Y. Richard Yang wrote:
> >
> > Hi Mark, Martin, Spencer,
> >
> > First, thank you so much for the reviews. Sorry for the delay in
> responding asap, due to summer and travel.
> >
> > One common comment we see from all three of you, in different te
Hi Mark,
Thank you so much for the feedback. Could you please see
https://mailarchive.ietf.org/arch/msg/alto/CBRGLTekers9PXQ5EE2MtMywMgE/
for an attempt to formulate a generic problem.
As soon as we have a discussion on the generic issue, we will update the
document accordingly, for example, to
Hi Martin,
Sorry that I did not include you in the previous email--auto completion of
email address included a different Martin :-( My apologies. Please kindly
see this message:
https://mailarchive.ietf.org/arch/msg/alto/CBRGLTekers9PXQ5EE2MtMywMgE/
Please see below for more comments.
On Mon,
Hi Mark, Martin, Spencer,
First, thank you so much for the reviews. Sorry for the delay in responding
asap, due to summer and travel.
One common comment we see from all three of you, in different texts, is
essentially on the service model of the current document (
something to discuss with.
>
Yes. See above. Let’s write the draft soon.
Richard
>
> A preprint of the W2 paper is available at
> https://zilimeng.com/papers/zhuge-sigcomm22.pdf for your information.
> We'll also be highly appreciated if there are any comments or feedback.
Hi all,
During the weekly ALTO meeting today, we discussed the coming hackathon and
Qin suggested that we send an update to the mailing list on the FTS+ALTO
project, and here is the update:
- In short, if you want to work on ALTO integration with production, open
projects, this can be a
his information.
>
>
>
> Just out of curiosity, are the proposed extensions currently discussed in
> the 3GPP?
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* alto *De la part de* Y. Richard Yang
> *Envoyé :* mardi 19 juillet 2022 20:14
> *À :* IETF ALTO
>
on behalf of Tuesday meeting team
-- Forwarded message -
From:
Date: Mon, Jul 11, 2022 at 2:14 PM
Subject: New Version Notification for
draft-huang-alto-mowie-for-network-aware-app-04.txt
To: Y. Richard Yang , Gang Li <
ligan...@chinamobile.com>, Sabine Randr
Hi ALToers, and experts on HTTP/2,
As we make progress on the transport document (
https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/), we have
one issue to discuss: stream management to take advantage of this HTTP/2
feature. Can we kindly ask that members read Section 8 of the
Hi ALTO group,
We will meet with the PBE-CC team (Kyle Jamieson, Jen Rexford, and Yaxiong
Xie, all from Princeton) tomorrow at 9:00 AM US ET to discuss the
possibility of exposing more network information for applications.
The direct relevant paper is:
https://arxiv.org/abs/2002.03475
Another
Hi all,
Some of us will make a presentation on ALTO at the DOMA (Data Organization,
Management and Access) Group of WCLG (World-Wide LHC Computing Grid) on
Wednesday. The goal is to further (1) drive the implementation of openalto
and (2) integrate ALTO into Rucio and FDS. Anyone with an interest
Hi Éric,
Thank you so much for the update.
For the comment on IPv4: we had some discussions on how to address it. In
earlier documents, we used a mix of IPv4 and IPv6 addresses (e.g., an
earlier version of RFC7285 used a mix of ipv4 and ipv6 in examples such as
l2=draft-ietf-alto-performance-metrics-26.txt
>
> *发件人:* Zaheduzzaman Sarker [mailto:zaheduzzaman.sar...@ericsson.com]
> *发送时间:* 2022年3月2日 18:30
> *收件人:* Y. Richard Yang
> *抄送:* Qin Wu ; The IESG <
> i...@ietf.org>; alto-cha...@ietf.org;
> draft-ietf-alto-performance-metr
Hi ALTOers,
Several of us (Roland, Kai, me) are working on ALTO transport, and our plan
is to update a relatively complete version by the draft deadline of March 7
(one week from today).
Here is a brief summary of current design points:
- It will be RESTful, as the current design
- It will
2021 at 9:55 AM Y. Richard Yang wrote:
> Hi Eric, Martin, all,
>
> The authors agree that 8312bis should be a normative reference, and it is
> in -v22, which we will upload soon.
>
> Thanks,
> Richard
>
> On Tue, Dec 21, 2021 at 8:52 AM Qin Wu 40huawei@dmarc.ietf
Hi Zaheduzzaman,
We have posted the latest version of the document:
https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-24
Could you please take a look to see if all of your comments are addressed?
In particular,
- We checked and made sure that the normative references are
lable"},
> "endpoints": {
> "srcs": [ "ipv4 : 192.0.2.2" ],
> "dsts": [
>"ipv4:192.0.2.89",
>"ipv4:198.51.100.34"
> ]
> }
>}
>
> FP: JSON doe
in Kaduk wrote:
> Hi Richard,
>
> On Tue, Dec 21, 2021 at 08:13:02PM -0500, Y. Richard Yang wrote:
> > Hi Ben,
> >
> > Thank you so much for the wonderful, fast, thorough reviews! I understand
> > that Qin has already sent a reply and please see below.
>
> Ye
, Nov 30, 2021 at 9:27 PM Y. Richard Yang wrote:
> Hi Lars,
>
> Just posted an updated version, and a diff from the previous version is
> available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-20
>
> Thanks!
> Richard
>
> On Tue, Nov
Hi Ben,
Thank you so much for the wonderful, fast, thorough reviews! I understand
that Qin has already sent a reply and please see below.
On Mon, Dec 20, 2021 at 7:58 PM Benjamin Kaduk via Datatracker <
nore...@ietf.org> wrote:
> Benjamin Kaduk has entered the following ballot position for
>
> -- Section 4.1 --
> Is the intent of ALTO to only work for TCP and not for other transport
> protocols ? I.e., is QUIC out of scope ?
>
> -- Section 4.2.3 --
> Where are those 'tunnels
;
> Ben
>
> On Mon, Dec 06, 2021 at 01:25:20PM +, Qin Wu wrote:
> > Hi, Ben:
> > -邮件原件-
> > 发件人: alto [mailto:alto-boun...@ietf.org] 代表 Benjamin Kaduk
> > 发送时间: 2021年12月4日 6:30
> > 收件人: Qin Wu
> > 抄送: draft-ietf-alto-performance-metr...@ietf.
his communication in error and then delete
>> it.
>>
>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
>> destinatário, pode conter informação privilegiada ou confidencial e é para
>> uso exclusivo da pessoa ou entidade de destino. Se
Hi Martin,
Add the WG, so that we can hear others' comments as well. Please see below
for a small addition.
On Fri, Dec 3, 2021 at 1:46 PM Y. Richard Yang wrote:
> Martin,
>
> Thanks a lot for the update! A quick reply on performance metrics.
>
> On Fri, Dec 3, 2021 at 1:22
Hi Francesca,
Thank you so much for the review! Please see inline.
On Wed, Dec 1, 2021 at 4:57 PM Francesca Palombini via Datatracker <
nore...@ietf.org> wrote:
> Francesca Palombini has entered the following ballot position for
> draft-ietf-alto-performance-metrics-20: Discuss
>
> When
Hi Lars,
Just posted an updated version, and a diff from the previous version is
available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-performance-metrics-20
Thanks!
Richard
On Tue, Nov 30, 2021 at 8:49 PM Y. Richard Yang wrote:
> Hi Lars,
>
> Thanks for the review! Please
tion
> (apart fr
> >
> The usual collocation for "independent" is "of", not "from". Did you mean
> "independent of"?
>
> Section 3.4.3. , paragraph 6, nit:
> > imation
> some promotional material for IETF, and it would be a good testimonial.
>
> Thanks,
> Martin
> ___
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
--
--
==========
Hi Christian,
We made two changes to address your comments. Please see below.
>
> > > * Allowing decimals into the cost metric identifier introduces a dot
> which
> > > is reserved as per RFC7285 Section 10.6.
> >
> > Yes. Correct. From the grammar above, we made sure that we would not
> >
Hi Christian,
On Tue, Oct 19, 2021 at 2:54 AM Christian Amsüss
wrote:
> Hello Richard,
>
> On Mon, Oct 18, 2021 at 03:43:50PM -0400, Y. Richard Yang wrote:
> > Good comment. The document gives the high-level grammar (1 line) at the
> > beginning of Sec. 2.2.
> > It
Dear all,
It looks that we have some confusion or we have scheduled two
meetings, first 9-10 (this one), and then 10-11 (G2).
Richard
On Mon, Oct 18, 2021 at 9:49 PM wrote:
> Dear all,
>
>
> This is a friendly reminder that we will have the weekly ALTO meeting* on
> 9:00 am US EST (3:00 pm
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
--
--
=
| Y. Richard Yang|
| Professor of Computer Science |
| http://www.cs.yale.edu/~yry/|
=
___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto
Hi Christian,
Thank you so much for the review. Please see below.
On Mon, Oct 18, 2021 at 10:02 AM Christian Amsüss via Datatracker <
nore...@ietf.org> wrote:
> Reviewer: Christian Amsüss
> Review result: Ready with Issues
>
> ## Summary for the IoT Directorate
>
> This document extends the
Dear ALTOers,
The weekly meeting tomorrow Oct. 19, 2021 is one hour later than the
traditional time. The goal of the meeting is to discuss collaboration
between ALTO and G2.
Time: Oct. 19 from 10-11 AM US ET
Format: Hybrid (G2 team + Richard) at Yale campus + Zoom (
_____
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
--
--
=
| Y. Richard Yang|
| Professor of Computer Science |
| http://www.cs.yale.edu/~yry/|
=
___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto
Hi Lars,
I saw your comment and have to chime in.
I have to respectfully disagree with your assessment: "Overall, I remain
unconvinced that there is sufficient work/interest in this space to warrant
a chartered WG." I am not sure if you attended the NAI@SIGCOMM'21 Workshop
yesterday. There was
://conferences.sigcomm.org/sigcomm/2021/workshop-nai.html
We look forward to seeing many of you.
Richard
--
--
=
| Y. Richard Yang|
| Professor of Computer Science |
| http://www.cs.yale.edu/~yry
TO Performance Cost Metrics
Authors : Qin Wu
Y. Richard Yang
Young Lee
Dhruv Dhody
Sabine Randriamasy
Luis Miguel Contreras
Filename: d
Hi Martin,
Thanks for the quick feedback. Please see below.
On Mon, Apr 5, 2021 at 11:03 AM Martin Duke wrote:
> Hi Richard,
>
> Where needed, responses inline.
>
> On Fri, Apr 2, 2021 at 6:18 PM Y. Richard Yang wrote:
>
>> - Sec 2.1. The cost-source mod
Hi Martin,
On Tue, Mar 30, 2021 at 2:24 PM Martin Duke wrote:
> Sorry for the fragmented review, but there are a couple of more issues:
>
> - The authors should do a review of all lower-case occurrences of must,
> should, may, and recommended. At least a few of them should be capitalized
> to
Hi Martin,
Thank you so much for the wonderful review. Please see below.
On Mon, Mar 29, 2021 at 2:35 PM Martin Duke wrote:
> Hello authors,
>
> Thank you very much for writing this draft. It is clearly a useful
> extension to ALTO and is quite clearly written, even to someone who is not
> a
Hi Sabine, Qin,
Good discussions.
I support the use cases of the design direction. One suggestion is to look
at the design in a slightly abstract, general framework. In particular, the
abstract framework looks like this to me:
- Ve: A set of "volatile" (ephemeral) variables; Ve tends to be
e network
(ALTO) server can provide highly valuable information, but the client may
not obtain it easily (due to more limited state access, limited computation
power, the latency involved, ...)
Now back to your two use cases, I see that they can be supported using a
single mechanism (i.e., language gramma
ossa senhoria o destinatário
> indicado, fica notificado de que a leitura, utilização, divulgação e/ou
> cópia sem autorização pode estar proibida em virtude da legislação vigente.
> Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
> imediatamente por esta
Dear all,
I renamed the generic email Subject line so that we may focus this thread
on item 2.
Here are two quick comments related with this thread, and I will go to more
details as soon as I can.
1. ALTO SSE appears to be a quite useful service and it helps to adapt it
to use more modern
PM 刘鹏 wrote:
>
>> Hi Richard,
>>
>> Thank you. please see my reply inline below.
>>
>>
>> Peng Liu | 刘鹏
>> China Mobile | 移动研究院
>> mobile phone：13810146105
>> email: * liupeng...@chinamobile.com *
>>
>>
>> 发件人: Y. Richard Y
Dear all,
FYI: Our proposal for the second ACM SIGCOMM NAI Workshop during ACM
SIGCOMM'21 has been accepted. Please do consider submission to this highly
relevant venue.
Call for Submissions: ACM SIGCOMM NAI’21
The Second ACM SIGCOMM Workshop on Network-Application Integration/CoDesign
- Is the distribution of the information allowed by the operator of the
> network? Does the exposure of the information introduce privacy and
> information leakage concerns?
>
>
>
> Issues related to the specific content exchanged in systems that make use
&g
the IETF.
>
> Title : ALTO Performance Cost Metrics
> Authors : Qin Wu
> Y. Richard Yang
> Young Lee
> Dhruv Dhody
> Sabine Randriamasy
therefore the
> metric identifier can be used without as suffix.
>
> I think your proposed change makes sense to me.
>
>
>
> -Qin
>
> *发件人:* Jensen Zhang [mailto:jingxuan.n.zh...@gmail.com]
> *发送时间:* 2021年1月12日 15:36
> *收件人:* Qin Wu
> *抄送:* IETF ALTO ; Y. Richard Yang ; K
Hi Jan, Qin,
Please see below.
On Tue, Jan 12, 2021 at 1:43 AM Qin Wu wrote:
> Hi, Jan and authors of draft-ietf-alto-performance-metrics:
> -邮件原件-
> 发件人: alto [mailto:alto-boun...@ietf.org] 代表 Jan Seedorf
> 发送时间: 2020年11月12日 6:32
> 收件人: alto@ietf.org
> 主题: [alto] Normative References
> “metric value” and “metric’s value”
>
> Are used inconsistently, I suggest to change metric’s value into metric
> value.
>
> I hope these comments can be addressed before being moved forward.
>
>
>
> -Qin
>
> *发件人:* alto [mailto:alto-boun...@ietf.org] *代表 *Y. R
Hi all,
I have to skip the meeting this morning.
One quick update is on the first agenda item: an updated version of
performance metrics is just posted and we believe that it has addressed all
of the review comments by Danny and Jensen.
Richard
On Mon, Jan 11, 2021 at 10:36 AM wrote:
> Dear
any networks.
> 3. is there any ALTO protocol extension? E.g., network map
> extension, Cost map extension, or property map extension?
>
>
> Not sure I fully understand the question. Some generic extensions (e.g.,
the one by Sabine) will extend cost map and property map. Is t
Dear ALTOers,
The chairs suggested that we collect all of the paragraphs into a single
document, and hence we have created the shared document for our use today:
https://docs.google.com/document/d/1O0x_AaegY9RU9bAVjm9wfWlel-vjOVFlIi9stmz9VXw/edit?usp=sharing
The document will be a live document
at
>
> https://mailarchive.ietf.org/arch/msg/alto/9CAIL0hEW4cy90iVeOJn_gYO84o/
>
> we miss item 2 and 3.
>
>
>
> -Qin
>
> *发件人:* alto [mailto:alto-boun...@ietf.org] *代表 *Y. Richard Yang
> *发送时间:* 2020年11月17日 11:02
> *收件人:* Kai Gao
> *抄送:* alto-weekly-meet...@goog
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
--
--
=
| Y. Richard Yang|
| Professor of Computer Science |
| http://www.cs.yale.edu/~yry/|
=
___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto
Hi Sabine,
Thanks a lot for the paragraph describing a potential recharter item.
I have three quick comments, according to my understanding:
- [C1] The extension will focus on "additional" information such as
conditions/context on entities (e.g., extend unified properties) and path
costs (e.g.,
and then during the meeting later this week.
Any comments are highly welcome.
Richard
On Thu, Nov 12, 2020 at 7:10 PM Y. Richard Yang wrote:
> Dear ALTOers,
>
> Please see attached an updated version of the slides intended to
> contribute to the multidomain item. The slides are team
the initial
design to make clear the problem and feasibility.
Thanks!
Richard
On Tue, Nov 10, 2020 at 4:12 PM Y. Richard Yang wrote:
> Dear ALTOers,
>
> One item which we discussed this morning during our weekly meeting is ALTO
> extension to multi-domain settings. Please
Hi Vijay,
- I believe that there was an implementation of unified properties by Wendy
Roome. But it is for an earlier version, not the latest one which we just
posted.
- I understand that there was an implementation of path vector used in
super computing demonstration; but it was for an earlier
ove on to other
> things.
>
> See you next week,
> Martin
> ___
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
--
--
=
| Y. Richard Yang|
| Professor o
Dear ALTOers,
One item which we discussed this morning during our weekly meeting is ALTO
extension to multi-domain settings. Please see attached for the deck of
slides that we used.
At a high level, it tried to extend ALTO into a multi-domain setting for
one of the most basic ALTO services ---
Hi Vijay, Jan,
Wonderful suggestion and organization!
As a regular attendee of the Wed (lately it changed to Tuesday as well)
meetings, I agree that the meetings members should focus on making progress
on the charter text and . We will send more updates soon.
Thanks again!
Richard
On Thu, Nov
Dear ALTOers,
During the weekly meeting yesterday, one issue discussed is an extension of
ALTO to multidomains. This is a relevant issue and investigated by Ingmar,
Sebastian, Kai and Qiao. Below is a proposal to get the WG feedback.
Problem: Consider a basic ALTO service say the endpoint-cost
1 - 100 of 469 matches
Mail list logo
