Re: [alto] Proposed Agenda for Interims #2-5

[Jordi Ros Giralt]

Hi Qiufang,

Many thanks for the quick turnaround and update of your draft.

I am adding your presentation to the agenda for the next ALTO weekly meeting 
this coming Tuesday. Thanks for presenting your work.

B/R,
Jordi

From: maqiufang (A) 
Sent: Saturday, May 6, 2023 4:50
To: Jordi Ros Giralt ; 
luismiguel.contrerasmuri...@telefonica.com 

Cc: IETF ALTO ; draft-xie-alto-l...@ietf.org 

Subject: RE: [alto] Proposed Agenda for Interims #2-5


WARNING: This email originated from outside of Qualcomm. Please be wary of any 
links or attachments, and do not enable macros.

Thank you Jordi for doing the proofreading, much appreciated. I’ve uploaded a 
new version (https://www.ietf.org/archive/id/draft-xie-alto-lmap-02.txt) with 
your annotations incorporated. And also see repo 
https://github.com/QiufangMa/alto-lmap for this document. Happy to work with 
you and receive your further comments via either Github or mailing list.



Yes, I would be glad to present during next Tuesday’s ALTO weekly meeting, 
thank you for arranging this!



Best Regards,

Qiufang



From: Jordi Ros Giralt [mailto:j...@qti.qualcomm.com]
Sent: Friday, May 5, 2023 10:15 PM
To: maqiufang (A) ; 
luismiguel.contrerasmuri...@telefonica.com
Cc: IETF ALTO ; draft-xie-alto-l...@ietf.org
Subject: Re: [alto] Proposed Agenda for Interims #2-5



Hi Qiufang,



Thank you for reviving your ALTO/LMAP draft and for incorporating the LMAP data 
source in the ALTO data sources document.



I agree with Luis and your comments below.



I did a pass on your draft and made some annotations, see the attached doc. 
Would you be able to generate an updated version and push it to the 
datatracker? If your draft is in a github repo, I can propose the changes and 
issue a pull request for your review. Otherwise, feel free to take the feedback 
from the attached doc.



Also, we apologize that during the interim meeting we could not cover all the 
material. Would you be able to present your ALTO/LMAP slide deck during the 
next ALTO meeting on Tuesday next week at 9am EST? I am happy to add it into 
the meeting's agenda.



Thanks,

Jordi on behalf of ALTO



From: alto mailto:alto-boun...@ietf.org>> on behalf of 
maqiufang (A) 
mailto:maqiufang1=40huawei@dmarc.ietf.org>>
Sent: Thursday, May 4, 2023 4:10
To: 
luismiguel.contrerasmuri...@telefonica.com<mailto:luismiguel.contrerasmuri...@telefonica.com>
 
mailto:luismiguel.contrerasmuri...@telefonica.com>>
Cc: IETF ALTO mailto:alto@ietf.org>>; 
draft-xie-alto-l...@ietf.org<mailto:draft-xie-alto-l...@ietf.org> 
mailto:draft-xie-alto-l...@ietf.org>>
Subject: Re: [alto] Proposed Agenda for Interims #2-5



WARNING: This email originated from outside of Qualcomm. Please be wary of any 
links or attachments, and do not enable macros.

Hi, Luis



Thank you for getting back to me! Please see my reply inline.

From: LUIS MIGUEL CONTRERAS MURILLO 
mailto:luismiguel.contrerasmuri...@telefonica.com>>
Sent: Sunday, April 30, 2023 1:15 AM
To: maqiufang (A) mailto:maqiufa...@huawei.com>>; Jensen 
Zhang mailto:jingxuan.n.zh...@gmail.com>>; 
kai...@scu.edu.cn<mailto:kai...@scu.edu.cn>
Cc: IETF ALTO mailto:alto@ietf.org>>; 
xie...@chinatelecom.cn<mailto:xie...@chinatelecom.cn>; 
wang...@chinatelecom.cn<mailto:wang...@chinatelecom.cn>
Subject: RE: [alto] Proposed Agenda for Interims #2-5



Hi Qiufang,



Thanks for pointing this out.



I think what you propose makes sense. Probably details should be clarified in 
terms of how PIDs defined for the measurement agents could correlate with 
conventional PIDs, i.e., those representing IP address pools. Some ideas come 
to my mind that probably we could discuss.

[Qiufang] Good. I think you are right that we need to clarify how measurement 
agents is correlated with conventional PIDs, and How to represent ALTO cost map 
using LMAP results, given that the LMAP results is based on specific 
measurement agent located in particular endpoint or network device, while ALTO 
cost map is cost metric between aggregation of endpoints. Would appreciate your 
ideas and happy to have further discussion with you.



But yes, I see this interesting to contemplate to understand what kind of 
extensions could be derived from this scenario, certainly interesting for 
network operations.

[Qiufang] Happy to know that you’re interested in this work. Currently we are 
also trying to explore what kinds of extensions could be derived from this. 
Answers to this might dependent on whether the LMAP details(e.g., 
measurement/report agent location, report schedule info) need to be organized 
into ALTO information and exposed to ALTO clients and to what extent.



Thanks for commenting and good to see this reported in the compilation sheet.

[Qiufang] Thank you!

Best regards



Luis



Best Regards,

Qiufang



De: maqiufang (A) mailto:maqiufa...@

Re: [alto] Proposed Agenda for Interims #2-5

[maqiufang (A)]

Thank you Jordi for doing the proofreading, much appreciated. I’ve uploaded a 
new version (https://www.ietf.org/archive/id/draft-xie-alto-lmap-02.txt) with 
your annotations incorporated. And also see repo 
https://github.com/QiufangMa/alto-lmap for this document. Happy to work with 
you and receive your further comments via either Github or mailing list.

Yes, I would be glad to present during next Tuesday’s ALTO weekly meeting, 
thank you for arranging this!

Best Regards,
Qiufang

From: Jordi Ros Giralt [mailto:j...@qti.qualcomm.com]
Sent: Friday, May 5, 2023 10:15 PM
To: maqiufang (A) ; 
luismiguel.contrerasmuri...@telefonica.com
Cc: IETF ALTO ; draft-xie-alto-l...@ietf.org
Subject: Re: [alto] Proposed Agenda for Interims #2-5

Hi Qiufang,

Thank you for reviving your ALTO/LMAP draft and for incorporating the LMAP data 
source in the ALTO data sources document.

I agree with Luis and your comments below.

I did a pass on your draft and made some annotations, see the attached doc. 
Would you be able to generate an updated version and push it to the 
datatracker? If your draft is in a github repo, I can propose the changes and 
issue a pull request for your review. Otherwise, feel free to take the feedback 
from the attached doc.

Also, we apologize that during the interim meeting we could not cover all the 
material. Would you be able to present your ALTO/LMAP slide deck during the 
next ALTO meeting on Tuesday next week at 9am EST? I am happy to add it into 
the meeting's agenda.

Thanks,
Jordi on behalf of ALTO

From: alto mailto:alto-boun...@ietf.org>> on behalf of 
maqiufang (A) 
mailto:maqiufang1=40huawei@dmarc.ietf.org>>
Sent: Thursday, May 4, 2023 4:10
To: 
luismiguel.contrerasmuri...@telefonica.com<mailto:luismiguel.contrerasmuri...@telefonica.com>
 
mailto:luismiguel.contrerasmuri...@telefonica.com>>
Cc: IETF ALTO mailto:alto@ietf.org>>; 
draft-xie-alto-l...@ietf.org<mailto:draft-xie-alto-l...@ietf.org> 
mailto:draft-xie-alto-l...@ietf.org>>
Subject: Re: [alto] Proposed Agenda for Interims #2-5


WARNING: This email originated from outside of Qualcomm. Please be wary of any 
links or attachments, and do not enable macros.

Hi, Luis



Thank you for getting back to me! Please see my reply inline.

From: LUIS MIGUEL CONTRERAS MURILLO 
mailto:luismiguel.contrerasmuri...@telefonica.com>>
Sent: Sunday, April 30, 2023 1:15 AM
To: maqiufang (A) mailto:maqiufa...@huawei.com>>; Jensen 
Zhang mailto:jingxuan.n.zh...@gmail.com>>; 
kai...@scu.edu.cn<mailto:kai...@scu.edu.cn>
Cc: IETF ALTO mailto:alto@ietf.org>>; 
xie...@chinatelecom.cn<mailto:xie...@chinatelecom.cn>; 
wang...@chinatelecom.cn<mailto:wang...@chinatelecom.cn>
Subject: RE: [alto] Proposed Agenda for Interims #2-5



Hi Qiufang,



Thanks for pointing this out.



I think what you propose makes sense. Probably details should be clarified in 
terms of how PIDs defined for the measurement agents could correlate with 
conventional PIDs, i.e., those representing IP address pools. Some ideas come 
to my mind that probably we could discuss.

[Qiufang] Good. I think you are right that we need to clarify how measurement 
agents is correlated with conventional PIDs, and How to represent ALTO cost map 
using LMAP results, given that the LMAP results is based on specific 
measurement agent located in particular endpoint or network device, while ALTO 
cost map is cost metric between aggregation of endpoints. Would appreciate your 
ideas and happy to have further discussion with you.



But yes, I see this interesting to contemplate to understand what kind of 
extensions could be derived from this scenario, certainly interesting for 
network operations.

[Qiufang] Happy to know that you’re interested in this work. Currently we are 
also trying to explore what kinds of extensions could be derived from this. 
Answers to this might dependent on whether the LMAP details(e.g., 
measurement/report agent location, report schedule info) need to be organized 
into ALTO information and exposed to ALTO clients and to what extent.



Thanks for commenting and good to see this reported in the compilation sheet.

[Qiufang] Thank you!

Best regards



Luis



Best Regards,

Qiufang



De: maqiufang (A) mailto:maqiufa...@huawei.com>>
Enviado el: miércoles, 26 de abril de 2023 11:12
Para: LUIS MIGUEL CONTRERAS MURILLO 
mailto:luismiguel.contrerasmuri...@telefonica.com>>;
 Jensen Zhang mailto:jingxuan.n.zh...@gmail.com>>; 
kai...@scu.edu.cn<mailto:kai...@scu.edu.cn>
CC: IETF ALTO mailto:alto@ietf.org>>; 
xie...@chinatelecom.cn<mailto:xie...@chinatelecom.cn>; 
wang...@chinatelecom.cn<mailto:wang...@chinatelecom.cn>
Asunto: RE: [alto] Proposed Agenda for Interims #2-5



Hi, Luis and all



Thanks for this effort. Jensen and Kai, I think your proposals make sense to 
me, maybe could be reflected on the sh

Re: [alto] Proposed Agenda for Interims #2-5

[maqiufang (A)]

Hi, Luis

Thank you for getting back to me! Please see my reply inline.
From: LUIS MIGUEL CONTRERAS MURILLO 
mailto:luismiguel.contrerasmuri...@telefonica.com>>
Sent: Sunday, April 30, 2023 1:15 AM
To: maqiufang (A) mailto:maqiufa...@huawei.com>>; Jensen 
Zhang mailto:jingxuan.n.zh...@gmail.com>>; 
kai...@scu.edu.cn<mailto:kai...@scu.edu.cn>
Cc: IETF ALTO mailto:alto@ietf.org>>; 
xie...@chinatelecom.cn<mailto:xie...@chinatelecom.cn>; 
wang...@chinatelecom.cn<mailto:wang...@chinatelecom.cn>
Subject: RE: [alto] Proposed Agenda for Interims #2-5

Hi Qiufang,

Thanks for pointing this out.

I think what you propose makes sense. Probably details should be clarified in 
terms of how PIDs defined for the measurement agents could correlate with 
conventional PIDs, i.e., those representing IP address pools. Some ideas come 
to my mind that probably we could discuss.
[Qiufang] Good. I think you are right that we need to clarify how measurement 
agents is correlated with conventional PIDs, and How to represent ALTO cost map 
using LMAP results, given that the LMAP results is based on specific 
measurement agent located in particular endpoint or network device, while ALTO 
cost map is cost metric between aggregation of endpoints. Would appreciate your 
ideas and happy to have further discussion with you.

But yes, I see this interesting to contemplate to understand what kind of 
extensions could be derived from this scenario, certainly interesting for 
network operations.
[Qiufang] Happy to know that you’re interested in this work. Currently we are 
also trying to explore what kinds of extensions could be derived from this. 
Answers to this might dependent on whether the LMAP details(e.g., 
measurement/report agent location, report schedule info) need to be organized 
into ALTO information and exposed to ALTO clients and to what extent.

Thanks for commenting and good to see this reported in the compilation sheet.
[Qiufang] Thank you!
Best regards

Luis

Best Regards,
Qiufang

De: maqiufang (A) mailto:maqiufa...@huawei.com>>
Enviado el: miércoles, 26 de abril de 2023 11:12
Para: LUIS MIGUEL CONTRERAS MURILLO 
mailto:luismiguel.contrerasmuri...@telefonica.com>>;
 Jensen Zhang mailto:jingxuan.n.zh...@gmail.com>>; 
kai...@scu.edu.cn<mailto:kai...@scu.edu.cn>
CC: IETF ALTO mailto:alto@ietf.org>>; 
xie...@chinatelecom.cn<mailto:xie...@chinatelecom.cn>; 
wang...@chinatelecom.cn<mailto:wang...@chinatelecom.cn>
Asunto: RE: [alto] Proposed Agenda for Interims #2-5

Hi, Luis and all

Thanks for this effort. Jensen and Kai, I think your proposals make sense to 
me, maybe could be reflected on the shared spreadsheet?

I’ve Just added one more potential data source to the spreadsheet: LMAP 
(Large-Scale Measurement of Broadband Performance, RFC7594) network measurement 
results. That said, ALTO server can simply work as the LMAP collector and 
accept the report from the measurement agent which performs the measurement 
tasks as instructed by the LMAP controller.

PS. There is a draft 
(https://www.ietf.org/archive/id/draft-xie-alto-lmap-00.txt) related to that, 
the authors plan to revive it very soon.

Best Regards,
Qiufang

From: alto [mailto:alto-boun...@ietf.org] On Behalf Of Jensen Zhang
Sent: Wednesday, April 26, 2023 8:29 AM
To: kai...@scu.edu.cn<mailto:kai...@scu.edu.cn>
Cc: IETF ALTO mailto:alto@ietf.org>>; Qin Wu 
mailto:bill...@huawei.com>>
Subject: Re: [alto] Proposed Agenda for Interims #2-5

Hi Luis and all,

Thanks for this useful collection of data sources. Besides the data sources 
listed in this collection, I am wondering if the following kinds of data 
sources can also be considered:

1. Prefix information, e.g., internet routing registry (IRR). It provides route 
and provider related information attached to IP prefixes. It may be helpful for 
network/property map generation, or locating the network domain in multidomain 
settings.

2. Data plane information, e.g., routing and forwarding tables read from BGP 
looking glass server or other OAM tools. Although I see the "IETF TE Network 
topology" source can already provide routing information, it may focus on the 
control plane, e.g., routing policy, not the data plane.

3. Telemetry information, e.g., traceroute. It can get both routing and 
performance information. It may have some overlap with the performance metrics.

Looking forward to seeing more discussions on this topic.

Best,
Jensen

On Tue, Apr 25, 2023 at 10:55 PM mailto:kai...@scu.edu.cn>> 
wrote:

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 whether it is beneficial to discuss gaps and constraints 
as well.



For example, I used to work 

Re: [alto] Proposed Agenda for Interims #2-5

[LUIS MIGUEL CONTRERAS MURILLO]

Hi Qiufang,

Thanks for pointing this out.

I think what you propose makes sense. Probably details should be clarified in 
terms of how PIDs defined for the measurement agents could correlate with 
conventional PIDs, i.e., those representing IP address pools. Some ideas come 
to my mind that probably we could discuss.

But yes, I see this interesting to contemplate to understand what kind of 
extensions could be derived from this scenario, certainly interesting for 
network operations.

Thanks for commenting and good to see this reported in the compilation sheet.

Best regards

Luis


De: maqiufang (A) 
Enviado el: miércoles, 26 de abril de 2023 11:12
Para: LUIS MIGUEL CONTRERAS MURILLO 
; Jensen Zhang 
; kai...@scu.edu.cn
CC: IETF ALTO ; xie...@chinatelecom.cn; wang...@chinatelecom.cn
Asunto: RE: [alto] Proposed Agenda for Interims #2-5

Hi, Luis and all

Thanks for this effort. Jensen and Kai, I think your proposals make sense to 
me, maybe could be reflected on the shared spreadsheet?

I’ve Just added one more potential data source to the spreadsheet: LMAP 
(Large-Scale Measurement of Broadband Performance, RFC7594) network measurement 
results. That said, ALTO server can simply work as the LMAP collector and 
accept the report from the measurement agent which performs the measurement 
tasks as instructed by the LMAP controller.

PS. There is a draft 
(https://www.ietf.org/archive/id/draft-xie-alto-lmap-00.txt) related to that, 
the authors plan to revive it very soon.

Best Regards,
Qiufang

From: alto [mailto:alto-boun...@ietf.org] On Behalf Of Jensen Zhang
Sent: Wednesday, April 26, 2023 8:29 AM
To: kai...@scu.edu.cn<mailto:kai...@scu.edu.cn>
Cc: IETF ALTO mailto:alto@ietf.org>>; Qin Wu 
mailto:bill...@huawei.com>>
Subject: Re: [alto] Proposed Agenda for Interims #2-5

Hi Luis and all,

Thanks for this useful collection of data sources. Besides the data sources 
listed in this collection, I am wondering if the following kinds of data 
sources can also be considered:

1. Prefix information, e.g., internet routing registry (IRR). It provides route 
and provider related information attached to IP prefixes. It may be helpful for 
network/property map generation, or locating the network domain in multidomain 
settings.

2. Data plane information, e.g., routing and forwarding tables read from BGP 
looking glass server or other OAM tools. Although I see the "IETF TE Network 
topology" source can already provide routing information, it may focus on the 
control plane, e.g., routing policy, not the data plane.

3. Telemetry information, e.g., traceroute. It can get both routing and 
performance information. It may have some overlap with the performance metrics.

Looking forward to seeing more discussions on this topic.

Best,
Jensen

On Tue, Apr 25, 2023 at 10:55 PM mailto:kai...@scu.edu.cn>> 
wrote:

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 whether it is beneficial to discuss gaps and constraints 
as well.



For example, I used to work on providing ALTO maps using SDN, or more 
precisely, using Open Daylight. Open Daylight has very good (among the best 
AFAIK) YANG support and the topology models were already support a few years 
back. One problem, however, was that using the topology information alone 
cannot generate high-precision network map or cost map: you still need to know 
where the hosts are attached and what is the routing. Thus, it has to be 
combined with other data sources, for example, host tracker in the SDN case or 
BGP/BGP-LS in provider networks, or be limited to specific networks, for 
example, those using link state routing protocols.



I am not saying that the document should summarize the gaps and/or constraints 
of all the data sources. Rather, I feel that the topic might be a useful input 
to the interim meeting and to future ALTO extensions.



Best,

Kai


-Original Messages
From:"LUIS MIGUEL CONTRERAS MURILLO" 
mailto:luismiguel.contrerasmuri...@telefonica.com>>
Sent Time:2023-04-18 06:23:51 (Tuesday)
To: "mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>" 
mailto:mohamed.boucad...@orange.com>>, "IETF 
ALTO" mailto:alto@ietf.org>>
Cc: "Qin Wu" mailto:bill...@huawei.com>>
Subject: Re: [alto] Proposed Agenda for Interims #2-5
Hi Med, Qin, WG,

In order to provide inputs for:


* interim #3: Deployment Catalysts

• Proposals to fix the integration complexity and integration with data 
sources

Jordi and I have been working on collecting some references that we consider as 
potential data sources of relevance for the WG and possible integration with 
ALTO. We have collected those inputs here: 
http

Re: [alto] Proposed Agenda for Interims #2-5

[LUIS MIGUEL CONTRERAS MURILLO]

Hi Jensen,

Thanks for your comment.

Please, see my answer in line.

Thank you,

Luis

De: Jensen Zhang 
Enviado el: miércoles, 26 de abril de 2023 2:29
Para: kai...@scu.edu.cn
CC: LUIS MIGUEL CONTRERAS MURILLO ; 
IETF ALTO ; Qin Wu 
Asunto: Re: [alto] Proposed Agenda for Interims #2-5

Hi Luis and all,

Thanks for this useful collection of data sources. Besides the data sources 
listed in this collection, I am wondering if the following kinds of data 
sources can also be considered:

1. Prefix information, e.g., internet routing registry (IRR). It provides route 
and provider related information attached to IP prefixes. It may be helpful for 
network/property map generation, or locating the network domain in multidomain 
settings.

[[Luis>]] This can be a useful information to add if different policies apply 
to different administrative domains. I think it could be used for map filtering 
purposes (as described in section 4.1.2 of RFC 7285). For instance thinking on 
the pilot we are doing in Telefonica for integrating ALTO with the Telefonica 
CDN, this property could be used for deciding from which streamer send the 
content to external prefixes of subscribers sitting in ISPs different from 
Telefonica.


2. Data plane information, e.g., routing and forwarding tables read from BGP 
looking glass server or other OAM tools. Although I see the "IETF TE Network 
topology" source can already provide routing information, it may focus on the 
control plane, e.g., routing policy, not the data plane.

[[Luis>]] Not 100% clear to me this point (i.e., your reference to data plane). 
So my answer could not be exactly addressing your question. In my view, 
relaying on tools like BGP looking glass can certainly provide information 
about reachability of prefixes, especially in multi-domain settings where there 
is no possibility of retrieving such information e.g. for another ALTO server. 
So it can help to infer some notion of cost map for a given point in time in 
relation with some IP prefixes. The best would be probably to pair with the 
corresponding ALTO server for that domain for getting the information directly, 
but if this is not possible, BGP looking glass could be certainly an 
alternative for indirectly obtaining such information.

3. Telemetry information, e.g., traceroute. It can get both routing and 
performance information. It may have some overlap with the performance metrics.

[[Luis>]] As before, it would be preferible to pair with corresponding ALTO 
servers for this. If not possible, that could be a way of inferring 
performance, which is somehow similar to what most of the applications make 
today for taking their own service decisions (I mean, inferring behaviors from 
performance metrics observed by their own).


Looking forward to seeing more discussions on this topic.

Best,
Jensen

On Tue, Apr 25, 2023 at 10:55 PM mailto:kai...@scu.edu.cn>> 
wrote:

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 whether it is beneficial to discuss gaps and constraints 
as well.



For example, I used to work on providing ALTO maps using SDN, or more 
precisely, using Open Daylight. Open Daylight has very good (among the best 
AFAIK) YANG support and the topology models were already support a few years 
back. One problem, however, was that using the topology information alone 
cannot generate high-precision network map or cost map: you still need to know 
where the hosts are attached and what is the routing. Thus, it has to be 
combined with other data sources, for example, host tracker in the SDN case or 
BGP/BGP-LS in provider networks, or be limited to specific networks, for 
example, those using link state routing protocols.



I am not saying that the document should summarize the gaps and/or constraints 
of all the data sources. Rather, I feel that the topic might be a useful input 
to the interim meeting and to future ALTO extensions.



Best,

Kai



-Original Messages
From:"LUIS MIGUEL CONTRERAS MURILLO" 
mailto:luismiguel.contrerasmuri...@telefonica.com>>
Sent Time:2023-04-18 06:23:51 (Tuesday)
To: "mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>" 
mailto:mohamed.boucad...@orange.com>>, "IETF 
ALTO" mailto:alto@ietf.org>>
Cc: "Qin Wu" mailto:bill...@huawei.com>>
Subject: Re: [alto] Proposed Agenda for Interims #2-5
Hi Med, Qin, WG,

In order to provide inputs for:


* interim #3: Deployment Catalysts

• Proposals to fix the integration complexity and integration with data 
sources

Jordi and I have been working on collecting some references that we consider as 
potential data sources of relevance for the WG and possible integ

Re: [alto] Proposed Agenda for Interims #2-5

[LUIS MIGUEL CONTRERAS MURILLO]

Hi Kai,

You are touching relevant points.

First, regarding the idea of retrieving the topology from the controller. In 
the simpler case, since the controller will already have a topology processed 
from the information retrieved from the network, it can make sense to get it 
from the controller. So, ALTO can benefit from that, thus avoiding to process 
twice the same information. In the more complex situation, to could be the case 
that the SDN controller collects and aggregates information from different 
domains (even under the same administrative responsibility) then simplifying 
again the aggregation and processing of the overall topological information. Or 
even it could be the case where the SDN controllers builds a general view of a 
network leveraging partial views even collected through different protocols 
(e.g., BGP-LS, LLDP, etc). In summary, the benefit could come from simplifying 
the ALTO server processes, just retrieving what has been already aggregated and 
processed.

However it is important what you say. Not all the information could be on the 
topology provided by the SDN controller. For instance, the subnets (IP 
prefixes) representing e.g. residential broadband users which are attached to 
border routers are not present in IETF Network Topology. These subnets should 
be obtained by means of BGP sessions with the route reflectors in the network.

So, even though we can simplify the process of the ALTO server by retrieving 
the internals of the network from the controller (which is useful for building 
the cost map) we yet need to maintain BGP sessions with the RR for 
understanding the IP pools in each PIC (i.e. to build the network map).

Finally going to your question about if it is useful to discuss gaps and 
constraints, my answer id definitely YES.

Thanks so much for your comment,

Luis

De: kai...@scu.edu.cn 
Enviado el: martes, 25 de abril de 2023 16:55
Para: LUIS MIGUEL CONTRERAS MURILLO 
CC: mohamed.boucad...@orange.com; IETF ALTO ; Qin Wu 

Asunto: Re: Re: [alto] Proposed Agenda for Interims #2-5


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 whether it is beneficial to discuss gaps and constraints 
as well.



For example, I used to work on providing ALTO maps using SDN, or more 
precisely, using Open Daylight. Open Daylight has very good (among the best 
AFAIK) YANG support and the topology models were already support a few years 
back. One problem, however, was that using the topology information alone 
cannot generate high-precision network map or cost map: you still need to know 
where the hosts are attached and what is the routing. Thus, it has to be 
combined with other data sources, for example, host tracker in the SDN case or 
BGP/BGP-LS in provider networks, or be limited to specific networks, for 
example, those using link state routing protocols.



I am not saying that the document should summarize the gaps and/or constraints 
of all the data sources. Rather, I feel that the topic might be a useful input 
to the interim meeting and to future ALTO extensions.



Best,

Kai



-Original Messages
From:"LUIS MIGUEL CONTRERAS MURILLO" 
mailto:luismiguel.contrerasmuri...@telefonica.com>>
Sent Time:2023-04-18 06:23:51 (Tuesday)
To: "mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>" 
mailto:mohamed.boucad...@orange.com>>, "IETF 
ALTO" mailto:alto@ietf.org>>
Cc: "Qin Wu" mailto:bill...@huawei.com>>
Subject: Re: [alto] Proposed Agenda for Interims #2-5
Hi Med, Qin, WG,

In order to provide inputs for:


* interim #3: Deployment Catalysts

• Proposals to fix the integration complexity and integration with data 
sources

Jordi and I have been working on collecting some references that we consider as 
potential data sources of relevance for the WG and possible integration with 
ALTO. We have collected those inputs here: 
https://docs.google.com/spreadsheets/d/1P4GrhQz_t17jIWg-3b1ycldhBWEEgIAAUZe2vjeO_1U/edit#gid=0

Please, feel free to access and check, all of you should be able to add/drop 
comments as well (let me know in case you need some permission for that). In 
the table we cover potential data sources, the rationale for considering them, 
existing reference work, as well as impacts on current ALTO. We hope this could 
be a basis for discussion for interim #3, but also to trigger discussions on 
the mailing list so we as WG can go to the interim with a more clear notion of 
the data sources and their implications.

Thanks

Best regards

Luis


De: alto mailto:alto-boun...@ietf.org>> En nombre de 
mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>
Enviado el: martes, 4 de abril de 2023 8:58
Pa

Re: [alto] Proposed Agenda for Interims #2-5

[maqiufang (A)]

Hi, Luis and all

Thanks for this effort. Jensen and Kai, I think your proposals make sense to 
me, maybe could be reflected on the shared spreadsheet?

I’ve Just added one more potential data source to the spreadsheet: LMAP 
(Large-Scale Measurement of Broadband Performance, RFC7594) network measurement 
results. That said, ALTO server can simply work as the LMAP collector and 
accept the report from the measurement agent which performs the measurement 
tasks as instructed by the LMAP controller.

PS. There is a draft 
(https://www.ietf.org/archive/id/draft-xie-alto-lmap-00.txt) related to that, 
the authors plan to revive it very soon.

Best Regards,
Qiufang

From: alto [mailto:alto-boun...@ietf.org] On Behalf Of Jensen Zhang
Sent: Wednesday, April 26, 2023 8:29 AM
To: kai...@scu.edu.cn
Cc: IETF ALTO ; Qin Wu 
Subject: Re: [alto] Proposed Agenda for Interims #2-5

Hi Luis and all,

Thanks for this useful collection of data sources. Besides the data sources 
listed in this collection, I am wondering if the following kinds of data 
sources can also be considered:

1. Prefix information, e.g., internet routing registry (IRR). It provides route 
and provider related information attached to IP prefixes. It may be helpful for 
network/property map generation, or locating the network domain in multidomain 
settings.

2. Data plane information, e.g., routing and forwarding tables read from BGP 
looking glass server or other OAM tools. Although I see the "IETF TE Network 
topology" source can already provide routing information, it may focus on the 
control plane, e.g., routing policy, not the data plane.

3. Telemetry information, e.g., traceroute. It can get both routing and 
performance information. It may have some overlap with the performance metrics.

Looking forward to seeing more discussions on this topic.

Best,
Jensen

On Tue, Apr 25, 2023 at 10:55 PM mailto:kai...@scu.edu.cn>> 
wrote:

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 whether it is beneficial to discuss gaps and constraints 
as well.



For example, I used to work on providing ALTO maps using SDN, or more 
precisely, using Open Daylight. Open Daylight has very good (among the best 
AFAIK) YANG support and the topology models were already support a few years 
back. One problem, however, was that using the topology information alone 
cannot generate high-precision network map or cost map: you still need to know 
where the hosts are attached and what is the routing. Thus, it has to be 
combined with other data sources, for example, host tracker in the SDN case or 
BGP/BGP-LS in provider networks, or be limited to specific networks, for 
example, those using link state routing protocols.



I am not saying that the document should summarize the gaps and/or constraints 
of all the data sources. Rather, I feel that the topic might be a useful input 
to the interim meeting and to future ALTO extensions.



Best,

Kai



-Original Messages
From:"LUIS MIGUEL CONTRERAS MURILLO" 
mailto:luismiguel.contrerasmuri...@telefonica.com>>
Sent Time:2023-04-18 06:23:51 (Tuesday)
To: "mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>" 
mailto:mohamed.boucad...@orange.com>>, "IETF 
ALTO" mailto:alto@ietf.org>>
Cc: "Qin Wu" mailto:bill...@huawei.com>>
Subject: Re: [alto] Proposed Agenda for Interims #2-5
Hi Med, Qin, WG,

In order to provide inputs for:


* interim #3: Deployment Catalysts

• Proposals to fix the integration complexity and integration with data 
sources

Jordi and I have been working on collecting some references that we consider as 
potential data sources of relevance for the WG and possible integration with 
ALTO. We have collected those inputs here: 
https://docs.google.com/spreadsheets/d/1P4GrhQz_t17jIWg-3b1ycldhBWEEgIAAUZe2vjeO_1U/edit#gid=0

Please, feel free to access and check, all of you should be able to add/drop 
comments as well (let me know in case you need some permission for that). In 
the table we cover potential data sources, the rationale for considering them, 
existing reference work, as well as impacts on current ALTO. We hope this could 
be a basis for discussion for interim #3, but also to trigger discussions on 
the mailing list so we as WG can go to the interim with a more clear notion of 
the data sources and their implications.

Thanks

Best regards

Luis


De: alto mailto:alto-boun...@ietf.org>> En nombre de 
mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>
Enviado el: martes, 4 de abril de 2023 8:58
Para: IETF ALTO mailto:alto@ietf.org>>
CC: Qin Wu mailto:bill...@huawei.com>>
Asunto: [alto] Proposed Agenda for Interim

Re: [alto] Proposed Agenda for Interims #2-5

[Jensen Zhang]

Hi Luis and all,

Thanks for this useful collection of data sources. Besides the data sources
listed in this collection, I am wondering if the following kinds of data
sources can also be considered:

1. Prefix information, e.g., internet routing registry (IRR). It provides
route and provider related information attached to IP prefixes. It may be
helpful for network/property map generation, or locating the network domain
in multidomain settings.

2. Data plane information, e.g., routing and forwarding tables read from
BGP looking glass server or other OAM tools. Although I see the "IETF TE
Network topology" source can already provide routing information, it may
focus on the control plane, e.g., routing policy, not the data plane.

3. Telemetry information, e.g., traceroute. It can get both routing and
performance information. It may have some overlap with the performance
metrics.

Looking forward to seeing more discussions on this topic.

Best,
Jensen

On Tue, Apr 25, 2023 at 10:55 PM  wrote:

> 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 whether it is beneficial to discuss gaps and
> constraints as well.
>
>
> For example, I used to work on providing ALTO maps using SDN, or more
> precisely, using Open Daylight. Open Daylight has very good (among the best
> AFAIK) YANG support and the topology models were already support a few
> years back. One problem, however, was that using the topology information
> alone cannot generate high-precision network map or cost map: you still
> need to know where the hosts are attached and what is the routing. Thus, it
> has to be combined with other data sources, for example, host tracker in
> the SDN case or BGP/BGP-LS in provider networks, or be limited to specific
> networks, for example, those using link state routing protocols.
>
>
> I am not saying that the document should summarize the gaps and/or
> constraints of all the data sources. Rather, I feel that the topic might be
> a useful input to the interim meeting and to future ALTO extensions.
>
>
> Best,
>
> Kai
>
>
> -Original Messages
> *From:*"LUIS MIGUEL CONTRERAS MURILLO" <
> luismiguel.contrerasmuri...@telefonica.com>
> *Sent Time:*2023-04-18 06:23:51 (Tuesday)
> *To:* "mohamed.boucad...@orange.com" ,
> "IETF ALTO" 
> *Cc:* "Qin Wu" 
> *Subject:* Re: [alto] Proposed Agenda for Interims #2-5
>
> Hi Med, Qin, WG,
>
>
>
> In order to provide inputs for:
>
>
>
> * interim #3: Deployment Catalysts
>
> · Proposals to fix the integration complexity and integration
> with data sources
>
>
>
> Jordi and I have been working on collecting some references that we
> consider as potential data sources of relevance for the WG and possible
> integration with ALTO. We have collected those inputs here:
> https://docs.google.com/spreadsheets/d/1P4GrhQz_t17jIWg-3b1ycldhBWEEgIAAUZe2vjeO_1U/edit#gid=0
>
>
>
> Please, feel free to access and check, all of you should be able to
> add/drop comments as well (let me know in case you need some permission for
> that). In the table we cover potential data sources, the rationale for
> considering them, existing reference work, as well as impacts on current
> ALTO. We hope this could be a basis for discussion for interim #3, but also
> to trigger discussions on the mailing list so we as WG can go to the
> interim with a more clear notion of the data sources and their implications.
>
>
>
> Thanks
>
>
>
> Best regards
>
>
>
> Luis
>
>
>
>
>
> *De:* alto  *En nombre de *
> mohamed.boucad...@orange.com
> *Enviado el:* martes, 4 de abril de 2023 8:58
> *Para:* IETF ALTO 
> *CC:* Qin Wu 
> *Asunto:* [alto] Proposed Agenda for Interims #2-5
>
>
>
> Hi all,
>
>
>
> Please find below the proposed agenda for the forthcoming interims
>
>
>
> * interim #2: WGLC follow-up of OAM/Transport I-Ds
>
> * interim #3: Deployment Catalysts
>
>- Reuse existing network resources to identify ALTO resources (e.g.,
>BGP communities)
>- Proposals to fix the integration complexity and integration with
>data sources
>
> * interim #4: OAM/Transport I-Ds
>
> * interim #5: Deployment Catalysts
>
>- Security/privacy isolation
>
>
>
> Comments and suggestions are welcome.
>
>
>
> Cheers,
>
> Qin & Med
>
>
>
> ___

Re: [alto] Proposed Agenda for Interims #2-5

[kaigao]

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 whether it is beneficial to discuss gaps and constraints 
as well.




For example, I used to work on providing ALTO maps using SDN, or more 
precisely, using Open Daylight. Open Daylight has very good (among the best 
AFAIK) YANG support and the topology models were already support a few years 
back. One problem, however, was that using the topology information alone 
cannot generate high-precision network map or cost map: you still need to know 
where the hosts are attached and what is the routing. Thus, it has to be 
combined with other data sources, for example, host tracker in the SDN case or 
BGP/BGP-LS in provider networks, or be limited to specific networks, for 
example, those using link state routing protocols.




I am not saying that the document should summarize the gaps and/or constraints 
of all the data sources. Rather, I feel that the topic might be a useful input 
to the interim meeting and to future ALTO extensions.




Best,

Kai



-Original Messages
From:"LUIS MIGUEL CONTRERAS MURILLO" 

Sent Time:2023-04-18 06:23:51 (Tuesday)
To: "mohamed.boucad...@orange.com" , "IETF ALTO" 

Cc: "Qin Wu" 
Subject: Re: [alto] Proposed Agenda for Interims #2-5



Hi Med, Qin, WG,

 

In order to provide inputs for:

 

* interim #3: Deployment Catalysts

· Proposals to fix the integration complexity and integration with data 
sources

 

Jordi and I have been working on collecting some references that we consider as 
potential data sources of relevance for the WG and possible integration with 
ALTO. We have collected those inputs here: 
https://docs.google.com/spreadsheets/d/1P4GrhQz_t17jIWg-3b1ycldhBWEEgIAAUZe2vjeO_1U/edit#gid=0

 

Please, feel free to access and check, all of you should be able to add/drop 
comments as well (let me know in case you need some permission for that). In 
the table we cover potential data sources, the rationale for considering them, 
existing reference work, as well as impacts on current ALTO. We hope this could 
be a basis for discussion for interim #3, but also to trigger discussions on 
the mailing list so we as WG can go to the interim with a more clear notion of 
the data sources and their implications.

 

Thanks

 

Best regards

 

Luis

 

 

De: alto  En nombre de mohamed.boucad...@orange.com
Enviado el: martes, 4 de abril de 2023 8:58
Para: IETF ALTO 
CC: Qin Wu 
Asunto: [alto] Proposed Agenda for Interims #2-5

 

Hi all,

 

Please find below the proposed agenda for the forthcoming interims

 

* interim #2: WGLC follow-up of OAM/Transport I-Ds

* interim #3: Deployment Catalysts

Reuse existing network resources to identify ALTO resources (e.g., BGP 
communities)
Proposals to fix the integration complexity and integration with data sources

* interim #4: OAM/Transport I-Ds

* interim #5: Deployment Catalysts

Security/privacy isolation

 

Comments and suggestions are welcome.

 

Cheers,

Qin & Med

 

_
 
Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.
 
This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.



Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede 
contener información privilegiada o confidencial y es para uso exclusivo de la 
persona o entidad de destino. Si no es usted. el destinatario indicado, queda 
notificado de que la lectura, utilización, divulgación y/o copia sin 
autorización puede estar prohibida en virtud de la legislación vigente. Si ha 
recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente 
por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileged 
information intended only for the use of the individual or entity named above. 
If the reader of this message is not the

Re: [alto] Proposed Agenda for Interims #2-5

[LUIS MIGUEL CONTRERAS MURILLO]

Hi Med, Qin, WG,

In order to provide inputs for:


* interim #3: Deployment Catalysts

* Proposals to fix the integration complexity and integration with data 
sources

Jordi and I have been working on collecting some references that we consider as 
potential data sources of relevance for the WG and possible integration with 
ALTO. We have collected those inputs here: 
https://docs.google.com/spreadsheets/d/1P4GrhQz_t17jIWg-3b1ycldhBWEEgIAAUZe2vjeO_1U/edit#gid=0

Please, feel free to access and check, all of you should be able to add/drop 
comments as well (let me know in case you need some permission for that). In 
the table we cover potential data sources, the rationale for considering them, 
existing reference work, as well as impacts on current ALTO. We hope this could 
be a basis for discussion for interim #3, but also to trigger discussions on 
the mailing list so we as WG can go to the interim with a more clear notion of 
the data sources and their implications.

Thanks

Best regards

Luis


De: alto  En nombre de mohamed.boucad...@orange.com
Enviado el: martes, 4 de abril de 2023 8:58
Para: IETF ALTO 
CC: Qin Wu 
Asunto: [alto] Proposed Agenda for Interims #2-5

Hi all,

Please find below the proposed agenda for the forthcoming interims

* interim #2: WGLC follow-up of OAM/Transport I-Ds
* interim #3: Deployment Catalysts

  *   Reuse existing network resources to identify ALTO resources (e.g., BGP 
communities)
  *   Proposals to fix the integration complexity and integration with data 
sources
* interim #4: OAM/Transport I-Ds
* interim #5: Deployment Catalysts

  *   Security/privacy isolation

Comments and suggestions are welcome.

Cheers,
Qin & Med


_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.



Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede 
contener informaci?n privilegiada o confidencial y es para uso exclusivo de la 
persona o entidad de destino. Si no es usted. el destinatario indicado, queda 
notificado de que la lectura, utilizaci?n, divulgaci?n y/o copia sin 
autorizaci?n puede estar prohibida en virtud de la legislaci?n vigente. Si ha 
recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente 
por esta misma v?a y proceda a su destrucci?n.

The information contained in this transmission is confidential and privileged 
information intended only for the use of the individual or entity named above. 
If the reader of this message is not the intended recipient, you are hereby 
notified that any dissemination, distribution or copying of this communication 
is strictly prohibited. If you have received this transmission in error, do not 
read it. Please immediately reply to the sender that you have received this 
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 n?o ? vossa 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 mesma via e 
proceda a sua destrui??o
___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

Re: [alto] Proposed Agenda for Interims #2-5

[Jordi Ros Giralt]

Thanks for explaining Qin.

Jordi

From: Qin Wu 
Sent: Saturday, April 8, 2023 16:48
To: Jordi Ros Giralt ; mohamed.boucad...@orange.com 
; IETF ALTO 
Subject: RE: Proposed Agenda for Interims #2-5


WARNING: This email originated from outside of Qualcomm. Please be wary of any 
links or attachments, and do not enable macros.

Hi, Jordi:

Compute related draft, in my understanding, fits into interim #3: Deployment 
Catalysts,

draft-zhang-alto-bgp-ls and draft-contreras-alto-bgp-communities actually can 
lay foundation for compute related work, i.e., 
https://datatracker.ietf.org/doc/draft-contreras-alto-service-edge/



Regarding multi-domain, Security/privacy isolation for interim #5 might have 
relation to mulit-domain use cases, but my general strategy is to set 
multi-domain as lower priority.

Focus on more concrete pieces or urgent pieces.



-Qin

发件人: Jordi Ros Giralt [mailto:j...@qti.qualcomm.com]
发送时间: 2023年4月8日 5:36
收件人: mohamed.boucad...@orange.com; IETF ALTO 
抄送: Qin Wu 
主题: Re: Proposed Agenda for Interims #2-5



Hi Med, Qin:



Many thanks for proposing the agendas, the proposed scope makes sense.



Let me ask one question to ensure the agenda is comprehensive. There are 
currently 3 technical topics/proposals being discussed within the WG for the 
rechartering: (1) compute, (2) multi-domain and (3) trust. It looks like trust 
would be discussed during the interim #5. Could you clarify in which interims 
we will be discussing #1 compute and #2 multi-domain? Note that several drafts 
have been recently updated or created anew to enable the discussion for these 
two topics, such as:



- Compute: https://datatracker.ietf.org/doc/draft-contreras-alto-service-edge/

- Multi-domain: https://datatracker.ietf.org/doc/draft-yang-alto-multi-domain/



We look forward to very productive conversations on these topics.



Thanks,

Jordi





From: alto mailto:alto-boun...@ietf.org>> on behalf of 
mohamed.boucad...@orange.com 
mailto:mohamed.boucad...@orange.com>>
Sent: Tuesday, April 4, 2023 8:58 AM
To: IETF ALTO mailto:alto@ietf.org>>
Cc: Qin Wu mailto:bill...@huawei.com>>
Subject: [alto] Proposed Agenda for Interims #2-5



WARNING: This email originated from outside of Qualcomm. Please be wary of any 
links or attachments, and do not enable macros.

Hi all,



Please find below the proposed agenda for the forthcoming interims



* interim #2: WGLC follow-up of OAM/Transport I-Ds

* interim #3: Deployment Catalysts

・ Reuse existing network resources to identify ALTO resources (e.g., 
BGP communities)

・ Proposals to fix the integration complexity and integration with data 
sources

* interim #4: OAM/Transport I-Ds

* interim #5: Deployment Catalysts

・ Security/privacy isolation



Comments and suggestions are welcome.



Cheers,

Qin & Med



_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may 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

Re: [alto] Proposed Agenda for Interims #2-5

[Qin Wu]

BTW, I also see
https://www.ietf.org/archive/id/draft-xie-alto-lmap-00.txt
https://datatracker.ietf.org/doc/draft-hzx-alto-network-topo/
relevant to interim #3
Would it be great to see these drafts to be further cooked or consolidate with 
other related work.

-Qin
发件人: alto [mailto:alto-boun...@ietf.org] 代表 Qin Wu
发送时间: 2023年4月8日 22:48
收件人: Jordi Ros Giralt ; mohamed.boucad...@orange.com; 
IETF ALTO 
主题: Re: [alto] Proposed Agenda for Interims #2-5

Hi, Jordi:
Compute related draft, in my understanding, fits into interim #3: Deployment 
Catalysts,
draft-zhang-alto-bgp-ls and draft-contreras-alto-bgp-communities actually can 
lay foundation for compute related work, i.e., 
https://datatracker.ietf.org/doc/draft-contreras-alto-service-edge/

Regarding multi-domain, Security/privacy isolation for interim #5 might have 
relation to mulit-domain use cases, but my general strategy is to set 
multi-domain as lower priority.
Focus on more concrete pieces or urgent pieces.

-Qin
发件人: Jordi Ros Giralt [mailto:j...@qti.qualcomm.com]
发送时间: 2023年4月8日 5:36
收件人: mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>; IETF 
ALTO mailto:alto@ietf.org>>
抄送: Qin Wu mailto:bill...@huawei.com>>
主题: Re: Proposed Agenda for Interims #2-5

Hi Med, Qin:

Many thanks for proposing the agendas, the proposed scope makes sense.

Let me ask one question to ensure the agenda is comprehensive. There are 
currently 3 technical topics/proposals being discussed within the WG for the 
rechartering: (1) compute, (2) multi-domain and (3) trust. It looks like trust 
would be discussed during the interim #5. Could you clarify in which interims 
we will be discussing #1 compute and #2 multi-domain? Note that several drafts 
have been recently updated or created anew to enable the discussion for these 
two topics, such as:

- Compute: https://datatracker.ietf.org/doc/draft-contreras-alto-service-edge/
- Multi-domain: https://datatracker.ietf.org/doc/draft-yang-alto-multi-domain/

We look forward to very productive conversations on these topics.

Thanks,
Jordi


From: alto mailto:alto-boun...@ietf.org>> on behalf of 
mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com> 
mailto:mohamed.boucad...@orange.com>>
Sent: Tuesday, April 4, 2023 8:58 AM
To: IETF ALTO mailto:alto@ietf.org>>
Cc: Qin Wu mailto:bill...@huawei.com>>
Subject: [alto] Proposed Agenda for Interims #2-5


WARNING: This email originated from outside of Qualcomm. Please be wary of any 
links or attachments, and do not enable macros.
Hi all,

Please find below the proposed agenda for the forthcoming interims

* interim #2: WGLC follow-up of OAM/Transport I-Ds
* interim #3: Deployment Catalysts
・ Reuse existing network resources to identify ALTO resources (e.g., 
BGP communities)
・ Proposals to fix the integration complexity and integration with data 
sources
* interim #4: OAM/Transport I-Ds
* interim #5: Deployment Catalysts
・ Security/privacy isolation

Comments and suggestions are welcome.

Cheers,
Qin & Med


_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may 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

Re: [alto] Proposed Agenda for Interims #2-5

[Qin Wu]

Hi, Jordi:
Compute related draft, in my understanding, fits into interim #3: Deployment 
Catalysts,
draft-zhang-alto-bgp-ls and draft-contreras-alto-bgp-communities actually can 
lay foundation for compute related work, i.e., 
https://datatracker.ietf.org/doc/draft-contreras-alto-service-edge/

Regarding multi-domain, Security/privacy isolation for interim #5 might have 
relation to mulit-domain use cases, but my general strategy is to set 
multi-domain as lower priority.
Focus on more concrete pieces or urgent pieces.

-Qin
发件人: Jordi Ros Giralt [mailto:j...@qti.qualcomm.com]
发送时间: 2023年4月8日 5:36
收件人: mohamed.boucad...@orange.com; IETF ALTO 
抄送: Qin Wu 
主题: Re: Proposed Agenda for Interims #2-5

Hi Med, Qin:

Many thanks for proposing the agendas, the proposed scope makes sense.

Let me ask one question to ensure the agenda is comprehensive. There are 
currently 3 technical topics/proposals being discussed within the WG for the 
rechartering: (1) compute, (2) multi-domain and (3) trust. It looks like trust 
would be discussed during the interim #5. Could you clarify in which interims 
we will be discussing #1 compute and #2 multi-domain? Note that several drafts 
have been recently updated or created anew to enable the discussion for these 
two topics, such as:

- Compute: https://datatracker.ietf.org/doc/draft-contreras-alto-service-edge/
- Multi-domain: https://datatracker.ietf.org/doc/draft-yang-alto-multi-domain/

We look forward to very productive conversations on these topics.

Thanks,
Jordi


From: alto mailto:alto-boun...@ietf.org>> on behalf of 
mohamed.boucad...@orange.com 
mailto:mohamed.boucad...@orange.com>>
Sent: Tuesday, April 4, 2023 8:58 AM
To: IETF ALTO mailto:alto@ietf.org>>
Cc: Qin Wu mailto:bill...@huawei.com>>
Subject: [alto] Proposed Agenda for Interims #2-5


WARNING: This email originated from outside of Qualcomm. Please be wary of any 
links or attachments, and do not enable macros.
Hi all,

Please find below the proposed agenda for the forthcoming interims

* interim #2: WGLC follow-up of OAM/Transport I-Ds
* interim #3: Deployment Catalysts
・ Reuse existing network resources to identify ALTO resources (e.g., 
BGP communities)
・ Proposals to fix the integration complexity and integration with data 
sources
* interim #4: OAM/Transport I-Ds
* interim #5: Deployment Catalysts
・ Security/privacy isolation

Comments and suggestions are welcome.

Cheers,
Qin & Med


_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may 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

Re: [alto] Proposed Agenda for Interims #2-5

[Jordi Ros Giralt]

Hi Med, Qin:

Many thanks for proposing the agendas, the proposed scope makes sense.

Let me ask one question to ensure the agenda is comprehensive. There are 
currently 3 technical topics/proposals being discussed within the WG for the 
rechartering: (1) compute, (2) multi-domain and (3) trust. It looks like trust 
would be discussed during the interim #5. Could you clarify in which interims 
we will be discussing #1 compute and #2 multi-domain? Note that several drafts 
have been recently updated or created anew to enable the discussion for these 
two topics, such as:

- Compute: https://datatracker.ietf.org/doc/draft-contreras-alto-service-edge/
- Multi-domain: https://datatracker.ietf.org/doc/draft-yang-alto-multi-domain/

We look forward to very productive conversations on these topics.

Thanks,
Jordi


From: alto  on behalf of mohamed.boucad...@orange.com 

Sent: Tuesday, April 4, 2023 8:58 AM
To: IETF ALTO 
Cc: Qin Wu 
Subject: [alto] Proposed Agenda for Interims #2-5


WARNING: This email originated from outside of Qualcomm. Please be wary of any 
links or attachments, and do not enable macros.
Hi all,

Please find below the proposed agenda for the forthcoming interims

* interim #2: WGLC follow-up of OAM/Transport I-Ds
* interim #3: Deployment Catalysts

  *   Reuse existing network resources to identify ALTO resources (e.g., BGP 
communities)
  *   Proposals to fix the integration complexity and integration with data 
sources
* interim #4: OAM/Transport I-Ds
* interim #5: Deployment Catalysts

  *   Security/privacy isolation

Comments and suggestions are welcome.

Cheers,
Qin & Med


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may 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