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

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-18.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-instanceid-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
>