<div dir="ltr">Hi Alex,<div> This is really an interesting topics, and I tried to summarize some principles too. And here is my comments.</div><div>1. The meaning of "NDN principle" is not very clear (at least to me). I think you do not refer to the design principle of NDN architecture itself, but more or less refer to NDN-based applications. But anyway, to clarify its meaning and usage would make it easier to understand. </div><div>2. I would say REST-style application layer interaction. Since no session is built between producer and consumer, Interest should not rely on context of communication in order to retrieve a data.</div><div>This also relates to Interest concurrency, here I mean how many Interests can be sent in parallel. I categories the Interests to two kinds: 1) safe one, which does not change the status of producer, but "read" data only; 2) sensitive one, which may change the status. When there is sensitive Interests, the sequence of Interests is critical; otherwise, multiple Interests can be sent in parallel for better throughput.</div><div>3. Apps do not have to worry about scalability, since multiple data source, caching and hop-by-hop flow control effectively enables app to scale its throughput. But apps should avoid to move NDN communication back to end-to-end style by building session manually. (although session may be a must for some apps.)</div><div><br></div><div>Xiaoke </div>
</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 11, 2016 at 3:46 PM, Alex Afanasyev <span dir="ltr"><<a href="mailto:aa@cs.ucla.edu" target="_blank">aa@cs.ucla.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear all,<br>
<br>
Recently, we have been working to formalize a list of basic principles that underly the design of the NDN architecture. We have assembled the initial list of 6 principles and would like to ask everybody for the all kind of feedback about the identified principles, other potential principles, wording clarification, etc.<br>
<br>
We also hope that the NDN design principles will start a new round of public architectural discussions, clarifying the current and future design decisions and overall architecture objectives.<br>
<br>
The latest version of the principles and additional information is available on NDN website:<br>
<a href="http://named-data.net/project/ndn-design-principles/" rel="noreferrer" target="_blank">http://named-data.net/project/ndn-design-principles/</a><br>
<br>
* * *<br>
<br>
For convenience, here is the current version of the list without additional information:<br>
<br>
[1] **Universality**:<br>
NDN should be a common network protocol for all applications and network environments.<br>
<br>
[2] **Data-Centricity and Data Immutability**:<br>
NDN should fetch uniquely named, immutable “data packets” requested using “interest packets”.<br>
<br>
[3] **Securing Data Directly**:<br>
Security should be the property of data packets, staying the same whether the packets are in motion or at rest.<br>
<br>
[4] **Hierarchical Naming**:<br>
Packets should carry hierarchical names to enable demultiplexing and provide structured context.<br>
<br>
[5] **In-Network Name Discovery**:<br>
Interests should be able use incomplete names to retrieve data packets.<br>
<br>
[6] **Hop-by-Hop Flow Balance**:<br>
Over each link, one interest packet should bring back no more than one data packet.<br>
<br>
* * *<br>
<br>
Sincerely,<br>
Alex<br>
<br>
<br>_______________________________________________<br>
Ndn-interest mailing list<br>
<a href="mailto:Ndn-interest@lists.cs.ucla.edu">Ndn-interest@lists.cs.ucla.edu</a><br>
<a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest" rel="noreferrer" target="_blank">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</a><br>
<br></blockquote></div><br></div>