Re: [dispatch] draft-montemurro-gsma-imei-urn-18

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 25 November 2013 17:50 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19A981AD8D5 for <dispatch@ietfa.amsl.com>; Mon, 25 Nov 2013 09:50:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XsTlkEkxzVIV for <dispatch@ietfa.amsl.com>; Mon, 25 Nov 2013 09:50:19 -0800 (PST)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id 87BE61ADFE6 for <dispatch@ietf.org>; Mon, 25 Nov 2013 09:50:18 -0800 (PST)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta05.westchester.pa.mail.comcast.net with comcast id toel1m00127AodY55tqJUT; Mon, 25 Nov 2013 17:50:18 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta19.westchester.pa.mail.comcast.net with comcast id ttqJ1m00B3ZTu2S3ftqJX9; Mon, 25 Nov 2013 17:50:18 +0000
Message-ID: <52938DDA.5070003@alum.mit.edu>
Date: Mon, 25 Nov 2013 09:50:18 -0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Andrew Allen <aallen@blackberry.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "dispatch@ietf.org" <dispatch@ietf.org>
References: <BBF5DDFE515C3946BC18D733B20DAD2338E67A36@XMB104ADS.rim.net> <528E69CC.9040909@alum.mit.edu> <52936A3C.4090804@ericsson.com> <529371DD.8080307@alum.mit.edu> <BBF5DDFE515C3946BC18D733B20DAD2338E6B648@XMB104ADS.rim.net>
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD2338E6B648@XMB104ADS.rim.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1385401818; bh=1iYKQH+UILCBgem42wvHd8AFVG0+p1XzRpMiT/h0P5g=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=Te7dQLjtX7k/Bh/QnoHRrG9M0fPAx1gTbMMwAV3k2o5PByKReBszQ2FvoTGvSCwiA 9uGtP+PVAzV7AGqbcBnGUAWpihbNv9FsyEljWj9hRUHW98p3Zpxy30mEm8W8M2eaCO dRBFh56EkWF4SRg44eXjMB2A9q9u2ygN8bF87TBuWvuWcNBFV9jmnTDYjMztkyrB44 EbhQwS9cf0aeFGfpYDeItFBVvHBxtxILtT0NDgrJ73doGnZc5GIBHgdhNnWliquZzt WtP14RO33lHlWiakYO1KFkTvp3/6Pi/Bq/PRJml38wo56qgl5XkGaCUsdOfsynRFSW 6PciAMYfWA8lw==
Subject: Re: [dispatch] draft-montemurro-gsma-imei-urn-18
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Nov 2013 17:50:20 -0000

On 11/25/13 9:18 AM, Andrew Allen wrote:
> Paul
>
> I propose to change the ABNF to not allow ";" as an ext-imei character

OK. If that works for you it works for me.

	Thanks,
	Paul

> Andrew
>
> -----Original Message-----
> From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: Monday, November 25, 2013 10:51 AM
> To: Gonzalo Camarillo; dispatch@ietf.org
> Subject: Re: [dispatch] draft-montemurro-gsma-imei-urn-18
>
> On 11/25/13 7:18 AM, Gonzalo Camarillo wrote:
>> Hi Paul,
>>
>> thanks for the comment. Andrew will try and address it as an IETF LC
>> once the new IETF LC on the draft is over.
>
> OK. Note that this is more than editorial. To fix it, either the ";"
> must be excluded as an alternative, or quoting or escaping will need to be introduced.
>
> 	Thanks,
> 	Paul
>
>> Cheers,
>>
>> Gonzalo
>>
>> On 21/11/2013 9:15 PM, Paul Kyzivat wrote:
>>> One comment on this.
>>>
>>> I see the syntax has been extended. The extension has introduced an
>>> ambiguity:
>>>
>>>            imei-specifier = "imei:" ( imeival / ext-imei )
>>>                                             [ ";" sw-version-param ]
>>>                                             [ ";" imei-version-param ]
>>>            ext-imei = gsma-defined-nonempty-string ;GSMA defined
>>>                                                    ;and IETF
>>>                                                    ;consensus
>>>                                                    ;required ...
>>>            gsma-defined-nonempty-string = 1*gsma-urn-char
>>>            gsma-urn-char  = ALPHA / DIGIT
>>>                            / "-" / "." / "_" / "%"/":"/";"/"="
>>>
>>> ext-imei may contain a semicolon, and then following that a semicolon
>>> may also be used to initiate parameters.
>>>
>>>       Thanks,
>>>       Paul
>>>
>>> On 11/21/13 9:56 AM, Andrew Allen wrote:
>>>> Revised versions of draft-montemurro-gsma-imei-urn  and
>>>> draft-allen-dispatch-imei-urn-as-instanceid have been submitted.
>>>>
>>>> They can be found at:
>>>>
>>>> http://www.ietf.org/internet-drafts/draft-montemurro-gsma-imei-urn-1
>>>> 8.txt
>>>>
>>>> http://www.ietf.org/internet-drafts/draft-allen-dispatch-imei-urn-as
>>>> -instanceid-12.txt
>>>>
>>>>
>>>> along with the diffs from the previous versions at:
>>>>
>>>> http://www.ietf.org/rfcdiff?url2=draft-montemurro-gsma-imei-urn-18
>>>>
>>>> http://www.ietf.org/rfcdiff?url2=draft-allen-dispatch-imei-urn-as-in
>>>> stanceid-12
>>>>
>>>>
>>>> The main changes are as follows:
>>>>
>>>> draft-montemurro-gsma-imei-urn:
>>>>
>>>> The  ABNF has been updated to include the ability to extend the IMEI
>>>> value format in the future (as previously stated in the text) while
>>>> allowing a parser compliant with the current version of the
>>>> specification to still validate the URN.
>>>>
>>>> draft-allen-dispatch-imei-urn-as-instanceid
>>>>
>>>> The Emergency Access Transfer Function has been mentioned in the
>>>> Emergency Session transfer Use case.
>>>>
>>>> Various NITS have also been addressed.
>>>>
>>>> Please provide any comments as soon as possible. I understand that
>>>> the AD plans to make another IETF Last Call on these soon.
>>>>
>>>> Thanks
>>>>
>>>> Andrew
>>>>
>>>> --------------------------------------------------------------------
>>>> - This transmission (including any attachments) may contain
>>>> confidential information, privileged material (including material
>>>> protected by the solicitor-client or other applicable privileges),
>>>> or constitute non-public information. Any use of this information by
>>>> anyone other than the intended recipient is prohibited. If you have
>>>> received this transmission in error, please immediately reply to the
>>>> sender and delete this information from your system. Use,
>>>> dissemination, distribution, or reproduction of this transmission by
>>>> unintended recipients is not authorized and may be unlawful.
>>>>
>>>>
>>>> _______________________________________________
>>>> dispatch mailing list
>>>> dispatch@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/dispatch
>>>>
>>>
>>> _______________________________________________
>>> dispatch mailing list
>>> dispatch@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dispatch
>>>
>>>
>>
>>
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
>
>