<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p></p>
<div>Dear Gala,</div>
<div><span style="font-size:12pt"><br>
</span></div>
<div><span style="font-size:12pt">I have just sent the acceptance email to all five authors of Paper #75.</span></div>
<div><br>
</div>
<div>If you encounter any issues, please let us know.</div>
<div><br>
</div>
<div>Best wishes,</div>
<div>Young-ri</div>
<br>
<p></p>
<p></p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>보낸 사람:</b> Gala Yadgar via Hotstorage-chairs <hotstorage-chairs@fsl.cs.sunysb.edu> 대신 Hotstorage-chairs <hotstorage-chairs-bounces@fsl.cs.sunysb.edu><br>
<b>보낸 날짜:</b> 2026년 8월 20일 목요일 오후 9:17:03<br>
<b>받는 사람:</b> chairs26@hotstorage.org<br>
<b>제목:</b> Re: [Hotstorage-chairs] [HotStorage 2026] Accepted submission #75 "Towards A System Model for DNA-based..."</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Dear Young-ri and Bryan,<br>
I am writing to ask help in a small administrative matter: when we submitted the paper, we neglected to mark the students (first two authors) as contact authors in HotCRP.<br>
The second author, Libi Kogan, will present the paper at the conference. To approve my funding of her travel, the university requires an acceptance email addressed to her. Is it possible for you to re-send the acceptance notice to all authors (contact and non-contact)
or even just to her?<br>
Her full details are as they appear in HotCRP: Libi Kogan (Technion – Israel Institute of Technology) <libi.kogan@campus.technion.ac.il>.<br>
<br>
Thanks in advance,<br>
Gala<br>
<br>
-----Original Message-----<br>
From: HotStorage 2026 HotCRP <noreply-hotstorage26@hotcrp.com><br>
Sent: Saturday, July 25, 2026 5:59<br>
To: Dalit Naor <dalit.naor@mta.ac.il>; Michael Factor <factor@il.ibm.com>; Gala Yadgar <gala@cs.technion.ac.il><br>
Subject: [HotStorage 2026] Accepted submission #75 "Towards A System Model for DNA-based..."<br>
<br>
[You don't often get email from noreply-hotstorage26@hotcrp.com. Learn why this is important at
<a href="https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fprotect.checkpoint.com%2fv2%2fr02%2f___https%3a%2f%2faka.ms%2fLearnAboutSenderIdentification___.YzJlOnRlY2huaW9uOmM6bzpmNzc4Mzk5YWI0ZTkyNmI0ODIyNjE1OWE2ZTZiOGVhMjo3OjUzMTE6ZWRjODVmZThjMWVhNmMxNTFjZGEzNjlmYzU3MWFjYTNiNmQyNjVmNjJiMmY2YWMyNGUyODQ0YjM2YjcxZTEyOTpwOlQ6Rg&c=E,1,CzbXcuDynmzxW7Uht10F1jRbGe1JViAP1kds4lIk7qMjAtotKZU_0RySbQHGBH5hAI1cWVZWcUQ6Jom_WkPK61YLQAQjsIJ50J_fqcddWupvMESQq3hRyU53heEX&typo=1">
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fprotect.checkpoint.com%2fv2%2fr02%2f___https%3a%2f%2faka.ms%2fLearnAboutSenderIdentification___.YzJlOnRlY2huaW9uOmM6bzpmNzc4Mzk5YWI0ZTkyNmI0ODIyNjE1OWE2ZTZiOGVhMjo3OjUzMTE6ZWRjODVmZThjMWVhNmMxNTFjZGEzNjlmYzU3MWFjYTNiNmQyNjVmNjJiMmY2YWMyNGUyODQ0YjM2YjcxZTEyOTpwOlQ6Rg&c=E,1,CzbXcuDynmzxW7Uht10F1jRbGe1JViAP1kds4lIk7qMjAtotKZU_0RySbQHGBH5hAI1cWVZWcUQ6Jom_WkPK61YLQAQjsIJ50J_fqcddWupvMESQq3hRyU53heEX&typo=1</a>
]<br>
<br>
Dear authors,<br>
<br>
The program committee for the 2026 ACM Workshop on Hot Topics in Storage and File Systems (HotStorage 2026) is delighted to inform you that your submission #75 has been accepted to appear in the workshop.<br>
<br>
* Title: Towards A System Model for DNA-based Storage<br>
* Site: <a href="https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fprotect.checkpoint.com%2fv2%2fr02%2f___https%3a%2f%2fhotstorage26.hotcrp.com%2fpaper%2f75___.YzJlOnRlY2huaW9uOmM6bzpmNzc4Mzk5YWI0ZTkyNmI0ODIyNjE1OWE2ZTZiOGVhMjo3OmUxMGE6NDM3ZDIzMmI5NzQ0OTUyZjlkZDRmNDZhYjY4ZTkzOGUyYTg4NzFiNTEyNTcxMzk4ZWY3YTAyMTJhMGMzOWVlMjpwOlQ6Rg&c=E,1,JPSos0eDRJB0HOhX7j1PprgWTxOFPlF1u8002KX5qjwr1SpJ-VNOjpPM4jC2AoUmrOxGN1k7-M75QVc8tbeeKKPtmUjFoTbBAw71M1yt_mLjBAaUXwE1tQE,&typo=1">
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fprotect.checkpoint.com%2fv2%2fr02%2f___https%3a%2f%2fhotstorage26.hotcrp.com%2fpaper%2f75___.YzJlOnRlY2huaW9uOmM6bzpmNzc4Mzk5YWI0ZTkyNmI0ODIyNjE1OWE2ZTZiOGVhMjo3OmUxMGE6NDM3ZDIzMmI5NzQ0OTUyZjlkZDRmNDZhYjY4ZTkzOGUyYTg4NzFiNTEyNTcxMzk4ZWY3YTAyMTJhMGMzOWVlMjpwOlQ6Rg&c=E,1,JPSos0eDRJB0HOhX7j1PprgWTxOFPlF1u8002KX5qjwr1SpJ-VNOjpPM4jC2AoUmrOxGN1k7-M75QVc8tbeeKKPtmUjFoTbBAw71M1yt_mLjBAaUXwE1tQE,&typo=1</a><br>
<br>
23 of 78 submissions were accepted. Congratulations!<br>
<br>
The camera-ready version is due August 12, 2026 (Wednesday); this is a hard deadline. The page limit for the camera-ready version is 6 pages, excluding the references. Please improve your draft by addressing the concerns mentioned in the reviews.<br>
<br>
Please visit the HotStorage'26 HotCRP site for reviews, comments, and related information. Reviews and comments are also included below.<br>
<br>
Contact PC chairs <chairs26@hotstorage.org> with any questions or concerns.<br>
<br>
Sincerely,<br>
Young-ri Choi and Bryan S. Kim<br>
HotStorage 2026 Program Co-Chairs<br>
<br>
Review #75A<br>
===========================================================================<br>
<br>
Overall merit<br>
-------------<br>
4. Accept<br>
<br>
Reviewer expertise<br>
------------------<br>
3. Knowledgeable<br>
<br>
Paper summary<br>
-------------<br>
The paper presents a system model for DNA storage that captures key biological and operational constraints, including limited pool capacity, object count, read endurance, and replenishment requirements. The results show that improving density and primer libraries
alone is insufficient, and that practical DNA storage systems also need higher read limits, efficient bulk retrieval, and DNA-aware management policies to preserve long-term durability.<br>
<br>
Comments for authors<br>
--------------------<br>
Thank you for submitting the paper to HotStorage’26. The paper introduces an interesting and timely perspective on DNA storage, especially for the systems community. Although the analysis is based on relatively simple statistical models and simulated scenarios,
the paper offers valuable insights by highlighting system-level constraints and design implications that are often overlooked in DNA storage research. I appreciate the paper’s framing and believe it opens several promising research directions for future DNA
storage systems. The main takeaways are also clear, interesting, and valuable for the community.<br>
<br>
<br>
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *<br>
<br>
<br>
Review #75B<br>
===========================================================================<br>
<br>
Overall merit<br>
-------------<br>
3. Weak accept<br>
<br>
Reviewer expertise<br>
------------------<br>
1. No familiarity<br>
<br>
Paper summary<br>
-------------<br>
This paper presents the first system-level abstraction of DNA storage by modeling its key biological constraints with three parameters: objects per pool, pool capacity, and read limit. Through simulation, it reveals several counterintuitive tradeoffs. Increasing
pool size without a proportional increase in read limit leads to excessive replenishment synthesis costs. Object-level hash replication balances load but widens the hydration blast radius, accelerating DNA decay. Traditional LRU caching, unaware of physical
pool state, cannot fundamentally eliminate the need to recover data from expended pools. Based on these findings, the paper argues that future caching, replication, and placement policies must be aware of whether pools are dry, wet, or expended, making DNA-aware
management a necessary condition for system optimization.<br>
<br>
Comments for authors<br>
--------------------<br>
Thank you for submitting your manuscript to HotStorage'26. Below are my detailed comments and recommendations.<br>
<br>
Strengths:<br>
- The paper addresses a timely and important gap by abstracting DNA storage into a system-level model, enabling storage researchers to reason about this medium without deep biochemical expertise.<br>
- The simulation reveals several non-intuitive and practically relevant tradeoffs, such as the tension between pool size and replenishment cost when read limits do not scale, and the hydration blast radius caused by object-level replication.<br>
- The work clearly establishes the need for DNA-aware management policies and provides a set of concrete takeaways that effectively define a research agenda for the community.<br>
<br>
Weaknesses:<br>
- The model and the interactions among its parameters (pool size, read limit, hydration state, replenishment overhead) are described and explained entirely through text, which makes it hard for readers to follow the proposed model. A mathematical formulation
or a structural diagram that captures these relationships of the model would significantly improve readability and allow others to verify or extend the analysis.<br>
- The current abstraction oversimplifies several DNA-specific characteristics that could materially affect the conclusions. For example, the model does not incorporate the time-dependent degradation rate of DNA in hydrated pools, which determines how urgently
replenishment must happen, nor does it account for variable object sizes and the resulting packing constraints within fixed-capacity pools with a limited primer library. Incorporating even a simple representation of these factors, or explicitly discussing
their expected impact, would make the results more grounded and the storage policy implications more convincing.<br>
<br>
<br>
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *<br>
<br>
<br>
Review #75C<br>
===========================================================================<br>
<br>
Overall merit<br>
-------------<br>
3. Weak accept<br>
<br>
Reviewer expertise<br>
------------------<br>
2. Some familiarity<br>
<br>
Paper summary<br>
-------------<br>
The paper presents a system model of DNA storage to capture various constraints and analyze their system-level implications. The authors conclude that DNA storage requires fundamentally different system designs than conventional digital storage.<br>
<br>
Comments for authors<br>
--------------------<br>
There is a need for exploring systems issues regarding DNA storage and this paper is therefore timely.<br>
<br>
The def used for Zipf is somewhat non-std as it is given as 1/i^a. Should a be not negative? Setting a=1 (as mentioned in the paper) seems problematic as the normalization factor diverges if the number of objects is unbounded. (For more details see the wikipedia
entry on Zipf law where the normalization factor is discussed.)<br>
<br>
While "device-independence" is a good goal, it is not clear what parameters can be ignored and what cannot be. In the case of a HDD, rotational latencies were considered in early designs but buffering techniques made this not that critical (though imp still
when desiring high perf on large problems). For example, on p. 2, "we assume that the pool’s content can be retrieved for replenishment purposes, either by a “bulk-read” operation or by reserving a portion of its read limit." It is not clear if and when some
aspect of the system like the time taken for this bulk-read has to be taken as an important design parameter just as pool expiration time has been discussed in the paper. More importantly, whether some parameter is imp or not is based on the workload, computational
resources avlbl (whether internally avlbl thru "biological logic" or thru digital logic) if errors have to be corrected...<br>
<br>
An imp part of the problem is working with external digital systems. In this case, the analog of "ADC" conversion or the reverse (from digital logic to dna representation, and vice versa) can be a bottleneck. What is the breakpoint?<br>
<br>
There are also higher level "flow" issues such as the "balance" betw the size of information transfer from one pool to another and the size of read in a pool. These need to be discussed also.<br>
<br>
Comment @A1 by Reviewer A<br>
---------------------------------------------------------------------------<br>
The paper presents a timely system-level model of DNA storage that captures key biological and operational constraints, including pool capacity, object count, read endurance, hydration state, and replenishment. Reviewers found the paper’s framing, counterintuitive
findings, and research agenda valuable to the storage community, while noting that the model could be strengthened through clearer formalization and discussion of additional factors such as degradation, variable object sizes, etc.<br>
<br>
<br>
External e-mail, be judicious when opening attachments or links<br>
-- <br>
Hotstorage-chairs mailing list<br>
Hotstorage-chairs@fsl.cs.sunysb.edu<br>
<a href="https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.fsl.cs.sunysb.edu%2fmailman%2flistinfo%2fhotstorage-chairs&c=E,1,1WWATaImIyolZYK0ZOEJkBfXBI6G3JHB1Uq39D479FVMxECPNuKmnUVTyopEIP3pw5tXh4UG3vuJpOMJzBHW7Z7IbhQ8BrOqKbpjUtUaHbGNUAqQCV6a1CVWutNV&typo=1">https://lists.fsl.cs.sunysb.edu/mailman/listinfo/hotstorage-chairs</a><br>
</div>
</span></font>
</body>
</html>