From extest-admin@lists.bell-labs.com  Thu Mar  1 05:07:35 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA28981
	for <spirits-archive@odin.ietf.org>; Thu, 1 Mar 2001 05:07:34 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP id 4DFB244468
	for <spirits-archive@lists.ietf.org>; Thu,  1 Mar 2001 05:06:49 -0500 (EST)
Subject: lists.bell-labs.com mailing list memberships reminder
From: mailman-owner@lists.bell-labs.com
To: spirits-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: extest-admin@lists.bell-labs.com
Errors-To: extest-admin@lists.bell-labs.com
X-BeenThere: extest@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
Message-Id: <20010301100649.4DFB244468@lists.bell-labs.com>
Date: Thu,  1 Mar 2001 05:06:49 -0500 (EST)

This is a reminder, sent out once a month, about your
lists.bell-labs.com mailing list memberships.  It includes your
subscription info and how to use it to change it or unsubscribe from a
list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, spirits-request@lists.bell-labs.com) containing
just the word 'help' in the message body, and an email message will be
sent to you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@lists.bell-labs.com.  Thanks!

Passwords for spirits-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
spirits@lists.bell-labs.com              QMKP      
http://lists.bell-labs.com/mailman/options/spirits/spirits-archive%40lists.ietf.org


From spirits-admin@lists.bell-labs.com  Tue Mar  6 14:41:02 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA24479
	for <spirits-archive@odin.ietf.org>; Tue, 6 Mar 2001 14:41:01 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 1C5BA4438D; Tue,  6 Mar 2001 14:41:01 -0500 (EST)
Delivered-To: spirits@share.research.bell-labs.com
Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6])
	by lists.bell-labs.com (Postfix) with SMTP id 7593E44336
	for <spirits@share.research.bell-labs.com>; Tue,  6 Mar 2001 14:40:02 -0500 (EST)
Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Tue Mar  6 14:38:41 EST 2001
Received: by lists.bell-labs.com (Postfix)
	id 495B444380; Tue,  6 Mar 2001 14:25:32 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from ans.ih.lucent.com (ans.ih.lucent.com [135.1.218.156])
	by lists.bell-labs.com (Postfix) with SMTP id EFCFC4437D
	for <spirits@lists.bell-labs.com>; Tue,  6 Mar 2001 14:25:31 -0500 (EST)
Received: by ans.ih.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id NAA16717; Tue, 6 Mar 2001 13:25:28 -0600
Cc: Steve Bellovin <smb@research.att.com>
Received: from lucent.com by ans.ih.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id NAA16709; Tue, 6 Mar 2001 13:25:26 -0600
Message-ID: <3AA53A18.E91010D9@lucent.com>
From: Alec Brusilovsky <abrusilovsky@lucent.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en,ru,uk
MIME-Version: 1.0
To: SPIRITS list <spirits@lists.bell-labs.com>
Original-CC: Steve Bellovin <smb@research.att.com>
Content-Type: multipart/mixed;
 boundary="------------CCE81585E60CCC06283A6D26"
Subject: [SPIRITS] WG Last Call - Protocol Requirements
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
Reply-To: spirits@lists.bell-labs.com
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Tue, 06 Mar 2001 13:27:20 -0600

This is a multi-part message in MIME format.
--------------CCE81585E60CCC06283A6D26
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear members of the SPIRITS WG,

The newly published I-D, that can be found at:
http://www.ietf.org/internet-drafts/draft-ietf-spirits-reqs-00.txt

is a candidate for the SPIRITS Protocol Requirements
Informational RFC.

Both Steve and I are encouraging online discussion of this
document.

Current Last call status is valid through March 27, 2001.
After that date and upon reaching consensus, the resulting
document will be submitted to the IESG.

Regards,
Alec

--------------CCE81585E60CCC06283A6D26
Content-Type: text/x-vcard; charset=us-ascii;
 name="abrusilovsky.vcf"
Content-Description: Card for Alec Brusilovsky
Content-Disposition: attachment;
 filename="abrusilovsky.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Brusilovsky;Alec 
tel;fax:+1 630 713 5840 
tel;work:+1 630 713 8401
x-mozilla-html:FALSE
org:e-Services Group;Next Generation Evolution and Architecture
version:2.1
email;internet:abrusilovsky@lucent.com
title:MTS 
adr;quoted-printable:;;IHP 1A-423=0D=0A263 Shuman Blvd,P O Box 3050;Naperville;IL;60566-7050;U S
x-mozilla-cpt:;5312
fn:Alec  Brusilovsky
end:vcard

--------------CCE81585E60CCC06283A6D26--


_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Tue Mar 13 05:59:01 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA18051
	for <spirits-archive@odin.ietf.org>; Tue, 13 Mar 2001 05:59:01 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 2177744352; Tue, 13 Mar 2001 05:59:02 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from cvis28.marconicomms.com (cvis28.marconicomms.com [195.99.244.60])
	by lists.bell-labs.com (Postfix) with ESMTP id CCA6244336
	for <spirits@lists.bell-labs.com>; Tue, 13 Mar 2001 05:58:49 -0500 (EST)
Received: from cvis03.gpt.co.uk (unverified) by cvis28.marconicomms.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc363f43c5244001ea6@cvis28.marconicomms.com> for <spirits@lists.bell-labs.com>;
 Tue, 13 Mar 2001 10:42:56 +0000
Received: from marconicomms.com by cvis03.gpt.co.uk with SMTP
 (8.8.8+Sun/cvms-30) id KAA26805; Tue, 13 Mar 2001 10:42:54 GMT
Received: by marconicomms.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 80256A0E.003AD391 ; Tue, 13 Mar 2001 10:42:32 +0000
X-Lotus-FromDomain: MCMAIN@MCEXT
From: "Dave Hewins" <Dave.Hewins@marconi.com>
To: spirits@lists.bell-labs.com
Message-ID: <80256A0E.003AD187.00@marconicomms.com>
Subject: Re: [SPIRITS] WG Last Call - Protocol Requirements
Mime-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
Reply-To: spirits@lists.bell-labs.com
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Tue, 13 Mar 2001 10:42:39 +0000
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA18051



Hi,

just a few comments on the I-D draft-ietf-spirits-reqs-00.txt, which I hope are
useful.

Comments on the SPIRITS protocol requirements I-D


1.   Page 1,section 1,para 2, 1st sentence replace:  "...documents to
consensus..." with "...documents the consensus...".

2.   Page 2,section 3, 2nd sentence replace same as comment 1.

3.   Page 5, para 1, reference to section 6 should be to section 7.

4.   Page 5, section 5, item 3, 2nd sentence, replace:  "In case the SPIRITS..."
with "As the SPIRITS...".

5.   Page 5, section 5, item 4, line 3, replace: "...encoded Neither..." with
"...encoded.  Neither...".

6.   Page 6 "The list of CS-2 DP's envisaged in SPIRITS is... " this statement
conflicts with that made on page 5, section 5
                clause 1 which states that  "The list of the DPs to be covered
encompasses those defined by the IN Capability Set 3...".
               Other references to CS-2 also occur on pages 7(section 6 last
para) & 11(first para).  The 3 references to CS-2 need
               changing to CS-3.

7.   Pages 6 & 7 Clarification required, I am confused about what is being
stated in section 5 regarding the DPs.  If the first
                list of DPs are those required for a base SPIRITS implementation
with the second list of 3 DPs the additional DPs for the
               milestone services,   then the sentence before the last 3 listed
DPs needs rewording. Because at present it appears
               that all you need for mile stone services is those 3 DPs and not
the others.  The possible change is simple , replace:
               "With that, the only DPs... " with "In addition the following DPs
are..."

8.   Page 9, section 7, para 1, 2nd sentence states: "Thus, Registration is an
essential service (not yet addressed by PINT),
                which is initiated from the IP side."   However to quote from
the last PINT email "With the publication of the PINT MIB the
                PINT working group has fulfilled its mission and milestones and
it is time to close the working group."  Which group will
               address the registration service?

9.   Page 9, section 7, item 1, second line replace: "...which is then passed to
by PINT server ..." with "...which is then passed
                by the PINT server...".

10.  Page 9, section 8, 1st line, reads: "...this section is neither
PINT-specific, nor IN-specific;..." but never discusses PINT,  the
                sentence should read "...this section is neither
SPIRITS-specific, nor IN-specific; ..."

11.  Page 10 Methodology section needs section number changing to 9.


Dave Hewins




_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Tue Mar 13 17:52:00 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA29717
	for <spirits-archive@odin.ietf.org>; Tue, 13 Mar 2001 17:51:59 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id F063C44345; Tue, 13 Mar 2001 17:52:01 -0500 (EST)
Delivered-To: spirits@share.research.bell-labs.com
Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49])
	by lists.bell-labs.com (Postfix) with SMTP id B682944336
	for <spirits@share.research.bell-labs.com>; Tue, 13 Mar 2001 17:51:54 -0500 (EST)
Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Tue Mar 13 17:49:26 EST 2001
Received: by lists.bell-labs.com (Postfix)
	id 2930644380; Tue, 13 Mar 2001 17:38:09 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from hotair.hobl.lucent.com (hotair.hobl.lucent.com [199.118.135.2])
	by lists.bell-labs.com (Postfix) with SMTP id EC8814437D
	for <spirits@lists.bell-labs.com>; Tue, 13 Mar 2001 17:38:08 -0500 (EST)
Received: from bell-labs.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id RAA26397; Tue, 13 Mar 2001 17:38:08 -0500
Message-ID: <3AAEA144.B5635D83@bell-labs.com>
From: Igor Faynberg <faynberg@bell-labs.com>
Reply-To: faynberg@lucent.com
Organization: Lucent Technologies
X-Mailer: Mozilla 4.73 [en]C-CCK-MCD EMS-1.4  (Win95; U)
X-Accept-Language: en,ru
MIME-Version: 1.0
To: spirits@lists.bell-labs.com
Subject: Re: [SPIRITS] WG Last Call - Protocol Requirements
References: <80256A0E.003AD187.00@marconicomms.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Tue, 13 Mar 2001 17:37:56 -0500
Content-Transfer-Encoding: 7bit

Dave,

Thank you very much for a detailed analysis and excellent comments. I
will get to work on them after the IETF meeting. A few comments in-line
(mainly, responses to your questions):

Dave Hewins wrote:
> 
> ...
> 
> 
> 
> 
> 8.   Page 9, section 7, para 1, 2nd sentence states: "Thus, Registration is an
> essential service (not yet addressed by PINT),
>                 which is initiated from the IP side."   However to quote from
> the last PINT email "With the publication of the PINT MIB the
>                 PINT working group has fulfilled its mission and milestones and
> it is time to close the working group."  Which group will
>                address the registration service?

It does not need to be a group, actually.  There could be four
possibilities:

1) The PINT RFC gets updated (by its authors) and then sent for the IESG
last call 

2) The registration (although a PINT service) is done in SPIRITS as part
of the protocol

3) A new group is formed to deal with the new services (so far, I don't
see a reason for that)

4) The registration is agreed to be just plain vanilla SIP registration,
and that will be reflected in the protocol document (I think this is the
most likely outcome)

> 
> 9.   Page 9, section 7, item 1, second line replace: "...which is then passed to
> by PINT server ..." with "...which is then passed
>                 by the PINT server...".
> 
> 10.  Page 9, section 8, 1st line, reads: "...this section is neither
> PINT-specific, nor IN-specific;..." but never discusses PINT,  the
>                 sentence should read "...this section is neither
> SPIRITS-specific, nor IN-specific; ..."

Ah, that was written because the section was part of the PINT & IN
requirements. Anyway, I will take a closer look.


Again, many thanks for reading, and thinking, and commenting
constructively! This is great help. I especially appreciate it that you
offer a specific fix rather than just say that something is wrong.

