IETF Logo Mail Archive

[Sipping] draft-elwell-sipping-service-retargeting-00.txt, RFC 387, and netann draft

Dean Willis <dean.willis@softarmor.com> Fri, 14 October 2005 21:51 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQXSD-0003QU-L5; Fri, 14 Oct 2005 17:51:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQXSC-0003QO-I2 for sipping@megatron.ietf.org; Fri, 14 Oct 2005 17:51:04 -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 RAA28821 for <sipping@ietf.org>; Fri, 14 Oct 2005 17:51:00 -0400 (EDT)
Received: from nylon.softarmor.com ([66.135.38.164]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQXd0-00082n-3i for sipping@ietf.org; Fri, 14 Oct 2005 18:02:14 -0400
Received: from [64.101.149.214] ([64.101.149.214]) (authenticated bits=0) by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id j9ELu1bA027961 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for <sipping@ietf.org>; Fri, 14 Oct 2005 16:56:02 -0500
Mime-Version: 1.0 (Apple Message framework v734)
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF04BEE0BF@zrc2hxm0.corp.nortel.com>
References: <1ECE0EB50388174790F9694F77522CCF04BEE0BF@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <64C25FE8-8150-4680-B440-3D2B48F5D257@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Date: Fri, 14 Oct 2005 16:51:00 -0500
To: sipping <sipping@ietf.org>
X-Mailer: Apple Mail (2.734)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit
Subject: [Sipping] draft-elwell-sipping-service-retargeting-00.txt, RFC 387, and netann draft
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

On Oct 13, 2005, at 9:22 PM, Francois Audet wrote:

> draft-elwell-sipping-service-retargeting provides EXPLICIT service
> invocation, in exactly the same way RFC 3087 does. The only difference
> with RFC 3087 is that the URI parameters in RFC 3087 are abstract
> "examples", while we would like the parameters to be well-known
> so we could do interoperable products.
>

So how does this relate to draft-burger-sipping-netann-11, which  
provides mechanisms for forward-encoding of standard imperatives into  
the request URI in accordance with RFC 3087?


--
Dean

_______________________________________________
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