[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Sipping] SIP Identity Usage in Enterprise Scenarios
As a further update to my previous email, look at the USERNAME provision
in the current ID for ICE (draft 05), which I consider a weakness of the
protocol.
My preference would be to replace that password with some kind of MIKEY
exchange such that the password is only for that session, otherwise
you'll see cheap phones or all with the same password being vulnerable,
which I suggest is a strong weakness of ICE.
Regards
Michael
It is amazing what you can accomplish if you do not care who gets the
credit.
- Harry S Truman
-----Original Message-----
From: Fries, Steffen [mailto:steffen.fries at siemens.com]
Sent: September 14, 2005 11:10 AM
To: Michael Slavitch; sipping at ietf.org
Cc: Tschofenig, Hannes
Subject: RE: [Sipping] SIP Identity Usage in Enterprise Scenarios
Hi Michael,
no, from us there is just the draft available.
What is your approach/your thoughts with respect to the draft?
Regards
Steffen
> -----Original Message-----
> From: Michael Slavitch [mailto:slavitch at objectworld.com]
> Sent: Wednesday, September 14, 2005 5:07 PM
> To: Fries, Steffen; sipping at ietf.org
> Subject: RE: [Sipping] SIP Identity Usage in Enterprise Scenarios
>
> Hello,
>
> We are very much interesting in discussing SIP identity in the
> enterprise. Is there more documentation than this brief draft? If
> need be we could collaborate using our own implementations as an
> example.
>
> Regards
>
> Michael
>
>
>
> -----Original Message-----
> From: sipping-bounces at ietf.org
> [mailto:sipping-bounces at ietf.org] On Behalf Of Fries, Steffen
> Sent: September 14, 2005 10:57 AM
> To: sipping at ietf.org
> Subject: [Sipping] SIP Identity Usage in Enterprise Scenarios
>
> Hi all,
>
> shortly before the last IETF meeting we submitted a draft regarding
> SIP Identity Usage in Enterprise Scenarios. This document describes a
> scenario for the SIP identity work involving certificate management in
> enterprise environments.
> A discussion of possible solutions is included.
> The document
> would be targeted for a BCP, as the available SIP identity work
> already provides the base on the standards track.
>
> Unfortunately there hasn't been discussion at the mailing list so far.
> We would like to see if there is any interest in doing this work
> within this WG.
>
> You may download the document from
> http://www.tschofenig.priv.at/drafts/draft-fries-sipping-identity-
> enterprise
> -scenario-00.txt
>
> With friendly regards
>
> Steffen
>
> _______________________________________________
> Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use
> sip-implementors at cs.columbia.edu for questions on current sip Use
> sip at ietf.org for new developments of core SIP
>
>
> --
>
>
>
--
BEGIN-ANTISPAM-VOTING-LINKS
------------------------------------------------------
Teach CanIt if this mail (ID 434179) is spam:
Spam:
http://asteroid.objectworld.com/canit/b.php?c=s&i=434179&m=a059b2857d4f
Not spam:
http://asteroid.objectworld.com/canit/b.php?c=n&i=434179&m=a059b2857d4f
Forget vote:
http://asteroid.objectworld.com/canit/b.php?c=f&i=434179&m=a059b2857d4f
------------------------------------------------------
END-ANTISPAM-VOTING-LINKS
_______________________________________________
Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP