IETF Logo Mail Archive

Re: [sipcore] #28: UACs should add H-I if they implement it

Mary Barnes <mary.ietf.barnes@gmail.com> Wed, 13 October 2010 19:20 UTC

Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2625D3A6983 for <sipcore@core3.amsl.com>; Wed, 13 Oct 2010 12:20:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.5
X-Spam-Level:
X-Spam-Status: No, score=-102.5 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 n2o7OElSoRPw for <sipcore@core3.amsl.com>; Wed, 13 Oct 2010 12:20:29 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 1178A3A6916 for <sipcore@ietf.org>; Wed, 13 Oct 2010 12:20:28 -0700 (PDT)
Received: by gxk8 with SMTP id 8so169959gxk.31 for <sipcore@ietf.org>; Wed, 13 Oct 2010 12:21:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=CEjmRHKYujN4fMpd0FGv0kpDQSgYG/75wto4Ks4RrL0=; b=R7Ity9uVzrzvYuWVLgZEv1oGH9abQCV5FGMkRUk/gjEOKexK6Y/tr2pixGmJ/8zXOO /MypzZXH/w8PiF8TaAhPWCd8B3HXmlwPd5ylUbtq0p0cl8OtCJ6oPTRuL9/v6qBAF4I8 TeJEigs+a3HsbGJNoUSdrZDkXPSETOtD6Ck/s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=DPIVcEiWGnDy/gXKbr3wyHwNRmRAV/HkQhmq9/yrOVPrgp5QmEOeSR0lfXKQaAK8JH a1JsSzZhz9zKDX4Vbv7ImNnC+yMH2uQA38Vej0Ajo4g5Y8DTwTloMkhxo4QbIEynM8Mr CIMq64YZY4Ah+v9zONZ4iBQX8ySlee+FVzPXE=
MIME-Version: 1.0
Received: by 10.42.15.12 with SMTP id j12mr4413429ica.382.1286997705647; Wed, 13 Oct 2010 12:21:45 -0700 (PDT)
Received: by 10.236.108.172 with HTTP; Wed, 13 Oct 2010 12:21:45 -0700 (PDT)
In-Reply-To: <A444A0F8084434499206E78C106220CA01C48DAF11@MCHP058A.global-ad.net>
References: <061.57b8764c42d447c660e2242094ef9cb2@tools.ietf.org> <A444A0F8084434499206E78C106220CA01C48DAF11@MCHP058A.global-ad.net>
Date: Wed, 13 Oct 2010 14:21:45 -0500
Message-ID: <AANLkTimqruxJr4tXd93uvJdrCf12p5AAooPTNHeVbigc@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "worley@alum.mit.edu" <worley@alum.mit.edu>, "sipcore@ietf.org" <sipcore@ietf.org>, sipcore issue tracker <trac@tools.ietf.org>
Subject: Re: [sipcore] #28: UACs should add H-I if they implement it
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 19:20:30 -0000

Agreed. I've changed that text.

On Wed, Sep 1, 2010 at 2:28 AM, Elwell, John
<john.elwell@siemens-enterprise.com> wrote:
> This makes sense to me.
>
> John
>
>> -----Original Message-----
>> From: sipcore-bounces@ietf.org
>> [mailto:sipcore-bounces@ietf.org] On Behalf Of sipcore issue tracker
>> Sent: 31 August 2010 18:49
>> To: worley@alum.mit.edu
>> Cc: sipcore@ietf.org
>> Subject: [sipcore] #28: UACs should add H-I if they implement it
>>
>> #28: UACs should add H-I if they implement it
>> ---------------------------------+----------------------------
>> --------------
>>  Reporter:  worley@...             |       Owner:
>>      Type:  defect               |      Status:  new
>>  Priority:  major                |   Milestone:  milestone1
>> Component:  rfc4244bis           |     Version:
>>  Severity:  In WG Last Call      |    Keywords:
>> ---------------------------------+----------------------------
>> --------------
>>  In section 4.1 is:
>>
>>      Normally, UACs are not expected to include a
>> History-Info header in an
>>  initial request as it is more of a Proxy function; the main
>> reason it is
>>  allowed is for B2BUAs who are performing proxy-like functions such as
>>  routing.
>>
>>  This is not a good idea; a UAC that wants History-Info should add the
>>  initial hi-entry.  The reason is that the UAC does not know
>> that the next
>>  proxy that will modify the request-URI implements H-I; if
>> the UAC does not
>>  provide an hi-entry, the UAS won't see the original request-URI.
>>  Conversely, adding "History-Info: <[request-URI]>;index=1"
>> is not much
>>  more work than adding "Supported: histinfo", which we
>> already assume the
>>  UAC will do.
>>
>> --
>> Ticket URL: <http://trac.tools.ietf.org/wg/sipcore/trac/ticket/28>
>> sipcore <http://tools.ietf.org/sipcore/>
>>
>> _______________________________________________
>> sipcore mailing list
>> sipcore@ietf.org
>> https://www.ietf.org/mailman/listinfo/sipcore
>>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>

v2.23.0 | Report a Bug | By Email