draft-ietf-p2psip-base-14.txt   draft-ietf-p2psip-base-15.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
Intended status: Standards Track B. Lowekamp, Ed. Intended status: Standards Track B. Lowekamp, Ed.
Expires: November 28, 2011 Skype Expires: November 28, 2011 Skype
E. Rescorla E. Rescorla
RTFM, Inc. RTFM, Inc.
S. Baset S. Baset
H. Schulzrinne H. Schulzrinne
Columbia University Columbia University
May 27, 2011 May 27, 2011
REsource LOcation And Discovery (RELOAD) Base Protocol REsource LOcation And Discovery (RELOAD) Base Protocol
draft-ietf-p2psip-base-14 draft-ietf-p2psip-base-15
Abstract Abstract
This specification defines REsource LOcation And Discovery (RELOAD), This specification defines REsource LOcation And Discovery (RELOAD),
a peer-to-peer (P2P) signaling protocol for use on the Internet. A a peer-to-peer (P2P) signaling protocol for use on the Internet. A
P2P signaling protocol provides its clients with an abstract storage P2P signaling protocol provides its clients with an abstract storage
and messaging service between a set of cooperating peers that form and messaging service between a set of cooperating peers that form
the overlay network. RELOAD is designed to support a P2P Session the overlay network. RELOAD is designed to support a P2P Session
Initiation Protocol (P2PSIP) network, but can be utilized by other Initiation Protocol (P2PSIP) network, but can be utilized by other
applications with similar requirements by defining new usages that applications with similar requirements by defining new usages that
skipping to change at page 6, line 51 skipping to change at page 6, line 51
13.11. Overlay Link Protocols . . . . . . . . . . . . . . . . . 145 13.11. Overlay Link Protocols . . . . . . . . . . . . . . . . . 145
13.12. Forwarding Options . . . . . . . . . . . . . . . . . . . 146 13.12. Forwarding Options . . . . . . . . . . . . . . . . . . . 146
13.13. Probe Information Types . . . . . . . . . . . . . . . . 146 13.13. Probe Information Types . . . . . . . . . . . . . . . . 146
13.14. Message Extensions . . . . . . . . . . . . . . . . . . . 146 13.14. Message Extensions . . . . . . . . . . . . . . . . . . . 146
13.15. reload URI Scheme . . . . . . . . . . . . . . . . . . . 147 13.15. reload URI Scheme . . . . . . . . . . . . . . . . . . . 147
13.15.1. URI Registration . . . . . . . . . . . . . . . . . . 147 13.15.1. URI Registration . . . . . . . . . . . . . . . . . . 147
13.16. Media Type Registration . . . . . . . . . . . . . . . . 148 13.16. Media Type Registration . . . . . . . . . . . . . . . . 148
14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 149 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 149
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 150 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 150
15.1. Normative References . . . . . . . . . . . . . . . . . . 150 15.1. Normative References . . . . . . . . . . . . . . . . . . 150
15.2. Informative References . . . . . . . . . . . . . . . . . 152 15.2. Informative References . . . . . . . . . . . . . . . . . 151
Appendix A. Routing Alternatives . . . . . . . . . . . . . . . . 155 Appendix A. Routing Alternatives . . . . . . . . . . . . . . . . 155
A.1. Iterative vs Recursive . . . . . . . . . . . . . . . . . 155 A.1. Iterative vs Recursive . . . . . . . . . . . . . . . . . 155
A.2. Symmetric vs Forward response . . . . . . . . . . . . . 155 A.2. Symmetric vs Forward response . . . . . . . . . . . . . 155
A.3. Direct Response . . . . . . . . . . . . . . . . . . . . 156 A.3. Direct Response . . . . . . . . . . . . . . . . . . . . 156
A.4. Relay Peers . . . . . . . . . . . . . . . . . . . . . . 157 A.4. Relay Peers . . . . . . . . . . . . . . . . . . . . . . 157
A.5. Symmetric Route Stability . . . . . . . . . . . . . . . 157 A.5. Symmetric Route Stability . . . . . . . . . . . . . . . 157
Appendix B. Why Clients? . . . . . . . . . . . . . . . . . . . . 158 Appendix B. Why Clients? . . . . . . . . . . . . . . . . . . . . 158
B.1. Why Not Only Peers? . . . . . . . . . . . . . . . . . . 158 B.1. Why Not Only Peers? . . . . . . . . . . . . . . . . . . 158
B.2. Clients as Application-Level Agents . . . . . . . . . . 159 B.2. Clients as Application-Level Agents . . . . . . . . . . 159
Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 159 Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 159
skipping to change at page 149, line 7 skipping to change at page 149, line 7
One way of doing this is specified in RFC-AAAA. In the case when the One way of doing this is specified in RFC-AAAA. In the case when the
media includes a "shared-secret" element, then the contents of the media includes a "shared-secret" element, then the contents of the
file need to be kept confidential or else anyone that can see the file need to be kept confidential or else anyone that can see the
shared-secret and effect the RELOAD overlay network. shared-secret and effect the RELOAD overlay network.
Interoperability considerations: Same as application/xml as defined Interoperability considerations: Same as application/xml as defined
in [RFC3023]. in [RFC3023].
Published specification: RFC-AAAA Published specification: RFC-AAAA
Applications that use this media type: The type is used by systems Applications that use this media type: The type is used to configure
that report electrical power usage and environmental information such the peer to peer overlay networks defined in RFC-AAAA.
as temperature and humidity. It can be used for a wide range of
sensor reporting systems.
Additional information: The syntax for this media type is specified Additional information: The syntax for this media type is specified
in Section 10.1 of RFC-AAAA. in Section 10.1 of RFC-AAAA.
Magic number(s): none Magic number(s): none
File extension(s): relo File extension(s): relo
Macintosh file type code(s): none Macintosh file type code(s): none
 End of changes. 3 change blocks. 
6 lines changed or deleted 4 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/