Igor

_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Wed Mar 14 13:35:03 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00830
	for <spirits-archive@odin.ietf.org>; Wed, 14 Mar 2001 13:35:03 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 81E9F44351; Wed, 14 Mar 2001 13:35:02 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by lists.bell-labs.com (Postfix) with ESMTP id 42A3144336
	for <spirits@lists.bell-labs.com>; Wed, 14 Mar 2001 13:34:39 -0500 (EST)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-green.research.att.com (Postfix) with ESMTP id B3C5E1E120
	for <spirits@lists.bell-labs.com>; Wed, 14 Mar 2001 13:34:31 -0500 (EST)
Received: from berkshire.research.att.com (secure.research.att.com [135.207.24.10])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id NAA06288
	for <spirits@lists.bell-labs.com>; Wed, 14 Mar 2001 13:34:29 -0500 (EST)
Received: from berkshire.research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP id 1E52D35C44
	for <spirits@lists.bell-labs.com>; Wed, 14 Mar 2001 13:34:24 -0500 (EST)
X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.3 #1[UCI]
From: Steve Bellovin <smb@research.att.com>
To: spirits@lists.bell-labs.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-Id: <20010314183425.1E52D35C44@berkshire.research.att.com>
Subject: [SPIRITS] SIP-H.323 Interworking Requirements draft
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
Reply-To: spirits@lists.bell-labs.com
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Wed, 14 Mar 2001 13:34:06 -0500

SPIRITS folks may want to take a look at
draft-agrawal-sip-h323-interworking-reqs-02.txt.
The authors request that comments be sent to them via
sip-h323@yahoogroups.com


		--Steve Bellovin, http://www.research.att.com/~smb



_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Wed Mar 14 13:37:03 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00866
	for <spirits-archive@odin.ietf.org>; Wed, 14 Mar 2001 13:37:02 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 82EE844351; Wed, 14 Mar 2001 13:37:00 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69])
	by lists.bell-labs.com (Postfix) with ESMTP id C83A144336
	for <spirits@lists.bell-labs.com>; Wed, 14 Mar 2001 13:36:53 -0500 (EST)
Received: from gab200r1.ems.att.com ([135.37.94.32])
	by kcmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id f2EIap701148
	for <spirits@lists.bell-labs.com>; Wed, 14 Mar 2001 13:36:52 -0500 (EST)
Received: from njb140bh2.ems.att.com by gab200r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2)
	id NAA14677; Wed, 14 Mar 2001 13:36:04 -0500 (EST)
Received: by njb140bh2.ems.att.com with Internet Mail Service (5.5.2653.19)
	id <G5G853R4>; Wed, 14 Mar 2001 13:36:47 -0500
Message-ID: <E5B80B001D76D211879C00E029107761083F16A2@njc240po05.mt.att.com>
From: "Roy, Radhika R, ALCOO" <rrroy@att.com>
To: spirits@lists.bell-labs.com
Subject: RE: [SPIRITS] SIP-H.323 Interworking Requirements draft
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
Reply-To: spirits@lists.bell-labs.com
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Wed, 14 Mar 2001 13:36:40 -0500

Hi, Steve:

Many thanks.

Radhika

-----Original Message-----
From: Steve Bellovin [mailto:smb@research.att.com]
Sent: Wednesday, March 14, 2001 1:34 PM
To: spirits@lists.bell-labs.com
Subject: [SPIRITS] SIP-H.323 Interworking Requirements draft


SPIRITS folks may want to take a look at
draft-agrawal-sip-h323-interworking-reqs-02.txt.
The authors request that comments be sent to them via
sip-h323@yahoogroups.com


		--Steve Bellovin, http://www.research.att.com/~smb



_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits

_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Sun Mar 25 19:17:01 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27593
	for <spirits-archive@odin.ietf.org>; Sun, 25 Mar 2001 19:17:00 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id B733D4433C; Sun, 25 Mar 2001 19:17:01 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from mailhub.wlg.nec.co.nz (nzls21.wlg.nec.co.nz [202.37.54.144])
	by lists.bell-labs.com (Postfix) with ESMTP id AB08644336
	for <spirits@lists.bell-labs.com>; Sun, 25 Mar 2001 19:16:51 -0500 (EST)
Received: from mailhost.wlg.nec.co.nz (nzlu02.wlg.nec.co.nz [202.37.54.14])
	by mailhub.wlg.nec.co.nz (8.9.1/8.9.1) with ESMTP id MAA09925
	for <spirits@lists.bell-labs.com>; Mon, 26 Mar 2001 12:37:25 +1200 (NZST)
Received: from nzls54.wlg.nec.co.nz by mailhost.wlg.nec.co.nz (8.8.8+Sun/SMI-SVR4)
	id MAA24090; Mon, 26 Mar 2001 12:14:24 +1200 (NZST)
Received: (from bchapman@localhost)
	by nzls54.wlg.nec.co.nz (8.8.8+Sun/8.8.8) id MAA16727
	for spirits@lists.bell-labs.com; Mon, 26 Mar 2001 12:19:13 +1200 (NZST)
From: Bruce Chapman <bchapman@wlg.nec.co.nz>
Message-Id: <200103260019.MAA16727@nzls54.wlg.nec.co.nz>
To: spirits@lists.bell-labs.com
X-Sun-Charset: US-ASCII
Subject: [SPIRITS] Some Thoughts On Protocol Requirements
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
Reply-To: spirits@lists.bell-labs.com
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Mon, 26 Mar 2001 12:19:13 +1200 (NZST)

Hello all,

Sorry this is running quite late, but this has been my 
first opportunity get down some thoughts on 
draft-ietf-spirits-reqs-00.txt

They are thoughts as opposed to opinions, and are personal 
and may not reflect the official views of my employer.




B Interface Requirements
------------------------

Also there seem to be some unusual characteristics of the B ( Server - Gateway) interface, which I think should be considered.

Specifically, there are 'sessions' on B that may be real or virtual. 
These sessions need to have the characteristic that the Gateway can 
determine if the session is still active. 
The unusual charateristics 
are those related to traffic profiles. These sessions will (in the 
case of ICW service at least), last for several minutes, and in some 
cases several hours. However transactions will be at a very low rate 
in the order of 1 transaction per several minutes. There are lots 
(in the order of ten thousand plus) of these sessions in place at any 
one time, possibly more than can be supported by transport protocols with 
'real' sessions due to the 64K limit on TCP sessions per host.

There may be desired latency requirements which affect the transport 
protocol choice, because the transactions are signalling the presence 
of real-time events at the Service Switching Function. 

There is also a requirement that this interface B is/may be secure, since 
it is carried over the internet, and there is an opportunity for fraud if 
it is not. 

These requirements should be discussed.


Thoughts on the requirements Document & Requirements
----------------------------------------------------

Did I miss something?

Where was the discussion that resulted in SIP being chosen as the
transport protocol for spirits?

We have but one sentence in section 4 attempting to justify the choice
of SIP.

The background work in the draft is good but I cannot find any analysis
of the options for the transport protocol.



from my limited experience I think there are at least 3 addtional factors to
consider in choosing the protocol.

1. What are the protocols used at the boundary of the architecture?

2. Do we have a preference for a binary or text based protocol?

3. Do we have a preference for a legacy protocol or not?


Here is my 2 cents worth of analysis:

1. What are the protocols used at the boundary of the architecture?

The draft provides a good analysis of PSTN and Mobile considerations
here, which is the only communication channel crossing the boundary into
or out of the architecture. These protocols are binary and described
with  ASN.1

2. Do we have preference for a binary or text based protocol?

The draft makes fleeting mention of this ( 5.4)

"Neither the use
   of the ASN.1, nor the requirement for binary encoding are the typical
   requirements for the IETF application protocols"   

(eds please note, there is a missing period prior to this sentence !!)

However the draft does not analyse whether this normal lack of
requirement is applicable in this case (as it was for SNMP!)

Personally, I don't see binary encoding as a requirement, but that does
not necessarily mean it is not an option, just as text encoding is not a
requirement but is an option.

Given the use of ASN.1 and binary encoding in the only boundary
protocols, I don't think this option should be dismissed so lightly.

We are probably all familiar with the pros and cons of binary versus
text encoding, but how do those apply to our architecture?
Which of the two has more relevant benefits, and less relevant
negatives?

3. Do we have a preference for a legacy protocol or not?

Do we want something old, with all its embodied wisdom, and warts, or do
we want to start afresh?

If we want a legacy protocol, we could choose an ITU protocol if we also
want binary encoding. 

If we want a text based encoding in a legacy protocol, we can choose
SIP. (this would give us at least 4 preceding generations - SIP
(RFC-2543) son-of  HTTP (RFC-2068 ) son of  MIME (RFC -2045). son-of 
email RFC-822, which says
"This standard specifies a syntax for text messages that  are
     sent  among  computer  users",   

thats quite a lot of accumulated wisdom and warts. 

One of the legacies is that SIP still has the attribute of a compromise
between machine readability / and human readability. Perhaps we could
sacrifice the human readability a little to gain a more easily
implemented protocol which better maps to the requirement that the
protocol can support the type of structured information found in INAP
(and other) messages. (I assume this is an implied requirement from the
draft)

If we want a roll-our-own protocol (non legacy), then we can choose
binary or text. 

If we choose to roll our own binary (but I think not)
we could use ASN.1 to define it. 

If we choose to use a non-legacy text protocol maybe XML is a good
option. (although it could be argued even XML is legacy) 

My conclusions
--------------

XML may well be the best way to encode the structured data in the INAP
messages at the boundary of the architecture into a text based protocol
for use within the architecture. 

Given that there are standard, machine readable definition 'languages'
DTD for XML and ASN.1 for INAP et al, then automatic code generation of
the translator would offer many benefits.

There has been some work looking at encoding various ITU/T protocols
into SIP, but these merely put the ITU/T message into the body as a new
MIME type. This approach means that each element in the architecture
needs to support SIP as a transport protocol, then be able to decode the
embedded INAP message. If as builders of SPIRITS applications we have to
do that, would it not be easier to drop SIP and just decode the binary
ASN.1 encoded data? 

There are some unusual requirements and characteristics on the B interface 
which may make most commonly used tranport protocols unacceptable.

regards



Bruce


-------------------------------------------------------
Bruce Chapman, Software Systems Architect,
NEC New Zealand
LEVEL 6
CORNER TARANAKI AND MANNERS STREETS
WELLINGTON
PHONE: 64  4  381-6279
FAX:   64  4  381-1110
EMAIL: bchapman@wlg.nec.co.nz
--------------------------------------------------------

_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Mon Mar 26 04:22:02 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA16433
	for <spirits-archive@odin.ietf.org>; Mon, 26 Mar 2001 04:22:01 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id B8C6D44377; Mon, 26 Mar 2001 04:22:01 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from m2-pasarela3.airtel.es (unknown [212.73.32.197])
	by lists.bell-labs.com (Postfix) with ESMTP id 55D2E44336
	for <spirits@lists.bell-labs.com>; Mon, 26 Mar 2001 04:21:06 -0500 (EST)
Subject: Re: [SPIRITS] Some Thoughts On Protocol Requirements
To: spirits@lists.bell-labs.com
From: jgato@airtel.es
Message-ID: <OFAED55A66.54722476-ONC1256A1B.003232A8@airtel.es>
X-MIMETrack: Serialize by Router on M2-SMTP3/AIRTEL(Release 5.0.5 |September 22, 2000) at
 03/26/2001 11:21:06 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
Reply-To: spirits@lists.bell-labs.com
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Mon, 26 Mar 2001 11:20:59 +0200


Hi Bruce,

I think you have provided a clever set of comments/ideas. It is excellent
to have someone proposing a different protocol for SPIRITS. I think that It
is better to compare possibilities and not just follow what the rest of the
world is saying.

Your proposal to use XML is very interesting, and I agree it needs to be
considered a candidate protocol for SPIRITS. By the way, I understand that
you mean XML based on HTTP (since XML is just about contents and needs a
protocol) .. or do you mean XML using SIP?.

After a very quick thought (and not being a SIP expert), I think that the
use of XML would be preferrable if we decide to map a lot of INAP protocol
information into SPIRITS protocol (and not if the amount of information we
pass to SPIRITS is limited).

I tend to think that we will not need to copy many INAP parameters into
SPIRITS protocol, and SIP could be better, but I would need to think more
into it.

What does the rest of the list think about it?.

Best Regards,

Jorge Gato

P.D. By the way, did you send the proposal to use XML to transfer ISUP
messages using SIP (instead that using MIME) to the SIP group ?.




My conclusions
--------------

XML may well be the best way to encode the structured data in the INAP
messages at the boundary of the architecture into a text based protocol
for use within the architecture.

Given that there are standard, machine readable definition 'languages'
DTD for XML and ASN.1 for INAP et al, then automatic code generation of
the translator would offer many benefits.

There has been some work looking at encoding various ITU/T protocols
into SIP, but these merely put the ITU/T message into the body as a new
MIME type. This approach means that each element in the architecture
needs to support SIP as a transport protocol, then be able to decode the
embedded INAP message. If as builders of SPIRITS applications we have to
do that, would it not be easier to drop SIP and just decode the binary
ASN.1 encoded data?

There are some unusual requirements and characteristics on the B interface
which may make most commonly used tranport protocols unacceptable.

regards



Bruce


-------------------------------------------------------
Bruce Chapman, Software Systems Architect,
NEC New Zealand
LEVEL 6
CORNER TARANAKI AND MANNERS STREETS
WELLINGTON
PHONE: 64  4  381-6279
FAX:   64  4  381-1110
EMAIL: bchapman@wlg.nec.co.nz
--------------------------------------------------------

_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits




_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Mon Mar 26 09:59:03 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA01266
	for <spirits-archive@odin.ietf.org>; Mon, 26 Mar 2001 09:59:02 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 18DA944355; Mon, 26 Mar 2001 09:59:02 -0500 (EST)
Delivered-To: spirits@share.research.bell-labs.com
Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49])
	by lists.bell-labs.com (Postfix) with SMTP id 1F34844336
	for <spirits@share.research.bell-labs.com>; Mon, 26 Mar 2001 09:58:05 -0500 (EST)
Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Mon Mar 26 09:55:42 EST 2001
Received: by lists.bell-labs.com (Postfix)
	id BD9AE44380; Mon, 26 Mar 2001 09:44:34 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from ihgp0.ih.lucent.com (ihgp0.ih.lucent.com [135.1.53.24])
	by lists.bell-labs.com (Postfix) with ESMTP id 799584437D
	for <spirits@lists.bell-labs.com>; Mon, 26 Mar 2001 09:44:34 -0500 (EST)
Received: by ihgp0.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id IAA21441; Mon, 26 Mar 2001 08:44:33 -0600 (CST)
Received: from lucent.com by ihgp0.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id IAA21421; Mon, 26 Mar 2001 08:44:31 -0600 (CST)
Message-ID: <3ABF55CE.924A18AB@lucent.com>
From: "Kumar V. Vemuri" <vvkumar@lucent.com>
Reply-To: vvkumar@lucent.com
Organization: Bell Labs
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: spirits@lists.bell-labs.com
Subject: Re: [SPIRITS] Some Thoughts On Protocol Requirements
References: <OFAED55A66.54722476-ONC1256A1B.003232A8@airtel.es>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Mon, 26 Mar 2001 08:44:30 -0600
Content-Transfer-Encoding: 7bit

Bruce, Jorge,
 that was a very interesting discussion. Here are some thoughts
 on how we could proceed with the protocol work if we continued
 to pursue using SIP. As you very well know, use of SIP does
 not preclude the use of XML. Comments?
regards,
Kumar.
--
There seem to be at least four alternatives for addressing how 
the Spirits related information could be carried within the body 
of SIP messages. We need to agree on a particular technique after 
studying the various possibilities and their associated pros and 
cons. I'm not claiming these are THE only ways of doing this, 
just that these are some ideas for discussion.
--
 Alternatives:
1. Extend the traditional SDP as defined, to encode Spirits data 
   as well. This is (sort of) supported by the SDP draft. To 
   quote from RFC 2327 (The SDP Protocol):
   "Some lines in each description are required and some are 
    optional but all must appear in exactly the order given here 
    (the fixed order greatly enhances error detection and allows 
    for a simple parser). Optional items are marked with a `*'.

    Session description
        v=  (protocol version)
        o=  (owner/creator and session identifier).
        s=  (session name)
        i=* (session information)
        u=* (URI of description)
        e=* (email address)
        p=* (phone number)
        c=* (connection information - not required if included in 
              all media)
        b=* (bandwidth information)

         One or more time descriptions (see below)
         z=* (time zone adjustments)
         k=* (encryption key)
         a=* (zero or more session attribute lines)

         Zero or more media descriptions (see below)
         Time description
         t=  (time the session is active)
         r=* (zero or more repeat times)

         Media description
         m=  (media name and transport address)
         i=* (media title)
         c=* (connection information - optional if included at 
              session-level)
         b=* (bandwidth information)
         k=* (encryption key)
         a=* (zero or more media attribute lines)

   The set of `type' letters is deliberately small and not 
   intended to be extensible -- SDP parsers must completely 
   ignore any announcement that contains a `type' letter that it 
   does not understand. The 'attribute' mechanism ("a=" described 
   below) is the primary means for extending SDP and tailoring it 
   to particular applications or media. Some attributes (the ones 
   listed in this document) have a defined meaning but others may 
   be added on an application-, media- or session-specific basis. 
   A session directory must ignore any attribute it doesn't 
   understand.

   [...]
   
   Attributes

   a=<attribute>
   a=<attribute>:<value>

   Attributes are the primary means for extending SDP.  
   Attributes may be defined to be used as "session-level" 
   attributes, "media-level" attributes, or both.

   A media description may have any number of attributes
   ("a=" fields) which are media specific.  These are referred
   to as "media-level" attributes and add information about the 
   media stream.  Attribute fields can also be added before the 
   first media field; these "session-level" attributes convey 
   additional information that applies to the conference as a 
   whole rather than to individual media; an example might be 
   the conference's floor control policy. 

   Attribute fields may be of two forms:
   o property attributes.  A property attribute is simply of the 
     form "a=<flag>".  These are binary attributes, and the 
     presence of the attribute conveys that the attribute is a 
     property of the session.
     An example might be "a=recvonly".

   o value attributes.  A value attribute is of the form
     "a=<attribute>:<value>".  An example might be that a 
     whiteboard could have the value attribute 
     "a=orient:landscape"

   Attribute interpretation depends on the media tool being 
   invoked. Thus receivers of session descriptions should be 
   configurable in their interpretation of announcements in 
   general and of attributes in particular.

   Attribute names must be in the US-ASCII subset of 
   ISO-10646/UTF-8.

   Attribute values are byte strings, and MAY use any byte value 
   except 0x00 (Nul), 0x0A (LF), and 0x0D (CR). By default, 
   attribute values are to be interpreted as in ISO-10646 
   character set with UTF-8 encoding.  Unlike other text fields, 
   attribute values are NOT normally affected by the `charset' 
   attribute as this would make comparisons against known values 
   problematic.  However, when an attribute is defined, it can be 
   defined to be charset-dependent, in which case it's value 
   should be interpreted in the session charset rather than in 
   ISO-10646.

   Attributes that will be commonly used can be registered with 
   IANA (see Appendix B).  Unregistered attributes should begin 
   with "X-" to  prevent inadvertent collision with registered 
   attributes.  In either case, if an attribute is received that 
   is not understood, it should simply be ignored by the 
   receiver." (end excerpt).

   We can therefore embed the Spirits information that needs to 
   be conveyed using the "a" parameter in traditional SDP bodies,
   and proposing extensions to the attribute header set to carry
   the parameters of immediate interest to us.

2. develop a new "description protocol" called (say) the "Trigger 
   and Event Description Protocol" (TEDP), write a draft on it, 
   encode the Spirits level details into that, and set up the 
   attribute list with a set of letters for appropriate use in 
   identifying the contents of the message so that fast parsers 
   could be written.

    An example message would then look like:
      INVITE sip:schooler@vlsi.caltech.edu SIP/2.0
      v:SIP/2.0/UDP 131.215.131.131;maddr=239.128.16.254;ttl=16
      v:SIP/2.0/UDP 128.16.64.19
      f:sip:mjh@isi.edu
      t:sip:schooler@cs.caltech.edu
      i:62729-27@128.16.64.19
      c:application/tedp
      CSeq: 4711 INVITE
      l:187

      <tedp fields and body>

3. define an XML encoding with suitable DTD to encode the 
   information Spirits requires. Thus, one now has a 
   Spirits-specific format that is easily extensible and usable, 
   and has a standard means of sharing this information. Either 
   suitably extended CPL or a new XML DTD may be developed for 
   this. Note that the latter is probably preferable, since 
   standard CPL is unlikely to have existing support for the
   encoding of Spirits information. The message would have a "c" 
   field (see above for reference) that would look like: 
   "c:application/xml" if we have a specific type of XML for 
   this purpose (TEXML?) then if there is a registered 
   non-binary MIME type registered for this, the MIME encoding 
   may be done as "MIME subtype name: texml+xml". 
   Please see CPL draft for this.

4. follow the ISUP encoding techiques as in SIP-T, and support 
   the encapsulation of binary encoded INAP message data into the 
   SIP message body. This way, the Spirits client does not need 
   to do much of a parsing function. Can define a new MIME type 
   to do this:
   (adapted from the ISUP and QSIG MIME proposal draft)
      "Media type name: application
       Media subtype name: SPIRITS
       Required parameters: version
       Optional parameters: base
       Encoding scheme: binary
       Security considerations: ..."
--

_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Mon Mar 26 10:50:03 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA09957
	for <spirits-archive@odin.ietf.org>; Mon, 26 Mar 2001 10:50:03 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 87F2744353; Mon, 26 Mar 2001 10:50:02 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from cundall.co.uk (dorfl.roke.co.uk [193.118.192.45])
	by lists.bell-labs.com (Postfix) with SMTP id BB7A544336
	for <spirits@lists.bell-labs.com>; Mon, 26 Mar 2001 10:49:45 -0500 (EST)
Received: from [193.118.192.55] ([193.118.192.55] verified) by cundall.co.uk (Stalker SMTP Server 1.7) with ESMTP id S.0000052901 for <spirits@lists.bell-labs.com>; Mon, 26 Mar 2001 16:49:40 +0000
Mime-Version: 1.0
X-Sender: lwc@derek.roke.co.uk
Message-Id: <p05010400b6e50ec38049@[193.118.192.55]>
In-Reply-To: <3ABF55CE.924A18AB@lucent.com>
References: <OFAED55A66.54722476-ONC1256A1B.003232A8@airtel.es>
 <3ABF55CE.924A18AB@lucent.com>
To: spirits@lists.bell-labs.com
From: Lawrence Conroy <lwc@roke.co.uk>
Subject: Re: [SPIRITS] Some Thoughts On Protocol Requirements
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
Reply-To: spirits@lists.bell-labs.com
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Mon, 26 Mar 2001 16:50:27 +0100

Hi fellow SPIRITualists,

I believe that Bruce has given a good argument for the use of SIP.
...............................................^^^

