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 <brett@broadsoft.com> 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
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>