f81d4fae-7ced-11d0-a765-00a0c91e6bf6
SIP Subscription URN example

Seen in rfc6080

Seen in RFC 6080
Counts : rfc6080:1
RFC 6080               SIP Configuration Framework            March 2011


   If the device needs to create a Subscription URI and needs to use its
   device identifier, it MUST use the UUID-based (Universally Unique
   Identifier) URN representation as specified in [RFC4122].  The
   following requirements apply:

   o  When the device has a non-alterable Media Access Control (MAC)
      address, it SHOULD use the version 1 UUID representation with the
      timestamp and clock sequence bits set to a value of '0'.  This
      will allow for easy recognition, and uniqueness of MAC-address-
      based UUIDs.  An exception is the case where the device supports
      independent device configuration for more than one SIP UA.  An
      example would be multiple SIP UAs on the same platform.

   o  If the device cannot use a non-alterable device identifier, it
      SHOULD use an alternative non-alterable device identifier.  For
      example, the International Mobile Equipment Identity (IMEI) for
      mobile devices.

   o  If the device cannot use a non-alterable MAC address, it MUST use
      the same approach as defining a user agent instance ID in
      [RFC5626].

   o  Note: when the URN is used as the user part of the Request-URI, it
      MUST be URL escaped since the colon (":") is not a legal character
      in the user part of an addr-spec ([RFC4122]), and must be escaped.

         For example, the instance ID:
         urn:uuid:f81d4fae-7ced-11d0-a765-00a0c91e6bf6@example.com

         would be escaped to look as follows in a URI:
         sip:urn%3auuid%3af81d4fae-7ced-11d0-a765-00a0c91e6bf6@
         example.com

         The ABNF ([RFC5234]) for the UUID representation is provided in
         [RFC4122].

5.1.4.3.  User Profile Type

   To create a Subscription URI to request the user profile on behalf of
   a user, the device needs to know the user's AoR.  This can be
   statically or dynamically configured on the device (e.g., user input,
   or propagated as part of the device profile).  Similar to device
   profiles, the content and propagation of user profiles may differ,
   based on deployment scenarios (i.e., users belonging to the same
   domain may -- or may not -- be provided the same profile).  To create
   a Subscription URI, the following rules apply:





Petrie & Channabasappa       Standards Track                   [Page 21]
-1 RFC regex push
SIP Subscription URN example

0