Vijay K. Gurbani wrote:
Wouldn't drafts like sec-flows, sip-certs, sip-sips, domain-certs
all lead towards providing guidelines for the use of SIP
security?
Certainly, and these are all both within the charter of the working
group, and individually milestoned when the WG develops a consensus to
deliver them.
So I'd like to propose that we delete these milestones for now, and
bring them back only when we have a concrete proposal on the table
for what we think we can actually do (and should do) here.
It looks like the drafts and a substantive body of the work in
this area is out there; just needs to be organized for a more
amenable deadline. But, I may be mistaken...
Otherwise said, you think the milestones in question were essentially
made redundandt by the adoption of the more-focused drafts? If so, then
we can just delete the milestones in question, as we know we can add new
milestones for new "more focused" drafts under our existing charter.
Or do we need something like a meta or framework document that brings
all these pieces together into a more coherent structure?
--
Dean
_______________________________________________
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
