draft-ietf-decade-arch-08.txt   draft-ietf-decade-arch-09.txt 
DECADE R. Alimi DECADE R. Alimi
Internet-Draft Google Internet-Draft Google
Intended status: Informational A. Rahman Intended status: Informational A. Rahman
Expires: January 14, 2013 InterDigital Communications, LLC Expires: February 14, 2013 InterDigital Communications, LLC
D. Kutscher D. Kutscher
NEC NEC
Y. Yang Y. Yang
Yale University Yale University
July 13, 2012 August 13, 2012
DECADE Architecture DECADE Architecture
draft-ietf-decade-arch-08 draft-ietf-decade-arch-09
Abstract Abstract
Content Distribution Applications (e.g., P2P applications) are widely Content Distribution Applications (e.g., P2P applications) are widely
used on the Internet and make up a large portion of the traffic in used on the Internet and make up a large portion of the traffic in
many networks. One technique to improve the network efficiency of many networks. One technique to improve the network efficiency of
these applications is to introduce storage capabilities within the these applications is to introduce storage capabilities within the
networks; this is the capability provided by a DECADE (DECoupled networks; this is the capability provided by a DECADE (DECoupled
Application Data Enroute) compatible system. This document presents Application Data Enroute) compatible system. This document presents
an architecture, discusses the underlying principles, and identifies an architecture, discusses the underlying principles, and identifies
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 14, 2013. This Internet-Draft will expire on February 14, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 27, line 19 skipping to change at page 27, line 19
on stored objects, but Application End-Points MUST NOT rely on that. on stored objects, but Application End-Points MUST NOT rely on that.
In other words, Application End-Points SHOULD perform name-object In other words, Application End-Points SHOULD perform name-object
binding validation on received objects. binding validation on received objects.
8. IANA Considerations 8. IANA Considerations
This document does not have any IANA considerations. This document does not have any IANA considerations.
9. Acknowledgments 9. Acknowledgments
We thank the following people for their contributions to this We thank the following people for their contributions to and/or
document: detailed reviews of this document:
Carsten Bormann
David Bryan David Bryan
Dave Crocker Dave Crocker
Yingjie Gu Yingjie Gu
David Harrington
Hongqiang (Harry) Liu Hongqiang (Harry) Liu
David McDysan David McDysan
Borje Ohlman Borje Ohlman
Konstantinos Pentikousis Konstantinos Pentikousis
Haibin Song Haibin Song
skipping to change at page 28, line 9 skipping to change at page 28, line 9
Richard Woundy Richard Woundy
Ning Zong Ning Zong
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC6646] Song, H., Zong, N., Yang, Y., and R. Alimi, "DECoupled
Application Data Enroute (DECADE) Problem Statement",
RFC 6646, July 2012.
[I-D.ietf-decade-reqs]
Yingjie, G., Bryan, D., Yang, Y., Zhang, P., and R. Alimi,
"DECADE Requirements", draft-ietf-decade-reqs-08 (work in
progress), August 2012.
10.2. Informative References 10.2. Informative References
[RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and
Registration Procedures", BCP 13, RFC 4288, December 2005. Registration Procedures", BCP 13, RFC 4288, December 2005.
[RFC5661] Shepler, S., Eisler, M., and D. Noveck, "Network File [RFC5661] Shepler, S., Eisler, M., and D. Noveck, "Network File
System (NFS) Version 4 Minor Version 1 Protocol", System (NFS) Version 4 Minor Version 1 Protocol",
RFC 5661, January 2010. RFC 5661, January 2010.
[RFC5849] Hammer-Lahav, E., "The OAuth 1.0 Protocol", RFC 5849, [RFC5849] Hammer-Lahav, E., "The OAuth 1.0 Protocol", RFC 5849,
April 2010. April 2010.
[RFC6392] Alimi, R., Rahman, A., and Y. Yang, "A Survey of In- [RFC6392] Alimi, R., Rahman, A., and Y. Yang, "A Survey of In-
Network Storage Systems", RFC 6392, October 2011. Network Storage Systems", RFC 6392, October 2011.
[RFC6646] Song, H., Zong, N., Yang, Y., and R. Alimi, "DECoupled
Application Data Enroute (DECADE) Problem Statement",
RFC 6646, July 2012.
[I-D.ietf-decade-reqs]
Yingjie, G., Bryan, D., Yang, Y., and R. Alimi, "DECADE
Requirements", draft-ietf-decade-reqs-06 (work in
progress), March 2012.
[OpenFlow] [OpenFlow]
"OpenFlow Organization", <http://www.openflow.org/>. "OpenFlow Organization", <http://www.openflow.org/>.
[GoogleFileSystem] [GoogleFileSystem]
Ghemawat, S., Gobioff, H., and S. Leung, "The Google File Ghemawat, S., Gobioff, H., and S. Leung, "The Google File
System", SOSP 2003, October 2003. System", SOSP 2003, October 2003.
Appendix A. In-Network Storage Components Mapped to DECADE Architecture Appendix A. In-Network Storage Components Mapped to DECADE Architecture
In this section we evaluate how the basic components of an in-network In this section we evaluate how the basic components of an in-network
 End of changes. 8 change blocks. 
15 lines changed or deleted 19 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/