IETF Logo Mail Archive

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

Francois Audet <francois.audet@skype.net> Tue, 01 October 2013 17:47 UTC

Return-Path: <francois.audet@skype.net>
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 94A5E11E8153 for <sipcore@ietfa.amsl.com>; Tue, 1 Oct 2013 10:47:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 WnlC9guCCAvG for <sipcore@ietfa.amsl.com>; Tue, 1 Oct 2013 10:47:23 -0700 (PDT)
Received: from na01-sn2-obe.outbound.o365filtering.com (na01-sn2-obe.ptr.o365filtering.com [157.55.158.27]) by ietfa.amsl.com (Postfix) with ESMTP id BDC3721E805F for <sipcore@ietf.org>; Tue, 1 Oct 2013 10:47:17 -0700 (PDT)
Received: from BY2SR01CA104.namsdf01.sdf.exchangelabs.com (10.255.93.149) by BY2SR01MB609.namsdf01.sdf.exchangelabs.com (10.255.93.168) with Microsoft SMTP Server (TLS) id 15.0.800.2; Tue, 1 Oct 2013 17:47:14 +0000
Received: from BY1FFOFD001.ffo.gbl (64.4.22.90) by BY2SR01CA104.outlook.office365.com (10.255.93.149) with Microsoft SMTP Server (TLS) id 15.0.800.2 via Frontend Transport; Tue, 1 Oct 2013 17:47:14 +0000
Received: from hybrid.exchange.microsoft.com (131.107.1.17) by BY1FFOFD001.mail.o365filtering.com (10.1.16.83) with Microsoft SMTP Server (TLS) id 15.0.795.3 via Frontend Transport; Tue, 1 Oct 2013 17:47:14 +0000
Received: from DFM-TK5MBX15-03.exchange.corp.microsoft.com (157.54.110.22) by DF-G14-01.exchange.corp.microsoft.com (157.54.87.87) with Microsoft SMTP Server (TLS) id 14.3.123.1; Tue, 1 Oct 2013 17:46:54 +0000
Received: from DFM-DB3MBX15-08.exchange.corp.microsoft.com (10.166.18.226) by DFM-TK5MBX15-03.exchange.corp.microsoft.com (157.54.110.22) with Microsoft SMTP Server (TLS) id 15.0.775.14; Tue, 1 Oct 2013 10:46:41 -0700
Received: from DFM-DB3MBX15-06.exchange.corp.microsoft.com (10.166.18.224) by DFM-DB3MBX15-08.exchange.corp.microsoft.com (10.166.18.226) with Microsoft SMTP Server (TLS) id 15.0.775.14; Tue, 1 Oct 2013 10:46:27 -0700
Received: from DFM-DB3MBX15-06.exchange.corp.microsoft.com ([10.166.18.224]) by DFM-DB3MBX15-06.exchange.corp.microsoft.com ([169.254.10.253]) with mapi id 15.00.0775.014; Tue, 1 Oct 2013 10:46:27 -0700
From: Francois Audet <francois.audet@skype.net>
To: Mary Barnes <mary.ietf.barnes@gmail.com>, Brett Tate <brett@broadsoft.com>
Thread-Topic: [sipcore] draft-ietf-sipcore-rfc4244bis-11: ABNF backward compatibility
Thread-Index: AQHOvs2LaFm4ZTyhCE6+C75znn+hHpngHpCg
Date: Tue, 01 Oct 2013 17:46:26 +0000
Message-ID: <620020d3b4ca4d2fad8e7ad55a290f41@DFM-DB3MBX15-06.exchange.corp.microsoft.com>
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: [157.54.51.13]
Content-Type: multipart/alternative; boundary="_000_620020d3b4ca4d2fad8e7ad55a290f41DFMDB3MBX1506exchangeco_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.1.17; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(164054003)(24454002)(199002)(189002)(377454003)(56776001)(54316002)(49866001)(66066001)(31966008)(71186001)(80022001)(47446002)(74502001)(46102001)(50986001)(47736001)(47976001)(59766001)(19580395003)(512954002)(81686001)(6806004)(79102001)(80976001)(65816001)(20776003)(84326002)(15975445006)(63696002)(81342001)(76482001)(69226001)(81542001)(33646001)(76786001)(74706001)(81816001)(74876001)(53806001)(74662001)(74366001)(56816003)(83072001)(4396001)(77982001)(83322001)(19580405001)(54356001)(51856001)(44976005)(16236675003)(15202345003)(19300405004)(76796001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2SR01MB609; H:hybrid.exchange.microsoft.com; CLIP:131.107.1.17; FPR:; RD:mail1.exchange.microsoft.com; A:1; MX:1; LANG:en;
X-Forefront-PRVS: 09860C2161
X-OriginatorOrg: msft.ccsctp.net
Cc: "draft-ietf-sipcore-rfc4244bis@tools.ietf.org" <draft-ietf-sipcore-rfc4244bis@tools.ietf.org>, "sipcore@ietf.org" <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: Tue, 01 Oct 2013 17:47:29 -0000

It does indeed look like an error to be fixed.

From: sipcore-bounces@ietf.org [mailto:sipcore-bounces@ietf.org] On Behalf Of Mary Barnes
Sent: Tuesday, October 1, 2013 10:41 AM
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