CINXE.COM
Common Questions on Trusted Community Representatives
<!doctype html> <html> <head> <title>Common Questions on Trusted Community Representatives</title> <meta charset="utf-8" /> <meta http-equiv="Content-type" content="text/html; charset=utf-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> <link rel="stylesheet" href="/_css/2025.01/iana_website.css"/> <link rel="shortcut icon" type="image/ico" href="/_img/bookmark_icon.ico"/> <script type="text/javascript" src="/_js/jquery.js"></script> <script type="text/javascript" src="/_js/iana.js"></script> </head> <body> <header> <div id="header"> <div id="logo"> <a href="/"><img src="/_img/2025.01/iana-logo-header.svg" alt="Homepage"/></a> </div> <div class="navigation"> <ul> <li><a href="/domains">Domains</a></li> <li><a href="/protocols">Protocols</a></li> <li><a href="/numbers">Numbers</a></li> <li><a href="/about">About</a></li> </ul> </div> </div> </header> <div id="body"> <article class="hemmed sidenav"> <main> <div class="help-article"> <h1>Common Questions on Trusted Community Representatives</h1> <h2>Who pays for travel?</h2> <p>We provide a <a href="/help/tcr-travel-support">travel support program</a> for trusted community representatives that covers airfares, accommodation and other costs. This program is optional, and TCRs may choose to arrange their own travel at their own cost.</p> <h2>What part of the TCR Statement of Interest will be published?</h2> <p>A list of names and country of citizenship of selected TCR candidates will be <a href="/dnssec/tcrs">published</a>, but any details (e.g. references) submitted will be kept confidential.</p> <h2>How long is the key ceremony?</h2> <p>Typical ceremonies take 3-4 hours, see our <a href="/help/key-ceremony-schedule">typical ceremony schedule</a> for a rundown on how they are configured.</p> <p>The first key ceremony is expected to be the longest and took around 8 hours. Longer ceremonies in the future will likely be when there needs to be a re-issuing of credentials due to personnel changes or the need to rebuild the KSK.</p> <h2>How often should a CO expect to travel to a ceremony?</h2> <p>To handle travel problems (e.g. delayed flights), we will call more than 3 Crypto Officers (CO) for each ceremony. That makes 1-2 travels per year for the average crypto officer, as the two (2) sets of Crypto Officers are normally called alternately.</p> <h2>How often should a RKSH expect to travel to a ceremony?</h2> <p>Except for the first ceremony, in which the Recovery Key Share Holders (RKSH) were needed for both phases (and thus had to travel between the east and west coast facilities), the RKSH are not expected to travel to a ceremony except in case of a key management emergency.</p> <h2>Can a RKSH pass international borders with its RKSH smart card?</h2> <p>As the contents of the card does not contain a complete cryptographic key, only a small fragment of one, we do not expect any general import/export restrictions on the smart card.</p> <p>It is safe to pass the smart card through airport x-ray and security screening, just like it is safe to pass your EMV credit card or the like.</p> <h2>Where should the RKSH keep its smart card?</h2> <p>A safe deposit box (or equivalent) at the recover key share holder鈥檚 local bank is a good choice. The smart card should be protected from theft and physical damage (e.g., fire, flooding).</p> <h2>What type of inventory of are the RKSH expected to performed?</h2> <p>The KSK operator DNSSEC Practice Statement (DPS) states that an inventory of Recovery Key Shares should be performed annually. This will typically be performed by having each RKSH submit a picture of its key share together with a secret phrase we provide.</p> <h2>What happens if a RKSH loses its key share?</h2> <p>If more than one key share is lost, we will start to plan to re-split the recovery key and recommission the share holders.</p> <div class="last-updated">Last revised 2017-05-13.</div> </div> </main> <nav id="sidenav"> </nav> </article> </div> <footer> <div id="footer"> <table class="navigation"> <tr> <td class="section"><a href="/domains">Domain Names</a></td> <td class="subsection"> <ul> <li><a href="/domains/root">Root Zone Registry</a></li> <li><a href="/domains/int">.INT Registry</a></li> <li><a href="/domains/arpa">.ARPA Registry</a></li> <li><a href="/domains/idn-tables">IDN Repository</a></li> </ul> </td> </tr> <tr> <td class="section"><a href="/numbers">Number Resources</a></td> <td class="subsection"> <ul> <li><a href="/abuse">Abuse Information</a></li> </ul> </td> </tr> <tr> <td class="section"><a href="/protocols">Protocols</a></td> <td class="subsection"> <ul> <li><a href="/protocols">Protocol Registries</a></li> <li><a href="/time-zones">Time Zone Database</a></li> </ul> </td> </tr> <tr> <td class="section"><a href="/about">About Us</a></td> <td class="subsection"> <ul> <li><a href="/news">News</a></li> <li><a href="/performance">Performance</a></li> <li><a href="/about/excellence">Excellence</a></li> <li><a href="/archive">Archive</a></li> <li><a href="/contact">Contact Us</a></li> </ul> </td> </tr> </table> <div id="custodian"> <p>The IANA functions coordinate the Internet鈥檚 globally unique identifiers, and are provided by <a href="https://pti.icann.org">Public Technical Identifiers</a>, an affiliate of <a href="http://www.icann.org/">ICANN</a>.</p> </div> <div id="legalnotice"> <ul> <li><a href="https://www.icann.org/privacy/policy">Privacy Policy</a></li> <li><a href="https://www.icann.org/privacy/tos">Terms of Service</a></li> </ul> </div> </div> </footer> </body> </html>