IETF Logo Mail Archive

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

Brett Tate <brett@broadsoft.com> Tue, 01 October 2013 18:25 UTC

Return-Path: <brett@broadsoft.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 4B20321F9DAF for <sipcore@ietfa.amsl.com>; Tue, 1 Oct 2013 11:25:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 flzkM8G3lZhA for <sipcore@ietfa.amsl.com>; Tue, 1 Oct 2013 11:25:19 -0700 (PDT)
Received: from smtpout01.partnerhosted.com (smtpout01.partnerhosted.com [173.225.22.203]) by ietfa.amsl.com (Postfix) with ESMTP id F123321F9DA8 for <sipcore@ietf.org>; Tue, 1 Oct 2013 11:25:18 -0700 (PDT)
Received: from CASUMHUB05.citservers.local (172.16.98.229) by smtpedge.partnerhosted.com (172.16.98.247) with Microsoft SMTP Server (TLS) id 14.2.247.3; Tue, 1 Oct 2013 11:26:17 -0700
Received: from MBX08.citservers.local ([fe80::2564:652:8dc8:caae]) by casumhub05.citservers.local ([::1]) with mapi id 14.02.0247.003; Tue, 1 Oct 2013 11:26:17 -0700
From: Brett Tate <brett@broadsoft.com>
To: "draft-ietf-sipcore-rfc4244bis@tools.ietf.org" <draft-ietf-sipcore-rfc4244bis@tools.ietf.org>, "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: [sipcore] draft-ietf-sipcore-rfc4244bis-11: ABNF backward compatibility
Thread-Index: AQHOvs2SCjLCpQxSiEm3Y+LPiDjPAZngJOEg
Date: Tue, 01 Oct 2013 18:26:15 +0000
Message-ID: <576A8B541C219D4E9CEB1DF8C19C7B881A061FED@MBX08.citservers.local>
References: <576A8B541C219D4E9CEB1DF8C19C7B881A061F01@MBX08.citservers.local> <CAHBDyN5zNiLjihMO-o96Avu7zDbm96ihfwgifvgbx28aQ1Vv7Q@mail.gmail.com>
In-Reply-To: <CAHBDyN5zNiLjihMO-o96Avu7zDbm96ihfwgifvgbx28aQ1Vv7Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.16.98.77]
Content-Type: multipart/alternative; boundary="_000_576A8B541C219D4E9CEB1DF8C19C7B881A061FEDMBX08citservers_"
MIME-Version: 1.0
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: Tue, 01 Oct 2013 18:25:23 -0000

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

Thanks,
Brett

From: Mary Barnes [mailto:mary.ietf.barnes@gmail.com]
Sent: Tuesday, October 01, 2013 1:41 PM
To: Brett Tate
Cc: draft-ietf-sipcore-rfc4244bis@tools.ietf.org; sipcore@ietf.org
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 <brett@broadsoft.com<mailto: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<mailto:sipcore@ietf.org>
https://www.ietf.org/mailman/listinfo/sipcore

v2.23.0 | Report a Bug | By Email