Hmm, you might be reading slightly too much into this thread. I think
the summary of the thread from my point of view is simply
As an individual contributor, I'm sending you comment which amounts to
1) I think it is good to keep domain-cert and sip-eku as separate drafts
2) I would suggest changing
OLD
I-D.sip-eku [9] describes the method to validate any Extended Key
Usage values found in the certificate for a SIP domain.
Implementations MUST perform the checks prescribed by that
specification.
NEW
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.
And move the I-D.sip-eku[9] reference to be informative.
There's a bit more in the thread on why I think this change is good
that I won't repeat here. My implication that domain-certs might
become an essential correction was clearly wrong and should just be
ignored.
Thanks, Cullen <with my individual contributor hat on>
On Mar 21, 2008, at 11:40 AM, Vijay K. Gurbani wrote:
> 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
