IETF Logo Mail Archive

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

Mary Barnes <mary.ietf.barnes@gmail.com> Tue, 31 August 2010 19:41 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 436803A6A99 for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 12:41:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.488
X-Spam-Level:
X-Spam-Status: No, score=-102.488 tagged_above=-999 required=5 tests=[AWL=0.111, 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 p6HgK8OjXS+l for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 12:41:55 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 163C13A6A84 for <sipcore@ietf.org>; Tue, 31 Aug 2010 12:41:55 -0700 (PDT)
Received: by gwb20 with SMTP id 20so3276926gwb.31 for <sipcore@ietf.org>; Tue, 31 Aug 2010 12:42:25 -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=rPQ7ZZ702hfvUAA+ee/E/SxDxor9LqbHQiSsE0Gjys8=; b=AOfODgF4u4dqLFJ50VHl0suR2r3enKgXYn6wgNXVzDRaGH8XEO7MDZbq2rbQbWJFbg O9nSYF2S5uB6b37L5+iyRGB8ARb69VI05gs4In3k9h2DS9/OphTJmQc6q0pecwierlgL zCp4OvlHL3yLgDnVvyLwm2lyMFeWkVVRJMdt4=
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=Wp3cDd99Fj0N+s4peXa91irv21CEnfht9lDnYvzBU5ag9JnLDT7TxiqZHT9Y36QkMo M6zjb8jwgH6073eMI2v1uQOqXK+rdxqeT5Xxd8B/rovkvd56wGdCMkatvX0vDHeW5mYN gZnLXebXMyLtuXo2mC9XvXYXAyoBeEkXQECWs=
MIME-Version: 1.0
Received: by 10.151.92.4 with SMTP id u4mr2056657ybl.395.1283283744798; Tue, 31 Aug 2010 12:42:24 -0700 (PDT)
Received: by 10.231.169.14 with HTTP; Tue, 31 Aug 2010 12:42:24 -0700 (PDT)
In-Reply-To: <061.a0f2ecdd8a145270021e7d7f4271c829@tools.ietf.org>
References: <061.a0f2ecdd8a145270021e7d7f4271c829@tools.ietf.org>
Date: Tue, 31 Aug 2010 14:42:24 -0500
Message-ID: <AANLkTikQz6dN30bKZdj0F99Frrm5kwvcKPrgz-Uza2sr@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: sipcore issue tracker <trac@tools.ietf.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Cc: worley@alum.mit.edu, 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: Tue, 31 Aug 2010 19:41:56 -0000

I'm not sure what you mean about "explicitly authorizing" - we don't
have anything normative for B2BUAs defined, so I don't see how we can
do anything authoritative in this document. What are the known
problems you would like highlighted?

On Tue, Aug 31, 2010 at 12:51 PM, sipcore issue tracker
<trac@tools.ietf.org> wrote:
> #29: B2BUAs passing H-I through?
> ---------------------------------+------------------------------------------
>  Reporter:  worley@…             |       Owner:
>     Type:  enhancement          |      Status:  new
>  Priority:  major                |   Milestone:  milestone1
> Component:  rfc4244bis           |     Version:
>  Severity:  In WG Last Call      |    Keywords:
> ---------------------------------+------------------------------------------
>  In sections 4.1 and 4.2.1 there is text suggesting that B2BUAs that are
>  functioning as "quasi-proxies" may want to copy the incoming H-I into the
>  outgoing request (as if they were a proxy).  This seems like a good idea
>  to me, but it would be wise to have a short section explicitly authorizing
>  this behavior and perhaps listing any known problems with this.
>
> --
> Ticket URL: <http://trac.tools.ietf.org/wg/sipcore/trac/ticket/29>
> sipcore <http://tools.ietf.org/sipcore/>
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>

v2.23.0 | Report a Bug | By Email