Re: [sipcore] draft-barnes-sipcore-rfc4244bis - hi-targeted-to-uri

"Dale Worley" <dworley@nortel.com> Fri, 10 July 2009 20:04 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 7896228C29D for <sipcore@core3.amsl.com>; Fri, 10 Jul 2009 13:04:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.682
X-Spam-Level:
X-Spam-Status: No, score=-6.682 tagged_above=-999 required=5 tests=[AWL=-0.083, 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 ahmgxy8iDr9T for <sipcore@core3.amsl.com>; Fri, 10 Jul 2009 13:04:56 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 67E363A6961 for <sipcore@ietf.org>; Fri, 10 Jul 2009 13:04:56 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n6AK5Ll09482; Fri, 10 Jul 2009 20:05:21 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 10 Jul 2009 16:05:03 -0400
From: Dale Worley <dworley@nortel.com>
To: OKUMURA Shinji <shin@softfront.co.jp>
In-Reply-To: <6CA0129806DD4shin@softfront.co.jp>
References: <6CA0129806DD4shin@softfront.co.jp>
Content-Type: text/plain
Organization: Nortel Networks
Date: Fri, 10 Jul 2009 16:05:03 -0400
Message-Id: <1247256303.3757.45.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: 10 Jul 2009 20:05:03.0786 (UTC) FILETIME=[B68DF0A0:01CA0199]
Cc: sipcore@ietf.org
Subject: Re: [sipcore] draft-barnes-sipcore-rfc4244bis - hi-targeted-to-uri
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, 10 Jul 2009 20:04:57 -0000

On Fri, 2009-07-10 at 15:41 +0900, OKUMURA Shinji wrote:
> In the draft hi-targeted-to-uri is defined as follows
> 
> hi-targeted-to-uri = name-addr
> 
> If there is no special reason for the restriction, I think
> addr-spec should be added as follows
> 
> hi-targeted-to-uri = name-addr/addr-spec

That is an interesting point.  If we made that change, History-Info
would have the same overall syntax as Contact, From, To, etc., namely
that if the URI was not contained in <...>, the first ';' would start
the first header-parameter.

On the other hand, Route and Record route do not allow addr-spec, that
is, the <...> is mandatory.

In SIP 3.0, we should force all these headers to use the same syntax.

Dale