[P2PSIP] Design decisions

["Henry Sinnreich" <[e-mail]>]

The good news is we have now four excellent contributions to the design
of the peer protocol for P2P SIP. They are in no particular order (add
http://www.ietf.org/internet-drafts/ in front of the file name):

"The Peer Protocol for P2PSIP Networks"
<draft-hautakorpi-p2psip-peer-protocol-00.txt>

"Peer-to-Peer Protocol (P2PP)"
<draft-baset-p2psip-p2pcommon-01>

"dSIP: A P2P Approach to SIP Registration and Resource Location"
<draft-bryan-p2psip-dsip-00>

"Data format and interface to an external peer-to-peer network for SIP
location service" 
<draft-singh-p2p-sip-01> 

It is apparent that while these drafts contain valuable design items,
the opinions also differ widely on such points as:

- Using any of the 'native' p2p protocols,
- Is SIP a good peer protocol?
- The meaning of REGISTER and its replacement with LOCSER,
- Mechanisms for choosing any DHT peer protocol, examples,
- Other applications: Search, app layer multicast for conferences, etc.,
- The data mode, the service mode, control of DHT routing for other
apps,
- Flexibility of the design,
- For implementers: Is open source code available? What is the
footprint?

Besides reconciling the peer protocol design decisions, there are also
serious performance considerations, such as (there are more):

- What is the _measured_ success ration for NAT traversal using ICE?
- What is the distribution of call setup time on the Internet?
- What is the failure rate for peers that cannot see each other?
  (non-transitivity)
- Sensitivity to various churn rates such as wired vs. mobile
- Security and trust models,...

Since we don't have the luxury of an R&D budget, the most sensible
approach is to use results from years of work on p2p. Hint: openDHT.org 
Show me the numbers for performance! 
Or just trusting the assertions of authors of I-Ds? Think of the cost.
Just in case someone is tempted to try anyhow, please see:

http://www.ietf.org/internet-drafts/draft-irtf-p2prg-survey-search-01.tx
t 

Proposal: 

1. Use the above four contributions and the other P2P SIP I-Ds as well
to edit a design document with options, recommendations, examples, etc.
for the peer protocol for P2P SIP. This is the first key WG deliverable.

2. Last but not least: Open source code is the most dependable approach
for a successful standard. The P2P SIP peer protocol MUST be backed up
by open source code, free of patent claims.

3. Define the P2P SIP peer protocol based on both items 1. and 2.
No less.

What do you think?

Thanks, 
Henry Sinnreich





_______________________________________________
P2PSIP mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/p2psip