My efforts, independently of the WGLC, to find reviewers of this document have met with insufficient support.
Are there a couple of people out there in the SIP community, who are familiar with the requirements of RFC 3265, who are prepared to look at this draft with a new pair of eyes (figuratively speaking), and essentially pull the document apart from one end to the other. Please send me a mail directly if you consider you can do this within a reasonable short timescale (2 or 3 weeks). Regards Keith > -----Original Message----- > From: DRAGE, Keith (Keith) > Sent: Wednesday, September 19, 2007 2:48 PM > To: [email protected] > Subject: RE: [Sip] WGLC for draft-ietf-sip-subnot-etags-01 > > (As WG chair) > > This was a response to say that there had been no comments at > all on this WGLC - however Dale Worley successfully precluded > me saying that (thanks Dale). > > Just to make sure, I would like to extend the WGLC by a week > to Wednesday September 26th just in case it is still sitting > in your pile of documents to read. Instructions for response as below. > > Now I know that we had some comments from people that > indicated that they were pretty happy with previous versions. > Just in case the document is now so perfect that there are no > WGLC comments to make, please send the SIP WG chairs if you > have read the document and believe this to be the case! > > Otherwise get out there and read it. > > Regards > > Keith > > > -----Original Message----- > > From: DRAGE, Keith (Keith) [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, September 04, 2007 10:28 AM > > To: [email protected] > > Subject: [Sip] WGLC for draft-ietf-sip-subnot-etags-01 > > > > (As WG chair) > > > > This is to announce a Working Group Last Call for > > > > > http://www.ietf.org/internet-drafts/draft-ietf-sip-subnot-etags-01.txt > > > > This is a two week last call. Please provide comments and review of > > this document by Tuesday 18th September 2007. > > > > Ideally please try to identify for each comment > > > > - the precise point in the text where the comment applies (copying > > the text and quoting the section number may help here), > > > > - the nature of the comment (NIT, minor technical, major > > technical), > > > > - if possible a proposed solution to the comment. > > > > Please send comments to the SIP WG list, and also to the > editor listed > > in the document. > > > > Regards > > > > Keith > > > > > > > > _______________________________________________ > > Sip mailing list https://www1.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://www1.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
