< draft-ietf-alto-problem-statement-03.txt   draft-ietf-alto-problem-statement-04.txt >
Network Working Group J. Seedorf Network Working Group J. Seedorf
Internet-Draft NEC Internet-Draft NEC
Intended status: Informational E. Burger Intended status: Informational E. Burger
Expires: March 19, 2010 Neustar Inc. Expires: March 22, 2010 Neustar Inc.
September 15, 2009 September 18, 2009
Application-Layer Traffic Optimization (ALTO) Problem Statement Application-Layer Traffic Optimization (ALTO) Problem Statement
draft-ietf-alto-problem-statement-03 draft-ietf-alto-problem-statement-04
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on March 19, 2010. This Internet-Draft will expire on March 22, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 41 skipping to change at page 2, line 41
5. Aspects of the Problem . . . . . . . . . . . . . . . . . . . . 9 5. Aspects of the Problem . . . . . . . . . . . . . . . . . . . . 9
5.1. Information provided by an ALTO service . . . . . . . . . 9 5.1. Information provided by an ALTO service . . . . . . . . . 9
5.2. ALTO Service Providers . . . . . . . . . . . . . . . . . . 10 5.2. ALTO Service Providers . . . . . . . . . . . . . . . . . . 10
5.3. ALTO Service Implementation . . . . . . . . . . . . . . . 10 5.3. ALTO Service Implementation . . . . . . . . . . . . . . . 10
5.4. User Privacy . . . . . . . . . . . . . . . . . . . . . . . 10 5.4. User Privacy . . . . . . . . . . . . . . . . . . . . . . . 10
5.5. Topology Hiding . . . . . . . . . . . . . . . . . . . . . 11 5.5. Topology Hiding . . . . . . . . . . . . . . . . . . . . . 11
5.6. Coexistence with Caching . . . . . . . . . . . . . . . . . 11 5.6. Coexistence with Caching . . . . . . . . . . . . . . . . . 11
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 12 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 12
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
10. Informative References . . . . . . . . . . . . . . . . . . . . 13 10. Informative References . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
1.1. Overview 1.1. Overview
Distributed applications, both peer-to-peer (P2P) and client/server Distributed applications, both peer-to-peer (P2P) and client/server
used for file sharing, real-time communication, and live and on- used for file sharing, real-time communication, and live and on-
demand media streaming, use a significant amount of network capacity demand media streaming, use a significant amount of network capacity
skipping to change at page 11, line 47 skipping to change at page 11, line 47
6. Security Considerations 6. Security Considerations
This document is neither a requirements document nor a protocol This document is neither a requirements document nor a protocol
specification. However, we believe it is important for the reader to specification. However, we believe it is important for the reader to
understand areas of security and privacy that will be important for understand areas of security and privacy that will be important for
the design and implementation of an ALTO solution. Moreover, issues the design and implementation of an ALTO solution. Moreover, issues
such as digital rights management are out of scope for ALTO, as they such as digital rights management are out of scope for ALTO, as they
are not technically enforceable at this level. are not technically enforceable at this level.
Some environments and use cases of ALTO may require client or server
authentication before providing sensitive information. In order to
support those environments interoperably, ALTO requirements
[I-D.ietf-alto-reqs] outlines minimum-to-implement authentication and
other security requirements.
Applications can decide to rely on information provided by an ALTO Applications can decide to rely on information provided by an ALTO
server to enhance the peer selection process. In principle, this server to enhance the peer selection process. In principle, this
enables the ALTO service that provides such information to influence enables the ALTO service that provides such information to influence
the behavior of the application, basically letting a third-party -- the behavior of the application, basically letting a third-party --
the ALTO service provider -- take an important role in a distributed the ALTO service provider -- take an important role in a distributed
system it was not previously involved in. system it was not previously involved in.
For example, in the case of an ALTO server deployed and run by an For example, in the case of an ALTO server deployed and run by an
ISP, the P2P community might consider it hostile because the operator ISP, the P2P community might consider it hostile because the operator
could: could:
 End of changes. 5 change blocks. 
5 lines changed or deleted 11 lines changed or added

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