Bruce mentions the need for protection, plus the need for a large number
of long lived but low data rate sessions. AFAIK, SIP copes with these
requirements; calls are quite long lived, and there had better be a lot
of them (or we're all out of business :). SIP runs over UDP so that we
don't have the problem that HTTP/HTTPS servers have with limits to the
number of concurrent sessions.

We based PINT on SIP - it works for us, so you may need to give some
details on why it doesn't work for SPIRITS.

PINT messages traverse existing SIP (and 3GPP CSCF) proxies.
I was particularly happy that we didn't have to re-invent a
worldwide infrastructure.

I'm intrigued by the comment that:
>  "These sessions need to have the characteristic that the Gateway can
>  determine if the session is still active.

Perhaps an expansion would be useful?
-- 
lwc@roke.co.uk: +44 1794 833666::<my opinions>:

_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Mon Mar 26 17:19:02 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA19005
	for <spirits-archive@odin.ietf.org>; Mon, 26 Mar 2001 17:19:01 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 2A41C443A4; Mon, 26 Mar 2001 17:19:02 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from mailhub.wlg.nec.co.nz (nzls21.wlg.nec.co.nz [202.37.54.144])
	by lists.bell-labs.com (Postfix) with ESMTP id 719C6443A3
	for <spirits@lists.bell-labs.com>; Mon, 26 Mar 2001 17:18:03 -0500 (EST)
Received: from mailhost.wlg.nec.co.nz (nzlu02.wlg.nec.co.nz [202.37.54.14])
	by mailhub.wlg.nec.co.nz (8.9.1/8.9.1) with ESMTP id KAA13466
	for <spirits@lists.bell-labs.com>; Tue, 27 Mar 2001 10:38:42 +1200 (NZST)
Received: from nzls54.wlg.nec.co.nz by mailhost.wlg.nec.co.nz (8.8.8+Sun/SMI-SVR4)
	id KAA21684; Tue, 27 Mar 2001 10:15:34 +1200 (NZST)
Received: (from bchapman@localhost)
	by nzls54.wlg.nec.co.nz (8.8.8+Sun/8.8.8) id KAA17146
	for spirits@lists.bell-labs.com; Tue, 27 Mar 2001 10:20:24 +1200 (NZST)
From: Bruce Chapman <bchapman@wlg.nec.co.nz>
Message-Id: <200103262220.KAA17146@nzls54.wlg.nec.co.nz>
To: spirits@lists.bell-labs.com
Subject: Re: [SPIRITS] Some Thoughts On Protocol Requirements
X-Sun-Charset: US-ASCII
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
Reply-To: spirits@lists.bell-labs.com
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Tue, 27 Mar 2001 10:20:24 +1200 (NZST)

Good Morning all,


Some replies to Jorge, Kumar and Lawrence,


Jorge wrote
-----------

> Your proposal to use XML is very interesting, and I agree it needs to be
> considered a candidate protocol for SPIRITS. By the way, I understand that
> you mean XML based on HTTP (since XML is just about contents and needs a
> protocol) .. or do you mean XML using SIP?.

The suggestion of using XML was at the presentation layer, rather than the 
transport layer. (but if we use SIP the two get very blurred since it does both),
maybe it would be XML over TCP/IP but that collides with the B interface requirements. 
(we are implementing B using a reliable layer over WTLS). The B interface is a 
problem here because the initial pointers are toward a secure reliable packet transport
layer. TLS/SSL without the 64K ports limit. WTLS maps quite well to these requirements.

> After a very quick thought (and not being a SIP expert), I think that the
> use of XML would be preferrable if we decide to map a lot of INAP protocol
> information into SPIRITS protocol (and not if the amount of information we
>pass to SPIRITS is limited).

If we pass a limited amount of INAP data into the SPIRITS protocol we potentially limit
the possibilities for new services. That is, for each item we omit, we may later find that
it would have been useful to have had it for some service. We probably don't need to 
include everything, 

but if we do a good job on SPIRITS then it should be possible to include everything. 
Think of this as foreshadowed extensions. In the case of INAP/XML, then the SPIRITS protocol 
would say how we map the data back and forth, and which data was mandatory. Anyone extending 
SPIRITS to use additional parameters would do so in exactly the same way as someone else wanting the same parameter. Although this does not guarantee interoperability per se, it goes most of the way. 

> P.D. By the way, did you send the proposal to use XML to transfer ISUP
> messages using SIP (instead that using MIME) to the SIP group ?.

No, 

But ISUP encoded by XML in SIP would still be MIME, it would just be a new MIME type in the SIP body. The difference is that the SIP proposals for ISUP puts the bare binary ISUP as a MIME type.


Kumar wrote
----------

> Alternatives:
> 1. Extend the traditional SDP as defined, to encode Spirits data 
>   as well. This is (sort of) supported by the SDP draft. To 
 

This is, I think, the only thing I have a very strong view on. 
SPIRITS should not extend SDP. in a word it would be UGLY. I am 
not convinced about using SIP, but if that is the choice, the 
SPIRITS information can be carried in one (or both) of two ways. 
Either as a (probably new) MIME type in the body of the SIP message, 
and/or using the extension mechanisms defined in SIP such as  
other-param(s) in a SIP URL  (see RFC-2543 section 2).


Lawrence wrote
--------------

> I'm intrigued by the comment that:
> >  "These sessions need to have the characteristic that the Gateway can
> >  determine if the session is still active.
>
> Perhaps an expansion would be useful?

The spirits servers will in many cases be running over a dial up 
connection to an ISP (the whole reason for the ICW service), and 
will have dynamically allocated IP addresses. 

This means that any requirement for the SPIRITS server to close 
the (real or virtual) session, either by deregistering or whatever, 
before the server closes down, is completely unreasonable. Servers 
WILL just disappear (not just occassionally but in fact in most cases).
We can't do anything about that, we must design for it.

The SPIRITS protocol must be robust against the following scenario:

	A server starts a 'session' with the gateway, 
	then the dial up connection through which  the server is connnected 
	to the internet is broken. 
	Another ISP customer then is allocated that same IP address, 
	This new machine (same IP address) starts a SPIRITS server running.
	The gateway must not confuse this new 'session' with the old one.

Also, to manage resources effectively at the gateway, we need to know 
when a server is no longer available so that those resources can be 
released, and we cannot rely on the server telling the gateway when it 
is about to become unavailable. Remember a gateway may have in the order 
of tens of thousands (or more) servers with active 'sessions' at any one time.



regards


Bruce


_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Wed Mar 28 12:02:37 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA04966
	for <spirits-archive@odin.ietf.org>; Wed, 28 Mar 2001 12:02:31 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 5EAB444369; Wed, 28 Mar 2001 12:01:04 -0500 (EST)
Delivered-To: spirits@share.research.bell-labs.com
Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49])
	by lists.bell-labs.com (Postfix) with SMTP id 9E69F44336
	for <spirits@share.research.bell-labs.com>; Wed, 28 Mar 2001 12:00:03 -0500 (EST)
Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Wed Mar 28 11:56:50 EST 2001
Received: by lists.bell-labs.com (Postfix)
	id 17AB044380; Wed, 28 Mar 2001 11:45:42 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from ihgp0.ih.lucent.com (ihgp0.ih.lucent.com [135.1.53.24])
	by lists.bell-labs.com (Postfix) with ESMTP id CA06A4437D
	for <spirits@lists.bell-labs.com>; Wed, 28 Mar 2001 11:45:41 -0500 (EST)
Received: by ihgp0.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id KAA19119; Wed, 28 Mar 2001 10:45:40 -0600 (CST)
Received: from lucent.com by ihgp0.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id KAA18868; Wed, 28 Mar 2001 10:45:38 -0600 (CST)
Message-ID: <3AC21531.E02E3DDF@lucent.com>
From: "Kumar V. Vemuri" <vvkumar@lucent.com>
Reply-To: vvkumar@lucent.com
Organization: Bell Labs
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: spirits@lists.bell-labs.com
Subject: Re: [SPIRITS] Some Thoughts On Protocol Requirements
References: <200103262220.KAA17146@nzls54.wlg.nec.co.nz>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Wed, 28 Mar 2001 10:45:37 -0600
Content-Transfer-Encoding: 7bit

Bruce, I must say I agree with you that "Alternative 1" I listed
  in my email is UGLY. IMHO, it is important and interesting
  to consider all alternatives that occur to us, and capture
  the reasoning for or against, so that we may build concensus
  on the mailing list.

  Please elaborate on the use of SIP URIs to transport this
  information. An example would help me understand this better.
  Are you suggesting adding support for new params in the
  "sip:<name>;..." structure? Seems interesting. Alternative 5.
  Any others occur to anyone? Does SIP with an XML body seem the 
  most favorable option?
regards,
Kumar.
--
Bruce Chapman wrote:
> Good Morning all,
> Some replies to Jorge, Kumar and Lawrence,
> --
> Jorge wrote:
>> Your proposal to use XML is very interesting, and I agree it 
>> needs to be considered a candidate protocol for SPIRITS. By 
>> the way, I understand that you mean XML based on HTTP (since 
>> XML is just about contents and needs a protocol) .. or do you 
>> mean XML using SIP?.
> 
> The suggestion of using XML was at the presentation layer, 
> rather than the transport layer. (but if we use SIP the two get 
> very blurred since it does both), maybe it would be XML over 
> TCP/IP but that collides with the B interface requirements. 
> (we are implementing B using a reliable layer over WTLS). The
> B interface is a problem here because the initial pointers are 
> toward a secure reliable packet transport layer. TLS/SSL 
> without the 64K ports limit. WTLS maps quite well to these 
> requirements.

<snip>

> Kumar wrote:
>> Alternatives:
>> 1. Extend the traditional SDP as defined, to encode Spirits 
>>   data as well. This is (sort of) supported by the SDP draft. 
>> 
> This is, I think, the only thing I have a very strong view on.
> SPIRITS should not extend SDP. in a word it would be UGLY. I am
> not convinced about using SIP, but if that is the choice, the
> SPIRITS information can be carried in one (or both) of two 
> ways. Either as a (probably new) MIME type in the body of the 
> SIP message, and/or using the extension mechanisms defined in 
> SIP such as other-param(s) in a SIP URL (see RFC-2543 
> section 2).
[...] 
> regards
> Bruce

_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Wed Mar 28 12:41:03 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA05926
	for <spirits-archive@odin.ietf.org>; Wed, 28 Mar 2001 12:41:02 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id A20C94433F; Wed, 28 Mar 2001 12:41:01 -0500 (EST)
Delivered-To: spirits@share.research.bell-labs.com
Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49])
	by lists.bell-labs.com (Postfix) with SMTP id D6FE644336
	for <spirits@share.research.bell-labs.com>; Wed, 28 Mar 2001 12:40:06 -0500 (EST)
Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Wed Mar 28 12:37:10 EST 2001
Received: by lists.bell-labs.com (Postfix)
	id 2CC4F44380; Wed, 28 Mar 2001 12:26:05 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from ans.ih.lucent.com (ans.ih.lucent.com [135.1.218.156])
	by lists.bell-labs.com (Postfix) with SMTP id E461F4437D
	for <spirits@lists.bell-labs.com>; Wed, 28 Mar 2001 12:26:04 -0500 (EST)
Received: by ans.ih.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id LAA24570; Wed, 28 Mar 2001 11:26:01 -0600
Received: from lucent.com by ans.ih.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id LAA24566; Wed, 28 Mar 2001 11:26:00 -0600
Message-ID: <3AC21F27.7B0CF42@lucent.com>
From: Alec Brusilovsky <abrusilovsky@lucent.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en,ru,uk
MIME-Version: 1.0
To: spirits@lists.bell-labs.com
Subject: Re: [SPIRITS] Some Thoughts On Protocol Requirements
References: <200103262220.KAA17146@nzls54.wlg.nec.co.nz> <3AC21531.E02E3DDF@lucent.com>
Content-Type: multipart/mixed;
 boundary="------------091E10C6553CF1EA20D9758B"
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
Reply-To: spirits@lists.bell-labs.com
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Wed, 28 Mar 2001 11:28:07 -0600

