IETF Logo Mail Archive

Re: [Sip] SIP instance identifiers

Cullen Jennings <fluffy@cisco.com> Fri, 20 February 2004 05:24 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17967 for <sip-archive@odin.ietf.org>; Fri, 20 Feb 2004 00:24:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au39F-0002mY-Gh for sip-archive@odin.ietf.org; Fri, 20 Feb 2004 00:24:30 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1K5OPdY010442 for sip-archive@odin.ietf.org; Fri, 20 Feb 2004 00:24:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au38r-0002TO-NE; Fri, 20 Feb 2004 00:24:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Au38X-0002ST-Ga for sip@optimus.ietf.org; Fri, 20 Feb 2004 00:23:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17809 for <sip@ietf.org>; Fri, 20 Feb 2004 00:23:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Au38U-0002df-00 for sip@ietf.org; Fri, 20 Feb 2004 00:23:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Au37X-0002XQ-00 for sip@ietf.org; Fri, 20 Feb 2004 00:22:40 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1Au36Z-0002Qe-00 for sip@ietf.org; Fri, 20 Feb 2004 00:21:39 -0500
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i1K5L7uA021868; Thu, 19 Feb 2004 21:21:07 -0800 (PST)
Received: from [10.0.1.3] (sjc-vpn1-148.cisco.com [10.21.96.148]) by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AMN04130; Thu, 19 Feb 2004 21:21:06 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Thu, 19 Feb 2004 18:00:57 -0800
Subject: Re: [Sip] SIP instance identifiers
From: Cullen Jennings <fluffy@cisco.com>
To: Paul H Kyzivat <pkyzivat@cisco.com>, Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: sip@ietf.org
Message-ID: <BC5AAA59.32260%fluffy@cisco.com>
In-Reply-To: <40329592.1080001@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,DATE_IN_PAST_03_06 autolearn=no version=2.60
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 2/17/04 2:28 PM, "Paul Kyzivat" <pkyzivat@cisco.com> wrote:

> I can see 
> validity in Brian's desire to have it in a header of its own,
> potentially in any message. I don't see those usages as conflicting.

Just to be clear, I don't want it to have multiple possible place it could
be in a SIP message and I have to go traipsing around the message trying
here then there unless it is a FOO message where you look over here. A
header would work or caller pref but I don't see an argument for doing both.
I want it just one place.

The case with PUBLISH not having contact header had concerned me (actually I
think this was a mistake) but seems what happens in PIDF bodies could be
different.


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

v2.46.0 | Report a Bug | By Email | System Status