[Sipping] draft-vanelburg-sipping-served-user-02.txt

jh@tutpro.com (Juha Heinanen) Tue, 25 September 2007 13:57 UTC

Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IaAuL-0004Vn-GD; Tue, 25 Sep 2007 09:57:01 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43) id 1IaAuJ-0004Vi-MZ for sipping-confirm+ok@megatron.ietf.org; Tue, 25 Sep 2007 09:56:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IaAuJ-0004Va-D5 for sipping@ietf.org; Tue, 25 Sep 2007 09:56:59 -0400
Received: from lohi.tutpro.com ([192.98.100.2] helo=tutpro.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IaAuD-00062O-RG for sipping@ietf.org; Tue, 25 Sep 2007 09:56:59 -0400
Received: from localhost (localhost [127.0.0.1]) by tutpro.com (Postfix) with ESMTP id 8EB751EC63A; Tue, 25 Sep 2007 16:56:42 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1]) by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p0exv1zd+hww; Tue, 25 Sep 2007 16:56:35 +0300 (EEST)
Received: from taimen (isozyme245.gprs.dnafinland.fi [62.78.107.245]) by tutpro.com (Postfix) with ESMTP; Tue, 25 Sep 2007 16:56:35 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000) id A69DCAC06A; Tue, 25 Sep 2007 16:56:30 +0300 (EEST)
Message-ID: <18169.5006.656893.962725@taimen.test.fi>
Date: Tue, 25 Sep 2007 16:56:30 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: Hans Erik van Elburg <hanserik.van.elburg@ericsson.com>
Subject: [Sipping] draft-vanelburg-sipping-served-user-02.txt
In-Reply-To: <2C685FA24AE8004CA8F0DCCC7AF6AD081AF718@esealmw109.eemea.ericsson.se>
References: <2C685FA24AE8004CA8F0DCCC7AF6AD081AF718@esealmw109.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 21.4.1
From: jh@tutpro.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: 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>
Errors-To: sipping-bounces@ietf.org

hans,

when reading further i got into normative section 

5.  P-Served-User header field Definition 

and found it to be full of all kinds of 3gpp terms that i don't have any
glue what they mean.  if this is supposed to become an ietf sipping
working group specification, could you please rewrite the section using
only ietf sip terms.  after done, i'll try to figure out, what the draft
tries to say.

why i started to read this in the first place was that i may have an
application for this kind of header in regular sip environment where one
proxy finds out the user to whom the request uri belongs to and then
passes this information to another proxy so that this other proxy does
not need to repeat a possibly slow process of finding out the user of
the request uri.

so what you say in section 6 about applicability of p-s-u header does
not hold.

-- juha


_______________________________________________
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