RE: I-D ACTION:draft-ietf-mmusic-sccp-01.txt

Heil Franca Marcelo ICM N MC MI E 73 <Marcelo.HeilFranca@icn.siemens.de> Fri, 09 March 2001 22:47 UTC

Return-Path: <owner-confctrl>
Received: (from majordom@localhost) by zephyr.isi.edu (8.9.3/8.9.3) id OAA09731 for confctrl-outgoing; Fri, 9 Mar 2001 14:47:49 -0800 (PST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by zephyr.isi.edu (8.9.3/8.9.3) with ESMTP id OAA09726 for <confctrl@zephyr.isi.edu>; Fri, 9 Mar 2001 14:47:48 -0800 (PST)
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163]) by tnt.isi.edu (8.11.2/8.11.2) with ESMTP id f29Mlkq21743 for <confctrl@ISI.EDU>; Fri, 9 Mar 2001 14:47:46 -0800 (PST)
Received: from moody.mchh.siemens.de ([194.138.158.226]) by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id XAA24849; Fri, 9 Mar 2001 23:38:43 +0100 (MET)
Received: from mchh159e.mch.pn.siemens.de ([139.21.130.171]) by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id SAA26174; Fri, 9 Mar 2001 18:43:44 +0100 (MET)
Received: by mchh159e.mch.pn.siemens.de with Internet Mail Service (5.5.2653.19) id <FSJN4KTK>; Fri, 9 Mar 2001 18:43:48 +0100
Message-ID: <EB2D9281A815D31181DA0001FA7E2E188CE52D@mchh157e.mch.pn.siemens.de>
From: Heil Franca Marcelo ICM N MC MI E 73 <Marcelo.HeilFranca@icn.siemens.de>
To: "'cabo@tzi.org'" <cabo@tzi.org>
Cc: confctrl@ISI.EDU
Subject: RE: I-D ACTION:draft-ietf-mmusic-sccp-01.txt
Date: Fri, 09 Mar 2001 18:43:40 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by zephyr.isi.edu id OAA09727
Sender: owner-confctrl@zephyr.isi.edu
Precedence: bulk

Carsten,

I see SCCP as an interesting option for tighly-coupled conference control in
the context of the internet multimedia conference architecture and would
like to support it. Could you please give me some background information on
the history of SCCP? 

There seems to be no specific statement to it in the MMUSIC WG charter and I
have not seen any directly related discussions in the mailing list in the
past weeks. Also the recently expired draft-ietf-mmusic-confarch-03.txt
makes references to a SCCP internet-draft from 1996(!). 

Thanks,
Marcelo

Marcelo Heil França  
Siemens AG
ICM N MC MI E 73
Tel: +49 89 72245095
E-Mail: marcelo.heilfranca@icn.siemens.de


-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Dienstag, 6. März 2001 12:51
Cc: confctrl@ISI.EDU
Subject: I-D ACTION:draft-ietf-mmusic-sccp-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Multiparty Multimedia Session Control
Working Group of the IETF.

	Title		: Simple Conference Control Protocol
                          Service Specofocation
	Author(s)	: C. Bormann
	Filename	: draft-ietf-mmusic-sccp-01.txt
	Pages		: 24
	Date		: 05-Mar-01
	
This document defines the services for a simple conference control
protocol (SCCP) to be used for tightly coupled conferences. It is
part of the Internet Multimedia Conferencing Architecture, proposed
in [1].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sccp-01.txt

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-ietf-mmusic-sccp-01.txt".

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mmusic-sccp-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.