[Sip] review comments on draft-khartabil-sip-conferencing-00
Timothy SOETENS <timothy.soetens@alcatel.be> Fri, 14 September 2001 14:18 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18450 for <sip-archive@odin.ietf.org>; Fri, 14 Sep 2001 10:18:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA28617; Fri, 14 Sep 2001 09:30:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA28586 for <sip@optimus.ietf.org>; Fri, 14 Sep 2001 09:30:46 -0400 (EDT)
Received: from relay1.alcatel.be (alc119.alcatel.be [195.207.101.119]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17632 for <sip@ietf.org>; Fri, 14 Sep 2001 09:31:13 -0400 (EDT)
Received: from bemail01.net.alcatel.be (localhost [127.0.0.1]) by relay1.alcatel.be (8.10.1/8.10.1) with SMTP id f8EDUD102106 for <sip@ietf.org>; Fri, 14 Sep 2001 15:30:13 +0200 (MET DST)
Received: from alcatel.be ([138.203.67.193]) by bemail01.net.alcatel.be (Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) with SMTP id C1256AC7.004A292E; Fri, 14 Sep 2001 15:30:02 +0200
Message-ID: <3BA20659.95DD13F0@alcatel.be>
Date: Fri, 14 Sep 2001 15:30:01 +0200
From: Timothy SOETENS <timothy.soetens@alcatel.be>
Organization: Alcatel
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: sip mailing list <sip@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sip] review comments on draft-khartabil-sip-conferencing-00
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>
X-BeenThere: sip@ietf.org
Content-Transfer-Encoding: 7bit
Hi, I have some, mainly editorial, comments about the draft draft-khartabil-sip-conferencing-00.txt. 5.1 (page 5) "The 200 response will contain a list of current participants, ..." I think emphasising that this is the 200 OK response for the REGISTER request will make this more clear. (I first interpreted it as a 200 for the SUBSCRIBE request, but did not understand, because the CPS has to send a NOTIFY with exactly this information.) 5.5.1 (page 6) NOTIFY message example The contact header contains the conference ID. Is this correct? I though to have understood that the contact headers should be a list of participants of the conference. 5.2 & 5.3 (pages 6 and 7) the accronyms cps., imcs. and imcps. are mixed. Is this intentionally or do they all signify the same type of server? If intentionally, I think it would be opportune to clarify which specific feature on an IMCPS is used. If the same type of server is meant, I suggest to use only cps. to avoid confusion. Regards, Tim. -- Timothy Soetens _________________________________________ From the Network Strategy Group @ Alcatel Tel. +32-3-240.42.11 Fax +32-3-240.48.88 _______________________________________________ Sip mailing list http://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] review comments on draft-khartabil-sip-conf… Timothy SOETENS