If you mandate using TLS you are stuck with it. You can mandate implementing it which will allow alternative mechanisms, today and in the future. The fear is that implementers will not do it but the same concerns should have been about implementing Chord in Reload Roni
> -----Original Message----- > From: Francois Audet [mailto:[email protected]] > Sent: Saturday, December 12, 2009 6:15 AM > To: P2PSIP WG > Cc: Roni Even; jc > Subject: Re: [P2PSIP] Concerns, questions and nits about base -06 as > part of the WGLC > > Perhaps what should be done is mandate TLS for now, and leave it open > for alternative mechanisms to be later standardized. > > > On Dec 11, 2009, at 18:16 , jc wrote: > > > The overlay should obtain the transport layer security mechanism > > from the configuration file. > > > > I was a senior engineer at gizmo5 recently aquired by google. One > > thing that occured prior to my arrival was that we had bricked > > ourselfs off via TLS and this could only decrypt/encrypt gizmo to > > gizmo. Skype has a hard coded security mechanism of the base overlay > > protocol. > > > > Let's not do the same. > > > > Julian_______________________________________________ > > P2PSIP mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/p2psip _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
