IETF Logo Mail Archive

RE: [Sipping] Re: draft-elwell-sipping-service-retargeting-00.txt

"Francois Audet" <audet@nortel.com> Tue, 18 October 2005 18:46 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERwTJ-0002Od-5A; Tue, 18 Oct 2005 14:46:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERwTH-0002OS-C5 for sipping@megatron.ietf.org; Tue, 18 Oct 2005 14:45:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21592 for <sipping@ietf.org>; Tue, 18 Oct 2005 14:45:47 -0400 (EDT)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERwem-000710-OL for sipping@ietf.org; Tue, 18 Oct 2005 14:57:55 -0400
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j9IIjZp29656; Tue, 18 Oct 2005 14:45:35 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Re: draft-elwell-sipping-service-retargeting-00.txt
Date: Tue, 18 Oct 2005 13:45:29 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF04CE96DE@zrc2hxm0.corp.nortel.com>
Thread-Topic: [Sipping] Re: draft-elwell-sipping-service-retargeting-00.txt
Thread-Index: AcXUCgEPIF3xejCrRXGg7afmeSYQeQACQw+w
From: Francois Audet <audet@nortel.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: quoted-printable
Cc: "Elwell, John" <john.elwell@siemens.com>, sipping <sipping@ietf.org>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org


> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
> I think I see progress here. More below.

Mee too...

> I would say that in the VM case the proxy knows the target is a VM 
> system, and in the other case the proxy knows *nothing* about the 
> characteristics of the target. It might be an application. It 
> might be a 
> user device, or it might be an AOR that could route to either a user 
> device, a VM, some other application, or yet another unknown target.

OK, sure. I can buy that.

In my mind I was separating the service logic from the proxy which
I tought of being just a SIP router. That's why in my head, the two
cases where essentially the same.

But you could certainly implement it the way you are discribing, where
the proxy is aware of the concept of VM.

_______________________________________________
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

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