April 2024 - RACI-list - mailman.ripe.net

CFP: INDIS Workshop (Deadline August 1st)
by Nik Sultana 29 Jul '24

29 Jul '24

CALL FOR PAPERS The 11th Annual International Workshop on Innovating the Network for Data-Intensive Science (INDIS 2024) in conjunction with SC24 (Supercomputing) Atlanta, Georgia, USA | November 17th, 2024 We invite researchers and engineers to submit high-quality technical academic papers to the 11th Annual International Workshop on Innovating the Network for Data-Intensive Science (INDIS 2024). The workshop will be held in conjunction with the SC24: IEEE/ACM International Conference for High Performance Computing, Networking, Storage and Analysis (Supercomputing), which will be held in Atlanta, Georgia, November 17-22, 2024. We invite papers that propose new and novel techniques that increase the capacity and functionality of scientific computing and high-performance networks. This workshop encourages submissions that address one or more of the workshop topics addressing networking research challenges; and developments that are essential in information systems infrastructure for the scientific discovery process. We also welcome participants from SCinet to present high-quality experimental papers on their latest designs and solutions. SCinet, as the high-speed network engine of the SC conference, represents state of the art, connects many demonstrators of big science data processing infrastructures at the highest line speeds, deploys the newest technologies available, and demonstrates network instrumentation techniques and novel functionality. The show floor network connects to many laboratories and universities worldwide using high-bandwidth connections. Topics of interest include but are not limited to: * Network innovations: novel approaches, protocols and algorithms to meet the current and emerging requirements for data intensive applications. * High-performance network testbeds and simulations for parallel and distributed science experiments and workloads. * High-performance and large-scale network monitoring, control and management services. * Software-defined networking (SDN) and Network Function Virtualization (NFV) in service of data science applications. * Machine learning algorithms for network telemetry, performance measurements, network and Input/Output (I/O) profile analytics, and high-touch solutions on network packets, flows and hardware stats to identify patterns and troubleshooting issues. * Compute in-network (aka edge- middleware computing platforms) and offloaded infrastructure services on programmable hardware (e.g. FPGA). * High-performance data streaming and memory-to-memory transfer applications and techniques * Wireless and Quantum networking and testbeds. * End-to-end quality of service (QoS) performance and Traffic Engineering (TE) applications. * Multi-domain networking, including hybrid clouds and multi-domain authorization. * Scientific data privacy, security, integrity, provenance and sharing in multi-domain environments. Important Dates: Paper Submission Due: August 1st, 2024 Notification of acceptance: September 5th, 2024 Camera-ready version: September 27th, 2024 Workshop Date: November 17th, 2024 Submission Guidelines: Papers will be published in the SC24 conference workshop proceedings through IEEE TCHPC upon approval. Workshop papers are expected to be in IEEE standard conference format (two-column and 10 point font size) with 8-10 pages for full papers and 4 pages for short papers describing novel work in the topics of interest. Experiments from SCinet and show floor are encouraged (e.g. Traveling FABRIC node). Manuscripts should be submitted via the SC Linklings system (Visit Wokshop website for more information). Organizing Committee: Anees Al-Najjar: Oak Ridge National Laboratory, TN, USA (Co-Chair) Akbar Kara: Ciena Corporation, TX, USA (Co-Chair) Nik Sultana: Illinois Institute of Technology, IL, USA Cees de Laat: Univ. of Amsterdam, Netherland Mariam Kiran: Oak Ridge National Laboratory, TN, USA -- http://www.cs.iit.edu/~nsultana1

1 2

RIPE 88 Student Event: What Keeps the Internet Working?
by Jelena Cosic 15 May '24

15 May '24