This is a multi-part message in MIME format.
--------------091E10C6553CF1EA20D9758B
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit

Bruce, Jorge, Kumar and Lawrence,

Thanks for starting a good and much needed discussion!
Obviously, we cannot complete SPIRITS protocol without specifying the
exact way to transport SPIRITS parameters.

Let me do (maybe preliminary) summary of this discussion:
1. There is definite drive towards utilizing XML ("XML may well be
the best way to encode the structured data in
the INAP messages at the boundary of the architecture into a text
based protocol for use within the architecture" - JG; "define an XML
encoding with suitable DTD to encode the information Spirits
requires." - KV);

2. SIP seems to be a "natural" transport vehicle for SPIRITS
parameters ("We based PINT on SIP - it works for
us, so you may need to give some details on why it doesn't work for
SPIRITS. . . we didn't have to re-invent a
worldwide infrastructure" - LC).

I, personally, think that there is a way to use both of these
approaches (i.e. XML encoded parameters transported over SIP).

Regards,
Alec

"Kumar V. Vemuri" wrote:

> Bruce, I must say I agree with you that "Alternative 1" I listed
>   in my email is UGLY. IMHO, it is important and interesting
>   to consider all alternatives that occur to us, and capture
>   the reasoning for or against, so that we may build concensus
>   on the mailing list.
>
>   Please elaborate on the use of SIP URIs to transport this
>   information. An example would help me understand this better.
>   Are you suggesting adding support for new params in the
>   "sip:<name>;..." structure? Seems interesting. Alternative 5.
>   Any others occur to anyone? Does SIP with an XML body seem the
>   most favorable option?
> regards,
> Kumar.
> --
> Bruce Chapman wrote:
> > Good Morning all,
> > Some replies to Jorge, Kumar and Lawrence,
> > --
> > Jorge wrote:
> >> Your proposal to use XML is very interesting, and I agree it
> >> needs to be considered a candidate protocol for SPIRITS. By
> >> the way, I understand that you mean XML based on HTTP (since
> >> XML is just about contents and needs a protocol) .. or do you
> >> mean XML using SIP?.
> >
> > The suggestion of using XML was at the presentation layer,
> > rather than the transport layer. (but if we use SIP the two get
> > very blurred since it does both), maybe it would be XML over
> > TCP/IP but that collides with the B interface requirements.
> > (we are implementing B using a reliable layer over WTLS). The
> > B interface is a problem here because the initial pointers are
> > toward a secure reliable packet transport layer. TLS/SSL
> > without the 64K ports limit. WTLS maps quite well to these
> > requirements.
>
> <snip>
>
> > Kumar wrote:
> >> Alternatives:
> >> 1. Extend the traditional SDP as defined, to encode Spirits
> >>   data as well. This is (sort of) supported by the SDP draft.
> >>
> > This is, I think, the only thing I have a very strong view on.
> > SPIRITS should not extend SDP. in a word it would be UGLY. I am
> > not convinced about using SIP, but if that is the choice, the
> > SPIRITS information can be carried in one (or both) of two
> > ways. Either as a (probably new) MIME type in the body of the
> > SIP message, and/or using the extension mechanisms defined in
> > SIP such as other-param(s) in a SIP URL (see RFC-2543
> > section 2).
> [...]
> > regards
> > Bruce
>
> _______________________________________________
> SPIRITS mailing list
> SPIRITS@lists.bell-labs.com
> http://lists.bell-labs.com/mailman/listinfo/spirits

--------------091E10C6553CF1EA20D9758B
Content-Type: text/x-vcard; charset=koi8-r;
 name="abrusilovsky.vcf"
Content-Description: Card for Alec Brusilovsky
Content-Disposition: attachment;
 filename="abrusilovsky.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Brusilovsky;Alec 
tel;fax:+1 630 713 5840 
tel;work:+1 630 713 8401
x-mozilla-html:FALSE
org:e-Services Group;Next Generation Evolution and Architecture
version:2.1
email;internet:abrusilovsky@lucent.com
title:MTS 
adr;quoted-printable:;;IHP 1A-423=0D=0A263 Shuman Blvd,P O Box 3050;Naperville;IL;60566-7050;U S
x-mozilla-cpt:;5312
fn:Alec  Brusilovsky
end:vcard

--------------091E10C6553CF1EA20D9758B--


_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Wed Mar 28 13:36:02 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA07139
	for <spirits-archive@odin.ietf.org>; Wed, 28 Mar 2001 13:36:01 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 3E15A44355; Wed, 28 Mar 2001 13:36:01 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from www.mobilerain.com (sdsl-208-185-234-252.dsl.sjc.megapath.net [208.185.234.252])
	by lists.bell-labs.com (Postfix) with ESMTP id 387CF4433F
	for <spirits@lists.bell-labs.com>; Wed, 28 Mar 2001 13:35:50 -0500 (EST)
Received: from mobilerain.com (IDENT:dsardana@[192.168.1.102])
	by www.mobilerain.com (8.9.3/8.9.3) with ESMTP id LAA13549
	for <spirits@lists.bell-labs.com>; Wed, 28 Mar 2001 11:32:42 -0800
Message-ID: <3AC23DA2.63AC9606@mobilerain.com>
From: Bobby Sardana <bobby.sardana@mobilerain.com>
Organization: MobileRAIN Technologies, Inc.
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: spirits@lists.bell-labs.com
Subject: Re: [SPIRITS] Some Thoughts On Protocol Requirements
References: <200103262220.KAA17146@nzls54.wlg.nec.co.nz> <3AC21531.E02E3DDF@lucent.com> <3AC21F27.7B0CF42@lucent.com>
Content-Type: multipart/mixed;
 boundary="------------CEB5C46806AA475E28539532"
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
Reply-To: spirits@lists.bell-labs.com
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Wed, 28 Mar 2001 11:38:10 -0800

This is a multi-part message in MIME format.
--------------CEB5C46806AA475E28539532
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings:

A popular transport for XML documents is HTTP.  Has any thought being
given to use HTTP?

Regards,

Bobby.Sardana@mobilerain.com

Alec Brusilovsky wrote:

> Bruce, Jorge, Kumar and Lawrence,
>
> Thanks for starting a good and much needed discussion!
> Obviously, we cannot complete SPIRITS protocol without specifying the
> exact way to transport SPIRITS parameters.
>
> Let me do (maybe preliminary) summary of this discussion:
> 1. There is definite drive towards utilizing XML ("XML may well be
> the best way to encode the structured data in
> the INAP messages at the boundary of the architecture into a text
> based protocol for use within the architecture" - JG; "define an XML
> encoding with suitable DTD to encode the information Spirits
> requires." - KV);
>
> 2. SIP seems to be a "natural" transport vehicle for SPIRITS
> parameters ("We based PINT on SIP - it works for
> us, so you may need to give some details on why it doesn't work for
> SPIRITS. . . we didn't have to re-invent a
> worldwide infrastructure" - LC).
>
> I, personally, think that there is a way to use both of these
> approaches (i.e. XML encoded parameters transported over SIP).
>
> Regards,
> Alec
>
> "Kumar V. Vemuri" wrote:
>
> > Bruce, I must say I agree with you that "Alternative 1" I listed
> >   in my email is UGLY. IMHO, it is important and interesting
> >   to consider all alternatives that occur to us, and capture
> >   the reasoning for or against, so that we may build concensus
> >   on the mailing list.
> >
> >   Please elaborate on the use of SIP URIs to transport this
> >   information. An example would help me understand this better.
> >   Are you suggesting adding support for new params in the
> >   "sip:<name>;..." structure? Seems interesting. Alternative 5.
> >   Any others occur to anyone? Does SIP with an XML body seem the
> >   most favorable option?
> > regards,
> > Kumar.
> > --
> > Bruce Chapman wrote:
> > > Good Morning all,
> > > Some replies to Jorge, Kumar and Lawrence,
> > > --
> > > Jorge wrote:
> > >> Your proposal to use XML is very interesting, and I agree it
> > >> needs to be considered a candidate protocol for SPIRITS. By
> > >> the way, I understand that you mean XML based on HTTP (since
> > >> XML is just about contents and needs a protocol) .. or do you
> > >> mean XML using SIP?.
> > >
> > > The suggestion of using XML was at the presentation layer,
> > > rather than the transport layer. (but if we use SIP the two get
> > > very blurred since it does both), maybe it would be XML over
> > > TCP/IP but that collides with the B interface requirements.
> > > (we are implementing B using a reliable layer over WTLS). The
> > > B interface is a problem here because the initial pointers are
> > > toward a secure reliable packet transport layer. TLS/SSL
> > > without the 64K ports limit. WTLS maps quite well to these
> > > requirements.
> >
> > <snip>
> >
> > > Kumar wrote:
> > >> Alternatives:
> > >> 1. Extend the traditional SDP as defined, to encode Spirits
> > >>   data as well. This is (sort of) supported by the SDP draft.
> > >>
> > > This is, I think, the only thing I have a very strong view on.
> > > SPIRITS should not extend SDP. in a word it would be UGLY. I am
> > > not convinced about using SIP, but if that is the choice, the
> > > SPIRITS information can be carried in one (or both) of two
> > > ways. Either as a (probably new) MIME type in the body of the
> > > SIP message, and/or using the extension mechanisms defined in
> > > SIP such as other-param(s) in a SIP URL (see RFC-2543
> > > section 2).
> > [...]
> > > regards
> > > Bruce
> >
> > _______________________________________________
> > SPIRITS mailing list
> > SPIRITS@lists.bell-labs.com
> > http://lists.bell-labs.com/mailman/listinfo/spirits

--------------CEB5C46806AA475E28539532
Content-Type: text/x-vcard; charset=us-ascii;
 name="bobby.sardana.vcf"
Content-Description: Card for Bobby Sardana
Content-Disposition: attachment;
 filename="bobby.sardana.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Sardana;Bobby
x-mozilla-html:FALSE
org:MobileRAIN Technologies, Inc.;R & D
adr:;;;;;;
version:2.1
email;internet:bobby.sardana@mobilerain.com
title:Engineer
x-mozilla-cpt:;0
fn:Bobby Sardana
end:vcard

--------------CEB5C46806AA475E28539532--


_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Wed Mar 28 16:55:02 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA13175
	for <spirits-archive@odin.ietf.org>; Wed, 28 Mar 2001 16:55:01 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 4532F44341; Wed, 28 Mar 2001 16:55:02 -0500 (EST)
Delivered-To: spirits@share.research.bell-labs.com
Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49])
	by lists.bell-labs.com (Postfix) with SMTP id 00BF544336
	for <spirits@share.research.bell-labs.com>; Wed, 28 Mar 2001 16:54:06 -0500 (EST)
Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Wed Mar 28 16:51:04 EST 2001
Received: by lists.bell-labs.com (Postfix)
	id CF90644380; Wed, 28 Mar 2001 16:39:58 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from ihgp0.ih.lucent.com (ihgp0.ih.lucent.com [135.1.53.24])
	by lists.bell-labs.com (Postfix) with ESMTP id 812554437D
	for <spirits@lists.bell-labs.com>; Wed, 28 Mar 2001 16:39:58 -0500 (EST)
Received: by ihgp0.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id PAA23765; Wed, 28 Mar 2001 15:39:40 -0600 (CST)
Received: from lucent.com by ihgp0.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id PAA23711; Wed, 28 Mar 2001 15:39:38 -0600 (CST)
Message-ID: <3AC25A16.DB9EE69E@lucent.com>
From: "Kumar V. Vemuri" <vvkumar@lucent.com>
Reply-To: vvkumar@lucent.com
Organization: Bell Labs
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: spirits@lists.bell-labs.com
Subject: Re: [SPIRITS] Some Thoughts On Protocol Requirements
References: <200103262220.KAA17146@nzls54.wlg.nec.co.nz> <3AC21531.E02E3DDF@lucent.com> <3AC21F27.7B0CF42@lucent.com> <3AC23DA2.63AC9606@mobilerain.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Wed, 28 Mar 2001 15:39:34 -0600
Content-Transfer-Encoding: 7bit

Bobby, 
  IMHO, the question becomes one of whether or not one needs
 the use of SIP semantics in addition to the meaning conveyed
 by the XML content in the body.

 One way we could make use of that semantic content is where
 we use the INVITE, or SUBSCRIBE and NOTIFY primitives from 
 SIP to register interest in specific events, and request 
 notifications when they occur.

 Is there an analogous mechanism in HTTP to accomplish similar
 goals?
regards,
Kumar.
--
Bobby Sardana wrote:
> Greetings:
> A popular transport for XML documents is HTTP.  Has any 
> thought being given to use HTTP?
> Regards,
> Bobby.Sardana@mobilerain.com

_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Wed Mar 28 18:11:02 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA14619
	for <spirits-archive@odin.ietf.org>; Wed, 28 Mar 2001 18:11:01 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 956F344361; Wed, 28 Mar 2001 18:11:01 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from www.mobilerain.com (sdsl-208-185-234-252.dsl.sjc.megapath.net [208.185.234.252])
	by lists.bell-labs.com (Postfix) with ESMTP id D33FE44336
	for <spirits@lists.bell-labs.com>; Wed, 28 Mar 2001 18:10:40 -0500 (EST)
Received: from mobilerain.com (IDENT:dsardana@[192.168.1.102])
	by www.mobilerain.com (8.9.3/8.9.3) with ESMTP id QAA17309;
	Wed, 28 Mar 2001 16:07:40 -0800
Message-ID: <3AC27E14.F1261784@mobilerain.com>
From: Bobby Sardana <bobby.sardana@mobilerain.com>
Organization: MobileRAIN Technologies, Inc.
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: vvkumar@lucent.com
Cc: spirits@lists.bell-labs.com
Subject: Re: [SPIRITS] Some Thoughts On Protocol Requirements
References: <200103262220.KAA17146@nzls54.wlg.nec.co.nz> <3AC21531.E02E3DDF@lucent.com> <3AC21F27.7B0CF42@lucent.com> <3AC23DA2.63AC9606@mobilerain.com> <3AC25A16.DB9EE69E@lucent.com>
Content-Type: multipart/mixed;
 boundary="------------9CB483F108601BFFBDF93523"
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
Reply-To: spirits@lists.bell-labs.com
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Wed, 28 Mar 2001 16:13:08 -0800

This is a multi-part message in MIME format.
--------------9CB483F108601BFFBDF93523
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings:

Comments inline!

"Kumar V. Vemuri" wrote:

> Bobby,
>   IMHO, the question becomes one of whether or not one needs
>  the use of SIP semantics in addition to the meaning conveyed
>  by the XML content in the body.
>
>  One way we could make use of that semantic content is where
>  we use the INVITE, or SUBSCRIBE and NOTIFY primitives from
>  SIP to register interest in specific events, and request
>  notifications when they occur.

INVITE, SUBSCRIBE, NOTIFY have been defined for certain specific
purposes. Trying to convey a different behavior
for a simplistic operation like XML document exchange is an overkill
(MHO). HTTP on the other hand is being used
for much complicated XML document exchange(s). Look or study any BtoB --
any exchange, and that will outline the
benefits.

Several issues, for which many proposals exist for SIP, regarding
firewall traversal, TLS, have already been solved and matured
with regards to HTTP.

>
>
>  Is there an analogous mechanism in HTTP to accomplish similar
>  goals?

Yes. I would recommend an analysis of PUSH framework of WAP to
understand how asynchronous events can be managed and
executed using HTTP.

Regards,

Bobby.Sardana@mobilerain.com

>
> regards,
> Kumar.
> --
> Bobby Sardana wrote:
> > Greetings:
> > A popular transport for XML documents is HTTP.  Has any
> > thought being given to use HTTP?
> > Regards,
> > Bobby.Sardana@mobilerain.com
>
> _______________________________________________
> SPIRITS mailing list
> SPIRITS@lists.bell-labs.com
> http://lists.bell-labs.com/mailman/listinfo/spirits

--------------9CB483F108601BFFBDF93523
Content-Type: text/x-vcard; charset=us-ascii;
 name="bobby.sardana.vcf"
Content-Description: Card for Bobby Sardana
Content-Disposition: attachment;
 filename="bobby.sardana.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Sardana;Bobby
x-mozilla-html:FALSE
org:MobileRAIN Technologies, Inc.;R & D
adr:;;;;;;
version:2.1
email;internet:bobby.sardana@mobilerain.com
title:Engineer
x-mozilla-cpt:;0
fn:Bobby Sardana
end:vcard

--------------9CB483F108601BFFBDF93523--


_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Thu Mar 29 00:46:04 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA01725
	for <spirits-archive@odin.ietf.org>; Thu, 29 Mar 2001 00:46:04 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 9B3094434E; Thu, 29 Mar 2001 00:46:01 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from mailhub.wlg.nec.co.nz (nzls21.wlg.nec.co.nz [202.37.54.144])
	by lists.bell-labs.com (Postfix) with ESMTP id C294844349
	for <spirits@lists.bell-labs.com>; Thu, 29 Mar 2001 00:44:59 -0500 (EST)
Received: from mailhost.wlg.nec.co.nz (nzlu02.wlg.nec.co.nz [202.37.54.14])
	by mailhub.wlg.nec.co.nz (8.9.1/8.9.1) with ESMTP id SAA23237
	for <spirits@lists.bell-labs.com>; Thu, 29 Mar 2001 18:05:44 +1200 (NZST)
Received: from nzls54.wlg.nec.co.nz by mailhost.wlg.nec.co.nz (8.8.8+Sun/SMI-SVR4)
	id RAA24047; Thu, 29 Mar 2001 17:42:16 +1200 (NZST)
Received: (from bchapman@localhost)
	by nzls54.wlg.nec.co.nz (8.8.8+Sun/8.8.8) id RAA19129
	for spirits@lists.bell-labs.com; Thu, 29 Mar 2001 17:47:13 +1200 (NZST)
From: Bruce Chapman <bchapman@wlg.nec.co.nz>
Message-Id: <200103290547.RAA19129@nzls54.wlg.nec.co.nz>
To: spirits@lists.bell-labs.com
Subject: Re: [SPIRITS] Some Thoughts On Protocol Requirements
X-Sun-Charset: US-ASCII
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
Reply-To: spirits@lists.bell-labs.com
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Thu, 29 Mar 2001 17:47:13 +1200 (NZST)

Alec summarized ...

> 2. SIP seems to be a "natural" transport vehicle for SPIRITS
> parameters ("We based PINT on SIP - it works for
> us, so you may need to give some details on why it doesn't work for
> SPIRITS. . . we didn't have to re-invent a
> worldwide infrastructure" - LC).
> 

As pointed out in my earlier emails, the B interface has some unusual characteristics. 

I dont think we can just assume therefore that because SIP worked for PINT, it will work for SPIRITS where (for ICW service at least) the thousands of SERVERs are vagrants. (my term, it has no fixed abode, it may be old fashioned, it is possibly antisocial, it is certainly unmanaged, it probably won't have trusted relationship with anything (crytographically speaking) (unless we build one), its platforms may have worn thin, you don't know its whereabouts, and it may just disappear without warning)


This doesn't mean that SIP wont work, it just means that we need to explore all the implications of having many vagrant SERVERs, and factor this into our choice of transport protocol.



Someone convince me please.


regards


Bruce

-------------------------------------------------------
Bruce Chapman, Software Systems Architect,
NEC New Zealand
LEVEL 6
CORNER TARANAKI AND MANNERS STREETS
WELLINGTON
PHONE: 64  4  381-6279
FAX:   64  4  381-1110
EMAIL: bchapman@wlg.nec.co.nz
--------------------------------------------------------

_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Thu Mar 29 14:11:58 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA04789
	for <spirits-archive@odin.ietf.org>; Thu, 29 Mar 2001 14:11:57 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 6D6CB44365; Thu, 29 Mar 2001 14:10:07 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69])
	by lists.bell-labs.com (Postfix) with ESMTP id 36E7F44336
	for <spirits@lists.bell-labs.com>; Thu, 29 Mar 2001 14:09:45 -0500 (EST)
Received: from njb140r1.ems.att.com ([135.65.202.58])
	by kcmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id f2TJ9d711385;
	Thu, 29 Mar 2001 14:09:40 -0500 (EST)
Received: from njb140bh1.ems.att.com by njb140r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2)
	id OAA24788; Thu, 29 Mar 2001 14:08:30 -0500 (EST)
