[Ndn-interest] NDN Protocol Design Principles

[Alex Afanasyev]

Dear all,

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.

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.

The latest version of the principles and additional information is available on NDN website:
http://named-data.net/project/ndn-design-principles/

* * *

For convenience, here is the current version of the list without additional information:

[1] **Universality**:
    NDN should be a common network protocol for all applications and network environments.

[2] **Data-Centricity and Data Immutability**:
    NDN should fetch uniquely named, immutable “data packets” requested using “interest packets”.

[3] **Securing Data Directly**:
    Security should be the property of data packets, staying the same whether the packets are in motion or at rest.

[4] **Hierarchical Naming**:
    Packets should carry hierarchical names to enable demultiplexing and provide structured context.

[5] **In-Network Name Discovery**:
    Interests should be able use incomplete names to retrieve data packets.

[6] **Hop-by-Hop Flow Balance**:
    Over each link, one interest packet should bring back no more than one data packet.

* * *

Sincerely,
Alex

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160310/732ccf68/attachment.bin>