Dear colleagues, In a month, RIPE NCC will be hosting another RIPE meeting and this time around we're heading to the beautiful city of Krakow, Poland! The dates are May 20-24; registration for the meeting is still open and a draft agenda is published with the final version coming soon. For more details, check the official page: https://ripe88.ripe.net Pre-RIPE 88 Online student event On Tuesday May 7, NCC will organise a free online event aimed at people currently studying in the fields of networking, computer science, internet governance and other fields relevant to the RIPE community. The goal is to introduce them to the RIPE Community, encourage them to participate at the RIPE Meeting (in-person or online) and provide them with tips on how to make the most out of it. The planned duration of the event is 1h and 30 min. Speakers: - Valerie Aurora, systems programming consultant - Ben Cartwright-Cox, CEO at bgp.tools - Qasim Lone, Specialist Research Engineer at RIPE NCC - Mirjam Kühne, RIPE Chair - Jelena Ćosić, Community Builder at RIPE NCC NCC has also set aside a limited number of free student tickets (for all 5 days of the conference). We especially encourage students from Polish universities to apply, but the offer is extended to all. You can find more about the online event here: https://ripe88.ripe.net/programme/parallel-events/student-event Registration <https://meeting-registration.ripe.net/meeting-pub/registration?6&meetingId=…> for the online event is free and will be open until the day of the event. If you are working with students that might be interested in attending, we'd appreciate it if you could help with spreading the word around. Thank you! RACI at RIPE 88 We are glad to share the news that the RACI applicants for RIPE 88 have been selected. Congrats to Yury, Radu, Savvas, Pawel, Zubair and Sawsan! Here's the overview of their talks, don't miss them out: https://ripe88.ripe.net/programme/raci/ If you have any questions about the RIPE academic engagements, feel free to reach out to me. Kind regards, Jelena

1 1

Re: [RACI-list] [manrs-community] Routine Monitoring of Source Address Validation Deployment by Operators
by Lailson Araujo 26 Apr '24

26 Apr '24

Excelente iniciativa, desde já me disponho juntamente com a PJM Net ( AS266152) a ajudar no que estiver ao nosso alcance, assim como tambem consigo disponibilizar a VM necessária. Em sex., 26 de abr. de 2024 às 12:32, Brandon Zhi <Brandon(a)huize.asia> escreveu: > Dear MANRS and RIPE members, > > My name is Gaoxing Zhang, and I am a computer enthusiast from the High > School Competition Team at Hangzhou Dongfang High School. > > Recently, I've observed that although MANRS requirements mandate Source > Address Validation(SAV) for its members, some operators have not fully > implemented this practice in their networks. Therefore, I propose to > routinely monitor the deployment status of SAV across ASNs to ensure > compliance with MANRS guidelines and enhance network security. I am > currently unaware of any existing projects with a similar focus. > > It has come to my attention that operators at IXP facilities, even > including major entities like Google, fail to enable SAV. This issue also > persists in-home broadband services obtained through PPPoE, which could > lead to Infected Home Routers becoming sources of DDoS Attacks and Are > Difficult to Trace. In my tests, I announced my IP thought tunnel on a > different operator’s network and configured the Next-hop Address to a home > broadband gateway obtained via PPPoE. The results indicated that Source > Address Validation by China Telecom’s home broadband is only partially > implemented in Mainland China, with most IP addresses from the region being > accessible through this method. > > Here are some methods I have considered for ongoing monitoring: > > 1. Announce a new IP block upstream to receive inbound traffic. > 2. Deploy a tunnel on the device connected to the ISP being tested, which > will link to the upstream receiving the inbound traffic. > 3. The IP block will not be announced to the ISP being tested but only to > the upstream used to receive inbound traffic. Check the connectivity to > major public DNS servers when the Next-hop address is set to the ISP being > tested. > 4. If it is reachable, it indicates that the ISP’s device lacks Source > Address Validation. > > I plan to deploy test equipment at major IXPs (currently seeking equipment > sponsors) and access points for some residential ISPs (with the assistance > of volunteers). The testing environment will be a Linux-based VM, utilizing > Python to switch Next-hop based on test targets and assess the > accessibility to major public DNS servers, as well as to upload data to a > backend system. > > I would really appreciate it if you could share your valuable suggestions > or feedback on this initiative. > > Best regards, > *Brandon Zhang* > HUIZE LTD > www.huize.asia <https://huize.asia/>| www.ixp.su | Twitter > > This e-mail and any attachments or any reproduction of this e-mail in > whatever manner are confidential and for the use of the addressee(s) only. > HUIZE LTD can’t take any liability and guarantee of the text of the email > message and virus. > -- > Manrs-community mailing list > Manrs-community(a)elists.manrs.org > https://elists.manrs.org/mailman/listinfo/manrs-community > --

1 0

Routine Monitoring of Source Address Validation Deployment by Operators
by Brandon 26 Apr '24

26 Apr '24

