draft-ietf-decade-reqs-07.txt   draft-ietf-decade-reqs-08.txt 
DECADE Y. Gu DECADE Y. Gu
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Informational D. Bryan Intended status: Informational D. Bryan
Expires: February 7, 2013 Polycom, Inc. Expires: February 14, 2013 Ethernot.org
Y. Yang Y. Yang
Yale University Yale University
P. Zhang P. Zhang
Tsinghua University/Yale Tsinghua University/Yale
University University
R. Alimi R. Alimi
Google Google
August 6, 2012 August 13, 2012
DECADE Requirements DECADE Requirements
draft-ietf-decade-reqs-07 draft-ietf-decade-reqs-08
Abstract Abstract
The target of the DECoupled Application Data Enroute (DECADE) system The target of the DECoupled Application Data Enroute (DECADE) system
is to provide an open and standard in-network storage system for is to provide an open and standard in-network storage system for
applications, primarily P2P (peer-to-peer) applications, to store, applications, primarily P2P (peer-to-peer) applications, to store,
retrieve and manage their data. This draft enumerates and explains retrieve and manage their data. This draft enumerates and explains
requirements, not only for storage and retrieval, but also for data requirements, not only for storage and retrieval, but also for data
management, access control and resource control, that should be management, access control and resource control, that should be
considered during the design and implementation of a DECADE- considered during the design and implementation of a DECADE-
skipping to change at page 2, line 11 skipping to change at page 2, line 11
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 February 7, 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 5, line 30 skipping to change at page 5, line 30
This draft enumerates and explains the rationale behind specific This draft enumerates and explains the rationale behind specific
requirements on the protocol design and on any data store requirements on the protocol design and on any data store
implementation that may be used to implement DECADE servers that implementation that may be used to implement DECADE servers that
should be considered during the design and implementation of a should be considered during the design and implementation of a
DECADE-compatible system. As such, it does not include general DECADE-compatible system. As such, it does not include general
guiding principles. General design considerations, explanation of guiding principles. General design considerations, explanation of
the problem being addressed, and enumeration of the types of the problem being addressed, and enumeration of the types of
applications to which a DECADE-compatible system may be suited is not applications to which a DECADE-compatible system may be suited is not
considered in this document. For general information, please see considered in this document. For general information, please see
[I-D.ietf-decade-problem-statement] and [I-D.ietf-decade-arch]. [RFC6646] and [I-D.ietf-decade-arch].
This document enumerates the requirements to enable target This document enumerates the requirements to enable target
applications to utilize in-network storage. In this context, using applications to utilize in-network storage. In this context, using
storage resources includes not only basic capabilities such as storage resources includes not only basic capabilities such as
writing, reading, and managing data, but also controlling access for writing, reading, and managing data, but also controlling access for
particular remote clients with which it is sharing data. particular remote clients with which it is sharing data.
Additionally, we also consider controlling the resources used by Additionally, we also consider controlling the resources used by
remote clients when they access data as an integral part of utilizing remote clients when they access data as an integral part of utilizing
the network storage. the network storage.
skipping to change at page 6, line 8 skipping to change at page 6, line 8
administrative domain). These in-network storage systems can administrative domain). These in-network storage systems can
communicate and transfer data through internal or non-standard communicate and transfer data through internal or non-standard
communication messages that are outside of the scope of these communication messages that are outside of the scope of these
requirements, but they should use DECADE-compatible protocol(s) when requirements, but they should use DECADE-compatible protocol(s) when
communicating with other DECADE-compatible in-network storage communicating with other DECADE-compatible in-network storage
systems. systems.
2. Terminology 2. Terminology
This document uses the term 'In-network storage' which is defined in This document uses the term 'In-network storage' which is defined in
[I-D.ietf-decade-problem-statement]. [RFC6646].
This document also defines these additional terms: This document also defines these additional terms:
2.1. DECADE-compatible Client 2.1. DECADE-compatible Client
A DECADE-compatible client uploads and/or retrieves data from DECADE- A DECADE-compatible client uploads and/or retrieves data from DECADE-
compatible servers. We use the shorter term "client" if there is no compatible servers. We use the shorter term "client" if there is no
ambiguity. ambiguity.
2.2. DECADE-compatible Server 2.2. DECADE-compatible Server
skipping to change at page 18, line 43 skipping to change at page 18, line 43
EXCEPTION: A DECADE-compatible server may not provide such a EXCEPTION: A DECADE-compatible server may not provide such a
response if doing so increases the load or due to security response if doing so increases the load or due to security
concerns. concerns.
9.4. Overload Condition 9.4. Overload Condition
REQUIREMENT(S): A DECADE-compatible server, which is operating close REQUIREMENT(S): A DECADE-compatible server, which is operating close
to its capacity limit (e.g., too busy servicing other requests), to its capacity limit (e.g., too busy servicing other requests),
MUST be permitted to reject requests and not be required to MUST be permitted to reject requests and not be required to
generate response to additional requests. A DECADE-compatible generate response to additional requests. A DECADE-compatible
server MUST also be permitted to redirect requests (see Section server MUST also be permitted to redirect requests as a load-
4.1.3.5) as a load-shedding technique. shedding technique.
RATIONALE: The Insufficient Resources response allows a client to RATIONALE: The Insufficient Resources response allows a client to
back off, free up necessary resources or waiting for such back off, free up necessary resources or waiting for such
resources to be freed. resources to be freed.
EXCEPTION: A DECADE-compatible server may not provide such a EXCEPTION: A DECADE-compatible server may not provide such a
response if doing so increases the load or due to security response if doing so increases the load or due to security
concerns. concerns.
9.5. Attack Mitigation 9.5. Attack Mitigation
skipping to change at page 20, line 36 skipping to change at page 20, line 36
There are no IANA considerations with this document. There are no IANA considerations with this document.
13. References 13. References
13.1. Normative References 13.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.
[I-D.ietf-decade-problem-statement] [RFC6646] Song, H., Zong, N., Yang, Y., and R. Alimi, "DECoupled
Song, H., Zong, N., Yang, Y., and R. Alimi, "DECoupled
Application Data Enroute (DECADE) Problem Statement", Application Data Enroute (DECADE) Problem Statement",
draft-ietf-decade-problem-statement-03 (work in progress), RFC 6646, July 2012.
March 2011.
13.2. Informative References 13.2. Informative References
[I-D.ietf-decade-arch] [I-D.ietf-decade-arch]
Alimi, R., Yang, Y., Rahman, A., Kutscher, D., and H. Liu, Alimi, R., Rahman, A., Kutscher, D., and Y. Yang, "DECADE
"DECADE Architecture", draft-ietf-decade-arch-02 (work in Architecture", draft-ietf-decade-arch-08 (work in
progress), July 2011. progress), July 2012.
[LLSB08] Levin, D., LaCurts, K., Spring, N., and B. Bhattacharjee, [LLSB08] Levin, D., LaCurts, K., Spring, N., and B. Bhattacharjee,
"BitTorrent is an Auction: Analyzing and Improving "BitTorrent is an Auction: Analyzing and Improving
BitTorrent's Incentives", SIGCOMM 2008, August 2008. BitTorrent's Incentives", SIGCOMM 2008, August 2008.
[PPLive] "PPLive", <http://www.pplive.com>.
Appendix A. Acknowledgments Appendix A. Acknowledgments
We would also like to thank Haibin Song for substantial contributions We would also like to thank Haibin Song for substantial contributions
to earlier versions of this document. We would also like to thank to earlier versions of this document. We would also like to thank
Reinaldo Penno, Alexey Melnikov, Rich Woundy, Ning Zong, Roni Even, Reinaldo Penno, Alexey Melnikov, Rich Woundy, Ning Zong, Roni Even,
David McDysan, Borje Ohlman, Dirk Kutscher, Akbar Rahman, Xiao Zhu, David McDysan, Borje Ohlman, Dirk Kutscher, Akbar Rahman, Xiao Zhu,
Yunfei Zhang, Peng Zhang and Jin Peng for contributions and general Yunfei Zhang, Peng Zhang and Jin Peng for contributions and general
feedback. feedback.
Authors' Addresses Authors' Addresses
skipping to change at page 21, line 29 skipping to change at page 21, line 26
Yingjie Gu Yingjie Gu
Huawei Huawei
No. 101 Software Avenue No. 101 Software Avenue
Nanjing, Jiangsu Province 210012 Nanjing, Jiangsu Province 210012
P.R.China P.R.China
Phone: +86-25-56624760 Phone: +86-25-56624760
Email: guyingjie@huawei.com Email: guyingjie@huawei.com
David A. Bryan David A. Bryan
Polycom, Inc. Ethernot.org
Email: dbryan@ethernot.org Email: dbryan@ethernot.org
Yang Richard Yang Yang Richard Yang
Yale University Yale University
Email: yry@cs.yale.edu Email: yry@cs.yale.edu
Peng Zhang Peng Zhang
Tsinghua University/Yale University Tsinghua University/Yale University
 End of changes. 12 change blocks. 
18 lines changed or deleted 14 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/