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

[Mary Barnes <[e-mail]>]

On Tue, Oct 1, 2013 at 2:53 PM, Paul Kyzivat <[e-mail]> 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]

>
> 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]

>
>         Thanks,
>         Paul
>
>
> On 10/1/13 2:38 PM, Mary Barnes wrote:
>
>> Yes, you are correct - I misread the diffs and we did make the change
>> based on Dale's comment, but we (authors) agree that it should be
>> consistent with RFC 4244.
>>
>> Mary.
>>
>>
>> On Tue, Oct 1, 2013 at 1:26 PM, Brett Tate <[e-mail]
>> <mailto:[e-mail]>> wrote:
>>
>>     Hi Mary,____
>>
>>     __ __
>>
>>
>>     It looks like Dale requested the change; however, I think that it
>>     will cause interoperability issues with rfc4244 devices if an
>>     rfc4244bis devices sends an addr-spec.  Thus I think that the change
>>     should be reverted (to be hi-targeted-to-uri= name-addr).____
>>
>>     __ __
>>
>>     http://www.ietf.org/mail-**archive/web/sipcore/current/**
>> msg04158.html<http://www.ietf.org/mail-archive/web/sipcore/current/msg04158.html>____
>>
>>     __ __
>>
>>     Thanks,____
>>
>>     Brett____
>>
>>     __ __
>>
>>     *From:*Mary Barnes [mailto:mary.ietf.barnes@**gmail.com<[e-mail]>
>>     <mailto:mary.ietf.barnes@**gmail.com <[e-mail]>>]
>>     *Sent:* Tuesday, October 01, 2013 1:41 PM
>>
>>
>>     *To:* Brett Tate
>>     *Cc:* draft-ietf-sipcore-rfc4244bis@**tools.ietf.org<[e-mail]>
>>     <mailto:draft-ietf-sipcore-**[e-mail]<[e-mail]>
>> >;
>>     [e-mail] <mailto:[e-mail]>
>>     *Subject:* Re: [sipcore] draft-ietf-sipcore-rfc4244bis-**11: ABNF
>>     backward compatibility____
>>
>>     __ __
>>
>>
>>     I don't think it was intentional.  I backtracked and for whatever
>>     reason that change appeared in the individual -00 and I could find
>>     no email threads as to why we would have made that change.   It
>>     appears Dale pointed out that issue a long time back, as well, but
>>     it seems we didn't make that fix. ____
>>
>>     __ __
>>
>>
>>     So, that is an error and we should fix that.  We have a couple other
>>     editorial/clarification points that Dale has pointed out that we
>>     will also include in a revision shortly.____
>>
>>     __ __
>>
>>     Thanks,____
>>
>>     Mary. ____
>>
>>     __ __
>>
>>
>>     On Tue, Oct 1, 2013 at 9:46 AM, Brett Tate <[e-mail]
>>     <mailto:[e-mail]>> wrote:____
>>
>>
>>     Hi,
>>
>>     The ABNF of draft-ietf-sipcore-rfc4244bis-**11's hi-targeted-to-uri
>> is
>>     not backwards compatible with RFC 4244.
>>
>>     Is this intentional?  And if so, should it be mentioned within
>>     section 16 and/or 16.1?
>>
>>     Thanks,
>>     Brett
>>
>>     -----
>>
>>     draft-ietf-sipcore-rfc4244bis-**11:
>>
>>        History-Info = "History-Info" HCOLON hi-entry *(COMMA hi-entry)
>>
>>        hi-entry = hi-targeted-to-uri *(SEMI hi-param)
>>
>>        hi-targeted-to-uri = addr-spec / name-addr
>>
>>
>>     RFC 4244:
>>
>>        History-Info = "History-Info" HCOLON hi-entry *(COMMA hi-entry)
>>
>>        hi-entry = hi-targeted-to-uri *( SEMI hi-param )
>>
>>        hi-targeted-to-uri= name-addr
>>
>>     This email is intended solely for the person or entity to which it
>>     is addressed and may contain confidential and/or privileged
>>     information. If you are not the intended recipient and have received
>>     this email in error, please notify BroadSoft, Inc. immediately by
>>     replying to this message, and destroy all copies of this message,
>>     along with any attachment, prior to reading, distributing or copying
>> it.
>>     ______________________________**_________________
>>     sipcore mailing list
>>     [e-mail] <mailto:[e-mail]>
>>     https://www.ietf.org/mailman/**listinfo/sipcore____<https://www.ietf.org/mailman/listinfo/sipcore____>
>>
>>     __ __
>>
>>
>>
>>
>>
>> ______________________________**_________________
>> sipcore mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/**listinfo/sipcore<https://www.ietf.org/mailman/listinfo/sipcore>
>>
>>
> ______________________________**_________________
> sipcore mailing list
> [e-mail]
> https://www.ietf.org/mailman/**listinfo/sipcore<https://www.ietf.org/mailman/listinfo/sipcore>
>