On Jun 23, 2008, at 3:23 PM, Hadriel Kaplan wrote:
[fixed subject title, since I apparently broke it]
How about a compromise: 2 WG's of 2-hour meetings each (since
today's SIP WG actually takes 2 of 2-hour meeting slots I think).
One for the general SIP stuff as today, and one for "SIP Security".
Ah yes, two eternal working groups to replace one.
The new security group would take such things as:
draft-ietf-sip-dtls-srtp-framework
-- This one is arguably done, depending on what we believe about RFC
4474 and gateways/b2buas.
draft-ietf-sip-eku
-- EKU is basically done.
draft-ietf-sip-media-security-requirements
-- This one is done
draft-ietf-sip-ua-privacy
-- This one is done,
draft-ietf-sip-domain-certs
-- This one is done
draft-ietf-sip-e2m-sec
-- This one is done
draft-ietf-sip-saml
-- I'm not sure this one is ever getting done.
So I'm not sure there's enough there to justify a WG.
How about an "Identity in SIP" working group that takes on fixing RFC
4474 for gateways/b2buas and possibly considers identity/role
assertion using SAML?
--
Dean
_______________________________________________
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