Dear MANRS and RIPE members, My name is Gaoxing Zhang, and I am a computer enthusiast from the High School Competition Team at Hangzhou Dongfang High School. Recently, I've observed that although MANRS requirements mandate Source Address Validation(SAV) for its members, some operators have not fully implemented this practice in their networks. Therefore, I propose to routinely monitor the deployment status of SAV across ASNs to ensure compliance with MANRS guidelines and enhance network security. I am currently unaware of any existing projects with a similar focus. It has come to my attention that operators at IXP facilities, even including major entities like Google, fail to enable SAV. This issue also persists in-home broadband services obtained through PPPoE, which could lead to Infected Home Routers becoming sources of DDoS Attacks and Are Difficult to Trace. In my tests, I announced my IP thought tunnel on a different operator’s network and configured the Next-hop Address to a home broadband gateway obtained via PPPoE. The results indicated that Source Address Validation by China Telecom’s home broadband is only partially implemented in Mainland China, with most IP addresses from the region being accessible through this method. Here are some methods I have considered for ongoing monitoring: 1. Announce a new IP block upstream to receive inbound traffic. 2. Deploy a tunnel on the device connected to the ISP being tested, which will link to the upstream receiving the inbound traffic. 3. The IP block will not be announced to the ISP being tested but only to the upstream used to receive inbound traffic. Check the connectivity to major public DNS servers when the Next-hop address is set to the ISP being tested. 4. If it is reachable, it indicates that the ISP’s device lacks Source Address Validation. I plan to deploy test equipment at major IXPs (currently seeking equipment sponsors) and access points for some residential ISPs (with the assistance of volunteers). The testing environment will be a Linux-based VM, utilizing Python to switch Next-hop based on test targets and assess the accessibility to major public DNS servers, as well as to upload data to a backend system. I would really appreciate it if you could share your valuable suggestions or feedback on this initiative. Best regards, *Brandon Zhang* Huicast Telecom Limited www.huicast.com | Twitter This e-mail and any attachments or any reproduction of this e-mail in whatever manner are confidential and for the use of the addressee(s) only. Huicast Telecom Limited can’t take any liability and guarantee of the text of the email message and virus.

1 0

ACM IMC (May 15t submission deadline )
by Ignacio Castro 24 Apr '24

24 Apr '24

