[XCON] CPCP Issue 23: Authenticating a User

To: <xcon at ietf.org>
Subject: [XCON] CPCP Issue 23: Authenticating a User
From: hisham.khartabil at nokia.com
Date: Fri, 13 Aug 2004 15:24:16 +0300
List-help: <mailto:xcon-request@ietf.org?subject=help>
List-id: Centralized Conferencing <xcon.ietf.org>
List-post: <mailto:xcon@ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
Sender: xcon-bounces at ietf.org
Thread-index: AcSBMHL6igP2gMYYQtCHDe5cpc2L/w==
Thread-topic: CPCP Issue 23: Authenticating a User

The <authenticate> action defines the mechanism used by the conference focus to authenticate a user.  This element is an enumerated integer type, with defined values of: none, asserted-id, shared-secret and certificate.

We already have the necessary tools in conditions (<any>, conditions without identities). So this not useful and will be removed as agreed during the meeting.

Regards,
Hisham

_______________________________________________
XCON mailing list
XCON at ietf.org
https://www1.ietf.org/mailman/listinfo/xcon

Prev by Date: [XCON] CPCP Issue 22: Media Stream Security Policy
Next by Date: [XCON] CPCP Issue 24: Meta Policy as separate document
Previous by thread: [XCON] CPCP Issue 22: Media Stream Security Policy
Next by thread: [XCON] CPCP Issue 24: Meta Policy as separate document
Index(es):
- Date
- Thread

[XCON] CPCP Issue 23: Authenticating a User

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.