Hi, My position of the draft is supportive.
Regards, Christer -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of DRAGE, Keith (Keith) Sent: 12. kesäkuuta 2008 16:50 To: [email protected] Subject: Re: [Sip] draft-dotson-sip-mutual-auth-03 (As SIP WG cochair) The document has now been updated based on comments received. http://www.ietf.org/internet-drafts/draft-dotson-sip-mutual-auth-03.txt I will give a few more days for responses to the question of support / no support. Please read the draft and indicate your postion. Regards Keith > -----Original Message----- > From: Stuart Hoggan [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 10, 2008 11:01 PM > To: DRAGE, Keith (Keith); [email protected] > Subject: RE: [Sip] draft-dotson-sip-mutual-auth-02 > > All, > > We have updated the document to incorporate feedback received so far. > It now contains a section that helps clarify the motivation. > Let us know if you have further comments. > > -Stuart > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of > > DRAGE, Keith (Keith) > > Sent: Wednesday, June 04, 2008 3:48 AM > > To: [email protected] > > Subject: Re: [Sip] draft-dotson-sip-mutual-auth-02 > > > > (As SIP WG cochair) > > > > This has been raised in the SIP group a couple of times, and we have > not > > yet gained an idea of whether to proceed with it in the SIP > WG or not. > > > > There have been a couple of technical comments raised in > the past from > > the security experts; my understanding is that these have now been > > clarified. > > > > I believe in the past there has been an interested > community that says > > this is useful. It has also been clarified that 3GPP would > like to use > > it in their specifications. > > > > So could I ask the WG to look at this document, and formally to > indicate > > whether they believe some work with this scope should be > progressed as > a > > SIP WG item. > > > > > http://www.ietf.org/internet-drafts/draft-dotson-sip-mutual-au > th-02.txt > > > > So if you support it please indicate to the SIP WG chairs. > > > > If you have technical concerns (i.e. it should not proceed > because it > is > > technically flawed beyond fixing) then please ideally mail > the list, > > although the SIP WG chairs will also accept input. > > > > Responses please in 1 calendar week from this date. > > > > Regards > > > > Keith > > > > > > ________________________________ > > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > > Stuart Hoggan > > Sent: Friday, May 02, 2008 5:15 PM > > To: [email protected] > > Subject: [Sip] draft-dotson-sip-mutual-auth-02 > > > > > > > > Folks, > > > > > > > > Based on the feedback received in Philadelphia, we have updated > > draft-dotson-sip-mutual-auth. The changes clarify the usage of the > > Proxy-Authentication-Info header, including support for multiple > values. > > > > > > > > > > Any further comments or suggestions will be > appreciated. It would > > also be nice to obtain WG feedback on pursuing this I-D as a WG > > document. > > > > > > > > Regards, > > > > Stuart > > > > > > > > _______________________________________________ > > 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 _______________________________________________ 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
