Re: draft-ietf-sip-connect-reuse
"DRAGE, Keith \(Keith\)" <[email protected]>
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <[email protected]> |
(As WG chair) Well I went looking for any consensus you are referring to. In the limited time I have available I failed to find it. Can you be more explicit about when you think a decision was made in this respect, and whether it was on list or in a meeting. Please note by the way that I believe the document has been in pretty much its current form for at least 18 months. regards Keith > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Cullen Jennings > Sent: Saturday, November 08, 2008 4:24 PM > To: SIP List > Subject: [Sip] draft-ietf-sip-connect-reuse > > > I do not believe this draft represents the consensus that we > have agree in the SIP WG . > > This does not work for TCP. Reverse DNS lookup is not strong > enough to replace TLS. I'm not even interested in discussing > the reason why yet again but I would like to see the draft > updated to reflect the WG consensus. To do this it need to > say MUST use TLS. Having it allow straight SCTP and TCP when > the reverse DNS or some other unspecified thing happens is > not what we agreed to. This can be fixed by changing a few > words and deleting a sentence or two in security consideration. > I'm glad to send edits if you want. > > This draft is important for the SIP Connect work - lets make > these changes to what we agreed to and get this finished quickly. > > Cullen as individual contributor > > > > > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol Use > [email protected] for questions on current sip > Use [email protected] for new developments on the application of sip > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [email protected] for questions on current sip Use [email protected] for new developments on the application of sip