- mat-wg - mailman.ripe.net

The Resilience of the Internet in Ukraine - One Year On
by Emile Aben 17 Apr '23

17 Apr '23

Dear Colleagues, A year ago I wrote about the resilience of the Internet in Ukraine a few weeks after the war broke out in the country. In this article I revisit the topic and analyse what has changed after more than a year of war, based on data the RIPE NCC collects through RIPE RIS and RIPE Atlas: https://labs.ripe.net/author/emileaben/the-resilience-of-the-internet-in-uk… kind regards, Emile Aben RIPE NCC

1 0

Contribution submission for MAT WG at RIPE86
by Marco Polverini 10 Apr '23

10 Apr '23

Dear Nina, Massimo and Stephen My name is Marco Polverini, an assistant professor at Sapienza University of Rome. I would like to submit the following proposal to be presented at the next MAT WG. This work has been accepted to be presented at the IEEE NOMS 23 ( https://noms2023.ieee-noms.org/) Attached to this email you can find the original paper (in case you need further details about the topic of the presentation I would like to do). Thanks Marco *Title:* A Digital Twin based Framework to Enable "What-If" Analysis in BGP Optimization *Outline of the speech:* - introduction and motivation: in this talk we aim to introduce a framework for the creation of Digital Twins of Autonomous Systems in order to enable the execution of "what if" analysis in the context of inter domain routing optimization - background on digital twins: this section is to introduce the basic terminology and concepts on Digital Twins - presentation of the proposed framework: in this section we provide an overview of the architecture of the proposed framework and detail the responsibilities of each functional block - proof of concept: a simple proof of concept is presented, with the aim of showing the effectiveness of the proposal - conclusion and future work *Abstract:* Nowadays, inter domain routing optimization is performed based on the so called "Tweak and Pray" approach, which consists in performing changes in the configuration of the BGP protocol without knowing in advance the consequences of such a modification. This is due to the lack of cooperation among Network Operators in the configuration of the BGP to optimize the inter domain routing. Inefficiency in the resource usage, network anomalies and outages are common consequences of wrong configuration changes performed by Network Operators in an attempt to improve the performance of their infrastructures. In this paper we propose a novel framework based on the Digital Twin technology to enable the execution of "what-if" analysis in the context of Traffic Engineering performed by tuning BGP parameters. Such a paradigm shift will allow Network Operators to be aware of the effects of BGP configuration changes before their actual execution. A proof of concept related to the balancing of inbound traffic in an Autonomous System network, based on the use of the AS Path Prepending technique, is realized to validate the feasibility of the proposed approach.

2 1

delegate LIR portal access to specific user for specific resources - was: [address-policy-wg] 2023-02 New Policy Proposal (Minimum Size for IPv4 Temporary Assignments)
by Massimo Candela 07 Apr '23

07 Apr '23

Hi Elvis, On 14/03/2023 08:42, Elvis Daniel Velea wrote: > Hi Massimo, > > thank you for your message. Let me see if I have an answer to some of > your questions/comments. See inline. > > ------- > I also mention below a variation of this proposal, which could be it's > own proposal/thread (suggestions welcome): > > There should be an easy way to do "temporary assignments" (which may or > may not be the correct term in this case) to researchers/developers, > starting from address space of a company which is "sponsoring" the > research. > > > The key part of what I would like to have is the possibility to provide > somebody with access to LIR portal services but limited to a specific > subset of my resources. > > In general, a company is not going to support a research/experiment by > providing indiscriminate access to the LIR portal. Creating a new > LIR or > transferring prefixes is not a plausible solution in this context. > > > An existing LIR can do an assignment to a researcher/developer as we > speak. All assignments an LIR makes are ‘temporary’, some may last a day > and some may last 10 years… Can you explain this better? I have been asking to several ncc contacts and there was no suitable solution for this at the moment. Asking researchers/developers to create their own LIRs so that resources can be transferred is not a practical solution, but I'm not sure you are referring to this. Giving the researcher/developer access to the LIR portal/APIs for all the resources is also not a solution. > > If you want the researcher to have access to services like RPKI, they > can ask their LIR. In some cases, maybe temporary transfers could also > be of use. Again, I don't see a way to do this at the moment. > > Note that this proposal aims to update the temporary assignment proposal > that is currently in place. The RIPE NCC makes these temporary > assignments from a pool of IPs they have reserved specifically for this > purpose. I understand. This is why I said that this could be a different proposal (even if related by a similar purpose). I changed the email subject to avoid confusion. > > > Also, I believe this would remove the need for an approval procedure > from the RIPE NCC side: (1) if the address space used is of a company, > there is less need to validate the research project motivations; and > (2) > the company "sponsoring" is also the one responsible for the address > space. > > > I am not sure I understand what you mean by this. The NCC does not need > to approve any assignments made by LIRs. The NCC will need to approve > temporary assignments if the request is sent by an LIR (for an end-user) > based on the current temporary assignment policy. That's exactly what I'm saying. Assignments done by LIRs of their own resources do not require approval, while they would satisfy the research use case (in summary: using prefixes from the ncc stash is not needed in all cases). Thanks for your answers. Ciao, Massimo

1 0

Call for presentations for MAT WG at RIPE86 in May
by Stephen Strowes 06 Apr '23

06 Apr '23

Hi all, RIPE86 is coming up fast: 22 -- 26 May! We are seeking your presentations for the next MAT WG session during that week. Presentations for the WG session are preferably 10-15min long. Please include in your proposal: * a title * a draft of your proposed presentation, even if just an outline * a paragraph describing the topic, and why the topic is of interest for the community. Interesting topics include (but are not limited to): recent measurement research which has an operational impact; recent operational work that may open avenues to research; projects, tools, or datasets that support either operations or research. Please submit your presentation proposal by Friday 28 April by emailing us at mat-wg-chairs at ripe.net. We will make our selections and post the agenda soon after. RIPE meetings are fully hybrid, and we encourage presentations from anywhere. Sessions are facilitated through meetecho. For our planning, we'd appreciate it if you can indicate whether you are likely to be online or on-site. Please ask if you have any questions regarding the setup on either side. Thanks! Cheers, Nina, Massimo, Stephen, as WG co-chairs

1 1

Subject: RIPE Atlas, RIPEstat and RIS Quarterly Planning Q2 2023
by Robert Kisteleki 30 Mar '23

30 Mar '23

Dear colleagues, The quarterly plans for RIPE Atlas, RIPEstat and RIS can now be found at: https://www.ripe.net/support/documentation/quarterly-planning The goal of our quarterly planning is to communicate the work we’re doing for the coming months, get your input and start a discussion on other developments we should work on. If you have any input on our plans or want to let us know what you would like to see us work on, please let us know. Kind regards, Robert Kisteleki RIPE NCC

1 0

Re: [mat-wg] [address-policy-wg] 2023-02 New Policy Proposal (Minimum Size for IPv4 Temporary Assignments)
by Massimo Candela 07 Mar '23

07 Mar '23

Hi all, I added in cc the MAT mailing list, which is frequented by researchers. I believe that is the right audience for this proposal. @MAT: Support for this proposal should be expressed before this Friday (March 10). See proposal below. Reply by keeping both list. @Addres-policy: I support this proposal. ------- I also mention below a variation of this proposal, which could be it's own proposal/thread (suggestions welcome): There should be an easy way to do "temporary assignments" (which may or may not be the correct term in this case) to researchers/developers, starting from address space of a company which is "sponsoring" the research. The key part of what I would like to have is the possibility to provide somebody with access to LIR portal services but limited to a specific subset of my resources. In general, a company is not going to support a research/experiment by providing indiscriminate access to the LIR portal. Creating a new LIR or transferring prefixes is not a plausible solution in this context. Also, I believe this would remove the need for an approval procedure from the RIPE NCC side: (1) if the address space used is of a company, there is less need to validate the research project motivations; and (2) the company "sponsoring" is also the one responsible for the address space. Ciao, Massimo On 27/02/2023 16:44, Leo Vegoda wrote: > Hi, > > We've not had any feedback on this proposal yet. > > As a reminder, this proposal would set "the minimum assignment size to > a /24 while still allowing for a smaller assignment if requested by > the End User. This policy proposal also allows routing requirements to > justify the request for more than a /24 for research purposes." > > Support for the proposal, or arguments against it are welcome. > > Many thanks, > > Leo Vegoda > Address Policy WG co-chair > > On Thu, 9 Feb 2023 at 00:26, Angela Dall'Ara <adallara(a)ripe.net> wrote: >> >> Dear colleagues, >> >> A new RIPE Policy Proposal, 2023-02, "Minimum Size for IPv4 Temporary >> Assignments" >> is now available for discussion. >> >> This policy proposal recommends setting the minimum assignment size for >> temporary assignments to a /24 while still allowing for a smaller >> assignment if requested by the End User. This policy proposal also >> allows routing requirements to justify the request for more than a /24 >> for research purposes. >> >> You can find the full proposal at: >> https://www.ripe.net/participate/policies/proposals/2023-02 >> >> As per the RIPE Policy Development Process (PDP), the purpose of this >> four-week Discussion Phase is to discuss the proposal and provide >> feedback to the proposers. >> >> At the end of the Discussion Phase, the proposers, with the agreement of >> the WG Chairs, will decide how to proceed with the proposal. >> >> The PDP document can be found at: >> https://www.ripe.net/publications/docs/ripe-781 >> >> We encourage you to review this proposal and send your comments to >> address-policy-wg(a)ripe.net before 10 March 2023. >> >> >> Kind regards, >> >> Angela Dall'Ara >> Policy Officer >> RIPE NCC >> >> >> -- >> >> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/address-policy-wg >

1 0

Improved timeliness of RIS dump files
by Emile Aben 07 Mar '23

07 Mar '23

Dear colleagues, We are planning to replace the pipeline that generates MRT dump files publicly available from the RIPE NCC. The new pipeline will have significantly less delay, and also some changes on the structure of the MRT file format [*]. Files in the newer format are available for testing here: https://www.ris.ripe.net/dumps-per-rrc-rest/prototype/ We have received feedback from MRT parser implementers that these files work fine for their parsers, but in case you haven't tested your MRT parser implementation, we ask you to test the new files before we make the switch. Our plan is to make this switch on 3 April 2023. After we make the switch the bview files available at our main location for downloading MRT files will be generated using the new pipeline and we will be able to produce these files in a more timely manner. Kind regards, Emile Aben RIPE NCC [*] These changes are documented here: https://ris.ripe.net/docs/40_Prototypes/15_per_rrc_dumps.html, but beware at this point we are only changing the files, not the frequency of dump files, nor putting the API in production. We did not receive feedback about these, but please let us know if you find them useful.

1 0

Re: [mat-wg] [atlas] Proposal: Remove support for non-public measurements [ONLY-PUBLIC]
by Stephen Strowes 11 Jan '23

11 Jan '23

Hi, On 12/31/22 18:37, Randy Bush wrote: > hi robert, > > and thanks > >> I seem to remember that a typical non-public measurement is a one-off, >> and as such the data volume collected and stored is likely to be >> relatiely low. > interesting There is an old (late 2016) labs post worth referring to for this discussion [1]. In 2020 there was a survey of the users of private measurements [2], which was intended to get feedback on their actual use-cases. I seem to recall a very small set of respondents from an already small set of surveyees. The results are probably lost in the ether. I feel there's an aspect of the broader question that is rarely touched upon in these discussions: would user behaviour actually change if non-public measurements went away? I'm never sure how many use-cases are truly secret. Cheers, S. [1] https://labs.ripe.net/author/kistel/non-public-measurements-in-ripe-atlas/ [2] https://www.ripe.net/participate/forms/apply/ripe-atlas-private-measurement… > >> I don't have the numbers readily available to me at this moment, but >> we can certainly dig up recent statistics about this. > i did not intend to create a lot of work for you. but, as a measurement > person, i am a bit fond of basing decisions on facts. > > randy >

1 0

Fwd: [atlas] Proposal: Remove support for non-public measurements [ONLY-PUBLIC]
by Stephen Strowes 22 Dec '22

22 Dec '22

Hi all, I'm forwarding these five threads into the MAT WG because they're all probably of interest to folks here. Please share your feedback with the NCC! Cheers, S. -------- Forwarded Message -------- Subject: [atlas] Proposal: Remove support for non-public measurements [ONLY-PUBLIC] Date: Wed, 14 Dec 2022 15:04:40 +0100 From: Robert Kisteleki <robert(a)ripe.net> Organization: RIPE NCC To: ripe-atlas(a)ripe.net <ripe-atlas(a)ripe.net> Dear RIPE Atlas users, We recently published a RIPE Labs article containing a few proposals: https://labs.ripe.net/author/kistel/five-proposals-for-a-better-ripe-atlas/. We'd like to encourage you to express your comments about this proposal (if you'd like to share them) here. Regards, Robert Kisteleki For the RIPE Atlas team -- ripe-atlas mailing list ripe-atlas(a)ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas

2 1

Re: [mat-wg] [atlas] Proposal: Measure well-known CDNs,[CDN-HTTP]
by Massimo Candela 17 Dec '22

17 Dec '22

On 17/12/2022 00:19, Barry Raveendran Greene wrote: > > >> On Dec 16, 2022, at 23:29, Stephane Bortzmeyer <bortzmeyer(a)nic.fr> wrote: >> >> There is a larger problem here, a more strategic one: such a feature >> would contribute to the centralisation of the Internet, which is >> already too important. Tagging some targets are "important" and >> "worthy of measurements" would mean that we consider some HTTP servers >> to be more useful than others. That would be a bad message from RIPE. > > We’ve come full circle - we started with centralized PTTs - moved to a decentralized ASN/Paul Baran model - now Re-centralized based on marketing domination. > > +1 with Stephane’s observation. The selection of who to measure is a statement. +1 Also, while the data would be useful, I don't think the role of the ripe ncc is to grade commercial services. Let other companies or individual researchers do that.

1 0