Dear colleagues, Please consider submitting your work to ACM IMC 2024<https://imc2024.hotcrp.com/>. Abstract registration (May 8th) and paper submission (May 15th) deadlines are quickly approaching (see details in the CFP below) We are looking forward to see your submission and you in Madrid! Best wishes, Ignacio Call For Papers, ACM IMC 2024 The Internet Measurement Conference (IMC) is a highly selective venue for the presentation of measurement-based research in data communications. As we are in the era of data-driven research, IMC 2024 will focus on improving the standard in the collection, usage, and sharing of network measurements for the research community. Despite the efforts in stimulating reproducibility of research as well as sharing of data, little progress has been made in our community to make research data open. Therefore, without fundamentally changing the topics in scope compared to previous years, our attention when assessing contributions will be particularly on the willingness of the authors to share their data and make their work reproducible. To encourage data sharing and reproducibility, authors will be required to make a declaration on artifact availability (full, partial, or no availability) for the submitted work. Since legitimate reasons (such as proprietary and privacy reasons) may prevent authors from sharing artifacts, papers will be assessed based on whether the contributions warrant acceptance despite the lack of artifact availability. In the case of no availability of artifacts, the authors are expected to explain why this is the case in a specific section. Artifact submission is not required at the paper submission time. All papers accepted to the program will be shepherded to ensure that the artifacts promised have been made available. IMC takes a broad view of contributions that are considered in scope for improving the practice of network measurement, including, but not limited to: * collection and analysis of data that yield new insights about network structure and network performance (e.g., traffic, topology, routing, energy utilization, performance) * collection and analysis of data that yield new insights about application and end-user behavior (e.g., economics, privacy, security, application interaction with protocols) * measurement-based modeling (e.g., workloads, scaling behavior, assessment of performance bottlenecks, causality) * methods and tools to monitor and visualize network-based phenomena * systems and algorithms that build on measurement-based findings * theoretical analysis and modeling of networked-systems and measurement techniques * novel methods for data collection, analysis, and storage (e.g., anonymization, querying, sharing) * reappraisal of previous empirical network measurements and measurement-based conclusions * descriptions of challenges and future directions the measurement community should pursue Networks of interest include: * Internet transit networks * edge networks, including home networks, broadband access networks (e.g., cable, fiber), and cellular networks * data center networks and cloud computing infrastructure * peer-to-peer, overlay, and content distribution networks * software-defined networks * online social networks * online services, platforms, and content providers * experimental networks, prototype networks, and future internetworks Replicability Track: IMC 2024 will continue the Replicability Track for submissions that aim to reproduce or replicate results that have been previously published at IMC. Papers accepted to this track will be published in ACM SIGCOMM Computer Communication Review (CCR). Priority will be given to replicability studies, although reproducibility studies are also in scope. For the definitions, please see ACM's site<https://www.acm.org/publications/policies/artifact-review-and-badging-curre…>. The authors of outstanding replicability papers may receive an invitation to present at the main conference. In that case, the paper would also be included in IMC's proceedings (rather than CCR). Submissions to this track are two-phase. Prospective authors are invited to submit an Expression of Interest (EoI) via the submission system in the form of an abstract which must explain: * Which paper the authors aim to replicate * Whether the paper will be replicated or reproduced * What the IMC community stands to learn from the replication or reproduction * Chosen approach, and why it will lead to new insights A small committee will evaluate the EoIs and their potential to be of interest to the IMC community. The authors of strong abstracts will receive an invitation to a full submission. The EoI serves to avoid misunderstandings and disappointment for authors as we acknowledge that replicating or reproducing a paper is a very significant effort to which potential authors would commit much time. Full submissions will then be assessed by the TPC. Full submissions must otherwise conform to the same criteria and rules as full submissions on the main track (see below). See the Important Dates section<https://conferences.sigcomm.org/imc/2024/#important-dates> for the EoI deadline. Full submissions have the same deadlines (abstract registration and full submission) as the IMC main deadline. Review process and criteria IMC 2024 invites two forms of submissions: * Full papers (up to 13 pages for text and figures + unlimited pages for references and appendix) that describe original research, with succinctness appropriate to the topics and themes they discuss. * Short papers (up to 6 pages for text and figures + unlimited pages for references and appendix) that convey work that is less mature but shows exciting promise, OR offer results that do not merit a full submission. Short papers could articulate a high-level vision and describe challenging future directions that the authors believe the community should tackle; validate, verify, or update important results; or present new ideas that challenge existing assumptions. Our plan is to assign a subset of the reviewers to the evaluation of short papers (only). These reviewers will be reminded of the specific expectations for short papers. Any submission exceeding the short paper page-length limit will be evaluated as a full paper. Authors should submit only original work that has not been published before and is not under submission to any other venue. We will consider full paper submissions that extend previously published short, preliminary papers (including IMC short papers), in accordance with the SIGCOMM policy<https://www.sigcomm.org/about/policies/frequently-asked-questions-faq/> and the ACM Plagiarism Policy<https://www.acm.org/publications/policies/plagiarism_policy>. The ACM policy on simultaneous submissions<https://www.acm.org/publications/policies/simultaneous-submissions> does not consider technical reports (including arXiv) to be concurrent publication or submission. The review process will have several reviewing rounds. To allow authors time to improve their work and submit to other venues, authors of submissions for which there is a consensus on rejection will be notified early. IMC 2024 will bestow three awards on paper submissions, (1) a Best Paper award; (2) a Best Student Paper award; and (3) a Community Contribution award. All accepted papers are eligible for the best paper award; the best student paper award is limited to papers whose main author is a student at the time of submission. The community contribution award will recognize a paper with an outstanding contribution to the community in the form of a new dataset, source code distribution, open platform, or other noteworthy service to the community. To be eligible for the community award, the authors must make data or source code publicly available or have a software artifact that is accessible and usable by the public at the time of the camera-ready deadline. The authors indicate their eligibility on the submission form and are also encouraged to include a link to the contribution in the submitted paper. A few accepted papers may be forwarded for fast-track submission to IEEE/ACM Transactions on Networking. Detailed submission instructions For all information about paper submission-including anonymity, ethics, use of generative AI, and paper formatting-please see the Detailed Submission Instructions page<https://conferences.sigcomm.org/imc/2024/submission-instructions/>. Expression of Interest (papers for the Replicability Track) Feb 28th, 2024 Notification for the Replicability Track Expression of Interest Mar 8th, 2024 Paper registration (with abstract, including invited papers to Replicability Track) May 8th, 2024 Paper submission (including invited papers to Replicability Track) May 15th, 2024 Early reject notification June 28th, 2024 Notification July 31st, 2024 Camera-ready due Sep 11th, 2024 Conference Nov 4th - 6th, 2024 Diversity and Inclusiveness As part of our efforts at fostering diversity and inclusiveness, we provide the following guidelines to assist you when preparing your paper submission and/or your conference presentation. Inclusivity Guidelines: Good technical writing often requires pedagogical examples to explain complex ideas. These provide an opportunity to promote inclusiveness by challenging implicit biases and assumptions. * Avoid gender-specific pronouns if possible. Where required, consider interspersing a balance of male ("he", "his"), female ("she", "her"), and gender-neutral ("they", "their") ones. * Use gender-neutral names in examples. Instead of Alice and Bob, try Alex and Jun. Consider names that reflect a variety of cultural backgrounds: Esteban, Naveena, Sasha, Sergey, Tuan, Xin, and so on. * Refrain from assuming binary gender. For instance, the "gender" column in a table of data should have more than just "male" and "female" values. * Be mindful of people's diverse backgrounds. Not everyone has two parents. Not every marriage involves "husband" and "wife". Not everyone lives in a house, or has a car. Accessibility Guidelines: Color and hearing perception varies from person to person depending on age, color blindness, distance, visual acuity, etc. Make sure that the contents of your paper are accessible to all, by considering the following: * Use patterns, symbols, and textures to emphasize and contrast visual elements in graphs and figures, rather than using colors alone. Graphs should be readable either in monochrome or color versions. * Use a color palette that is designed for visually-impaired or color-blind people. Avoid poor color combinations such as green/red or blue/purple. Submission Site Please submit your paper at https://imc2024.hotcrp.com<https://imc2024.hotcrp.com/>.

