9:00-9:10 Agenda bash
 presenter: chairs

9:10-9:20 what charter is, what we are doing here, how we are going to
move forward
 presenter: chairs

9:20-9:40 Overview Document work: What are the major open questions in
this draft?
 presenters: Philip Matthews and Dean Willis
 relevant drafts: draft-willis-p2psip-concepts-04
 :10 minutes for presentation, remainder discussion

9:40-10:00 Open Question: Selecting a DHT
 Charter states we will support multiple DHTs. We need to select one
(or a very, very few) "base", must implement DHTs. Leading candidates
today *appear* to be Chord and Bamboo, and possibly Kademlia.
 Discussion of Protocol Implementations of pluggable DHTs and the
tradeoffs between Chord, Bamboo, and Kademlia
 presenters: Henning Schulzrinne and David Bryan
 relevant drafts: draft-baset-sipping-p2pcommon-01,
draft-zangrilli-p2psip-dsip-dhtchord-00,
draft-zangrilli-p2psip-dsip-dhtbamboo-00
 :05 minutes for presentation, remainder discussion

10:00-10:30 Open Question: How do NATs affect the requirements of a protocol?
 Discussion of lessons learned from proposals for NAT traversal and
how they translate into requirements for the protocol
 presenters: Bruce Lowekamp and Philip Matthews
 relevant drafts: draft-matthews-p2psip-nats-and-overlays-01,
draft-matthews-p2psip-dsip-nat-traversal-00
 :10 minutes for presentation, remainder discussion

10:30-11:00 Open Question: What are the requirements for the peer protocol?
 We know we need this protocol. What are the things that a protocol
proposal must do to be considered? What have we learned from the
proposals made to date? We want rough consensus on what this needs to
do, so we can have firm (real) proposals to consider at Chicago. What
sort of routing? Other properties?
 presenters: Henning Schulzrinne, Bruce Lowekamp, Jiang XingFeng
 relevant drafts: draft-bryan-p2psip-dsip-00,
draft-willis-p2psip-concepts-04,
draft-jiang-p2psip-peer-protocol-requirement-00
 :10 minutes for presentation, remainder discussion

11:00-11:30 Open Question: What would a client protocol need to do and
do we need it?
 Discussion of client protocol: Do we need a new client protocol
that is separate from the peer protocol and isn't SIP? If so, what
would it need to do?
 presenters: Henning Schulzrinne, Dean Willis, Spencer Dawkins
 relevant drafts: draft-willis-p2psip-concepts-04
 :10 minutes for presentation, remainder discussion