Re: [sipcore] #34: Semantics of History-Info values need to be documented explicitly
"Worley, Dale R (Dale)" <dworley@avaya.com> Fri, 03 September 2010 18:16 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 24F583A6969 for <sipcore@core3.amsl.com>; Fri, 3 Sep 2010 11:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.457
X-Spam-Level:
X-Spam-Status: No, score=-102.457 tagged_above=-999 required=5 tests=[AWL=0.142, 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 1ihCTWTNhUeq for <sipcore@core3.amsl.com>; Fri, 3 Sep 2010 11:16:29 -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 CB2463A67E4 for <sipcore@ietf.org>; Fri, 3 Sep 2010 11:16:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,314,1280721600"; d="scan'208";a="236197256"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 03 Sep 2010 14:16:56 -0400
X-IronPort-AV: E=Sophos;i="4.56,314,1280721600"; d="scan'208";a="512095840"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 03 Sep 2010 14:16:55 -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 14:16:55 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Fri, 03 Sep 2010 14:16:12 -0400
Thread-Topic: [sipcore] #34: Semantics of History-Info values need to be documented explicitly
Thread-Index: ActJRTiFisejEUR7QiyZpW4+DqIyTACTt4/8
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FFC79C1D@DC-US1MBEX4.global.avaya.com>
References: <061.0a5978795ae778ef21b5c72dd4fd4248@tools.ietf.org>, <AANLkTimd0g-meQVzEZX5a8KD2SiQsVh4Pc67HO-V6HnB@mail.gmail.com>
In-Reply-To: <AANLkTimd0g-meQVzEZX5a8KD2SiQsVh4Pc67HO-V6HnB@mail.gmail.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] #34: Semantics of History-Info values need to be documented explicitly
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 18:16:42 -0000
________________________________________ From: sipcore-bounces@ietf.org [sipcore-bounces@ietf.org] On Behalf Of Mary Barnes [mary.ietf.barnes@gmail.com] You'll have to send text on this one - it's not clear to me at all what you are talking about. _______________________________________________ Here's a start: The History-Info header field(s) of a request contain a sequence of hi-entrys. Each hi-entry contains an 'index' parameter. The values of the 'index' parameters organize the hi-entrys into a tree, with each hi-entry being a child of the hi-entry whose index is the same except for the final ("." 1*DIGIT) being removed. The hi-entrys whose 'index' value is just 1*DIGIT are the children of an implicit root hi-entry. The child hi-entrys of an hi-entry have as their final 1*DIGIT distinct consecutive integers starting with 1. [Question: Are the values required to be consecutive?] The hi-entrys appear in preorder, the lexicographic ordering of their 'index' values. [Question: Are the hi-entrys constrained to appear in this order?] The hi-entrys correspond to requests that are derived from one initial out-of-dialog request, that is requests that share their Call-Id and CSeq values, and have no to-tag. An hi-entry's parent hi-entry corresponds to its immediate predecessor request, that is, the one which contains all of its Vias except the topmost. An hi-entry with only one 1*DIGIT in its 'index' value corresponds to a request with one Via, that is, one sent by the UAC. The last hi-entry corresponds to the request containing this History-Info header field. [Question: Is this true? Or is the hi-entry that corresponds to the containing request marked in some other way?] An hi-entry's name-addr contains as its URI either the request-URI of the corresponding request, or "sip:anonymous@anonymous.invalid" (to indicate that the request-URI is being hidden). [Note that the actual anonymous value is not specified in 4244bis.] If an hi-entry contains a *** or *** parameter, then the request-URI of the corresponding request was derived by the proxy from the request-URI of its parent by the corresponding process. If an hi-entry contains a *** or *** parameter, then the request-URI of the corresponding request was obtained from a 3xx response to the request corresponding to the hi-entry whose 'index' value is the value of the parameter. The parameter was obtained from the corresponding header parameter of the Contact header field of the 3xx response, and indicates that the generator of the 3xx response indicated that the Contact URI was derived by the corresponding process. Dale
- [sipcore] #34: Semantics of History-Info values n… sipcore issue tracker
- Re: [sipcore] #34: Semantics of History-Info valu… Mary Barnes
- Re: [sipcore] #34: Semantics of History-Info valu… Worley, Dale R (Dale)
- Re: [sipcore] #34: Semantics of History-Info valu… Mary Barnes