Cullen Jennings wrote: > On Mar 21, 2008, at 9:25 AM, Dean Willis wrote: > >> Ok, is this what you mean? >> >> Discussion of Extended Key Usage in certificates used with SIP is >> outside the scope of this document. See I-D.sip-eku[9] for further >> discussion of this topic. > > Yes, that seems to pretty much capture what I was trying to say. > Thanks you for getting that nice and crisp.
Cullen: So what I think I am gathering from the seminal conversation between you and Dean are the following points: 1) Keep domain-certs and sip-eku separate. 2) In domain-certs, have a pointer text of the form Dean outlines above referencing sip-eku. 3) domain-certs updates rfc3261 (i.e., not essential correction); proceeds as a PS. 4) sip-eku stands on its own as a PS. 5) Revise domain-certs and sip-eku based on WGLC and PHL IETF discussion (of course.) Is this an accurate and representational summary of the discussion? Thanks, - vijay -- Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA) Email: [EMAIL PROTECTED],bell-labs.com,acm.org} WWW: http://www.alcatel-lucent.com/bell-labs _______________________________________________ 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
