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

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

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERyjo-0001l5-93; Tue, 18 Oct 2005 17:11:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERyjm-0001iv-5o for sipping@megatron.ietf.org; Tue, 18 Oct 2005 17:11:10 -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 RAA27689 for <sipping@ietf.org>; Tue, 18 Oct 2005 17:11:01 -0400 (EDT)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERyvK-0004E7-M2 for sipping@ietf.org; Tue, 18 Oct 2005 17:23:08 -0400
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j9ILAhN29351; Tue, 18 Oct 2005 17:10:44 -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 16:10:36 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF04CE99CC@zrc2hxm0.corp.nortel.com>
Thread-Topic: [Sipping] Re: draft-elwell-sipping-service-retargeting-00.txt
Thread-Index: AcXUImJ1Zl8xQkWtSRKv/nCCwJ4PrwABZo7Q
From: Francois Audet <audet@nortel.com>
To: Dean Willis <dean.willis@softarmor.com>, Paul Kyzivat <pkyzivat@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
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

> In which case, if we follow the principles of RFC 3087, it becomes  
> the responsibility of whoever fills in this URI to include whatever  
> parameters are needed by the target. I'm fairly happy with that  
> understanding, if that's what Francois is really saying, and if John  
> and the other folks agree.

That's what I was saying indeed. 

Let's wait for John to clarify what he meant...

> So if that's true, what we're talking about here is really something  
> like the netann draft, in that it is informationally defining some  
> reusable parameters for specific services that are invoked in a  
> manner consistent with RFC 3087. If that's what we want, I think  
> that's a manageable scope and something we know how to do.

Yes.

> Like netann and 3087, this doesn't even have to be (although 
> it could  
> be, if we have that sort of consensus) a working group document. It  
> could proceed as an individual informational. Of course, like 
> netann,  
> we'd still want to make sure it actually answers the questions and  
> doesn't confuse people excessively.

I think it's pretty obvious we failed on the "confusion" front...

Thanks.

_______________________________________________
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