IETF Logo Mail Archive

Re: [sipcore] #27: Functionality of "Supported: histinfo" is not clear

Mary Barnes <mary.ietf.barnes@gmail.com> Fri, 03 September 2010 14:48 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 5DE193A68D8 for <sipcore@core3.amsl.com>; Fri, 3 Sep 2010 07:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.482
X-Spam-Level:
X-Spam-Status: No, score=-102.482 tagged_above=-999 required=5 tests=[AWL=0.117, 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 UuOkxxGTt+0Q for <sipcore@core3.amsl.com>; Fri, 3 Sep 2010 07:48:26 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id BC9D33A68D3 for <sipcore@ietf.org>; Fri, 3 Sep 2010 07:48:26 -0700 (PDT)
Received: by gyc15 with SMTP id 15so872327gyc.31 for <sipcore@ietf.org>; Fri, 03 Sep 2010 07:48:56 -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=6c/4B921fRKVc9IGSKhe/SyRiBJVK9lOUtE4zUJlZZA=; b=MXIYFvgNKN69ZaZTXXZBa0dETNDJaTr8mh9xUkOpYZk1hzBb5GCKXqH+2aopjTGPmP GTrol+9/Dax+5oPoYK5hiUbzKu0vLYETc1/97epbCI5/2ocPjIPoB+wQKoRFZ27miglW BrfXD0G1fYPHkHWM2ORJgtWVIw/6xpBD5x5FA=
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=dkQxmb4M2ix/ulB4iIMpzCm5tTh+I24Rj7xC2unfpxojq5J38NuNEcY4EBtLcacdXd sNeXfzK+On/8yaOUKLF5SsMH3H65IKD+ntrrIesZ6jm1HQWsjveommRmhpbnKcR8SycZ GCHr8udz9uK91dVc3jfei2EAM47D2tBOcc1/w=
MIME-Version: 1.0
Received: by 10.151.150.4 with SMTP id c4mr21953ybo.25.1283525334109; Fri, 03 Sep 2010 07:48:54 -0700 (PDT)
Received: by 10.231.169.14 with HTTP; Fri, 3 Sep 2010 07:48:54 -0700 (PDT)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B21FFC79C16@DC-US1MBEX4.global.avaya.com>
References: <061.1ad850c04d811993da48994773153dd6@tools.ietf.org> <A444A0F8084434499206E78C106220CA01C48DAF5A@MCHP058A.global-ad.net> <CD5674C3CD99574EBA7432465FC13C1B21FFC79C15@DC-US1MBEX4.global.avaya.com> <A444A0F8084434499206E78C106220CA01C48DBA80@MCHP058A.global-ad.net> <CD5674C3CD99574EBA7432465FC13C1B21FFC79C16@DC-US1MBEX4.global.avaya.com>
Date: Fri, 03 Sep 2010 09:48:54 -0500
Message-ID: <AANLkTi=qFsTV6nU8PsBsB9r5RV71zZMF=g_nmqszt5DU@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] #27: Functionality of "Supported: histinfo" is not clear
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, 03 Sep 2010 14:48:30 -0000

Yes, you would need it in the case that a proxy might only be
capturing HI if the supported tag is there. But, that's not mandatory
behavior.   However, it does no harm to keep the tag to ensure
backwards compatibility - it's just that a 4244bis proxy would just
ignore it.

Mary.

On Fri, Sep 3, 2010 at 9:43 AM, Worley, Dale R (Dale) <dworley@avaya.com> wrote:
> ________________________________________
> From: Elwell, John [john.elwell@siemens-enterprise.com]
>
> This raises the question whether the option tag is needed at all. What harm would be done by removing the option tag?
> ________________________________________
>
> To some extent we're constrained by compatibility with RFC 4244.  Even if we wanted to eliminate histinfo, UACs would still need to include "Supported: histinfo" to cause 4244-but-not-4244bis proxies to do H-I processing.
>
> Dale
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>

v2.23.0 | Report a Bug | By Email