IETF Logo Mail Archive

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

"Dale Worley" <dworley@nortel.com> Fri, 10 July 2009 20:07 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 D015028C2E7 for <sipcore@core3.amsl.com>; Fri, 10 Jul 2009 13:07:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.679
X-Spam-Level:
X-Spam-Status: No, score=-7.679 tagged_above=-999 required=5 tests=[AWL=0.920, BAYES_00=-2.599, GB_I_LETTER=-2, 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 vWRzhZqCOHVF for <sipcore@core3.amsl.com>; Fri, 10 Jul 2009 13:07:16 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id DED1028C2AF for <sipcore@ietf.org>; Fri, 10 Jul 2009 13:07:15 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n6AK7fl10238; Fri, 10 Jul 2009 20:07:41 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:07:11 -0400
From: Dale Worley <dworley@nortel.com>
To: Francois Audet <audet@nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1EEDE3C8@zrc2hxm0.corp.nortel.com>
References: <6CA0129806DD4shin@softfront.co.jp> <1ECE0EB50388174790F9694F77522CCF1EEDE21D@zrc2hxm0.corp.nortel.com> <1ECE0EB50388174790F9694F77522CCF1EEDE3C8@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain
Organization: Nortel Networks
Date: Fri, 10 Jul 2009 16:07:10 -0400
Message-Id: <1247256430.3757.48.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:07:11.0210 (UTC) FILETIME=[02814CA0:01CA019A]
Cc: sipcore@ietf.org, OKUMURA Shinji <shin@softfront.co.jp>
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:07:16 -0000

On Fri, 2009-07-10 at 12:19 -0500, Francois Audet wrote:
> I guess we could have done something similar here, but as you
> can see, it it very nasty logic. Furthermore, since H-I very
> often includes header parameters, the value of allowing 
> addr-spec ends up being very low (i.e., you only same a couple
> of letters "<" and ">" in only simple circumstances.

Actually, you could save them any time the URI does not contain ',',
';', or '?'.

> Therefore, using always the "<" ">" makes it much cleaner and
> simpler, and easier to parse.

Although the value of this is relatively low, as we can already parse
the complicated case (in To, From, and Contact headers).

Dale

v2.23.0 | Report a Bug | By Email