Received: by njb140bh1.ems.att.com with Internet Mail Service (5.5.2653.19)
	id <H78VALDP>; Thu, 29 Mar 2001 14:09:38 -0500
Message-ID: <E5B80B001D76D211879C00E02910776108672A4B@njc240po05.mt.att.com>
From: "Roy, Radhika R, ALCOO" <rrroy@att.com>
To: spirits@lists.bell-labs.com
Cc: ndeason@ubiquity.net
Subject: RE: [SPIRITS] Some Thoughts On Protocol Requirements
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C0B85C.4F765130"
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
Reply-To: spirits@lists.bell-labs.com
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Thu, 29 Mar 2001 09:26:57 -0500

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C0B85C.4F765130
Content-Type: text/plain;
	charset="iso-8859-1"

Folks:

It might be interesting to see the enclosed draft.

Radhika R. Roy

Technology Consultant
AT&T
Room 3D-2C09
200 S. Laurel Avenue
Middletown, NJ 07748
+1 732 420 1580
rrroy@att.com

-----Original Message-----
From: Bruce Chapman [mailto:bchapman@wlg.nec.co.nz]
Sent: Thursday, March 29, 2001 12:47 AM
To: spirits@lists.bell-labs.com
Subject: Re: [SPIRITS] Some Thoughts On Protocol Requirements


Alec summarized ...

