es

Overview

• The MACE URN and OID documentation is found on the Interent2 website here: https://www.internet2.edu/products-services/trust-identity/mace-registries/
• See the original MACE URN RFC here https://tools.ietf.org/html/rfc3613

Frequency of Requests for URNS and OIDs:

• • URNs: Since 2015 Internet2 has tried to discourage new URN requests with a note about a preference for URLs. See here: https://www.internet2.edu/products-services/trust-identity/mace-registries/#service-faq 
    However we still get several URN requests each year.    
    • 4 new URNs in 2016
    • 6 new URNs in 2017
    • 4 new URNs in 2018
  • OIDs: There was only one change to the OID registry in the past 5 years. That was for TIER Data Structures and APIs work. The requestor was Keith Hazelton. https://www.internet2.edu/products-services/trust-identity/mace-registries/internet2-object-identifier-oid-registrations/

URN Process

1. Request for an URN
   1. The MACE URN request form is found here:  https://www.internet2.edu/products-services/trust-identity/mace-registries/urnmace-request-form/
   2. The form is to be copied and sent be email to mace-submit@internet2.edu
   3. The recipients of the email are Tom Barton, Keith Hazelton, Jim Jokl, Jessica and Dean.
2. Processing the URN Request
   
   1. Upon receipt of an email requesting an URN,  Keith and Jim  and Tom check:

• • •  is the domain requested .edu (or equivalent in other countries) 

                          -- or --

• • •   If not edu, determine does the domain represent a recognized identity federation or research facility

                         Next

• • • Does the primary requester hold a title that makes it appropriate for her to speak for the requested domain?
    • Do the requesters' emails come from the same domain that they are seeking to register?
    • If they don't provide a documentation URL, request that they send it as soon as they get one.

1. 1.  If Keith, Jim  and TomB have concerns based on  the above checks, they reply to the requester with  the concerns with a copy to mace-submit@internet2.edu.
   2. Assuming Keith, Jim and TomB  approve the request, they reply to the requestor, with a copy to mace-submit@internet2.edu informing that the request has been approved.
   3. Jessica then adds the URN to the bottom of the table on this web page https://www.internet2.edu/products-services/trust-identity/mace-registries/urnmace-namespace/
      1.  has been adding the URNs to the web table using the source code editing feature in Django content manager. 
         It   also works to add a table row without editing the source code. Here is info from webmaster Mike Creech as of Aug 2018:
         1. Once you have opened the page and double-clicked on the text plugin with the table in it, you can right-click with your mouse on the previous row of the table and be offered the option to insert a new row.  
   4. Jessica emails the submitter, copying mace-submit@internet2.edu informing the submitter that their URN is on the website.
2. Maintaining the URNs
   1. occasionally someone emails with an update of the contact person to their existing URN. In this case, Jessica makes the update on the website and replies that the update has been made. 
3. See sample emails for an URN request and approval here

OID Process

• • The OID requestor sends an email to mace-submit@internet2.edu as explained here  https://www.internet2.edu/products-services/trust-identity/mace-registries/#service-registries
  •  Keith or Jim respond.
  • Jessica updates the registrations page on the website.