[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] [Sipping] status of draft-ietf-sip-gruu-15
Dean Willis writes:
> So what do you think is broken now?
see my message a few days ago to the list. i have read only a few
percent of outbound text and at least this paragraph is broken:
If the UAC is sending a dialog-forming request, and wants all
subsequent requests in the dialog to arrive over the same flow, the
UAC adds an 'ob' parameter to its Contact header. Typically this is
desirable, but it is not necessary for example if the Contact is a
GRUU [I-D.ietf-sip-gruu]. The flow used for the request is typically
the same flow the UA registered over, but it could be a new flow, for
example the initial subcription dialog for the configuration
framework [I-D.ietf-sipping-config-framework] needs to exist before
registration.
also, i'm questioning why outbound i-d does not provide a general
solution to "usage of the same flow for in-dialog requests" problem:
outbound behavior is also needed in case of regular presence server.
that is why i don't quite understand is why is this "usage of the same
flow for in-dialog requests" feature tied to outbound proxy. why is it
not useful From sip-bounces at ietf.org Thu Oct 2 09:04:18 2008
Return-Path: <sip-bounces at ietf.org>
X-Original-To: sip-web-archive at optimus.ietf.org
Delivered-To: ietfarch-sip-web-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 80E9F28C1A5;
Thu, 2 Oct 2008 09:04:18 -0700 (PDT)
X-Original-To: sip at core3.amsl.com
Delivered-To: sip at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 3BCD428C1A5
for <sip at core3.amsl.com>; Thu, 2 Oct 2008 09:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id m2mFavn-yiYu for <sip at core3.amsl.com>;
Thu, 2 Oct 2008 09:04:16 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
by core3.amsl.com (Postfix) with ESMTP id 6A13E28C25E
for <sip at ietf.org>; Thu, 2 Oct 2008 09:04:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
by tutpro.com (Postfix) with ESMTP id 0A7EA1EC306;
Thu, 2 Oct 2008 19:03:49 +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 lX0EOy5-vp1l; Thu, 2 Oct 2008 19:03:47 +0300 (EEST)
Received: from taimen (h128142.gprs.dnafinland.fi [87.93.128.142])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by tutpro.com (Postfix) with ESMTPSA;
Thu, 2 Oct 2008 19:03:47 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
id 9125A1C8105; Thu, 2 Oct 2008 19:03:43 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18660.61663.416336.165388 at taimen.test.fi>
Date: Thu, 2 Oct 2008 19:03:43 +0300
To: Dean Willis <dean.willis at softarmor.com>
In-Reply-To: <CDF0F938-3B8C-442C-87E4-D9B319F939DB at softarmor.com>
References: <EE9B10212E22466DAE8D10EECAF11291 at rildelhi.com>
<5D1A7985295922448D5550C94DE291800236151C at DEEXC1U01.de.lucent.com>
<18659.54337.452872.203497 at taimen.test.fi>
<CDF0F938-3B8C-442C-87E4-D9B319F939DB at softarmor.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh at tutpro.com (Juha Heinanen)
Cc: SIP IETF <sip at ietf.org>
Subject: Re: [Sip] [Sipping] status of draft-ietf-sip-gruu-15
X-BeenThere: sip at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:sip at ietf.org>
List-Help: <mailto:sip-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
Dean Willis writes:
> So what do you think is broken now?
see my message a few days ago to the list. i have read only a few
percent of outbound text and at least this paragraph is broken:
If the UAC is sending a dialog-forming request, and wants all
subsequent requests in the dialog to arrive over the same flow, the
UAC adds an 'ob' parameter to its Contact header. Typically this is
desirable, but it is not necessary for example if the Contact is a
GRUU [I-D.ietf-sip-gruu]. The flow used for the request is typically
the same flow the UA registered over, but it could be a new flow, for
example the initial subcription dialog for the configuration
framework [I-D.ietf-sipping-config-framework] needs to exist before
registration.
also, i'm questioning why outbound i-d does not provide a general
solution to "usage of the same flow for in-dialog requests" problem:
outbound behavior is also needed in case of regular presence server.
that is why i don't quite understand is why is this "usage of the same
flow for in-dialog requests" feature tied to outbound proxy. why is it
notto have a generic capability for UAC to tell to the next hop
(a proxy or UAS) in its dialog initiating request that "please use this
flow for subsequent requests of this dialog"?
-- juha
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
useful to have a generic capability for UAC to tell to the next hop
(a proxy or UAS) in its dialog initiating request that "please use this
flow for subsequent requests of this dialog"?
-- juha
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip