Re: [sipcore] #2: Editorial: section 2 is really confusing

"Worley, Dale R (Dale)" <dworley@avaya.com> Thu, 02 September 2010 21:39 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 015DD3A69E1 for <sipcore@core3.amsl.com>; Thu, 2 Sep 2010 14:39:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.446
X-Spam-Level:
X-Spam-Status: No, score=-102.446 tagged_above=-999 required=5 tests=[AWL=0.153, 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 jhxP2xFNLUHM for <sipcore@core3.amsl.com>; Thu, 2 Sep 2010 14:39:24 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 2A7473A69B8 for <sipcore@ietf.org>; Thu, 2 Sep 2010 14:39:24 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,310,1280721600"; d="scan'208";a="32907264"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 02 Sep 2010 17:39:54 -0400
X-IronPort-AV: E=Sophos;i="4.56,310,1280721600"; d="scan'208";a="506037799"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 02 Sep 2010 17:39:18 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.129]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Thu, 2 Sep 2010 17:39:18 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>, Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Thu, 02 Sep 2010 17:37:33 -0400
Thread-Topic: [sipcore] #2: Editorial: section 2 is really confusing
Thread-Index: ActK4Rffrp/hLbpBS9i0FN/7ryhcQQABfXGj
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FFC79C14@DC-US1MBEX4.global.avaya.com>
References: <294E3E61-2DFE-4427-92F0-EDBDBE2888CC@acmepacket.com> <CD5674C3CD99574EBA7432465FC13C1B21FFC79BFD@DC-US1MBEX4.global.avaya.com> <EDC0A1AE77C57744B664A310A0B23AE214D298AE@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <3A1175B1-93F3-440E-9965-5073BB426D8B@acmepacket.com> <AANLkTikcQQbjxzUD4qcXG=FDbv3MbhFJya=0bZp5oLkk@mail.gmail.com>, <2D6DDDBC-4064-4F74-A614-1DEF111C2CB8@acmepacket.com>
In-Reply-To: <2D6DDDBC-4064-4F74-A614-1DEF111C2CB8@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: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Subject: Re: [sipcore] #2: Editorial: section 2 is really confusing
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: Thu, 02 Sep 2010 21:39:27 -0000

________________________________________
From: Hadriel Kaplan [HKaplan@acmepacket.com]

And I was probably one of the people arguing against too many tags. :)
Unfortunately, the use-case I personally really care about is recording diversions.  Both in order to interwork to/from the Diversion header, and for ISUP interworking, and because I still hear complaints from operators that SIP doesn't have the redirection information so they have to still carry ISUP IAMs.  So I need an identifier of which of these H-I entries are *actual* diverts and not just SIP being SIP.  I know it's just one use-case among many, but I'm probably not alone in needing it.(?)  If I am I'll shut up about it.
________________________________________

Can you point us to the data model of the info that they want/need?  And do you know how parallel the models of Diversion and ISUP are?

(BTW, would it be possible to carry this information in Reason headers in the hi-entry URIs?)

Dale