Re: [sipcore] #29: B2BUAs passing H-I through?

"Worley, Dale R (Dale)" <dworley@avaya.com> Fri, 10 September 2010 19:53 UTC

Return-Path: <dworley@avaya.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 8B9823A6836 for <sipcore@core3.amsl.com>; Fri, 10 Sep 2010 12:53:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.467
X-Spam-Level:
X-Spam-Status: No, score=-102.467 tagged_above=-999 required=5 tests=[AWL=0.132, 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 yF5Tp6Ru3OzU for <sipcore@core3.amsl.com>; Fri, 10 Sep 2010 12:53:40 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 77D0A3A677E for <sipcore@ietf.org>; Fri, 10 Sep 2010 12:53:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,347,1280721600"; d="scan'208";a="237303076"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 10 Sep 2010 15:54:07 -0400
X-IronPort-AV: E=Sophos;i="4.56,347,1280721600"; d="scan'208";a="510054240"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 10 Sep 2010 15:54:07 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.129]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Fri, 10 Sep 2010 15:54:06 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>, Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Fri, 10 Sep 2010 15:50:36 -0400
Thread-Topic: [sipcore] #29: B2BUAs passing H-I through?
Thread-Index: ActJaao6mrNOe26PSH25OgbHoWgj2AHt8V2Y
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FFC79C54@DC-US1MBEX4.global.avaya.com>
References: <061.a0f2ecdd8a145270021e7d7f4271c829@tools.ietf.org> <AANLkTikQz6dN30bKZdj0F99Frrm5kwvcKPrgz-Uza2sr@mail.gmail.com>, <451EA107-5853-486E-804B-1EE11FECCAF2@acmepacket.com>
In-Reply-To: <451EA107-5853-486E-804B-1EE11FECCAF2@acmepacket.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] #29: B2BUAs passing H-I through?
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: Fri, 10 Sep 2010 19:53:42 -0000

________________________________________
From: sipcore-bounces@ietf.org [sipcore-bounces@ietf.org] On Behalf Of Hadriel Kaplan [HKaplan@acmepacket.com]

Since a B2BUA is a UAC and UAS, one might think it should follow the rules for a UAC and UAS in this draft, restarting/clearing the H-I on each side. 

What you really want is a sentence/para saying a B2BUA would follow the rules for a Proxy with regards to H-I for requests which it forwards, unless local policy says otherwise; while for requests it generates itself it should act as a UAC.  For example if it generates a dialog-creating INVITE due to receiving a REFER, it would act as a UAC per the 4424bis draft, but if it is merely forwarding a dialog-creating INVITE (i.e. generating one due to receiving one) then it should follow the rules for a Proxy and copy the received H-I and add an entry, etc.  Right?
_______________________________________________

Yes.  Or perhaps even more flexibly -- E.g., a B2BUA that is creating an INVITE due to receiving a REFER, but that continues a dialog "from the other side", might send the new INVITE with the H-I received well in the past, when the other side dialog was created.  But the main point is as you stated, as the text stands now, a B2BUA sending an INVITE is acting as a UAC and must reinitialize the H-I.

Dale