And just to clarify, the SIP list is addressed at the remaining work that existed in the SIP WG at the time it closed. Indeed many SIP experts have left this list, or are newcomers and were never on it.
As this is potential new work, it should follow the rules for introducing new work into the RAI area. This would ultimately end up in the SIPCORE WG. Whether the SIPCORE chairs would feel it needed to be DISPATCHed first I will leave you to consult on. Of course what you do with it prior to the request to charter the work is entirely up to you as authors and collaborators, but at some point you need to bring other experts up to speed with what you would like IETF to do. Regards Keith > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > DRAGE, Keith (Keith) > Sent: 16 September 2011 15:23 > To: Iñaki Baz Castillo; Gurbani, Vijay K (Vijay) > Cc: [email protected]; Horvath, Ernst > Subject: Re: [Sip] Using TLS in the first hop - Bug in RFC 5630 > > I would suggest moving the discussion to either SIPCORE or DISPATCH. > > Keith > > > -----Original Message----- > > From: Iñaki Baz Castillo [mailto:[email protected]] > > Sent: 16 September 2011 15:22 > > To: Gurbani, Vijay K (Vijay) > > Cc: DRAGE, Keith (Keith); Horvath, Ernst; [email protected] > > Subject: Re: [Sip] Using TLS in the first hop - Bug in RFC 5630 > > > > 2011/9/16 Vijay K. Gurbani <[email protected]>: > > > The draft Keith is referring to here, if you are interested, is: > > > "The SIPSEC Uniform Resource Identifier (URI)" [1]. > > > > > > There was a follow-up paper [2] that used the idea in the sipsec URI > > > draft to benchmark TLS per-hop and TLS end-to-end, treating the > > > intermediary proxies as a blind byte forwarder. If you are interested > > > in the paper, drop me a private message and I can send you the PDF. > > > > Hi Vijay, the PDF is already accesible in the link below :) > > > > > [1] http://tools.ietf.org/html/draft-gurbani-sip-sipsec-01 > > > > > > I would like to comment about this draft, is it the appropriate maillist > > for it? > > > > > > -- > > Iñaki Baz Castillo > > <[email protected]> > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is essentially closed and only used for finishing old business. > Use [email protected] for questions on how to develop a SIP > implementation. > Use [email protected] for new developments on the application of sip. > Use [email protected] for issues related to maintenance of the core SIP > specifications. _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is essentially closed and only used for finishing old business. Use [email protected] for questions on how to develop a SIP implementation. Use [email protected] for new developments on the application of sip. Use [email protected] for issues related to maintenance of the core SIP specifications.
