idnits 2.17.1 draft-rahman-decade-survey-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 112 has weird spacing: '...f their servi...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (June 29, 2010) is 5048 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'ImageShack' is mentioned on line 108, but not defined == Unused Reference: 'I-D.draft-song-decade-problem-statement' is defined on line 235, but no explicit reference was found in the text == Unused Reference: 'I-D.draft-song-decade-survey' is defined on line 240, but no explicit reference was found in the text == Outdated reference: A later version (-02) exists of draft-song-decade-problem-statement-01 == Outdated reference: A later version (-04) exists of draft-song-decade-survey-03 Summary: 1 error (**), 0 flaws (~~), 8 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 DECADE Group A. Rahman 2 Internet Draft JC. Zuniga 3 Intended status: Informational InterDigital Communications, LLC 4 Expires: December 29, 2010 June 29, 2010 6 An Additional Survey of In-Network Storage Systems 7 draft-rahman-decade-survey-00 9 Abstract 11 This document describes some additional network based storage 12 systems to complement the surveys already performed in the DECADE 13 working group. 15 Status of this Memo 17 This Internet-Draft is submitted to IETF in full conformance with 18 the provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six 26 months and may be updated, replaced, or obsoleted by other documents 27 at any time. It is inappropriate to use Internet-Drafts as 28 reference material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html 36 This Internet-Draft will expire on December 29, 2010. 38 Copyright Notice 40 Copyright (c) 2010 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with 48 respect to this document. Code Components extracted from this 49 document must include Simplified BSD License text as described in 50 Section 4.e of the Trust Legal Provisions and are provided without 51 warranty as described in the BSD License. 53 Table of Contents 55 1. Introduction...................................................2 56 2. Conventions and Terminology....................................3 57 3. Photo Sharing..................................................3 58 3.1. Data Access Interface.....................................3 59 3.2. Data Management Operations................................4 60 3.3. Data Search Capability....................................4 61 3.4. Access Control Authorization..............................4 62 3.5. Resource Control Interface................................4 63 3.6. Discovery Mechanism.......................................4 64 3.7. Storage Mode..............................................5 65 4. Web Mail.......................................................5 66 4.1. Data Access Interface.....................................5 67 4.2. Data Management Operations................................5 68 4.3. Data Search Capability....................................5 69 4.4. Access Control Authorization..............................5 70 4.5. Resource Control Interface................................6 71 4.6. Discovery Mechanism.......................................6 72 4.7. Storage Mode..............................................6 73 5. Conclusions....................................................6 74 6. Security Considerations........................................6 75 7. IANA Considerations............................................6 76 8. References.....................................................7 77 8.1. Normative References......................................7 78 8.2. Informative References....................................7 79 9. Acknowledgments................................................7 81 1. Introduction 83 The DECADE (DECoupled Application Data Enroute) working group is 84 chartered to design and standardize an architecture and protocol 85 that will enable Peer-to-Peer (P2P) applications to utilize network 86 based storage systems as described in [I-D.draft-song-decade- 87 problem-statement]. 89 In this draft, we propose considering two key systems in addition to 90 the DECADE survey of existing in-network storage [I-D.draft-song- 91 decade-survey]. These systems include both P2P and other modes and 92 help provide further useful insights for DECADE. This document 93 responds to the call made at the IETF #77 meeting by the WG chair, 94 requesting the group to contribute to enhancing the existing survey. 96 2. Conventions and Terminology 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 100 document are to be interpreted as described in [RFC2119]. 102 3. Photo Sharing 104 There are a growing number of popular on line Photo Sharing 105 (storing) systems. For example, the Kodak Gallery system 106 [KodakGallery01] serves over 60 million users and stores billions of 107 images [KodakGallery02]. Other well known examples of Photo Sharing 108 systems include Flickr [Flickr] and ImageShack [ImageShack]. Also 109 there a number of popular blogging services, such as Tumblr 110 [Tumblr], which specialize in also sharing large number of photos 111 and other multimedia content (e.g. video, text, audio, etc.) as part 112 of their service. All these in-network storage systems utilize 113 both free and paid subscription models. 115 Most Photo Sharing systems use traditional client-server 116 architecture. However, a minority of systems also offer a P2P mode 117 of operation. 119 3.1. Data Access Interface 121 Users can read (view) and write (store) objects (photos). 123 3.2. Data Management Operations 125 Users can delete previously stored objects (photos). 127 3.3. Data Search Capability 129 Users can tag objects (photos) and/or organize them using 130 sophisticated web photo album generators. Users can then search for 131 objects (photos) matching desired criteria. 133 3.4. Access Control Authorization 135 We consider three types of Access Control Authorization: Public- 136 unrestricted, Public-restricted, and Private. Public-unrestricted 137 refers to content that is widely available to anyone (e.g. 138 Wikipedia.com). Public-restricted refers to content that is 139 available to a public which is restricted by certain criteria (e.g. 140 country or region), but does not require any confidential 141 credentials from the client. Finally, Private refers to content that 142 is only made available to clients presenting the required 143 credentials (e.g. password or key). 145 In the case of Photo Sharing, access to stored objects (photos) 146 typically can be Private, or Public-unrestricted. 148 3.5. Resource Control Interface 150 Not provided. 152 3.6. Discovery Mechanism 154 Usually by logging on to a central web page for the service and 155 entering the appropriate information to access the desired 156 information. 158 3.7. Storage Mode 160 Objects (photos) are usually stored as files. They can then be 161 organized into meta-structures (e.g. albums, galleries, etc.) using 162 sophisticated web photo album generators. 164 4. Web Mail 166 Web Mail systems are email services primarily accessed via a web 167 browser as opposed to a desktop email client. Well known examples 168 of Web Mail systems are Google Gmail, Yahoo Mail, and Microsoft 169 Hotmail. A key aspect of these web based mail systems is that they 170 offer a relatively large amount of in-network storage to store 171 emails and attachments. The amount of network storage typically 172 starts from 1GB free of charge, and goes up to larger amounts which 173 may be charged. Some Web Mail systems, such as Yahoo, now claim to 174 offer "unlimited amount of (network) storage" [WebMail]. All Web 175 Mail systems use traditional client-server architecture. 177 4.1. Data Access Interface 179 Users can read and write objects (email). 181 4.2. Data Management Operations 183 Users can delete previously stored objects (email). 185 4.3. Data Search Capability 187 Users can tag objects (email) and/or organize them into folders. 188 Users can then search for objects (email) matching desired criteria 189 (including searching text within the body of the email). 191 4.4. Access Control Authorization 193 Access is Private. 195 4.5. Resource Control Interface 197 Not provided. 199 4.6. Discovery Mechanism 201 Not provided. 203 4.7. Storage Mode 205 Objects (email) are usually stored as files. They can then be 206 organized into directories. 208 5. Conclusions 210 This draft describes two additional key in-network storage systems, 211 Photo Sharing and Web Mail, to be considered for the DECADE survey 212 of existing storage technologies. These two systems are very 213 popular and store a large amount of cumulative data in the network 214 and thus are instructive to consider for DECADE. 216 6. Security Considerations 218 This draft is a survey of existing in-network storage systems, and 219 does not introduce any security considerations beyond those of the 220 surveyed systems. 222 7. IANA Considerations 224 This document makes no request of IANA. 226 8. References 228 8.1. Normative References 230 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 231 Requirement Levels", BCP 14, RFC 2119, March 1997. 233 8.2. Informative References 235 [I-D.draft-song-decade-problem-statement] Song, H., Zong, N., Yang, 236 Y., Alimi, R., "DECoupled Application Data Enroute 237 (DECADE) Problem Statement", draft-song-decade-problem- 238 statement-01 (Work in progress), March 8, 2010. 240 [I-D.draft-song-decade-survey] Alimi, R., Lu, Z., Song, H., Yang, 241 Y., "A Survey of In-network Storage Systems", draft-song- 242 decade-survey-03 (Work in progress), March 8, 2010. 244 [KodakGallery01] Kodak, "Kodak Gallery Home Page", 245 http://www.kodakgallery.com/gallery/welcome.jsp 247 [KodakGallery02] Wikipedia, "Kodak Gallery", 248 http://en.wikipedia.org/wiki/Kodak_Gallery 250 [Flickr] Flickr, "Flickr Home Page", http://www.flickr.com/ 252 [Tumblr] Tumblr, "Tumblr Home Page", http://www.tumblr.com/ 254 [WebMail] Wikipedia, "Comparison of webmail providers", 255 http://en.wikipedia.org/wiki/Comparison_of_webmail_provide 256 rs 258 9. Acknowledgments 260 Thanks to Serhad Doken and Milan Patel for their useful comments and 261 discussions. 263 Authors' Addresses 265 Akbar Rahman 266 InterDigital Communications, LLC 267 Email: Akbar.Rahman@InterDigital.com 268 Juan Carlos Zuniga 269 InterDigital Communications, LLC 270 Email: JuanCarlos.Zuniga@InterDigital.com