Cullen Jennings wrote:
> 
> Hmm, you might be reading slightly too much into this thread. 

Cullen: In the words of a British ITV sitcom character I used to
watch as a kid, "A thousand apologies, please!" (beer in Dublin for
the first correct guess)  More serious stuff inline...

> 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
[...]

OK; noted these two points.

> My implication that domain-certs might become an essential correction 
> was clearly wrong and should just be ignored.

OK; with the essential corrections bit out of the way, we have
made some progress from where we started off when we had our
initial phone conference on this back in Nov/Dec 2007.  The
guidance back then was split the drafts and have domain-certs
proceed as Informational.  The drafts were split soon after.

The drafts can proceed in the split format with the changes noted
above (speaking for myself here as 1/2 of the editor team -- I have
not conversed with Scott yet.)  However, we need to now converge on
which track to put domain-certs on: Info, BCP, or PS?  Both Scott
and I believe that it should be at least BCP, if not PS; and
others that reviewed the draft also assumed it was PS.

What would be the best way to close this one administrative issue
so we can submit the revised drafts accordingly: list discussion or
phone conference?  If the latter, I can send email out to the chairs,
you, Scott and me, and any interested list participants to
converge on a time and date.

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

Reply via email to