(An informational note from one of the WG co-chairs) This document is not about to go to the RFC editor's for publishing.
It is about to go to the IETF to see if they agree it, i.e. the SIP WG have submitted a publication request. That means it still gets reviewed by: Our AD The security directorate The GEN ART review team Any other review teams that think they have a hand in this IANA The IETF as a whole (and that definitely does include you unless you explicitly exclude yourself) The IESG as a whole Once that has happened, the world just may let the RFC editors get their hands on it. I am sure somewhere in that process you can get to make any comments you think relevant - as I believe I have said before. And I would note that at the moment I have see any proposal that adds more than about 4 lines of text to outbound, and no other issues that are so far looking like they achieve consensus that there is an issue. On that basis there are many many more documents that score lower in their readiness for publication request - and I note that none of this current discussion got raised by you until we had completed at least two WGLC and at least two requests to see if we were ready for the publication request. So yes carry on making comments, but lets look to start building some consensus from the responses. Regards Keith > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Juha Heinanen > Sent: Friday, October 17, 2008 6:00 PM > To: Dean Willis > Cc: SIP IETF > Subject: [Sip] Outbound and mid-dialog requests with GRUU > > Dean Willis writes: > > > Any clues? > > it is very revealing that at the stage when these i-d are > about to go to rfc editors for publishing, there is lots of > all kind of issues that even the experts are not sure about. > > even if these issues finally get sorted out on the list, > there is absolutely no chance whatsoever that an average > implementer who has not participated in these discussions > could even get his/her implementation correct. these > specifications are far too complicated for that. > > it should be a high time to take a timeout and go back to the basics. > > -- juha > _______________________________________________ > 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
