[sipcore] draft-barnes-sipcore-rfc4244bis

"Dale Worley" <dworley@nortel.com> Wed, 01 July 2009 19:21 UTC

Return-Path: <dworley@nortel.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 A70D13A6B24 for <sipcore@core3.amsl.com>; Wed, 1 Jul 2009 12:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.717
X-Spam-Level:
X-Spam-Status: No, score=-6.717 tagged_above=-999 required=5 tests=[AWL=-0.118, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 sPGS0u3agH+E for <sipcore@core3.amsl.com>; Wed, 1 Jul 2009 12:21:14 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id BA1223A67E4 for <sipcore@ietf.org>; Wed, 1 Jul 2009 12:21:13 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id n61JJTq01180 for <sipcore@ietf.org>; Wed, 1 Jul 2009 19:19:29 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 1 Jul 2009 15:21:00 -0400
From: "Dale Worley" <dworley@nortel.com>
To: SIPCORE <sipcore@ietf.org>
Content-Type: text/plain
Organization: Nortel Networks
Date: Wed, 01 Jul 2009 15:20:59 -0400
Message-Id: <1246476059.3751.63.camel@victoria-pingtel-com.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8)
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Jul 2009 19:21:00.0086 (UTC) FILETIME=[11119560:01C9FA81]
Subject: [sipcore] draft-barnes-sipcore-rfc4244bis
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: Wed, 01 Jul 2009 19:21:14 -0000

I am eager to see draft-barnes-sipcore-rfc4244bis progress, as it
appears to be a mechanism that can solve a great number of problems
(some of which are yet to appear fully).  Because History-Info can
record multiple retargeting events, it can handle situations where there
are multiple interacting services.  I see that as essential to support
the complex scenarios that "next generation" networks will need to
support.

I do see some problems in the exposition, and I will propose
improvements to the wording.

Is a -02 version in the works?

Dale