[XCON] Consensus and Actions
Adam Roach <adam@nostrum.com> Tue, 18 March 2008 17:44 UTC
Return-Path: <xcon-bounces@ietf.org>
X-Original-To: ietfarch-xcon-archive@core3.amsl.com
Delivered-To: ietfarch-xcon-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 015293A6800; Tue, 18 Mar 2008 10:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.625
X-Spam-Level:
X-Spam-Status: No, score=-100.625 tagged_above=-999 required=5 tests=[AWL=-0.188, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tH4ye0-R3OxG; Tue, 18 Mar 2008 10:44:08 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CF903A6A82; Tue, 18 Mar 2008 10:44:08 -0700 (PDT)
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8468C3A69B2 for <xcon@core3.amsl.com>; Tue, 18 Mar 2008 10:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VTc1UE6dV5iW for <xcon@core3.amsl.com>; Tue, 18 Mar 2008 10:44:06 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 010A53A6B55 for <xcon@ietf.org>; Tue, 18 Mar 2008 10:44:05 -0700 (PDT)
Received: from sparc108.santera.com (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.2/8.14.1) with ESMTP id m2IHfk26094223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <xcon@ietf.org>; Tue, 18 Mar 2008 12:41:47 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <47DFFEE6.6010606@nostrum.com>
Date: Tue, 18 Mar 2008 12:41:58 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: XCON-IETF <xcon@ietf.org>
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Virus-Scanned: ClamAV 0.92.1/6288/Tue Mar 18 05:43:22 2008 on shaman.nostrum.com
X-Virus-Status: Clean
Subject: [XCON] Consensus and Actions
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org
[as chair]
At the face-to-face meeting in Philadelphia, we discussed the following
points, and took polls to determine the sense of the room on the topics.
I am repeating the points here for discussion. Interested parties are
encouraged to express their opinions (even if merely repeating what was
said in Philadelphia):
1. On the conference control protocol, we had a discussion regarding
whether CCMP operations are primarily semantic or primarily
syntactic in nature. None of the present parties favored a
syntactic model.
2. We discussed using draft-barnes-xcon-ccmp-04 as a basis for the
document to meet our milestone for a conference control protocol.
Several parties present at the face-to-face meeting supported such
adoption. No parties objected to such adoption.
3. In regards to draft-ietf-xcon-event-package-00, we discussed the
model to be used for partial updates of conference information.
The sense of the room was to use XML patch operations, as defined
in the current version of the document.
Additionally, the draft-ietf-xcon-event-package-00 document will be
updated with use cases in its next revision; and
draft-boulton-xcon-session-chat-01 will be updated with call flows as
the conference control protocol is specified.
/a
_______________________________________________
XCON mailing list
XCON@ietf.org
https://www.ietf.org/mailman/listinfo/xcon
- [XCON] Consensus and Actions Adam Roach