http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instanceid is also required in order to use the IMEI as a SIP instance ID. So just not registering the sub namespace doesn't avoid the IETF having to address the issue. As John pointed out having the sub namespace reviewed by IETF provides the opportunity to add text to address privacy concerns with any inappropriate usage. ----- Original Message ----- From: S Moonesamy [mailto:sm+ietf@xxxxxxxxxxxx] Sent: Saturday, July 20, 2013 06:50 PM Central Standard Time To: Andrew Allen Cc: scott.brim@xxxxxxxxx <scott.brim@xxxxxxxxx>; sm+ietf@xxxxxxxxxxxx <sm+ietf@xxxxxxxxxxxx>; ietf@xxxxxxxx <ietf@xxxxxxxx>; tbray@xxxxxxxxxxxxxx <tbray@xxxxxxxxxxxxxx>; draft-montemurro-gsma-imei-urn.all@xxxxxxxxxxxxxx <draft-montemurro-gsma-imei-urn.all@xxxxxxxxxxxxxx> Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt Hi Andrew, At 13:48 20-07-2013, Andrew Allen wrote: >I think IANA registration of namespaces has a lot of value. draft-montemurro-gsma-imei-urn-16 discusses about two namespaces: (i) gsma (ii) imei It is not possible to get a IANA registration for (ii) as according to draft-montemurro-gsma-imei-urn-16 (ii) is managed by (i). In simple terms (ii) does not require IETF approval. Regards, S. Moonesamy --------------------------------------------------------------------- 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.