Re: [Sip] Location-conveyance: ISSUE #3 - multiple locations

Dale.Worley@comcast.net Thu, 03 May 2007 02:37 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HjRBp-0008Iw-Vo; Wed, 02 May 2007 22:37:05 -0400
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1HjRBp-0008Ir-5E for sip-confirm+ok@megatron.ietf.org; Wed, 02 May 2007 22:37:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HjRBo-0008Ij-Rt for sip@ietf.org; Wed, 02 May 2007 22:37:04 -0400
Received: from sccrmhc11.comcast.net ([63.240.77.81]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjRBn-0008Q0-M5 for sip@ietf.org; Wed, 02 May 2007 22:37:04 -0400
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42]) by comcast.net (sccrmhc11) with ESMTP id <2007050302370301100fh87pe>; Thu, 3 May 2007 02:37:03 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1]) by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l432b2qi026121 for <sip@ietf.org>; Wed, 2 May 2007 22:37:03 -0400
Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l432b2G2026117; Wed, 2 May 2007 22:37:02 -0400
Date: Wed, 02 May 2007 22:37:02 -0400
Message-Id: <200705030237.l432b2G2026117@dragon.ariadne.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <0e7701c78c1c$6df76050$640fa8c0@cis.neustar.com> (br@brianrosen.net)
Subject: Re: [Sip] Location-conveyance: ISSUE #3 - multiple locations
References: <0e7701c78c1c$6df76050$640fa8c0@cis.neustar.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

   From: "Brian Rosen" <br@brianrosen.net>

   Yeah, I wanted to limit options.  I wanted two representations of the same
   location as a single header.  I'm not really stuck on that, but cutting down
   on options is good.

Permit me to exercise one of my peeves -- though it appears that
limiting the syntax of the header is beneficial, it is in fact
harmful.  You want as much uniformity in header syntax as possible, so
that implementations can use generic parsers to do the low-level
conversion of the character stream to a data structure of
names/values/whatever.  You also want to allow generic "un-parsing" to
convert the data structure to the character stream.  But if you make
ideosyncratic declarations that a particular header does things
*slightly differently* than all similar headers, implementations are
reduced to using custom code to generate every header.

Dale


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip