idnits 2.17.1 draft-xue-decade-usecase-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 == The document doesn't use any RFC 2119 keywords, yet has text resembling RFC 2119 boilerplate text. -- The document date (March 5, 2012) is 4429 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'I-D.ietf-cdni-problem-statement-03' is mentioned on line 383, but not defined == Unused Reference: 'I-D.ietf-decade-problem-statement' is defined on line 469, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-decade-arch' is defined on line 474, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-cdni-problem-statement' is defined on line 478, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 6 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group H. Xue 3 Internet-Draft Tsinghua University 4 Intended status: Standards Track D. Wang 5 Expires: September 6, 2012 Huawei 6 March 5, 2012 8 DECADE Use Cases 9 draft-xue-decade-usecase-00 11 Abstract 13 The objective of DECADE is to provide storage access to Content 14 Distribution Applications to improve their efficiency and reduce load 15 on the network infrastructure. 17 In this document, we outline several potential use cases (not 18 technical solutions) for DECADE. These use cases may provide 19 motivations for DECADE. Interactions within DECADE and between 20 DECADE Servers and DECADE Clients are described at an abstract level 21 so as to not constrain future protocol development. 23 Status of this Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on September 6, 2012. 40 Copyright Notice 42 Copyright (c) 2012 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 3 59 3. Example Use Cases . . . . . . . . . . . . . . . . . . . . . . 4 60 3.1. P2P File Sharing . . . . . . . . . . . . . . . . . . . . . 4 61 3.2. End User Video Conference . . . . . . . . . . . . . . . . 5 62 3.3. Offline P2P live streaming . . . . . . . . . . . . . . . . 6 63 3.4. Social Networks . . . . . . . . . . . . . . . . . . . . . 7 64 4. Integration of DECADE and CDNI . . . . . . . . . . . . . . . . 9 65 4.1. Consideration of Integrating DECADE and CDNI . . . . . . . 9 66 4.2. An Example Use Case . . . . . . . . . . . . . . . . . . . 10 67 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 68 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 69 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 70 7.1. Normative Reference . . . . . . . . . . . . . . . . . . . 12 71 7.2. Informative Reference . . . . . . . . . . . . . . . . . . 12 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 74 1. Introduction 76 DECADE provides standard in-network storage for content distribution 77 applications. Specifically, with access to in-network storage, 78 content distribution applications can improve their efficiency and 79 reduce load on the network infrastructure. For example, instead of 80 always uploading data objects directly from a source/owner client to 81 a requesting client, the source/owner client can upload from in- 82 network storage, saving uplink bandwidth. 84 This document describes several use cases to motivate DECADE. These 85 use cases may provide motivations for the design and deployment of 86 DECADE. Also, a use case indicating our consideration of integrating 87 DECADE with CDNI is presented in this draft, in order to explore 88 potential benifits of combining them as well as possible further work 89 directions. 91 2. Terminologies 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHOULD", "WOULD", 94 "COULD", "CANNOT", "MIGHT", and "MAY"in this document are to be 95 interpreted as described in [RFC2119]. 97 We use the following terms that are defined [draft-ietf-decade-arch- 98 03]. 100 Provider based in-network storage: A service inside a network that 101 provides storage and bandwidth to network applications. In-network 102 storage may reduce upload/transit/backbone traffic and improve 103 network application performance. 105 DECADE Server: A DECADE Server stores data from Application End- 106 Points, and provides control and access of those data to Application 107 End-Points. Note that a DECADE Server is not necessarily a single 108 physical machine; it could also be implemented as a cluster of 109 machines. 111 DECADE Client: A DECADE Client stores and retrieves data at DECADE 112 Servers. 114 Application End-Point: An Application End-Point is an instance of a 115 Content Distribution Application that makes use of DECADE Server(s). 116 A particular Application End-Point may be a DECADE Content Provider, 117 a DECADE Content Consumer, or both. For example, an Application End- 118 Point may be an instance of a video streaming client, or it may be 119 the source providing the video to a set of clients. 121 3. Example Use Cases 123 3.1. P2P File Sharing 125 Related Applications: There are many P2P file sharing applications, 126 e.g., BitTorrent, Shareaza, Ares. The most widely used is 127 BitTorrent. 129 Original setting: In BiTorrent without DECADE, a client uploads to 130 its peers using its last mile. This consumes expensive last-mile 131 uplink bandwidth. 133 BiTorrent with DECADE: In the new setting, a client first uploads to 134 a DECADE Server, who can then serve other clients. 136 Figure 1 shows an example. In this example, Client B first uploads 137 shared files to DECADE Server B, then Client A and Client C can get 138 the file by their DECADE Servers. 139 +-------------------+ +-------------------+ 140 | | | | 141 | DECADE Server A | | DECADE Server C | 142 | | | | 143 +-------------------+ +-------------------+ 144 | ^ ^ | 145 | \ / | 146 | \ / | 147 | \ / | 148 | \ / | 149 | \ / | 150 | \ / | 151 | +-------------------+ | 152 | | | | 153 | | DECADE Server B | | 154 | | | | 155 | +-------------------+ | 156 | ^ | 157 | | | 158 V | V 159 +----------+ +----------+ +----------+ 160 | | | | | | 161 | Client A | | Client B | | Client C | 162 | | | | | | 163 +----------+ +----------+ +----------+ 165 Figure 1 167 Benefits: in Original setting, Client B may need send content to both 168 Client A and Client C, while in DECADE Client B only need send the 169 shared file to its DECADE server for one time. This saves last mile 170 uplink bandwidth, which is expensive. 172 3.2. End User Video Conference 174 Related Applications: There are multiple widely video conference 175 applications, including Skype, Webex. The end users using the 176 conference applications can be either desktop based or mobile 177 devices. 179 Video Conference without DECADE: As it is shown if figure 2, Client A 180 and Client C send the voice and video to Client B, Client B mix its 181 own packets with those send from Client A and Client C, then send the 182 mixed packets to them. 183 +----------+ A+C +----------+ A+B +----------+ 184 | | <------ | | ------> | | 185 | Client A | | Client B | | Client C | 186 | | ------> | | <------ | | 187 +----------+ B +----------+ C +----------+ 189 Figure 2 191 Video Conference with DECADE: Figure 3 shows a example of video 192 conference using DECADE. In this example, each client upload its 193 video and audio data for one time, and DECACE Servers will mixed the 194 packets and send to each users. 196 +----------+ 197 | | 198 | Client A | 199 | | 200 +----------+ 201 ^ | 202 B+C | | A 203 | | 204 | V 205 +-------------------+ 206 | | 207 | DECADE Server A | 208 | | 209 +-------------------+ 210 ^ ^ 211 B / \ C 212 / \ 213 / A A \ 214 V V 215 +-------------------+ +-------------------+ 216 | | C | | 217 | DECADE Server B | <--------> | DECADE Server C | 218 | | B | | 219 +-------------------+ +-------------------+ 220 ^ | ^ | 221 B | | A+C C | | A+B 222 | V | V 223 +----------+ +----------+ 224 | | | | 225 | Client B | | Client C | 226 | | | | 227 +----------+ +----------+ 229 Figure 3 231 Benefits: in Original setting, the mixer (Client B in figure 2) need 232 upload twice, while in Video Conference with DECADE each user only 233 need upload its video and audio for one time. This saves last mile 234 uplink bandwidth. 236 3.3. Offline P2P live streaming 238 Related Applications: There are many P2P live streaming applications, 239 e.g., PPLive, PPStream. 241 Original setting: In P2P live streaming without DECADE, clients may 242 get a bad user experience when they watch the streaming after 243 broadcasting at a later time, Since there will be not enough 244 audiences to watch it after living broadcast. 246 P2P live streaming with DECADE: By using DECADE, a client can watch a 247 live streaming at a later time, and still have a good video quality. 249 Figure 4 shows an example. In this example, Client B is broadcasting 250 a live streaming. Client C is offline and wants to watch this 251 streaming at a later time. DECADE Server C will hold the living 252 streaming data for Client C. After Client C once is online, it can 253 get the streaming directly for its DCEADE Server C. 254 +-------------------+ +-------------------+ 255 | | <---------------- | | 256 | DECADE Server A | | DECADE Server C | 257 | | ----------------> | | 258 +-------------------+ +-------------------+ 259 | ^ ^ | 260 | \ / . 261 | \ / | 262 | \ / . 263 | \ / | 264 | \ / . 265 | \ / | 266 | +-------------------+ . 267 | | | | 268 | | DECADE Server B | . 269 | | | | 270 | +-------------------+ . 271 | ^ | 272 | | . 273 V | V 274 +----------+ +----------+ +----------+ 275 | | | | | | 276 | Client A | | Client B | | Client C | 277 | | | | | | 278 +----------+ +----------+ +----------+ 280 Figure 4 282 Benefits: in Original setting, clients missed living streaming 283 broadcast, may get a bad video quality when they watch it at a latter 284 time. While in DECADE the video quality is also good since Client C 285 download it directly from its DECADE Server. Also, DECADE can help 286 to save last mile uplink bandwidth in this use case. 288 3.4. Social Networks 290 Related Applications: Facebook, Renren. 292 Social Networks without DECADE: As it is shown in figure 5, Client A 293 post a message to Facebook Server, then the Server update this 294 message to Client B, Client C and Client D. There are data 295 transmission both in inter-domain and intra-domain. 296 +------------------------------------------------------+ 297 | +----------+ ISP | 298 | | | | 299 | +----------| Client A | | 300 | | | | | 301 | | +----------+ | 302 | | | 303 | | | 304 | | | 305 | +--------------+ +----------+ | 306 | | | | | 307 | | +-------------------->| Client B | | 308 | | | | | | 309 | | +----------+ +----------+ | 310 | | | | | 311 | | | | | 312 | | | | +----------+ | 313 | | | | | | | 314 | | | +--------->| Client C | | 315 | | | | | | 316 | | | +----------+ | 317 +--------|---|-----------------------------------------+ 318 | | 319 | | 320 V | 321 +---------+ 322 | | +----------+ 323 | Facebook| | | 324 | Server |--------------->| Client D | 325 | | | | 326 +---------+ +----------+ 328 Figure 5 330 Social Networks using DECADE: Figure 6 shows Facebook using DECADE. 331 Client A post the message to its DECADE Server X, then DECADE Server 332 X will update these clients in intra-domain, simultaneously update 333 Facebook Server. 335 +------------------------------------------------------+ 336 | +----------+ ISP | 337 | | | | 338 | +----------| Client A | | 339 | | | | | 340 | | +----------+ | 341 | | | 342 | | | 343 | +---------+ | | 344 | | |<----+ +----------+ | 345 | | DECADE | | | | 346 | | Server |--------------->| Client B | | 347 | | X | | | | 348 | | |-----+ +----------+ | 349 | +---------+ | | 350 | | | | 351 | | | +----------+ | 352 | | | | | | 353 | | +--------->| Client C | | 354 | | | | | 355 | | +----------+ | 356 +------------|-----------------------------------------+ 357 | 358 | 359 V 360 +---------+ 361 | | +----------+ 362 | Facebook| | | 363 | Server |--------------->| Client D | 364 | | | | 365 +---------+ +----------+ 367 Figure 6 369 Benefits: Cut down data transmission in inter-domain. And also 370 DECADE Server will help to reduce Facebook Server load. 372 4. Integration of DECADE and CDNI 374 4.1. Consideration of Integrating DECADE and CDNI 376 As mentioned above, DECADE provides standard in-network storage for 377 content distribution applications, which can reduce load on internet 378 infrastructure as well as improve the efficiency of these 379 applications. CDNI is aimded at providing uniformed interfaces over 380 which two or more CDNs communicate with each other in order to 381 achieve the delivery of content to User Agents by Surrogates in one 382 CDN (the downstream CDN) on behalf of another CDN (the upstream 383 CDN)[I-D.ietf-cdni-problem-statement-03]. The work of DECADE and 384 CDNI are complementary to each other in some respects. DECADE 385 architecture and mechanism can be used for data exchange between 386 different CDNs, while CDNI supports negotiation between them, in 387 which upstream CDN could indicate the downstream CDN to acquire 388 content from certain in-network storages (DECADE Servers). 390 4.2. An Example Use Case 392 Taking Multi-player Online Game application as an example, Figure 8 393 shows the idea of integrating DECADE and CDNI. In this example, both 394 Client A and Client B belong to CDN-1, while Client C is connected to 395 CDN-2. Each Client store its own game-related data to its own DECADE 396 Server and also retrieve other Clients' data from it. The 397 communication between CDN-1 and CDN-2 is conducted by CDNI. Through 398 CDNI, the upstream CDN indicates where its downstream CDN could 399 retrieve data it wants. 401 +-------------------+ +-------------------+ 402 | | | | 403 | DECADE Server A | | DECADE Server C | 404 | | | | 405 +-------------------+ +-------------------+ 406 ^ ^ ^ ^ 407 | \ / | 408 | \ / | 409 | \ / | 410 | \ / | 411 | \ / | 412 | v v | 413 | +-------------------+ | 414 | | | | 415 | | DECADE Server B | | 416 | | | | 417 | +-------------------+ | 418 | ^ | 419 | | | 420 | | | 421 v v v 422 +----------+ +----------+ +----------+ 423 | | | | | | 424 | Client A | | Client B | | Client C | 425 | | | | | | 426 +----------+ +----------+ +----------+ 427 | | | 428 | | | 429 | | | 430 | | | 431 -------------------- | 432 | | 433 | | 434 | | 435 +----------+ +----------+ 436 | | CDNI | | 437 | CDN-1 |<------------------>| CDN-2 | 438 | | | | 439 +----------+ +----------+ 441 Figure 8 443 Benefits: The integration of DECADE and CDNI may result in improved 444 quality of experience for end users, as well as reduced last-mile 445 uplink bandwidth. The benefits may not be obvious when there are 446 only few content delivery between two different CDNs, but it may have 447 significant benefits in certain situations. 449 TBA. 451 5. Security Considerations 453 This draft does not introduce any security considerations beyond 454 those of these use cases. 456 6. IANA Considerations 458 This document has no actions for IANA. 460 7. References 462 7.1. Normative Reference 464 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 465 Requirement Levels", March 1997. 467 7.2. Informative Reference 469 [I-D.ietf-decade-problem-statement] 470 Song, H., Zong, N., Yang, Y., and R. Alimi, "DECoupled 471 Application Data Enroute (DECADE) Problem Statement", 472 March 2011. 474 [I-D.ietf-decade-arch] 475 Alimi, R., Yang, Y., Kutscher, D., and H. Liu, "DECADE 476 Architecture", July 2011. 478 [I-D.ietf-cdni-problem-statement] 479 Ben, N., Francois, F., and B. Nabil , "Content 480 Distribution Network Interconnection (CDNI) Problem 481 Statement", Jan 2012. 483 Authors' Addresses 485 Xue Haiwei 486 Tsinghua University 487 Tsinghua University 488 Beijing, 100000 489 P.R.China 491 Phone: 492 Fax: 493 Email: heavyxue@gmail.com 495 Wang Danhua 496 Huawei 497 No. 101 Software Avenue 498 Nanjing, Jiangsu Province 210001 499 P.R.China 501 Phone: +86-25-56624734 502 Fax: +86-25-56624702 503 Email: wangdanhua@huawei.com