> 2. SIP seems to be a "natural" transport vehicle for SPIRITS
> parameters ("We based PINT on SIP - it works for
> us, so you may need to give some details on why it doesn't work for
> SPIRITS. . . we didn't have to re-invent a
> worldwide infrastructure" - LC).
> 

As pointed out in my earlier emails, the B interface has some unusual
characteristics. 

I dont think we can just assume therefore that because SIP worked for PINT,
it will work for SPIRITS where (for ICW service at least) the thousands of
SERVERs are vagrants. (my term, it has no fixed abode, it may be old
fashioned, it is possibly antisocial, it is certainly unmanaged, it probably
won't have trusted relationship with anything (crytographically speaking)
(unless we build one), its platforms may have worn thin, you don't know its
whereabouts, and it may just disappear without warning)


This doesn't mean that SIP wont work, it just means that we need to explore
all the implications of having many vagrant SERVERs, and factor this into
our choice of transport protocol.



Someone convince me please.


regards


Bruce

-------------------------------------------------------
Bruce Chapman, Software Systems Architect,
NEC New Zealand
LEVEL 6
CORNER TARANAKI AND MANNERS STREETS
WELLINGTON
PHONE: 64  4  381-6279
FAX:   64  4  381-1110
EMAIL: bchapman@wlg.nec.co.nz
--------------------------------------------------------

_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


------_=_NextPart_000_01C0B85C.4F765130
Content-Type: text/plain;
	name="draft-deason-sip-soap-00.txt"
Content-Disposition: attachment;
	filename="draft-deason-sip-soap-00.txt"
Content-Transfer-Encoding: quoted-printable



Internet Engineering Task Force                               N. Deason
Internet Draft                                        Ubiquity Software
draft-deason-sip-soap-00.txt                           Corporation Ltd.
June 30, 2000
Expires December 2000


                              SIP and SOAP
STATUS OF THIS MEMO

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups. Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six
   months and may be updated, replaced, or obsoleted by other documents
   at any time. It is inappropriate to use Internet- Drafts as
   reference material or to cite them other than as work in progress.

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.


1. Abstract

   This document describes an extension to the Session Initiation
   Protocol (SIP) [1] . The purpose of this extension is to provide
   an extremely generic and extensible framework through which SIP
   nodes can request additional services from remote nodes. Examples of
   such nodes include SIP Network Servers, SIP User Agents, SIP/PSTN
   Gateways, SIP/H.323 Gateways and SIP Enabled Application Service
   Brokers. It also a candidate for providing a remote procedure call
   mechanism for Call Processing Language (CPL) scripts [2] .

   This proposal is based upon a new SIP method, called SERVICE. The
   SERVICE method can carry a Simple Object Access Protocol (SOAP) [3]
   message as it's payload. SOAP is a lightweight protocol for exchange
   of information in a decentralized, distributed environment. SOAP
   defines a framework for encoding request and response messages in
   XML. Typically SOAP uses HTTP as a transport protocol but this
   proposal enables SIP to be used instead.


2. Conventions used in this document




Deason                                                        [Page 1]
=0C
Internet Draft               SIP and SOAP                    June 2000


   In examples, "C:" and "S:" indicate lines sent by the client and
   server respectively.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in
   this document are to be interpreted as described in RFC-2119 [4].


3. Introduction

   Many SIP enabled network components will need to collaborate in the
   creation of future services. As well as the core SIP components of
   User Agents, Proxy Servers and Redirect Servers, there are SIP/H.323
   gateways, SIP/PSTN gateways and SIP based Application Service
   Brokers (ASBs). Empowering these components with a generic and
   flexible way, within SIP, to request additional services of each
   other provides a basis for sophisticated service creation.

   It is also noted that the requirements for Call Processing Language
   identifies a clean interface for scripts to remote procedure calls,
   for instance to access an external billing database, as desirable.
   While Corba, RMI, or DCOM are given as possible candidates the
   mechanism described here is equally suitable and has the attraction
   of reusing SIP signaling.

   SOAP is a protocol specification for invoking methods on servers,
   services, components and objects. SOAP defines a XML vocabulary for
   encoding requests and responses messages and typically uses HTTP as
   a transport protocol. However, the definition of the XML vocabulary
   is entirely independent of the fact that it is usually carried over
   HTTP. SOAP implementations that use SMTP instead of HTTP already
   exist. The SOAP XML vocabulary can be used to represent method
   parameters, return values, and exceptions. It has been designed to
   be highly extensible. Like SIP, SOAP can be implemented in any
   language that supports text processing and is platform agnostic. As
   SIP shares much in common with HTTP it is relatively simple for SIP
   to be used as the transport protocol for SOAP requests and
   responses. All that is required is an additional SIP method defined
   here; "SERVICE".

   As this proposed extension is, by intention, highly flexible the
   question of when it's use is appropriate must be carefully
   considered by implementers. It should not be used to duplicate
   functionality that already exists within SIP. For example, a SIP
   node can inform another node about user location through an
   INVITE/3XX transaction. There is no need for a SERVICE request to be
   issued to implement this form of basic user location service between
   SIP nodes. Similarly SERVICE requests should not be used to tackle
   problems that lie outside of SIP's solution space. SIP's solution
   space has been defined within the guidelines to extending SIP [5].
   Implementers should also recognise that SIP is not designed to
   provide the basis for a high efficiency or general computing RPC
   mechanism.

Deason                                                        [Page 2]
=0C
Internet Draft               SIP and SOAP                    June 2000




4. The SERVICE Method

   The SERVICE method can be used by a SIP client to request a service
   of a SIP server. It is a standard SIP message and will be forwarded
   until it reaches the server or end user which is performing the
   service. The SERVICE method body is typically of the type text/xml
   and contains a description of the service request in the form of a
   SOAP request message. As the body of SIP messages are opaque other
   payloads are possible. The response to the SERVICE request follows
   the standard SIP response codes. 200-class responses indicate
   success, 300 redirection to an alternate server, 400 client error,
   500 server error, and 600 global failure. Responses MAY contain a
   message body also of the type text/xml representing results of the
   service request described by a SOAP response message.

   The request message must contain a Request-URI plus To, From, Call-
   ID, Via, and CSeq fields. The Request-URI contains the destination
   of the SERVICE request. The To field contains the address of the
   service provider, and the From field contains the address of the
   service requester. All SERVICE requests from the same Client SHOULD
   use the same Call-ID, at least within the same reboot cycle. SERVICE
   request with the same Call-ID MUST have increasing CSeq header
   values. However, the server does not have to reject out-of-order
   requests. As the SERVICE request has no direct effect on any
   existing call state it represents a new Call leg. If information
   relating to en existing Call leg or SIP transaction is required to
   complete the service request it should be sent with the SOAP
   message.

   All of the SIP general headers, Date, Encryption, Expires,
   Organization may be present and retain the same meaning as they do
   in SIP. All the request headers also have the same semantics as in
   SIP. The entity headers are used to describe the XML payload
   containing the SOAP message, or any other type of payload, if
   present. This table expands on tables 4 and 5 in RFC 2543 [1].

        Header                    Where     SERV
        ------                    -----     ----
        Accept                      R        o
        Accept                     415       o
        Accept                      r        o
        Accept-Encoding             R        o
        Accept-Encoding            415       o
        Accept-Language             R        o
        Accept-Language            415       o
        Allow                      200       o
        Allow                      405       m
        Authorization               R        o
        Authorization               r        o
        Call-ID                    gc        m
        Contact                     R        o

Deason                                                        [Page 3]
=0C
Internet Draft               SIP and SOAP                    June 2000


        Contact                    1xx       o
        Contact                    2xx       o
        Contact                    3xx       o
        Contact                    485       o
        Content-Disposition         e        o
        Content-Encoding            e        o
        Content-Function            e        o
        Content-Language            e        m
        Content-Length              e        m
        Content-Type                e        *
        CSeq                       gc        m
        Date                        g        o
        Encryption                  g        o
        Expires                     g        o
        From                       gc        m
        Hide                        R        o
        In-Reply-To                 R        -
        Max-Forwards                R        o
        MIME-Version                g        o
        Organization                g        o
        Priority                    R        o
        Proxy-Authenticate         407       o
        Proxy-Authorization         R        o
        Proxy-Require               R        o
        Record-Route                R        o
        Record-Route           2xx,401,484   o
        Require                     g        o
        Response-Key                R        o
        Retry-After                 R        -
        Retry-After          404,413,480,486 o
        Retry-After              500,503     o
        Retry-After              600,603     o
        Route                       R        o
        Server                      r        o
        Subject                     R        -
        Supported                   g        o
        Timestamp                   g        o
        To                        gc(1)      m
        Unsupported                 R        o
        Unsupported                420       o
        User-Agent                  g        o
        Via                       gc(2)      m
        Warning                     r        o
        WWW-Authenticate            R        o
        WWW-Authenticate           401       o

   Table 1. Summary of header fields. (1) copied with possible addition
   of tags; (2) UAS removes first Via header field.

   It is generally anticipated that a SERVICE request will be sent from
   a SIP Client to a well known destination SIP Server that it expects
   to be able to support the method. If this is not the case the Client
   can probe a Server for support of the SERVICE method by sending an

Deason                                                        [Page 4]
=0C
Internet Draft               SIP and SOAP                    June 2000


   OPTIONS request. The response to this request should contain the
   Allow header entity-field listing the set of supported methods. If
   the token SERVICE included in this field the method is supported.


5. SOAP Messages

   As detailed descriptions of how a SOAP message encodes a service
   request, and the results of service requests in a response, exist
   elsewhere [3] this section only provides an overview.

   The SOAP message component is made up of a XML document containing a
   mandatory SOAP envelope, an optional SOAP header, and a mandatory
   SOAP body. This can be carried within the SIP message body of type
   text/xml.

   The SOAP envelope is the top element of the XML document. The SOAP
   header is a generic mechanism for adding features to a SOAP message.
   SOAP provides a few attributes to indicate who should deal with a
   feature and whether it is mandatory or optional. In this way
   features can be added without prior agreement between the
   communicating parties. Extensions that could be implemented as
   header entries include transaction management, payment, specific
   method versioning, QoS specification etc. The SOAP body is a
   container for all mandatory information intended for the ultimate
   recipient of the SOAP message. The encoding rules for this
   information are well defined. SOAP also defines a Fault element that
   can be used in the SOAP body for reporting errors.

   The SOAP encoding style is based on a simple type system that is a
   generalisation of the common features found in type systems in
   programming languages, databases and semi-structured data. A type is
   either a simple (scalar) type or is a compound type constructed as a
   composite of several parts, each with a type. This allows the
   encoding of simple types (e.g. int, float, string), enumerations,
   arrays, compound values, structs and references to values. It is
   worth noting that it is possible to use other encoding styles that
   specify different serialization rules within a SOAP message. The
   SOAP encodingStyle global attribute can be used to indicate the
   encoding style being used.


6. Examples

   The following section illustrates example call flows. It uses
   a trivial credit check service that could be implemented using the
   the SIP SERVICE method to make SOAP requests. This example is
   modeled on Example 1 from the SOAP Protocol proposal [3]. As such
   it is an example designed to aid understanding of the SOAP messages
   rather than illustrate a meaningful service.

   The first example shows a successful response to a service
   request.

Deason                                                        [Page 5]
=0C
Internet Draft               SIP and SOAP                    June 2000



   C->S:

   SERVICE sip:application_service_broker.ubiquity.net SIP/2.0
   To: sip:application_service_broker.ubiquity.net
   From: sip:proxy.ubiquity.net
   Call-ID:648324@193.195.52.30
   CSeq: 1 SERVICE
   Via: SIP/2.0/UDP proxy.ubiquity.net
   Content-Type: text/xml
   Content-Length: 381

   <SOAP-ENV:Envelope
     xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope"
     SOAPENV:encodingStyle=3D
     "http://schemas.xmlsoap.org/soap/encoding/">
       <SOAP-ENV:Body>
           <m:GetCreditStatus xmlns:m=3D
           "http://www.ubiquity.net/sipservices">
               <user>sip:jo@ubiquity.net</user>
           </m:GetCreditStatus>
       </SOAP-ENV:Body>
   </SOAP-ENV:Envelope>

   S->C:

   SIP/2.0 200 OK
   To: sip:application_service_broker.ubiquity.net
   From: sip:proxy.ubiquity.net
   Call-ID:648324@193.195.52.30
   CSeq: 1 SERVICE
   Via: SIP/2.0/UDP proxy.ubiquity.net
   Content-Type: text/xml
   Content-Length: 371

   <SOAP-ENV:Envelope
     xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope"
     SOAP-ENV:encodingStyle=3D
     "http://schemas.xmlsoap.org/soap/encoding/">
       <SOAP-ENV:Body>
           <m:GetCreditStatus xmlns:m=3D
           "http://www.ubiquity.net/sipservices">
               <return>34.5</return>
           </m:GetCreditStatus>
       </SOAP-ENV:Body>
   </SOAP-ENV:Envelope>

   The next example shows an unsuccessful call flow where the
   application service does not support the requested service.

   C->S:

   SERVICE sip:application_service_broker.there.com SIP/2.0

Deason                                                        [Page 6]
=0C
Internet Draft               SIP and SOAP                    June 2000


   To: sip:application_service_broker.there.com
   From: sip:proxy.here.com
   Call-ID:648324@112.33.58.22
   CSeq: 1 SERVICE
   Via: SIP/2.0/UDP proxy.here.com
   Content-Type: text/xml
   Content-Length: 376

   <SOAP-ENV:Envelope
     xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope"
     SOAP-ENV:encodingStyle=3D
     "http://schemas.xmlsoap.org/soap/encoding/">
       <SOAP-ENV:Body>
           <m:GetCreditStatus xmlns:m=3D
           "http://www.there.com/services">
               <user>sip:jo@ubiquity.net</user>
           </m:GetCreditStatus>
       </SOAP-ENV:Body>
   </SOAP-ENV:Envelope>

   S->C:

   SIP/2.0 501 Not Implemented
   To: sip:application_service_broker.there.com
   From: sip:proxy.here.com
   Call-ID:648324@112.33.58.22
   CSeq: 1 SERVICE
   Via: SIP/2.0/UDP proxy.here.com

   The final example illustrates the call flow when the requested
   service is unsuccessful.

   C->S:

   SERVICE sip:application_service_broker.ubiquity.net SIP/2.0
   To: sip:application_service_broker.ubiquity.net
   From: sip:proxy.ubiquity.net
   Call-ID:648324@193.195.52.30
   CSeq: 1 SERVICE
   Via: SIP/2.0/UDP proxy.ubiquity.net
   Content-Type: text/xml
   Content-Length: 400

   <SOAP-ENV:Envelope
     xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope"
     SOAP-ENV:encodingStyle=3D
     "http://schemas.xmlsoap.org/soap/encoding/">
       <SOAP-ENV:Body>
           <m:GetCreditStatus xmlns:m=3D
           "http://www.ubiquity.net/sipservices">
               <user>sip:jo@gods.org</user>
           </m:GetCreditStatus>


Deason                                                        [Page 7]
=0C
Internet Draft               SIP and SOAP                    June 2000


       </SOAP-ENV:Body>
   </SOAP-ENV:Envelope>

   S->C:

   SIP/2.0 500 Server Internal Error
   To: sip:application_service_broker.ubiquity.net
   From: sip:proxy.ubiquity.net
   Call-ID:648324@193.195.52.30
   CSeq: 1 SERVICE
   Via: SIP/2.0/UDP proxy.ubiquity.net
   Content-Type: text/xml
   Content-Length: 418

   <SOAP-ENV:Envelope
     xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope"
     SOAP-ENV:encodingStyle=3D
     "http://schemas.xmlsoap.org/soap/encoding/" >
       <SOAP-ENV:Body>
           <SOAP-ENV:Fault>
               <faultcode>404</faultcode>
               <faultstring>
                   Unknown User - sip:jo@gods.org
               </faultstring>
           </SOAP-ENV:Fault>
       </SOAP-ENV:Body>
   </SOAP-ENV:Envelope>


7. Security Considerations

   This extension does not require any security capabilities to be
   added to SIP. It is expected that both authentication and encryption
   as already described by SIP will be of high importance to
   implementers.


8. References

   1  M. Handley, H. Schulzrinne, E. Schooler, and J. Rosenberg, "SIP:
      Session Initiation Protocol" Request for Comments (Proposed
      Standard) 2543, Internet Engineering Task Force, Mar. 1999

   2  J. Lennox and H. Schulzrinne, "Call Processing Language Framework
      and Requirements" Request for Comments (Informational) 2824,
      Internet Engineering Task Force, May 2000

   3  D. Box, D. Ehnebuske, G. Kakivaya, A. Layman, N. Mendelsohn,
      H. Nielsen, S. Thatte, and D. Winer, " Simple Object Access
      Protocol (SOAP) 1.1", W3C Note 08 May 2000,
      http://www.w3.org/TR/2000/NOTE-SOAP-20000508/



Deason                                                        [Page 8]
=0C
Internet Draft               SIP and SOAP                    June 2000



   4  Bradner, S., "Key words for use in RFCs to Indicate Requirement
      Levels", BCP 14, RFC 2119, March 1997

   5  J. Rosenberg and H. Schulzrinne, "Guidelines for Authors of SIP
      Extensions", Internet Draft, Internet Engineering Task Force,
      March 2000. Work in progress


9. Acknowledgments

   I would like to thank the authors of both SIP and SOAP for their
   hard work. Jo Hornsby and James Undery of Ubiquity Software for
   their useful discussions and comments.


10. Author's Addresses

   Neil Deason
   Ubiquity Software Corporation Limited
   Ubiquity House
   Langstone Park
   Newport
   South Wales
   United Kingdom
   NP18 2LH
   email: ndeason@ubiquity.net


Full Copyright Statement

   "Copyright (C) The Internet Society (2000). All Rights Reserved.
   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph
   are included on all such copies and derivative works. However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into."











Deason                                                        [Page 9]
=0C


------_=_NextPart_000_01C0B85C.4F765130--

_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


From spirits-admin@lists.bell-labs.com  Thu Mar 29 15:39:04 2001
Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA09507
	for <spirits-archive@odin.ietf.org>; Thu, 29 Mar 2001 15:39:03 -0500 (EST)
Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1])
	by lists.bell-labs.com (Postfix) with ESMTP
	id 41E1444369; Thu, 29 Mar 2001 15:39:02 -0500 (EST)
Delivered-To: spirits@share.research.bell-labs.com
Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49])
	by lists.bell-labs.com (Postfix) with SMTP id F352D44368
	for <spirits@share.research.bell-labs.com>; Thu, 29 Mar 2001 15:38:07 -0500 (EST)
Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Thu Mar 29 15:34:34 EST 2001
Received: by lists.bell-labs.com (Postfix)
	id 86B4044380; Thu, 29 Mar 2001 15:23:28 -0500 (EST)
Delivered-To: spirits@lists.bell-labs.com
Received: from ans.ih.lucent.com (ans.ih.lucent.com [135.1.218.156])
	by lists.bell-labs.com (Postfix) with SMTP id 489824437D
	for <spirits@lists.bell-labs.com>; Thu, 29 Mar 2001 15:23:28 -0500 (EST)
Received: by ans.ih.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id OAA25065; Thu, 29 Mar 2001 14:23:24 -0600
Received: from lucent.com by ans.ih.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id OAA25062; Thu, 29 Mar 2001 14:23:23 -0600
Message-ID: <3AC39A33.63C8DBCB@lucent.com>
From: Alec Brusilovsky <abrusilovsky@lucent.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en,ru,uk
MIME-Version: 1.0
To: spirits@lists.bell-labs.com
Subject: Re: [SPIRITS] Some Thoughts On Protocol Requirements
References: <E5B80B001D76D211879C00E02910776108672A4B@njc240po05.mt.att.com>
Content-Type: multipart/mixed;
 boundary="------------A4CCA161450D0986C29E61EC"
Sender: spirits-admin@lists.bell-labs.com
Errors-To: spirits-admin@lists.bell-labs.com
X-BeenThere: spirits@lists.bell-labs.com
X-Mailman-Version: 2.0beta6
Precedence: bulk
Reply-To: spirits@lists.bell-labs.com
List-Help: <mailto:spirits-request@lists.bell-labs.com?subject=help>
List-Post: <mailto:spirits@lists.bell-labs.com>
List-Subscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=subscribe>
List-Id: IETF SPIRITS Working Group <spirits.lists.bell-labs.com>
List-Unsubscribe: <http://lists.bell-labs.com/mailman/listinfo/spirits>, <mailto:spirits-request@lists.bell-labs.com?subject=unsubscribe>
List-Archive: http://lists.bell-labs.com/pipermail/spirits/
Date: Thu, 29 Mar 2001 14:25:24 -0600

This is a multi-part message in MIME format.
--------------A4CCA161450D0986C29E61EC
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Group,

We have a good discussion here.
One comment, though. To preserve bandwidth for those of us who are on a slow
dial-up, please next time post a pointer to the document, instead of a document
itself.

Thanks,
Alec

"Roy, Radhika R, ALCOO" wrote:

> Folks:
>
> It might be interesting to see the enclosed draft.
>
> Radhika R. Roy
>
> Technology Consultant
> AT&T
> Room 3D-2C09
> 200 S. Laurel Avenue
> Middletown, NJ 07748
> +1 732 420 1580
> rrroy@att.com
>
> -----Original Message-----
> From: Bruce Chapman [mailto:bchapman@wlg.nec.co.nz]
> Sent: Thursday, March 29, 2001 12:47 AM
> To: spirits@lists.bell-labs.com
> Subject: Re: [SPIRITS] Some Thoughts On Protocol Requirements
>
> Alec summarized ...
>
> > 2. SIP seems to be a "natural" transport vehicle for SPIRITS
> > parameters ("We based PINT on SIP - it works for
> > us, so you may need to give some details on why it doesn't work for
> > SPIRITS. . . we didn't have to re-invent a
> > worldwide infrastructure" - LC).
> >
>
> As pointed out in my earlier emails, the B interface has some unusual
> characteristics.
>
> I dont think we can just assume therefore that because SIP worked for PINT,
> it will work for SPIRITS where (for ICW service at least) the thousands of
> SERVERs are vagrants. (my term, it has no fixed abode, it may be old
> fashioned, it is possibly antisocial, it is certainly unmanaged, it probably
> won't have trusted relationship with anything (crytographically speaking)
> (unless we build one), its platforms may have worn thin, you don't know its
> whereabouts, and it may just disappear without warning)
>
> This doesn't mean that SIP wont work, it just means that we need to explore
> all the implications of having many vagrant SERVERs, and factor this into
> our choice of transport protocol.
>
> Someone convince me please.
>
> regards
>
> Bruce
>
> -------------------------------------------------------
> Bruce Chapman, Software Systems Architect,
> NEC New Zealand
> LEVEL 6
> CORNER TARANAKI AND MANNERS STREETS
> WELLINGTON
> PHONE: 64  4  381-6279
> FAX:   64  4  381-1110
> EMAIL: bchapman@wlg.nec.co.nz
> --------------------------------------------------------
>
> _______________________________________________
> SPIRITS mailing list
> SPIRITS@lists.bell-labs.com
> http://lists.bell-labs.com/mailman/listinfo/spirits
>
>   ------------------------------------------------------------
>                                    Name: draft-deason-sip-soap-00.txt
>    draft-deason-sip-soap-00.txt    Type: Plain Text (text/plain)
>                                Encoding: quoted-printable

--------------A4CCA161450D0986C29E61EC
Content-Type: text/x-vcard; charset=us-ascii;
 name="abrusilovsky.vcf"
Content-Description: Card for Alec Brusilovsky
Content-Disposition: attachment;
 filename="abrusilovsky.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Brusilovsky;Alec 
tel;fax:+1 630 713 5840 
tel;work:+1 630 713 8401
x-mozilla-html:FALSE
org:e-Services Group;Next Generation Evolution and Architecture
version:2.1
email;internet:abrusilovsky@lucent.com
title:MTS 
adr;quoted-printable:;;IHP 1A-423=0D=0A263 Shuman Blvd,P O Box 3050;Naperville;IL;60566-7050;U S
x-mozilla-cpt:;5312
fn:Alec  Brusilovsky
end:vcard

--------------A4CCA161450D0986C29E61EC--


_______________________________________________
SPIRITS mailing list
SPIRITS@lists.bell-labs.com
http://lists.bell-labs.com/mailman/listinfo/spirits


