Subject: Re: [XCON] draft-ietf-xcon-common-data-model-14

From: Oscar Novo <[email-masked]>
Date: Wed, 3 Feb 2010 16:11:27 +0100

Hi Sean,

True, the field should be defined as multiple password. I'll change that in the following version of the draft.
The propose to have different passwords in the flexibility to have different set of users with different credentials. So, the conference server can restrict access to a set of users by just removing the credentials from the server.

I think the extension of the <conf-uris> element is not really needed since the limitations of the credentials can be done using the same roles (you might want to restrict access to the group of participants A but not the group of participants B).

Regards,

Oscar

________________________________
From: [email-masked] [mailto:[email-masked]] On Behalf Of Duddy, Sean (Sean)
Sent: 27. tammikuuta 2010 14:14
To: [email-masked]
Subject: [XCON] draft-ietf-xcon-common-data-model-14

Hi all,
    The new password field in  draft-ietf-xcon-common-data-model-14 is defined as follows:-

    <xs:element name="conference-password" type="xs:string"/>

In section 4.2.10, it states that this field contain password(s). What would be the usecase for multiple passcodes on the same URI?
If it is a valid use case then the xsd type for this should xs::list.

Does the purpose field defined in rfc4575 need to be extended to indicate the type of URI i.e. moderator,particpant etc?
Or how would a client that just created a conference distinguish between the URIs?

Regards
Sean