IETF Logo Mail Archive

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

"Worley, Dale R (Dale)" <dworley@avaya.com> Fri, 03 September 2010 14:43 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 C11213A68D8 for <sipcore@core3.amsl.com>; Fri, 3 Sep 2010 07:43:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.45
X-Spam-Level:
X-Spam-Status: No, score=-102.45 tagged_above=-999 required=5 tests=[AWL=0.149, 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 wZRxf6kdoskM for <sipcore@core3.amsl.com>; Fri, 3 Sep 2010 07:43:54 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id A46EE3A68B9 for <sipcore@ietf.org>; Fri, 3 Sep 2010 07:43:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,313,1280721600"; d="scan'208";a="205858553"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 03 Sep 2010 10:44:22 -0400
X-IronPort-AV: E=Sophos;i="4.56,313,1280721600"; d="scan'208";a="506425772"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 03 Sep 2010 10:44:20 -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, 3 Sep 2010 10:44:20 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Date: Fri, 03 Sep 2010 10:43:06 -0400
Thread-Topic: [sipcore] #27: Functionality of "Supported: histinfo" is not clear
Thread-Index: ActJND0SAMI916bZQ9yMkfjcIpLE6gAeVROwAFWey/UAC9hV4AAQuRER
Message-ID: <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>
In-Reply-To: <A444A0F8084434499206E78C106220CA01C48DBA80@MCHP058A.global-ad.net>
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] #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:43:54 -0000

________________________________________
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

v2.23.0 | Report a Bug | By Email