1 0

ANRW'24 deadline extension to Apr 22
by Ignacio Castro 12 Apr '24

12 Apr '24

Dear colleagues, We have extended the deadline for ANRW'24 by one week due to popular demand. The new deadline is: Apr 22, 2024, 11:59 PM AoE. Note that the travel grants application (May 10, 2024) and notification (May 24, 2024) deadline are now also available. See the CFP for more details<https://www.irtf.org/anrw/2024/cfp.html> and/or emails us if or have questions. Best, Jayasree, Simone, and Ignacio ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Call for Papers The ACM<https://www.acm.org/>/IRTF Applied Networking Research Workshop 2024 (ANRW'24), co-located with IETF-120<https://www.ietf.org/how/meetings/120/>, is the ninth edition of an academic workshop that provides a forum for researchers, vendors, network operators, and the Internet standards community to present and discuss emerging results in applied networking research. The workshop combines presentations of new research in the form of short papers and lightning papers. ANRW'24 accepts the following types of submissions: * Short papers are publications that present new research that has not been previously published. For a short paper to be considered for publication, please submit work describing early/emerging results in a relevant topic area. Position papers are also welcome. There is a 6-page limit for short papers, including figures, tables, and any appendices, optionally followed by unlimited additional pages for references. * Lightning papers can provide a summary of early, emerging, or on-going work as well as short updates of previously published work. Position papers are also welcome. This type of submission will be presented in a short, lightning-talk style. For a lightning paper to be considered for presentation, please submit an extended abstract that is no longer than 2 pages, with a maximum of one additional page for references only. Paper topics are not restricted to current standardization activities of related IETF working groups or activity in related IRTF research groups. We welcome papers on topics the IETF/IRTF should be looking at. We note that the structure and use of the Internet, and Internet services, are constantly evolving. The list is long, including but not limited to shifts in traffic patterns and demands with remote work over broadband access networks, operational responses to large-scale physical and socio-political events, also trends towards increased multiplexing of connections over fewer IP addresses for various reasons that include scale, adaptability, and privacy. * Development and deployment experience of new or enhanced Internet protocols (e.g., for transport, security, or routing). * Improvements, measurements, and analysis of the security and privacy of new and existing Internet protocols and privacy enhancing technologies. * Evolution of interconnection, and new approaches on network management, operations, and control. * Practical congestion control for heterogeneous networks and novel applications. * Better ways of specifying protocols, including usable techniques for protocol verification. * Interactions between CDNs, anycast, and edge services such as DNS and Firewalls. * Research and analysis of consolidation and centralization of the Internet. * Techniques for logging/monitoring of Internet traffic and root-cause analysis, as well as debugging of (encrypted) Internet protocols. * Measurement and analysis of the performance of networks, including the performance or quality of experience of networked applications. * Design, measurement, analysis, or deployment of wireless, mobile, and cellular networks. * Internet resilience and recovery in physically challenging environments and events (e.g., remote areas, natural disaster situations). * Approaches and efforts towards decentralizing and democratizing the Internet. * Understanding the impact and interoperability of diverse clients (e.g., IoT, robotics, manufacturing). * The changing semantics of IP addresses and connection-level metadata at large-scale (e.g. Addressing Agility, Private Relay). * Formal verification of protocols. * Topics relevant to the standardization activities of related IETF working groups. * Topics relevant to activity in related IRTF research groups. ANRW'24 is co-located with IETF-120<https://www.ietf.org/how/meetings/120/> in Vancouver, and takes place in the week of July 20-26, 2024. This gives IETF as well as workshop attendees the opportunity to exchange ideas on topics and open problems discussed at the workshop and the IETF. ANRW'24 will be a hybrid event. Remote participation options will be available; please contact the chairs if you intend to submit work but know in advance that you will not be able to present the work in-person at the workshop. ANRW'24 particularly encourages the submission of results that could form the basis for future engineering work in the IETF, by, for example providing input and analysis on Internet protocols or operational Internet practices, as well as influence further research and experimentation in the IRTF. Formatting All submissions must satisfy the following requirements: * Short papers: up to 6 pages for technical content (including appendices) + unlimited pages for references * Lightning papers: up to 2 pages for an extended abstract (including appendices) + a maximum of one page for references. * 10-point font for main text; font used in other places (e.g., figures) should be no smaller than 9 point * Two-column format, with the size of each column being at most 3.33 x 9.25 inches and the space between columns being at least 0.33 inches letter page size (8.5 x 11 inches) * Include names and affiliations of all authors on the title page (no anonymization). * We strongly encourage the use of the new ACM LaTeX template, which satisfies these style requirements provided you specify a 10-point font size. The following settings should produce this output: \documentclass[10pt,sigconf,letterpaper]{acmart} Submissions that do not comply with these requirements will be rejected without review. It is your responsibility to ensure that your submission satisfies the above requirements. Paper Novelty An accepted paper that is published must not be based on previously published work, and cannot describe work that is currently under submission to another venue. An accepted paper that is published also must not plagiarize the work of its authors or of any other authors. The ACM Policy and Procedures on Plagiarism applies to the ANRW, and action will be taken against submitters who have engaged in such practices. Papers accompanied by nondisclosure agreement requests will not be considered for review or publication, nor ever be disclosed. Reviews All submissions will be peer reviewed (single-blind). Reviews will be shared with the authors. Authors and TPC members provide conflict-of-interest information. It is important that all authors of a submission are indicated in the submission system and that all authors enter any conflicts of interest. Broadly, a conflict of interest exists when: * You are currently employed at the same organization, have been previously employed at the same organization within the last twelve months, or are going to begin employment at the same organization. * You have a past or present professional relationship, such as thesis advisement, collaboration on a project, publication, or grant proposal within the past two years. These are examples - use your own good judgement. ACM<https://www.acm.org/> Policies By submitting your article to an ACM<https://www.acm.org/> Publication, you are hereby acknowledging that you and your co-authors are subject to all ACM Publications Policies, <https://www.acm.org/publications/policies> including ACM<https://www.acm.org/>'s new Publications Policy on Research Involving Human Participants and Subjects. <https://www.acm.org/publications/policies/research-involving-human-particip…> Alleged violations of this policy or any ACM<https://www.acm.org/> Publications Policy will be investigated by ACM<https://www.acm.org/> and may result in a full retraction of your paper, in addition to other potential penalties, as per ACM<https://www.acm.org/> Publications Policy. Please ensure that you and your co-authors obtain an ORCID ID, <https://orcid.org/register> so you can complete the publishing process for your accepted paper. ACM<https://www.acm.org/> has been involved in ORCID from the start and we have recently made a commitment to collect ORCID IDs <https://authors.acm.org/author-resources/orcid-faqs> from all of our published authors. The collection process has started and will roll out as a requirement throughout 2022. We are committed to improve author discoverability, ensure proper attribution and contribute to ongoing community efforts around name normalization; your ORCID ID will help in these efforts. Important Dates Paper submission deadline: 22 April 2024 (11:59pm AoE) Paper notification deadline: 5 June 2024 Camera-ready paper deadline: 15 June 2024 Registration opens: (TBC) 2024 Travel grants application deadline: May 10 2024 Travel grants notification deadline: May 24 2024 ANRW '24 workshop: (TBC) July 2024 Submission site anrw2024.hotcrp.com<https://anrw2024.hotcrp.com/>

