-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/25/2011 03:22 PM, David A. Bryan wrote: > Thanks for the comments. I'm working on a new version. Many of these are great > suggestions and require no comment, but a few comments on a few are inline: >
[...] > > 9. Security Section > > Security section missing. > > > This is an interesting point. Since it has turned out that security is > discussed > in more detailed context in the specific drafts, do we want something like > this > in here, and if so, what do we want in this draft? My thought would be either > a) > we don't have a security section in here or b) we have a generic section on > P2P > security threats, but although I'm making the other changes, I'm not sure I'll > have time to write something like that. > > Thoughts on that? My comment was more about the fact that such section is mandatory, according to RFC 2223. Because this spec is for "Peer to Peer SIP", not "Peer to Peer", I do not think that a generic section on P2P security threats is needed. Perhaps it is OK to just say that the security sections of p2psip-base and p2psip-sip cover everything. - -- Marc Petit-Huguenin Personal email: [email protected] Professional email: [email protected] Blog: http://blog.marc.petit-huguenin.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk5W03kACgkQ9RoMZyVa61ezpQCfa+8o9EJYiAcKzhV5JtdO30lo fdoAn3apUi8oq09fvLJyiR+UEZddO6Oc =ZHdU -----END PGP SIGNATURE----- _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
