Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: ABNF backward compatibility

worley@ariadne.com (Dale R. Worley) Wed, 02 October 2013 19:33 UTC

Return-Path: <worley@shell01.TheWorld.com>
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 AA4DB11E80D3 for <sipcore@ietfa.amsl.com>; Wed, 2 Oct 2013 12:33:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level:
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 pUAbBUHFpqyD for <sipcore@ietfa.amsl.com>; Wed, 2 Oct 2013 12:33:34 -0700 (PDT)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id B707C21F90E5 for <sipcore@ietf.org>; Wed, 2 Oct 2013 12:21:21 -0700 (PDT)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r92JKqpR027932; Wed, 2 Oct 2013 15:20:54 -0400
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r92JKp3e2240644; Wed, 2 Oct 2013 15:20:51 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r92JKkvX2240019; Wed, 2 Oct 2013 15:20:46 -0400 (EDT)
Date: Wed, 02 Oct 2013 15:20:46 -0400
Message-Id: <201310021920.r92JKkvX2240019@shell01.TheWorld.com>
From: worley@ariadne.com
Sender: worley@ariadne.com
To: Mary Barnes <mary.ietf.barnes@gmail.com>
In-reply-to: <CAHBDyN6JFwUWhzdq1iyH3NTdParjKpt7Ghs0TuJqQ0vfvYC7XQ@mail.gmail.com> (mary.ietf.barnes@gmail.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>
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: Wed, 02 Oct 2013 19:33:46 -0000

> From: Mary Barnes <mary.ietf.barnes@gmail.com>
> 
> On Tue, Oct 1, 2013 at 2:53 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> 
> > IIUC, the change was to permit addr-spec as well as name-addr.
> > And this issue is then that a 4244 implementation won't be able to parse
> > that. Right?
> >
> [MB] It's possible that some folks might be able to parse it, but we
> shouldn't count on that.[/MB]

It's unfortunate, because essentially everywhere else where a header
has this general syntax, either a name-addr or an addr-spec is
allowed.  But for upward compatibility, we're stuck with what 4244
allowed.

> > Please ensure that the use cases are still correct after the change.
> >
> [MB] I don't think there's an issue with the call flows. [/MB]

I searched both drafts, and all hi-entries use name-addrs.

Dale