An Extension to the REsource LOcation And Discovery (RELOAD) Protocol to Support Relay Peer Routing
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: RFC Editor <email@example.com>, p2psip mailing list <firstname.lastname@example.org>, p2psip chair <email@example.com> Subject: Protocol Action: 'An Extension to REsource LOcation And Discovery (RELOAD) Protocol to Support Relay Peer Routing' to Proposed Standard (draft-ietf-p2psip-rpr-11.txt) The IESG has approved the following document: - 'An Extension to REsource LOcation And Discovery (RELOAD) Protocol to Support Relay Peer Routing' (draft-ietf-p2psip-rpr-11.txt) as Proposed Standard This document is the product of the Peer-to-Peer Session Initiation Protocol Working Group. The IESG contact persons are Gonzalo Camarillo and Richard Barnes. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-p2psip-rpr/
Technical Summary: RELOAD recommends symmetric recursive routing for routing messages. An optional extesion that can be used to provide shorter routes for responses (reducing the overhead on intermediate nodes) consists in supporting a relay peer routing mode. This defines the required extension as well as describes potential use cases where it can be used. Working Group Summary: The normal WG process was followed and the document has been discussed for several years. The document as it is now, reflects WG consensus, with nothing special worth noting. Document Quality: The document was thoroughly reviewed by Marc Petit-Huguenin and Carlos J. Bernardos. Personnel: Who is the Document Shepherd? Carlos J. Bernardos Who is the Responsible Area Director? Gonzalo Camarillo RFC Editor Note: In Section 4.2: "using RPR SHOULD be discouraged in the open Internet or if the" should be "RPR SHOULD NOT be used in the open Internet"