Concepts and Terminology for Peer-to-Peer SIP (P2PSIP)
draft-ietf-p2psip-concepts-09

[Ballot comment]
Thanks for doing this. I wish more of our protocols had high-level concept descriptions like this.

- 1, first paragraph:
I was slightly surprised not to see the word "rendezvous" turn up here. It's not critical, but it's a term that has meaning to a lot of "conventional SIP " people.

- 2.2, last paragraph:
While I assume the client in the first sentence is the conventional SIP client mentioned further down the paragraph, the initial paragraph structure led me to expect you to call the special peer offering the SIP registrar service a "client".

- 2.5, first paragraph:
consider expanding "zeroconf" to "zero configuration"

-6: I’m not going to push the matter this late in the process, but there might have been an opportunity to describe the security concepts of p2psip at a similar level of detail.

(Via drafts-lastcall-comment@iana.org): IESG/Authors/WG Chairs:

IANA has reviewed draft-ietf-p2psip-concepts-08.txt, which is currently in Last Call, and has the following comments:

We understand that this document doesn't require any IANA actions.

While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, IANA does not object.

If this assessment is not accurate, please respond as soon as possible.

Thank you,

Sabrina Tanamal
IANA Specialist
ICANN

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: draft-ietf-p2psip-concepts@ietf.org, br@brianrosen.net, alcoop@cisco.com, p2psip@ietf.org, p2psip-chairs@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Concepts and Terminology for Peer to Peer SIP) to Informational RFC


The IESG has received a request from the Peer-to-Peer Session Initiation
Protocol WG (p2psip) to consider the following document:
- 'Concepts and Terminology for Peer to Peer SIP'
  as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-03-04. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  This document defines concepts and terminology for the use of the
  Session Initiation Protocol in a peer-to-peer environment where the
  traditional proxy-registrar and message routing functions are
  replaced by a distributed mechanism.  These mechanisms may be
  implemented using a distributed hash table or other distributed data
  mechanism with similar external properties.  This document includes a
  high-level view of the functional relationships between the network
  elements defined herein, a conceptual model of operations, and an
  outline of the related problems addressed by the P2PSIP working group
  and the RELOAD protocol and SIP usage document defined by the working
  group.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-p2psip-concepts/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-p2psip-concepts/ballot/


No IPR declarations have been submitted directly on this I-D.

Shepherd Writeup for draft-ietf-p2psip-concepts, current version 7.  Date of this writeup: November 31, 2015.  Document Shepherd: Brian Rosen

(1) This document is Informational.  The document header indicates Informational.  This document only contains explanatory information concerning the p2psip protocol and other documents and is properly classified as “Informational”.
(2) Document Announcement Write-Up:
Technical Summary:
This document defines concepts and terminology for the use of the Session Initiation Protocol in a peer-to-peer environment where the traditional proxy-registrar and message routing functions are replaced by a distributed mechanism.  These mechanisms may be implemented using a distributed hash table or other distributed data mechanism with similar external properties.  This document includes a high-level view of the functional relationships between the network elements defined herein, a conceptual model of operations, and an outline of the related problems addressed by the P2PSIP working group and the RELOAD protocol [RFC6940] and SIP usage.

Working Group Summary:
This document has had a relatively long gestation period in the working group, and it fact languished for several years.  After development of the protocol and other documents, it was felt that completing the concepts document would be helpful for readers of the protocol and other documents to understand the basic concepts behind the protocol.  As  result, this document was updated to reflect the evolution of the various documents and it now reflects the documented state of the protocol.  There were no notable disagreements within the working group over the development of the document. 
Document Quality:
The document was written by one of the original contributors to the entire p2psip effort, and has benefitted from review of the more active workgroup’s participants.  I believe it accurately reflects the concepts behind the RELOAD protocol.
Personnel:
Brian Rosen is the Document Shepherd.  Alissa Cooper is the Responsible Area Director.
(3) I have completed a thorough review of the document and believe it is ready to be published.
(4) Knowledgeable people have reviewed the document and no significant concerns were raised.  All minor issues have been resolved.
(5) This document only explains the concepts behind the protocol and thus has no concerns requiring specialized review.
(6) Neither the work group nor I have any concerns or issues.
(7) Each author has confirmed that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed.
(8) There are no IPR disclosures filed on the draft.
(9) As with many IETF working groups, interest in finishing has flagged, and we did struggle to get sufficient reviews.  However, we had strong concurrence within the larger working group that the document should be published.  There were no dissents.
(10) There are no threatened appeals and no dissenters, strong or otherwise. 
(11) There are some minor nits that should be handled in normal RFC editor processing: the abstract has references which need to be turned into text descriptions.
(12) This document does not define any MIBs, media types or URNs, and thus no reviews for those items is needed.
(13) The references all informative.
(14) There is a reference to other p2psip documents, all of which are in the final stages of review and publication.
(15) See (14) above.
(16) This document does not change the status of any RFCs. 
(17) This document orequires no IANA actions.
(18) The document does not create any new registries.
(19) This document does not contain any XML, BNF, MIB or other formal language constructs.  The document does contain XML schemas.