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