Re: [XCON] FW: I-D ACTION:draft-barnes-xcon-framework-01.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [XCON] FW: I-D ACTION:draft-barnes-xcon-framework-01.txt

Not that anyone will read these before tomorrow's meeting, but here are some additional remarks on the latest draft. Apologies for any redundancies with others' comments; just haven't had the time and/or mental capacity to compare and contrast those with these...

- In general, I appreciate the attempt to simplify this document, thus dramatically reduce the overlap with the SIPPING conferencing framework. On the other hand, I think too much has been removed -- as suggested both by some of the comments already posted and by what follows. The pendulum needs to swing back toward the goal of making this a self-standing document that doesn't require one to read the SIPPING conferencing framework in order to get a coherent picture.

- Key issues that I think are missing from the document include:

a) A clear "statement of direction" vis a vis the TYPE of conferences that are intended to be addressed by XCON -- in particular, if and the degree to which ad hoc/reservation-less and scheduled/reserved conferences are supported.

b) Per my previous message, a clear definition of "conference start" ... and clear definitions of "active conference" and "conference instance" -- if those labels are to be retained.

c) A clear definition of "conference policy". (The existing definition is too constructionist, speaking only of a data object, its lifetime and when it can be modified.)

d) A clear description of who/what a client talks to in order to CREATE a reservation/conference.

        e) In general, a clear, high level architecture diagram.

- As you predict in the document, I continue to have a problem with the definition of "multimedia stream". ;-) For the record, here's my original critique (as sent on 11/12):

I don't much like the definition of <A> (single) stream to include multiple media -- as in "The stream includes voice, video, ...". If nothing else, such a definition is clearly inconsistent with the notion of an RTP stream. Better to be consistent with that definition, IMHO.

- I have a really hard time thinking of "Conference Information" as a data type.

- For reasons that are probably obvious, I like Figure 1 ;-) ... even though it doesn't really follow from the surrounding prose, which doesn't mention "instances".

- Sections 4.1 and 5.1, as written, are awfully redundant with Section 2. I would recommend removing them entirely, incorporating anything that is NOT redundant with Section 2 in to the subsections that follow each. Put another way, if you don't do this, then you'll basically be providing the same definitions THREE times -- in Section 2, in Section 4.1 or 5.1, and in the in the referenced subsections.

- Section 5.2: A template "provides relevant information that enables an authorized creating entity the ability to define the required granularity of conference configuration detail." Say what?!

- Section 5.4 seems to IMPLY that "conference start" is at the time a reservation is created. As noted in my previous email, I'm not happy with this. Regardless, implication is insufficient; a definitive statement is required -- somewhere.

- Section 5.5: "conference instance in progress". How is that different from a "conference instance" or an "active conference" or a "specific conference instance" (cf. Section 6.3). See related comments above.

- Section 6.5: Although not specific to this document, can someone remind me why user ids are instance-specific -- rather than user-specific?!


Regards, Keith

At 08:28 PM 12/29/2004, Mary Barnes wrote:

FYI, the updated (and entirely rewritten) XCON framework document is now available (Chris did try to post the file to the list earlier, but it appears that it didn't make it).

Comments and feedback are appreciated (there are clearly many Editor's notes where we recognize additional work is required, but those are likely not the only areas needing additional work).

Regards,
Mary

-----Original Message-----
From: i-d-announce-bounces at ietf.org [<mailto:i-d-announce-bounces at ietf.org>mailto:i-d-announce-bounces at ietf.org] On Behalf Of Internet-Drafts at ietf.org
Sent: Wednesday, December 29, 2004 2:39 PM
To: i-d-announce at ietf.org
Subject: I-D ACTION:draft-barnes-xcon-framework-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

Title : A Framework and Data Model for Centralized Conferencingg
Author(s) : M. Barnes, et al.
Filename : draft-barnes-xcon-framework-01.txt
Pages : 19
Date : 2004-12-29

This document introduces a framework and data model for Centralized
   Conferencing (XCON) applicable to participants using different call
   signaling protocols and sending media over varying network
   topologies.  The XCON framework outlines the conferencing protocols,
   which are complementary to the call signaling protocols, for building
   advanced conferencing applications.  It also introduces the concept
   of an XCON conferencing data model which binds all the defined
   components together.

A URL for this Internet-Draft is:
<http://www.ietf.org/internet-drafts/draft-barnes-xcon-framework-01.txt>http://www.ietf.org/internet-drafts/draft-barnes-xcon-framework-01.txt


To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request at ietf.org with the word unsubscribe in the body of the message.
You can also visit <https://www1.ietf.org/mailman/listinfo/I-D-announce>https://www1.ietf.org/mailman/listinfo/I-D-announce 

to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
        "get draft-barnes-xcon-framework-01.txt".

A list of Internet-Drafts directories can be found in
<http://www.ietf.org/shadow.html>http://www.ietf.org/shadow.html
or <ftp://ftp.ietf.org/ietf/1shadow-sites.txt>ftp://ftp.ietf.org/ietf/1shadow-sites.txt 


Internet-Drafts can also be obtained by e-mail.

Send a message to:
        mailserv at ietf.org.
In the body type:
        "FILE /internet-drafts/draft-barnes-xcon-framework-01.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


------------------------------------------------------------------------- CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY ------------------------------------------------------------------------- In order to maintain computing infrastructure integrity, Cisco Systems Enterprise Messaging Services and InfoSec teams have set a mail policy disallowing executable attachments in email. This message contained an executable attachment type that is prohibited by this policy. The attachment has been removed from this message and copied to quarantine by our systems. It will be held in quarantine for seven days in the event that the content needs to be retrieved. Please be aware many viruses attempt to look like legitimate email or notifications from anti-virus systems. We will clearly mark a seperation between our notifications and the original email as follows: "CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY" For further reference information about viruses and email antivirus efforts within Cisco, please visit: http://wwwin.cisco.com/it/ems/services/antiviral If your concern isn't addressed by the information in this notification or the above web page, you may open a support request: http://wwwin.cisco.com/support/ Select "Messaging", "Email-Related", "Mail Routing" Please include in the text of your case the following information: * Full headers of the message. Documentation on displaying the full headers is available at this URL: http://wwwin.cisco.com/support/library/faqs/solution002471.html * This unique quarantine identifier: iBU4e5RO016073 If the matter is urgent, you may follow up by calling one of the below referenced numbers. Please make every effort to provide the above requested information via the support web tool prior to calling as it will greatly aid the resolution of your issue. Americas: 1 408 526 8888 Asiapac +61 2 8446 8888 EMEA +31 20 485 4888 Japan +81 3 5549 6888 US (Toll Free) 1| 800| 888| 8187| (ext.68888) Thank you for your cooperation, Enterprise Messaging Services Cisco Systems, Inc

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


_______________________________________________
XCON mailing list
XCON at 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.