1 0

PhD and Postdoc position in Infrastructural Ideologies at the critical infrastructure lab at the University of Amsterdam
by Niels ten Oever 10 Apr '24

10 Apr '24

Dear friends, comrades, and colleagues, The [critical infrastructure lab](https://www.criticalinfralab.net/) at the University of Amsterdam offers a fully funded four-year PhD position and a fully funded two-year postdoc position. In the project, we will examine the structuration of internet infrastructure with a particular emphasis on the research-policy-implementation pipeline of communication controls. Through this work, we hope to find different infrastructural ideologies in the communications networks of the EU, Russia, and China. Please consider applying or sharing this with others who might be interested: PhD candidate position (application deadline May 10): https://vacatures.uva.nl/UvA/job/PhD-Position-in-Infrastructural-Ideologies… Postdoc position (application deadline May 1): https://vacatures.uva.nl/UvA/job/Postdoc-Infrastuctural-Ideologies-in-the-E… At the critical infrastructure lab, we are dedicated to researching power and contestation in transnational communication infrastructures. Our ultimate goal is to foster the development of alternative infrastructural futures that prioritize people and planet over profit and capital. All the best, Niels -- Niels ten Oever, PhD Co-Principal Investigator - critical infrastructure lab - University of Amsterdam Assistant Professor - Department of European Studies - University of Amsterdam W: https://criticalinfralab.net W: https://nielstenoever.net PGP: 4254 ECD5 D4CF F6AF 8B91 0D9F EFAD 2E49 CC90 C10C

1 0

ACM APSys calling for contributions
by Aaron Ding 06 Apr '24

06 Apr '24

For RACI community, ACM SIGOPS APSys is calling for submissions: 15th ACM SIGOPS Asia-Pacific Workshop on Systems (APSys 2024) Kyoto, Japan September 4-5, 2024 The 15th SIGOPS Asia-Pacific Workshop on Systems will be held in Kyoto, Japan on September 4-5, 2024. Building on the success of its predecessors, APSys 2024 will continue to be a lively forum for systems researchers and practitioners across the world to meet, interact, and collaborate with their peers from the Asia/Pacific region. APSys takes a broad view of systems, including but no limited to: * Operating systems * Virtualization * File and storage systems * Networked systems * Mobile, embedded, and IoT systems * Cloud computing and data centers * Edge computing * Big data systems * Distributed systems * Green and sustainable computing * Debugging, testing, verification * Measurement, monitoring, and modeling * Reliability, scalability, and fault tolerance * Security and privacy * Systems for machine learning, machine learning for systems * Hardware and software interaction * Experience with deployed systems * Blockchain and cryptocurrency systems # Submissions Submissions should be five or fewer pages in length excluding references, formatted in standard ACM two-column conference style with 10-pt font size. Authors should consult the ACM website (https://www.acm.org/publications/proceedings-template) for the up to date template. Reviewing will be double-blind: no author or affiliation information should appear in the submission. The authors should additionally follow the best practice in order not to disclose their identities implicitly. A submission may present preliminary results, propose a new research direction, provide insightful retrospective, or offer a provocative viewpoint on an important systems topic. Papers will be selected based on their likelihood of generating insightful technical discussions at the workshop and influencing future systems research. Relevant attributes include originality, technical merit, clarity, and technical relevance. Accepted papers will appear in the proceedings of the workshop, which will be published in the ACM Digital Library. Consistent with standard scholarly practice, the authors should not have substantially similar work in review anywhere else. Submissions can be made online at https://apsys24.hotcrp.com # Important Dates Abstract due: April 25, 2024 AoE Submission due: May 2, 2024 AoE Notification to authors: July 1, 2024 Camera-ready due: July 30, 2024 Workshop: September 4-5, 2024 Aaron

1 0