Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: ABNF backward compatibility
Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 04 October 2013 19:43 UTC
Return-Path: <pkyzivat@alum.mit.edu>
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 6617C21F9AA8 for <sipcore@ietfa.amsl.com>; Fri, 4 Oct 2013 12:43:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.004
X-Spam-Level:
X-Spam-Status: No, score=-0.004 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oWq0xiy+J61T for <sipcore@ietfa.amsl.com>; Fri, 4 Oct 2013 12:43:38 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 72E3221F994C for <sipcore@ietf.org>; Fri, 4 Oct 2013 12:43:38 -0700 (PDT)
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta03.westchester.pa.mail.comcast.net with comcast id Z0Ad1m00217dt5G537jdAy; Fri, 04 Oct 2013 19:43:37 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta13.westchester.pa.mail.comcast.net with comcast id Z7jd1m0093ZTu2S3Z7jdmP; Fri, 04 Oct 2013 19:43:37 +0000
Message-ID: <524F1A69.7000901@alum.mit.edu>
Date: Fri, 04 Oct 2013 15:43:37 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Dale R. Worley" <worley@ariadne.com>
References: <576A8B541C219D4E9CEB1DF8C19C7B881A061F01@MBX08.citservers.local> <CAHBDyN5zNiLjihMO-o96Avu7zDbm96ihfwgifvgbx28aQ1Vv7Q@mail.gmail.com> <576A8B541C219D4E9CEB1DF8C19C7B881A061FED@MBX08.citservers.local> <CAHBDyN4q=qrc8ti_MWXxwi5SPW8-zOHMz0z27krA+VtHNg3PFg@mail.gmail.com> <524B2832.9040201@alum.mit.edu> <CAHBDyN6JFwUWhzdq1iyH3NTdParjKpt7Ghs0TuJqQ0vfvYC7XQ@mail.gmail.com> <201310021920.r92JKkvX2240019@shell01.TheWorld.com> <201310041800.r94I0wWo2353227@shell01.TheWorld.com>
In-Reply-To: <201310041800.r94I0wWo2353227@shell01.TheWorld.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1380915817; bh=pP+ZQFb7HMQY5SJNo3zG9XuKPBNeOe1eWzS9Rz0y+Qc=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=C/FraEby2RyKGhO9xxhhfvD0LUmMVzoHVZ+1P5mzYsZkGQNLoG/k/+CU6KFMT4wwB lV40+ZUmk68ECxlVLb3z1Lo/C0iOJRE0FSe6vY9VrCQEciFJ1MrNivUoMdnSe396f/ dR51kcdPCyEwApHj56mOQ3FYBnX7/rX6Vcxuvf/MoxoU+O4xXUXXrJ+lGL+APrA5RF w6QMruNVa51LkLQ3zcYnZNKQ7ZnBhtU0ZBzG5KinO5N2i+KLYY2mFwsUyclqCTgmE1 ldjW0PxzlDeLj+6NDPmaFrs80+PMfa3i4Wu1Lf9jjvVCyZkU+4O+ESDByFd5ndxT9u Bkh2Q/mYHrAqA==
Cc: sipcore@ietf.org
Subject: Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: ABNF backward compatibility
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, 04 Oct 2013 19:43:44 -0000
On 10/4/13 2:00 PM, Dale R. Worley wrote: > However, we should carefully consider what we are doing here. All the > recent versions, from -06 to -11, use the "hi-targeted-to-uri = > addr-spec / name-addr" syntax. The WGLCs seem to have been on the -06 > and -09 versions. So we're on thin ice here, changing a significant > technical element of the draft. What do the chairs think, officially? I think this flew under the radar and most people didn't even realize it was changed. I personally was in favor of the change just for reasons of consistency, but hadn't recognized the backward compatibility issue. No functionality is lost here. The only difference the change made was to allow "<" and ">" to be omitted in some cases. The only risk I see is that somebody has *deployed* code that uses addr-spec. But since the new version hasn't become an RFC yet I don't have a lot of sympathy. So I think we should be fine with this fix. Thanks, Paul
- [sipcore] draft-ietf-sipcore-rfc4244bis-11: ABNF … Brett Tate
- Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: A… Mary Barnes
- Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: A… Francois Audet
- Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: A… Brett Tate
- Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: A… Mary Barnes
- Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: A… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: A… Mary Barnes
- Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: A… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: A… Shida Schubert
- Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: A… Dale R. Worley
- Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: A… Dale R. Worley
- Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: A… Paul Kyzivat
- Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: A… DRAGE, Keith (Keith)