Re: [Sipping] FW: I-D ACTION:draft-donovan-sipping-service-override-01.txt

"Arjun Roychowdhury" <arjunrc@gmail.com> Fri, 30 June 2006 16:59 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FwMKy-00016A-UI; Fri, 30 Jun 2006 12:59:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FwMKx-0000zY-Dw for sipping@ietf.org; Fri, 30 Jun 2006 12:59:23 -0400
Received: from nz-out-0102.google.com ([64.233.162.207]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FwMKw-0005jo-0s for sipping@ietf.org; Fri, 30 Jun 2006 12:59:23 -0400
Received: by nz-out-0102.google.com with SMTP id n29so349094nzf for <sipping@ietf.org>; Fri, 30 Jun 2006 09:59:21 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=l0f+5bjhNc9q60TVI0vZGQwgnhzn1V5buqJe+pEun2ICzWOTj38GKswor5CGKrr9pBfd9Mmr2jtlEJhqcvuhpAw+CE7Bmvs1uhySze7KuaouiWkhO5em/mIfhzFuNir86bmyqpeeFum6dByKXxbwDqaiSy28JLBlC4+LLyOwk3w=
Received: by 10.36.74.19 with SMTP id w19mr972335nza; Fri, 30 Jun 2006 09:59:21 -0700 (PDT)
Received: by 10.36.59.3 with HTTP; Fri, 30 Jun 2006 09:59:20 -0700 (PDT)
Message-ID: <a9994e940606300959y12408a40rba5613f65483c3c7@mail.gmail.com>
Date: Fri, 30 Jun 2006 12:59:20 -0400
From: Arjun Roychowdhury <arjunrc@gmail.com>
To: "Steve Donovan (stdonova)" <stdonova@cisco.com>
Subject: Re: [Sipping] FW: I-D ACTION:draft-donovan-sipping-service-override-01.txt
In-Reply-To: <6C1428F48A2C0147974E96533CDB2F9502249E3F@xmb-sjc-232.amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <6C1428F48A2C0147974E96533CDB2F9502249E3F@xmb-sjc-232.amer.cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi,
This document does not describe how to populate the Service-State,
what really is 'state' and how does one ensure that it is understood
by the xAS, xSM and xUA.

I would like to hear the author's opininon on what really is this
State. Unless it is defined, I don't see how it is beneficial over any
proprietary tag.  Judging by the current discussion about the IMS CSI,
it looks like the term 'service' is found to be too restrictive in
this group, and it is preferred to leave it as 'primitives', in which
case, I am curious how a service state can be defined (and even if
defined, what use would it be, if service cannot be defined).

regds
arjun


regds
arjun



On 6/30/06, Steve Donovan (stdonova) <stdonova@cisco.com> wrote:
> All,
>
> Please find the attached reference to a draft for consideration by the
> SIPPING working group.
>
> Comments are welcome and solicited.
>
> Regards,
>
> Steve Donovan
>
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Thursday, June 29, 2006 2:50 PM
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-donovan-sipping-service-override-01.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>        Title           : The Service-State Header
>        Author(s)       : C. Sivachelvan, S. Donovan
>        Filename        : draft-donovan-sipping-service-override-01.txt
>        Pages           : 21
>        Date            : 2006-6-29
>
> This document proposes a new header for the Session Initiation
>   Protocol.  This header, the Service-State header, is used to
>   communicate application state between two SIP elements.
>
>   Note: The name of the file will be updated to be consistent with the
>   proposed header name in the next revision of the draft.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-donovan-sipping-service-overri
> de-01.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then
>        "get draft-donovan-sipping-service-override-01.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
>        mailserv@ietf.org.
> In the body type:
>        "FILE
> /internet-drafts/draft-donovan-sipping-service-override-01.txt".
>
> NOTE:   The mail server at ietf.org can return the document in
>        MIME-encoded form by using the "mpack" utility.  To use this
>        feature, insert the command "ENCODING mime" before the "FILE"
>        command.  To decode the response(s), you will need "munpack" or
>        a MIME-compliant mail reader.  Different MIME-compliant mail
> readers
>        exhibit different behavior, especially when dealing with
>        "multipart" MIME messages (i.e. documents which have been split
>        up into multiple messages), so check your local documentation on
>        how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>
>
>


-- 
Arjun Roychowdhury

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP