Re: [sipcore] 4244bis-05: Semantics of History-Info

"Worley, Dale R (Dale)" <dworley@avaya.com> Fri, 17 June 2011 21:12 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28DA921F8466 for <sipcore@ietfa.amsl.com>; Fri, 17 Jun 2011 14:12:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.398
X-Spam-Level:
X-Spam-Status: No, score=-103.398 tagged_above=-999 required=5 tests=[AWL=0.201, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3LRTQf4Sd4nR for <sipcore@ietfa.amsl.com>; Fri, 17 Jun 2011 14:12:10 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 9B29121F8462 for <sipcore@ietf.org>; Fri, 17 Jun 2011 14:12:10 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EABzC+02HCzI1/2dsb2JhbABSplR3rUACmyKGJwSWWosd
X-IronPort-AV: E=Sophos;i="4.65,383,1304308800"; d="scan'208";a="251966299"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 17 Jun 2011 17:12:07 -0400
X-IronPort-AV: E=Sophos;i="4.65,383,1304308800"; d="scan'208";a="667637179"
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; 17 Jun 2011 17:12:06 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.192]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Fri, 17 Jun 2011 17:12:06 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, Hadriel Kaplan <HKaplan@acmepacket.com>, Shida Schubert <shida@ntt-at.com>
Date: Fri, 17 Jun 2011 17:09:34 -0400
Thread-Topic: [sipcore] 4244bis-05: Semantics of History-Info
Thread-Index: AQHMLTM2z4uZAgdj40ilXcDNMv+BZg==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222907EA05@DC-US1MBEX4.global.avaya.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 WG" <sipcore@ietf.org>
Subject: Re: [sipcore] 4244bis-05: Semantics of History-Info
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 17 Jun 2011 21:12:12 -0000

The -05 draft is considerably better written than the earlier drafts, but it still
lacks what I think is a critical explanation:  A description of what a given History-Info
header means.  The draft gives a series of procedures, but there's no way to check
whether they are correct or not, because there's no way to say whether their results
are correct.  It's like trying to check the correctness of an algorithm when there's no
specification of the desired output.

I'll write a draft of such a thing this weekend.

Dale