RE: [XCON] CPCP Requirement: Conference and Host Info
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [XCON] CPCP Requirement: Conference and Host Info
I think its simple to have these. If we were prioritizing, I'd
leave the last two off, but I don't see any reason to not
implement them.
Brian
> -----Original Message-----
> From: hisham.khartabil@nokia.com [mailto:hisham.khartabil@nokia.com]
> Sent: Monday, December 15, 2003 7:57 AM
> To: xcon@ietf.org
> Subject: [XCON] CPCP Requirement: Conference and Host Info
>
>
> This is in reference to requirements REQ-B1 to REG-B6, and
> REG-B10 in
> http://www.ietf.org/internet-drafts/draft-ietf-xcon-cpcp-reqs-00.txt
>
> REQ-B1: It MUST be possible to set, modify and delete a conference
> Subject.
>
> REQ-B2: It MUST be possible to set, modify and delete
> conference URI
> display name.
>
> REQ-B3: It MUST be possible to set, modify and delete conference
> creator information.
>
> REQ-B4: It MUST be possible to set, modify and delete
> conference URI
> link for more information.
>
> REQ-B5: It MUST be possible to set, modify and delete
> conference host
> contact information.
>
> REQ-B6: It MUST be possible to set, modify and delete short
> conference session description.
>
> REQ-B10: It SHOULD be possible to set, modify and delete conference
> Keywords. (This may be useful e.g. for search engines).
>
> I think a conference subject and display name as well as
> conference session description are useful. Perhaps the
> conference session description can appear on a conference web
> sight. What about conference host and creator information?
>
> I would like opinions on what people deem necessary
> information. Of course, we can have all if needed.
>
> Regards,
> Hisham
>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www1.ietf.org/mailman/listinfo/xcon
>
_______________________________________________
XCON mailing list
XCON@ietf.org
https://www1.ietf.org/mailman/listinfo/xcon
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.