A Survey of In-Network Storage Systems
RFC 6392

Note: This ballot was opened for revision 06 and is now closed.

(Wesley Eddy) (was Discuss) Yes

(David Harrington) Yes

(Jari Arkko) No Objection

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

Comment (2011-08-08 for -)
The draft references the DECADE problem statement draft for further discussions on use cases. Additionally, it might be useful to provide a brief description (e.g., a one liner) of the prototypical use case for DECADE. For example the problem statement draft provides this example:

"As a simple example, a peer of a P2P application may upload to other peers through its in-network storage,
saving its usage of last-mile uplink bandwidth."

In the section on Amazon S3, an additional example of a third-party service (which is very popular nowadays) that uses it would be dropbox.

(Ralph Droms) No Objection

Comment (2011-08-09 for -)
Minor editorial suggestions.

In section 4.5.2:

   The content
   provider can access network edge servers and store content on them.
   Or edge servers can retrieve content from content providers.

Combine these two sentences into one with a comma.

In section 4.7:

   A key aspect of NDN is that router have the capability


(Adrian Farrel) No Objection

Comment (2011-08-06 for -)
Thanks for a readable and informative document.  I have just a few
very petty comments.


The Abstract says...

   This document surveys deployed and experimental in-network storage
   systems and describes their applicability for DECADE.

This may be too terse. Replacing "DECADE" with the name of the working 
group doesn't really help. Can you spell out what you mean by "DECADE"


Section 1

   High-capacity and low-cost in-network storage devices introduces



   Deploying a CDN for publicly
   available content is expensive.

Is the price really a function of whether the content is publicly 


   Second, applications may benefit from explicit control of in-network
   storage, which P2P caches do not provided.




   CDMI-specific operations are specified in
   which data objects are embedded as fields inside of a JavaScript
   Object Notation (JSON) object, but the protocol also defines
   interfaces in which the contents of data objects can be written via
   simple HTTP GET/PUT operations.

I can't parse the start of the sentence.


Section 4.5

   A Content Delivery Network (CDN) provides services that improve
   network performance by maximizing bandwidth, improving accessibility
   and maintaining correctness through content replication.

Technically they don't change the bandwidth. I'm not sure they maximize
the utilized bandwidth either. But I'm being pedantic.



   A key aspect of NDN is that router have the capability to cache the




   In addition, making use of P2P caches
   do not require changes to P2P protocols and can be deployed
   transparently from clients.

s/do not/does not/



   P2P caches operate similarly to web caches, in that they temporarily

Could use a forward pointer to 4.14

(Stephen Farrell) No Objection

(Russ Housley) No Objection

Comment (2011-08-10 for -)
  Please consider the comments from the Gen-ART Review by
  Kathleen Moriarty on 18-July-2011.  The review can be found here:

(Pete Resnick) No Objection

(Peter Saint-Andre) No Objection

(Robert Sparks) No Objection

(Sean Turner) No Objection