[XCON] Boston Meeting Consensus Points

[Adam Roach <adam at nostrum.com>]

[As chair]

This message summarizes the points of consensus that were reached at the 
Boston meeting last month. The intention of this mail is to summarize 
the agreed consensus as concisely as possible. Each consensus point had 
further discussion than what is summarized below, and I will be sending 
messages shortly that attempt to spur progress on those discussions.

Process requires that any consensus reached at an interim meeting is 
brought to the list for confirmation. Interested parties are encouraged 
to respond, even if such a response is nothing more than agreeing with 
each point.

I have attempted to make each consensus point stand on its own, 
sometimes adding context beyond what the notes record as consensus. As 
such, the following points may colored by my understanding and memory of 
what occurred during the meeting. In the case that any description of a 
point of consensus doesn't match what is recorded in the notes, please 
point it out. Full details and context for each of these points are 
available in the notes, which can be retrieved from 
http://www.softarmor.com/xcon/meets/interim2005/

Finally, I would like to apologize for the delay in getting this list 
posted to the mailing list; the past month has been very busy for both 
me and Alan.

---

Consensus point 1: We need the ability to identify (a) a single 
occurrence/instance of a recurring meeting and (b) all instances of a 
recurring meeting.

---

Consensus point 2: The term "multimedia stream" is not required, and 
will be removed from the documents.

---

Consensus point 3a: Templates are associated with human-readable 
documents (e.g. RFCs) that contain a text description of a kind of 
conference and XML schema.

Consensus point 3b: Templates define a "thing" that has specific 
parameters to be filled in.

Consensus point 3c: The client has the ability to query the server for a 
list of the templates that a server supports.

Consensus point 3d: The IANA registry of a template contains entries 
that are a triplet of {name, RFC, XML Schema}

---

Consensus point 4a: Conference times, dates, and recurrence information 
will be conveyed using iCal objects.

Consensus point 4b: XCON will not engage in extending iCal in any way.

---

Consensus point 5: When a conference is finished, it may go back to a 
latent state before being purged later.

---

Consensus point 6: ACLs for conference policy manipulation apply on a 
per-object level, not a per-field level.

---

Consensus point 7: The hierarchical state model presented by Henning 
(see slides at above URL) is not sufficiently detailed to adopt at this 
point in time.

---

Consensus point 8a: The term "conference object" will be used to 
describe the container for the total state of a conference.

Consensus point 8b: The term "conference template" will be used to 
describe that portion of the conference object that is different for 
different kinds of conference; in other words, it is the portion of the 
conference object that varies depending on the selected registered 
conference document.

Consensus point 8c: The term "common conference information" will be 
used to describe that portion of the conference object that does not 
change depending on the kind of conference.

Consensus point 8d: The term "registered conference document" will be 
used to describe the IANA-registered human-readable document

Consensus point 8e: In XCON, the term focus will be defined as "a call 
signaling endpoint that is addressed by a unique conference identifier. 
The focus maintains a call signaling relationship."

Consensus point 8f: The term "client" will be used to describe the 
software that implements the client functionality of the various 
protocols defined by XCON. In particular, any appearance of the phrase 
"XCON client" will be removed from all documents.

---

Consensus point 9a: Policy uses ranges to control limits on values.

Consensus point 9b: Policy will use a simplified list format (not common 
policy) to define permissions and membership.

---

Consensus point 10: The framework document will include text that 
discusses how a conference is created

---

Consensus point 11a: The floor control discussion in the framework 
document will be synced with the BFCP document.

Consensus point 11b: Additional discussions of security mechanisms 
around BFCP need to be addressed.

---

Consensus point 12: The framework document is not ready to adopt in its 
current format. The issue of adoption will be revisited after the next 
revision.

---

Possible consensus point 13: The minutes do not directly reflect this, 
but several of the above points are based on an underlying assumption 
that I believe was a de facto consensus reached in the room: that the 
distinction between rules and state is no longer useful, and that rules 
will consequently be going away.

---

/a


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