From mailnull@www1.ietf.org  Sun Sep  1 05:45:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11619
	for <sip-archive@odin.ietf.org>; Sun, 1 Sep 2002 05:45:42 -0400 (EDT)
From: mailnull@www1.ietf.org
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g819kjC16565
	for sip-archive@odin.ietf.org; Sun, 1 Sep 2002 05:46:45 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g819kjo16562
	for <sip-web-archive@optimus.ietf.org>; Sun, 1 Sep 2002 05:46:45 -0400
Date: Sun, 01 Sep 2002 05:46:45 -0400
Message-ID: <20020901094645.1916.58457.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
To: sip-web-archive@optimus.ietf.org
X-No-Archive: yes
X-Ack: no
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org 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, sip-request@ietf.org) 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@.  Thanks!

Passwords for sip-web-archive@optimus.ietf.org:

List                                     Password // URL
----                                     --------  
sip@ietf.org                             itiU      
https://www1.ietf.org/mailman/options/sip/sip-web-archive%40optimus.ietf.org



From mailnull@www1.ietf.org  Sun Sep  1 15:20:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26694
	for <sip-archive@odin.ietf.org>; Sun, 1 Sep 2002 15:20:42 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g81JLoA06335
	for sip-archive@odin.ietf.org; Sun, 1 Sep 2002 15:21:50 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g81JLEo06300;
	Sun, 1 Sep 2002 15:21:14 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g81JIUo06164
	for <sip@optimus.ietf.org>; Sun, 1 Sep 2002 15:18:30 -0400
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26591;
	Sun, 1 Sep 2002 15:16:50 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g81JHp3x010316;
	Sun, 1 Sep 2002 12:17:52 -0700 (PDT)
Received: from open-131-161-248-81.cliq.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.1.0.54-GA)
	with ESMTP id AAU15666;
	Sun, 1 Sep 2002 12:16:14 -0700 (PDT)
Date: Sun, 1 Sep 2002 12:18:33 -0700
Mime-Version: 1.0 (Apple Message framework v482)
Content-Type: text/plain; charset=US-ASCII; format=flowed
From: Rohan Mahy <rohan@cisco.com>
To: sip@ietf.org, "'sipping@ietf.org'" <sipping@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <9B8EB1AE-BDDF-11D6-98F6-0003938AF740@cisco.com>
X-Mailer: Apple Mail (2.482)
Content-Transfer-Encoding: 7bit
Subject: [Sip] FYI: IETF Liason Statement to 3GPP
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Folks,

Below is a copy of the liason statement that will be sent to 3GPP later 
today.

thanks,
-rohan

----------------

From: Chairs, SIP, SIPPING, and SIMPLE Working Groups of the Internet 
Engineering Task Force
Cc:   Area Directors, Transport Area, Internet Engineering Steering Group
To: CN and SA Working Groups of the Third-Generation Partnership Program
Subject: Liaison Statement on Interoperability Issues and SIP in IMS

I. Introduction

The IETF is made up of working groups, such as the Session Initiation
Protocol (SIP) Working Group, and these are supervised by the
Internet Engineering Steering Group, or IESG, whose goals
include maintaining technical quality and assuring that
its work is consistent with the "big picture" of Internet principles
and architecture.  The IETF also has the Internet Architecture
Board, or IAB, ensuring the big picture is clear.

The IESG's Area Director for SIP, and the IESG as a whole have given
repeated guidance to the SIP Working Group in the process of development 
and
approval of the consensus standards such as RFC 3261, during which
several points have been raised that we believe are related to the usage
of SIP in the Internet Multimedia Subsystem (IMS) specifications
being developed in 3GPP.  Our goal is to communicate these points at a
technical level, from the consensus of our approved standards, as
the Working Group chairs, to you as counterpart technical Working Group
chairs.  We wish to convey introductory points here, points about
interoperability in section 2, and specific issues about the IETF
SIP standards in section 3.

The key guidance is:


a) Internet standards are intended to have broad applicability for all
    aspects of the Internet, including private networks that use IP,
    whether or not connected to the public network. Developing
    "profiles"--subsets of or exceptions to these standards, whether
    for use on public or private networks, is dangerous because of
    the very high probability that such profiles will be incompatible
    with those deployed on the Internet as a whole, and we have
    learned that networks which are disconnected today somehow
    become connected tomorrow.  Thus inter-operability remains
    a critical issue, even for currently disconnected networks.

b) Any implementation of a protocol claimed or named to be an Internet
    protocol, such as SIP, should be greatly consistent with both the
    specification and the practice of that protocol on the Internet. If
    an implementation doesn't interoperate, and/or does not operate
    (if suitably configured) in general Internet environments, it
    is actually a separate protocol and should not be advertised or
    named the same as an implementation of an Internet protocol.

We believe that 3GPP chose to use SIP and other Internet protocols in
the IMS specification not only as a matter of expedient reuse, but
because of advantages such as interoperability, open
specification, and widespread deployment offered by these
protocols. Further, we believe that 3GPP's choice was influenced by
the expectation that these Internet advantages would lead to benefits
such as reduced systems cost, access to a wide variety of applications
being developed around the Internet, and the consequent ability to
develop and offer new value-added applications to wireless subscribers
and generate new revenue for wireless operators. We support this
choice and rationale, and welcome 3GPP as a collaborator in making the
best possible use of our protocols. To that end, we welcome 3GPP input
on requirements for the unique aspects of their environment, in the 
further
development of SIP and other Internet protocols, and look forward to
collaborating with 3GPP to facilitate developing the best understanding
for all about how best to configure SIP and other Internet protocols for
interoperability between the IM subsystem and the Internet.

II. Interoperability Issues

Careful review of published IMS specifications, by knowledgeable
individuals who participate in both 3GPP and IETF, has raised
certain concerns relating to interoperability (both in terms of a and b)
between IMS and the Internet.  The Chairs of the IETF SIP and
SIPPING Working Groups offer this liaison statement as guidance and
suggestions to 3GPP, in hopes of assuring effective interoperability.
We realize that some of these concerns stem from recent enhancements
to the SIP protocol, and cannot be immediately rectified in the IMS
specifications, whereas other concerns may be more readily
addressable. We encourage 3GPP to address these concerns to the
extent possible in IMS Release 5, and to address them and any
underlying issues before the finalization of IMS Release 6. We will
assist wherever reasonably possible, and welcome further
involvement with 3GPP to resolve these concerns.

In general, we would like 3GPP to consider two interopability goals:

1) While operator and business policy configurations (which are
    not matters of IETF concern) may prevent such behavior,
    the IMS specification itself should not prevent the possibility that
    an IMS user can access SIP services on the Internet, or establish
    SIP sessions with users on the Internet. This should be possible
    without requiring that some sort of application-level-gateway to
    modify the IMS protocols. In most cases, we expect that an IMS
    user should be able to access Internet applications even if there
    is no explicit support in IMS for that application.  This implies that
    IMS users have access to complete SIP implementations including
    security capabilities.

2) The SIP specification (RFC 3261) and the other related IETF
    standards allow for building strong and secure Internet applications.
    An IMS operator should be able to buy an off-the-shelf, IETF
    standard, commercial SIP system that implements the RFCs related
    to SIP, and which also has support for IMS-specific capabilites,
    plug it in, use configuration options to set up policies, and make
    it work in IMS systems.  Configuration and local policies would 
establish
    what local authentication, authorization, AAA, reporting, SIP
    P-headers, and other options are used that might not be widely
    implemented in the Internet--or indeed are not in the case of 
P-headers.
    Vendors building an IMS system should not need to build two
    completely separate products to address IMS and SIP in the Internet.
    The key point here is that there should be little or no difference
    other than the configuration choices conceptually in an
    implementation used in IMS and one used outside IMS.  This would
    be an ideal interoperability goal, and well suited to the IETF's
    orientation of standardizing what is implemented and available
    to the operator or user of the equipment (e.g. minimum
    mandatory to implement strong security), not what is used or how
    it is used.


III. Specific Concerns on SIP in IMS Release 5

The following discusses some of our technical concerns with IMS. It
should be noted that this is by no means an exhaustive list of
issues. It is intended primarily to introduce the types of
behaviors that concern us and the probable impact of these behaviors
on interoperability. However, where specific issues are illustrated,
we request specific consideration of these concerns by 3GPP.


There are three general classes of issues that we have identified:

1. IMS Call State Control Function (CSCF) nodes send messages that
    the SIP RFCs reserve to User Agents without implementing
    the functions required for User Agents. There is some 3GPP
    view that this is justified by viewing the CSCF as a "back to back
    user agent" with the User Agent, but it is not done correctly,
    because the CSCF must be implemented in all ways as User Agent
    in order to be serve as a B2BUA in this manner.

2. IMS CSCF nodes modify headers in ways explicitly prohibited to
    proxies by the SIP RFCs, again without implementing associated UA
    behavior.

3. IMS CSCF nodes modify bodies in messages which is not permitted to
    proxies by SIP RFCs, again without implementing the associated UA
    behavior.

A number of participants in the SIP working group, including the
chairs authoring this liaison statement, have identified specific
concerns with the IMS Release 5 specifications as we understand
them.  Some of these have been discussed in the context of
SIP or SIPPING chartered work.  We do not propose solutions here,
but we invite consideration of these concerns, with the goal of
3GPP achieving a better alignment to the IETF's SIP RFCs after
discussion in 3GPP and in the SIP and SIPPING mailing lists over some
period.  IETF will provide any support and assistance that will
help.

1) The P-CSCF may send a BYE on behalf of the UA, generally because
    the P-CSCF has been notified by the radio layer that the UA has
    lost contact.  Of course, the P-CSCF doesn't have the credentials
    to provide authentication of the BYE, so many UAs will consider this
    to be a forged message. This also renders 3GPP UAs vulnerable to
    denial of service attacks using forged BYEs.

2) The P-CSCF strips away Route, Record-Route, Via, Path, and
    Service-Route headers before passing messages on to the UA. It
    then reinserts them messages in the other direction,
    and may also strip out Route headers inserted by the UA. This
    breaks end-to-end protection using S/MIME and prevents the UA from
    accessing external services using loose routing. It also prevents
    the UA from knowing about any proxies that may have piggybacked on
    its registration using the Path mechanism, which is a serious
    violation of the openness principle and leaves 3GPP users
    registering with external servers subject to certain
    man-in-the-middle attacks affecting REGISTER messages without any
    way to detect those attacks.

3) The CSCF may edit SDP sent from or to the UA in order to force the
    selection of codecs considered favorable to the operator. This has
    the side effect of breaking end-to-end protection of the SDP using
    S/MIME. It also precludes interoperating with external elements
    when both the IMS UA and the external UA share only a common
    codec not supported by the P-CSCF.

4) The S-CSCF MAY (we believe this is still being discussed in 3GPP)
    obfuscate the To: and From: fields in messages. This appear to be
    based on a particular interpretation of privacy regulation in
    certain European domains.  It has the side effect of breaking
    end-to-end protection with S/MIME and breaking external services
    using the To: and From: fields, such as the most common forms of
    caller-ID used with SIP today.

5) The P-CSCF filters messages from the UA to assure that only an
    identity known to the P-CSCF is presented by the UA. This may
    interact with the preceding characteristic. This appears to be
    required to accommodate the authorization model of 3GPP, which
    authenticates only REGISTER transactions and uses them to establish
    a security association between a UA and the P-CSCF. The side effect is
    that a 3GPP user may use only the operator-provided identity and
    may not be able to effectively use third-party services that
    provide other identities unless those services provide identity
    transformation with a back-to-back user agent.

6) The I-CSCF (or THIG) may encrypt Via and Route information when
    acting in topology-hiding mode. This was allowed for in earlier SIP
    specifications, but the use has been deprecated for a variety of
    reasons. The exact impact on interoperability remains unknown.

7) Some CSCF elements and AS may manipulate message bodies.
    Manipulating message bodies in a proxy is forbidden in RFC 3261
    because it breaks end-to-end protection using S/MIME. These
    elements do not appear to implement all of the UA behavior that
    would enable them to preserve end-to-end protections.

As stated above, this statement does not recommend a timeframe for
aligning on the issues decribed above, but they are important.  One
way to ensure better aligment going forward is in a general 
recommendation.
The SIP Working Group chairs suggest that the implementers of
systems for IMS should consider doing interoperability testing of their
implementations against other SIP implementations. The SIPit
interoperability events are organized explicitly for this purpose,
and we intend to use these events to support the documentation of
interoperability of features required for advancing SIP and related
RFCs from "Proposed Standard" to "Draft Standard" status in the
IETF. Your participation in such testing would be helpful to the whole
SIP community.


IV.  Contacts:

Dean Willis, dean.willis@softarmor.com, for SIP Working Group Chairs
Rohan Mahy,  rmahy@cisco.com, for other SIP-related WGs' Chairs
Allison Mankin, mankin@isi.edu, for the IESG

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



From mailnull@www1.ietf.org  Mon Sep  2 09:42:45 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22498
	for <sip-archive@odin.ietf.org>; Mon, 2 Sep 2002 09:42:45 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g82DhqC05320
	for sip-archive@odin.ietf.org; Mon, 2 Sep 2002 09:43:52 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82Dgno05283;
	Mon, 2 Sep 2002 09:42:49 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82DeMo05205
	for <sip@optimus.ietf.org>; Mon, 2 Sep 2002 09:40:22 -0400
Received: from lohi.eng.song.fi (lohi.eng.song.fi [195.10.149.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22463
	for <sip@ietf.org>; Mon, 2 Sep 2002 09:38:44 -0400 (EDT)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.34 #1 (Debian))
	id 17lrQY-0008Ox-00; Mon, 02 Sep 2002 16:39:38 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15731.27162.249185.762069@harjus.eng.song.fi>
Date: Mon, 2 Sep 2002 16:39:38 +0300
To: Rohan Mahy <rohan@cisco.com>
Cc: sip@ietf.org, mankin@psg.com, fluffy@cisco.com, jon.peterson@neustar.biz,
        Mark Watson <mwatson@nortelnetworks.com>
Subject: [Sip] asserted-identity-02
In-Reply-To: <88CD607D-BAF1-11D6-BC81-0003938AF740@cisco.com>
References: <88CD607D-BAF1-11D6-BC81-0003938AF740@cisco.com>
X-Mailer: VM 7.03 under Emacs 21.2.1
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

i have the same problem as before with this document, i.e., that the
concept of an identity of a user and the user's sip uri are not clear
and not necessarily the same thing.  when a proxy authenticates a user,
for example, using digest authentication, the proxy finds out the user's
identity, but that is not what the proxy places in the p-a-i header.
the header should be called-asserted-uri rather than
p-asserted-identity.

what comes to "hinting", as i have said many times before, i don't like
the term at all.  if the proxy doesn't agree with p-preferred-identity,
the document should say that the proxy SHOULD reject the request.
otherwise the whole thing would be dangerous to the user.

-- juha

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



From mailnull@www1.ietf.org  Mon Sep  2 11:41:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24840
	for <sip-archive@odin.ietf.org>; Mon, 2 Sep 2002 11:41:23 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g82FgTF12010
	for sip-archive@odin.ietf.org; Mon, 2 Sep 2002 11:42:29 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82Ffgo11991;
	Mon, 2 Sep 2002 11:41:42 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82Feio11946
	for <sip@optimus.ietf.org>; Mon, 2 Sep 2002 11:40:44 -0400
Received: from auemail1.firewall.lucent.com ([192.11.223.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24826
	for <sip@ietf.org>; Mon, 2 Sep 2002 11:39:07 -0400 (EDT)
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g82Fe9811425
	for <sip@ietf.org>; Mon, 2 Sep 2002 11:40:09 -0400 (EDT)
Received: by en0060D057.uk.lucent.com with Internet Mail Service (5.5.2653.19)
	id <R7G0Y5FY>; Mon, 2 Sep 2002 16:40:08 +0100
Message-ID: <475FF955A05DD411980D00508B6D5FB00439EA93@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'sip@ietf.org'" <sip@ietf.org>
Date: Mon, 2 Sep 2002 16:40:07 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sip] use of MESSAGE method for passing display information to the user
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

Within 3GPP, there is a requirement for intermediate servers to pass textual information for display to the user. This may be related to a dialog or not.

A typical example may be (in the case of a prepay user):

"Please top up your units or your call may be terminated prematurely".

There are a number of methods that are defined which essentially convey body information between User Agents (INFO, NOTIFY, MESSAGE, PUBLISH?).

Some of these would appear more suitable that others for passing this information. 

Of the existing methods, MESSAGE would appear to be the most suitable (and indeed is the one selected by some of the experts involved). However the internet draft specifically talks about the body being an "Instant Message".

Rather than get into a situation similar to that which affects INFO (i.e. people seem to have implemented various applications on INFO and IETF experts say INFO is not appropriate for that application), could I request an exchange of views on the applicability or not of MESSAGE for this type of information, and if not, what solution would otherwise be suggested.

Note that the information would normally be expected to come from some network based entity (acting as a UA). When related to a dialog, the source may well be some B2BUA between the two end UAs involved in the dialog.

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



From mailnull@www1.ietf.org  Mon Sep  2 12:43:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26586
	for <sip-archive@odin.ietf.org>; Mon, 2 Sep 2002 12:43:22 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g82GiTl15810
	for sip-archive@odin.ietf.org; Mon, 2 Sep 2002 12:44:29 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82Ghho15773;
	Mon, 2 Sep 2002 12:43:43 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82Ggvo15719
	for <sip@optimus.ietf.org>; Mon, 2 Sep 2002 12:42:57 -0400
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26571
	for <sip@ietf.org>; Mon, 2 Sep 2002 12:41:19 -0400 (EDT)
From: krisztian.kiss@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g82Geul12278
	for <sip@ietf.org>; Mon, 2 Sep 2002 19:40:57 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5d188b9da5ac158f2114f@esvir01nok.ntc.nokia.com>;
 Mon, 2 Sep 2002 19:42:41 +0300
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 2 Sep 2002 19:42:41 +0300
Received: from esebe005.NOE.Nokia.com ([172.21.138.45]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 2 Sep 2002 19:42:41 +0300
Received: from trebe003.NOE.Nokia.com ([172.22.232.175]) by esebe005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 2 Sep 2002 19:42:40 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] use of MESSAGE method for passing display information to the user
Date: Mon, 2 Sep 2002 19:42:40 +0300
Message-ID: <DED1F2C6CE07FA498D7AD0CCAC03401B01513DE4@trebe003.europe.nokia.com>
Thread-Topic: [Sip] use of MESSAGE method for passing display information to the user
Thread-Index: AcJSl8EkLkK6fZv/SGGMrl7YiytgiQABxM3w
To: <drage@lucent.com>, <sip@ietf.org>
X-OriginalArrivalTime: 02 Sep 2002 16:42:40.0731 (UTC) FILETIME=[C0C68AB0:01C2529F]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g82Ggwo15720
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit


Keith,

> Within 3GPP, there is a requirement for intermediate servers 
> to pass textual information for display to the user. This may 
> be related to a dialog or not.
> 
> A typical example may be (in the case of a prepay user):
> 
> "Please top up your units or your call may be terminated prematurely".
> 
> There are a number of methods that are defined which 
> essentially convey body information between User Agents 
> (INFO, NOTIFY, MESSAGE, PUBLISH?).
> 
> Some of these would appear more suitable that others for 
> passing this information. 
> 
> Of the existing methods, MESSAGE would appear to be the most 
> suitable (and indeed is the one selected by some of the 
> experts involved). However the internet draft specifically 
> talks about the body being an "Instant Message".

draft-ietf-sip-message-06 states that the body can be of ANY MIME type:
"The body of the request will contain the message to be delivered.
   This body can be of any MIME type, including message/cpim."

Regards,
Krisztian


> Rather than get into a situation similar to that which 
> affects INFO (i.e. people seem to have implemented various 
> applications on INFO and IETF experts say INFO is not 
> appropriate for that application), could I request an 
> exchange of views on the applicability or not of MESSAGE for 
> this type of information, and if not, what solution would 
> otherwise be suggested.
> 
> Note that the information would normally be expected to come 
> from some network based entity (acting as a UA). When related 
> to a dialog, the source may well be some B2BUA between the 
> two end UAs involved in the dialog.
> 
> Keith Drage
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Mon Sep  2 13:02:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26848
	for <sip-archive@odin.ietf.org>; Mon, 2 Sep 2002 13:02:22 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g82H3TW16375
	for sip-archive@odin.ietf.org; Mon, 2 Sep 2002 13:03:29 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82H3Co16361;
	Mon, 2 Sep 2002 13:03:12 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82H28o16313
	for <sip@optimus.ietf.org>; Mon, 2 Sep 2002 13:02:08 -0400
Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26811
	for <sip@ietf.org>; Mon, 2 Sep 2002 13:00:29 -0400 (EDT)
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g82H22J25834
	for <sip@ietf.org>; Mon, 2 Sep 2002 13:02:02 -0400 (EDT)
Received: by en0060D057.uk.lucent.com with Internet Mail Service (5.5.2653.19)
	id <R7G0Y6NS>; Mon, 2 Sep 2002 18:02:01 +0100
Message-ID: <475FF955A05DD411980D00508B6D5FB00439EA95@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'krisztian.kiss@nokia.com'" <krisztian.kiss@nokia.com>,
        "Drage, Keith (Keith)" <drage@lucent.com>, sip@ietf.org
Subject: RE: [Sip] use of MESSAGE method for passing display information t
	o the user
Date: Mon, 2 Sep 2002 18:01:58 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

With hindsight, I drafted the last paragraph of my original message badly.

Rather than try to paraphrase again, I will select a direct quote from the message draft abstract:

The MESSAGE method is an extension to the Session Initiation Protocol
   (SIP) that allows the transfer of Instant Messages.  MESSAGE requests
   carry the content in the form of MIME body parts.  

My concern is not over how such a body should be coded. The questions is does such a usage to carry "Please top up your units or your call may be terminated prematurely" qualify as an Instant Message, i.e. is it within the semantics of MESSAGE to perform this function.

Keith

> -----Original Message-----
> From: krisztian.kiss@nokia.com [mailto:krisztian.kiss@nokia.com]
> Sent: 02 September 2002 17:43
> To: drage@lucent.com; sip@ietf.org
> Subject: RE: [Sip] use of MESSAGE method for passing display 
> information
> to the user
> 
> 
> 
> Keith,
> 
> > Within 3GPP, there is a requirement for intermediate servers 
> > to pass textual information for display to the user. This may 
> > be related to a dialog or not.
> > 
> > A typical example may be (in the case of a prepay user):
> > 
> > "Please top up your units or your call may be terminated 
> prematurely".
> > 
> > There are a number of methods that are defined which 
> > essentially convey body information between User Agents 
> > (INFO, NOTIFY, MESSAGE, PUBLISH?).
> > 
> > Some of these would appear more suitable that others for 
> > passing this information. 
> > 
> > Of the existing methods, MESSAGE would appear to be the most 
> > suitable (and indeed is the one selected by some of the 
> > experts involved). However the internet draft specifically 
> > talks about the body being an "Instant Message".
> 
> draft-ietf-sip-message-06 states that the body can be of ANY 
> MIME type:
> "The body of the request will contain the message to be delivered.
>    This body can be of any MIME type, including message/cpim."
> 
> Regards,
> Krisztian
> 
> 
> > Rather than get into a situation similar to that which 
> > affects INFO (i.e. people seem to have implemented various 
> > applications on INFO and IETF experts say INFO is not 
> > appropriate for that application), could I request an 
> > exchange of views on the applicability or not of MESSAGE for 
> > this type of information, and if not, what solution would 
> > otherwise be suggested.
> > 
> > Note that the information would normally be expected to come 
> > from some network based entity (acting as a UA). When related 
> > to a dialog, the source may well be some B2BUA between the 
> > two end UAs involved in the dialog.
> > 
> > Keith Drage
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> > 
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Mon Sep  2 13:24:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27301
	for <sip-archive@odin.ietf.org>; Mon, 2 Sep 2002 13:24:47 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g82HPsr17671
	for sip-archive@odin.ietf.org; Mon, 2 Sep 2002 13:25:54 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82HPKo17655;
	Mon, 2 Sep 2002 13:25:21 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82HOIo17608
	for <sip@optimus.ietf.org>; Mon, 2 Sep 2002 13:24:18 -0400
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27240
	for <sip@ietf.org>; Mon, 2 Sep 2002 13:22:35 -0400 (EDT)
From: krisztian.kiss@nokia.com
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g82HMDl23388
	for <sip@ietf.org>; Mon, 2 Sep 2002 20:22:13 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5d18b10433ac158f256fa@esvir05nok.ntc.nokia.com>;
 Mon, 2 Sep 2002 20:23:32 +0300
Received: from esebe014.NOE.Nokia.com ([172.21.138.53]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 2 Sep 2002 20:23:32 +0300
Received: from trebe003.NOE.Nokia.com ([172.22.232.175]) by esebe014.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 2 Sep 2002 20:23:32 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] use of MESSAGE method for passing display information to the user
Date: Mon, 2 Sep 2002 20:23:31 +0300
Message-ID: <DED1F2C6CE07FA498D7AD0CCAC03401B01513DE7@trebe003.europe.nokia.com>
Thread-Topic: [Sip] use of MESSAGE method for passing display information to the user
Thread-Index: AcJSonhL/Jhg4lEoS76gOTX94mUS7gAAQ6bQ
To: <drage@lucent.com>
Cc: <sip@ietf.org>
X-OriginalArrivalTime: 02 Sep 2002 17:23:32.0237 (UTC) FILETIME=[75FCABD0:01C252A5]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g82HOIo17609
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hi Keith,

> With hindsight, I drafted the last paragraph of my original 
> message badly.
> 
> Rather than try to paraphrase again, I will select a direct 
> quote from the message draft abstract:
> 
> The MESSAGE method is an extension to the Session Initiation Protocol
>    (SIP) that allows the transfer of Instant Messages.  
> MESSAGE requests
>    carry the content in the form of MIME body parts.  
> 
> My concern is not over how such a body should be coded. The 
> questions is does such a usage to carry "Please top up your 
> units or your call may be terminated prematurely" qualify as 
> an Instant Message, i.e. is it within the semantics of 
> MESSAGE to perform this function.

The introduction part of the draft contains some "hint" about this:
"Instant messaging is defined as the exchange of content between a set
   of participants in near real time.  Generally, the content is short
   text messages, although that need not be the case."

Based on this, my guess is that carrying "Please top up your units or your call may be terminated prematurely" fits to the semantics of the MESSAGE request.

Regards,
Krisztian

 
> Keith
> 
> > -----Original Message-----
> > From: krisztian.kiss@nokia.com [mailto:krisztian.kiss@nokia.com]
> > Sent: 02 September 2002 17:43
> > To: drage@lucent.com; sip@ietf.org
> > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > information
> > to the user
> > 
> > 
> > 
> > Keith,
> > 
> > > Within 3GPP, there is a requirement for intermediate servers 
> > > to pass textual information for display to the user. This may 
> > > be related to a dialog or not.
> > > 
> > > A typical example may be (in the case of a prepay user):
> > > 
> > > "Please top up your units or your call may be terminated 
> > prematurely".
> > > 
> > > There are a number of methods that are defined which 
> > > essentially convey body information between User Agents 
> > > (INFO, NOTIFY, MESSAGE, PUBLISH?).
> > > 
> > > Some of these would appear more suitable that others for 
> > > passing this information. 
> > > 
> > > Of the existing methods, MESSAGE would appear to be the most 
> > > suitable (and indeed is the one selected by some of the 
> > > experts involved). However the internet draft specifically 
> > > talks about the body being an "Instant Message".
> > 
> > draft-ietf-sip-message-06 states that the body can be of ANY 
> > MIME type:
> > "The body of the request will contain the message to be delivered.
> >    This body can be of any MIME type, including message/cpim."
> > 
> > Regards,
> > Krisztian
> > 
> > 
> > > Rather than get into a situation similar to that which 
> > > affects INFO (i.e. people seem to have implemented various 
> > > applications on INFO and IETF experts say INFO is not 
> > > appropriate for that application), could I request an 
> > > exchange of views on the applicability or not of MESSAGE for 
> > > this type of information, and if not, what solution would 
> > > otherwise be suggested.
> > > 
> > > Note that the information would normally be expected to come 
> > > from some network based entity (acting as a UA). When related 
> > > to a dialog, the source may well be some B2BUA between the 
> > > two end UAs involved in the dialog.
> > > 
> > > Keith Drage
> > > _______________________________________________
> > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > > This list is for NEW development of the core SIP Protocol
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sipping@ietf.org for new developments on the 
> application of sip
> > > 
> > 
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Mon Sep  2 13:39:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27580
	for <sip-archive@odin.ietf.org>; Mon, 2 Sep 2002 13:39:44 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g82HeqO18713
	for sip-archive@odin.ietf.org; Mon, 2 Sep 2002 13:40:52 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82HeHo18698;
	Mon, 2 Sep 2002 13:40:17 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82Hd2o18610
	for <sip@optimus.ietf.org>; Mon, 2 Sep 2002 13:39:02 -0400
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.54])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27528
	for <sip@ietf.org>; Mon, 2 Sep 2002 13:37:23 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-4.cisco.com (8.12.2/8.12.2) with ESMTP id g82HcRW4008916;
	Mon, 2 Sep 2002 10:38:27 -0700 (PDT)
Received: from open-131-161-248-81.cliq.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.1.0.54-GA)
	with ESMTP id AAU20587;
	Mon, 2 Sep 2002 10:36:45 -0700 (PDT)
Date: Mon, 2 Sep 2002 10:39:06 -0700
Subject: Re: [Sip] asserted-identity-02
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v482)
Cc: sip@ietf.org, mankin@psg.com, fluffy@cisco.com, jon.peterson@neustar.biz,
        Mark Watson <mwatson@nortelnetworks.com>
To: <jh@lohi.eng.song.fi>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <15731.27162.249185.762069@harjus.eng.song.fi>
Message-Id: <E1484B14-BE9A-11D6-98F6-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.482)
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Juha,

On Monday, September 2, 2002, at 06:39 AM, <jh@lohi.eng.song.fi> wrote:
> i have the same problem as before with this document, i.e., that the
> concept of an identity of a user and the user's sip uri are not clear
> and not necessarily the same thing.  when a proxy authenticates a user,
> for example, using digest authentication, the proxy finds out the user's
> identity, but that is not what the proxy places in the p-a-i header.
> the header should be called-asserted-uri rather than
> p-asserted-identity.

Your objections are noted.  Other than your individual objections, we 
have very strong consensus on the draft, so IETF is publishing it.  
You've made a lot of other comments that the WG has agreed with and have 
been incorporated.  The WG just didn't agree with you on that one.

> what comes to "hinting", as i have said many times before, i don't like
> the term at all.  if the proxy doesn't agree with p-preferred-identity,
> the document should say that the proxy SHOULD reject the request.
> otherwise the whole thing would be dangerous to the user.

I agree that that is a very good policy to configure in your network and 
its equipment. I would recommend similar policies, but there are other 
folks who want to use different policies to satisfy different 
requirements.

If you want to write an Informational document describing SIP privacy 
policies that benefit the end-user, I will give it agenda time in 
SIPPING. I'd personally like to see such a document published.

thanks,
-rohan

> -- juha
>

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



From mailnull@www1.ietf.org  Mon Sep  2 13:52:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28028
	for <sip-archive@odin.ietf.org>; Mon, 2 Sep 2002 13:52:54 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g82Hs2N19181
	for sip-archive@odin.ietf.org; Mon, 2 Sep 2002 13:54:02 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82Hreo19159;
	Mon, 2 Sep 2002 13:53:40 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82HqXo19115
	for <sip@optimus.ietf.org>; Mon, 2 Sep 2002 13:52:33 -0400
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27984;
	Mon, 2 Sep 2002 13:50:53 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id g82Hpvds007247;
	Mon, 2 Sep 2002 10:51:57 -0700 (PDT)
Received: from open-131-161-248-81.cliq.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.1.0.54-GA)
	with ESMTP id AAU20633;
	Mon, 2 Sep 2002 10:50:15 -0700 (PDT)
Date: Mon, 2 Sep 2002 10:52:36 -0700
Subject: Re: [Sip] FYI: IETF Liason Statement to 3GPP
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v482)
Cc: sip@ietf.org, "'sipping@ietf.org'" <sipping@ietf.org>
To: Rohan Mahy <rohan@cisco.com>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <9B8EB1AE-BDDF-11D6-98F6-0003938AF740@cisco.com>
Message-Id: <C4189D18-BE9C-11D6-98F6-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.482)
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hello again,

I just wanted to clarify something.  Despite the subject of *this* 
thread, this liason statement is from the chairs, not from "IETF" as a 
whole.  When I sent this to 3GPP the subject was "Liaison Statement on 
Interoperability Issues and SIP in IMS".

thanks,
-rohan

On Sunday, September 1, 2002, at 12:18 PM, Rohan Mahy wrote:

> Hi Folks,
>
> Below is a copy of the liason statement that will be sent to 3GPP later 
> today.
>
> thanks,
> -rohan
>
> ----------------
>
> From: Chairs, SIP, SIPPING, and SIMPLE Working Groups of the Internet 
> Engineering Task Force
> Cc:   Area Directors, Transport Area, Internet Engineering Steering 
> Group
> To: CN and SA Working Groups of the Third-Generation Partnership Program
> Subject: Liaison Statement on Interoperability Issues and SIP in IMS
>
> I. Introduction
>
> The IETF is made up of working groups, such as the Session Initiation
> Protocol (SIP) Working Group, and these are supervised by the
> Internet Engineering Steering Group, or IESG, whose goals
> include maintaining technical quality and assuring that
> its work is consistent with the "big picture" of Internet principles
> and architecture.  The IETF also has the Internet Architecture
> Board, or IAB, ensuring the big picture is clear.
>
> The IESG's Area Director for SIP, and the IESG as a whole have given
> repeated guidance to the SIP Working Group in the process of 
> development and
> approval of the consensus standards such as RFC 3261, during which
> several points have been raised that we believe are related to the usage
> of SIP in the Internet Multimedia Subsystem (IMS) specifications
> being developed in 3GPP.  Our goal is to communicate these points at a
> technical level, from the consensus of our approved standards, as
> the Working Group chairs, to you as counterpart technical Working Group
> chairs.  We wish to convey introductory points here, points about
> interoperability in section 2, and specific issues about the IETF
> SIP standards in section 3.
>
> The key guidance is:
>
>
> a) Internet standards are intended to have broad applicability for all
>    aspects of the Internet, including private networks that use IP,
>    whether or not connected to the public network. Developing
>    "profiles"--subsets of or exceptions to these standards, whether
>    for use on public or private networks, is dangerous because of
>    the very high probability that such profiles will be incompatible
>    with those deployed on the Internet as a whole, and we have
>    learned that networks which are disconnected today somehow
>    become connected tomorrow.  Thus inter-operability remains
>    a critical issue, even for currently disconnected networks.
>
> b) Any implementation of a protocol claimed or named to be an Internet
>    protocol, such as SIP, should be greatly consistent with both the
>    specification and the practice of that protocol on the Internet. If
>    an implementation doesn't interoperate, and/or does not operate
>    (if suitably configured) in general Internet environments, it
>    is actually a separate protocol and should not be advertised or
>    named the same as an implementation of an Internet protocol.
>
> We believe that 3GPP chose to use SIP and other Internet protocols in
> the IMS specification not only as a matter of expedient reuse, but
> because of advantages such as interoperability, open
> specification, and widespread deployment offered by these
> protocols. Further, we believe that 3GPP's choice was influenced by
> the expectation that these Internet advantages would lead to benefits
> such as reduced systems cost, access to a wide variety of applications
> being developed around the Internet, and the consequent ability to
> develop and offer new value-added applications to wireless subscribers
> and generate new revenue for wireless operators. We support this
> choice and rationale, and welcome 3GPP as a collaborator in making the
> best possible use of our protocols. To that end, we welcome 3GPP input
> on requirements for the unique aspects of their environment, in the 
> further
> development of SIP and other Internet protocols, and look forward to
> collaborating with 3GPP to facilitate developing the best understanding
> for all about how best to configure SIP and other Internet protocols for
> interoperability between the IM subsystem and the Internet.
>
> II. Interoperability Issues
>
> Careful review of published IMS specifications, by knowledgeable
> individuals who participate in both 3GPP and IETF, has raised
> certain concerns relating to interoperability (both in terms of a and b)
> between IMS and the Internet.  The Chairs of the IETF SIP and
> SIPPING Working Groups offer this liaison statement as guidance and
> suggestions to 3GPP, in hopes of assuring effective interoperability.
> We realize that some of these concerns stem from recent enhancements
> to the SIP protocol, and cannot be immediately rectified in the IMS
> specifications, whereas other concerns may be more readily
> addressable. We encourage 3GPP to address these concerns to the
> extent possible in IMS Release 5, and to address them and any
> underlying issues before the finalization of IMS Release 6. We will
> assist wherever reasonably possible, and welcome further
> involvement with 3GPP to resolve these concerns.
>
> In general, we would like 3GPP to consider two interopability goals:
>
> 1) While operator and business policy configurations (which are
>    not matters of IETF concern) may prevent such behavior,
>    the IMS specification itself should not prevent the possibility that
>    an IMS user can access SIP services on the Internet, or establish
>    SIP sessions with users on the Internet. This should be possible
>    without requiring that some sort of application-level-gateway to
>    modify the IMS protocols. In most cases, we expect that an IMS
>    user should be able to access Internet applications even if there
>    is no explicit support in IMS for that application.  This implies 
> that
>    IMS users have access to complete SIP implementations including
>    security capabilities.
>
> 2) The SIP specification (RFC 3261) and the other related IETF
>    standards allow for building strong and secure Internet applications.
>    An IMS operator should be able to buy an off-the-shelf, IETF
>    standard, commercial SIP system that implements the RFCs related
>    to SIP, and which also has support for IMS-specific capabilites,
>    plug it in, use configuration options to set up policies, and make
>    it work in IMS systems.  Configuration and local policies would 
> establish
>    what local authentication, authorization, AAA, reporting, SIP
>    P-headers, and other options are used that might not be widely
>    implemented in the Internet--or indeed are not in the case of 
> P-headers.
>    Vendors building an IMS system should not need to build two
>    completely separate products to address IMS and SIP in the Internet.
>    The key point here is that there should be little or no difference
>    other than the configuration choices conceptually in an
>    implementation used in IMS and one used outside IMS.  This would
>    be an ideal interoperability goal, and well suited to the IETF's
>    orientation of standardizing what is implemented and available
>    to the operator or user of the equipment (e.g. minimum
>    mandatory to implement strong security), not what is used or how
>    it is used.
>
>
> III. Specific Concerns on SIP in IMS Release 5
>
> The following discusses some of our technical concerns with IMS. It
> should be noted that this is by no means an exhaustive list of
> issues. It is intended primarily to introduce the types of
> behaviors that concern us and the probable impact of these behaviors
> on interoperability. However, where specific issues are illustrated,
> we request specific consideration of these concerns by 3GPP.
>
>
> There are three general classes of issues that we have identified:
>
> 1. IMS Call State Control Function (CSCF) nodes send messages that
>    the SIP RFCs reserve to User Agents without implementing
>    the functions required for User Agents. There is some 3GPP
>    view that this is justified by viewing the CSCF as a "back to back
>    user agent" with the User Agent, but it is not done correctly,
>    because the CSCF must be implemented in all ways as User Agent
>    in order to be serve as a B2BUA in this manner.
>
> 2. IMS CSCF nodes modify headers in ways explicitly prohibited to
>    proxies by the SIP RFCs, again without implementing associated UA
>    behavior.
>
> 3. IMS CSCF nodes modify bodies in messages which is not permitted to
>    proxies by SIP RFCs, again without implementing the associated UA
>    behavior.
>
> A number of participants in the SIP working group, including the
> chairs authoring this liaison statement, have identified specific
> concerns with the IMS Release 5 specifications as we understand
> them.  Some of these have been discussed in the context of
> SIP or SIPPING chartered work.  We do not propose solutions here,
> but we invite consideration of these concerns, with the goal of
> 3GPP achieving a better alignment to the IETF's SIP RFCs after
> discussion in 3GPP and in the SIP and SIPPING mailing lists over some
> period.  IETF will provide any support and assistance that will
> help.
>
> 1) The P-CSCF may send a BYE on behalf of the UA, generally because
>    the P-CSCF has been notified by the radio layer that the UA has
>    lost contact.  Of course, the P-CSCF doesn't have the credentials
>    to provide authentication of the BYE, so many UAs will consider this
>    to be a forged message. This also renders 3GPP UAs vulnerable to
>    denial of service attacks using forged BYEs.
>
> 2) The P-CSCF strips away Route, Record-Route, Via, Path, and
>    Service-Route headers before passing messages on to the UA. It
>    then reinserts them messages in the other direction,
>    and may also strip out Route headers inserted by the UA. This
>    breaks end-to-end protection using S/MIME and prevents the UA from
>    accessing external services using loose routing. It also prevents
>    the UA from knowing about any proxies that may have piggybacked on
>    its registration using the Path mechanism, which is a serious
>    violation of the openness principle and leaves 3GPP users
>    registering with external servers subject to certain
>    man-in-the-middle attacks affecting REGISTER messages without any
>    way to detect those attacks.
>
> 3) The CSCF may edit SDP sent from or to the UA in order to force the
>    selection of codecs considered favorable to the operator. This has
>    the side effect of breaking end-to-end protection of the SDP using
>    S/MIME. It also precludes interoperating with external elements
>    when both the IMS UA and the external UA share only a common
>    codec not supported by the P-CSCF.
>
> 4) The S-CSCF MAY (we believe this is still being discussed in 3GPP)
>    obfuscate the To: and From: fields in messages. This appear to be
>    based on a particular interpretation of privacy regulation in
>    certain European domains.  It has the side effect of breaking
>    end-to-end protection with S/MIME and breaking external services
>    using the To: and From: fields, such as the most common forms of
>    caller-ID used with SIP today.
>
> 5) The P-CSCF filters messages from the UA to assure that only an
>    identity known to the P-CSCF is presented by the UA. This may
>    interact with the preceding characteristic. This appears to be
>    required to accommodate the authorization model of 3GPP, which
>    authenticates only REGISTER transactions and uses them to establish
>    a security association between a UA and the P-CSCF. The side effect 
> is
>    that a 3GPP user may use only the operator-provided identity and
>    may not be able to effectively use third-party services that
>    provide other identities unless those services provide identity
>    transformation with a back-to-back user agent.
>
> 6) The I-CSCF (or THIG) may encrypt Via and Route information when
>    acting in topology-hiding mode. This was allowed for in earlier SIP
>    specifications, but the use has been deprecated for a variety of
>    reasons. The exact impact on interoperability remains unknown.
>
> 7) Some CSCF elements and AS may manipulate message bodies.
>    Manipulating message bodies in a proxy is forbidden in RFC 3261
>    because it breaks end-to-end protection using S/MIME. These
>    elements do not appear to implement all of the UA behavior that
>    would enable them to preserve end-to-end protections.
>
> As stated above, this statement does not recommend a timeframe for
> aligning on the issues decribed above, but they are important.  One
> way to ensure better aligment going forward is in a general 
> recommendation.
> The SIP Working Group chairs suggest that the implementers of
> systems for IMS should consider doing interoperability testing of their
> implementations against other SIP implementations. The SIPit
> interoperability events are organized explicitly for this purpose,
> and we intend to use these events to support the documentation of
> interoperability of features required for advancing SIP and related
> RFCs from "Proposed Standard" to "Draft Standard" status in the
> IETF. Your participation in such testing would be helpful to the whole
> SIP community.
>
>
> IV.  Contacts:
>
> Dean Willis, dean.willis@softarmor.com, for SIP Working Group Chairs
> Rohan Mahy,  rmahy@cisco.com, for other SIP-related WGs' Chairs
> Allison Mankin, mankin@isi.edu, for the IESG
>
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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



From mailnull@www1.ietf.org  Mon Sep  2 14:04:21 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28340
	for <sip-archive@odin.ietf.org>; Mon, 2 Sep 2002 14:04:21 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g82I5Ti19636
	for sip-archive@odin.ietf.org; Mon, 2 Sep 2002 14:05:29 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82I5Do19626;
	Mon, 2 Sep 2002 14:05:13 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g82I4co19595
	for <sip@optimus.ietf.org>; Mon, 2 Sep 2002 14:04:38 -0400
Received: from lohi.eng.song.fi (lohi.eng.song.fi [195.10.149.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28329
	for <sip@ietf.org>; Mon, 2 Sep 2002 14:02:58 -0400 (EDT)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.34 #1 (Debian))
	id 17lvYa-0008Rt-00; Mon, 02 Sep 2002 21:04:12 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15731.43036.591793.30282@harjus.eng.song.fi>
Date: Mon, 2 Sep 2002 21:04:12 +0300
To: Rohan Mahy <rohan@cisco.com>
Cc: sip@ietf.org, mankin@psg.com, fluffy@cisco.com, jon.peterson@neustar.biz,
        Mark Watson <mwatson@nortelnetworks.com>
Subject: Re: [Sip] asserted-identity-02
In-Reply-To: <E1484B14-BE9A-11D6-98F6-0003938AF740@cisco.com>
References: <15731.27162.249185.762069@harjus.eng.song.fi>
	<E1484B14-BE9A-11D6-98F6-0003938AF740@cisco.com>
X-Mailer: VM 7.03 under Emacs 21.2.1
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

forgot one more thing:

the preferred-identity (should be preferred-uri) header should not be a
p-header, because it solves a general problem in sip, i.e., sip today
doesn't have a means for an anonymous user to tell which calling party
number it prefers to use when the proxy forwards the request to pstn.

-- juha

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



From mailnull@www1.ietf.org  Tue Sep  3 03:29:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18251
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 03:29:40 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g837Utd04302
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 03:30:55 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g837Tbo04260;
	Tue, 3 Sep 2002 03:29:37 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g837Qto04125
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 03:26:55 -0400
Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18213
	for <sip@ietf.org>; Tue, 3 Sep 2002 03:25:07 -0400 (EDT)
From: hisham.khartabil@nokia.com
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g837Qg710563
	for <sip@ietf.org>; Tue, 3 Sep 2002 10:26:42 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5d1bb4f033ac158f23168@esvir03nok.nokia.com>;
 Tue, 3 Sep 2002 10:26:41 +0300
Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 3 Sep 2002 10:26:41 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] use of MESSAGE method for passing display information to the user
Date: Tue, 3 Sep 2002 10:26:09 +0300
Message-ID: <2038BCC78B1AD641891A0D1AE133DBB7C20584@esebe019.ntc.nokia.com>
Thread-Topic: [Sip] use of MESSAGE method for passing display information to the user
Thread-Index: AcJSox27Cjscq69xTriAOy2WQ6dsQwAd8OsQ
To: <drage@lucent.com>, <krisztian.kiss@nokia.com>, <sip@ietf.org>
X-OriginalArrivalTime: 03 Sep 2002 07:26:41.0051 (UTC) FILETIME=[3F4516B0:01C2531B]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g837Quo04126
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

I guess it could be done that way, but you might find that others would prefer some sort of Notification package for this type of thing.

/Hisham

> -----Original Message-----
> From: ext Drage, Keith (Keith) [mailto:drage@lucent.com]
> Sent: Monday, September 02, 2002 8:02 PM
> To: Kiss Krisztian (NRC/Tampere); Drage, Keith (Keith); sip@ietf.org
> Subject: RE: [Sip] use of MESSAGE method for passing display 
> information
> to the user
> 
> 
> With hindsight, I drafted the last paragraph of my original 
> message badly.
> 
> Rather than try to paraphrase again, I will select a direct 
> quote from the message draft abstract:
> 
> The MESSAGE method is an extension to the Session Initiation Protocol
>    (SIP) that allows the transfer of Instant Messages.  
> MESSAGE requests
>    carry the content in the form of MIME body parts.  
> 
> My concern is not over how such a body should be coded. The 
> questions is does such a usage to carry "Please top up your 
> units or your call may be terminated prematurely" qualify as 
> an Instant Message, i.e. is it within the semantics of 
> MESSAGE to perform this function.
> 
> Keith
> 
> > -----Original Message-----
> > From: krisztian.kiss@nokia.com [mailto:krisztian.kiss@nokia.com]
> > Sent: 02 September 2002 17:43
> > To: drage@lucent.com; sip@ietf.org
> > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > information
> > to the user
> > 
> > 
> > 
> > Keith,
> > 
> > > Within 3GPP, there is a requirement for intermediate servers 
> > > to pass textual information for display to the user. This may 
> > > be related to a dialog or not.
> > > 
> > > A typical example may be (in the case of a prepay user):
> > > 
> > > "Please top up your units or your call may be terminated 
> > prematurely".
> > > 
> > > There are a number of methods that are defined which 
> > > essentially convey body information between User Agents 
> > > (INFO, NOTIFY, MESSAGE, PUBLISH?).
> > > 
> > > Some of these would appear more suitable that others for 
> > > passing this information. 
> > > 
> > > Of the existing methods, MESSAGE would appear to be the most 
> > > suitable (and indeed is the one selected by some of the 
> > > experts involved). However the internet draft specifically 
> > > talks about the body being an "Instant Message".
> > 
> > draft-ietf-sip-message-06 states that the body can be of ANY 
> > MIME type:
> > "The body of the request will contain the message to be delivered.
> >    This body can be of any MIME type, including message/cpim."
> > 
> > Regards,
> > Krisztian
> > 
> > 
> > > Rather than get into a situation similar to that which 
> > > affects INFO (i.e. people seem to have implemented various 
> > > applications on INFO and IETF experts say INFO is not 
> > > appropriate for that application), could I request an 
> > > exchange of views on the applicability or not of MESSAGE for 
> > > this type of information, and if not, what solution would 
> > > otherwise be suggested.
> > > 
> > > Note that the information would normally be expected to come 
> > > from some network based entity (acting as a UA). When related 
> > > to a dialog, the source may well be some B2BUA between the 
> > > two end UAs involved in the dialog.
> > > 
> > > Keith Drage
> > > _______________________________________________
> > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > > This list is for NEW development of the core SIP Protocol
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sipping@ietf.org for new developments on the 
> application of sip
> > > 
> > 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Tue Sep  3 03:47:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18598
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 03:47:56 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g837nBp05525
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 03:49:11 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g837mFo05503;
	Tue, 3 Sep 2002 03:48:15 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g837lCo05456
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 03:47:12 -0400
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18535
	for <sip@ietf.org>; Tue, 3 Sep 2002 03:45:26 -0400 (EDT)
From: aki.niemi@nokia.com
Received: from esvir02nok.ntc.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x2.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g837kwU28037
	for <sip@ietf.org>; Tue, 3 Sep 2002 10:46:59 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir02nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5d1bc76ea3ac158f2208c@esvir02nok.ntc.nokia.com>;
 Tue, 3 Sep 2002 10:46:53 +0300
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 3 Sep 2002 10:46:52 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] use of MESSAGE method for passing display information to the user
Date: Tue, 3 Sep 2002 10:46:52 +0300
Message-ID: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD9010FE417@esebe013.ntc.nokia.com>
Thread-Topic: [Sip] use of MESSAGE method for passing display information to the user
Thread-Index: AcJSox27Cjscq69xTriAOy2WQ6dsQwAd8OsQAACU5cA=
To: <hisham.khartabil@nokia.com>, <drage@lucent.com>,
        <krisztian.kiss@nokia.com>, <sip@ietf.org>
X-OriginalArrivalTime: 03 Sep 2002 07:46:52.0989 (UTC) FILETIME=[11A426D0:01C2531E]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g837lCo05457
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

This application seems rather different from the presence type notifications because it seems these notifications are unsolicited. So to me MESSAGE seems like a perfect fit. I don't have to "subscribe" in order to receive instant messages either.

So by saying "Notification package" perhaps you mean a new MIME type specifically for these unsolicited notifications?

Cheers,
Aki

> -----Original Message-----
> From: ext hisham.khartabil@nokia.com 
> [mailto:hisham.khartabil@nokia.com]
> Sent: Tuesday, September 03, 2002 10:26 AM
> To: drage@lucent.com; Kiss Krisztian (NRC/Tampere); sip@ietf.org
> Subject: RE: [Sip] use of MESSAGE method for passing display 
> information
> to the user
> 
> 
> I guess it could be done that way, but you might find that 
> others would prefer some sort of Notification package for 
> this type of thing.
> 
> /Hisham
> 
> > -----Original Message-----
> > From: ext Drage, Keith (Keith) [mailto:drage@lucent.com]
> > Sent: Monday, September 02, 2002 8:02 PM
> > To: Kiss Krisztian (NRC/Tampere); Drage, Keith (Keith); sip@ietf.org
> > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > information
> > to the user
> > 
> > 
> > With hindsight, I drafted the last paragraph of my original 
> > message badly.
> > 
> > Rather than try to paraphrase again, I will select a direct 
> > quote from the message draft abstract:
> > 
> > The MESSAGE method is an extension to the Session 
> Initiation Protocol
> >    (SIP) that allows the transfer of Instant Messages.  
> > MESSAGE requests
> >    carry the content in the form of MIME body parts.  
> > 
> > My concern is not over how such a body should be coded. The 
> > questions is does such a usage to carry "Please top up your 
> > units or your call may be terminated prematurely" qualify as 
> > an Instant Message, i.e. is it within the semantics of 
> > MESSAGE to perform this function.
> > 
> > Keith
> > 
> > > -----Original Message-----
> > > From: krisztian.kiss@nokia.com [mailto:krisztian.kiss@nokia.com]
> > > Sent: 02 September 2002 17:43
> > > To: drage@lucent.com; sip@ietf.org
> > > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > > information
> > > to the user
> > > 
> > > 
> > > 
> > > Keith,
> > > 
> > > > Within 3GPP, there is a requirement for intermediate servers 
> > > > to pass textual information for display to the user. This may 
> > > > be related to a dialog or not.
> > > > 
> > > > A typical example may be (in the case of a prepay user):
> > > > 
> > > > "Please top up your units or your call may be terminated 
> > > prematurely".
> > > > 
> > > > There are a number of methods that are defined which 
> > > > essentially convey body information between User Agents 
> > > > (INFO, NOTIFY, MESSAGE, PUBLISH?).
> > > > 
> > > > Some of these would appear more suitable that others for 
> > > > passing this information. 
> > > > 
> > > > Of the existing methods, MESSAGE would appear to be the most 
> > > > suitable (and indeed is the one selected by some of the 
> > > > experts involved). However the internet draft specifically 
> > > > talks about the body being an "Instant Message".
> > > 
> > > draft-ietf-sip-message-06 states that the body can be of ANY 
> > > MIME type:
> > > "The body of the request will contain the message to be delivered.
> > >    This body can be of any MIME type, including message/cpim."
> > > 
> > > Regards,
> > > Krisztian
> > > 
> > > 
> > > > Rather than get into a situation similar to that which 
> > > > affects INFO (i.e. people seem to have implemented various 
> > > > applications on INFO and IETF experts say INFO is not 
> > > > appropriate for that application), could I request an 
> > > > exchange of views on the applicability or not of MESSAGE for 
> > > > this type of information, and if not, what solution would 
> > > > otherwise be suggested.
> > > > 
> > > > Note that the information would normally be expected to come 
> > > > from some network based entity (acting as a UA). When related 
> > > > to a dialog, the source may well be some B2BUA between the 
> > > > two end UAs involved in the dialog.
> > > > 
> > > > Keith Drage
> > > > _______________________________________________
> > > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > > > This list is for NEW development of the core SIP Protocol
> > > > Use sip-implementors@cs.columbia.edu for questions on 
> current sip
> > > > Use sipping@ietf.org for new developments on the 
> > application of sip
> > > > 
> > > 
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> > 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Tue Sep  3 04:49:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19368
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 04:49:54 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g838pAC09208
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 04:51:10 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g838oho09166;
	Tue, 3 Sep 2002 04:50:44 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g838nNo09096
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 04:49:23 -0400
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19329
	for <sip@ietf.org>; Tue, 3 Sep 2002 04:47:35 -0400 (EDT)
From: hisham.khartabil@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g838lEl24176
	for <sip@ietf.org>; Tue, 3 Sep 2002 11:47:14 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5d1bffe870ac158f2114f@esvir01nok.ntc.nokia.com>;
 Tue, 3 Sep 2002 11:48:34 +0300
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 3 Sep 2002 11:48:34 +0300
Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 3 Sep 2002 11:48:34 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] use of MESSAGE method for passing display information to the user
Date: Tue, 3 Sep 2002 11:48:33 +0300
Message-ID: <2038BCC78B1AD641891A0D1AE133DBB7C2058B@esebe019.ntc.nokia.com>
Thread-Topic: [Sip] use of MESSAGE method for passing display information to the user
Thread-Index: AcJSox27Cjscq69xTriAOy2WQ6dsQwAd8OsQAACU5cAAAjI6kA==
To: <aki.niemi@nokia.com>, <drage@lucent.com>, <krisztian.kiss@nokia.com>,
        <sip@ietf.org>
X-OriginalArrivalTime: 03 Sep 2002 08:48:34.0194 (UTC) FILETIME=[AFBB3720:01C25326]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g838nNo09097
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

You're not subscribing to get an instant message, you're subscribing to get information about your prepaid units.

Why is it unsolicited? 

/Hisham

> -----Original Message-----
> From: Niemi Aki (NET/Espoo) 
> Sent: Tuesday, September 03, 2002 10:47 AM
> To: Khartabil Hisham (NMP/Helsinki); drage@lucent.com; Kiss Krisztian
> (NRC/Tampere); sip@ietf.org
> Subject: RE: [Sip] use of MESSAGE method for passing display 
> information
> to the user
> 
> 
> This application seems rather different from the presence 
> type notifications because it seems these notifications are 
> unsolicited. So to me MESSAGE seems like a perfect fit. I 
> don't have to "subscribe" in order to receive instant messages either.
> 
> So by saying "Notification package" perhaps you mean a new 
> MIME type specifically for these unsolicited notifications?
> 
> Cheers,
> Aki
> 
> > -----Original Message-----
> > From: ext hisham.khartabil@nokia.com 
> > [mailto:hisham.khartabil@nokia.com]
> > Sent: Tuesday, September 03, 2002 10:26 AM
> > To: drage@lucent.com; Kiss Krisztian (NRC/Tampere); sip@ietf.org
> > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > information
> > to the user
> > 
> > 
> > I guess it could be done that way, but you might find that 
> > others would prefer some sort of Notification package for 
> > this type of thing.
> > 
> > /Hisham
> > 
> > > -----Original Message-----
> > > From: ext Drage, Keith (Keith) [mailto:drage@lucent.com]
> > > Sent: Monday, September 02, 2002 8:02 PM
> > > To: Kiss Krisztian (NRC/Tampere); Drage, Keith (Keith); 
> sip@ietf.org
> > > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > > information
> > > to the user
> > > 
> > > 
> > > With hindsight, I drafted the last paragraph of my original 
> > > message badly.
> > > 
> > > Rather than try to paraphrase again, I will select a direct 
> > > quote from the message draft abstract:
> > > 
> > > The MESSAGE method is an extension to the Session 
> > Initiation Protocol
> > >    (SIP) that allows the transfer of Instant Messages.  
> > > MESSAGE requests
> > >    carry the content in the form of MIME body parts.  
> > > 
> > > My concern is not over how such a body should be coded. The 
> > > questions is does such a usage to carry "Please top up your 
> > > units or your call may be terminated prematurely" qualify as 
> > > an Instant Message, i.e. is it within the semantics of 
> > > MESSAGE to perform this function.
> > > 
> > > Keith
> > > 
> > > > -----Original Message-----
> > > > From: krisztian.kiss@nokia.com [mailto:krisztian.kiss@nokia.com]
> > > > Sent: 02 September 2002 17:43
> > > > To: drage@lucent.com; sip@ietf.org
> > > > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > > > information
> > > > to the user
> > > > 
> > > > 
> > > > 
> > > > Keith,
> > > > 
> > > > > Within 3GPP, there is a requirement for intermediate servers 
> > > > > to pass textual information for display to the user. This may 
> > > > > be related to a dialog or not.
> > > > > 
> > > > > A typical example may be (in the case of a prepay user):
> > > > > 
> > > > > "Please top up your units or your call may be terminated 
> > > > prematurely".
> > > > > 
> > > > > There are a number of methods that are defined which 
> > > > > essentially convey body information between User Agents 
> > > > > (INFO, NOTIFY, MESSAGE, PUBLISH?).
> > > > > 
> > > > > Some of these would appear more suitable that others for 
> > > > > passing this information. 
> > > > > 
> > > > > Of the existing methods, MESSAGE would appear to be the most 
> > > > > suitable (and indeed is the one selected by some of the 
> > > > > experts involved). However the internet draft specifically 
> > > > > talks about the body being an "Instant Message".
> > > > 
> > > > draft-ietf-sip-message-06 states that the body can be of ANY 
> > > > MIME type:
> > > > "The body of the request will contain the message to be 
> delivered.
> > > >    This body can be of any MIME type, including message/cpim."
> > > > 
> > > > Regards,
> > > > Krisztian
> > > > 
> > > > 
> > > > > Rather than get into a situation similar to that which 
> > > > > affects INFO (i.e. people seem to have implemented various 
> > > > > applications on INFO and IETF experts say INFO is not 
> > > > > appropriate for that application), could I request an 
> > > > > exchange of views on the applicability or not of MESSAGE for 
> > > > > this type of information, and if not, what solution would 
> > > > > otherwise be suggested.
> > > > > 
> > > > > Note that the information would normally be expected to come 
> > > > > from some network based entity (acting as a UA). When related 
> > > > > to a dialog, the source may well be some B2BUA between the 
> > > > > two end UAs involved in the dialog.
> > > > > 
> > > > > Keith Drage
> > > > > _______________________________________________
> > > > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > > > > This list is for NEW development of the core SIP Protocol
> > > > > Use sip-implementors@cs.columbia.edu for questions on 
> > current sip
> > > > > Use sipping@ietf.org for new developments on the 
> > > application of sip
> > > > > 
> > > > 
> > > _______________________________________________
> > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > > This list is for NEW development of the core SIP Protocol
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sipping@ietf.org for new developments on the 
> application of sip
> > > 
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> > 
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Tue Sep  3 04:57:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19471
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 04:57:12 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g838wSr09463
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 04:58:28 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g838wAo09439;
	Tue, 3 Sep 2002 04:58:10 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g838vao09409
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 04:57:36 -0400
Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19458
	for <sip@ietf.org>; Tue, 3 Sep 2002 04:55:49 -0400 (EDT)
From: aki.niemi@nokia.com
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g838vP717426
	for <sip@ietf.org>; Tue, 3 Sep 2002 11:57:25 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5d1c07fd79ac158f24140@esvir04nok.ntc.nokia.com>;
 Tue, 3 Sep 2002 11:57:24 +0300
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 3 Sep 2002 11:57:24 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] use of MESSAGE method for passing display information to the user
Date: Tue, 3 Sep 2002 11:56:44 +0300
Message-ID: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD9010FE419@esebe013.ntc.nokia.com>
Thread-Topic: [Sip] use of MESSAGE method for passing display information to the user
Thread-Index: AcJSox27Cjscq69xTriAOy2WQ6dsQwAd8OsQAACU5cAAAjI6kAAAW9EQ
To: <hisham.khartabil@nokia.com>, <drage@lucent.com>,
        <krisztian.kiss@nokia.com>, <sip@ietf.org>
X-OriginalArrivalTime: 03 Sep 2002 08:57:24.0064 (UTC) FILETIME=[EB8EF600:01C25327]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g838vao09410
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Is it feasible to have that subscription state hanging around just in case you may some day run out of credit?

Cheers,
Aki

> -----Original Message-----
> From: Khartabil Hisham (NMP/Helsinki) 
> Sent: Tuesday, September 03, 2002 11:49 AM
> To: Niemi Aki (NET/Espoo); drage@lucent.com; Kiss Krisztian
> (NRC/Tampere); sip@ietf.org
> Subject: RE: [Sip] use of MESSAGE method for passing display 
> information
> to the user
> 
> 
> You're not subscribing to get an instant message, you're 
> subscribing to get information about your prepaid units.
> 
> Why is it unsolicited? 
> 
> /Hisham
> 
> > -----Original Message-----
> > From: Niemi Aki (NET/Espoo) 
> > Sent: Tuesday, September 03, 2002 10:47 AM
> > To: Khartabil Hisham (NMP/Helsinki); drage@lucent.com; Kiss 
> Krisztian
> > (NRC/Tampere); sip@ietf.org
> > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > information
> > to the user
> > 
> > 
> > This application seems rather different from the presence 
> > type notifications because it seems these notifications are 
> > unsolicited. So to me MESSAGE seems like a perfect fit. I 
> > don't have to "subscribe" in order to receive instant 
> messages either.
> > 
> > So by saying "Notification package" perhaps you mean a new 
> > MIME type specifically for these unsolicited notifications?
> > 
> > Cheers,
> > Aki
> > 
> > > -----Original Message-----
> > > From: ext hisham.khartabil@nokia.com 
> > > [mailto:hisham.khartabil@nokia.com]
> > > Sent: Tuesday, September 03, 2002 10:26 AM
> > > To: drage@lucent.com; Kiss Krisztian (NRC/Tampere); sip@ietf.org
> > > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > > information
> > > to the user
> > > 
> > > 
> > > I guess it could be done that way, but you might find that 
> > > others would prefer some sort of Notification package for 
> > > this type of thing.
> > > 
> > > /Hisham
> > > 
> > > > -----Original Message-----
> > > > From: ext Drage, Keith (Keith) [mailto:drage@lucent.com]
> > > > Sent: Monday, September 02, 2002 8:02 PM
> > > > To: Kiss Krisztian (NRC/Tampere); Drage, Keith (Keith); 
> > sip@ietf.org
> > > > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > > > information
> > > > to the user
> > > > 
> > > > 
> > > > With hindsight, I drafted the last paragraph of my original 
> > > > message badly.
> > > > 
> > > > Rather than try to paraphrase again, I will select a direct 
> > > > quote from the message draft abstract:
> > > > 
> > > > The MESSAGE method is an extension to the Session 
> > > Initiation Protocol
> > > >    (SIP) that allows the transfer of Instant Messages.  
> > > > MESSAGE requests
> > > >    carry the content in the form of MIME body parts.  
> > > > 
> > > > My concern is not over how such a body should be coded. The 
> > > > questions is does such a usage to carry "Please top up your 
> > > > units or your call may be terminated prematurely" qualify as 
> > > > an Instant Message, i.e. is it within the semantics of 
> > > > MESSAGE to perform this function.
> > > > 
> > > > Keith
> > > > 
> > > > > -----Original Message-----
> > > > > From: krisztian.kiss@nokia.com 
> [mailto:krisztian.kiss@nokia.com]
> > > > > Sent: 02 September 2002 17:43
> > > > > To: drage@lucent.com; sip@ietf.org
> > > > > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > > > > information
> > > > > to the user
> > > > > 
> > > > > 
> > > > > 
> > > > > Keith,
> > > > > 
> > > > > > Within 3GPP, there is a requirement for 
> intermediate servers 
> > > > > > to pass textual information for display to the 
> user. This may 
> > > > > > be related to a dialog or not.
> > > > > > 
> > > > > > A typical example may be (in the case of a prepay user):
> > > > > > 
> > > > > > "Please top up your units or your call may be terminated 
> > > > > prematurely".
> > > > > > 
> > > > > > There are a number of methods that are defined which 
> > > > > > essentially convey body information between User Agents 
> > > > > > (INFO, NOTIFY, MESSAGE, PUBLISH?).
> > > > > > 
> > > > > > Some of these would appear more suitable that others for 
> > > > > > passing this information. 
> > > > > > 
> > > > > > Of the existing methods, MESSAGE would appear to be 
> the most 
> > > > > > suitable (and indeed is the one selected by some of the 
> > > > > > experts involved). However the internet draft specifically 
> > > > > > talks about the body being an "Instant Message".
> > > > > 
> > > > > draft-ietf-sip-message-06 states that the body can be of ANY 
> > > > > MIME type:
> > > > > "The body of the request will contain the message to be 
> > delivered.
> > > > >    This body can be of any MIME type, including message/cpim."
> > > > > 
> > > > > Regards,
> > > > > Krisztian
> > > > > 
> > > > > 
> > > > > > Rather than get into a situation similar to that which 
> > > > > > affects INFO (i.e. people seem to have implemented various 
> > > > > > applications on INFO and IETF experts say INFO is not 
> > > > > > appropriate for that application), could I request an 
> > > > > > exchange of views on the applicability or not of 
> MESSAGE for 
> > > > > > this type of information, and if not, what solution would 
> > > > > > otherwise be suggested.
> > > > > > 
> > > > > > Note that the information would normally be 
> expected to come 
> > > > > > from some network based entity (acting as a UA). 
> When related 
> > > > > > to a dialog, the source may well be some B2BUA between the 
> > > > > > two end UAs involved in the dialog.
> > > > > > 
> > > > > > Keith Drage
> > > > > > _______________________________________________
> > > > > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > > > > > This list is for NEW development of the core SIP Protocol
> > > > > > Use sip-implementors@cs.columbia.edu for questions on 
> > > current sip
> > > > > > Use sipping@ietf.org for new developments on the 
> > > > application of sip
> > > > > > 
> > > > > 
> > > > _______________________________________________
> > > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > > > This list is for NEW development of the core SIP Protocol
> > > > Use sip-implementors@cs.columbia.edu for questions on 
> current sip
> > > > Use sipping@ietf.org for new developments on the 
> > application of sip
> > > > 
> > > _______________________________________________
> > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > > This list is for NEW development of the core SIP Protocol
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sipping@ietf.org for new developments on the 
> application of sip
> > > 
> > 
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Tue Sep  3 07:36:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22171
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 07:36:17 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g83BbMv17928
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 07:37:22 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83Ba5o17347;
	Tue, 3 Sep 2002 07:36:05 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83BU2o17120
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 07:30:02 -0400
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21724
	for <sip@ietf.org>; Tue, 3 Sep 2002 07:28:24 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g83BTrrU017450;
	Tue, 3 Sep 2002 13:29:53 +0200 (MEST)
Received: from ericsson.com (3NJPI0013L1IJOG.lmf.ericsson.se [131.160.30.102])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g83BTqpk013192;
	Tue, 3 Sep 2002 14:29:52 +0300 (EET DST)
Message-ID: <3D749D2F.DA898F33@ericsson.com>
Date: Tue, 03 Sep 2002 14:29:51 +0300
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
Organization: OY LM Ericsson AB
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: "Drage, Keith (Keith)" <drage@lucent.com>
CC: "'krisztian.kiss@nokia.com'" <krisztian.kiss@nokia.com>, sip@ietf.org
Subject: Re: [Sip] use of MESSAGE method for passing display information to the 
 user
References: <475FF955A05DD411980D00508B6D5FB00439EA95@en0033exch001u.uk.lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Keith:

I have found some hints into the message draft that makes me think this is the appropriate usage of the method. This hints are:

    The MESSAGE method is an extension to the Session Initiation Protocol
   (SIP) that allows the transfer of Instant Messages. 

I guess instant message is a message delivered instantly to the user, and displayed to the user.

    All UAs which support the MESSAGE method MUST be prepared to send and
    receive MESSAGE requests with a body of type text/plain.

Text/plain seems to be textual information that can be displayed to a user.
If it was message/sipfrag, perhaps the information wasn't intended to be
delivered to the user, but text/plain seems to be unformatted information
intended to be readable by a human being.

   Normally, a 200 OK
   response will be generated by the user agent of the request's final
   recipient.  Note that this indicates that the user agent accepted the
   message, not that the user has seen it.

This again suggest that the payload of the MESSAGE method is typically
displayed to the user.

All these hints, make me think that your usage example seems to be a correct
usage of the MESSAGE method.

/Miguel

"Drage, Keith (Keith)" wrote:
> 
> With hindsight, I drafted the last paragraph of my original message badly.
> 
> Rather than try to paraphrase again, I will select a direct quote from the message draft abstract:
> 
> The MESSAGE method is an extension to the Session Initiation Protocol
>    (SIP) that allows the transfer of Instant Messages.  MESSAGE requests
>    carry the content in the form of MIME body parts.
> 
> My concern is not over how such a body should be coded. The questions is does such a usage to carry "Please top up your units or your call may be terminated prematurely" qualify as an Instant Message, i.e. is it within the semantics of MESSAGE to perform this function.
> 
> Keith
> 
> > -----Original Message-----
> > From: krisztian.kiss@nokia.com [mailto:krisztian.kiss@nokia.com]
> > Sent: 02 September 2002 17:43
> > To: drage@lucent.com; sip@ietf.org
> > Subject: RE: [Sip] use of MESSAGE method for passing display
> > information
> > to the user
> >
> >
> >
> > Keith,
> >
> > > Within 3GPP, there is a requirement for intermediate servers
> > > to pass textual information for display to the user. This may
> > > be related to a dialog or not.
> > >
> > > A typical example may be (in the case of a prepay user):
> > >
> > > "Please top up your units or your call may be terminated
> > prematurely".
> > >
> > > There are a number of methods that are defined which
> > > essentially convey body information between User Agents
> > > (INFO, NOTIFY, MESSAGE, PUBLISH?).
> > >
> > > Some of these would appear more suitable that others for
> > > passing this information.
> > >
> > > Of the existing methods, MESSAGE would appear to be the most
> > > suitable (and indeed is the one selected by some of the
> > > experts involved). However the internet draft specifically
> > > talks about the body being an "Instant Message".
> >
> > draft-ietf-sip-message-06 states that the body can be of ANY
> > MIME type:
> > "The body of the request will contain the message to be delivered.
> >    This body can be of any MIME type, including message/cpim."
> >
> > Regards,
> > Krisztian
> >
> >
> > > Rather than get into a situation similar to that which
> > > affects INFO (i.e. people seem to have implemented various
> > > applications on INFO and IETF experts say INFO is not
> > > appropriate for that application), could I request an
> > > exchange of views on the applicability or not of MESSAGE for
> > > this type of information, and if not, what solution would
> > > otherwise be suggested.
> > >
> > > Note that the information would normally be expected to come
> > > from some network based entity (acting as a UA). When related
> > > to a dialog, the source may well be some B2BUA between the
> > > two end UAs involved in the dialog.
> > >
> > > Keith Drage
> > > _______________________________________________
> > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > > This list is for NEW development of the core SIP Protocol
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sipping@ietf.org for new developments on the application of sip
> > >
> >
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Tue Sep  3 09:57:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27252
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 09:57:19 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g83DwRT25401
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 09:58:27 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83DuYo25265;
	Tue, 3 Sep 2002 09:56:34 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83DnXo24942
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 09:49:33 -0400
Received: from acmepacket.com (mail1.acmepacket.com [63.67.143.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26608
	for <sip@ietf.org>; Tue, 3 Sep 2002 09:47:54 -0400 (EDT)
Received: from BPenfield [63.67.143.2] by acmepacket.com
  (SMTPD32-7.07) id ADE89B60005A; Tue, 03 Sep 2002 09:49:28 -0400
Message-ID: <00e701c25350$b5a7b030$2300000a@BPenfield>
From: "Bob Penfield" <bpenfield@acmepacket.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>, <sip@ietf.org>
References: <3D6EACB3.CC2C8F04@cisco.com>
Subject: Re: [Sip] Re: RFC 3264  An Offer/Answer Model Session Description Protocol
Date: Tue, 3 Sep 2002 09:49:22 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: "Paul Kyzivat" <pkyzivat@cisco.com>


> I have a question of interpretation regarding section 8.3.2 (Changing the
Set of Media Formats).
>
> When describing how an offer is to be constructed for a change (a
reINVITE), this section says:
>
> "However, in the case of RTP, the mapping from a particular dynamic
payload type number to a particular codec within that media stream MUST NOT
change for the duration of a session.  For example, if A generates an offer
with G.711 assigned to dynamic payload type number 46, payload type number
46 MUST refer to G.711 from that point forward in any offers or answers for
that media stream within the session."
>
> What I question is the "or answers" at the end of this section. This seems
to be inconsistent with section 6.1, which says that the payload type
numbers for answers may be different than those for offers.
>

I believe it is talking about any offers or answers that a given endpoint
generates during the session since either side may re-INVITE. The two side
may use different payload numbers, but each has to use its same original
payload number in all SDP it generates.



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



From mailnull@www1.ietf.org  Tue Sep  3 11:19:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00869
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 11:19:12 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g83FKLj05528
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 11:20:21 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83FJZo05446;
	Tue, 3 Sep 2002 11:19:35 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83FD1o17661
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 11:13:01 -0400
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00402
	for <sip@ietf.org>; Tue, 3 Sep 2002 11:11:22 -0400 (EDT)
Received: from cannon.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g83FCVjI010759;
	Tue, 3 Sep 2002 11:12:31 -0400 (EDT)
Received: from cisco.com (dhcp-161-44-241-140.cisco.com [161.44.241.140])
	by cannon.cisco.com (Mirapoint)
	with ESMTP id AAQ13950;
	Tue, 3 Sep 2002 11:17:06 -0400 (EDT)
Message-ID: <3D74D154.4279B5DB@cisco.com>
Date: Tue, 03 Sep 2002 11:12:20 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD   (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Bob Penfield <bpenfield@acmepacket.com>
CC: sip@ietf.org
Subject: Re: [Sip] Re: RFC 3264  An Offer/Answer Model Session Description 
 Protocol
References: <3D6EACB3.CC2C8F04@cisco.com> <00e701c25350$b5a7b030$2300000a@BPenfield>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Bob - OK, if you read it that way then all is ok.
It wasn't obvious to me that this is what that text
intended, but since it is only an example I guess it
is good enough.

	Thanks,
	Paul

Bob Penfield wrote:
> 
> ----- Original Message -----
> From: "Paul Kyzivat" <pkyzivat@cisco.com>
> 
> > I have a question of interpretation regarding section 8.3.2 (Changing the
> Set of Media Formats).
> >
> > When describing how an offer is to be constructed for a change (a
> reINVITE), this section says:
> >
> > "However, in the case of RTP, the mapping from a particular dynamic
> payload type number to a particular codec within that media stream MUST NOT
> change for the duration of a session.  For example, if A generates an offer
> with G.711 assigned to dynamic payload type number 46, payload type number
> 46 MUST refer to G.711 from that point forward in any offers or answers for
> that media stream within the session."
> >
> > What I question is the "or answers" at the end of this section. This seems
> to be inconsistent with section 6.1, which says that the payload type
> numbers for answers may be different than those for offers.
> >
> 
> I believe it is talking about any offers or answers that a given endpoint
> generates during the session since either side may re-INVITE. The two side
> may use different payload numbers, but each has to use its same original
> payload number in all SDP it generates.
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Tue Sep  3 12:11:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02850
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 12:11:59 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g83GD7o09550
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 12:13:07 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83GCNo09505;
	Tue, 3 Sep 2002 12:12:23 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83G9Fo09356
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 12:09:15 -0400
Received: from magus.nostrum.com (root@magus.nostrum.com [66.119.225.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02615
	for <sip@ietf.org>; Tue, 3 Sep 2002 12:07:36 -0400 (EDT)
Received: from dynamicsoft.com (root@magus.nostrum.com [66.119.225.66])
	by magus.nostrum.com (8.12.5/8.12.5) with ESMTP id g83G94pA065185;
	Tue, 3 Sep 2002 11:09:04 -0500 (CDT)
Message-ID: <3D74DE80.60208@dynamicsoft.com>
Date: Tue, 03 Sep 2002 11:08:32 -0500
From: Ben Campbell <bcampbell@dynamicsoft.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Drage, Keith (Keith)" <drage@lucent.com>
CC: "'sip@ietf.org'" <sip@ietf.org>
Subject: Re: [Sip] use of MESSAGE method for passing display information to
 the user
References: <475FF955A05DD411980D00508B6D5FB00439EA93@en0033exch001u.uk.lucent.com>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

This seems to me to be an entirely appropriate use of page mode MESSAGE. 
Specifically, I would interpret a message, sent by an automaton, that is 
intended to be rendered for and interpreted by a human being in a timely 
manner, to fall into the category of "instant message."



Drage, Keith (Keith) wrote:
> Within 3GPP, there is a requirement for intermediate servers to pass textual information for display to the user. This may be related to a dialog or not.
> 
> A typical example may be (in the case of a prepay user):
> 
> "Please top up your units or your call may be terminated prematurely".
> 
> There are a number of methods that are defined which essentially convey body information between User Agents (INFO, NOTIFY, MESSAGE, PUBLISH?).
> 
> Some of these would appear more suitable that others for passing this information. 
> 
> Of the existing methods, MESSAGE would appear to be the most suitable (and indeed is the one selected by some of the experts involved). However the internet draft specifically talks about the body being an "Instant Message".
> 
> Rather than get into a situation similar to that which affects INFO (i.e. people seem to have implemented various applications on INFO and IETF experts say INFO is not appropriate for that application), could I request an exchange of views on the applicability or not of MESSAGE for this type of information, and if not, what solution would otherwise be suggested.
> 
> Note that the information would normally be expected to come from some network based entity (acting as a UA). When related to a dialog, the source may well be some B2BUA between the two end UAs involved in the dialog.
> 
> Keith Drage
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 


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



From mailnull@www1.ietf.org  Tue Sep  3 14:08:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07793
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 14:08:40 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g83I9nL10497
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 14:09:49 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83I9Wo10482;
	Tue, 3 Sep 2002 14:09:32 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83I4Uo09778
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 14:04:30 -0400
Received: from mail2.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07591
	for <sip@ietf.org>; Tue, 3 Sep 2002 14:02:51 -0400 (EDT)
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail2.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id g83I377p005769;
	Tue, 3 Sep 2002 14:03:08 -0400 (EDT)
Received: by DYN-TX-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <R5G8ZBVN>; Tue, 3 Sep 2002 13:03:40 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3A640CC@DYN-TX-EXCH-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Tirthankar Saha'" <tsaha@del3.vsnl.net.in>,
        Adam Roach
	 <adam@dynamicsoft.com>, SIP Mailing List <sip@ietf.org>
Subject: RE: [Sip] Session Timer Issues and Proposal
Date: Tue, 3 Sep 2002 13:03:37 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

> From: Tirthankar Saha [mailto:tsaha@del3.vsnl.net.in]
> 
> Adam, it's true that the strategy is uniform but what I 
> wanted to say is
> that we have to implement the same thing differently for 
> different methods.
> It'd better having one single message which can refresh 
> different types of
> dialogs/sessions. Consider the case of a dialog-stateful 
> proxy: it has to be
> aware of the separate keep-alive mechanisms of SUBSCRIBE, INVITE etc.
> dialogs. Now suppose a new method is introduced with its own 
> keep-alive
> mechanism, the proxy has to be updated to account for this.

This, too, is an age old debate: does a proxy have any business
tracking dialogs it does not understand? This has been brought
up repeatedly, and consensus has been consistent throughout the
years: no.

If a proxy knows how a method behaves, it makes perfect sense to
track various related state. For new methods with which the proxy
is unfamiliar, a proxy assigns no semantics. It doesn't know whether
unknown requests have the ability to start, extend, modify, or end
a dialog. New methods may necessarily decide to implement their
own rules about dialog handling to suit whatever purpose the method
is being created for. Can we predict the behavior of all such
methods? Of course not -- otherwise, we'd define them all right now
and not worry about making the protocol extensible. But, to paraphrase
one of Dave Oran's maxims: events are always hard to predict,
especially when they involve the future.

While the principle you advocate is admirable, it cannot be
implemented in such a way that will stand the test of time.

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



From mailnull@www1.ietf.org  Tue Sep  3 14:32:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08649
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 14:32:46 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g83IXut14106
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 14:33:56 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83IXZo14079;
	Tue, 3 Sep 2002 14:33:35 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83IUZo13924
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 14:30:35 -0400
Received: from mail2.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08500
	for <sip@ietf.org>; Tue, 3 Sep 2002 14:28:56 -0400 (EDT)
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail2.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id g83ITO7p005944;
	Tue, 3 Sep 2002 14:29:25 -0400 (EDT)
Received: by DYN-TX-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <R5G8ZBVV>; Tue, 3 Sep 2002 13:29:57 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3A640CD@DYN-TX-EXCH-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Drage, Keith (Keith)'" <drage@lucent.com>,
        "'sip@ietf.org'"
	 <sip@ietf.org>
Subject: RE: [Sip] use of MESSAGE method for passing display information t
	o the user
Date: Tue, 3 Sep 2002 13:29:55 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

As long as MESSAGE carries content which is intended to be
rendered to the party to whom it is addressed, I assert
that it is serving its intended purpose. The purposes
you describe below meet these criteria compeletely.

Ignoring the other problems with using INFO, it does not
meet your requirement that the information to be conveyed
may not be related to a dialog.

NOTIFY would require definition of event packages for
every sort of information you'd want to convey, which is
probably not what you want. On the other hand, there is
already work ongoing for message waiting indication. For
this sort of notification in particular, it would make
great sense for 3GPP to use SUBSCRIBE/NOTIFY.

PUBLISH is meant for publication of event package state 
information to an event agent, not general publication
of data. Its use in this context would be gross
misapplication of that method. (If you want a mechanism
for general publication of data, you need to check out
WEBDAV).

/a

> -----Original Message-----
> From: Drage, Keith (Keith) [mailto:drage@lucent.com]
> Sent: Monday, September 02, 2002 10:40
> To: 'sip@ietf.org'
> Subject: [Sip] use of MESSAGE method for passing display 
> information to
> the user
> 
> 
> Within 3GPP, there is a requirement for intermediate servers 
> to pass textual information for display to the user. This may 
> be related to a dialog or not.
> 
> A typical example may be (in the case of a prepay user):
> 
> "Please top up your units or your call may be terminated prematurely".
> 
> There are a number of methods that are defined which 
> essentially convey body information between User Agents 
> (INFO, NOTIFY, MESSAGE, PUBLISH?).
> 
> Some of these would appear more suitable that others for 
> passing this information. 
> 
> Of the existing methods, MESSAGE would appear to be the most 
> suitable (and indeed is the one selected by some of the 
> experts involved). However the internet draft specifically 
> talks about the body being an "Instant Message".
> 
> Rather than get into a situation similar to that which 
> affects INFO (i.e. people seem to have implemented various 
> applications on INFO and IETF experts say INFO is not 
> appropriate for that application), could I request an 
> exchange of views on the applicability or not of MESSAGE for 
> this type of information, and if not, what solution would 
> otherwise be suggested.
> 
> Note that the information would normally be expected to come 
> from some network based entity (acting as a UA). When related 
> to a dialog, the source may well be some B2BUA between the 
> two end UAs involved in the dialog.
> 
> Keith Drage
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Tue Sep  3 16:18:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12919
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 16:18:08 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g83KJJU21345
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 16:19:19 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83KIvo21290;
	Tue, 3 Sep 2002 16:18:57 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83KFbo21165
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 16:15:37 -0400
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12818
	for <sip@ietf.org>; Tue, 3 Sep 2002 16:13:56 -0400 (EDT)
Received: from TXDWILLIS2 (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with ESMTP id g83KF8323493
	for <sip@ietf.org>; Tue, 3 Sep 2002 15:15:08 -0500
From: "Dean Willis" <dean.willis@softarmor.com>
To: <sip@ietf.org>
Date: Tue, 3 Sep 2002 15:14:45 -0500
Message-ID: <006901c25386$8bead020$1e036e3f@TXDWILLIS2>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Sip] FW:SIP MESSAGE Discussion from 3GPP CN-1 Mailing List
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


I had already responded to Keith's inqury on MESSAGE as raised in the
CN-1 list before I noticed he had also raised it on the SIP list. Here's
my response, just in case anybody cares . . .

-----Original Message-----
From: Dean Willis [mailto:dean.willis@softarmor.com] 
Sent: Tuesday, September 03, 2002 2:16 PM
To: 'Drage, Keith (Keith)'; '3GPP_TSG_CN_WG1@LIST.ETSI.FR'
Cc: 'jdrosen@dynamicsoft.com'
Subject: RE: N1-021814 (Adding MESSAGE to 24.229)


> -----Original Message-----
Keith wrote:
> I am currently seeking clarification as to whether this is
> the right SIP method to use for this function or not. (My 
> concern in this area is that MESSAGE semantics are defined as 
> loosely as those of INFO, and acceptable INFO usage now seems 
> to be restricted only to applications discussed and endorsed 
> within IETF - a view that seems to have evolved after the RFC 
> was published). Based on the result, I will either propose 
> revisions or propose an alternative strategy for dealing with 
> the requirement in 23.228 subclause 5.4.9. I would point out 
> that any revision is likely to be "substantial" rather than a 
> "refinement".


The current IETF position is that MESSAGE is appropriate for material
that will be rendered and displayed directly to a human user. It is
considered to be less appropriate, and debatably INappropriate, for
inter-machine communications. Fundamentally, MESSAGE is NOT an RPC
mechanism, it's for talking to people.

Here's an example. Let's say that an application wants to send
unstructured text to a user, informing the user about the state of the
application -- perhaps "It is Tuesday. Call your Mother." MESSAGE is
probably very appropriate for this usage.

On the other hand, assume that a voice mail application wishes to
communicate with a user's phone in such a way that the "you have Voice
Mail" light is illuminated on the phone, if the phone has such a light.
This is a more structured piece of information. It relies on explicit
knowledge of the capabilities of the phone (for example, does it have
the ability to display this sort of notification?) , and is probably not
appropriate for  MESSAGE. In fact, there is ongoing work in SIPPING to
define this specific behavior using an "event package". You can read
about it in Rohan's Message Waiting draft: 

http://www.ietf.org/internet-drafts/draft-ietf-sipping-mwi-00.txt

Event packages allow the structured content needed for machine
processing to be explicitly defined, making them far more likely to
provide interoperable behavior.

INFO is problematic. The only generally accepted use of INFO currently
in IETF is its use to support mid-call signaling in PSTN interworking
scenarios. This behavior and usage is defined by the SIP-T drafts.
Current thinking is leaning towards either deprecating INFO for other
tasks (define it to have a role only in SIP-T), or to define an "INFO
Package" model so that new usages of INFO can be effectively
standardized. The authors of INFO are leaning towards the SIP-T-only
approach. The IETF does not endorse arbitrary usage of INFO with
proprietary payloads, as such usage is by definition proprietary and not
interoperable.

There have been suggestions made that MESSAGE could be used for carrying
machine-readable structured information if the format and semantic of
the structured information are appropriately specified in an RFC. While
this approach may proceed, it is still under discussion and there is no
firm consensus for this approach at this time.

Guidance to 3GPP, unil further notice: Where the transmitted information
is to be presented to the user and explicit understanding of the
informations's semantic is not required in the phone, use MESSAGE. Where
these conditions are not met, use something else. In many (but not all)
cases, an event package will be an appropriate alternatve.

--
dean

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



From mailnull@www1.ietf.org  Tue Sep  3 17:11:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14426
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 17:11:44 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g83LCuR24833
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 17:12:56 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83LAso24708;
	Tue, 3 Sep 2002 17:10:54 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83H0ao06216
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 13:00:36 -0400
Received: from stamail.telecom.sna.samsung.com (mail1.sta.samsung.com [63.166.115.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04895
	for <sip@ietf.org>; Tue, 3 Sep 2002 12:58:57 -0400 (EDT)
Received: by stamail.telecom.sna.samsung.com with Internet Mail Service (5.5.2653.19)
	id <QCTY4DNY>; Tue, 3 Sep 2002 12:00:10 -0500
Message-ID: <4B9386E83999D411997100508BAF206A061F506C@stamail.telecom.sna.samsung.com>
From: Kedar Patil <kpatil@sta.samsung.com>
To: "'aki.niemi@nokia.com'" <aki.niemi@nokia.com>, hisham.khartabil@nokia.com,
        drage@lucent.com, krisztian.kiss@nokia.com
Cc: sip@ietf.org
Subject: RE: [Sip] use of MESSAGE method for passing display information t
	o the user
Date: Tue, 3 Sep 2002 12:00:10 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2536B.5CAAAAD0"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

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_001_01C2536B.5CAAAAD0
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,

I have some input on having event-notification package
for this :

Although it looks like a user may have to subscribe to
"Credit overflow" kind of event all the time, I guess
this is going to be only during the calls.

This one case may be solved by "MESSAGE". However, is it the
only case? I believe there could be more. The commonality
is that all of them are going to be from the network (not the
peer) and are asynchrounous. For this why not have an event
pacakge under the framework of RFC3265. A UA may subscribe
to network of all network events, and any such event would
trigger the appropriate event notification.

If all the events are for human interaction then "Message"
looks fine. Is there any event where user interaction is
taken over by automatic actions by s/w config? (e.g. in this
case automatic credit upgrade just enough to avoid premature
call termination!)

The question remains : Is there one network element to which
a UA may have to subscribe or many?

thanks,
= Kedar =


> -----Original Message-----
> From: aki.niemi@nokia.com [mailto:aki.niemi@nokia.com]
> Sent: Tuesday, September 03, 2002 3:57 AM
> To: hisham.khartabil@nokia.com; drage@lucent.com;
> krisztian.kiss@nokia.com; sip@ietf.org
> Subject: RE: [Sip] use of MESSAGE method for passing display 
> information
> to the user
> 
> 
> Is it feasible to have that subscription state hanging around 
> just in case you may some day run out of credit?
> 
> Cheers,
> Aki
> 
> > -----Original Message-----
> > From: Khartabil Hisham (NMP/Helsinki) 
> > Sent: Tuesday, September 03, 2002 11:49 AM
> > To: Niemi Aki (NET/Espoo); drage@lucent.com; Kiss Krisztian
> > (NRC/Tampere); sip@ietf.org
> > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > information
> > to the user
> > 
> > 
> > You're not subscribing to get an instant message, you're 
> > subscribing to get information about your prepaid units.
> > 
> > Why is it unsolicited? 
> > 
> > /Hisham
> > 
> > > -----Original Message-----
> > > From: Niemi Aki (NET/Espoo) 
> > > Sent: Tuesday, September 03, 2002 10:47 AM
> > > To: Khartabil Hisham (NMP/Helsinki); drage@lucent.com; Kiss 
> > Krisztian
> > > (NRC/Tampere); sip@ietf.org
> > > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > > information
> > > to the user
> > > 
> > > 
> > > This application seems rather different from the presence 
> > > type notifications because it seems these notifications are 
> > > unsolicited. So to me MESSAGE seems like a perfect fit. I 
> > > don't have to "subscribe" in order to receive instant 
> > messages either.
> > > 
> > > So by saying "Notification package" perhaps you mean a new 
> > > MIME type specifically for these unsolicited notifications?
> > > 
> > > Cheers,
> > > Aki
> > > 
> > > > -----Original Message-----
> > > > From: ext hisham.khartabil@nokia.com 
> > > > [mailto:hisham.khartabil@nokia.com]
> > > > Sent: Tuesday, September 03, 2002 10:26 AM
> > > > To: drage@lucent.com; Kiss Krisztian (NRC/Tampere); sip@ietf.org
> > > > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > > > information
> > > > to the user
> > > > 
> > > > 
> > > > I guess it could be done that way, but you might find that 
> > > > others would prefer some sort of Notification package for 
> > > > this type of thing.
> > > > 
> > > > /Hisham
> > > > 
> > > > > -----Original Message-----
> > > > > From: ext Drage, Keith (Keith) [mailto:drage@lucent.com]
> > > > > Sent: Monday, September 02, 2002 8:02 PM
> > > > > To: Kiss Krisztian (NRC/Tampere); Drage, Keith (Keith); 
> > > sip@ietf.org
> > > > > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > > > > information
> > > > > to the user
> > > > > 
> > > > > 
> > > > > With hindsight, I drafted the last paragraph of my original 
> > > > > message badly.
> > > > > 
> > > > > Rather than try to paraphrase again, I will select a direct 
> > > > > quote from the message draft abstract:
> > > > > 
> > > > > The MESSAGE method is an extension to the Session 
> > > > Initiation Protocol
> > > > >    (SIP) that allows the transfer of Instant Messages.  
> > > > > MESSAGE requests
> > > > >    carry the content in the form of MIME body parts.  
> > > > > 
> > > > > My concern is not over how such a body should be coded. The 
> > > > > questions is does such a usage to carry "Please top up your 
> > > > > units or your call may be terminated prematurely" qualify as 
> > > > > an Instant Message, i.e. is it within the semantics of 
> > > > > MESSAGE to perform this function.
> > > > > 
> > > > > Keith
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: krisztian.kiss@nokia.com 
> > [mailto:krisztian.kiss@nokia.com]
> > > > > > Sent: 02 September 2002 17:43
> > > > > > To: drage@lucent.com; sip@ietf.org
> > > > > > Subject: RE: [Sip] use of MESSAGE method for 
> passing display 
> > > > > > information
> > > > > > to the user
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > Keith,
> > > > > > 
> > > > > > > Within 3GPP, there is a requirement for 
> > intermediate servers 
> > > > > > > to pass textual information for display to the 
> > user. This may 
> > > > > > > be related to a dialog or not.
> > > > > > > 
> > > > > > > A typical example may be (in the case of a prepay user):
> > > > > > > 
> > > > > > > "Please top up your units or your call may be terminated 
> > > > > > prematurely".
> > > > > > > 
> > > > > > > There are a number of methods that are defined which 
> > > > > > > essentially convey body information between User Agents 
> > > > > > > (INFO, NOTIFY, MESSAGE, PUBLISH?).
> > > > > > > 
> > > > > > > Some of these would appear more suitable that others for 
> > > > > > > passing this information. 
> > > > > > > 
> > > > > > > Of the existing methods, MESSAGE would appear to be 
> > the most 
> > > > > > > suitable (and indeed is the one selected by some of the 
> > > > > > > experts involved). However the internet draft 
> specifically 
> > > > > > > talks about the body being an "Instant Message".
> > > > > > 
> > > > > > draft-ietf-sip-message-06 states that the body can 
> be of ANY 
> > > > > > MIME type:
> > > > > > "The body of the request will contain the message to be 
> > > delivered.
> > > > > >    This body can be of any MIME type, including 
> message/cpim."
> > > > > > 
> > > > > > Regards,
> > > > > > Krisztian
> > > > > > 
> > > > > > 
> > > > > > > Rather than get into a situation similar to that which 
> > > > > > > affects INFO (i.e. people seem to have 
> implemented various 
> > > > > > > applications on INFO and IETF experts say INFO is not 
> > > > > > > appropriate for that application), could I request an 
> > > > > > > exchange of views on the applicability or not of 
> > MESSAGE for 
> > > > > > > this type of information, and if not, what solution would 
> > > > > > > otherwise be suggested.
> > > > > > > 
> > > > > > > Note that the information would normally be 
> > expected to come 
> > > > > > > from some network based entity (acting as a UA). 
> > When related 
> > > > > > > to a dialog, the source may well be some B2BUA 
> between the 
> > > > > > > two end UAs involved in the dialog.
> > > > > > > 
> > > > > > > Keith Drage
> > > > > > > _______________________________________________
> > > > > > > Sip mailing list  
https://www1.ietf.org/mailman/listinfo/sip
> > > > > > This list is for NEW development of the core SIP Protocol
> > > > > > Use sip-implementors@cs.columbia.edu for questions on 
> > > current sip
> > > > > > Use sipping@ietf.org for new developments on the 
> > > > application of sip
> > > > > > 
> > > > > 
> > > > _______________________________________________
> > > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > > > This list is for NEW development of the core SIP Protocol
> > > > Use sip-implementors@cs.columbia.edu for questions on 
> current sip
> > > > Use sipping@ietf.org for new developments on the 
> > application of sip
> > > > 
> > > _______________________________________________
> > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > > This list is for NEW development of the core SIP Protocol
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sipping@ietf.org for new developments on the 
> application of sip
> > > 
> > 
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip

------_=_NextPart_001_01C2536B.5CAAAAD0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>RE: [Sip] use of MESSAGE method for passing display information to the user</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Hi,</FONT>
</P>

<P><FONT SIZE=2>I have some input on having event-notification package</FONT>
<BR><FONT SIZE=2>for this :</FONT>
</P>

<P><FONT SIZE=2>Although it looks like a user may have to subscribe to</FONT>
<BR><FONT SIZE=2>&quot;Credit overflow&quot; kind of event all the time, I guess</FONT>
<BR><FONT SIZE=2>this is going to be only during the calls.</FONT>
</P>

<P><FONT SIZE=2>This one case may be solved by &quot;MESSAGE&quot;. However, is it the</FONT>
<BR><FONT SIZE=2>only case? I believe there could be more. The commonality</FONT>
<BR><FONT SIZE=2>is that all of them are going to be from the network (not the</FONT>
<BR><FONT SIZE=2>peer) and are asynchrounous. For this why not have an event</FONT>
<BR><FONT SIZE=2>pacakge under the framework of RFC3265. A UA may subscribe</FONT>
<BR><FONT SIZE=2>to network of all network events, and any such event would</FONT>
<BR><FONT SIZE=2>trigger the appropriate event notification.</FONT>
</P>

<P><FONT SIZE=2>If all the events are for human interaction then &quot;Message&quot;</FONT>
<BR><FONT SIZE=2>looks fine. Is there any event where user interaction is</FONT>
<BR><FONT SIZE=2>taken over by automatic actions by s/w config? (e.g. in this</FONT>
<BR><FONT SIZE=2>case automatic credit upgrade just enough to avoid premature</FONT>
<BR><FONT SIZE=2>call termination!)</FONT>
</P>

<P><FONT SIZE=2>The question remains : Is there one network element to which</FONT>
<BR><FONT SIZE=2>a UA may have to subscribe or many?</FONT>
</P>

<P><FONT SIZE=2>thanks,</FONT>
<BR><FONT SIZE=2>= Kedar =</FONT>
</P>
<BR>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; From: aki.niemi@nokia.com [<A HREF="mailto:aki.niemi@nokia.com">mailto:aki.niemi@nokia.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; Sent: Tuesday, September 03, 2002 3:57 AM</FONT>
<BR><FONT SIZE=2>&gt; To: hisham.khartabil@nokia.com; drage@lucent.com;</FONT>
<BR><FONT SIZE=2>&gt; krisztian.kiss@nokia.com; sip@ietf.org</FONT>
<BR><FONT SIZE=2>&gt; Subject: RE: [Sip] use of MESSAGE method for passing display </FONT>
<BR><FONT SIZE=2>&gt; information</FONT>
<BR><FONT SIZE=2>&gt; to the user</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Is it feasible to have that subscription state hanging around </FONT>
<BR><FONT SIZE=2>&gt; just in case you may some day run out of credit?</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Cheers,</FONT>
<BR><FONT SIZE=2>&gt; Aki</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; &gt; From: Khartabil Hisham (NMP/Helsinki) </FONT>
<BR><FONT SIZE=2>&gt; &gt; Sent: Tuesday, September 03, 2002 11:49 AM</FONT>
<BR><FONT SIZE=2>&gt; &gt; To: Niemi Aki (NET/Espoo); drage@lucent.com; Kiss Krisztian</FONT>
<BR><FONT SIZE=2>&gt; &gt; (NRC/Tampere); sip@ietf.org</FONT>
<BR><FONT SIZE=2>&gt; &gt; Subject: RE: [Sip] use of MESSAGE method for passing display </FONT>
<BR><FONT SIZE=2>&gt; &gt; information</FONT>
<BR><FONT SIZE=2>&gt; &gt; to the user</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; You're not subscribing to get an instant message, you're </FONT>
<BR><FONT SIZE=2>&gt; &gt; subscribing to get information about your prepaid units.</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Why is it unsolicited? </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; /Hisham</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; From: Niemi Aki (NET/Espoo) </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Sent: Tuesday, September 03, 2002 10:47 AM</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; To: Khartabil Hisham (NMP/Helsinki); drage@lucent.com; Kiss </FONT>
<BR><FONT SIZE=2>&gt; &gt; Krisztian</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; (NRC/Tampere); sip@ietf.org</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Subject: RE: [Sip] use of MESSAGE method for passing display </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; information</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; to the user</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; This application seems rather different from the presence </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; type notifications because it seems these notifications are </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; unsolicited. So to me MESSAGE seems like a perfect fit. I </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; don't have to &quot;subscribe&quot; in order to receive instant </FONT>
<BR><FONT SIZE=2>&gt; &gt; messages either.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; So by saying &quot;Notification package&quot; perhaps you mean a new </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; MIME type specifically for these unsolicited notifications?</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Cheers,</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Aki</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; From: ext hisham.khartabil@nokia.com </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; [<A HREF="mailto:hisham.khartabil@nokia.com">mailto:hisham.khartabil@nokia.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; Sent: Tuesday, September 03, 2002 10:26 AM</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; To: drage@lucent.com; Kiss Krisztian (NRC/Tampere); sip@ietf.org</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; Subject: RE: [Sip] use of MESSAGE method for passing display </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; information</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; to the user</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; I guess it could be done that way, but you might find that </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; others would prefer some sort of Notification package for </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; this type of thing.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; /Hisham</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; From: ext Drage, Keith (Keith) [<A HREF="mailto:drage@lucent.com">mailto:drage@lucent.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; Sent: Monday, September 02, 2002 8:02 PM</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; To: Kiss Krisztian (NRC/Tampere); Drage, Keith (Keith); </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; sip@ietf.org</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; Subject: RE: [Sip] use of MESSAGE method for passing display </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; information</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; to the user</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; With hindsight, I drafted the last paragraph of my original </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; message badly.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; Rather than try to paraphrase again, I will select a direct </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; quote from the message draft abstract:</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; The MESSAGE method is an extension to the Session </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; Initiation Protocol</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt;&nbsp;&nbsp;&nbsp; (SIP) that allows the transfer of Instant Messages.&nbsp; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; MESSAGE requests</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt;&nbsp;&nbsp;&nbsp; carry the content in the form of MIME body parts.&nbsp; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; My concern is not over how such a body should be coded. The </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; questions is does such a usage to carry &quot;Please top up your </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; units or your call may be terminated prematurely&quot; qualify as </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; an Instant Message, i.e. is it within the semantics of </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; MESSAGE to perform this function.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; Keith</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; From: krisztian.kiss@nokia.com </FONT>
<BR><FONT SIZE=2>&gt; &gt; [<A HREF="mailto:krisztian.kiss@nokia.com">mailto:krisztian.kiss@nokia.com</A>]</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; Sent: 02 September 2002 17:43</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; To: drage@lucent.com; sip@ietf.org</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; Subject: RE: [Sip] use of MESSAGE method for </FONT>
<BR><FONT SIZE=2>&gt; passing display </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; information</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; to the user</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; Keith,</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; Within 3GPP, there is a requirement for </FONT>
<BR><FONT SIZE=2>&gt; &gt; intermediate servers </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; to pass textual information for display to the </FONT>
<BR><FONT SIZE=2>&gt; &gt; user. This may </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; be related to a dialog or not.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; A typical example may be (in the case of a prepay user):</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; &quot;Please top up your units or your call may be terminated </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; prematurely&quot;.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; There are a number of methods that are defined which </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; essentially convey body information between User Agents </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; (INFO, NOTIFY, MESSAGE, PUBLISH?).</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; Some of these would appear more suitable that others for </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; passing this information. </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; Of the existing methods, MESSAGE would appear to be </FONT>
<BR><FONT SIZE=2>&gt; &gt; the most </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; suitable (and indeed is the one selected by some of the </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; experts involved). However the internet draft </FONT>
<BR><FONT SIZE=2>&gt; specifically </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; talks about the body being an &quot;Instant Message&quot;.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; draft-ietf-sip-message-06 states that the body can </FONT>
<BR><FONT SIZE=2>&gt; be of ANY </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; MIME type:</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &quot;The body of the request will contain the message to be </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; delivered.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt;&nbsp;&nbsp;&nbsp; This body can be of any MIME type, including </FONT>
<BR><FONT SIZE=2>&gt; message/cpim.&quot;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; Regards,</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; Krisztian</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; Rather than get into a situation similar to that which </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; affects INFO (i.e. people seem to have </FONT>
<BR><FONT SIZE=2>&gt; implemented various </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; applications on INFO and IETF experts say INFO is not </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; appropriate for that application), could I request an </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; exchange of views on the applicability or not of </FONT>
<BR><FONT SIZE=2>&gt; &gt; MESSAGE for </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; this type of information, and if not, what solution would </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; otherwise be suggested.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; Note that the information would normally be </FONT>
<BR><FONT SIZE=2>&gt; &gt; expected to come </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; from some network based entity (acting as a UA). </FONT>
<BR><FONT SIZE=2>&gt; &gt; When related </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; to a dialog, the source may well be some B2BUA </FONT>
<BR><FONT SIZE=2>&gt; between the </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; two end UAs involved in the dialog.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; Keith Drage</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; _______________________________________________</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; &gt; Sip mailing list&nbsp; </FONT>
<BR><FONT SIZE=2><A HREF="https://www1.ietf.org/mailman/listinfo/sip" TARGET="_blank">https://www1.ietf.org/mailman/listinfo/sip</A></FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; This list is for NEW development of the core SIP Protocol</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; Use sip-implementors@cs.columbia.edu for questions on </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; current sip</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; Use sipping@ietf.org for new developments on the </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; application of sip</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; _______________________________________________</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; Sip mailing list&nbsp; <A HREF="https://www1.ietf.org/mailman/listinfo/sip" TARGET="_blank">https://www1.ietf.org/mailman/listinfo/sip</A></FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; This list is for NEW development of the core SIP Protocol</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; Use sip-implementors@cs.columbia.edu for questions on </FONT>
<BR><FONT SIZE=2>&gt; current sip</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; Use sipping@ietf.org for new developments on the </FONT>
<BR><FONT SIZE=2>&gt; &gt; application of sip</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; _______________________________________________</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Sip mailing list&nbsp; <A HREF="https://www1.ietf.org/mailman/listinfo/sip" TARGET="_blank">https://www1.ietf.org/mailman/listinfo/sip</A></FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; This list is for NEW development of the core SIP Protocol</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Use sip-implementors@cs.columbia.edu for questions on current sip</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Use sipping@ietf.org for new developments on the </FONT>
<BR><FONT SIZE=2>&gt; application of sip</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>Sip mailing list&nbsp; <A HREF="https://www1.ietf.org/mailman/listinfo/sip" TARGET="_blank">https://www1.ietf.org/mailman/listinfo/sip</A></FONT>
<BR><FONT SIZE=2>This list is for NEW development of the core SIP Protocol</FONT>
<BR><FONT SIZE=2>Use sip-implementors@cs.columbia.edu for questions on current sip</FONT>
<BR><FONT SIZE=2>Use sipping@ietf.org for new developments on the application of sip</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2536B.5CAAAAD0--
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Tue Sep  3 17:47:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15372
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 17:47:46 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g83LmuG26512
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 17:48:56 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83LmXo26488;
	Tue, 3 Sep 2002 17:48:33 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83Lj5o26385
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 17:45:05 -0400
Received: from mail2.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15262
	for <sip@ietf.org>; Tue, 3 Sep 2002 17:43:24 -0400 (EDT)
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail2.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id g83Lhm7p007400;
	Tue, 3 Sep 2002 17:43:49 -0400 (EDT)
Received: by DYN-TX-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <R5G8ZBXR>; Tue, 3 Sep 2002 16:44:22 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3A640D0@DYN-TX-EXCH-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Kedar Patil'" <kpatil@sta.samsung.com>,
        "'aki.niemi@nokia.com'"
	 <aki.niemi@nokia.com>,
        hisham.khartabil@nokia.com, drage@lucent.com, krisztian.kiss@nokia.com
Cc: sip@ietf.org
Subject: RE: [Sip] use of MESSAGE method for passing display information t
	 o the user
Date: Tue, 3 Sep 2002 16:44:21 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>


I understand the intention behind what you are proposing.

The ability to have these kind of things be interpretable
by atomata would certainly be useful; however, the proposal
that we define some unified "network notification" event
package is a bit unworkable. Doing so would first require
standardization of all of the information that the network
would want to convey so that you can define a machine-readable
format for each. To do so requires standardizing all of the
network-provided services, which is something we have
strenuously avoided doing. We instead provide tools that can
be combined to provide services, since such an approach is
far more powerful.

I propose that we hold the course: when we identify information
that is commonly communicated and warrants interpretation by
atomata (such as a message waiting indication), we can define
an event package for it. However, if service designers want to
communicate information from the network to the terminal, they
should feel free to use MESSAGE to do so.

/a


-----Original Message-----
From: Kedar Patil [mailto:kpatil@sta.samsung.com]
Sent: Tuesday, September 03, 2002 12:00
To: 'aki.niemi@nokia.com'; hisham.khartabil@nokia.com; drage@lucent.com;
krisztian.kiss@nokia.com
Cc: sip@ietf.org
Subject: RE: [Sip] use of MESSAGE method for passing display information t o
the user


Hi, 
I have some input on having event-notification package 
for this : 
Although it looks like a user may have to subscribe to 
"Credit overflow" kind of event all the time, I guess 
this is going to be only during the calls. 
This one case may be solved by "MESSAGE". However, is it the 
only case? I believe there could be more. The commonality 
is that all of them are going to be from the network (not the 
peer) and are asynchrounous. For this why not have an event 
pacakge under the framework of RFC3265. A UA may subscribe 
to network of all network events, and any such event would 
trigger the appropriate event notification. 
If all the events are for human interaction then "Message" 
looks fine. Is there any event where user interaction is 
taken over by automatic actions by s/w config? (e.g. in this 
case automatic credit upgrade just enough to avoid premature 
call termination!) 
The question remains : Is there one network element to which 
a UA may have to subscribe or many? 
thanks, 
= Kedar = 


> -----Original Message----- 
> From: aki.niemi@nokia.com [mailto:aki.niemi@nokia.com] 
> Sent: Tuesday, September 03, 2002 3:57 AM 
> To: hisham.khartabil@nokia.com; drage@lucent.com; 
> krisztian.kiss@nokia.com; sip@ietf.org 
> Subject: RE: [Sip] use of MESSAGE method for passing display 
> information 
> to the user 
> 
> 
> Is it feasible to have that subscription state hanging around 
> just in case you may some day run out of credit? 
> 
> Cheers, 
> Aki 
> 
> > -----Original Message----- 
> > From: Khartabil Hisham (NMP/Helsinki) 
> > Sent: Tuesday, September 03, 2002 11:49 AM 
> > To: Niemi Aki (NET/Espoo); drage@lucent.com; Kiss Krisztian 
> > (NRC/Tampere); sip@ietf.org 
> > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > information 
> > to the user 
> > 
> > 
> > You're not subscribing to get an instant message, you're 
> > subscribing to get information about your prepaid units. 
> > 
> > Why is it unsolicited? 
> > 
> > /Hisham 
> > 
> > > -----Original Message----- 
> > > From: Niemi Aki (NET/Espoo) 
> > > Sent: Tuesday, September 03, 2002 10:47 AM 
> > > To: Khartabil Hisham (NMP/Helsinki); drage@lucent.com; Kiss 
> > Krisztian 
> > > (NRC/Tampere); sip@ietf.org 
> > > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > > information 
> > > to the user 
> > > 
> > > 
> > > This application seems rather different from the presence 
> > > type notifications because it seems these notifications are 
> > > unsolicited. So to me MESSAGE seems like a perfect fit. I 
> > > don't have to "subscribe" in order to receive instant 
> > messages either. 
> > > 
> > > So by saying "Notification package" perhaps you mean a new 
> > > MIME type specifically for these unsolicited notifications? 
> > > 
> > > Cheers, 
> > > Aki 
> > > 
> > > > -----Original Message----- 
> > > > From: ext hisham.khartabil@nokia.com 
> > > > [mailto:hisham.khartabil@nokia.com] 
> > > > Sent: Tuesday, September 03, 2002 10:26 AM 
> > > > To: drage@lucent.com; Kiss Krisztian (NRC/Tampere); sip@ietf.org 
> > > > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > > > information 
> > > > to the user 
> > > > 
> > > > 
> > > > I guess it could be done that way, but you might find that 
> > > > others would prefer some sort of Notification package for 
> > > > this type of thing. 
> > > > 
> > > > /Hisham 
> > > > 
> > > > > -----Original Message----- 
> > > > > From: ext Drage, Keith (Keith) [mailto:drage@lucent.com] 
> > > > > Sent: Monday, September 02, 2002 8:02 PM 
> > > > > To: Kiss Krisztian (NRC/Tampere); Drage, Keith (Keith); 
> > > sip@ietf.org 
> > > > > Subject: RE: [Sip] use of MESSAGE method for passing display 
> > > > > information 
> > > > > to the user 
> > > > > 
> > > > > 
> > > > > With hindsight, I drafted the last paragraph of my original 
> > > > > message badly. 
> > > > > 
> > > > > Rather than try to paraphrase again, I will select a direct 
> > > > > quote from the message draft abstract: 
> > > > > 
> > > > > The MESSAGE method is an extension to the Session 
> > > > Initiation Protocol 
> > > > >    (SIP) that allows the transfer of Instant Messages.  
> > > > > MESSAGE requests 
> > > > >    carry the content in the form of MIME body parts.  
> > > > > 
> > > > > My concern is not over how such a body should be coded. The 
> > > > > questions is does such a usage to carry "Please top up your 
> > > > > units or your call may be terminated prematurely" qualify as 
> > > > > an Instant Message, i.e. is it within the semantics of 
> > > > > MESSAGE to perform this function. 
> > > > > 
> > > > > Keith 
> > > > > 
> > > > > > -----Original Message----- 
> > > > > > From: krisztian.kiss@nokia.com 
> > [mailto:krisztian.kiss@nokia.com] 
> > > > > > Sent: 02 September 2002 17:43 
> > > > > > To: drage@lucent.com; sip@ietf.org 
> > > > > > Subject: RE: [Sip] use of MESSAGE method for 
> passing display 
> > > > > > information 
> > > > > > to the user 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > Keith, 
> > > > > > 
> > > > > > > Within 3GPP, there is a requirement for 
> > intermediate servers 
> > > > > > > to pass textual information for display to the 
> > user. This may 
> > > > > > > be related to a dialog or not. 
> > > > > > > 
> > > > > > > A typical example may be (in the case of a prepay user): 
> > > > > > > 
> > > > > > > "Please top up your units or your call may be terminated 
> > > > > > prematurely". 
> > > > > > > 
> > > > > > > There are a number of methods that are defined which 
> > > > > > > essentially convey body information between User Agents 
> > > > > > > (INFO, NOTIFY, MESSAGE, PUBLISH?). 
> > > > > > > 
> > > > > > > Some of these would appear more suitable that others for 
> > > > > > > passing this information. 
> > > > > > > 
> > > > > > > Of the existing methods, MESSAGE would appear to be 
> > the most 
> > > > > > > suitable (and indeed is the one selected by some of the 
> > > > > > > experts involved). However the internet draft 
> specifically 
> > > > > > > talks about the body being an "Instant Message". 
> > > > > > 
> > > > > > draft-ietf-sip-message-06 states that the body can 
> be of ANY 
> > > > > > MIME type: 
> > > > > > "The body of the request will contain the message to be 
> > > delivered. 
> > > > > >    This body can be of any MIME type, including 
> message/cpim." 
> > > > > > 
> > > > > > Regards, 
> > > > > > Krisztian 
> > > > > > 
> > > > > > 
> > > > > > > Rather than get into a situation similar to that which 
> > > > > > > affects INFO (i.e. people seem to have 
> implemented various 
> > > > > > > applications on INFO and IETF experts say INFO is not 
> > > > > > > appropriate for that application), could I request an 
> > > > > > > exchange of views on the applicability or not of 
> > MESSAGE for 
> > > > > > > this type of information, and if not, what solution would 
> > > > > > > otherwise be suggested. 
> > > > > > > 
> > > > > > > Note that the information would normally be 
> > expected to come 
> > > > > > > from some network based entity (acting as a UA). 
> > When related 
> > > > > > > to a dialog, the source may well be some B2BUA 
> between the 
> > > > > > > two end UAs involved in the dialog. 
> > > > > > > 
> > > > > > > Keith Drage 
> > > > > > > _______________________________________________ 
> > > > > > > Sip mailing list  
https://www1.ietf.org/mailman/listinfo/sip 
> > > > > > This list is for NEW development of the core SIP Protocol 
> > > > > > Use sip-implementors@cs.columbia.edu for questions on 
> > > current sip 
> > > > > > Use sipping@ietf.org for new developments on the 
> > > > application of sip 
> > > > > > 
> > > > > 
> > > > _______________________________________________ 
> > > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip 
> > > > This list is for NEW development of the core SIP Protocol 
> > > > Use sip-implementors@cs.columbia.edu for questions on 
> current sip 
> > > > Use sipping@ietf.org for new developments on the 
> > application of sip 
> > > > 
> > > _______________________________________________ 
> > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip 
> > > This list is for NEW development of the core SIP Protocol 
> > > Use sip-implementors@cs.columbia.edu for questions on current sip 
> > > Use sipping@ietf.org for new developments on the 
> application of sip 
> > > 
> > 
> 
_______________________________________________ 
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip 
This list is for NEW development of the core SIP Protocol 
Use sip-implementors@cs.columbia.edu for questions on current sip 
Use sipping@ietf.org for new developments on the application of sip 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Tue Sep  3 18:02:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15837
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 18:02:46 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g83M3uc27258
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 18:03:56 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83M1Ko27126;
	Tue, 3 Sep 2002 18:01:20 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83LwRo26990
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 17:58:27 -0400
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15661
	for <sip@ietf.org>; Tue, 3 Sep 2002 17:56:47 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g83Lvk3x029755;
	Tue, 3 Sep 2002 14:57:46 -0700 (PDT)
Received: from dhcp-128-107-139-56.cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.1.0.54-GA)
	with ESMTP id AAU34554;
	Tue, 3 Sep 2002 14:56:09 -0700 (PDT)
Date: Tue, 3 Sep 2002 14:58:32 -0700
Subject: Re: [Sip] use of MESSAGE method for passing display information to the  user
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v482)
Cc: "Drage, Keith (Keith)" <drage@lucent.com>,
        "'krisztian.kiss@nokia.com'" <krisztian.kiss@nokia.com>, sip@ietf.org
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <3D749D2F.DA898F33@ericsson.com>
Message-Id: <49A35337-BF88-11D6-B6D6-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.482)
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hmmm...

I think the problem lies in the presentation to the user.  What Keith is 
describing is a message about a specific call, so it really should be 
sent in the context of that dialog.  (Otherwise, it might arrive with a 
whole pile of SMS messages). Unfortunately, the dialog identifiers and 
cseqs are being managed by the user agents, so the "system" really can't 
just send a MESSAGE mid-dialog unless it is a B2BUA managing the cseqs, 
dialog identifiers, and security associations for that user.   If you 
want this message to be handled differently than other messages, it 
needs to be different.

thanks,
-rohan




On Tuesday, September 3, 2002, at 04:29 AM, Miguel A. Garcia wrote:

> Keith:
>
> I have found some hints into the message draft that makes me think this 
> is the appropriate usage of the method. This hints are:
>
>     The MESSAGE method is an extension to the Session Initiation 
> Protocol
>    (SIP) that allows the transfer of Instant Messages.
>
> I guess instant message is a message delivered instantly to the user, 
> and displayed to the user.
>
>     All UAs which support the MESSAGE method MUST be prepared to send 
> and
>     receive MESSAGE requests with a body of type text/plain.
>
> Text/plain seems to be textual information that can be displayed to a 
> user.
> If it was message/sipfrag, perhaps the information wasn't intended to be
> delivered to the user, but text/plain seems to be unformatted 
> information
> intended to be readable by a human being.
>
>    Normally, a 200 OK
>    response will be generated by the user agent of the request's final
>    recipient.  Note that this indicates that the user agent accepted the
>    message, not that the user has seen it.
>
> This again suggest that the payload of the MESSAGE method is typically
> displayed to the user.
>
> All these hints, make me think that your usage example seems to be a 
> correct
> usage of the MESSAGE method.
>
> /Miguel
>
> "Drage, Keith (Keith)" wrote:
>>
>> With hindsight, I drafted the last paragraph of my original message 
>> badly.
>>
>> Rather than try to paraphrase again, I will select a direct quote from 
>> the message draft abstract:
>>
>> The MESSAGE method is an extension to the Session Initiation Protocol
>>    (SIP) that allows the transfer of Instant Messages.  MESSAGE 
>> requests
>>    carry the content in the form of MIME body parts.
>>
>> My concern is not over how such a body should be coded. The questions 
>> is does such a usage to carry "Please top up your units or your call 
>> may be terminated prematurely" qualify as an Instant Message, i.e. is 
>> it within the semantics of MESSAGE to perform this function.
>>
>> Keith
>>
>>> -----Original Message-----
>>> From: krisztian.kiss@nokia.com [mailto:krisztian.kiss@nokia.com]
>>> Sent: 02 September 2002 17:43
>>> To: drage@lucent.com; sip@ietf.org
>>> Subject: RE: [Sip] use of MESSAGE method for passing display
>>> information
>>> to the user
>>>
>>>
>>>
>>> Keith,
>>>
>>>> Within 3GPP, there is a requirement for intermediate servers
>>>> to pass textual information for display to the user. This may
>>>> be related to a dialog or not.
>>>>
>>>> A typical example may be (in the case of a prepay user):
>>>>
>>>> "Please top up your units or your call may be terminated
>>> prematurely".
>>>>
>>>> There are a number of methods that are defined which
>>>> essentially convey body information between User Agents
>>>> (INFO, NOTIFY, MESSAGE, PUBLISH?).
>>>>
>>>> Some of these would appear more suitable that others for
>>>> passing this information.
>>>>
>>>> Of the existing methods, MESSAGE would appear to be the most
>>>> suitable (and indeed is the one selected by some of the
>>>> experts involved). However the internet draft specifically
>>>> talks about the body being an "Instant Message".
>>>
>>> draft-ietf-sip-message-06 states that the body can be of ANY
>>> MIME type:
>>> "The body of the request will contain the message to be delivered.
>>>    This body can be of any MIME type, including message/cpim."
>>>
>>> Regards,
>>> Krisztian
>>>
>>>
>>>> Rather than get into a situation similar to that which
>>>> affects INFO (i.e. people seem to have implemented various
>>>> applications on INFO and IETF experts say INFO is not
>>>> appropriate for that application), could I request an
>>>> exchange of views on the applicability or not of MESSAGE for
>>>> this type of information, and if not, what solution would
>>>> otherwise be suggested.
>>>>
>>>> Note that the information would normally be expected to come
>>>> from some network based entity (acting as a UA). When related
>>>> to a dialog, the source may well be some B2BUA between the
>>>> two end UAs involved in the dialog.
>>>>
>>>> Keith Drage
>>>> _______________________________________________
>>>> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>>>> This list is for NEW development of the core SIP Protocol
>>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>>> Use sipping@ietf.org for new developments on the application of sip
>>>>
>>>
>> _______________________________________________
>> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of sip
>
> --
> Miguel-Angel Garcia                     Oy LM Ericsson AB
>                                         Jorvas, Finland
> mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
> mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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



From mailnull@www1.ietf.org  Tue Sep  3 18:05:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15876
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 18:05:09 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g83M6JX27339
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 18:06:19 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83M5Eo27297;
	Tue, 3 Sep 2002 18:05:14 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83M2go27225
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 18:02:42 -0400
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15807
	for <sip@ietf.org>; Tue, 3 Sep 2002 18:01:01 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id g83M25ds014286;
	Tue, 3 Sep 2002 15:02:05 -0700 (PDT)
Received: from dhcp-128-107-139-56.cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.1.0.54-GA)
	with ESMTP id AAU34612;
	Tue, 3 Sep 2002 15:00:24 -0700 (PDT)
Date: Tue, 3 Sep 2002 15:02:47 -0700
Subject: Re: [Sip] use of MESSAGE method for passing display information t o the user
Content-Type: multipart/alternative; boundary=Apple-Mail-1--903723336
Mime-Version: 1.0 (Apple Message framework v482)
Cc: "'aki.niemi@nokia.com'" <aki.niemi@nokia.com>, hisham.khartabil@nokia.com,
        drage@lucent.com, krisztian.kiss@nokia.com, sip@ietf.org
To: Kedar Patil <kpatil@sta.samsung.com>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <4B9386E83999D411997100508BAF206A061F506C@stamail.telecom.sna.samsung.com>
Message-Id: <E1C6AF22-BF88-11D6-B6D6-0003938AF740@cisco.com>
X-Mailer: Apple Mail (2.482)
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>


--Apple-Mail-1--903723336
Content-Type: text/plain;
	charset=ISO-8859-1;
	format=flowed
Content-Transfer-Encoding: quoted-printable


On Tuesday, September 3, 2002, at 10:00 AM, Kedar Patil wrote:

> Hi,
>
> I have some input on having event-notification package
> for this :
>
> Although it looks like a user may have to subscribe to
> "Credit overflow" kind of event all the time, I guess
> this is going to be only during the calls.
is it? what if I have 2 phones using the same pool of credits.  do you=20=

want a notification that you are running out of credits on both phones=20=

or just the one?

thanks,
-rohan

> This one case may be solved by "MESSAGE". However, is it the
> only case? I believe there could be more. The commonality
> is that all of them are going to be from the network (not the
> peer) and are asynchrounous. For this why not have an event
> pacakge under the framework of RFC3265. A UA may subscribe
> to network of all network events, and any such event would
> trigger the appropriate event notification.
>
> If all the events are for human interaction then "Message"
> looks fine. Is there any event where user interaction is
> taken over by automatic actions by s/w config? (e.g. in this
> case automatic credit upgrade just enough to avoid premature
> call termination!)
>
> The question remains : Is there one network element to which
> a UA may have to subscribe or many?
>
> thanks,
> =3D Kedar =3D
>
>
> > -----Original Message-----
> > From: aki.niemi@nokia.com [mailto:aki.niemi@nokia.com]
> > Sent: Tuesday, September 03, 2002 3:57 AM
> > To: hisham.khartabil@nokia.com; drage@lucent.com;
> > krisztian.kiss@nokia.com; sip@ietf.org
> > Subject: RE: [Sip] use of MESSAGE method for passing display
> > information
> > to the user
> >
> >
> > Is it feasible to have that subscription state hanging around
> > just in case you may some day run out of credit?
> >
> > Cheers,
> > Aki
> >
> > > -----Original Message-----
> > > From: Khartabil Hisham (NMP/Helsinki)
> > > Sent: Tuesday, September 03, 2002 11:49 AM
> > > To: Niemi Aki (NET/Espoo); drage@lucent.com; Kiss Krisztian
> > > (NRC/Tampere); sip@ietf.org
> > > Subject: RE: [Sip] use of MESSAGE method for passing display
> > > information
> > > to the user
> > >
> > >
> > > You're not subscribing to get an instant message, you're
> > > subscribing to get information about your prepaid units.
> > >
> > > Why is it unsolicited?
> > >
> > > /Hisham
> > >
> > > > -----Original Message-----
> > > > From: Niemi Aki (NET/Espoo)
> > > > Sent: Tuesday, September 03, 2002 10:47 AM
> > > > To: Khartabil Hisham (NMP/Helsinki); drage@lucent.com; Kiss
> > > Krisztian
> > > > (NRC/Tampere); sip@ietf.org
> > > > Subject: RE: [Sip] use of MESSAGE method for passing display
> > > > information
> > > > to the user
> > > >
> > > >
> > > > This application seems rather different from the presence
> > > > type notifications because it seems these notifications are
> > > > unsolicited. So to me MESSAGE seems like a perfect fit. I
> > > > don't have to "subscribe" in order to receive instant
> > > messages either.
> > > >
> > > > So by saying "Notification package" perhaps you mean a new
> > > > MIME type specifically for these unsolicited notifications?
> > > >
> > > > Cheers,
> > > > Aki
> > > >
> > > > > -----Original Message-----
> > > > > From: ext hisham.khartabil@nokia.com
> > > > > [mailto:hisham.khartabil@nokia.com]
> > > > > Sent: Tuesday, September 03, 2002 10:26 AM
> > > > > To: drage@lucent.com; Kiss Krisztian (NRC/Tampere); =
sip@ietf.org
> > > > > Subject: RE: [Sip] use of MESSAGE method for passing display
> > > > > information
> > > > > to the user
> > > > >
> > > > >
> > > > > I guess it could be done that way, but you might find that
> > > > > others would prefer some sort of Notification package for
> > > > > this type of thing.
> > > > >
> > > > > /Hisham
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: ext Drage, Keith (Keith) [mailto:drage@lucent.com]
> > > > > > Sent: Monday, September 02, 2002 8:02 PM
> > > > > > To: Kiss Krisztian (NRC/Tampere); Drage, Keith (Keith);
> > > > sip@ietf.org
> > > > > > Subject: RE: [Sip] use of MESSAGE method for passing display
> > > > > > information
> > > > > > to the user
> > > > > >
> > > > > >
> > > > > > With hindsight, I drafted the last paragraph of my original
> > > > > > message badly.
> > > > > >
> > > > > > Rather than try to paraphrase again, I will select a direct
> > > > > > quote from the message draft abstract:
> > > > > >
> > > > > > The MESSAGE method is an extension to the Session
> > > > > Initiation Protocol
> > > > > >=A0=A0=A0 (SIP) that allows the transfer of Instant =
Messages.=A0
> > > > > > MESSAGE requests
> > > > > >=A0=A0=A0 carry the content in the form of MIME body parts.=A0
> > > > > >
> > > > > > My concern is not over how such a body should be coded. The
> > > > > > questions is does such a usage to carry "Please top up your
> > > > > > units or your call may be terminated prematurely" qualify as
> > > > > > an Instant Message, i.e. is it within the semantics of
> > > > > > MESSAGE to perform this function.
> > > > > >
> > > > > > Keith
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: krisztian.kiss@nokia.com
> > > [mailto:krisztian.kiss@nokia.com]
> > > > > > > Sent: 02 September 2002 17:43
> > > > > > > To: drage@lucent.com; sip@ietf.org
> > > > > > > Subject: RE: [Sip] use of MESSAGE method for
> > passing display
> > > > > > > information
> > > > > > > to the user
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Keith,
> > > > > > >
> > > > > > > > Within 3GPP, there is a requirement for
> > > intermediate servers
> > > > > > > > to pass textual information for display to the
> > > user. This may
> > > > > > > > be related to a dialog or not.
> > > > > > > >
> > > > > > > > A typical example may be (in the case of a prepay user):
> > > > > > > >
> > > > > > > > "Please top up your units or your call may be terminated
> > > > > > > prematurely".
> > > > > > > >
> > > > > > > > There are a number of methods that are defined which
> > > > > > > > essentially convey body information between User Agents
> > > > > > > > (INFO, NOTIFY, MESSAGE, PUBLISH?).
> > > > > > > >
> > > > > > > > Some of these would appear more suitable that others for
> > > > > > > > passing this information.
> > > > > > > >
> > > > > > > > Of the existing methods, MESSAGE would appear to be
> > > the most
> > > > > > > > suitable (and indeed is the one selected by some of the
> > > > > > > > experts involved). However the internet draft
> > specifically
> > > > > > > > talks about the body being an "Instant Message".
> > > > > > >
> > > > > > > draft-ietf-sip-message-06 states that the body can
> > be of ANY
> > > > > > > MIME type:
> > > > > > > "The body of the request will contain the message to be
> > > > delivered.
> > > > > > >=A0=A0=A0 This body can be of any MIME type, including
> > message/cpim."
> > > > > > >
> > > > > > > Regards,
> > > > > > > Krisztian
> > > > > > >
> > > > > > >
> > > > > > > > Rather than get into a situation similar to that which
> > > > > > > > affects INFO (i.e. people seem to have
> > implemented various
> > > > > > > > applications on INFO and IETF experts say INFO is not
> > > > > > > > appropriate for that application), could I request an
> > > > > > > > exchange of views on the applicability or not of
> > > MESSAGE for
> > > > > > > > this type of information, and if not, what solution =
would
> > > > > > > > otherwise be suggested.
> > > > > > > >
> > > > > > > > Note that the information would normally be
> > > expected to come
> > > > > > > > from some network based entity (acting as a UA).
> > > When related
> > > > > > > > to a dialog, the source may well be some B2BUA
> > between the
> > > > > > > > two end UAs involved in the dialog.
> > > > > > > >
> > > > > > > > Keith Drage
> > > > > > > > _______________________________________________
> > > > > > > > Sip mailing list=A0
> https://www1.ietf.org/mailman/listinfo/sip
> > > > > > > This list is for NEW development of the core SIP Protocol
> > > > > > > Use sip-implementors@cs.columbia.edu for questions on
> > > > current sip
> > > > > > > Use sipping@ietf.org for new developments on the
> > > > > application of sip
> > > > > > >
> > > > > >
> > > > > _______________________________________________
> > > > > Sip mailing list=A0 https://www1.ietf.org/mailman/listinfo/sip
> > > > > This list is for NEW development of the core SIP Protocol
> > > > > Use sip-implementors@cs.columbia.edu for questions on
> > current sip
> > > > > Use sipping@ietf.org for new developments on the
> > > application of sip
> > > > >
> > > > _______________________________________________
> > > > Sip mailing list=A0 https://www1.ietf.org/mailman/listinfo/sip
> > > > This list is for NEW development of the core SIP Protocol
> > > > Use sip-implementors@cs.columbia.edu for questions on current =
sip
> > > > Use sipping@ietf.org for new developments on the
> > application of sip
> > > >
> > >
> >
> _______________________________________________
> Sip mailing list=A0 https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>

--Apple-Mail-1--903723336
Content-Type: text/enriched;
	charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


On Tuesday, September 3, 2002, at 10:00 AM, Kedar Patil wrote:


<excerpt><smaller>Hi,</smaller>


<smaller>I have some input on having event-notification package

for this :</smaller>


<smaller>Although it looks like a user may have to subscribe to

"Credit overflow" kind of event all the time, I guess

this is going to be only during the calls.</smaller>

</excerpt>is it? what if I have 2 phones using the same pool of
credits.  do you want a notification that you are running out of
credits on both phones or just the one?


thanks,

-rohan


<excerpt><smaller>This one case may be solved by "MESSAGE". However,
is it the

only case? I believe there could be more. The commonality

is that all of them are going to be from the network (not the

peer) and are asynchrounous. For this why not have an event

pacakge under the framework of RFC3265. A UA may subscribe

to network of all network events, and any such event would

trigger the appropriate event notification.</smaller>


<smaller>If all the events are for human interaction then "Message"

looks fine. Is there any event where user interaction is

taken over by automatic actions by s/w config? (e.g. in this

case automatic credit upgrade just enough to avoid premature

call termination!)</smaller>


<smaller>The question remains : Is there one network element to which

a UA may have to subscribe or many?</smaller>


<smaller>thanks,

=3D Kedar =3D</smaller>



<smaller>> -----Original Message-----

> From: aki.niemi@nokia.com
=
[<underline><color><param>1999,1999,FFFF</param>mailto:aki.niemi@nokia.com=
</color></underline>]

> Sent: Tuesday, September 03, 2002 3:57 AM

> To: hisham.khartabil@nokia.com; drage@lucent.com;

> krisztian.kiss@nokia.com; sip@ietf.org

> Subject: RE: [Sip] use of MESSAGE method for passing display

> information

> to the user

>

>

> Is it feasible to have that subscription state hanging around

> just in case you may some day run out of credit?

>

> Cheers,

> Aki

>

> > -----Original Message-----

> > From: Khartabil Hisham (NMP/Helsinki)

> > Sent: Tuesday, September 03, 2002 11:49 AM

> > To: Niemi Aki (NET/Espoo); drage@lucent.com; Kiss Krisztian

> > (NRC/Tampere); sip@ietf.org

> > Subject: RE: [Sip] use of MESSAGE method for passing display

> > information

> > to the user

> >

> >

> > You're not subscribing to get an instant message, you're

> > subscribing to get information about your prepaid units.

> >

> > Why is it unsolicited?

> >

> > /Hisham

> >

> > > -----Original Message-----

> > > From: Niemi Aki (NET/Espoo)

> > > Sent: Tuesday, September 03, 2002 10:47 AM

> > > To: Khartabil Hisham (NMP/Helsinki); drage@lucent.com; Kiss

> > Krisztian

> > > (NRC/Tampere); sip@ietf.org

> > > Subject: RE: [Sip] use of MESSAGE method for passing display

> > > information

> > > to the user

> > >

> > >

> > > This application seems rather different from the presence

> > > type notifications because it seems these notifications are

> > > unsolicited. So to me MESSAGE seems like a perfect fit. I

> > > don't have to "subscribe" in order to receive instant

> > messages either.

> > >

> > > So by saying "Notification package" perhaps you mean a new

> > > MIME type specifically for these unsolicited notifications?

> > >

> > > Cheers,

> > > Aki

> > >

> > > > -----Original Message-----

> > > > From: ext hisham.khartabil@nokia.com

> > > >
=
[<underline><color><param>1999,1999,FFFF</param>mailto:hisham.khartabil@no=
kia.com</color></underline>]

> > > > Sent: Tuesday, September 03, 2002 10:26 AM

> > > > To: drage@lucent.com; Kiss Krisztian (NRC/Tampere);
sip@ietf.org

> > > > Subject: RE: [Sip] use of MESSAGE method for passing display

> > > > information

> > > > to the user

> > > >

> > > >

> > > > I guess it could be done that way, but you might find that

> > > > others would prefer some sort of Notification package for

> > > > this type of thing.

> > > >

> > > > /Hisham

> > > >

> > > > > -----Original Message-----

> > > > > From: ext Drage, Keith (Keith)
=
[<underline><color><param>1999,1999,FFFF</param>mailto:drage@lucent.com</c=
olor></underline>]

> > > > > Sent: Monday, September 02, 2002 8:02 PM

> > > > > To: Kiss Krisztian (NRC/Tampere); Drage, Keith (Keith);

> > > sip@ietf.org

> > > > > Subject: RE: [Sip] use of MESSAGE method for passing display

> > > > > information

> > > > > to the user

> > > > >

> > > > >

> > > > > With hindsight, I drafted the last paragraph of my original

> > > > > message badly.

> > > > >

> > > > > Rather than try to paraphrase again, I will select a direct

> > > > > quote from the message draft abstract:

> > > > >

> > > > > The MESSAGE method is an extension to the Session

> > > > Initiation Protocol

> > > > >=A0=A0=A0 (SIP) that allows the transfer of Instant Messages.=A0

> > > > > MESSAGE requests

> > > > >=A0=A0=A0 carry the content in the form of MIME body parts.=A0

> > > > >

> > > > > My concern is not over how such a body should be coded. The

> > > > > questions is does such a usage to carry "Please top up your

> > > > > units or your call may be terminated prematurely" qualify as

> > > > > an Instant Message, i.e. is it within the semantics of

> > > > > MESSAGE to perform this function.

> > > > >

> > > > > Keith

> > > > >

> > > > > > -----Original Message-----

> > > > > > From: krisztian.kiss@nokia.com

> >
=
[<underline><color><param>1999,1999,FFFF</param>mailto:krisztian.kiss@noki=
a.com</color></underline>]

> > > > > > Sent: 02 September 2002 17:43

> > > > > > To: drage@lucent.com; sip@ietf.org

> > > > > > Subject: RE: [Sip] use of MESSAGE method for

> passing display

> > > > > > information

> > > > > > to the user

> > > > > >

> > > > > >

> > > > > >

> > > > > > Keith,

> > > > > >

> > > > > > > Within 3GPP, there is a requirement for

> > intermediate servers

> > > > > > > to pass textual information for display to the

> > user. This may

> > > > > > > be related to a dialog or not.

> > > > > > >

> > > > > > > A typical example may be (in the case of a prepay user):

> > > > > > >

> > > > > > > "Please top up your units or your call may be terminated

> > > > > > prematurely".

> > > > > > >

> > > > > > > There are a number of methods that are defined which

> > > > > > > essentially convey body information between User Agents

> > > > > > > (INFO, NOTIFY, MESSAGE, PUBLISH?).

> > > > > > >

> > > > > > > Some of these would appear more suitable that others for

> > > > > > > passing this information.

> > > > > > >

> > > > > > > Of the existing methods, MESSAGE would appear to be

> > the most

> > > > > > > suitable (and indeed is the one selected by some of the

> > > > > > > experts involved). However the internet draft

> specifically

> > > > > > > talks about the body being an "Instant Message".

> > > > > >

> > > > > > draft-ietf-sip-message-06 states that the body can

> be of ANY

> > > > > > MIME type:

> > > > > > "The body of the request will contain the message to be

> > > delivered.

> > > > > >=A0=A0=A0 This body can be of any MIME type, including

> message/cpim."

> > > > > >

> > > > > > Regards,

> > > > > > Krisztian

> > > > > >

> > > > > >

> > > > > > > Rather than get into a situation similar to that which

> > > > > > > affects INFO (i.e. people seem to have

> implemented various

> > > > > > > applications on INFO and IETF experts say INFO is not

> > > > > > > appropriate for that application), could I request an

> > > > > > > exchange of views on the applicability or not of

> > MESSAGE for

> > > > > > > this type of information, and if not, what solution would

> > > > > > > otherwise be suggested.

> > > > > > >

> > > > > > > Note that the information would normally be

> > expected to come

> > > > > > > from some network based entity (acting as a UA).

> > When related

> > > > > > > to a dialog, the source may well be some B2BUA

> between the

> > > > > > > two end UAs involved in the dialog.

> > > > > > >

> > > > > > > Keith Drage

> > > > > > > _______________________________________________

> > > > > > > Sip mailing list=A0

=
<underline><color><param>1999,1999,FFFF</param>https://www1.ietf.org/mailm=
an/listinfo/sip

</color></underline>> > > > > > This list is for NEW development of
the core SIP Protocol

> > > > > > Use sip-implementors@cs.columbia.edu for questions on

> > > current sip

> > > > > > Use sipping@ietf.org for new developments on the

> > > > application of sip

> > > > > >

> > > > >

> > > > _______________________________________________

> > > > Sip mailing list=A0
=
<underline><color><param>1999,1999,FFFF</param>https://www1.ietf.org/mailm=
an/listinfo/sip

</color></underline>> > > > This list is for NEW development of the
core SIP Protocol

> > > > Use sip-implementors@cs.columbia.edu for questions on

> current sip

> > > > Use sipping@ietf.org for new developments on the

> > application of sip

> > > >

> > > _______________________________________________

> > > Sip mailing list=A0
=
<underline><color><param>1999,1999,FFFF</param>https://www1.ietf.org/mailm=
an/listinfo/sip

</color></underline>> > > This list is for NEW development of the core
SIP Protocol

> > > Use sip-implementors@cs.columbia.edu for questions on current sip

> > > Use sipping@ietf.org for new developments on the

> application of sip

> > >

> >

>

_______________________________________________

Sip mailing list=A0
=
<underline><color><param>1999,1999,FFFF</param>https://www1.ietf.org/mailm=
an/listinfo/sip

</color></underline>This list is for NEW development of the core SIP
Protocol

Use sip-implementors@cs.columbia.edu for questions on current sip

Use sipping@ietf.org for new developments on the application of =
sip</smaller>


</excerpt>=

--Apple-Mail-1--903723336--

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



From mailnull@www1.ietf.org  Tue Sep  3 21:01:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19090
	for <sip-archive@odin.ietf.org>; Tue, 3 Sep 2002 21:01:08 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8412Lr03959
	for sip-archive@odin.ietf.org; Tue, 3 Sep 2002 21:02:21 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g84110o03901;
	Tue, 3 Sep 2002 21:01:00 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g840x8o03825
	for <sip@optimus.ietf.org>; Tue, 3 Sep 2002 20:59:08 -0400
Received: from mail2.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18992
	for <sip@ietf.org>; Tue, 3 Sep 2002 20:57:25 -0400 (EDT)
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail2.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id g840vg7p008243;
	Tue, 3 Sep 2002 20:57:42 -0400 (EDT)
Received: by DYN-TX-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <R5G8ZBYQ>; Tue, 3 Sep 2002 19:58:16 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3A640D7@DYN-TX-EXCH-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Rohan Mahy'" <rohan@cisco.com>,
        "Miguel A. Garcia"
	 <Miguel.A.Garcia@ericsson.com>
Cc: "Drage, Keith (Keith)" <drage@lucent.com>,
        "'krisztian.kiss@nokia.com'" <krisztian.kiss@nokia.com>, sip@ietf.org
Subject: RE: [Sip] use of MESSAGE method for passing display information t
	o the  user
Date: Tue, 3 Sep 2002 19:58:12 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

> If you 
> want this message to be handled differently than other messages, it 
> needs to be different.

You mean like "Priority: Urgent" or something like that?

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



From mailnull@www1.ietf.org  Wed Sep  4 04:12:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20123
	for <sip-archive@odin.ietf.org>; Wed, 4 Sep 2002 04:12:48 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g848E4I03355
	for sip-archive@odin.ietf.org; Wed, 4 Sep 2002 04:14:04 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g848AWo03114;
	Wed, 4 Sep 2002 04:10:32 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8485bo02357
	for <sip@optimus.ietf.org>; Wed, 4 Sep 2002 04:05:37 -0400
Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19964
	for <sip@ietf.org>; Wed, 4 Sep 2002 04:03:50 -0400 (EDT)
From: hisham.khartabil@nokia.com
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g8485P713591
	for <sip@ietf.org>; Wed, 4 Sep 2002 11:05:25 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5d20febfabac158f23168@esvir03nok.nokia.com>;
 Wed, 4 Sep 2002 11:05:24 +0300
Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 4 Sep 2002 11:05:24 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] use of MESSAGE method for passing display information to the user
Date: Wed, 4 Sep 2002 11:05:23 +0300
Message-ID: <2038BCC78B1AD641891A0D1AE133DBB7C2059C@esebe019.ntc.nokia.com>
Thread-Topic: [Sip] use of MESSAGE method for passing display information to the user
Thread-Index: AcJTZPQWVVah48yARvuA/AK0oqEsHgAgycAg
To: <bcampbell@dynamicsoft.com>, <drage@lucent.com>
Cc: <sip@ietf.org>
X-OriginalArrivalTime: 04 Sep 2002 08:05:24.0550 (UTC) FILETIME=[D298A660:01C253E9]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g8485bo02358
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

How useful can this be when I'm talking on the phone and I get an Instant Message with text telling me that I'm running out of credit? How often do you stop talking on the phone just to read your SMS? The most likely scenario is that your phone call will be cut short, then you go and read your IM and only then you find out what the contents of the IM were.

I think this type of information should be conveyed by a special tone that the phone plays or by a light going red of the phone. Perhaps implementation specific. The point is that we can't standardise that "your running out of credit" type of IM MUST be rendered to the user.

Having said that, I agree that MESSAGE is the choice if contents of a request are to be rendered to a user. But if I, as a phone manufacturer want my phone to flash a red light when suck IM is received, then I can't.

/Hisham

> -----Original Message-----
> From: ext Ben Campbell [mailto:bcampbell@dynamicsoft.com]
> Sent: Tuesday, September 03, 2002 7:09 PM
> To: Drage, Keith (Keith)
> Cc: 'sip@ietf.org'
> Subject: Re: [Sip] use of MESSAGE method for passing display 
> information
> to the user
> 
> 
> This seems to me to be an entirely appropriate use of page 
> mode MESSAGE. 
> Specifically, I would interpret a message, sent by an 
> automaton, that is 
> intended to be rendered for and interpreted by a human being 
> in a timely 
> manner, to fall into the category of "instant message."
> 
> 
> 
> Drage, Keith (Keith) wrote:
> > Within 3GPP, there is a requirement for intermediate 
> servers to pass textual information for display to the user. 
> This may be related to a dialog or not.
> > 
> > A typical example may be (in the case of a prepay user):
> > 
> > "Please top up your units or your call may be terminated 
> prematurely".
> > 
> > There are a number of methods that are defined which 
> essentially convey body information between User Agents 
> (INFO, NOTIFY, MESSAGE, PUBLISH?).
> > 
> > Some of these would appear more suitable that others for 
> passing this information. 
> > 
> > Of the existing methods, MESSAGE would appear to be the 
> most suitable (and indeed is the one selected by some of the 
> experts involved). However the internet draft specifically 
> talks about the body being an "Instant Message".
> > 
> > Rather than get into a situation similar to that which 
> affects INFO (i.e. people seem to have implemented various 
> applications on INFO and IETF experts say INFO is not 
> appropriate for that application), could I request an 
> exchange of views on the applicability or not of MESSAGE for 
> this type of information, and if not, what solution would 
> otherwise be suggested.
> > 
> > Note that the information would normally be expected to 
> come from some network based entity (acting as a UA). When 
> related to a dialog, the source may well be some B2BUA 
> between the two end UAs involved in the dialog.
> > 
> > Keith Drage
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> > 
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Wed Sep  4 04:46:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20633
	for <sip-archive@odin.ietf.org>; Wed, 4 Sep 2002 04:46:25 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g848lgC05287
	for sip-archive@odin.ietf.org; Wed, 4 Sep 2002 04:47:42 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g848lLo05268;
	Wed, 4 Sep 2002 04:47:21 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g848kco05225
	for <sip@optimus.ietf.org>; Wed, 4 Sep 2002 04:46:38 -0400
Received: from lohi.eng.song.fi (lohi.eng.song.fi [195.10.149.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20621
	for <sip@ietf.org>; Wed, 4 Sep 2002 04:44:50 -0400 (EDT)
Received: from jh by lohi.eng.song.fi with local (Exim 3.34 #1 (Debian))
	id 17mVno-0000wJ-00; Wed, 04 Sep 2002 11:46:20 +0300
From: Juha Heinanen <jh@lohi.eng.song.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15733.51292.85389.463358@lohi.eng.song.fi>
Date: Wed, 4 Sep 2002 11:46:20 +0300
To: hisham.khartabil@nokia.com
Cc: <bcampbell@dynamicsoft.com>, <drage@lucent.com>, <sip@ietf.org>
Subject: RE: [Sip] use of MESSAGE method for passing display information to the user
In-Reply-To: <2038BCC78B1AD641891A0D1AE133DBB7C2059C@esebe019.ntc.nokia.com>
References: <2038BCC78B1AD641891A0D1AE133DBB7C2059C@esebe019.ntc.nokia.com>
X-Mailer: VM 6.97 under Emacs 20.7.2
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

could you please move this discussion to sipping list.

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



From mailnull@www1.ietf.org  Wed Sep  4 06:20:14 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21805
	for <sip-archive@odin.ietf.org>; Wed, 4 Sep 2002 06:20:14 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g84ALJo10268
	for sip-archive@odin.ietf.org; Wed, 4 Sep 2002 06:21:19 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g84AJgo10196;
	Wed, 4 Sep 2002 06:19:42 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g84AISo10151
	for <sip@optimus.ietf.org>; Wed, 4 Sep 2002 06:18:28 -0400
Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21773
	for <sip@ietf.org>; Wed, 4 Sep 2002 06:16:52 -0400 (EDT)
From: aki.niemi@nokia.com
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g84AIP711196
	for <sip@ietf.org>; Wed, 4 Sep 2002 13:18:25 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5d21787f96ac158f23168@esvir03nok.nokia.com>;
 Wed, 4 Sep 2002 13:18:23 +0300
Received: from esebe013.NOE.Nokia.com ([172.21.138.52]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 4 Sep 2002 13:18:23 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] use of MESSAGE method for passing display information to the user
Date: Wed, 4 Sep 2002 13:18:23 +0300
Message-ID: <98C7D2E5BCD2374C9AAE0BCD2E9C1DD90FEDCC@esebe013.ntc.nokia.com>
Thread-Topic: [Sip] use of MESSAGE method for passing display information to the user
Thread-Index: AcJTZPQWVVah48yARvuA/AK0oqEsHgAgycAgAASdUHA=
To: <hisham.khartabil@nokia.com>, <bcampbell@dynamicsoft.com>,
        <drage@lucent.com>
Cc: <sip@ietf.org>
X-OriginalArrivalTime: 04 Sep 2002 10:18:23.0496 (UTC) FILETIME=[666B3080:01C253FC]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g84AISo10152
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

> How useful can this be when I'm talking on the phone and I 
> get an Instant Message with text telling me that I'm running 
> out of credit? How often do you stop talking on the phone 
> just to read your SMS? 

At least my phone gives me an audible indication that a message has arrived. Especially while I'm using a hands-free set, I often read SMSs *while* I'm talking.

> The most likely scenario is that your 
> phone call will be cut short, then you go and read your IM 
> and only then you find out what the contents of the IM were.

Same as a user ignoring an in-band notification of low credit.
 
> I think this type of information should be conveyed by a 
> special tone that the phone plays or by a light going red of 
> the phone. Perhaps implementation specific. The point is that 
> we can't standardise that "your running out of credit" type 
> of IM MUST be rendered to the user.

Again, the phone can give you an audible tone when a message arrives. If its urgent, maybe the tone is a little louder...

> Having said that, I agree that MESSAGE is the choice if 
> contents of a request are to be rendered to a user. But if I, 
> as a phone manufacturer want my phone to flash a red light 
> when suck IM is received, then I can't.

Are you saying that a phone should have a red light for indicating low credit? If that same red light is used for anything else, you will anyway need to stop talking to determine exactly why it's blinking this time.

Perhaps this sort of functionality could be implemented using the Explode-Your-Phone header? ;-D

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



From mailnull@www1.ietf.org  Wed Sep  4 09:32:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28119
	for <sip-archive@odin.ietf.org>; Wed, 4 Sep 2002 09:32:44 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g84DXq021506
	for sip-archive@odin.ietf.org; Wed, 4 Sep 2002 09:33:52 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g84DWYo21219;
	Wed, 4 Sep 2002 09:32:34 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g84DTNo20994
	for <sip@optimus.ietf.org>; Wed, 4 Sep 2002 09:29:23 -0400
Received: from magus.nostrum.com (root@magus.nostrum.com [66.119.225.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27782
	for <sip@ietf.org>; Wed, 4 Sep 2002 09:27:45 -0400 (EDT)
Received: from dynamicsoft.com (root@magus.nostrum.com [66.119.225.66])
	by magus.nostrum.com (8.12.5/8.12.5) with ESMTP id g84DTIpA049549;
	Wed, 4 Sep 2002 08:29:19 -0500 (CDT)
Message-ID: <3D760A8F.8000306@dynamicsoft.com>
Date: Wed, 04 Sep 2002 08:28:47 -0500
From: Ben Campbell <bcampbell@dynamicsoft.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: hisham.khartabil@nokia.com
CC: drage@lucent.com, sip@ietf.org
Subject: Re: [Sip] use of MESSAGE method for passing display information to
 the user
References: <2038BCC78B1AD641891A0D1AE133DBB7C2059C@esebe019.ntc.nokia.com>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

hisham.khartabil@nokia.com wrote:
> How useful can this be when I'm talking on the phone and I get an Instant Message with text telling me that I'm running out of credit? How often do you stop talking on the phone just to read your SMS? The most likely scenario is that your phone call will be cut short, then you go and read your IM and only then you find out what the contents of the IM were.
> 
> I think this type of information should be conveyed by a special tone that the phone plays or by a light going red of the phone. Perhaps implementation specific. The point is that we can't standardise that "your running out of credit" type of IM MUST be rendered to the user.
> 
> Having said that, I agree that MESSAGE is the choice if contents of a request are to be rendered to a user. But if I, as a phone manufacturer want my phone to flash a red light when suck IM is received, then I can't.
> 

Hmm. My phone plays a tone and turns on an indicator whenever it gets 
SMS. I think this is just a matter of phone user interface design.



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



From mailnull@www1.ietf.org  Wed Sep  4 10:13:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00751
	for <sip-archive@odin.ietf.org>; Wed, 4 Sep 2002 10:13:34 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g84EEho23998
	for sip-archive@odin.ietf.org; Wed, 4 Sep 2002 10:14:43 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g84EDBo23956;
	Wed, 4 Sep 2002 10:13:11 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g84EBvo23893
	for <sip@optimus.ietf.org>; Wed, 4 Sep 2002 10:11:57 -0400
Received: from cozumel.we-host.com (cozumel.we-host.com.47.37.216.in-addr.arpa [216.37.47.200] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA00565
	for <sip@ietf.org>; Wed, 4 Sep 2002 10:10:18 -0400 (EDT)
Received: (qmail 30621 invoked from network); 4 Sep 2002 13:59:56 -0000
Received: from adsl-65-71-246-65.dsl.rcsntx.swbell.net (HELO StephenJames) (65.71.246.65)
  by cozumel.we-host.com.47.37.216.in-addr.arpa with SMTP; 4 Sep 2002 13:59:56 -0000
Message-ID: <000e01c2541c$e7fc6310$6979a8c0@StephenJames>
From: "Stephen James" <sjames@voiceramp.com>
To: <sip@ietf.org>
Date: Wed, 4 Sep 2002 09:10:34 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000B_01C253F2.ECDF6690"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: [Sip] Call-ID and Authorization
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_000B_01C253F2.ECDF6690
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Question with regard to RFC 3261, Call-ID and Authorization.
Suppose I send an Request (Invite) with a specific Call-ID and that=20
Request is rejected with a 401/407 requiring authentication (user to =
user
or user to proxy). When resubmitting the request is it a MUST that=20
the Call-ID be the same Call-ID as in the original request? There are
some statements that seem to imply that, but there is nothing that
seems to require it.=20

Stephen James


------=_NextPart_000_000B_01C253F2.ECDF6690
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 6.00.2719.2200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Question with regard to RFC 3261, =
Call-ID and=20
Authorization.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Suppose I send an Request (Invite) with =
a specific=20
Call-ID and that </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Request is rejected with a 401/407 =
requiring=20
authentication (user to user</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>or user to proxy). When resubmitting =
the request is=20
it a MUST that </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the Call-ID be the same Call-ID as in =
the original=20
request? There are</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>some statements that seem to imply =
that, but there=20
is nothing that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>seems to require it. </FONT></DIV><FONT =
face=3DArial=20
size=3D2>
<DIV><BR>Stephen James</DIV>
<DIV></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_000B_01C253F2.ECDF6690--


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



From mailnull@www1.ietf.org  Wed Sep  4 14:33:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14703
	for <sip-archive@odin.ietf.org>; Wed, 4 Sep 2002 14:33:40 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g84IYom08032
	for sip-archive@odin.ietf.org; Wed, 4 Sep 2002 14:34:50 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g84IYWo08016;
	Wed, 4 Sep 2002 14:34:32 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g84IXpo07939
	for <sip@optimus.ietf.org>; Wed, 4 Sep 2002 14:33:51 -0400
Received: from tnint11.telogy.design.ti.com ([209.116.120.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14626
	for <sip@ietf.org>; Wed, 4 Sep 2002 14:32:11 -0400 (EDT)
Received: by tnint11.telogy.design.ti.com with Internet Mail Service (5.5.2653.19)
	id <R6SWRDV0>; Wed, 4 Sep 2002 14:33:06 -0400
Message-ID: <37A3C2F21006D611995100B0D0F9B73C012A2B9D@tnint11.telogy.design.ti.com>
From: "Yadavalli, Satyamurthy" <syadavalli@telogy.com>
To: sip@ietf.org, sip-implementors@cs.columbia.edu
Date: Wed, 4 Sep 2002 14:33:01 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="GB2312"
Subject: [Sip] RE: [Sip-implementors] sip version
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

Am I missing something here?

I thought the RFC3261 SHOULD have assigned a different SIP version number...
that's what a version number is meant for!

- Satya

> -----Original Message-----
> From: Yadavalli, Satyamurthy [mailto:syadavalli@telogy.com]
> Sent: Thursday, August 15, 2002 12:18 PM
> To: sip@ietf.org; sip-implementors@cs.columbia.edu
> Subject: [Sip-implementors] sip version
> 
> 
> The new SIP RFC-3261 specifies the SIP protocol version to be 
> used as SIP/2.0. So was it with the obsoleted RFC 2543.
> How do SIP entities distinguish between these implementations?
> 
> Thanks,
> Satya
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@cs.columbia.edu
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Thu Sep  5 03:03:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11640
	for <sip-archive@odin.ietf.org>; Thu, 5 Sep 2002 03:03:56 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8575C813077
	for sip-archive@odin.ietf.org; Thu, 5 Sep 2002 03:05:12 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8573mo13029;
	Thu, 5 Sep 2002 03:03:48 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8572Qo12982
	for <sip@optimus.ietf.org>; Thu, 5 Sep 2002 03:02:26 -0400
Received: from wiprom2mx1.wipro.com (wiprom2mx1.wipro.com [203.197.164.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11604
	for <sip@ietf.org>; Thu, 5 Sep 2002 03:00:38 -0400 (EDT)
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5])
	by wiprom2mx1.wipro.com (8.11.3/8.11.3) with SMTP id g8571gi23227
	for <sip@ietf.org>; Thu, 5 Sep 2002 12:31:42 +0530 (IST)
Received: from blr-m1-bh2.wipro.com ([10.115.50.92]) by
          ace.mail.wipro.com (Netscape Messaging Server 4.15) with ESMTP
          id H1YE6O00.N0M for <sip@ietf.org>; Thu, 5 Sep 2002 12:31:36 +0530 
Received: from blr-m1-msg.wipro.com ([10.115.50.99]) by blr-m1-bh2.wipro.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 5 Sep 2002 12:31:36 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01C254AA.13066A9B"
Date: Thu, 5 Sep 2002 12:31:36 +0530
Message-ID: <860BFD79D602F0409BB9EEA42B9E3BC0279F7E@blr-m1-msg.wipro.com>
X-MS-Has-Attach: yes
Thread-Topic: Tool to test Refer with replaces
Thread-Index: AcI0pki1GXsLQAZMReKLTN91D0WbOQgA0FYw
From: "Reshmi Nair" <reshmi.nair@wipro.com>
To: <sip@ietf.org>
X-OriginalArrivalTime: 05 Sep 2002 07:01:36.0171 (UTC) FILETIME=[131E1FB0:01C254AA]
Subject: [Sip] FW: [Sip-implementors] Tool to test Refer with replaces
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C254AA.13066A9B
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,
Thanks for your answers on refer subscription.

I am reposting a query here, which I had posted some time back on the =
implementors list.
Please let me know if there are any rfc-3261 compliant sipua's available =
which I can use for testing.

Regards,
Reshmi


-----Original Message-----
From: Reshmi Nair=20
Sent: Friday, July 26, 2002 6:44 PM
To: sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] Tool to test Refer with replaces


Hi,

I wanted to know if there's any tool or SIP UA implementation available =
which I could use for testing scenarios involving REFER with & without =
the "replaces" parameter.

Any information would be of great help.

Regards,
Reshmi



------_=_NextPart_001_01C254AA.13066A9B
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Description: Wipro_Disclaimer.txt
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: base64

KioqKioqKioqKioqKioqKioqKioqKioqKipEaXNjbGFpbWVyKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKiogICAgDQogDQogSW5mb3JtYXRpb24gY29udGFp
bmVkIGluIHRoaXMgRS1NQUlMIGJlaW5nIHByb3ByaWV0YXJ5IHRvIFdpcHJvIExpbWl0ZWQgaXMg
J3ByaXZpbGVnZWQnIA0KYW5kICdjb25maWRlbnRpYWwnIGFuZCBpbnRlbmRlZCBmb3IgdXNlIG9u
bHkgYnkgdGhlIGluZGl2aWR1YWwgb3IgZW50aXR5IHRvIHdoaWNoIGl0IGlzIA0KYWRkcmVzc2Vk
LiBZb3UgYXJlIG5vdGlmaWVkIHRoYXQgYW55IHVzZSwgY29weWluZyBvciBkaXNzZW1pbmF0aW9u
IG9mIHRoZSBpbmZvcm1hdGlvbiANCmNvbnRhaW5lZCBpbiB0aGUgRS1NQUlMIGluIGFueSBtYW5u
ZXIgd2hhdHNvZXZlciBpcyBzdHJpY3RseSBwcm9oaWJpdGVkLg0KDQoqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqDQo=

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



From mailnull@www1.ietf.org  Thu Sep  5 06:46:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14359
	for <sip-archive@odin.ietf.org>; Thu, 5 Sep 2002 06:46:29 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g85Albn21842
	for sip-archive@odin.ietf.org; Thu, 5 Sep 2002 06:47:37 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85AkGo21816;
	Thu, 5 Sep 2002 06:46:16 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Aiio21767
	for <sip@optimus.ietf.org>; Thu, 5 Sep 2002 06:44:44 -0400
Received: from auemail2.firewall.lucent.com ([192.11.223.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14335
	for <sip@ietf.org>; Thu, 5 Sep 2002 06:43:05 -0400 (EDT)
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by auemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g85AiA922221
	for <sip@ietf.org>; Thu, 5 Sep 2002 06:44:10 -0400 (EDT)
Received: by en0060D057.uk.lucent.com with Internet Mail Service (5.5.2653.19)
	id <R7G052A9>; Thu, 5 Sep 2002 11:44:09 +0100
Message-ID: <475FF955A05DD411980D00508B6D5FB005E34AD8@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: Ben Campbell <bcampbell@dynamicsoft.com>
Cc: "'sip@ietf.org'" <sip@ietf.org>
Subject: RE: [Sip] use of MESSAGE method for passing display information t
	o the user
Date: Thu, 5 Sep 2002 11:44:06 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

To summarize what I understand so far from the responses.

1)	Where the information is not semantically understood by the UA, but is simply rendered to the user, then MESSAGE method is appropriate. (This is the old ISDN definition of stimulus.) Where it is sent in the context of an existing dialog by an intermediate entity between the two endpoints, that intermediate entity would have to be a B2BUA. The current 3GPP requirements we are trying to address is this one.

2)	Where the information is to be semantically understood by the UA, before it is rendered to the user (e.g. to light an appropriate lamp, or flash an appropriate ikon on a display) then an Event package with the information carried in NOTIFY would be appropriate. (This is the old ISDN definition of functional.) This would require prior UA subscription to the package, which in my opinion is not unreasonable, as the terminal subscribes to packages that match its display or other characteristics.

3)	Nobody is proposing that these methods do not support this capability, or suggesting we need to go away and work on new methods (via SIPPING then SIP).

Thanks for your assistance.

Keith

> -----Original Message-----
> From: Ben Campbell [mailto:bcampbell@dynamicsoft.com]
> Sent: 03 September 2002 17:09
> To: Drage, Keith (Keith)
> Cc: 'sip@ietf.org'
> Subject: Re: [Sip] use of MESSAGE method for passing display 
> information
> to the user
> 
> 
> This seems to me to be an entirely appropriate use of page 
> mode MESSAGE. 
> Specifically, I would interpret a message, sent by an 
> automaton, that is 
> intended to be rendered for and interpreted by a human being 
> in a timely 
> manner, to fall into the category of "instant message."
> 
> 
> 
> Drage, Keith (Keith) wrote:
> > Within 3GPP, there is a requirement for intermediate 
> servers to pass textual information for display to the user. 
> This may be related to a dialog or not.
> > 
> > A typical example may be (in the case of a prepay user):
> > 
> > "Please top up your units or your call may be terminated 
> prematurely".
> > 
> > There are a number of methods that are defined which 
> essentially convey body information between User Agents 
> (INFO, NOTIFY, MESSAGE, PUBLISH?).
> > 
> > Some of these would appear more suitable that others for 
> passing this information. 
> > 
> > Of the existing methods, MESSAGE would appear to be the 
> most suitable (and indeed is the one selected by some of the 
> experts involved). However the internet draft specifically 
> talks about the body being an "Instant Message".
> > 
> > Rather than get into a situation similar to that which 
> affects INFO (i.e. people seem to have implemented various 
> applications on INFO and IETF experts say INFO is not 
> appropriate for that application), could I request an 
> exchange of views on the applicability or not of MESSAGE for 
> this type of information, and if not, what solution would 
> otherwise be suggested.
> > 
> > Note that the information would normally be expected to 
> come from some network based entity (acting as a UA). When 
> related to a dialog, the source may well be some B2BUA 
> between the two end UAs involved in the dialog.
> > 
> > Keith Drage
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> > 
> 
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Thu Sep  5 12:01:01 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23694
	for <sip-archive@odin.ietf.org>; Thu, 5 Sep 2002 12:01:01 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g85G2BF07781
	for sip-archive@odin.ietf.org; Thu, 5 Sep 2002 12:02:11 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85G1io07744;
	Thu, 5 Sep 2002 12:01:44 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85FxCo07502
	for <sip@optimus.ietf.org>; Thu, 5 Sep 2002 11:59:12 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23573
	for <sip@ietf.org>; Thu, 5 Sep 2002 11:57:32 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.52])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g85Fv6YH016765;
	Thu, 5 Sep 2002 11:57:06 -0400 (EDT)
Message-ID: <3D777ED0.8000305@dynamicsoft.com>
Date: Thu, 05 Sep 2002 11:57:04 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tirthankar Saha <tsaha@del3.vsnl.net.in>
CC: SIP Mailing List <sip@ietf.org>
Subject: Re: [Sip] Session Timer Issues and Proposal
References: <001401c24f47$6e654c80$24c9c5cb@t>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Adam has made many good points in response to this, and I generally 
agree with what he is saying. Some more comments inline.

Tirthankar Saha wrote:

> Issues:
> 
> 1) Why do we have to refresh the session with a re-INVITE?
> 
> Lots of unnecessary processing for a simple keepalive.
>    - 3 way handshake
>    - sdp re-negotiation & possible re-opening of media channels
> 
> This could have been justified earlier when the refresh-intervals were
> recommended to be 30 mins. but this feature is now being considered to be
> used for keeping the NAT bindings alive. 

Oh? It should not. We removed REGISTER refreshes as a way to keep NAT 
bindings alive from the most recent draft-ietf-sip-nat.

> I think using the re-INVITE to refresh a dialog is seriously flawed; I can't
> think of any good reason for having this procedure.
> We MUST address this issue ASAP.

The current draft in the repository allows for UPDATE, which is 
"lighter" than INVITE. It also allows for the UPDATE to be used without 
SDP, so there is no new offer/answer exchange. I don't think you can ask 
for much ligher than that.



> 
> 
> 2) Unnecessary processing & complications with "refresher" param.
> 
> What do we gain by negotiating who's going to be the referesher?
> On the other hand, extra work is required which can be avoided by having a
> simple rule for deciding the refresher (ref. proposal below). This way we
> can avoid the min-timer checks for DoS attacks and reduce interoperability
> issues arising out
> of certain non-conforming vendor implementations which don't use this param
> at all.

Originally, the UAC was the refresher, period.

However, subsequent discussions on the list indicated that people wanted 
a model whereby session timer could work so long as only one side 
supported the extension. This would facilitate its introduction. That 
means that either UAC or UAS could be the refresher. Once you do that, 
you need an explicit way to determine and indicate who it is. I don't 
know of a simpler way to do this given the constraints that it should 
work so long as one of the two UA support it.

Another design goal was to allow proxies to set the timer. Indeed, the 
primary point of the extension is for proxies to get refreshes on their 
call state, so they can know when to expire it. Just like other 
soft-state methods - such as REGISTER and SUBSCRIBE - the refresh 
intervals need to be negotiated. Otherwise, you get locked into an 
interval that you may find is useless, and you cannot ever change it 
since its burned into the spec. Now, once you add negotiation, the user 
to user nature of the timer introduces the DoS problems that need to be 
addressed.



> 
> 3) Unnecessary confusion with call-hold.
> 
> There's no way to tell whether incoming re-INVITE is for session-refresh or
> session-modification.
> 
>  e.g   A & B in call & A is the refresher. Now, B holds the call and A is
> still the refresher due to a specific case of negotiation
> of refresher param.
> If, A sends the refresh then B can't determine whether A is trying to modify
> the session or refresh the session. B would reject the request (because he's
> holding the call & won't allow A to unhold himself) & A MIGHT terminate the
> call.

This doesn't make sense to me. The origin field in the SDP will indicate 
whether it has changed. Thus, it is easy to determine whether this is a 
refresh or modification. Furthermore, if you use UPDATE, there need not 
even be SDP.


> 
> 4) No uniform strategy for dialog keep-alive : separate procedures for
> INVITE,REGISTER & SUBSCRIBE/NOTIFY dialogs.

I think Adam has addressed this point, so there is no need for me to 
belabor it.


> 
> 
> PROPOSAL
> ========
> 
> Common dialog-keepalive strategy though I've considered only INVITE dialogs.
> Can be extended easily for other dialogs (I feel).
> 
> New feature tag (for use in Supported,Require headers):
>     dtimer
> 
> New Header
>     Dialog-Expires: <time-in-seconds>
> 
>        - Can be included in ANY request and/or its response except BYE or
>          other requests terminating the dialog.
> 
>        - It MUST be included in the dialog-refresh request
>          which can be any valid request in the dialog although
>          the INFO request is recommended.
> 
>        - It is recommended that the UA intiating the dialog
>          SHOULD send this header in the initial INVITE.
> 
>        - If the request doesn't contain this header, the UAS can
>          add it in the response ONLY if the Supported header of
>          request contains the feature-tag "dtimer".
> 
>        - The endpoint (uac/uas) MUST include a supported header in
>          the message containing this header with the feature-tag "dtimer".
> 
>        - Proxies MUST NOT CHANGE this header.
> 
>        - Logic for determining the refresher:
> 
>          if (message contains "Supported: dtimer")
>                         AND
>             ("Dialog-Expires" hdr present in the message)
>          {
> 
>              if (message is REQUEST) {
>                   uac becomes the refresher
>              } else {
>                   uas becomes the refresher
>              }
> 
>          }
>          else
>          {
>              feature disabled
>          }
> 
>          ie. whoever sends this hdr in a transaction first becomes
>          the refresher.

It seems that you are getting simplification from two changes - proxies 
cannot request the timer, and the timer value cannot be negotiated. 
These are two important features of the specification as it stands today.

Again, one of the design goals is for proxies to request session timer, 
since they are the primary consumers of the timer. A UA has other means 
at its disposal to determine that a session has terminated (RTCP 
heartbeats, for example). So, a session timer whereby the proxies cant 
request it, is broken.

Similar point about negotiation of the value.


> 
>        - Logic for (re)starting expiry timer:
>             if (incoming-message contains "Dialog-Expires" header)
>                     AND
>                (message contains Supported header with the
>                 feature-tag "dtimer")
> 
>        - refresher role CANNOT be renegotiated.
> 
>          QUERY: Is this OK? Would renegotiation be needed in any case?
>          If yes, does it justify the extra renegotiation logic reqd.?

IMHO, idempotency of INVITE requires that whatever procedure is done for 
INVITE, also be the one that is implied for re-INVITE.

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Thu Sep  5 14:03:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29862
	for <sip-archive@odin.ietf.org>; Thu, 5 Sep 2002 14:03:52 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g85I52t16551
	for sip-archive@odin.ietf.org; Thu, 5 Sep 2002 14:05:02 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85I3qp16429;
	Thu, 5 Sep 2002 14:03:52 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85GIZG08677
	for <sip@optimus.ietf.org>; Thu, 5 Sep 2002 12:18:35 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24218
	for <sip@ietf.org>; Thu, 5 Sep 2002 12:16:54 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.52])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g85GI2YH016773;
	Thu, 5 Sep 2002 12:18:02 -0400 (EDT)
Message-ID: <3D7783B8.4000702@dynamicsoft.com>
Date: Thu, 05 Sep 2002 12:18:00 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Stephen James <sjames@voiceramp.com>
CC: sip@ietf.org
Subject: Re: [Sip] Call-ID and Authorization
References: <000e01c2541c$e7fc6310$6979a8c0@StephenJames>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Section 8.1.3.5 spells this out explicitly:

  In all of the above cases, the request is retried by creating a new
    request with the appropriate modifications.  This new request
    constitutes a new transaction and SHOULD have the same value of the
    Call-ID, To, and From of the previous request, but the CSeq should
    contain a new sequence number that is one higher than the previous.

-Jonathan R.

Stephen James wrote:
> Question with regard to RFC 3261, Call-ID and Authorization.
> Suppose I send an Request (Invite) with a specific Call-ID and that
> Request is rejected with a 401/407 requiring authentication (user to user
> or user to proxy). When resubmitting the request is it a MUST that
> the Call-ID be the same Call-ID as in the original request? There are
> some statements that seem to imply that, but there is nothing that
> seems to require it.
> 
> Stephen James
>  


-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Thu Sep  5 14:28:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01038
	for <sip-archive@odin.ietf.org>; Thu, 5 Sep 2002 14:28:56 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g85IU4518890
	for sip-archive@odin.ietf.org; Thu, 5 Sep 2002 14:30:04 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85IPip18516;
	Thu, 5 Sep 2002 14:25:44 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85GnWG10073
	for <sip@optimus.ietf.org>; Thu, 5 Sep 2002 12:49:32 -0400
Received: from imo-d01.mx.aol.com (imo-d01.mx.aol.com [205.188.157.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25073
	for <sip@ietf.org>; Thu, 5 Sep 2002 12:47:51 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d01.mx.aol.com (mail_out_v34.10.) id x.f3.20aa2d74 (3940);
	Thu, 5 Sep 2002 12:48:54 -0400 (EDT)
Message-ID: <f3.20aa2d74.2aa8e4f6@aol.com>
Date: Thu, 5 Sep 2002 12:48:54 EDT
Subject: Re: [Sip] RE: [Sip-implementors] sip version
To: syadavalli@telogy.com, sip@ietf.org, sip-implementors@cs.columbia.edu
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_f3.20aa2d74.2aa8e4f6_boundary"
X-Mailer: AOL 6.0 for Windows US sub 353
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>


--part1_f3.20aa2d74.2aa8e4f6_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 9/4/02 3:16:44 PM Eastern Daylight Time, 
syadavalli@telogy.com writes:


> Am I missing something here?
> 
> I thought the RFC3261 SHOULD have assigned a different SIP version number...
> that's what a version number is meant for!
> 
> - Satya
> 

I'm waiting with bated breadth for the answer to this one!

Mike Pierce
Artel


--part1_f3.20aa2d74.2aa8e4f6_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 9/4/02 3:16:44 PM Eastern Daylight Time, syadavalli@telogy.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Am I missing something here?
<BR>
<BR>I thought the RFC3261 SHOULD have assigned a different SIP version number...
<BR>that's what a version number is meant for!
<BR>
<BR>- Satya
<BR></BLOCKQUOTE>
<BR>
<BR>I'm waiting with bated breadth for the answer to this one!
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

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



From mailnull@www1.ietf.org  Thu Sep  5 14:29:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01098
	for <sip-archive@odin.ietf.org>; Thu, 5 Sep 2002 14:29:34 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g85IUiO19081
	for sip-archive@odin.ietf.org; Thu, 5 Sep 2002 14:30:44 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85IU5p18904;
	Thu, 5 Sep 2002 14:30:05 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Gvkp10534
	for <sip@optimus.ietf.org>; Thu, 5 Sep 2002 12:57:46 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25221
	for <sip@ietf.org>; Thu, 5 Sep 2002 12:56:05 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.52])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g85Gv9YH016862;
	Thu, 5 Sep 2002 12:57:10 -0400 (EDT)
Message-ID: <3D778CE3.70407@dynamicsoft.com>
Date: Thu, 05 Sep 2002 12:57:07 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
CC: Robert Sparks <rsparks@dynamicsoft.com>,
        Adam Roach
 <adam@dynamicsoft.com>, hisham.khartabil@nokia.com,
        sip@ietf.org
Subject: Re: [Sip] Max-Forward checking at UAS
References: <9BF66EBF6BEFD942915B4D4D45C051F3A64086@DYN-TX-EXCH-001.dynamicsoft.com> <1030125957.1356.54.camel@dhcp116.dfw.dynamicsoft.com> <3D673D27.20F0D8A6@lmf.ericsson.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

jumping in a bit late. Responses inline.

Christer Holmberg wrote:
> Hi,
> 
> I agree with you all that the cookie should not be used to determine if the
> sender does things according to RFC3261 or RFC2543. However, even if you
> say that "z9hG4bK" means that the branch-id is "safe" to use as transaction
> identifier, it indirectly does indicate if the sender does things according
> to RFC3261 or RFC2543, doesn't it? Anyway, there is no idea to argue about
> that :)

Absolutely not.

As Adam and Robert have pointed out, you cannot infer anything from the 
via cookie except that the branch ID is a transaction ID. 
Implementations aren't binary in terms of their support for 3261. Some 
support some of the features, others more, and others, all. Such mixed 
implementations are a reality, and that is why we choose to support 
backwards compatibility on a feature-by-feature basis rather than 
glomming it all into a new version of SIP.


> 
> I also agree with Robert that at least a UAS should not care about the
> value of the Max-Forwards header, since the message has reached its
> "destination". I guess another question is what proxies do when they
> receive a message without the header. A few options (all implementation
> specific, I think, so there is no idea to define any specific behaviour in
> the spec):

Well, I think I disagree with Robert on this one.

I would like Max-Forwards treatment at a server to be generic to all 
servers - proxies and UAS alike. If a proxy rejects a request with 
Max-Forwards: 0, so too should a UAS. However, the point is really one 
of philosophy; I can find no specific problem with a UAS ignoring 
Max-Forwards.

An interesting point of comparison, however, is the TTL header in the IP 
packet. Do hosts look at this field or not? I suspect they don't, which 
would probably support Robert's position....


-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Thu Sep  5 14:46:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02281
	for <sip-archive@odin.ietf.org>; Thu, 5 Sep 2002 14:46:40 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g85Ilox21963
	for sip-archive@odin.ietf.org; Thu, 5 Sep 2002 14:47:50 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85IlWp21716;
	Thu, 5 Sep 2002 14:47:32 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Id0p20356
	for <sip@optimus.ietf.org>; Thu, 5 Sep 2002 14:39:00 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01668
	for <sip@ietf.org>; Thu, 5 Sep 2002 14:37:20 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.52])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g85IcKYH016941;
	Thu, 5 Sep 2002 14:38:22 -0400 (EDT)
Message-ID: <3D77A49A.3060908@dynamicsoft.com>
Date: Thu, 05 Sep 2002 14:38:18 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Prasanna <prasanna@huawei.com>
CC: sip@ietf.org, chengzhengqun@huawei.com, li_wen@huawei.com
Subject: Re: [Sip] How to respond if the request has no Call-ID
References: <KPEPLFDHIJPLNICJNCJJOELFCBAA.prasanna@huawei.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Time for my normal "sip error handling" speech...

The spec does not dictate the error treatment for unrecoverable errors 
caused by misimplemented clients and servers. It would be futile. In 
these cases, an implementation is encouraged to be as forgiving as 
possible. In this case, either discarding the message, or a 4xx without 
a call-id header, would be reasonable choices.

Please don't read 21.4.1 so literally that it implies that you are 
supposed to generate a 4xx to a request without an invite. Its merely 
providing some general guidance on usage of the reason phrase. However, 
I will make a note to change the example for draft standard.

-Jonathan R.

Prasanna wrote:
> Hi,
> 	According to RFC 3261 section 21.4.1
> "The Reason-Phrase SHOULD identify the syntax problem in more detail,
> for
>    example, "Missing Call-ID header field"."
> 
> If a request comes without a Call-ID header field, what call-ID should
> the
> 400 response bear.
> 
> The same issue is applicable for "To" "From" CSeq" headers also.
> 
> Another issue is, if a request does not bear a "Via" header, where
> should
> the response go, if at all the UAS decides to respond.
> 
> Thanks in advance for the responses,
> Regards,
> Prasanna
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 


-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Thu Sep  5 14:56:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02904
	for <sip-archive@odin.ietf.org>; Thu, 5 Sep 2002 14:56:29 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g85IveO23596
	for sip-archive@odin.ietf.org; Thu, 5 Sep 2002 14:57:40 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85IvLp23447;
	Thu, 5 Sep 2002 14:57:21 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Ilep21925
	for <sip@optimus.ietf.org>; Thu, 5 Sep 2002 14:47:40 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02189
	for <sip@ietf.org>; Thu, 5 Sep 2002 14:46:00 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.52])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g85IkxYH016945;
	Thu, 5 Sep 2002 14:46:59 -0400 (EDT)
Message-ID: <3D77A6A1.2050407@dynamicsoft.com>
Date: Thu, 05 Sep 2002 14:46:57 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tom-PT Taylor <taylor@nortelnetworks.com>
CC: "'sip@ietf.org'" <sip@ietf.org>
Subject: Re: [Sip] Missing Phrase In RFC 3261 Sec. 23.2 (S/MIME)?
References: <4D79C746863DD51197690002A52CDA0001E8A79D@zcard0kc.ca.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Old mail, but I want to make sure we capture any possible bugs in the 
spec. Responses inline:

Tom-PT Taylor wrote:
> Section 23.2 of RFC 3261 has this text: 
> 
> When a UAC sends a request containing an S/MIME body that initiates a 
>    dialog, or sends a non-INVITE request outside the context of a 
>    dialog, the UAC SHOULD structure the body as an S/MIME [sic, no
> period] 

I'm confused. In my version of the spec, it does in fact read properly:

When a UAC sends a request containing an S/MIME body that initiates a
    dialog, or sends a non-INVITE request outside the context of a
    dialog, the UAC SHOULD structure the body as an S/MIME
    'multipart/signed' CMS SignedData body.  If the desired CMS service
    is EnvelopedData (and the public key of the target user is known),
    the UAC SHOULD send the EnvelopedData message encapsulated within a
    SignedData message.

Are you sure you are looking at 3261, and not bis-09? This was an error 
in older versions of the draft, but it was caught.

-Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Thu Sep  5 15:01:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03116
	for <sip-archive@odin.ietf.org>; Thu, 5 Sep 2002 15:01:00 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g85J2AC24448
	for sip-archive@odin.ietf.org; Thu, 5 Sep 2002 15:02:10 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85J1pp24218;
	Thu, 5 Sep 2002 15:01:51 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85ItCp23175
	for <sip@optimus.ietf.org>; Thu, 5 Sep 2002 14:55:12 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02682
	for <sip@ietf.org>; Thu, 5 Sep 2002 14:53:31 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.52])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g85IsaYH016951;
	Thu, 5 Sep 2002 14:54:37 -0400 (EDT)
Message-ID: <3D77A86B.1030500@dynamicsoft.com>
Date: Thu, 05 Sep 2002 14:54:35 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: JackLix@attbi.com
CC: sip@ietf.org
Subject: Re: [Sip] caller preferences and RFC 2533
References: <KEEOKCLFOECADJEMHAJGKEJHCEAA.JackLix@attbi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

responses inline.

Jack W. Lix wrote:
> Hi,
> 
> I've been reviewing
> http://search.ietf.org/internet-drafts/draft-ietf-sip-message-06.txt and
> have a couple questions.
> 
> First, in section 5.2 the following paragraph is found:
> 
> 
>>The proxy then takes each URI in the target set (the set of URI it is
>>going to proxy to), and obtains there capabilities as an RFC 2533
>>formatted feature set. If target URI was obtained through a
>>registration, the proxy computes the feature set by taking all
>>Contact URI parameters except for the q and expires parameters, and
>>converting them to RFC 2533 syntax using the rules of Section 6.1.
> 
> 
> Should the word "there" in the 1st sentence be their or it's?  Or,
> should
> the sentence read "and there obtains capabilities"?


I think "its capabilities" is correct. Its referring to the capabilities 
of one of the target URI. I fixed it.

> 
> Second, the text makes many references to RFC 2533 and that is fine for
> describing the intended behaviour.  However, it implies that you MUST
> translate the headers into RFC 2533 format.  Doesn't that impose an
> implementation rather than define the protocol?  Is there any reason
> that I
> really have to use RFC 2533?

There is no need to actually do any format conversions to rfc 2533 
syntax, no. Whats important is that the rule matching procedures of 
rfc2533 are used. The easiest way to do that is to specify that the 
behavior of your implementation has to be as if it had done the 
conversion, and then ran rfc2533.

I'll clarify that.

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Fri Sep  6 11:41:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08191
	for <sip-archive@odin.ietf.org>; Fri, 6 Sep 2002 11:41:35 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g86Fgj716482
	for sip-archive@odin.ietf.org; Fri, 6 Sep 2002 11:42:45 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86FfsX16082;
	Fri, 6 Sep 2002 11:41:54 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Kgmt29890
	for <sip@optimus.ietf.org>; Thu, 5 Sep 2002 16:42:48 -0400
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05352
	for <sip@ietf.org>; Thu, 5 Sep 2002 16:41:06 -0400 (EDT)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g85KfvT09204;
	Thu, 5 Sep 2002 16:41:57 -0400 (EDT)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <RL8PCT0S>; Thu, 5 Sep 2002 16:41:59 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A85F@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>
Cc: "'sip@ietf.org'" <sip@ietf.org>
Subject: RE: [Sip] Missing Phrase In RFC 3261 Sec. 23.2 (S/MIME)?
Date: Thu, 5 Sep 2002 16:41:56 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

I see it's correct in the on-line version.  Not sure what happened, and
sorry to waste your time.

> -----Original Message-----
> From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com] 
> Sent: Thursday, September 05, 2002 2:47 PM
> To: Taylor, Tom-PT [CAR:B602:EXCH]
> Cc: 'sip@ietf.org'
> Subject: Re: [Sip] Missing Phrase In RFC 3261 Sec. 23.2 (S/MIME)?
> 
> 
> Old mail, but I want to make sure we capture any possible bugs in the 
> spec. Responses inline:
> 
> Tom-PT Taylor wrote:
> > Section 23.2 of RFC 3261 has this text:
> > 
> > When a UAC sends a request containing an S/MIME body that 
> initiates a 
> >    dialog, or sends a non-INVITE request outside the context of a 
> >    dialog, the UAC SHOULD structure the body as an S/MIME [sic, no 
> > period]
> 
> I'm confused. In my version of the spec, it does in fact read 
> properly:
> 
> When a UAC sends a request containing an S/MIME body that initiates a
>     dialog, or sends a non-INVITE request outside the context of a
>     dialog, the UAC SHOULD structure the body as an S/MIME
>     'multipart/signed' CMS SignedData body.  If the desired 
> CMS service
>     is EnvelopedData (and the public key of the target user is known),
>     the UAC SHOULD send the EnvelopedData message 
> encapsulated within a
>     SignedData message.
> 
> Are you sure you are looking at 3261, and not bis-09? This 
> was an error 
> in older versions of the draft, but it was caught.
> 
> -Jonathan R.
> -- 
> Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
> Chief Scientist                             First Floor
> dynamicsoft                                 East Hanover, NJ 07936
> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com
> 
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Fri Sep  6 11:47:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08679
	for <sip-archive@odin.ietf.org>; Fri, 6 Sep 2002 11:47:59 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g86Fn8l17654
	for sip-archive@odin.ietf.org; Fri, 6 Sep 2002 11:49:08 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86FlrX17152;
	Fri, 6 Sep 2002 11:47:53 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g860dft12856
	for <sip@optimus.ietf.org>; Thu, 5 Sep 2002 20:39:41 -0400
Received: from mta0 ([61.144.161.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12671
	for <sip@ietf.org>; Thu, 5 Sep 2002 20:37:57 -0400 (EDT)
Received: from PRASANNA (mta0 [172.17.1.62])
 by mta0.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.8 (built Jul 12
 2002)) with ESMTPA id <0H1Z00IW2R20TZ@mta0.huawei.com> for sip@ietf.org; Fri,
 06 Sep 2002 08:37:13 +0800 (CST)
Date: Fri, 06 Sep 2002 08:42:27 +0800
From: Prasanna <prasanna@huawei.com>
Subject: RE: [Sip] How to respond if the request has no Call-ID
In-reply-to: <3D77A49A.3060908@dynamicsoft.com>
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: sip@ietf.org, chengzhengqun@huawei.com, li_wen@huawei.com
Message-id: <KPEPLFDHIJPLNICJNCJJAEBBCCAA.prasanna@huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Thanks for the comments Mr. Rosenberg.  Since this particular case is also a
part of the torture test cases (2.11), I was really stumped on this.
Regards,
Prasanna

-----Original Message-----
From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
Sent: Friday, September 06, 2002 2:38 AM
To: Prasanna
Cc: sip@ietf.org; chengzhengqun@huawei.com; li_wen@huawei.com
Subject: Re: [Sip] How to respond if the request has no Call-ID


Time for my normal "sip error handling" speech...

The spec does not dictate the error treatment for unrecoverable errors
caused by misimplemented clients and servers. It would be futile. In
these cases, an implementation is encouraged to be as forgiving as
possible. In this case, either discarding the message, or a 4xx without
a call-id header, would be reasonable choices.

Please don't read 21.4.1 so literally that it implies that you are
supposed to generate a 4xx to a request without an invite. Its merely
providing some general guidance on usage of the reason phrase. However,
I will make a note to change the example for draft standard.

-Jonathan R.

Prasanna wrote:
> Hi,
> 	According to RFC 3261 section 21.4.1
> "The Reason-Phrase SHOULD identify the syntax problem in more detail,
> for
>    example, "Missing Call-ID header field"."
>
> If a request comes without a Call-ID header field, what call-ID should
> the
> 400 response bear.
>
> The same issue is applicable for "To" "From" CSeq" headers also.
>
> Another issue is, if a request does not bear a "Via" header, where
> should
> the response go, if at all the UAS decides to respond.
>
> Thanks in advance for the responses,
> Regards,
> Prasanna
>
>
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>


--
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Fri Sep  6 13:58:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15642
	for <sip-archive@odin.ietf.org>; Fri, 6 Sep 2002 13:58:31 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g86HxhT30501
	for sip-archive@odin.ietf.org; Fri, 6 Sep 2002 13:59:43 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86HxHX30464;
	Fri, 6 Sep 2002 13:59:17 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86HPAX29131
	for <sip@optimus.ietf.org>; Fri, 6 Sep 2002 13:25:10 -0400
Received: from postmark.nist.gov (pullyou.nist.gov [129.6.16.93])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14607
	for <sip@ietf.org>; Fri, 6 Sep 2002 13:23:29 -0400 (EDT)
Received: from jitterbug.antd.nist.gov (jitterbug.antd.nist.gov [129.6.55.8])
	by postmark.nist.gov (8.12.5/8.12.5) with ESMTP id g86HP50Y027771;
	Fri, 6 Sep 2002 13:25:05 -0400 (EDT)
Date: Fri, 6 Sep 2002 13:25:05 -0400 (EDT)
From: "M. Ranganathan" <mranga@nist.gov>
X-X-Sender:  <mranga@jitterbug.antd.nist.gov>
To: <Mpierce1@aol.com>
cc: <syadavalli@telogy.com>, <sip@ietf.org>,
        <sip-implementors@cs.columbia.edu>
Subject: Re: [Sip] RE: [Sip-implementors] sip version
In-Reply-To: <f3.20aa2d74.2aa8e4f6@aol.com>
Message-ID: <Pine.LNX.4.33.0209061322540.17665-100000@jitterbug.antd.nist.gov>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>


But it does! The new version number is 2.0z9hG4bK

(where z9hG4bK is the branch magic cookie :-)

Ranga.

On Thu, 5 Sep 2002 Mpierce1@aol.com wrote:

> In a message dated 9/4/02 3:16:44 PM Eastern Daylight Time,
> syadavalli@telogy.com writes:
>
>
> > Am I missing something here?
> >
> > I thought the RFC3261 SHOULD have assigned a different SIP version number...
> > that's what a version number is meant for!
> >
> > - Satya
> >
>
> I'm waiting with bated breadth for the answer to this one!
>
> Mike Pierce
> Artel
>
>

-- 
M. Ranganathan
Advanced Networking Technologies Divsion
National Institute of Standards and Technology (NIST)
100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899.
Tel: 301 975 3664 ; Fax: 301 590 0932

Advanced Networking Technologies For the People!


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



From mailnull@www1.ietf.org  Fri Sep  6 13:58:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15656
	for <sip-archive@odin.ietf.org>; Fri, 6 Sep 2002 13:58:35 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g86Hxkl30514
	for sip-archive@odin.ietf.org; Fri, 6 Sep 2002 13:59:46 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86HwwX30439;
	Fri, 6 Sep 2002 13:58:58 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86Ehct11528
	for <sip@optimus.ietf.org>; Fri, 6 Sep 2002 10:43:38 -0400
Received: from hotmail.com (f46.sea2.hotmail.com [207.68.165.46])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05617
	for <sip@ietf.org>; Fri, 6 Sep 2002 10:41:58 -0400 (EDT)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 6 Sep 2002 07:43:05 -0700
Received: from 213.156.59.10 by sea2fd.sea2.hotmail.msn.com with HTTP;
	Fri, 06 Sep 2002 14:43:04 GMT
X-Originating-IP: [213.156.59.10]
From: "e e" <satjuice53@hotmail.com>
To: sip@ietf.org
Date: Fri, 06 Sep 2002 14:43:04 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F462eyuslVsO3WMEOE90002f661@hotmail.com>
X-OriginalArrivalTime: 06 Sep 2002 14:43:05.0073 (UTC) FILETIME=[B5670610:01C255B3]
Subject: [Sip] CSCF - 3GPP IMS question about unknown header
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>


Hello to everybody,
I need some help.
Does anyone know which is the behaviour of CSCF (P-CSCF, I-CSCF and S-CSCF) 
of 3GPP IMS when these entities try to process an unknown header (e.g. a 
proprietary header specified by a company) ?
Do they threat such messages just ignoring the header and proceeding in the 
standard way?

Thank you in advance,

Peter


_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

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



From mailnull@www1.ietf.org  Fri Sep  6 16:14:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20110
	for <sip-archive@odin.ietf.org>; Fri, 6 Sep 2002 16:14:59 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g86KGBF03683
	for sip-archive@odin.ietf.org; Fri, 6 Sep 2002 16:16:11 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86KEHX03582;
	Fri, 6 Sep 2002 16:14:17 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86KBYX03440
	for <sip@optimus.ietf.org>; Fri, 6 Sep 2002 16:11:34 -0400
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19896
	for <sip@ietf.org>; Fri, 6 Sep 2002 16:09:51 -0400 (EDT)
Received: from TXDWILLIS2 (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with ESMTP id g86KB0312910;
	Fri, 6 Sep 2002 15:11:01 -0500
From: "Dean Willis" <dean.willis@softarmor.com>
To: "'e e'" <satjuice53@hotmail.com>, <sip@ietf.org>
Subject: RE: [Sip] CSCF - 3GPP IMS question about unknown header
Date: Fri, 6 Sep 2002 15:10:29 -0500
Message-ID: <00a701c255e1$73c5f170$1e036e3f@TXDWILLIS2>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <F462eyuslVsO3WMEOE90002f661@hotmail.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


This would properly be a question for 3GPP, not IETF.

SIP proxies compliant to RFC 3261 will pass the unknown header along
unmodified.

Whether or not the 3GPP x-CSCFs will be RFC3261 compliant proxies or
some kind of user agent will be determined by 3GPP. 

My initial guess at a response might be "it depends -- which x-CSCF are
you talking about, and in which operator's network?"

--
dean

> -----Original Message-----
> From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of e e
> Sent: Friday, September 06, 2002 9:43 AM
> To: sip@ietf.org
> Subject: [Sip] CSCF - 3GPP IMS question about unknown header
> 
> 
> 
> Hello to everybody,
> I need some help.
> Does anyone know which is the behaviour of CSCF (P-CSCF, 
> I-CSCF and S-CSCF) 
> of 3GPP IMS when these entities try to process an unknown 
> header (e.g. a 
> proprietary header specified by a company) ?
> Do they threat such messages just ignoring the header and 
> proceeding in the 
> standard way?
> 
> Thank you in advance,
> 
> Peter
> 
> 
> _________________________________________________________________
> MSN Photos is the easiest way to share and print your photos: 
> http://photos.msn.com/support/worldwide.aspx
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sipping@ietf.org for new developments on the 
> application of sip
> 
> 

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



From mailnull@www1.ietf.org  Fri Sep  6 16:37:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20661
	for <sip-archive@odin.ietf.org>; Fri, 6 Sep 2002 16:37:26 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g86Kccq05641
	for sip-archive@odin.ietf.org; Fri, 6 Sep 2002 16:38:38 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86KbmX05610;
	Fri, 6 Sep 2002 16:37:48 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86KanX05031
	for <sip@optimus.ietf.org>; Fri, 6 Sep 2002 16:36:49 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20612
	for <sip@ietf.org>; Fri, 6 Sep 2002 16:35:05 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.47])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g86KZxYH017900;
	Fri, 6 Sep 2002 16:35:59 -0400 (EDT)
Message-ID: <3D7911AD.8040308@dynamicsoft.com>
Date: Fri, 06 Sep 2002 16:35:57 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Adam Roach <adam@dynamicsoft.com>
CC: "'Kedar Patil'" <kpatil@sta.samsung.com>,
        "'aki.niemi@nokia.com'"
 <aki.niemi@nokia.com>,
        hisham.khartabil@nokia.com, drage@lucent.com, krisztian.kiss@nokia.com,
        sip@ietf.org
Subject: Re: [Sip] use of MESSAGE method for passing display information t
  o the user
References: <9BF66EBF6BEFD942915B4D4D45C051F3A640D0@DYN-TX-EXCH-001.dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Let me add one more point to Adam's.

There does exist a common means by which the user can express
willingness to receive instant messages about different types
of events. This mechanism is in widespread use for email today.
Its called "the web". One would go to a web page for stock quotes,
say, and sign up by giving your SIP URL. You would then pick
which stocks you like, and it would send an IM when they go
up or down by too much.

Since the information in the IM is itself for consumption
by a human, not an automata, the process by which the
information can be requested can also be done by human,
through the web.

-Jonathan R.

Adam Roach wrote:
> I understand the intention behind what you are proposing.
> 
> The ability to have these kind of things be interpretable
> by atomata would certainly be useful; however, the proposal
> that we define some unified "network notification" event
> package is a bit unworkable. Doing so would first require
> standardization of all of the information that the network
> would want to convey so that you can define a machine-readable
> format for each. To do so requires standardizing all of the
> network-provided services, which is something we have
> strenuously avoided doing. We instead provide tools that can
> be combined to provide services, since such an approach is
> far more powerful.
> 
> I propose that we hold the course: when we identify information
> that is commonly communicated and warrants interpretation by
> atomata (such as a message waiting indication), we can define
> an event package for it. However, if service designers want to
> communicate information from the network to the terminal, they
> should feel free to use MESSAGE to do so.
> 
> /a
> 
> 
> -----Original Message-----
> From: Kedar Patil [mailto:kpatil@sta.samsung.com]
> Sent: Tuesday, September 03, 2002 12:00
> To: 'aki.niemi@nokia.com'; hisham.khartabil@nokia.com; drage@lucent.com;
> krisztian.kiss@nokia.com
> Cc: sip@ietf.org
> Subject: RE: [Sip] use of MESSAGE method for passing display information t o
> the user
> 
> 
> Hi, 
> I have some input on having event-notification package 
> for this : 
> Although it looks like a user may have to subscribe to 
> "Credit overflow" kind of event all the time, I guess 
> this is going to be only during the calls. 
> This one case may be solved by "MESSAGE". However, is it the 
> only case? I believe there could be more. The commonality 
> is that all of them are going to be from the network (not the 
> peer) and are asynchrounous. For this why not have an event 
> pacakge under the framework of RFC3265. A UA may subscribe 
> to network of all network events, and any such event would 
> trigger the appropriate event notification. 
> If all the events are for human interaction then "Message" 
> looks fine. Is there any event where user interaction is 
> taken over by automatic actions by s/w config? (e.g. in this 
> case automatic credit upgrade just enough to avoid premature 
> call termination!) 
> The question remains : Is there one network element to which 
> a UA may have to subscribe or many? 
> thanks, 
> = Kedar = 
> 
> 
> 
>>-----Original Message----- 
>>From: aki.niemi@nokia.com [mailto:aki.niemi@nokia.com] 
>>Sent: Tuesday, September 03, 2002 3:57 AM 
>>To: hisham.khartabil@nokia.com; drage@lucent.com; 
>>krisztian.kiss@nokia.com; sip@ietf.org 
>>Subject: RE: [Sip] use of MESSAGE method for passing display 
>>information 
>>to the user 
>>
>>
>>Is it feasible to have that subscription state hanging around 
>>just in case you may some day run out of credit? 
>>
>>Cheers, 
>>Aki 
>>
>>
>>>-----Original Message----- 
>>>From: Khartabil Hisham (NMP/Helsinki) 
>>>Sent: Tuesday, September 03, 2002 11:49 AM 
>>>To: Niemi Aki (NET/Espoo); drage@lucent.com; Kiss Krisztian 
>>>(NRC/Tampere); sip@ietf.org 
>>>Subject: RE: [Sip] use of MESSAGE method for passing display 
>>>information 
>>>to the user 
>>>
>>>
>>>You're not subscribing to get an instant message, you're 
>>>subscribing to get information about your prepaid units. 
>>>
>>>Why is it unsolicited? 
>>>
>>>/Hisham 
>>>
>>>
>>>>-----Original Message----- 
>>>>From: Niemi Aki (NET/Espoo) 
>>>>Sent: Tuesday, September 03, 2002 10:47 AM 
>>>>To: Khartabil Hisham (NMP/Helsinki); drage@lucent.com; Kiss 
>>>
>>>Krisztian 
>>>
>>>>(NRC/Tampere); sip@ietf.org 
>>>>Subject: RE: [Sip] use of MESSAGE method for passing display 
>>>>information 
>>>>to the user 
>>>>
>>>>
>>>>This application seems rather different from the presence 
>>>>type notifications because it seems these notifications are 
>>>>unsolicited. So to me MESSAGE seems like a perfect fit. I 
>>>>don't have to "subscribe" in order to receive instant 
>>>
>>>messages either. 
>>>
>>>>So by saying "Notification package" perhaps you mean a new 
>>>>MIME type specifically for these unsolicited notifications? 
>>>>
>>>>Cheers, 
>>>>Aki 
>>>>
>>>>
>>>>>-----Original Message----- 
>>>>>From: ext hisham.khartabil@nokia.com 
>>>>>[mailto:hisham.khartabil@nokia.com] 
>>>>>Sent: Tuesday, September 03, 2002 10:26 AM 
>>>>>To: drage@lucent.com; Kiss Krisztian (NRC/Tampere); sip@ietf.org 
>>>>>Subject: RE: [Sip] use of MESSAGE method for passing display 
>>>>>information 
>>>>>to the user 
>>>>>
>>>>>
>>>>>I guess it could be done that way, but you might find that 
>>>>>others would prefer some sort of Notification package for 
>>>>>this type of thing. 
>>>>>
>>>>>/Hisham 
>>>>>
>>>>>
>>>>>>-----Original Message----- 
>>>>>>From: ext Drage, Keith (Keith) [mailto:drage@lucent.com] 
>>>>>>Sent: Monday, September 02, 2002 8:02 PM 
>>>>>>To: Kiss Krisztian (NRC/Tampere); Drage, Keith (Keith); 
>>>>>
>>>>sip@ietf.org 
>>>>
>>>>>>Subject: RE: [Sip] use of MESSAGE method for passing display 
>>>>>>information 
>>>>>>to the user 
>>>>>>
>>>>>>
>>>>>>With hindsight, I drafted the last paragraph of my original 
>>>>>>message badly. 
>>>>>>
>>>>>>Rather than try to paraphrase again, I will select a direct 
>>>>>>quote from the message draft abstract: 
>>>>>>
>>>>>>The MESSAGE method is an extension to the Session 
>>>>>
>>>>>Initiation Protocol 
>>>>>
>>>>>>   (SIP) that allows the transfer of Instant Messages.  
>>>>>>MESSAGE requests 
>>>>>>   carry the content in the form of MIME body parts.  
>>>>>>
>>>>>>My concern is not over how such a body should be coded. The 
>>>>>>questions is does such a usage to carry "Please top up your 
>>>>>>units or your call may be terminated prematurely" qualify as 
>>>>>>an Instant Message, i.e. is it within the semantics of 
>>>>>>MESSAGE to perform this function. 
>>>>>>
>>>>>>Keith 
>>>>>>
>>>>>>
>>>>>>>-----Original Message----- 
>>>>>>>From: krisztian.kiss@nokia.com 
>>>>>>
>>>[mailto:krisztian.kiss@nokia.com] 
>>>
>>>>>>>Sent: 02 September 2002 17:43 
>>>>>>>To: drage@lucent.com; sip@ietf.org 
>>>>>>>Subject: RE: [Sip] use of MESSAGE method for 
>>>>>>
>>passing display 
>>
>>>>>>>information 
>>>>>>>to the user 
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>Keith, 
>>>>>>>
>>>>>>>
>>>>>>>>Within 3GPP, there is a requirement for 
>>>>>>>
>>>intermediate servers 
>>>
>>>>>>>>to pass textual information for display to the 
>>>>>>>
>>>user. This may 
>>>
>>>>>>>>be related to a dialog or not. 
>>>>>>>>
>>>>>>>>A typical example may be (in the case of a prepay user): 
>>>>>>>>
>>>>>>>>"Please top up your units or your call may be terminated 
>>>>>>>
>>>>>>>prematurely". 
>>>>>>>
>>>>>>>>There are a number of methods that are defined which 
>>>>>>>>essentially convey body information between User Agents 
>>>>>>>>(INFO, NOTIFY, MESSAGE, PUBLISH?). 
>>>>>>>>
>>>>>>>>Some of these would appear more suitable that others for 
>>>>>>>>passing this information. 
>>>>>>>>
>>>>>>>>Of the existing methods, MESSAGE would appear to be 
>>>>>>>
>>>the most 
>>>
>>>>>>>>suitable (and indeed is the one selected by some of the 
>>>>>>>>experts involved). However the internet draft 
>>>>>>>
>>specifically 
>>
>>>>>>>>talks about the body being an "Instant Message". 
>>>>>>>
>>>>>>>draft-ietf-sip-message-06 states that the body can 
>>>>>>
>>be of ANY 
>>
>>>>>>>MIME type: 
>>>>>>>"The body of the request will contain the message to be 
>>>>>>
>>>>delivered. 
>>>>
>>>>>>>   This body can be of any MIME type, including 
>>>>>>
>>message/cpim." 
>>
>>>>>>>Regards, 
>>>>>>>Krisztian 
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>Rather than get into a situation similar to that which 
>>>>>>>>affects INFO (i.e. people seem to have 
>>>>>>>
>>implemented various 
>>
>>>>>>>>applications on INFO and IETF experts say INFO is not 
>>>>>>>>appropriate for that application), could I request an 
>>>>>>>>exchange of views on the applicability or not of 
>>>>>>>
>>>MESSAGE for 
>>>
>>>>>>>>this type of information, and if not, what solution would 
>>>>>>>>otherwise be suggested. 
>>>>>>>>
>>>>>>>>Note that the information would normally be 
>>>>>>>
>>>expected to come 
>>>
>>>>>>>>from some network based entity (acting as a UA). 
>>>>>>>
>>>When related 
>>>
>>>>>>>>to a dialog, the source may well be some B2BUA 
>>>>>>>
>>between the 
>>
>>>>>>>>two end UAs involved in the dialog. 
>>>>>>>>
>>>>>>>>Keith Drage 
>>>>>>>>_______________________________________________ 
>>>>>>>>Sip mailing list  
>>>>>>>
> https://www1.ietf.org/mailman/listinfo/sip 
> 
>>>>>>>This list is for NEW development of the core SIP Protocol 
>>>>>>>Use sip-implementors@cs.columbia.edu for questions on 
>>>>>>
>>>>current sip 
>>>>
>>>>>>>Use sipping@ietf.org for new developments on the 
>>>>>>
>>>>>application of sip 
>>>>>
>>>>>_______________________________________________ 
>>>>>Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip 
>>>>>This list is for NEW development of the core SIP Protocol 
>>>>>Use sip-implementors@cs.columbia.edu for questions on 
>>>>
>>current sip 
>>
>>>>>Use sipping@ietf.org for new developments on the 
>>>>
>>>application of sip 
>>>
>>>>_______________________________________________ 
>>>>Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip 
>>>>This list is for NEW development of the core SIP Protocol 
>>>>Use sip-implementors@cs.columbia.edu for questions on current sip 
>>>>Use sipping@ietf.org for new developments on the 
>>>
>>application of sip 
>>
> _______________________________________________ 
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip 
> This list is for NEW development of the core SIP Protocol 
> Use sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application of sip 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 


-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Fri Sep  6 16:42:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20766
	for <sip-archive@odin.ietf.org>; Fri, 6 Sep 2002 16:42:12 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g86KhOZ05902
	for sip-archive@odin.ietf.org; Fri, 6 Sep 2002 16:43:24 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86Kg7X05817;
	Fri, 6 Sep 2002 16:42:07 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86KfJX05750
	for <sip@optimus.ietf.org>; Fri, 6 Sep 2002 16:41:19 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20692
	for <sip@ietf.org>; Fri, 6 Sep 2002 16:39:36 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.47])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g86KedYH017903;
	Fri, 6 Sep 2002 16:40:40 -0400 (EDT)
Message-ID: <3D7912C6.1020603@dynamicsoft.com>
Date: Fri, 06 Sep 2002 16:40:38 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Drage, Keith (Keith)" <drage@lucent.com>
CC: Ben Campbell <bcampbell@dynamicsoft.com>, "'sip@ietf.org'"
 <sip@ietf.org>
Subject: Re: [Sip] use of MESSAGE method for passing display information t
 o the user
References: <475FF955A05DD411980D00508B6D5FB005E34AD8@en0033exch001u.uk.lucent.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I concur on all points below. I just want to add a few sentences of 
motivation, inline:

Drage, Keith (Keith) wrote:
 > To summarize what I understand so far from the responses.
 >
 > 1)	Where the information is not semantically understood by the UA,
 > but is simply rendered to the user, then MESSAGE method is
 > appropriate. (This is the old ISDN definition of stimulus.)

Correct.

 > Where it
 > is sent in the context of an existing dialog by an intermediate
 > entity between the two endpoints, that intermediate entity would have
 > to be a B2BUA. The current 3GPP requirements we are trying to address
 > is this one.

Right.

 >
 > 2)	Where the information is to be semantically understood by the UA,
 > before it is rendered to the user (e.g. to light an appropriate lamp,
 > or flash an appropriate ikon on a display) then an Event package with
 > the information carried in NOTIFY would be appropriate. (This is the
 > old ISDN definition of functional.) This would require prior UA
 > subscription to the package, which in my opinion is not unreasonable,
 > as the terminal subscribes to packages that match its display or
 > other characteristics.

Exactly. It makes no sense to send information to an automata unless you 
know it can process it, and is ready and interested in receiving it. A 
package provides all of that, and allows you to negotiate the types, for 
example.

For a message meant for a human, you can be more flexible. Even if they 
device can't render the type, the human is smart enough to do something 
about it - download a new renderer, or forward it to their email 
account, or ask someone for help, or whatever. Humans are also better at 
understanding whether a message that is receivd late (because it was 
stored in a message store as the user was offline when it was sent) is 
still useful or not. An automata cannot easily make this judgement, and 
so storage of things like notifications to an automata (for message 
waiting, for example), make less sense to me.


-Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Fri Sep  6 17:06:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21476
	for <sip-archive@odin.ietf.org>; Fri, 6 Sep 2002 17:06:54 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g86L86B07652
	for sip-archive@odin.ietf.org; Fri, 6 Sep 2002 17:08:06 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86L6gX07025;
	Fri, 6 Sep 2002 17:06:42 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86L4BX06935
	for <sip@optimus.ietf.org>; Fri, 6 Sep 2002 17:04:11 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21331
	for <sip@ietf.org>; Fri, 6 Sep 2002 17:02:27 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.47])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g86L3WYH017917;
	Fri, 6 Sep 2002 17:03:32 -0400 (EDT)
Message-ID: <3D791822.70609@dynamicsoft.com>
Date: Fri, 06 Sep 2002 17:03:30 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
CC: Bob Penfield <bpenfield@acmepacket.com>, sip@ietf.org
Subject: Re: [Sip] Re: RFC 3264  An Offer/Answer Model Session Description
  Protocol
References: <3D6EACB3.CC2C8F04@cisco.com> <00e701c25350$b5a7b030$2300000a@BPenfield> <3D74D154.4279B5DB@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Bob's interpretation is correct. It means that each sid maintains its 
own mapping of payload type numbers to codecs, and that mapping applies 
to any offers and answers sent within the dialog by that UA.

Usage of the same payload type numbers for the same codec in each 
direction (ie. using PT 100 for g.723 from A to B and from B to A) is 
SHOULD strength, I believe. We allowed them to be asymmetric primarily 
to support H.323 interop.

-Jonathan R.

Paul Kyzivat wrote:
> Bob - OK, if you read it that way then all is ok.
> It wasn't obvious to me that this is what that text
> intended, but since it is only an example I guess it
> is good enough.
> 
> 	Thanks,
> 	Paul
> 
> Bob Penfield wrote:
> 
>>----- Original Message -----
>>From: "Paul Kyzivat" <pkyzivat@cisco.com>
>>
>>>I have a question of interpretation regarding section 8.3.2 (Changing the
>>
>>Set of Media Formats).
>>
>>>When describing how an offer is to be constructed for a change (a
>>
>>reINVITE), this section says:
>>
>>>"However, in the case of RTP, the mapping from a particular dynamic
>>
>>payload type number to a particular codec within that media stream MUST NOT
>>change for the duration of a session.  For example, if A generates an offer
>>with G.711 assigned to dynamic payload type number 46, payload type number
>>46 MUST refer to G.711 from that point forward in any offers or answers for
>>that media stream within the session."
>>
>>>What I question is the "or answers" at the end of this section. This seems
>>
>>to be inconsistent with section 6.1, which says that the payload type
>>numbers for answers may be different than those for offers.
>>
>>I believe it is talking about any offers or answers that a given endpoint
>>generates during the session since either side may re-INVITE. The two side
>>may use different payload numbers, but each has to use its same original
>>payload number in all SDP it generates.
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 


-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Fri Sep  6 17:11:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20109
	for <sip-archive@odin.ietf.org>; Fri, 6 Sep 2002 16:14:59 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g86KGA603671
	for sip-archive@odin.ietf.org; Fri, 6 Sep 2002 16:16:10 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86KEZX03612;
	Fri, 6 Sep 2002 16:14:35 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86KBxX03451
	for <sip@optimus.ietf.org>; Fri, 6 Sep 2002 16:11:59 -0400
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19905
	for <sip@ietf.org>; Fri, 6 Sep 2002 16:10:16 -0400 (EDT)
Received: from TXDWILLIS2 (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with ESMTP id g86KB0312908;
	Fri, 6 Sep 2002 15:11:03 -0500
From: "Dean Willis" <dwillis@dynamicsoft.com>
To: <sip@ietf.org>
Cc: <jdrosen@dynamicsoft.com>, <rohan@cisco.com>, <jo@ipdialog.com>,
        <brian.rosen@marconi.com>
Date: Fri, 6 Sep 2002 15:10:29 -0500
Message-ID: <00a901c255e1$76077d00$1e036e3f@TXDWILLIS2>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [Sip] WGLC for draft-ietf-sip-nat
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


Version 02 of draft-ietf-sip-nat was posted two months ago (5Jul02) in
response to earlier suggestions and there seem to have been no further
comments.

I am therefore requesting working group last call of the sip-nat draft.
According to our posted milestones, this should have concluded last call
last week, so we're not doing too badly. I'd like to send it on to the
IESG by 20Sep, so get your comments in posthaste.

The draft in question is available at:

http://www.ietf.org/internet-drafts/draft-ietf-sip-nat-02.txt

As usual, please post dicussion to the list and copy the lead author,
jdrosen@dynamicsoft.com

Thanks,

--
Dean

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



From mailnull@www1.ietf.org  Fri Sep  6 17:16:24 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21819
	for <sip-archive@odin.ietf.org>; Fri, 6 Sep 2002 17:16:24 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g86LHa808198
	for sip-archive@odin.ietf.org; Fri, 6 Sep 2002 17:17:36 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86LG0X08145;
	Fri, 6 Sep 2002 17:16:00 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86KuSX06259
	for <sip@optimus.ietf.org>; Fri, 6 Sep 2002 16:56:28 -0400
Received: from mail.aastra.com (mail.aastra.com [216.94.98.95])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21064
	for <sip@ietf.org>; Fri, 6 Sep 2002 16:54:45 -0400 (EDT)
Received: by mail.aastra.com with Internet Mail Service (5.5.2653.19)
	id <S2JPM9NA>; Fri, 6 Sep 2002 16:52:37 -0400
Message-ID: <F924CEFBBF62D611A0C600D0B76ED03712FE7F@h3s68a245n132.user.nortelnetworks.com>
From: Jitender Arora <jarora@aastra.com>
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: sip@ietf.org
Date: Fri, 6 Sep 2002 16:51:15 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sip] Regarding SIP CDR inforamtion ( from a Media Gateway Controller p
 erspective)
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

Hi ,

     could somebody please point to the draft or RFC which contains the
information about how the 
     CDR ( call detail records ) are generated for the SIP calls ( what all
informaion should be there 
     in the CDR ) from the Media Gateway Controller Perspective . 

     Is there any document available for this ...If yes please let me know
....

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



From mailnull@www1.ietf.org  Fri Sep  6 19:09:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24195
	for <sip-archive@odin.ietf.org>; Fri, 6 Sep 2002 19:09:43 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g86NAvO13537
	for sip-archive@odin.ietf.org; Fri, 6 Sep 2002 19:10:57 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86N9uX13504;
	Fri, 6 Sep 2002 19:09:56 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86N8IX13477
	for <sip@optimus.ietf.org>; Fri, 6 Sep 2002 19:08:18 -0400
Received: from ihemail2.firewall.lucent.com ([192.11.222.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24148
	for <sip@ietf.org>; Fri, 6 Sep 2002 19:06:34 -0400 (EDT)
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by ihemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g86N89J01062
	for <sip@ietf.org>; Fri, 6 Sep 2002 19:08:09 -0400 (EDT)
Received: by en0060D057.uk.lucent.com with Internet Mail Service (5.5.2653.19)
	id <R7G0616H>; Sat, 7 Sep 2002 00:08:08 +0100
Message-ID: <475FF955A05DD411980D00508B6D5FB005E34E72@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'e e'" <satjuice53@hotmail.com>, sip@ietf.org
Subject: RE: [Sip] CSCF - 3GPP IMS question about unknown header
Date: Sat, 7 Sep 2002 00:08:07 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

Depending on whose storyline you read 3GPP CSCFs are either proxies, or B2BUAs, or some horrible and illegal mismash of both. Different types of CSCFs fall into different categories. 

As Dean says, proxies relay unknown headers from one side to the other.

RFC 3261 does not define the transfer characteristics of B2BUAs. While UASs are required to ignore unrecognized headers received in requests, this appears to be specified such that the request gets processed by the UAS despite the header. It would therefore appear to be legal to pass the unrecognized header to the B2B UAC for transmission at the outgoing side. For responses I guess similar arguments would apply.

So in summary, those 3GPP entities that behave as proxies will pass on; those 3GPP entities that behave as B2BUAs may (and in practice probably will); those that are argued to be neither one or the other will do one or the other.

Note that the sipchanges draft says that there is no such thing as a company defined proprietary header. All proprietary headers are defined in internet drafts --> informational RFCs. Therefore by a stroke of publication they will all cease to exist!

Keith


Keith Drage
Lucent Technologies
Tel: +44 1793 776249
Email: drage@lucent.com 

> -----Original Message-----
> From: Dean Willis [mailto:dean.willis@softarmor.com]
> Sent: 06 September 2002 21:10
> To: 'e e'; sip@ietf.org
> Subject: RE: [Sip] CSCF - 3GPP IMS question about unknown header
> 
> 
> 
> This would properly be a question for 3GPP, not IETF.
> 
> SIP proxies compliant to RFC 3261 will pass the unknown header along
> unmodified.
> 
> Whether or not the 3GPP x-CSCFs will be RFC3261 compliant proxies or
> some kind of user agent will be determined by 3GPP. 
> 
> My initial guess at a response might be "it depends -- which 
> x-CSCF are
> you talking about, and in which operator's network?"
> 
> --
> dean
> 
> > -----Original Message-----
> > From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On 
> Behalf Of e e
> > Sent: Friday, September 06, 2002 9:43 AM
> > To: sip@ietf.org
> > Subject: [Sip] CSCF - 3GPP IMS question about unknown header
> > 
> > 
> > 
> > Hello to everybody,
> > I need some help.
> > Does anyone know which is the behaviour of CSCF (P-CSCF, 
> > I-CSCF and S-CSCF) 
> > of 3GPP IMS when these entities try to process an unknown 
> > header (e.g. a 
> > proprietary header specified by a company) ?
> > Do they threat such messages just ignoring the header and 
> > proceeding in the 
> > standard way?
> > 
> > Thank you in advance,
> > 
> > Peter
> > 
> > 
> > _________________________________________________________________
> > MSN Photos is the easiest way to share and print your photos: 
> > http://photos.msn.com/support/worldwide.aspx
> > 
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current 
> > sip Use sipping@ietf.org for new developments on the 
> > application of sip
> > 
> > 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Fri Sep  6 20:08:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25033
	for <sip-archive@odin.ietf.org>; Fri, 6 Sep 2002 20:08:19 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8709Yl16044
	for sip-archive@odin.ietf.org; Fri, 6 Sep 2002 20:09:34 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8709GX16032;
	Fri, 6 Sep 2002 20:09:16 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8708UX15993
	for <sip@optimus.ietf.org>; Fri, 6 Sep 2002 20:08:30 -0400
Received: from localhost.localdomain (adsl-64-219-190-5.dsl.rcsntx.swbell.net [64.219.190.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25004
	for <sip@ietf.org>; Fri, 6 Sep 2002 20:06:42 -0400 (EDT)
Received: from infravast.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (8.11.6/8.11.6) with ESMTP id g870IPY31338;
	Fri, 6 Sep 2002 19:18:33 -0500
Message-ID: <3D7945D1.ECF0EE63@infravast.com>
Date: Fri, 06 Sep 2002 19:18:25 -0500
From: Chris Martin <chris@infravast.com>
Reply-To: chris@infravast.com
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-3 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Dean Willis <dwillis@dynamicsoft.com>
CC: sip@ietf.org, jdrosen@dynamicsoft.com, rohan@cisco.com, jo@ipdialog.com,
        brian.rosen@marconi.com
Subject: Re: [Sip] WGLC for draft-ietf-sip-nat
References: <00a901c255e1$76077d00$1e036e3f@TXDWILLIS2>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I have been absent from this list for awhile, and just caught this
message... I agree with the following paragraphs, 

"In the case where there is a NAT between the client and server, in
   order for the response to always be received, the NAT binding must
   remain in existence for the duration of the transaction. Most UDP NAT
   bindings appear to have a timeout of about one minute. Therefore,
   non-INVITE transactions will have no problem. For INVITE
   transactions, the client may need to retransmit its INVITE every 20
   seconds or so, even after receiving a provisional response, in order
   to keep the binding open to receive the final response.


        OPEN ISSUE: This is awful. Perhaps a further sign that the
        only real answer is TCP? Or, perhaps this belongs in
        sipping-nat-scenarios, not here.
"

From my brief reading of the draft it appears that only SIP rport is
being requested...  how is this useful to sdp negotiation...is it merely
for such items as IM?

I think that this would be useful, and possibly not require the multiple
invites mentioned, if the rport were used in the sdp as well... then the
media could maintain the open connections.

Since I am shooting very quickly from the hip with jsut a five minute
speed read of the draft let me know if this is way off or if I am going
in the right direction and reasoning and I will put more of my thoughts
on this in a form that can be useful for use within this draft. (With a
lot more effort  :^)    )

I will try to read more this weekend and offer more input as well.

Christopher A. Martin

Dean Willis wrote:
> 
> Version 02 of draft-ietf-sip-nat was posted two months ago (5Jul02) in
> response to earlier suggestions and there seem to have been no further
> comments.
> 
> I am therefore requesting working group last call of the sip-nat draft.
> According to our posted milestones, this should have concluded last call
> last week, so we're not doing too badly. I'd like to send it on to the
> IESG by 20Sep, so get your comments in posthaste.
> 
> The draft in question is available at:
> 
> http://www.ietf.org/internet-drafts/draft-ietf-sip-nat-02.txt
> 
> As usual, please post dicussion to the list and copy the lead author,
> jdrosen@dynamicsoft.com
> 
> Thanks,
> 
> --
> Dean
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Fri Sep  6 21:46:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26738
	for <sip-archive@odin.ietf.org>; Fri, 6 Sep 2002 21:46:25 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g871ldd19920
	for sip-archive@odin.ietf.org; Fri, 6 Sep 2002 21:47:39 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g871kiX19901;
	Fri, 6 Sep 2002 21:46:44 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g871jiX19881
	for <sip@optimus.ietf.org>; Fri, 6 Sep 2002 21:45:44 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26696
	for <sip@ietf.org>; Fri, 6 Sep 2002 21:44:00 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.47])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g871iqYH018083;
	Fri, 6 Sep 2002 21:44:54 -0400 (EDT)
Message-ID: <3D795A12.2000908@dynamicsoft.com>
Date: Fri, 06 Sep 2002 21:44:50 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: chris@infravast.com
CC: Dean Willis <dwillis@dynamicsoft.com>, sip@ietf.org, rohan@cisco.com,
        jo@ipdialog.com, brian.rosen@marconi.com
Subject: Re: [Sip] WGLC for draft-ietf-sip-nat
References: <00a901c255e1$76077d00$1e036e3f@TXDWILLIS2> <3D7945D1.ECF0EE63@infravast.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Responses inline.

Chris Martin wrote:
> I have been absent from this list for awhile, and just caught this
> message... I agree with the following paragraphs, 
> 
> "In the case where there is a NAT between the client and server, in
>    order for the response to always be received, the NAT binding must
>    remain in existence for the duration of the transaction. Most UDP NAT
>    bindings appear to have a timeout of about one minute. Therefore,
>    non-INVITE transactions will have no problem. For INVITE
>    transactions, the client may need to retransmit its INVITE every 20
>    seconds or so, even after receiving a provisional response, in order
>    to keep the binding open to receive the final response.
> 
> 
>         OPEN ISSUE: This is awful. Perhaps a further sign that the
>         only real answer is TCP? Or, perhaps this belongs in
>         sipping-nat-scenarios, not here.
> "
> 
>>From my brief reading of the draft it appears that only SIP rport is
> being requested...  how is this useful to sdp negotiation...is it merely
> for such items as IM?

Its only for SIP. In fact, its only for getting responses back when the 
request is sent through a NAT; handling registrations through a NAT is 
also not addressed here. Dealing with NAT for media signaled through SDP 
is a different problem as well.

> 
> I think that this would be useful, and possibly not require the multiple
> invites mentioned, if the rport were used in the sdp as well... then the
> media could maintain the open connections.

Huh?

Media isn't sent to the proxy. To deal with media, you need something 
like STUN or SPAN/TURN.

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Fri Sep  6 22:54:14 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27906
	for <sip-archive@odin.ietf.org>; Fri, 6 Sep 2002 22:54:13 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g872tSR22630
	for sip-archive@odin.ietf.org; Fri, 6 Sep 2002 22:55:28 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g872sfX22613;
	Fri, 6 Sep 2002 22:54:41 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g872rkX22553
	for <sip@optimus.ietf.org>; Fri, 6 Sep 2002 22:53:46 -0400
Received: from localhost.localdomain (adsl-64-219-190-5.dsl.rcsntx.swbell.net [64.219.190.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27882
	for <sip@ietf.org>; Fri, 6 Sep 2002 22:52:00 -0400 (EDT)
Received: from infravast.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (8.11.6/8.11.6) with ESMTP id g8733vY31740;
	Fri, 6 Sep 2002 22:03:57 -0500
Message-ID: <3D796C9D.602673CC@infravast.com>
Date: Fri, 06 Sep 2002 22:03:57 -0500
From: Chris Martin <chris@infravast.com>
Reply-To: chris@infravast.com
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-3 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: Dean Willis <dwillis@dynamicsoft.com>, sip@ietf.org, rohan@cisco.com,
        jo@ipdialog.com, brian.rosen@marconi.com
Subject: Re: [Sip] WGLC for draft-ietf-sip-nat
References: <00a901c255e1$76077d00$1e036e3f@TXDWILLIS2> <3D7945D1.ECF0EE63@infravast.com> <3D795A12.2000908@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Jonathan Rosenberg wrote:
> 
> Responses inline.
> 
> Chris Martin wrote:
> > I have been absent from this list for awhile, and just caught this
> > message... I agree with the following paragraphs,
> >
> > "In the case where there is a NAT between the client and server, in
> >    order for the response to always be received, the NAT binding must
> >    remain in existence for the duration of the transaction. Most UDP NAT
> >    bindings appear to have a timeout of about one minute. Therefore,
> >    non-INVITE transactions will have no problem. For INVITE
> >    transactions, the client may need to retransmit its INVITE every 20
> >    seconds or so, even after receiving a provisional response, in order
> >    to keep the binding open to receive the final response.
> >
> >
> >         OPEN ISSUE: This is awful. Perhaps a further sign that the
> >         only real answer is TCP? Or, perhaps this belongs in
> >         sipping-nat-scenarios, not here.
> > "
> >
> >>From my brief reading of the draft it appears that only SIP rport is
> > being requested...  how is this useful to sdp negotiation...is it merely
> > for such items as IM?
> 
> Its only for SIP. In fact, its only for getting responses back when the
> request is sent through a NAT; handling registrations through a NAT is
> also not addressed here. Dealing with NAT for media signaled through SDP
> is a different problem as well.
> 
> >
> > I think that this would be useful, and possibly not require the multiple
> > invites mentioned, if the rport were used in the sdp as well... then the
> > media could maintain the open connections.
> 
> Huh?




> 
> Media isn't sent to the proxy. To deal with media, you need something
> like STUN or SPAN/TURN.
> 

Good catch...  :^)   Sometimes I get ahead of myself.... thats speed
reading for ya.

:^)



> -Jonathan R.
> 
> --
> Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
> Chief Scientist                             First Floor
> dynamicsoft                                 East Hanover, NJ 07936
> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Sat Sep  7 12:16:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15129
	for <sip-archive@odin.ietf.org>; Sat, 7 Sep 2002 12:16:31 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g87GHfF28398
	for sip-archive@odin.ietf.org; Sat, 7 Sep 2002 12:17:41 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g87GE9X28295;
	Sat, 7 Sep 2002 12:14:09 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g87GA5X28197
	for <sip@optimus.ietf.org>; Sat, 7 Sep 2002 12:10:05 -0400
Received: from acmepacket.com (mail1.acmepacket.com [63.67.143.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15050
	for <sip@ietf.org>; Sat, 7 Sep 2002 12:08:23 -0400 (EDT)
Received: from RPORTER [63.67.143.2] by acmepacket.com
  (SMTPD32-7.07) id A4D7B3C7005A; Sat, 07 Sep 2002 12:09:59 -0400
Message-ID: <037001c25689$41841a40$2a00000a@RPORTER>
From: "Rick W. Porter" <rporter@acmepacket.com>
To: "Jitender Arora" <jarora@aastra.com>
Cc: <sip@ietf.org>
References: <F924CEFBBF62D611A0C600D0B76ED03712FE7F@h3s68a245n132.user.nortelnetworks.com>
Subject: Re: [Sip] Regarding SIP CDR inforamtion ( from a Media Gateway Controller p erspective)
Date: Sat, 7 Sep 2002 12:11:42 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Although it has expired, here is one draft you may find interesting:

http://www.ietf.org/internet-drafts/draft-schulzrinne-sipping-radius-account
ing-00.txt

There has been some discussion of whether RADIUS is the appropriate protocol
to use. The general consensus is that it is not ideal, but it is what some
providers have installed. However, I do not know what other drafts may be
available describing CDR generation.

Good luck,
Rick

----- Original Message -----
From: "Jitender Arora" <jarora@aastra.com>
To: "Jonathan Rosenberg" <jdrosen@dynamicsoft.com>
Cc: <sip@ietf.org>
Sent: Friday, September 06, 2002 4:51 PM
Subject: [Sip] Regarding SIP CDR inforamtion ( from a Media Gateway
Controller p erspective)


> Hi ,
>
>      could somebody please point to the draft or RFC which contains the
> information about how the
>      CDR ( call detail records ) are generated for the SIP calls ( what
all
> informaion should be there
>      in the CDR ) from the Media Gateway Controller Perspective .
>
>      Is there any document available for this ...If yes please let me know
> ....
>
> Thanks and Regards,
> jitender .
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>

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



From mailnull@www1.ietf.org  Sat Sep  7 12:41:36 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15465
	for <sip-archive@odin.ietf.org>; Sat, 7 Sep 2002 12:41:36 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g87GgmH29638
	for sip-archive@odin.ietf.org; Sat, 7 Sep 2002 12:42:48 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g87GbOX29288;
	Sat, 7 Sep 2002 12:37:24 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g87Ga9X28729
	for <sip@optimus.ietf.org>; Sat, 7 Sep 2002 12:36:09 -0400
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15287
	for <sip@ietf.org>; Sat, 7 Sep 2002 12:34:27 -0400 (EDT)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g87Ga0MK027537;
	Sat, 7 Sep 2002 12:36:00 -0400 (EDT)
Received: from cs.columbia.edu ([128.163.6.250])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g87GZxcD010304
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sat, 7 Sep 2002 12:35:59 -0400 (EDT)
Message-ID: <3D7A2A9D.4020203@cs.columbia.edu>
Date: Sat, 07 Sep 2002 12:34:37 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Rick W. Porter" <rporter@acmepacket.com>
CC: Jitender Arora <jarora@aastra.com>, sip@ietf.org
Subject: Re: [Sip] Regarding SIP CDR inforamtion ( from a Media Gateway Controller
 p erspective)
References: <F924CEFBBF62D611A0C600D0B76ED03712FE7F@h3s68a245n132.user.nortelnetworks.com> <037001c25689$41841a40$2a00000a@RPORTER>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

See ipdr.org for another approach. (We also have a DIAMETER version for 
accounting: draft-narayanan-sipping-aaa-diameter-00.txt.) Comments on 
both would be most welcome. Unfortunately, while there are plenty of 
public-domain and commercial RADIUS servers, the number of DIAMETER 
servers seems to be approximately one.

Rick W. Porter wrote:
> Although it has expired, here is one draft you may find interesting:
> 
> http://www.ietf.org/internet-drafts/draft-schulzrinne-sipping-radius-account
> ing-00.txt
> 
> There has been some discussion of whether RADIUS is the appropriate protocol
> to use. The general consensus is that it is not ideal, but it is what some
> providers have installed. However, I do not know what other drafts may be
> available describing CDR generation.
> 
> Good luck,
> Rick
> 
> ----- Original Message -----
> From: "Jitender Arora" <jarora@aastra.com>
> To: "Jonathan Rosenberg" <jdrosen@dynamicsoft.com>
> Cc: <sip@ietf.org>
> Sent: Friday, September 06, 2002 4:51 PM
> Subject: [Sip] Regarding SIP CDR inforamtion ( from a Media Gateway
> Controller p erspective)
> 
> 
> 
>>Hi ,
>>
>>     could somebody please point to the draft or RFC which contains the
>>information about how the
>>     CDR ( call detail records ) are generated for the SIP calls ( what
> 
> all
> 
>>informaion should be there
>>     in the CDR ) from the Media Gateway Controller Perspective .
>>
>>     Is there any document available for this ...If yes please let me know
>>....
>>
>>Thanks and Regards,
>>jitender .
>>_______________________________________________
>>Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>>This list is for NEW development of the core SIP Protocol
>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>Use sipping@ietf.org for new developments on the application of sip
>>
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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



From mailnull@www1.ietf.org  Sat Sep  7 17:18:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19008
	for <sip-archive@odin.ietf.org>; Sat, 7 Sep 2002 17:18:49 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g87LK3T09727
	for sip-archive@odin.ietf.org; Sat, 7 Sep 2002 17:20:03 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g87LHUX09659;
	Sat, 7 Sep 2002 17:17:30 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g87LFLX09623
	for <sip@optimus.ietf.org>; Sat, 7 Sep 2002 17:15:21 -0400
Received: from pmesmtp02.wcom.com (pmesmtp02.wcom.com [199.249.20.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18974
	for <sip@ietf.org>; Sat, 7 Sep 2002 17:13:38 -0400 (EDT)
Received: from pmismtp06.wcomnet.com ([166.38.62.54])
 by firewall.wcom.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7
 2002)) with ESMTP id <0H23004BC6ZEU1@firewall.wcom.com> for sip@ietf.org; Sat,
 07 Sep 2002 21:14:03 +0000 (GMT)
Received: from pmismtp06.wcomnet.com by pmismtp06.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0H2300C016ZEBL@pmismtp06.wcomnet.com>; Sat,
 07 Sep 2002 21:14:02 +0000 (GMT)
Received: from hsinnreich2 ([166.50.116.41])
 by pmismtp06.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0H23004O76ZDML@pmismtp06.wcomnet.com>; Sat,
 07 Sep 2002 21:14:02 +0000 (GMT)
Date: Sat, 07 Sep 2002 16:14:01 -0500
From: Henry Sinnreich <Henry.Sinnreich@wcom.com>
Subject: RE: [Sip] Regarding SIP CDR inforamtion ( from a Media Gateway
 Controller p erspective)
In-reply-to: 
 <F924CEFBBF62D611A0C600D0B76ED03712FE7F@h3s68a245n132.user.nortelnetworks.com>
To: "'Jitender Arora'" <jarora@aastra.com>,
        "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>
Cc: sip@ietf.org
Message-id: <000201c256b3$7d51e910$297432a6@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1097
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

One long term view on AAA and CDRs for voice services is that all AAA
transactions and payments should fit in the emerging Web services for
any type of service or merchandise. 

Internal systems for authentication, billing, traffic measurments, etc.
may need to be outsourced or resold, just like any other service. Having
only VoIP using specific (or even obscure ones like DIAMETER) platforms
does not seem a very good proposition for service providers, where
streaminling IT is a perenial objective.

Here is some good reading material:

Tutorials: http://www.w3schools.com/

Web Services:
 
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/Dnwebsr
v/html/webservbasics.asp?frame=true

The core references: http://www.w3.org/2002/ws/

Thanks, Henry

> -----Original Message-----
> From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On 
> Behalf Of Jitender Arora
> Sent: Friday, September 06, 2002 3:51 PM
> To: Jonathan Rosenberg
> Cc: sip@ietf.org
> Subject: [Sip] Regarding SIP CDR inforamtion ( from a Media 
> Gateway Controller p erspective)
> 
> 
> Hi ,
> 
>      could somebody please point to the draft or RFC which 
> contains the information about how the 
>      CDR ( call detail records ) are generated for the SIP 
> calls ( what all informaion should be there 
>      in the CDR ) from the Media Gateway Controller Perspective . 
> 
>      Is there any document available for this ...If yes 
> please let me know ....
> 
> Thanks and Regards,
> jitender .
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sipping@ietf.org for new developments on the 
> application of sip
> 

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



From mailnull@www1.ietf.org  Mon Sep  9 11:14:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06633
	for <sip-archive@odin.ietf.org>; Mon, 9 Sep 2002 11:14:32 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g89FFbQ10976
	for sip-archive@odin.ietf.org; Mon, 9 Sep 2002 11:15:37 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89FEkv10697;
	Mon, 9 Sep 2002 11:14:46 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89F6Pv09066
	for <sip@optimus.ietf.org>; Mon, 9 Sep 2002 11:06:25 -0400
Received: from stingray.shentel.net (stingray.shentel.net [204.111.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06073
	for <sip@ietf.org>; Mon, 9 Sep 2002 11:04:49 -0400 (EDT)
Received: from stevesilverman (ha96s273.d.shentel.net [204.111.97.17])
	by stingray.shentel.net (8.11.3/8.11.3) with SMTP id g89F5lD17699;
	Mon, 9 Sep 2002 11:05:47 -0400
From: "Steve Silverman" <steves@shentel.net>
To: <chris@infravast.com>, "Dean Willis" <dwillis@dynamicsoft.com>
Cc: <sip@ietf.org>, <jdrosen@dynamicsoft.com>, <rohan@cisco.com>,
        <jo@ipdialog.com>, <brian.rosen@marconi.com>
Subject: RE: [Sip] WGLC for draft-ietf-sip-nat
Date: Mon, 9 Sep 2002 11:05:42 -0400
Message-ID: <EBEKKAOLIIHPGDPHMEKAKEKDCCAA.steves@shentel.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <3D7945D1.ECF0EE63@infravast.com>
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

If the system can not complete a phone call in less than one minute, the
caller will have hung up long ago.  When you dial a call today, how long
will you wait for the called party?  In most parts of the world, about 10
seconds is  the limit and then the caller hangs up and tries again.

Steve Silverman

>
> "In the case where there is a NAT between the client and server, in
>    order for the response to always be received, the NAT binding must
>    remain in existence for the duration of the transaction. Most UDP NAT
>    bindings appear to have a timeout of about one minute. Therefore,
>    non-INVITE transactions will have no problem. For INVITE
>    transactions, the client may need to retransmit its INVITE every 20
>    seconds or so, even after receiving a provisional response, in order
>    to keep the binding open to receive the final response.
>
>
>         OPEN ISSUE: This is awful. Perhaps a further sign that the
>         only real answer is TCP? Or, perhaps this belongs in
>         sipping-nat-scenarios, not here.
> "
>
> >From my brief reading of the draft it appears that only SIP rport is
> being requested...  how is this useful to sdp negotiation...is it merely
> for such items as IM?
>
> I think that this would be useful, and possibly not require the multiple
> invites mentioned, if the rport were used in the sdp as well... then the
> media could maintain the open connections.
>
> Since I am shooting very quickly from the hip with jsut a five minute
> speed read of the draft let me know if this is way off or if I am going
> in the right direction and reasoning and I will put more of my thoughts
> on this in a form that can be useful for use within this draft. (With a
> lot more effort  :^)    )
>
> I will try to read more this weekend and offer more input as well.
>
> Christopher A. Martin
>
> Dean Willis wrote:
> >
> > Version 02 of draft-ietf-sip-nat was posted two months ago (5Jul02) in
> > response to earlier suggestions and there seem to have been no further
> > comments.
> >
> > I am therefore requesting working group last call of the sip-nat draft.
> > According to our posted milestones, this should have concluded last call
> > last week, so we're not doing too badly. I'd like to send it on to the
> > IESG by 20Sep, so get your comments in posthaste.
> >
> > The draft in question is available at:
> >
> > http://www.ietf.org/internet-drafts/draft-ietf-sip-nat-02.txt
> >
> > As usual, please post dicussion to the list and copy the lead author,
> > jdrosen@dynamicsoft.com
> >
> > Thanks,
> >
> > --
> > Dean
> >
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>
>


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



From mailnull@www1.ietf.org  Mon Sep  9 18:54:18 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18661
	for <sip-archive@odin.ietf.org>; Mon, 9 Sep 2002 18:54:18 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g89MtRK05759
	for sip-archive@odin.ietf.org; Mon, 9 Sep 2002 18:55:27 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89Mt7v05747;
	Mon, 9 Sep 2002 18:55:07 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89Mrxv05703
	for <sip@optimus.ietf.org>; Mon, 9 Sep 2002 18:53:59 -0400
Received: from localhost.localdomain (adsl-64-219-190-5.dsl.rcsntx.swbell.net [64.219.190.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18638
	for <sip@ietf.org>; Mon, 9 Sep 2002 18:52:18 -0400 (EDT)
Received: from infravast.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (8.11.6/8.11.6) with ESMTP id g89N4XY17392;
	Mon, 9 Sep 2002 18:04:37 -0500
Message-ID: <3D7D2901.CDA17467@infravast.com>
Date: Mon, 09 Sep 2002 18:04:33 -0500
From: Chris Martin <chris@infravast.com>
Reply-To: chris@infravast.com
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-3 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Steve Silverman <steves@shentel.net>
CC: Dean Willis <dwillis@dynamicsoft.com>, sip@ietf.org,
        jdrosen@dynamicsoft.com, rohan@cisco.com, jo@ipdialog.com,
        brian.rosen@marconi.com
Subject: Re: [Sip] WGLC for draft-ietf-sip-nat
References: <EBEKKAOLIIHPGDPHMEKAKEKDCCAA.steves@shentel.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

This is one of the reasons that I am wodering why we need this
functionality. My comment earlier, that Johnathan responded to, was in
relation to a client to client communication (though I didnt explain it
clearly and the response was appropriate to my answer).  

In a situation such as this, client to client, a mechanism to keep a
translation open I thought it might be useful.  But if this is merely to
keep a sip session open during sip session establishment, I havent seen
a need for this as all sip traffic going through NAT that I have seen
hasnt had an issue with timeouts.  On the other hand registrations may
be a good reason to do this, but is already addressed at this point by
many clients that now offer a nat feature that permits a more permanent
feature to maintain constant ports per client for this purpose.... so
why do this at all?


Chris





Steve Silverman wrote:
> 
> If the system can not complete a phone call in less than one minute, the
> caller will have hung up long ago.  When you dial a call today, how long
> will you wait for the called party?  In most parts of the world, about 10
> seconds is  the limit and then the caller hangs up and tries again.
> 
> Steve Silverman
> 
> >
> > "In the case where there is a NAT between the client and server, in
> >    order for the response to always be received, the NAT binding must
> >    remain in existence for the duration of the transaction. Most UDP NAT
> >    bindings appear to have a timeout of about one minute. Therefore,
> >    non-INVITE transactions will have no problem. For INVITE
> >    transactions, the client may need to retransmit its INVITE every 20
> >    seconds or so, even after receiving a provisional response, in order
> >    to keep the binding open to receive the final response.
> >
> >
> >         OPEN ISSUE: This is awful. Perhaps a further sign that the
> >         only real answer is TCP? Or, perhaps this belongs in
> >         sipping-nat-scenarios, not here.
> > "
> >
> > >From my brief reading of the draft it appears that only SIP rport is
> > being requested...  how is this useful to sdp negotiation...is it merely
> > for such items as IM?
> >
> > I think that this would be useful, and possibly not require the multiple
> > invites mentioned, if the rport were used in the sdp as well... then the
> > media could maintain the open connections.
> >
> > Since I am shooting very quickly from the hip with jsut a five minute
> > speed read of the draft let me know if this is way off or if I am going
> > in the right direction and reasoning and I will put more of my thoughts
> > on this in a form that can be useful for use within this draft. (With a
> > lot more effort  :^)    )
> >
> > I will try to read more this weekend and offer more input as well.
> >
> > Christopher A. Martin
> >
> > Dean Willis wrote:
> > >
> > > Version 02 of draft-ietf-sip-nat was posted two months ago (5Jul02) in
> > > response to earlier suggestions and there seem to have been no further
> > > comments.
> > >
> > > I am therefore requesting working group last call of the sip-nat draft.
> > > According to our posted milestones, this should have concluded last call
> > > last week, so we're not doing too badly. I'd like to send it on to the
> > > IESG by 20Sep, so get your comments in posthaste.
> > >
> > > The draft in question is available at:
> > >
> > > http://www.ietf.org/internet-drafts/draft-ietf-sip-nat-02.txt
> > >
> > > As usual, please post dicussion to the list and copy the lead author,
> > > jdrosen@dynamicsoft.com
> > >
> > > Thanks,
> > >
> > > --
> > > Dean
> > >
> > > _______________________________________________
> > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > > This list is for NEW development of the core SIP Protocol
> > > Use sip-implementors@cs.columbia.edu for questions on current sip
> > > Use sipping@ietf.org for new developments on the application of sip
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> >
> >
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Mon Sep  9 23:52:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24176
	for <sip-archive@odin.ietf.org>; Mon, 9 Sep 2002 23:52:24 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8A3raY20636
	for sip-archive@odin.ietf.org; Mon, 9 Sep 2002 23:53:36 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8A3lXv20451;
	Mon, 9 Sep 2002 23:47:33 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8A3hpv20362
	for <sip@optimus.ietf.org>; Mon, 9 Sep 2002 23:43:51 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23990
	for <sip@ietf.org>; Mon, 9 Sep 2002 23:42:09 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.53])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g8A3h1YH019664;
	Mon, 9 Sep 2002 23:43:03 -0400 (EDT)
Message-ID: <3D7D6A44.2000203@dynamicsoft.com>
Date: Mon, 09 Sep 2002 23:43:00 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: chris@infravast.com
CC: Steve Silverman <steves@shentel.net>,
        Dean Willis
 <dwillis@dynamicsoft.com>, sip@ietf.org, rohan@cisco.com,
        jo@ipdialog.com, brian.rosen@marconi.com
Subject: Re: [Sip] WGLC for draft-ietf-sip-nat
References: <EBEKKAOLIIHPGDPHMEKAKEKDCCAA.steves@shentel.net> <3D7D2901.CDA17467@infravast.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit



Chris Martin wrote:
> This is one of the reasons that I am wodering why we need this
> functionality.

Which functionality? Your original note was talking about SDP, which is 
not what the sip-nat draft is about. Or, are you questioning the need 
for sip-nat at all?

> My comment earlier, that Johnathan responded to, was in
> relation to a client to client communication (though I didnt explain it
> clearly and the response was appropriate to my answer).  
> 
> In a situation such as this, client to client, a mechanism to keep a
> translation open I thought it might be useful. 

SIP-NAT is not about keeping translations open. sip-nat is about making 
sure responses are received properly for any request sent through a NAT. 
If you want to keep a binding active to receive media traffic, you use 
STUN.


> But if this is merely to
> keep a sip session open during sip session establishment, I havent seen
> a need for this as all sip traffic going through NAT that I have seen
> hasnt had an issue with timeouts.

Your comment makes no sense to me without defining "this".


> On the other hand registrations may
> be a good reason to do this, but is already addressed at this point by
> many clients that now offer a nat feature that permits a more permanent
> feature to maintain constant ports per client for this purpose.... so
> why do this at all?

I cannot understand this sentence since I do not know what a "nat 
feature that permits a more permanent feature" is, nor do I know what 
"this" is.

Please, before complaining about this specification, kindly spell out 
exactly what your complaints are.

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Mon Sep  9 23:54:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24204
	for <sip-archive@odin.ietf.org>; Mon, 9 Sep 2002 23:54:51 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8A3u2W20708
	for sip-archive@odin.ietf.org; Mon, 9 Sep 2002 23:56:02 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8A3tSv20691;
	Mon, 9 Sep 2002 23:55:28 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8A3qdv20604
	for <sip@optimus.ietf.org>; Mon, 9 Sep 2002 23:52:39 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24168
	for <sip@ietf.org>; Mon, 9 Sep 2002 23:50:57 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.53])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g8A3kxYH019668;
	Mon, 9 Sep 2002 23:46:59 -0400 (EDT)
Message-ID: <3D7D6B31.1050600@dynamicsoft.com>
Date: Mon, 09 Sep 2002 23:46:57 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Steve Silverman <steves@shentel.net>
CC: chris@infravast.com, Dean Willis <dwillis@dynamicsoft.com>, sip@ietf.org,
        rohan@cisco.com, jo@ipdialog.com, brian.rosen@marconi.com
Subject: Re: [Sip] WGLC for draft-ietf-sip-nat
References: <EBEKKAOLIIHPGDPHMEKAKEKDCCAA.steves@shentel.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit



Steve Silverman wrote:
> If the system can not complete a phone call in less than one minute, the
> caller will have hung up long ago.  When you dial a call today, how long
> will you wait for the called party?  In most parts of the world, about 10
> seconds is  the limit and then the caller hangs up and tries again.

Great, and that case works.

However, we have sevearl other cases of concern. The most irritating of 
these is the case where a UAS is a gateway that connects to an 800 
number system that actually never generates an ACM. Rather, it uses the 
reverse media path to prompt the user that they are in a queue. Once the 
user is out of the queue, the call is actually answered. As a result of 
this, the call can "ring" for minutes, perhaps even hours. To keep the 
binding alive to receive the SIP response is this case, the client will 
need to retransmit the INVITE every 30s or so. Of course, TCP is better 
here, and won't require any retransmits. The provisional response sent 
by the UAS, in order to keep timer C going, will maintain the bindings.

However, the main feature provided by this specification, rport, ensures 
that the response, whether generated immediately or later on, is 
received by the UAC behind the NAT.

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Tue Sep 10 07:58:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09928
	for <sip-archive@odin.ietf.org>; Tue, 10 Sep 2002 07:58:48 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8ABxxq19198
	for sip-archive@odin.ietf.org; Tue, 10 Sep 2002 07:59:59 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8ABwtv19114;
	Tue, 10 Sep 2002 07:58:55 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8ABrCv18901
	for <sip@optimus.ietf.org>; Tue, 10 Sep 2002 07:53:12 -0400
Received: from cozumel.we-host.com (cozumel.we-host.com.47.37.216.in-addr.arpa [216.37.47.200] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA09788
	for <sip@ietf.org>; Tue, 10 Sep 2002 07:51:31 -0400 (EDT)
Received: (qmail 6109 invoked from network); 10 Sep 2002 11:34:40 -0000
Received: from adsl-65-71-246-66.dsl.rcsntx.swbell.net (HELO StephenJames) (65.71.246.66)
  by cozumel.we-host.com.47.37.216.in-addr.arpa with SMTP; 10 Sep 2002 11:34:40 -0000
Message-ID: <000a01c258c0$848bba30$42f64741@StephenJames>
From: "Stephen James" <sjames@voiceramp.com>
To: <sip@ietf.org>
Date: Tue, 10 Sep 2002 06:52:19 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C25896.9B3B7920"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: [Sip] Locating Sip Servers
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C25896.9B3B7920
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

What is the level of support in the network for the RFC 2363 type of SIP =
server
location? I have been trying to use dig to look up records for examples =
of the
records described in the RFC. Are there servers that I can query. Is dig =
the
appropriate program, or am I way off base. If so, can someone push me at
least in the right direction.

Stephen James

------=_NextPart_000_0007_01C25896.9B3B7920
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 6.00.2719.2200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>What is the level of support in the =
network for the=20
RFC 2363 type of SIP server</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>location? I have been trying to use dig =
to look up=20
records for examples of the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>records described in the RFC. Are there =
servers=20
that I can query. Is dig the</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>appropriate program, or am I way off =
base. If so,=20
can someone push me at</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>least in the right =
direction.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Stephen =
James</FONT></DIV></BODY></HTML>

------=_NextPart_000_0007_01C25896.9B3B7920--


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



From mailnull@www1.ietf.org  Tue Sep 10 14:35:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22907
	for <sip-archive@odin.ietf.org>; Tue, 10 Sep 2002 14:35:52 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8AIb6x15507
	for sip-archive@odin.ietf.org; Tue, 10 Sep 2002 14:37:06 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8AIZHv15233;
	Tue, 10 Sep 2002 14:35:17 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8AIW7v15158
	for <sip@optimus.ietf.org>; Tue, 10 Sep 2002 14:32:07 -0400
Received: from dyn-tx-app-007.dfw.dynamicsoft.com ([63.110.3.105])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22653
	for <sip@ietf.org>; Tue, 10 Sep 2002 14:30:23 -0400 (EDT)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by dyn-tx-app-007.dfw.dynamicsoft.com (8.11.6/8.11.6) with ESMTP id g8ACgI115532
	for <sip@ietf.org>; Tue, 10 Sep 2002 07:42:18 -0500
From: Robert Sparks <rsparks@dynamicsoft.com>
To: sip@ietf.org
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) 
Date: 10 Sep 2002 13:27:46 -0500
Message-Id: <1031682466.2674.69.camel@dhcp151.dfw.dynamicsoft.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [Sip] SiPIT 11 registration closing in 10 days
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

If you're planning to attend SIPIT 11 and have not yet registered,
please do so before Sep 20. See http://www.pulver.com/sipit11 to
register.

RjS



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



From mailnull@www1.ietf.org  Tue Sep 10 20:10:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29958
	for <sip-archive@odin.ietf.org>; Tue, 10 Sep 2002 20:10:07 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8B0BNH32594
	for sip-archive@odin.ietf.org; Tue, 10 Sep 2002 20:11:23 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8B08xv32536;
	Tue, 10 Sep 2002 20:08:59 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8B073v32010
	for <sip@optimus.ietf.org>; Tue, 10 Sep 2002 20:07:03 -0400
Received: from localhost.localdomain (adsl-64-219-190-5.dsl.rcsntx.swbell.net [64.219.190.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29808
	for <sip@ietf.org>; Tue, 10 Sep 2002 20:05:12 -0400 (EDT)
Received: from infravast.com (localhost.localdomain [127.0.0.1])
	by localhost.localdomain (8.11.6/8.11.6) with ESMTP id g8B0HfY20352;
	Tue, 10 Sep 2002 19:17:42 -0500
Message-ID: <3D7E8BA5.3C3ADE12@infravast.com>
Date: Tue, 10 Sep 2002 19:17:41 -0500
From: Chris Martin <chris@infravast.com>
Reply-To: chris@infravast.com
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-3 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: Steve Silverman <steves@shentel.net>,
        Dean Willis <dwillis@dynamicsoft.com>, sip@ietf.org, rohan@cisco.com,
        jo@ipdialog.com, brian.rosen@marconi.com
Subject: Re: [Sip] WGLC for draft-ietf-sip-nat
References: <EBEKKAOLIIHPGDPHMEKAKEKDCCAA.steves@shentel.net> <3D7D2901.CDA17467@infravast.com> <3D7D6A44.2000203@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Jonathan Rosenberg wrote:
> 
> Chris Martin wrote:
> > This is one of the reasons that I am wodering why we need this
> > functionality.
> 
> Which functionality? Your original note was talking about SDP, which is
> not what the sip-nat draft is about. Or, are you questioning the need
> for sip-nat at all?

Yes that was off topic and out of place.... :^) I was thinking of my
current focus which is traversal/enablement.... not part of this thread.

And yes, the question is why sip-nat...

> 
> > My comment earlier, that Johnathan responded to, was in
> > relation to a client to client communication (though I didnt explain it
> > clearly and the response was appropriate to my answer).
> >
> > In a situation such as this, client to client, a mechanism to keep a
> > translation open I thought it might be useful.
> 
> SIP-NAT is not about keeping translations open. sip-nat is about making
> sure responses are received properly for any request sent through a NAT.
> If you want to keep a binding active to receive media traffic, you use
> STUN.

By having the ability of ensuring that sip is recieved properly I am
assuming that the intention is that of maintaining a nat binding for sip
to be contacted through. I am not referring to media traffic.. you
clarified the intent in your first email. I am now questioning why
sip-nat? Not to be argumentative, merely to understand the intent.

> 
> > But if this is merely to
> > keep a sip session open during sip session establishment, I havent seen
> > a need for this as all sip traffic going through NAT that I have seen
> > hasnt had an issue with timeouts.
> 
> Your comment makes no sense to me without defining "this".
> 
> > On the other hand registrations may
> > be a good reason to do this, but is already addressed at this point by
> > many clients that now offer a nat feature that permits a more permanent
> > feature to maintain constant ports per client for this purpose.... so
> > why do this at all?
> 
> I cannot understand this sentence since I do not know what a "nat
> feature that permits a more permanent feature" is, nor do I know what
> "this" is.
> 
> Please, before complaining about this specification, kindly spell out
> exactly what your complaints are.
> 
> -Jonathan R.
> 
> --
> Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
> Chief Scientist                             First Floor
> dynamicsoft                                 East Hanover, NJ 07936
> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Tue Sep 10 21:56:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02063
	for <sip-archive@odin.ietf.org>; Tue, 10 Sep 2002 21:56:29 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8B1vl904282
	for sip-archive@odin.ietf.org; Tue, 10 Sep 2002 21:57:47 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8B1tjv04243;
	Tue, 10 Sep 2002 21:55:45 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8B1oov04122
	for <sip@optimus.ietf.org>; Tue, 10 Sep 2002 21:50:50 -0400
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.54])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01997
	for <sip@ietf.org>; Tue, 10 Sep 2002 21:49:01 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-4.cisco.com (8.12.2/8.12.2) with ESMTP id g8B1o5W4001019;
	Tue, 10 Sep 2002 18:50:05 -0700 (PDT)
Received: from open-131-161-248-87.cliq.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.1.0.54-GA)
	with ESMTP id AAV32948;
	Tue, 10 Sep 2002 18:48:24 -0700 (PDT)
Date: Tue, 10 Sep 2002 18:50:58 -0700
Subject: Re: [Sip] WGLC for draft-ietf-sip-nat
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v482)
Cc: Jonathan Rosenberg <jdrosen@dynamicsoft.com>,
        Steve Silverman <steves@shentel.net>,
        Dean Willis <dwillis@dynamicsoft.com>, sip@ietf.org, jo@ipdialog.com,
        brian.rosen@marconi.com
To: chris@infravast.com
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <3D7E8BA5.3C3ADE12@infravast.com>
Message-Id: <EB002EF9-C528-11D6-9030-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.482)
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Chris,

We have sufficient interest and consensus to proceed with this 
(chartered) document, even if you think it will not be useful to you 
personally.  If you want further explanations about why 
draft-ietf-sip-nat is useful, please take that discussion off the list. 
If there are other SIP and NAT related topics you would like to see 
addressed that are not discussed in draft-ietf-sipping-nat-
scenarios-00.txt, then you are free to propose this as new work in 
SIPPING.

thanks,
-rohan

On Tuesday, September 10, 2002, at 05:17 PM, Chris Martin wrote:

> Jonathan Rosenberg wrote:
>>
>> Chris Martin wrote:
>>> This is one of the reasons that I am wodering why we need this
>>> functionality.
>>
>> Which functionality? Your original note was talking about SDP, which is
>> not what the sip-nat draft is about. Or, are you questioning the need
>> for sip-nat at all?
>
> Yes that was off topic and out of place.... :^) I was thinking of my
> current focus which is traversal/enablement.... not part of this thread.
>
> And yes, the question is why sip-nat...
>
>>
>>> My comment earlier, that Johnathan responded to, was in
>>> relation to a client to client communication (though I didnt explain 
>>> it
>>> clearly and the response was appropriate to my answer).
>>>
>>> In a situation such as this, client to client, a mechanism to keep a
>>> translation open I thought it might be useful.
>>
>> SIP-NAT is not about keeping translations open. sip-nat is about making
>> sure responses are received properly for any request sent through a 
>> NAT.
>> If you want to keep a binding active to receive media traffic, you use
>> STUN.
>
> By having the ability of ensuring that sip is recieved properly I am
> assuming that the intention is that of maintaining a nat binding for sip
> to be contacted through. I am not referring to media traffic.. you
> clarified the intent in your first email. I am now questioning why
> sip-nat? Not to be argumentative, merely to understand the intent.
>
>>
>>> But if this is merely to
>>> keep a sip session open during sip session establishment, I havent 
>>> seen
>>> a need for this as all sip traffic going through NAT that I have seen
>>> hasnt had an issue with timeouts.
>>
>> Your comment makes no sense to me without defining "this".
>>
>>> On the other hand registrations may
>>> be a good reason to do this, but is already addressed at this point by
>>> many clients that now offer a nat feature that permits a more 
>>> permanent
>>> feature to maintain constant ports per client for this purpose.... so
>>> why do this at all?
>>
>> I cannot understand this sentence since I do not know what a "nat
>> feature that permits a more permanent feature" is, nor do I know what
>> "this" is.
>>
>> Please, before complaining about this specification, kindly spell out
>> exactly what your complaints are.
>>
>> -Jonathan R.
>>
>> --
>> Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
>> Chief Scientist                             First Floor
>> dynamicsoft                                 East Hanover, NJ 07936
>> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
>> http://www.jdrosen.net                      PHONE: (973) 952-5000
>> http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Tue Sep 10 22:38:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02896
	for <sip-archive@odin.ietf.org>; Tue, 10 Sep 2002 22:38:04 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8B2dNP06518
	for sip-archive@odin.ietf.org; Tue, 10 Sep 2002 22:39:23 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8B2afv05899;
	Tue, 10 Sep 2002 22:36:41 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8B2Xuv05821
	for <sip@optimus.ietf.org>; Tue, 10 Sep 2002 22:33:56 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02724
	for <sip@ietf.org>; Tue, 10 Sep 2002 22:32:07 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.112])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g8B2WvYH020495;
	Tue, 10 Sep 2002 22:32:58 -0400 (EDT)
Message-ID: <3D7EAB59.2040305@dynamicsoft.com>
Date: Tue, 10 Sep 2002 22:32:57 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: chris@infravast.com
CC: Steve Silverman <steves@shentel.net>,
        Dean Willis
 <dwillis@dynamicsoft.com>, sip@ietf.org, rohan@cisco.com,
        jo@ipdialog.com, brian.rosen@marconi.com
Subject: Re: [Sip] WGLC for draft-ietf-sip-nat
References: <EBEKKAOLIIHPGDPHMEKAKEKDCCAA.steves@shentel.net> <3D7D2901.CDA17467@infravast.com> <3D7D6A44.2000203@dynamicsoft.com> <3D7E8BA5.3C3ADE12@infravast.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit



Chris Martin wrote:

>>SIP-NAT is not about keeping translations open. sip-nat is about making
>>sure responses are received properly for any request sent through a NAT.
>>If you want to keep a binding active to receive media traffic, you use
>>STUN.
> 
> 
> By having the ability of ensuring that sip is recieved properly I am
> assuming that the intention is that of maintaining a nat binding for sip
> to be contacted through.

No, that is not correct.

The normal behavior for sending a response to a SIP request is to send 
it to the source IP address of the request, but to the port in the Via 
header. This rule will cause responses to be lost through all NAT types, 
even if the bindings last forever. sip-nat allows for the response to 
actually be received.

-Jonathan R.



-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Tue Sep 10 22:42:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03055
	for <sip-archive@odin.ietf.org>; Tue, 10 Sep 2002 22:42:47 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8B2i6h06678
	for sip-archive@odin.ietf.org; Tue, 10 Sep 2002 22:44:06 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8B2fHv06582;
	Tue, 10 Sep 2002 22:41:17 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8B2b0v05926
	for <sip@optimus.ietf.org>; Tue, 10 Sep 2002 22:37:00 -0400
Received: from services1.dasecurenetworks.com (adsl-64-219-190-5.dsl.rcsntx.swbell.net [64.219.190.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02881
	for <sip@ietf.org>; Tue, 10 Sep 2002 22:35:11 -0400 (EDT)
Received: from infravast.com (servics1.dasecurenetworks.com [192.168.0.10])
	by services1.dasecurenetworks.com (8.11.6/8.9.3) with ESMTP id g8B2LKv06905;
	Tue, 10 Sep 2002 21:21:20 -0500
Message-ID: <3D7EAC15.391C5194@infravast.com>
Date: Tue, 10 Sep 2002 21:36:05 -0500
From: Chris Martin <chris@infravast.com>
Reply-To: chris@infravast.com
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: Steve Silverman <steves@shentel.net>,
        Dean Willis <dwillis@dynamicsoft.com>, sip@ietf.org, rohan@cisco.com,
        jo@ipdialog.com, brian.rosen@marconi.com
Subject: Re: [Sip] WGLC for draft-ietf-sip-nat
References: <EBEKKAOLIIHPGDPHMEKAKEKDCCAA.steves@shentel.net> <3D7D2901.CDA17467@infravast.com> <3D7D6A44.2000203@dynamicsoft.com> <3D7E8BA5.3C3ADE12@infravast.com> <3D7EAB59.2040305@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Thanks Johnathan, thats what I was looking for, and it makes perfect sense
now. (I was premature earlier...)

:^)

Chris

Jonathan Rosenberg wrote:

> Chris Martin wrote:
>
> >>SIP-NAT is not about keeping translations open. sip-nat is about making
> >>sure responses are received properly for any request sent through a NAT.
> >>If you want to keep a binding active to receive media traffic, you use
> >>STUN.
> >
> >
> > By having the ability of ensuring that sip is recieved properly I am
> > assuming that the intention is that of maintaining a nat binding for sip
> > to be contacted through.
>
> No, that is not correct.
>
> The normal behavior for sending a response to a SIP request is to send
> it to the source IP address of the request, but to the port in the Via
> header. This rule will cause responses to be lost through all NAT types,
> even if the bindings last forever. sip-nat allows for the response to
> actually be received.
>
> -Jonathan R.
>
> --
> Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
> Chief Scientist                             First Floor
> dynamicsoft                                 East Hanover, NJ 07936
> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com



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



From mailnull@www1.ietf.org  Tue Sep 10 22:51:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03240
	for <sip-archive@odin.ietf.org>; Tue, 10 Sep 2002 22:51:15 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8B2qYP06904
	for sip-archive@odin.ietf.org; Tue, 10 Sep 2002 22:52:34 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8B2oHv06861;
	Tue, 10 Sep 2002 22:50:17 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8B2nDv06831
	for <sip@optimus.ietf.org>; Tue, 10 Sep 2002 22:49:13 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03149
	for <sip@ietf.org>; Tue, 10 Sep 2002 22:47:23 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.112])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g8B2mYYH020511;
	Tue, 10 Sep 2002 22:48:34 -0400 (EDT)
Message-ID: <3D7EAF01.6000600@dynamicsoft.com>
Date: Tue, 10 Sep 2002 22:48:33 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3) Gecko/20020523
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Stephen James <sjames@voiceramp.com>
CC: sip@ietf.org
Subject: Re: [Sip] Locating Sip Servers
References: <000a01c258c0$848bba30$42f64741@StephenJames>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

The usage of NAPTR records is very new, and was added close to the end 
of the standardization process of rfc's 3261-5. Thus, I suspect there 
are not that many deployments or DNS servers you can query for these 
records. However, I believe there are increasing numbers of 
implementations.

Would be nice to test some of rfc3263 at sipit...

-Jonathan R.

Stephen James wrote:
> What is the level of support in the network for the RFC 2363 type of SIP 
> server
> location? I have been trying to use dig to look up records for examples 
> of the
> records described in the RFC. Are there servers that I can query. Is dig the
> appropriate program, or am I way off base. If so, can someone push me at
> least in the right direction.
>  
> Stephen James


-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Wed Sep 11 09:31:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08950
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 09:31:39 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BDWqd15276
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 09:32:52 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BDWTv15253;
	Wed, 11 Sep 2002 09:32:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BDUwv15166
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 09:30:58 -0400
Received: from NREXCH.netrake.net (nrexch.Netrake.com [65.119.52.238])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08911
	for <sip@ietf.org>; Wed, 11 Sep 2002 09:29:14 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Subject: RE: [Sip] WGLC for draft-ietf-sip-nat
Date: Wed, 11 Sep 2002 08:30:28 -0500
Message-ID: <7E06D3212981524CA10D2A114937C41447B894@NREXCH.netrake.net>
Thread-Topic: [Sip] WGLC for draft-ietf-sip-nat
Thread-Index: AcJYf3nRIhZMRkA4QU25UIglQkSOtwBFuZJ8
From: "Jasson Casey" <jasson@netrake.com>
To: "Jonathan Rosenberg" <jdrosen@dynamicsoft.com>,
        "Steve Silverman" <steves@shentel.net>
Cc: <chris@infravast.com>, "Dean Willis" <dwillis@dynamicsoft.com>,
        <sip@ietf.org>, <rohan@cisco.com>, <jo@ipdialog.com>,
        <brian.rosen@marconi.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id g8BDUwv15168
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

I've got a quick question. Timer C >= 180s. When timer c fires a couple things should happen to expire the transaction or keep it going. How does having a minimum value of 180s allow the provisional responses to keep the binding alive through a NAT if we're talking about NAT expirations ~ 30s? 
 
I just didn't understand the sentence 'The provisional response sent
by the UAS, in order to keep timer C going, will maintain the bindings.'

-jasson

	-----Original Message----- 
	From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com] 
	Sent: Mon 9/9/2002 10:46 PM 
	To: Steve Silverman 
	Cc: chris@infravast.com; Dean Willis; sip@ietf.org; rohan@cisco.com; jo@ipdialog.com; brian.rosen@marconi.com 
	Subject: Re: [Sip] WGLC for draft-ietf-sip-nat
	
	



	Steve Silverman wrote:
	> If the system can not complete a phone call in less than one minute, the
	> caller will have hung up long ago.  When you dial a call today, how long
	> will you wait for the called party?  In most parts of the world, about 10
	> seconds is  the limit and then the caller hangs up and tries again.
	
	Great, and that case works.
	
	However, we have sevearl other cases of concern. The most irritating of
	these is the case where a UAS is a gateway that connects to an 800
	number system that actually never generates an ACM. Rather, it uses the
	reverse media path to prompt the user that they are in a queue. Once the
	user is out of the queue, the call is actually answered. As a result of
	this, the call can "ring" for minutes, perhaps even hours. To keep the
	binding alive to receive the SIP response is this case, the client will
	need to retransmit the INVITE every 30s or so. Of course, TCP is better
	here, and won't require any retransmits. The provisional response sent
	by the UAS, in order to keep timer C going, will maintain the bindings.
	
	However, the main feature provided by this specification, rport, ensures
	that the response, whether generated immediately or later on, is
	received by the UAC behind the NAT.
	
	-Jonathan R.
	
	
	--
	Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
	Chief Scientist                             First Floor
	dynamicsoft                                 East Hanover, NJ 07936
	jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
	http://www.jdrosen.net                      PHONE: (973) 952-5000
	http://www.dynamicsoft.com
	
	_______________________________________________
	Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
	This list is for NEW development of the core SIP Protocol
	Use sip-implementors@cs.columbia.edu for questions on current sip
	Use sipping@ietf.org for new developments on the application of sip
	

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



From mailnull@www1.ietf.org  Wed Sep 11 09:51:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09530
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 09:51:32 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BDqjj16514
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 09:52:45 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BDpmv16487;
	Wed, 11 Sep 2002 09:51:48 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BDo9v16422
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 09:50:09 -0400
Received: from znsgs01r.europe.nortel.com (h2s128a211n47.user.nortelnetworks.com [47.211.128.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09475
	for <sip@ietf.org>; Wed, 11 Sep 2002 09:48:21 -0400 (EDT)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.160.46.124])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g8BDnNC10485
	for <sip@ietf.org>; Wed, 11 Sep 2002 14:49:24 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <S3PAHF9B>; Wed, 11 Sep 2002 14:49:15 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7693@zwcwd00r.europe.nortel.com>
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'sip@ietf.org'" <sip@ietf.org>
Date: Wed, 11 Sep 2002 14:49:13 +0100
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Sip] S/MIME certificates question
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

All,

In RFC3261 23.2 it states:

"Whenever the CMS SignedData message is used in S/MIME for SIP, it MUST
contain the certificate bearing the public key necessary to verify the
signature."

I assume that "it" refers to the CMS SignedData message.

An alternative would presumably be for the certificate to be contained in a
separate MIME part of type application/pks7-mime with
smime-type="certs-only". This would have the advantage that the certificate,
which does not change often, and which I understand can be fairly large,
could make use of content indirection.

If the certificate is required to be embedded in the same SignedData object
as the signature itself, then I guess this would not be possible.

So, is inclusion of the certificate as a separate body part, prohibited by
the SIP specification ?

Regards...Mark

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



From mailnull@www1.ietf.org  Wed Sep 11 10:28:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10858
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 10:28:44 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BETvD18805
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 10:29:57 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BETWv18782;
	Wed, 11 Sep 2002 10:29:32 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BESAv18685
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 10:28:10 -0400
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10794
	for <sip@ietf.org>; Wed, 11 Sep 2002 10:26:26 -0400 (EDT)
Received: from mira-sjc5-7.cisco.com (IDENT:mirapoint@mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g8BERW3x027363;
	Wed, 11 Sep 2002 07:27:32 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ACO73342;
	Wed, 11 Sep 2002 07:23:08 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id HAA23100; Wed, 11 Sep 2002 07:27:35 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15743.21207.535381.269510@thomasm-u1.cisco.com>
Date: Wed, 11 Sep 2002 07:27:35 -0700 (PDT)
To: "Mark Watson" <mwatson@nortelnetworks.com>
Cc: "'sip@ietf.org'" <sip@ietf.org>
Subject: [Sip] S/MIME certificates question
In-Reply-To: <A3C2399B2FACD411A54200508BE39C74054F7693@zwcwd00r.europe.nortel.com>
References: <A3C2399B2FACD411A54200508BE39C74054F7693@zwcwd00r.europe.nortel.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


Uh, unless it's actually a MUST in the S/MIME
spec, there's no reason why the certificate has to
be carried in the message. Certs are public data
and can be fetched from any source, including... a
(x.500) directory. In fact, I believe this would
probably harm interoperability if you wanted to
just use naked public keys since self-signed certs
are much more likely to have agreement problems
than just a naked key.

	  Mike

Mark Watson writes:
 > All,
 > 
 > In RFC3261 23.2 it states:
 > 
 > "Whenever the CMS SignedData message is used in S/MIME for SIP, it MUST
 > contain the certificate bearing the public key necessary to verify the
 > signature."
 > 
 > I assume that "it" refers to the CMS SignedData message.
 > 
 > An alternative would presumably be for the certificate to be contained in a
 > separate MIME part of type application/pks7-mime with
 > smime-type="certs-only". This would have the advantage that the certificate,
 > which does not change often, and which I understand can be fairly large,
 > could make use of content indirection.
 > 
 > If the certificate is required to be embedded in the same SignedData object
 > as the signature itself, then I guess this would not be possible.
 > 
 > So, is inclusion of the certificate as a separate body part, prohibited by
 > the SIP specification ?
 > 
 > Regards...Mark
 > 
 > _______________________________________________
 > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
 > This list is for NEW development of the core SIP Protocol
 > Use sip-implementors@cs.columbia.edu for questions on current sip
 > Use sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Wed Sep 11 10:32:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11030
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 10:32:59 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BEYCp19141
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 10:34:12 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BEXav19097;
	Wed, 11 Sep 2002 10:33:36 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BETXv18784
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 10:29:33 -0400
Received: from brmx1.fl.icn.siemens.com (brmx1.fl.icn.siemens.com [12.147.96.32])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10840
	for <sip@ietf.org>; Wed, 11 Sep 2002 10:27:49 -0400 (EDT)
Received: from boca210a.boca.ssc.siemens.com (boca210a.boca.ssc.siemens.com [165.218.12.110])
	by brmx1.fl.icn.siemens.com (8.9.3/8.9.3) with ESMTP id KAA02104;
	Wed, 11 Sep 2002 10:29:25 -0400 (EDT)
Received: by boca210a.boca.ssc.siemens.com with Internet Mail Service (5.5.2653.19)
	id <SMQ2DKFS>; Wed, 11 Sep 2002 10:29:24 -0400
Message-ID: <DC26B4448BEC824C8C4E58845FF9F04C3B1BBD@EMAIL2>
From: "Mahey, Sonit" <Sonit.Mahey@icn.siemens.com>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'sip@ietf.org'"
	 <sip@ietf.org>
Cc: "Sandhu, Hari" <Hari.Sandhu@icn.siemens.com>
Subject: RE: [Sip] S/MIME certificates question
Date: Wed, 11 Sep 2002 10:30:43 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

Hi All,

If SIP does not prohibit what Mark suggests, I think Mark's idea is good. I
like the notion of decoupling to the extent possible.

regards,
- sonit
Sonit Mahey,
Systems Architect,
Siemens Network Convergence,
*: 10 Technology Park Dr., Westford, MA 01886
': 978.923.3271
*: Sonit.Mahey@icn.siemens.com 
http://www.siemens.com


-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Wednesday, September 11, 2002 9:49 AM
To: 'sip@ietf.org'
Subject: [Sip] S/MIME certificates question


All,

In RFC3261 23.2 it states:

"Whenever the CMS SignedData message is used in S/MIME for SIP, it MUST
contain the certificate bearing the public key necessary to verify the
signature."

I assume that "it" refers to the CMS SignedData message.

An alternative would presumably be for the certificate to be contained in a
separate MIME part of type application/pks7-mime with
smime-type="certs-only". This would have the advantage that the certificate,
which does not change often, and which I understand can be fairly large,
could make use of content indirection.

If the certificate is required to be embedded in the same SignedData object
as the signature itself, then I guess this would not be possible.

So, is inclusion of the certificate as a separate body part, prohibited by
the SIP specification ?

Regards...Mark

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



From mailnull@www1.ietf.org  Wed Sep 11 10:45:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11548
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 10:45:50 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BEl4M20279
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 10:47:04 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BEkHv20215;
	Wed, 11 Sep 2002 10:46:18 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BEj5v20162
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 10:45:05 -0400
Received: from znsgs01r.europe.nortel.com (h2s128a211n47.user.nortelnetworks.com [47.211.128.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11429
	for <sip@ietf.org>; Wed, 11 Sep 2002 10:43:16 -0400 (EDT)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.160.46.124])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g8BEi6C26296;
	Wed, 11 Sep 2002 15:44:06 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <S3PAH2TK>; Wed, 11 Sep 2002 15:44:07 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7696@zwcwd00r.europe.nortel.com>
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Michael Thomas'" <mat@cisco.com>
Cc: "'sip@ietf.org'" <sip@ietf.org>
Subject: RE: [Sip] S/MIME certificates question
Date: Wed, 11 Sep 2002 15:44:03 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C259A1.AC7487C0"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

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_001_01C259A1.AC7487C0
Content-Type: text/plain;
	charset="iso-8859-1"

Mike,

Well, I guess it's a MUST in the SIP spec (section quoted below), if you
assume that the 'it' in that sentence refers to the CMS SignedData message,
and not to the SIP message in which it (err, the CMS SignedData message) is
contained.

...Mark


> -----Original Message-----
> From: Michael Thomas [mailto:mat@cisco.com]
> Sent: 11 September 2002 15:28
> To: Watson, Mark [MOP:EP10:EXCH]
> Cc: 'sip@ietf.org'
> Subject: [Sip] S/MIME certificates question
> 
> 
> 
> Uh, unless it's actually a MUST in the S/MIME
> spec, there's no reason why the certificate has to
> be carried in the message. Certs are public data
> and can be fetched from any source, including... a
> (x.500) directory. In fact, I believe this would
> probably harm interoperability if you wanted to
> just use naked public keys since self-signed certs
> are much more likely to have agreement problems
> than just a naked key.
> 
> 	  Mike
> 
> Mark Watson writes:
>  > All,
>  > 
>  > In RFC3261 23.2 it states:
>  > 
>  > "Whenever the CMS SignedData message is used in S/MIME for 
> SIP, it MUST
>  > contain the certificate bearing the public key necessary 
> to verify the
>  > signature."
>  > 
>  > I assume that "it" refers to the CMS SignedData message.
>  > 
>  > An alternative would presumably be for the certificate to 
> be contained in a
>  > separate MIME part of type application/pks7-mime with
>  > smime-type="certs-only". This would have the advantage 
> that the certificate,
>  > which does not change often, and which I understand can be 
> fairly large,
>  > could make use of content indirection.
>  > 
>  > If the certificate is required to be embedded in the same 
> SignedData object
>  > as the signature itself, then I guess this would not be possible.
>  > 
>  > So, is inclusion of the certificate as a separate body 
> part, prohibited by
>  > the SIP specification ?
>  > 
>  > Regards...Mark
>  > 
>  > _______________________________________________
>  > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>  > This list is for NEW development of the core SIP Protocol
>  > Use sip-implementors@cs.columbia.edu for questions on current sip
>  > Use sipping@ietf.org for new developments on the application of sip
> 

------_=_NextPart_001_01C259A1.AC7487C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sip] S/MIME certificates question</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Mike,</FONT>
</P>

<P><FONT SIZE=3D2>Well, I guess it's a MUST in the SIP spec (section =
quoted below), if you assume that the 'it' in that sentence refers to =
the CMS SignedData message, and not to the SIP message in which it =
(err, the CMS SignedData message) is contained.</FONT></P>

<P><FONT SIZE=3D2>...Mark</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Michael Thomas [<A =
HREF=3D"mailto:mat@cisco.com">mailto:mat@cisco.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 11 September 2002 15:28</FONT>
<BR><FONT SIZE=3D2>&gt; To: Watson, Mark [MOP:EP10:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: 'sip@ietf.org'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [Sip] S/MIME certificates =
question</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Uh, unless it's actually a MUST in the =
S/MIME</FONT>
<BR><FONT SIZE=3D2>&gt; spec, there's no reason why the certificate has =
to</FONT>
<BR><FONT SIZE=3D2>&gt; be carried in the message. Certs are public =
data</FONT>
<BR><FONT SIZE=3D2>&gt; and can be fetched from any source, =
including... a</FONT>
<BR><FONT SIZE=3D2>&gt; (x.500) directory. In fact, I believe this =
would</FONT>
<BR><FONT SIZE=3D2>&gt; probably harm interoperability if you wanted =
to</FONT>
<BR><FONT SIZE=3D2>&gt; just use naked public keys since self-signed =
certs</FONT>
<BR><FONT SIZE=3D2>&gt; are much more likely to have agreement =
problems</FONT>
<BR><FONT SIZE=3D2>&gt; than just a naked key.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; =
Mike</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mark Watson writes:</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; All,</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; In RFC3261 23.2 it states:</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; &quot;Whenever the CMS SignedData =
message is used in S/MIME for </FONT>
<BR><FONT SIZE=3D2>&gt; SIP, it MUST</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; contain the certificate bearing the =
public key necessary </FONT>
<BR><FONT SIZE=3D2>&gt; to verify the</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; signature.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; I assume that &quot;it&quot; refers =
to the CMS SignedData message.</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; An alternative would presumably be =
for the certificate to </FONT>
<BR><FONT SIZE=3D2>&gt; be contained in a</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; separate MIME part of type =
application/pks7-mime with</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; smime-type=3D&quot;certs-only&quot;. =
This would have the advantage </FONT>
<BR><FONT SIZE=3D2>&gt; that the certificate,</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; which does not change often, and =
which I understand can be </FONT>
<BR><FONT SIZE=3D2>&gt; fairly large,</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; could make use of content =
indirection.</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; If the certificate is required to be =
embedded in the same </FONT>
<BR><FONT SIZE=3D2>&gt; SignedData object</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; as the signature itself, then I =
guess this would not be possible.</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; So, is inclusion of the certificate =
as a separate body </FONT>
<BR><FONT SIZE=3D2>&gt; part, prohibited by</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; the SIP specification ?</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; Regards...Mark</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; Sip mailing list&nbsp; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sip" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sip</A></FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; This list is for NEW development of =
the core SIP Protocol</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; Use sip-implementors@cs.columbia.edu =
for questions on current sip</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; Use sipping@ietf.org for new =
developments on the application of sip</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C259A1.AC7487C0--
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Wed Sep 11 12:01:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14222
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 12:01:29 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BG2ig24646
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 12:02:44 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BG1dv24563;
	Wed, 11 Sep 2002 12:01:39 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BFxiv24443
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 11:59:44 -0400
Received: from smtp017.mail.yahoo.com (smtp017.mail.yahoo.com [216.136.174.114])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA14043
	for <sip@ietf.org>; Wed, 11 Sep 2002 11:57:59 -0400 (EDT)
Received: from 12-235-146-159.client.attbi.com (HELO cranberry) (seancolson@12.235.146.159 with login)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 11 Sep 2002 15:59:37 -0000
Reply-To: <seancolson@yahoo.com>
From: "Sean Olson" <seancolson@yahoo.com>
To: "'Mahey, Sonit'" <Sonit.Mahey@icn.siemens.com>,
        "'Mark Watson'" <mwatson@nortelnetworks.com>, <sip@ietf.org>
Cc: "'Sandhu, Hari'" <Hari.Sandhu@icn.siemens.com>
Subject: RE: [Sip] S/MIME certificates question
Date: Wed, 11 Sep 2002 08:59:51 -0700
Message-ID: <003601c259ac$43d0ce80$6601a8c0@cranberry>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1081
In-Reply-To: <DC26B4448BEC824C8C4E58845FF9F04C3B1BBD@EMAIL2>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

This does make a great deal of sense. And I think it would be an
excellent
use of content indirection. Could someone clarify the purpose of the
"MUST"
in this text?

Cheers,
Sean Olson
Microsoft

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of Mahey,
Sonit
Sent: Wednesday, September 11, 2002 7:31 AM
To: 'Mark Watson'; 'sip@ietf.org'
Cc: Sandhu, Hari
Subject: RE: [Sip] S/MIME certificates question


Hi All,

If SIP does not prohibit what Mark suggests, I think Mark's idea is
good. I like the notion of decoupling to the extent possible.

regards,
- sonit
Sonit Mahey,
Systems Architect,
Siemens Network Convergence,
*: 10 Technology Park Dr., Westford, MA 01886
': 978.923.3271
*: Sonit.Mahey@icn.siemens.com 
http://www.siemens.com


-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Wednesday, September 11, 2002 9:49 AM
To: 'sip@ietf.org'
Subject: [Sip] S/MIME certificates question


All,

In RFC3261 23.2 it states:

"Whenever the CMS SignedData message is used in S/MIME for SIP, it MUST
contain the certificate bearing the public key necessary to verify the
signature."

I assume that "it" refers to the CMS SignedData message.

An alternative would presumably be for the certificate to be contained
in a separate MIME part of type application/pks7-mime with
smime-type="certs-only". This would have the advantage that the
certificate, which does not change often, and which I understand can be
fairly large, could make use of content indirection.

If the certificate is required to be embedded in the same SignedData
object as the signature itself, then I guess this would not be possible.

So, is inclusion of the certificate as a separate body part, prohibited
by the SIP specification ?

Regards...Mark

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

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



From mailnull@www1.ietf.org  Wed Sep 11 12:27:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15171
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 12:27:29 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BGSiL26446
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 12:28:44 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BGRjv26378;
	Wed, 11 Sep 2002 12:27:45 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BGQUv26310
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 12:26:30 -0400
Received: from mirlo.dit.upm.es (mirlo.dit.upm.es [138.4.5.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15032
	for <sip@ietf.org>; Wed, 11 Sep 2002 12:24:44 -0400 (EDT)
Received: from perdiz (perdiz [138.4.50.3]) by mirlo.dit.upm.es (8.8.5/8.7.3) with SMTP id QAA25628 for <sip@ietf.org>; Wed, 11 Sep 2002 16:27:04 GMT
From: =?iso-8859-1?Q?Manuel_Moreno_Mart=EDn?= <mmoreno@cipres.upm.es>
To: "Sip" <sip@ietf.org>
Date: Wed, 11 Sep 2002 18:25:30 +0200
Message-ID: <NFBBLGNBALMEBCOCNPCCMEPDCEAA.mmoreno@cipres.upm.es>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Subject: [Sip] Over SIP Timer
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi

Are the SIP timer B, F and T4 necessary with reliable transports (TCP,
SCTP)???

Why??


Thanks

Manuel

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



From mailnull@www1.ietf.org  Wed Sep 11 12:49:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16015
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 12:49:29 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BGoiB27869
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 12:50:44 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BGo2v27826;
	Wed, 11 Sep 2002 12:50:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BGkfv27656
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 12:46:41 -0400
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15811
	for <sip@ietf.org>; Wed, 11 Sep 2002 12:44:55 -0400 (EDT)
Received: from mira-sjc5-9.cisco.com (IDENT:mirapoint@mira-sjc5-9.cisco.com [171.71.163.32])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8BGk5KB002332;
	Wed, 11 Sep 2002 09:46:05 -0700 (PDT)
Received: from cj14 (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-9.cisco.com (Mirapoint)
	with SMTP id ADZ25979;
	Wed, 11 Sep 2002 09:46:11 -0700 (PDT)
From: "Cullen Jennings" <fluffy@cisco.com>
To: "M. Ranganathan" <mranga@nist.gov>, <Mpierce1@aol.com>
Cc: <syadavalli@telogy.com>, <sip@ietf.org>
Subject: RE: [Sip] RE: [Sip-implementors] sip version
Date: Wed, 11 Sep 2002 09:46:21 -0700
Message-ID: <DLEHICEBMNEIPCACNLPCEEPECEAA.fluffy@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <Pine.LNX.4.33.0209061322540.17665-100000@jitterbug.antd.nist.gov>
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


Ok, I have put on my asbestos underwear and will take a minor stab at this
one....

It does not need a new version number because a 2543 sip device will
interoperate fine with a 3261 device.

The "z9hG4bK forever" hack does not mean that the device is 3261 compliant.
There are lots of things that do z9hG4bK but don't do loose routing.

Anyway, give 3261 is out, it is probably a mute point.

Cullen

> -----Original Message-----
> From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of M.
> Ranganathan
> Sent: Friday, September 06, 2002 10:25 AM
> To: Mpierce1@aol.com
> Cc: syadavalli@telogy.com; sip@ietf.org;
> sip-implementors@cs.columbia.edu
> Subject: Re: [Sip] RE: [Sip-implementors] sip version
>
>
>
> But it does! The new version number is 2.0z9hG4bK
>
> (where z9hG4bK is the branch magic cookie :-)
>
> Ranga.
>
> On Thu, 5 Sep 2002 Mpierce1@aol.com wrote:
>
> > In a message dated 9/4/02 3:16:44 PM Eastern Daylight Time,
> > syadavalli@telogy.com writes:
> >
> >
> > > Am I missing something here?
> > >
> > > I thought the RFC3261 SHOULD have assigned a different SIP
> version number...
> > > that's what a version number is meant for!
> > >
> > > - Satya
> > >
> >
> > I'm waiting with bated breadth for the answer to this one!
> >
> > Mike Pierce
> > Artel
> >
> >
>
> --
> M. Ranganathan
> Advanced Networking Technologies Divsion
> National Institute of Standards and Technology (NIST)
> 100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899.
> Tel: 301 975 3664 ; Fax: 301 590 0932
>
> Advanced Networking Technologies For the People!
>
>
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>

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



From mailnull@www1.ietf.org  Wed Sep 11 12:58:30 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16432
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 12:58:30 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BGxjk28415
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 12:59:45 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BGxBv28378;
	Wed, 11 Sep 2002 12:59:11 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BGuhv28253
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 12:56:43 -0400
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16339;
	Wed, 11 Sep 2002 12:54:56 -0400 (EDT)
Received: from mira-sjc5-9.cisco.com (IDENT:mirapoint@mira-sjc5-9.cisco.com [171.71.163.32])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8BGu7KB007805;
	Wed, 11 Sep 2002 09:56:07 -0700 (PDT)
Received: from cj14 (ssh-sjc-1.cisco.com [171.68.225.134])
	by mira-sjc5-9.cisco.com (Mirapoint)
	with SMTP id ADZ26340;
	Wed, 11 Sep 2002 09:56:12 -0700 (PDT)
From: "Cullen Jennings" <fluffy@cisco.com>
To: "Jitender Arora" <jarora@aastra.com>
Cc: <sip@ietf.org>, <sipping@ietf.org>
Subject: RE: [Sip] Regarding SIP CDR inforamtion ( from a Media Gateway Controller p erspective)
Date: Wed, 11 Sep 2002 09:56:23 -0700
Message-ID: <DLEHICEBMNEIPCACNLPCGEPECEAA.fluffy@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <F924CEFBBF62D611A0C600D0B76ED03712FE7F@h3s68a245n132.user.nortelnetworks.com>
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


The current mapping of SIP to Radius accounting that many shipping proxies
and gateways use is pretty bizarre stuff. The whole billing area is
something I think could use some work but it is pretty hard to get good
consensus on it. On one hand there is a good argument that Radius is
woefully inadequate and on the other hand there is the argument that most
deployed systems that are doing minute based billing use Radius.

Please move this thread to sipping and remove sip from any replies.

Cullen


> -----Original Message-----
> From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of
> Jitender Arora
> Sent: Friday, September 06, 2002 1:51 PM
> To: Jonathan Rosenberg
> Cc: sip@ietf.org
> Subject: [Sip] Regarding SIP CDR inforamtion ( from a Media Gateway
> Controller p erspective)
>
>
> Hi ,
>
>      could somebody please point to the draft or RFC which contains the
> information about how the
>      CDR ( call detail records ) are generated for the SIP calls
> ( what all
> informaion should be there
>      in the CDR ) from the Media Gateway Controller Perspective .
>
>      Is there any document available for this ...If yes please let me know
> ....
>
> Thanks and Regards,
> jitender .
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>

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



From mailnull@www1.ietf.org  Wed Sep 11 13:02:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16577
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 13:02:56 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BH4BJ28707
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 13:04:11 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BH3nv28643;
	Wed, 11 Sep 2002 13:03:49 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BGxYv28406
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 12:59:34 -0400
Received: from znsgs01r.europe.nortel.com (h2s128a211n47.user.nortelnetworks.com [47.211.128.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16414
	for <sip@ietf.org>; Wed, 11 Sep 2002 12:57:47 -0400 (EDT)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.160.46.124])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g8BGvqC24952;
	Wed, 11 Sep 2002 17:57:52 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <S3PAHNNW>; Wed, 11 Sep 2002 17:57:52 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7698@zwcwd00r.europe.nortel.com>
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'seancolson@yahoo.com'" <seancolson@yahoo.com>,
        "'Mahey, Sonit'"
	 <Sonit.Mahey@icn.siemens.com>, sip@ietf.org
Cc: "'Sandhu, Hari'" <Hari.Sandhu@icn.siemens.com>
Subject: RE: [Sip] S/MIME certificates question
Date: Wed, 11 Sep 2002 17:57:44 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C259B3.C5EDC10A"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

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_001_01C259B3.C5EDC10A
Content-Type: text/plain;
	charset="iso-8859-1"

I guess I can see why you "MUST" include the certificate in the SIP message,
as you have no way of knowing whether the receiver has any other way to get
it. The question is whether it MUST be in the same CMS SignedData structure
as the signature itself, or wherther it could be in another MIME body part,
where it could be indirected.

Note that if you use indirection, you still have no idea whether the
receiver has any way to get the data. But it is a requirement of the
indirection mechanism that it can fall back to in-line carriage of the data,
if the receiver doesn't support indirection or the URI scheme provided. At
least this is what I thought - Sean can correct me if I'm wrong!

...Mark

> -----Original Message-----
> From: Sean Olson [mailto:seancolson@yahoo.com]
> Sent: 11 September 2002 17:00
> To: 'Mahey, Sonit'; Watson, Mark [MOP:EP10:EXCH]; sip@ietf.org
> Cc: 'Sandhu, Hari'
> Subject: RE: [Sip] S/MIME certificates question
> 
> 
> This does make a great deal of sense. And I think it would be an
> excellent
> use of content indirection. Could someone clarify the purpose of the
> "MUST"
> in this text?
> 
> Cheers,
> Sean Olson
> Microsoft
> 
> -----Original Message-----
> From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On 
> Behalf Of Mahey,
> Sonit
> Sent: Wednesday, September 11, 2002 7:31 AM
> To: 'Mark Watson'; 'sip@ietf.org'
> Cc: Sandhu, Hari
> Subject: RE: [Sip] S/MIME certificates question
> 
> 
> Hi All,
> 
> If SIP does not prohibit what Mark suggests, I think Mark's idea is
> good. I like the notion of decoupling to the extent possible.
> 
> regards,
> - sonit
> Sonit Mahey,
> Systems Architect,
> Siemens Network Convergence,
> *: 10 Technology Park Dr., Westford, MA 01886
> ': 978.923.3271
> *: Sonit.Mahey@icn.siemens.com 
> http://www.siemens.com
> 
> 
> -----Original Message-----
> From: Mark Watson [mailto:mwatson@nortelnetworks.com]
> Sent: Wednesday, September 11, 2002 9:49 AM
> To: 'sip@ietf.org'
> Subject: [Sip] S/MIME certificates question
> 
> 
> All,
> 
> In RFC3261 23.2 it states:
> 
> "Whenever the CMS SignedData message is used in S/MIME for 
> SIP, it MUST
> contain the certificate bearing the public key necessary to verify the
> signature."
> 
> I assume that "it" refers to the CMS SignedData message.
> 
> An alternative would presumably be for the certificate to be contained
> in a separate MIME part of type application/pks7-mime with
> smime-type="certs-only". This would have the advantage that the
> certificate, which does not change often, and which I 
> understand can be
> fairly large, could make use of content indirection.
> 
> If the certificate is required to be embedded in the same SignedData
> object as the signature itself, then I guess this would not 
> be possible.
> 
> So, is inclusion of the certificate as a separate body part, 
> prohibited
> by the SIP specification ?
> 
> Regards...Mark
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip Use
> sipping@ietf.org for new developments on the application of sip
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip Use
> sipping@ietf.org for new developments on the application of sip
> 
> 

------_=_NextPart_001_01C259B3.C5EDC10A
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sip] S/MIME certificates question</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I guess I can see why you &quot;MUST&quot; include =
the certificate in the SIP message, as you have no way of knowing =
whether the receiver has any other way to get it. The question is =
whether it MUST be in the same CMS SignedData structure as the =
signature itself, or wherther it could be in another MIME body part, =
where it could be indirected.</FONT></P>

<P><FONT SIZE=3D2>Note that if you use indirection, you still have no =
idea whether the receiver has any way to get the data. But it is a =
requirement of the indirection mechanism that it can fall back to =
in-line carriage of the data, if the receiver doesn't support =
indirection or the URI scheme provided. At least this is what I thought =
- Sean can correct me if I'm wrong!</FONT></P>

<P><FONT SIZE=3D2>...Mark</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Sean Olson [<A =
HREF=3D"mailto:seancolson@yahoo.com">mailto:seancolson@yahoo.com</A>]</F=
ONT>
<BR><FONT SIZE=3D2>&gt; Sent: 11 September 2002 17:00</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'Mahey, Sonit'; Watson, Mark =
[MOP:EP10:EXCH]; sip@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: 'Sandhu, Hari'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Sip] S/MIME certificates =
question</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; This does make a great deal of sense. And I =
think it would be an</FONT>
<BR><FONT SIZE=3D2>&gt; excellent</FONT>
<BR><FONT SIZE=3D2>&gt; use of content indirection. Could someone =
clarify the purpose of the</FONT>
<BR><FONT SIZE=3D2>&gt; &quot;MUST&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; in this text?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Cheers,</FONT>
<BR><FONT SIZE=3D2>&gt; Sean Olson</FONT>
<BR><FONT SIZE=3D2>&gt; Microsoft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: sip-admin@ietf.org [<A =
HREF=3D"mailto:sip-admin@ietf.org">mailto:sip-admin@ietf.org</A>] On =
</FONT>
<BR><FONT SIZE=3D2>&gt; Behalf Of Mahey,</FONT>
<BR><FONT SIZE=3D2>&gt; Sonit</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Wednesday, September 11, 2002 7:31 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'Mark Watson'; 'sip@ietf.org'</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: Sandhu, Hari</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Sip] S/MIME certificates =
question</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hi All,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; If SIP does not prohibit what Mark suggests, I =
think Mark's idea is</FONT>
<BR><FONT SIZE=3D2>&gt; good. I like the notion of decoupling to the =
extent possible.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; regards,</FONT>
<BR><FONT SIZE=3D2>&gt; - sonit</FONT>
<BR><FONT SIZE=3D2>&gt; Sonit Mahey,</FONT>
<BR><FONT SIZE=3D2>&gt; Systems Architect,</FONT>
<BR><FONT SIZE=3D2>&gt; Siemens Network Convergence,</FONT>
<BR><FONT SIZE=3D2>&gt; *: 10 Technology Park Dr., Westford, MA =
01886</FONT>
<BR><FONT SIZE=3D2>&gt; ': 978.923.3271</FONT>
<BR><FONT SIZE=3D2>&gt; *: Sonit.Mahey@icn.siemens.com </FONT>
<BR><FONT SIZE=3D2>&gt; <A HREF=3D"http://www.siemens.com" =
TARGET=3D"_blank">http://www.siemens.com</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Mark Watson [<A =
HREF=3D"mailto:mwatson@nortelnetworks.com">mailto:mwatson@nortelnetworks=
.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Wednesday, September 11, 2002 9:49 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'sip@ietf.org'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [Sip] S/MIME certificates =
question</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; All,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; In RFC3261 23.2 it states:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &quot;Whenever the CMS SignedData message is =
used in S/MIME for </FONT>
<BR><FONT SIZE=3D2>&gt; SIP, it MUST</FONT>
<BR><FONT SIZE=3D2>&gt; contain the certificate bearing the public key =
necessary to verify the</FONT>
<BR><FONT SIZE=3D2>&gt; signature.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I assume that &quot;it&quot; refers to the CMS =
SignedData message.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; An alternative would presumably be for the =
certificate to be contained</FONT>
<BR><FONT SIZE=3D2>&gt; in a separate MIME part of type =
application/pks7-mime with</FONT>
<BR><FONT SIZE=3D2>&gt; smime-type=3D&quot;certs-only&quot;. This would =
have the advantage that the</FONT>
<BR><FONT SIZE=3D2>&gt; certificate, which does not change often, and =
which I </FONT>
<BR><FONT SIZE=3D2>&gt; understand can be</FONT>
<BR><FONT SIZE=3D2>&gt; fairly large, could make use of content =
indirection.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; If the certificate is required to be embedded =
in the same SignedData</FONT>
<BR><FONT SIZE=3D2>&gt; object as the signature itself, then I guess =
this would not </FONT>
<BR><FONT SIZE=3D2>&gt; be possible.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; So, is inclusion of the certificate as a =
separate body part, </FONT>
<BR><FONT SIZE=3D2>&gt; prohibited</FONT>
<BR><FONT SIZE=3D2>&gt; by the SIP specification ?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Regards...Mark</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Sip mailing list&nbsp; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sip" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sip</A></FONT>
<BR><FONT SIZE=3D2>&gt; This list is for NEW development of the core =
SIP Protocol</FONT>
<BR><FONT SIZE=3D2>&gt; Use sip-implementors@cs.columbia.edu for =
questions on current sip Use</FONT>
<BR><FONT SIZE=3D2>&gt; sipping@ietf.org for new developments on the =
application of sip</FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Sip mailing list&nbsp; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sip" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sip</A></FONT>
<BR><FONT SIZE=3D2>&gt; This list is for NEW development of the core =
SIP Protocol</FONT>
<BR><FONT SIZE=3D2>&gt; Use sip-implementors@cs.columbia.edu for =
questions on current sip Use</FONT>
<BR><FONT SIZE=3D2>&gt; sipping@ietf.org for new developments on the =
application of sip</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C259B3.C5EDC10A--
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Wed Sep 11 13:17:36 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17356
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 13:17:36 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BHIno30147
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 13:18:49 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BHIWv30117;
	Wed, 11 Sep 2002 13:18:32 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BHHUv30036
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 13:17:30 -0400
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17276
	for <sip@ietf.org>; Wed, 11 Sep 2002 13:15:46 -0400 (EDT)
Received: from mira-sjc5-7.cisco.com (IDENT:mirapoint@mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8BHGPKB019645;
	Wed, 11 Sep 2002 10:16:25 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ACO77273;
	Wed, 11 Sep 2002 10:11:56 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id KAA23119; Wed, 11 Sep 2002 10:16:22 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15743.31334.338536.75474@thomasm-u1.cisco.com>
Date: Wed, 11 Sep 2002 10:16:22 -0700 (PDT)
To: "Mark Watson" <mwatson@nortelnetworks.com>
Cc: "'seancolson@yahoo.com'" <seancolson@yahoo.com>,
        "'Mahey, Sonit'"
	 <Sonit.Mahey@icn.siemens.com>, sip@ietf.org,
        "'Sandhu, Hari'" <Hari.Sandhu@icn.siemens.com>
Subject: RE: [Sip] S/MIME certificates question
In-Reply-To: <A3C2399B2FACD411A54200508BE39C74054F7698@zwcwd00r.europe.nortel.com>
References: <A3C2399B2FACD411A54200508BE39C74054F7698@zwcwd00r.europe.nortel.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Mark Watson writes:
 > I guess I can see why you "MUST" include the certificate in the SIP message,
 > as you have no way of knowing whether the receiver has any other way to get
 > it. The question is whether it MUST be in the same CMS SignedData structure
 > as the signature itself, or wherther it could be in another MIME body part,
 > where it could be indirected.

   That's only the start of your problems. Even if you
   send a cert, you have no idea whether the other side
   trusts the cert's signing root. Nor without any
   prior contact are you likely to know the other
   side's public key, so you're not likely to be
   able to encrypt the body. Which all makes the
   need for some sort of directory service all the
   more likely, especially since these kinds of 
   considerations cannot be dealt with by the
   signaling alone... 

   Yet another reason why just plopping S/MIME in
   as a replacement for PGP didn't actually do
   much to solve real life problems. Yes, yes, I
   know... dead horse. I'll shut up now.

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



From mailnull@www1.ietf.org  Wed Sep 11 13:30:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17791
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 13:30:08 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BHVMX30735
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 13:31:22 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BHUav30706;
	Wed, 11 Sep 2002 13:30:36 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BHTfv30661
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 13:29:41 -0400
Received: from mirlo.dit.upm.es (mirlo.dit.upm.es [138.4.5.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17724
	for <sip@ietf.org>; Wed, 11 Sep 2002 13:27:56 -0400 (EDT)
Received: from perdiz (perdiz [138.4.50.3]) by mirlo.dit.upm.es (8.8.5/8.7.3) with SMTP id RAA25707 for <sip@ietf.org>; Wed, 11 Sep 2002 17:30:19 GMT
From: =?iso-8859-1?Q?Manuel_Moreno_Mart=EDn?= <mmoreno@cipres.upm.es>
To: "Sip" <sip@ietf.org>
Date: Wed, 11 Sep 2002 19:28:45 +0200
Message-ID: <NFBBLGNBALMEBCOCNPCCIEPFCEAA.mmoreno@cipres.upm.es>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Subject: [Sip] Question
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


I wanted to know if there's any tool or SIP UA implementation available
which I could use for testing scenarios involving INFO.

Any information would be of great help.

Thanks

MAnuel

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



From mailnull@www1.ietf.org  Wed Sep 11 15:49:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22788
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 15:49:39 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BJosA06703
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 15:50:54 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BJo8v06692;
	Wed, 11 Sep 2002 15:50:08 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BJmJv06606
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 15:48:19 -0400
Received: from oak.neustar.com (oak.neustar.com [209.173.53.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22702
	for <sip@ietf.org>; Wed, 11 Sep 2002 15:46:33 -0400 (EDT)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by oak.neustar.com (8.11.0/8.11.0) with ESMTP id g8BJlbG12331;
	Wed, 11 Sep 2002 19:47:37 GMT
Received: by STNTIMC1 with Internet Mail Service (5.5.2653.19)
	id <RZ7WB1XV>; Wed, 11 Sep 2002 15:48:45 -0400
Message-ID: <15A2739B7DAA624D8091C65981D7DA815EB1AE@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'sip@ietf.org'"
	 <sip@ietf.org>
Subject: RE: [Sip] S/MIME certificates question
Date: Wed, 11 Sep 2002 15:47:38 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>


Our intention was not to rule out things like content indirection, although
at the time we didn't understand SIP-based content indirection well enough
to make special allowances for it. The MUST is present, as Mark conjectures,
in order to ensure that the cert will be available to the destination, not
to dictate any particular manner in which it must be made available. I think
the use of content indirection meets the spirit, if not exactly the letter,
of the passage quoted below.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Mark Watson [mailto:mwatson@nortelnetworks.com]
> Sent: Wednesday, September 11, 2002 6:49 AM
> To: 'sip@ietf.org'
> Subject: [Sip] S/MIME certificates question
> 
> 
> All,
> 
> In RFC3261 23.2 it states:
> 
> "Whenever the CMS SignedData message is used in S/MIME for 
> SIP, it MUST
> contain the certificate bearing the public key necessary to verify the
> signature."
> 
> I assume that "it" refers to the CMS SignedData message.
> 
> An alternative would presumably be for the certificate to be 
> contained in a
> separate MIME part of type application/pks7-mime with
> smime-type="certs-only". This would have the advantage that 
> the certificate,
> which does not change often, and which I understand can be 
> fairly large,
> could make use of content indirection.
> 
> If the certificate is required to be embedded in the same 
> SignedData object
> as the signature itself, then I guess this would not be possible.
> 
> So, is inclusion of the certificate as a separate body part, 
> prohibited by
> the SIP specification ?
> 
> Regards...Mark
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Wed Sep 11 17:52:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26244
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 17:52:54 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BLsCD13561
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 17:54:12 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BLrrv13551;
	Wed, 11 Sep 2002 17:53:53 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BLqNv13521
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 17:52:23 -0400
Received: from imail02.net2phone.com (imail02.net2phone.com [216.53.16.65])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26232
	for <sip@ietf.org>; Wed, 11 Sep 2002 17:50:35 -0400 (EDT)
Received: from mailsvr.net2phone.com (exchange.net2phone.com [216.53.60.1])
	by imail02.net2phone.com (8.12.2/8.12.2) with ESMTP id g8BLplJC002313
	for <sip@ietf.org>; Wed, 11 Sep 2002 17:51:47 -0400 (EDT)
Received: by mailsvr with Internet Mail Service (5.5.2653.19)
	id <SWZYKQY7>; Wed, 11 Sep 2002 17:51:47 -0400
Message-ID: <C987333A50714943A7633CFD9243024C07A9E9@wlbmail01>
From: Romel Khan <rkhan@net2phone.com>
To: "'sip@ietf.org'" <sip@ietf.org>
Date: Wed, 11 Sep 2002 17:46:32 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sip] Originating Line Information
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

Is there any existing internet draft that talks about how to pass
Originating Line Information (e.g. hotel, motel, prison) in SIP?
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Wed Sep 11 18:15:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26610
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 18:15:42 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BMH0314710
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 18:17:00 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BMGfv14699;
	Wed, 11 Sep 2002 18:16:41 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BMFDv14663
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 18:15:13 -0400
Received: from mail2.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26560
	for <sip@ietf.org>; Wed, 11 Sep 2002 18:13:25 -0400 (EDT)
Received: from DYN-TX-EXCH-001.dynamicsoft.com (dyn-tx-exch-001 [63.110.3.8])
	by mail2.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id g8BMDqm4017213;
	Wed, 11 Sep 2002 18:13:53 -0400 (EDT)
Received: by DYN-TX-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <S3PQXSC7>; Wed, 11 Sep 2002 17:14:29 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F3A64126@DYN-TX-EXCH-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Romel Khan'" <rkhan@net2phone.com>, "'sip@ietf.org'" <sip@ietf.org>
Subject: RE: [Sip] Originating Line Information
Date: Wed, 11 Sep 2002 17:14:29 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

I don't beleive so.

/a

> -----Original Message-----
> From: Romel Khan [mailto:rkhan@net2phone.com]
> Sent: Wednesday, September 11, 2002 16:47
> To: 'sip@ietf.org'
> Subject: [Sip] Originating Line Information
> 
> 
> Is there any existing internet draft that talks about how to pass
> Originating Line Information (e.g. hotel, motel, prison) in SIP?
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Wed Sep 11 18:56:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27715
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 18:56:39 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8BMvvk17017
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 18:57:57 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BMvav17002;
	Wed, 11 Sep 2002 18:57:36 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BMuQv16960
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 18:56:26 -0400
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27670
	for <sip@ietf.org>; Wed, 11 Sep 2002 18:54:37 -0400 (EDT)
Received: from mira-sjc5-7.cisco.com (IDENT:mirapoint@mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8BMteKB009680;
	Wed, 11 Sep 2002 15:55:49 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ACO87960;
	Wed, 11 Sep 2002 15:51:08 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id PAA23158; Wed, 11 Sep 2002 15:55:35 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15743.51687.155949.316538@thomasm-u1.cisco.com>
Date: Wed, 11 Sep 2002 15:55:35 -0700 (PDT)
To: "Peterson, Jon" <jon.peterson@neustar.biz>
Cc: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'sip@ietf.org'"
	 <sip@ietf.org>
Subject: RE: [Sip] S/MIME certificates question
In-Reply-To: <15A2739B7DAA624D8091C65981D7DA815EB1AE@stntexch2.va.neustar.com>
References: <15A2739B7DAA624D8091C65981D7DA815EB1AE@stntexch2.va.neustar.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Peterson, Jon writes:
 > 
 > Our intention was not to rule out things like content indirection, although
 > at the time we didn't understand SIP-based content indirection well enough
 > to make special allowances for it. The MUST is present, as Mark conjectures,
 > in order to ensure that the cert will be available to the destination, not
 > to dictate any particular manner in which it must be made available. I think
 > the use of content indirection meets the spirit, if not exactly the letter,
 > of the passage quoted below.

   If there are other ways to obtain the certificate -- 
   assuming that there's a certificate at all -- then
   forcing it to be sent through SIP is quite wasteful.
   In fact, the device itself may not even know what 
   certificates are associated with its public key.

   And this, of course, doesn't even begin to address
   the larger issue of not knowing what certs roots
   and namespaces are in common between the two UA's.
   My browser, for example, knows about the roots of
   about 3 dozen CA's; there's no guarantee that the
   cert under the root the UAC chooses will have any
   relevance to the UAS; it's pretty much the same
   shot in the dark as not sending any cert at
   all. As in, the likelihood of interoperablity
   on almost any scale beyond "lab" is extremely
   low as currently specified.

	  Mike

 > 
 > Jon Peterson
 > NeuStar, Inc.
 > 
 > > -----Original Message-----
 > > From: Mark Watson [mailto:mwatson@nortelnetworks.com]
 > > Sent: Wednesday, September 11, 2002 6:49 AM
 > > To: 'sip@ietf.org'
 > > Subject: [Sip] S/MIME certificates question
 > > 
 > > 
 > > All,
 > > 
 > > In RFC3261 23.2 it states:
 > > 
 > > "Whenever the CMS SignedData message is used in S/MIME for 
 > > SIP, it MUST
 > > contain the certificate bearing the public key necessary to verify the
 > > signature."
 > > 
 > > I assume that "it" refers to the CMS SignedData message.
 > > 
 > > An alternative would presumably be for the certificate to be 
 > > contained in a
 > > separate MIME part of type application/pks7-mime with
 > > smime-type="certs-only". This would have the advantage that 
 > > the certificate,
 > > which does not change often, and which I understand can be 
 > > fairly large,
 > > could make use of content indirection.
 > > 
 > > If the certificate is required to be embedded in the same 
 > > SignedData object
 > > as the signature itself, then I guess this would not be possible.
 > > 
 > > So, is inclusion of the certificate as a separate body part, 
 > > prohibited by
 > > the SIP specification ?
 > > 
 > > Regards...Mark
 > > 
 > > _______________________________________________
 > > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
 > > This list is for NEW development of the core SIP Protocol
 > > Use sip-implementors@cs.columbia.edu for questions on current sip
 > > Use sipping@ietf.org for new developments on the application of sip
 > > 
 > _______________________________________________
 > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
 > This list is for NEW development of the core SIP Protocol
 > Use sip-implementors@cs.columbia.edu for questions on current sip
 > Use sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Wed Sep 11 22:17:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00995
	for <sip-archive@odin.ietf.org>; Wed, 11 Sep 2002 22:17:46 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8C2J5r26438
	for sip-archive@odin.ietf.org; Wed, 11 Sep 2002 22:19:05 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8C2IOv26408;
	Wed, 11 Sep 2002 22:18:24 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8C2G7v26345
	for <sip@optimus.ietf.org>; Wed, 11 Sep 2002 22:16:07 -0400
Received: from oak.neustar.com (oak.neustar.com [209.173.53.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00940
	for <sip@ietf.org>; Wed, 11 Sep 2002 22:14:17 -0400 (EDT)
Received: from stntimc1.va.neustar.com (stntimc1.va.neustar.com [10.31.13.11])
	by oak.neustar.com (8.11.0/8.11.0) with ESMTP id g8C2FBG21891;
	Thu, 12 Sep 2002 02:15:11 GMT
Received: by STNTIMC1 with Internet Mail Service (5.5.2653.19)
	id <RZ7WBG5D>; Wed, 11 Sep 2002 22:16:19 -0400
Message-ID: <15A2739B7DAA624D8091C65981D7DA815EB1B0@stntexch2.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Romel Khan'" <rkhan@net2phone.com>, "'sip@ietf.org'" <sip@ietf.org>
Subject: RE: [Sip] Originating Line Information
Date: Wed, 11 Sep 2002 22:15:12 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

This is more a SIPPING issue than a SIP issue... but yes, I was hoping that
my proposal for a calling party's category tel URL parameter cover this (it
speaks to the fact that in North American networks, the OLI is often the
repository for information that appears in the CPC elsewhere). The draft
happens to be expired at the moment, though I will be resubmitting it fairly
soon.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Romel Khan [mailto:rkhan@net2phone.com]
> Sent: Wednesday, September 11, 2002 2:47 PM
> To: 'sip@ietf.org'
> Subject: [Sip] Originating Line Information
> 
> 
> Is there any existing internet draft that talks about how to pass
> Originating Line Information (e.g. hotel, motel, prison) in SIP?
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Thu Sep 12 05:35:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17791
	for <sip-archive@odin.ietf.org>; Thu, 12 Sep 2002 05:35:20 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8C9aWK25964
	for sip-archive@odin.ietf.org; Thu, 12 Sep 2002 05:36:32 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8C9Zpv25925;
	Thu, 12 Sep 2002 05:35:51 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8C9Ykv25812
	for <sip@optimus.ietf.org>; Thu, 12 Sep 2002 05:34:46 -0400
Received: from znsgs01r.europe.nortel.com (h2s128a211n47.user.nortelnetworks.com [47.211.128.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17737
	for <sip@ietf.org>; Thu, 12 Sep 2002 05:32:59 -0400 (EDT)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.160.46.124])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g8C9Xmk05483;
	Thu, 12 Sep 2002 10:33:48 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <S3PAH8QQ>; Thu, 12 Sep 2002 10:33:48 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F769B@zwcwd00r.europe.nortel.com>
From: "Mark Watson" <mwatson@nortelnetworks.com>
To: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'sip@ietf.org'"
	 <sip@ietf.org>
Subject: RE: [Sip] S/MIME certificates question
Date: Thu, 12 Sep 2002 10:33:47 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25A3E.BEB44996"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

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_001_01C25A3E.BEB44996
Content-Type: text/plain;
	charset="iso-8859-1"

If there is agreement about the interpretation of this 'MUST', along the
lines that Jon suggests below, is there any way we can clarify this in a
specification ? For example by providing an example somewhere in which the
cert is in a separate MIME body & not in the CMS SignedData ? Perhaps in the
eventual Content Indirection specification ?

[It seems there is some discussion about whether the MUST should be there
*at all*, which is a separate issue. My suggestion above is based on the
fact that it IS there in RFC3261 & we should clarify how it should be
(re)interpreted.]

...Mark

> -----Original Message-----
> From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> Sent: 11 September 2002 20:48
> To: Watson, Mark [MOP:EP10:EXCH]; 'sip@ietf.org'
> Subject: RE: [Sip] S/MIME certificates question
> 
> 
> 
> Our intention was not to rule out things like content 
> indirection, although
> at the time we didn't understand SIP-based content 
> indirection well enough
> to make special allowances for it. The MUST is present, as 
> Mark conjectures,
> in order to ensure that the cert will be available to the 
> destination, not
> to dictate any particular manner in which it must be made 
> available. I think
> the use of content indirection meets the spirit, if not 
> exactly the letter,
> of the passage quoted below.
> 
> Jon Peterson
> NeuStar, Inc.
> 
> > -----Original Message-----
> > From: Mark Watson [mailto:mwatson@nortelnetworks.com]
> > Sent: Wednesday, September 11, 2002 6:49 AM
> > To: 'sip@ietf.org'
> > Subject: [Sip] S/MIME certificates question
> > 
> > 
> > All,
> > 
> > In RFC3261 23.2 it states:
> > 
> > "Whenever the CMS SignedData message is used in S/MIME for 
> > SIP, it MUST
> > contain the certificate bearing the public key necessary to 
> verify the
> > signature."
> > 
> > I assume that "it" refers to the CMS SignedData message.
> > 
> > An alternative would presumably be for the certificate to be 
> > contained in a
> > separate MIME part of type application/pks7-mime with
> > smime-type="certs-only". This would have the advantage that 
> > the certificate,
> > which does not change often, and which I understand can be 
> > fairly large,
> > could make use of content indirection.
> > 
> > If the certificate is required to be embedded in the same 
> > SignedData object
> > as the signature itself, then I guess this would not be possible.
> > 
> > So, is inclusion of the certificate as a separate body part, 
> > prohibited by
> > the SIP specification ?
> > 
> > Regards...Mark
> > 
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> > 
> 

------_=_NextPart_001_01C25A3E.BEB44996
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sip] S/MIME certificates question</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>If there is agreement about the interpretation of =
this 'MUST', along the lines that Jon suggests below, is there any way =
we can clarify this in a specification ? For example by providing an =
example somewhere in which the cert is in a separate MIME body &amp; =
not in the CMS SignedData ? Perhaps in the eventual Content Indirection =
specification ?</FONT></P>

<P><FONT SIZE=3D2>[It seems there is some discussion about whether the =
MUST should be there *at all*, which is a separate issue. My suggestion =
above is based on the fact that it IS there in RFC3261 &amp; we should =
clarify how it should be (re)interpreted.]</FONT></P>

<P><FONT SIZE=3D2>...Mark</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Peterson, Jon [<A =
HREF=3D"mailto:jon.peterson@neustar.biz">mailto:jon.peterson@neustar.biz=
</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 11 September 2002 20:48</FONT>
<BR><FONT SIZE=3D2>&gt; To: Watson, Mark [MOP:EP10:EXCH]; =
'sip@ietf.org'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Sip] S/MIME certificates =
question</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Our intention was not to rule out things like =
content </FONT>
<BR><FONT SIZE=3D2>&gt; indirection, although</FONT>
<BR><FONT SIZE=3D2>&gt; at the time we didn't understand SIP-based =
content </FONT>
<BR><FONT SIZE=3D2>&gt; indirection well enough</FONT>
<BR><FONT SIZE=3D2>&gt; to make special allowances for it. The MUST is =
present, as </FONT>
<BR><FONT SIZE=3D2>&gt; Mark conjectures,</FONT>
<BR><FONT SIZE=3D2>&gt; in order to ensure that the cert will be =
available to the </FONT>
<BR><FONT SIZE=3D2>&gt; destination, not</FONT>
<BR><FONT SIZE=3D2>&gt; to dictate any particular manner in which it =
must be made </FONT>
<BR><FONT SIZE=3D2>&gt; available. I think</FONT>
<BR><FONT SIZE=3D2>&gt; the use of content indirection meets the =
spirit, if not </FONT>
<BR><FONT SIZE=3D2>&gt; exactly the letter,</FONT>
<BR><FONT SIZE=3D2>&gt; of the passage quoted below.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Jon Peterson</FONT>
<BR><FONT SIZE=3D2>&gt; NeuStar, Inc.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: Mark Watson [<A =
HREF=3D"mailto:mwatson@nortelnetworks.com">mailto:mwatson@nortelnetworks=
.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: Wednesday, September 11, 2002 6:49 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: 'sip@ietf.org'</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: [Sip] S/MIME certificates =
question</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; All,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; In RFC3261 23.2 it states:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &quot;Whenever the CMS SignedData message =
is used in S/MIME for </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; SIP, it MUST</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; contain the certificate bearing the public =
key necessary to </FONT>
<BR><FONT SIZE=3D2>&gt; verify the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; signature.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I assume that &quot;it&quot; refers to the =
CMS SignedData message.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; An alternative would presumably be for the =
certificate to be </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; contained in a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; separate MIME part of type =
application/pks7-mime with</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; smime-type=3D&quot;certs-only&quot;. This =
would have the advantage that </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the certificate,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; which does not change often, and which I =
understand can be </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; fairly large,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; could make use of content =
indirection.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; If the certificate is required to be =
embedded in the same </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; SignedData object</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; as the signature itself, then I guess this =
would not be possible.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; So, is inclusion of the certificate as a =
separate body part, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; prohibited by</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the SIP specification ?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Regards...Mark</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sip mailing list&nbsp; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sip" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sip</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; This list is for NEW development of the =
core SIP Protocol</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Use sip-implementors@cs.columbia.edu for =
questions on current sip</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Use sipping@ietf.org for new developments =
on the application of sip</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C25A3E.BEB44996--
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Thu Sep 12 14:59:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03630
	for <sip-archive@odin.ietf.org>; Thu, 12 Sep 2002 14:59:52 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8CJ17k24115
	for sip-archive@odin.ietf.org; Thu, 12 Sep 2002 15:01:07 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CIxwv23941;
	Thu, 12 Sep 2002 14:59:58 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CIugv23761
	for <sip@optimus.ietf.org>; Thu, 12 Sep 2002 14:56:42 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03289
	for <sip@ietf.org>; Thu, 12 Sep 2002 14:54:55 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.76])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g8CIu2YH021918;
	Thu, 12 Sep 2002 14:56:03 -0400 (EDT)
Message-ID: <3D80E342.1060702@dynamicsoft.com>
Date: Thu, 12 Sep 2002 14:56:02 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mark Watson <mwatson@nortelnetworks.com>
CC: "'Peterson, Jon'" <jon.peterson@neustar.biz>,
        "'sip@ietf.org'" <sip@ietf.org>
Subject: Re: [Sip] S/MIME certificates question
References: <A3C2399B2FACD411A54200508BE39C74054F769B@zwcwd00r.europe.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit



Mark Watson wrote:
> If there is agreement about the interpretation of this 'MUST', along the 
> lines that Jon suggests below, is there any way we can clarify this in a 
> specification ? For example by providing an example somewhere in which 
> the cert is in a separate MIME body & not in the CMS SignedData ? 
> Perhaps in the eventual Content Indirection specification ?

I'll log this in bugzilla for clarification.

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Thu Sep 12 15:07:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03994
	for <sip-archive@odin.ietf.org>; Thu, 12 Sep 2002 15:07:17 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8CJ8Wu25005
	for sip-archive@odin.ietf.org; Thu, 12 Sep 2002 15:08:32 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CJ7tv24961;
	Thu, 12 Sep 2002 15:07:55 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CJ4hv24245
	for <sip@optimus.ietf.org>; Thu, 12 Sep 2002 15:04:43 -0400
Received: from dyn-tx-app-007.dfw.dynamicsoft.com ([63.110.3.105])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03754
	for <sip@ietf.org>; Thu, 12 Sep 2002 15:02:56 -0400 (EDT)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by dyn-tx-app-007.dfw.dynamicsoft.com (8.11.6/8.11.6) with ESMTP id g8CDEq121340
	for <sip@ietf.org>; Thu, 12 Sep 2002 08:14:52 -0500
From: Robert Sparks <rsparks@dynamicsoft.com>
To: sip@ietf.org
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) 
Date: 12 Sep 2002 14:00:33 -0500
Message-Id: <1031857233.1586.62.camel@dhcp116.dfw.dynamicsoft.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [Sip] SIP working group bugzilla instance
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Folks -

For some time, we've been using bugzilla to track open-issues and
document errors for rfc2542bis/rfc3261 and a few other documents.
It has proven to be an extremely effective tool for the document
editors.

We think it will make a good reference tool for the working group
as a whole, so we're making it generally available for query and
browsing. You won't be able to enter bugs or comments unless you
are the editor for the document that's being tracked - we need to
keep the discussion on this mailing list. You will be able to search
for open issues (all bugs representing an open issue are tagged with
the keyword "OPEN-ISSUE"), and track the resolution of reported
errors.

The interface is at http://www.sipwg.org

It has lots of online help, but if you need more, see
http://www.bugzilla.org/

Enjoy!
RjS

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



From mailnull@www1.ietf.org  Thu Sep 12 15:07:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04025
	for <sip-archive@odin.ietf.org>; Thu, 12 Sep 2002 15:07:48 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8CJ94v25027
	for sip-archive@odin.ietf.org; Thu, 12 Sep 2002 15:09:04 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CJ8Jv24993;
	Thu, 12 Sep 2002 15:08:19 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CJ65v24279
	for <sip@optimus.ietf.org>; Thu, 12 Sep 2002 15:06:05 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03822
	for <sip@ietf.org>; Thu, 12 Sep 2002 15:04:19 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.76])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g8CIgnYH021896;
	Thu, 12 Sep 2002 14:42:52 -0400 (EDT)
Message-ID: <3D80E028.20707@dynamicsoft.com>
Date: Thu, 12 Sep 2002 14:42:48 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Manuel_Moreno_Mart=EDn?= <mmoreno@cipres.upm.es>
CC: Sip <sip@ietf.org>
Subject: Re: [Sip] Over SIP Timer
References: <NFBBLGNBALMEBCOCNPCCMEPDCEAA.mmoreno@cipres.upm.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

inline.

Manuel Moreno Martín wrote:
> Hi
> 
> Are the SIP timer B,

According to 17.1.1.2:

  For
    any transport, the client transaction MUST start timer B with a value
    of 64*T1 seconds (Timer B controls transaction timeouts).

So, yes.




> F

Yes.



  and T4 necessary with reliable transports (TCP,
> SCTP)???

T4 is not a timer, its a constant. Timer K is set to zero for reliable 
transports, T4 for unreliable.

B and F still need to be set, because even though a TCP connection is up 
to the downstream element, it doesn't mean it is sufficiently alive to 
generate a response.

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Thu Sep 12 15:09:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04082
	for <sip-archive@odin.ietf.org>; Thu, 12 Sep 2002 15:09:58 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8CJBEX25106
	for sip-archive@odin.ietf.org; Thu, 12 Sep 2002 15:11:14 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CJ7Tv24845;
	Thu, 12 Sep 2002 15:07:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CJ4Iv24230
	for <sip@optimus.ietf.org>; Thu, 12 Sep 2002 15:04:18 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03747
	for <sip@ietf.org>; Thu, 12 Sep 2002 15:02:31 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.76])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g8CJ3JYH021925;
	Thu, 12 Sep 2002 15:03:20 -0400 (EDT)
Message-ID: <3D80E4F7.3090805@dynamicsoft.com>
Date: Thu, 12 Sep 2002 15:03:19 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jasson Casey <jasson@netrake.com>
CC: Steve Silverman <steves@shentel.net>, chris@infravast.com,
        Dean Willis <dwillis@dynamicsoft.com>, sip@ietf.org, rohan@cisco.com,
        jo@ipdialog.com, brian.rosen@marconi.com
Subject: Re: [Sip] WGLC for draft-ietf-sip-nat
References: <7E06D3212981524CA10D2A114937C41447B894@NREXCH.netrake.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit



Jasson Casey wrote:
 > I've got a quick question. Timer C >= 180s. When timer c fires a
 > couple things should happen to expire the transaction or keep it
 > going. How does having a minimum value of 180s allow the provisional
 > responses to keep the binding alive through a NAT if we're talking
 > about NAT expirations ~ 30s?
 >
 > I just didn't understand the sentence 'The provisional response sent
 > by the UAS, in order to keep timer C going, will maintain the
 > bindings.'
 >

My comment below refers to the TCP case. TCP bindings expire too if 
there is no TCP keepalive or traffic on the connection. That expiration 
is usually many minutes, 10-30 it seems. So, a message every 3m will 
keep it alive if the TCP keepalive isn't doing so.


-Jonathan R.

 > -----Original Message----- From: Jonathan Rosenberg
 > [mailto:jdrosen@dynamicsoft.com] Sent: Mon 9/9/2002 10:46 PM To:
 > Steve Silverman Cc: chris@infravast.com; Dean Willis; sip@ietf.org;
 > rohan@cisco.com; jo@ipdialog.com; brian.rosen@marconi.com Subject:
 > Re: [Sip] WGLC for draft-ietf-sip-nat
 >
 >
 >
 > Steve Silverman wrote: > If the system can not complete a phone call
 > in less than one minute, the > caller will have hung up long ago.
 > When you dial a call today, how long > will you wait for the called
 > party?  In most parts of the world, about 10 > seconds is  the limit
 > and then the caller hangs up and tries again.  Great, and that case
 > works.  However, we have sevearl other cases of concern. The most
 > irritating of these is the case where a UAS is a gateway that
 > connects to an 800 number system that actually never generates an
 > ACM. Rather, it uses the reverse media path to prompt the user that
 > they are in a queue. Once the user is out of the queue, the call is
 > actually answered. As a result of this, the call can "ring" for
 > minutes, perhaps even hours. To keep the binding alive to receive the
 > SIP response is this case, the client will need to retransmit the
 > INVITE every 30s or so. Of course, TCP is better here, and won't
 > require any retransmits. The provisional response sent by the UAS, in
 > order to keep timer C going, will maintain the bindings.  However,
 > the main feature provided by this specification, rport, ensures that
 > the response, whether generated immediately or later on, is received
 > by the UAC behind the NAT.  -Jonathan R.   -- Jonathan D. Rosenberg,
 > Ph.D.                72 Eagle Rock Ave. Chief Scientist
 > First Floor dynamicsoft                                 East Hanover,
 > NJ 07936 jdrosen@dynamicsoft.com                     FAX:   (973)
 > 952-5050 http://www.jdrosen.net                      PHONE: (973)
 > 952-5000 http://www.dynamicsoft.com
 > _______________________________________________ Sip mailing list
 > https://www1.ietf.org/mailman/listinfo/sip This list is for NEW
 > development of the core SIP Protocol Use
 > sip-implementors@cs.columbia.edu for questions on current sip Use
 > sipping@ietf.org for new developments on the application of sip
 >

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Fri Sep 13 13:10:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12510
	for <sip-archive@odin.ietf.org>; Fri, 13 Sep 2002 13:10:51 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8DHC7B04380
	for sip-archive@odin.ietf.org; Fri, 13 Sep 2002 13:12:07 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8DHAlv04318;
	Fri, 13 Sep 2002 13:10:47 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8DG3Ev31868
	for <sip@optimus.ietf.org>; Fri, 13 Sep 2002 12:03:14 -0400
Received: from zmamail05.zma.compaq.com (zmamail05.zma.compaq.com [161.114.64.105])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10274
	for <sip@ietf.org>; Fri, 13 Sep 2002 12:01:28 -0400 (EDT)
Received: from demexg11.emea.cpqcorp.net (demexg11.emea.cpqcorp.net [16.41.94.66])
	by zmamail05.zma.compaq.com (Postfix) with ESMTP id 4277C3538
	for <sip@ietf.org>; Fri, 13 Sep 2002 12:03:10 -0400 (EDT)
Received: from vbeexc02.emea.cpqcorp.net ([16.188.146.229]) by demexg11.emea.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Fri, 13 Sep 2002 18:03:02 +0200
x-mimeole: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Fri, 13 Sep 2002 18:03:01 +0200
Message-ID: <06CAA4D3753C53408D2CE6340B684442D77AD3@vbeexc02.emea.cpqcorp.net>
Thread-Topic: INVITEs and re-INVITEs
Thread-Index: AcJbPwk45uzJ0kurSi63YmmvyTwRxQ==
From: "Nikichine, Alexis" <alexis.nikichine@hp.com>
To: <sip@ietf.org>
X-OriginalArrivalTime: 13 Sep 2002 16:03:02.0677 (UTC) FILETIME=[09E38C50:01C25B3F]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g8DG3Ev31869
Subject: [Sip] INVITEs and re-INVITEs
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

Hello,

RFC 3261 says, in session 14.2 

"Section 13.3.1 describes the procedure for distinguishing incoming re-INVITEs from incoming initial INVITEs "

but all I can read in section 13.3.1 on that topic is

"If the request is a mid-dialog request, the method-independent processing described in Section 12.2.2 is first applied."

Now I wonder if there is a way to statelessly distinguish a INVITE from a re-INVITE ?

Any answer appreciated,

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



From mailnull@www1.ietf.org  Fri Sep 13 14:29:21 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14990
	for <sip-archive@odin.ietf.org>; Fri, 13 Sep 2002 14:29:21 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8DIUdp08699
	for sip-archive@odin.ietf.org; Fri, 13 Sep 2002 14:30:39 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8DIU7v08676;
	Fri, 13 Sep 2002 14:30:07 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8DIQKv08556
	for <sip@optimus.ietf.org>; Fri, 13 Sep 2002 14:26:20 -0400
Received: from sj_ntserver3.sj.nuera.com (h-207-20-110-62.ncal.verio.net [207.20.110.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14856
	for <sip@ietf.org>; Fri, 13 Sep 2002 14:24:32 -0400 (EDT)
Received: by sj_ntserver3.sj.nuera.com with Internet Mail Service (5.5.2653.19)
	id <SWLZCNLX>; Fri, 13 Sep 2002 11:27:06 -0700
Message-ID: <DD70FD1C981BD411B64400508BA547C15B42FA@sj_ntserver3.sj.nuera.com>
From: "Srivastava, Samir" <SSrivastava@nuera.com>
To: "'Nikichine, Alexis'" <alexis.nikichine@hp.com>, sip@ietf.org
Subject: RE: [Sip] INVITEs and re-INVITEs
Date: Fri, 13 Sep 2002 11:26:58 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

Hi,

INVITE will not have to Tag. re-INVITE MUST have the to tag. 

This applies if UA's are RFC 3261 compliant, not the old ones.

Thx
Samir

-----Original Message-----
From: Nikichine, Alexis [mailto:alexis.nikichine@hp.com]
Sent: Friday, September 13, 2002 9:03 AM
To: sip@ietf.org
Subject: [Sip] INVITEs and re-INVITEs


Hello,

RFC 3261 says, in session 14.2 

"Section 13.3.1 describes the procedure for distinguishing incoming
re-INVITEs from incoming initial INVITEs "

but all I can read in section 13.3.1 on that topic is

"If the request is a mid-dialog request, the method-independent processing
described in Section 12.2.2 is first applied."

Now I wonder if there is a way to statelessly distinguish a INVITE from a
re-INVITE ?

Any answer appreciated,

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



From mailnull@www1.ietf.org  Sat Sep 14 19:37:11 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16650
	for <sip-archive@odin.ietf.org>; Sat, 14 Sep 2002 19:37:11 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8ENcV121074
	for sip-archive@odin.ietf.org; Sat, 14 Sep 2002 19:38:31 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8ENbZv21051;
	Sat, 14 Sep 2002 19:37:35 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8ENU9v20428
	for <sip@optimus.ietf.org>; Sat, 14 Sep 2002 19:30:09 -0400
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16578
	for <sip@ietf.org>; Sat, 14 Sep 2002 19:28:19 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8ENTPKB011962;
	Sat, 14 Sep 2002 16:29:25 -0700 (PDT)
Received: from open-131-161-248-87.cliq.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.1.0.54-GA)
	with ESMTP id AAV89446;
	Sat, 14 Sep 2002 16:27:44 -0700 (PDT)
Date: Sat, 14 Sep 2002 16:30:26 -0700
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v482)
Cc: rohan@cisco.com, bcampbell@dynamicsoft.com, mankin@psg.com
To: sip@ietf.org
From: Rohan Mahy <rohan@cisco.com>
Content-Transfer-Encoding: 7bit
Message-Id: <F28C5ED6-C839-11D6-A5C1-0003938AF740@cisco.com>
X-Mailer: Apple Mail (2.482)
Content-Transfer-Encoding: 7bit
Subject: [Sip] heads up: status of MESSAGE method draft
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Folks,

I wanted to give everyone a quick heads up on the MESSAGE draft.

In response to IESG requested changes, Ben just submitted version -07 of 
draft-ietf-sip-message. In general, the IESG response to the draft was 
very good. Most of the requested changes were very minor. The only real 
significant change, was to make implementation of SMIME a MUST to allow 
folks to have end-to-end protection of their messages.  Note that this 
does not require folks to always *use* SMIME, just that it needs to be 
available in implementations.  This is following a general policy of the 
the Security Area (with the blessing of the IESG and IAB) that newly 
standardized protocols, or newly standardized usages of protocols, need 
end-to-end security. I'm sure the IESG will require the same thing of 
the Jabber community for XMPP as they did for us, and as they required 
of the BEEP community for APEX.

Now before anyone complains, I would like to remind you all that it is 
extremely unlikely that we could get MESSAGE approved without some 
end-to-end security mechanism. Feel free to bring the issue up on the 
saag list or in Atlanta if you feel strongly that the Security Area is 
out of line.

Once the new draft appears in the archives, I expect that the IESG will 
approve MESSAGE shortly.

thanks,
-rohan

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



From mailnull@www1.ietf.org  Mon Sep 16 07:54:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01093
	for <sip-archive@odin.ietf.org>; Mon, 16 Sep 2002 07:54:54 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8GBuAg25445
	for sip-archive@odin.ietf.org; Mon, 16 Sep 2002 07:56:10 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8GBs8v25365;
	Mon, 16 Sep 2002 07:54:08 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8GBmOv25152
	for <sip@optimus.ietf.org>; Mon, 16 Sep 2002 07:48:24 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00777;
	Mon, 16 Sep 2002 07:46:29 -0400 (EDT)
Message-Id: <200209161146.HAA00777@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: mmusic@ietf.org, sip@ietf.org, sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 16 Sep 2002 07:46:28 -0400
Subject: [Sip] I-D ACTION:draft-camarillo-mmusic-source-sink-00.txt
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: The source and sink attributes for the Session 
                          Description Protocol
	Author(s)	: G. Camarillo, H. Schulzrinne, E. Burger
	Filename	: draft-camarillo-mmusic-source-sink-00.txt
	Pages		: 7
	Date		: 2002-9-13
	
This document defines two media level SDP attributes, namely source
and sink. They are intended to be used to invoke services that
involve media manipulation, such as transcoding services.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-camarillo-mmusic-source-sink-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-camarillo-mmusic-source-sink-00.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-camarillo-mmusic-source-sink-00.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2002-9-13143711.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-camarillo-mmusic-source-sink-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-camarillo-mmusic-source-sink-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-9-13143711.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From mailnull@www1.ietf.org  Mon Sep 16 07:56:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01167
	for <sip-archive@odin.ietf.org>; Mon, 16 Sep 2002 07:56:00 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8GBvGU25579
	for sip-archive@odin.ietf.org; Mon, 16 Sep 2002 07:57:16 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8GBv0v25513;
	Mon, 16 Sep 2002 07:57:00 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8GBmev25167
	for <sip@optimus.ietf.org>; Mon, 16 Sep 2002 07:48:40 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00864;
	Mon, 16 Sep 2002 07:46:53 -0400 (EDT)
Message-Id: <200209161146.HAA00864@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sip@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 16 Sep 2002 07:46:52 -0400
Subject: [Sip] I-D ACTION:draft-ietf-sip-sipfrag-00.txt
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: Internet Media Type message/sipfrag
	Author(s)	: R. Sparks
	Filename	: draft-ietf-sip-sipfrag-00.txt
	Pages		: 9
	Date		: 2002-9-13
	
This document registers the message/sipfrag MIME media type.  This
type is similar to message/sip , but allows certain subsets of well
formed SIP messages to be represented instead of requiring a complete
SIP message.  In addition to end-to-end security uses, message/
sipfrag is used with the REFER method to convey information about the
status of a referenced request

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-sipfrag-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sip-sipfrag-00.txt".

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


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

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

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2002-9-13143758.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sip-sipfrag-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sip-sipfrag-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-9-13143758.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From mailnull@www1.ietf.org  Mon Sep 16 10:29:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06456
	for <sip-archive@odin.ietf.org>; Mon, 16 Sep 2002 10:29:42 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8GEV0f02245
	for sip-archive@odin.ietf.org; Mon, 16 Sep 2002 10:31:00 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8GEUYv02215;
	Mon, 16 Sep 2002 10:30:34 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8GERpv02102
	for <sip@optimus.ietf.org>; Mon, 16 Sep 2002 10:27:51 -0400
Received: from dyn-tx-app-007.dfw.dynamicsoft.com ([63.110.3.105])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06338
	for <sip@ietf.org>; Mon, 16 Sep 2002 10:26:03 -0400 (EDT)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by dyn-tx-app-007.dfw.dynamicsoft.com (8.11.6/8.11.6) with ESMTP id g8G8c9102076
	for <sip@ietf.org>; Mon, 16 Sep 2002 03:38:09 -0500
Subject: Re: [Sip] I-D ACTION:draft-ietf-sip-sipfrag-00.txt
From: Robert Sparks <rsparks@dynamicsoft.com>
To: sip@ietf.org
In-Reply-To: <200209161146.HAA00864@ietf.org>
References: <200209161146.HAA00864@ietf.org>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) 
Date: 16 Sep 2002 09:26:49 -0500
Message-Id: <1032186409.10822.12.camel@dhcp151.dfw.dynamicsoft.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

This draft replaces draft-sparks-sip-mimetypes-03, and incorporates 
review comments from the IESG.

The syntax has not changed. The draft now contains examples of sipfrag
mime parts and discussion of their use. In particular, the security
section has been fleshed out and now requires extensions that use REFER
to explicitly discuss certain attacks. 

This is ready for approval. However, enough words changed during this
review phase that its appropriate for the working group to give it a
quick inspection before moving forward. Please look it over and comment
quickly. This draft is holding up a train of others.

RjS

On Mon, 2002-09-16 at 06:46, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Session Initiation Protocol Working Group of the IETF.
> 
> 	Title		: Internet Media Type message/sipfrag
> 	Author(s)	: R. Sparks
> 	Filename	: draft-ietf-sip-sipfrag-00.txt
> 	Pages		: 9
> 	Date		: 2002-9-13
> 	
> This document registers the message/sipfrag MIME media type.  This
> type is similar to message/sip , but allows certain subsets of well
> formed SIP messages to be represented instead of requiring a complete
> SIP message.  In addition to end-to-end security uses, message/
> sipfrag is used with the REFER method to convey information about the
> status of a referenced request
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sip-sipfrag-00.txt
> 
> To remove yourself from the IETF Announcement list, send a message to 
> ietf-announce-request with the word unsubscribe in the body of the message.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-sip-sipfrag-00.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-sip-sipfrag-00.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.
> 


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



From mailnull@www1.ietf.org  Tue Sep 17 04:43:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07746
	for <sip-archive@odin.ietf.org>; Tue, 17 Sep 2002 04:43:58 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8H8jPb32073
	for sip-archive@odin.ietf.org; Tue, 17 Sep 2002 04:45:25 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8H8gMv31935;
	Tue, 17 Sep 2002 04:42:22 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8H8c6v31759
	for <sip@optimus.ietf.org>; Tue, 17 Sep 2002 04:38:06 -0400
Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07655;
	Tue, 17 Sep 2002 04:36:04 -0400 (EDT)
Received: from m7.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0205-Fujitsu Gateway)
	id RAA06601; Tue, 17 Sep 2002 17:37:18 +0900 (JST)
	(envelope-from shingo_fujimoto@jp.fujitsu.com)
Received: from dm.akashi.flab.fujitsu.co.jp by m7.gw.fujitsu.co.jp (8.9.3/3.7W-0208-Fujitsu Domain Master)
	id RAA23836; Tue, 17 Sep 2002 17:37:16 +0900
	(envelope-from shingo_fujimoto@jp.fujitsu.com)
Received: from dm.akashi.flab.fujitsu.co.jp by dm.akashi.flab.fujitsu.co.jp (8.9.3/3.7W-020129-Fujitsu Labs. Akashi Domain Mail Master)
	id RAA17732; Tue, 17 Sep 2002 17:37:16 +0900 (JST)
Received: from kmailserv.akashi.flab.fujitsu.co.jp ([10.254.200.15])
 by dm.akashi.flab.fujitsu.co.jp (NAVGW 2.5.2.9) with SMTP id M2002091717371617556
 ; Tue, 17 Sep 2002 17:37:16 +0900
Received: from jp.fujitsu.com (suzume.pssys.flab.fujitsu.co.jp [10.254.215.64])
	by kmailserv.akashi.flab.fujitsu.co.jp (8.8.8+Sun/8.8.8) with ESMTP id RAA14859;
	Tue, 17 Sep 2002 17:37:15 +0900 (JST)
Message-ID: <3D86E9DD.7030109@jp.fujitsu.com>
Date: Tue, 17 Sep 2002 17:37:49 +0900
From: Shingo Fujimoto <shingo_fujimoto@jp.fujitsu.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; ja-JP; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: ja,en-US,en
MIME-Version: 1.0
To: Adam Roach <adam@dynamicsoft.com>
CC: sipping-WG <sipping@ietf.org>, SIP-WG <sip@ietf.org>
References: <9BF66EBF6BEFD942915B4D4D45C051F3A6412D@DYN-TX-EXCH-001.dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sip] Re: [Sipping] I-D ACTION:draft-fujimoto-sipping-header-lang-00.tx
 t
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Thank you for your comments.

My comments are inline.

Adam Roach wrote:
> It's a bit odd to have the requirements and the solution specified
> in the same document; you might want to split them out into separate
> documents. I suspect you will be able to get consensus on the
> requirements faster than the mechanism. Also, as a minor procedural
> point, if this work is put on the charters, I think the requirements
> will be specified in SIPPING, and the mechanism will be specified
> in SIP.

Your are right. When the I-D is updated they will be two documents 
(requirements, and proposal).

Since I am kind of new comer in SIP community, I am not sure which 
WG should handle these problem.

> Speaking to the mechanism, the current draft has the following
> text, which acknowledges but rejects Unicode language tags:
> 
>     UTF-8 allows to represent any UCS-2/4 characters, including recent 
>     proposed "language tag" which used to specifying the languages 
>     information for following character strings. However, the deployed 
>     SIP implementations may not have enough knowledge to handle them 
>     correctly.  
> 
> Your assertion that most (if not all) deployed SIP implementations
> don't support Unicode language tagging is almost certainly correct;
> however, since *no* existing SIP implementations support the mechanism
> proposed in your draft, it seems to be a wash. In other words,
> this argument provides no motivation for discarding Unicode language
> tagging.

I think major differece between "language tag" and my proposal is 
ease of ignorance. The inline language tag is hard to separate the 
language tagging and other parts.

I cannot provide enough evidence about this statement, but here is 
the 3rd party article which described why "language tag" is 
discourged in most cases.

http://xml.coverpages.org/languageIdentifiers.html#unicode

> I invite members of the SIP community to chime in with their opinion
> on this topic. As I see it, the primary differences involved are:
> 
> - Selecting Unicode language tags would be more standard, inasmuch
>   as the representation of languages in this fashion is likely
>   to see far wider deployment than any SIP-specific solution. So,
>   for example, if the receiving UA uses Unicode libraries that
>   inherently understand language tags, it makes implementation much
>   simpler.
> 
> - Shingo Fujimoto's proposal is more space efficient. For example,
>   to encode a set of ISO639/ISO3166 (language, country) codes into
>   a header takes only 9 additional octets, instead of the 24 that
>   UTF-8 encoding of language tags would; encoding just the language
>   takes 6 additional octets instead of 12.

I hope SIP-WG will also pay attension to my proposal.

The URL for my I-D is:
http://www.ietf.org/internet-drafts/draft-fujimoto-sipping-header-lang-00.txt

Best.
-- 
======================================
          SHINGO FUJIMOTO
     FUJITSU LABORATORIES LIMITED
E-mail: shingo_fujimoto@jp.fujitsu.com


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



From mailnull@www1.ietf.org  Tue Sep 17 07:17:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10310
	for <sip-archive@odin.ietf.org>; Tue, 17 Sep 2002 07:17:12 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8HBIRC07023
	for sip-archive@odin.ietf.org; Tue, 17 Sep 2002 07:18:27 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HBHvv06994;
	Tue, 17 Sep 2002 07:17:57 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HBGdv06947
	for <sip@optimus.ietf.org>; Tue, 17 Sep 2002 07:16:39 -0400
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10284
	for <sip@ietf.org>; Tue, 17 Sep 2002 07:14:50 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g8HBGarU005123
	for <sip@ietf.org>; Tue, 17 Sep 2002 13:16:36 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.22])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g8HBGaG3022754
	for <sip@ietf.org>; Tue, 17 Sep 2002 14:16:36 +0300 (EET DST)
Message-ID: <3D870F16.D1840CED@lmf.ericsson.se>
Date: Tue, 17 Sep 2002 14:16:38 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: sip@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sip] TEL-URL questions
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


Hi,

A couple of questions related to TEL-URL use in SIP:


Q1.

When SIP-URI is used, if we include any uri-parameters we MUST put
brackets around the uri.

example:

To: <sip:12345;user=ip>

Also, I assume that the same applies for TEL-URL, ie if any tel-url
parameters are present brackets must also be used.

example:

To: <tel:12345;param=value>

Now, the TEL-URL also defines "isdn-subaddress" and "phone-context".
They are not defined as parameters, but as optional parts of the number
itself, even if they "look" like parameters from a SIP point of view
(since they are separated by ";"), so I would like to clarify if
brackets still must be used with those (otherwise the SIP parser will
treat them as header parameters), even if they are not defined as uri
parameters.

example:

To: <tel:12345;phone-context=123>

...instead of...

To: tel:12345;phone-context=123


Q2:

Which of the SIP-URI parameters (transport, ttl, user, method and maddr)
are valid also for TEL-URL? They are allowed from a ABNF point of view
(as tel url parameters), but I would like to clarify if they (or, at
least parts of them) shall be treated in the same way as if they are
received in a SIP-URL.


Regards,

Christer Holmberg
Ericsson Finland

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



From mailnull@www1.ietf.org  Tue Sep 17 08:05:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11537
	for <sip-archive@odin.ietf.org>; Tue, 17 Sep 2002 08:05:35 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8HC6p909218
	for sip-archive@odin.ietf.org; Tue, 17 Sep 2002 08:06:51 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HC4Yv09126;
	Tue, 17 Sep 2002 08:04:34 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HC2Mv09058
	for <sip@optimus.ietf.org>; Tue, 17 Sep 2002 08:02:22 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11334;
	Tue, 17 Sep 2002 08:00:31 -0400 (EDT)
Message-Id: <200209171200.IAA11334@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sip@ietf.org, simple@mailman.dynamicsoft.com
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 17 Sep 2002 08:00:31 -0400
Subject: [Sip] I-D ACTION:draft-ietf-sip-message-07.txt
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: Session Initiation Protocol Extension for Instant 
                          Messaging
	Author(s)	: B. Campbell, J. Rosenberg
	Filename	: draft-ietf-sip-message-07.txt
	Pages		: 22
	Date		: 2002-9-16
	
Instant Messageing (IM) refers to the transfer of messages between
users in near real-time.  These messages are usually, but not
required to be, short.  IMs are often used in a conversational mode,
that is, the transfer of messages back and forth is fast enough for
participants to maintain an interactive conversation.
The MESSAGE method is an extension to the Session Initation Protocol
(SIP) that allows the transfer of Instant Messages.  MESSAGE requests
carry the content in the form of MIME body parts.  MESSAGE requests
do not themselves initiate a SIP dialog; under normal usage each
Instant Message stands alone, much like pager messages.  MESSAGE
requests may be sent in the context of a dialog initiated by some
other SIP request.
Since the MESSAGE request is an extension to SIP it inherits all the
request routing and security features of that protocol.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-message-07.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sip-message-07.txt".

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


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

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

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2002-9-16152033.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sip-message-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sip-message-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-9-16152033.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From mailnull@www1.ietf.org  Tue Sep 17 09:27:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14208
	for <sip-archive@odin.ietf.org>; Tue, 17 Sep 2002 09:27:54 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8HDTCs13708
	for sip-archive@odin.ietf.org; Tue, 17 Sep 2002 09:29:12 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HDR1v13616;
	Tue, 17 Sep 2002 09:27:01 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HDObv13542
	for <sip@optimus.ietf.org>; Tue, 17 Sep 2002 09:24:37 -0400
Received: from nt-mail.radvision.com ([212.143.185.30])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14060
	for <sip@ietf.org>; Tue, 17 Sep 2002 09:22:48 -0400 (EDT)
Received: by nt-mail.tlv.radvision.com with Internet Mail Service (5.5.2650.21)
	id <S5HZCTL3>; Tue, 17 Sep 2002 16:22:35 +0300
Message-ID: <EE5AF23B5764D511A6B900508BB82A0B02E5F013@nt-mail.tlv.radvision.com>
From: Sarit Galanos Mekler <Sarit@radvision.com>
To: sip@ietf.org
Date: Tue, 17 Sep 2002 16:22:34 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="windows-1255"
Subject: [Sip] Handling UNSUBSCRIBE before Subscription is completed
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

Hello,

draft-ietf-sip-events does not specify how a server should handle an
UNSUBSCRIBE request that
is received before the SUBSCRIBE process was completed.


In other words, If the server receives a SUBSCRIBE request and before it
responds with a final response
an UNSUBSCRIBE is received for the same dialog. 

Should the server reject the UNSUBSCRIBE?


Regards,
Sarit Galanos.













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



From mailnull@www1.ietf.org  Tue Sep 17 10:14:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15848
	for <sip-archive@odin.ietf.org>; Tue, 17 Sep 2002 10:14:43 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8HEG1816569
	for sip-archive@odin.ietf.org; Tue, 17 Sep 2002 10:16:01 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HEFcv16551;
	Tue, 17 Sep 2002 10:15:38 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HEEjv16506
	for <sip@optimus.ietf.org>; Tue, 17 Sep 2002 10:14:45 -0400
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15645
	for <sip@ietf.org>; Tue, 17 Sep 2002 10:12:56 -0400 (EDT)
Received: from blues.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.227])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id QAA03415;
	Tue, 17 Sep 2002 16:14:39 +0200 (MET DST)
Received: from mchh168e.mch4.siemens.de ([139.21.130.175])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id QAA02053;
	Tue, 17 Sep 2002 16:14:40 +0200 (MET DST)
Received: by mchh168e.mch4.siemens.de with Internet Mail Service (5.5.2653.19)
	id <S54LZFQX>; Tue, 17 Sep 2002 16:14:42 +0200
Message-ID: <5B4D0C5BA65ECA46969C1419122317E6E74F39@mchh161e>
From: Tan Ya-Ching  ICM N PG U ID A 1 <Ya-Ching.Tan@icn.siemens.de>
To: "'Sarit Galanos Mekler'" <Sarit@radvision.com>, sip@ietf.org
Subject: RE: [Sip] Handling UNSUBSCRIBE before Subscription is completed
Date: Tue, 17 Sep 2002 16:14:24 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="windows-1255"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>


| In other words, If the server receives a SUBSCRIBE request 
| and before it responds with a final response
| an UNSUBSCRIBE is received for the same dialog. 

RFC 3265 does not expect provisional response for SUBSCRIBE, so before the
notifier responds with a final response, there is no dialog created yet and
no unSUBSCRIBE can possibly be received for the same dialog.

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



From mailnull@www1.ietf.org  Tue Sep 17 10:37:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17066
	for <sip-archive@odin.ietf.org>; Tue, 17 Sep 2002 10:37:20 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8HEcci18173
	for sip-archive@odin.ietf.org; Tue, 17 Sep 2002 10:38:38 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HEcGv18162;
	Tue, 17 Sep 2002 10:38:16 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HEY9v17470
	for <sip@optimus.ietf.org>; Tue, 17 Sep 2002 10:34:09 -0400
Received: from cozumel.we-host.com (cozumel.we-host.com.47.37.216.in-addr.arpa [216.37.47.200] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA16907
	for <sip@ietf.org>; Tue, 17 Sep 2002 10:32:20 -0400 (EDT)
Received: (qmail 20787 invoked from network); 17 Sep 2002 14:07:45 -0000
Received: from adsl-65-71-246-65.dsl.rcsntx.swbell.net (HELO StephenJames) (65.71.246.65)
  by cozumel.we-host.com.47.37.216.in-addr.arpa with SMTP; 17 Sep 2002 14:07:45 -0000
Message-ID: <002c01c25e57$25e9cc00$6579a8c0@StephenJames>
From: "Stephen James" <sjames@voiceramp.com>
To: <sip@ietf.org>
References: <3D870F16.D1840CED@lmf.ericsson.se>
Subject: Re: [Sip] TEL-URL questions
Date: Tue, 17 Sep 2002 09:32:40 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

According to RFC 3261, 20.20.

"... the "name-addr" form MUST be used if the "addr-spec" contains
 a comma, question mark, or semicolon."

That says to me if the "isdn-subaddress" and "phone-context"
are part of the URL then the "name-addr" form MUST be used.

> Q1.
> 
> When SIP-URI is used, if we include any uri-parameters we MUST put
> brackets around the uri.
> 
> 
> To: <tel:12345;param=value>
> 
> Now, the TEL-URL also defines "isdn-subaddress" and "phone-context".
> They are not defined as parameters, but as optional parts of the number
> itself, even if they "look" like parameters from a SIP point of view
> (since they are separated by ";"), so I would like to clarify if
> brackets still must be used with those (otherwise the SIP parser will
> treat them as header parameters), even if they are not defined as uri
> parameters.
> 

Don't know the answer for Q2.


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



From mailnull@www1.ietf.org  Tue Sep 17 10:53:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17604
	for <sip-archive@odin.ietf.org>; Tue, 17 Sep 2002 10:53:56 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8HEtFn18870
	for sip-archive@odin.ietf.org; Tue, 17 Sep 2002 10:55:15 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HErXv18790;
	Tue, 17 Sep 2002 10:53:33 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HEquv18721
	for <sip@optimus.ietf.org>; Tue, 17 Sep 2002 10:52:56 -0400
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17530
	for <sip@ietf.org>; Tue, 17 Sep 2002 10:51:06 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g8HEqprU019929;
	Tue, 17 Sep 2002 16:52:51 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.22])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g8HEqpG3012904;
	Tue, 17 Sep 2002 17:52:51 +0300 (EET DST)
Message-ID: <3D8741C5.8B06C4C3@lmf.ericsson.se>
Date: Tue, 17 Sep 2002 17:52:53 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Stephen James <sjames@voiceramp.com>
CC: sip@ietf.org
Subject: Re: [Sip] TEL-URL questions
References: <3D870F16.D1840CED@lmf.ericsson.se> <002c01c25e57$25e9cc00$6579a8c0@StephenJames>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


Hi

> "... the "name-addr" form MUST be used if the "addr-spec" contains
>  a comma, question mark, or semicolon."

>
> That says to me if the "isdn-subaddress" and "phone-context"
> are part of the URL then the "name-addr" form MUST be used.

True. Thanks!

Christer Holmberg
Ericsson Finland






>
>
> > Q1.
> >
> > When SIP-URI is used, if we include any uri-parameters we MUST put
> > brackets around the uri.
> >
> >
> > To: <tel:12345;param=value>
> >
> > Now, the TEL-URL also defines "isdn-subaddress" and "phone-context".
> > They are not defined as parameters, but as optional parts of the number
> > itself, even if they "look" like parameters from a SIP point of view
> > (since they are separated by ";"), so I would like to clarify if
> > brackets still must be used with those (otherwise the SIP parser will
> > treat them as header parameters), even if they are not defined as uri
> > parameters.
> >
>
> Don't know the answer for Q2.
>
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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



From mailnull@www1.ietf.org  Tue Sep 17 14:35:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25414
	for <sip-archive@odin.ietf.org>; Tue, 17 Sep 2002 14:35:38 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8HIav232252
	for sip-archive@odin.ietf.org; Tue, 17 Sep 2002 14:36:57 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HIZWv32220;
	Tue, 17 Sep 2002 14:35:32 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8HIXQv32162
	for <sip@optimus.ietf.org>; Tue, 17 Sep 2002 14:33:26 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25285
	for <sip@ietf.org>; Tue, 17 Sep 2002 14:31:36 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.12])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g8HIWnYH025009;
	Tue, 17 Sep 2002 14:32:49 -0400 (EDT)
Message-ID: <3D877550.4060906@dynamicsoft.com>
Date: Tue, 17 Sep 2002 14:32:48 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
CC: Stephen James <sjames@voiceramp.com>, sip@ietf.org
Subject: Re: [Sip] TEL-URL questions
References: <3D870F16.D1840CED@lmf.ericsson.se> <002c01c25e57$25e9cc00$6579a8c0@StephenJames> <3D8741C5.8B06C4C3@lmf.ericsson.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Please take a look at 19.1.6 of RFC 3261. It describes how tel URIs are 
mapped into SIP URIs. Note that the tel URI parameters appear in the 
user part of the SIP URL.

-Jonathan R.

Christer Holmberg wrote:
> Hi
> 
> 
>>"... the "name-addr" form MUST be used if the "addr-spec" contains
>> a comma, question mark, or semicolon."
> 
> 
>>That says to me if the "isdn-subaddress" and "phone-context"
>>are part of the URL then the "name-addr" form MUST be used.
> 
> 
> True. Thanks!
> 
> Christer Holmberg
> Ericsson Finland
> 
> 
> 
> 
> 
> 
> 
>>
>>>Q1.
>>>
>>>When SIP-URI is used, if we include any uri-parameters we MUST put
>>>brackets around the uri.
>>>
>>>
>>>To: <tel:12345;param=value>
>>>
>>>Now, the TEL-URL also defines "isdn-subaddress" and "phone-context".
>>>They are not defined as parameters, but as optional parts of the number
>>>itself, even if they "look" like parameters from a SIP point of view
>>>(since they are separated by ";"), so I would like to clarify if
>>>brackets still must be used with those (otherwise the SIP parser will
>>>treat them as header parameters), even if they are not defined as uri
>>>parameters.
>>>
>>
>>Don't know the answer for Q2.
>>
>>_______________________________________________
>>Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>>This list is for NEW development of the core SIP Protocol
>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>Use sipping@ietf.org for new developments on the application of sip
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Wed Sep 18 00:55:26 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09073
	for <sip-archive@odin.ietf.org>; Wed, 18 Sep 2002 00:55:26 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8I4uq631416
	for sip-archive@odin.ietf.org; Wed, 18 Sep 2002 00:56:52 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8I4uTv31395;
	Wed, 18 Sep 2002 00:56:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8I4sSv31336
	for <sip@optimus.ietf.org>; Wed, 18 Sep 2002 00:54:28 -0400
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09052
	for <sip@ietf.org>; Wed, 18 Sep 2002 00:52:31 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g8I4sCrU017066;
	Wed, 18 Sep 2002 06:54:13 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.22])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g8I4sBG3011854;
	Wed, 18 Sep 2002 07:54:12 +0300 (EET DST)
Message-ID: <3D8806F6.C604863B@lmf.ericsson.se>
Date: Wed, 18 Sep 2002 07:54:15 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: Stephen James <sjames@voiceramp.com>, sip@ietf.org
Subject: Re: [Sip] TEL-URL questions
References: <3D870F16.D1840CED@lmf.ericsson.se> <002c01c25e57$25e9cc00$6579a8c0@StephenJames> <3D8741C5.8B06C4C3@lmf.ericsson.se> <3D877550.4060906@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


Hi Jonathan,

> Please take a look at 19.1.6 of RFC 3261. It describes how tel URIs are
> mapped into SIP URIs. Note that the tel URI parameters appear in the
> user part of the SIP URL.

My issue is more related to how SIP-URI parameters are mapped into TEL-URI
parameters, and if SIP-URI parameters can be used also in TEL-URIs.

The only SIP-URI parameter 19.1.6 mentions is the user parameter, ie when a
TEL-URI parameter is mapped into a SIP-URI then user=phone.

But, what about the ttl-, method-, lr- and maddr parameters? How shall they be
handled if received within a TEL-URL? I guess some of those can't be used, and
can simply be ignored, but there may be some that should be treated the same
way as if received within a SIP-URI. Or?

Regards,

Christer Holmberg
Ericsson Finland




>
>
> -Jonathan R.
>
> Christer Holmberg wrote:
> > Hi
> >
> >
> >>"... the "name-addr" form MUST be used if the "addr-spec" contains
> >> a comma, question mark, or semicolon."
> >
> >
> >>That says to me if the "isdn-subaddress" and "phone-context"
> >>are part of the URL then the "name-addr" form MUST be used.
> >
> >
> > True. Thanks!
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> >
> >
> >
> >
> >
> >
> >>
> >>>Q1.
> >>>
> >>>When SIP-URI is used, if we include any uri-parameters we MUST put
> >>>brackets around the uri.
> >>>
> >>>
> >>>To: <tel:12345;param=value>
> >>>
> >>>Now, the TEL-URL also defines "isdn-subaddress" and "phone-context".
> >>>They are not defined as parameters, but as optional parts of the number
> >>>itself, even if they "look" like parameters from a SIP point of view
> >>>(since they are separated by ";"), so I would like to clarify if
> >>>brackets still must be used with those (otherwise the SIP parser will
> >>>treat them as header parameters), even if they are not defined as uri
> >>>parameters.
> >>>
> >>
> >>Don't know the answer for Q2.
> >>
> >>_______________________________________________
> >>Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> >>This list is for NEW development of the core SIP Protocol
> >>Use sip-implementors@cs.columbia.edu for questions on current sip
> >>Use sipping@ietf.org for new developments on the application of sip
> >
> >
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> >
>
> --
> Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
> Chief Scientist                             First Floor
> dynamicsoft                                 East Hanover, NJ 07936
> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Wed Sep 18 03:19:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04960
	for <sip-archive@odin.ietf.org>; Wed, 18 Sep 2002 03:19:49 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8I7LFf14879
	for sip-archive@odin.ietf.org; Wed, 18 Sep 2002 03:21:15 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8I7Dtv14636;
	Wed, 18 Sep 2002 03:13:55 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8I7Cqv14597
	for <sip@optimus.ietf.org>; Wed, 18 Sep 2002 03:12:52 -0400
Received: from bjapp9.163.net ([202.108.255.197])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04763
	for <sip@ietf.org>; Wed, 18 Sep 2002 03:10:53 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by bjapp9.163.net (Postfix) with SMTP id 26BCC1D0D147C
	for <sip@ietf.org>; Wed, 18 Sep 2002 15:12:35 +0800 (CST)
Received: from yangming (unknown [202.110.185.60])
	by bjapp9.163.net (Coremail) with SMTP id 8gEAAFwniD0jG7k8.3
	for <sip@ietf.org>; Wed, 18 Sep 2002 15:12:35 +0800 (CST)
Message-ID: <001501c25ee3$1e293780$7358a8c0@combrio>
From: "yangming" <cust_yangming@163.net>
To: <sip@ietf.org>
References: <20020916160002.8026.12746.Mailman@www1.ietf.org>
Date: Wed, 18 Sep 2002 15:15:02 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id g8I7Cqv14598
Subject: [Sip] help Re: Sip digest, Vol 1 #783 - 3 msgs
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit


----- Original Message ----- 
From: <sip-request@ietf.org>
To: <sip@ietf.org>
Sent: Tuesday, September 17, 2002 12:00 AM
Subject: Sip digest, Vol 1 #783 - 3 msgs


> Send Sip mailing list submissions to
> sip@ietf.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> https://www1.ietf.org/mailman/listinfo/sip
> or, via email, send a message with subject or body 'help' to
> sip-request@ietf.org
> 
> You can reach the person managing the list at
> sip-admin@ietf.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Sip digest..."
> 
> 
> Today's Topics:
> 
>    1. I-D ACTION:draft-camarillo-mmusic-source-sink-00.txt (Internet-Drafts@ietf.org)
>    2. I-D ACTION:draft-ietf-sip-sipfrag-00.txt (Internet-Drafts@ietf.org)
>    3. Re: I-D ACTION:draft-ietf-sip-sipfrag-00.txt (Robert Sparks)
> 
> --__--__--
> 
> Message: 1
> To: IETF-Announce: ;
> CC: mmusic@ietf.org, sip@ietf.org, sipping@ietf.org
> From: Internet-Drafts@ietf.org
> Reply-to: Internet-Drafts@ietf.org
> Date: Mon, 16 Sep 2002 07:46:28 -0400
> Subject: [Sip] I-D ACTION:draft-camarillo-mmusic-source-sink-00.txt
> 
> --NextPart
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
> Title : The source and sink attributes for the Session 
>                           Description Protocol
> Author(s) : G. Camarillo, H. Schulzrinne, E. Burger
> Filename : draft-camarillo-mmusic-source-sink-00.txt
> Pages : 7
> Date : 2002-9-13
> 
> This document defines two media level SDP attributes, namely source
> and sink. They are intended to be used to invoke services that
> involve media manipulation, such as transcoding services.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-camarillo-mmusic-source-sink-00.txt
> 
> To remove yourself from the IETF Announcement list, send a message to 
> ietf-announce-request with the word unsubscribe in the body of the message.
> 
> 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-camarillo-mmusic-source-sink-00.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-camarillo-mmusic-source-sink-00.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.
> 
> --NextPart
> Content-Type: Multipart/Alternative; Boundary="OtherAccess"
> 
> --OtherAccess
> Content-Type: Message/External-body;
> access-type="mail-server";
> server="mailserv@ietf.org"
> 
> Content-Type: text/plain
> Content-ID: <2002-9-13143711.I-D@ietf.org>
> 
> ENCODING mime
> FILE /internet-drafts/draft-camarillo-mmusic-source-sink-00.txt
> 
> --OtherAccess
> Content-Type: Message/External-body;
> name="draft-camarillo-mmusic-source-sink-00.txt";
> site="ftp.ietf.org";
> access-type="anon-ftp";
> directory="internet-drafts"
> 
> Content-Type: text/plain
> Content-ID: <2002-9-13143711.I-D@ietf.org>
> 
> --OtherAccess--
> 
> --NextPart--
> 
> 
> 
> --__--__--
> 
> Message: 2
> To: IETF-Announce: ;
> Cc: sip@ietf.org
> From: Internet-Drafts@ietf.org
> Reply-to: Internet-Drafts@ietf.org
> Date: Mon, 16 Sep 2002 07:46:52 -0400
> Subject: [Sip] I-D ACTION:draft-ietf-sip-sipfrag-00.txt
> 
> --NextPart
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Session Initiation Protocol Working Group of the IETF.
> 
> Title : Internet Media Type message/sipfrag
> Author(s) : R. Sparks
> Filename : draft-ietf-sip-sipfrag-00.txt
> Pages : 9
> Date : 2002-9-13
> 
> This document registers the message/sipfrag MIME media type.  This
> type is similar to message/sip , but allows certain subsets of well
> formed SIP messages to be represented instead of requiring a complete
> SIP message.  In addition to end-to-end security uses, message/
> sipfrag is used with the REFER method to convey information about the
> status of a referenced request
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sip-sipfrag-00.txt
> 
> To remove yourself from the IETF Announcement list, send a message to 
> ietf-announce-request with the word unsubscribe in the body of the message.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> "get draft-ietf-sip-sipfrag-00.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> mailserv@ietf.org.
> In the body type:
> "FILE /internet-drafts/draft-ietf-sip-sipfrag-00.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.
> 
> --NextPart
> Content-Type: Multipart/Alternative; Boundary="OtherAccess"
> 
> --OtherAccess
> Content-Type: Message/External-body;
> access-type="mail-server";
> server="mailserv@ietf.org"
> 
> Content-Type: text/plain
> Content-ID: <2002-9-13143758.I-D@ietf.org>
> 
> ENCODING mime
> FILE /internet-drafts/draft-ietf-sip-sipfrag-00.txt
> 
> --OtherAccess
> Content-Type: Message/External-body;
> name="draft-ietf-sip-sipfrag-00.txt";
> site="ftp.ietf.org";
> access-type="anon-ftp";
> directory="internet-drafts"
> 
> Content-Type: text/plain
> Content-ID: <2002-9-13143758.I-D@ietf.org>
> 
> --OtherAccess--
> 
> --NextPart--
> 
> 
> 
> --__--__--
> 
> Message: 3
> Subject: Re: [Sip] I-D ACTION:draft-ietf-sip-sipfrag-00.txt
> From: Robert Sparks <rsparks@dynamicsoft.com>
> To: sip@ietf.org
> Date: 16 Sep 2002 09:26:49 -0500
> 
> This draft replaces draft-sparks-sip-mimetypes-03, and incorporates 
> review comments from the IESG.
> 
> The syntax has not changed. The draft now contains examples of sipfrag
> mime parts and discussion of their use. In particular, the security
> section has been fleshed out and now requires extensions that use REFER
> to explicitly discuss certain attacks. 
> 
> This is ready for approval. However, enough words changed during this
> review phase that its appropriate for the working group to give it a
> quick inspection before moving forward. Please look it over and comment
> quickly. This draft is holding up a train of others.
> 
> RjS
> 
> On Mon, 2002-09-16 at 06:46, Internet-Drafts@ietf.org wrote:
> > A New Internet-Draft is available from the on-line Internet-Drafts directories.
> > This draft is a work item of the Session Initiation Protocol Working Group of the IETF.
> > 
> > Title : Internet Media Type message/sipfrag
> > Author(s) : R. Sparks
> > Filename : draft-ietf-sip-sipfrag-00.txt
> > Pages : 9
> > Date : 2002-9-13
> > 
> > This document registers the message/sipfrag MIME media type.  This
> > type is similar to message/sip , but allows certain subsets of well
> > formed SIP messages to be represented instead of requiring a complete
> > SIP message.  In addition to end-to-end security uses, message/
> > sipfrag is used with the REFER method to convey information about the
> > status of a referenced request
> > 
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-sip-sipfrag-00.txt
> > 
> > To remove yourself from the IETF Announcement list, send a message to 
> > ietf-announce-request with the word unsubscribe in the body of the message.
> > 
> > Internet-Drafts are also available by anonymous FTP. Login with the username
> > "anonymous" and a password of your e-mail address. After logging in,
> > type "cd internet-drafts" and then
> > "get draft-ietf-sip-sipfrag-00.txt".
> > 
> > A list of Internet-Drafts directories can be found in
> > http://www.ietf.org/shadow.html 
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > 
> > 
> > Internet-Drafts can also be obtained by e-mail.
> > 
> > Send a message to:
> > mailserv@ietf.org.
> > In the body type:
> > "FILE /internet-drafts/draft-ietf-sip-sipfrag-00.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.
> > 
> 
> 
> 
> 
> --__--__--
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
> End of Sip Digest
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Wed Sep 18 05:31:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06806
	for <sip-archive@odin.ietf.org>; Wed, 18 Sep 2002 05:31:17 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8I9WXP21928
	for sip-archive@odin.ietf.org; Wed, 18 Sep 2002 05:32:33 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8I9Vlv21884;
	Wed, 18 Sep 2002 05:31:47 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8I9RVv21734
	for <sip@optimus.ietf.org>; Wed, 18 Sep 2002 05:27:31 -0400
Received: from hss.hns.com ([164.164.94.118])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06676
	for <sip@ietf.org>; Wed, 18 Sep 2002 05:25:37 -0400 (EDT)
From: pnath@hss.hns.com
Received: from sampark.hss.hns.com (sampark [139.85.229.22])
	by hss.hns.com (8.11.6/8.11.2) with SMTP id g8I9FLi30057;
	Wed, 18 Sep 2002 14:45:21 +0530
Received: by sampark.hss.hns.com(Lotus SMTP MTA Internal build v4.6.2  (651.2 6-10-1998))  id 65256C38.0033E8F2 ; Wed, 18 Sep 2002 14:56:59 +0530
X-Lotus-FromDomain: HSSBLR
To: sip@ietf.org
cc: jdrosen@dynamicsoft.com
Message-ID: <65256C38.0033E7C3.00@sampark.hss.hns.com>
Date: Wed, 18 Sep 2002 14:56:56 +0530
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Sip] draft-ietf-sip-update-02.txt- Sending 500 response
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>



Hello
       I have doubt regarding the following  statement of the
draft-ietf-sip-update-02.txt

"A UAS that receives an UPDATE before it has generated a final
response to a previous UPDATE or INVITE on the same dialog
 MUST return a 500 response to the new UPDATE, and MUST
include a Retry-After field with a Retry-After header field with a
randomly chosen  value between 0 and 10 seconds."

From my understanding, the UPDATE method allows the caller or
callee to provide updated session information before a final response
to the initial INVITE request is generated. So, why need to send the 500
 response to UPDATE request where the UAS has not generated a final
response to a previous  INVITE  on the same dialog.

I think the statement should be
"A UAS that receives an UPDATE before it has generated a final
response to a previous UPDATE or re-INVITE on the same dialog
 MUST return a 500 response to the new UPDATE, and MUST
include a Retry-After field with a Retry-After header field with a
randomly chosen  value between 0 and 10 seconds."

Please correct me if I am wrong.


Regds
Pankaj Nath






This message is proprietary to Hughes Software Systems Limited (HSS) and is
intended solely for the use of the individual to whom it is addressed.  It
may contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended.  If
you have received this message in error, please notify the originator
immediately.  If you are not the intended recipient, you are notified that
you are strictly prohibited from using, copying, altering, or disclosing
the contents of this message.  HSS accepts no responsibility for loss or
damage arising from the use of the information transmitted by this email
including damage from virus.


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



From mailnull@www1.ietf.org  Wed Sep 18 08:14:24 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09729
	for <sip-archive@odin.ietf.org>; Wed, 18 Sep 2002 08:14:24 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8ICFff29949
	for sip-archive@odin.ietf.org; Wed, 18 Sep 2002 08:15:41 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8ICFDv29918;
	Wed, 18 Sep 2002 08:15:13 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IBwKv28818
	for <sip@optimus.ietf.org>; Wed, 18 Sep 2002 07:58:20 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09167;
	Wed, 18 Sep 2002 07:56:30 -0400 (EDT)
Message-Id: <200209181156.HAA09167@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sip@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 18 Sep 2002 07:56:30 -0400
Subject: [Sip] I-D ACTION:draft-ietf-sip-compression-01.txt
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: Compressing the Session Initiation Protocol
	Author(s)	: G. Camarillo
	Filename	: draft-ietf-sip-compression-01.txt
	Pages		: 12
	Date		: 2002-9-17
	
This document describes a mechanism to signal that compression is
desired for one or more SIP messages. It also states when it is
appropriate to send compressed SIP messages to a SIP entity.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sip-compression-01.txt".

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


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

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

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2002-9-17141002.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sip-compression-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-sip-compression-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-9-17141002.I-D@ietf.org>

--OtherAccess--

--NextPart--


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



From mailnull@www1.ietf.org  Wed Sep 18 16:41:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29447
	for <sip-archive@odin.ietf.org>; Wed, 18 Sep 2002 16:41:52 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8IKhEa10391
	for sip-archive@odin.ietf.org; Wed, 18 Sep 2002 16:43:14 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IKgnv10359;
	Wed, 18 Sep 2002 16:42:49 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IKevv10262
	for <sip@optimus.ietf.org>; Wed, 18 Sep 2002 16:40:57 -0400
Received: from mail2.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29333
	for <sip@ietf.org>; Wed, 18 Sep 2002 16:39:05 -0400 (EDT)
Received: from DYN-EXCH-001.dynamicsoft.com (dyn-exch-001 [63.113.44.7])
	by mail2.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id g8IKdeNo016420;
	Wed, 18 Sep 2002 16:39:40 -0400 (EDT)
Received: by DYN-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <S3Q8L94C>; Wed, 18 Sep 2002 16:40:19 -0400
Message-ID: <1407568FD28578458C2F1FFFF30B82BB5494C6@DYN-EXCH-001.dynamicsoft.com>
From: Igor Slepchin <ISlepchin@dynamicsoft.com>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>,
        Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Cc: Stephen James <sjames@voiceramp.com>, sip@ietf.org
Subject: RE: [Sip] TEL-URL questions
Date: Wed, 18 Sep 2002 16:40:16 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

I'd say any TEL URL params should be treated within the context of TEL URL
only. Since RFC2806 does not define ttl, method, maddr or lr params, they
should be treated as future-extension params and, hence, given no special
meaning. In other words, tel:12345;transport=TCP does not imply the use of
TCP. 

Thank you,
Igor Slepchin


> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> <...>
> But, what about the ttl-, method-, lr- and maddr parameters? 
> How shall they be
> handled if received within a TEL-URL? I guess some of those 
> can't be used, and
> can simply be ignored, but there may be some that should be 
> treated the same
> way as if received within a SIP-URI. Or?
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Thu Sep 19 00:45:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11383
	for <sip-archive@odin.ietf.org>; Thu, 19 Sep 2002 00:45:00 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8J4kQI02660
	for sip-archive@odin.ietf.org; Thu, 19 Sep 2002 00:46:26 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J4j8v02614;
	Thu, 19 Sep 2002 00:45:08 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J4hnv02549
	for <sip@optimus.ietf.org>; Thu, 19 Sep 2002 00:43:49 -0400
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11338
	for <sip@ietf.org>; Thu, 19 Sep 2002 00:41:51 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g8J4harU024108;
	Thu, 19 Sep 2002 06:43:36 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.22])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g8J4hZG3027407;
	Thu, 19 Sep 2002 07:43:35 +0300 (EET DST)
Message-ID: <3D8955F7.6DAA565B@lmf.ericsson.se>
Date: Thu, 19 Sep 2002 07:43:35 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Igor Slepchin <ISlepchin@dynamicsoft.com>
CC: Jonathan Rosenberg <jdrosen@dynamicsoft.com>,
        Stephen James <sjames@voiceramp.com>, sip@ietf.org
Subject: Re: [Sip] TEL-URL questions
References: <1407568FD28578458C2F1FFFF30B82BB5494C6@DYN-EXCH-001.dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


Hi,

> I'd say any TEL URL params should be treated within the context of TEL URL
> only. Since RFC2806 does not define ttl, method, maddr or lr params, they
> should be treated as future-extension params and, hence, given no special
> meaning. In other words, tel:12345;transport=TCP does not imply the use of
> TCP.

I guess one issue with that solution is that in the future parameters with the
same names may be defined also for Tel-Url, but they may have a completely
separate function from the Sip-Uri parameter with the same name. So, by simply
moving the parameters from one Uri to anther could problems, or at least
unwanted behaviour.

The other solution would of course to discard the Sip-Uri parameters, when the
Sip-to-Tel mapping... Would that cause any problems?

Regards,

Christer Holmberg
Ericsson Finland




>
>
> Thank you,
> Igor Slepchin
>
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > <...>
> > But, what about the ttl-, method-, lr- and maddr parameters?
> > How shall they be
> > handled if received within a TEL-URL? I guess some of those
> > can't be used, and
> > can simply be ignored, but there may be some that should be
> > treated the same
> > way as if received within a SIP-URI. Or?

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



From mailnull@www1.ietf.org  Thu Sep 19 06:00:13 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28556
	for <sip-archive@odin.ietf.org>; Thu, 19 Sep 2002 06:00:13 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8JA1VB27771
	for sip-archive@odin.ietf.org; Thu, 19 Sep 2002 06:01:31 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JA0qv27652;
	Thu, 19 Sep 2002 06:00:53 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J9rkv27348
	for <sip@optimus.ietf.org>; Thu, 19 Sep 2002 05:53:46 -0400
Received: from hclnpd.hclt.co.in ([202.54.64.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28384
	for <sip@ietf.org>; Thu, 19 Sep 2002 05:51:57 -0400 (EDT)
Received: from blaze.hcltech.com (blaze.hclt-ntl.co.in [192.168.19.30]) by hclnpd.hclt.co.in with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id SP90QZMT; Thu, 19 Sep 2002 15:23:16 +0530
Received: from sachin-pc.netlab.hcltech.com ([192.168.19.142])
	by blaze.hcltech.com (8.9.3/8.9.3) with ESMTP id PAA19541
	for <sip@ietf.org>; Thu, 19 Sep 2002 15:52:09 +0530
Message-Id: <4.3.2.7.0.20020919150512.00e96920@blaze>
X-Sender: sachins@blaze
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 19 Sep 2002 15:16:10 +0530
To: sip@ietf.org
From: Sachin Shenoy <sachins@netlab.hcltech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Sip] BranchID in CANCEL & INVITE
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

Hi,
This is regarding branches in CANCEL & INVITE.

Section 9.1 of RFC says

"9.1 Client Behavior
...
The CANCEL request MUST NOT contain any Require or Proxy-Require header 
fields."


Consider the following scenario
UAC sends INVITE to P1.
P1 forwards it statlessley to UAS.
UAC sends CANCEL to P1 (to cancel the INVITE).
P1 forwards CANCEL also to UAS.

Let INVITE request have Proxy-Require header.

While handling INVITE at proxy,
P1 calculates the VIA's loop-detection part using the Proxy-Require header.
(The unique part would be calculated using a combinatronic function.) So the
INVITE's VIA would reflect the contents of the proxy-require header.

While handling CANCEL at proxy,
P1 calculates the VIA's loop-detection part without the Proxy-Require header,
As CANCEL would not have it.

At UAS:
INVITE & CANCEL would have different top-most via branches.

But according to RFC they have to have the same branches for the UAS to
match the CANCEL & INVITE properly.

"9.1 Client Behavior
...
A CANCEL constructed by a client MUST have only a single Via header field
value matching the top Via value in the request being cancelled.  Using the 
same
values for these header fields allows the CANCEL to be matched with the
request it cancels (Section 9.2 indicates how such matching occurs)."

Is it that Stateless proxies are not supposed to do loop-detection?

I thought the idea of having loop-detection part in branch-id was to
allow proxies to detect loop even while being stateless. If only stateful
proxies were to do loop-detection, we wouldn't have required the hash
to be kept in the message at all.

Thanks in advance
Sachin

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



From mailnull@www1.ietf.org  Thu Sep 19 07:09:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29657
	for <sip-archive@odin.ietf.org>; Thu, 19 Sep 2002 07:09:29 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8JBAmx31877
	for sip-archive@odin.ietf.org; Thu, 19 Sep 2002 07:10:48 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JB9tv31832;
	Thu, 19 Sep 2002 07:09:55 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JB8Fv31785
	for <sip@optimus.ietf.org>; Thu, 19 Sep 2002 07:08:15 -0400
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29633
	for <sip@ietf.org>; Thu, 19 Sep 2002 07:06:26 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id NAA00366
	for <sip@ietf.org>; Thu, 19 Sep 2002 13:08:13 +0200 (MET DST)
Received: from mchh9ega.mchh.siemens.de (mchh9ega.mchh.siemens.de [139.21.194.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id NAA05613
	for <sip@ietf.org>; Thu, 19 Sep 2002 13:08:12 +0200 (MET DST)
Received: by mchh9ega.mchh.siemens.de with Internet Mail Service (5.5.2653.19)
	id <S8QPRT5Z>; Thu, 19 Sep 2002 13:08:12 +0200
Message-ID: <B3028CA9D0B8D511874E0002A53F24D566D1C7@mchh9mla.mchh.siemens.de>
From: BECKMANN MARK <mark.beckmann@siemens.com>
To: "'sip@ietf.org'" <sip@ietf.org>
Date: Thu, 19 Sep 2002 13:08:11 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sip] Schedule for draft-rosenberg-sip-reg-00
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

Hi,

I'd like to know what the planned schedule for the I-D
draft-rosenberg-sip-reg is? There haven't been a lot of dicussions on the
list about this draft. I think a revision is needed based on the comments
raised in the following messages:

http://www.ietf.org/mail-archive/working-groups/sip/current/msg06113.html
http://www.ietf.org/mail-archive/working-groups/sip/current/msg06118.html
http://www.ietf.org/mail-archive/working-groups/sip/current/msg06124.html

Are there any plans yet when this draft is supposed to move to WG LC? The
main reason I'm asking is that 3GPP needs this draft to finalise their
Release 5 specifications.

Regards,

Mark

Mark Beckmann			Siemens AG

ICM MP P PS 4S2
P.O.Box 100702			phone: +49 (5341) 906 1814
D-38228 Salzgitter   		fax:   +49 (5341) 906 2010

mailto: Mark.Beckmann@siemens.com


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



From mailnull@www1.ietf.org  Thu Sep 19 09:00:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02845
	for <sip-archive@odin.ietf.org>; Thu, 19 Sep 2002 09:00:44 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8JD24X05369
	for sip-archive@odin.ietf.org; Thu, 19 Sep 2002 09:02:04 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JD1ev05332;
	Thu, 19 Sep 2002 09:01:40 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J5xvv05981
	for <sip@optimus.ietf.org>; Thu, 19 Sep 2002 01:59:57 -0400
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12280
	for <sip@ietf.org>; Thu, 19 Sep 2002 01:57:59 -0400 (EDT)
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id HAA07246
	for <sip@ietf.org>; Thu, 19 Sep 2002 07:59:46 +0200 (MET DST)
Received: from mchh9ega.mchh.siemens.de (mchh9ega.mchh.siemens.de [139.21.194.56])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id HAA27903
	for <sip@ietf.org>; Thu, 19 Sep 2002 07:59:46 +0200 (MET DST)
Received: by mchh9ega.mchh.siemens.de with Internet Mail Service (5.5.2653.19)
	id <S8QPRQ75>; Thu, 19 Sep 2002 07:59:45 +0200
Message-ID: <B3028CA9D0B8D511874E0002A53F24D566D1B9@mchh9mla.mchh.siemens.de>
From: BECKMANN MARK <mark.beckmann@siemens.com>
To: sip@ietf.org
Date: Thu, 19 Sep 2002 07:59:42 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sip] Schedule for draft-rosenberg-sip-reg-00
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

Hi,

I'd like to know what the planned schedule for the I-D
draft-rosenberg-sip-reg is? There haven't been a lot of dicussions on the
list about this draft. I think a revision is needed based on the comments
raised in the following messages:

http://www.ietf.org/mail-archive/working-groups/sip/current/msg06113.html
http://www.ietf.org/mail-archive/working-groups/sip/current/msg06118.html
http://www.ietf.org/mail-archive/working-groups/sip/current/msg06124.html

Are there any plans yet when this draft is supposed to move to WG LC? The
main reason I'm asking is that 3GPP needs this draft to finalise their
Release 5 specifications.

Regards,

Mark

Mark Beckmann			Siemens AG

ICM MP P PS 4S2
P.O.Box 100702			phone: +49 (5341) 906 1814
D-38228 Salzgitter   		fax:   +49 (5341) 906 2010

mailto: Mark.Beckmann@siemens.com


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



From mailnull@www1.ietf.org  Thu Sep 19 11:25:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09746
	for <sip-archive@odin.ietf.org>; Thu, 19 Sep 2002 11:25:39 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8JFQwR15589
	for sip-archive@odin.ietf.org; Thu, 19 Sep 2002 11:26:58 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JFQ9v15523;
	Thu, 19 Sep 2002 11:26:09 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JFOmv15434
	for <sip@optimus.ietf.org>; Thu, 19 Sep 2002 11:24:48 -0400
Received: from mail2.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09590
	for <sip@ietf.org>; Thu, 19 Sep 2002 11:22:58 -0400 (EDT)
Received: from DYN-EXCH-001.dynamicsoft.com (dyn-exch-001 [63.113.44.7])
	by mail2.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id g8JFNYNo019968;
	Thu, 19 Sep 2002 11:23:34 -0400 (EDT)
Received: by DYN-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <S3Q8MAN6>; Thu, 19 Sep 2002 11:24:13 -0400
Message-ID: <1407568FD28578458C2F1FFFF30B82BB5494C8@DYN-EXCH-001.dynamicsoft.com>
From: Igor Slepchin <ISlepchin@dynamicsoft.com>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>,
        Igor Slepchin
	 <ISlepchin@dynamicsoft.com>
Cc: Jonathan Rosenberg <jdrosen@dynamicsoft.com>,
        Stephen James
	 <sjames@voiceramp.com>, sip@ietf.org
Subject: RE: [Sip] TEL-URL questions
Date: Thu, 19 Sep 2002 11:24:12 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

I actually did not mean that these parameters should be copied when
converting SIP URLs into TEL URLs (I believe they should not be). What I was
trying to say is that even if they do appear in TEL URL used in a SIP
message for whatever reason, their meaning is not defined in SIP.

Thank you,
Igor Slepchin

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> 
> I guess one issue with that solution is that in the future 
> parameters with the
> same names may be defined also for Tel-Url, but they may have 
> a completely
> separate function from the Sip-Uri parameter with the same 
> name. So, by simply
> moving the parameters from one Uri to anther could problems, 
> or at least
> unwanted behaviour.
> 
> The other solution would of course to discard the Sip-Uri 
> parameters, when the
> Sip-to-Tel mapping... Would that cause any problems?
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Thu Sep 19 12:17:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09747
	for <sip-archive@odin.ietf.org>; Thu, 19 Sep 2002 11:25:39 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8JFQxb15594
	for sip-archive@odin.ietf.org; Thu, 19 Sep 2002 11:26:59 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JFPKv15481;
	Thu, 19 Sep 2002 11:25:20 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JFNPv15393
	for <sip@optimus.ietf.org>; Thu, 19 Sep 2002 11:23:25 -0400
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09565
	for <sip@ietf.org>; Thu, 19 Sep 2002 11:21:34 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8JFMp1X024306;
	Thu, 19 Sep 2002 08:22:51 -0700 (PDT)
Received: from open-131-161-248-87.cliq.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.1.0.54-GA)
	with ESMTP id AAW60498;
	Thu, 19 Sep 2002 08:21:10 -0700 (PDT)
Date: Thu, 19 Sep 2002 08:23:59 -0700
Subject: Re: [Sip] Schedule for draft-rosenberg-sip-reg-00
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v482)
Cc: "'sip@ietf.org'" <sip@ietf.org>
To: BECKMANN MARK <mark.beckmann@siemens.com>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <B3028CA9D0B8D511874E0002A53F24D566D1C7@mchh9mla.mchh.siemens.de>
Message-Id: <D2455915-CBE3-11D6-A5C1-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.482)
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Mark,

The SIPPING WG asked for AD approval to adopt this as a WG item in 
SIPPING.  Currently Jonathan is aware that this needs a revision, but is 
working on another draft which is blocking other stuff now.  I'll try to 
get a realistic date soon.

thanks,
-rohan



On Thursday, September 19, 2002, at 04:08 AM, BECKMANN MARK wrote:

> Hi,
>
> I'd like to know what the planned schedule for the I-D
> draft-rosenberg-sip-reg is? There haven't been a lot of dicussions on 
> the
> list about this draft. I think a revision is needed based on the 
> comments
> raised in the following messages:
>
> http://www.ietf.org/mail-archive/working-
> groups/sip/current/msg06113.html
> http://www.ietf.org/mail-archive/working-
> groups/sip/current/msg06118.html
> http://www.ietf.org/mail-archive/working-
> groups/sip/current/msg06124.html
>
> Are there any plans yet when this draft is supposed to move to WG LC? 
> The
> main reason I'm asking is that 3GPP needs this draft to finalise their
> Release 5 specifications.
>
> Regards,
>
> Mark
>
> Mark Beckmann			Siemens AG
>
> ICM MP P PS 4S2
> P.O.Box 100702			phone: +49 (5341) 906 1814
> D-38228 Salzgitter   		fax:   +49 (5341) 906 2010
>
> mailto: Mark.Beckmann@siemens.com
>
>
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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



From mailnull@www1.ietf.org  Thu Sep 19 15:53:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20943
	for <sip-archive@odin.ietf.org>; Thu, 19 Sep 2002 15:53:16 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8JJscE01796
	for sip-archive@odin.ietf.org; Thu, 19 Sep 2002 15:54:38 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JJsDv01779;
	Thu, 19 Sep 2002 15:54:13 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JJqLv01704
	for <sip@optimus.ietf.org>; Thu, 19 Sep 2002 15:52:21 -0400
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20860
	for <sip@ietf.org>; Thu, 19 Sep 2002 15:50:28 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g8JJq6rU012432;
	Thu, 19 Sep 2002 21:52:06 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.106.10])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g8JJq5G3018723;
	Thu, 19 Sep 2002 22:52:05 +0300 (EET DST)
Message-ID: <3D8A2AE5.2306020C@lmf.ericsson.se>
Date: Thu, 19 Sep 2002 22:52:05 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Igor Slepchin <ISlepchin@dynamicsoft.com>
CC: Jonathan Rosenberg <jdrosen@dynamicsoft.com>,
        Stephen James <sjames@voiceramp.com>, sip@ietf.org
Subject: Re: [Sip] TEL-URL questions
References: <1407568FD28578458C2F1FFFF30B82BB5494C8@DYN-EXCH-001.dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


Hi,

> I actually did not mean that these parameters should be copied when
> converting SIP URLs into TEL URLs (I believe they should not be). What I was
> trying to say is that even if they do appear in TEL URL used in a SIP
> message for whatever reason, their meaning is not defined in SIP.

I guess that sounds fine to me.

In fact, if they did appear in a TEL-URL, I guess we would put them in the user
part of the SIP-URI, as we do with all other TEL-URI parameters...

Regards,

Christer Holmberg
Ericsson Finland



>
>
> Thank you,
> Igor Slepchin
>
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> >
> > I guess one issue with that solution is that in the future
> > parameters with the
> > same names may be defined also for Tel-Url, but they may have
> > a completely
> > separate function from the Sip-Uri parameter with the same
> > name. So, by simply
> > moving the parameters from one Uri to anther could problems,
> > or at least
> > unwanted behaviour.
> >
> > The other solution would of course to discard the Sip-Uri
> > parameters, when the
> > Sip-to-Tel mapping... Would that cause any problems?
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland

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



From mailnull@www1.ietf.org  Fri Sep 20 08:55:18 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20759
	for <sip-archive@odin.ietf.org>; Fri, 20 Sep 2002 08:55:18 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8KCuX728153
	for sip-archive@odin.ietf.org; Fri, 20 Sep 2002 08:56:33 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KCtrv28124;
	Fri, 20 Sep 2002 08:55:53 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KCpSv28021
	for <sip@optimus.ietf.org>; Fri, 20 Sep 2002 08:51:28 -0400
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20570
	for <sip@ietf.org>; Fri, 20 Sep 2002 08:49:37 -0400 (EDT)
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate.mot.com (motgate 2.1) with ESMTP id FAA19920 for <sip@ietf.org>; Fri, 20 Sep 2002 05:50:54 -0700 (MST)]
Received: [from nadhi.migv.mot.com ([217.2.42.15]) by mothost.mot.com (MOT-pobox 2.0) with ESMTP id FAA04584 for <sip@ietf.org>; Fri, 20 Sep 2002 05:50:52 -0700 (MST)]
Received: from golfmail.migv.mot.com (golfmail.migv.mot.com [217.2.42.13])
	by migv.mot.com (8.9.3/8.9.3) with ESMTP id SAA03873
	for <sip@ietf.org>; Fri, 20 Sep 2002 18:26:15 +0530 (IST)
Received: by golfmail.migv.mot.com with Internet Mail Service (5.5.2650.21)
	id <PS0R9RR7>; Fri, 20 Sep 2002 18:20:50 +0530
Message-ID: <195FE1D3531BD411A50F00B0D021783402907C9A@golfmail.migv.mot.com>
From: ABDUL SATTAR SHAIK <abdulss@migv.mot.com>
To: "'sip@ietf.org'" <sip@ietf.org>
Date: Fri, 20 Sep 2002 18:19:22 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C260A4.2706DF20"
Subject: [Sip] Branch in  INVITE ,ACK,BYE
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

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_001_01C260A4.2706DF20
Content-Type: text/plain;
	charset="iso-8859-1"

The branch parameter  should change with each request send by UAC  or per
Transaction Basis. If it is on transaction  basis INVITE and ACK should have
same branch parameter

In RFC 3261 Examples The branch parameter is different for  INVITE and ACK
message sent By UAC

 24.2 Session Setup

   This example contains the full details of the example session setup
   in Section 4.  The message flow is shown in Figure 1.  Note that
   these flows show the minimum required set of header fields - some
   other header fields such as Allow and Supported would normally be
   present.

F1 INVITE Alice -> atlanta.com proxy

INVITE sip:bob@biloxi.com SIP/2.0
Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bKnashds8
Max-Forwards: 70
To: Bob <sip:bob@biloxi.com>
From: Alice <sip:alice@atlanta.com>;tag=1928301774
Call-ID: a84b4c76e66710
CSeq: 314159 INVITE
Contact: <sip:alice@pc33.atlanta.com>
Content-Type: application/sdp
Content-Length: 142

(Alice's SDP not shown)


ACK sip:bob@192.0.2.4 SIP/2.0
Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bKnashds9 
Max-Forwards: 70
To: Bob <sip:bob@biloxi.com>;tag=a6c85cf
From: Alice <sip:alice@atlanta.com>;tag=1928301774
Call-ID: a84b4c76e66710
CSeq: 314159 ACK
Content-Length: 0


Thanks in Advance
Abdul Sattar


------_=_NextPart_001_01C260A4.2706DF20
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>Branch in  INVITE ,ACK,BYE</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">The branch parameter&nbsp; should =
change with each request send by UAC&nbsp; or per&nbsp; Transaction =
Basis. If it is on transaction&nbsp; basis INVITE and ACK should have =
same branch parameter</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">In RFC 3261 Examples The branch =
parameter is different for&nbsp; INVITE and ACK message sent By =
UAC</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;24.2 Session Setup</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; This example contains the =
full details of the example session setup</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; in Section 4.&nbsp; The =
message flow is shown in Figure 1.&nbsp; Note that</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; these flows show the =
minimum required set of header fields - some</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; other header fields such =
as Allow and Supported would normally be</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; present.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">F1 INVITE Alice -&gt; atlanta.com =
proxy</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">INVITE sip:bob@biloxi.com =
SIP/2.0</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Via: SIP/2.0/UDP =
pc33.atlanta.com;branch=3Dz9hG4bKnashds8</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Max-Forwards: 70</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">To: Bob =
&lt;sip:bob@biloxi.com&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">From: Alice =
&lt;sip:alice@atlanta.com&gt;;tag=3D1928301774</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Call-ID: a84b4c76e66710</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">CSeq: 314159 INVITE</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Contact: =
&lt;sip:alice@pc33.atlanta.com&gt;</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Content-Type: application/sdp</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Content-Length: 142</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">(Alice's SDP not shown)</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">ACK sip:bob@192.0.2.4 SIP/2.0</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Via: SIP/2.0/UDP =
pc33.atlanta.com;branch=3Dz9hG4bKnashds9 </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Max-Forwards: 70</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">To: Bob =
&lt;sip:bob@biloxi.com&gt;;tag=3Da6c85cf</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">From: Alice =
&lt;sip:alice@atlanta.com&gt;;tag=3D1928301774</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Call-ID: a84b4c76e66710</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">CSeq: 314159 ACK</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Content-Length: 0</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks in Advance</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Abdul Sattar</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C260A4.2706DF20--
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Fri Sep 20 09:25:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21522
	for <sip-archive@odin.ietf.org>; Fri, 20 Sep 2002 09:25:08 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8KDQS330053
	for sip-archive@odin.ietf.org; Fri, 20 Sep 2002 09:26:28 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KDPVv30022;
	Fri, 20 Sep 2002 09:25:31 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KDLhv29858
	for <sip@optimus.ietf.org>; Fri, 20 Sep 2002 09:21:43 -0400
Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21401
	for <sip@ietf.org>; Fri, 20 Sep 2002 09:19:51 -0400 (EDT)
From: hisham.khartabil@nokia.com
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g8KDM2Z20611
	for <sip@ietf.org>; Fri, 20 Sep 2002 16:22:02 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5d7485fc72ac158f2438e@esvir04nok.ntc.nokia.com>;
 Fri, 20 Sep 2002 16:21:36 +0300
Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 20 Sep 2002 16:21:36 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C260A8.A4E21778"
Subject: RE: [Sip] Branch in  INVITE ,ACK,BYE
Date: Fri, 20 Sep 2002 16:21:35 +0300
Message-ID: <2038BCC78B1AD641891A0D1AE133DBB7C20658@esebe019.ntc.nokia.com>
Thread-Topic: [Sip] Branch in  INVITE ,ACK,BYE
Thread-Index: AcJgpWU9pUObLVjUSzeJX99MJrsqfAAAuzZg
To: <abdulss@migv.mot.com>, <sip@ietf.org>
X-OriginalArrivalTime: 20 Sep 2002 13:21:36.0375 (UTC) FILETIME=[A54B6870:01C260A8]
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C260A8.A4E21778
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

ACK is only part of the transaction only if the response to the INVITE =
was an non-2xx final response. If the response was 200, then the ACK is =
a new transaction.
=20
The example you talk about below is for an INVITE than got a 200 ok =
response.
=20
Regards,
Hisham

-----Original Message-----
From: ext ABDUL SATTAR SHAIK [mailto:abdulss@migv.mot.com]
Sent: Friday, September 20, 2002 3:49 PM
To: 'sip@ietf.org'
Subject: [Sip] Branch in INVITE ,ACK,BYE



The branch parameter  should change with each request send by UAC  or =
per  Transaction Basis. If it is on transaction  basis INVITE and ACK =
should have same branch parameter

In RFC 3261 Examples The branch parameter is different for  INVITE and =
ACK message sent By UAC=20

 24.2 Session Setup=20

   This example contains the full details of the example session setup=20
   in Section 4.  The message flow is shown in Figure 1.  Note that=20
   these flows show the minimum required set of header fields - some=20
   other header fields such as Allow and Supported would normally be=20
   present.=20

F1 INVITE Alice -> atlanta.com proxy=20

INVITE sip:bob@biloxi.com SIP/2.0=20
Via: SIP/2.0/UDP pc33.atlanta.com;branch=3Dz9hG4bKnashds8=20
Max-Forwards: 70=20
To: Bob <sip:bob@biloxi.com>=20
From: Alice <sip:alice@atlanta.com>;tag=3D1928301774=20
Call-ID: a84b4c76e66710=20
CSeq: 314159 INVITE=20
Contact: <sip:alice@pc33.atlanta.com>=20
Content-Type: application/sdp=20
Content-Length: 142=20

(Alice's SDP not shown)=20


ACK sip:bob@192.0.2.4 SIP/2.0=20
Via: SIP/2.0/UDP pc33.atlanta.com;branch=3Dz9hG4bKnashds9=20
Max-Forwards: 70=20
To: Bob <sip:bob@biloxi.com>;tag=3Da6c85cf=20
From: Alice <sip:alice@atlanta.com>;tag=3D1928301774=20
Call-ID: a84b4c76e66710=20
CSeq: 314159 ACK=20
Content-Length: 0=20


Thanks in Advance=20
Abdul Sattar=20


------_=_NextPart_001_01C260A8.A4E21778
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>Branch in INVITE ,ACK,BYE</TITLE>

<META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D797161913-20092002><FONT face=3DArial color=3D#0000ff =
size=3D2>ACK is=20
only part of the transaction only&nbsp;if the response to the INVITE was =
an=20
non-2xx final response. If the response was 200, then the ACK is a new=20
transaction.</FONT></SPAN></DIV>
<DIV><SPAN class=3D797161913-20092002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D797161913-20092002><FONT face=3DArial color=3D#0000ff =
size=3D2>The=20
example you talk about below is for an INVITE than got a 200 ok=20
response.</FONT></SPAN></DIV>
<DIV><SPAN class=3D797161913-20092002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D797161913-20092002><FONT face=3DArial color=3D#0000ff =

size=3D2>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D797161913-20092002><FONT face=3DArial color=3D#0000ff =

size=3D2>Hisham</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> ext ABDUL SATTAR =
SHAIK=20
  [mailto:abdulss@migv.mot.com]<BR><B>Sent:</B> Friday, September 20, =
2002 3:49=20
  PM<BR><B>To:</B> 'sip@ietf.org'<BR><B>Subject:</B> [Sip] Branch in =
INVITE=20
  ,ACK,BYE<BR><BR></FONT></DIV>
  <P><FONT face=3DArial size=3D2>The branch parameter&nbsp; should =
change with each=20
  request send by UAC&nbsp; or per&nbsp; Transaction Basis. If it is on=20
  transaction&nbsp; basis INVITE and ACK should have same branch=20
  parameter</FONT></P>
  <P><FONT face=3DArial size=3D2>In RFC 3261 Examples The branch =
parameter is=20
  different for&nbsp; INVITE and ACK message sent By UAC</FONT> </P>
  <P><FONT face=3DArial size=3D2>&nbsp;24.2 Session Setup</FONT> </P>
  <P><FONT face=3DArial size=3D2>&nbsp;&nbsp; This example contains the =
full details=20
  of the example session setup</FONT> <BR><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;=20
  in Section 4.&nbsp; The message flow is shown in Figure 1.&nbsp; Note=20
  that</FONT> <BR><FONT face=3DArial size=3D2>&nbsp;&nbsp; these flows =
show the=20
  minimum required set of header fields - some</FONT> <BR><FONT =
face=3DArial=20
  size=3D2>&nbsp;&nbsp; other header fields such as Allow and Supported =
would=20
  normally be</FONT> <BR><FONT face=3DArial size=3D2>&nbsp;&nbsp; =
present.</FONT>=20
  </P>
  <P><FONT face=3DArial size=3D2>F1 INVITE Alice -&gt; atlanta.com =
proxy</FONT> </P>
  <P><FONT face=3DArial size=3D2>INVITE sip:bob@biloxi.com =
SIP/2.0</FONT> <BR><FONT=20
  face=3DArial size=3D2>Via: SIP/2.0/UDP=20
  pc33.atlanta.com;branch=3Dz9hG4bKnashds8</FONT> <BR><FONT face=3DArial =

  size=3D2>Max-Forwards: 70</FONT> <BR><FONT face=3DArial size=3D2>To: =
Bob=20
  &lt;sip:bob@biloxi.com&gt;</FONT> <BR><FONT face=3DArial =
size=3D2>From: Alice=20
  &lt;sip:alice@atlanta.com&gt;;tag=3D1928301774</FONT> <BR><FONT =
face=3DArial=20
  size=3D2>Call-ID: a84b4c76e66710</FONT> <BR><FONT face=3DArial =
size=3D2>CSeq: 314159=20
  INVITE</FONT> <BR><FONT face=3DArial size=3D2>Contact:=20
  &lt;sip:alice@pc33.atlanta.com&gt;</FONT> <BR><FONT face=3DArial=20
  size=3D2>Content-Type: application/sdp</FONT> <BR><FONT face=3DArial=20
  size=3D2>Content-Length: 142</FONT> </P>
  <P><FONT face=3DArial size=3D2>(Alice's SDP not shown)</FONT> </P><BR>
  <P><FONT face=3DArial size=3D2>ACK sip:bob@192.0.2.4 SIP/2.0</FONT> =
<BR><FONT=20
  face=3DArial size=3D2>Via: SIP/2.0/UDP =
pc33.atlanta.com;branch=3Dz9hG4bKnashds9=20
  </FONT><BR><FONT face=3DArial size=3D2>Max-Forwards: 70</FONT> =
<BR><FONT=20
  face=3DArial size=3D2>To: Bob =
&lt;sip:bob@biloxi.com&gt;;tag=3Da6c85cf</FONT>=20
  <BR><FONT face=3DArial size=3D2>From: Alice=20
  &lt;sip:alice@atlanta.com&gt;;tag=3D1928301774</FONT> <BR><FONT =
face=3DArial=20
  size=3D2>Call-ID: a84b4c76e66710</FONT> <BR><FONT face=3DArial =
size=3D2>CSeq: 314159=20
  ACK</FONT> <BR><FONT face=3DArial size=3D2>Content-Length: 0</FONT> =
</P><BR>
  <P><FONT face=3DArial size=3D2>Thanks in Advance</FONT> <BR><FONT =
face=3DArial=20
  size=3D2>Abdul Sattar</FONT> </P></BLOCKQUOTE></BODY></HTML>

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



From mailnull@www1.ietf.org  Fri Sep 20 10:45:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24529
	for <sip-archive@odin.ietf.org>; Fri, 20 Sep 2002 10:45:53 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8KElDU02741
	for sip-archive@odin.ietf.org; Fri, 20 Sep 2002 10:47:13 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KEkjv02710;
	Fri, 20 Sep 2002 10:46:45 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KEh9v02558
	for <sip@optimus.ietf.org>; Fri, 20 Sep 2002 10:43:09 -0400
Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24361
	for <sip@ietf.org>; Fri, 20 Sep 2002 10:41:18 -0400 (EDT)
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate2.mot.com (motgate2 2.1) with ESMTP id GAA07645 for <sip@ietf.org>; Fri, 20 Sep 2002 06:46:18 -0700 (MST)]
Received: [from nadhi.migv.mot.com ([217.2.42.15]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id GAA09387 for <sip@ietf.org>; Fri, 20 Sep 2002 06:45:54 -0700 (MST)]
Received: from golfmail.migv.mot.com (golfmail.migv.mot.com [217.2.42.13])
	by migv.mot.com (8.9.3/8.9.3) with ESMTP id TAA07965
	for <sip@ietf.org>; Fri, 20 Sep 2002 19:21:18 +0530 (IST)
Received: by golfmail.migv.mot.com with Internet Mail Service (5.5.2650.21)
	id <PS0R9RVS>; Fri, 20 Sep 2002 19:15:53 +0530
Message-ID: <195FE1D3531BD411A50F00B0D021783402908D76@golfmail.migv.mot.com>
From: VINAYA KUMAR KANDULA <kvinaya@migv.mot.com>
To: sip@ietf.org
Date: Fri, 20 Sep 2002 19:13:50 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C260AB.C62DD804"
Subject: [Sip] Regarding the  to tag field in the ACK
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

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_001_01C260AB.C62DD804
Content-Type: text/plain;
	charset="iso-8859-1"

	Hi ,		

		I have a doubt Regarding the to tag field in the ACK .

		In RFC 3261 in section  17.1.1.3 Construction of the ACK
Request 
	It was said that The To  header field in the ACK must be  equal to
the To header field in the
	  response being acknowledged . 

	Suppose If the ACK contains the to tag field different from the one
in the ok message sent by the user agent 
	what will be the action taken by the user agent . whether it has to
reject this ACK and send ok messages 
	or it has to send any other message saying that ACK has wrong to tag
.


	And also Suppose If the ACK does not contains the to tag at all
.what will be the action taken by the user agent . 




   F1 INVITE User A -> User B

   INVITE sip:UserB@there.com SIP/2.0
   Via: SIP/2.0/UDP here.com:5060
   From: BigGuy <sip:UserA@here.com>
   To: LittleGuy <sip:UserB@there.com>
   Call-ID: 12345601@here.com
   CSeq: 1 INVITE
   Contact: <sip:UserA@100.101.102.103>
   Content-Type: application/sdp
   Content-Length: 147

   v=0
   o=UserA 2890844526 2890844526 IN IP4 here.com
   s=Session SDP
   c=IN IP4 100.101.102.103
   t=0 0
   m=audio 49172 RTP/AVP 0
   a=rtpmap:0 PCMU/8000


   F2 (100 Trying) User B -> User A

   SIP/2.0 100 Trying
   Via: SIP/2.0/UDP here.com:5060
   From: BigGuy <sip:UserA@here.com>
   To: LittleGuy <sip:UserB@there.com>
   Call-ID: 12345601@here.com
   CSeq: 1 INVITE
   Content-Length: 0


   F3 180 Ringing User B -> User A

   SIP/2.0 180 Ringing
   Via: SIP/2.0/UDP here.com:5060
   From: BigGuy <sip:UserA@here.com>
   To: LittleGuy <sip:UserB@there.com>;tag=8321234356
   Call-ID: 12345601@here.com
   CSeq: 1 INVITE
   Content-Length: 0


   F4 200 OK User B -> User A

   SIP/2.0 200 OK
   Via: SIP/2.0/UDP here.com:5060
   From: BigGuy <sip:UserA@here.com>
   To: LittleGuy <sip:UserB@there.com>;tag=8321234356
   Call-ID: 12345601@here.com
   CSeq: 1 INVITE
   Contact: <sip:UserB@110.111.112.113>
   Content-Type: application/sdp
   Content-Length: 147

   v=0
   o=UserB 2890844527 2890844527 IN IP4 there.com
   s=Session SDP
   c=IN IP4 110.111.112.113
   t=0 0
   m=audio 3456 RTP/AVP 0
   a=rtpmap:0 PCMU/8000


   F5 ACK User A -> User B

   ACK sip:UserB@there.com SIP/2.0
   Via: SIP/2.0/UDP here.com:5060
   From: BigGuy <sip:UserA@here.com>
   To: LittleGuy <sip:UserB@there.com>;tag=6534123232   
   Call-ID: 12345601@here.com
   CSeq: 1 ACK


------_=_NextPart_001_01C260AB.C62DD804
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>Regarding the  to tag field in the ACK </TITLE>
</HEAD>
<BODY>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Hi ,&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">I have a doubt Regarding the to tag field in the ACK =
.</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">In RFC 3261 in section&nbsp; 17.1.1.3 Construction of =
the ACK Request </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">It was said that The To&nbsp; header field in the ACK =
must be&nbsp; equal to the To header field in the</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp; response being acknowledged . </FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Suppose If the ACK contains the to tag field different =
from the one in the ok message sent by the user agent </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">what will be the action taken by the user agent . =
whether it has to reject this ACK and send ok messages </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">or it has to send any other message saying that ACK has =
wrong to tag .</FONT>
</P>
<BR>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">And also Suppose If the ACK does not contains the to tag =
at all .what will be the action taken by the user agent . </FONT></P>
<BR>
<BR>
<BR>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; F1 INVITE User A -&gt; =
User B</FONT></B>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; INVITE =
sip:UserB@there.com SIP/2.0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Via: SIP/2.0/UDP =
here.com:5060</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; From: BigGuy =
&lt;sip:UserA@here.com&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; To: LittleGuy =
&lt;sip:UserB@there.com&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Call-ID: =
12345601@here.com</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; CSeq: 1 =
INVITE</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Contact: =
&lt;sip:UserA@100.101.102.103&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Content-Type: =
application/sdp</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Content-Length: =
147</FONT></B>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; v=3D0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o=3DUserA 2890844526 =
2890844526 IN IP4 here.com</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; s=3DSession =
SDP</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; c=3DIN IP4 =
100.101.102.103</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; t=3D0 0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; m=3Daudio 49172 =
RTP/AVP 0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; a=3Drtpmap:0 =
PCMU/8000</FONT></B>
</P>
<BR>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; F2 (100 Trying) User B =
-&gt; User A</FONT></B>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; SIP/2.0 100 =
Trying</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Via: SIP/2.0/UDP =
here.com:5060</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; From: BigGuy =
&lt;sip:UserA@here.com&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; To: LittleGuy =
&lt;sip:UserB@there.com&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Call-ID: =
12345601@here.com</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; CSeq: 1 =
INVITE</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Content-Length: =
0</FONT></B>
</P>
<BR>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; F3 180 Ringing User B =
-&gt; User A</FONT></B>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; SIP/2.0 180 =
Ringing</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Via: SIP/2.0/UDP =
here.com:5060</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; From: BigGuy =
&lt;sip:UserA@here.com&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; To: LittleGuy =
&lt;sip:UserB@there.com&gt;;tag=3D8321234356</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Call-ID: =
12345601@here.com</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; CSeq: 1 =
INVITE</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Content-Length: =
0</FONT></B>
</P>
<BR>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; F4 200 OK User B -&gt; =
User A</FONT></B>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; SIP/2.0 200 =
OK</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Via: SIP/2.0/UDP =
here.com:5060</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; From: BigGuy =
&lt;sip:UserA@here.com&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; To: LittleGuy =
&lt;sip:UserB@there.com&gt;;tag=3D8321234356</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Call-ID: =
12345601@here.com</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; CSeq: 1 =
INVITE</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Contact: =
&lt;sip:UserB@110.111.112.113&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Content-Type: =
application/sdp</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Content-Length: =
147</FONT></B>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; v=3D0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o=3DUserB 2890844527 =
2890844527 IN IP4 there.com</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; s=3DSession =
SDP</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; c=3DIN IP4 =
110.111.112.113</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; t=3D0 0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; m=3Daudio 3456 =
RTP/AVP 0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; a=3Drtpmap:0 =
PCMU/8000</FONT></B>
</P>
<BR>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; F5 ACK User A -&gt; =
User B</FONT></B>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; ACK =
sip:UserB@there.com SIP/2.0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Via: SIP/2.0/UDP =
here.com:5060</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; From: BigGuy =
&lt;sip:UserA@here.com&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; To: LittleGuy =
&lt;sip:UserB@there.com&gt;;tag=3D6534123232&nbsp;&nbsp; </FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Call-ID: =
12345601@here.com</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; CSeq: 1 =
ACK</FONT></B>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C260AB.C62DD804--
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Fri Sep 20 11:19:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25813
	for <sip-archive@odin.ietf.org>; Fri, 20 Sep 2002 11:19:50 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8KFLBb04983
	for sip-archive@odin.ietf.org; Fri, 20 Sep 2002 11:21:11 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KFKjv04950;
	Fri, 20 Sep 2002 11:20:45 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KFJEv04864
	for <sip@optimus.ietf.org>; Fri, 20 Sep 2002 11:19:14 -0400
Received: from broadsoft.com (broadsoft.com [198.104.184.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25756
	for <sip@ietf.org>; Fri, 20 Sep 2002 11:17:23 -0400 (EDT)
Received: from tate (host4.brodsoft.com [66.160.10.4] (may be forged)) by broadsoft.com (8.11.6) id g8KFJBa36466; Fri, 20 Sep 2002 11:19:11 -0400 (EDT)
Reply-To: <brett@broadsoft.com>
From: "Brett Tate" <brett@broadsoft.com>
To: <sip@ietf.org>
Subject: RE: [Sip] Regarding the  to tag field in the ACK
Date: Fri, 20 Sep 2002 11:22:35 -0400
Message-ID: <000b01c260b9$8cf97490$2b01a8c0@broadsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
In-Reply-To: <195FE1D3531BD411A50F00B0D021783402908D76@golfmail.migv.mot.com>
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> In RFC 3261 in section 17.1.1.3 
> Construction of the ACK Request, 
> it was said that The To header field 
> in the ACK must be equal to the 
> To header field in the response 
> being acknowledged. 
>
> Suppose If the ACK contains the 
> to tag field different from the 
> one in the ok message sent by the 
> user agent, what will be the action 
> taken by the user agent. whether 
> it has to reject this ACK and 
> send ok messages or it has to send 
> any other message saying that ACK 
> has wrong to tag . 

The ACK does not match the response.
The response should continue to retry.

> And also Suppose If the ACK does not 
> contains the to tag at all .
> what will be the action taken by the 
> user agent. 

The ACK does not match the response.
The response should continue to retry.

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



From mailnull@www1.ietf.org  Fri Sep 20 12:57:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29627
	for <sip-archive@odin.ietf.org>; Fri, 20 Sep 2002 12:57:54 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8KGxGb10470
	for sip-archive@odin.ietf.org; Fri, 20 Sep 2002 12:59:16 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KGw5v10415;
	Fri, 20 Sep 2002 12:58:05 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KGuGv10316
	for <sip@optimus.ietf.org>; Fri, 20 Sep 2002 12:56:16 -0400
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29523
	for <sip@ietf.org>; Fri, 20 Sep 2002 12:54:24 -0400 (EDT)
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate.mot.com (motgate 2.1) with ESMTP id GAA16238 for <sip@ietf.org>; Fri, 20 Sep 2002 06:59:11 -0700 (MST)]
Received: [from nadhi.migv.mot.com ([217.2.42.15]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id GAA00059 for <sip@ietf.org>; Fri, 20 Sep 2002 06:56:26 -0700 (MST)]
Received: from golfmail.migv.mot.com (golfmail.migv.mot.com [217.2.42.13])
	by migv.mot.com (8.9.3/8.9.3) with ESMTP id TAA08703
	for <sip@ietf.org>; Fri, 20 Sep 2002 19:30:48 +0530 (IST)
Received: by golfmail.migv.mot.com with Internet Mail Service (5.5.2650.21)
	id <PS0R9RWM>; Fri, 20 Sep 2002 19:25:23 +0530
Message-ID: <195FE1D3531BD411A50F00B0D021783402908D78@golfmail.migv.mot.com>
From: VINAYA KUMAR KANDULA <kvinaya@migv.mot.com>
To: "'sip@ietf.org'" <sip@ietf.org>
Date: Fri, 20 Sep 2002 19:25:00 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C260AD.55E4B6BA"
Subject: [Sip] Regarding the to tag field in the ACK
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

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_001_01C260AD.55E4B6BA
Content-Type: text/plain;
	charset="iso-8859-1"

	Hi ,		

		I have a doubt Regarding the to tag field in the ACK .

		In RFC 3261 in section  17.1.1.3 Construction of the ACK
Request 
	It was said that The To  header field in the ACK must be  equal to
the To header field in the
	  response being acknowledged . 

	Suppose If the ACK contains the to tag field different from the one
in the ok message sent by the user agent 
	what will be the action taken by the user agent . whether it has to
reject this ACK and send ok messages 
	or it has to send any other message saying that ACK has wrong to tag
.


	And also Suppose If the ACK does not contains the to tag at all
.what will be the action taken by the user agent . 




   F1 INVITE User A -> User B

   INVITE sip:UserB@there.com SIP/2.0
   Via: SIP/2.0/UDP here.com:5060
   From: BigGuy <sip:UserA@here.com>
   To: LittleGuy <sip:UserB@there.com>
   Call-ID: 12345601@here.com
   CSeq: 1 INVITE
   Contact: <sip:UserA@100.101.102.103>
   Content-Type: application/sdp
   Content-Length: 147

   v=0
   o=UserA 2890844526 2890844526 IN IP4 here.com
   s=Session SDP
   c=IN IP4 100.101.102.103
   t=0 0
   m=audio 49172 RTP/AVP 0
   a=rtpmap:0 PCMU/8000


   F2 (100 Trying) User B -> User A

   SIP/2.0 100 Trying
   Via: SIP/2.0/UDP here.com:5060
   From: BigGuy <sip:UserA@here.com>
   To: LittleGuy <sip:UserB@there.com>
   Call-ID: 12345601@here.com
   CSeq: 1 INVITE
   Content-Length: 0


   F3 180 Ringing User B -> User A

   SIP/2.0 180 Ringing
   Via: SIP/2.0/UDP here.com:5060
   From: BigGuy <sip:UserA@here.com>
   To: LittleGuy <sip:UserB@there.com>;tag=8321234356
   Call-ID: 12345601@here.com
   CSeq: 1 INVITE
   Content-Length: 0


   F4 200 OK User B -> User A

   SIP/2.0 200 OK
   Via: SIP/2.0/UDP here.com:5060
   From: BigGuy <sip:UserA@here.com>
   To: LittleGuy <sip:UserB@there.com>;tag=8321234356
   Call-ID: 12345601@here.com
   CSeq: 1 INVITE
   Contact: <sip:UserB@110.111.112.113>
   Content-Type: application/sdp
   Content-Length: 147

   v=0
   o=UserB 2890844527 2890844527 IN IP4 there.com
   s=Session SDP
   c=IN IP4 110.111.112.113
   t=0 0
   m=audio 3456 RTP/AVP 0
   a=rtpmap:0 PCMU/8000


   F5 ACK User A -> User B

   ACK sip:UserB@there.com SIP/2.0
   Via: SIP/2.0/UDP here.com:5060
   From: BigGuy <sip:UserA@here.com>
   To: LittleGuy <sip:UserB@there.com>;tag=6534123232   
   Call-ID: 12345601@here.com
   CSeq: 1 ACK



------_=_NextPart_001_01C260AD.55E4B6BA
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>Regarding the to tag field in the ACK </TITLE>
</HEAD>
<BODY>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Hi ,&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">I have a doubt Regarding the to tag field in the ACK =
.</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">In RFC 3261 in section&nbsp; 17.1.1.3 Construction of =
the ACK Request </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">It was said that The To&nbsp; header field in the ACK =
must be&nbsp; equal to the To header field in the</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">&nbsp; response being acknowledged . </FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">Suppose If the ACK contains the to tag field different =
from the one in the ok message sent by the user agent </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">what will be the action taken by the user agent . =
whether it has to reject this ACK and send ok messages </FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">or it has to send any other message saying that ACK has =
wrong to tag .</FONT>
</P>
<BR>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2 =
FACE=3D"Arial">And also Suppose If the ACK does not contains the to tag =
at all .what will be the action taken by the user agent . </FONT></P>
<BR>
<BR>
<BR>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; F1 INVITE User A -&gt; =
User B</FONT></B>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; INVITE =
sip:UserB@there.com SIP/2.0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Via: SIP/2.0/UDP =
here.com:5060</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; From: BigGuy =
&lt;sip:UserA@here.com&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; To: LittleGuy =
&lt;sip:UserB@there.com&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Call-ID: =
12345601@here.com</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; CSeq: 1 =
INVITE</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Contact: =
&lt;sip:UserA@100.101.102.103&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Content-Type: =
application/sdp</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Content-Length: =
147</FONT></B>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; v=3D0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o=3DUserA 2890844526 =
2890844526 IN IP4 here.com</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; s=3DSession =
SDP</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; c=3DIN IP4 =
100.101.102.103</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; t=3D0 0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; m=3Daudio 49172 =
RTP/AVP 0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; a=3Drtpmap:0 =
PCMU/8000</FONT></B>
</P>
<BR>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; F2 (100 Trying) User B =
-&gt; User A</FONT></B>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; SIP/2.0 100 =
Trying</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Via: SIP/2.0/UDP =
here.com:5060</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; From: BigGuy =
&lt;sip:UserA@here.com&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; To: LittleGuy =
&lt;sip:UserB@there.com&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Call-ID: =
12345601@here.com</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; CSeq: 1 =
INVITE</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Content-Length: =
0</FONT></B>
</P>
<BR>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; F3 180 Ringing User B =
-&gt; User A</FONT></B>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; SIP/2.0 180 =
Ringing</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Via: SIP/2.0/UDP =
here.com:5060</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; From: BigGuy =
&lt;sip:UserA@here.com&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; To: LittleGuy =
&lt;sip:UserB@there.com&gt;;tag=3D8321234356</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Call-ID: =
12345601@here.com</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; CSeq: 1 =
INVITE</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Content-Length: =
0</FONT></B>
</P>
<BR>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; F4 200 OK User B -&gt; =
User A</FONT></B>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; SIP/2.0 200 =
OK</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Via: SIP/2.0/UDP =
here.com:5060</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; From: BigGuy =
&lt;sip:UserA@here.com&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; To: LittleGuy =
&lt;sip:UserB@there.com&gt;;tag=3D8321234356</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Call-ID: =
12345601@here.com</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; CSeq: 1 =
INVITE</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Contact: =
&lt;sip:UserB@110.111.112.113&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Content-Type: =
application/sdp</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Content-Length: =
147</FONT></B>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; v=3D0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; o=3DUserB 2890844527 =
2890844527 IN IP4 there.com</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; s=3DSession =
SDP</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; c=3DIN IP4 =
110.111.112.113</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; t=3D0 0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; m=3Daudio 3456 =
RTP/AVP 0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; a=3Drtpmap:0 =
PCMU/8000</FONT></B>
</P>
<BR>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; F5 ACK User A -&gt; =
User B</FONT></B>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; ACK =
sip:UserB@there.com SIP/2.0</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Via: SIP/2.0/UDP =
here.com:5060</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; From: BigGuy =
&lt;sip:UserA@here.com&gt;</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; To: LittleGuy =
&lt;sip:UserB@there.com&gt;;tag=3D6534123232&nbsp;&nbsp; </FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Call-ID: =
12345601@here.com</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; CSeq: 1 =
ACK</FONT></B>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C260AD.55E4B6BA--
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Fri Sep 20 14:37:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03783
	for <sip-archive@odin.ietf.org>; Fri, 20 Sep 2002 14:37:29 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8KIcqd16596
	for sip-archive@odin.ietf.org; Fri, 20 Sep 2002 14:38:52 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KIcTv16583;
	Fri, 20 Sep 2002 14:38:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KIb5v16089
	for <sip@optimus.ietf.org>; Fri, 20 Sep 2002 14:37:05 -0400
Received: from sj_ntserver3.sj.nuera.com (h-207-20-110-62.ncal.verio.net [207.20.110.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03685
	for <sip@ietf.org>; Fri, 20 Sep 2002 14:35:11 -0400 (EDT)
Received: by sj_ntserver3.sj.nuera.com with Internet Mail Service (5.5.2653.19)
	id <SWLZCVGR>; Fri, 20 Sep 2002 11:37:24 -0700
Message-ID: <DD70FD1C981BD411B64400508BA547C15B430E@sj_ntserver3.sj.nuera.com>
From: "Srivastava, Samir" <SSrivastava@nuera.com>
To: "'VINAYA KUMAR KANDULA'" <kvinaya@migv.mot.com>,
        "'sip@ietf.org'"
	 <sip@ietf.org>
Subject: RE: [Sip] Regarding the to tag field in the ACK
Date: Fri, 20 Sep 2002 11:37:24 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C260D4.C2FABA20"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

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_001_01C260D4.C2FABA20
Content-Type: text/plain;
	charset="iso-8859-1"

As per RFC 3261, INVITE MUST have the "From" tag. Which is not given in your
message flow.
While your other UA is 3261 compliant, providing it's tag. It's also
backward compatible with
older UA's (RFC 2543) which may not give the TAG, as it is accepting the REQ
and in the  
 RSP giving the TO-TAG.
 
The originating UA should copy the Complete TO field including the Tag in
the RSP. If remote side
is supporting complete backward compatibility with older RFC 2543, It can
accept the ACK without
 the tag. It depends how much it is backward compatible.
 
Thx
Samir

-----Original Message-----
From: VINAYA KUMAR KANDULA [mailto:kvinaya@migv.mot.com]
Sent: Friday, September 20, 2002 6:55 AM
To: 'sip@ietf.org'
Subject: [Sip] Regarding the to tag field in the ACK



        Hi ,            

                I have a doubt Regarding the to tag field in the ACK . 

                In RFC 3261 in section  17.1.1.3 Construction of the ACK
Request 
        It was said that The To  header field in the ACK must be  equal to
the To header field in the 
          response being acknowledged . 

        Suppose If the ACK contains the to tag field different from the one
in the ok message sent by the user agent 
        what will be the action taken by the user agent . whether it has to
reject this ACK and send ok messages 
        or it has to send any other message saying that ACK has wrong to tag
. 


        And also Suppose If the ACK does not contains the to tag at all
.what will be the action taken by the user agent . 




   F1 INVITE User A -> User B 

   INVITE sip:UserB@there.com SIP/2.0 
   Via: SIP/2.0/UDP here.com:5060 
   From: BigGuy <sip:UserA@here.com> 
   To: LittleGuy <sip:UserB@there.com> 
   Call-ID: 12345601@here.com 
   CSeq: 1 INVITE 
   Contact: <sip:UserA@100.101.102.103> 
   Content-Type: application/sdp 
   Content-Length: 147 

   v=0 
   o=UserA 2890844526 2890844526 IN IP4 here.com 
   s=Session SDP 
   c=IN IP4 100.101.102.103 
   t=0 0 
   m=audio 49172 RTP/AVP 0 
   a=rtpmap:0 PCMU/8000 


   F2 (100 Trying) User B -> User A 

   SIP/2.0 100 Trying 
   Via: SIP/2.0/UDP here.com:5060 
   From: BigGuy <sip:UserA@here.com> 
   To: LittleGuy <sip:UserB@there.com> 
   Call-ID: 12345601@here.com 
   CSeq: 1 INVITE 
   Content-Length: 0 


   F3 180 Ringing User B -> User A 

   SIP/2.0 180 Ringing 
   Via: SIP/2.0/UDP here.com:5060 
   From: BigGuy <sip:UserA@here.com> 
   To: LittleGuy <sip:UserB@there.com>;tag=8321234356 
   Call-ID: 12345601@here.com 
   CSeq: 1 INVITE 
   Content-Length: 0 


   F4 200 OK User B -> User A 

   SIP/2.0 200 OK 
   Via: SIP/2.0/UDP here.com:5060 
   From: BigGuy <sip:UserA@here.com> 
   To: LittleGuy <sip:UserB@there.com>;tag=8321234356 
   Call-ID: 12345601@here.com 
   CSeq: 1 INVITE 
   Contact: <sip:UserB@110.111.112.113> 
   Content-Type: application/sdp 
   Content-Length: 147 

   v=0 
   o=UserB 2890844527 2890844527 IN IP4 there.com 
   s=Session SDP 
   c=IN IP4 110.111.112.113 
   t=0 0 
   m=audio 3456 RTP/AVP 0 
   a=rtpmap:0 PCMU/8000 


   F5 ACK User A -> User B 

   ACK sip:UserB@there.com SIP/2.0 
   Via: SIP/2.0/UDP here.com:5060 
   From: BigGuy <sip:UserA@here.com> 
   To: LittleGuy <sip:UserB@there.com>;tag=6534123232   
   Call-ID: 12345601@here.com 
   CSeq: 1 ACK 



------_=_NextPart_001_01C260D4.C2FABA20
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Regarding the to tag field in the ACK</TITLE>

<META content="MSHTML 5.50.4522.1800" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=177421118-20092002><FONT face=Arial color=#0000ff size=2>As per 
RFC 3261, INVITE MUST have the "From" tag. Which is not given in your message 
flow.</FONT></SPAN></DIV>
<DIV><SPAN class=177421118-20092002><FONT face=Arial color=#0000ff size=2>While 
your other UA is 3261 compliant, providing it's tag. It's also backward 
compatible with</FONT></SPAN></DIV>
<DIV><SPAN class=177421118-20092002><FONT face=Arial color=#0000ff size=2>older 
UA's (RFC 2543) which&nbsp;may not&nbsp;give the TAG, a</FONT></SPAN><SPAN 
class=177421118-20092002><FONT face=Arial color=#0000ff size=2>s it is accepting 
the REQ and in the&nbsp; </FONT></SPAN></DIV>
<DIV><SPAN class=177421118-20092002><FONT face=Arial color=#0000ff 
size=2>&nbsp;RSP giving the TO-TAG.</FONT></SPAN></DIV>
<DIV><SPAN class=177421118-20092002><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=177421118-20092002><FONT face=Arial color=#0000ff size=2>The 
originating UA should copy the Complete TO field including the Tag in the RSP. 
If&nbsp;remote side</FONT></SPAN></DIV>
<DIV><SPAN class=177421118-20092002><FONT face=Arial color=#0000ff size=2>is 
supporting complete backward compatibility with older RFC 2543, It&nbsp;can 
accept the ACK without</FONT></SPAN></DIV>
<DIV><SPAN class=177421118-20092002></SPAN><SPAN class=177421118-20092002><FONT 
face=Arial color=#0000ff size=2>&nbsp;the </FONT></SPAN><SPAN 
class=177421118-20092002><FONT face=Arial color=#0000ff size=2>tag. It depends 
how much it is backward compatible.</FONT></SPAN></DIV>
<DIV><SPAN class=177421118-20092002><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=177421118-20092002><FONT face=Arial color=#0000ff 
size=2>Thx</FONT></SPAN></DIV>
<DIV><SPAN class=177421118-20092002><FONT face=Arial color=#0000ff 
size=2>Samir</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> VINAYA KUMAR KANDULA 
  [mailto:kvinaya@migv.mot.com]<BR><B>Sent:</B> Friday, September 20, 2002 6:55 
  AM<BR><B>To:</B> 'sip@ietf.org'<BR><B>Subject:</B> [Sip] Regarding the to tag 
  field in the ACK<BR><BR></FONT></DIV>
  <P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT face=Arial size=2>Hi 
  ,&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT></P>
  <P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT face=Arial size=2>I have a 
  doubt Regarding the to tag field in the ACK .</FONT> </P>
  <P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT face=Arial size=2>In RFC 3261 
  in section&nbsp; 17.1.1.3 Construction of the ACK Request 
  </FONT><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT face=Arial 
  size=2>It was said that The To&nbsp; header field in the ACK must be&nbsp; 
  equal to the To header field in the</FONT> 
  <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT face=Arial size=2>&nbsp; 
  response being acknowledged . </FONT></P>
  <P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT face=Arial size=2>Suppose 
  If the ACK contains the to tag field different from the one in the ok message 
  sent by the user agent </FONT><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  <FONT face=Arial size=2>what will be the action taken by the user agent . 
  whether it has to reject this ACK and send ok messages 
  </FONT><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT face=Arial 
  size=2>or it has to send any other message saying that ACK has wrong to tag 
  .</FONT> </P><BR>
  <P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT face=Arial size=2>And also 
  Suppose If the ACK does not contains the to tag at all .what will be the 
  action taken by the user agent . </FONT></P><BR><BR><BR>
  <P><B><FONT face=Arial size=2>&nbsp;&nbsp; F1 INVITE User A -&gt; User 
  B</FONT></B> </P>
  <P><B><FONT face=Arial size=2>&nbsp;&nbsp; INVITE sip:UserB@there.com 
  SIP/2.0</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; Via: 
  SIP/2.0/UDP here.com:5060</FONT></B> <BR><B><FONT face=Arial 
  size=2>&nbsp;&nbsp; From: BigGuy &lt;sip:UserA@here.com&gt;</FONT></B> 
  <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; To: LittleGuy 
  &lt;sip:UserB@there.com&gt;</FONT></B> <BR><B><FONT face=Arial 
  size=2>&nbsp;&nbsp; Call-ID: 12345601@here.com</FONT></B> <BR><B><FONT 
  face=Arial size=2>&nbsp;&nbsp; CSeq: 1 INVITE</FONT></B> <BR><B><FONT 
  face=Arial size=2>&nbsp;&nbsp; Contact: 
  &lt;sip:UserA@100.101.102.103&gt;</FONT></B> <BR><B><FONT face=Arial 
  size=2>&nbsp;&nbsp; Content-Type: application/sdp</FONT></B> <BR><B><FONT 
  face=Arial size=2>&nbsp;&nbsp; Content-Length: 147</FONT></B> </P>
  <P><B><FONT face=Arial size=2>&nbsp;&nbsp; v=0</FONT></B> <BR><B><FONT 
  face=Arial size=2>&nbsp;&nbsp; o=UserA 2890844526 2890844526 IN IP4 
  here.com</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; s=Session 
  SDP</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; c=IN IP4 
  100.101.102.103</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; t=0 
  0</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; m=audio 49172 RTP/AVP 
  0</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; a=rtpmap:0 
  PCMU/8000</FONT></B> </P><BR>
  <P><B><FONT face=Arial size=2>&nbsp;&nbsp; F2 (100 Trying) User B -&gt; User 
  A</FONT></B> </P>
  <P><B><FONT face=Arial size=2>&nbsp;&nbsp; SIP/2.0 100 Trying</FONT></B> 
  <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; Via: SIP/2.0/UDP 
  here.com:5060</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; From: 
  BigGuy &lt;sip:UserA@here.com&gt;</FONT></B> <BR><B><FONT face=Arial 
  size=2>&nbsp;&nbsp; To: LittleGuy &lt;sip:UserB@there.com&gt;</FONT></B> 
  <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; Call-ID: 
  12345601@here.com</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; CSeq: 
  1 INVITE</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; 
  Content-Length: 0</FONT></B> </P><BR>
  <P><B><FONT face=Arial size=2>&nbsp;&nbsp; F3 180 Ringing User B -&gt; User 
  A</FONT></B> </P>
  <P><B><FONT face=Arial size=2>&nbsp;&nbsp; SIP/2.0 180 Ringing</FONT></B> 
  <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; Via: SIP/2.0/UDP 
  here.com:5060</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; From: 
  BigGuy &lt;sip:UserA@here.com&gt;</FONT></B> <BR><B><FONT face=Arial 
  size=2>&nbsp;&nbsp; To: LittleGuy 
  &lt;sip:UserB@there.com&gt;;tag=8321234356</FONT></B> <BR><B><FONT face=Arial 
  size=2>&nbsp;&nbsp; Call-ID: 12345601@here.com</FONT></B> <BR><B><FONT 
  face=Arial size=2>&nbsp;&nbsp; CSeq: 1 INVITE</FONT></B> <BR><B><FONT 
  face=Arial size=2>&nbsp;&nbsp; Content-Length: 0</FONT></B> </P><BR>
  <P><B><FONT face=Arial size=2>&nbsp;&nbsp; F4 200 OK User B -&gt; User 
  A</FONT></B> </P>
  <P><B><FONT face=Arial size=2>&nbsp;&nbsp; SIP/2.0 200 OK</FONT></B> 
  <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; Via: SIP/2.0/UDP 
  here.com:5060</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; From: 
  BigGuy &lt;sip:UserA@here.com&gt;</FONT></B> <BR><B><FONT face=Arial 
  size=2>&nbsp;&nbsp; To: LittleGuy 
  &lt;sip:UserB@there.com&gt;;tag=8321234356</FONT></B> <BR><B><FONT face=Arial 
  size=2>&nbsp;&nbsp; Call-ID: 12345601@here.com</FONT></B> <BR><B><FONT 
  face=Arial size=2>&nbsp;&nbsp; CSeq: 1 INVITE</FONT></B> <BR><B><FONT 
  face=Arial size=2>&nbsp;&nbsp; Contact: 
  &lt;sip:UserB@110.111.112.113&gt;</FONT></B> <BR><B><FONT face=Arial 
  size=2>&nbsp;&nbsp; Content-Type: application/sdp</FONT></B> <BR><B><FONT 
  face=Arial size=2>&nbsp;&nbsp; Content-Length: 147</FONT></B> </P>
  <P><B><FONT face=Arial size=2>&nbsp;&nbsp; v=0</FONT></B> <BR><B><FONT 
  face=Arial size=2>&nbsp;&nbsp; o=UserB 2890844527 2890844527 IN IP4 
  there.com</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; s=Session 
  SDP</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; c=IN IP4 
  110.111.112.113</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; t=0 
  0</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; m=audio 3456 RTP/AVP 
  0</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; a=rtpmap:0 
  PCMU/8000</FONT></B> </P><BR>
  <P><B><FONT face=Arial size=2>&nbsp;&nbsp; F5 ACK User A -&gt; User 
  B</FONT></B> </P>
  <P><B><FONT face=Arial size=2>&nbsp;&nbsp; ACK sip:UserB@there.com 
  SIP/2.0</FONT></B> <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; Via: 
  SIP/2.0/UDP here.com:5060</FONT></B> <BR><B><FONT face=Arial 
  size=2>&nbsp;&nbsp; From: BigGuy &lt;sip:UserA@here.com&gt;</FONT></B> 
  <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; To: LittleGuy 
  &lt;sip:UserB@there.com&gt;;tag=6534123232&nbsp;&nbsp; </FONT></B><BR><B><FONT 
  face=Arial size=2>&nbsp;&nbsp; Call-ID: 12345601@here.com</FONT></B> 
  <BR><B><FONT face=Arial size=2>&nbsp;&nbsp; CSeq: 1 ACK</FONT></B> 
</P><BR></BLOCKQUOTE></BODY></HTML>

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



From mailnull@www1.ietf.org  Fri Sep 20 15:13:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04827
	for <sip-archive@odin.ietf.org>; Fri, 20 Sep 2002 15:13:50 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8KJFDS18209
	for sip-archive@odin.ietf.org; Fri, 20 Sep 2002 15:15:13 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KJEqv18180;
	Fri, 20 Sep 2002 15:14:53 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KJDbv18153
	for <sip@optimus.ietf.org>; Fri, 20 Sep 2002 15:13:37 -0400
Received: from sj_ntserver3.sj.nuera.com (h-207-20-110-62.ncal.verio.net [207.20.110.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04803
	for <sip@ietf.org>; Fri, 20 Sep 2002 15:11:43 -0400 (EDT)
Received: by sj_ntserver3.sj.nuera.com with Internet Mail Service (5.5.2653.19)
	id <SWLZCV2F>; Fri, 20 Sep 2002 12:13:56 -0700
Message-ID: <DD70FD1C981BD411B64400508BA547C15B430F@sj_ntserver3.sj.nuera.com>
From: "Srivastava, Samir" <SSrivastava@nuera.com>
To: "'ABDUL SATTAR SHAIK'" <abdulss@migv.mot.com>,
        "'sip@ietf.org'"
	 <sip@ietf.org>
Subject: RE: [Sip] Branch in  INVITE ,ACK,BYE
Date: Fri, 20 Sep 2002 12:13:55 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C260D9.DD4C9AB0"
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

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_001_01C260D9.DD4C9AB0
Content-Type: text/plain;
	charset="iso-8859-1"

ACK for 2XX is different Transaction. 
While ACK for non 2xx final responses is the part of same INVITE
transaction. 
Therefore ACK for the 2xx is having different Branch ID.
 
Thx
Samir

-----Original Message-----
From: ABDUL SATTAR SHAIK [mailto:abdulss@migv.mot.com]
Sent: Friday, September 20, 2002 5:49 AM
To: 'sip@ietf.org'
Subject: [Sip] Branch in INVITE ,ACK,BYE



The branch parameter  should change with each request send by UAC  or per
Transaction Basis. If it is on transaction  basis INVITE and ACK should have
same branch parameter

In RFC 3261 Examples The branch parameter is different for  INVITE and ACK
message sent By UAC 

 24.2 Session Setup 

   This example contains the full details of the example session setup 
   in Section 4.  The message flow is shown in Figure 1.  Note that 
   these flows show the minimum required set of header fields - some 
   other header fields such as Allow and Supported would normally be 
   present. 

F1 INVITE Alice -> atlanta.com proxy 

INVITE sip:bob@biloxi.com SIP/2.0 
Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bKnashds8 
Max-Forwards: 70 
To: Bob <sip:bob@biloxi.com> 
From: Alice <sip:alice@atlanta.com>;tag=1928301774 
Call-ID: a84b4c76e66710 
CSeq: 314159 INVITE 
Contact: <sip:alice@pc33.atlanta.com> 
Content-Type: application/sdp 
Content-Length: 142 

(Alice's SDP not shown) 


ACK sip:bob@192.0.2.4 SIP/2.0 
Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bKnashds9 
Max-Forwards: 70 
To: Bob <sip:bob@biloxi.com>;tag=a6c85cf 
From: Alice <sip:alice@atlanta.com>;tag=1928301774 
Call-ID: a84b4c76e66710 
CSeq: 314159 ACK 
Content-Length: 0 


Thanks in Advance 
Abdul Sattar 


------_=_NextPart_001_01C260D9.DD4C9AB0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Branch in INVITE ,ACK,BYE</TITLE>

<META content="MSHTML 5.50.4522.1800" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=868031119-20092002><FONT face=Arial color=#0000ff size=2>ACK 
for 2XX is different Transaction. </FONT></SPAN></DIV>
<DIV><SPAN class=868031119-20092002><FONT face=Arial color=#0000ff size=2>While 
ACK for non 2xx final responses is the part of same INVITE transaction. 
</FONT></SPAN></DIV>
<DIV><SPAN class=868031119-20092002></SPAN><SPAN class=868031119-20092002><FONT 
face=Arial color=#0000ff size=2>Therefore ACK for the 2xx is having different 
Branch ID.</FONT></SPAN></DIV>
<DIV><SPAN class=868031119-20092002><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=868031119-20092002><FONT face=Arial color=#0000ff 
size=2>Thx</FONT></SPAN></DIV>
<DIV><SPAN class=868031119-20092002><FONT face=Arial color=#0000ff 
size=2>Samir</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> ABDUL SATTAR SHAIK 
  [mailto:abdulss@migv.mot.com]<BR><B>Sent:</B> Friday, September 20, 2002 5:49 
  AM<BR><B>To:</B> 'sip@ietf.org'<BR><B>Subject:</B> [Sip] Branch in INVITE 
  ,ACK,BYE<BR><BR></FONT></DIV>
  <P><FONT face=Arial size=2>The branch parameter&nbsp; should change with each 
  request send by UAC&nbsp; or per&nbsp; Transaction Basis. If it is on 
  transaction&nbsp; basis INVITE and ACK should have same branch 
  parameter</FONT></P>
  <P><FONT face=Arial size=2>In RFC 3261 Examples The branch parameter is 
  different for&nbsp; INVITE and ACK message sent By UAC</FONT> </P>
  <P><FONT face=Arial size=2>&nbsp;24.2 Session Setup</FONT> </P>
  <P><FONT face=Arial size=2>&nbsp;&nbsp; This example contains the full details 
  of the example session setup</FONT> <BR><FONT face=Arial size=2>&nbsp;&nbsp; 
  in Section 4.&nbsp; The message flow is shown in Figure 1.&nbsp; Note 
  that</FONT> <BR><FONT face=Arial size=2>&nbsp;&nbsp; these flows show the 
  minimum required set of header fields - some</FONT> <BR><FONT face=Arial 
  size=2>&nbsp;&nbsp; other header fields such as Allow and Supported would 
  normally be</FONT> <BR><FONT face=Arial size=2>&nbsp;&nbsp; present.</FONT> 
  </P>
  <P><FONT face=Arial size=2>F1 INVITE Alice -&gt; atlanta.com proxy</FONT> </P>
  <P><FONT face=Arial size=2>INVITE sip:bob@biloxi.com SIP/2.0</FONT> <BR><FONT 
  face=Arial size=2>Via: SIP/2.0/UDP 
  pc33.atlanta.com;branch=z9hG4bKnashds8</FONT> <BR><FONT face=Arial 
  size=2>Max-Forwards: 70</FONT> <BR><FONT face=Arial size=2>To: Bob 
  &lt;sip:bob@biloxi.com&gt;</FONT> <BR><FONT face=Arial size=2>From: Alice 
  &lt;sip:alice@atlanta.com&gt;;tag=1928301774</FONT> <BR><FONT face=Arial 
  size=2>Call-ID: a84b4c76e66710</FONT> <BR><FONT face=Arial size=2>CSeq: 314159 
  INVITE</FONT> <BR><FONT face=Arial size=2>Contact: 
  &lt;sip:alice@pc33.atlanta.com&gt;</FONT> <BR><FONT face=Arial 
  size=2>Content-Type: application/sdp</FONT> <BR><FONT face=Arial 
  size=2>Content-Length: 142</FONT> </P>
  <P><FONT face=Arial size=2>(Alice's SDP not shown)</FONT> </P><BR>
  <P><FONT face=Arial size=2>ACK sip:bob@192.0.2.4 SIP/2.0</FONT> <BR><FONT 
  face=Arial size=2>Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bKnashds9 
  </FONT><BR><FONT face=Arial size=2>Max-Forwards: 70</FONT> <BR><FONT 
  face=Arial size=2>To: Bob &lt;sip:bob@biloxi.com&gt;;tag=a6c85cf</FONT> 
  <BR><FONT face=Arial size=2>From: Alice 
  &lt;sip:alice@atlanta.com&gt;;tag=1928301774</FONT> <BR><FONT face=Arial 
  size=2>Call-ID: a84b4c76e66710</FONT> <BR><FONT face=Arial size=2>CSeq: 314159 
  ACK</FONT> <BR><FONT face=Arial size=2>Content-Length: 0</FONT> </P><BR>
  <P><FONT face=Arial size=2>Thanks in Advance</FONT> <BR><FONT face=Arial 
  size=2>Abdul Sattar</FONT> </P></BLOCKQUOTE></BODY></HTML>

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



From mailnull@www1.ietf.org  Fri Sep 20 17:05:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08379
	for <sip-archive@odin.ietf.org>; Fri, 20 Sep 2002 17:05:44 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8KL77J23849
	for sip-archive@odin.ietf.org; Fri, 20 Sep 2002 17:07:07 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KL6mv23586;
	Fri, 20 Sep 2002 17:06:48 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KL3Tv23395
	for <sip@optimus.ietf.org>; Fri, 20 Sep 2002 17:03:29 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08202;
	Fri, 20 Sep 2002 17:01:32 -0400 (EDT)
Message-Id: <200209202101.RAA08202@ietf.org>
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>, Internet Architecture Board <iab@iab.org>,
        sip@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Date: Fri, 20 Sep 2002 17:01:32 -0400
Subject: [Sip] Protocol Action: Session Initiation Protocol Extension for
 Instant Messaging to Proposed Standard
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>



The IESG has approved the Internet-Draft 'Session Initiation Protocol
Extension for Instant Messaging' <draft-ietf-sip-message-07.txt> as a
Proposed Standard.  This document is the product of the Session
Initiation Protocol Working Group.  The IESG contact persons are
Allison Mankin and Scott Bradner.

 
Technical Summary
 
  RFC 2778 and RFC 2779 give a model and requirements for presence
  and instant messaging protocols. The Session Initiation Protocol
  (RFC 3261) provides mechanisms that are useful for presence
  applicatons, and for session-oriented communication applications.
  This document specifies a new method for SIP called MESSAGE, which
  adds an instant message mechanism as well, fulfilling
  RFC 2779. This IM mechanism is intended for pager style use,
  in which a MESSAGE carries a short text, or message/cpim body,
  as a stand-alone communication, rather than a stream of connected
  data, in a "session mode." The SIMPLE working group is currently
  working to understand the session model more fully and determine
  how SIMPLE should best support it (for instance with multiple
  types of session modes).
   
Working Group Summary
   
  The requirements for this specification originated in the
  IMPP and SIMPLE Working Groups, and then the protocol
  extension was completed by SIP. The major point of contention
  was to ensure that MESSAGE did not become a congestion-prone
  transport-replacement, taking advantage of SIP's original ability
  to run over UDP. Fortunately, beginning with RFC 3261, any SIP
  message with a large payload is likely to use TCP for its transport.
  The MESSAGE specification achieved strong working group and
  Transport area consensus after vigorous discussion of its first
  few revisions.

Protocol Quality
   
    Allison Mankin reviewed the specification for the IESG.
    Several early commercial implementations have been identified.


Note to RFC Editor:

Please make the following changes:

Before the Introduction, add an unnumbered section -

Terminology

      In this document, the key words "MUST", "MUST NOT", "REQUIRED",
      "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT
      RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as
      described in BCP 14, RFC 2119 and indicate requirement levels for
      compliant SIP implementations.

-------
References

Add RFC 2119 to Normative references.


-------

11. Security Considerations

Old:

      In particular, UAs that
      support the MESSAGE request SHOULD support end-to-end authentication,
      body integrity, and body confidentiality mechanisms.
New:

      In particular, UAs that
      support the MESSAGE request MUST implement end-to-end authentication,
      body integrity, and body confidentiality mechanisms.

------
11.1 Outbound authentication

Old:
      When local proxies are used for transmission of outbound messages,
      proxy authentication is RECOMMENDED. This is useful to verify the
      identity of the originator, and prevent spoofing and spamming at the
      originating network.

New:
      When local proxies are used for transmission of outbound messages,
      proxy authentication, as specified in RFC 3261, is RECOMMENDED. 
      This is useful to verify the identity of the originator, and prevent
      spoofing and spamming at the originating network.

------
11.3 End-to-End Protection

Old:
      To alleviate the concerns stated above, the MESSAGE bodies SHOULD be
      secured with S/MIME.

New:

      For remedying the concerns stated above, the MESSAGE bodies
      MUST be secured with S/MIME. If bodies specified in future to be
      carried by the MESSAGE method have different means of providing
      end-to-end security, their specification MUST describe the usage.
-------

11.4 Replay Prevention

OLD:
   To prevent the replay of old SIP requests, all signed MESSAGE
   requests and responses SHOULD contain a Date header field covered by
   the message signature.


NEW:

   To prevent the replay of old SIP requests, all signed MESSAGE
   requests and responses MUST contain a Date header field covered by
   the message signature.
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Fri Sep 20 18:24:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11932
	for <sip-archive@odin.ietf.org>; Fri, 20 Sep 2002 18:24:32 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8KMPuo29691
	for sip-archive@odin.ietf.org; Fri, 20 Sep 2002 18:25:56 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KMOlv29587;
	Fri, 20 Sep 2002 18:24:47 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KMLhv29458
	for <sip@optimus.ietf.org>; Fri, 20 Sep 2002 18:21:43 -0400
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11685;
	Fri, 20 Sep 2002 18:19:47 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
	by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8KMLYD24227;
	Fri, 20 Sep 2002 15:21:34 -0700 (PDT)
Message-Id: <200209202221.g8KMLYD24227@gamma.isi.edu>
To: IETF-Announce: ;
Cc: rfc-editor@rfc-editor.org, sip@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Fri, 20 Sep 2002 15:21:34 -0700
Subject: [Sip] RFC 3310 on Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 3310

        Title:	    Hypertext Transfer Protocol (HTTP) Digest
                    Authentication Using Authentication and Key
                    Agreement (AKA) 
        Author(s):  A. Niemi, J. Arkko, V. Torvinen
        Status:	    Informational
	Date:       September 2002
        Mailbox:    aki.niemi@nokia.com, jari.arkko@ericsson.com,
                    vesa.torvinen@ericsson.fi 
        Pages:      18
        Characters: 36985
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sip-digest-aka-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3310.txt


This memo specifies an Authentication and Key Agreement (AKA) based
one-time password generation mechanism for Hypertext Transfer Protocol
(HTTP) Digest access authentication.  The HTTP Authentication
Framework includes two authentication schemes: Basic and Digest.  Both
schemes employ a shared secret based mechanism for access
authentication.  The AKA mechanism performs user authentication and
session key distribution in Universal Mobile Telecommunications System
(UMTS) networks.  AKA is a challenge-response based mechanism that
uses symmetric cryptography.

This document is a product of the Session Initiation Protocol Working
Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <020920151959.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3310

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc3310.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <020920151959.RFC@RFC-EDITOR.ORG>

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



From mailnull@www1.ietf.org  Sat Sep 21 09:27:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11016
	for <sip-archive@odin.ietf.org>; Sat, 21 Sep 2002 09:27:25 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8LDSkE07869
	for sip-archive@odin.ietf.org; Sat, 21 Sep 2002 09:28:46 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8LDS1v07833;
	Sat, 21 Sep 2002 09:28:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8LDOUv07718
	for <sip@optimus.ietf.org>; Sat, 21 Sep 2002 09:24:30 -0400
Received: from motgate4.mot.com (motgate4.mot.com [144.189.100.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10961
	for <sip@ietf.org>; Sat, 21 Sep 2002 09:22:39 -0400 (EDT)
Received: [from pobox4.mot.com (pobox4.mot.com [10.64.251.243]) by motgate4.mot.com (motgate4 2.1) with ESMTP id GAA18531 for <sip@ietf.org>; Sat, 21 Sep 2002 06:24:27 -0700 (MST)]
Received: [from nadhi.migv.mot.com ([217.2.42.15]) by pobox4.mot.com (MOT-pobox4 2.0) with ESMTP id GAA09224 for <sip@ietf.org>; Sat, 21 Sep 2002 06:24:25 -0700 (MST)]
Received: from golfmail.migv.mot.com (golfmail.migv.mot.com [217.2.42.13])
	by migv.mot.com (8.9.3/8.9.3) with ESMTP id SAA22443
	for <sip@ietf.org>; Sat, 21 Sep 2002 18:59:49 +0530 (IST)
Received: by golfmail.migv.mot.com with Internet Mail Service (5.5.2650.21)
	id <PS0R9TYM>; Sat, 21 Sep 2002 18:54:23 +0530
Message-ID: <195FE1D3531BD411A50F00B0D021783402907CA6@golfmail.migv.mot.com>
From: ABDUL SATTAR SHAIK <abdulss@migv.mot.com>
To: "'sip@ietf.org'" <sip@ietf.org>
Date: Sat, 21 Sep 2002 18:53:23 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C26172.13BB7114"
Subject: [Sip] URI's in To and StartLine in ACK Messages
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

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_001_01C26172.13BB7114
Content-Type: text/plain;
	charset="iso-8859-1"

Hi
Consider Scenario
UAC -> UAS


UAC sends  INVITE with URI 's   LittleGuy@there.com in both startline and To
Header Field.

After receiving  OK, UAC sends  ACK with URI   LittleGuy@there.com in To
Header Field
    and SmallGuy@there.com   in Startline. Whether UAS  should  accept ACK
or reject  with   error. 

Thanks
Abdul Sattar                                 

------_=_NextPart_001_01C26172.13BB7114
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>URI's in To and StartLine in ACK Messages</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Consider Scenario</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">UAC -&gt; UAS</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">UAC sends&nbsp; INVITE with URI =
's&nbsp;&nbsp; LittleGuy@there.com in both startline and To Header =
Field.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">After receiving&nbsp; OK, UAC =
sends&nbsp; ACK with URI&nbsp;&nbsp; LittleGuy@there.com in To Header =
Field</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp; and =
SmallGuy@there.com&nbsp;&nbsp; in Startline. Whether UAS&nbsp; =
should&nbsp; accept ACK or reject&nbsp; with&nbsp;&nbsp; error. </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Abdul =
Sattar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C26172.13BB7114--
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Sat Sep 21 16:08:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16688
	for <sip-archive@odin.ietf.org>; Sat, 21 Sep 2002 16:08:54 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8LKAJJ23244
	for sip-archive@odin.ietf.org; Sat, 21 Sep 2002 16:10:19 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8LK9fv23212;
	Sat, 21 Sep 2002 16:09:42 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8LK7Qv23164
	for <sip@optimus.ietf.org>; Sat, 21 Sep 2002 16:07:26 -0400
Received: from broadsoft.com (broadsoft.com [198.104.184.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16662
	for <sip@ietf.org>; Sat, 21 Sep 2002 16:05:31 -0400 (EDT)
Received: from tate (host4.brodsoft.com [66.160.10.4] (may be forged)) by broadsoft.com (8.11.6) id g8KDOes29176; Fri, 20 Sep 2002 09:24:40 -0400 (EDT)
Reply-To: <brett@broadsoft.com>
From: "Brett Tate" <brett@broadsoft.com>
To: "'ABDUL SATTAR SHAIK'" <abdulss@migv.mot.com>, <sip@ietf.org>
Subject: RE: [Sip] Branch in  INVITE ,ACK,BYE
Date: Fri, 20 Sep 2002 09:28:04 -0400
Message-ID: <000501c260a9$8d7db300$2b01a8c0@broadsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
In-Reply-To: <195FE1D3531BD411A50F00B0D021783402907C9A@golfmail.migv.mot.com>
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> The branch parameter should change with 
> each request send by UAC or per 
> Transaction Basis. 

It is per transaction.

> If it is on transaction basis INVITE and ACK 
> should have same branch parameter

The ACK is a special case.  The ACK's branch
changes for 2xx response; the ACK's branch
remains the same for other final responses.

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



From mailnull@www1.ietf.org  Sat Sep 21 23:56:14 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22231
	for <sip-archive@odin.ietf.org>; Sat, 21 Sep 2002 23:56:13 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8M3veH06844
	for sip-archive@odin.ietf.org; Sat, 21 Sep 2002 23:57:40 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8M3ulv06823;
	Sat, 21 Sep 2002 23:56:47 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8M3svv06782
	for <sip@optimus.ietf.org>; Sat, 21 Sep 2002 23:54:57 -0400
Received: from hclnpd.hclt.co.in ([202.54.64.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22206
	for <sip@ietf.org>; Sat, 21 Sep 2002 23:52:59 -0400 (EDT)
Received: from blaze.hcltech.com (blaze.hclt-ntl.co.in [192.168.19.30]) by hclnpd.hclt.co.in with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id SP90RZ0X; Sun, 22 Sep 2002 09:24:21 +0530
Received: from sachinhome ([192.168.19.43])
	by blaze.hcltech.com (8.9.3/8.9.3) with SMTP id JAA27136
	for <sip@ietf.org>; Sun, 22 Sep 2002 09:53:05 +0530
Message-ID: <002301c261ed$57f654e0$a5f1fea9@sachinhome>
From: "Sachin Shenoy" <sachins@netlab.hcltech.com>
To: <sip@ietf.org>
References: <4.3.2.7.0.20020919150512.00e96920@blaze>
Subject: Re: [Sip] BranchID in CANCEL & INVITE
Date: Sat, 21 Sep 2002 20:42:35 +0530
Organization: HCL Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Someone please help me with this.

Thanks
Sachin

> Hi,
> This is regarding branches in CANCEL & INVITE.
>
> Section 9.1 of RFC says
>
> "9.1 Client Behavior
> ...
> The CANCEL request MUST NOT contain any Require or Proxy-Require header
> fields."
>
>
> Consider the following scenario
> UAC sends INVITE to P1.
> P1 forwards it statlessley to UAS.
> UAC sends CANCEL to P1 (to cancel the INVITE).
> P1 forwards CANCEL also to UAS.
>
> Let INVITE request have Proxy-Require header.
>
> While handling INVITE at proxy,
> P1 calculates the VIA's loop-detection part using the Proxy-Require
header.
> (The unique part would be calculated using a combinatronic function.) So
the
> INVITE's VIA would reflect the contents of the proxy-require header.
>
> While handling CANCEL at proxy,
> P1 calculates the VIA's loop-detection part without the Proxy-Require
header,
> As CANCEL would not have it.
>
> At UAS:
> INVITE & CANCEL would have different top-most via branches.
>
> But according to RFC they have to have the same branches for the UAS to
> match the CANCEL & INVITE properly.
>
> "9.1 Client Behavior
> ...
> A CANCEL constructed by a client MUST have only a single Via header field
> value matching the top Via value in the request being cancelled.  Using
the
> same
> values for these header fields allows the CANCEL to be matched with the
> request it cancels (Section 9.2 indicates how such matching occurs)."
>
> Is it that Stateless proxies are not supposed to do loop-detection?
>
> I thought the idea of having loop-detection part in branch-id was to
> allow proxies to detect loop even while being stateless. If only stateful
> proxies were to do loop-detection, we wouldn't have required the hash
> to be kept in the message at all.
>
> Thanks in advance
> Sachin
>
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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



From mailnull@www1.ietf.org  Sun Sep 22 23:41:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18502
	for <sip-archive@odin.ietf.org>; Sun, 22 Sep 2002 23:41:32 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8N3h1508017
	for sip-archive@odin.ietf.org; Sun, 22 Sep 2002 23:43:01 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N3evv07958;
	Sun, 22 Sep 2002 23:40:57 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N3Xbv07207
	for <sip@optimus.ietf.org>; Sun, 22 Sep 2002 23:33:37 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18397
	for <sip@ietf.org>; Sun, 22 Sep 2002 23:31:35 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2V007CZGJS7T@mta2.huawei.com> for sip@ietf.org; Mon,
 23 Sep 2002 11:33:29 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2V007DMGJR82@mta2.huawei.com> for sip@ietf.org; Mon,
 23 Sep 2002 11:33:28 +0800 (CST)
Received: from himanshoo ([10.18.5.112])
 by mailin.huawei.com (Netscape Messaging Server 4.15)
 with ESMTP id H2VGLA01.B06; Mon, 23 Sep 2002 11:34:22 +0800
Date: Mon, 23 Sep 2002 08:56:02 +0530
From: Himanshoo Ks <himanshooks@huawei.com>
In-reply-to: <002301c261ed$57f654e0$a5f1fea9@sachinhome>
To: sip@ietf.org, sip-implementors@cs.columbia.edu
Message-id: <000001c262b0$f2271950$7005120a@himanshoo>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Subject: [Sip] SIP INFO
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Hi,

This is with reference to the SIP INFO Method defined in RFC2976.
SIP INFO method is used for sending mid call signaling information. The way
information is sent by a UAC to UAS is clear. But I have one basic question:
1. How does the UAC generating this INFO message know that the UAS is
ineterested in knowing that event.
2. Also we have SUBSCRIBE/NOTIFY messages in SIP which can be used to
subscribe for soem information and then report the same. So in what way is
INFO different than these ..
Could somebody please answer these questions ?

regards
Himanshoo

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



From mailnull@www1.ietf.org  Mon Sep 23 00:50:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19554
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 00:50:35 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8N4q3G10418
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 00:52:03 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N4jvv10332;
	Mon, 23 Sep 2002 00:45:57 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N4f0v10228
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 00:41:00 -0400
Received: from btlmail.bplmail.com ([203.200.31.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19431
	for <sip@ietf.org>; Mon, 23 Sep 2002 00:39:01 -0400 (EDT)
Received: from [10.10.13.95] (helo=ranjit)
	by btlmail.bplmail.com with smtp (Exim 3.22 #1 (Red Hat Linux))
	id 17tL3m-0007Ki-00; Mon, 23 Sep 2002 10:13:02 +0530
Reply-To: <ranjit.avasarala@bplmail.com>
From: "Ranjit Avasarala" <ranjit.avasarala@bplmail.com>
To: "Himanshoo Ks" <himanshooks@huawei.com>, <sip@ietf.org>,
        <sip-implementors@cs.columbia.edu>
Subject: RE: [Sip] SIP INFO
Date: Wed, 18 Sep 2002 10:10:28 +0530
Message-ID: <FEEJJMJJLHGIMEGAPBJJAEFKCAAA.ranjit.avasarala@bplmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
In-Reply-To: <000001c262b0$f2271950$7005120a@himanshoo>
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Himanshoo

SUBSCRIBE / NOTIFY methods are used to register for specific events like
call fowrward, automatic call back , etc.

while INFO method is used to convey mid session information. The INFO method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not.

Ranjit :-)

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of
Himanshoo Ks
Sent: Monday, September 23, 2002 8:56 AM
To: sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip] SIP INFO


Hi,

This is with reference to the SIP INFO Method defined in RFC2976.
SIP INFO method is used for sending mid call signaling information. The way
information is sent by a UAC to UAS is clear. But I have one basic question:
1. How does the UAC generating this INFO message know that the UAS is
ineterested in knowing that event.
2. Also we have SUBSCRIBE/NOTIFY messages in SIP which can be used to
subscribe for soem information and then report the same. So in what way is
INFO different than these ..
Could somebody please answer these questions ?

regards
Himanshoo

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

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



From mailnull@www1.ietf.org  Mon Sep 23 01:04:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19736
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 01:04:38 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8N566710746
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 01:06:06 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N55iv10710;
	Mon, 23 Sep 2002 01:05:44 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N535v10648
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 01:03:05 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19675
	for <sip@ietf.org>; Mon, 23 Sep 2002 01:01:01 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2V00FOXKOS29@mta2.huawei.com> for sip@ietf.org; Mon,
 23 Sep 2002 13:02:53 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2V00FSOKOR2L@mta2.huawei.com> for sip@ietf.org; Mon,
 23 Sep 2002 13:02:52 +0800 (CST)
Received: from himanshoo ([10.18.5.112])
 by mailin.huawei.com (Netscape Messaging Server 4.15)
 with ESMTP id H2VKQA01.90B; Mon, 23 Sep 2002 13:03:46 +0800
Date: Mon, 23 Sep 2002 10:25:27 +0530
From: Himanshoo Ks <himanshooks@huawei.com>
Subject: RE: [Sip] SIP INFO
In-reply-to: <FEEJJMJJLHGIMEGAPBJJAEFKCAAA.ranjit.avasarala@bplmail.com>
To: ranjit.avasarala@bplmail.com, sip@ietf.org,
        sip-implementors@cs.columbia.edu
Message-id: <000001c262bd$6f57a0f0$7005120a@himanshoo>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Your mail says that:

"while INFO method is used to convey mid session information. The INFO
method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not."

If UAS can't tell what information it is interested in, then what is the use
of INFO method...

Also, then how does UAC decide which information to send.

regards
Himanshoo
-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 10:10 AM
To: Himanshoo Ks; sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: RE: [Sip] SIP INFO


Hi Himanshoo

SUBSCRIBE / NOTIFY methods are used to register for specific events like
call fowrward, automatic call back , etc.

while INFO method is used to convey mid session information. The INFO method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not.

Ranjit :-)

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of
Himanshoo Ks
Sent: Monday, September 23, 2002 8:56 AM
To: sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip] SIP INFO


Hi,

This is with reference to the SIP INFO Method defined in RFC2976.
SIP INFO method is used for sending mid call signaling information. The way
information is sent by a UAC to UAS is clear. But I have one basic question:
1. How does the UAC generating this INFO message know that the UAS is
ineterested in knowing that event.
2. Also we have SUBSCRIBE/NOTIFY messages in SIP which can be used to
subscribe for soem information and then report the same. So in what way is
INFO different than these ..
Could somebody please answer these questions ?

regards
Himanshoo

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

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

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



From mailnull@www1.ietf.org  Mon Sep 23 01:15:13 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19904
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 01:15:13 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8N5Gf311550
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 01:16:41 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N5GFv11536;
	Mon, 23 Sep 2002 01:16:15 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N5Eov11495
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 01:14:50 -0400
Received: from mta0 ([61.144.161.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19885
	for <sip@ietf.org>; Mon, 23 Sep 2002 01:12:49 -0400 (EDT)
Received: from P70008 (mta0 [172.17.1.62])
 by mta0.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.8 (built Jul 12
 2002)) with ESMTPA id <0H2V00EV4L4KPB@mta0.huawei.com> for sip@ietf.org; Mon,
 23 Sep 2002 13:12:22 +0800 (CST)
Date: Mon, 23 Sep 2002 13:17:52 +0800
From: Prasanna <prasanna@huawei.com>
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO
In-reply-to: <000001c262bd$6f57a0f0$7005120a@himanshoo>
To: Himanshoo Ks <himanshooks@huawei.com>, ranjit.avasarala@bplmail.com,
        sip@ietf.org, sip-implementors@cs.columbia.edu
Message-id: <KPEPLFDHIJPLNICJNCJJMEFLCCAA.prasanna@huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Hi Himanshoo,
	While it is theoritically possible to generate a complete Event framework
of INFO methods, the SUBSCRIBE / NOTIFY methods provide the formal Event
framework for SIP.
	As Ranjit had mentioned, INFO conveys optional extra information and in the
case of INFO, the UAC does not care if the UAS requires it or not.  The
precise difference lies in this point.  In the Event framework, the UAC
(Notifier) caters to what the UAS (Subscriber) requires, while the INFO
mechanism is adhoc.
	As in case of SIP-T like applications, where INFO is used, the UAS may drop
the message totally, while in the case of NOTIFICATIONs it is not expected
to do that, as he requested the notification.
Regards,
Prasanna

-----Original Message-----
From: sip-implementors-admin@cs.columbia.edu
[mailto:sip-implementors-admin@cs.columbia.edu]On Behalf Of Himanshoo Ks
Sent: Monday, September 23, 2002 12:55 PM
To: ranjit.avasarala@bplmail.com; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] RE: [Sip] SIP INFO


Your mail says that:

"while INFO method is used to convey mid session information. The INFO
method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not."

If UAS can't tell what information it is interested in, then what is the use
of INFO method...

Also, then how does UAC decide which information to send.

regards
Himanshoo
-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 10:10 AM
To: Himanshoo Ks; sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: RE: [Sip] SIP INFO


Hi Himanshoo

SUBSCRIBE / NOTIFY methods are used to register for specific events like
call fowrward, automatic call back , etc.

while INFO method is used to convey mid session information. The INFO method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not.

Ranjit :-)

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of
Himanshoo Ks
Sent: Monday, September 23, 2002 8:56 AM
To: sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip] SIP INFO


Hi,

This is with reference to the SIP INFO Method defined in RFC2976.
SIP INFO method is used for sending mid call signaling information. The way
information is sent by a UAC to UAS is clear. But I have one basic question:
1. How does the UAC generating this INFO message know that the UAS is
ineterested in knowing that event.
2. Also we have SUBSCRIBE/NOTIFY messages in SIP which can be used to
subscribe for soem information and then report the same. So in what way is
INFO different than these ..
Could somebody please answer these questions ?

regards
Himanshoo

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

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

_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

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



From mailnull@www1.ietf.org  Mon Sep 23 01:26:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20282
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 01:26:25 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8N5RrO11799
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 01:27:53 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N5R2v11776;
	Mon, 23 Sep 2002 01:27:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N5Pav11755
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 01:25:36 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20249
	for <sip@ietf.org>; Mon, 23 Sep 2002 01:23:35 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2V00F8ALQN29@mta2.huawei.com> for sip@ietf.org; Mon,
 23 Sep 2002 13:25:36 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2V00F6HLQM2L@mta2.huawei.com> for sip@ietf.org; Mon,
 23 Sep 2002 13:25:35 +0800 (CST)
Received: from himanshoo ([10.18.5.112])
 by mailin.huawei.com (Netscape Messaging Server 4.15)
 with ESMTP id H2VLS600.I0G; Mon, 23 Sep 2002 13:26:30 +0800
Date: Mon, 23 Sep 2002 10:48:10 +0530
From: Himanshoo Ks <himanshooks@huawei.com>
In-reply-to: <FEEJJMJJLHGIMEGAPBJJAEFKCAAA.ranjit.avasarala@bplmail.com>
To: sip@ietf.org, sip-implementors@cs.columbia.edu
Message-id: <000101c262c0$9c8f11e0$7005120a@himanshoo>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Subject: [Sip] draft-culpepper-sip-info-event-00.txt
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Hi,

I have a question on draft-culpepper-sip-info-event-00.txt:

1. It says that MGCP subtype can be used to indicate the protocol between
MGC and MG and then some MGCP message can be encapsulated to request and
report the events as per MGCP packages. Does this mean that I can send the
complete command line ( I mean whole of RQNT) as message body for the INFO
request. It is needed since I also need to identify the end point where I
want event to be detected.

2. And more importantly, as per the date mentioned ni draft, this draft has
expired on October 2000. Is there some other draft / RFC which is taing care
of there issues ? Should I refer to some other document for finding solution
to this problem.

regards
Himanshoo

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



From mailnull@www1.ietf.org  Mon Sep 23 01:41:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20506
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 01:41:55 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8N5hNw12724
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 01:43:23 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N5h2v12713;
	Mon, 23 Sep 2002 01:43:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N5fAv12664
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 01:41:10 -0400
Received: from btlmail.bplmail.com ([203.200.31.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20439
	for <sip@ietf.org>; Mon, 23 Sep 2002 01:39:06 -0400 (EDT)
Received: from [10.10.13.95] (helo=ranjit)
	by btlmail.bplmail.com with smtp (Exim 3.22 #1 (Red Hat Linux))
	id 17tLzu-00007M-00; Mon, 23 Sep 2002 11:13:06 +0530
Reply-To: <ranjit.avasarala@bplmail.com>
From: "Ranjit Avasarala" <ranjit.avasarala@bplmail.com>
To: "Himanshoo Ks" <himanshooks@huawei.com>, <sip@ietf.org>,
        <sip-implementors@cs.columbia.edu>
Subject: RE: [Sip] SIP INFO
Date: Wed, 18 Sep 2002 11:10:32 +0530
Message-ID: <FEEJJMJJLHGIMEGAPBJJKEFOCAAA.ranjit.avasarala@bplmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <000001c262bd$6f57a0f0$7005120a@himanshoo>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Himanshoo

  if there is any extra info to be conveyed to UAS, then UAC generates INFO
request and sends it to UAS. but if UAS is not interested in the info, then
UAS can respond with "487 Request Cancelled" response.

HTH
Ranjit :-)

-----Original Message-----
From: Himanshoo Ks [mailto:himanshooks@huawei.com]
Sent: Monday, September 23, 2002 10:25 AM
To: ranjit.avasarala@bplmail.com; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip] SIP INFO


Your mail says that:

"while INFO method is used to convey mid session information. The INFO
method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not."

If UAS can't tell what information it is interested in, then what is the use
of INFO method...

Also, then how does UAC decide which information to send.

regards
Himanshoo
-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 10:10 AM
To: Himanshoo Ks; sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: RE: [Sip] SIP INFO


Hi Himanshoo

SUBSCRIBE / NOTIFY methods are used to register for specific events like
call fowrward, automatic call back , etc.

while INFO method is used to convey mid session information. The INFO method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not.

Ranjit :-)

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of
Himanshoo Ks
Sent: Monday, September 23, 2002 8:56 AM
To: sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip] SIP INFO


Hi,

This is with reference to the SIP INFO Method defined in RFC2976.
SIP INFO method is used for sending mid call signaling information. The way
information is sent by a UAC to UAS is clear. But I have one basic question:
1. How does the UAC generating this INFO message know that the UAS is
ineterested in knowing that event.
2. Also we have SUBSCRIBE/NOTIFY messages in SIP which can be used to
subscribe for soem information and then report the same. So in what way is
INFO different than these ..
Could somebody please answer these questions ?

regards
Himanshoo

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

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

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



From mailnull@www1.ietf.org  Mon Sep 23 01:56:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20705
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 01:56:39 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8N5w7M12946
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 01:58:07 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N5vfv12936;
	Mon, 23 Sep 2002 01:57:41 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N5skv12883
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 01:54:46 -0400
Received: from mta0 ([61.144.161.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20653
	for <sip@ietf.org>; Mon, 23 Sep 2002 01:52:44 -0400 (EDT)
Received: from P70008 (mta0 [172.17.1.62])
 by mta0.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.8 (built Jul 12
 2002)) with ESMTPA id <0H2V00EX1MZ7PB@mta0.huawei.com> for sip@ietf.org; Mon,
 23 Sep 2002 13:52:20 +0800 (CST)
Date: Mon, 23 Sep 2002 13:57:50 +0800
From: Prasanna <prasanna@huawei.com>
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO
In-reply-to: <FEEJJMJJLHGIMEGAPBJJKEFOCAAA.ranjit.avasarala@bplmail.com>
To: ranjit.avasarala@bplmail.com, Himanshoo Ks <himanshooks@huawei.com>,
        sip@ietf.org, sip-implementors@cs.columbia.edu
Message-id: <KPEPLFDHIJPLNICJNCJJOEFMCCAA.prasanna@huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

HI Ranjit,
	I do not believe 487 is a suitable response for such a condition.  As such
there is no response that is suitable that is usable in this case, but we
can respond with a 400 response.  But do we even have an agreement that this
is a client error!
Rgds,
Prasanna

-----Original Message-----
From: sip-implementors-admin@cs.columbia.edu
[mailto:sip-implementors-admin@cs.columbia.edu]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 1:41 PM
To: Himanshoo Ks; sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] RE: [Sip] SIP INFO


Hi Himanshoo

  if there is any extra info to be conveyed to UAS, then UAC generates INFO
request and sends it to UAS. but if UAS is not interested in the info, then
UAS can respond with "487 Request Cancelled" response.

HTH
Ranjit :-)

-----Original Message-----
From: Himanshoo Ks [mailto:himanshooks@huawei.com]
Sent: Monday, September 23, 2002 10:25 AM
To: ranjit.avasarala@bplmail.com; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip] SIP INFO


Your mail says that:

"while INFO method is used to convey mid session information. The INFO
method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not."

If UAS can't tell what information it is interested in, then what is the use
of INFO method...

Also, then how does UAC decide which information to send.

regards
Himanshoo
-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 10:10 AM
To: Himanshoo Ks; sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: RE: [Sip] SIP INFO


Hi Himanshoo

SUBSCRIBE / NOTIFY methods are used to register for specific events like
call fowrward, automatic call back , etc.

while INFO method is used to convey mid session information. The INFO method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not.

Ranjit :-)

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of
Himanshoo Ks
Sent: Monday, September 23, 2002 8:56 AM
To: sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip] SIP INFO


Hi,

This is with reference to the SIP INFO Method defined in RFC2976.
SIP INFO method is used for sending mid call signaling information. The way
information is sent by a UAC to UAS is clear. But I have one basic question:
1. How does the UAC generating this INFO message know that the UAS is
ineterested in knowing that event.
2. Also we have SUBSCRIBE/NOTIFY messages in SIP which can be used to
subscribe for soem information and then report the same. So in what way is
INFO different than these ..
Could somebody please answer these questions ?

regards
Himanshoo

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

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

_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

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



From mailnull@www1.ietf.org  Mon Sep 23 02:09:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00008
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 02:09:07 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8N6AaB18652
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 02:10:36 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N69Rv16419;
	Mon, 23 Sep 2002 02:09:27 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N62Kv13078
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 02:02:20 -0400
Received: from mailserv.intranet.gr (mailserv.intranet.GR [146.124.14.106])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21217;
	Mon, 23 Sep 2002 02:00:19 -0400 (EDT)
Received: from mailserv.intranet.gr (localhost [127.0.0.1])
	by mailserv.intranet.gr (8.11.3/8.11.3) with ESMTP id g8N62R425329;
	Mon, 23 Sep 2002 09:02:27 +0300 (EEST)
Received: from hal.intranet.gr (hal.intranet.GR [146.124.2.254])
	by mailserv.intranet.gr (8.11.3/8.11.3) with ESMTP id g8N62Qp25323;
	Mon, 23 Sep 2002 09:02:26 +0300 (EEST)
Received: from garfield (pcdpd217 [146.124.2.204])
	by hal.intranet.gr (8.10.2+Sun/8.10.2) with ESMTP id g8N5slN13554;
	Mon, 23 Sep 2002 08:54:47 +0300 (EEST)
From: "F.S.Salloum" <ssal@intracom.gr>
To: <sip@ietf.org>, <sipping@ietf.org>
Date: Mon, 23 Sep 2002 09:01:22 +0300
Message-ID: <NGBBLHKPJKCDNEIOOKKOGEIACEAA.ssal@intracom.gr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Sip] INAP and SIP INFO
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Dear All,

Is there a draft dealing with encapsulation of INAP messages with the SIP
info message ?

Regards,

F.S.Salloum

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



From mailnull@www1.ietf.org  Mon Sep 23 04:05:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01659
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 04:05:32 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8N873v27293
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 04:07:03 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N85Bv27164;
	Mon, 23 Sep 2002 04:05:11 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N83wv27092
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 04:03:58 -0400
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01583
	for <sip@ietf.org>; Mon, 23 Sep 2002 04:01:56 -0400 (EDT)
Received: from blues.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.227])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id KAA05107;
	Mon, 23 Sep 2002 10:03:39 +0200 (MET DST)
Received: from mchh169e.mch4.siemens.de ([139.21.130.176])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id KAA04473;
	Mon, 23 Sep 2002 10:03:40 +0200 (MET DST)
Received: by mchh169e.mch4.siemens.de with Internet Mail Service (5.5.2653.19)
	id <T24KJ78Q>; Mon, 23 Sep 2002 10:03:42 +0200
Message-ID: <5B4D0C5BA65ECA46969C1419122317E6E74F55@mchh161e>
From: Tan Ya-Ching  ICM N PG U ID A 1 <Ya-Ching.Tan@icn.siemens.de>
To: RFC Editor <rfc-editor@isi.edu>
Cc: sip@ietf.org
Subject: RE: [Sip] Protocol Action: Session Initiation Protocol Extension 
	for Instant Messaging to Proposed Standard
Date: Mon, 23 Sep 2002 10:03:16 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>



| -----Original Message-----
| From: The IESG [mailto:iesg-secretary@ietf.org]
| Sent: 20 September 2002 23:02
| Cc: RFC Editor; Internet Architecture Board; sip@ietf.org
| Subject: [Sip] Protocol Action: Session Initiation Protocol Extension
| for Instant Messaging to Proposed Standard
| 
| 
| 
| 
| The IESG has approved the Internet-Draft 'Session Initiation Protocol
| Extension for Instant Messaging' <draft-ietf-sip-message-07.txt> as a
| Proposed Standard.  This document is the product of the Session
| Initiation Protocol Working Group.  The IESG contact persons are
| Allison Mankin and Scott Bradner.
| 



Note to RFC Editor,

Table 1 and Table 2 of draft-ietf-sip-message-07 seem to be based on the
older version of SIP RFC.  Table 1 and Table 2 of RFC 3261 have the
following headers which are missing in the 07 draft :

Min-Expires
MIME-Version
Supported


Regards,
Ya-Ching Tan

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



From mailnull@www1.ietf.org  Mon Sep 23 04:09:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01740
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 04:09:07 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8N8AcB27928
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 04:10:38 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N88gv27850;
	Mon, 23 Sep 2002 04:08:42 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N85Xv27179
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 04:05:33 -0400
Received: from obsoft.com (sdsl-64-139-4-113.dsl.sca.megapath.net [64.139.4.113])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01624;
	Mon, 23 Sep 2002 04:03:31 -0400 (EDT)
Received: from obsoft.com (IDENT:dsardana@[192.168.1.4])
	by obsoft.com (8.11.6/8.11.6) with ESMTP id g8N8APa18576;
	Mon, 23 Sep 2002 01:10:26 -0700
Message-ID: <3D8ED007.D22638A2@obsoft.com>
Date: Mon, 23 Sep 2002 01:25:43 -0700
From: Bobby Sardana <sardana@obsoft.com>
Organization: ObjectSoftware, 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: "F.S.Salloum" <ssal@intracom.gr>
CC: sip@ietf.org, sipping@ietf.org
Subject: Re: [Sip] INAP and SIP INFO
References: <NGBBLHKPJKCDNEIOOKKOGEIACEAA.ssal@intracom.gr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Check out the following drafts:

1) SIP-IN Interworking Protocol Architecture and Procedures
(http://www.bell-labs.com/mailing-lists/ietf-sin/draft-gurbani-sin-00.txt)

2) Intelligent Network Application Part (INAP) Support of the SIP/SDP
Architecture
(http://www.bell-labs.com/mailing-lists/ietf-sin/draft-haerens-sip-inap-00.txt)

regards,

Bobby Sardana.
sardana@obsoft.com

"F.S.Salloum" wrote:

> Dear All,
>
> Is there a draft dealing with encapsulation of INAP messages with the SIP
> info message ?
>
> Regards,
>
> F.S.Salloum
>
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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



From mailnull@www1.ietf.org  Mon Sep 23 04:14:06 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01830
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 04:14:06 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8N8Fb928069
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 04:15:37 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N8ECv28030;
	Mon, 23 Sep 2002 04:14:12 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N8Dvv28011
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 04:13:57 -0400
Received: from btlmail.bplmail.com ([203.200.31.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01796
	for <sip@ietf.org>; Mon, 23 Sep 2002 04:11:55 -0400 (EDT)
Received: from [10.10.13.95] (helo=ranjit)
	by btlmail.bplmail.com with smtp (Exim 3.22 #1 (Red Hat Linux))
	id 17tONx-000313-00; Mon, 23 Sep 2002 13:46:05 +0530
Reply-To: <ranjit.avasarala@bplmail.com>
From: "Ranjit Avasarala" <ranjit.avasarala@bplmail.com>
To: "Prasanna" <prasanna@huawei.com>, "Himanshoo Ks" <himanshooks@huawei.com>,
        <sip@ietf.org>, <sip-implementors@cs.columbia.edu>
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO
Date: Wed, 18 Sep 2002 13:43:31 +0530
Message-ID: <FEEJJMJJLHGIMEGAPBJJOEGBCAAA.ranjit.avasarala@bplmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <KPEPLFDHIJPLNICJNCJJOEFMCCAA.prasanna@huawei.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

487 is ok be'se if UAS does not want to accept the INFO request, it will
cancel it. U cannot send 400 Bad Request be'se its not a bad request.

Ranjit :-)

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of
Prasanna
Sent: Monday, September 23, 2002 11:28 AM
To: ranjit.avasarala@bplmail.com; Himanshoo Ks; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


HI Ranjit,
	I do not believe 487 is a suitable response for such a condition.  As such
there is no response that is suitable that is usable in this case, but we
can respond with a 400 response.  But do we even have an agreement that this
is a client error!
Rgds,
Prasanna

-----Original Message-----
From: sip-implementors-admin@cs.columbia.edu
[mailto:sip-implementors-admin@cs.columbia.edu]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 1:41 PM
To: Himanshoo Ks; sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] RE: [Sip] SIP INFO


Hi Himanshoo

  if there is any extra info to be conveyed to UAS, then UAC generates INFO
request and sends it to UAS. but if UAS is not interested in the info, then
UAS can respond with "487 Request Cancelled" response.

HTH
Ranjit :-)

-----Original Message-----
From: Himanshoo Ks [mailto:himanshooks@huawei.com]
Sent: Monday, September 23, 2002 10:25 AM
To: ranjit.avasarala@bplmail.com; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip] SIP INFO


Your mail says that:

"while INFO method is used to convey mid session information. The INFO
method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not."

If UAS can't tell what information it is interested in, then what is the use
of INFO method...

Also, then how does UAC decide which information to send.

regards
Himanshoo
-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 10:10 AM
To: Himanshoo Ks; sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: RE: [Sip] SIP INFO


Hi Himanshoo

SUBSCRIBE / NOTIFY methods are used to register for specific events like
call fowrward, automatic call back , etc.

while INFO method is used to convey mid session information. The INFO method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not.

Ranjit :-)

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of
Himanshoo Ks
Sent: Monday, September 23, 2002 8:56 AM
To: sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip] SIP INFO


Hi,

This is with reference to the SIP INFO Method defined in RFC2976.
SIP INFO method is used for sending mid call signaling information. The way
information is sent by a UAC to UAS is clear. But I have one basic question:
1. How does the UAC generating this INFO message know that the UAS is
ineterested in knowing that event.
2. Also we have SUBSCRIBE/NOTIFY messages in SIP which can be used to
subscribe for soem information and then report the same. So in what way is
INFO different than these ..
Could somebody please answer these questions ?

regards
Himanshoo

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

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

_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

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

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



From mailnull@www1.ietf.org  Mon Sep 23 04:24:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01998
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 04:24:31 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8N8Q2l28334
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 04:26:02 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N8Onv28306;
	Mon, 23 Sep 2002 04:24:49 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N8Nvv28254
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 04:23:57 -0400
Received: from mta0 ([61.144.161.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01963
	for <sip@ietf.org>; Mon, 23 Sep 2002 04:21:49 -0400 (EDT)
Received: from P70008 (mta0 [172.17.1.62])
 by mta0.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.8 (built Jul 12
 2002)) with ESMTPA id <0H2V00H05TVIYH@mta0.huawei.com> for sip@ietf.org; Mon,
 23 Sep 2002 16:21:20 +0800 (CST)
Date: Mon, 23 Sep 2002 16:26:50 +0800
From: Prasanna <prasanna@huawei.com>
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO
In-reply-to: <FEEJJMJJLHGIMEGAPBJJOEGBCAAA.ranjit.avasarala@bplmail.com>
To: ranjit.avasarala@bplmail.com, Himanshoo Ks <himanshooks@huawei.com>,
        sip@ietf.org, sip-implementors@cs.columbia.edu
Message-id: <KPEPLFDHIJPLNICJNCJJAEGACCAA.prasanna@huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

As such 487 is sent when a cancellation of a request is triggered by the UAC
itself (conditions like CANCEL, expiration of the request), but I do not
believe that this is a UAC triggered cancellation.  I withdraw my suggestion
for a 400, for I am also not convinced if UAC behaves erroneously sending
this request or the server behaves erroneously by not able to understand
this.
Do we have a clarity if this is a client error or a server error?
-Prasanna

-----Original Message-----
From: Ranjit Avasarala [mailto:ranjit.avasarala@bplmail.com]
Sent: Wednesday, September 18, 2002 4:14 PM
To: Prasanna; Himanshoo Ks; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


487 is ok be'se if UAS does not want to accept the INFO request, it will
cancel it. U cannot send 400 Bad Request be'se its not a bad request.

Ranjit :-)

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of
Prasanna
Sent: Monday, September 23, 2002 11:28 AM
To: ranjit.avasarala@bplmail.com; Himanshoo Ks; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


HI Ranjit,
	I do not believe 487 is a suitable response for such a condition.  As such
there is no response that is suitable that is usable in this case, but we
can respond with a 400 response.  But do we even have an agreement that this
is a client error!
Rgds,
Prasanna

-----Original Message-----
From: sip-implementors-admin@cs.columbia.edu
[mailto:sip-implementors-admin@cs.columbia.edu]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 1:41 PM
To: Himanshoo Ks; sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] RE: [Sip] SIP INFO


Hi Himanshoo

  if there is any extra info to be conveyed to UAS, then UAC generates INFO
request and sends it to UAS. but if UAS is not interested in the info, then
UAS can respond with "487 Request Cancelled" response.

HTH
Ranjit :-)

-----Original Message-----
From: Himanshoo Ks [mailto:himanshooks@huawei.com]
Sent: Monday, September 23, 2002 10:25 AM
To: ranjit.avasarala@bplmail.com; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip] SIP INFO


Your mail says that:

"while INFO method is used to convey mid session information. The INFO
method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not."

If UAS can't tell what information it is interested in, then what is the use
of INFO method...

Also, then how does UAC decide which information to send.

regards
Himanshoo
-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 10:10 AM
To: Himanshoo Ks; sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: RE: [Sip] SIP INFO


Hi Himanshoo

SUBSCRIBE / NOTIFY methods are used to register for specific events like
call fowrward, automatic call back , etc.

while INFO method is used to convey mid session information. The INFO method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not.

Ranjit :-)

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of
Himanshoo Ks
Sent: Monday, September 23, 2002 8:56 AM
To: sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip] SIP INFO


Hi,

This is with reference to the SIP INFO Method defined in RFC2976.
SIP INFO method is used for sending mid call signaling information. The way
information is sent by a UAC to UAS is clear. But I have one basic question:
1. How does the UAC generating this INFO message know that the UAS is
ineterested in knowing that event.
2. Also we have SUBSCRIBE/NOTIFY messages in SIP which can be used to
subscribe for soem information and then report the same. So in what way is
INFO different than these ..
Could somebody please answer these questions ?

regards
Himanshoo

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

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

_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

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

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



From mailnull@www1.ietf.org  Mon Sep 23 04:26:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02036
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 04:26:20 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8N8Rp728436
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 04:27:51 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N8R6v28403;
	Mon, 23 Sep 2002 04:27:06 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N8Qpv28366
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 04:26:51 -0400
Received: from btlmail.bplmail.com ([203.200.31.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02024;
	Mon, 23 Sep 2002 04:24:49 -0400 (EDT)
Received: from [10.10.13.95] (helo=ranjit)
	by btlmail.bplmail.com with smtp (Exim 3.22 #1 (Red Hat Linux))
	id 17tOaA-0003EL-00; Mon, 23 Sep 2002 13:58:42 +0530
Reply-To: <ranjit.avasarala@bplmail.com>
From: "Ranjit Avasarala" <ranjit.avasarala@bplmail.com>
To: "F.S.Salloum" <ssal@intracom.gr>, <sip@ietf.org>, <sipping@ietf.org>
Date: Wed, 18 Sep 2002 13:56:08 +0530
Message-ID: <FEEJJMJJLHGIMEGAPBJJOEGCCAAA.ranjit.avasarala@bplmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
In-Reply-To: <NGBBLHKPJKCDNEIOOKKOGEIACEAA.ssal@intracom.gr>
Content-Transfer-Encoding: 7bit
Subject: [Sip] RE: [Sipping] INAP and SIP INFO
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

refer this draft : draft-gurbani-sin-02.txt

Ranjit :-) 

-----Original Message-----
From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
F.S.Salloum
Sent: Monday, September 23, 2002 11:31 AM
To: sip@ietf.org; sipping@ietf.org
Subject: [Sipping] INAP and SIP INFO


Dear All,

Is there a draft dealing with encapsulation of INAP messages with the SIP
info message ?

Regards,

F.S.Salloum

_______________________________________________
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
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Mon Sep 23 05:08:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02757
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 05:08:07 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8N99Rk30782
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 05:09:27 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N987v30744;
	Mon, 23 Sep 2002 05:08:07 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N97mv30717
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 05:07:48 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02733
	for <sip@ietf.org>; Mon, 23 Sep 2002 05:05:39 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2V00FAMW0A29@mta2.huawei.com> for sip@ietf.org; Mon,
 23 Sep 2002 17:07:22 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2V00FF3W012L@mta2.huawei.com> for sip@ietf.org; Mon,
 23 Sep 2002 17:07:22 +0800 (CST)
Received: from himanshoo ([10.18.5.112])
 by mailin.huawei.com (Netscape Messaging Server 4.15)
 with ESMTP id H2VTUA00.Q0U; Mon, 23 Sep 2002 16:20:35 +0800
Date: Mon, 23 Sep 2002 13:42:14 +0530
From: Himanshoo Ks <himanshooks@huawei.com>
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO
In-reply-to: <KPEPLFDHIJPLNICJNCJJOEFMCCAA.prasanna@huawei.com>
To: sip@ietf.org, sip-implementors@cs.columbia.edu
Message-id: <000001c262d8$edadbf00$7005120a@himanshoo>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Hi ,

After reading all of your mails I looked at some of the drafts which are
related to carrying MGCP events  / messages inside SIP INFO Message. If I
follow that approach then it appears that I can first send an INFO request
and include 'MGCP Requested Events' to request detection of events. Later
when that event is deteted, the detectng entitiy will send another INFO
Request with 'MGCP observed events' . By using this approach I can control
the events which are reported to the requestign entity.
This is one use of the INFO message which seems to be very useful.

Regards
Himanshoo

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



From mailnull@www1.ietf.org  Mon Sep 23 05:10:16 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02866
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 05:10:09 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8N9BTh30837
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 05:11:29 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N95hv30108;
	Mon, 23 Sep 2002 05:05:43 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N948v30072
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 05:04:08 -0400
Received: from btlmail.bplmail.com ([203.200.31.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02708
	for <sip@ietf.org>; Mon, 23 Sep 2002 05:02:11 -0400 (EDT)
Received: from [10.10.13.95] (helo=ranjit)
	by btlmail.bplmail.com with smtp (Exim 3.22 #1 (Red Hat Linux))
	id 17tPAY-0003xs-00; Mon, 23 Sep 2002 14:36:18 +0530
Reply-To: <ranjit.avasarala@bplmail.com>
From: "Ranjit Avasarala" <ranjit.avasarala@bplmail.com>
To: "Prasanna" <prasanna@huawei.com>, "Himanshoo Ks" <himanshooks@huawei.com>,
        <sip@ietf.org>, <sip-implementors@cs.columbia.edu>
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO
Date: Wed, 18 Sep 2002 14:33:44 +0530
Message-ID: <FEEJJMJJLHGIMEGAPBJJMEGECAAA.ranjit.avasarala@bplmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
In-Reply-To: <KPEPLFDHIJPLNICJNCJJAEGACCAA.prasanna@huawei.com>
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

it is neither a clinet nor server error, but UAS sends 487 indicating to UAC
that it is not interested in accepting the request.

Ranjit :-)

-----Original Message-----
From: Prasanna [mailto:prasanna@huawei.com]
Sent: Monday, September 23, 2002 1:57 PM
To: ranjit.avasarala@bplmail.com; Himanshoo Ks; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


As such 487 is sent when a cancellation of a request is triggered by the UAC
itself (conditions like CANCEL, expiration of the request), but I do not
believe that this is a UAC triggered cancellation.  I withdraw my suggestion
for a 400, for I am also not convinced if UAC behaves erroneously sending
this request or the server behaves erroneously by not able to understand
this.
Do we have a clarity if this is a client error or a server error?
-Prasanna

-----Original Message-----
From: Ranjit Avasarala [mailto:ranjit.avasarala@bplmail.com]
Sent: Wednesday, September 18, 2002 4:14 PM
To: Prasanna; Himanshoo Ks; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


487 is ok be'se if UAS does not want to accept the INFO request, it will
cancel it. U cannot send 400 Bad Request be'se its not a bad request.

Ranjit :-)

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of
Prasanna
Sent: Monday, September 23, 2002 11:28 AM
To: ranjit.avasarala@bplmail.com; Himanshoo Ks; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


HI Ranjit,
	I do not believe 487 is a suitable response for such a condition.  As such
there is no response that is suitable that is usable in this case, but we
can respond with a 400 response.  But do we even have an agreement that this
is a client error!
Rgds,
Prasanna

-----Original Message-----
From: sip-implementors-admin@cs.columbia.edu
[mailto:sip-implementors-admin@cs.columbia.edu]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 1:41 PM
To: Himanshoo Ks; sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] RE: [Sip] SIP INFO


Hi Himanshoo

  if there is any extra info to be conveyed to UAS, then UAC generates INFO
request and sends it to UAS. but if UAS is not interested in the info, then
UAS can respond with "487 Request Cancelled" response.

HTH
Ranjit :-)

-----Original Message-----
From: Himanshoo Ks [mailto:himanshooks@huawei.com]
Sent: Monday, September 23, 2002 10:25 AM
To: ranjit.avasarala@bplmail.com; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip] SIP INFO


Your mail says that:

"while INFO method is used to convey mid session information. The INFO
method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not."

If UAS can't tell what information it is interested in, then what is the use
of INFO method...

Also, then how does UAC decide which information to send.

regards
Himanshoo
-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 10:10 AM
To: Himanshoo Ks; sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: RE: [Sip] SIP INFO


Hi Himanshoo

SUBSCRIBE / NOTIFY methods are used to register for specific events like
call fowrward, automatic call back , etc.

while INFO method is used to convey mid session information. The INFO method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not.

Ranjit :-)

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of
Himanshoo Ks
Sent: Monday, September 23, 2002 8:56 AM
To: sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip] SIP INFO


Hi,

This is with reference to the SIP INFO Method defined in RFC2976.
SIP INFO method is used for sending mid call signaling information. The way
information is sent by a UAC to UAS is clear. But I have one basic question:
1. How does the UAC generating this INFO message know that the UAS is
ineterested in knowing that event.
2. Also we have SUBSCRIBE/NOTIFY messages in SIP which can be used to
subscribe for soem information and then report the same. So in what way is
INFO different than these ..
Could somebody please answer these questions ?

regards
Himanshoo

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

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

_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

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

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



From mailnull@www1.ietf.org  Mon Sep 23 10:40:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10956
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 10:40:49 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8NEgCG15308
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 10:42:12 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NEeHv15257;
	Mon, 23 Sep 2002 10:40:17 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NEcwv15169
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 10:38:58 -0400
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10745
	for <sip@ietf.org>; Mon, 23 Sep 2002 10:37:04 -0400 (EDT)
From: hisham.khartabil@nokia.com
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g8NEcmT19793
	for <sip@ietf.org>; Mon, 23 Sep 2002 17:38:48 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5d843de86bac158f25147@esvir05nok.ntc.nokia.com> for <sip@ietf.org>;
 Mon, 23 Sep 2002 17:36:48 +0300
Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 23 Sep 2002 17:36:48 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Mon, 23 Sep 2002 17:36:47 +0300
Message-ID: <2038BCC78B1AD641891A0D1AE133DBB7C20665@esebe019.ntc.nokia.com>
Thread-Topic: Comments on draft-ietf-sip-compression-01.txt
Thread-Index: AcJjDqVOE6xYHbcvRe6Lbt4c59WJ+Q==
To: <sip@ietf.org>
X-OriginalArrivalTime: 23 Sep 2002 14:36:48.0047 (UTC) FILETIME=[A5B32BF0:01C2630E]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g8NEcwv15172
Subject: [Sip] Comments on draft-ietf-sip-compression-01.txt
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

- Section 4: it says:

"If a client sends a compressed request, it SHOULD add the parameter
   comp=sigcomp to the topmost entry of the Via header field."

Why isn't that so also for proxies?


Section 5: Second and third paragraph. What is the purpose of this? If I understand correctly, it is to allow the UAC sending compressed requests within this dialog. But this doesn't work.

Consider this scenario


UA1 --- P1 --- P2 --- P3 --- UA2

P1 wants to compress
P2 doesn't want to compress
P3 wants to compress

They all record-route

Initial INVITE from UA1 is not compressed. So INVITE arrive at UA2 looking like this:

INVITE: sip:ua2@example.com SIP/2.0
via: p3
via: p2
via: p1
via:ua1
Record-route: <p1;comp=sigcomp> , <p2> , <p3;comp=sigcomp>
contact: ua1
...


Response from UA2 to P2 looks like:

SIP/2.0 200 Ok
via: p2
via: p1
via:ua1
Record-route: <p1;comp=sigcomp> , <p2> , <p3;comp=sigcomp>
...

According to the above mentioned paragraphs, P3 removes its comp=sigcomp and forwards response to P2:

SIP/2.0 200 Ok
via: p1
via:ua1
Record-route: <p1;comp=sigcomp> , <p2> , <p3>
...

Again P2 applies the same logic, but this time adds comp=sigcomp, therefore making the response sent to P1 look like

SIP/2.0 200 Ok
via:ua1
Record-route: <p1;comp=sigcomp> , <p2;comp=sigcomp> , <p3>

and finally P1 will remove comp=sigcomp. Record-Route header looks like

Record-route: <p1> , <p2;comp=sigcomp> , <p3>

That is not the desired behaviour. The requirement should be that each proxy that record-routes examines the contact-header sent in the request and add/remove comp=sigcomp in the record-route header of the response. In this way, if the UAC wishes for requests within dialogs to be compressed, it indicates so in the contact-header.

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



From mailnull@www1.ietf.org  Mon Sep 23 10:42:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11026
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 10:42:09 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8NEhWL15386
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 10:43:32 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NEhCv15365;
	Mon, 23 Sep 2002 10:43:12 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NEgDv15320
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 10:42:13 -0400
Received: from imo-r07.mx.aol.com (imo-r07.mx.aol.com [152.163.225.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10897
	for <sip@ietf.org>; Mon, 23 Sep 2002 10:40:20 -0400 (EDT)
Received: from bertculpepper@netscape.net
	by imo-r07.mx.aol.com (mail_out_v34.10.) id p.56.4664496 (22683);
	Mon, 23 Sep 2002 10:41:25 -0400 (EDT)
Received: from  netscape.net ([207.30.138.149]) by air-in04.mx.aol.com (v88.20) with ESMTP id MAILININ44-0923104125; Mon, 23 Sep 2002 10:41:25 -0400
Message-ID: <3D8F2839.3080400@netscape.net>
Date: Mon, 23 Sep 2002 10:42:01 -0400
From: Bert Culpepper <bertculpepper@netscape.net>
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.4.1) Gecko/20020314 Netscape6/6.2.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: Himanshoo Ks <himanshooks@huawei.com>
CC: sip@ietf.org, sip-implementors@cs.columbia.edu
Subject: Re: [Sip] draft-culpepper-sip-info-event-00.txt
References: <000101c262c0$9c8f11e0$7005120a@himanshoo>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailer: Unknown (No Version)
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

As you noted, that I-D is expired.  In addition, work is being done to 
define a general mechanism for conveying user indications to support 
user interaction with applications.  The current I-Ds are:

http://www.ietf.org/internet-drafts/draft-rosenberg-sipping-markup-00.txt
http://www.ietf.org/internet-drafts/draft-culpepper-sipping-app-interact-reqs-01.txt
http://www.ietf.org/internet-drafts/draft-fairlie-sipping-netapp-session-00.txt
http://www.ietf.org/internet-drafts/draft-culpepper-sip-key-events-01.txt

You can expect an update to the requirements I-D shortly I believe.  And 
a general framework, to follow.


Himanshoo Ks wrote:

> Hi,
> 
> I have a question on draft-culpepper-sip-info-event-00.txt:
> 
> 1. It says that MGCP subtype can be used to indicate the protocol between
> MGC and MG and then some MGCP message can be encapsulated to request and
> report the events as per MGCP packages. Does this mean that I can send the
> complete command line ( I mean whole of RQNT) as message body for the INFO
> request. It is needed since I also need to identify the end point where I
> want event to be detected.


The idea was that the the call identifying info in the SIP request would 
be used by the MGC to identify MGCP/Megaco connection.  Just as it would 
for any other interworking function.  The only proposed INFO message 
content was the actual event request/notification.


> 
> 2. And more importantly, as per the date mentioned ni draft, this draft has
> expired on October 2000. Is there some other draft / RFC which is taing care
> of there issues ? Should I refer to some other document for finding solution
> to this problem.


Yes, the forthcoming I-Ds mentioned above.

Best Regards,
Bert Culpepper


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


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



From mailnull@www1.ietf.org  Mon Sep 23 12:06:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14482
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 12:06:28 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8NG7qb20586
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 12:07:52 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NG7Xv20538;
	Mon, 23 Sep 2002 12:07:33 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N9VIv31474
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 05:31:18 -0400
Received: from mail.bhartitelesoft.com ([202.56.229.147])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03193
	for <sip@ietf.org>; Mon, 23 Sep 2002 05:29:09 -0400 (EDT)
Received: from sharad (sharad [172.16.3.67])
	by mail.bhartitelesoft.com (8.11.0/8.11.0) with SMTP id g8N9Ko913428;
	Mon, 23 Sep 2002 14:50:50 +0530
Reply-To: <sharad@bhartitelesoft.com>
From: "Sharad Goklani" <sharad@bhartitelesoft.com>
To: "'Himanshoo Ks'" <himanshooks@huawei.com>, <sip@ietf.org>,
        <sip-implementors@cs.columbia.edu>
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO
Date: Mon, 23 Sep 2002 15:00:43 +0530
Message-ID: <000901c262e3$e39b4fe0$430310ac@bhartitelesoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
In-reply-to: <000001c262d8$edadbf00$7005120a@himanshoo>
X-ECS-MailScanner: Found to be clean
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

But can't this be done using SUBSCRIBE/NOTIFY ?
Sharad

-----Original Message-----
From: sip-implementors-admin@cs.columbia.edu
[mailto:sip-implementors-admin@cs.columbia.edu]On Behalf Of Himanshoo Ks
Sent: Monday, September 23, 2002 1:42 PM
To: sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


Hi ,

After reading all of your mails I looked at some of the drafts which are
related to carrying MGCP events  / messages inside SIP INFO Message. If I
follow that approach then it appears that I can first send an INFO request
and include 'MGCP Requested Events' to request detection of events. Later
when that event is deteted, the detectng entitiy will send another INFO
Request with 'MGCP observed events' . By using this approach I can control
the events which are reported to the requestign entity.
This is one use of the INFO message which seems to be very useful.

Regards
Himanshoo

_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

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



From mailnull@www1.ietf.org  Mon Sep 23 12:06:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14499
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 12:06:41 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8NG85W20613
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 12:08:05 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NG7lv20575;
	Mon, 23 Sep 2002 12:07:47 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8N9W5v31497
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 05:32:05 -0400
Received: from mail.bhartitelesoft.com ([202.56.229.147])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03194
	for <sip@ietf.org>; Mon, 23 Sep 2002 05:29:26 -0400 (EDT)
Received: from sharad (sharad [172.16.3.67])
	by mail.bhartitelesoft.com (8.11.0/8.11.0) with SMTP id g8N9Je913316;
	Mon, 23 Sep 2002 14:50:16 +0530
Reply-To: <sharad@bhartitelesoft.com>
From: "Sharad Goklani" <sharad@bhartitelesoft.com>
To: <ranjit.avasarala@bplmail.com>, "'Prasanna'" <prasanna@huawei.com>,
        "'Himanshoo Ks'" <himanshooks@huawei.com>, <sip@ietf.org>,
        <sip-implementors@cs.columbia.edu>
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO
Date: Mon, 23 Sep 2002 14:59:32 +0530
Message-ID: <000801c262e3$b9b2db80$430310ac@bhartitelesoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
In-reply-to: <FEEJJMJJLHGIMEGAPBJJMEGECAAA.ranjit.avasarala@bplmail.com>
X-ECS-MailScanner: Found to be clean
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Actually 487 does not seem to be a correct response to INFO ...
When the originator of the INFO wishes to cancel the INFO sent, it sends a
CANCEL, and 487 can only be sent in response to this CANCEL request.

Per RFC 2976, sec. 2.2:
      A 200 OK response MUST be sent by a UAS for an INFO request with
      no message body if the INFO request was successfully received for
      an existing call.  Beyond that, no additional operations are
      required.
and
      If a server receives an INFO request with a body it understands,
      but it has no knowledge of INFO associated processing rules for
      the body, the body MAY be rendered and displayed to the user. The
      INFO is responded to with a 200 OK.

      If the INFO request contains a body that the server does not
      understand then, in the absence of INFO associated processing
      rules for the body, the server MUST respond with a 415 Unsupported
      Media Type message.

From the above, it seems to mean that:
1. If the (SIP) request is syntactically incorrect,
   it sends a 400
2. If it is syntactically correct, but doesn't understand the (SDP) body,
   it sends 415
3. If it is syntactically correct, and it also understands the body,
   but does not implement the processing rules for the request,
   it sends a 200

Apart from the above, I guess only 481 and 501 are other possible responses.

Hence, if the sender of INFO receives a 200, it has no way of knowing
whether the other end has actually processed the request or has ignored the
same.

Sharad

-----Original Message-----
From: sip-implementors-admin@cs.columbia.edu
[mailto:sip-implementors-admin@cs.columbia.edu]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 2:34 PM
To: Prasanna; Himanshoo Ks; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


it is neither a clinet nor server error, but UAS sends 487 indicating to UAC
that it is not interested in accepting the request.

Ranjit :-)

-----Original Message-----
From: Prasanna [mailto:prasanna@huawei.com]
Sent: Monday, September 23, 2002 1:57 PM
To: ranjit.avasarala@bplmail.com; Himanshoo Ks; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


As such 487 is sent when a cancellation of a request is triggered by the UAC
itself (conditions like CANCEL, expiration of the request), but I do not
believe that this is a UAC triggered cancellation.  I withdraw my suggestion
for a 400, for I am also not convinced if UAC behaves erroneously sending
this request or the server behaves erroneously by not able to understand
this.
Do we have a clarity if this is a client error or a server error?
-Prasanna

-----Original Message-----
From: Ranjit Avasarala [mailto:ranjit.avasarala@bplmail.com]
Sent: Wednesday, September 18, 2002 4:14 PM
To: Prasanna; Himanshoo Ks; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


487 is ok be'se if UAS does not want to accept the INFO request, it will
cancel it. U cannot send 400 Bad Request be'se its not a bad request.

Ranjit :-)

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of
Prasanna
Sent: Monday, September 23, 2002 11:28 AM
To: ranjit.avasarala@bplmail.com; Himanshoo Ks; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


HI Ranjit,
	I do not believe 487 is a suitable response for such a condition.  As such
there is no response that is suitable that is usable in this case, but we
can respond with a 400 response.  But do we even have an agreement that this
is a client error!
Rgds,
Prasanna

-----Original Message-----
From: sip-implementors-admin@cs.columbia.edu
[mailto:sip-implementors-admin@cs.columbia.edu]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 1:41 PM
To: Himanshoo Ks; sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip-implementors] RE: [Sip] SIP INFO


Hi Himanshoo

  if there is any extra info to be conveyed to UAS, then UAC generates INFO
request and sends it to UAS. but if UAS is not interested in the info, then
UAS can respond with "487 Request Cancelled" response.

HTH
Ranjit :-)

-----Original Message-----
From: Himanshoo Ks [mailto:himanshooks@huawei.com]
Sent: Monday, September 23, 2002 10:25 AM
To: ranjit.avasarala@bplmail.com; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip] SIP INFO


Your mail says that:

"while INFO method is used to convey mid session information. The INFO
method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not."

If UAS can't tell what information it is interested in, then what is the use
of INFO method...

Also, then how does UAC decide which information to send.

regards
Himanshoo
-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 10:10 AM
To: Himanshoo Ks; sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: RE: [Sip] SIP INFO


Hi Himanshoo

SUBSCRIBE / NOTIFY methods are used to register for specific events like
call fowrward, automatic call back , etc.

while INFO method is used to convey mid session information. The INFO method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not.

Ranjit :-)

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of
Himanshoo Ks
Sent: Monday, September 23, 2002 8:56 AM
To: sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: [Sip] SIP INFO


Hi,

This is with reference to the SIP INFO Method defined in RFC2976.
SIP INFO method is used for sending mid call signaling information. The way
information is sent by a UAC to UAS is clear. But I have one basic question:
1. How does the UAC generating this INFO message know that the UAS is
ineterested in knowing that event.
2. Also we have SUBSCRIBE/NOTIFY messages in SIP which can be used to
subscribe for soem information and then report the same. So in what way is
INFO different than these ..
Could somebody please answer these questions ?

regards
Himanshoo

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

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

_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

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

_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

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



From mailnull@www1.ietf.org  Mon Sep 23 12:41:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15652
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 12:41:15 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8NGgcI22553
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 12:42:38 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NGg9v22528;
	Mon, 23 Sep 2002 12:42:09 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NGe0v22419
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 12:40:00 -0400
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15548
	for <sip@ietf.org>; Mon, 23 Sep 2002 12:38:06 -0400 (EDT)
Received: from jet.isi.edu (jet.isi.edu [128.9.160.87])
	by tnt.isi.edu (8.11.6/8.11.2) with ESMTP id g8NGdiQ26988;
	Mon, 23 Sep 2002 09:39:44 -0700 (PDT)
Received: from jet.isi.edu (jet.isi.edu [128.9.160.87])
	by jet.isi.edu (8.8.7/8.8.6) with SMTP id QAA10840;
	Mon, 23 Sep 2002 16:39:44 GMT
Message-Id: <200209231639.QAA10840@jet.isi.edu>
Date: Mon, 23 Sep 2002 09:39:44 -0700 (PDT)
From: rfc-editor@rfc-editor.org
Reply-To: rfc-editor@rfc-editor.org
Subject: RE: [Sip] Protocol Action: Session Initiation Protocol Extension  for Instant Messaging to Proposed Standard
To: rfc-editor@ISI.EDU, Ya-Ching.Tan@icn.siemens.de
Cc: sip@ietf.org, bcampbell@dynamicsoft.com, jdrosen@dynamicsoft.com,
        schulzrinne@cs.columbia.edu, huitema@microsoft.com,
        dgurle@microsoft.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: AwwDNXlFSktyZhKQOaulfg==
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

Tan,

Thank you for bringing this to our attention.  If this is correct, the
authors will have the opportunity to correct this during the "authors
48 hours" period.

Thank you.

RFC Editor


> From: Tan Ya-Ching  ICM N PG U ID A 1 <Ya-Ching.Tan@icn.siemens.de>
> To: RFC Editor <rfc-editor@ISI.EDU>
> Cc: sip@ietf.org
> Subject: RE: [Sip] Protocol Action: Session Initiation Protocol Extension  for 
Instant Messaging to Proposed Standard
> Date: Mon, 23 Sep 2002 10:03:16 +0200
> MIME-Version: 1.0
> 
> 
> 
> | -----Original Message-----
> | From: The IESG [mailto:iesg-secretary@ietf.org]
> | Sent: 20 September 2002 23:02
> | Cc: RFC Editor; Internet Architecture Board; sip@ietf.org
> | Subject: [Sip] Protocol Action: Session Initiation Protocol Extension
> | for Instant Messaging to Proposed Standard
> | 
> | 
> | 
> | 
> | The IESG has approved the Internet-Draft 'Session Initiation Protocol
> | Extension for Instant Messaging' <draft-ietf-sip-message-07.txt> as a
> | Proposed Standard.  This document is the product of the Session
> | Initiation Protocol Working Group.  The IESG contact persons are
> | Allison Mankin and Scott Bradner.
> | 
> 
> 
> 
> Note to RFC Editor,
> 
> Table 1 and Table 2 of draft-ietf-sip-message-07 seem to be based on the
> older version of SIP RFC.  Table 1 and Table 2 of RFC 3261 have the
> following headers which are missing in the 07 draft :
> 
> Min-Expires
> MIME-Version
> Supported
> 
> 
> Regards,
> Ya-Ching Tan

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



From mailnull@www1.ietf.org  Mon Sep 23 13:01:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16425
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 13:01:58 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8NH3Lx23470
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 13:03:21 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NH1Cv23369;
	Mon, 23 Sep 2002 13:01:12 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NGxmv23237
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 12:59:48 -0400
Received: from chuckie.dgms.com (angelica.ulticom.com [208.255.120.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16215
	for <sip@ietf.org>; Mon, 23 Sep 2002 12:57:54 -0400 (EDT)
Received: from ulticom.com (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with ESMTP id MAA02810;
	Mon, 23 Sep 2002 12:59:07 -0400 (EDT)
Message-ID: <3D8F4860.F0B35436@ulticom.com>
Date: Mon, 23 Sep 2002 12:59:12 -0400
From: Vijaya Venkatachalam <vijaya@ulticom.com>
Organization: Ulticom, Inc.
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18-3 i686)
X-Accept-Language: en
MIME-Version: 1.0
CC: "'Doug Whitson'" <douglas.whitson@ulticom.com>, sip@ietf.org
Subject: Re: [Sip] followup email
References: <9BF66EBF6BEFD942915B4D4D45C051F3A64087@DYN-TX-EXCH-001.dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Adam Roach wrote:

> Your end sequence is \r\n followed by anything that is not
> a tab or a space. Please read RFC3261, section 7.3 and its
> subsections.
>
> Any further implementation questions should go to
> sip-implementors@cs.columbia.edu, as noted at the bottom of
> every single note posted to this list.
>
> /a
>
> > -----Original Message-----
> > From: Doug Whitson [mailto:douglas.whitson@ulticom.com]
> > Sent: Thursday, August 22, 2002 16:14
> > To: sip@ietf.org
> > Subject: [Sip] followup email
> >
> >
> > Hi,
> >  My earlier email may not have been exact. It seems all open
> > ended headers,
> > ie: extensions, organization, and subject have the same
> > trouble. The parser
> > needs to know when to stop parsing these headers and since
> > they may span
> > multiple \r\n this cannot be used as a end sequence. I am thinking a
> > subject-length and the like may be required.
> >
> >  Please let me know your thoughts...
> >
> >
> > -------------------------------------------------------------
> > Thank you.
> >
> > Doug Whitson
> > Senior Software Engineer
> > Ulticom Inc.
> > 1020 Briggs Road, Mt Laurel NJ, 08054
> > (856)787-2927
> > whitson@ulticom.com
> >
> > In seeking wisdom, the first step is silence, the second
> > listening, the
> > third remembering, the fourth practicing, the fifth --
> > teaching others.
> >
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> >
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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



From mailnull@www1.ietf.org  Mon Sep 23 14:49:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20439
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 14:49:41 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8NIp5R30091
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 14:51:05 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NIoev29808;
	Mon, 23 Sep 2002 14:50:40 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NInbv29705
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 14:49:37 -0400
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20324
	for <sip@ietf.org>; Mon, 23 Sep 2002 14:47:42 -0400 (EDT)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g8NImw712684;
	Mon, 23 Sep 2002 14:48:58 -0400 (EDT)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <TLKBZ0RN>; Mon, 23 Sep 2002 14:49:00 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A91D@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "'Henry Sinnreich'" <Henry.Sinnreich@wcom.com>
Cc: sip@ietf.org, "Arora, Jitender [Business:LIZD:T912]"
	 <jarora@aastra.com>,
        "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>
Subject: RE: [Sip] Regarding SIP CDR inforamtion ( from a Media Gateway Co
	ntroller p erspective)
Date: Mon, 23 Sep 2002 14:48:58 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

You imply that VoIP is one more web service.  This makes perfect sense for
PC-like user interfaces, but does it make sense for SIP phones?

> -----Original Message-----
> From: Henry Sinnreich [mailto:Henry.Sinnreich@wcom.com] 
> Sent: Saturday, September 07, 2002 5:14 PM
> To: Arora, Jitender [Business:LIZD:T912]; 'Jonathan Rosenberg'
> Cc: sip@ietf.org
> Subject: RE: [Sip] Regarding SIP CDR inforamtion ( from a 
> Media Gateway Controller p erspective)
> 
> 
> One long term view on AAA and CDRs for voice services is that 
> all AAA transactions and payments should fit in the emerging 
> Web services for any type of service or merchandise. 
> 
> Internal systems for authentication, billing, traffic 
> measurments, etc. may need to be outsourced or resold, just 
> like any other service. Having only VoIP using specific (or 
> even obscure ones like DIAMETER) platforms does not seem a 
> very good proposition for service providers, where 
> streaminling IT is a perenial objective.
> 
> Here is some good reading material:
> 
> Tutorials: http://www.w3schools.com/
> 
> Web Services:
>  
> http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/Dnwebsr
v/html/webservbasics.asp?frame=true

The core references: http://www.w3.org/2002/ws/

Thanks, Henry

> -----Original Message-----
> From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On
> Behalf Of Jitender Arora
> Sent: Friday, September 06, 2002 3:51 PM
> To: Jonathan Rosenberg
> Cc: sip@ietf.org
> Subject: [Sip] Regarding SIP CDR inforamtion ( from a Media 
> Gateway Controller p erspective)
> 
> 
> Hi ,
> 
>      could somebody please point to the draft or RFC which
> contains the information about how the 
>      CDR ( call detail records ) are generated for the SIP 
> calls ( what all informaion should be there 
>      in the CDR ) from the Media Gateway Controller Perspective . 
> 
>      Is there any document available for this ...If yes
> please let me know ....
> 
> Thanks and Regards,
> jitender .
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current
> sip Use sipping@ietf.org for new developments on the 
> application of sip
> 

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



From mailnull@www1.ietf.org  Mon Sep 23 15:39:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21989
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 15:39:25 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8NJeoh00932
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 15:40:50 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NJeRv00863;
	Mon, 23 Sep 2002 15:40:27 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NJd3v00763
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 15:39:03 -0400
Received: from pmesmtp02.wcom.com (pmesmtp02.wcom.com [199.249.20.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21899
	for <sip@ietf.org>; Mon, 23 Sep 2002 15:37:08 -0400 (EDT)
Received: from pmismtp02.wcomnet.com ([166.38.62.37])
 by firewall.wcom.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7
 2002)) with ESMTP id <0H2W008JJP83ZE@firewall.wcom.com> for sip@ietf.org; Mon,
 23 Sep 2002 19:38:28 +0000 (GMT)
Received: from pmismtp02.wcomnet.com by pmismtp02.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0H2W00401P83FI@pmismtp02.wcomnet.com>; Mon,
 23 Sep 2002 19:38:27 +0000 (GMT)
Received: from hsinnreich2 ([166.35.136.36])
 by pmismtp02.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with ESMTP id <0H2W0041BP82CK@pmismtp02.wcomnet.com>; Mon,
 23 Sep 2002 19:38:27 +0000 (GMT)
Date: Mon, 23 Sep 2002 14:38:26 -0500
From: Henry Sinnreich <Henry.Sinnreich@wcom.com>
Subject: RE: [Sip] Regarding SIP CDR inforamtion ( from a Media Gateway
 Controller p erspective)
In-reply-to: <4D79C746863DD51197690002A52CDA0001E8A91D@zcard0kc.ca.nortel.com>
To: "'Tom-PT Taylor'" <taylor@nortelnetworks.com>
Cc: sip@ietf.org, "'Arora, Jitender [Business:LIZD:T912]'" <jarora@aastra.com>,
        "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>
Message-id: <003f01c26338$c98748c0$248823a6@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1097
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> perfect sense for PC-like user interfaces, but does it make 
> sense for SIP phones?

Laptops with side tone & echo control (MS Messenger 4.7) are decent
speakerphones and PDA's are decent mobile phones. There are also 802.11
IP phones emerging. Why should we make a difference? They are all IP
hosts running SIP and RTP IMHO.

Henry

> -----Original Message-----
> From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On 
> Behalf Of Tom-PT Taylor
> Sent: Monday, September 23, 2002 1:49 PM
> To: 'Henry Sinnreich'
> Cc: sip@ietf.org; Arora, Jitender [Business:LIZD:T912]; 
> 'Jonathan Rosenberg'
> Subject: RE: [Sip] Regarding SIP CDR inforamtion ( from a 
> Media Gateway Controller p erspective)
> 
> 
> You imply that VoIP is one more web service.  This makes 
> perfect sense for PC-like user interfaces, but does it make 
> sense for SIP phones?
> 
> > -----Original Message-----
> > From: Henry Sinnreich [mailto:Henry.Sinnreich@wcom.com]
> > Sent: Saturday, September 07, 2002 5:14 PM
> > To: Arora, Jitender [Business:LIZD:T912]; 'Jonathan Rosenberg'
> > Cc: sip@ietf.org
> > Subject: RE: [Sip] Regarding SIP CDR inforamtion ( from a 
> > Media Gateway Controller p erspective)
> > 
> > 
> > One long term view on AAA and CDRs for voice services is that
> > all AAA transactions and payments should fit in the emerging 
> > Web services for any type of service or merchandise. 
> > 
> > Internal systems for authentication, billing, traffic
> > measurments, etc. may need to be outsourced or resold, just 
> > like any other service. Having only VoIP using specific (or 
> > even obscure ones like DIAMETER) platforms does not seem a 
> > very good proposition for service providers, where 
> > streaminling IT is a perenial objective.
> > 
> > Here is some good reading material:
> > 
> > Tutorials: http://www.w3schools.com/
> > 
> > Web Services:
> >  
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-
> us/Dnwebsr
> v/html/webservbasics.asp?frame=true
> 
> The core references: http://www.w3.org/2002/ws/
> 
> Thanks, Henry
> 
> > -----Original Message-----
> > From: sip-admin@ietf.org [mailto:sip-admin@ietf.org] On Behalf Of 
> > Jitender Arora
> > Sent: Friday, September 06, 2002 3:51 PM
> > To: Jonathan Rosenberg
> > Cc: sip@ietf.org
> > Subject: [Sip] Regarding SIP CDR inforamtion ( from a Media
> > Gateway Controller p erspective)
> > 
> > 
> > Hi ,
> > 
> >      could somebody please point to the draft or RFC which contains 
> > the information about how the
> >      CDR ( call detail records ) are generated for the SIP
> > calls ( what all informaion should be there 
> >      in the CDR ) from the Media Gateway Controller Perspective . 
> > 
> >      Is there any document available for this ...If yes 
> please let me 
> > know ....
> > 
> > Thanks and Regards,
> > jitender .
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on 
> current sip Use 
> > sipping@ietf.org for new developments on the application of sip
> > 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sipping@ietf.org for new developments on the 
> application of sip _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sipping@ietf.org for new developments on the 
> application of sip
> 

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



From mailnull@www1.ietf.org  Mon Sep 23 15:39:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22003
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 15:39:29 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8NJesf00944
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 15:40:54 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NJeav00919;
	Mon, 23 Sep 2002 15:40:36 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NJduv00796
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 15:39:56 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21936;
	Mon, 23 Sep 2002 15:37:59 -0400 (EDT)
Message-Id: <200209231937.PAA21936@ietf.org>
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>, Internet Architecture Board <iab@iab.org>,
        sip@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Date: Mon, 23 Sep 2002 15:37:59 -0400
Subject: [Sip] Protocol Action: Message/sipfrag to Proposed Standard
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>


The IESG has approved publication of the following Internet-Draft as 
a Proposed Standard:

o Internet Media Types message/sipfrag 
<draft-ietf-sip-sipfrag-00.txt>

This document is a product of the Session Initiation Protocol 
Working Group. The IESG contact persons are Allison Mankin and 
Scott Bradner.

Technical Summary

The spec registers the message/sipfrag MIME media type. This 
type is similar to message/sip, but allows certain subsets of well 
formed SIP messages to be represented instead of requiring a complete 
SIP message. In addition to end-to-end security uses, message/ 
sipfrag is used with the REFER method to convey information about the 
status of a referenced request. The message/sipfrag is used with 
S/MIME for gaining integrity and other security services. Advice 
is given for anti-replay and reference integrity when used. The 
type is not analogous to message/partial.

Working Group Summary 

The working group had excellent consensus on this document. 
NOTE: the document was Last Called along with draft-ietf-sip- 
refer under another its original internet-draft name of 
draft-sparks-sip-mimetypes. 

Changes to the document represent responses to the Last Call 
and IESG comments and improved clarity, security, anti-replay, 
protection, reference integrity. 

Protocol Quality 

The specification was reviewed for the IESG by Allison Mankin. 
Last Call comments by the IESG on sipfrag resulted in considerable 
clarification of the document.


Note to RFC Editor:

Please insert the following just before section 2:

    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].

and add the following to the normative references

   [RFC2119] Bradner, S., "Key words for use in RFCs to 	
   Indicate Requirement Levels.", RFC 2119, March 1997


Also, please make the following reference correction:

Old:

      The concepts in that section can be extended to allow SIP entities to
      make assertions about a subset of a SIP message (for example, as
      described in [3]).

New:
      The concepts in that section can be extended to allow SIP entities to
      make assertions about a subset of a SIP message (for example, as
      described in [4]).

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



From mailnull@www1.ietf.org  Mon Sep 23 18:10:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27246
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 18:10:22 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8NMBnp09844
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 18:11:49 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NMB1v09821;
	Mon, 23 Sep 2002 18:11:01 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NM8ev09770
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 18:08:40 -0400
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27122
	for <sip@ietf.org>; Mon, 23 Sep 2002 18:06:40 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g8NM7p3x019984;
	Mon, 23 Sep 2002 15:07:55 -0700 (PDT)
Received: from open-131-161-248-87.cliq.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.1.0.66-GA)
	with ESMTP id AAY39525;
	Mon, 23 Sep 2002 15:05:52 -0700 (PDT)
Date: Mon, 23 Sep 2002 15:09:09 -0700
Subject: Re: [Sip] URI's in To and StartLine in ACK Messages
Content-Type: multipart/alternative; boundary=Apple-Mail-2-824658834
Mime-Version: 1.0 (Apple Message framework v482)
Cc: "'sip@ietf.org'" <sip@ietf.org>
To: ABDUL SATTAR SHAIK <abdulss@migv.mot.com>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <195FE1D3531BD411A50F00B0D021783402907CA6@golfmail.migv.mot.com>
Message-Id: <15D2D1B4-CF41-11D6-A5C1-0003938AF740@cisco.com>
X-Mailer: Apple Mail (2.482)
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>


--Apple-Mail-2-824658834
Content-Type: text/plain;
	charset=ISO-8859-1;
	format=flowed
Content-Transfer-Encoding: quoted-printable

Hi,

In future, when you want to ask questions about how to interpret the SIP=20=

specification, please send your question instead to sip-
implementors@cs.columbia.edu.

 >This list is for NEW development of the core SIP Protocol
 >Use sip-implementors@cs.columbia.edu for questions on current sip
 >Use sipping@ietf.org for new developments on the application of sip

To answer your specific question, there is no requirement that the=20
request-URI has to be the same in both INVITE and ACK.  The request-URI=20=

for the ACK is typically copied from the Contact header in the 2xx=20
response to the INVITE.

thanks,
-rohan



On Saturday, September 21, 2002, at 06:23 AM, ABDUL SATTAR SHAIK wrote:\
> Hi
> Consider Scenario
> UAC -> UAS
>
>
> UAC sends=A0 INVITE with URI 's=A0=A0 LittleGuy@there.com in both =
startline=20
> and To Header Field.
>
> After receiving=A0 OK, UAC sends=A0 ACK with URI=A0=A0 =
LittleGuy@there.com in=20
> To Header Field
> =A0=A0=A0 and SmallGuy@there.com=A0=A0 in Startline. Whether UAS=A0 =
should=A0 accept=20
> ACK or reject=A0 with=A0=A0 error.
>
> Thanks
> Abdul Sattar=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0
>

--Apple-Mail-2-824658834
Content-Type: text/enriched;
	charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,


In future, when you want to ask questions about how to interpret the
SIP specification, please send your question instead to
sip-implementors@cs.columbia.edu.


>This list is for NEW development of the core SIP Protocol

>Use sip-implementors@cs.columbia.edu for questions on current sip

>Use sipping@ietf.org for new developments on the application of sip

=20

To answer your specific question, there is no requirement that the
request-URI has to be the same in both INVITE and ACK.  The
request-URI for the ACK is typically copied from the Contact header in
the 2xx response to the INVITE.


thanks,

-rohan




On Saturday, September 21, 2002, at 06:23 AM, ABDUL SATTAR SHAIK
wrote:\

<excerpt><fontfamily><param>Arial</param><smaller>Hi

Consider Scenario

UAC -> UAS</smaller></fontfamily>



<fontfamily><param>Arial</param><smaller>UAC sends=A0 INVITE with URI
's=A0=A0 LittleGuy@there.com in both startline and To Header =
Field.</smaller></fontfamily>


<fontfamily><param>Arial</param><smaller>After receiving=A0 OK, UAC
sends=A0 ACK with URI=A0=A0 LittleGuy@there.com in To Header Field

=A0=A0=A0 and SmallGuy@there.com=A0=A0 in Startline. Whether UAS=A0 =
should=A0 accept
ACK or reject=A0 with=A0=A0 error.</smaller></fontfamily>


<fontfamily><param>Arial</param><smaller>Thanks

Abdul Sattar=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0</smaller></fontfamily>


</excerpt>=

--Apple-Mail-2-824658834--

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



From mailnull@www1.ietf.org  Mon Sep 23 22:35:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04725
	for <sip-archive@odin.ietf.org>; Mon, 23 Sep 2002 22:35:57 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8O2bPG23081
	for sip-archive@odin.ietf.org; Mon, 23 Sep 2002 22:37:25 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8O2aPv22564;
	Mon, 23 Sep 2002 22:36:25 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8O2Yxv22510
	for <sip@optimus.ietf.org>; Mon, 23 Sep 2002 22:34:59 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04574
	for <sip@ietf.org>; Mon, 23 Sep 2002 22:32:59 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2X00FKZ8I729@mta2.huawei.com> for sip@ietf.org; Tue,
 24 Sep 2002 10:34:55 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2X00F188I62L@mta2.huawei.com> for sip@ietf.org; Tue,
 24 Sep 2002 10:34:55 +0800 (CST)
Received: from HIMANSHOOCL1153 ([10.18.5.85]) by          mailin.huawei.com
 (Netscape Messaging Server 4.15) with ESMTP id          H2X8JQ00.T05; Tue,
 24 Sep 2002 10:35:50 +0800
Date: Tue, 24 Sep 2002 08:02:58 +0530
From: Himanshoo <himanshooks@huawei.com>
Subject: Re: [Sip] draft-culpepper-sip-info-event-00.txt
To: Bert Culpepper <bertculpepper@netscape.net>
Cc: sip@ietf.org, sip-implementors@cs.columbia.edu
Reply-to: Himanshoo <himanshooks@huawei.com>
Message-id: <000701c26372$b29a1860$5505120a@in.huawei.com>
Organization: Huawei
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <000101c262c0$9c8f11e0$7005120a@himanshoo>
 <3D8F2839.3080400@netscape.net>
Content-Transfer-Encoding: 7BIT
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Thanks for your clarification. But let me clarify one last thing :

> > 1. It says that MGCP subtype can be used to indicate the protocol
between
> > MGC and MG and then some MGCP message can be encapsulated to request and
> > report the events as per MGCP packages. Does this mean that I can send
the
> > complete command line ( I mean whole of RQNT) as message body for the
INFO
> > request. It is needed since I also need to identify the end point where
I
> > want event to be detected.
>
>
> The idea was that the the call identifying info in the SIP request would
> be used by the MGC to identify MGCP/Megaco connection.  Just as it would
> for any other interworking function.  The only proposed INFO message
> content was the actual event request/notification.

As per your mail , it says :
"The only proposed INFO message content was the actual event
request/notification."
Does this mean (a part of or full ) event request / notification message ,
as per MGCP ?

Best Regards
Himanshoo


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



From mailnull@www1.ietf.org  Tue Sep 24 00:34:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07078
	for <sip-archive@odin.ietf.org>; Tue, 24 Sep 2002 00:34:05 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8O4ZZB28038
	for sip-archive@odin.ietf.org; Tue, 24 Sep 2002 00:35:35 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8O4Z9v28023;
	Tue, 24 Sep 2002 00:35:09 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8O4X2v27938
	for <sip@optimus.ietf.org>; Tue, 24 Sep 2002 00:33:02 -0400
Received: from btlmail.bplmail.com ([203.200.31.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06946
	for <sip@ietf.org>; Tue, 24 Sep 2002 00:30:59 -0400 (EDT)
Received: from [10.10.13.95] (helo=ranjit)
	by btlmail.bplmail.com with smtp (Exim 3.22 #1 (Red Hat Linux))
	id 17thP9-00036H-00; Tue, 24 Sep 2002 10:04:35 +0530
Reply-To: <ranjit.avasarala@bplmail.com>
From: "Ranjit Avasarala" <ranjit.avasarala@bplmail.com>
To: <sharad@bhartitelesoft.com>, "'Himanshoo Ks'" <himanshooks@huawei.com>,
        <sip@ietf.org>, <sip-implementors@cs.columbia.edu>
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO
Date: Tue, 24 Sep 2002 10:02:02 +0530
Message-ID: <FEEJJMJJLHGIMEGAPBJJCEGMCAAA.ranjit.avasarala@bplmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <000901c262e3$e39b4fe0$430310ac@bhartitelesoft.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

u cannot use SUBSCRIBE/NOTIFY be'se you get NOTIFY when there is a change in
the state of the subscription. but here the case is of event detection. so
as Himanshoo says INFO could be useful

Ranjit :-)

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Sharad
Goklani
Sent: Monday, September 23, 2002 3:01 PM
To: 'Himanshoo Ks'; sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


But can't this be done using SUBSCRIBE/NOTIFY ?
Sharad

-----Original Message-----
From: sip-implementors-admin@cs.columbia.edu
[mailto:sip-implementors-admin@cs.columbia.edu]On Behalf Of Himanshoo Ks
Sent: Monday, September 23, 2002 1:42 PM
To: sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


Hi ,

After reading all of your mails I looked at some of the drafts which are
related to carrying MGCP events  / messages inside SIP INFO Message. If I
follow that approach then it appears that I can first send an INFO request
and include 'MGCP Requested Events' to request detection of events. Later
when that event is deteted, the detectng entitiy will send another INFO
Request with 'MGCP observed events' . By using this approach I can control
the events which are reported to the requestign entity.
This is one use of the INFO message which seems to be very useful.

Regards
Himanshoo

_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

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

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



From mailnull@www1.ietf.org  Tue Sep 24 00:52:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07440
	for <sip-archive@odin.ietf.org>; Tue, 24 Sep 2002 00:52:58 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8O4sQj29213
	for sip-archive@odin.ietf.org; Tue, 24 Sep 2002 00:54:26 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8O4s5v29202;
	Tue, 24 Sep 2002 00:54:06 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8O4qwv29148
	for <sip@optimus.ietf.org>; Tue, 24 Sep 2002 00:52:58 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07417
	for <sip@ietf.org>; Tue, 24 Sep 2002 00:50:52 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2X007YSEW3LS@mta2.huawei.com> for sip@ietf.org; Tue,
 24 Sep 2002 12:52:51 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2X007D1EW2M0@mta2.huawei.com> for sip@ietf.org; Tue,
 24 Sep 2002 12:52:51 +0800 (CST)
Received: from HIMANSHOOCL1153 ([10.18.5.85]) by          mailin.huawei.com
 (Netscape Messaging Server 4.15) with ESMTP id          H2XEXM00.T0B; Tue,
 24 Sep 2002 12:53:46 +0800
Date: Tue, 24 Sep 2002 10:20:55 +0530
From: Himanshoo <himanshooks@huawei.com>
To: sip@ietf.org, sip-implementors@cs.columbia.edu, sip@vovida.org
Reply-to: Himanshoo <himanshooks@huawei.com>
Message-id: <00cd01c26385$f7a1c710$5505120a@in.huawei.com>
Organization: Huawei
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <000101c262c0$9c8f11e0$7005120a@himanshoo>
 <3D8F2839.3080400@netscape.net> <000701c26372$b29a1860$5505120a@in.huawei.com>
Content-Transfer-Encoding: 7BIT
Subject: [Sip] certain questions on third party call control ...
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Hi,

I have certain questions related to the scenario explained below. In
addition to the questions, can somebody please also comment if my
understanding is correct:

SCENARIO
-------------
Caller first dials a service access number and therefore call is given to
the App Server by switch :

Caller --(INVITE)--> Switch--(INVITE)--> App Server

After this App Server Invites Media Server into the call and collects the
destination number to which caller wants to talk to .

After getting the destination number , App Server would request the switch
to connect caller to destination number . But Application Server would
always like to monitor the call progress (e.g. is and when call was
answered/terminated/media characteristics changed). So finally it will be
like this:

                    App Server

                         ^
                         | (Monitoring Link)

Caller----> Switch ----->Destination


App server acts as controller . After playing the prompt to user, it
collects digits from user and then it has to connect caller to the called
party. Now I donot want the to develop a module on App Server, which
connects two parties in a call, because softswitch already knows how to do
it.. SO I use REFER (with refer-to field = Destination Number) to ask switch
to connect caller to the destination number, and automatically I am
subscriber for progress of the INVITE which is used to INVITE the
destination number . In additon I need the following:

1. Capability to do Remote Hang UP : My controller should be able to
terminate call to the destination if the call duration exceeds 'allowed
time'. Can I do this using 'REFER ;method = BYE' ?
2. After initiating the dialog using 'REFER; method = INVITE', I also need
to know the progress of dialog. For example if either of caller and called
party hangsup, I need to stop billing. In other words, I want to subscribe
for the state of dialogs involving softswitch and Calling/Called Party.
First I want to know whether I can do this by sending a SUBSCRIBE , using
dialog package 'draft-ietf-sipping-dialog-package-00.txt'?
Also, I want to know whether the dailog state information as per
'draft-ietf-sipping-dialog-package-00.txt' can also notify me of changes in
media characteristics (i.e. SDP for the dialog).?
3. Further in another scenario, if the time allowed for the calling user
(i.e. pre-paid user) expires, and if I want to connect hm to a Media Server
for playing some prompt (to decide future course of action) , then can I do
this by sending 'REFER ; method = BYE for the dialog between softswitch and
called party' and then send 'REFER; method=INVITE for connecting to MRS; In
this case if I want to tell MRS to send the digits to APP server, instead of
switch , how do I do that?


Best Regards
Himanshoo

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



From mailnull@www1.ietf.org  Tue Sep 24 01:56:18 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08581
	for <sip-archive@odin.ietf.org>; Tue, 24 Sep 2002 01:56:18 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8O5vlJ32208
	for sip-archive@odin.ietf.org; Tue, 24 Sep 2002 01:57:47 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8O5usv32178;
	Tue, 24 Sep 2002 01:56:54 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8O5tQv32147
	for <sip@optimus.ietf.org>; Tue, 24 Sep 2002 01:55:26 -0400
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08525
	for <sip@ietf.org>; Tue, 24 Sep 2002 01:53:26 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g8O5tFKV010923;
	Tue, 24 Sep 2002 07:55:15 +0200 (MEST)
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.51])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g8O5tEG3000164;
	Tue, 24 Sep 2002 08:55:14 +0300 (EET DST)
Message-ID: <3D8FFE42.7CC8D487@lmf.ericsson.se>
Date: Tue, 24 Sep 2002 08:55:14 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: hisham.khartabil@nokia.com
CC: sip@ietf.org
Subject: Re: [Sip] Comments on draft-ietf-sip-compression-01.txt
References: <2038BCC78B1AD641891A0D1AE133DBB7C20665@esebe019.ntc.nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hisham,

inline:

hisham.khartabil@nokia.com wrote:
> 
> - Section 4: it says:
> 
> "If a client sends a compressed request, it SHOULD add the parameter
>    comp=sigcomp to the topmost entry of the Via header field."
> 
> Why isn't that so also for proxies?


Where did you read that proxies are not clients?


 
> Section 5: Second and third paragraph. What is the purpose of this? If I understand correctly, it is to allow the UAC sending compressed requests within this dialog. But this doesn't work.
> 
> Consider this scenario
> 
> UA1 --- P1 --- P2 --- P3 --- UA2
> 
> P1 wants to compress
> P2 doesn't want to compress
> P3 wants to compress
> 

When you provide an example like this, you should indicate on which
interface each SIP entity wants to compress. In fact, the purpose of the
paragraph you are referring to, is to avoid asymmetrical compression.
That is, if SIP messages from P1 to P2 are compressed, messages from P2
to P1 will be compressed as well.

In an example like this, you also have to define if, regardless of waht
they want, they support SigComp or not. I assume that they all support
it.

> They all record-route
> 
> Initial INVITE from UA1 is not compressed. So INVITE arrive at UA2 looking like this:
> 
> INVITE: sip:ua2@example.com SIP/2.0
> via: p3
> via: p2
> via: p1
> via:ua1
> Record-route: <p1;comp=sigcomp> , <p2> , <p3;comp=sigcomp>
> contact: ua1
> ...

A proxy adding sigcomp to the Record-route will add it to the Via header
as well. Therefore the Vias in your example are likely to be different.
But anyway, let's focus on the R-R header.

If the proxies have record-routed like this, it is because they want the
following scenario:

UA1 --- P1 -c- P2 --- P3 -c- UA2

--- means no compression
-c- means SigComp

 
> Response from UA2 to P2 looks like:
> 

It should be UA2 to *P3* (not P2). And the Via headers are wrong again.

> SIP/2.0 200 Ok
> via: p2
> via: p1
> via:ua1
> Record-route: <p1;comp=sigcomp> , <p2> , <p3;comp=sigcomp>
> ...

You do not mention the Contact header in the response, which would be
ua2;comp=sigcomp

Therefore, you already have bidirectional compression between P3 and
UA2, which was what you wanted.

> 
> According to the above mentioned paragraphs, P3 removes its comp=sigcomp and forwards response to P2:
> 
> SIP/2.0 200 Ok
> via: p1
> via:ua1
> Record-route: <p1;comp=sigcomp> , <p2> , <p3>
> ...

Here you have bidirectional NO compression between P2 and P3, which is
what you wanted.

> 
> Again P2 applies the same logic, but this time adds comp=sigcomp, therefore making the response sent to P1 look like
> 
> SIP/2.0 200 Ok
> via:ua1
> Record-route: <p1;comp=sigcomp> , <p2;comp=sigcomp> , <p3>

Here you have bidirectional compression between P1 and P2, which was
what you wanted.

 
> and finally P1 will remove comp=sigcomp. Record-Route header looks like
> 
> Record-route: <p1> , <p2;comp=sigcomp> , <p3>

Here you have bidirectinal NO compression between UA1 and P1, which was
what you wanted.

> 
> That is not the desired behaviour.

This *IS* the intended behaviour if the proxies Record-Routed in the
request in the way you described it.

> The requirement should be that each proxy that record-routes examines the contact-header sent in the request and add/remove comp=sigcomp in the record-route header of the response. In this way, if the UAC wishes for requests within dialogs to be compressed, it indicates so in the contact-header.
> 

This mechanism allows compression between proxies as well. That's why
you have to inspect the RR headers as well.

Regards,

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



From mailnull@www1.ietf.org  Tue Sep 24 04:46:36 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20195
	for <sip-archive@odin.ietf.org>; Tue, 24 Sep 2002 04:46:36 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8O8m8g17727
	for sip-archive@odin.ietf.org; Tue, 24 Sep 2002 04:48:08 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8O8ljv17712;
	Tue, 24 Sep 2002 04:47:45 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8O8kmv17676
	for <sip@optimus.ietf.org>; Tue, 24 Sep 2002 04:46:48 -0400
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20187
	for <sip@ietf.org>; Tue, 24 Sep 2002 04:44:46 -0400 (EDT)
Received: from blues.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.227])
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id KAA26984;
	Tue, 24 Sep 2002 10:45:52 +0200 (MET DST)
Received: from mchh168e.mch4.siemens.de ([139.21.130.175])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id KAA13365;
	Tue, 24 Sep 2002 10:45:51 +0200 (MET DST)
Received: by mchh168e.mch4.siemens.de with Internet Mail Service (5.5.2653.19)
	id <S54L5JK9>; Tue, 24 Sep 2002 10:45:51 +0200
Message-ID: <5B4D0C5BA65ECA46969C1419122317E6E74F65@mchh161e>
From: Tan Ya-Ching  ICM N PG U ID A 1 <Ya-Ching.Tan@icn.siemens.de>
To: bcampbell@dynamicsoft.com
Cc: sip@ietf.org, jdrosen@dynamicsoft.com, schulzrinne@cs.columbia.edu,
        huitema@microsoft.com, dgurle@microsoft.com
Subject: RE: [Sip] Protocol Action: Session Initiation Protocol Extension 
	 for Instant Messaging to Proposed Standard
Date: Tue, 24 Sep 2002 10:45:26 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>


| -----Original Message-----
| From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org]
| Sent: 23 September 2002 18:40
| 
| Thank you for bringing this to our attention.  If this is correct, the
| authors will have the opportunity to correct this during the "authors
| 48 hours" period.

Hi,

While you are at it, you may want to add the Max-Forwards header to the
example messages in section 10. Max-Forwards headers are mandatory in RFC
3261.

Perhaps this is too late, but here is my last attempt to bring up the issue
of provisional response again. The last paragraph of section 8 is
self-contradictory.

   It has been suggested that provisional responses should not be
   allowed for pager-model MESSAGE requests.  However, it is not
   possible to require special treatment for MESSAGE, since many proxy
   servers will not be aware of the MESSAGE method.  Therefore MESSAGE
   requests will receive the same provisional response treatment as any
   other non-INVITE method, as described in the SIP specification.

The "same provisional response treatment as any other non-INVITE method, as
described in the SIP specification", is exactly as the first sentence said :
"provisional responses should not be allowed". I have raised the issue of
allowing provisional response for MESSAGE some months ago on the SIMPLE
mailing list but there has been no response from the authors. Here is the
link to the previous mails :

http://mailman.dynamicsoft.com/pipermail/simple/2002-July/001664.html


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



From mailnull@www1.ietf.org  Tue Sep 24 06:19:19 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21658
	for <sip-archive@odin.ietf.org>; Tue, 24 Sep 2002 06:19:19 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8OAKfv22451
	for sip-archive@odin.ietf.org; Tue, 24 Sep 2002 06:20:41 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8OAJmv22357;
	Tue, 24 Sep 2002 06:19:48 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8OAC5v22082
	for <sip@optimus.ietf.org>; Tue, 24 Sep 2002 06:12:05 -0400
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21551
	for <sip@ietf.org>; Tue, 24 Sep 2002 06:10:13 -0400 (EDT)
From: hisham.khartabil@nokia.com
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g8OABuT29887
	for <sip@ietf.org>; Tue, 24 Sep 2002 13:11:56 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5d8871dfd9ac158f21081@esvir01nok.ntc.nokia.com>;
 Tue, 24 Sep 2002 13:12:02 +0300
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 24 Sep 2002 13:12:01 +0300
Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 24 Sep 2002 13:12:01 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sip] Comments on draft-ietf-sip-compression-01.txt
Date: Tue, 24 Sep 2002 13:12:00 +0300
Message-ID: <2038BCC78B1AD641891A0D1AE133DBB7C20671@esebe019.ntc.nokia.com>
Thread-Topic: [Sip] Comments on draft-ietf-sip-compression-01.txt
Thread-Index: AcJjjyufgzxHtx/kTnWhgwuK1LYtQwABGdpA
To: <Gonzalo.Camarillo@lmf.ericsson.se>
Cc: <sip@ietf.org>
X-OriginalArrivalTime: 24 Sep 2002 10:12:01.0412 (UTC) FILETIME=[D2F0CC40:01C263B2]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g8OAC5v22083
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit



> -----Original Message-----
> From: ext Gonzalo Camarillo [mailto:Gonzalo.Camarillo@lmf.ericsson.se]
> Sent: Tuesday, September 24, 2002 8:55 AM
> To: Khartabil Hisham (NMP/Helsinki)
> Cc: sip@ietf.org
> Subject: Re: [Sip] Comments on draft-ietf-sip-compression-01.txt
> 
> 
> Hisham,
> 
> inline:
> 
> hisham.khartabil@nokia.com wrote:
> > 
> > - Section 4: it says:
> > 
> > "If a client sends a compressed request, it SHOULD add the parameter
> >    comp=sigcomp to the topmost entry of the Via header field."
> > 
> > Why isn't that so also for proxies?
> 
> 
> Where did you read that proxies are not clients?
> 

Are you asking me a genuine question or are you just answering my question in a patronising manner?

> 
>  
> > Section 5: Second and third paragraph. What is the purpose 
> of this? If I understand correctly, it is to allow the UAC 
> sending compressed requests within this dialog. But this doesn't work.
> > 
> > Consider this scenario
> > 
> > UA1 --- P1 --- P2 --- P3 --- UA2
> > 
> > P1 wants to compress
> > P2 doesn't want to compress
> > P3 wants to compress
> > 
> 
> When you provide an example like this, you should indicate on which
> interface each SIP entity wants to compress. In fact, the 
> purpose of the
> paragraph you are referring to, is to avoid asymmetrical compression.
> That is, if SIP messages from P1 to P2 are compressed, 
> messages from P2
> to P1 will be compressed as well.

Well, why doesn't the draft say that? I was only guessing what those 2 paragraphs where trying to achieve. I guessed so because your example gives this impression, you say "This will allow the UAC sending compressed requests within this dialog." And the result was compression all the way.

You should change your example so it shows how asymmetrical compression is avoided, not how UAC can get compression all the way.

Also, if there is such requirement that a client can request compression all the way, then you need a solution for that.


> 
> In an example like this, you also have to define if, 
> regardless of waht
> they want, they support SigComp or not. I assume that they all support
> it.

Yes, your assumption is correct. Sorry for the inconvenience.


> ...
> 
> A proxy adding sigcomp to the Record-route will add it to the 
> Via header
> as well. Therefore the Vias in your example are likely to be 
> different.

I was concentrating on RR and wasn't bothered with Vias.

Sorry again, I should have said "For clarity, only parts of the sip messages are shown".

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



From mailnull@www1.ietf.org  Tue Sep 24 22:57:16 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19322
	for <sip-archive@odin.ietf.org>; Tue, 24 Sep 2002 22:57:16 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8P2wk512210
	for sip-archive@odin.ietf.org; Tue, 24 Sep 2002 22:58:46 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8P2vSv12165;
	Tue, 24 Sep 2002 22:57:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8P2ssv12087
	for <sip@optimus.ietf.org>; Tue, 24 Sep 2002 22:54:54 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19238
	for <sip@ietf.org>; Tue, 24 Sep 2002 22:52:52 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2Z007ZY43HLS@mta2.huawei.com> for sip@ietf.org; Wed,
 25 Sep 2002 10:54:54 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2Z007UL43GM0@mta2.huawei.com> for sip@ietf.org; Wed,
 25 Sep 2002 10:54:53 +0800 (CST)
Received: from HIMANSHOOCL1153 ([10.18.5.85]) by          mailin.huawei.com
 (Netscape Messaging Server 4.15) with ESMTP id          H2Z45100.B0D; Wed,
 25 Sep 2002 10:55:49 +0800
Date: Wed, 25 Sep 2002 08:22:59 +0530
From: Himanshoo <himanshooks@huawei.com>
Subject: [Sip] certain questions on third party call control ... [2]
To: sip@ietf.org, sip-implementors@cs.columbia.edu, sip@vovida.org
Cc: jdrosen@dynamicsoft.com, schulzrinne@cs.columbia.edu
Reply-to: Himanshoo <himanshooks@huawei.com>
Message-id: <005b01c2643e$a8396980$5505120a@in.huawei.com>
Organization: Huawei
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <000101c262c0$9c8f11e0$7005120a@himanshoo>
 <3D8F2839.3080400@netscape.net> <000701c26372$b29a1860$5505120a@in.huawei.com>
 <00cd01c26385$f7a1c710$5505120a@in.huawei.com>
Content-Transfer-Encoding: 7BIT
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Hi All,

This is with reference to the mail I wrote yesterday. Kindly read the
scenario explained below and please comment on my understanding / questions.
Also, let me ask my main question again , with reference to
'draft-ietf-sipping-dialog-package-00':

Following is quoted from the above mentioned package :

 ------------------------
Abstract

    This document defines a dialog event package for the SIP Events
architecture, along with a data format used in notifications for this
package. The dialog package allows users to subscribe to another user, and
receive notifications about the changes in state of INVITE initiated dialogs
that the user is involved in.

------------------------

Can I use this package to receive notification for INVITE initiated dialogs
that the initiator is not invo,ved in ( by using "REFER; method = INVITE") ?

If not this way then is there some other way , using SIP, in which a
controller(e.g. App Server) is allowed to have monitoring session with a
switching entity (softswitch) for calls which are actually maintained by the
switch but are also monitored for call processing events by the App Server ?

Kindly do comment...

regards

Himanshoo

----- Original Message -----
From: "Himanshoo" <himanshooks@huawei.com>
To: <sip@ietf.org>; <sip-implementors@cs.columbia.edu>; <sip@vovida.org>
Sent: Tuesday, September 24, 2002 10:20 AM
Subject: [Sip] certain questions on third party call control ...


> Hi,
>
> I have certain questions related to the scenario explained below. In
> addition to the questions, can somebody please also comment if my
> understanding is correct:
>
> SCENARIO
> -------------
> Caller first dials a service access number and therefore call is given to
> the App Server by switch :
>
> Caller --(INVITE)--> Switch--(INVITE)--> App Server
>
> After this App Server Invites Media Server into the call and collects the
> destination number to which caller wants to talk to .
>
> After getting the destination number , App Server would request the switch
> to connect caller to destination number . But Application Server would
> always like to monitor the call progress (e.g. is and when call was
> answered/terminated/media characteristics changed). So finally it will be
> like this:
>
>                     App Server
>
>                          ^
>                          | (Monitoring Link)
>
> Caller----> Switch ----->Destination
>
>
> App server acts as controller . After playing the prompt to user, it
> collects digits from user and then it has to connect caller to the called
> party. Now I donot want the to develop a module on App Server, which
> connects two parties in a call, because softswitch already knows how to do
> it.. SO I use REFER (with refer-to field = Destination Number) to ask
switch
> to connect caller to the destination number, and automatically I am
> subscriber for progress of the INVITE which is used to INVITE the
> destination number . In additon I need the following:
>
> 1. Capability to do Remote Hang UP : My controller should be able to
> terminate call to the destination if the call duration exceeds 'allowed
> time'. Can I do this using 'REFER ;method = BYE' ?
> 2. After initiating the dialog using 'REFER; method = INVITE', I also need
> to know the progress of dialog. For example if either of caller and called
> party hangsup, I need to stop billing. In other words, I want to subscribe
> for the state of dialogs involving softswitch and Calling/Called Party.
> First I want to know whether I can do this by sending a SUBSCRIBE , using
> dialog package 'draft-ietf-sipping-dialog-package-00.txt'?
> Also, I want to know whether the dailog state information as per
> 'draft-ietf-sipping-dialog-package-00.txt' can also notify me of changes
in
> media characteristics (i.e. SDP for the dialog).?
> 3. Further in another scenario, if the time allowed for the calling user
> (i.e. pre-paid user) expires, and if I want to connect hm to a Media
Server
> for playing some prompt (to decide future course of action) , then can I
do
> this by sending 'REFER ; method = BYE for the dialog between softswitch
and
> called party' and then send 'REFER; method=INVITE for connecting to MRS;
In
> this case if I want to tell MRS to send the digits to APP server, instead
of
> switch , how do I do that?
>
>
> Best Regards
> Himanshoo
>
> _______________________________________________
> sip mailing list
> sip@vovida.org
> To unsubscribe, please go to http://www.vovida.org/mailman/listinfo/sip

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



From mailnull@www1.ietf.org  Wed Sep 25 02:54:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17161
	for <sip-archive@odin.ietf.org>; Wed, 25 Sep 2002 02:54:59 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8P6uT300302
	for sip-archive@odin.ietf.org; Wed, 25 Sep 2002 02:56:29 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8P6tTv32702;
	Wed, 25 Sep 2002 02:55:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8P6sDv32645
	for <sip@optimus.ietf.org>; Wed, 25 Sep 2002 02:54:13 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17101
	for <sip@ietf.org>; Wed, 25 Sep 2002 02:52:12 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.47])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g8P6rVYH029320;
	Wed, 25 Sep 2002 02:53:32 -0400 (EDT)
Message-ID: <3D915D6A.5000400@dynamicsoft.com>
Date: Wed, 25 Sep 2002 02:53:30 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
CC: sip@ietf.org
Subject: Re: [Sip] 200 UPDATE race condition
References: <3C89CD3F.4D1EA6DA@lmf.ericsson.se> <3C956590.8267E758@dynamicsoft.com> <3C95CF36.69215F7A@lmf.ericsson.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit



Christer Holmberg wrote:
> Hi,

>>>1. UA_A (the caller) receives the 200 for the INVITE, sends ACK, and
>>>then sends UPDATE, but for whatever reason the UPDATE reaches UA_B
>>>before the ACK.
>>>
>>>2. UA_A sends the UPDATE at the same time as UA_B sends the 200 for the
>>>INVITE, ie we have a race condition.
>>
>>Why? There is no SDP in the 2xx to the INVITE, or in the ACK. Thus, the
>>relative ordering of the 2xx and the UPDATE are irrelevant. There is no
>>race condition.
> 
> 
> That is true for SDP, but let's assume it's a general message body (even if
> the offer/answer rules don't allow us to include an SDP in the 2xx, I assume
> we can include other kind of message bodies - ISUP MIMEs, for example...),
> then, where the CONTENT of the message body in the UPDATE would be different
> if generated before or after the 2xx. Yes, UA_A may always generate a new
> UPDATE when it has received the 2xx, but the first UPDATE may already have
> caused some "damage".

This has nothing to do with the UPDATE spec. Sending a request with a 
body whose interpretation depends on whether the other side has sent a 
specific message or not, is a bad idea. There is no way to know whether 
or not that other message has been sent.

Anyway, this sounds academic. Is there a real problem here?

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Wed Sep 25 07:16:42 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21875
	for <sip-archive@odin.ietf.org>; Wed, 25 Sep 2002 07:16:42 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8PBI5v14565
	for sip-archive@odin.ietf.org; Wed, 25 Sep 2002 07:18:05 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PBHdv14533;
	Wed, 25 Sep 2002 07:17:39 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PBFAv14461
	for <sip@optimus.ietf.org>; Wed, 25 Sep 2002 07:15:10 -0400
Received: from david.sae.siemens.com.sg (david.sae.siemens.com.sg [194.138.243.252])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21799
	for <sip@ietf.org>; Wed, 25 Sep 2002 07:13:15 -0400 (EDT)
X-Envelope-Sender-Is: kokjeng.loh@siemens.com (at relayer david.sae.siemens.com.sg)
Received: from mail.sae.siemens.com.sg (mail.sae.siemens.com.sg [194.138.237.14])
	by david.sae.siemens.com.sg (8.11.6/8.11.6) with ESMTP id g8PBCYl02872
	for <sip@ietf.org>; Wed, 25 Sep 2002 19:12:34 +0800 (SGT)
Received: from sgpk001a.sae.siemens.com.sg (sgpk001a.sae.siemens.com.sg [140.231.107.1])
	by mail.sae.siemens.com.sg (8.11.6/8.11.6) with ESMTP id g8PBDnX05159
	for <sip@ietf.org>; Wed, 25 Sep 2002 19:13:49 +0800 (SGT)
Received: by sgpk001a.sae.siemens.com.sg with Internet Mail Service (5.5.2655.55)
	id <TG948PKN>; Wed, 25 Sep 2002 19:09:53 +0800
Message-ID: <7319EDDDE0CD7C458023FF64886CB177021FC079@sgpk001a.sae.siemens.com.sg>
From: Loh Kok Jeng <kokjeng.loh@siemens.com>
To: "'sip@ietf.org'" <sip@ietf.org>
Date: Wed, 25 Sep 2002 19:09:53 +0800
X-Mailer: Internet Mail Service (5.5.2655.55)
Subject: [Sip] Overlapping REGISTER
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>

Dear all,

In RFC3261, page 58:

      Call-ID: All registrations from a UAC SHOULD use the same Call-ID
           header field value for registrations sent to a particular
           registrar.

           If the same client were to use different Call-ID values, a
           registrar could not detect whether a delayed REGISTER request
           might have arrived out of order.

   ....

   UAs MUST NOT send a new registration (that is, containing new Contact
   header field values, as opposed to a retransmission) until they have
   received a final response from the registrar for the previous one or
   the previous REGISTER request has timed out.

If a stateful proxy receive multiple REGISTER with the same Call-ID (but
different From, To, and Contact) from the same UAC before it receives the
final response, how should it handle these REGISTER messages?  According to
the above paragraphs, this is not allowed.


regards,
KJ Loh

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



From mailnull@www1.ietf.org  Wed Sep 25 08:53:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24158
	for <sip-archive@odin.ietf.org>; Wed, 25 Sep 2002 08:53:58 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8PCtKl19284
	for sip-archive@odin.ietf.org; Wed, 25 Sep 2002 08:55:20 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PCsWv19229;
	Wed, 25 Sep 2002 08:54:32 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PCrXv19187
	for <sip@optimus.ietf.org>; Wed, 25 Sep 2002 08:53:33 -0400
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24091
	for <sip@ietf.org>; Wed, 25 Sep 2002 08:51:39 -0400 (EDT)
Received: from era-t.ericsson.se (koff.ericsson.se [147.214.173.137])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g8PCrQKV007133;
	Wed, 25 Sep 2002 14:53:26 +0200 (MEST)
Received: from ericsson.com by era-t.ericsson.se (SMI-8.6/LME-DOM-2.2.5(ERA/T))
	id OAA12327; Wed, 25 Sep 2002 14:53:24 +0200
Message-ID: <3D91B179.46E78F7F@ericsson.com>
Date: Wed, 25 Sep 2002 15:52:09 +0300
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: sip@ietf.org, Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: Keith Drage <drage@LUCENT.COM>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sip] Question about caller preferences
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi:

I had a discussion with some folks about the caller preferences draft, and we have some questions that we weren't able to answer by reading the document.

We understand that by not publishing the support for a feature set, the UA is not providing any information. Therefore, the feature set may or may not be supported at the UA.

But the question is, if the UA decides to provide information about a supported feature set, shall that information be complete?

We are thinking of the methods parameter in the Contact header for registration. In case the methods parameter is included, shall it be complete and list all the methods supported by the UA?

Example:

Contact: <sip:ua.example.com>;methods="INVITE,ACK,BYE,CANCEL,OPTIONS,REGISTER,UPDATE,SUBSCRIBE,NOTIFY,PRACK,MESSAGE"

Some folks think that the complete list is not essential. In my opinion, if a feature is present, it should be complete. In this case, all the methods supported by the UA must be present.

Other folks didn't see the need to publish the support for methods like ACK (implicitly supported if INVITE is supported), or NOTIFY (implicitly supported if SUBSCRIBE is supported).

In my opinion, that assumption is always wrong, because the methods parameter indicates support for SIP methods, not for SIP capabilities.

I would like to hear the opinion of the WG to give us some guidance.

Last, but not least, whatever is the correct thing to do, can you please add a very clear sentence to the caller preferences draft, so that there is no doubt as with respect the interpretation?

Regards,

       Miguel
-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002

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



From mailnull@www1.ietf.org  Wed Sep 25 10:11:34 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27001
	for <sip-archive@odin.ietf.org>; Wed, 25 Sep 2002 10:11:34 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8PECv923705
	for sip-archive@odin.ietf.org; Wed, 25 Sep 2002 10:12:57 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PEBlv23657;
	Wed, 25 Sep 2002 10:11:47 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PEAtv23628
	for <sip@optimus.ietf.org>; Wed, 25 Sep 2002 10:10:55 -0400
Received: from dyn-tx-app-007.dfw.dynamicsoft.com ([63.110.3.105])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26837
	for <sip@ietf.org>; Wed, 25 Sep 2002 10:09:01 -0400 (EDT)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by dyn-tx-app-007.dfw.dynamicsoft.com (8.11.6/8.11.6) with ESMTP id g8P8LH130428;
	Wed, 25 Sep 2002 03:21:17 -0500
Subject: RE: [Sip] Protocol Action: Session Initiation Protocol Extension 
	for Instant Messaging to Proposed Standard
From: Robert Sparks <rsparks@dynamicsoft.com>
To: Tan Ya-Ching ICM N PG U ID A 1 <Ya-Ching.Tan@icn.siemens.de>
Cc: sip@ietf.org
In-Reply-To: <5B4D0C5BA65ECA46969C1419122317E6E74F65@mchh161e>
References: <5B4D0C5BA65ECA46969C1419122317E6E74F65@mchh161e>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) 
Date: 25 Sep 2002 09:04:36 -0500
Message-Id: <1032962677.2122.37.camel@dhcp26.dfw.dynamicsoft.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

inline

On Tue, 2002-09-24 at 03:45, Tan Ya-Ching ICM N PG U ID A 1 wrote:
> 
> | -----Original Message-----
> | From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org]
> | Sent: 23 September 2002 18:40
> | 
> | Thank you for bringing this to our attention.  If this is correct, the
> | authors will have the opportunity to correct this during the "authors
> | 48 hours" period.
> 
> Hi,
> 
> While you are at it, you may want to add the Max-Forwards header to the
> example messages in section 10. Max-Forwards headers are mandatory in RFC
> 3261.
> 
> Perhaps this is too late, but here is my last attempt to bring up the issue
> of provisional response again. The last paragraph of section 8 is
> self-contradictory.
> 
>    It has been suggested that provisional responses should not be
>    allowed for pager-model MESSAGE requests.  However, it is not
>    possible to require special treatment for MESSAGE, since many proxy
>    servers will not be aware of the MESSAGE method.  Therefore MESSAGE
>    requests will receive the same provisional response treatment as any
>    other non-INVITE method, as described in the SIP specification.
> 
> The "same provisional response treatment as any other non-INVITE method, as
> described in the SIP specification", is exactly as the first sentence said :
> "provisional responses should not be allowed". I have raised the issue of
> allowing provisional response for MESSAGE some months ago on the SIMPLE
> mailing list but there has been no response from the authors. Here is the
> link to the previous mails :

You are misreading the first sentence. This points out that the language
should be tuned. What the first sentence tried, (and failed) to convey
to you was that some people were saying the Message spec should forbid
provisional responses, that is make them a MUST NOT (an earlier draft
contained exactly this). 3261 makes non-INVITE provisionals SHOULD NOT. 


As for:
> http://mailman.dynamicsoft.com/pipermail/simple/2002-July/001664.html

I don't understand your motivation here at all. A provisional
response to a non-INVITE doesn't squelch retransmission over UDP - it
only slows it down. Lay out the timing of messages with and without
an immediate provisional and you'll see that you reduce the total number
of messages by exactly two - and you truly damage recovery time from
loss of the final response.

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


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



From mailnull@www1.ietf.org  Wed Sep 25 10:47:30 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28180
	for <sip-archive@odin.ietf.org>; Wed, 25 Sep 2002 10:47:30 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8PEmsx25701
	for sip-archive@odin.ietf.org; Wed, 25 Sep 2002 10:48:54 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PElbv25611;
	Wed, 25 Sep 2002 10:47:37 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PEkKv25522
	for <sip@optimus.ietf.org>; Wed, 25 Sep 2002 10:46:20 -0400
Received: from magus.nostrum.com (root@magus.nostrum.com [66.119.225.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28110
	for <sip@ietf.org>; Wed, 25 Sep 2002 10:44:25 -0400 (EDT)
Received: from dynamicsoft.com (root@magus.nostrum.com [66.119.225.66])
	by magus.nostrum.com (8.12.5/8.12.5) with ESMTP id g8PEjdpA046533;
	Wed, 25 Sep 2002 09:45:40 -0500 (CDT)
Message-ID: <3D91CC0D.2010605@dynamicsoft.com>
Date: Wed, 25 Sep 2002 09:45:33 -0500
From: Ben Campbell <bcampbell@dynamicsoft.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tan Ya-Ching ICM N PG U ID A 1 <Ya-Ching.Tan@icn.siemens.de>
CC: sip@ietf.org, jdrosen@dynamicsoft.com, schulzrinne@cs.columbia.edu,
        huitema@microsoft.com, dgurle@microsoft.com
Subject: Re: [Sip] Protocol Action: Session Initiation Protocol Extension
 	 for Instant Messaging to Proposed Standard
References: <5B4D0C5BA65ECA46969C1419122317E6E74F65@mchh161e>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Tan Ya-Ching ICM N PG U ID A 1 wrote:
> | -----Original Message-----
> | From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org]
> | Sent: 23 September 2002 18:40
> | 
> | Thank you for bringing this to our attention.  If this is correct, the
> | authors will have the opportunity to correct this during the "authors
> | 48 hours" period.
> 
> Hi,
> 
> While you are at it, you may want to add the Max-Forwards header to the
> example messages in section 10. Max-Forwards headers are mandatory in RFC
> 3261.

Thanks for catching that one--we will fix in the author's 48

> 
> Perhaps this is too late, but here is my last attempt to bring up the issue
> of provisional response again. The last paragraph of section 8 is
> self-contradictory.
> 
>    It has been suggested that provisional responses should not be
>    allowed for pager-model MESSAGE requests.  However, it is not
>    possible to require special treatment for MESSAGE, since many proxy
>    servers will not be aware of the MESSAGE method.  Therefore MESSAGE
>    requests will receive the same provisional response treatment as any
>    other non-INVITE method, as described in the SIP specification.
> 
> The "same provisional response treatment as any other non-INVITE method, as
> described in the SIP specification", is exactly as the first sentence said :
> "provisional responses should not be allowed". I have raised the issue of
> allowing provisional response for MESSAGE some months ago on the SIMPLE
> mailing list but there has been no response from the authors. Here is the
> link to the previous mails :

No, 3261 says SHOULD NOT, which is not the same as MUST NOT.

> 
> http://mailman.dynamicsoft.com/pipermail/simple/2002-July/001664.html
> 

I thought we had responded to that one--sorry if it fell through the 
cracks. MESSAGE is based on the non-invite transaction model, where 
provisionals essentially do more harm than good. If we wanted to use 
provisionals for the purpose you suggest, we would need a completely new 
transaction model, which does not seem worthwhile.

> 
> Regards,
> Ya-Ching Tan


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



From mailnull@www1.ietf.org  Wed Sep 25 10:59:45 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28625
	for <sip-archive@odin.ietf.org>; Wed, 25 Sep 2002 10:59:45 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8PF19L26258
	for sip-archive@odin.ietf.org; Wed, 25 Sep 2002 11:01:09 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PF0nv26226;
	Wed, 25 Sep 2002 11:00:49 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8O4oDv29058
	for <sip@optimus.ietf.org>; Tue, 24 Sep 2002 00:50:13 -0400
Received: from mail.bhartitelesoft.com ([202.56.229.147])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07352
	for <sip@ietf.org>; Tue, 24 Sep 2002 00:48:04 -0400 (EDT)
Received: from sharad (sharad [172.16.3.67])
	by mail.bhartitelesoft.com (8.11.0/8.11.0) with SMTP id g8O4dA918307;
	Tue, 24 Sep 2002 10:09:10 +0530
Reply-To: <sharad@bhartitelesoft.com>
From: "Sharad Goklani" <sharad@bhartitelesoft.com>
To: <ranjit.avasarala@bplmail.com>, "'Himanshoo Ks'" <himanshooks@huawei.com>,
        <sip@ietf.org>, <sip-implementors@cs.columbia.edu>
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO
Date: Tue, 24 Sep 2002 10:19:09 +0530
Message-ID: <001001c26385$b8c7d7a0$430310ac@bhartitelesoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
In-Reply-To: <FEEJJMJJLHGIMEGAPBJJCEGMCAAA.ranjit.avasarala@bplmail.com>
X-ECS-MailScanner: Found to be clean
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Cool ... Got it!
Sharad

-----Original Message-----
From: Ranjit Avasarala [mailto:ranjit.avasarala@bplmail.com]
Sent: Tuesday, September 24, 2002 10:02 AM
To: sharad@bhartitelesoft.com; 'Himanshoo Ks'; sip@ietf.org;
sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


u cannot use SUBSCRIBE/NOTIFY be'se you get NOTIFY when there is a change in
the state of the subscription. but here the case is of event detection. so
as Himanshoo says INFO could be useful

Ranjit :-)

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Sharad
Goklani
Sent: Monday, September 23, 2002 3:01 PM
To: 'Himanshoo Ks'; sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


But can't this be done using SUBSCRIBE/NOTIFY ?
Sharad

-----Original Message-----
From: sip-implementors-admin@cs.columbia.edu
[mailto:sip-implementors-admin@cs.columbia.edu]On Behalf Of Himanshoo Ks
Sent: Monday, September 23, 2002 1:42 PM
To: sip@ietf.org; sip-implementors@cs.columbia.edu
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO


Hi ,

After reading all of your mails I looked at some of the drafts which are
related to carrying MGCP events  / messages inside SIP INFO Message. If I
follow that approach then it appears that I can first send an INFO request
and include 'MGCP Requested Events' to request detection of events. Later
when that event is deteted, the detectng entitiy will send another INFO
Request with 'MGCP observed events' . By using this approach I can control
the events which are reported to the requestign entity.
This is one use of the INFO message which seems to be very useful.

Regards
Himanshoo

_______________________________________________
Sip-implementors mailing list
Sip-implementors@cs.columbia.edu
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

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

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



From mailnull@www1.ietf.org  Wed Sep 25 13:42:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04187
	for <sip-archive@odin.ietf.org>; Wed, 25 Sep 2002 13:42:02 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8PHhSw03029
	for sip-archive@odin.ietf.org; Wed, 25 Sep 2002 13:43:28 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PHh1v02999;
	Wed, 25 Sep 2002 13:43:01 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PHfjv02955
	for <sip@optimus.ietf.org>; Wed, 25 Sep 2002 13:41:45 -0400
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04081
	for <sip@ietf.org>; Wed, 25 Sep 2002 13:39:48 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id g8PHf2Ha001465;
	Wed, 25 Sep 2002 10:41:02 -0700 (PDT)
Received: from open-131-161-248-87.cliq.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.1.0.66-GA)
	with ESMTP id AAY88418;
	Wed, 25 Sep 2002 10:38:58 -0700 (PDT)
Date: Wed, 25 Sep 2002 10:42:20 -0700
Subject: Re: [Sip] Protocol Action: Session Initiation Protocol Extension  for Instant Messaging to Proposed Standard
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v482)
Cc: Tan Ya-Ching ICM N PG U ID A 1 <Ya-Ching.Tan@icn.siemens.de>, sip@ietf.org
To: Robert Sparks <rsparks@dynamicsoft.com>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <1032962677.2122.37.camel@dhcp26.dfw.dynamicsoft.com>
Message-Id: <2437DB66-D0AE-11D6-A5C1-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.482)
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


On Wednesday, September 25, 2002, at 07:04 AM, Robert Sparks wrote:
>> Perhaps this is too late, but here is my last attempt to bring up the 
>> issue
>> of provisional response again. The last paragraph of section 8 is
>> self-contradictory.
>>
>>    It has been suggested that provisional responses should not be
>>    allowed for pager-model MESSAGE requests.  However, it is not
>>    possible to require special treatment for MESSAGE, since many proxy
>>    servers will not be aware of the MESSAGE method.  Therefore MESSAGE
>>    requests will receive the same provisional response treatment as any
>>    other non-INVITE method, as described in the SIP specification.

we are discussing two issues here.  one is how the UAS TU acts, and the 
other is how the non-INVITE transaction layer acts.  we can more 
stringently enforce UAS behavior for MESSAGE requests if we'd like.  two 
suggestions below (I prefer #1).

thanks,
-rohan


Suggested replacement text #1:
A UAS compliant to this specification MUST NOT respond to MESSAGE 
requests with a provisional response. Provisional responses to 
non-INVITE requests cause more harm than good (they prevent timely 
retransmission of the final response). Note that for 
backward-compatibility reasons, the SIP transaction layer still MUST be 
prepared to receive a provisional response to any request as described 
in RFC3261.

Suggested replacement text #2:
Provisional responses to MESSAGE requests are handled the same way as 
for any non-INVITE request. As discussed in RFC3261 section x.y, a UAS 
SHOULD NOT respond to MESSAGE requests (or other non-INVITE methods) 
with a provisional response. In general, provisional responses to 
non-INVITE requests cause more harm than good (they prevent timely 
retransmission of the final response).


>> The "same provisional response treatment as any other non-INVITE 
>> method, as
>> described in the SIP specification", is exactly as the first sentence 
>> said :
>> "provisional responses should not be allowed". I have raised the issue 
>> of
>> allowing provisional response for MESSAGE some months ago on the SIMPLE
>> mailing list but there has been no response from the authors. Here is 
>> the
>> link to the previous mails :
>
> You are misreading the first sentence. This points out that the language
> should be tuned. What the first sentence tried, (and failed) to convey
> to you was that some people were saying the Message spec should forbid
> provisional responses, that is make them a MUST NOT (an earlier draft
> contained exactly this). 3261 makes non-INVITE provisionals SHOULD NOT.
>
>
> As for:
>> http://mailman.dynamicsoft.com/pipermail/simple/2002-July/001664.html
>
> I don't understand your motivation here at all. A provisional
> response to a non-INVITE doesn't squelch retransmission over UDP - it
> only slows it down. Lay out the timing of messages with and without
> an immediate provisional and you'll see that you reduce the total number
> of messages by exactly two - and you truly damage recovery time from
> loss of the final response.
>
>>
>>
>> Regards,
>> Ya-Ching Tan
>> _______________________________________________
>> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of sip
>
>
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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



From mailnull@www1.ietf.org  Wed Sep 25 16:49:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09799
	for <sip-archive@odin.ietf.org>; Wed, 25 Sep 2002 16:49:59 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8PKpQ212577
	for sip-archive@odin.ietf.org; Wed, 25 Sep 2002 16:51:26 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PKo6v12530;
	Wed, 25 Sep 2002 16:50:06 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PKlOv12364
	for <sip@optimus.ietf.org>; Wed, 25 Sep 2002 16:47:24 -0400
Received: from magus.nostrum.com (root@magus.nostrum.com [66.119.225.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09618
	for <sip@ietf.org>; Wed, 25 Sep 2002 16:45:26 -0400 (EDT)
Received: from dynamicsoft.com (root@magus.nostrum.com [66.119.225.66])
	by magus.nostrum.com (8.12.5/8.12.5) with ESMTP id g8PKkFpA072669;
	Wed, 25 Sep 2002 15:46:16 -0500 (CDT)
Message-ID: <3D922090.3070402@dynamicsoft.com>
Date: Wed, 25 Sep 2002 15:46:08 -0500
From: Ben Campbell <bcampbell@dynamicsoft.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rohan Mahy <rohan@cisco.com>
CC: Robert Sparks <rsparks@dynamicsoft.com>,
        Tan Ya-Ching ICM N PG U ID A 1 <Ya-Ching.Tan@icn.siemens.de>,
        sip@ietf.org
Subject: Re: [Sip] Protocol Action: Session Initiation Protocol Extension
  for Instant Messaging to Proposed Standard
References: <2437DB66-D0AE-11D6-A5C1-0003938AF740@cisco.com>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

The current version pretty much is the same as your option 2, except 
that avoided repeating the 3261 language. I guess that is a trade off 
between manageablility vs. convenience of the reader. Since 3261 is 
stable now, it is no big deal to add it in the author's 48.

As for option 1, I'm not sure why MESSAGE needs to have any more or less 
restriction here than any other non-invite method. If your desire is to 
strengthen the restriction for all non-invites, then it seems that the 
place to do that is in the base spec, not the extension.

It is worth noting that the original paragraph was there in response to 
an AD suggestion that was later withdrawn as we added more 
congestion-control language. It may be the best thing to do is strike 
the whole paragraph. Provisionals are treated the same as for any other 
non-invite, therefore this draft doesn't need to discuss them.

Rohan Mahy wrote:
> 
> On Wednesday, September 25, 2002, at 07:04 AM, Robert Sparks wrote:
> 
>>> Perhaps this is too late, but here is my last attempt to bring up the 
>>> issue
>>> of provisional response again. The last paragraph of section 8 is
>>> self-contradictory.
>>>
>>>    It has been suggested that provisional responses should not be
>>>    allowed for pager-model MESSAGE requests.  However, it is not
>>>    possible to require special treatment for MESSAGE, since many proxy
>>>    servers will not be aware of the MESSAGE method.  Therefore MESSAGE
>>>    requests will receive the same provisional response treatment as any
>>>    other non-INVITE method, as described in the SIP specification.
>>
> 
> we are discussing two issues here.  one is how the UAS TU acts, and the 
> other is how the non-INVITE transaction layer acts.  we can more 
> stringently enforce UAS behavior for MESSAGE requests if we'd like.  two 
> suggestions below (I prefer #1).
> 
> thanks,
> -rohan
> 
> 
> Suggested replacement text #1:
> A UAS compliant to this specification MUST NOT respond to MESSAGE 
> requests with a provisional response. Provisional responses to 
> non-INVITE requests cause more harm than good (they prevent timely 
> retransmission of the final response). Note that for 
> backward-compatibility reasons, the SIP transaction layer still MUST be 
> prepared to receive a provisional response to any request as described 
> in RFC3261.
> 
> Suggested replacement text #2:
> Provisional responses to MESSAGE requests are handled the same way as 
> for any non-INVITE request. As discussed in RFC3261 section x.y, a UAS 
> SHOULD NOT respond to MESSAGE requests (or other non-INVITE methods) 
> with a provisional response. In general, provisional responses to 
> non-INVITE requests cause more harm than good (they prevent timely 
> retransmission of the final response).
> 
> 
>>> The "same provisional response treatment as any other non-INVITE 
>>> method, as
>>> described in the SIP specification", is exactly as the first sentence 
>>> said :
>>> "provisional responses should not be allowed". I have raised the 
>>> issue of
>>> allowing provisional response for MESSAGE some months ago on the SIMPLE
>>> mailing list but there has been no response from the authors. Here is 
>>> the
>>> link to the previous mails :
>>
>>
>> You are misreading the first sentence. This points out that the language
>> should be tuned. What the first sentence tried, (and failed) to convey
>> to you was that some people were saying the Message spec should forbid
>> provisional responses, that is make them a MUST NOT (an earlier draft
>> contained exactly this). 3261 makes non-INVITE provisionals SHOULD NOT.
>>
>>
>> As for:
>>
>>> http://mailman.dynamicsoft.com/pipermail/simple/2002-July/001664.html
>>
>>
>> I don't understand your motivation here at all. A provisional
>> response to a non-INVITE doesn't squelch retransmission over UDP - it
>> only slows it down. Lay out the timing of messages with and without
>> an immediate provisional and you'll see that you reduce the total number
>> of messages by exactly two - and you truly damage recovery time from
>> loss of the final response.
>>
>>>
>>>
>>> Regards,
>>> Ya-Ching Tan
>>> _______________________________________________
>>> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol
>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>> Use sipping@ietf.org for new developments on the application of sip
>>
>>
>>
>> _______________________________________________
>> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of sip
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 


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



From mailnull@www1.ietf.org  Wed Sep 25 16:54:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09895
	for <sip-archive@odin.ietf.org>; Wed, 25 Sep 2002 16:54:43 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8PKuAI12716
	for sip-archive@odin.ietf.org; Wed, 25 Sep 2002 16:56:10 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PKtBv12689;
	Wed, 25 Sep 2002 16:55:11 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PKs1v12631
	for <sip@optimus.ietf.org>; Wed, 25 Sep 2002 16:54:01 -0400
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09825
	for <sip@ietf.org>; Wed, 25 Sep 2002 16:52:03 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8PKrA1X008387;
	Wed, 25 Sep 2002 13:53:10 -0700 (PDT)
Received: from open-131-161-248-87.cliq.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.1.0.66-GA)
	with ESMTP id AAY97910;
	Wed, 25 Sep 2002 13:51:06 -0700 (PDT)
Date: Wed, 25 Sep 2002 13:54:27 -0700
Subject: Re: [Sip] Protocol Action: Session Initiation Protocol Extension for Instant Messaging to Proposed Standard
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v482)
Cc: Robert Sparks <rsparks@dynamicsoft.com>,
        Tan Ya-Ching ICM N PG U ID A 1 <Ya-Ching.Tan@icn.siemens.de>,
        sip@ietf.org
To: Ben Campbell <bcampbell@dynamicsoft.com>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <3D922090.3070402@dynamicsoft.com>
Message-Id: <FAE61372-D0C8-11D6-A5C1-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.482)
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


On Wednesday, September 25, 2002, at 01:46 PM, Ben Campbell wrote:

> The current version pretty much is the same as your option 2, except 
> that avoided repeating the 3261 language. I guess that is a trade off 
> between manageablility vs. convenience of the reader. Since 3261 is 
> stable now, it is no big deal to add it in the author's 48.

option 2 is also more clear than the current language.

> As for option 1, I'm not sure why MESSAGE needs to have any more or 
> less restriction here than any other non-invite method. If your desire 
> is to strengthen the restriction for all non-invites, then it seems 
> that the place to do that is in the base spec, not the extension.

well, since the base spec didn't say this, and won't be updated for a 
while, we certainly have a legitimate reason to say this now for all NEW 
non-INVITE extension methods.

> It is worth noting that the original paragraph was there in response to 
> an AD suggestion that was later withdrawn as we added more 
> congestion-control language. It may be the best thing to do is strike 
> the whole paragraph. Provisionals are treated the same as for any other 
> non-invite, therefore this draft doesn't need to discuss them.

i really want us to prevent folks from sending provisionals and CANCELs 
for non-INVITE.  I don't think that's a lot to ask.

thanks,
-rohan


> Rohan Mahy wrote:
>> On Wednesday, September 25, 2002, at 07:04 AM, Robert Sparks wrote:
>>>> Perhaps this is too late, but here is my last attempt to bring up 
>>>> the issue
>>>> of provisional response again. The last paragraph of section 8 is
>>>> self-contradictory.
>>>>
>>>>    It has been suggested that provisional responses should not be
>>>>    allowed for pager-model MESSAGE requests.  However, it is not
>>>>    possible to require special treatment for MESSAGE, since many 
>>>> proxy
>>>>    servers will not be aware of the MESSAGE method.  Therefore 
>>>> MESSAGE
>>>>    requests will receive the same provisional response treatment as 
>>>> any
>>>>    other non-INVITE method, as described in the SIP specification.
>>>
>> we are discussing two issues here.  one is how the UAS TU acts, and 
>> the other is how the non-INVITE transaction layer acts.  we can more 
>> stringently enforce UAS behavior for MESSAGE requests if we'd like.  
>> two suggestions below (I prefer #1).
>> thanks,
>> -rohan
>> Suggested replacement text #1:
>> A UAS compliant to this specification MUST NOT respond to MESSAGE 
>> requests with a provisional response. Provisional responses to 
>> non-INVITE requests cause more harm than good (they prevent timely 
>> retransmission of the final response). Note that for 
>> backward-compatibility reasons, the SIP transaction layer still MUST 
>> be prepared to receive a provisional response to any request as 
>> described in RFC3261.
>> Suggested replacement text #2:
>> Provisional responses to MESSAGE requests are handled the same way as 
>> for any non-INVITE request. As discussed in RFC3261 section x.y, a UAS 
>> SHOULD NOT respond to MESSAGE requests (or other non-INVITE methods) 
>> with a provisional response. In general, provisional responses to 
>> non-INVITE requests cause more harm than good (they prevent timely 
>> retransmission of the final response).
>>>> The "same provisional response treatment as any other non-INVITE 
>>>> method, as
>>>> described in the SIP specification", is exactly as the first 
>>>> sentence said :
>>>> "provisional responses should not be allowed". I have raised the 
>>>> issue of
>>>> allowing provisional response for MESSAGE some months ago on the 
>>>> SIMPLE
>>>> mailing list but there has been no response from the authors. Here 
>>>> is the
>>>> link to the previous mails :
>>>
>>>
>>> You are misreading the first sentence. This points out that the 
>>> language
>>> should be tuned. What the first sentence tried, (and failed) to convey
>>> to you was that some people were saying the Message spec should forbid
>>> provisional responses, that is make them a MUST NOT (an earlier draft
>>> contained exactly this). 3261 makes non-INVITE provisionals SHOULD 
>>> NOT.
>>>
>>>
>>> As for:
>>>
>>>> http://mailman.dynamicsoft.com/pipermail/simple/2002-July/001664.html
>>>
>>>
>>> I don't understand your motivation here at all. A provisional
>>> response to a non-INVITE doesn't squelch retransmission over UDP - it
>>> only slows it down. Lay out the timing of messages with and without
>>> an immediate provisional and you'll see that you reduce the total 
>>> number
>>> of messages by exactly two - and you truly damage recovery time from
>>> loss of the final response.
>>>
>>>>
>>>>
>>>> Regards,
>>>> Ya-Ching Tan
>>>> _______________________________________________
>>>> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>>>> This list is for NEW development of the core SIP Protocol
>>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>>> Use sipping@ietf.org for new developments on the application of sip
>>>
>>>
>>>
>>> _______________________________________________
>>> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol
>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>> Use sipping@ietf.org for new developments on the application of sip
>> _______________________________________________
>> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of sip
>
>

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



From mailnull@www1.ietf.org  Wed Sep 25 17:08:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10286
	for <sip-archive@odin.ietf.org>; Wed, 25 Sep 2002 17:08:59 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8PLAQ213962
	for sip-archive@odin.ietf.org; Wed, 25 Sep 2002 17:10:26 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PL9Ov13928;
	Wed, 25 Sep 2002 17:09:24 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PL8Jv13894
	for <sip@optimus.ietf.org>; Wed, 25 Sep 2002 17:08:19 -0400
Received: from magus.nostrum.com (root@magus.nostrum.com [66.119.225.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10216
	for <sip@ietf.org>; Wed, 25 Sep 2002 17:06:21 -0400 (EDT)
Received: from dynamicsoft.com (root@magus.nostrum.com [66.119.225.66])
	by magus.nostrum.com (8.12.5/8.12.5) with ESMTP id g8PL7qpA074226;
	Wed, 25 Sep 2002 16:07:52 -0500 (CDT)
Message-ID: <3D9225A0.2060509@dynamicsoft.com>
Date: Wed, 25 Sep 2002 16:07:44 -0500
From: Ben Campbell <bcampbell@dynamicsoft.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rohan Mahy <rohan@cisco.com>
CC: Robert Sparks <rsparks@dynamicsoft.com>,
        Tan Ya-Ching ICM N PG U ID A 1 <Ya-Ching.Tan@icn.siemens.de>,
        sip@ietf.org
Subject: Re: [Sip] Protocol Action: Session Initiation Protocol Extension
 for Instant Messaging to Proposed Standard
References: <FAE61372-D0C8-11D6-A5C1-0003938AF740@cisco.com>
X-Enigmail-Version: 0.65.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Rohan Mahy wrote:
> i really want us to prevent folks from sending provisionals and CANCELs 
> for non-INVITE.  I don't think that's a lot to ask.

Regardless of whether I agree that we should forbid provisionals for 
non-invite, I really hate to encumber MESSAGE with that discussion at 
this point in time--The IESG has approved the current version with a few 
unrelated edits. This seems a bit much for an author's 48 change.

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



From mailnull@www1.ietf.org  Thu Sep 26 13:24:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15740
	for <sip-archive@odin.ietf.org>; Thu, 26 Sep 2002 13:24:52 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8QHQJi19820
	for sip-archive@odin.ietf.org; Thu, 26 Sep 2002 13:26:19 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QHPEv19784;
	Thu, 26 Sep 2002 13:25:14 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QHMDv19678
	for <sip@optimus.ietf.org>; Thu, 26 Sep 2002 13:22:13 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15666
	for <sip@ietf.org>; Thu, 26 Sep 2002 13:20:15 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.47])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g8QHLSYH000353;
	Thu, 26 Sep 2002 13:21:28 -0400 (EDT)
Message-ID: <3D934217.50505@dynamicsoft.com>
Date: Thu, 26 Sep 2002 13:21:27 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
CC: sip@ietf.org, Keith Drage <drage@LUCENT.COM>
References: <3D91B179.46E78F7F@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sip] Re: Question about caller preferences
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

inline.

Miguel A. Garcia wrote:
 > Hi:
 >
 > I had a discussion with some folks about the caller preferences
 > draft, and we have some questions that we weren't able to answer by
 > reading the document.
 >
 > We understand that by not publishing the support for a feature set,
 > the UA is not providing any information. Therefore, the feature set
 > may or may not be supported at the UA.

Actually, RFC 2533 (which we are using) does say something concrete 
about what it means to say nothing about a feature tag. It means that 
you are supporting all values. This means you need to be careful about 
the semantics of the headers - the existing Reject-Contact semantic of 
"reject this contact if its feature set matches" is bad, because it will 
cause a UA to be rejected even if it has said nothing about a particular 
feature tag!

 >
 > But the question is, if the UA decides to provide information about a
 > supported feature set, shall that information be complete?

Yes.

 >
 > We are thinking of the methods parameter in the Contact header for
 > registration. In case the methods parameter is included, shall it be
 > complete and list all the methods supported by the UA?

Yes.

There was a thread on the list (likely followed by no one) between 
myself, Juha, and Paul K. on this exact issue. Our conclusion was that 
it was reasonable to mandate that a UA include all values it supports 
for a feature tag, when it includes that feature tag.

 >
 > Example:
 >
 > Contact:
 > <sip:ua.example.com>;methods="INVITE,ACK,BYE,CANCEL,OPTIONS,REGISTER,-
 > UPDATE,SUBSCRIBE,NOTIFY,PRACK,MESSAGE"
 >
 > Some folks think that the complete list is not essential. In my
 > opinion, if a feature is present, it should be complete. In this
 > case, all the methods supported by the UA must be present.

That is correct.

 >
 > Other folks didn't see the need to publish the support for methods
 > like ACK (implicitly supported if INVITE is supported), or NOTIFY
 > (implicitly supported if SUBSCRIBE is supported).
 >
 > In my opinion, that assumption is always wrong, because the methods
 > parameter indicates support for SIP methods, not for SIP
 > capabilities.

I would agree. Without listing all methods, you put the burden on the 
server to lean what other methods a UA will support based on the ones it 
listed. That won't always be a trivial exercise.

 >
 > I would like to hear the opinion of the WG to give us some guidance.
 >
 > Last, but not least, whatever is the correct thing to do, can you
 > please add a very clear sentence to the caller preferences draft, so
 > that there is no doubt as with respect the interpretation?

Yes. I have already done that in my working draft as a result of the 
aforementioned thread with Paul K. and Juha.

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Thu Sep 26 20:01:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26088
	for <sip-archive@odin.ietf.org>; Thu, 26 Sep 2002 20:01:47 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8R03Hi07392
	for sip-archive@odin.ietf.org; Thu, 26 Sep 2002 20:03:17 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8R01kv07358;
	Thu, 26 Sep 2002 20:01:46 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QNxqv07267
	for <sip@optimus.ietf.org>; Thu, 26 Sep 2002 19:59:52 -0400
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26048
	for <sip@ietf.org>; Thu, 26 Sep 2002 19:57:52 -0400 (EDT)
Received: from era-t.ericsson.se (koff.ericsson.se [147.214.173.137])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g8QNxbKV020374;
	Fri, 27 Sep 2002 01:59:37 +0200 (MEST)
Received: from ericsson.com by era-t.ericsson.se (SMI-8.6/LME-DOM-2.2.5(ERA/T))
	id BAA26052; Fri, 27 Sep 2002 01:59:36 +0200
Message-ID: <3D939F74.C9F7F983@ericsson.com>
Date: Fri, 27 Sep 2002 02:59:48 +0300
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: es,en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: sip@ietf.org, Keith Drage <drage@LUCENT.COM>
References: <3D91B179.46E78F7F@ericsson.com> <3D934217.50505@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sip] Re: Question about caller preferences
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Jonathan Rosenberg wrote:
> 
> inline.
> 
> Miguel A. Garcia wrote:
>  > Hi:
>  >
>  > I had a discussion with some folks about the caller preferences
>  > draft, and we have some questions that we weren't able to answer by
>  > reading the document.
>  >
>  > We understand that by not publishing the support for a feature set,
>  > the UA is not providing any information. Therefore, the feature set
>  > may or may not be supported at the UA.
> 
> Actually, RFC 2533 (which we are using) does say something concrete
> about what it means to say nothing about a feature tag. It means that
> you are supporting all values. This means you need to be careful about
> the semantics of the headers - the existing Reject-Contact semantic of
> "reject this contact if its feature set matches" is bad, because it will
> cause a UA to be rejected even if it has said nothing about a particular
> feature tag!s
> 
> 

This is a little bit weird. I consider that the feature tags are not closed,
they are or will be expanding, and new feature tags will appear in the 
future. 

Imagine that my UA implements feature tags 1, 2 and 3. A new feature 4 is 
defined, and my proxy or the remote UA supports that feature, by not my UA. 
Then, are you saying that the proxy or the remote UA will think that my 
terminal supports feature 4 because my UA didn't say anything about that?

That is not what I consider support for backward compatibility.

/Miguel
-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                        Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 5140002
_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip



From mailnull@www1.ietf.org  Fri Sep 27 16:10:36 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09331
	for <sip-archive@odin.ietf.org>; Fri, 27 Sep 2002 16:10:36 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8RKC5O11472
	for sip-archive@odin.ietf.org; Fri, 27 Sep 2002 16:12:05 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8RKBSv11411;
	Fri, 27 Sep 2002 16:11:28 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8RK4Av10724
	for <sip@optimus.ietf.org>; Fri, 27 Sep 2002 16:04:10 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08920
	for <sip@ietf.org>; Fri, 27 Sep 2002 16:02:09 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.40])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g8RK3SYH001228;
	Fri, 27 Sep 2002 16:03:28 -0400 (EDT)
Message-ID: <3D94B98B.6060907@dynamicsoft.com>
Date: Fri, 27 Sep 2002 16:03:23 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
CC: sip@ietf.org, Keith Drage <drage@LUCENT.COM>
References: <3D91B179.46E78F7F@ericsson.com> <3D934217.50505@dynamicsoft.com> <3D939F74.C9F7F983@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sip] Re: Question about caller preferences
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

inline.

Miguel A. Garcia wrote:
> Jonathan Rosenberg wrote:
> 
>>inline.
>>
>>Miguel A. Garcia wrote:
>> > Hi:
>> >
>> > I had a discussion with some folks about the caller preferences
>> > draft, and we have some questions that we weren't able to answer by
>> > reading the document.
>> >
>> > We understand that by not publishing the support for a feature set,
>> > the UA is not providing any information. Therefore, the feature set
>> > may or may not be supported at the UA.
>>
>>Actually, RFC 2533 (which we are using) does say something concrete
>>about what it means to say nothing about a feature tag. It means that
>>you are supporting all values. This means you need to be careful about
>>the semantics of the headers - the existing Reject-Contact semantic of
>>"reject this contact if its feature set matches" is bad, because it will
>>cause a UA to be rejected even if it has said nothing about a particular
>>feature tag!s
>>
>>
> 
> 
> This is a little bit weird. I consider that the feature tags are not closed,
> they are or will be expanding, and new feature tags will appear in the 
> future. 

Absolutely.

> 
> Imagine that my UA implements feature tags 1, 2 and 3. A new feature 4 is 
> defined, and my proxy or the remote UA supports that feature, by not my UA. 
> Then, are you saying that the proxy or the remote UA will think that my 
> terminal supports feature 4 because my UA didn't say anything about that?

No, I'm not saying that.

 From the syntax in the contact header that describes the capabilities 
(the predicate), its clear what the UA is explicitly saying, and what 
its omitting. So, a UA that sees the predicate in a 200 OK to an INVITE, 
for example, will know what is supported and what is omitted, and so 
does a proxy that sees one in a REGISTER.

What I AM saying is that the matching operation used for routing doesn't 
care. If a caller places into an INVITE an Accept-Contact saying that 
feature tag 4 should have a value of foo, a proxy will route this call 
to UA's that explicitly indicate that they support this value, and to 
those that say nothing.

This is reasonable; the complete lack of information about a feature tag 
should not imply its not supported. Interoperability is better if you 
assume that no information means that it may or may not be supported, 
and then let the protocol itself deal with the situation where its not 
(i.e., reject with 405, 415, etc). This is explicitly called out in rfc2533:

> 3.4.2 Recipient capabilities
> 
>    The following expression describes a receiving system that has:
>    (a)  a screen capable of displaying 640*480 pixels and 16 million
>         colours (24 bits per pixel), 800*600 pixels and 64 thousand
>         colours (16 bits per pixel) or 1024*768 pixels and 256 colours
>         (8 bits per pixel), or
>    (b)  a printer capable of rendering 300dpi on A4 paper.
> 
>          (| (& (| (& (pix-x<=640)  (pix-y<=480) (color<=16777216) )
>                   (& (pix-x<=800)  (pix-y<=600) (color<=65535) )
>                   (& (pix-x<=1024) (pix-y<=768) (color<=256) ) )
>                (ua-media=screen) )
>             (& (dpi=300)
>                (ua-media=stationery) (papersize=iso-A4) ) )
> 
>    Note that this expression says nothing about the colour or grey-scale
>    capabilities of the printer.  In the scheme presented here, it is
>    presumed to be unconstrained in this respect (or, more realistically,
>    any such constraints are handled out-of-band by anyone sending to
>    this recipient).

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Mon Sep 30 01:45:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15261
	for <sip-archive@odin.ietf.org>; Mon, 30 Sep 2002 01:45:32 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8U5l8706189
	for sip-archive@odin.ietf.org; Mon, 30 Sep 2002 01:47:08 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8U5jtv06157;
	Mon, 30 Sep 2002 01:45:55 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8U5fdv06040
	for <sip@optimus.ietf.org>; Mon, 30 Sep 2002 01:41:39 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15187
	for <sip@ietf.org>; Mon, 30 Sep 2002 01:39:32 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.14])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g8U5elYH002095;
	Mon, 30 Sep 2002 01:40:48 -0400 (EDT)
Message-ID: <3D97E3DE.6040101@dynamicsoft.com>
Date: Mon, 30 Sep 2002 01:40:46 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Loh Kok Jeng <kokjeng.loh@siemens.com>
CC: "'sip@ietf.org'" <sip@ietf.org>
Subject: Re: [Sip] Overlapping REGISTER
References: <7319EDDDE0CD7C458023FF64886CB177021FC079@sgpk001a.sae.siemens.com.sg>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

inline.

Loh Kok Jeng wrote:
> Dear all,
> 
> In RFC3261, page 58:
> 
>       Call-ID: All registrations from a UAC SHOULD use the same Call-ID
>            header field value for registrations sent to a particular
>            registrar.
> 
>            If the same client were to use different Call-ID values, a
>            registrar could not detect whether a delayed REGISTER request
>            might have arrived out of order.
> 
>    ....
> 
>    UAs MUST NOT send a new registration (that is, containing new Contact
>    header field values, as opposed to a retransmission) until they have
>    received a final response from the registrar for the previous one or
>    the previous REGISTER request has timed out.
> 
> If a stateful proxy receive multiple REGISTER with the same Call-ID (but
> different From, To, and Contact) from the same UAC before it receives the
> final response, how should it handle these REGISTER messages?  According to
> the above paragraphs, this is not allowed.

This is an unusual case. The spec does prohibit a client from sending 
it. However, there is actually nothing wrong with this scenario, and the 
regular server processing in 10.3 will do the right thing. If the To 
field changes between the two registrations, the ordering is no longer 
relevant in terms of the processing of the two transactions - they refer 
to different addresses of record. It is totally irrelevant in this case 
that they happen to come from the same UA.


-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Mon Sep 30 01:47:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15308
	for <sip-archive@odin.ietf.org>; Mon, 30 Sep 2002 01:47:58 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8U5nYK06272
	for sip-archive@odin.ietf.org; Mon, 30 Sep 2002 01:49:34 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8U5mpv06239;
	Mon, 30 Sep 2002 01:48:51 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8U5hkv06093
	for <sip@optimus.ietf.org>; Mon, 30 Sep 2002 01:43:46 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15213
	for <sip@ietf.org>; Mon, 30 Sep 2002 01:41:39 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.14])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g8U5h3YH002098;
	Mon, 30 Sep 2002 01:43:03 -0400 (EDT)
Message-ID: <3D97E466.4020608@dynamicsoft.com>
Date: Mon, 30 Sep 2002 01:43:02 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ben Campbell <bcampbell@dynamicsoft.com>
CC: Rohan Mahy <rohan@cisco.com>, Robert Sparks <rsparks@dynamicsoft.com>,
        Tan Ya-Ching ICM N PG U ID A 1 <Ya-Ching.Tan@icn.siemens.de>,
        sip@ietf.org
Subject: Re: [Sip] Protocol Action: Session Initiation Protocol Extension
 for Instant Messaging to Proposed Standard
References: <FAE61372-D0C8-11D6-A5C1-0003938AF740@cisco.com> <3D9225A0.2060509@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I strongly concur with Ben; the MESSAGE spec is not the place to change 
the wording on the strength of sending provisionals for non-INVITE requests.

-Jonathan R.

Ben Campbell wrote:
> Rohan Mahy wrote:
> 
>> i really want us to prevent folks from sending provisionals and 
>> CANCELs for non-INVITE.  I don't think that's a lot to ask.
> 
> 
> Regardless of whether I agree that we should forbid provisionals for 
> non-invite, I really hate to encumber MESSAGE with that discussion at 
> this point in time--The IESG has approved the current version with a few 
> unrelated edits. This seems a bit much for an author's 48 change.
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Mon Sep 30 02:20:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24851
	for <sip-archive@odin.ietf.org>; Mon, 30 Sep 2002 02:20:22 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8U6Lw715877
	for sip-archive@odin.ietf.org; Mon, 30 Sep 2002 02:21:58 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8U6LTv15858;
	Mon, 30 Sep 2002 02:21:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8U6Kav15802
	for <sip@optimus.ietf.org>; Mon, 30 Sep 2002 02:20:36 -0400
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24831
	for <sip@ietf.org>; Mon, 30 Sep 2002 02:18:29 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.14])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g8U6CKYH002103;
	Mon, 30 Sep 2002 02:12:20 -0400 (EDT)
Message-ID: <3D97EB42.6060702@dynamicsoft.com>
Date: Mon, 30 Sep 2002 02:12:18 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sachin Shenoy <sachins@netlab.hcltech.com>
CC: sip@ietf.org
Subject: Re: [Sip] BranchID in CANCEL & INVITE
References: <4.3.2.7.0.20020919150512.00e96920@blaze>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Interesting.

The normative strengths in the specification are correct, but the 
recommended algorithm for performing the branch ID computation for loop 
detection will not work for stateless proxies, as you have identified. 
The algorithm in 16.11 for branch ID computation is stateless proxies is 
correct, but by its definition rules out loop detection using the branch 
ID computation in 16.6.

However, the spec doesn't explicitly point this out, and it should. The 
spec also needs to clarify that the branch ID computation for stateless 
proxies needs to be invariant across retranmits AND CANCEL AND ACK-non-2xx.

I've logged this into bugzilla:
http://www.sipwg.org/sipwg/show_bug.cgi?id=659

Really, loop detection is not something I would recommend. It has caused 
countless problems over the years and thats why max-forwards processing 
is now the preferred approach. So, just turn off loop detection and you 
won't have a problem.

-Jonathan R.



Sachin Shenoy wrote:
> Hi,
> This is regarding branches in CANCEL & INVITE.
> 
> Section 9.1 of RFC says
> 
> "9.1 Client Behavior
> ...
> The CANCEL request MUST NOT contain any Require or Proxy-Require header 
> fields."
> 
> 
> Consider the following scenario
> UAC sends INVITE to P1.
> P1 forwards it statlessley to UAS.
> UAC sends CANCEL to P1 (to cancel the INVITE).
> P1 forwards CANCEL also to UAS.
> 
> Let INVITE request have Proxy-Require header.
> 
> While handling INVITE at proxy,
> P1 calculates the VIA's loop-detection part using the Proxy-Require header.
> (The unique part would be calculated using a combinatronic function.) So 
> the
> INVITE's VIA would reflect the contents of the proxy-require header.
> 
> While handling CANCEL at proxy,
> P1 calculates the VIA's loop-detection part without the Proxy-Require 
> header,
> As CANCEL would not have it.
> 
> At UAS:
> INVITE & CANCEL would have different top-most via branches.
> 
> But according to RFC they have to have the same branches for the UAS to
> match the CANCEL & INVITE properly.
> 
> "9.1 Client Behavior
> ...
> A CANCEL constructed by a client MUST have only a single Via header field
> value matching the top Via value in the request being cancelled.  Using 
> the same
> values for these header fields allows the CANCEL to be matched with the
> request it cancels (Section 9.2 indicates how such matching occurs)."
> 
> Is it that Stateless proxies are not supposed to do loop-detection?
> 
> I thought the idea of having loop-detection part in branch-id was to
> allow proxies to detect loop even while being stateless. If only stateful
> proxies were to do loop-detection, we wouldn't have required the hash
> to be kept in the message at all.
> 
> Thanks in advance
> Sachin
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 

-- 
Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
Chief Scientist                             First Floor
dynamicsoft                                 East Hanover, NJ 07936
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

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



From mailnull@www1.ietf.org  Mon Sep 30 13:48:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14570
	for <sip-archive@odin.ietf.org>; Mon, 30 Sep 2002 13:48:04 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id g8UHnYe11919
	for sip-archive@odin.ietf.org; Mon, 30 Sep 2002 13:49:34 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8UHmRv11877;
	Mon, 30 Sep 2002 13:48:27 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8UHkvv11785
	for <sip@optimus.ietf.org>; Mon, 30 Sep 2002 13:46:57 -0400
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.54])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14442
	for <sip@ietf.org>; Mon, 30 Sep 2002 13:44:56 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-4.cisco.com (8.12.2/8.12.2) with ESMTP id g8UHkFot006302;
	Mon, 30 Sep 2002 10:46:15 -0700 (PDT)
Received: from cisco.com (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.1.0.66-GA)
	with ESMTP id ABA12361;
	Mon, 30 Sep 2002 10:44:07 -0700 (PDT)
Date: Mon, 30 Sep 2002 10:47:34 -0700
Subject: Re: [Sip] Re: Question about caller preferences
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v546)
Cc: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>, sip@ietf.org,
        Keith Drage <drage@lucent.com>
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
From: Rohan Mahy <rohan@cisco.com>
In-Reply-To: <3D94B98B.6060907@dynamicsoft.com>
Message-Id: <B395901C-D49C-11D6-8705-0003938AF740@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.546)
Content-Transfer-Encoding: 7bit
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Jonathan,

So are you saying that:

	Reject-Contact: *;class="personal"

should assume a mobility attribute of "any"  (Reject any personal 
contact whether mobile or not), and:

	Accept-Contact: *;class="business"

should also assume a mobility attribute of any (accept any business 
contact regardless of other attributes)?
(if so, i think this is goodness).

What would the status be of unincluded attributes in a REGISTER?  Is 
the semantic "unknown", "none", or "any"?

	Contact: <sip:rmahy@dhcp2357.cisco.com>;class=business
	Contact: <sip:rohan@iptel.org>;class=personal

thanks,
-rohan

On Friday, September 27, 2002, at 01:03 PM, Jonathan Rosenberg wrote:

> inline.
>
> Miguel A. Garcia wrote:
>> Jonathan Rosenberg wrote:
>>> inline.
>>>
>>> Miguel A. Garcia wrote:
>>> > Hi:
>>> >
>>> > I had a discussion with some folks about the caller preferences
>>> > draft, and we have some questions that we weren't able to answer by
>>> > reading the document.
>>> >
>>> > We understand that by not publishing the support for a feature set,
>>> > the UA is not providing any information. Therefore, the feature set
>>> > may or may not be supported at the UA.
>>>
>>> Actually, RFC 2533 (which we are using) does say something concrete
>>> about what it means to say nothing about a feature tag. It means that
>>> you are supporting all values. This means you need to be careful 
>>> about
>>> the semantics of the headers - the existing Reject-Contact semantic 
>>> of
>>> "reject this contact if its feature set matches" is bad, because it 
>>> will
>>> cause a UA to be rejected even if it has said nothing about a 
>>> particular
>>> feature tag!s
>>>
>>>
>> This is a little bit weird. I consider that the feature tags are not 
>> closed,
>> they are or will be expanding, and new feature tags will appear in 
>> the future.
>
> Absolutely.
>
>> Imagine that my UA implements feature tags 1, 2 and 3. A new feature 
>> 4 is defined, and my proxy or the remote UA supports that feature, by 
>> not my UA. Then, are you saying that the proxy or the remote UA will 
>> think that my terminal supports feature 4 because my UA didn't say 
>> anything about that?
>
> No, I'm not saying that.
>
> From the syntax in the contact header that describes the capabilities 
> (the predicate), its clear what the UA is explicitly saying, and what 
> its omitting. So, a UA that sees the predicate in a 200 OK to an 
> INVITE, for example, will know what is supported and what is omitted, 
> and so does a proxy that sees one in a REGISTER.
>
> What I AM saying is that the matching operation used for routing 
> doesn't care. If a caller places into an INVITE an Accept-Contact 
> saying that feature tag 4 should have a value of foo, a proxy will 
> route this call to UA's that explicitly indicate that they support 
> this value, and to those that say nothing.
>
> This is reasonable; the complete lack of information about a feature 
> tag should not imply its not supported. Interoperability is better if 
> you assume that no information means that it may or may not be 
> supported, and then let the protocol itself deal with the situation 
> where its not (i.e., reject with 405, 415, etc). This is explicitly 
> called out in rfc2533:
>
>> 3.4.2 Recipient capabilities
>>    The following expression describes a receiving system that has:
>>    (a)  a screen capable of displaying 640*480 pixels and 16 million
>>         colours (24 bits per pixel), 800*600 pixels and 64 thousand
>>         colours (16 bits per pixel) or 1024*768 pixels and 256 colours
>>         (8 bits per pixel), or
>>    (b)  a printer capable of rendering 300dpi on A4 paper.
>>          (| (& (| (& (pix-x<=640)  (pix-y<=480) (color<=16777216) )
>>                   (& (pix-x<=800)  (pix-y<=600) (color<=65535) )
>>                   (& (pix-x<=1024) (pix-y<=768) (color<=256) ) )
>>                (ua-media=screen) )
>>             (& (dpi=300)
>>                (ua-media=stationery) (papersize=iso-A4) ) )
>>    Note that this expression says nothing about the colour or 
>> grey-scale
>>    capabilities of the printer.  In the scheme presented here, it is
>>    presumed to be unconstrained in this respect (or, more 
>> realistically,
>>    any such constraints are handled out-of-band by anyone sending to
>>    this recipient).
>
> -Jonathan R.
>
> -- 
> Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
> Chief Scientist                             First Floor
> dynamicsoft                                 East Hanover, NJ 07936
> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com
>
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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



