Subject: Re: [sipcore] draft-ietf-sipcore-rfc4244bis-11: ABNF backward compatibility
From: [email-masked] (Dale R. Worley)
To: Mary Barnes <[email-masked]>
Cc: [email-masked]
Date: Wed, 2 Oct 2013 15:20:46 -0400 (EDT)
List-Id: SIP Core Working Group <sipcore.ietf.org>

> From: Mary Barnes <[email-masked]>
> 
> On Tue, Oct 1, 2013 at 2:53 PM, Paul Kyzivat <[email-masked]> 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