Here is the change log for p2psip-base-03:
* Rearranged forwarding header to fix alignment among other issues
* Removed route logging
* Switched to binary ICE for Attach
* ConfigUpdate improved
* Change from close DTLS session on fragmentation attack to drop
fragments, indirect attack
* Updates to trivial sender/receiver text
* Updates to data model based on list discussion
* Updates to chord overlay algorithm section
* Added AppAttach and removed port number from Attach
* Changed via-list to use shorter structure
* Rewrote fragmentation
* Moved AIMD and TFRC congestion control algorithms to appendix
until further wg effort decides direction there.
For a more thorough view of changes, take a look at the diff
http://tools.ietf.org/rfcdiff?url2=draft-ietf-p2psip-base-03.txt
Bruce
On Mon, Jul 13, 2009 at 8:00 PM, <[email protected]> wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Peer-to-Peer Session Initiation Protocol
> Working Group of the IETF.
>
>
> Title : REsource LOcation And Discovery (RELOAD) Base
> Protocol
> Author(s) : C. Jennings, et al.
> Filename : draft-ietf-p2psip-base-03.txt
> Pages : 146
> Date : 2009-07-13
>
> In this document the term BCP 78 and BCP 79 refer to RFC 3978 and RFC
> 3979 respectively. They refer only to those RFCs and not any
> documents that update or supersede them.
>
> This document 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
> specify the kinds of data that must be stored for a particular
> application. RELOAD defines a security model based on a certificate
> enrollment service that provides unique identities. NAT traversal is
> a fundamental service of the protocol. RELOAD also allows access
> from "client" nodes that do not need to route traffic or store data
> for others.
>
> Legal
>
> This documents and the information contained therein are provided on
> an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
> REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
> IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
> WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
> WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE
> ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
> FOR A PARTICULAR PURPOSE.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-p2psip-base-03.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
> _______________________________________________
> P2PSIP mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/p2psip
>
>
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
