discontinued / server · Files

index.html 358 KB
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 2566 2567 2568 2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 2582 2583 2584 2585 2586 2587 2588 2589 2590 2591 2592 2593 2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751 2752 2753 2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942 2943 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3000 3001 3002 3003 3004 3005 3006 3007 3008 3009 3010 3011 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 3069 3070 3071 3072 3073 3074 3075 3076 3077 3078 3079 3080 3081 3082 3083 3084 3085 3086 3087 3088 3089 3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 3129 3130 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3482 3483 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3972 3973 3974 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390 4391 4392 4393 4394 4395 4396 4397 4398 4399 4400 4401 4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 4418 4419 4420 4421 4422 4423 4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4450 4451 4452 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510 4511 4512 4513 4514 4515 4516 4517 4518 4519 4520 4521 4522 4523 4524 4525 4526 4527 4528 4529 4530 4531 4532 4533 4534 4535 4536 4537 4538 4539 4540 4541 4542 4543 4544 4545 4546 4547 4548 4549 4550 4551 4552 4553 4554 4555 4556 4557 4558 4559 4560 4561 4562 4563 4564 4565 4566 4567 4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 4610 4611 4612 4613 4614 4615 4616 4617 4618 4619 4620 4621 4622 4623 4624 4625 4626 4627 4628 4629 4630 4631 4632 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644 4645 4646 4647 4648 4649 4650 4651 4652 4653 4654 4655 4656 4657 4658 4659 4660 4661 4662 4663 4664 4665 4666 4667 4668 4669 4670 4671 4672 4673 4674 4675 4676 4677 4678 4679 4680 4681 4682 4683 4684 4685 4686 4687 4688 4689 4690 4691 4692 4693 4694 4695 4696 4697 4698 4699 4700 4701 4702 4703 4704 4705 4706 4707 4708 4709 4710 4711 4712 4713 4714 4715 4716 4717 4718 4719 4720 4721 4722 4723 4724 4725 4726 4727 4728 4729 4730 4731 4732 4733 4734 4735 4736 4737 4738 4739 4740 4741 4742 4743 4744 4745 4746 4747 4748 4749 4750 4751 4752 4753 4754 4755 4756 4757 4758 4759 4760 4761 4762 4763 4764 4765 4766 4767 4768 4769 4770 4771 4772 4773 4774 4775 4776 4777 4778 4779 4780 4781 4782 4783 4784 4785 4786 4787 4788 4789 4790 4791 4792 4793 4794 4795 4796 4797 4798 4799 4800 4801 4802 4803 4804 4805 4806 4807 4808 4809 4810 4811 4812 4813 4814 4815 4816 4817 4818 4819 4820 4821 4822 4823 4824 4825 4826 4827 4828 4829 4830 4831 4832 4833 4834 4835 4836 4837 4838 4839 4840 4841 4842 4843 4844 4845 4846 4847 4848 4849 4850 4851 4852 4853 4854 4855 4856 4857 4858 4859 4860 4861 4862 4863 4864 4865 4866 4867 4868 4869 4870 4871 4872 4873 4874 4875 4876 4877 4878 4879 4880 4881 4882 4883 4884 4885 4886 4887 4888 4889 4890 4891 4892 4893 4894 4895 4896 4897 4898 4899 4900 4901 4902 4903 4904 4905 4906 4907 4908 4909 4910 4911 4912 4913 4914 4915 4916 4917 4918 4919 4920 4921 4922 4923 4924 4925 4926 4927 4928 4929 4930 4931 4932 4933 4934 4935 4936 4937 4938 4939 4940 4941 4942 4943 4944 4945 4946 4947 4948 4949 4950 4951 4952 4953 4954 4955 4956 4957 4958 4959 4960 4961 4962 4963 4964 4965 4966 4967 4968 4969 4970 4971 4972 4973 4974 4975 4976 4977 4978 4979 4980 4981 4982 4983 4984 4985 4986 4987 4988 4989 4990 4991 4992 4993 4994 4995 4996 4997 4998 4999 5000 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020 5021 5022 5023 5024 5025 5026 5027 5028 5029 5030 5031 5032 5033 5034 5035 5036 5037 5038 5039 5040 5041 5042 5043 5044 5045 5046 5047 5048 5049 5050 5051 5052 5053 5054 5055 5056 5057 5058 5059 5060 5061 5062 5063 5064 5065 5066 5067 5068 5069 5070 5071 5072 5073 5074 5075 5076 5077 5078 5079 5080 5081 5082 5083 5084 5085 5086 5087 5088 5089 5090 5091 5092 5093 5094 5095 5096 5097 5098 5099 5100 5101 5102 5103 5104 5105 5106 5107 5108 5109 5110 5111 5112 5113 5114 5115 5116 5117 5118 5119 5120 5121 5122 5123 5124 5125 5126 5127 5128 5129 5130 5131 5132 5133 5134 5135 5136 5137 5138 5139 5140 5141 5142 5143 5144 5145 5146 5147 5148 5149 5150 5151 5152 5153 5154 5155 5156 5157 5158 5159 5160 5161 5162 5163 5164 5165 5166 5167 5168 5169 5170 5171 5172 5173 5174 5175 5176 5177 5178 5179 5180 5181 5182 5183 5184 5185 5186 5187 5188 5189 5190 5191 5192 5193 5194 5195 5196 5197 5198 5199 5200 5201 5202 5203 5204 5205 5206 5207 5208 5209 5210 5211 5212 5213 5214 5215 5216 5217 5218 5219 5220 5221 5222 5223 5224 5225 5226 5227 5228 5229 5230 5231 5232 5233 5234 5235 5236 5237 5238 5239 5240 5241 5242 5243 5244 5245 5246 5247 5248 5249 5250 5251 5252 5253 5254 5255 5256 5257 5258 5259 5260 5261 5262 5263 5264 5265 5266 5267 5268 5269 5270 5271 5272 5273 5274 5275 5276 5277 5278 5279 5280 5281 5282 5283 5284 5285 5286 5287 5288 5289 5290 5291 5292 5293 5294 5295 5296 5297 5298 5299 5300 5301 5302 5303 5304 5305 5306 5307 5308 5309 5310 5311 5312 5313 5314 5315 5316 5317 5318 5319 5320 5321 5322 5323 5324 5325 5326 5327 5328 5329 5330 5331 5332 5333 5334 5335 5336 5337 5338 5339 5340 5341 5342 5343 5344 5345 5346 5347 5348 5349 5350 5351 5352 5353 5354 5355 5356 5357 5358 5359 5360 5361 5362 5363 5364 5365 5366 5367 5368 5369 5370 5371 5372 5373 5374 5375 5376 5377 5378 5379 5380 5381 5382 5383 5384 5385 5386 5387 5388 5389 5390 5391 5392 5393 5394 5395 5396 5397 5398 5399 5400 5401 5402 5403 5404 5405 5406 5407 5408 5409 5410 5411 5412 5413 5414 5415 5416 5417 5418 5419 5420 5421 5422 5423 5424 5425 5426 5427 5428 5429 5430 5431 5432 5433 5434 5435 5436 5437 5438 5439 5440 5441 5442 5443 5444 5445 5446 5447 5448 5449 5450 5451 5452 5453 5454 5455 5456 5457 5458 5459 5460 5461 5462 5463 5464 5465 5466 5467 5468 5469 5470 5471 5472 5473 5474 5475 5476 5477 5478 5479 5480 5481 5482 5483 5484 5485 5486 5487 5488 5489 5490 5491 5492 5493 5494 5495 5496 5497 5498 5499 5500 5501 5502 5503 5504 5505 5506 5507 5508 5509 5510 5511 5512 5513 5514 5515 5516 5517 5518 5519 5520 5521 5522 5523 5524 5525 5526 5527 5528 5529 5530 5531 5532 5533 5534 5535 5536 5537 5538 5539 5540 5541 5542 5543 5544 5545 5546 5547 5548 5549 5550 5551 5552 5553 5554 5555 5556 5557 5558 5559 5560 5561 5562 5563 5564 5565 5566 5567 5568 5569 5570 5571 5572 5573 5574 5575 5576 5577 5578 5579 5580 5581 5582 5583 5584 5585 5586 5587 5588 5589 5590 5591 5592 5593 5594 5595 5596 5597 5598 5599 5600 5601 5602 5603 5604 5605 5606 5607 5608 5609 5610 5611 5612 5613 5614 5615 5616 5617 5618 5619 5620 5621 5622 5623 5624 5625 5626 5627 5628 5629 5630 5631 5632 5633 5634 5635 5636 5637 5638 5639 5640 5641 5642 5643 5644 5645 5646 5647 5648 5649 5650 5651 5652 5653 5654 5655 5656 5657 5658 5659 5660 5661 5662 5663 5664 5665 5666 5667 5668 5669 5670 5671 5672 5673 5674 5675 5676 5677 5678 5679 5680 5681 5682 5683 5684 5685 5686 5687 5688 5689 5690 5691 5692 5693 5694 5695 5696 5697 5698 5699 5700 5701 5702 5703 5704 5705 5706 5707 5708 5709 5710 5711 5712 5713 5714 5715 5716 5717 5718 5719 5720 5721 5722 5723 5724 5725 5726 5727 5728 5729 5730 5731 5732 5733 5734 5735 5736 5737 5738 5739 5740 5741 5742 5743 5744 5745 5746 5747 5748 5749 5750 5751 5752 5753 5754 5755 5756 5757 5758 5759 5760 5761 5762 5763 5764 5765 5766 5767 5768 5769 5770 5771 5772 5773 5774 5775 5776 5777 5778 5779 5780 5781 5782 5783 5784 5785 5786 5787 5788 5789 5790 5791 5792 5793 5794 5795 5796 5797 5798 5799 5800 5801 5802 5803 5804 5805 5806 5807 5808 5809 5810 5811 5812 5813 5814 5815 5816 5817 5818 5819 5820 5821 5822 5823 5824 5825 5826 5827 5828 5829 5830 5831 5832 5833 5834 5835 5836 5837 5838 5839 5840 5841 5842 5843 5844 5845 5846 5847 5848 5849 5850 5851 5852 5853 5854 5855 5856 5857 5858 5859 5860 5861 5862 5863 5864 5865 5866 5867 5868 5869 5870 5871 5872 5873 5874 5875 5876 5877 5878 5879 5880 5881 5882 5883 5884 5885 5886 5887 5888 5889 5890 5891 5892 5893 5894 5895 5896 5897 5898 5899 5900 5901 5902 5903 5904 5905 5906 5907 5908 5909 5910 5911 5912 5913 5914 5915 5916 5917 5918 5919 5920 5921 5922 5923 5924 5925 5926 5927 5928 5929 5930 5931 5932 5933 5934 5935 5936 5937 5938 5939 5940 5941 5942 5943 5944 5945 5946 5947 5948 5949 5950 5951 5952 5953 5954 5955 5956 5957 5958 5959 5960 5961 5962 5963 5964 5965 5966 5967 5968 5969 5970 5971 5972 5973 5974 5975 5976 5977 5978 5979 5980 5981 5982 5983 5984 5985 5986 5987 5988 5989 5990 5991 5992 5993 5994 5995 5996 5997 5998 5999 6000 6001 6002 6003 6004 6005 6006 6007 6008 6009 6010 6011 6012 6013 6014 6015 6016 6017 6018 6019 6020 6021 6022 6023 6024 6025 6026 6027 6028 6029 6030 6031 6032 6033 6034 6035 6036 6037 6038 6039 6040 6041 6042 6043 6044 6045 6046 6047 6048 6049 6050 6051 6052 6053 6054 6055 6056 6057 6058 6059 6060 6061 6062 6063 6064 6065 6066 6067 6068 6069 6070 6071 6072 6073 6074 6075 6076 6077 6078 6079 6080 6081 6082 6083 6084 6085 6086 6087 6088 6089 6090 6091 6092 6093 6094 6095 6096 6097 6098 6099 6100 6101 6102 6103 6104 6105 6106 6107 6108 6109 6110 6111 6112 6113 6114 6115 6116 6117 6118 6119 6120 6121 6122 6123 6124 6125 6126 6127 6128 6129 6130 6131 6132 6133 6134 6135 6136 6137 6138 6139 6140 6141 6142 6143 6144 6145 6146 6147 6148 6149 6150 6151 6152 6153 6154 6155 6156 6157 6158 6159 6160 6161 6162 6163 6164 6165 6166 6167 6168 6169 6170 6171 6172 6173 6174 6175 6176 6177 6178 6179 6180 6181 6182 6183 6184 6185 6186 6187 6188 6189 6190 6191 6192 6193 6194 6195 6196 6197 6198 6199 6200 6201 6202 6203 6204 6205 6206 6207 6208 6209 6210 6211 6212 6213 6214 6215 6216 6217 6218 6219 6220 6221 6222 6223 6224 6225 6226 6227 6228 6229 6230 6231 6232 6233 6234 6235 6236 6237 6238 6239 6240 6241 6242 6243 6244 6245 6246 6247 6248 6249 6250 6251 6252 6253 6254 6255 6256 6257 6258 6259 6260 6261 6262 6263 6264 6265 6266 6267 6268 6269 6270 6271 6272 6273 6274 6275 6276 6277 6278 6279 6280 6281 6282 6283 6284 6285 6286 6287 6288 6289 6290 6291 6292 6293 6294 6295 6296 6297 6298 6299 6300 6301 6302 6303 6304 6305 6306 6307 6308 6309 6310 
<?xml version="1.0"?> 
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
  <title>XML Key Management Specification (XKMS 2.0)</title>
  <style type="text/css" xml:space="preserve">
      <!-- /*<![CDATA[*/
p.Code       { background-color: #00ffa7; background-repeat: repeat;
               background-attachment: scroll; font-family: Courier;
               margin-left: 0.5in; margin-right: 0.5in; margin-top: 0in;
               margin-bottom: 0pt }
a.markParagraph { }
p.toc1       { text-align: left; margin-left: 1pt; margin-top: 6pt;
               margin-bottom: 1pt }
p.toc2       { line-height: 100%; margin-top: 4pt; margin-bottom: 0 }
p.toc3       { line-height: 100%; margin-top: 2pt; margin-bottom: 10pt }
span.ID      { font-family: Courier }
pre.Code     { background-color: #ffffa7; background-repeat: repeat;
               background-attachment: scroll; font-family: Courier;
               margin-left: 0in; margin-right: 0in; margin-top: 0in;
               margin-bottom: 0pt }
pre.Example  { background-color: #d2e9ff; background-repeat: repeat;
               background-attachment: scroll; font-family: Courier;
               margin-left: 0in; margin-right: 0in; margin-top: 0in;
               margin-bottom: 0pt }
p.Comment    { background-color: #d2e9ff; background-repeat: repeat;
               background-attachment: scroll; font-family: Courier; color:
               #0000FF; font-style: italic; margin-left: 0.5in; margin-right:
               0.5in }
th.ID        { font-family: Courier }
c2 td.ID     { font-family: Courier }
p.center     { text-align: center }
p.caption    { text-align: center }
p.warning    { font-weight: bold }
h1.appendix  { page-break-before: always }
div.center   { text-align: center }
:link        { color: #0000FF }
:visited     { color: #800080 }
span.c32     { background-color: #FFFF00 }
span.c25     { color: red }
span.c13     { font-family: Arial }

div.contents ul li    { font-weight: bold }
div.contents ul li ul li { font-weight: normal }
/*]]>*/
 -->














































    </style>
  <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-REC" />
</head>

<body xml:lang="EN-US" lang="EN-US">

<div class="head">
<a href="http://www.w3.org/" shape="rect"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72" /></a> 

<h1 class="NoNumber" id="title"><a name="XKMS_2_0_Section_Marker_1" shape="rect" id="XKMS_2_0_Section_Marker_1"></a>XML
Key Management Specification (XKMS 2.0)</h1>

<h2 class="NoNumber" id="version"><a name="XKMS_2_0_Section_Marker_2" shape="rect" id="XKMS_2_0_Section_Marker_2"></a>Version 2.0</h2>

<h2 class="NoNumber" id="W3C-doctype"><a name="XKMS_2_0_Section_Marker_3" shape="rect" id="XKMS_2_0_Section_Marker_3"></a> <a name="Masthead" id="Masthead" shape="rect">W3C Recommendation 28 June 2005</a></h2>

<dl>
  <dt>This version:</dt>
    <dd><a href="http://www.w3.org/TR/2005/REC-xkms2-20050628/" shape="rect">http://www.w3.org/TR/2005/REC-xkms2-20050628/</a></dd>
  <dt>Latest version:</dt>
    <dd><a href="http://www.w3.org/TR/xkms2/" shape="rect">http://www.w3.org/TR/xkms2/</a></dd>
  <dt>Previous version:</dt>
    <dd><a href="http://www.w3.org/TR/2005/PR-xkms2-20050502/" shape="rect">http://www.w3.org/TR/2005/PR-xkms2-20050502/</a></dd>
  <dt>Editors:</dt>
    <dd>Phillip Hallam-Baker, Verisign</dd>
    <dd>Shivaram H. Mysore</dd>
  <dt>Contributors:</dt>
    <dd>See the <a href="#Acknowledgments" shape="rect">Acknowledgments</a>.</dd>
</dl>

<p>Please refer to the <a
href="http://www.w3.org/2005/06/xkms2-errata.html"><strong>errata</strong></a>
for this document, which may include some normative corrections.</p>

<p>See also <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=xkms2"><strong>translations</strong></a>.</p>

<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright"> Copyright</a> &#xa9;2005 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&#xae;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p>
</div>
<hr title="Separator from Header" />

<div>
<h2 class="Abstract"><a name="XKMS_2_0_Section_Marker_4" id="XKMS_2_0_Section_Marker_4" shape="rect"></a> <a id="abstract" name="abstract" shape="rect">Abstract</a></h2>

<p><a name="XKMS_2_0_Paragraph_2" id="XKMS_2_0_Paragraph_2" class="markParagraph" shape="rect">[2]</a>This document specifies protocols for
distributing and registering public keys, suitable for use in conjunction
with the W3C Recommendations for XML Signature <a href="#XML-SIG" shape="rect">[XML-SIG]</a> and XML Encryption [<a href="#XML-Enc" shape="rect">XML-Enc</a>]. The XML Key Management Specification (XKMS)
comprises two parts &#x2014; the XML Key Information Service Specification
(X-KISS) and the XML Key Registration Service Specification (X-KRSS).</p>

<h2 class="NoNumber"><a name="XKMS_2_0_Section_Marker_5" id="XKMS_2_0_Section_Marker_5" shape="rect"></a> <a name="status" id="status" shape="rect">Status of
this document</a></h2>

<p><em>This section describes the status of this document at the time
of its publication. Other documents may supersede this document. A
list of current W3C publications and the latest revision of this
technical report can be found in the <a
href="http://www.w3.org/TR/">W3C technical reports index</a> at
http://www.w3.org/TR/.</em></p>

<p>This document is a <a href="/2003/06/Process-20030618/tr.html#RecsW3C">W3C
Recommendation</a>. It has been reviewed by W3C Members and other interested
parties and has been endorsed by the Director. It is a stable document and
may be used as reference material or cited as a normative reference from
another document. W3C's role in making the Recommendation is to draw
attention to the specification and to promote its widespread deployment. This
enhances the functionality and interoperability of the Web.</p>

<p>This document has been produced by the <a
href="http://www.w3.org/2001/XKMS/" shape="rect">XKMS Working Group</a> (WG).
The English version of this specification is the only normative version. <a
href="http://www.w3.org/2003/03/Translations/byTechnology?technology=xkms2">Translations</a>
of this document may be available.</p>

<p>If you have any comments on this document, send them to <a
href="mailto:www-xkms@w3.org" shape="rect">www-xkms@w3.org</a>, a mailing
list with a <a href="http://lists.w3.org/Archives/Public/www-xkms/"
shape="rect">public archive</a>. An <a href="http://www.w3.org/2005/06/xkms2-errata">errata 
list</a> for this edition is available.</p>

<p>This is Part 1 of the W3C Recommendation for the XML Key
Management Specification (XKMS Version 2.0). This document specifies
protocols for distributing and registering public keys, suitable for use in
conjunction with the proposed standard for <a
href="http://www.w3.org/TR/xmldsig-core/">XML Signature</a> and <a
href="http://www.w3.org/TR/xmlenc-core/">XML Encryption</a>. <a
href="/TR/xkms2/">The XML Key Management Specification (XKMS)</a> comprises
two services &#x2014; the XML Key Information Service (X-KISS) and the XML Key
Registration Service Specification (X-KRSS). <a
href="/TR/2005/REC-xkms2-bindings-20050628/">Part 2</a> of this
specification covers different protocol bindings with security
characteristics for XKMS. For background on this work, please see the <a
href="http://www.w3.org/2001/XKMS/Activity" shape="rect">XKMS Activity Statement</a>.</p>

<p>This document is based on the <a href="/TR/2005/PR-xkms2-20050502/">XKMS
Version 2.0 Proposed Recommendation</a> of 2 May 2005. <a
href="/2001/XKMS/Drafts/pr-issues/issues.html">Feedback</a> received during
that review resulted in minor editorial changes. Evidence of interoperation
between at least two implementations of this specification are documented in
the <a
href="/2001/XKMS/Drafts/test-suite/CR-XKMS-Summary.html">Implementation
Report</a>. Changes to this document since the Proposed Recommendation
version are detailed in <a href="#XKMS_2_0_Section_Appendix_F">Appendix
F</a>.</p>

<p>This document was produced under the <a
href="http://www.w3.org/TR/2002/NOTE-patent-practice-20020124">24
January 2002 CPP</a> as amended by the <a
href="http://www.w3.org/2004/02/05-pp-transition">W3C Patent Policy
Transition Procedure</a>. The Working Group maintains a <a
rel="disclosure" 
href="http://www.w3.org/2001/XKMS/Disclosures.html">public list of
patent disclosures</a> relevant to this document; that page also
includes instructions for disclosing a patent. An individual who has
actual knowledge of a patent which the individual believes contains
Essential Claim(s) with respect to this specification should disclose
the information in accordance with <a
href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
6 of the W3C Patent Policy</a>.</p>

<hr title="Separator from Header" />
</div>

<!-- *************************** -->
<!--      TABLE OF CONTENTS      -->
<!-- *************************** -->

<div class="contents">

<h2 class="no-toc" id="toc"><a name="XKMS_2_0_Section_Marker_6" id="XKMS_2_0_Section_Marker_6" shape="rect"></a><a name="TableOfContents" id="TableOfContents" shape="rect">Table of Contents</a></h2>


<ul class="toc">
<li class="tocline"><a href="#XKMS_2_0_Section_1" shape="rect">1 Introduction</a>
<ul class="toc">
<li class="tocline"><a href="#XKMS_2_0_Section_1_1" shape="rect">1.1 Editorial and Conformance
Conventions</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_1_2" shape="rect">1.2 Definition of
Terms</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_1_3" shape="rect">1.3 Versions Namespaces and
Identifiers</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_1_4" shape="rect">1.4 Key Information Service
Overview</a> <strong>(Non-Normative)</strong></li>
<li class="tocline"><a href="#XKMS_2_0_Section_1_5" shape="rect">1.5 Key Registration Service
Overview</a> <strong>(Non-Normative)</strong></li>
<li class="tocline"><a href="#XKMS_2_0_Section_1_6" shape="rect">1.6 Structure of this
document</a></li>
</ul></li>

<li class="tocline"><a href="#XKMS_2_0_Section_2" shape="rect">2 Protocol Exchanges</a>
<ul class="toc">
<li class="tocline"><a href="#XKMS_2_0_Section_2_1" shape="rect">2.1 All Messages</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_2_2" shape="rect">2.2 Request Types</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_2_3" shape="rect">2.3 Responses</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_2_4" shape="rect">2.4 Synchronous and
Asynchronous Processing</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_2_5" shape="rect">2.5 Asynchronous
Processing</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_2_6" shape="rect">2.6 Two-Phase Request
Protocol</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_2_7" shape="rect">2.7 Two-Phase Protocol with
Asynchronous Processing</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_2_8" shape="rect">2.8 Compound Requests and
Responses</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_2_9" shape="rect">2.9 Security Binding</a></li>
</ul></li>

<li class="tocline"><a href="#XKMS_2_0_Section_3" shape="rect">3 Message Syntax</a>
<ul class="toc">
<li class="tocline"><a href="#XKMS_2_0_Section_3_1" shape="rect">3.1 Message Base</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_3_2" shape="rect">3.2 Request Message</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_3_3" shape="rect">3.3 Response Message</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_3_4" shape="rect">3.4 Compound Requests</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_3_5" shape="rect">3.5 Status Request</a></li>
</ul></li>

<li class="tocline"><a href="#XKMS_2_0_Section_4" shape="rect">4 Key Information Service
Description</a>
<ul class="toc">
<li class="tocline"><a href="#XKMS_2_0_Section_4_1" shape="rect">4.1 Locate
Service</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_4_2" shape="rect">4.2 Validate
Service</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_4_3" shape="rect">4.3 Using Locate and
Validate</a></li>
</ul></li>

<li class="tocline"><a href="#XKMS_2_0_Section_5" shape="rect">5 Key Information Service
Message Set</a>
<ul class="toc">
<li class="tocline"><a href="#XKMS_2_0_Section_5_1" shape="rect">5.1 Key Binding
Specification</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_5_2" shape="rect">5.2 Locate Service</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_5_3" shape="rect">5.3 Validate Service</a></li>
</ul></li>

<li class="tocline"><a href="#XKMS_2_0_Section_6" shape="rect">6 Key Registration Service
Description</a>
<ul class="toc">
<li class="tocline"><a href="#XKMS_2_0_Section_6_1" shape="rect">6.1 Registration</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_6_2" shape="rect">6.2 Reissue</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_6_3" shape="rect">6.3 Revocation</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_6_4" shape="rect">6.4 Key Recovery</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_6_5" shape="rect">6.5 Request
Authentication</a></li>
</ul></li>

<li class="tocline"><a href="#XKMS_2_0_Section_7" shape="rect">7 Key Registration Service
Message Set</a>
<ul class="toc">
<li class="tocline"><a href="#XKMS_2_0_Section_7_1" shape="rect">7.1 Common Elements</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_7_2" shape="rect">7.2 Register</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_7_3" shape="rect">7.3 Reissue</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_7_4" shape="rect">7.4 Revoke</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_7_5" shape="rect">7.5 Recover</a></li>
</ul></li>

<li class="tocline"><a href="#XKMS_2_0_Section_8" shape="rect">8 Cryptographic Algorithm
Specific Parameters</a>
<ul class="toc">
<li class="tocline"><a href="#XKMS_2_0_Section_8_1" shape="rect">8.1 Use of Limited-Use Shared
Secret Data</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_8_2" shape="rect">8.2 Private Key
Parameters</a></li>
</ul></li>

<li class="tocline"><a href="#XKMS_2_0_Section_9" shape="rect">9 Conformance</a></li>

<li class="tocline"><a href="#XKMS_2_0_Section_10" shape="rect">10 Security
Considerations</a>
<ul class="toc">
<li class="tocline"><a href="#XKMS_2_0_Section_10_1" shape="rect">10.1 Replay Attacks</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_10_2" shape="rect">10.2 Denial of
Service</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_10_3" shape="rect">10.3 Recovery Policy</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_10_4" shape="rect">10.4 Security of Limited Use
Shared Secret</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_10_5" shape="rect">10.5 Confidentiality of
Opaque Client Data</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_10_6" shape="rect">10.6 Security of Not Bound
Authentication Data</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_10_7" shape="rect">10.7 Signature Oracle</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_10_8" shape="rect">10.8 Privacy</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_10_9" shape="rect">10.9 Security of the Private
Key</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_10_10" shape="rect">10.10 Message Length
Disclosure Vulnerabilities</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_10_11" shape="rect">10.11 Check for
Signature Value in a Signed SOAP Message</a></li>
</ul></li>

<li class="tocline"><a href="#XKMS_2_0_Section_Appendix_A" shape="rect">Appendix A
Schemas</a><ul class="toc">
<li class="tocline"><a href="#XKMS_2_0_Section_A_1" shape="rect">A.1 XKMS Schema</a></li>
</ul></li>

<li class="tocline"><a href="#XKMS_2_0_Section_Appendix_B" shape="rect">Appendix B Service
Location Configuration</a> (Non-Normative)
<ul class="toc">
<li class="tocline"><a href="#XKMS_2_0_Section_B_1" shape="rect">B.1 Domain Name Service
(DNS)</a></li>
</ul></li>

<li class="tocline"><a href="#XKMS_2_0_Section_Appendix_C" shape="rect">Appendix C Sample
Protocol Exchanges</a> (Non-Normative)
<ul class="toc">
<li class="tocline"><a href="#XKMS_2_0_Section_C_1" shape="rect">C.1 Authentication
Computation</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_C_2" shape="rect">C.2 Pass Phrase
Computation</a></li>
<li class="tocline"><a href="#XKMS_2_0_Section_C_3" shape="rect">C.3 Private Key
Parameters</a></li>
</ul></li>

<li class="tocline"><a href="#XKMS_2_0_Section_Appendix_D" shape="rect">Appendix D
References</a> (Non-Normative)</li>

<li class="tocline"><a href="#XKMS_2_0_Section_Appendix_E" shape="rect">Appendix E 
Acknowledgments</a> (Non-Normative)</li>

<li class="tocline"><a href="#XKMS_2_0_Section_Appendix_F" shape="rect">Appendix F
Changes</a> (Non-Normative)</li>
</ul>
</div>

<!-- <h2 class="TableOfFigures">Table of Figures</h2>
		<p class="Comment">To be generated</p> -->

<h1><a name="XKMS_2_0_Section_1" id="XKMS_2_0_Section_1" shape="rect">1</a> <a name="Introduction" id="Introduction" shape="rect">Introduction</a></h1>

<p><a name="XKMS_2_0_Paragraph_8" id="XKMS_2_0_Paragraph_8" class="markParagraph" shape="rect">[8]</a>This document specifies protocols for
distributing and registering public keys, suitable for use in conjunction
with the standard for XML Signatures <a href="#XML-SIG" shape="rect">[XML-SIG]</a> defined
by the World Wide Web Consortium (W3C) and the Internet Engineering Task
Force (IETF) and companion standard for XML encryption <a href="#XML-Enc" shape="rect">[XML-ENC]</a>.&#xA0; The XML Key Management Specification
(XKMS) comprises two parts -- the XML Key Information Service Specification
(X-KISS) and the XML Key Registration Service Specification (X-KRSS).</p>

<p><a name="XKMS_2_0_Paragraph_9" id="XKMS_2_0_Paragraph_9" class="markParagraph" shape="rect">[9]</a>These protocols do not require any particular
underlying public key infrastructure (such as X.509) but are designed to be
compatible with such infrastructures.</p>

<p><a name="XKMS_2_0_Paragraph_10" id="XKMS_2_0_Paragraph_10" class="markParagraph" shape="rect">[10]</a>This document defines the following service
specifications:</p>
<dl>
  <dt><a href="#KISSOverview" shape="rect">XML Key Information Service
  Specification</a>:&#xA0;</dt>
    <dd>A protocol to support the delegation by an application to a service
      of the processing of key information associated with an XML signature,
      XML encryption, or other usage of the XML Signature <a href="#XML-SIG" shape="rect">[XML-SIG]</a> <span class="ID">&lt;ds:KeyInfo&gt;</span>
      element.&#xA0;</dd>
  <dt><a href="#KRSSOverview" shape="rect">XML Key Registration Service
  Specification</a>:&#xA0;</dt>
    <dd>A protocol to support the registration of a key pair by a key pair
      holder, with the intent that the key pair subsequently be usable in
      conjunction with the XML Key Information Service Specification or a
      Public Key Infrastructure (PKI) such as <a href="#x509" shape="rect">[X.509]</a><a href="#pkix" shape="rect">[PKIX]</a>.</dd>
</dl>

<h2><a name="XKMS_2_0_Section_1_1" id="XKMS_2_0_Section_1_1" shape="rect">1.1</a> <a id="sec-Editorial" name="sec-Editorial" shape="rect">Editorial</a> and Conformance
Conventions</h2>

<p><a name="XKMS_2_0_Paragraph_11" id="XKMS_2_0_Paragraph_11" class="markParagraph" shape="rect">[11]</a>This specification uses XML Schemas [<a href="#XML-Schema1" shape="rect">XML-schema</a>] to describe the content model.</p>

<p><a name="XKMS_2_0_Paragraph_12" id="XKMS_2_0_Paragraph_12" class="markParagraph" shape="rect">[12]</a>The key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this specification are to be interpreted as described in [<a href="#ref-KEYWORDS" shape="rect">RFC2119</a>]:</p>

<blockquote>
  <p><a name="XKMS_2_0_Paragraph_13" id="XKMS_2_0_Paragraph_13" class="markParagraph" shape="rect">[13]</a>"they MUST only be used where it is actually
  required for interoperation or to limit behavior which has potential for
  causing harm (e.g., limiting retransmissions)"</p>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_14" id="XKMS_2_0_Paragraph_14" class="markParagraph" shape="rect">[14]</a>Consequently, we use these capitalized keywords
to unambiguously specify requirements over protocol and application features
and behavior that affect the interoperability and security of
implementations. These key words are not used (capitalized) to describe XML
grammar; schema definitions unambiguously describe such requirements and we
wish to reserve the prominence of these terms for the natural language
descriptions of protocols and features. For instance, an XML attribute might
be described as being "optional." Compliance with the XML-namespace
specification [<a href="#ref-XML-NS" shape="rect">XML-NS</a>] is described as
"REQUIRED."</p>

<h2><a name="XKMS_2_0_Section_1_2" id="XKMS_2_0_Section_1_2" shape="rect">1.2</a> <a name="DefinitionofTerms" id="DefinitionofTerms" shape="rect">Definition of Terms</a></h2>

<p><a name="XKMS_2_0_Paragraph_17" id="XKMS_2_0_Paragraph_17" class="markParagraph" shape="rect">[17]</a>The following terms are used within this
document with the particular meaning indicated below:</p>

<blockquote>
  <p class="Ref"><a name="XKMS_2_0_Paragraph_18" id="XKMS_2_0_Paragraph_18" class="markParagraph" shape="rect">[18]</a> <b>Service<br clear="none" />
  &#xA0;&#xA0;&#xA0;</b> An application that provides computational or
  informational resources on request. A service may be provided by several
  physical servers operating as a unit.</p>

  <p class="Ref"><a name="XKMS_2_0_Paragraph_20" id="XKMS_2_0_Paragraph_20" class="markParagraph" shape="rect">[20]</a> <b>Client<br clear="none" />
  &#xA0;&#xA0;&#xA0;</b> An application that makes requests of a
  service.&#xA0; The concept of 'client' is relative to a service request; an
  application may have the role of client for some requests and service for
  others.</p>

  <p class="Ref"><a name="XKMS_2_0_Paragraph_20a" id="XKMS_2_0_Paragraph_20a" class="markParagraph" shape="rect">[20a]</a> <b>Payload Security<br clear="none" />
  &#xA0;&#xA0;&#xA0;</b>  Use of end-to-end security mechanisms, such as XML DSIG, not dependent 
  on the transport mechanism (HTTP, TLS, SOAP, ...).</p>
</blockquote>

<h2><a name="XKMS_2_0_Section_1_3" id="XKMS_2_0_Section_1_3" shape="rect">1.3</a> <a name="Namespaces" id="Namespaces" shape="rect">Versions Namespaces and Identifiers</a></h2>

<p><a name="XKMS_2_0_Paragraph_21" id="XKMS_2_0_Paragraph_21" class="markParagraph" shape="rect">[21]</a>No provision is made for an explicit version
number in this syntax. If a future version is needed, it will use a different
namespace. The XML namespace [<a href="#ref-XML-NS" shape="rect">XML-ns</a>] URI that MUST
be used by implementations of this (dated) specification is:</p>
<pre class="xml-example" xml:space="preserve">   http://www.w3.org/2002/03/xkms#</pre>

<p><a name="XKMS_2_0_Paragraph_22" id="XKMS_2_0_Paragraph_22" class="markParagraph" shape="rect">[22]</a>This namespace is also used as the prefix for
algorithm identifiers used by this specification. While applications MUST
support XML and XML namespaces, the use of internal entities [<a href="#ref-XML" shape="rect">XML</a>] or the "xkms" XML namespace prefix and
defaulting/scoping conventions are OPTIONAL; we use these facilities to
provide compact and readable examples.</p>

<p><a name="XKMS_2_0_Paragraph_23" id="XKMS_2_0_Paragraph_23" class="markParagraph" shape="rect">[23]</a>In this document, certain namespace prefixes
represent certain namespaces in the schema fragments (shown on a yellow
background) as follows:</p>

<div class="center">

<table border="1" cellspacing="0" cellpadding="3">
  <tbody>
    <tr>
      <td>Prefix&#xA0;</td>
      <td>Specification&#xA0;&#xA0;&#xA0;&#xA0;&#xA0;</td>
      <td>Schema</td>
    </tr>
    <tr>
      <td align="left">xsi</td>
      <td align="left">XML Schema</td>
      <td class="ID" align="left">http://www.w3.org/2001/XMLSchema</td>
    </tr>
    <tr>
      <td class="ID" align="left">ds</td>
      <td align="left">XML Signature</td>
      <td class="ID" align="left">http://www.w3.org/2000/09/xmldsig#</td>
    </tr>
    <tr>
      <td class="ID" align="left">xenc</td>
      <td align="left">XML Encryption</td>
      <td class="ID" align="left">http://www.w3.org/2001/04/xmlenc#</td>
    </tr>
    <tr>
      <td class="ID" align="left">ec</td>
      <td align="left">Exclusive Canonicalization</td>
      <td class="ID" align="left">http://www.w3.org/2001/10/xml-exc-c14n#</td>
    </tr>
    <tr>
      <td class="ID" align="left">xkms</td>
      <td align="left">XKMS</td>
      <td class="ID" align="left">http://www.w3.org/2002/03/xkms#</td>
    </tr>
  </tbody>
</table>
</div>

<p><a name="XKMS_2_0_Paragraph_24" id="XKMS_2_0_Paragraph_24" class="markParagraph" shape="rect">[24]</a>For clarity, some examples of XML are not
complete documents and namespace declarations may be omitted from XML
fragments.</p>

<p><a name="XKMS_2_0_Paragraph_25" id="XKMS_2_0_Paragraph_25" class="markParagraph" shape="rect">[25]</a>In all examples (shown on a light blue
background) and in the body of the text the default namespace refers to the
xkms namespace itself. This means that namespace prefixes are omitted for all
element and type names in the <span class="ID">xkms</span>
namespace.</p>

<p><a name="XKMS_2_0_Paragraph_26" id="XKMS_2_0_Paragraph_26" class="markParagraph" shape="rect">[26]</a>These namespaces are declared in the XKMS
schema as follows:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">&lt;?xml version="1.0"?&gt;
&lt;schema targetNamespace="http://www.w3.org/2002/03/xkms#"
      xmlns:xkms="http://www.w3.org/2002/03/xkms#"
      xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
      xmlns="http://www.w3.org/2001/XMLSchema"
      elementFormDefault="qualified" attributeFormDefault="unqualified"&gt;
   &lt;import namespace="http://www.w3.org/2000/09/xmldsig#"
         schemaLocation="xmldsig-core-schema.xsd"/&gt;
   &lt;import namespace="http://www.w3.org/2001/04/xmlenc#"
         schemaLocation="xenc-schema.xsd"/&gt;
   &lt;annotation&gt;
      &lt;documentation xml:lang="en"&gt;
         XML Schema for XKMS 2.0 Proposed Recommendation Candidate 2005
      &lt;/documentation&gt;
   &lt;/annotation&gt;
   &lt;!-- /Namespace --&gt;</pre>
<pre class="Code" xml:space="preserve">   ...</pre>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- End Schema --&gt;
&lt;/schema&gt;</pre>

<p><a name="XKMS_2_0_Paragraph_27" id="XKMS_2_0_Paragraph_27" class="markParagraph" shape="rect">[27]</a>Internet Protocol addresses and Domain Name
System names used in examples are purposely chosen to avoid confusion with
assigned addresses and names. All Internet Protocol Addresses are in the
reserved non-routable network 10.x.x.x. All DNS names are in the reserved
domain <span class="ID">example.com</span>.</p>

<h2><a name="XKMS_2_0_Section_1_4" id="XKMS_2_0_Section_1_4" shape="rect">1.4</a> <a name="KISSOverview" id="KISSOverview" shape="rect">Key Information Service Overview</a>
(Non-Normative)</h2>

<p><a name="XKMS_2_0_Paragraph_28" id="XKMS_2_0_Paragraph_28" class="markParagraph" shape="rect">[28]</a>X-KISS allows a client to delegate part or all
of the tasks required to process XML Signature <a href="#XML-SIG" shape="rect">[XML-SIG]</a> <span class="ID">&lt;ds:KeyInfo&gt;</span> elements to an XKMS service.
A key objective of the protocol design is to minimize the complexity of
applications using XML Signature <a href="#XML-SIG" shape="rect">[XML-SIG]</a>. By
becoming a client of the XKMS service, the application is relieved of the
complexity and syntax of the underlying PKI used to establish trust
relationships, which may be based upon a different specification such as
X.509/PKIX, SPKI or PGP.</p>

<p><a name="XKMS_2_0_Paragraph_29" id="XKMS_2_0_Paragraph_29" class="markParagraph" shape="rect">[29]</a>By design, the XML Signature specification <a href="#XML-SIG" shape="rect">[XML-SIG]</a> does not mandate use of a particular trust
policy. The signer of a document is not required to include any key
information but may include a <span class="ID">&lt;ds:KeyInfo&gt;</span>
element that specifies the key itself, a key name, X.509 certificate, a PGP
key identifier etc. Alternatively, a link may be provided to a location where
the full <span class="ID">&lt;ds:KeyInfo&gt;</span> information may be
found.</p>

<p><a name="XKMS_2_0_Paragraph_30" id="XKMS_2_0_Paragraph_30" class="markParagraph" shape="rect">[30]</a>The information provided by the signer may
therefore be insufficient by itself to perform cryptographic verification and
decide whether to trust the signing key, or the information may not be in a
format the client can use. For example:</p>
<ul type="disc">
  <li>The key may be specified by a name only.</li>
  <li>The local trust policy of the client may require additional information
    in order to trust the key.</li>
  <li>The key may be encoded in an X.509 certificate that the client cannot
    parse.</li>
</ul>

<p><a name="XKMS_2_0_Paragraph_31" id="XKMS_2_0_Paragraph_31" class="markParagraph" shape="rect">[31]</a>In the case of an encryption operation:</p>
<ul type="disc">
  <li>The client may not know the public key of the recipient.</li>
</ul>

<h2><a name="XKMS_2_0_Section_1_5" id="XKMS_2_0_Section_1_5" shape="rect">1.5</a> <a name="KRSSOverview" id="KRSSOverview" shape="rect">Key Registration Service Overview</a>
(Non-Normative)</h2>

<p><a name="XKMS_2_0_Paragraph_32" id="XKMS_2_0_Paragraph_32" class="markParagraph" shape="rect">[32]</a>X-KRSS describes a protocol for registration
and subsequent management of public key information. A client of a conforming
service may request that the registration service bind information to a
public key. The information bound may include a name, an identifier or
extended attributes defined by the implementation.</p>

<p><a name="XKMS_2_0_Paragraph_33" id="XKMS_2_0_Paragraph_33" class="markParagraph" shape="rect">[33]</a>The key pair to which the information is bound
may be generated in advance by the client or on request generated by the
service. The Registration protocol may also be used for subsequent management
operations including recovery of the private key and reissue or revocation of
the key binding.</p>

<p><a name="XKMS_2_0_Paragraph_34" id="XKMS_2_0_Paragraph_34" class="markParagraph" shape="rect">[34]</a>The protocol provides for authentication of the
applicant and, in the case that the key pair is generated by the client,
Proof of Possession (POP) of the private key. A means of communicating the
private key to the client is provided in the case that the private key is
generated by the registration service.</p>

<p><a name="XKMS_2_0_Paragraph_35" id="XKMS_2_0_Paragraph_35" class="markParagraph" shape="rect">[35]</a>This document specifies means of registering
RSA and DSA keys and a framework for extending the protocol to support other
cryptographic algorithms such as Diffie-Hellman and Elliptic Curve
variants.</p>

<h2><a name="XKMS_2_0_Section_1_6" id="XKMS_2_0_Section_1_6" shape="rect">1.6</a> <a name="Structure" id="Structure" shape="rect">Structure</a> of this document</h2>

<p><a name="XKMS_2_0_Paragraph_36" id="XKMS_2_0_Paragraph_36" class="markParagraph" shape="rect">[36]</a>The remainder of this document describes the
XML Key Information Service Specification and XML Key Registration Service
Specification.</p>
<dl>
  <dt><b>Section 2</b>: Protocol Exchanges</dt>
    <dd>Features of the XKMS protocol that are common to the XKMS services
      are described.</dd>
  <dt><b>Section 3</b>: Message Syntax</dt>
    <dd>The common syntax elements shared by XKMS messages are described.</dd>
  <dt>Section 4: Key Information Service Specification Overview.</dt>
    <dd>The functional behavior of the X-KISS service is described.</dd>
  <dt><b>Section 5</b>: Key Information Service Specification Message
  Set.</dt>
    <dd>The semantics of the X-KISS protocol messages are defined.</dd>
  <dt><b>Section 6</b>: Key Registration Service Specification Overview.</dt>
    <dd>The functional behavior of the X-KRSS service is described.</dd>
  <dt><b>Section 7</b>: Key Registration Service Specification Message
  Set.</dt>
    <dd>The semantics of the X-KRSS protocol messages is defined.</dd>
  <dt><b>Section 8</b>: Cryptographic Algorithm Specific Parameters</dt>
    <dd>Parameters and data formats specific to the use of particular
      cryptographic algorithms are defined.</dd>
  <dt><b>Section 9</b>: Conformance</dt>
    <dd>Conformance criteria for compliant XKMS 2.0 applications are
      specified.</dd>
  <dt>Section 10: Security Considerations</dt>
    <dd>Security considerations for implementation and deployment of XKMS are
      described.</dd>
</dl>

<h1><a name="XKMS_2_0_Section_2" id="XKMS_2_0_Section_2" shape="rect">2</a> <a name="MessageFormat" id="MessageFormat" shape="rect">Protocol Exchanges</a></h1>

<p><a name="XKMS_2_0_Paragraph_37" id="XKMS_2_0_Paragraph_37" class="markParagraph" shape="rect">[37]</a>XKMS protocol exchanges consist of a sequence
of either one or two request response pairs.</p>

<p><a name="XKMS_2_0_Paragraph_38" id="XKMS_2_0_Paragraph_38" class="markParagraph" shape="rect">[38]</a>XKMS protocol messages share a common format
that may be carried within a variety of protocols.&#xA0; A binding to the
SOAP&#xA0;<a href="#SOAP" shape="rect">[SOAP]</a><a href="#XMLP" shape="rect">[XMLP]</a> message
protocol is provided in <a href="/TR/2005/REC-xkms2-bindings-20050628/" shape="rect">Part II:
Protocol Bindings</a>. It is recommended XKMS implementers support SOAP over
HTTP for interoperability purposes. XKMS is transport protocol agnostic
however and MAY be layered over any SOAP transport.</p>

<p><a name="XKMS_2_0_Paragraph_39" id="XKMS_2_0_Paragraph_39" class="markParagraph" shape="rect">[39]</a>Implementers MAY implement bindings to other
protocols at their option.</p>

<p><a name="XKMS_2_0_Paragraph_40" id="XKMS_2_0_Paragraph_40" class="markParagraph" shape="rect">[40]</a>No XKMS operations are idempotent, that is all
XKMS requests MAY cause a change of state.</p>

<p><a name="XKMS_2_0_Paragraph_41" id="XKMS_2_0_Paragraph_41" class="markParagraph" shape="rect">[41]</a> <a href="/TR/2005/REC-xkms2-bindings-20050628/" shape="rect">Part II of this specification</a>
describes the XKMS Security Protocol bindings.</p>

<p><a name="XKMS_2_0_Paragraph_42" id="XKMS_2_0_Paragraph_42" class="markParagraph" shape="rect">[42]</a>The XKMS protocol consists of pairs of requests
and responses. The XKMS protocol binding allows for the case in which an
additional request/response round trip is required to support cases such as
pending responses and two-phase requests for replay attack protection.</p>

<p><a name="XKMS_2_0_Paragraph_43" id="XKMS_2_0_Paragraph_43" class="markParagraph" shape="rect">[43]</a>Each XKMS response message contains a <span class="ID">MajorResult</span> code that
determines whether the response is final or further processing is required.
The protocol is specified in the CSP formalism <a href="#CSP" shape="rect">[CSP]</a> as
follows:</p>

<blockquote>
  <dl>
    <dt><i>Final</i> = { <i>Success</i>, <i>VersionMismatch</i>,
    <i>Sender</i>, <i>Receiver</i> }</dt>
      <dd>&#xA0;</dd>
    <dt><i>Request</i> <span class="ID">-&gt;</span>
    <i>Result</i>.<i>Final</i></dt>
      <dd>|</dd>
    <dt><i>Request</i> <span class="ID">-&gt;</span>
    <i>Result</i>.<i>Pending</i><span class="ID">-&gt;</span><i>PendingNotification</i><span class="ID">-&gt;</span><i>Request</i><span class="ID">-&gt;</span><i>Result</i>.<i>Final</i></dt>
      <dd>|</dd>
    <dt><i>Request</i> <span class="ID">-&gt;</span>
    <i>Result</i>.<i>Represent</i><span class="ID">-&gt;</span><i>Request</i><span class="ID">-&gt;</span><i>Result</i>.<i>Final</i></dt>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_44" id="XKMS_2_0_Paragraph_44" class="markParagraph" shape="rect">[44]</a>The following sections describe the message
protocol and the message processing steps taken by both parties in each of
the messages.</p>

<h2><a name="XKMS_2_0_Section_2_1" id="XKMS_2_0_Section_2_1" shape="rect">2.1</a> <a name="AllMessages" id="AllMessages" shape="rect">All Messages</a></h2>

<p><a name="XKMS_2_0_Paragraph_45" id="XKMS_2_0_Paragraph_45" class="markParagraph" shape="rect">[45]</a>The following processing steps are taken with
respect to all messages regardless of whether they are a request or a
response:</p>
<dl>
  <dt>Generation</dt>
    <dd><span class="ID">Id</span> is set to a randomly generated unique
    value</dd>
    <dd><span class="ID">Service</span> is set to the value of the URI to
      which the XKMS request is directed<br clear="none" />
      Authentication Signature is generated (if required).</dd>
  <dt>Processing</dt>
    <dd>The value of <span class="ID">Service</span> is verified<br clear="none" />
      The Authentication Signature value is verified (if required).</dd>
</dl>

<h3><a name="XKMS_2_0_Section_2_1_1" id="XKMS_2_0_Section_2_1_1" shape="rect">2.1.1</a>Example</h3>
<!-- Include file -->
<pre class="Example" xml:space="preserve">&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;MessageAbstractType Id="1noOYHt5Lx7xUuizWZLOMw=="
      Service="http://www.example.org/XKMS"
      xmlns="http://www.w3.org/2002/03/xkms#" /&gt;</pre>

<h2><a name="XKMS_2_0_Section_2_2" id="XKMS_2_0_Section_2_2" shape="rect">2.2</a> <a name="MessageRequestTypes" id="MessageRequestTypes" shape="rect">Request Types</a></h2>

<p><a name="XKMS_2_0_Paragraph_46" id="XKMS_2_0_Paragraph_46" class="markParagraph" shape="rect">[46]</a>The XKMS specification defines three types of
request:</p>
<dl>
  <dt>X-KISS Request</dt>
    <dd>A Locate or Validate request as specified by the Key Information
      Service Specification.</dd>
  <dt>X-KRSS Request</dt>
    <dd>A Register, Reissue, Revoke or Recover request as specified by the
      Key Registration Service Specification.</dd>
  <dt>Compound Request</dt>
    <dd>A compound request consists of a set of one or more X-KISS or X-KRSS
      requests.</dd>
</dl>

<p><a name="XKMS_2_0_Paragraph_47" id="XKMS_2_0_Paragraph_47" class="markParagraph" shape="rect">[47]</a>The XKMS protocol supports a number of protocol
options, including asynchronous processing, two-phase requests and compound
requests. The client specifies the protocol options it supports in relation
to a specific request through <span class="ID">ResponseMechanism</span> 
elements in the request.</p>

<p><a name="XKMS_2_0_Paragraph_48" id="XKMS_2_0_Paragraph_48" class="markParagraph" shape="rect">[48]</a>The means by which the service specifies
protocol options which it accepts is outside the scope of this document. If
the mechanism used for this purpose uses URI based identifiers for this
purpose the following identifiers SHOULD be used:</p>
<dl>
  <dt>Asynchronous Processing</dt>
    <dd>http://www.w3.org/2002/03/xkms#Asynchronous</dd>
  <dt>Two-Phase Request Protocol</dt>
    <dd>http://www.w3.org/2002/03/xkms#Represent</dd>
  <dt>Compound Requests and Responses</dt>
    <dd>http://www.w3.org/2002/03/xkms#Compound</dd>
</dl>

<h2><a name="XKMS_2_0_Section_2_3" id="XKMS_2_0_Section_2_3" shape="rect">2.3</a> <a name="Responses" id="Responses" shape="rect">Responses</a></h2>

<p><a name="XKMS_2_0_Paragraph_49" id="XKMS_2_0_Paragraph_49" class="markParagraph" shape="rect">[49]</a>All XKMS responses contain a Result code
comprised of a major and minor component. If a service applies a protocol
processing option the client is informed by means of the <span class="ID">MajorResult</span> code value of the
response.</p>

<h2><a name="XKMS_2_0_Section_2_4" id="XKMS_2_0_Section_2_4" shape="rect">2.4</a> <a name="SynchronousandAsynchronous" id="SynchronousandAsynchronous" shape="rect">Synchronous
and Asynchronous</a> Processing</h2>

<p><a name="XKMS_2_0_Paragraph_50" id="XKMS_2_0_Paragraph_50" class="markParagraph" shape="rect">[50]</a>XKMS supports two processing modes, synchronous
processing and asynchronous processing.</p>
<ul>
  <li>In synchronous processing the service responds to a request such&#xA0;
    that it has satisfied its obligation and will issue no more responses
    with respect to that request: a response code in the set <i>Final</i>
    defined above is returned.</li>
  <li>In asynchronous processing the service will not complete the request
    immediately and notifies that the request is not yet satisfied and
    subsequent responses will be forthcoming: a response code that is not in
    the set <i>Final</i> is returned in intermediate responses.</li>
</ul>

<p><a name="XKMS_2_0_Paragraph_51" id="XKMS_2_0_Paragraph_51" class="markParagraph" shape="rect">[51]</a>A client MAY advise a service that it will
accept asynchronous processing of a request by specifying the <span class="ID">ResponseMechanism</span> value <span class="ID">Pending</span>. An XKMS service that receives a request that
specifies the <span class="ID">ResponseMechanism</span> value <span class="ID">Pending</span> MAY respond either synchronously or
asynchronously. If the service is to respond asynchronously it advises the
client that the response value will be returned asynchronously by specifying
the <span class="ID">MajorResult</span> code
<span class="ID">Pending</span>.</p>

<p><a name="XKMS_2_0_Paragraph_52" id="XKMS_2_0_Paragraph_52" class="markParagraph" shape="rect">[52]</a>An XKMS service MUST NOT return the <span class="ID">MajorResult</span> code <span class="ID">Pending</span> unless the <span class="ID">ResponseMechanism</span> value <span class="ID">Pending</span> was specified in the corresponding request. If
an XKMS service receives a request that cannot be processed synchronously and
the <span class="ID">ResponseMechanism</span> value <span class="ID">Pending</span> is not specified the <span class="ID">MajorResult</span> code <span class="ID">Receiver</span> and <span class="ID">MinorResult</span> code <span class="ID">NotSynchronous</span> are returned.</p>

<p><a name="XKMS_2_0_Paragraph_53" id="XKMS_2_0_Paragraph_53" class="markParagraph" shape="rect">[53]</a>Asynchronous processing MAY be used to allow
administrator intervention during the processing of a request. For example an
administrator might be required to verify and approve all X-KRSS Registration
requests before they are processed.</p>

<h3><a name="XKMS_2_0_Section_2_4_1" id="XKMS_2_0_Section_2_4_1" shape="rect">2.4.1</a> <a name="SynchronousRequestResponse" id="SynchronousRequestResponse" shape="rect">Synchronous
Request / Response</a></h3>

<p><a name="XKMS_2_0_Paragraph_54" id="XKMS_2_0_Paragraph_54" class="markParagraph" shape="rect">[54]</a>Processing of a synchronous Request and
Response takes place as follows:</p>
<dl>
  <dt>Requestor generation of the Request Message</dt>
    <dd><span class="ID">Nonce</span> and <span class="ID">OriginalRequestId</span>&#xA0; are not present<br clear="none" /> 
      <span class="ID">ResponseMechanism</span> value <span class="ID">Pending</span> MAY be specified but the service will ignore it</dd>
  <dt>Service processing of the Request Message</dt>
    <dd><i>Verify that request meets service authorization policy<br clear="none" />
      Process request to completion</i></dd>
  <dt>Service generation of the Response Message</dt>
    <dd><span class="ID">RequestId</span> is set to the value of <span class="ID">Id</span> in the request message</dd>
    <dd><span class="ID">Nonce</span> is not present<br clear="none" />
      <span class="ID">MajorResult</span> is set to a Final result value</dd>
  <dt>Requestor processing of the Response Message</dt>
    <dd><i>The value of <span class="ID">RequestId</span> is verified</i></dd>
</dl>

<h3><a name="XKMS_2_0_Section_2_4_2" id="XKMS_2_0_Section_2_4_2" shape="rect">2.4.2</a>
Example</h3>

<h4><a name="XKMS_2_0_Section_2_4_2_1" id="XKMS_2_0_Section_2_4_2_1" shape="rect">2.4.2.1</a> Request</h4>
<!-- Include file -->
<pre class="Example" xml:space="preserve">&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;LocateRequest Id="I6d995b8d05a9a2ce0573d29e32ab9441"
      Service="http://www.example.org/XKMS"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;QueryKeyBinding /&gt;
&lt;/LocateRequest&gt;</pre>

<h4><a name="XKMS_2_0_Section_2_4_2_2" id="XKMS_2_0_Section_2_4_2_2" shape="rect">2.4.2.2</a> Response</h4>
<!-- Include file -->
<pre class="Example" xml:space="preserve">&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;LocateResult Id="I089b18dc1a520b26e2e6689dd3a5a820"
      Service=
      "http://www.example.org/XKMS"
      ResultMajor="http://www.w3.org/2002/03/xkms#Success"
      RequestId="I6d995b8d05a9a2ce0573d29e32ab9441"
      xmlns="http://www.w3.org/2002/03/xkms#" /&gt;</pre>

<h2><a name="XKMS_2_0_Section_2_5" id="XKMS_2_0_Section_2_5" shape="rect">2.5</a> <a name="AsynchronousProcessing" id="AsynchronousProcessing" shape="rect">Asynchronous
Processing</a></h2>

<p><a name="XKMS_2_0_Paragraph_55" id="XKMS_2_0_Paragraph_55" class="markParagraph" shape="rect">[55]</a>Asynchronous processing consists of a sequence of request/response
pairs; an initial request which specifies the request values, zero or
more status requests and a pending request which obtains the result of
the operation.  The client may issue status requests in order to poll
the status of an asynchronous operation independently of the use of
the notification mechanism indicated (by the client) in the initial
request.</p>

<h3><a name="XKMS_2_0_Section_2_5_1" id="XKMS_2_0_Section_2_5_1" shape="rect">2.5.1</a> Initial Request</h3>

<p><a name="XKMS_2_0_Paragraph_56" id="XKMS_2_0_Paragraph_56" class="markParagraph" shape="rect">[56]</a>The initial request message is processed as
follows:</p>
<dl>
  <dt>Requestor generation of the Initial Request Message</dt>
    <dd><span class="ID">Nonce</span> and <span class="ID">OriginalRequestId</span>&#xA0; are not present<br clear="none" />
      <span class="ID">ResponseMechanism</span> value <span class="ID">Pending</span> MUST be specified</dd>
  <dt>Service processing of the Initial Request Message</dt>
    <dd><i>Schedule request for asynchronous processing</i></dd>
  <dt>Service generation of the Initial Response Message</dt>
    <dd><span class="ID">RequestId</span> is set to the value <span class="ID">Id</span> in the initial request message</dd>
    <dd><span class="ID">Nonce</span> is not present</dd>
    <dd><span class="ID">MajorResult</span> is set to <span class="ID">Pending</span></dd>
  <dt>Requestor processing of the Initial Response Message</dt>
    <dd><i>Register request as pending completion, poll processing status and/or wait for
    notification</i></dd>
</dl>

<h3><a name="XKMS_2_0_Section_2_5_2" id="XKMS_2_0_Section_2_5_2" shape="rect">2.5.2</a> Status Request</h3>

<p><a name="XKMS_2_0_Paragraph_56a" id="XKMS_2_0_Paragraph_56a" class="markParagraph" shape="rect">[56a]</a>The client may poll the status of the asynchronous operation as follows:</p>

<dl>
  <dt>Requestor generation of the Status Request Message</dt>
    <dd>The request element is <span class="ID">StatusRequest</span></dd>
    <dd><span class="ID">OriginalRequestId</span> is set to the value of
      <span class="ID">Id</span> in the initial request message<br clear="none" />
      <span class="ID">ResponseId</span> is set to value of <span class="ID">Id</span> in the initial response message</dd>
  <dt>Service processing of the Status Request Message</dt>
    <dd><em>Identify pending request using <span class="ID">OriginalRequestId</span>
       and <span class="ID">ResponseId</span>.</em></dd>
  <dt>Service generation of the Status Response Message</dt>
    <dd><span class="ID">RequestId</span> is set to the value of <span class="ID">Id</span> in the Status request message</dd>
    <dd><span class="ID">Nonce</span> is not present</dd>
  <dt>Requestor processing of the Status Response Message</dt>
    <dd><em>For non-compound messages, the <span class="ID">ResultMajor</span>
     attribute indicates the status of the operation.  For compound
     messages, the <span class="ID">Success</span>, <span class="ID">Failure</span>,
     and <span class="ID">Pending</span> attributes further indicate the number of 
     inner requests that have the respective status.</em></dd>
</dl>

<h3><a name="XKMS_2_0_Section_2_5_3" id="XKMS_2_0_Section_2_5_3" shape="rect">2.5.3</a> Pending Request</h3>

<p><a name="XKMS_2_0_Paragraph_57" id="XKMS_2_0_Paragraph_57" class="markParagraph" shape="rect">[57]</a> The client determines, through notification or polling, that the
requested operation has completed and requests the return of the
result values by issuing a <span class="ID">PendingRequest</span> message as follows:</p>

<dl>
  <dt>Requestor generation of the Pending Request Message</dt>
    <dd>The request element is <span class="ID">PendingRequest</span></dd>
    <dd><span class="ID">OriginalRequestId</span> is set to the value of
      <span class="ID">Id</span> in the initial request message<br clear="none" />
      <span class="ID">ResponseId</span> is set to value of <span class="ID">Id</span> in the initial response message</dd>
  <dt>Service processing of the Pending Request Message</dt>
    <dd><em>Match pending request to pending response</em></dd>
  <dt>Service generation of the Pending Response Message</dt>
    <dd><span class="ID">RequestId</span> is set to the value of <span class="ID">Id</span> in the Pending request message</dd>
    <dd><span class="ID">Nonce</span> is not present</dd>
  <dt>Requestor processing of the Pending Response Message</dt>
    <dd><em>If <span class="ID">MajorResult</span>&#xA0; is set to a non-final
      value consider it to be <span class="ID">failure</span></em></dd>
</dl>

<p><a name="XKMS_2_0_Paragraph_58" id="XKMS_2_0_Paragraph_58" class="markParagraph" shape="rect">[58]</a>The client MAY request the return of the result
values before processing has been completed. In this case the service
responds to the Pending Request with the <span class="ID">MajorResult</span>
code <span class="ID">Pending</span>.</p>

<h3><a name="XKMS_2_0_Section_2_5_4" id="XKMS_2_0_Section_2_5_4" shape="rect">2.5.4</a> Example</h3>

<h4><a name="XKMS_2_0_Section_2_5_4_1" id="XKMS_2_0_Section_2_5_4_1" shape="rect">2.5.4.1</a> Request</h4>
<!-- Include file -->
<pre class="Example" xml:space="preserve">&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;LocateRequest Id="I6227979ae4073f2b3b145db7a488ce16"
      Service="http://www.example.org/XKMS"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;ResponseMechanism&gt;http://www.w3.org/2002/03/xkms#Pending&lt;/ResponseMechanism&gt;
  &lt;PendingNotification Mechanism="urn:ietf:rfc:822" 
      Identifier="mailto:alice@example.org"&gt;
  &lt;QueryKeyBinding /&gt;
&lt;/LocateRequest&gt;</pre>

<h4><a name="XKMS_2_0_Section_2_5_4_2" id="XKMS_2_0_Section_2_5_4_2" shape="rect">2.5.4.2</a> Response</h4>
<!-- Include file -->
<pre class="Example" xml:space="preserve">&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;LocateResult Id="I98366e407a2a78dff79687dbdb4d974c"
      Service="http://www.example.org/XKMS" 
      ResultMajor="http://www.w3.org/2002/03/xkms#Pending"
      RequestId="I6227979ae4073f2b3b145db7a488ce16"
      xmlns="http://www.w3.org/2002/03/xkms#" /&gt;</pre>

<h4><a name="XKMS_2_0_Section_2_5_4_3" id="XKMS_2_0_Section_2_5_4_3" shape="rect">2.5.4.3</a> Notification</h4>

<p><em>The XKMS service notifies the client about the completion of the
 request processing using the notification mechanism specified in the
 <span class="ID">&lt;PendingNotification&gt;</span> element.</em></p>

<h4><a name="XKMS_2_0_Section_2_5_4_4" id="XKMS_2_0_Section_2_5_4_4" shape="rect">2.5.4.4</a> Pending Request</h4>
<!-- Include file -->
<pre class="Example" xml:space="preserve">&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;PendingRequest Id="I6045ff8b2eb204edb538be1fa22e340a"
      Service="http://www.example.org/XKMS"
      OriginalRequestId="I6227979ae4073f2b3b145db7a488ce16"
      ResponseId="I98366e407a2a78dff79687dbdb4d974c"
      xmlns="http://www.w3.org/2002/03/xkms#" /&gt;</pre>

<h4><a name="XKMS_2_0_Section_2_5_4_5" id="XKMS_2_0_Section_2_5_4_5" shape="rect">2.5.4.5</a> Response</h4>
<!-- Include file -->
<pre class="Example" xml:space="preserve">&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;LocateResult Id="I4da52fc78e0391a11257d64926cd184c"
      Service="http://www.example.org/XKMS"
      ResultMajor="http://www.w3.org/2002/03/xkms#Success"
      RequestId="I6045ff8b2eb204edb538be1fa22e340a"
      xmlns="http://www.w3.org/2002/03/xkms#" /&gt;</pre>

<h2><a name="XKMS_2_0_Section_2_6" id="XKMS_2_0_Section_2_6" shape="rect">2.6</a> <a name="TwoPhaseRequest" id="TwoPhaseRequest" shape="rect">Two-Phase Request</a>
Protocol</h2>

<p><a name="XKMS_2_0_Paragraph_59" id="XKMS_2_0_Paragraph_59" class="markParagraph" shape="rect">[59]</a>XKMS requests may employ a two-phase request
protocol to protect against a denial of service attack. The two-phase request
protocol allows the service to perform a lightweight authentication of the
source of an XKMS request, specifically the service determines that the
client is able to read messages sent to the purported source address.
Although this mechanism provides only a weak form of authentication it
prevents an attacker performing a Denial of Service attack by forcing the
service to perform a resource intensive form of authentication such as the
verification of a digital signature.</p>

<p><a name="XKMS_2_0_Paragraph_60" id="XKMS_2_0_Paragraph_60" class="markParagraph" shape="rect">[60]</a>The two-phase protocol consists of two phases
as follows:</p>

<blockquote>
  <p><a name="XKMS_2_0_Paragraph_61" id="XKMS_2_0_Paragraph_61" class="markParagraph" shape="rect">[61]</a>In the first phase the requestor presents the
  request and the service responds the <span class="ID">MajorResult</span>
  value <span class="ID">Represent</span> and presents a nonce.</p>

  <p><a name="XKMS_2_0_Paragraph_62" id="XKMS_2_0_Paragraph_62" class="markParagraph" shape="rect">[62]</a>In the second phase the requestor represents
  the original request together with the nonce.</p>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_63" id="XKMS_2_0_Paragraph_63" class="markParagraph" shape="rect">[63]</a>A client MAY advise a service that it supports
the two-phase request protocol by specifying the <span class="ID">ResponseMechanism</span> value <span class="ID">Represent</span>. An XKMS service advises the client that the
use of the two-phase request protocol is required by specifying the <span class="ID">MajorResult</span> code <span class="ID">Represent</span>.</p>

<p><a name="XKMS_2_0_Paragraph_64" id="XKMS_2_0_Paragraph_64" class="markParagraph" shape="rect">[64]</a>An XKMS service MUST NOT return the <span class="ID">MajorResult</span> code <span class="ID">Represent</span> unless the <span class="ID">ResponseMechanism</span> value <span class="ID">Represent</span> was specified in the corresponding request.
If an XKMS service requires the use of the two-phase request protocol and the
<span class="ID">ResponseMechanism</span> value <span class="ID">Represent</span> is not specified in the corresponding request
the <span class="ID">MajorResult</span> code
<span class="ID">Sender</span> and <span class="ID">MinorResult</span> code <span class="ID">RepresentRequired</span> are returned.</p>

<p><a name="XKMS_2_0_Paragraph_65" id="XKMS_2_0_Paragraph_65" class="markParagraph" shape="rect">[65]</a>The two-phase request protocol bears some
similarity to asynchronous request processing. Both mechanisms introduce an
extra protocol round trip but each serve different purposes. The purpose of
asynchronous processing is to allow a delay to be introduced between the
initial request and the return of the result. In the two-phase request
protocol however there is no delay between the first request and the first
response or between the first response and the second request. The purpose of
the two-phase request protocol is to allow a service to protect itself
against a denial of service attack by allowing the service to perform a
lightweight authentication of the source of the request.</p>

<p><a name="XKMS_2_0_Paragraph_66" id="XKMS_2_0_Paragraph_66" class="markParagraph" shape="rect">[66]</a>The service SHOULD verify that the nonce value
specified in a second phase request was recently generated by the service.
The service MAY verify that the nonce value has not been previously responded
to. The actual construction of the nonce value is outside the scope of this
specification and may be chosen as site specific circumstances dictate. The
techniques described in the section <a href="#idsandnonces" shape="rect">Construction of
Nonce Values</a> describe a technique that reduces or avoids the need to
maintain server state in order to meet this requirement.</p>

<h3><a name="XKMS_2_0_Section_2_6_1" id="XKMS_2_0_Section_2_6_1" shape="rect">2.6.1</a> Processing Steps</h3>

<p><a name="XKMS_2_0_Paragraph_67" id="XKMS_2_0_Paragraph_67" class="markParagraph" shape="rect">[67]</a>In the first phase of the two-phase protocol
the processing steps specified for the single phase case are performed with
the following exceptions:</p>
<dl>
  <dt>Requestor generation of the Phase 1 Request Message</dt>
    <dd><span class="ID">ResponseMechanism</span> value <span class="ID">Represent</span> MUST be
      specified</dd>
  <dt>Service processing of the Phase 1 Request Message</dt>
    <dd><i>Service decides to exercise option to require two-phase
      processing</i></dd>
    <dd><i>Request is NOT processed</i></dd>
  <dt>Service generation of the Phase 1 Response Message</dt>
    <dd><span class="ID">RequestId</span> is set to the value <span class="ID">Id</span> in the Phase 1 request message</dd>
    <dd><span class="ID">Nonce</span> value is set in accordance with service
      replay protection requirements</dd>
    <dd><span class="ID">MajorResult</span> is set to <span class="ID">Represent</span></dd>
  <dt>Requestor processing of the Phase 1 Response Message</dt>
    <dd><i>Proceed to phase 2</i></dd>
</dl>

<p><a name="XKMS_2_0_Paragraph_68" id="XKMS_2_0_Paragraph_68" class="markParagraph" shape="rect">[68]</a>In the Second phase of the two-phase protocol
the processing steps specified for the single phase case are performed with
the following exceptions:</p>
<dl>
  <dt>Requestor generation of the Phase 2 Request Message</dt>
    <dd><span class="ID">OriginalRequestId</span>&#xA0; set to the value of
      <span class="ID">Id</span> in the Phase 1 request message<br clear="none" />
      <span class="ID">Nonce</span> value is set to the value of <span class="ID">Nonce</span> in the Phase 1 response message</dd>
  <dt>Service processing of the Phase 2 Request Message</dt>
    <dd><i>Verify value of <span class="ID">Nonce</span></i></dd>
    <dd><i>Verify that request meets service authorization policy<br clear="none" />
      Process request to completion</i></dd>
  <dt>Service generation of the Phase 2 Response Message</dt>
    <dd><span class="ID">RequestId</span> is set to the value of <span class="ID">Id</span> in the Phase2 request message</dd>
    <dd><span class="ID">Nonce</span> is not present<br clear="none" />
      <span class="ID">MajorResult</span> is set to a Final result value</dd>
  <dt>Requestor processing of the Phase 2 Response Message</dt>
    <dd><i>If <span class="ID">MajorResult</span> set to a non-final value
      consider to be failure</i></dd>
</dl>

<h3><a name="XKMS_2_0_Section_2_6_2" id="XKMS_2_0_Section_2_6_2" shape="rect">2.6.2</a> <a name="idsandnonces" id="idsandnonces" shape="rect"> Construction of Nonce Values</a></h3>

<p><a name="XKMS_2_0_Paragraph_69" id="XKMS_2_0_Paragraph_69" class="markParagraph" shape="rect">[69]</a>Nonce values may be constructed in any manner
that the service chooses. It may be useful to construct the nonce so as to
permit the service to determine that they were generated by the server at a
specific time in a computationally efficient manner as follows.</p>

<p><a name="XKMS_2_0_Paragraph_70" id="XKMS_2_0_Paragraph_70" class="markParagraph" shape="rect">[70]</a>The nonce is constructed from the current time
at the service, a unique serial number and a secret key known only to the
service using a Message Authentication Code as follows  
("<code>+</code>" indicates
concatenation):</p>

<blockquote>
  <p><a name="XKMS_2_0_Paragraph_71" id="XKMS_2_0_Paragraph_71" class="markParagraph" shape="rect">[71]</a> <i>nonce</i> = <i>time</i> + <i>serial</i> +
  <i>M</i> ( <i>time</i> + <i>serial</i> , <i>k</i> )</p>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_72" id="XKMS_2_0_Paragraph_72" class="markParagraph" shape="rect">[72]</a>The service may limit the time interval in
which replay attacks are possible by rejecting nonce values that specify an
unacceptable time value or an incorrect MAC value.</p>

<p><a name="XKMS_2_0_Paragraph_73" id="XKMS_2_0_Paragraph_73" class="markParagraph" shape="rect">[73]</a>The service may prevent replay attacks
completely by tracking the serial numbers for which responses have already
been given, using the nonce time construction value to limit the interval
over which the serial number is tracked.</p>

<p><a name="XKMS_2_0_Paragraph_74" id="XKMS_2_0_Paragraph_74" class="markParagraph" shape="rect">[74]</a>The nonce value may be encrypted to avoid
leaking information such as the serial number value which might be of
interest to an attacker.</p>

<h3><a name="XKMS_2_0_Section_2_6_3" id="XKMS_2_0_Section_2_6_3" shape="rect">2.6.3</a>
Example</h3>

<h4><a name="XKMS_2_0_Section_2_6_3_1" id="XKMS_2_0_Section_2_6_3_1" shape="rect">2.6.3.1</a> Request 1</h4>
<!-- Include file -->
<pre class="Example" xml:space="preserve">&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;LocateRequest Id="Ia1d6ca7a067fdd545f1a1396d2f26779"
      Service="http://www.example.org/XKMS"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;ResponseMechanism&gt;http://www.w3.org/2002/03/xkms#Represent&lt;/ResponseMechanism&gt;
  &lt;QueryKeyBinding /&gt;
&lt;/LocateRequest&gt;</pre>

<h4><a name="XKMS_2_0_Section_2_6_3_2" id="XKMS_2_0_Section_2_6_3_2" shape="rect">2.6.3.2</a> Response 1</h4>
<!-- Include file -->
<pre class="Example" xml:space="preserve">&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;LocateResult Id="Idbc77142059a3a51c9eccd2425d77757"
      Service="http://www.example.org/XKMS"
      Nonce="Rj2BoUZM7PisPX2ytSAAWA==" 
      ResultMajor="http://www.w3.org/2002/03/xkms#Represent"
      RequestId="Ia1d6ca7a067fdd545f1a1396d2f26779"
      xmlns="http://www.w3.org/2002/03/xkms#" /&gt;</pre>

<h4><a name="XKMS_2_0_Section_2_6_3_3" id="XKMS_2_0_Section_2_6_3_3" shape="rect">2.6.3.3</a> Request 2</h4>
<!-- Include file -->
<pre class="Example" xml:space="preserve">&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;LocateRequest Id="I47804adaec32e34afeecdb51f3e0f765"
      Service="http://www.example.org/XKMS"
      Nonce="Rj2BoUZM7PisPX2ytSAAWA=="
      OriginalRequestId="Ia1d6ca7a067fdd545f1a1396d2f26779"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;QueryKeyBinding /&gt;
&lt;/LocateRequest&gt;</pre>

<h4><a name="XKMS_2_0_Section_2_6_3_4" id="XKMS_2_0_Section_2_6_3_4" shape="rect">2.6.3.4</a> Response 2</h4>
<!-- Include file -->
<pre class="Example" xml:space="preserve">&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;LocateResult Id="I3b0111d2232507a56444c1bc85409a94"
      Service="http://www.example.org/XKMS"
      ResultMajor="http://www.w3.org/2002/03/xkms#Success"
      RequestId="I47804adaec32e34afeecdb51f3e0f765"
      xmlns="http://www.w3.org/2002/03/xkms#" /&gt;</pre>

<h2><a name="XKMS_2_0_Section_2_7" id="XKMS_2_0_Section_2_7" shape="rect">2.7</a> <a name="TwoPhaseProtocolwithAsynchronous" id="TwoPhaseProtocolwithAsynchronous" shape="rect">Two-Phase Protocol with
Asynchronous</a> Processing</h2>

<p><a name="XKMS_2_0_Paragraph_75" id="XKMS_2_0_Paragraph_75" class="markParagraph" shape="rect">[75]</a>The two-phase protocol may be combined with
Asynchronous Processing. In this case the operation will consist of three
round trips as follows:</p>
<ul>
  <li>Initial Request / Phase 1</li>
  <li>Initial Request / Phase 2</li>
  <li>Pending Response</li>
</ul>

<p><a name="XKMS_2_0_Paragraph_76" id="XKMS_2_0_Paragraph_76" class="markParagraph" shape="rect">[76]</a>Message processing is performed as described
above with the following exceptions.</p>
<ul>
  <li><span class="ID">OriginalRequestId</span>&#xA0; set to that value of
    <span class="ID">Id</span> in Initial Request / Phase 1 in
    <i>both</i> subsequent requests.</li>
  <li><span class="ID">Nonce</span> value is set to the value of <span class="ID">Nonce</span> in Phase 1 response in <i>both</i> subsequent
    requests.</li>
</ul>

<h2><a name="XKMS_2_0_Section_2_8" id="XKMS_2_0_Section_2_8" shape="rect">2.8</a> <a name="CompoundRequestsandResponses" id="CompoundRequestsandResponses" shape="rect">Compound Requests and Responses</a></h2>

<p><a name="XKMS_2_0_Paragraph_77" id="XKMS_2_0_Paragraph_77" class="markParagraph" shape="rect">[77]</a>An XKMS service MAY support processing of
Compound Requests. A compound request permits multiple XKMS requests to be
made at the same time. A compound request consists of an outer request and
one or more inner requests. There is no ordering implicit in the inner
requests. The semantics of making a set of requests as a compound request are
exactly the same as if each individual request in the set had been made
separately and simultaneously.</p>

<p><a name="XKMS_2_0_Paragraph_78" id="XKMS_2_0_Paragraph_78" class="markParagraph" shape="rect">[78]</a>The response to a compound request is a
compound response. A compound response consists of an outer response and zero
or more inner responses. If the <span class="ID">ResultMajor</span> value
of the outer response is <span class="ID">Success</span> the compound
response SHOULD contain an inner response response element corresponding to
each inner request element of the compound request. If the the <span class="ID">ResultMajor</span> value of the outer response is not
<span class="ID">Success</span> the response MUST NOT contain any inner
responses. If a compound response has an outer <span class="ID">ResultMajor</span> value <span class="ID">Success</span>
but does not contain a response corresponding to an inner request, that inner request is assumed to have failed.</p>

<p><a name="XKMS_2_0_Paragraph_79" id="XKMS_2_0_Paragraph_79" class="markParagraph" shape="rect">[79]</a>An XKMS service MAY support the use of the two
phase protocol on the outer request of a compound response. The two-phase
protocol SHOULD NOT be used on an inner response. If an inner request
specifies the <span class="ID">ResponseMechanism</span> value <span class="ID">Represent</span> the value SHOULD be ignored.</p>

<p><a name="XKMS_2_0_Paragraph_80" id="XKMS_2_0_Paragraph_80" class="markParagraph" shape="rect">[80]</a>An XKMS service MAY support the use of
asynchronous processing in conjunction with a compound request. Asynchronous
processing MAY be performed on the compound request as a whole, on individual
inner requests or both.</p>

<p><a name="XKMS_2_0_Paragraph_81" id="XKMS_2_0_Paragraph_81" class="markParagraph" shape="rect">[81]</a>If asynchronous processing is to be performed
on the compound request as a whole the outer request specifies the <span class="ID">ResponseMechanism</span> value <span class="ID">Pending</span>. If the service decides to return an asynchronous
response a compound response is returned with a ResultMajor code of <span class="ID">Pending</span>. When the service has completed the processing, as determined through polling or notification, the client issues a <span class="ID">PendingRequest</span> message for
the outer request to which the service replies with a compound response
returning either the inner responses corresponding to the original inner
requests or an error report.</p>

<p><a name="XKMS_2_0_Paragraph_82" id="XKMS_2_0_Paragraph_82" class="markParagraph" shape="rect">[82]</a>If asynchronous processing is performed on the
individual inner requests each inner request for which an asynchronous
response is to be accepted specifies the&#xA0;<span class="ID">ResponseMechanism</span> value <span class="ID">Pending</span>. If the service decides to return an asynchronous
response to an inner request a compound response is returned with an outer
<span class="ID">ResultMajor</span> code of <span class="ID">Success</span> and an inner <span class="ID">ResultMajor</span> code of <span class="ID">Pending</span>
for the requests for which an asynchronous response is to be issued. A
service MAY return synchronous and asynchronous responses in a single
compound response.</p>

<p><a name="XKMS_2_0_Paragraph_83" id="XKMS_2_0_Paragraph_83" class="markParagraph" shape="rect">[83]</a>Since the semantics of a compound request are
exactly the same as if each inner request were made separately a client MAY
issue separate pending requests to obtain the results of the inner requests
of a previous compound request.</p>

<h3><a name="XKMS_2_0_Section_2_8_1" id="XKMS_2_0_Section_2_8_1" shape="rect">2.8.1</a> Example</h3>

<h4><a name="XKMS_2_0_Section_2_8_1_1" id="XKMS_2_0_Section_2_8_1_1" shape="rect">2.8.1.1</a> Request 1</h4>
<!-- Include file -->
<pre class="Example" xml:space="preserve">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;CompoundRequest Id="I264f5da49b1ff367d4e7aef1f7a1df1a"
      Service="http://www.example.org/XKMS"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;LocateRequest Id="I8c26be5f1b4dd228b43fb6eaee285faa"
        Service="http://www.example.org/XKMS"&gt;
    &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#KeyValue&lt;/RespondWith&gt;
    &lt;QueryKeyBinding&gt;
      &lt;KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#"&gt;
        &lt;X509Data&gt;
          &lt;X509Certificate&gt;
            MIICEDCCAX2gAwIBAgIQimXeUAxYJbJMady9vV1bLjAJBgUrDgMCHQUAMBIxEDA
            OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMDUwODE1MDY1OTU5Wj
            ArMSkwJwYDVQQDEyBBbGljZSBBYXJkdmFyayBPPUFsaWNlIENvcnAgQz1VUzCBn
            zANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0nIsmR+aVW2egl5MIfOKy4HuMKkk
            9AZ/IQuDLVPlhzOfgngjVQCjr8uvmnqtNu8HBupui8LgGthO6U9D0CNT5mbmhIA
            ErRADUMIAFsi7LzBarUvNWTqYNEJmcHsAUZdrdcDrkNnG7SzbuJx+GDNiHKVDQg
            gPBLc1XagW20RMvokCAwEAAaNWMFQwDQYDVR0KBAYwBAMCBkAwQwYDVR0BBDwwO
            oAQAaVOkaVLLKoFmLN37pC8uqEUMBIxEDAOBgNVBAMTB1Rlc3QgQ0GCEC4MndUX
            jPG1TZxVKg+HutAwCQYFKw4DAh0FAAOBgQABU91ka7IlkXCfv4Zh2Ohwgg2yObt
            Y3+6C/BTFGrOEBJDy+DoxJ/NuBF18w3rrrR18xE6jNKYLCQb8zUGk4QOG5Y+HT/
            QTTFvWkiOLXcpTuhnOhXatr42FoYpDkjx2QWK+J5Q2l/Rgjgc/0ZV8U/kD8UuRk
            Xp4AZh7QsiX8AcO0w==
          &lt;/X509Certificate&gt;
        &lt;/X509Data&gt;
      &lt;/KeyInfo&gt;
      &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/KeyUsage&gt;
    &lt;/QueryKeyBinding&gt;
  &lt;/LocateRequest&gt;
  &lt;LocateRequest Id="If8e63d729384ad35498e7b65b3dc785e"
        Service="http://www.example.org/XKMS"&gt;
    &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#KeyName&lt;/RespondWith&gt;
    &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#KeyValue&lt;/RespondWith&gt;
    &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#X509Cert&lt;/RespondWith&gt;
    &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#X509Chain&lt;/RespondWith&gt;
    &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#PGPWeb&lt;/RespondWith&gt;
    &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#PGP&lt;/RespondWith&gt;
    &lt;QueryKeyBinding&gt;
      &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Encryption&lt;/KeyUsage&gt;
      &lt;UseKeyWith Application="urn:ietf:rfc:2440"
            Identifier="bob@example.com" /&gt;
      &lt;UseKeyWith Application="urn:ietf:rfc:2633"
            Identifier="bob@example.com" /&gt;
    &lt;/QueryKeyBinding&gt;
  &lt;/LocateRequest&gt;
&lt;/CompoundRequest&gt;</pre>

<h4><a name="XKMS_2_0_Section_2_8_1_2" id="XKMS_2_0_Section_2_8_1_2" shape="rect">2.8.1.2</a> Response 1</h4>
<!-- Include file -->
<pre class="Example" xml:space="preserve">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;CompoundResult Id="If2d286d4a542bd92989aa606d9f1a5ca"
      Service="http://www.example.org/XKMS"
      ResultMajor="http://www.w3.org/2002/03/xkms#Success"
      RequestId="I264f5da49b1ff367d4e7aef1f7a1df1a"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;LocateResult Id="I69044d458e0bceef5f78c79c32fa9ddf"
        Service="http://www.example.org/XKMS"
        ResultMajor="http://www.w3.org/2002/03/xkms#Success"
        RequestId="I8c26be5f1b4dd228b43fb6eaee285faa"&gt;
    &lt;UnverifiedKeyBinding Id="I8f7367375ac134872eab7acf42a8d1bd"&gt;
      &lt;KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#"&gt;
        &lt;KeyValue&gt;
          &lt;RSAKeyValue&gt;
            &lt;Modulus&gt;
              0nIsmR+aVW2egl5MIfOKy4HuMKkk9AZ/IQuDLVPlhzOfgngjVQCjr8uvmnqtNu8HBupui8LgG
              thO6U9D0CNT5mbmhIAErRADUMIAFsi7LzBarUvNWTqYNEJmcHsAUZdrdcDrkNnG7SzbuJx+GD
              NiHKVDQggPBLc1XagW20RMvok=
            &lt;/Modulus&gt;
            &lt;Exponent&gt;AQAB&lt;/Exponent&gt;
          &lt;/RSAKeyValue&gt;
        &lt;/KeyValue&gt;
      &lt;/KeyInfo&gt;
      &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/KeyUsage&gt;
      &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Encryption&lt;/KeyUsage&gt;
      &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Exchange&lt;/KeyUsage&gt;
      &lt;UseKeyWith Application="urn:ietf:rfc:2633"
            Identifier="alice@example.com" /&gt;
    &lt;/UnverifiedKeyBinding&gt;
  &lt;/LocateResult&gt;
  &lt;LocateResult Id="Ic3d02a8b1f63ba694a8fad11a74fb499"
        Service="http://www.example.org/XKMS"
        ResultMajor="http://www.w3.org/2002/03/xkms#Success"
        RequestId="If8e63d729384ad35498e7b65b3dc785e"&gt;
    &lt;UnverifiedKeyBinding Id="I42604b6f40f46b74b5c30077100fe8e9"&gt;
      &lt;KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#"&gt;
        &lt;KeyValue&gt;
          &lt;RSAKeyValue&gt;
            &lt;Modulus&gt;
              3FFtWUsvEajQt2SeSF+RvAxWdPPh5GSlQnp8SDvvqvCwE6PXcRWrIGmV7twNf2T
              UXCxYuztUUClMIy14B0Q+k1ej2nekmYL7+Ic3DDGVFVaYPoxaRY0Y2lV8tOreyn
              WegpFbITXc8V6Y02QfR5O7Pn1/10ElslaF/TF8MQGqYE8=
            &lt;/Modulus&gt;
            &lt;Exponent&gt;AQAB&lt;/Exponent&gt;
          &lt;/RSAKeyValue&gt;
        &lt;/KeyValue&gt;
        &lt;X509Data&gt;
          &lt;X509Certificate&gt;
            MIICCTCCAXagAwIBAgIQe0Sk4xr1VolGFFNMkCx07TAJBgUrDgMCHQUAMBIxEDA
            OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMDUwODE1MDY1OTU5Wj
            AkMSIwIAYDVQQDExlCb2IgQmFrZXIgTz1Cb2IgQ29ycCBDPVVTMIGfMA0GCSqGS
            Ib3DQEBAQUAA4GNADCBiQKBgQDcUW1ZSy8RqNC3ZJ5IX5G8DFZ08+HkZKVCenxI
            O++q8LATo9dxFasgaZXu3A1/ZNRcLFi7O1RQKUwjLXgHRD6TV6Pad6SZgvv4hzc
            MMZUVVpg+jFpFjRjaVXy06t7KdZ6CkVshNdzxXpjTZB9Hk7s+fX/XQSWyVoX9MX
            wxAapgTwIDAQABo1YwVDANBgNVHQoEBjAEAwIGQDBDBgNVHQEEPDA6gBABpU6Rp
            UssqgWYs3fukLy6oRQwEjEQMA4GA1UEAxMHVGVzdCBDQYIQLgyd1ReM8bVNnFUq
            D4e60DAJBgUrDgMCHQUAA4GBAF4jP1gGDbaq3rg/Vo3JY7EDNTp0HmwLiPMLmdn
            B3WTIGFcjS/jZFzRCbvKPeiPTZ6kRkGgydFOuCo5HMAxIks/LtnKFd/0qYT+AOD
            q/rCrwSx+F+Ro2rf9tPpja9o7gANqxs6Pm7f1QSPZO57bT/6afiVm7NdaCfjgMp
            hb+XNyn
          &lt;/X509Certificate&gt;
          &lt;X509Certificate&gt;
            MIIB9zCCAWSgAwIBAgIQLgyd1ReM8bVNnFUqD4e60DAJBgUrDgMCHQUAMBIxEDA
            OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMTAwODE1MDcwMDAwWj
            ASMRAwDgYDVQQDEwdUZXN0IENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBg
            QCn23HHp+HtXpiyKVSDtdE3dO0r0oLB/H9sxUEkeXB8oMxwbhdcizWH92zrtm1V
            fVtxkfmwF14ZXoyDZHeZXuCOtAfz/mW6s2gmfD45TfFFVGksDGVRNK5XmKXA5sE
            C51RCvaxzGBdGDlCuVPqX7Cq3IcZpRU1IXbi5YzGwV7j6LwIDAQABo1YwVDANBg
            NVHQoEBjAEAwIHgDBDBgNVHQEEPDA6gBABpU6RpUssqgWYs3fukLy6oRQwEjEQM
            A4GA1UEAxMHVGVzdCBDQYIQLgyd1ReM8bVNnFUqD4e60DAJBgUrDgMCHQUAA4GB
            ABDYD4Fwx2dscu+BgYcZ+GoQQtCJkwJEXytb4zlNl7HLFKbXSw4m0blQquIsfsi
            QgFYAQBXSbu7aeUqqmSGHvILu3BGwVOKjxbHfcM4/MefuTtpOpCN40wy3YwwngD
            tHTaIqm8NwS966PE+W9f8kD70q5FNwf+GF/lX9qGc/x435
          &lt;/X509Certificate&gt;
        &lt;/X509Data&gt;
      &lt;/KeyInfo&gt;
      &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/KeyUsage&gt;
      &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Encryption&lt;/KeyUsage&gt;
      &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Exchange&lt;/KeyUsage&gt;
      &lt;UseKeyWith Application="urn:ietf:rfc:2633"
            Identifier="bob@example.com" /&gt;
    &lt;/UnverifiedKeyBinding&gt;
  &lt;/LocateResult&gt;
&lt;/CompoundResult&gt;</pre>

<h2><a name="XKMS_2_0_Section_2_9" id="XKMS_2_0_Section_2_9" shape="rect">2.9</a> <a name="SecurityBinding" id="SecurityBinding" shape="rect">Security Binding</a></h2>

<p><a name="XKMS_2_0_Paragraph_84" id="XKMS_2_0_Paragraph_84" class="markParagraph" shape="rect">[84]</a>The security concerns that an XKMS service is
required to address are dependent on the specific service deployment. For
example a free XKMS Location service may not require controls for Request
Authentication or to prevent Request Replay attacks while a paid Validate
service might. The application of security enhancements is addressed in
<a href="/TR/2005/REC-xkms2-bindings-20050628/" shape="rect">Part II</a> which describes
the application of the following security enhancements:</p>
<ul>
  <li>Confidentiality</li>
  <li>Request Authentication</li>
  <li>Response Authentication</li>
  <li>Transitive Authentication</li>
  <li>Response Replay</li>
  <li>Request Substitution</li>
  <li>Request Replay</li>
  <li>Denial of Service</li>
</ul>

<p><a name="XKMS_2_0_Paragraph_85" id="XKMS_2_0_Paragraph_85" class="markParagraph" shape="rect">[85]</a>The use of security enhancements is further
discussed in the section <a href="#SecurityConsiderations" shape="rect">Security
Considerations</a> below.</p>

<h1><a name="XKMS_2_0_Section_3" id="XKMS_2_0_Section_3" shape="rect">3</a> Message
Syntax</h1>

<h2><a name="XKMS_2_0_Section_3_1" id="XKMS_2_0_Section_3_1" shape="rect">3.1</a> Message
Base</h2>

<h3><a name="XKMS_2_0_Section_3_1_1" id="XKMS_2_0_Section_3_1_1" shape="rect">3.1.1</a> <a name="TypeMessageAbstractType" id="TypeMessageAbstractType" shape="rect">Type <span class="ID">MessageAbstractType</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_86" id="XKMS_2_0_Paragraph_86" class="markParagraph" shape="rect">[86]</a>The <span class="ID">MessageAbstractType</span>
abstract type is the type from which all XKMS message element types are
derived. The <span class="ID">MessageAbstractType</span> abstract type
contains the following element and attributes</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;ds:Signature&gt;</b></span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>An XML Signature <a href="#XML-SIG" shape="rect">[XML-SIG]</a> in enveloped
        mode. The scope of the signature is the entire request message (i.e.
        the element derived from MessageAbstractType) and is specified using
        a reference to the <span class="ID">Id</span> attribute specified in
        the <span class="ID">MessageAbstractType</span> abstract type.</dd>
    <dt><span class="ID">&lt;MessageExtension&gt;</span>&nbsp;&nbsp;&nbsp;[Any Number]</dt>
      <dd>An extension element derived from the <span class="ID">MessageExtensionAbstractType</span>.</dd>
    <dt><b><span class="ID">&lt;OpaqueClientData&gt;</span>&nbsp;&nbsp;&nbsp;[Optional]</b></dt>
      <dd>A collection of data specified by the client
        that is opaque to the service. An XKMS service SHOULD return the
        value of the <span class="ID">&lt;OpaqueClientData&gt;</span> element
        unmodified in a request in a response with status code Success.</dd>
    <dt><span class="ID">Id</span>&nbsp;&nbsp;&nbsp;[Required]</dt>
      <dd>A unique identifier generated by the originator.</dd>
    <dt><span class="ID"><b>Service</b></span>&nbsp;&nbsp;&nbsp;[Required]</dt>
      <dd>The URI of the Web Service port to which the request is
      addressed.</dd>
    <dt><span class="ID"><b>Nonce</b></span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>Cryptographically random data used to defend against replay
      attack.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_87" id="XKMS_2_0_Paragraph_87" class="markParagraph" shape="rect">[87]</a>The following schema defines the <span class="ID">MessageAbstractType</span> abstract type:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- MessageAbstractType --&gt;
   &lt;complexType name="MessageAbstractType" abstract="true"&gt;
      &lt;sequence&gt;
         &lt;element ref="ds:Signature" minOccurs="0"/&gt;
         &lt;element ref="xkms:MessageExtension" minOccurs="0"
               maxOccurs="unbounded"/&gt;
         &lt;element ref="xkms:OpaqueClientData" minOccurs="0"/&gt;
      &lt;/sequence&gt;
      &lt;attribute name="Id" type="ID" use="required"/&gt;
      &lt;attribute name="Service" type="anyURI" use="required"/&gt;
      &lt;attribute name="Nonce" type="base64Binary" use="optional"/&gt;
   &lt;/complexType&gt;
   &lt;!-- /MessageAbstractType --&gt;</pre>

<h3><a name="XKMS_2_0_Section_3_1_2" id="XKMS_2_0_Section_3_1_2" shape="rect">3.1.2</a> <a name="ElementdsSignature" id="ElementdsSignature" shape="rect">Element <span class="ID">&lt;ds:Signature&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_88" id="XKMS_2_0_Paragraph_88" class="markParagraph" shape="rect">[88]</a>An XML Signature <a href="#XML-SIG" shape="rect">[XML-SIG]</a> in enveloped mode. The scope of the signature
is the entire request message&#xA0; (i.e. the element derrived from
MessageAbstractType)&#xA0; and is specified using a reference to the <span class="ID">Id</span> attribute specified in the <span class="ID">MessageAbstractType</span> abstract type. The empty identifier ""
MUST NOT be used.</p>

<p><a name="XKMS_2_0_Paragraph_89" id="XKMS_2_0_Paragraph_89" class="markParagraph" shape="rect">[89]</a>Validation of XML Signatures MUST be done
independent of any ancestral XML context of the message.&#xA0; This may be
achieved by:</p>
<ul>
  <li>Isolating the XKMS message from any 'wrapper' (eg. SOAP) before
    validation, or;</li>
  <li>Specifying a canonicalization algorithm, such as Exclusive XML
    Canonicalization, in <span class="ID">&lt;SignedInfo&gt;</span>:<span class="ID">&lt;CanonicalizationMethod&gt;</span> to exclude ancestral
    XML context during the validation of the message.</li>
</ul>

<p><a name="XKMS_2_0_Paragraph_90" id="XKMS_2_0_Paragraph_90" class="markParagraph" shape="rect">[90]</a>For interoperability purposes XKMS
implementations MUST support the use of Exclusive XML Canonicalization.</p>

<p><a name="XKMS_2_0_Paragraph_91" id="XKMS_2_0_Paragraph_91" class="markParagraph" shape="rect">[91]</a>The <span class="ID">&lt;ds:Signature&gt;</span> element is specified in the XML
Signature specification <a href="#XML-SIG" shape="rect">[XML-SIG]</a>.</p>

<h3><a name="XKMS_2_0_Section_3_1_3" id="XKMS_2_0_Section_3_1_3" shape="rect">3.1.3</a> <a name="ElementMessageExtension" id="ElementMessageExtension" shape="rect">Element <span class="ID">&lt;MessageExtension&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_92" id="XKMS_2_0_Paragraph_92" class="markParagraph" shape="rect">[92]</a>The <span class="ID">&lt;MessageExtension&gt;</span> element is an abstract element of
the abstract type MessageExtensionAbstractType. Implementations may define
subclasses of the MessageExtensionAbstractType to define message extension
elements that may be applied to any XKMS message.</p>

<p><a name="XKMS_2_0_Paragraph_93" id="XKMS_2_0_Paragraph_93" class="markParagraph" shape="rect">[93]</a>The following schema defines the <span class="ID">MessageExtension</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- MessageExtension --&gt;
   &lt;element name="MessageExtension" type="xkms:MessageExtensionAbstractType"
         abstract="true"/&gt;
   &lt;complexType name="MessageExtensionAbstractType" abstract="true"/&gt;
   &lt;!-- /MessageExtension --&gt;</pre>

<h3><a name="XKMS_2_0_Section_3_1_4" id="XKMS_2_0_Section_3_1_4" shape="rect">3.1.4</a> <a name="ElementOpaqueClientData" id="ElementOpaqueClientData" shape="rect">Element <span class="ID">&lt;OpaqueClientData&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_94" id="XKMS_2_0_Paragraph_94" class="markParagraph" shape="rect">[94]</a>The <span class="ID">&lt;OpaqueClientData&gt;</span> contains data specified by the
client that is opaque to the service. An XKMS service SHOULD return the value
of an <span class="ID">&lt;OpaqueClientData&gt;</span> element,
including its children, specified in a request unmodified in the
corresponding response.</p>

<p><a name="XKMS_2_0_Paragraph_95" id="XKMS_2_0_Paragraph_95" class="markParagraph" shape="rect">[95]</a>A client MAY use Opaque client data in
conjunction with asynchronous request processing to match a
response to the original request context. Opaque client data MAY
also be used in conjunction with synchronous request processing to provide
context information for purposes such as audit trail reconciliation.</p>

<p><a name="XKMS_2_0_Paragraph_96" id="XKMS_2_0_Paragraph_96" class="markParagraph" shape="rect">[96]</a>The following schema defines the <span class="ID">OpaqueClientData</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- OpaqueClientData --&gt;
   &lt;element name="OpaqueClientData" type="xkms:OpaqueClientDataType"/&gt;
   &lt;complexType name="OpaqueClientDataType"&gt;
      &lt;sequence maxOccurs="unbounded"&gt;
         &lt;element ref="xkms:OpaqueData" minOccurs="0"/&gt;
      &lt;/sequence&gt;
   &lt;/complexType&gt;
   &lt;element name="OpaqueData" type="base64Binary"/&gt;
   &lt;!-- /OpaqueClientData --&gt;</pre>

<h2><a name="XKMS_2_0_Section_3_2" id="XKMS_2_0_Section_3_2" shape="rect">3.2</a> Request
Message</h2>

<h3><a name="XKMS_2_0_Section_3_2_1" id="XKMS_2_0_Section_3_2_1" shape="rect">3.2.1</a> <a name="TypeRequestAbstractType" id="TypeRequestAbstractType" shape="rect">Type <span class="ID">RequestAbstractType</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_97" id="XKMS_2_0_Paragraph_97" class="markParagraph" shape="rect">[97]</a>The <span class="ID">RequestAbstractType</span>
abstract type is the type from which all XKMS request element types are
derived. The <span class="ID">RequestAbstractType</span> abstract type
inherits the element and attributes of the <span class="ID">MessageAbstractType</span> abstract type and in addition contains
the following elements and attributes</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;ResponseMechanism&gt;</b></span>&nbsp;&nbsp;&nbsp;[Any
    Number]</dt>
      <dd>Specifies the extended protocol mechanisms that the client supports
        in connection with this request.</dd>
    <dt><span class="ID"><b>&lt;RespondWith&gt;</b></span>&nbsp;&nbsp;&nbsp;[Any
    Number]</dt>
      <dd>Specifies the types of data the recipient requests to be sent in
        the response.</dd>
    <dt><span class="ID"><b>&lt;PendingNotification&gt;</b></span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>Specifies a means by which the service may notify the requestor of
        the completion of a pending response. If the <span class="ID">&lt;PendingNotification&gt;</span> element is present the
        value <span class="ID">Pending</span> MUST be specified as a <span class="ID">&lt;ResponseMechanism&gt;</span> value.</dd>
    <dt><span class="ID">OriginalRequestId</span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>Specifies the value <span class="ID">Id</span> of the first
        request made in a multi-stage protocol such as the asynchronous
        processing mechanism or the two-phase protocol.</dd>
    <dt><span class="ID">ResponseLimit</span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>Specifies the maximum number of data items the requestor can accept
        in the case that the schema specifies an unbounded number of
      elements.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_98" id="XKMS_2_0_Paragraph_98" class="markParagraph" shape="rect">[98]</a>The following schema defines the <span class="ID">RequestAbstractType</span> abstract type:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- RequestAbstractType --&gt;
   &lt;complexType name="RequestAbstractType" abstract="true"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:MessageAbstractType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:ResponseMechanism" minOccurs="0"
                     maxOccurs="unbounded"/&gt;
               &lt;element ref="xkms:RespondWith" minOccurs="0"
                     maxOccurs="unbounded"/&gt;
               &lt;element ref="xkms:PendingNotification" minOccurs="0"/&gt;
            &lt;/sequence&gt;
            &lt;attribute name="OriginalRequestId" type="NCName"
                  use="optional"/&gt;
            &lt;attribute name="ResponseLimit" type="integer" use="optional"/&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /RequestAbstractType --&gt;</pre>

<h3><a name="XKMS_2_0_Section_3_2_2" id="XKMS_2_0_Section_3_2_2" shape="rect">3.2.2</a> <a name="ElementResponseMechanism" id="ElementResponseMechanism" shape="rect">Element <span class="ID">&lt;ResponseMechanism&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_99" id="XKMS_2_0_Paragraph_99" class="markParagraph" shape="rect">[99]</a>The <span class="ID">&lt;ResponseMechanism&gt;</span> element in the request specifies
one or more strings included in the request that specify extended protocol
mechanisms that the client supports in connection with a request.</p>

<p><a name="XKMS_2_0_Paragraph_100" id="XKMS_2_0_Paragraph_100" class="markParagraph" shape="rect">[100]</a> <span class="ID">ResponseMechanism</span>values are specified as <span class="ID">anyURI</span>s, the following identifiers are defined:</p>

<div class="center">

<table border="1" cellpadding="3" cellspacing="0" width="100%">
  <tbody>
    <tr>
      <th valign="top"> anyURI Name</th>
      <td valign="top"><b>Description</b></td>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">http://www.w3.org/2002/03/xkms#Pending</span></td>
      <td valign="top" align="left">The requestor is prepared to accept a
        response that uses asynchronous processing, i.e. the service MAY
        return the <span class="ID">MajorResult</span> code <span class="ID">Pending</span></td>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">http://www.w3.org/2002/03/xkms#Represent</span></td>
      <td valign="top" align="left">The requestor is prepared to accept a
        response that uses the two-phase protocol, i.e. the service MAY
        return the <span class="ID">MajorResult</span> code <span class="ID">Represent</span></td>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">http://www.w3.org/2002/03/xkms#RequestSignatureValue</span></td>
      <td valign="top" align="left">The requestor is prepared to accept a
        response that carries a <span class="ID">&lt;RequestSignatureValue&gt; element.</span></td>
    </tr>
  </tbody>
</table>
</div>

<p><a name="XKMS_2_0_Paragraph_101" id="XKMS_2_0_Paragraph_101" class="markParagraph" shape="rect">[101]</a>The following schema defines the <span class="ID">&lt;ResponseMechanism&gt;</span> element::</p>
<!-- Include file -->

<pre class="Code" xml:space="preserve">   &lt;!-- ResponseMechanism --&gt;
   &lt;simpleType name="ResponseMechanismEnum"&gt;
      &lt;restriction base="anyURI"&gt;
         &lt;enumeration value="http://www.w3.org/2002/03/xkms#Pending"/&gt;
         &lt;enumeration value="http://www.w3.org/2002/03/xkms#Represent"/&gt;
         &lt;enumeration value="http://www.w3.org/2002/03/xkms#RequestSignatureValue"/&gt;
      &lt;/restriction&gt;
   &lt;/simpleType&gt;
   &lt;simpleType name="ResponseMechanismOpenEnum"&gt;
      &lt;union memberTypes="xkms:ResponseMechanismEnum anyURI"/&gt;
   &lt;/simpleType&gt;
   &lt;element name="ResponseMechanism" type="xkms:ResponseMechanismOpenEnum"/&gt;
   &lt;!-- /ResponseMechanism --&gt;</pre>

<h3><a name="XKMS_2_0_Section_3_2_3" id="XKMS_2_0_Section_3_2_3" shape="rect">3.2.3</a> <a name="ElementRespondWith" id="ElementRespondWith" shape="rect">Element <span class="ID">&lt;RespondWith&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_102" id="XKMS_2_0_Paragraph_102"
class="markParagraph" shape="rect">[102]</a>
The <span class="ID">&lt;RespondWith&gt;</span> element in a
request specifies one or more URI values that SHOULD resolve to data
elements provided in either the <span
class="ID">&lt;ds:KeyInfo&gt;</span> element or private key
information defined in the section <a href="#privatekeyparameters"
shape="rect">Cryptographic Algorithm Specific Parameters</a>
below. The <span class="ID">&lt;RespondWith&gt;</span> element SHOULD
be included in requests of type <span class="ID">LocateRequest</span>,
<span class="ID">ValidateRequest</span>, <span
class="ID">RegisterRequest</span>, <span
class="ID">ReissueRequest</span>, <span
class="ID">RevokeRequest</span>, and <span
class="ID">RecoverRequest</span>. The XML Signature elements are
described here for convenience. The normative reference is the XML
Digital Signature Specification <a href="#XML-SIG"
shape="rect">[XML-SIG]</a>.</p>

<p><a name="XKMS_2_0_Paragraph_103" id="XKMS_2_0_Paragraph_103" class="markParagraph" shape="rect">[103]</a>The Service SHOULD return any data elements that are resolvable
<span class="ID">&lt;RespondWith&gt;</span> URI values and that
are supported by the Service. The Service MAY return additional data
elements not requested.  In particular, the service MAY return data
elements specified in the request with the response.</p>

<p><a name="XKMS_2_0_Paragraph_104" id="XKMS_2_0_Paragraph_104" class="markParagraph" shape="rect">[104]</a> <span class="ID">RespondWith</span> values
are specified as <span class="ID">anyURI</span>s,
 the following identifiers are defined (all names under the first columnn are prefixed with URI <span class="ID">http://www.w3.org/2002/03/xkms#</span>):</p>

<div class="center">

<table border="1" cellpadding="3" cellspacing="0" width="100%">
  <tbody>
    <tr>
      <th valign="top">anyURI Name<br />
      </th>
      <td valign="top"><span class="ID"><b>&lt;ds:Keyinfo&gt;</b></span>
        <b>Element</b></td>
      <td valign="top"><b>Description</b></td>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">KeyName</span></td>
      <td valign="top" align="left"><span class="ID">&lt;ds:KeyName&gt;</span></td>
      <td valign="top" align="left">Key name</td>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">KeyValue</span></td>
      <td valign="top" align="left"><span class="ID">&lt;ds:KeyValue&gt;</span></td>
      <td valign="top" align="left">Public key parameters</td>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">X509Cert</span></td>
      <td valign="top" align="left"><span class="ID">&lt;ds:X509Data&gt;</span></td>
      <td valign="top" align="left">X509 Certificate v3 that authenticates
        the specified key</td>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">X509Chain</span></td>
      <td valign="top" align="left"><span class="ID">&lt;ds:X509Data&gt;*</span></td>
      <td valign="top" align="left">X509 Certificate v3 chain that
        authenticates the specified key. Note that no ordering is implied in
        the returned certificates.</td>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">X509CRL</span></td>
      <td valign="top" align="left"><span class="ID">&lt;ds:X509Data&gt;</span></td>
      <td valign="top" align="left">X509 Certificate Revocation List v2</td>
    </tr>
    
    <tr>
      <td valign="top" align="left"><span class="ID">RetrievalMethod</span></td>
      <td valign="top" align="left"><span class="ID">&lt;ds:RetrievalMethod&gt;</span></td>
      <td valign="top" align="left">Retrieval Method data</td>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">PGP</span></td>
      <td valign="top" align="left"><span class="ID">&lt;ds:PGPData&gt;</span></td>
      <td valign="top" align="left">PGP key signing data</td>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">PGPWeb</span></td>
      <td valign="top" align="left"><span class="ID">&lt;ds:PGPData&gt;*</span></td>
      <td valign="top" align="left">Collection of PGP key signing data</td>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">SPKI</span></td>
      <td valign="top" align="left"><span class="ID">&lt;ds:SPKIData&gt;*</span></td>
      <td valign="top" align="left">SPKI key signing</td>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">PrivateKey</span></td>
      <td valign="top" align="left">&#xA0;</td>
      <td valign="top" align="left">Request that the encrypted private key be
        returned in the response. [Used in the X-KRSS protocol]</td>
    </tr>
  </tbody>
</table>
</div>
<p><a name="XKMS_2_0_Paragraph_104a" id="XKMS_2_0_Paragraph_104a" class="markParagraph" shape="rect">[104a]</a>(In the above table, <span class="ID">*</span> stands for one or more.).</p>


<p><a name="XKMS_2_0_Paragraph_105" id="XKMS_2_0_Paragraph_105" class="markParagraph" shape="rect">[105]</a>For example, a client that has no X.509
processing capability might perform a <span class="ID">Locate</span>
operation to obtain the public key parameters and name information from a
<span class="ID">&lt;ds:Keyinfo&gt;</span> element that specifies only a
certificate. The <span class="ID">RespondWith</span> element values in this
case would be <span class="ID">KeyName</span> and <span class="ID">KeyValue</span>.</p>

<p><a name="XKMS_2_0_Paragraph_106" id="XKMS_2_0_Paragraph_106" class="markParagraph" shape="rect">[106]</a>The following schema defines the <span class="ID">&lt;RespondWith&gt;</span> element::</p>
<!-- Include file -->

<pre class="Code" xml:space="preserve">   &lt;!-- RespondWith --&gt;
    &lt;simpleType name="RespondWithEnum"&gt;
         &lt;restriction base="anyURI"&gt;
              &lt;enumeration value="http://www.w3.org/2002/03/xkms#KeyName"/&gt;
              &lt;enumeration value="http://www.w3.org/2002/03/xkms#KeyValue"/&gt;
              &lt;enumeration value="http://www.w3.org/2002/03/xkms#X509Cert"/&gt;
              &lt;enumeration value="http://www.w3.org/2002/03/xkms#X509Chain"/&gt;
              &lt;enumeration value="http://www.w3.org/2002/03/xkms#X509CRL"/&gt;
              &lt;enumeration value="http://www.w3.org/2002/03/xkms#RetrievalMethod"/&gt;
              &lt;enumeration value="http://www.w3.org/2002/03/xkms#PGP"/&gt;
              &lt;enumeration value="http://www.w3.org/2002/03/xkms#PGPWeb"/&gt;
              &lt;enumeration value="http://www.w3.org/2002/03/xkms#SPKI"/&gt;
              &lt;enumeration value="http://www.w3.org/2002/03/xkms#PrivateKey"/&gt;
         &lt;/restriction&gt;
    &lt;/simpleType&gt;
    &lt;simpleType name="RespondWithOpenEnum"&gt;
         &lt;union memberTypes="xkms:RespondWithEnum anyURI"/&gt;
    &lt;/simpleType&gt;
   &lt;element name="RespondWith" type="xkms:RespondWithOpenEnum"/&gt;
   &lt;!-- /RespondWith --&gt;</pre>

<h3><a name="XKMS_2_0_Section_3_2_4" id="XKMS_2_0_Section_3_2_4" shape="rect">3.2.4</a> <a name="ElementPendingNotification" id="ElementPendingNotification" shape="rect">Element
<span class="ID">&lt;PendingNotification&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_107" id="XKMS_2_0_Paragraph_107" class="markParagraph" shape="rect">[107]</a>The <span class="ID">&lt;PendingNotification&gt;</span> element is used to specify a
mechanism by means of which the service can inform a requestor that a pending
request has completed asynchronously.</p>

<p><a name="XKMS_2_0_Paragraph_108" id="XKMS_2_0_Paragraph_108" class="markParagraph" shape="rect">[108]</a>The <span class="ID">&lt;PendingNotification&gt;</span> element contains the following
attributes</p>

<blockquote>
  <dl>
    <dt><span class="ID">Mechanism</span>&nbsp;&nbsp;&nbsp;[Required]</dt>
      <dd>A URI that specifies the protocol by which the notification MAY be
        made.</dd>
    <dt><span class="ID">Identifier</span>&nbsp;&nbsp;&nbsp;[Required]</dt>
      <dd>A URI that specifies the address to which the notification MAY be
        made.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_109" id="XKMS_2_0_Paragraph_109" class="markParagraph" shape="rect">[109]</a>The following mechanisms are defined:</p>

<table border="1" id="AutoNumber1" cellspacing="0" cellpadding="2" width="100%">
  <tbody>
    <tr>
      <th width="68">Protocol</th>
      <th width="116">Mechanism</th>
      <th width="68">Identifier</th>
      <th width="644">Description</th>
    </tr>
    <tr>
      <td width="68" valign="top">SMTP</td>
      <td width="116" valign="top">urn:ietf:rfc:822</td>
      <td width="68" valign="top">mailto:</td>
      <td width="644" valign="top" align="left">Notification by email. The
        content of the email is outside the scope of this specification</td>
    </tr>
    <tr>
      <td width="68" valign="top">HTTP</td>
      <td width="116" valign="top">urn:ietf:rfc:2616</td>
      <td width="68" valign="top">http://</td>
      <td width="644" valign="top" align="left">Notification by HTTP. The
        content of the request is outside the scope of this specification</td>
    </tr>
  </tbody>
</table>

<p><a name="XKMS_2_0_Paragraph_110" id="XKMS_2_0_Paragraph_110" class="markParagraph" shape="rect">[110]</a>The following schema defines the <span class="ID">&lt;PendingNotification&gt;</span> element and <span class="ID">PendingNotificationType</span> type:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- PendingNotification --&gt;
   &lt;element name="PendingNotification" type="xkms:PendingNotificationType"/&gt;
   &lt;complexType name="PendingNotificationType"&gt;
      &lt;attribute name="Mechanism" type="anyURI" use="required"/&gt;
      &lt;attribute name="Identifier" type="anyURI" use="required"/&gt;
   &lt;/complexType&gt;
   &lt;!-- /PendingNotification --&gt;</pre>

<h3><a name="XKMS_2_0_Section_3_2_5" id="XKMS_2_0_Section_3_2_5" shape="rect">3.2.5</a> <a name="ElementPendingRequest" id="ElementPendingRequest" shape="rect">Element <span class="ID">&lt;PendingRequest&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_111" id="XKMS_2_0_Paragraph_111" class="markParagraph" shape="rect">[111]</a>The <span class="ID">PendingRequest</span>
element is used to request the result of a previously presented request for
which the <span class="ID">MajorResult</span>
code <span class="ID">Pending</span> was
returned. The <span class="ID">PendingRequest</span> element inherits the element and
attributes of 
<span class="ID">RequestAbstractType</span> and the following
attribute:</p>

<blockquote>
  <dl>
    <dt><span class="ID">ResponseId</span>&nbsp;&nbsp;&nbsp;[Required]</dt>
      <dd>The value of the <span class="ID">Id</span> attribute sent in the
        original response containing the <span class="ID">MajorResult</span> code <span class="ID">Pending</span>.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_112" id="XKMS_2_0_Paragraph_112" class="markParagraph" shape="rect">[112]</a>If the value of ResponseId is unknown to the
service the result <span class="ID">Sender.UnknownResponseId</span> is
returned.</p>

<p><a name="XKMS_2_0_Paragraph_112a" id="XKMS_2_0_Paragraph_112a" class="markParagraph" shape="rect">[112a]</a>The <span class="ID">RespondWith</span> element
MUST NOT be present
inside a <span class="ID">PendingRequest</span> element.</p>

<p><a name="XKMS_2_0_Paragraph_113" id="XKMS_2_0_Paragraph_113" class="markParagraph" shape="rect">[113]</a>The following schema defines the <span class="ID">PendingRequest</span> element and <span class="ID">PendingRequestType</span> type:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- PendingRequest --&gt;
   &lt;element name="PendingRequest" type="xkms:PendingRequestType"/&gt;
   &lt;complexType name="PendingRequestType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:RequestAbstractType"&gt;
            &lt;attribute name="ResponseId" type="NCName" use="required"/&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /PendingRequest --&gt;</pre>

<h2><a name="XKMS_2_0_Section_3_3" id="XKMS_2_0_Section_3_3" shape="rect">3.3</a> Response
Message</h2>

<h3><a name="XKMS_2_0_Section_3_3_1" id="XKMS_2_0_Section_3_3_1" shape="rect">3.3.1</a> <a name="ElementResultAbstractType" id="ElementResultAbstractType" shape="rect">Element <span class="ID">&lt;Result&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_114" id="XKMS_2_0_Paragraph_114" class="markParagraph" shape="rect">[114]</a>The <span class="ID">ResultType</span> type is
the type from which all XKMS response element types are derived. The <span class="ID">ResultType</span>&#xA0; type inherits the element and attributes
of the <span class="ID">MessageAbstractType</span> abstract type and in
addition contains the following attributes</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;RequestSignatureValue&gt;</b></span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>The value of the ds:SignatureValue element of the corresponding
        request.</dd>
    <dt><span class="ID"><b>ResultMajor</b></span>&nbsp;&nbsp;&nbsp;[Required]</dt>
      <dd>The most significant component of the result code.</dd>
    <dt><span class="ID"><b>ResultMinor</b></span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>The least significant component of the result code.</dd>
    <dt><span class="ID">RequestId</span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>The unique identifier <span class="ID">Id</span> specified in the
        request.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_115" id="XKMS_2_0_Paragraph_115" class="markParagraph" shape="rect">[115]</a>If the <span class="ID">MajorResult</span>
value has the value <span class="ID">Represent</span> the <span class="ID">Nonce</span> attribute MUST be present and
MUST NOT be the empty string.</p>

<p><a name="XKMS_2_0_Paragraph_116" id="XKMS_2_0_Paragraph_116" class="markParagraph" shape="rect">[116]</a>The <span class="ID">&lt;Result&gt;</span>
element is returned in response to an XKMS request if and only if the service
cannot return a more specific result element that inherits from the <span class="ID">ResultType</span>. For example if a request is made for the status
of a pending request whose identifier is unknown to the service.</p>

<p><a name="XKMS_2_0_Paragraph_117" id="XKMS_2_0_Paragraph_117" class="markParagraph" shape="rect">[117]</a> <b>Security Consideration:</b> Care must be
taken when signing responses to ensure that the service does not provide a
signing oracle, that is sign messages whose content is guessable by an
attacker. Implementations MUST ensure that response messages contain a
sufficient quantity of&#xA0; unpredictable data such as a pseudo-randomly
chosen <span class="ID">Id</span> attribute. For more information see the
section <a href="#SecurityConsiderations" shape="rect">Security Considerations</a>.</p>

<p><a name="XKMS_2_0_Paragraph_118" id="XKMS_2_0_Paragraph_118" class="markParagraph" shape="rect">[118]</a>The following schema defines the <span class="ID">&lt;Result&gt;</span> element and
<span class="ID">ResultType</span> type:</p>
<!-- Include file -->

<pre class="Code" xml:space="preserve">&lt;!-- ResultType --&gt;
&lt;element name="Result" type="xkms:ResultType"/&gt;
     &lt;simpleType name="ResultMajorEnum"&gt;
          &lt;restriction base="anyURI"&gt;
               &lt;enumeration value="http://www.w3.org/2002/03/xkms#Success"/&gt;
               &lt;enumeration value="http://www.w3.org/2002/03/xkms#VersionMismatch"/&gt;
               &lt;enumeration value="http://www.w3.org/2002/03/xkms#Sender"/&gt;
               &lt;enumeration value="http://www.w3.org/2002/03/xkms#Receiver"/&gt;
               &lt;enumeration value="http://www.w3.org/2002/03/xkms#Represent"/&gt;
               &lt;enumeration value="http://www.w3.org/2002/03/xkms#Pending"/&gt;
          &lt;/restriction&gt;
     &lt;/simpleType&gt;
     &lt;simpleType name="ResultMajorOpenEnum"&gt;
          &lt;union memberTypes="xkms:ResultMajorEnum anyURI"/&gt;
     &lt;/simpleType&gt;
     &lt;simpleType name="ResultMinorEnum"&gt;
          &lt;restriction base="anyURI"&gt;
             &lt;enumeration value="http://www.w3.org/2002/03/xkms#NoMatch"/&gt;
             &lt;enumeration value="http://www.w3.org/2002/03/xkms#TooManyResponses"/&gt;
             &lt;enumeration value="http://www.w3.org/2002/03/xkms#Incomplete"/&gt;
             &lt;enumeration value="http://www.w3.org/2002/03/xkms#Failure"/&gt;
             &lt;enumeration value="http://www.w3.org/2002/03/xkms#Refused"/&gt;
             &lt;enumeration value="http://www.w3.org/2002/03/xkms#NoAuthentication"/&gt;
             &lt;enumeration 
                 value="http://www.w3.org/2002/03/xkms#MessageNotSupported"/&gt;
             &lt;enumeration value="http://www.w3.org/2002/03/xkms#UnknownResponseId"/&gt;
             &lt;enumeration value="http://www.w3.org/2002/03/xkms#RepresentRequired"/&gt;
             &lt;enumeration value="http://www.w3.org/2002/03/xkms#NotSynchronous"/&gt;
             &lt;enumeration 
                 value="http://www.w3.org/2002/03/xkms#OptionalElementNotSupported"/&gt;
             &lt;enumeration 
                 value="http://www.w3.org/2002/03/xkms#ProofOfPossessionRequired"/&gt;
             &lt;enumeration 
                 value="http://www.w3.org/2002/03/xkms#TimeInstantNotSupported"/&gt;
             &lt;enumeration 
                 value="http://www.w3.org/2002/03/xkms#TimeInstantOutOfRange"/&gt;
          &lt;/restriction&gt;
     &lt;/simpleType&gt;
     &lt;simpleType name="ResultMinorOpenEnum"&gt;
          &lt;union memberTypes="xkms:ResultMinorEnum anyURI"/&gt;
     &lt;/simpleType&gt;
     &lt;complexType name="ResultType"&gt;
        &lt;complexContent&gt;
          &lt;extension base="xkms:MessageAbstractType"&gt;
             &lt;sequence&gt;
                 &lt;element ref="xkms:RequestSignatureValue" minOccurs="0"/&gt;
             &lt;/sequence&gt;
             &lt;attribute name="ResultMajor" type="xkms:ResultMajorOpenEnum" 
                 use="required"/&gt;
             &lt;attribute name="ResultMinor" type="xkms:ResultMinorOpenEnum" 
                 use="optional"/&gt;
             &lt;attribute name="RequestId" type="NCName" use="optional"/&gt;
          &lt;/extension&gt;
        &lt;/complexContent&gt;
     &lt;/complexType&gt;
&lt;!-- /ResultType --&gt;</pre>

<h4><a name="XKMS_2_0_Section_3_3_1_1" id="XKMS_2_0_Section_3_3_1_1" shape="rect">3.3.1.1</a> <a name="ResultCodes" id="ResultCodes" shape="rect">Result Codes</a></h4>

<p><a name="XKMS_2_0_Paragraph_119" id="XKMS_2_0_Paragraph_119" class="markParagraph" shape="rect">[119]</a>Result codes consist of a major code and an
optional minor code. The major and minor codes are expressed as XML 
 <code>anyURI</code> types.
This specification uses the notation <i>ResultMajor</i><span class="ID">.</span><i>ResultMinor</i> to specify a result code. For example
the result code <span class="ID">Sender.NoMatch</span> indicates a <span class="ID">ResultMajor</span> code of <span class="ID">Sender</span> and a
<span class="ID">ResultMinor</span> code of <span class="ID">NoMatch</span>.</p>

<p><a name="XKMS_2_0_Paragraph_120" id="XKMS_2_0_Paragraph_120" class="markParagraph" shape="rect">[120]</a>The following <span class="ID">ResultMajor</span> codes are defined (the <span class="ID">anyURI</span> name entries are all prefixed with <span class="ID">http://www.w3.org/2002/03/xkms#</span>):</p>

<table width="100%" cellpadding="0" cellspacing="0" border="1">
  <tbody>
    <tr>
      <th width="164"><code>anyURI</code>
        Name</th>
      <th width="139">Final</th>
      <th width="1397">Description</th>
    </tr>
    <tr>
      <td valign="top" class="ID" width="164"><span class="ID">Success</span></td>
      <td width="139" align="center">Final</td>
      <td width="1397">The operation succeeded.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="164"><span class="ID">VersionMismatch</span></td>
      <td width="139" align="center">Final</td>
      <td width="1397">The service does not support the protocol version
        specified in the request.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="164"><span class="ID">Sender</span></td>
      <td width="139" align="center">Final</td>
      <td width="1397">An error occurred that was due to the message sent by
        the sender.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="164"><span class="ID">Receiver</span></td>
      <td width="139" align="center">Final</td>
      <td width="1397">An error occurred at the receiver.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="164"><span class="ID">Represent</span></td>
      <td width="139" align="center">Not Final</td>
      <td width="1397">The service has not acted on the request. In order for
        the request to be acted upon the request MUST be represented with the
        specified nonce in accordance with the two-phase protocol.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="164"><span class="ID">Pending</span></td>
      <td width="139" align="center">Not Final</td>
      <td width="1397">The request has been accepted for processing and the
        service will return the result asynchronously.</td>
    </tr>
  </tbody>
</table>

<p><a name="XKMS_2_0_Paragraph_121" id="XKMS_2_0_Paragraph_121" class="markParagraph" shape="rect">[121]</a>The <span class="ID">ResultMajor</span> codes
<span class="ID">Success</span>, <span class="ID">VersionMismatch</span>,
<span class="ID">Sender</span> and <span class="ID">Receiver</span> are
<i>Final</i>, that is the protocol has completed when the code is returned.
The <span class="ID">ResultMajor</span> codes <span class="ID">Represent</span> and <span class="ID">Pending</span> are <i>Not
Final</i> and indicate that further processing is necessary to receive the
result.</p>

<p><a name="XKMS_2_0_Paragraph_122" id="XKMS_2_0_Paragraph_122" class="markParagraph" shape="rect">[122]</a>The following <span class="ID">ResultMinor</span> codes are defined (the <span class="ID">anyURI</span> name entries are all prefixed with <span class="ID">http://www.w3.org/2002/03/xkms#</span>):</p>

<table width="100%" cellpadding="0" cellspacing="0" border="1">
  <tbody>
    <tr>
      <th width="152" valign="top"><code>anyURI</code> Name</th>
      <th width="114" valign="top">Possible Major Codes</th>
      <th width="664" valign="top">Description</th>
    </tr>
    <tr>
      <td valign="top" class="ID" rowspan="3" width="152"><span class="ID">NoMatch</span></td>
      <td valign="top" class="ID" width="114">&#xA0;-</td>
      <td valign="top" width="664">Generic Description: No match
        was found for the search prototype provided.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="114"><span class="ID">Success</span></td>
      <td valign="top" width="664">The result code <span class="ID">Success.NoMatch</span> indicates that the service is
        authoritative for the search prototype specified and that the service
        positively asserts that no matches exist.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="114"><span class="ID">Receiver</span></td>
      <td valign="top" width="664">The result code <span class="ID">Receiver.NoMatch</span> indicates that the service is not
        authoritative for the search prototype provided.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" rowspan="3" width="152"><span class="ID">TooManyResponses</span></td>
      <td>&nbsp;-</td>
      <td valign="top" width="664">Generic Description: The request
        resulted in the number of responses that exceeded either&#xA0; the
        <span class="ID">ResponseLimit</span> value specified in the request
        or some other limit determined by the service. The service MAY either
        return a subset of the possible responses or none at all.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="114"><span class="ID">Success</span></td>
      <td valign="top" width="664">The service has returned one or more
        responses that represent a subset of the possible responses.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="114"><span class="ID">Receiver</span></td>
      <td valign="top" width="664">The service has returned no responses.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="152"><span class="ID">Incomplete</span></td>
      <td valign="top" class="ID" width="114"><span class="ID">Success</span></td>
      <td valign="top" width="664">Only part of the information requested
        could be provided.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" rowspan="3" width="152"><span class="ID">Failure</span></td>
      <td valign="top" width="114">&#xA0; -</td>
      <td valign="top" width="664">Generic Description: The service
        attempted to perform the request but the operation failed for
        unspecified reasons.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="114"><span class="ID">Sender</span></td>
      <td valign="top" width="664">The reason for failure is attributed to
        the sender (e.g., the request failed schema validation).</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="114"><span class="ID">Receiver</span></td>
      <td valign="top" width="664">The reason for failure is attributed to
        the receiver (e.g., a database lookup failed).</td>
    </tr>
    <tr>
      <td valign="top" class="ID" rowspan="3" width="152"><span class="ID">Refused</span></td>
      <td valign="top" width="114">&#xA0; -</td>
      <td valign="top" width="664">Generic Description: The
        operation was refused. The service did not attempt to perform the
        request.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="114"><span class="ID">Sender</span></td>
      <td valign="top" width="664">The sender failed to provide sufficient
        information to authenticate or authorize the request (e.g., payment
        not supplied).</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="114"><span class="ID">Receiver</span></td>
      <td valign="top" width="664">The receiver is currently refusing certain
        requests for unspecified reasons.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="152"><span class="ID">NoAuthentication</span></td>
      <td valign="top" class="ID" width="114"><span class="ID">Sender</span></td>
      <td valign="top" width="664">The operation was refused because the
        necessary authentication information was incorrect or missing.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="152"><span class="ID">MessageNotSupported</span></td>
      <td valign="top" class="ID" width="114"><span class="ID">Sender</span></td>
      <td valign="top" width="664">The receiver does not implement the
        specified operation.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="152"><span class="ID">UnknownResponseId</span></td>
      <td valign="top" class="ID" width="114"><span class="ID">Sender</span></td>
      <td valign="top" width="664">The ResponseId for which pending status
        was requested is unknown to the service.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="152"><span class="ID">RepresentRequired</span></td>
      <td valign="top" class="ID" width="114"><span class="ID">Sender</span></td>
      <td valign="top" width="664">The responder requires that the sender
        offer the represent protocol option in order to process the
      request.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="152"><span class="ID">NotSynchronous</span></td>
      <td valign="top" class="ID" width="114"><span class="ID">Receiver</span></td>
      <td valign="top" width="664">The receiver does not support synchronous
        processing of this type of request.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="152"><span class="ID">OptionalElementNotSupported</span></td>
      <td valign="top" class="ID" width="114"><span class="ID">Receiver</span></td>
      <td valign="top" width="664">The receiver has refused the
        operation because it does not support the OPTIONAL Element value
        present in the request.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="152"><span class="ID">ProofOfPossessionRequired</span></td>
      <td valign="top" class="ID" width="114"><span class="ID">Sender</span></td>
      <td valign="top" width="664">The receiver has refused the
        operation because it requires the sender to include
        the <span class="ID">ProofOfPossession</span> element in the
        request.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="152"><span class="ID">TimeInstantNotSupported</span></td>
      <td valign="top" class="ID" width="114"><span class="ID">Receiver</span></td>
      <td valign="top" width="664">The receiver has refused the
        operation because it does not support
        the <span class="ID">TimeInstant</span> element.</td>
    </tr>
    <tr>
      <td valign="top" class="ID" width="152"><span class="ID">TimeInstantOutOfRange</span></td>
      <td valign="top" class="ID" width="114"><span class="ID">Sender</span></td>
      <td valign="top" width="664">The receiver has refused the
        operation because the indicated time is outside the range that it
        responds to.</td>
    </tr>
  </tbody>
</table>

<h3><a name="XKMS_2_0_Section_3_3_2" id="XKMS_2_0_Section_3_3_2" shape="rect">3.3.2</a> <a name="ElementRequestSignatureValue" id="ElementRequestSignatureValue" shape="rect">Element
<span class="ID">&lt;RequestSignatureValue&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_123" id="XKMS_2_0_Paragraph_123" class="markParagraph" shape="rect">[123]</a>The <span class="ID">&lt;RequestSignatureValue&gt;</span> element in a response
contains the value of the base64 encoded value from the <span class="ID">&lt;ds:SignatureValue&gt;</span> content within the <span class="ID">&lt;ds:Signature&gt;</span> block in the corresponding request. If
the response is signed this provides a cryptographic linkage between the
request and the response.</p>

<p><a name="XKMS_2_0_Paragraph_124" id="XKMS_2_0_Paragraph_124" class="markParagraph" shape="rect">[124]</a>A service SHOULD include the <span class="ID">&lt;RequestSignatureValue&gt;</span> element in a response if the
following conditions are satisfied and MUST NOT include the value
otherwise:</p>
<ul>
  <li>The <span class="ID">&lt;ds:Signature&gt;</span> element was present in the corresponding
    request,</li>
  <li>The service successfully verified the <span class="ID">&lt;ds:Signature&gt;</span> element in
    the corresponding request, and</li>
  <li>The <span class="ID">ResponseMechanism</span> <span class="ID">RequestSignatureValue</span>
        was specified.</li>
</ul>

<p><a name="XKMS_2_0_Paragraph_125" id="XKMS_2_0_Paragraph_125" class="markParagraph" shape="rect">[125]</a>If the <span class="ID">&lt;RequestSignatureValue&gt;</span> element is present in a
response the requestor MUST reject the message if either:</p>
<ul>
  <li>The corresponding request was not authenticated, or</li>
  <li>The content of the <span class="ID">&lt;ds:SignatureValue&gt;</span> element used in the 
    request does not match the content of the <span class="ID">&lt;RequestSignatureValue&gt;</span>
    element in the response.</li>
</ul>

<p><a name="XKMS_2_0_Paragraph_126" id="XKMS_2_0_Paragraph_126" class="markParagraph" shape="rect">[126]</a>The <span class="ID">&lt;RequestSignatureValue&gt;</span> element is of <span class="ID">ds:SignatureValueType</span> type specified in the XML Signature
specification <a href="#XML-SIG" shape="rect">[XML-SIG]</a>.</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- RequestSignatureValue --&gt;
   &lt;element name="RequestSignatureValue" type="ds:SignatureValueType"/&gt;
   &lt;!-- /RequestSignatureValue --&gt;</pre>

<h2><a name="XKMS_2_0_Section_3_4" id="XKMS_2_0_Section_3_4" shape="rect">3.4</a> Compound
Requests</h2>

<p><a name="XKMS_2_0_Paragraph_127" id="XKMS_2_0_Paragraph_127" class="markParagraph" shape="rect">[127]</a>The compound request mechanism allows multiple
requests and the corresponding responses to be sent in a single request
message. This allows considerable processing resources to be saved as a
single signature on the compound message may be used in place of multiple
signatures on the individual requests or responses. There are no constraints
on the type of request that may be made within a single compound request. A
compound request may contain multiple instances of the same type of request,
a mixture of different types of request or both.</p>

<h3><a name="XKMS_2_0_Section_3_4_1" id="XKMS_2_0_Section_3_4_1" shape="rect">3.4.1</a> <a name="ElementCompoundRequest" id="ElementCompoundRequest" shape="rect">Element <span class="ID">&lt;CompoundRequest&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_128" id="XKMS_2_0_Paragraph_128" class="markParagraph" shape="rect">[128]</a>The <span class="ID">&lt;CompoundRequest&gt;</span> element is used to issue multiple
requests at the same time. The <span class="ID">&lt;CompoundRequest&gt;</span> element inherits the element and
attributes of 
<span class="ID">RequestAbstractType</span> together with the
following elements in any order:</p>

<blockquote>
  <dl>
    <dt><span class="ID">&lt;LocateRequest&gt;</span>&nbsp;&nbsp;&nbsp;[Any Number]</dt>
      <dd>An XKMS <span class="ID">Locate</span> Request</dd>
    <dt><span class="ID">&lt;ValidateRequest&gt;</span>&nbsp;&nbsp;&nbsp;[Any Number]</dt>
      <dd>An XKMS <span class="ID">Validate</span> Request.</dd>
    <dt><span class="ID">&lt;RegisterRequest&gt;</span>&nbsp;&nbsp;&nbsp;[Any Number]</dt>
      <dd>An XKMS <span class="ID">Register</span> Request.</dd>
    <dt><span class="ID">&lt;ReissueRequest&gt;</span>&nbsp;&nbsp;&nbsp;[Any Number]</dt>
      <dd>An XKMS <span class="ID">Reissue</span> Request.</dd>
    <dt><span class="ID">&lt;RecoverRequest&gt;</span>&nbsp;&nbsp;&nbsp;[Any Number]</dt>
      <dd>An XKMS <span class="ID">Recover</span> Request.</dd>
    <dt><span class="ID">&lt;RevokeRequest&gt;</span>&nbsp;&nbsp;&nbsp;[Any Number]</dt>
      <dd>An XKMS <span class="ID">Revoke</span> Request.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_128a" id="XKMS_2_0_Paragraph_128a" class="markParagraph" shape="rect">[128a]</a>The <span class="ID">RespondWith</span> element MUST NOT be a direct child of a <span class="ID">CompoundRequest</span> element. Each request that is encapsulated inside a <span class="ID">CompoundRequest</span> element may or may not have its own <span class="ID">RespondWith</span> element child.</p>

<p><a name="XKMS_2_0_Paragraph_129" id="XKMS_2_0_Paragraph_129" class="markParagraph" shape="rect">[129]</a>The following schema defines the <span class="ID">&lt;CompoundRequest&gt;</span> element and <span class="ID">CompoundRequestType</span> type:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- CompoundRequest --&gt;
   &lt;element name="CompoundRequest" type="xkms:CompoundRequestType"/&gt;
   &lt;complexType name="CompoundRequestType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:RequestAbstractType"&gt;
            &lt;choice maxOccurs="unbounded"&gt;
               &lt;element ref="xkms:LocateRequest"/&gt;
               &lt;element ref="xkms:ValidateRequest"/&gt;
               &lt;element ref="xkms:RegisterRequest"/&gt;
               &lt;element ref="xkms:ReissueRequest"/&gt;
               &lt;element ref="xkms:RecoverRequest"/&gt;
               &lt;element ref="xkms:RevokeRequest"/&gt;
            &lt;/choice&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /CompoundRequest --&gt;</pre>

<h3><a name="XKMS_2_0_Section_3_4_2" id="XKMS_2_0_Section_3_4_2" shape="rect">3.4.2</a> <a name="ElementCompoundResult" id="ElementCompoundResult" shape="rect">Element <span class="ID">&lt;CompoundResult&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_130" id="XKMS_2_0_Paragraph_130" class="markParagraph" shape="rect">[130]</a>The <span class="ID">&lt;CompoundResult&gt;</span> element is used to respond to a
<span class="ID">&lt;CompoundRequest&gt;</span>. If the compound result has
the <span class="ID">MajorResult</span> value <span class="ID">Success</span> it contains multiple responses corresponding to
the multiple requests specified in the <span class="ID">&lt;CompoundRequest&gt;</span>. The <span class="ID">&lt;CompoundResult&gt;</span> element inherits the element and
attributes of <span class="ID">ResultType</span> together with the following
additional elements in any order:</p>

<blockquote>
  <dl>
    <dt><span class="ID">&lt;LocateResult&gt;</span>&nbsp;&nbsp;&nbsp;[Any Number]</dt>
      <dd>An XKMS <span class="ID">Locate</span> Result.</dd>
    <dt><span class="ID">&lt;ValidateResult&gt;</span>&nbsp;&nbsp;&nbsp;[Any Number]</dt>
      <dd>An XKMS <span class="ID">Validate</span> Result.</dd>
    <dt><span class="ID">&lt;RegisterResult&gt;</span>&nbsp;&nbsp;&nbsp;[Any Number]</dt>
      <dd>An XKMS <span class="ID">Register</span> Result.</dd>
    <dt><span class="ID">&lt;ReissueResult&gt;</span>&nbsp;&nbsp;&nbsp;[Any Number]</dt>
      <dd>An XKMS <span class="ID">Reissue</span> Result.</dd>
    <dt><span class="ID">&lt;RecoverResult&gt;</span>&nbsp;&nbsp;&nbsp;[Any Number]</dt>
      <dd>An XKMS <span class="ID">Recover</span> Result.</dd>
    <dt><span class="ID">&lt;RevokeResult&gt;</span>&nbsp;&nbsp;&nbsp;[Any Number]</dt>
      <dd>An XKMS <span class="ID">Revoke</span> Result.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_131" id="XKMS_2_0_Paragraph_131" class="markParagraph" shape="rect">[131]</a>The following schema defines the <span class="ID">&lt;CompoundResult&gt;</span> element and <span class="ID">CompoundResultType</span> type:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- CompoundResult --&gt;
   &lt;element name="CompoundResult" type="xkms:CompoundResultType"/&gt;
   &lt;complexType name="CompoundResultType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:ResultType"&gt;
            &lt;choice minOccurs="0" maxOccurs="unbounded"&gt;
               &lt;element ref="xkms:LocateResult"/&gt;
               &lt;element ref="xkms:ValidateResult"/&gt;
               &lt;element ref="xkms:RegisterResult"/&gt;
               &lt;element ref="xkms:ReissueResult"/&gt;
               &lt;element ref="xkms:RecoverResult"/&gt;
               &lt;element ref="xkms:RevokeResult"/&gt;
            &lt;/choice&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /CompoundResult --&gt;</pre>

<h2><a name="XKMS_2_0_Section_3_5" id="XKMS_2_0_Section_3_5" shape="rect">3.5</a> Status
Request</h2>

<h3><a name="XKMS_2_0_Section_3_5_1" id="XKMS_2_0_Section_3_5_1" shape="rect">3.5.1</a> <a name="ElementStatusRequest" id="ElementStatusRequest" shape="rect">Element <span class="ID">&lt;StatusRequest&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_132" id="XKMS_2_0_Paragraph_132" class="markParagraph" shape="rect">[132]</a>The <span class="ID">StatusRequest</span>
element is used to request that the service return the status of a pending
request by means of a <span class="ID">&lt;StatusResult&gt;</span> element.
The <span class="ID">StatusRequest</span> element inherits the element and attributes
of <span class="ID">PendingRequestType</span>.
The <span class="ID">RespondWith</span> element MUST NOT be present
inside a <span class="ID">StatusRequest</span> element.</p>



<p><a name="XKMS_2_0_Paragraph_133" id="XKMS_2_0_Paragraph_133" class="markParagraph" shape="rect">[133]</a>The following schema defines the <span class="ID">StatusRequest</span> element and <span class="ID">StatusRequestType</span> type:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- StatusRequest --&gt;
   &lt;element name="StatusRequest" type="xkms:StatusRequestType"/&gt;
   &lt;complexType name="StatusRequestType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:PendingRequestType"/&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /StatusRequest --&gt;</pre>

<h3><a name="XKMS_2_0_Section_3_5_2" id="XKMS_2_0_Section_3_5_2" shape="rect">3.5.2</a> <a name="ElementStatusResult" id="ElementStatusResult" shape="rect">Element <span class="ID">&lt;StatusResult&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_134" id="XKMS_2_0_Paragraph_134" class="markParagraph" shape="rect">[134]</a>The <span class="ID">&lt;StatusResult&gt;</span> element returns the status of a
pending request. In the case of a non-compound request, the status is indicated in the
<span class="ID">ResultMajor</span> attribute. For a compound request, the status
of each of the inner compound requests is indicated with three different optional
attributes, defined here below.</p>

<p><a name="XKMS_2_0_Paragraph_134" id="XKMS_2_0_Paragraph_134a"
class="markParagraph" shape="rect">[134a]</a>The <span
class="ID">StatusResultType</span> inherits the element and attributes
of <span class="ID">ResultType</span> and contains the following
additional attributes for reporting the status of compound
requests:</p>

<blockquote>
  <dl>
    <dt><span class="ID">Success</span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>In the case of a compound request the number of inner compound
        operations that completed with status Success. 
      </dd>
    <dt><span class="ID">Failure</span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>In the case of a compound request the number of inner compound
        operations that completed with status other than Success. 
      </dd>
    <dt><span class="ID">Pending</span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>In the case of a compound request the number of inner compound
        operations that are still pending. 
      </dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_135" id="XKMS_2_0_Paragraph_135" class="markParagraph" shape="rect">[135]</a>The following schema defines the <span class="ID">StatusResult</span> element and <span class="ID">StatusResultType</span> type:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- StatusResult --&gt;
   &lt;element name="StatusResult" type="xkms:StatusResultType"/&gt;
   &lt;complexType name="StatusResultType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:ResultType"&gt;
            &lt;attribute name="Success" type="integer" use="optional"/&gt;
            &lt;attribute name="Failure" type="integer" use="optional"/&gt;
            &lt;attribute name="Pending" type="integer" use="optional"/&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /StatusResult --&gt;</pre>

<h1><a name="XKMS_2_0_Section_4" id="XKMS_2_0_Section_4" shape="rect">4</a> <a name="KeyInformationServiceOverview" id="KeyInformationServiceOverview" shape="rect">Key
Information Service Description</a></h1>

<p><a name="XKMS_2_0_Paragraph_136" id="XKMS_2_0_Paragraph_136" class="markParagraph" shape="rect">[136]</a>In the XML Signature Specification <a href="#XML-SIG" shape="rect">[XML-SIG]</a>, a signer may optionally include information
about his public signing key ("<span class="ID">&lt;ds:KeyInfo&gt;</span>")
within the signature block. This key information is designed to allow the
signer to communicate "hints" to a verifier about which public&#xA0;key to
select.</p>

<p><a name="XKMS_2_0_Paragraph_137" id="XKMS_2_0_Paragraph_137" class="markParagraph" shape="rect">[137]</a>Another important property of <span class="ID">&lt;ds:KeyInfo&gt;</span> is that it may or may not be
cryptographically bound to the signature itself.&#xA0; This allows the <span class="ID">&lt;ds:KeyInfo&gt;</span> to be substituted or supplemented
without "breaking" the digital signature.</p>

<p><a name="XKMS_2_0_Paragraph_138" id="XKMS_2_0_Paragraph_138" class="markParagraph" shape="rect">[138]</a>For example Alice signs a document and sends
it to Bob with a <span class="ID">&lt;ds:KeyInfo&gt;</span> element that
specifies only the signing key data. On receiving the message Bob retrieves
additional information required to validate the signature and adds this
information into the <span class="ID">&lt;ds:KeyInfo&gt;</span> element when
he passes the document on to Carol (see Figure 1 below).</p>

<p class="caption"><a name="XKMS_2_0_Paragraph_139" id="XKMS_2_0_Paragraph_139" class="markParagraph" shape="rect">[139]</a> <img alt="Substitution of the ds:KeyInfo element as a message is passed amongst processors." src="Images/image002.gif" width="420" height="372" /></p>

<p class="caption"><a name="XKMS_2_0_Paragraph_140" id="XKMS_2_0_Paragraph_140" class="markParagraph" shape="rect">[140]</a> <a id="Figure1" name="Figure1" shape="rect">Figure 1: Substitution of the <span class="ID">&lt;ds:KeyInfo&gt;</span> element as a message is passed amongst
processors</a></p>

<h2><a name="XKMS_2_0_Section_4_1" id="XKMS_2_0_Section_4_1" shape="rect">4.1</a> <a name="XKISSLocateService" id="XKISSLocateService" shape="rect">Locate
Service</a></h2>

<p><a name="XKMS_2_0_Paragraph_141" id="XKMS_2_0_Paragraph_141" class="markParagraph" shape="rect">[141]</a>The X-KISS <span class="ID">Locate</span>
service resolves a <span class="ID">&lt;ds:Keyinfo&gt;</span> element but
does NOT REQUIRE the service to make an assertion concerning the validity of
the binding between the data in the <span class="ID">&lt;ds:Keyinfo&gt;</span> element.</p>

<p><a name="XKMS_2_0_Paragraph_142" id="XKMS_2_0_Paragraph_142" class="markParagraph" shape="rect">[142]</a>The XKMS service MAY resolve the <span class="ID">&lt;ds:Keyinfo&gt;</span> element using local data or MAY relay
request to other servers. For example the XKMS service might resolve a <span class="ID">&lt;ds:RetrievalMethod&gt;</span> element (Figure 2) or act as a
gateway to an underlying PKI based on a non-XML syntax.</p>

<p class="center"><a name="XKMS_2_0_Paragraph_143" id="XKMS_2_0_Paragraph_143" class="markParagraph" shape="rect">[143]</a> <img alt="Diagram shows protocol exchange between a client, a trust service and a remote server (Server A). " src="Images/image006.gif" border="0" width="576" height="244" /></p>

<p class="caption"><a name="XKMS_2_0_Paragraph_144" id="XKMS_2_0_Paragraph_144" class="markParagraph" shape="rect">[144]</a>Figure 2: Locate
Service Provides Name Resolution</p>

<p><a name="XKMS_2_0_Paragraph_145" id="XKMS_2_0_Paragraph_145" class="markParagraph" shape="rect">[145]</a>Both the request and/or the response MAY be
signed, to both authenticate the sender and protect the integrity of the data
being transmitted, using an XML Signature <a href="#XML-SIG" shape="rect">[XML-SIG]</a>.</p>

<h3><a name="XKMS_2_0_Section_4_1_1" id="XKMS_2_0_Section_4_1_1" shape="rect">4.1.1</a> <a name="ExampleDataEncryption" id="ExampleDataEncryption" shape="rect">Example: Data
Encryption</a></h3>

<p><a name="XKMS_2_0_Paragraph_146" id="XKMS_2_0_Paragraph_146" class="markParagraph" shape="rect">[146]</a>Alice wants to send an encrypted email to Bob
but does not know his encryption key. Alice can use both the S/MIME and PGP
secure email formats. Alice's client uses DNS to locate the XKMS service that
provides a Locate service for keys bound to the domain example.com
 then sends an XKMS Locate request to the discovered
XKMS service for a key bound to bob@example.com
 and the S/MIME or PGP protocol. The application
then verifies that the certificate obtained meets its trust criteria by
standard certificate validation to a trusted root.</p>

<p><a name="XKMS_2_0_Paragraph_147" id="XKMS_2_0_Paragraph_147" class="markParagraph" shape="rect">[147]</a>Request:</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;LocateRequest xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
      Id="I8fc9f97052a34073312b22a69b3843b6"
      Service="http://www.example.org/XKMS"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#KeyName&lt;/RespondWith&gt;
  &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#KeyValue&lt;/RespondWith&gt;
  &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#X509Cert&lt;/RespondWith&gt;
  &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#X509Chain&lt;/RespondWith&gt;
  &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#PGPWeb&lt;/RespondWith&gt;
  &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#PGP&lt;/RespondWith&gt;
  &lt;QueryKeyBinding&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Encryption&lt;/KeyUsage&gt;
    &lt;UseKeyWith Application="urn:ietf:rfc:2440"
          Identifier="bob@example.com" /&gt;
    &lt;UseKeyWith Application="urn:ietf:rfc:2633"
          Identifier="bob@example.com" /&gt;
  &lt;/QueryKeyBinding&gt;
&lt;/LocateRequest&gt;</pre>

<p><a name="XKMS_2_0_Paragraph_148" id="XKMS_2_0_Paragraph_148" class="markParagraph" shape="rect">[148]</a>Response:</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;LocateResult xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
      Id="I8ce3809ab23500015cc27704b7eb0912"
      Service="http://www.example.org/XKMS"
      ResultMajor="http://www.w3.org/2002/03/xkms#Success"
      RequestId="I8fc9f97052a34073312b22a69b3843b6"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;UnverifiedKeyBinding Id="I809ca03cf85b3cb466859694dbd0627d"&gt;
    &lt;ds:KeyInfo&gt;
      &lt;ds:KeyValue&gt;
        &lt;ds:RSAKeyValue&gt;
          &lt;ds:Modulus&gt;
            3FFtWUsvEajQt2SeSF+RvAxWdPPh5GSlQnp8SDvvqvCwE6PXcRWrIGmV7twNf2T
            UXCxYuztUUClMIy14B0Q+k1ej2nekmYL7+Ic3DDGVFVaYPoxaRY0Y2lV8tOreyn
            WegpFbITXc8V6Y02QfR5O7Pn1/10ElslaF/TF8MQGqYE8=
          &lt;/ds:Modulus&gt;
          &lt;ds:Exponent&gt;AQAB&lt;/ds:Exponent&gt;
        &lt;/ds:RSAKeyValue&gt;
      &lt;/ds:KeyValue&gt;
      &lt;ds:X509Data&gt;
        &lt;ds:X509Certificate&gt;
          MIICCTCCAXagAwIBAgIQe0Sk4xr1VolGFFNMkCx07TAJBgUrDgMCHQUAMBIxEDA
          OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMDUwODE1MDY1OTU5Wj
          AkMSIwIAYDVQQDExlCb2IgQmFrZXIgTz1Cb2IgQ29ycCBDPVVTMIGfMA0GCSqGS
          Ib3DQEBAQUAA4GNADCBiQKBgQDcUW1ZSy8RqNC3ZJ5IX5G8DFZ08+HkZKVCenxI
          O++q8LATo9dxFasgaZXu3A1/ZNRcLFi7O1RQKUwjLXgHRD6TV6Pad6SZgvv4hzc
          MMZUVVpg+jFpFjRjaVXy06t7KdZ6CkVshNdzxXpjTZB9Hk7s+fX/XQSWyVoX9MX
          wxAapgTwIDAQABo1YwVDANBgNVHQoEBjAEAwIGQDBDBgNVHQEEPDA6gBABpU6Rp
          UssqgWYs3fukLy6oRQwEjEQMA4GA1UEAxMHVGVzdCBDQYIQLgyd1ReM8bVNnFUq
          D4e60DAJBgUrDgMCHQUAA4GBAF4jP1gGDbaq3rg/Vo3JY7EDNTp0HmwLiPMLmdn
          B3WTIGFcjS/jZFzRCbvKPeiPTZ6kRkGgydFOuCo5HMAxIks/LtnKFd/0qYT+AOD
          q/rCrwSx+F+Ro2rf9tPpja9o7gANqxs6Pm7f1QSPZO57bT/6afiVm7NdaCfjgMp
          hb+XNyn
        &lt;/ds:X509Certificate&gt;
        &lt;ds:X509Certificate&gt;
          MIIB9zCCAWSgAwIBAgIQLgyd1ReM8bVNnFUqD4e60DAJBgUrDgMCHQUAMBIxEDA
          OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMTAwODE1MDcwMDAwWj
          ASMRAwDgYDVQQDEwdUZXN0IENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBg
          QCn23HHp+HtXpiyKVSDtdE3dO0r0oLB/H9sxUEkeXB8oMxwbhdcizWH92zrtm1V
          fVtxkfmwF14ZXoyDZHeZXuCOtAfz/mW6s2gmfD45TfFFVGksDGVRNK5XmKXA5sE
          C51RCvaxzGBdGDlCuVPqX7Cq3IcZpRU1IXbi5YzGwV7j6LwIDAQABo1YwVDANBg
          NVHQoEBjAEAwIHgDBDBgNVHQEEPDA6gBABpU6RpUssqgWYs3fukLy6oRQwEjEQM
          A4GA1UEAxMHVGVzdCBDQYIQLgyd1ReM8bVNnFUqD4e60DAJBgUrDgMCHQUAA4GB
          ABDYD4Fwx2dscu+BgYcZ+GoQQtCJkwJEXytb4zlNl7HLFKbXSw4m0blQquIsfsi
          QgFYAQBXSbu7aeUqqmSGHvILu3BGwVOKjxbHfcM4/MefuTtpOpCN40wy3YwwngD
          tHTaIqm8NwS966PE+W9f8kD70q5FNwf+GF/lX9qGc/x435
        &lt;/ds:X509Certificate&gt;
      &lt;/ds:X509Data&gt;
    &lt;/ds:KeyInfo&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/KeyUsage&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Encryption&lt;/KeyUsage&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Exchange&lt;/KeyUsage&gt;
    &lt;UseKeyWith Application="urn:ietf:rfc:2633"
          Identifier="bob@example.com" /&gt;
  &lt;/UnverifiedKeyBinding&gt;
&lt;/LocateResult&gt;</pre>

<h3><a name="XKMS_2_0_Section_4_1_2" id="XKMS_2_0_Section_4_1_2" shape="rect">4.1.2</a> <a name="ExampleDocumentSignature" id="ExampleDocumentSignature" shape="rect">Example:
Document Signature</a></h3>

<p><a name="XKMS_2_0_Paragraph_149" id="XKMS_2_0_Paragraph_149" class="markParagraph" shape="rect">[149]</a>Bob receives the signed document from Alice
which specifies Alice's X.509v3 certificate but not the key value. Bob's
email client is not capable of processing X.509v3 certificates but can obtain
the key parameters from the XKMS service by means of the Locate service.
Bob's email client sends the <span class="ID">&lt;ds:Keyinfo&gt;</span>
element to the location service requesting that the
 corresponding <span class="ID">&lt;KeyValue&gt;</span> element be returned.</p>

<p><a name="XKMS_2_0_Paragraph_150" id="XKMS_2_0_Paragraph_150" class="markParagraph" shape="rect">[150]</a>Request:</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;LocateRequest xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
      Id="I045c66f6c525a9bf3842ecd3466cd422"
      Service="http://www.example.org/XKMS"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#KeyValue&lt;/RespondWith&gt;
  &lt;QueryKeyBinding&gt;
    &lt;ds:KeyInfo&gt;
      &lt;ds:X509Data&gt;
        &lt;ds:X509Certificate&gt;
          MIICEDCCAX2gAwIBAgIQimXeUAxYJbJMady9vV1bLjAJBgUrDgMCHQUAMBIxEDA
          OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMDUwODE1MDY1OTU5Wj
          ArMSkwJwYDVQQDEyBBbGljZSBBYXJkdmFyayBPPUFsaWNlIENvcnAgQz1VUzCBn
          zANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0nIsmR+aVW2egl5MIfOKy4HuMKkk
          9AZ/IQuDLVPlhzOfgngjVQCjr8uvmnqtNu8HBupui8LgGthO6U9D0CNT5mbmhIA
          ErRADUMIAFsi7LzBarUvNWTqYNEJmcHsAUZdrdcDrkNnG7SzbuJx+GDNiHKVDQg
          gPBLc1XagW20RMvokCAwEAAaNWMFQwDQYDVR0KBAYwBAMCBkAwQwYDVR0BBDwwO
          oAQAaVOkaVLLKoFmLN37pC8uqEUMBIxEDAOBgNVBAMTB1Rlc3QgQ0GCEC4MndUX
          jPG1TZxVKg+HutAwCQYFKw4DAh0FAAOBgQABU91ka7IlkXCfv4Zh2Ohwgg2yObt
          Y3+6C/BTFGrOEBJDy+DoxJ/NuBF18w3rrrR18xE6jNKYLCQb8zUGk4QOG5Y+HT/
          QTTFvWkiOLXcpTuhnOhXatr42FoYpDkjx2QWK+J5Q2l/Rgjgc/0ZV8U/kD8UuRk
          Xp4AZh7QsiX8AcO0w==
        &lt;/ds:X509Certificate&gt;
      &lt;/ds:X509Data&gt;
    &lt;/ds:KeyInfo&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/KeyUsage&gt;
  &lt;/QueryKeyBinding&gt;
&lt;/LocateRequest&gt;</pre>

<p><a name="XKMS_2_0_Paragraph_151" id="XKMS_2_0_Paragraph_151" class="markParagraph" shape="rect">[151]</a>The location service extracts the X.509v3
certificate from the <span class="ID">&lt;ds:Keyinfo&gt;</span> element and
returns the key values. The location service DOES NOT report the revocation
status or the trustworthiness of the certificate.</p>

<p><a name="XKMS_2_0_Paragraph_152" id="XKMS_2_0_Paragraph_152" class="markParagraph" shape="rect">[152]</a>Response:</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;LocateResult xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
      Id="I04cd4f17d0656413d744f55488369264"
      Service="http://www.example.org/XKMS"
      ResultMajor="http://www.w3.org/2002/03/xkms#Success"
      RequestId="I045c66f6c525a9bf3842ecd3466cd422"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;UnverifiedKeyBinding Id="I012f61e1d7b7b9944fe8d954bcb2d946"&gt;
    &lt;ds:KeyInfo&gt;
      &lt;ds:KeyValue&gt;
        &lt;ds:RSAKeyValue&gt;
          &lt;ds:Modulus&gt;
            0nIsmR+aVW2egl5MIfOKy4HuMKkk9AZ/IQuDLVPlhzOfgngjVQCjr8uvmnqtNu8
            HBupui8LgGthO6U9D0CNT5mbmhIAErRADUMIAFsi7LzBarUvNWTqYNEJmcHsAUZ
            drdcDrkNnG7SzbuJx+GDNiHKVDQggPBLc1XagW20RMvok=
          &lt;/ds:Modulus&gt;
          &lt;ds:Exponent&gt;AQAB&lt;/ds:Exponent&gt;
        &lt;/ds:RSAKeyValue&gt;
      &lt;/ds:KeyValue&gt;
    &lt;/ds:KeyInfo&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/KeyUsage&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Encryption&lt;/KeyUsage&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Exchange&lt;/KeyUsage&gt;
    &lt;UseKeyWith Application="urn:ietf:rfc:2633"
          Identifier="alice@example.com" /&gt;
  &lt;/UnverifiedKeyBinding&gt;
&lt;/LocateResult&gt;</pre>

<h2><a name="XKMS_2_0_Section_4_2" id="XKMS_2_0_Section_4_2" shape="rect">4.2</a> <a name="XKISSValidateService" id="XKISSValidateService" shape="rect">Validate
Service</a></h2>

<p><a name="XKMS_2_0_Paragraph_153" id="XKMS_2_0_Paragraph_153" class="markParagraph" shape="rect">[153]</a>The X-KISS Validate Service allows all that the
Locate Service does, and in addition, the client may obtain an assertion
specifying the status of the binding between the public key and other data,
for example a name or a set of extended attributes. Furthermore the service
represents that the status of each of the data elements returned is valid and
that all are bound to the same public key. The client sends to the XKMS
service a prototype containing some or all of the elements for which the
status of the key binding is required. If the information in the prototype is
incomplete, the XKMS service MAY obtain additional data required from an
underlying PKI Service. Once the validity of the key binding has been
determined the XKMS service returns the status result to the client (Figure
3).</p>

<p class="center"><a name="XKMS_2_0_Paragraph_154" id="XKMS_2_0_Paragraph_154" class="markParagraph" shape="rect">[154]</a> <img alt="Diagram shows a trust service acting as a gateway to 'PKI services'" src="Images/image008.gif" border="0"  /></p>

<p class="caption"><a name="XKMS_2_0_Paragraph_155" id="XKMS_2_0_Paragraph_155" class="markParagraph" shape="rect">[155]</a> <a id="FigureTier2" name="FigureTier2" shape="rect">Figure 3: Validate Service Provides Key
Validation</a></p>

<h3><a name="XKMS_2_0_Section_4_2_1" id="XKMS_2_0_Section_4_2_1" shape="rect">4.2.1</a> <a name="ExampleDocumentSignature2" id="ExampleDocumentSignature2" shape="rect">Example:
Document Signature</a></h3>

<p><a name="XKMS_2_0_Paragraph_156" id="XKMS_2_0_Paragraph_156" class="markParagraph" shape="rect">[156]</a>Bob has received Alice's message and his email
client has verified the signature on the document against the public key in
the certificate supplied by Alice. It is not yet known whether the
certificate is considered trustworthy however. To determine this, Bob's email
client sends the certificate chain to an XKMS Validate service. The service
reports back that it has successfully determined that the key binding has a
trusted issuer and has not been revoked.</p>

<p><a name="XKMS_2_0_Paragraph_157" id="XKMS_2_0_Paragraph_157" class="markParagraph" shape="rect">[157]</a>Request:</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;ValidateRequest xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
      Id="Ie26380bfeb9d0c5bc526d5213a162d46"
      Service="http://www.example.org/XKMS"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#X509Cert&lt;/RespondWith&gt;
  &lt;QueryKeyBinding&gt;
    &lt;ds:KeyInfo&gt;
      &lt;ds:X509Data&gt;
        &lt;ds:X509Certificate&gt;
          MIICEDCCAX2gAwIBAgIQimXeUAxYJbJMady9vV1bLjAJBgUrDgMCHQUAMBIxEDA
          OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMDUwODE1MDY1OTU5Wj
          ArMSkwJwYDVQQDEyBBbGljZSBBYXJkdmFyayBPPUFsaWNlIENvcnAgQz1VUzCBn
          zANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0nIsmR+aVW2egl5MIfOKy4HuMKkk
          9AZ/IQuDLVPlhzOfgngjVQCjr8uvmnqtNu8HBupui8LgGthO6U9D0CNT5mbmhIA
          ErRADUMIAFsi7LzBarUvNWTqYNEJmcHsAUZdrdcDrkNnG7SzbuJx+GDNiHKVDQg
          gPBLc1XagW20RMvokCAwEAAaNWMFQwDQYDVR0KBAYwBAMCBkAwQwYDVR0BBDwwO
          oAQAaVOkaVLLKoFmLN37pC8uqEUMBIxEDAOBgNVBAMTB1Rlc3QgQ0GCEC4MndUX
          jPG1TZxVKg+HutAwCQYFKw4DAh0FAAOBgQABU91ka7IlkXCfv4Zh2Ohwgg2yObt
          Y3+6C/BTFGrOEBJDy+DoxJ/NuBF18w3rrrR18xE6jNKYLCQb8zUGk4QOG5Y+HT/
          QTTFvWkiOLXcpTuhnOhXatr42FoYpDkjx2QWK+J5Q2l/Rgjgc/0ZV8U/kD8UuRk
          Xp4AZh7QsiX8AcO0w==
        &lt;/ds:X509Certificate&gt;
        &lt;ds:X509Certificate&gt;
          MIIB9zCCAWSgAwIBAgIQLgyd1ReM8bVNnFUqD4e60DAJBgUrDgMCHQUAMBIxEDA
          OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMTAwODE1MDcwMDAwWj
          ASMRAwDgYDVQQDEwdUZXN0IENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBg
          QCn23HHp+HtXpiyKVSDtdE3dO0r0oLB/H9sxUEkeXB8oMxwbhdcizWH92zrtm1V
          fVtxkfmwF14ZXoyDZHeZXuCOtAfz/mW6s2gmfD45TfFFVGksDGVRNK5XmKXA5sE
          C51RCvaxzGBdGDlCuVPqX7Cq3IcZpRU1IXbi5YzGwV7j6LwIDAQABo1YwVDANBg
          NVHQoEBjAEAwIHgDBDBgNVHQEEPDA6gBABpU6RpUssqgWYs3fukLy6oRQwEjEQM
          A4GA1UEAxMHVGVzdCBDQYIQLgyd1ReM8bVNnFUqD4e60DAJBgUrDgMCHQUAA4GB
          ABDYD4Fwx2dscu+BgYcZ+GoQQtCJkwJEXytb4zlNl7HLFKbXSw4m0blQquIsfsi
          QgFYAQBXSbu7aeUqqmSGHvILu3BGwVOKjxbHfcM4/MefuTtpOpCN40wy3YwwngD
          tHTaIqm8NwS966PE+W9f8kD70q5FNwf+GF/lX9qGc/x435
        &lt;/ds:X509Certificate&gt;
      &lt;/ds:X509Data&gt;
    &lt;/ds:KeyInfo&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/KeyUsage&gt;
    &lt;UseKeyWith Application="urn:ietf:rfc:2633"
          Identifier="alice@example.com" /&gt;
  &lt;/QueryKeyBinding&gt;
&lt;/ValidateRequest&gt;</pre>

<p><a name="XKMS_2_0_Paragraph_158" id="XKMS_2_0_Paragraph_158" class="markParagraph" shape="rect">[158]</a>Response:</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;ValidateResult xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
      Id="I34ef61b96f7db2250c229d37a17edfc0"
      Service="http://www.example.org/XKMS"
      ResultMajor="http://www.w3.org/2002/03/xkms#Success"
      RequestId="Ie26380bfeb9d0c5bc526d5213a162d46"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;KeyBinding Id="Icf608e9e8b07468fde1b7ee5449fe831"&gt;
    &lt;ds:KeyInfo&gt;
      &lt;ds:X509Data&gt;
        &lt;ds:X509Certificate&gt;
          MIICEDCCAX2gAwIBAgIQimXeUAxYJbJMady9vV1bLjAJBgUrDgMCHQUAMBIxEDA
          OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMDUwODE1MDY1OTU5Wj
          ArMSkwJwYDVQQDEyBBbGljZSBBYXJkdmFyayBPPUFsaWNlIENvcnAgQz1VUzCBn
          zANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0nIsmR+aVW2egl5MIfOKy4HuMKkk
          9AZ/IQuDLVPlhzOfgngjVQCjr8uvmnqtNu8HBupui8LgGthO6U9D0CNT5mbmhIA
          ErRADUMIAFsi7LzBarUvNWTqYNEJmcHsAUZdrdcDrkNnG7SzbuJx+GDNiHKVDQg
          gPBLc1XagW20RMvokCAwEAAaNWMFQwDQYDVR0KBAYwBAMCBkAwQwYDVR0BBDwwO
          oAQAaVOkaVLLKoFmLN37pC8uqEUMBIxEDAOBgNVBAMTB1Rlc3QgQ0GCEC4MndUX
          jPG1TZxVKg+HutAwCQYFKw4DAh0FAAOBgQABU91ka7IlkXCfv4Zh2Ohwgg2yObt
          Y3+6C/BTFGrOEBJDy+DoxJ/NuBF18w3rrrR18xE6jNKYLCQb8zUGk4QOG5Y+HT/
          QTTFvWkiOLXcpTuhnOhXatr42FoYpDkjx2QWK+J5Q2l/Rgjgc/0ZV8U/kD8UuRk
          Xp4AZh7QsiX8AcO0w==
        &lt;/ds:X509Certificate&gt;
      &lt;/ds:X509Data&gt;
    &lt;/ds:KeyInfo&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/KeyUsage&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Encryption&lt;/KeyUsage&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Exchange&lt;/KeyUsage&gt;
    &lt;UseKeyWith Application="urn:ietf:rfc:2633"
          Identifier="alice@example.com" /&gt;
    &lt;Status StatusValue="http://www.w3.org/2002/03/xkms#Valid"&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/ValidReason&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#IssuerTrust&lt;/ValidReason&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#RevocationStatus&lt;/ValidReason&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#ValidityInterval&lt;/ValidReason&gt;
    &lt;/Status&gt;
  &lt;/KeyBinding&gt;
&lt;/ValidateResult&gt;</pre>

<h2><a name="XKMS_2_0_Section_4_3" id="XKMS_2_0_Section_4_3" shape="rect">4.3</a> <a name="UsingLocateandValidate" id="UsingLocateandValidate" shape="rect">Using Locate and
Validate</a></h2>

<p><a name="XKMS_2_0_Paragraph_159" id="XKMS_2_0_Paragraph_159" class="markParagraph" shape="rect">[159]</a>The Locate and Validate operations are both
used to obtain information about a public key from an XKMS Service. Locate
and Validate services are both expected to attempt to provide correct
information to the requestor. The Locate and Validate services differ in the
extent to which the service vouches for the trustworthiness the information
returned.</p>

<p><a name="XKMS_2_0_Paragraph_160" id="XKMS_2_0_Paragraph_160" class="markParagraph" shape="rect">[160]</a>A Location service SHOULD attempt to provide
only information which is trustworthy <i>to the best of its knowledge but
does not provide any assurance that it will do so</i>. Information obtained
from a Locate service SHOULD NOT be relied upon unless it is validated.
Validation may be achieved by forwarding the data to a Validate service or by
performing the necessary trust path verification locally.</p>

<p><a name="XKMS_2_0_Paragraph_161" id="XKMS_2_0_Paragraph_161" class="markParagraph" shape="rect">[161]</a>A Validation service undertakes to only return
information which has been positively validated by the XKMS Service as
meeting specific validation criteria. A client MAY rely on the information
returned by the service without further validation provided that the client
has a means to determine that the information returned is authentic and is
assured that the validation service applied the means of validation
appropriate to the circumstances.</p>

<p><a name="XKMS_2_0_Paragraph_162" id="XKMS_2_0_Paragraph_162" class="markParagraph" shape="rect">[162]</a>No single set of validation criteria are
appropriate to every circumstance. Applications involving financial
transactions are likely to require the application of very specific
validation criteria that ensure that certain contractual and/or regulatory
policies are enforced. The Locate service provides a key discovery function
that is neutral with respect to the validation criteria that the client
application may apply. The Validate service provides a key discovery and
validation function that produces a results which are each specific to a
single set of validation criteria.</p>

<h3 align="left"><a name="XKMS_2_0_Section_4_3_1" id="XKMS_2_0_Section_4_3_1" shape="rect">4.3.1</a> <a name="DNSIntegration" id="DNSIntegration" shape="rect">DNS Integration</a></h3>

<p align="left"><a name="XKMS_2_0_Paragraph_163" id="XKMS_2_0_Paragraph_163" class="markParagraph" shape="rect">[163]</a>In many cases the key information which a
client requires is bound to some form of address specified by an Internet
protocol part of which consists of a DNS address. For example an email client
may require a trustworthy key to send an encrypted email to bob@example.com.
Unless an XKMS service which provides key information about keys bound to
email addresses in the domain example.com is known a priori, some means of
locating the correct XKMS service is required.</p>

<p align="left"><a name="XKMS_2_0_Paragraph_164" id="XKMS_2_0_Paragraph_164" class="markParagraph" shape="rect">[164]</a>Figure 5 shows an example of using the DNS SRV
record to perform discovery of XKMS services. The email client requests a key
for bob@example.com from a trusted Validate service. The Validate service
then queries the DNS to locate an XKMS service providing information on keys
bound to addresses in the zone example.com. The Validate service does not
have an established trust relationship with the example.com XKMS service and
so a Locate request is made to determine if any key information bound to
bob@example.com can be located. The Validate service then validates the
information received by such means as are appropriate (e.g., by verifying that
a certification chain may be constructed from a root of trust) and the
response returned to the email client.</p>

<p align="center"><a name="XKMS_2_0_Paragraph_165" id="XKMS_2_0_Paragraph_165" class="markParagraph" shape="rect">[165]</a> <img alt="see caption" src="Images/image012.gif" width="441" height="273" /></p>

<p class="caption" align="center"><a name="XKMS_2_0_Paragraph_166" id="XKMS_2_0_Paragraph_166" class="markParagraph" shape="rect">[166]</a>Figure 5: Combined
use of Locate and Validate service</p>

<p align="left"><a name="XKMS_2_0_Paragraph_167" id="XKMS_2_0_Paragraph_167" class="markParagraph" shape="rect">[167]</a>Appendix B provides further information on the
use of the DNS SRV record.</p>

<h1><a name="XKMS_2_0_Section_5" id="XKMS_2_0_Section_5" shape="rect">5</a> <a name="KeyInformationServiceMessageSet" id="KeyInformationServiceMessageSet" shape="rect">Key Information Service Message
Set</a></h1>

<p><a name="XKMS_2_0_Paragraph_168" id="XKMS_2_0_Paragraph_168" class="markParagraph" shape="rect">[168]</a>The protocol consists of pairs of messages,
with an application sending a request message to an XKMS service and the
service responding with another message.&#xA0;</p>

<h2><a name="XKMS_2_0_Section_5_1" id="XKMS_2_0_Section_5_1" shape="rect">5.1</a> <a name="KeyBindingSpecification" id="KeyBindingSpecification" shape="rect">Key Binding
Specification</a></h2>

<p><a name="XKMS_2_0_Paragraph_169" id="XKMS_2_0_Paragraph_169" class="markParagraph" shape="rect">[169]</a>A <i>key binding</i> asserts a binding between
data elements that relate to a public key including the <span class="ID">&lt;ds:KeyName&gt;</span>, <span class="ID">&lt;ds:KeyValue&gt;</span> and <span class="ID">&lt;ds:X509Data</span>&gt; components contained in a <span class="ID">&lt;ds:KeyInfo&gt;</span> element. Furthermore, the Service
represents <i>to the client accessing the service and to that client
alone</i> that the binding between the data elements is <i>valid</i> under
whatever trust policy the service offers to that client.</p>

<p><a name="XKMS_2_0_Paragraph_170" id="XKMS_2_0_Paragraph_170" class="markParagraph" shape="rect">[170]</a>XKMS specifies four elements that specify key
bindings, all of which are derived from the <span class="ID">KeyBindingAbstractType</span>. These elements are:</p>

<blockquote>
  <dl>
    <dt>UnverifiedKeyBinding</dt>
      <dd>Specifies the parameters of a particular instance of a key binding
        but not the status.</dd>
    <dt>KeyBinding</dt>
      <dd>Specifies the parameters of a particular instance of a key
      binding.</dd>
    <dt>QueryKeyBinding</dt>
      <dd>A template used to specify one or more key bindings using query by
        example.</dd>
    <dt>PrototypeKeyBinding</dt>
      <dd>A template used to specify the key binding parameters requested in
        a registration request.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_171" id="XKMS_2_0_Paragraph_171" class="markParagraph" shape="rect">[171]</a>An XKMS service MAY provide an interface to an
underlying PKI such as PKIX or PGP. This specification does not define how
XKMS operations interact with the underlying PKI. The XKMS key binding MAY be
<i>bound</i> to a data object such as a certificate or key signing in the
underlying PKI such that XKMS operations on the key binding result in a
corresponding change to the data structures in the underlying PKI and vice
versa. If for example the XKMS service provides a mapping to an underlying
PKIX/X.509 PKI the registration of a key binding would typically result in
the issue of a certificate, even if the client does not ask for the
certificate to be returned in the registration result. If the key binding
were subsequently revoked the corresponding certificate in the underlying PKI
would typically be revoked also.</p>

<h3><a name="XKMS_2_0_Section_5_1_1" id="XKMS_2_0_Section_5_1_1" shape="rect">5.1.1</a> Abstract <a name="TypeKeyBindingAbstractType" id="TypeKeyBindingAbstractType" shape="rect">Type <span class="ID">KeyBindingAbstractType</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_172" id="XKMS_2_0_Paragraph_172" class="markParagraph" shape="rect">[172]</a>The <span class="ID">KeyBindingAbstractType</span> is the abstract type from which all
XKMS key binding element specifiers are derived. It contains the following
elements and attribute:</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>Id</b></span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>Identifier of the key binding.</dd>
    <dt><span class="ID"><b>&lt;ds:KeyInfo&gt;</b></span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>The public key information to which the key binding information is
        bound.</dd>
    <dt><span class="ID"><b>&lt;KeyUsage&gt;</b></span>&nbsp;&nbsp;&nbsp;[0 to 3]</dt>
      <dd>The cryptographic key uses for which the key may be used.</dd>
    <dt><span class="ID"><b>&lt;UseKeyWith&gt;</b></span>&nbsp;&nbsp;&nbsp;[Any 
    Number]</dt>
      <dd>The applications with which the key may be used together with the
        application specific subject identifier of the key holder for that
        application.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_173" id="XKMS_2_0_Paragraph_173" class="markParagraph" shape="rect">[173]</a>The <span class="ID">Id</span> identifier is defined to provide a
means by which the key binding may be signed using XML Signature. Clients
MUST NOT rely on the key binding identifier being either unique or stable. In
the case that an XKMS service is providing an interface to an underlying PKI,
clients MUST NOT rely on the service choosing key binding identifiers that
are either the same as or bear a systematic relationship to the serial
numbers or other identifiers of the corresponding credentials in the
underlying PKI.</p>

<p><a name="XKMS_2_0_Paragraph_174" id="XKMS_2_0_Paragraph_174" class="markParagraph" shape="rect">[174]</a>The following schema defines the <span class="ID">KeyBindingAbstractType</span> type:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- KeyBindingAbstractType--&gt;
   &lt;complexType name="KeyBindingAbstractType" abstract="true"&gt;
      &lt;sequence&gt;
         &lt;element ref="ds:KeyInfo" minOccurs="0"/&gt;
         &lt;element ref="xkms:KeyUsage" minOccurs="0" maxOccurs="3"/&gt;
         &lt;element ref="xkms:UseKeyWith" minOccurs="0"
               maxOccurs="unbounded"/&gt;
      &lt;/sequence&gt;
      &lt;attribute name="Id" type="ID" use="optional"/&gt;
   &lt;/complexType&gt;
   &lt;!-- /KeyBindingAbstractType--&gt;</pre>

<h3><a name="XKMS_2_0_Section_5_1_2" id="XKMS_2_0_Section_5_1_2" shape="rect">5.1.2</a> <a name="ElementKeyUsage" id="ElementKeyUsage" shape="rect">Element <span class="ID">&lt;KeyUsage&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_175" id="XKMS_2_0_Paragraph_175" class="markParagraph" shape="rect">[175]</a>The <span class="ID">&lt;KeyUsage&gt;</span>
element specifies one or more intended uses of the key. If no <span class="ID">&lt;KeyUsage&gt;</span> is specified all uses are permitted. The
following key usages are defined:</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>Encryption</b></span></dt>
      <dd>The key pair may be used for encryption and decryption.</dd>
    <dt><span class="ID"><b>Signature</b></span></dt>
      <dd>The key pair may be used for signature and verification.</dd>
    <dt><span class="ID"><b>Exchange</b></span></dt>
      <dd>The key pair may be used for key exchange.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_176" id="XKMS_2_0_Paragraph_176" class="markParagraph" shape="rect">[176]</a>If a key usage is specified in a <span class="ID">KeyBinding</span> that the cryptographic algorithm associated
with the key does not support the element MUST be ignored. If a key usage is
specified in a <span class="ID">QueryKeyBinding</span> however the key
usage forms part of the criteria the service should attempt to match.</p>

<p><a name="XKMS_2_0_Paragraph_177" id="XKMS_2_0_Paragraph_177" class="markParagraph" shape="rect">[177]</a>For example if a KeyBinding specifies the key
usage <span class="ID">Encryption</span> for a Digital Signature Algorithm
key the relying application should ignore the key usage element. If however a
client makes a request that contains a <span class="ID">QueryKeyBinding</span> that specifies the key usage encryption
the service should not return a Digital Signature Algorithm key.</p>

<p><a name="XKMS_2_0_Paragraph_178" id="XKMS_2_0_Paragraph_178" class="markParagraph" shape="rect">[178]</a>The following schema defines the <span class="ID">&lt;KeyUsage&gt;</span> element:</p>
<!-- Include file -->

<pre class="Code" xml:space="preserve">   &lt;!-- KeyUsage --&gt;
   &lt;simpleType name="KeyUsageEnum"&gt;
      &lt;restriction base="anyURI"&gt;
         &lt;enumeration value="http://www.w3.org/2002/03/xkms#Encryption"/&gt;
         &lt;enumeration value="http://www.w3.org/2002/03/xkms#Signature"/&gt;
         &lt;enumeration value="http://www.w3.org/2002/03/xkms#Exchange"/&gt;
      &lt;/restriction&gt;
   &lt;/simpleType&gt;

   &lt;element name="KeyUsage" type="xkms:KeyUsageEnum"/&gt;
   &lt;!-- /KeyUsage --&gt;</pre>

<h3 dir="ltr"><a name="XKMS_2_0_Section_5_1_3" id="XKMS_2_0_Section_5_1_3" shape="rect">5.1.3</a> <a name="ElementUseKeyWith" id="ElementUseKeyWith" shape="rect">Element <span class="ID">&lt;UseKeyWith&gt;</span></a></h3>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_179" id="XKMS_2_0_Paragraph_179" class="markParagraph" shape="rect">[179]</a>The&#xA0;<span class="ID">&lt;UseKeyWith&gt;</span> element specifies a subject identifier
and application identifier that determine a use of the key. The
interpretation of <span class="ID">&lt;UseKeyWith&gt;</span> depends on the
enclosing construct.</p>
<dl>
  <dt dir="ltr">QueryKeyBinding /
  PrototypeKeyBinding</dt>
    <dd>A key binding is requested that meets the specified criteria. If the
      service is unable to meet the criteria exactly 'best guess' is
      acceptable.</dd>
  <dt dir="ltr">UnverifiedKeyBinding / KeyBinding</dt>
    <dd>The key may be used for the purpose specified (if unverified after
      validation). If more than one <span class="ID">&lt;UseKeyWith&gt;</span> element
       is specified then all are applicable
      jointly and severally.</dd>
</dl>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_180" id="XKMS_2_0_Paragraph_180" class="markParagraph" shape="rect">[180]</a>The <span class="ID">&lt;UseKeyWith&gt;</span>
element contains the following attributes:</p>

<blockquote dir="ltr">
  <dl dir="ltr">
    <dt dir="ltr"><span class="ID"><b>Application</b></span>
    <b>&nbsp;&nbsp;&nbsp;[Required]</b></dt>
      <dd>A URI that specifies the application protocol with which the key
        may be used.</dd>
      <dd></dd>
    <dt dir="ltr"><span class="ID"><b>Identifier</b></span>
    <b>&nbsp;&nbsp;&nbsp; [Required]</b></dt>
      <dd dir="ltr">Specifies the subject to which the key corresponds within
        the specified application protocol.</dd>
  </dl>
</blockquote>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_181" id="XKMS_2_0_Paragraph_181" class="markParagraph" shape="rect">[181]</a>Note that in some applications, in particular
X.509 an application identifier is not guaranteed to be globally unique. In
such circumstances the XKMS service is responsible for specifying rules to
unambiguously interpret identifiers.</p>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_182" id="XKMS_2_0_Paragraph_182" class="markParagraph" shape="rect">[182]</a>The following table lists application URIs for
common application protocols and the corresponding format for the identifier
information:</p>

<div align="center">

<table border="1" cellpadding="3" cellspacing="0" dir="ltr">
  <tbody>
    <tr>
      <th dir="ltr">Application</th>
      <th dir="ltr">Application URI</th>
      <th dir="ltr">Identifier</th>
      <th dir="ltr">Type</th>
    </tr>
    <tr>
      <td dir="ltr" align="left">XKMS</td>
      <td dir="ltr" align="left">http://www.w3.org/2002/03/xkms#</td>
      <td dir="ltr" align="left">URL identifying SOAP role</td>
      <td dir="ltr" align="left">URI</td>
    </tr>
    <tr>
      <td dir="ltr" align="left">XKMS/<i>profile</i></td>
      <td dir="ltr" align="left">http://www.w3.org/2002/03/xkms#<i>profile</i></td>
      <td dir="ltr" align="left">URL identifying SOAP role</td>
      <td dir="ltr" align="left">URI</td>
    </tr>
    <tr>
      <td dir="ltr" align="left">S/MIME</td>
      <td dir="ltr" align="left">urn:ietf:rfc:2633</td>
      <td dir="ltr" align="left">SMTP email address of subject</td>
      <td dir="ltr" align="left">RFC822 addr-spec</td>
    </tr>
    <tr>
      <td dir="ltr" align="left">PGP</td>
      <td dir="ltr" align="left">urn:ietf:rfc:2440</td>
      <td dir="ltr" align="left">SMTP email address of subject</td>
      <td dir="ltr" align="left">RFC822 addr-spec</td>
    </tr>
    <tr>
      <td dir="ltr" align="left">TLS</td>
      <td dir="ltr" align="left">urn:ietf:rfc:2246</td>
      <td dir="ltr" align="left">URI identifying certificate subject</td>
      <td dir="ltr" align="left">URI</td>
    </tr>
    <tr>
      <td dir="ltr" align="left">TLS/HTTPS</td>
      <td dir="ltr" align="left">urn:ietf:rfc:2818</td>
      <td dir="ltr" align="left">DNS address of http server</td>
      <td dir="ltr" align="left">DNS Address</td>
    </tr>
    <tr>
      <td dir="ltr" align="left">TLS/SMTP</td>
      <td dir="ltr" align="left">urn:ietf:rfc:2487</td>
      <td dir="ltr" align="left">DNS address of mail server</td>
      <td dir="ltr" align="left">DNS Address</td>
    </tr>
    <tr>
      <td dir="ltr" align="left">IPSEC</td>
      <td dir="ltr" align="left">urn:ietf:rfc:2401</td>
      <td dir="ltr" align="left">IP address of network resource</td>
      <td dir="ltr" align="left">IP Address</td>
    </tr>
    <tr>
      <td dir="ltr" align="left">PKIX</td>
      <td dir="ltr" align="left">urn:ietf:rfc:2459</td>
      <td dir="ltr" align="left">Certificate Subject Name</td>
      <td dir="ltr" align="left">X.509 Distinguished Name</td>
    </tr>
  </tbody>
</table>
</div>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_183" id="XKMS_2_0_Paragraph_183" class="markParagraph" shape="rect">[183]</a> The XKMS application URI is used to specify a
key binding that is used to secure an XKMS service. An XKMS service SHOULD
support discovery of the supported security profiles and corresponding key
bindings by means of a <span class="ID">Locate</span> operation that
specifies the XKMS application URI and the URL of the service role. Note that
as with any other Locate operation the credentials returned by this mechanism
SHOULD only be considered trustworthy if validated according to the trust
policy of the client.</p>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_184" id="XKMS_2_0_Paragraph_184" class="markParagraph" shape="rect">[184]</a> The primary use intended for <span class="ID">&lt;UseKeyWith&gt;</span> identifiers is to identify application
protocols. <span class="ID">&lt;UseKeyWith&gt;</span> URI identifiers MAY be
specified that represent key binding issuance and/or use policies instead of
or in addition to an application protocol. In this case the <span class="ID">&lt;UseKeyWith&gt;</span> element specifies that the key binding
complies with the specified policy. For example, applications handling XAdES
<a href="#XAdES" shape="rect">[XAdES]</a> compliant signatures could define their own
<span class="ID">&lt;UseKeyWith&gt;</span> application values.</p>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_185" id="XKMS_2_0_Paragraph_185" class="markParagraph" shape="rect">[185]</a>In the case that a client follows a referral
model in which raw key binding information is obtained from a Locate service
then forwarded to a validate service the <span class="ID">&lt;UseKeyWith&gt;</span> elements in the query should in both
cases specify the uses for which the application intends to use the key.
Applications SHOULD NOT forward <span class="ID">&lt;UseKeyWith&gt;</span>
elements returned in a Locate result in a subsequent Validate query.</p>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_186" id="XKMS_2_0_Paragraph_186" class="markParagraph" shape="rect">[186]</a>The following table describes the formatting
for the specified types of identifier:</p>

<table border="1" cellpadding="1" cellspacing="0" width="100%" id="AutoNumber2" dir="ltr">
  <tbody>
    <tr>
      <th height="19" dir="ltr">Identifier Type</th>
      <th height="19" dir="ltr">Example</th>
      <th height="19" dir="ltr">Description</th>
    </tr>
    <tr>
      <td valign="top" height="36" dir="ltr" align="left">RFC822
      addr-spec</td>
      <td valign="top" height="36" dir="ltr" align="left">bob@example.com</td>
      <td valign="top" height="36" dir="ltr" align="left">The addr-spec
        fragment of an RFC 822 email address as used by SMTP</td>
    </tr>
    <tr>
      <td valign="top" height="18" dir="ltr" align="left">URI</td>
      <td valign="top" height="18" dir="ltr" align="left">https://example.com/</td>
      <td valign="top" height="18" dir="ltr" align="left">A Uniform Resource
        Identifier</td>
    </tr>
    <tr>
      <td valign="top" height="18" dir="ltr" align="left">DNS Address</td>
      <td valign="top" height="18" dir="ltr" align="left">example.com</td>
      <td valign="top" height="18" dir="ltr" align="left">An Internet DNS
        address</td>
    </tr>
    <tr>
      <td rowspan="2" valign="top" height="43" dir="ltr" align="left">IP
        Address</td>
      <td valign="top" height="18" dir="ltr" align="left">10.23.0.20</td>
      <td valign="top" height="18" dir="ltr" align="left">An IPv4 address in
        decimal notation</td>
    </tr>
    <tr>
      <td valign="top" height="19" dir="ltr" align="left">1080::8:800:200C:417A</td>
      <td valign="top" height="19" dir="ltr" align="left">An IPv6 address in
        <a href="#RFC-2373" shape="rect">RFC 2373</a> notation</td>
    </tr>
    <tr>
      <td valign="top" height="36" dir="ltr" align="left">X.509 Distinguished
        Name</td>
      <td valign="top" height="36" dir="ltr" align="left">C="UK"
        O="CryptoGuys Ltd." CN="Bob"</td>
      <td valign="top" height="36" dir="ltr" align="left">An X.509
        Distinguished Name</td>
    </tr>
  </tbody>
</table>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_187" id="XKMS_2_0_Paragraph_187" class="markParagraph" shape="rect">[187]</a>The following schema defines the <span class="ID">&lt;UseKeyWith&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- UseKeyWith --&gt;
   &lt;element name="UseKeyWith" type="xkms:UseKeyWithType"/&gt;
   &lt;complexType name="UseKeyWithType"&gt;
      &lt;attribute name="Application" type="anyURI" use="required"/&gt;
      &lt;attribute name="Identifier" type="string" use="required"/&gt;
   &lt;/complexType&gt;
   &lt;!-- /UseKeyWith --&gt;</pre>

<h3><a name="XKMS_2_0_Section_5_1_4" id="XKMS_2_0_Section_5_1_4" shape="rect">5.1.4</a> <a name="ElementUnverifiedKeyBinding" id="ElementUnverifiedKeyBinding" shape="rect">Element
<span class="ID">&lt;UnverifiedKeyBinding&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_188" id="XKMS_2_0_Paragraph_188" class="markParagraph" shape="rect">[188]</a>The <span class="ID">&lt;UnverifiedKeyBinding&gt;</span> element is derived from the
<span class="ID">KeyBindingAbstractType</span>. It describes a key binding
but makes no assertion regarding the status of the key binding.</p>

<p><a name="XKMS_2_0_Paragraph_189" id="XKMS_2_0_Paragraph_189" class="markParagraph" shape="rect">[189]</a>The <span class="ID">&lt;UnverifiedKeyBinding&gt;</span> element extends the <span class="ID">KeyBindingAbstractType</span> with the following additional
elements:</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;ValidityInterval&gt;</b></span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>The time interval  for which the key
        binding relationship is requested to be asserted.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_190" id="XKMS_2_0_Paragraph_190" class="markParagraph" shape="rect">[190]</a>The following schema defines the <span class="ID">&lt;UnverifiedKeyBinding&gt;</span> element and <span class="ID">UnverifiedKeyBinding</span><span class="ID">Type</span>:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- UnverifiedKeyBinding --&gt;
   &lt;element name="UnverifiedKeyBinding"
         type="xkms:UnverifiedKeyBindingType"/&gt;
   &lt;complexType name="UnverifiedKeyBindingType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:KeyBindingAbstractType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:ValidityInterval" minOccurs="0"/&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /UnverifiedKeyBinding --&gt;</pre>

<h3><a name="XKMS_2_0_Section_5_1_5" id="XKMS_2_0_Section_5_1_5" shape="rect">5.1.5</a> <a name="ElementValidityInterval" id="ElementValidityInterval" shape="rect">Element <span class="ID">&lt;ValidityInterval&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_191" id="XKMS_2_0_Paragraph_191" class="markParagraph" shape="rect">[191]</a>The <span class="ID">&lt;ValidityInterval&gt;</span> element specifies limits on the
validity of the key binding.</p>

<blockquote>
  <dl>
    <dt><span class="ID">NotBefore</span>&nbsp;&nbsp;&nbsp;<b>[Optional]</b></dt>
      <dd>Time instant at which the validity interval begins.</dd>
    <dt><span class="ID">NotOnOrAfter</span>&nbsp;&nbsp;&nbsp;<b>[Optional]</b></dt>
      <dd>Time instant at which the validity interval has ended.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_192" id="XKMS_2_0_Paragraph_192" class="markParagraph" shape="rect">[192]</a>All dateTime values MUST fully specify the
date.</p>

<p><a name="XKMS_2_0_Paragraph_193" id="XKMS_2_0_Paragraph_193" class="markParagraph" shape="rect">[193]</a>The <span class="ID">NotBefore</span> and
<span class="ID">NotOnOrAfter</span> attributes are optional. If the <span class="ID">NotBefore</span> attribute is omitted the key binding is valid on
any date up to but excluding the date specified in the <span class="ID">NotOnOrAfter</span> attribute . If the <span class="ID">NotOnOrAfter</span> attribute is omitted the key binding is valid
from the <span class="ID">NotBefore</span> attribute with no expiry. If both
 attributes are omitted the key binding is
valid at any time.</p>

<p><a name="XKMS_2_0_Paragraph_194" id="XKMS_2_0_Paragraph_194" class="markParagraph" shape="rect">[194]</a>In accordance with the XML Schema
Specifications, all time instances are interpreted in Universal Coordinated
Time unless they explicitly indicate a time zone.</p>

<p><a name="XKMS_2_0_Paragraph_195" id="XKMS_2_0_Paragraph_195" class="markParagraph" shape="rect">[195]</a>Implementations MUST NOT generate time
instances that specify leap seconds.</p>

<p><a name="XKMS_2_0_Paragraph_196" id="XKMS_2_0_Paragraph_196" class="markParagraph" shape="rect">[196]</a>For purposes of comparison, the time interval
<span class="ID">NotBefore</span> to <span class="ID">NotOnOrAfter</span>
begins at the earliest time instant compatible with the specification of
<span class="ID">NotBefore</span> and <i><u>has ended</u></i> at the
<i><u>earliest</u></i> time instant compatible with the specification of
<span class="ID">NotOnOrAfter</span></p>

<p><a name="XKMS_2_0_Paragraph_197" id="XKMS_2_0_Paragraph_197" class="markParagraph" shape="rect">[197]</a>For example if the time interval specified is
<span class="ID"><i>day</i>T12:03:02</span> to <span class="ID"><i>day</i>T12:05:12</span> the times <span class="ID">12:03:02.00</span> and <span class="ID">12:05:11.9999</span> are
within the time interval. The time <span class="ID">12:05:12.0000</span> is
outside the time interval.</p>

<p><a name="XKMS_2_0_Paragraph_198" id="XKMS_2_0_Paragraph_198" class="markParagraph" shape="rect">[198]</a>The following schema defines the <span class="ID">&lt;ValidityInterval&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- ValidityInterval --&gt;
   &lt;element name="ValidityInterval" type="xkms:ValidityIntervalType"/&gt;
   &lt;complexType name="ValidityIntervalType"&gt;
      &lt;attribute name="NotBefore" type="dateTime" use="optional"/&gt;
      &lt;attribute name="NotOnOrAfter" type="dateTime" use="optional"/&gt;
   &lt;/complexType&gt;
   &lt;!-- /ValidityInterval --&gt;</pre>

<h3><a name="XKMS_2_0_Section_5_1_6" id="XKMS_2_0_Section_5_1_6" shape="rect">5.1.6</a> <a name="ElementKeyBinding" id="ElementKeyBinding" shape="rect">Element <span class="ID">&lt;KeyBinding&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_199" id="XKMS_2_0_Paragraph_199" class="markParagraph" shape="rect">[199]</a>The <span class="ID">&lt;KeyBinding&gt;</span>
element is derived from the <span class="ID">UnverifiedKeyBinding</span><span class="ID">Type</span>. It specifies a particular instance of a key binding
and its current status as known to the issuer of the key binding.</p>

<p><a name="XKMS_2_0_Paragraph_200" id="XKMS_2_0_Paragraph_200" class="markParagraph" shape="rect">[200]</a>The <span class="ID">&lt;KeyBinding&gt;</span>
element extends the <span class="ID">UnverifiedKeyBinding</span><span class="ID">Type</span> with the following additional elements:</p>

<blockquote>
  <dl>
    <dt><span class="ID">&lt;Status&gt;</span>&nbsp;&nbsp;&nbsp;[Required]</dt>
      <dd>The status of the key binding instance.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_201" id="XKMS_2_0_Paragraph_201" class="markParagraph" shape="rect">[201]</a>The following schema defines the <span class="ID">&lt;KeyBinding&gt;</span> element and <span class="ID">KeyBindingType</span>:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- KeyBinding --&gt;
   &lt;element name="KeyBinding" type="xkms:KeyBindingType"/&gt;
   &lt;complexType name="KeyBindingType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:UnverifiedKeyBindingType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:Status"/&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /KeyBinding --&gt;</pre>

<h3><a name="XKMS_2_0_Section_5_1_7" id="XKMS_2_0_Section_5_1_7" shape="rect">5.1.7</a> <a name="ElementStatus" id="ElementStatus" shape="rect">Element <span class="ID">&lt;Status&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_202" id="XKMS_2_0_Paragraph_202"
class="markParagraph" shape="rect">[202]</a>The <span class="ID">&lt;Status&gt;</span>
element specifies the status of a <span class="ID">&lt;KeyBinding&gt;</span>
instance.</p>

<p><a name="XKMS_2_0_Paragraph_203" id="XKMS_2_0_Paragraph_203" class="markParagraph" shape="rect">[203]</a>The status value MAY be supplemented with
codes that state the status of specific aspects of the key binding status
that were validated.</p>

<p><a name="XKMS_2_0_Paragraph_204" id="XKMS_2_0_Paragraph_204" class="markParagraph" shape="rect">[204]</a>The <span class="ID">&lt;Status&gt;</span>
element contains the following elements and attribute:</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;ValidReason&gt;</b></span>&nbsp;&nbsp;&nbsp;[Any
    Number]</dt>
      <dd>A status aspect that was evaluated and found to be Valid.</dd>
    <dt><span class="ID"><b>&lt;IndeterminateReason&gt;</b></span>&nbsp;&nbsp;&nbsp;[Any
    Number]</dt>
      <dd>A status aspect that could not be evaluated or was evaluated and
        returned an Indeterminate result.</dd>
    <dt><span class="ID"><b>&lt;InvalidReason&gt;</b></span>&nbsp;&nbsp;&nbsp;[Any
    Number]</dt>
      <dd>A status aspect that was evaluated and found to be Invalid.</dd>
    <dt><span class="ID">StatusValue</span>&nbsp;&nbsp;&nbsp;[Required]</dt>
      <dd>The key binding status.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_205" id="XKMS_2_0_Paragraph_205" class="markParagraph" shape="rect">[205]</a>The enumerated type <span class="ID">KeyBindingEnum</span> is used to
indicate the key binding status. The following values are defined:</p>

<blockquote>
  <dl>
    <dt><span class="ID">Valid</span></dt>
      <dd>The key binding is definitively valid.</dd>
    <dt><span class="ID">Indeterminate</span></dt>
      <dd>The status of the key binding cannot be determined. 
      </dd>
    <dt><span class="ID">Invalid</span></dt>
      <dd>The key binding is definitively invalid.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_206" id="XKMS_2_0_Paragraph_206" class="markParagraph" shape="rect">[206]</a>If reason codes are specified&#xA0;<span class="ID">StatusValue</span> attribute MUST be consistent with the reason
codes specified as follows:</p>
<ul>
  <li>If an <span class="ID">&lt;InvalidReason&gt;</span> code is present the
    <span class="ID">StatusValue</span> attibute MUST have the value <span class="ID">Invalid</span>.</li>
  <li>If an <span class="ID">&lt;IndeterminateReason&gt;</span> code is
    present the <span class="ID">StatusValue</span> attibute MUST have the
    either the value <span class="ID">Indeterminate</span> or the value <span class="ID">Invalid</span>.</li>
  <li>If neither an <span class="ID">&lt;InvalidReason&gt;</span> nor an
    <span class="ID">&lt;IndeterminateReason&gt;</span> code is present the
    <span class="ID">StatusValue</span> attibute MAY have any defined value,
    i.e. <span class="ID">Valid</span>, <span class="ID">Indeterminate</span>
    or <span class="ID">Invalid</span>.</li>
</ul>

<p><a name="XKMS_2_0_Paragraph_206a" id="XKMS_2_0_Paragraph_206a"
class="markParagraph" shape="rect">[206a]</a>Note
that the X-KRSS {<span class="ID">Revoke</span>, <span
class="ID">Reissue</span>, <span class="ID">Recover</span>} <span
class="ID">KeyBinding</span> elements are all of type <span
class="ID">KeyBindingType</span>, which requires a <span
class="ID">Status</span> element (c.f. <a
href="#XKMS_2_0_Section_7">Section 7</a>). In the case of <span
class="ID">Reissue</span>, <span class="ID">Revoke</span>, and <span
class="ID">Recover</span> requests, servers MAY ignore the <span
class="ID">Indeterminate</span> <span class="ID">&lt;Status&gt;</span>
status value and Clients MAY set <span class="ID">Indeterminate</span>
as status value.</p>

<p><a name="XKMS_2_0_Paragraph_207" id="XKMS_2_0_Paragraph_207" class="markParagraph" shape="rect">[207]</a>The following schema defines the <span class="ID">&lt;Status&gt;</span> element and <span class="ID">StatusType</span> and <span class="ID">AssertionType</span>
types:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- Status --&gt;
   &lt;element name="Status" type="xkms:StatusType"/&gt;
   &lt;complexType name="StatusType"&gt;
      &lt;sequence&gt;
         &lt;element ref="xkms:ValidReason" minOccurs="0"
               maxOccurs="unbounded"/&gt;
         &lt;element ref="xkms:IndeterminateReason" minOccurs="0"
               maxOccurs="unbounded"/&gt;
         &lt;element ref="xkms:InvalidReason" minOccurs="0"
               maxOccurs="unbounded"/&gt;
      &lt;/sequence&gt;
     
      &lt;attribute name="StatusValue" type="xkms:KeyBindingEnum" use="required"/&gt;
   &lt;/complexType&gt;
   
   &lt;simpleType name="KeyBindingEnum"&gt;
      &lt;restriction base="anyURI"&gt;
         &lt;enumeration value="http://www.w3.org/2002/03/xkms#Valid"/&gt;
         &lt;enumeration value="http://www.w3.org/2002/03/xkms#Invalid"/&gt;
         &lt;enumeration value="http://www.w3.org/2002/03/xkms#Indeterminate"/&gt;
      &lt;/restriction&gt;
   &lt;/simpleType&gt;
   &lt;!-- /Status --&gt;</pre>

<h3><a name="XKMS_2_0_Section_5_1_8" id="XKMS_2_0_Section_5_1_8" shape="rect">5.1.8</a> <a name="ElementsValidReasonetc" id="ElementsValidReasonetc" shape="rect">Elements <span class="ID">&lt;ValidReason</span></a> <span class="ID">&gt;</span>, <span class="ID">&lt;InvalidReason&gt;</span> and <span class="ID">&lt;IndeterminateReason&gt;</span></h3>

<p><a name="XKMS_2_0_Paragraph_208" id="XKMS_2_0_Paragraph_208" class="markParagraph" shape="rect">[208]</a>The <span class="ID">&lt;ValidReason&gt;</span>, <span class="ID">&lt;InvalidReason&gt;</span> and<span class="ID">&lt;IndeterminateReason&gt;</span> elements are used to specify a 
 <code>anyURI</code> type that specifies
a reason for a particular key binding status.</p>

<p><a name="XKMS_2_0_Paragraph_209" id="XKMS_2_0_Paragraph_209" class="markParagraph" shape="rect">[209]</a>The status aspects are defined in the table
below. For convenience the equivalent X509 processing steps are given:</p>

<div class="center">

<table cellspacing="0" cellpadding="4" border="1">
  <tbody>
    <tr>
      <th valign="top" rowspan="2">Reason 
        <code>anyURI</code> Type (prefixed with
        http://www.w3.org/2002/03/xkms#)</th>
      <th valign="top" rowspan="2">Description</th>
      <th valign="top" colspan="2" rowspan="1">X.509 Equivalent</th>
    </tr>
    <tr>
      <th valign="top" class="ID">Valid</th>
      <th valign="top" class="ID">Invalid</th>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">IssuerTrust</span></td>
      <td valign="top" align="left">The issuer of the information on which
        the key binding is based is considered to be trustworthy by the XKMS
        service</td>
      <td valign="top" align="left">Certificate path anchored by trusted root
        successfully constructed</td>
      <td valign="top" align="left">Certificate path could not be constructed
        to a trusted root</td>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">RevocationStatus</span></td>
      <td valign="top" align="left">The XKMS service has affirmatively
        verified the status of the key binding with an authoritative
      source</td>
      <td valign="top" align="left">Certificate status validated using CRL or
        OCSP</td>
      <td valign="top" align="left">Certificate status returned revoked or
        suspended.</td>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">ValidityInterval</span></td>
      <td valign="top" align="left">The requested time instant was within the
        validity interval of the key binding</td>
      <td valign="top" align="left">The certificate chain was valid at the
        requested time instant</td>
      <td valign="top" align="left">The requested time instant was before or
        after the certificate chain validity interval</td>
    </tr>
    <tr>
      <td valign="top" align="left"><span class="ID">Signature</span></td>
      <td valign="top" align="left">Signature on signed data provided by the
        client in the <span class="ID">&lt;Keyinfo&gt;</span> element was
        successfully verified.</td>
      <td valign="top" align="left">Certificate Signature verified</td>
      <td valign="top" align="left">Certificate Signature verification
      failed</td>
    </tr>
  </tbody>
</table>
</div>

<p><a name="XKMS_2_0_Paragraph_210" id="XKMS_2_0_Paragraph_210" class="markParagraph" shape="rect">[210]</a>The following schema defines the <span class="ID">&lt;ValidReason&gt;</span>, <span class="ID">&lt;InvalidReason&gt;</span> and<span class="ID">&lt;IndeterminateReason&gt;</span> elements:</p>
<!-- Include file -->

<pre class="Code" xml:space="preserve">   &lt;!-- Reason --&gt;
   &lt;simpleType name="ReasonEnum"&gt;
       &lt;restriction base="anyURI"&gt;
            &lt;enumeration value="http://www.w3.org/2002/03/xkms#IssuerTrust"/&gt;
            &lt;enumeration value="http://www.w3.org/2002/03/xkms#RevocationStatus"/&gt;
            &lt;enumeration value="http://www.w3.org/2002/03/xkms#ValidityInterval"/&gt;
            &lt;enumeration value="http://www.w3.org/2002/03/xkms#Signature"/&gt; 
       &lt;/restriction&gt;
    &lt;/simpleType&gt;
    &lt;simpleType name="ReasonOpenEnum"&gt;
       &lt;union memberTypes="xkms:ReasonEnum anyURI"/&gt;
   &lt;/simpleType&gt;
   &lt;element name="ValidReason" type="xkms:ReasonOpenEnum"/&gt;
   &lt;element name="InvalidReason" type="xkms:ReasonOpenEnum"/&gt;
   &lt;element name="IndeterminateReason" type="xkms:ReasonOpenEnum"/&gt;
   &lt;!-- /Reason --&gt;</pre>

<h3><a name="XKMS_2_0_Section_5_1_9" id="XKMS_2_0_Section_5_1_9" shape="rect">5.1.9</a> <a name="ElementQueryKeyBinding" id="ElementQueryKeyBinding" shape="rect">Element <span class="ID">&lt;QueryKeyBinding&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_211" id="XKMS_2_0_Paragraph_211" class="markParagraph" shape="rect">[211]</a>The <span class="ID">&lt;QueryKeyBinding&gt;</span> element is derived from the <span class="ID">KeyBindingAbstractType</span> and is used to perform a query that
results in the return of one or more matching key bindings.</p>

<p><a name="XKMS_2_0_Paragraph_212" id="XKMS_2_0_Paragraph_212" class="markParagraph" shape="rect">[212]</a>A key binding matches the <span class="ID">QueryKeyBinding</span> if:</p>
<ul>
  <li>The key binding contains all the <span class="ID">&lt;UseKeyWith&gt;</span> elements contained in the query,
    <i><u>and</u></i></li>
  <li>The key binding contains all the <span class="ID">&lt;KeyInfo&gt;</span> elements contained in the query.</li>
</ul>

<p><a name="XKMS_2_0_Paragraph_213" id="XKMS_2_0_Paragraph_213" class="markParagraph" shape="rect">[213]</a>The <span class="ID">&lt;QueryKeyBinding&gt;</span> element extends the <span class="ID">KeyBindingAbstractType</span> with the following additional
elements:</p>

<blockquote>
  <dl>
    <dt><span class="ID">&lt;TimeInstant&gt;</span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>The Time Instant for which the query is made. If no time instant is
        specified the default is the time the request was made. A 
        Service that does not support
        the <span class="ID">TimeInstant</span> element MUST return
        a <span class="ID">Receiver.TimeInstantNotSupported</span> result.
        Additionally, a Service that does support
        the <span class="ID">TimeInstant</span> element may be
        unable or unwilling to respond to requests indicating a time instant
        that is outside a certain range. In such cases, the service MUST
        return
        a <span class="ID">Sender.TimeInstantOutOfRange</span> result. 
      </dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_214" id="XKMS_2_0_Paragraph_214" class="markParagraph" shape="rect">[214]</a>The following schema defines the <span class="ID">&lt;QueryKeyBinding&gt;</span> element and <span class="ID">KeyBindingType</span>:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- QueryKeyBinding --&gt;
   &lt;element name="QueryKeyBinding" type="xkms:QueryKeyBindingType"/&gt;
   &lt;complexType name="QueryKeyBindingType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:KeyBindingAbstractType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:TimeInstant" minOccurs="0"/&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /QueryKeyBinding --&gt;</pre>

<h3><a name="XKMS_2_0_Section_5_1_10" id="XKMS_2_0_Section_5_1_10" shape="rect">5.1.10</a>
<a name="ElementTimeInstant" id="ElementTimeInstant" shape="rect">Element <span class="ID">&lt;TimeInstant&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_215" id="XKMS_2_0_Paragraph_215" class="markParagraph" shape="rect">[215]</a>The <span class="ID">&lt;TimeInstant&gt;</span> element specifies a specific instant in
time for which a key binding query is made. The <span class="ID">&lt;TimeInstant&gt;</span> element contains the following
attribute:</p>

<blockquote>
  <dl>
    <dt><span class="ID">Time</span>&nbsp;&nbsp;&nbsp;<b>[Required]</b></dt>
      <dd>Time instant to which a <span class="ID">&lt;QueryKeyBinding&gt;</span> relates.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_216" id="XKMS_2_0_Paragraph_216" class="markParagraph" shape="rect">[216]</a>All dateTime values MUST fully specify the
date.</p>

<p><a name="XKMS_2_0_Paragraph_217" id="XKMS_2_0_Paragraph_217" class="markParagraph" shape="rect">[217]</a>The following schema defines the <span class="ID">&lt;TimeInstant&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- TimeInstant --&gt;
   &lt;element name="TimeInstant" type="xkms:TimeInstantType"/&gt;
   &lt;complexType name="TimeInstantType"&gt;
      &lt;attribute name="Time" type="dateTime" use="required"/&gt;
   &lt;/complexType&gt;
   &lt;!-- /TimeInstant --&gt;</pre>

<h2><a name="XKMS_2_0_Section_5_2" id="XKMS_2_0_Section_5_2" shape="rect">5.2</a> <a name="LocateService" id="LocateService" shape="rect">Locate Service</a></h2>

<p><a name="XKMS_2_0_Paragraph_218" id="XKMS_2_0_Paragraph_218" class="markParagraph" shape="rect">[218]</a>The Locate service accepts as input a <span class="ID">&lt;QueryKeyBinding&gt;</span> element that specifies a key
binding and returns one or more <span class="ID">&lt;UnverifiedKeyBinding&gt;</span> elements that relate to the
same public key. The <span class="ID">&lt;UnverifiedKeyBinding&gt;</span>
elements returned are specified by the <span class="ID">RespondWith</span>
element in the request.</p>

<h3><a name="XKMS_2_0_Section_5_2_1" id="XKMS_2_0_Section_5_2_1" shape="rect">5.2.1</a> Locate Request <a name="ElementLocateRequest" id="ElementLocateRequest" shape="rect">Element <span class="ID">&lt;LocateRequest&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_219" id="XKMS_2_0_Paragraph_219" class="markParagraph" shape="rect">[219]</a>The request message contains a <span class="ID">&lt;LocateRequest&gt;</span> element that contains the following
element.</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;QueryKeyBinding&gt;</b></span>&nbsp;&nbsp;&nbsp;[Required]</dt>
      <dd>The key binding query to be matched in the response.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_220" id="XKMS_2_0_Paragraph_220" class="markParagraph" shape="rect">[220]</a>&#xA0;The following schema defines the <span class="ID">&lt;LocateRequest&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- LocateRequest --&gt;
   &lt;element name="LocateRequest" type="xkms:LocateRequestType"/&gt;
   &lt;complexType name="LocateRequestType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:RequestAbstractType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:QueryKeyBinding"/&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /LocateRequest --&gt;</pre>

<h3><a name="XKMS_2_0_Section_5_2_2" id="XKMS_2_0_Section_5_2_2" shape="rect">5.2.2</a> Locate Response <a name="ElementLocateResult" id="ElementLocateResult" shape="rect">Element <span class="ID">&lt;LocateResult&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_221" id="XKMS_2_0_Paragraph_221" class="markParagraph" shape="rect">[221]</a>The response message contains a <span class="ID">&lt;LocateResult&gt;</span> element</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;UnverifiedKeyBinding&gt;</b></span>&nbsp;&nbsp;&nbsp;[Any
    Number]</dt>
      <dd>A sequence of <span class="ID">&lt;UnverifiedKeyBinding&gt;</span>
        key binding that match the key binding query specified in
        the corresponding request. If no results are found the sequence is
        empty and the result code <span class="ID">NoMatch</span> is
        returned. In some circumstances a <span class="ID">Locate</span>
        operation MAY return multiple matching results. 
      </dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_222" id="XKMS_2_0_Paragraph_222" class="markParagraph" shape="rect">[222]</a>&#xA0;The following schema defines the <span class="ID">&lt;LocateResult&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- LocateResult --&gt;
   &lt;element name="LocateResult" type="xkms:LocateResultType"/&gt;
   &lt;complexType name="LocateResultType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:ResultType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:UnverifiedKeyBinding" minOccurs="0"
                     maxOccurs="unbounded"/&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /LocateResult --&gt;</pre>

<h2><a name="XKMS_2_0_Section_5_3" id="XKMS_2_0_Section_5_3" shape="rect">5.3</a> <a name="ValidateService" id="ValidateService" shape="rect">Validate Service</a></h2>

<p><a name="XKMS_2_0_Paragraph_223" id="XKMS_2_0_Paragraph_223" class="markParagraph" shape="rect">[223]</a>The <span class="ID">Validate</span> service
allows the client to query the binding between a <span class="ID">&lt;ds:Keyinfo&gt;</span> element and other data such as an
identifier. The client supplies a prototype for the key binding requested.
The prototype may specify either a <span class="ID">&lt;ds:Keyinfo&gt;</span>
element or one or more <span class="ID">&lt;UseKeyWith&gt;</span> elements
or&#xA0; both. If the validate request is successful the server returns one
or more <span class="ID">&lt;KeyBinding&gt;</span> elements that meet the
criteria specified in the request.</p>

<h3><a name="XKMS_2_0_Section_5_3_1" id="XKMS_2_0_Section_5_3_1" shape="rect">5.3.1</a> Validate Request <a name="ElementValidateRequest" id="ElementValidateRequest" shape="rect">Element <span class="ID">&lt;ValidateRequest&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_224" id="XKMS_2_0_Paragraph_224" class="markParagraph" shape="rect">[224]</a>The validate request message contains a <span class="ID">&lt;ValidateRequest&gt;</span> element:</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;QueryKeyBinding&gt;</b></span>&nbsp;&nbsp;&nbsp;<b>[Required]</b></dt>
      <dd>The key binding query to be matched in the response.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_225" id="XKMS_2_0_Paragraph_225" class="markParagraph" shape="rect">[225]</a>The following schema defines the <span class="ID">&lt;ValidateRequest&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- ValidateRequest --&gt;
   &lt;element name="ValidateRequest" type="xkms:ValidateRequestType"/&gt;
   &lt;complexType name="ValidateRequestType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:RequestAbstractType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:QueryKeyBinding"/&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /ValidateRequest --&gt;</pre>

<h3><a name="XKMS_2_0_Section_5_3_2" id="XKMS_2_0_Section_5_3_2" shape="rect">5.3.2</a> Validate Response <a name="ElementValidateResult" id="ElementValidateResult" shape="rect">Element <span class="ID">&lt;ValidateResult&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_226" id="XKMS_2_0_Paragraph_226" class="markParagraph" shape="rect">[226]</a>The validate response message contains a <span class="ID">&lt;ValidateResult&gt;</span> element:</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;Keybinding&gt;</b></span>&nbsp;&nbsp;&nbsp;<b>[Any Number]</b></dt>
      <dd>A sequence of <span class="ID">&lt;KeyBinding&gt;</span> key
        bindings that match the key binding query specified in the
        corresponding request. If no results are found the sequence is empty
        and the result code <span class="ID">NoMatch</span> is returned.
        In some circumstances a <span class="ID">Validate</span> operation
        MAY return multiple matching results.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_227" id="XKMS_2_0_Paragraph_227" class="markParagraph" shape="rect">[227]</a>The following schema defines the <span class="ID">&lt;ValidateResult&gt;</span> element and the <span class="ID">ValidateResultType</span> type.</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- ValidateResult --&gt;
   &lt;element name="ValidateResult" type="xkms:ValidateResultType"/&gt;
   &lt;complexType name="ValidateResultType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:ResultType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:KeyBinding" minOccurs="0"
                     maxOccurs="unbounded"/&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /ValidateResult --&gt;</pre>

<h1><a name="XKMS_2_0_Section_6" id="XKMS_2_0_Section_6" shape="rect">6</a> <a name="KeyRegistrationServiceOverview" id="KeyRegistrationServiceOverview" shape="rect">Key
Registration Service Description</a></h1>

<p><a name="XKMS_2_0_Paragraph_228" id="XKMS_2_0_Paragraph_228" class="markParagraph" shape="rect">[228]</a>The XML Key Registration Service Specification
permits management of information that is bound to a public key pair. The
X-KRSS service specification supports the following operations:</p>

<blockquote>
  <dl>
    <dt><span class="ID">Register</span></dt>
      <dd>Information is bound to a public key pair through a key binding.</dd>
    <dt><span class="ID">Reissue</span></dt>
      <dd>A previously registered key binding is reissued.</dd>
    <dt><span class="ID">Revoke</span></dt>
      <dd>A previously registered key binding is revoked.</dd>
    <dt><span class="ID">Recover</span></dt>
      <dd>The private key associated with a key binding is recovered.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_229" id="XKMS_2_0_Paragraph_229" class="markParagraph" shape="rect">[229]</a>An XKMS service may offer all or none of these
services.</p>

<p><a name="XKMS_2_0_Paragraph_230" id="XKMS_2_0_Paragraph_230" class="markParagraph" shape="rect">[230]</a>The <span class="ID">Register</span> operation
does not in itself place any requirement on the registration service to
communicate that information to any other party. In most applications,
however, a registration service will provide key information to other Web
Services such as those described in the XKMS specification or a separate
underlying PKI such as PKIX.</p>

<p><a name="XKMS_2_0_Paragraph_231" id="XKMS_2_0_Paragraph_231" class="markParagraph" shape="rect">[231]</a>The <span class="ID">Register</span> operation
MAY be used in a mode where client requests are accepted by an intermediary
such as a Local Registration Authority (LRA) and forwarded to a Master
Registration Authority (MRA). This mode of operation is entirely transparent
to the client which acts as if the LRA is the only registration authority
involved. The construction of the proof-of-possession of the private key and
the authentication information is completely separate of the message
authentication signature. This allows verification by both the LRA and any
other registration authority that it is relayed to, even if the message
authentication signature has been replaced by the LRA.</p>

<h2><a name="XKMS_2_0_Section_6_1" id="XKMS_2_0_Section_6_1" shape="rect">6.1</a> <a name="Registration" id="Registration" shape="rect">Registration</a></h2>

<p><a name="XKMS_2_0_Paragraph_232" id="XKMS_2_0_Paragraph_232" class="markParagraph" shape="rect">[232]</a>The <span class="ID">Register</span> request
is used to assert a binding of information to a public key pair. Generation
of the public key pair MAY be performed by either the client or the
Registration service.</p>

<p><a name="XKMS_2_0_Paragraph_233" id="XKMS_2_0_Paragraph_233" class="markParagraph" shape="rect">[233]</a>The Registration request message contains a
prototype of the requested key binding. The registration service MAY require
the client to provide additional information to authenticate the request. If
the public key pair is generated by the client, the service MAY require the
client to provide Proof of Possession of the private key.</p>

<p><a name="XKMS_2_0_Paragraph_234" id="XKMS_2_0_Paragraph_234" class="markParagraph" shape="rect">[234]</a>The prototype of the requested key binding may
contain only partial information, a key without a name or a name without a
key. In this case, the client is requesting that the registration service
provide the additional information required to complete the binding. All
information contained in the prototype of the requested key binding is
advisory to the service and MAY be ignored or overridden at the option of the
service.</p>

<p><a name="XKMS_2_0_Paragraph_235" id="XKMS_2_0_Paragraph_235" class="markParagraph" shape="rect">[235]</a>On receipt of a registration request, the
registration service verifies the authentication and POP information provided
(if any). If the registration service accepts the request a key binding is
registered. This key binding MAY include some, all or none of the information
provided by the prototype key binding and MAY include additional
information.</p>

<p><a name="XKMS_2_0_Paragraph_236" id="XKMS_2_0_Paragraph_236" class="markParagraph" shape="rect">[236]</a>The registration service MAY return part or
all of the registered key binding to the client.</p>

<p class="center"><a name="XKMS_2_0_Paragraph_237" id="XKMS_2_0_Paragraph_237" class="markParagraph" shape="rect">[237]</a> <img alt="Diagram shows the data passed from the client to the server for registration" src="Images/image010.gif" border="0" /></p>

<p class="caption"><a name="XKMS_2_0_Paragraph_238" id="XKMS_2_0_Paragraph_238" class="markParagraph" shape="rect">[238]</a>Figure 5:
Registration of a Key Binding</p>

<p><a name="XKMS_2_0_Paragraph_239" id="XKMS_2_0_Paragraph_239" class="markParagraph" shape="rect">[239]</a>The choice of generation of the key pair at
the client or the service depends on the application and the type of key. In
the case of a key used for signing purposes it is generally undesirable for
any party apart from the key bearer to have access to the private key. Should
access to the private key be lost a new key may be issued without affecting
the validity of any of the signatures created using the old private key.
Accordingly it is usually preferable for such keys to be generated at the
client and not the server.</p>

<p><a name="XKMS_2_0_Paragraph_240" id="XKMS_2_0_Paragraph_240" class="markParagraph" shape="rect">[240]</a>In the case of a private key used exclusively
for certain types of encryption, the loss of access to the private key may
result in the loss of access to the stored data encrypted under the key. In
such circumstances it is generally desirable for some form of key recovery to
be employed. In such systems the key pair is typically generated at the
service and delivered to the client.</p>

<p><a name="XKMS_2_0_Paragraph_241" id="XKMS_2_0_Paragraph_241" class="markParagraph" shape="rect">[241]</a>A key used for both signing and encryption
might be generated at the client or the server depending on whether key
recovery is to be supported.</p>

<h3><a name="XKMS_2_0_Section_6_1_1" id="XKMS_2_0_Section_6_1_1" shape="rect">6.1.1</a> <a name="ExampleRegistrationofClientGeneratedKeyPair" id="ExampleRegistrationofClientGeneratedKeyPair" shape="rect">Example: Registration of
Client-Generated Key Pair</a></h3>

<p><a name="XKMS_2_0_Paragraph_242" id="XKMS_2_0_Paragraph_242" class="markParagraph" shape="rect">[242]</a>Alice requests registration of an RSA key pair
for her email address <span class="ID">Alice@example.com</span>. Alice has
previously received from the XKMS service the code "024837" with which to
authenticate her request. Alice selects the pass phrase "Help I have revealed
my key" to authenticate herself should it be necessary to revoke the
registration at a later date.</p>

<p><a name="XKMS_2_0_Paragraph_243" id="XKMS_2_0_Paragraph_243" class="markParagraph" shape="rect">[243]</a>The X-KRSS request message contains the
following <span class="ID">&lt;RegisterRequest&gt;</span> element. Because
the registration request is for a client generated key the Authentication
element contains both a <span class="ID">&lt;ProofOfPossession&gt;</span>
element which demonstrates that the request is authorized by the holder of
the private key and a <span class="ID">&lt;KeyBindingAuthentication&gt;</span> element which
demonstrates that the request was made by a person who knows the
authentication code "024837".</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;RegisterRequest xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
   xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
   Id="I1494ac4351b7de5c174d455b7000e18f"
   Service="http://www.example.org/XKMS"
   xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#X509Cert&lt;/RespondWith&gt;
  &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#X509Chain&lt;/RespondWith&gt;
  &lt;PrototypeKeyBinding Id="I269e655567dbae568591c0a06957529e"&gt;
    &lt;ds:KeyInfo&gt;
      &lt;ds:KeyValue&gt;
        &lt;ds:RSAKeyValue&gt;
          &lt;ds:Modulus&gt;
            0nIsmR+aVW2egl5MIfOKy4HuMKkk9AZ/IQuDLVPlhzOfgngjVQCjr8uvmnqtNu8
            HBupui8LgGthO6U9D0CNT5mbmhIAErRADUMIAFsi7LzBarUvNWTqYNEJmcHsAUZ
            drdcDrkNnG7SzbuJx+GDNiHKVDQggPBLc1XagW20RMvok=
          &lt;/ds:Modulus&gt;
          &lt;ds:Exponent&gt;AQAB&lt;/ds:Exponent&gt;
        &lt;/ds:RSAKeyValue&gt;
      &lt;/ds:KeyValue&gt;
    &lt;/ds:KeyInfo&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/KeyUsage&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Encryption&lt;/KeyUsage&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Exchange&lt;/KeyUsage&gt;
    &lt;UseKeyWith Application="urn:ietf:rfc:2459"
         Identifier='C="US" O="Alice Corp" CN="Alice Aardvark"' /&gt;
    &lt;UseKeyWith Application="urn:ietf:rfc:2633"
         Identifier="alice@example.com" /&gt;
    &lt;UseKeyWith Application="http://ca.example.com/cps/20030401/class3"
         Identifier="alice@example.com" /&gt;
    &lt;RevocationCodeIdentifier&gt;
      5AEAai06hFJEkuqyDyqNh8k/u3M=
    &lt;/RevocationCodeIdentifier&gt;
  &lt;/PrototypeKeyBinding&gt;
  &lt;Authentication&gt;
    &lt;KeyBindingAuthentication&gt;
      &lt;Signature xmlns="http://www.w3.org/2000/09/xmldsig#"&gt;
        &lt;SignedInfo&gt;
          &lt;CanonicalizationMethod 
                  Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /&gt;
          &lt;SignatureMethod 
                  Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1" /&gt;
          &lt;Reference URI="#I269e655567dbae568591c0a06957529e"&gt;
            &lt;Transforms&gt;
              &lt;Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /&gt;
            &lt;/Transforms&gt;
            &lt;DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /&gt;
            &lt;DigestValue&gt;WCbpkifxJ1zIJ+V6/knZgxRhR34=&lt;/DigestValue&gt;
          &lt;/Reference&gt;
        &lt;/SignedInfo&gt;
        &lt;SignatureValue&gt;iJSKM+98hj5ae+btC2WjwBYP+/k=&lt;/SignatureValue&gt;
      &lt;/Signature&gt;
    &lt;/KeyBindingAuthentication&gt;
  &lt;/Authentication&gt;
  &lt;ProofOfPossession&gt;
    &lt;Signature xmlns="http://www.w3.org/2000/09/xmldsig#"&gt;
      &lt;SignedInfo&gt;
        &lt;CanonicalizationMethod 
                Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /&gt;
        &lt;SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" /&gt;
        &lt;Reference URI="#I269e655567dbae568591c0a06957529e"&gt;
          &lt;Transforms&gt;
            &lt;Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /&gt;
          &lt;/Transforms&gt;
          &lt;DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /&gt;
          &lt;DigestValue&gt;WCbpkifxJ1zIJ+V6/knZgxRhR34=&lt;/DigestValue&gt;
        &lt;/Reference&gt;
      &lt;/SignedInfo&gt;
      &lt;SignatureValue&gt;
        DcPw742vN120QNrCjCKw0jiCX3pUvbMeRkYjktZkn4nbgo1b7leXU0sJgXM2CY/
        oQugaRsgz18+qUzM0UX+jr1t1wtCMci5fjzVKZB63oZyKZ9+CJLcBCbirsgJAId
        +Pq9w4WiwKDf2AytsdXHlN5V1byQIkpfR1CypvBzQa1b4=
      &lt;/SignatureValue&gt;
    &lt;/Signature&gt;
  &lt;/ProofOfPossession&gt;
&lt;/RegisterRequest&gt; </pre>

<p><a name="XKMS_2_0_Paragraph_246" id="XKMS_2_0_Paragraph_246" class="markParagraph" shape="rect">[246]</a>The service accepts the registration and
returns the following response:</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;RegisterResult xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
      Id="I92ed24772e43843b3d23020ad9ec9754"
      Service="http://www.example.org/XKMS"
      ResultMajor="http://www.w3.org/2002/03/xkms#Success"
      RequestId="I1494ac4351b7de5c174d455b7000e18f"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;KeyBinding Id="Ia26450ebe93f62b3b3ab137fc6a61c36"&gt;
    &lt;ds:KeyInfo&gt;
      &lt;ds:X509Data&gt;
        &lt;ds:X509Certificate&gt;
          MIICEDCCAX2gAwIBAgIQimXeUAxYJbJMady9vV1bLjAJBgUrDgMCHQUAMBIxEDA
          OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMDUwODE1MDY1OTU5Wj
          ArMSkwJwYDVQQDEyBBbGljZSBBYXJkdmFyayBPPUFsaWNlIENvcnAgQz1VUzCBn
          zANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0nIsmR+aVW2egl5MIfOKy4HuMKkk
          9AZ/IQuDLVPlhzOfgngjVQCjr8uvmnqtNu8HBupui8LgGthO6U9D0CNT5mbmhIA
          ErRADUMIAFsi7LzBarUvNWTqYNEJmcHsAUZdrdcDrkNnG7SzbuJx+GDNiHKVDQg
          gPBLc1XagW20RMvokCAwEAAaNWMFQwDQYDVR0KBAYwBAMCBkAwQwYDVR0BBDwwO
          oAQAaVOkaVLLKoFmLN37pC8uqEUMBIxEDAOBgNVBAMTB1Rlc3QgQ0GCEC4MndUX
          jPG1TZxVKg+HutAwCQYFKw4DAh0FAAOBgQABU91ka7IlkXCfv4Zh2Ohwgg2yObt
          Y3+6C/BTFGrOEBJDy+DoxJ/NuBF18w3rrrR18xE6jNKYLCQb8zUGk4QOG5Y+HT/
          QTTFvWkiOLXcpTuhnOhXatr42FoYpDkjx2QWK+J5Q2l/Rgjgc/0ZV8U/kD8UuRk
          Xp4AZh7QsiX8AcO0w==
        &lt;/ds:X509Certificate&gt;
        &lt;ds:X509Certificate&gt;
          MIIB9zCCAWSgAwIBAgIQLgyd1ReM8bVNnFUqD4e60DAJBgUrDgMCHQUAMBIxEDA
          OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMTAwODE1MDcwMDAwWj
          ASMRAwDgYDVQQDEwdUZXN0IENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBg
          QCn23HHp+HtXpiyKVSDtdE3dO0r0oLB/H9sxUEkeXB8oMxwbhdcizWH92zrtm1V
          fVtxkfmwF14ZXoyDZHeZXuCOtAfz/mW6s2gmfD45TfFFVGksDGVRNK5XmKXA5sE
          C51RCvaxzGBdGDlCuVPqX7Cq3IcZpRU1IXbi5YzGwV7j6LwIDAQABo1YwVDANBg
          NVHQoEBjAEAwIHgDBDBgNVHQEEPDA6gBABpU6RpUssqgWYs3fukLy6oRQwEjEQM
          A4GA1UEAxMHVGVzdCBDQYIQLgyd1ReM8bVNnFUqD4e60DAJBgUrDgMCHQUAA4GB
          ABDYD4Fwx2dscu+BgYcZ+GoQQtCJkwJEXytb4zlNl7HLFKbXSw4m0blQquIsfsi
          QgFYAQBXSbu7aeUqqmSGHvILu3BGwVOKjxbHfcM4/MefuTtpOpCN40wy3YwwngD
          tHTaIqm8NwS966PE+W9f8kD70q5FNwf+GF/lX9qGc/x435
        &lt;/ds:X509Certificate&gt;
      &lt;/ds:X509Data&gt;
    &lt;/ds:KeyInfo&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/KeyUsage&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Encryption&lt;/KeyUsage&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Exchange&lt;/KeyUsage&gt;
    &lt;UseKeyWith Application="urn:ietf:rfc:2459" Identifier='C="US"
          O="Alice Corp" CN="Alice Aardvark"' /&gt;
    &lt;UseKeyWith Application="urn:ietf:rfc:2633"
          Identifier="alice@example.com" /&gt;
    &lt;UseKeyWith Application="http://ca.example.com/cps/20030401/class3"
          Identifier="alice@example.com" /&gt;
    &lt;Status StatusValue="http://www.w3.org/2002/03/xkms#Valid"&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/ValidReason&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#IssuerTrust&lt;/ValidReason&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#RevocationStatus&lt;/ValidReason&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#ValidityInterval&lt;/ValidReason&gt;
    &lt;/Status&gt;
  &lt;/KeyBinding&gt;
&lt;/RegisterResult&gt;</pre>

<h3><a name="XKMS_2_0_Section_6_1_2" id="XKMS_2_0_Section_6_1_2" shape="rect">6.1.2</a> <a name="ExampleRegistrationofServiceGeneratedKeyPair" id="ExampleRegistrationofServiceGeneratedKeyPair" shape="rect">Example: Registration of
Service-Generated Key Pair</a></h3>

<p><a name="XKMS_2_0_Paragraph_247" id="XKMS_2_0_Paragraph_247" class="markParagraph" shape="rect">[247]</a>The request for registration of a service
generated key pair omits the public key data and requests that private key
data be returned with the response.</p>

<p><a name="XKMS_2_0_Paragraph_248" id="XKMS_2_0_Paragraph_248" class="markParagraph" shape="rect">[248]</a>Bob requests a server generated key pair after
receiving the authentication code

<code>3N9CJ-K4JKS-04JWF-0934J-SR09JW-IK4</code> through some
out-of-band mechanism.&#xA0; The request specifies only <span class="ID">Encryption</span> and <span class="ID">Exchange</span> key uses as
the key is to be escrowed for possible later recovery and the security policy
of the issuer does not allow escrow of signature keys.&#xA0;</p>

<p><a name="XKMS_2_0_Paragraph_249" id="XKMS_2_0_Paragraph_249" class="markParagraph" shape="rect">[249]</a>The server generates a public-private key pair
in response to the request, generates appropriate certifications, and returns
the result to the client.&#xA0; The result includes the private key value
encrypted using a key derived from the authentication code value as described
in Section 8.1; see also Appendix C.1.3. The client can decrypt the
private key by computing the decryption key from the authentication code
value in the same manner as the service.</p>

<p><a name="XKMS_2_0_Paragraph_250" id="XKMS_2_0_Paragraph_250" class="markParagraph" shape="rect">[250]</a>To avoid leaking the private key value to
unauthorized entities it is critical that the service and client protect the
authentication code value from disclosure.&#xA0; The service should not reuse
authentication code values nor should the key derived from an authentication
code be used to encrypt more than a single private key communication.</p>

<p><a name="XKMS_2_0_Paragraph_251" id="XKMS_2_0_Paragraph_251" class="markParagraph" shape="rect">[251]</a>The calculation of the authentication data and
encryption of the private key for this example is shown in Appendix C.</p>

<p><a name="XKMS_2_0_Paragraph_252" id="XKMS_2_0_Paragraph_252" class="markParagraph" shape="rect">[252]</a>The response includes both the public key data
and the encrypted private key:</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">


&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;RegisterResult xmlns:ds="http://www.w3.org/2000/09/xmldsig#" 
      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" 
      Id="I2eb0b29bf38eeecfc5f099c8ca149f98" 
      Service="http://www.example.org/XKMS"
      ResultMajor="http://www.w3.org/2002/03/xkms#Success"
      RequestId="I4e442fc461a83f320d7a3afb4f2454a9" 
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;KeyBinding Id="Ia500663f4e4e578447407a38b9049c8b"&gt;
    &lt;ds:KeyInfo&gt;
      &lt;ds:X509Data&gt;
        &lt;ds:X509Certificate&gt;
          MIICCTCCAXagAwIBAgIQe0Sk4xr1VolGFFNMkCx07TAJBgUrDgMCHQUAMBIxEDA
          OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMDUwODE1MDY1OTU5Wj
          AkMSIwIAYDVQQDExlCb2IgQmFrZXIgTz1Cb2IgQ29ycCBDPVVTMIGfMA0GCSqGS
          Ib3DQEBAQUAA4GNADCBiQKBgQDcUW1ZSy8RqNC3ZJ5IX5G8DFZ08+HkZKVCenxI
          O++q8LATo9dxFasgaZXu3A1/ZNRcLFi7O1RQKUwjLXgHRD6TV6Pad6SZgvv4hzc
          MMZUVVpg+jFpFjRjaVXy06t7KdZ6CkVshNdzxXpjTZB9Hk7s+fX/XQSWyVoX9MX
          wxAapgTwIDAQABo1YwVDANBgNVHQoEBjAEAwIGQDBDBgNVHQEEPDA6gBABpU6Rp
          UssqgWYs3fukLy6oRQwEjEQMA4GA1UEAxMHVGVzdCBDQYIQLgyd1ReM8bVNnFUq
          D4e60DAJBgUrDgMCHQUAA4GBAF4jP1gGDbaq3rg/Vo3JY7EDNTp0HmwLiPMLmdn
          B3WTIGFcjS/jZFzRCbvKPeiPTZ6kRkGgydFOuCo5HMAxIks/LtnKFd/0qYT+AOD
          q/rCrwSx+F+Ro2rf9tPpja9o7gANqxs6Pm7f1QSPZO57bT/6afiVm7NdaCfjgMp
          hb+XNyn
        &lt;/ds:X509Certificate&gt;
        &lt;ds:X509Certificate&gt;
          MIIB9zCCAWSgAwIBAgIQLgyd1ReM8bVNnFUqD4e60DAJBgUrDgMCHQUAMBIxEDA
          OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMTAwODE1MDcwMDAwWj
          ASMRAwDgYDVQQDEwdUZXN0IENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBg
          QCn23HHp+HtXpiyKVSDtdE3dO0r0oLB/H9sxUEkeXB8oMxwbhdcizWH92zrtm1V
          fVtxkfmwF14ZXoyDZHeZXuCOtAfz/mW6s2gmfD45TfFFVGksDGVRNK5XmKXA5sE
          C51RCvaxzGBdGDlCuVPqX7Cq3IcZpRU1IXbi5YzGwV7j6LwIDAQABo1YwVDANBg
          NVHQoEBjAEAwIHgDBDBgNVHQEEPDA6gBABpU6RpUssqgWYs3fukLy6oRQwEjEQM
          A4GA1UEAxMHVGVzdCBDQYIQLgyd1ReM8bVNnFUqD4e60DAJBgUrDgMCHQUAA4GB
          ABDYD4Fwx2dscu+BgYcZ+GoQQtCJkwJEXytb4zlNl7HLFKbXSw4m0blQquIsfsi
          QgFYAQBXSbu7aeUqqmSGHvILu3BGwVOKjxbHfcM4/MefuTtpOpCN40wy3YwwngD
          tHTaIqm8NwS966PE+W9f8kD70q5FNwf+GF/lX9qGc/x435
        &lt;/ds:X509Certificate&gt;
      &lt;/ds:X509Data&gt;
    &lt;/ds:KeyInfo&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Encryption&lt;/KeyUsage&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Exchange&lt;/KeyUsage&gt;
    &lt;UseKeyWith Application="urn:ietf:rfc:2459" Identifier='C="UK"
          O="Bob Corp" CN="Bob Baker"' /&gt;
    &lt;UseKeyWith Application="urn:ietf:rfc:2633" 
          Identifier="bob@example.com" /&gt;
    &lt;Status StatusValue="http://www.w3.org/2002/03/xkms#Valid"&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/ValidReason&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#IssuerTrust&lt;/ValidReason&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#RevocationStatus&lt;/ValidReason&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#ValidityInterval&lt;/ValidReason&gt;
    &lt;/Status&gt;
  &lt;/KeyBinding&gt;
  &lt;PrivateKey&gt;
    &lt;xenc:EncryptedData&gt;
      &lt;xenc:EncryptionMethod 
            Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc" /&gt;
      &lt;xenc:CipherData&gt;
        &lt;xenc:CipherValue&gt;
          Em6xEIvjjlqqeEVOdf9Fq2E6ycz5OZrUU3jw7fBMhiM8BciSC3qry7GAlvRFp/D
          iD5zZduSaDriD27HGOuWo1fLihgOcw5sw+G9nyhfxKo7IZ2DEss0DD5H3AAZnTW
          reTYwposEBiBcuea4nYwzVWYFsIcplPYsHnXg1cq7MtMfaSu1WA4P/tQLhM1mdO
          V6FHkEHdyL4FBaZbjfmkB1Z++Yb0OlOUTNCQLcNxDkF6lNM75sprB+2FtwG1u9x
          ZnFXwP0Yt5euwCKeBRFm8Sfsf67CTIjKQ0+l9b66l/W1VszBgq2hMgSi8w+qILw
          mFP7p4AhJJNaYlOXHbJAQL6dOe4jtyEkjhEfXXJAO8497Dat9JU5l4Aeb8Mw5BA
          KDBT8RKnQTHqRTQZ8h5FPTapD1Av3KllxrIwRJG155enFrVwlxm6mLD+z4WeAdn
          U5l9gUSaS13E0PlBApi98zDjILihycV1m90SzUNRIuSnw/8tV0ykS3uquDSmNAO
          5YX7UZtieFMyQ2U8XBNRYYftLaN6RfPCejtxXZxIsGtvxyzzL+Yf3bl595J+IOt
          n3M73bBvkdq3ACgOG0SCaETlTE5i60Trw19um+f7gAD4QKXawKw72gyQ70GccML
          Dh4mypfstCbXxCG5nntGAPkCqT/c+t0TdPc7VrtyFLB3ta9z9yiRkeKqvkVZpvb
          lQwykzDd3fgn9ds1liuy8RagrVO6Zczii9b7AQmQ9dekw+QDVkeS53xNTbByau/
          aYAjOjIu4Xb6QNPOrNfHYOLMwGuf19o5nAjZEadZU83QhJq/ofwv3EL7tVMlOpF
          K7n6Apk7cwmS4OtU71cbAVBMcAsh3KbfrHm0TCy67DEZLtdE9ksTekZMpDKXayQ
          uRI0nyKugmwOVvI6oxyMt9JHRiSJRfyYF6yQoyGHGyX8nLX5imG8WNxHBur7j9h
          rt8Nf9XRvXY2N9RRfpoDTexN/KZJIZJhDFsY5gsjs1xy0kZqushvZ+jeElGylXs
          U/CSXwu3fgeM4qTnMKvJvHl9K4KlDtjIyYIRlBt22n238ADjMLFgUWS4+lyoWZ+
          EJPzo0y9CIqb2uUNqp5cSAnb0v7s7gsq6yTqaB9fFSrV0oLH/I65Xoa7XW4mY06
          xgwshdC/HHCaTyP/OEgq5Iv2VZUlWTGp1KuEmfko6MaRB/JqMhjNupi1esYTpre
          JsBexGjBiCpPPieykC8ngC8GEWLRUyWPdDCybiM/CRFdCvgD5n/Js7nkNY0JGLf
          BY0cGnkrxv7e5+5S1Be33yWonJSs8QQ6+y4/V5vPe+5tH8++VFm6dZXtL/oOU0S
          DyHruc0yGmdu9GCibRcaU49rPLWbwSfg/g7mVibah2YBXkDDolW1U6pOpry9fHM
          kEODQrnoIvGZLaOZ8UQ7jnI92WOTySdxylFL2ZvEHadlUKKN2KtW4zs7nhcQ6Tf
          6gjYLNXX9ztkNgCKCZRzI4TXOM2khtPhxTv83rfV0hlx1mtRjlifDdbiWInrCW7
          7IPgMEIkEa1oXoKcYb1pUw+W9xzeTp4hTx16izBqC9aWNSYJrT1AvX/Xa+oY8F4
          p+YGGgOSvn9Cb2h1Va8YTb3ntqWaFSE+0/YyOHYgCIsaeYXV9YFN8A+fw          
        &lt;/xenc:CipherValue&gt;
      &lt;/xenc:CipherData&gt;
    &lt;/xenc:EncryptedData&gt;
  &lt;/PrivateKey&gt;
&lt;/RegisterResult&gt;</pre>

<h2><a name="XKMS_2_0_Section_6_2" id="XKMS_2_0_Section_6_2" shape="rect">6.2</a> <a name="Reissue" id="Reissue" shape="rect">Reissue</a></h2>

<p><a name="XKMS_2_0_Paragraph_253" id="XKMS_2_0_Paragraph_253" class="markParagraph" shape="rect">[253]</a>A Registration service MAY permit clients to
reissue previously issued key bindings. A reissue request is similar to the
initial registration of a key.</p>

<p><a name="XKMS_2_0_Paragraph_254" id="XKMS_2_0_Paragraph_254" class="markParagraph" shape="rect">[254]</a>The principal reason a client would make a
Reissue request is to cause the registration service to generate new
credentials in the underlying PKI, e.g., X.509 Certificates.</p>

<h3><a name="XKMS_2_0_Section_6_2_1" id="XKMS_2_0_Section_6_2_1" shape="rect">6.2.1</a> <a name="ExampleReissue" id="ExampleReissue" shape="rect">Example: Reissue</a></h3>

<p><a name="XKMS_2_0_Paragraph_255" id="XKMS_2_0_Paragraph_255" class="markParagraph" shape="rect">[255]</a>Alice requests reissue of her previously
issued RSA key pair for her email address.</p>

<p><a name="XKMS_2_0_Paragraph_256" id="XKMS_2_0_Paragraph_256" class="markParagraph" shape="rect">[256]</a>The X-KRSS request message contains the
following <span class="ID">&lt;ReissueRequest&gt;</span> element:</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;ReissueRequest xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
      Id="I3a682dfb94cc8e9b3b648026783a8094"
      Service="http://www.example.org/XKMS"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#X509Cert&lt;/RespondWith&gt;
  &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#X509Chain&lt;/RespondWith&gt;
  &lt;ReissueKeyBinding Id="I518fc89b03369bccec3d1ee9d985c436"&gt;
    &lt;ds:KeyInfo&gt;
      &lt;ds:X509Data&gt;
        &lt;ds:X509Certificate&gt;
          MIICEDCCAX2gAwIBAgIQimXeUAxYJbJMady9vV1bLjAJBgUrDgMCHQUAMBIxEDA
          OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMDUwODE1MDY1OTU5Wj
          ArMSkwJwYDVQQDEyBBbGljZSBBYXJkdmFyayBPPUFsaWNlIENvcnAgQz1VUzCBn
          zANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0nIsmR+aVW2egl5MIfOKy4HuMKkk
          9AZ/IQuDLVPlhzOfgngjVQCjr8uvmnqtNu8HBupui8LgGthO6U9D0CNT5mbmhIA
          ErRADUMIAFsi7LzBarUvNWTqYNEJmcHsAUZdrdcDrkNnG7SzbuJx+GDNiHKVDQg
          gPBLc1XagW20RMvokCAwEAAaNWMFQwDQYDVR0KBAYwBAMCBkAwQwYDVR0BBDwwO
          oAQAaVOkaVLLKoFmLN37pC8uqEUMBIxEDAOBgNVBAMTB1Rlc3QgQ0GCEC4MndUX
          jPG1TZxVKg+HutAwCQYFKw4DAh0FAAOBgQABU91ka7IlkXCfv4Zh2Ohwgg2yObt
          Y3+6C/BTFGrOEBJDy+DoxJ/NuBF18w3rrrR18xE6jNKYLCQb8zUGk4QOG5Y+HT/
          QTTFvWkiOLXcpTuhnOhXatr42FoYpDkjx2QWK+J5Q2l/Rgjgc/0ZV8U/kD8UuRk
          Xp4AZh7QsiX8AcO0w==
        &lt;/ds:X509Certificate&gt;
      &lt;/ds:X509Data&gt;
    &lt;/ds:KeyInfo&gt;
    &lt;Status StatusValue="http://www.w3.org/2002/03/xkms#Valid" /&gt;
  &lt;/ReissueKeyBinding&gt;
  &lt;Authentication&gt;
    &lt;KeyBindingAuthentication&gt;
      &lt;Signature xmlns="http://www.w3.org/2000/09/xmldsig#"&gt;
        &lt;SignedInfo&gt;
          &lt;CanonicalizationMethod
                Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /&gt;
          &lt;SignatureMethod
                Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1" /&gt;
          &lt;Reference URI="#I518fc89b03369bccec3d1ee9d985c436"&gt;
            &lt;Transforms&gt;
              &lt;Transform
                    Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"&gt;
                &lt;ec:InclusiveNamespaces PrefixList="ds xenc #default"
                      xmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#" /&gt;
              &lt;/Transform&gt;
            &lt;/Transforms&gt;
            &lt;DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /&gt;
            &lt;DigestValue&gt;qnhsUF9RMxxGydG/5KdJjWhtBFE=&lt;/DigestValue&gt;
          &lt;/Reference&gt;
        &lt;/SignedInfo&gt;
        &lt;SignatureValue&gt;+gKw3b0qi9BaIqmN1gIyvj1UxRs=&lt;/SignatureValue&gt;
      &lt;/Signature&gt;
    &lt;/KeyBindingAuthentication&gt;
  &lt;/Authentication&gt;
  &lt;ProofOfPossession&gt;
    &lt;Signature xmlns="http://www.w3.org/2000/09/xmldsig#"&gt;
      &lt;SignedInfo&gt;
        &lt;CanonicalizationMethod
              Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /&gt;
        &lt;SignatureMethod
              Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" /&gt;
        &lt;Reference URI="#I518fc89b03369bccec3d1ee9d985c436"&gt;
          &lt;Transforms&gt;
            &lt;Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"&gt;
              &lt;ec:InclusiveNamespaces PrefixList="ds xenc #default"
                    xmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#" /&gt;
            &lt;/Transform&gt;
          &lt;/Transforms&gt;
          &lt;DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"
                /&gt;
          &lt;DigestValue&gt;qnhsUF9RMxxGydG/5KdJjWhtBFE=&lt;/DigestValue&gt;
        &lt;/Reference&gt;
      &lt;/SignedInfo&gt;
      &lt;SignatureValue&gt;
sP/RWAA7fnv86ZgwOlfxTwN05akxyf65rCw7rwXNkJmx0fxUNFJ+qKDqmIh2KyvFyBut6FredSXj
t3iDIXUKMmjA2/VPGEX8yyd71DbRqf9dXb2FzkvkKrCbYumlavbrChpEwiMUqk2rd5tjkFAZjYRA
tuURoFfmoOYY/M+mNUU=
      &lt;/SignatureValue&gt;
    &lt;/Signature&gt;
  &lt;/ProofOfPossession&gt;
&lt;/ReissueRequest&gt;</pre>

<p><a name="XKMS_2_0_Paragraph_257" id="XKMS_2_0_Paragraph_257" class="markParagraph" shape="rect">[257]</a>The service accepts the registration and
returns the following response:</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;ReissueResult xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
      Id="I4f0f13b32e4f43f0c1b390b5186fa997"
      Service="http://www.example.org/XKMS"
      ResultMajor="http://www.w3.org/2002/03/xkms#Success"
      RequestId="I3a682dfb94cc8e9b3b648026783a8094"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;KeyBinding Id="I9a894fff4149d2351c24241886e3900e"&gt;
    &lt;ds:KeyInfo&gt;
      &lt;ds:X509Data&gt;
        &lt;ds:X509Certificate&gt;
          MIICEDCCAX2gAwIBAgIQimXeUAxYJbJMady9vV1bLjAJBgUrDgMCHQUAMBIxEDA
          OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMDUwODE1MDY1OTU5Wj
          ArMSkwJwYDVQQDEyBBbGljZSBBYXJkdmFyayBPPUFsaWNlIENvcnAgQz1VUzCBn
          zANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0nIsmR+aVW2egl5MIfOKy4HuMKkk
          9AZ/IQuDLVPlhzOfgngjVQCjr8uvmnqtNu8HBupui8LgGthO6U9D0CNT5mbmhIA
          ErRADUMIAFsi7LzBarUvNWTqYNEJmcHsAUZdrdcDrkNnG7SzbuJx+GDNiHKVDQg
          gPBLc1XagW20RMvokCAwEAAaNWMFQwDQYDVR0KBAYwBAMCBkAwQwYDVR0BBDwwO
          oAQAaVOkaVLLKoFmLN37pC8uqEUMBIxEDAOBgNVBAMTB1Rlc3QgQ0GCEC4MndUX
          jPG1TZxVKg+HutAwCQYFKw4DAh0FAAOBgQABU91ka7IlkXCfv4Zh2Ohwgg2yObt
          Y3+6C/BTFGrOEBJDy+DoxJ/NuBF18w3rrrR18xE6jNKYLCQb8zUGk4QOG5Y+HT/
          QTTFvWkiOLXcpTuhnOhXatr42FoYpDkjx2QWK+J5Q2l/Rgjgc/0ZV8U/kD8UuRk
          Xp4AZh7QsiX8AcO0w==
        &lt;/ds:X509Certificate&gt;
        &lt;ds:X509Certificate&gt;
          MIIB9zCCAWSgAwIBAgIQLgyd1ReM8bVNnFUqD4e60DAJBgUrDgMCHQUAMBIxEDA
          OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMTAwODE1MDcwMDAwWj
          ASMRAwDgYDVQQDEwdUZXN0IENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBg
          QCn23HHp+HtXpiyKVSDtdE3dO0r0oLB/H9sxUEkeXB8oMxwbhdcizWH92zrtm1V
          fVtxkfmwF14ZXoyDZHeZXuCOtAfz/mW6s2gmfD45TfFFVGksDGVRNK5XmKXA5sE
          C51RCvaxzGBdGDlCuVPqX7Cq3IcZpRU1IXbi5YzGwV7j6LwIDAQABo1YwVDANBg
          NVHQoEBjAEAwIHgDBDBgNVHQEEPDA6gBABpU6RpUssqgWYs3fukLy6oRQwEjEQM
          A4GA1UEAxMHVGVzdCBDQYIQLgyd1ReM8bVNnFUqD4e60DAJBgUrDgMCHQUAA4GB
          ABDYD4Fwx2dscu+BgYcZ+GoQQtCJkwJEXytb4zlNl7HLFKbXSw4m0blQquIsfsi
          QgFYAQBXSbu7aeUqqmSGHvILu3BGwVOKjxbHfcM4/MefuTtpOpCN40wy3YwwngD
          tHTaIqm8NwS966PE+W9f8kD70q5FNwf+GF/lX9qGc/x435
        &lt;/ds:X509Certificate&gt;
      &lt;/ds:X509Data&gt;
    &lt;/ds:KeyInfo&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/KeyUsage&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Encryption&lt;/KeyUsage&gt;
    &lt;KeyUsage&gt;http://www.w3.org/2002/03/xkms#Exchange&lt;/KeyUsage&gt;
    &lt;UseKeyWith Application="urn:ietf:rfc:2633"
          Identifier="alice@example.com" /&gt;
    &lt;Status StatusValue="http://www.w3.org/2002/03/xkms#Valid"&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/ValidReason&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#IssuerTrust&lt;/ValidReason&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#RevocationStatus&lt;/ValidReason&gt;
      &lt;ValidReason&gt;http://www.w3.org/2002/03/xkms#ValidityInterval&lt;/ValidReason&gt;
    &lt;/Status&gt;
  &lt;/KeyBinding&gt;
&lt;/ReissueResult&gt;</pre>

<h2><a name="XKMS_2_0_Section_6_3" id="XKMS_2_0_Section_6_3" shape="rect">6.3</a> <a name="Revocation" id="Revocation" shape="rect">Revocation</a></h2>

<p><a name="XKMS_2_0_Paragraph_258" id="XKMS_2_0_Paragraph_258" class="markParagraph" shape="rect">[258]</a>A Registration service MAY permit clients to
revoke previously issued key bindings. A revocation request need only contain
sufficient information to identify the key binding to be revoked and the
authority for the revocation request.</p>

<p><a name="XKMS_2_0_Paragraph_259" id="XKMS_2_0_Paragraph_259" class="markParagraph" shape="rect">[259]</a>If an XKMS key binding is bound to a data
object in an underlying PKI the revocation of the key binding SHOULD result
in the revocation of the underlying data object. For example if the XKMS key
binding is bound to an X.509 certificate the revocation of the key binding
SHOULD result in revocation of the underlying certificate.</p>

<h3><a name="XKMS_2_0_Section_6_3_1" id="XKMS_2_0_Section_6_3_1" shape="rect">6.3.1</a> <a name="ExampleRevocation" id="ExampleRevocation" shape="rect">Example: Revocation</a></h3>

<p><a name="XKMS_2_0_Paragraph_260" id="XKMS_2_0_Paragraph_260" class="markParagraph" shape="rect">[260]</a>For some reason Alice requests the
registration service revoke the binding for her public key. Alice
authenticates herself using the pass phrase value established during
registration.</p>

<p><a name="XKMS_2_0_Paragraph_261" id="XKMS_2_0_Paragraph_261" class="markParagraph" shape="rect">[261]</a>The request message is:</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;RevokeRequest xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
      Id="I2aa2c2f37195c9c4364c55f15df68091"
      Service="http://www.example.org/XKMS"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;RevokeKeyBinding Id="Ie91dfbf1c948d5cf142099676968caf1"&gt;
    &lt;ds:KeyInfo&gt;
      &lt;ds:X509Data&gt;
        &lt;ds:X509Certificate&gt;
          MIICEDCCAX2gAwIBAgIQimXeUAxYJbJMady9vV1bLjAJBgUrDgMCHQUAMBIxEDA
          OBgNVBAMTB1Rlc3QgQ0EwHhcNMDMwODE1MDcwMDAwWhcNMDUwODE1MDY1OTU5Wj
          ArMSkwJwYDVQQDEyBBbGljZSBBYXJkdmFyayBPPUFsaWNlIENvcnAgQz1VUzCBn
          zANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0nIsmR+aVW2egl5MIfOKy4HuMKkk
          9AZ/IQuDLVPlhzOfgngjVQCjr8uvmnqtNu8HBupui8LgGthO6U9D0CNT5mbmhIA
          ErRADUMIAFsi7LzBarUvNWTqYNEJmcHsAUZdrdcDrkNnG7SzbuJx+GDNiHKVDQg
          gPBLc1XagW20RMvokCAwEAAaNWMFQwDQYDVR0KBAYwBAMCBkAwQwYDVR0BBDwwO
          oAQAaVOkaVLLKoFmLN37pC8uqEUMBIxEDAOBgNVBAMTB1Rlc3QgQ0GCEC4MndUX
          jPG1TZxVKg+HutAwCQYFKw4DAh0FAAOBgQABU91ka7IlkXCfv4Zh2Ohwgg2yObt
          Y3+6C/BTFGrOEBJDy+DoxJ/NuBF18w3rrrR18xE6jNKYLCQb8zUGk4QOG5Y+HT/
          QTTFvWkiOLXcpTuhnOhXatr42FoYpDkjx2QWK+J5Q2l/Rgjgc/0ZV8U/kD8UuRk
          Xp4AZh7QsiX8AcO0w==
        &lt;/ds:X509Certificate&gt;
      &lt;/ds:X509Data&gt;
    &lt;/ds:KeyInfo&gt;
    &lt;Status StatusValue="http://www.w3.org/2002/03/xkms#Indeterminate" /&gt;
  &lt;/RevokeKeyBinding&gt;
  &lt;RevocationCode&gt;PHx8li2SUhrJv2e1DyeWbGbD6rs=&lt;/RevocationCode&gt;
&lt;/RevokeRequest&gt;</pre>

<p><a name="XKMS_2_0_Paragraph_262" id="XKMS_2_0_Paragraph_262" class="markParagraph" shape="rect">[262]</a>The service responds that the key binding has
been revoked:</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;RevokeResult xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"
      Id="I252433a097631dca9a2775493f39c7d7"
      Service="http://www.example.org/XKMS"
      ResultMajor="http://www.w3.org/2002/03/xkms#Success"
      RequestId="I2aa2c2f37195c9c4364c55f15df68091"
      xmlns="http://www.w3.org/2002/03/xkms#" /&gt;</pre>

<h2><a name="XKMS_2_0_Section_6_4" id="XKMS_2_0_Section_6_4" shape="rect">6.4</a> <a name="KeyRecovery" id="KeyRecovery" shape="rect">Key Recovery</a></h2>

<p><a name="XKMS_2_0_Paragraph_263" id="XKMS_2_0_Paragraph_263" class="markParagraph" shape="rect">[263]</a>A Registration service MAY support key
recovery. For key recovery to be possible the private key to be recovered
MUST have been previously escrowed with the recovery service, for example by
means of the X-KRSS registration of a server generated key. A key recovery
request is similar to the initial registration of a key except that since the
registration service might not have a record of the key binding to be
recovered the result code <span class="ID">NotFound</span> MAY be
returned.</p>

<p><a name="XKMS_2_0_Paragraph_264" id="XKMS_2_0_Paragraph_264" class="markParagraph" shape="rect">[264]</a>The key recovery service is likely to require
time to respond to the recovery request. Clients supporting key recovery
SHOULD support asynchronous processing.</p>

<p><a name="XKMS_2_0_Paragraph_265" id="XKMS_2_0_Paragraph_265" class="markParagraph" shape="rect">[265]</a>The security policy of the issuer MAY consider
the key recovery process itself as an actual or potential compromise of the
recovered key and thus require the revocation of all associated key bindings,
particularly if the key recovery was requested by a third party such as the
supervisor of the key holder.</p>

<h3><a name="XKMS_2_0_Section_6_4_1" id="XKMS_2_0_Section_6_4_1" shape="rect">6.4.1</a> <a name="ExampleKeyRecovery" id="ExampleKeyRecovery" shape="rect">Example: Key
Recovery</a></h3>

<p><a name="XKMS_2_0_Paragraph_266" id="XKMS_2_0_Paragraph_266" class="markParagraph" shape="rect">[266]</a>Bob has forgotten the private key which he
obtained in the earlier registration example. He first contacts the
administrator of the key recovery service using an out-of-band authentication
procedure determined by site policy. The key recovery administrator issues to
Bob (using an out of band method) the key recovery authorization code "<span class="ID">A8YUT VUHHU C9H29 8Y43U H9J3I 23</span>". In this case the code is
read over the telephone and so it would be inconvenient to be required to
specify spacing between the code blocks or capitalization.</p>

<p><a name="XKMS_2_0_Paragraph_267" id="XKMS_2_0_Paragraph_267" class="markParagraph" shape="rect">[267]</a>The request parameters for the key recovery
are:</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">



&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;RecoverRequest xmlns:ds="http://www.w3.org/2000/09/xmldsig#" 
      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" 
      Id="I66f40510c322d281602ce76b9eb04d7d" 
      Service="http://www.example.org/XKMS" 
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;RespondWith&gt;http://www.w3.org/2002/03/xkms#PrivateKey&lt;/RespondWith&gt;
  &lt;RecoverKeyBinding Id="I29cb8ac8a2ad878f7be44edfe53ea77a"&gt;
    &lt;ds:KeyInfo&gt;
      &lt;ds:KeyValue&gt;
        &lt;ds:RSAKeyValue&gt;
          &lt;ds:Modulus&gt;
            3FFtWUsvEajQt2SeSF+RvAxWdPPh5GSlQnp8SDvvqvCwE6PXcRWrIGmV7twNf2T
            UXCxYuztUUClMIy14B0Q+k1ej2nekmYL7+Ic3DDGVFVaYPoxaRY0Y2lV8tOreyn
            WegpFbITXc8V6Y02QfR5O7Pn1/10ElslaF/TF8MQGqYE8=
          &lt;/ds:Modulus&gt;
          &lt;ds:Exponent&gt;AQAB&lt;/ds:Exponent&gt;
        &lt;/ds:RSAKeyValue&gt;
      &lt;/ds:KeyValue&gt;
    &lt;/ds:KeyInfo&gt;
    &lt;Status StatusValue="http://www.w3.org/2002/03/xkms#Indeterminate" /&gt;
  &lt;/RecoverKeyBinding&gt;
  &lt;Authentication&gt;
    &lt;KeyBindingAuthentication&gt;
      &lt;Signature xmlns="http://www.w3.org/2000/09/xmldsig#"&gt;
        &lt;SignedInfo&gt;
          &lt;CanonicalizationMethod 
                Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /&gt;
          &lt;SignatureMethod 
                Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1" /&gt;
          &lt;Reference URI="#I29cb8ac8a2ad878f7be44edfe53ea77a"&gt;
            &lt;Transforms&gt;
              &lt;Transform 
                    Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"&gt;
                &lt;ec:InclusiveNamespaces PrefixList="ds xenc #default" 
                      xmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#" /&gt;
              &lt;/Transform&gt;
            &lt;/Transforms&gt;
            &lt;DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /&gt;
            &lt;DigestValue&gt;GfV3xa/OL6EQAoo5sFL/nHQJCeo=&lt;/DigestValue&gt;
          &lt;/Reference&gt;
        &lt;/SignedInfo&gt;
        &lt;SignatureValue&gt;TtHM/i5L6ynzQHh2Xym8wnbjQ+w=&lt;/SignatureValue&gt;
      &lt;/Signature&gt;
    &lt;/KeyBindingAuthentication&gt;
  &lt;/Authentication&gt;
&lt;/RecoverRequest&gt;</pre>

<p><a name="XKMS_2_0_Paragraph_268" id="XKMS_2_0_Paragraph_268" class="markParagraph" shape="rect">[268]</a>The policy of this particular registration
service is to revoke a private key whenever key recovery is performed. A
registration service might adopt a revoke on recover policy for a number of
reasons which include concern that the recovery process might be considered
to have compromised the key in some way.&#xA0; The service returns the
revoked key binding and the private key parameters:</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">



&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;RecoverResult xmlns:ds="http://www.w3.org/2000/09/xmldsig#" 
      xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" 
      Id="Iacd24dbd4b3c79660f4d26aca7aaaea2" 
      Service="http://www.example.org/XKMS"
      ResultMajor="http://www.w3.org/2002/03/xkms#Success"
      RequestId="I66f40510c322d281602ce76b9eb04d7d" 
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;KeyBinding Id="I29cb8ac8a2ad878f7be44edfe53ea77a"&gt;
    &lt;ds:KeyInfo&gt;
      &lt;ds:KeyValue&gt;
        &lt;ds:RSAKeyValue&gt;
          &lt;ds:Modulus&gt;
            3FFtWUsvEajQt2SeSF+RvAxWdPPh5GSlQnp8SDvvqvCwE6PXcRWrIGmV7twNf2T
            UXCxYuztUUClMIy14B0Q+k1ej2nekmYL7+Ic3DDGVFVaYPoxaRY0Y2lV8tOreyn
            WegpFbITXc8V6Y02QfR5O7Pn1/10ElslaF/TF8MQGqYE8=
          &lt;/ds:Modulus&gt;
          &lt;ds:Exponent&gt;AQAB&lt;/ds:Exponent&gt;
        &lt;/ds:RSAKeyValue&gt;
      &lt;/ds:KeyValue&gt;
    &lt;/ds:KeyInfo&gt;
    &lt;Status StatusValue="http://www.w3.org/2002/03/xkms#Invalid"&gt;
      &lt;InvalidReason&gt;http://www.w3.org/2002/03/xkms#Signature&lt;/InvalidReason&gt;
      &lt;InvalidReason&gt;http://www.w3.org/2002/03/xkms#IssuerTrust&lt;/InvalidReason&gt;
      &lt;InvalidReason&gt;http://www.w3.org/2002/03/xkms#RevocationStatus&lt;/InvalidReason&gt;
      &lt;InvalidReason&gt;http://www.w3.org/2002/03/xkms#ValidityInterval&lt;/InvalidReason&gt;
    &lt;/Status&gt;
  &lt;/KeyBinding&gt;
  &lt;PrivateKey&gt;
    &lt;xenc:EncryptedData Type="http://www.w3.org/2001/04/xmlenc#Content"
     	                MimeType="text/xml"&gt;
      &lt;xenc:EncryptionMethod 
            Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc" /&gt;
      &lt;xenc:CipherData&gt;
        &lt;xenc:CipherValue&gt;
          DDSIEvW/tshnuCwCC+jX6y/srzMpt3qCIQ5zXmk/cHN4o/BItHsi9BJF85a3hnN
          C4/aFfPVJ3WgP6vIZNAUaDY2FbAJckWRgWhGku36p7DZTB14vmt5P5C1bXGU5ps
          CDw5Sbm+s/cFkReyfGk6khJTpbgQABPGIZBy2hiZMdSnu0eRgaVUXk9X5oPAhYU
          BjiQRq56ckHgEhkuwa+RiA+ybDNn/Ttjt5Uu5BjCONkOdeE8eJMlu0ykj99Vn7G
          NKUvt86bJsuwu5ZD1vSmVEwUAvHKV09UfVWfcKEINoj30t8Imj9naJ37oVRNPXl
          EKqZY9cxqzHiYEEhu0wxiTMiLbkEyh1DIcLNW78JXpWHRuRTrU5hgNzGEO1pKo7
          1uRT1/lArojeJGCJKAwQJvCDXU9zZSXVLzU/AqUshR3L0AoY8pJ/p+LbmlTh43E
          4TeT0iXNWkLz0mdgWdmwhhZtj8NcP/4auqfpv7+4NAP5OFVOEYJgE1I60F49K9m
          7FbNygiAczfN1YZwjc5lLoIXo75cXduxOZgTWN8ZnFKwrhG1IMhstrauywur6lr
          lyxZ1JXEj2aohE4Msa7HKx1LSzDi3dejtK3ZFRqnJcJ1bQ/liOA1IgonN0wvUaH
          DM9ibo2xUie2DfoSw3kWCDf0bcZEcV33UFNR3w8kOHgpSAwdHJi0pRyHdgfyd8w
          3NzvfCNy9AlrU2MbTdFF7hBxmgFK3fvaX7aEcgdqY17dqkiK75TAwzkVh5WkVjS
          WZGSiN49C8e4bY9zzq33lZwZabd5ts2Dvy3RuKc0hQj2rnCZcowXC+XJ7tVtMG+
          lNu1ykyeYmvR8VI5Ame5h1DFPjoFLAjkt/tUu2uZlqLYoSKvJU4FWNMAXRUge+f
          L3f35lObqwxPJN/LVJgvgGqoMt5hO+/uwgsb3nbR7rTHavPX2kS5LDAtW5xNcfF
          dJz8l+dDjlYBJMN8cgEKnNtHTcnVJ5NiFPsGIFv/3IGUZsiw7M4dff3GN6quv9A
          601e5rqG1ObMT6/7y7T0Z5IBXwiqs4HcdV+kyRfJwX1QpGat3nQsOZ59PTsIt5n
          oKSH0sB5AZmLJa1zgeOILJ574r+F6kD44R32NoLjqu0QL5IqfQ/0lQJuYhn0uEr
          FeZIn/lvjqzgf+rGPtgI5wtZ9Fv3qKrTPJOGM8atkzPkUtyJ8kR+WRhdAdFH9HM
          0PgyrSGjcCGgFIppsN1KJawrvcXokGRzF81cD/3pVaZC/ZIBtvp4DXM2JSLGoa1
          GpLuaIFUP5T/uxFf6MpW2v07bB/jqEZrcsB/ofmvv6RXD/gXrrw99iIiv0k2lyR
          sHDN5/syXglGGeskPvCUOZZ5oXrZruxER/IXKRnlsD+0wJ3JZCSuPy9wYmQk77F
          pynJ5//7w8UA2qWvkZ0B4rKXOgZYp2pCWaZIDknHJoY+VL7J3sQyAp7qlkQxSBj
          bhTEjSYXpHWA+Vj/TiH1ue7/ULlCKfDNvDaWFuEqGT/9H+xUJ5POfTDBhUh+Row
          rwCcfYe71B+pB/tylQEERKNpqqgu3TbNJZk5G8U9p41+PwJ0kw9EZnv+z8UEyFl
          qAZZxj64rTelurPUsiehBFwVwh2fATuMrW9fhGew11npVlF5k+WxE1Cz+          
        &lt;/xenc:CipherValue&gt;
      &lt;/xenc:CipherData&gt;
    &lt;/xenc:EncryptedData&gt;
  &lt;/PrivateKey&gt;
&lt;/RecoverResult&gt;</pre>

<p><a name="XKMS_2_0_Paragraph_269" id="XKMS_2_0_Paragraph_269" class="markParagraph" shape="rect">[269]</a>The decrypted private key parameters are:</p>
<!-- Include file -->
<pre class="Example" xml:space="preserve">
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;RSAKeyPair xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;Modulus&gt;
    3FFtWUsvEajQt2SeSF+RvAxWdPPh5GSlQnp8SDvvqvCwE6PXcRWrIGmV7twNf2TUXCxYuztUU
    ClMIy14B0Q+k1ej2nekmYL7+Ic3DDGVFVaYPoxaRY0Y2lV8tOreynWegpFbITXc8V6Y02QfR5
    O7Pn1/10ElslaF/TF8MQGqYE8=
  &lt;/Modulus&gt;
  &lt;Exponent&gt;AQAB&lt;/Exponent&gt;
  &lt;P&gt;
    8dnXAObQvcKL0Rr/A+5Ufp1yJgLpH+uohFcJV2kUDCzv5VWKcN+LTq2mciKlnFbAQXKa5dNPO
    x4qi3An/4NSMQ==
  &lt;/P&gt;
  &lt;Q&gt;
    6TUX4d9+enb/aLHtck39x7cPQWlKkNFFJAqXaaRScDhjf4d8b009uW/pu3O2BdIJPY8M/QnUR
    lqXGLqGGl26fw==
  &lt;/Q&gt;
  &lt;DP&gt;
    LVEcMFcPlf72I+BjGGF4A6GM2gKBnDGUCfglD/Pohb+F0/sLTcsVV1DCd3B2h6zZqWnIDHhjy
    DgG0MnbNM1ugQ==
  &lt;/DP&gt;
  &lt;DQ&gt;
    0DWm7PMtaQl1X3P8G2Gmgvjdlfj7qfAtWtBZ/ufG8oplyyab4oOD6FwSwlm82dV8iol9fy2Xa
    HjZDir6L/Ae4Q==
  &lt;/DQ&gt;
  &lt;InverseQ&gt;
    sD2Vl/CCVTDbhhLwdfc4IQDBOh8xpBUV7PPM5LFGjiLetlfwaYi7Bp2ol8WF1MX88iCV2E3xO
    PCNfbMhvEB5dA==
  &lt;/InverseQ&gt;
  &lt;D&gt;
    REUnMUhO6ZX6NxoCwkJ7El5wXAVGtlNJsnPqFygbeEjlBvD6TZx9TqnpP/8IX7WK6JUFWd9kn
    QJvCWeJjhbjnImSS/3xc+v+m4glnnebZbaghvfunbI++fQaNAFRVT1hLvEGknqC/7zsrUM04o
    gU7hP+XgdFTJ1QYGfGHl5c0IE=
  &lt;/D&gt;
&lt;/RSAKeyPair&gt;</pre>

<h2><a name="XKMS_2_0_Section_6_5" id="XKMS_2_0_Section_6_5" shape="rect">6.5</a> <a name="RequestAuthentication" id="RequestAuthentication" shape="rect">Request
Authentication</a></h2>

<p><a name="XKMS_2_0_Paragraph_270" id="XKMS_2_0_Paragraph_270" class="markParagraph" shape="rect">[270]</a>X-KRSS specifies a mechanism for
authenticating requests that is independent of any authentication mechanism
provided by the message security binding. By its nature the X-KRSS protocol
is required to support requests from parties who have yet to register their
credentials or who have impaired credentials which are to be revoked.</p>

<p><a name="XKMS_2_0_Paragraph_271" id="XKMS_2_0_Paragraph_271" class="markParagraph" shape="rect">[271]</a>An X-KRSS Service SHOULD ensure that all
requests are authentic and authorized.</p>

<blockquote>
  <p><a name="XKMS_2_0_Paragraph_272" id="XKMS_2_0_Paragraph_272" class="markParagraph" shape="rect">[272]</a> <b>Authenticity</b>: The request message
  originated from the specified party.</p>

  <p><a name="XKMS_2_0_Paragraph_273" id="XKMS_2_0_Paragraph_273" class="markParagraph" shape="rect">[273]</a> <b>Integrity</b>: The request message has
  not been modified.</p>

  <p><a name="XKMS_2_0_Paragraph_274" id="XKMS_2_0_Paragraph_274" class="markParagraph" shape="rect">[274]</a> <b>Possession</b>: If a public key is
  specified in a registration request, proof that the request is authorized
  by a party that has access to the corresponding private key.</p>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_275" id="XKMS_2_0_Paragraph_275" class="markParagraph" shape="rect">[275]</a>Registration services set their own
authentication policy. This specification defines an authentication mechanism
that employs a shared secret established out of band between the client and
the registration service.</p>

<p><a name="XKMS_2_0_Paragraph_276" id="XKMS_2_0_Paragraph_276" class="markParagraph" shape="rect">[276]</a>Services SHOULD require that clients
demonstrate Proof of Possession of the private key components of a public key
if a request is made to register a valid key binding bound to that public
key.</p>

<p><a name="XKMS_2_0_Paragraph_277" id="XKMS_2_0_Paragraph_277" class="markParagraph" shape="rect">[277]</a>Services SHOULD accept Proof of Possession of
the private key component of a public key to effect revocation of any key
binding bound to that key.</p>

<p><a name="XKMS_2_0_Paragraph_277a" id="XKMS_2_0_Paragraph_277a" class="markParagraph" shape="rect">[277a]</a>Clients and Responders MAY
use <span class="ID">dsig:KeyName</span> for HMAC validation.
Alternatively, they may use  other Identity related
information derived from security binding, such as the Sender's IP
address.</p>

<h1><a name="XKMS_2_0_Section_7" id="XKMS_2_0_Section_7" shape="rect">7</a> <a name="KeyRegistrationServiceMessageSet" id="KeyRegistrationServiceMessageSet" shape="rect">Key Registration Service Message
Set</a></h1>

<p><a name="XKMS_2_0_Paragraph_278" id="XKMS_2_0_Paragraph_278" class="markParagraph" shape="rect">[278]</a>The protocol operations consist of a remote
procedure call that consists of a single request message sent by the client
to the registration service followed by a single response message sent by the
server to the client.&#xA0;</p>

<p><a name="XKMS_2_0_Paragraph_279" id="XKMS_2_0_Paragraph_279" class="markParagraph" shape="rect">[279]</a>A response message MAY contain multiple key
bindings if the operation resulted in the creation or a change in the status
of multiple key bindings. For example a Register operation might cause two
independent key bindings with different policy identifiers and validity
intervals to be established in two independent underlying PKIs. Revocation of
one such key binding might cause the revocation of other associated key
bindings.</p>

<h2><a name="XKMS_2_0_Section_7_1" id="XKMS_2_0_Section_7_1" shape="rect">7.1</a> <a name="CommonElements" id="CommonElements" shape="rect">Common Elements</a></h2>

<h3><a name="XKMS_2_0_Section_7_1_1" id="XKMS_2_0_Section_7_1_1" shape="rect">7.1.1</a> <a name="ElementPrototypeKeyBinding" id="ElementPrototypeKeyBinding" shape="rect">Element
<span class="ID">&lt;PrototypeKeyBinding&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_280" id="XKMS_2_0_Paragraph_280" class="markParagraph" shape="rect">[280]</a>The <span class="ID">&lt;PrototypeKeyBinding&gt;</span> element is derived from the
<span class="ID">KeyBindingAbstractType</span>. It is used to specify the
values of elements that a client requests be present in the keybinding
resulting from a registration request.</p>

<p><a name="XKMS_2_0_Paragraph_281" id="XKMS_2_0_Paragraph_281" class="markParagraph" shape="rect">[281]</a>All fields in a <span class="ID">&lt;PrototypeKeyBinding&gt;</span> element are advisory and MAY be
ignored by the service. For example a client might request registration under
the policy identifier http://example.com/policy/high-security corresponding
to a high assurance issuance policy but the returned key binding might
specify the policy identifier http://example.com/policy/low-security
corresponding to a low assurance issuance policy instead.</p>

<p><a name="XKMS_2_0_Paragraph_282" id="XKMS_2_0_Paragraph_282" class="markParagraph" shape="rect">[282]</a>The <span class="ID">&lt;PrototypeKeyBinding&gt;</span> element extends the <span class="ID">KeyBindingAbstractType</span> with the following additional
elements:</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;ValidityInterval&gt;</b></span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>The suggested time interval for which the key binding relationship
        is valid.</dd>
    <dt><span class="ID">&lt;RevocationCodeIdentifier&gt;</span>&nbsp;&nbsp;&nbsp;[Optional]</dt>
      <dd>Specifies a value to be used to validate a <span class="ID">RevocationCode</span> value in a subsequent Revocation
        request.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_283" id="XKMS_2_0_Paragraph_283" class="markParagraph" shape="rect">[283]</a>The following schema defines the <span class="ID">&lt;PrototypeKeyBinding&gt;</span>element and <span class="ID">PrototypeKeyBindingType</span>:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- PrototypeKeyBinding --&gt;
   &lt;element name="PrototypeKeyBinding" type="xkms:PrototypeKeyBindingType"/&gt;
   &lt;complexType name="PrototypeKeyBindingType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:KeyBindingAbstractType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:ValidityInterval" minOccurs="0"/&gt;
               &lt;element ref="xkms:RevocationCodeIdentifier" minOccurs="0"/&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /PrototypeKeyBinding --&gt;</pre>

<h3><a name="XKMS_2_0_Section_7_1_2" id="XKMS_2_0_Section_7_1_2" shape="rect">7.1.2</a> <a name="ElementRevocationCodeIdentifier" id="ElementRevocationCodeIdentifier" shape="rect">Element <span class="ID">&lt;RevocationCodeIdentifier&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_284" id="XKMS_2_0_Paragraph_284" class="markParagraph" shape="rect">[284]</a>The <span class="ID">&lt;RevocationCodeIdentifier&gt;</span> element contains a MAC
output value encoded as a base64 string.</p>

<p><a name="XKMS_2_0_Paragraph_285" id="XKMS_2_0_Paragraph_285" class="markParagraph" shape="rect">[285]</a>The default MAC algorithm used is HMAC-SHA1.
Other MAC algorithms MAY be used provided that the client is advised that the
service accepts such algorithms by means of an out of band mechanism such as
a Web Service description or policy mechanism.</p>

<p><a name="XKMS_2_0_Paragraph_286" id="XKMS_2_0_Paragraph_286" class="markParagraph" shape="rect">[286]</a>On initial registration the <span class="ID">&lt;RevocationCodeIdentifier&gt;</span> value is obtained by first
performing the MAC calculation on the pass phrase value, then performing a
second MAC calculation on the result.</p>

<p><a name="XKMS_2_0_Paragraph_287" id="XKMS_2_0_Paragraph_287" class="markParagraph" shape="rect">[287]</a>To prove knowledge of the pass phrase in a
subsequent revocation request the <span class="ID">&lt;RevocationCode&gt;</span> value is obtained by performing the
MAC calculation on the pass phrase value.</p>

<p><a name="XKMS_2_0_Paragraph_288" id="XKMS_2_0_Paragraph_288" class="markParagraph" shape="rect">[288]</a>An advantage of employing the double MAC
calculation is that it ensures that an XKMS service does not place arbitrary
constraints on the length of or character set in which the pass phrase
is encoded.</p>

<p><a name="XKMS_2_0_Paragraph_289" id="XKMS_2_0_Paragraph_289" class="markParagraph" shape="rect">[289]</a>Details of the MAC output value calculation
are provided in the section <a href="#sharedsecret" shape="rect">Cryptographic Algorithm
Specific Parameters</a> below.</p>

<p><a name="XKMS_2_0_Paragraph_290" id="XKMS_2_0_Paragraph_290" class="markParagraph" shape="rect">[290]</a>The following schema defines the <span class="ID">&lt;RevocationCodeIdentifier&gt;</span> element and the <span class="ID">RevocationCodeIdentifierType</span>type:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- RevocationCodeIdentifier --&gt;
   &lt;element name="RevocationCodeIdentifier"
         type="xkms:RevocationCodeIdentifierType"/&gt;
   &lt;simpleType name="RevocationCodeIdentifierType"&gt;
      &lt;restriction base="base64Binary"/&gt;
   &lt;/simpleType&gt;
   &lt;!-- /RevocationCodeIdentifier --&gt;</pre>

<h3><a name="XKMS_2_0_Section_7_1_3" id="XKMS_2_0_Section_7_1_3" shape="rect">7.1.3</a> <a name="ElementAuthentication" id="ElementAuthentication" shape="rect">Element <span class="ID">&lt;Authentication&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_291" id="XKMS_2_0_Paragraph_291" class="markParagraph" shape="rect">[291]</a>The&#xA0;<span class="ID">&lt;Authentication&gt;</span> element is used to authenticate the
key binding element within an X-KRSS request. This may be a&#xA0; &lt;<span class="ID">PrototypeKeyBinding&gt;</span>, <span class="ID">&lt;ReissueKeyBinding&gt;</span>, <span class="ID">&lt;RevokeKeyBinding&gt;</span> or <span class="ID">&lt;RecoverKeyBinding&gt;</span> element depending on the type of
request.</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;KeyBindingAuthentication&gt;</b></span>&nbsp;&nbsp;&nbsp;
    <b>[Optional]</b></dt>
      <dd>Authentication of the key binding by means of a signature using a
        previously established key.</dd>
    <dt><span class="ID"><b>&lt;NotBoundAuthentication&gt;</b></span>&nbsp;&nbsp;&nbsp;
    [Optional]</dt>
      <dd>Plaintext data used to authenticate the X-KRSS
         request that is not bound to the key
      binding.</dd>
  </dl>
</blockquote>

<blockquote>
  <dl>
      <dd>XKMS Responders do not have to support both of these optional
        elements in a request message.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_292" id="XKMS_2_0_Paragraph_292" class="markParagraph" shape="rect">[292]</a>The following schema defines the <span class="ID">&lt;Authentication&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- Authentication --&gt;
   &lt;element name="Authentication" type="xkms:AuthenticationType"/&gt;
   &lt;complexType name="AuthenticationType"&gt;
      &lt;sequence&gt;
         &lt;element ref="xkms:KeyBindingAuthentication" minOccurs="0"/&gt;
         &lt;element ref="xkms:NotBoundAuthentication" minOccurs="0"/&gt;
      &lt;/sequence&gt;
   &lt;/complexType&gt;
   &lt;!-- /Authentication --&gt;</pre>

<h3><a name="XKMS_2_0_Section_7_1_4" id="XKMS_2_0_Section_7_1_4" shape="rect">7.1.4</a> <a name="ElementKeyBindingAuthentication" id="ElementKeyBindingAuthentication" shape="rect">Element <span class="ID">&lt;KeyBindingAuthentication&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_293" id="XKMS_2_0_Paragraph_293" class="markParagraph" shape="rect">[293]</a>The <span class="ID">&lt;KeyBindingAuthentication&gt;</span> element contains an XML
Signature <a href="#XML-SIG" shape="rect">[XML-SIG]</a> element that is used to
authenticate the request using a previously established key.</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;ds:Signature&gt;</b></span>&nbsp;&nbsp;&nbsp;
    <b>[Required]</b></dt>
      <dd>An XML Signature <a href="#XML-SIG" shape="rect">[XML-SIG]</a> element that
        contains a signature over the <span class="ID">&lt;KeyBinding</span>&gt; or &lt;<span class="ID">PrototypeKeyBinding&gt;</span> element.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_294" id="XKMS_2_0_Paragraph_294" class="markParagraph" shape="rect">[294]</a>The XML signature <a href="#XML-SIG" shape="rect">[XML-SIG]</a> is generated as a detached signature using the
Id attribute specified in <span class="ID">KeyBindingAbstractType</span> to
specify the signature scope.</p>

<p><a name="XKMS_2_0_Paragraph_295" id="XKMS_2_0_Paragraph_295" class="markParagraph" shape="rect">[295]</a>The following schema defines the <span class="ID">&lt;KeyBindingAuthentication&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- KeyBindingAuthentication --&gt;
   &lt;element name="KeyBindingAuthentication"
         type="xkms:KeyBindingAuthenticationType"/&gt;
   &lt;complexType name="KeyBindingAuthenticationType"&gt;
      &lt;sequence&gt;
         &lt;element ref="ds:Signature"/&gt;
      &lt;/sequence&gt;
   &lt;/complexType&gt;
   &lt;!-- /KeyBindingAuthentication --&gt;</pre>

<h3><a name="XKMS_2_0_Section_7_1_5" id="XKMS_2_0_Section_7_1_5" shape="rect">7.1.5</a> <a name="ElementNotBoundAuthentication" id="ElementNotBoundAuthentication" shape="rect">Element <span class="ID">&lt;NotBoundAuthentication&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_296" id="XKMS_2_0_Paragraph_296" class="markParagraph" shape="rect">[296]</a>The <span class="ID">&lt;NotBoundAuthentication&gt;</span> contains 
plaintext authentication data (e.g., limited use shared
secret) that is used to authenticate the request.</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>Protocol</b></span>&nbsp;&nbsp;&nbsp;<b>
    [Required]</b></dt>
      <dd>A URI specifying the authentication protocol used.</dd>
    <dt><b><span class="ID">Value</span>&nbsp;&nbsp;&nbsp;[Required]</b></dt>
      <dd>The plaintext authentication  data encoded in base64 format.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_297" id="XKMS_2_0_Paragraph_297" class="markParagraph" shape="rect">[297]</a>The specification of protocol URIs is outside
the scope of this document.</p>

<p><a name="XKMS_2_0_Paragraph_298" id="XKMS_2_0_Paragraph_298" class="markParagraph" shape="rect">[298]</a>This element is provided to support
applications in which the authentication scheme requires the server to have
plaintext access to the authentication data. The authentication data is not
securely bound to the request and thus the element MUST NOT be employed
except in circumstances where the message or transport protocol provides
adequate protection of both confidentiality and integrity.</p>

<p><a name="XKMS_2_0_Paragraph_299" id="XKMS_2_0_Paragraph_299" class="markParagraph" shape="rect">[299]</a>The following schema defines the <span class="ID">&lt;NotBoundAuthentication&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- NotBoundAuthentication --&gt;
   &lt;element name="NotBoundAuthentication"
         type="xkms:NotBoundAuthenticationType"/&gt;
   &lt;complexType name="NotBoundAuthenticationType"&gt;
      &lt;attribute name="Protocol" type="anyURI" use="required"/&gt;
      &lt;attribute name="Value" type="base64Binary" use="required"/&gt;
   &lt;/complexType&gt;
   &lt;!-- /NotBoundAuthentication --&gt;</pre>

<h3><a name="XKMS_2_0_Section_7_1_6" id="XKMS_2_0_Section_7_1_6" shape="rect">7.1.6</a> <a name="ElementProofOfPossession" id="ElementProofOfPossession" shape="rect">Element <span class="ID">&lt;ProofOfPossession&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_300" id="XKMS_2_0_Paragraph_300" class="markParagraph" shape="rect">[300]</a>The <span class="ID">&lt;ProofOfPossession&gt;</span> element contains a XML Signature
<a href="#XML-SIG" shape="rect">[XML-SIG]</a> element. The signature scope is the <span class="ID">&lt;PrototypeKeyBinding&gt;</span> using the public key that is to
be registered. The private key component of the public key contained within
the <span class="ID">&lt;PrototypeKeyBinding&gt;</span> is used to generate
the signature.</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;ds:Signature&gt;</b></span>
    &nbsp;&nbsp;&nbsp;<b>[Required]</b></dt>
      <dd>An XML Signature <a href="#XML-SIG" shape="rect">[XML-SIG]</a> element that
        contains a detached signature over the <span class="ID">&lt;PrototypeKeyBinding&gt;</span> element. The signing
        key is the key identified by the <span class="ID">ds:KeyInfo</span>
        element within the <span class="ID">&lt;PrototypeKeyBinding&gt;</span> element.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_301" id="XKMS_2_0_Paragraph_301" class="markParagraph" shape="rect">[301]</a>The XML signature <a href="#XML-SIG" shape="rect">[XML-SIG]</a> is generated as a detached signature using the
Id attribute specified in <span class="ID">KeyBindingAbstractType</span> to
specify the signature scope.</p>

<p><a name="XKMS_2_0_Paragraph_302" id="XKMS_2_0_Paragraph_302" class="markParagraph" shape="rect">[302]</a>The following schema defines the <span class="ID">&lt;</span><span class="ID">ProofOfPossession</span><span class="ID">&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- ProofOfPossession --&gt;
   &lt;element name="ProofOfPossession" type="xkms:ProofOfPossessionType"/&gt;
   &lt;complexType name="ProofOfPossessionType"&gt;
      &lt;sequence&gt;
         &lt;element ref="ds:Signature"/&gt;
      &lt;/sequence&gt;
   &lt;/complexType&gt;
   &lt;!-- /ProofOfPossession --&gt;</pre>

<h3><a name="XKMS_2_0_Section_7_1_7" id="XKMS_2_0_Section_7_1_7" shape="rect">7.1.7</a> <a name="ElementPrivateKey" id="ElementPrivateKey" shape="rect">Element <span class="ID">&lt;PrivateKey&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_303" id="XKMS_2_0_Paragraph_303" class="markParagraph" shape="rect">[303]</a> The <span class="ID">&lt;</span><span class="ID">PrivateKey&gt;</span> element contains the encrypted private key
parameters returned by the service in a response to a registration request
with server generated keys or a response to a successful recovery request.</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;xenc:EncryptedData&gt;</b></span>&nbsp;&nbsp;&nbsp;
    <b>[Required]</b></dt>
      <dd>The encrypted private key data. This element is as defined by
        the XML Encryption Specification <a href="#XML-Enc" shape="rect">[XML-Enc]</a>.
        The Type attribute SHOULD be present and, if present, MUST contain a
        value of <code>http://www.w3.org/2001/04/xmlenc#Content</code>. The
        MimeType attribute, SHOULD be "<code>text/xml</code>".</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_304" id="XKMS_2_0_Paragraph_304" class="markParagraph" shape="rect">[304]</a>The following schema defines the <span class="ID">&lt;</span><span class="ID">PrivateKey&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- PrivateKey --&gt;
   &lt;element name="PrivateKey" type="xkms:PrivateKeyType"/&gt;
   &lt;complexType name="PrivateKeyType"&gt;
      &lt;sequence&gt;
         &lt;element ref="xenc:EncryptedData"/&gt;
      &lt;/sequence&gt;
   &lt;/complexType&gt;
   &lt;!-- /PrivateKey --&gt;</pre>

<h3><a name="XKMS_2_0_Section_7_1_8" id="XKMS_2_0_Section_7_1_8" shape="rect">7.1.8</a> <a name="ElementRevocationCode" id="ElementRevocationCode" shape="rect">Element <span class="ID">&lt;RevocationCode&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_305" id="XKMS_2_0_Paragraph_305" class="markParagraph" shape="rect">[305]</a> The <span class="ID">&lt;RevocationCode&gt;</span> element contains a MAC output value
encoded as a base64 string.</p>

<p><a name="XKMS_2_0_Paragraph_306" id="XKMS_2_0_Paragraph_306" class="markParagraph" shape="rect">[306]</a>The default MAC algorithm used is HMAC-SHA1.
Other MAC algorithms MAY be used provided that the client is advised that the
service accepts such algorithms by means of an out of band mechanism such as
a Web Service description or policy mechanism.</p>

<p><a name="XKMS_2_0_Paragraph_307" id="XKMS_2_0_Paragraph_307" class="markParagraph" shape="rect">[307]</a>On initial registration the <span class="ID">&lt;RevocationCodeIdentifier&gt;</span> value is obtained by first
performing the MAC calculation on the pass phrase value, then performing a
second MAC calculation on the result.</p>

<p><a name="XKMS_2_0_Paragraph_308" id="XKMS_2_0_Paragraph_308" class="markParagraph" shape="rect">[308]</a>To prove knowledge of the pass phrase in a
subsequent revocation request the <span class="ID">&lt;RevocationCode&gt;</span> value is obtained by performing the
MAC calculation on the pass phrase value.</p>

<p><a name="XKMS_2_0_Paragraph_309" id="XKMS_2_0_Paragraph_309" shape="rect">[309]</a>
Details of the MAC output value calculation are provided in the section <a href="#sharedsecret" shape="rect">Cryptographic Algorithm Specific Parameters</a>
below.</p>

<p><a name="XKMS_2_0_Paragraph_310" id="XKMS_2_0_Paragraph_310" class="markParagraph" shape="rect">[310]</a>The following schema defines the <span class="ID">&lt;RevocationCode&gt;</span> element and the <span class="ID">RevocationCodeType</span>:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- RevocationCode --&gt;
   &lt;element name="RevocationCode" type="xkms:RevocationCodeType"/&gt;
   &lt;simpleType name="RevocationCodeType"&gt;
      &lt;restriction base="base64Binary"/&gt;
   &lt;/simpleType&gt;
   &lt;!-- /RevocationCode --&gt;</pre>

<h2><a name="XKMS_2_0_Section_7_2" id="XKMS_2_0_Section_7_2" shape="rect">7.2</a> <a name="RegisterOP" id="RegisterOP" shape="rect">Register</a></h2>

<h3><a name="XKMS_2_0_Section_7_2_1" id="XKMS_2_0_Section_7_2_1" shape="rect">7.2.1</a> Register Request <a name="ElementRegisterRequest" id="ElementRegisterRequest" shape="rect">Element <span class="ID">&lt;RegisterRequest&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_311" id="XKMS_2_0_Paragraph_311" class="markParagraph" shape="rect">[311]</a>The register request message contains a <span class="ID">&lt;</span><span class="ID">RegisterRequest</span><span class="ID">&gt;</span> element that contains the following elements:</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;</b>PrototypeKeyBinding<b>&gt;</b></span>&nbsp;&nbsp;&nbsp;
    <b>[Required]</b></dt>
      <dd>Specifies elements that the client requests be registered.</dd>
    <dt><span class="ID"><b>&lt;Authentication&gt;</b></span>&nbsp;&nbsp;&nbsp;
    <b>[Required]</b></dt>
      <dd>Information that authenticates the request.</dd>
    <dt><span class="ID"><b>&lt;ProofOfPossesion&gt;</b></span>&nbsp;&nbsp;&nbsp;
    <b>[Optional]</b></dt>
      <dd>Proof of possession of the private key component of the key
        binding. A Service that requires
        the <span class="ID">ProofOfPossession</span> element MUST
        return a 
        <span class="ID">Sender.ProofOfPossessionRequired</span> 
        result if the <span class="ID">ProofOfPossession</span> 
	element is not present in the request.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_312" id="XKMS_2_0_Paragraph_312" class="markParagraph" shape="rect">[312]</a>The following schema defines the <span class="ID">&lt;</span><span class="ID">RegisterRequest</span><span class="ID">&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- RegisterRequest --&gt;
   &lt;element name="RegisterRequest" type="xkms:RegisterRequestType"/&gt;
   &lt;complexType name="RegisterRequestType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:RequestAbstractType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:PrototypeKeyBinding"/&gt;
               &lt;element ref="xkms:Authentication"/&gt;
               &lt;element ref="xkms:ProofOfPossession" minOccurs="0"/&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /RegisterRequest --&gt;</pre>

<h3><a name="XKMS_2_0_Section_7_2_2" id="XKMS_2_0_Section_7_2_2" shape="rect">7.2.2</a> Register Response <a name="ElementRegisterResult" id="ElementRegisterResult" shape="rect">Element <span class="ID">&lt;RegisterResult&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_313" id="XKMS_2_0_Paragraph_313" class="markParagraph" shape="rect">[313]</a>The register response message contains a <span class="ID">&lt;</span><span class="ID">RegisterResult</span><span class="ID">&gt;</span> element that contains the following elements:</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;KeyBinding&gt;</b></span>&nbsp;&nbsp;&nbsp;
    <b>[Any number]</b></dt>
      <dd>If present specifies the key binding that was registered by the
        service.</dd>
    <dt><span class="ID"><b>&lt;PrivateKey&gt;</b></span>&nbsp;&nbsp;&nbsp;
    <b>[Optional]</b></dt>
      <dd>The values of the private key parameters of a private key generated
        by the registration service.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_314" id="XKMS_2_0_Paragraph_314" class="markParagraph" shape="rect">[314]</a>The following schema defines the <span class="ID">&lt;</span><span class="ID">RegisterResult</span><span class="ID">&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- RegisterResult --&gt;
   &lt;element name="RegisterResult" type="xkms:RegisterResultType"/&gt;
   &lt;complexType name="RegisterResultType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:ResultType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:KeyBinding" minOccurs="0"
                     maxOccurs="unbounded"/&gt;
               &lt;element ref="xkms:PrivateKey" minOccurs="0"/&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /RegisterResult --&gt;</pre>

<h2><a name="XKMS_2_0_Section_7_3" id="XKMS_2_0_Section_7_3" shape="rect">7.3</a> <a name="ReissueOP" id="ReissueOP" shape="rect">Reissue</a></h2>

<h3><a name="XKMS_2_0_Section_7_3_1" id="XKMS_2_0_Section_7_3_1" shape="rect">7.3.1</a> Reissue Request <a name="ElementReissueRequest" id="ElementReissueRequest" shape="rect">Element <span class="ID">&lt;ReissueRequest&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_315" id="XKMS_2_0_Paragraph_315" class="markParagraph" shape="rect">[315]</a>The reissue request message contains a <span class="ID">&lt;</span><span class="ID">ReissueRequest</span><span class="ID">&gt;</span> element that contains the following elements:</p>

<blockquote>
  <dl>
    <dt><span class="ID">&lt;ReissueKeyBinding<b>&gt;</b></span>&nbsp;&nbsp;&nbsp;
    <b>[Required]</b></dt>
      <dd>Identifies the key binding to be reissued.</dd>
    <dt><span class="ID"><b>&lt;Authentication&gt;</b></span>&nbsp;&nbsp;&nbsp;
    <b>[Required]</b></dt>
      <dd>Information that authenticates the request.</dd>
    <dt><span class="ID"><b>&lt;ProofOfPossesion&gt;</b></span>&nbsp;&nbsp;&nbsp;
    <b>[Optional]</b></dt>
      <dd>Proof of possession of the private key component of the key
        binding. A Service that requires
        the <span class="ID">ProofOfPossession</span>element MUST
        return a <span class="ID">Sender.ProofOfPossessionRequired</span> result if
        the <span class="ID">ProofOfPossession</span> element is
        not present in the request.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_316" id="XKMS_2_0_Paragraph_316" class="markParagraph" shape="rect">[316]</a>The following schema defines the <span class="ID">&lt;</span><span class="ID">ReissueRequest</span><span class="ID">&gt;</span> and <span class="ID">&lt;ReissueKeyBinding&gt;</span>
elements:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- ReissueRequest --&gt;
   &lt;element name="ReissueRequest" type="xkms:ReissueRequestType"/&gt;
   &lt;complexType name="ReissueRequestType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:RequestAbstractType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:ReissueKeyBinding"/&gt;
               &lt;element ref="xkms:Authentication"/&gt;
               &lt;element ref="xkms:ProofOfPossession" minOccurs="0"/&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;element name="ReissueKeyBinding" type="xkms:KeyBindingType"/&gt;
   &lt;!-- /ReissueRequest --&gt;</pre>

<h3><a name="XKMS_2_0_Section_7_3_2" id="XKMS_2_0_Section_7_3_2" shape="rect">7.3.2</a> Reissue Response <a name="ElementReissueResult" id="ElementReissueResult" shape="rect">Element <span class="ID">&lt;ReissueResult&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_317" id="XKMS_2_0_Paragraph_317" class="markParagraph" shape="rect">[317]</a>The reissue response message contains a <span class="ID">&lt;</span><span class="ID">ReissueResult</span><span class="ID">&gt;</span> element that contains the following element:</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;KeyBinding&gt;</b></span>&#xA0;&#xA0; [Any
    Number]</dt>
      <dd>If present specifies the key binding(s) that were reissued by the
        service</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_318" id="XKMS_2_0_Paragraph_318" class="markParagraph" shape="rect">[318]</a>&#xA0;The following schema defines the <span class="ID">&lt;</span><span class="ID">ReissueResult</span><span class="ID">&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- ReissueResult --&gt;
   &lt;element name="ReissueResult" type="xkms:ReissueResultType"/&gt;
   &lt;complexType name="ReissueResultType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:ResultType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:KeyBinding" minOccurs="0"
                     maxOccurs="unbounded"/&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /ReissueResult --&gt;</pre>

<h2><a name="XKMS_2_0_Section_7_4" id="XKMS_2_0_Section_7_4" shape="rect">7.4</a> <a name="RevokeOP" id="RevokeOP" shape="rect">Revoke</a></h2>

<h3><a name="XKMS_2_0_Section_7_4_1" id="XKMS_2_0_Section_7_4_1" shape="rect">7.4.1</a> Revoke Request <a name="ElementRevokeRequest" id="ElementRevokeRequest" shape="rect">Element <span class="ID">&lt;RevokeRequest&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_319" id="XKMS_2_0_Paragraph_319" class="markParagraph" shape="rect">[319]</a>The revoke request message contains a <span class="ID">&lt;</span><span class="ID">RevokeRequest</span><span class="ID">&gt;</span> element that contains the following elements:</p>

<blockquote>
  <dl>
    <dt><span class="ID">&lt;RevokeKeyBinding&gt;</span>&nbsp;&nbsp;&nbsp;
    [Required]</dt>
      <dd>Identifies the key binding to be revoked.</dd>
    <dt><span class="ID"><b>&lt;Authentication&gt;</b></span>&nbsp;&nbsp;&nbsp;
    <b>[Choice]</b></dt>
      <dd>Information that authenticates the request.</dd>
    <dt>&lt;<span class="ID">RevocationCode&gt;</span>&nbsp;&nbsp;&nbsp;[Choice]</dt>
      <dd>The revocation code value that generates the revocation code
        identifier value specified during registration.</dd>
      <dd></dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_320" id="XKMS_2_0_Paragraph_320" class="markParagraph" shape="rect">[320]</a>The following schema defines the <span class="ID">&lt;</span><span class="ID">RevokeRequest</span><span class="ID">&gt;</span> and <span class="ID">&lt;RevokeKeyBinding&gt;</span>
elements:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- RevokeRequest --&gt;
   &lt;element name="RevokeRequest" type="xkms:RevokeRequestType"/&gt;
   &lt;complexType name="RevokeRequestType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:RequestAbstractType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:RevokeKeyBinding"/&gt;
               &lt;choice&gt;
                  &lt;element ref="xkms:Authentication"/&gt;
                  &lt;element ref="xkms:RevocationCode"/&gt;
               &lt;/choice&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;element name="RevokeKeyBinding" type="xkms:KeyBindingType"/&gt;
   &lt;!-- /RevokeRequest --&gt;</pre>

<h3><a name="XKMS_2_0_Section_7_4_2" id="XKMS_2_0_Section_7_4_2" shape="rect">7.4.2</a> Revoke Response <a name="ElementRevokeResult" id="ElementRevokeResult" shape="rect">Element <span class="ID">&lt;RevokeResult&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_321" id="XKMS_2_0_Paragraph_321" class="markParagraph" shape="rect">[321]</a>The request message contains a <span class="ID">&lt;</span><span class="ID">RevokeResult</span><span class="ID">&gt;</span> element that contains the following element:</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;KeyBinding&gt;</b></span>&nbsp;&nbsp;&nbsp;
    <b>[Any Number]</b></dt>
      <dd>If present specifies the key binding that was revoked by the
      service.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_322" id="XKMS_2_0_Paragraph_322" class="markParagraph" shape="rect">[322]</a>The following schema defines the <span class="ID">&lt;</span><span class="ID">RevokeResult</span><span class="ID">&gt;</span>:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- RevokeResult --&gt;
   &lt;element name="RevokeResult" type="xkms:RevokeResultType"/&gt;
   &lt;complexType name="RevokeResultType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:ResultType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:KeyBinding" minOccurs="0"
                     maxOccurs="unbounded"/&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /RevokeResult --&gt;</pre>

<h2><a name="XKMS_2_0_Section_7_5" id="XKMS_2_0_Section_7_5" shape="rect">7.5</a> <a name="RecoverOP" id="RecoverOP" shape="rect">Recover</a></h2>

<h3><a name="XKMS_2_0_Section_7_5_1" id="XKMS_2_0_Section_7_5_1" shape="rect">7.5.1</a> Recover Request <a name="ElementRecoverRequest" id="ElementRecoverRequest" shape="rect">Element <span class="ID">&lt;RecoverRequest&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_323" id="XKMS_2_0_Paragraph_323" class="markParagraph" shape="rect">[323]</a>The recover request message contains a <span class="ID">&lt;</span><span class="ID">RecoverRequest</span><span class="ID">&gt;</span> element that contains the following elements:</p>

<blockquote>
  <dl>
    <dt><span class="ID">&lt;RecoverKeyBinding&gt;</span>&nbsp;&nbsp;&nbsp;
    [Required]</dt>
      <dd>Identifies the key binding to be recovered.</dd>
    <dt><span class="ID"><b>&lt;Authentication&gt;</b></span>&nbsp;&nbsp;&nbsp;
    <b>[Required]</b></dt>
      <dd>Information that authenticates the request.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_324" id="XKMS_2_0_Paragraph_324" class="markParagraph" shape="rect">[324]</a>The following schema defines the <span class="ID">&lt;</span><span class="ID">RecoverRequest</span><span class="ID">&gt;</span> and <span class="ID">&lt;RecoverKeyBinding&gt;</span>
elements:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- RecoverRequest --&gt;
   &lt;element name="RecoverRequest" type="xkms:RecoverRequestType"/&gt;
   &lt;complexType name="RecoverRequestType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:RequestAbstractType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:RecoverKeyBinding"/&gt;
               &lt;element ref="xkms:Authentication"/&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;element name="RecoverKeyBinding" type="xkms:KeyBindingType"/&gt;
   &lt;!-- /RecoverRequest --&gt;</pre>

<h3><a name="XKMS_2_0_Section_7_5_2" id="XKMS_2_0_Section_7_5_2" shape="rect">7.5.2</a> Recover Response <a name="ElementRecoverResult" id="ElementRecoverResult" shape="rect">Element <span class="ID">&lt;RecoverResult&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_325" id="XKMS_2_0_Paragraph_325" class="markParagraph" shape="rect">[325]</a>The request message contains a <span class="ID">&lt;RecoverResult&gt;</span> element that contains the following
elements:</p>

<blockquote>
  <dl>
    <dt><span class="ID">&lt;KeyBinding&gt;</span>&nbsp;&nbsp;&nbsp;
    [Any Number]</dt>
      <dd>May be present to advertise a change to the status of the key
        binding made as a result of the key recovery.</dd>
    <dt><span class="ID"><b>&lt;PrivateKey&gt;</b></span>&nbsp;&nbsp;&nbsp;<b>
    [Optional]</b></dt>
      <dd>The values of the private key parameters of the recovered private
        key.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_326" id="XKMS_2_0_Paragraph_326" class="markParagraph" shape="rect">[326]</a>The following schema defines the <span class="ID">&lt;RecoverResult&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- RecoverResult --&gt;
   &lt;element name="RecoverResult" type="xkms:RecoverResultType"/&gt;
   &lt;complexType name="RecoverResultType"&gt;
      &lt;complexContent&gt;
         &lt;extension base="xkms:ResultType"&gt;
            &lt;sequence&gt;
               &lt;element ref="xkms:KeyBinding" minOccurs="0"
                     maxOccurs="unbounded"/&gt;
               &lt;element ref="xkms:PrivateKey" minOccurs="0"/&gt;
            &lt;/sequence&gt;
         &lt;/extension&gt;
      &lt;/complexContent&gt;
   &lt;/complexType&gt;
   &lt;!-- /RecoverResult --&gt;</pre>

<h1><a name="XKMS_2_0_Section_8" id="XKMS_2_0_Section_8" shape="rect">8</a> <a name="CryptographicAlgorithmSpecificParameters" id="CryptographicAlgorithmSpecificParameters" shape="rect">Cryptographic Algorithm
Specific Parameters</a></h1>

<h2><a name="XKMS_2_0_Section_8_1" id="XKMS_2_0_Section_8_1" shape="rect">8.1</a> <a name="sharedsecret" id="sharedsecret" shape="rect">Use of Limited-Use Shared Secret
Data</a></h2>

<p><a name="XKMS_2_0_Paragraph_327" id="XKMS_2_0_Paragraph_327" class="markParagraph" shape="rect">[327]</a>It is frequently necessary or desirable to use
a limited use shared secret for authentication (i.e. a one time use PIN or
pass phrase) to authenticate registration request messages. In particular a
private key cannot be used for authentication until the corresponding public
key has been registered.</p>

<p><a name="XKMS_2_0_Paragraph_328" id="XKMS_2_0_Paragraph_328" class="markParagraph" shape="rect">[328]</a>In addition it is desirable that private key
parameters generated or recovered by the registration service be returned
encrypted. It is convenient to use symmetric data for this purpose.</p>



<p><a name="XKMS_2_0_Paragraph_329a" id="XKMS_2_0_Paragraph_329a" class="markParagraph" shape="rect">[329a]</a> The symmetric key data MAY be binary data
(as from an authentication device) or as a human-readable value (numeric,
alphabetic, or both). When it is binary data, no transformation is needed;
the data can be used directly as input to the MAC function.</p>

<p><a name="XKMS_2_0_Paragraph_329b" id="XKMS_2_0_Paragraph_329b" class="markParagraph" shape="rect">[329b]</a> When the symmetric key data is
human-readable, it may be issued to a human user in the form of a text string
which may in some circumstances be read over a telephone line. It may be
randomly generated and represent an underlying numeric value, or may be a
password or phrase. In either case, it is often convenient to present the
value to the human user as a string of characters in a character set the
particular user understands. To limit the possibility of human error in
processing the symmetric key data, and to provide a canonical binary
representation, the string text must be compliant to the SASLprep stringprep
profile for user names and passwords,<a href="#SASLPREP" shape="rect">[SASLPREP]</a>.</p>

<p><a name="XKMS_2_0_Paragraph_329c" id="XKMS_2_0_Paragraph_329c" class="markParagraph" shape="rect">[329c]</a> The algorithm for canonicalizing a
string-text before feeding it to the MAC function is the following:
</p>
<ol>
  <li>Convert the input string to an Unicode encoding.<br clear="none" />
    Removes the US-ASCII and ISO-LATIN-1 limitations! Let's a user type a
    password phrase that s/he can remember with ease or that's easy to type
    with his/her keyboard configuration.</li>
  <li>Verify that the input string is compliant to the SASLprep
    stringprep profile for user names and passwords <a href="#SASLPREP" shape="rect">[SASLPREP]</a>. Refuse the string otherwise. <br clear="none" />
    This operation consists of mapping and normalizing the characters in the
    string, and checking that it doesn't have any forbidden characters. In
    particular, there's no folding of multiple spaces or of case. Punctuation
    symbols are not removed either. Tabs are control characters and thus are
    considered to be forbidden.</li>
  <li>Encode the result into UTF-8.</li>
  <li>Apply the MAC functions.</li>
</ol>

<p><a name="XKMS_2_0_Paragraph_330" id="XKMS_2_0_Paragraph_330" class="markParagraph" shape="rect">[330]</a>Applications MUST ensure that the limited use
shared secret data contains sufficient entropy to prevent dictionary attacks.
For more details see the&#xA0; more detailed comment in the <a href="#limitedusesecurity" shape="rect">security considerations section</a> of this
document.</p>

<p><a name="XKMS_2_0_Paragraph_331" id="XKMS_2_0_Paragraph_331" class="markParagraph" shape="rect">[331]</a>Keying material is derived from the shared
string using a MAC function.</p>

<p><a name="XKMS_2_0_Paragraph_332" id="XKMS_2_0_Paragraph_332" class="markParagraph" shape="rect">[332]</a>The default MAC algorithm used is HMAC-SHA1.
Other MAC algorithms MAY be used provided that the client is advised that the
service accepts such algorithms by means of an out of band mechanism such as
a Web Service description or policy mechanism.</p>

<p><a name="XKMS_2_0_Paragraph_333" id="XKMS_2_0_Paragraph_333" class="markParagraph" shape="rect">[333]</a>Different MAC keying values are used according
to the use of the symmetric key derived as follows:</p>

<div class="center">

<table cellspacing="0" cellpadding="0" border="1">
  <tbody>
    <tr>
      <th valign="top" width="18%">Value</th>
      <th valign="top" width="81%">Application</th>
    </tr>
    <tr>
      <td valign="top" width="18%" align="center">0x1</td>
      <td valign="top" width="81%">Authentication</td>
    </tr>
    <tr>
      <td valign="top" width="18%" align="center">0x2</td>
      <td valign="top" width="81%">Encoding of <span class="ID">RevocationCodeIdentifier</span> - Pass 1</td>
    </tr>
    <tr>
      <td valign="top" width="18%" align="center">0x3</td>
      <td valign="top" width="81%">Encoding of <span class="ID">RevocationCodeIdentifier</span> - Pass 2</td>
    </tr>
    <tr>
      <td valign="top" width="18%" align="center">0x4</td>
      <td valign="top" width="81%">Encryption of <span class="ID">PrivateKey</span> data</td>
    </tr>
  </tbody>
</table>
</div>

<p><a name="XKMS_2_0_Paragraph_334" id="XKMS_2_0_Paragraph_334" class="markParagraph" shape="rect">[334]</a>If the output of the MAC function provides
more keying material than is required for a cryptographic operation (i.e.
encryption, MAC), the lowest significant bits are used.</p>

<p><a name="XKMS_2_0_Paragraph_335" id="XKMS_2_0_Paragraph_335" class="markParagraph" shape="rect">[335]</a>If the output of the MAC function provides
less keying material than is required additional keying material is obtained
as follows:</p>

<blockquote>
  <p><a name="XKMS_2_0_Paragraph_336" id="XKMS_2_0_Paragraph_336" class="markParagraph" shape="rect">[336]</a>block<sub>0</sub> = MAC (converted, key)</p>

  <p><a name="XKMS_2_0_Paragraph_337" id="XKMS_2_0_Paragraph_337" class="markParagraph" shape="rect">[337]</a>block<sub>n+1</sub> = MAC (converted, key
  XOR block<sub>n</sub>)</p>

  <p><a name="XKMS_2_0_Paragraph_338" id="XKMS_2_0_Paragraph_338" class="markParagraph" shape="rect">[338]</a>output = block<sub>0</sub> +
  block<sub>1</sub> ...&#xA0; block<sub>n</sub></p>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_339" id="XKMS_2_0_Paragraph_339" class="markParagraph" shape="rect">[339]</a>i.e. the first MAC output value is used to
supply the least significant bits of keying material. A second MAC output
value is then obtained by applying the MAC function to the converted string
again, this time the MAC keying value is obtained by XOR-ing the first output
with the previous keying value. This process may be repeated as many times as
necessary to produce a sufficient amount of keying material.</p>

<h2><a name="XKMS_2_0_Section_8_2" id="XKMS_2_0_Section_8_2" shape="rect">8.2</a> <a name="privatekeyparameters" id="privatekeyparameters" shape="rect">Private Key
Parameters</a></h2>

<p><a name="XKMS_2_0_Paragraph_340" id="XKMS_2_0_Paragraph_340" class="markParagraph" shape="rect">[340]</a>The <span class="ID">&lt;PrivateKey&gt;</span>
element may contain the private key parameters for any public key encryption
algorithm. The parameters for the RSA algorithm are specified below.</p>

<p><a name="XKMS_2_0_Paragraph_341" id="XKMS_2_0_Paragraph_341" class="markParagraph" shape="rect">[341]</a>This specification does not specify private
key parameters for the DSA signature algorithm since the algorithm only
supports signature modes and so the application of server generated keys and
key recovery is of limited value.</p>

<h3><a name="XKMS_2_0_Section_8_2_1" id="XKMS_2_0_Section_8_2_1" shape="rect">8.2.1</a> <a name="ElementRSAKeyPair" id="ElementRSAKeyPair" shape="rect">Element <span class="ID">&lt;RSAKeyPair&gt;</span></a></h3>

<p><a name="XKMS_2_0_Paragraph_342" id="XKMS_2_0_Paragraph_342" class="markParagraph" shape="rect">[342]</a>The <span class="ID">&lt;RSAKeyPair&gt;</span>
element specifies the public and private parameters of an RSA key pair. The
contents of the RSAKeyPair element are specified in [PKCS1]. The <span class="ID">RSAKeyPair&gt;</span> element contains the following
parameters:</p>

<blockquote>
  <dl>
    <dt><span class="ID"><b>&lt;Modulus&gt;</b></span>&nbsp;&nbsp;&nbsp;(Required)</dt>
      <dd>The modulus.</dd>
    <dt><span class="ID"><b>&lt;Exponent&gt;</b></span>&nbsp;&nbsp;&nbsp;(Required)</dt>
      <dd>The public exponent.</dd>
    <dt><span class="ID"><b><span class="ID">&lt;P&gt;</span></b></span>&nbsp;&nbsp;&nbsp;
    (Required)</dt>
      <dd>The first factor, a positive integer.</dd>
    <dt><span class="ID"><b>&lt;Q&gt;</b></span>&nbsp;&nbsp;&nbsp;(Required)</dt>
      <dd>The second factor, a positive integer.</dd>
    <dt><span class="ID"><b>&lt;DP&gt;</b></span>&nbsp;&nbsp;&nbsp;(Required)</dt>
      <dd>The first factor's CRT exponent, a positive integer.</dd>
    <dt><span class="ID"><b>&lt;DQ&gt;</b></span>&nbsp;&nbsp;&nbsp;(Required)</dt>
      <dd>The second factor's CRT exponent, a positive integer.</dd>
    <dt><span class="ID"><b>&lt;InverseQ&gt;</b></span>&nbsp;&nbsp;&nbsp;(Required)</dt>
      <dd>The (first) CRT coefficient, a positive integer.</dd>
    <dt><span class="ID"><b>&lt;D&gt;</b></span>&nbsp;&nbsp;&nbsp;(Required)</dt>
      <dd>The private exponent.</dd>
  </dl>
</blockquote>

<p><a name="XKMS_2_0_Paragraph_343" id="XKMS_2_0_Paragraph_343" class="markParagraph" shape="rect">[343]</a>&#xA0;The following schema defines the <span class="ID">&lt;RSAKeyPair&gt;</span> element:</p>
<!-- Include file -->
<pre class="Code" xml:space="preserve">   &lt;!-- RSAKeyPair --&gt;
   &lt;element name="RSAKeyPair" type="xkms:RSAKeyPairType"/&gt;
   &lt;complexType name="RSAKeyPairType"&gt;
      &lt;sequence&gt;
         &lt;element ref="xkms:Modulus"/&gt;
         &lt;element ref="xkms:Exponent"/&gt;
         &lt;element ref="xkms:P"/&gt;
         &lt;element ref="xkms:Q"/&gt;
         &lt;element ref="xkms:DP"/&gt;
         &lt;element ref="xkms:DQ"/&gt;
         &lt;element ref="xkms:InverseQ"/&gt;
         &lt;element ref="xkms:D"/&gt;
      &lt;/sequence&gt;
   &lt;/complexType&gt;
   &lt;element name="Modulus" type="ds:CryptoBinary"/&gt;
   &lt;element name="Exponent" type="ds:CryptoBinary"/&gt;
   &lt;element name="P" type="ds:CryptoBinary"/&gt;
   &lt;element name="Q" type="ds:CryptoBinary"/&gt;
   &lt;element name="DP" type="ds:CryptoBinary"/&gt;
   &lt;element name="DQ" type="ds:CryptoBinary"/&gt;
   &lt;element name="InverseQ" type="ds:CryptoBinary"/&gt;
   &lt;element name="D" type="ds:CryptoBinary"/&gt;
   &lt;!-- /RSAKeyPair --&gt;</pre>

<h1 dir="ltr"><a name="XKMS_2_0_Section_9" id="XKMS_2_0_Section_9" shape="rect">9</a> <a name="Conformance" id="Conformance" shape="rect">Conformance</a></h1>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_344" id="XKMS_2_0_Paragraph_344" class="markParagraph" shape="rect">[344]</a>The section describes features and operations
that XKMS applications whose support is either required or recommended to
ensure interoperability of XKMS services.</p>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_345" id="XKMS_2_0_Paragraph_345" class="markParagraph" shape="rect">[345]</a>As such the conformance requirements fall on
message recipients rather than message senders, although a sender SHOULD NOT
send a message unless it is known that it will be accepted by the
recipient.</p>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_346" id="XKMS_2_0_Paragraph_346" class="markParagraph" shape="rect">[346]</a>The following table specifies the conformance
requirements of XKMS as REQUIRED,. RECOMMENDED or OPTIONAL as follows:</p>
<ul dir="ltr">
  <li dir="ltr"><p dir="ltr"><a name="XKMS_2_0_Paragraph_347" id="XKMS_2_0_Paragraph_347" class="markParagraph" shape="rect">[347]</a>If support for
    a feature is specified as REQUIRED a conforming XKMS implementation MUST
    support the use of that feature in a message sent by another XKMS
    implementation.</p>
  </li>
  <li dir="ltr"><p dir="ltr"><a name="XKMS_2_0_Paragraph_348" id="XKMS_2_0_Paragraph_348" class="markParagraph" shape="rect">[348]</a>If support for
    a feature is specified as RECOMMENDED a conforming XKMS implementation
    SHOULD support the use of that feature if used by another XKMS
    implementation.</p>
  </li>
  <li dir="ltr"><p dir="ltr"><a name="XKMS_2_0_Paragraph_349" id="XKMS_2_0_Paragraph_349" class="markParagraph" shape="rect">[349]</a>If support for
    a feature is specified as OPTIONAL, XKMS implementations SHOULD NOT send
    messages requiring support for that feature.</p>
  </li>
</ul>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_350" id="XKMS_2_0_Paragraph_350" class="markParagraph" shape="rect">[350]</a>Some features are specified as REQUIRED* or
RECOMMENDED*. This signifies that the condition holds if another feature is
supported. For example an XKMS Locate service is not required to support XML
Signature. If however XML Signature is supported the use of Exclusive
Canonicalization MUST be supported.</p>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_351" id="XKMS_2_0_Paragraph_351" class="markParagraph" shape="rect">[351]</a>One feature is specified as RECOMMENDED +.
This signifies that even though this feature can only be used at the request
of the client it is strongly recommended that the client request use of this
feature since a service is likely to require it for the response to be
successful.</p>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_352" id="XKMS_2_0_Paragraph_352" class="markParagraph" shape="rect">[352]</a>Where a service supports a feature that is
advertised as OPTIONAL it is recommended that the service advertise this
feature by means of a Web Service description mechanism. For example an XKMS
service that supports the use of a transport encoding other than HTTP SHOULD
advertise that fact.</p>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_352a" id="XKMS_2_0_Paragraph_352a" class="markParagraph" shape="rect">[352a]</a> When a client request includes an
OPTIONAL element that is not supported by the Server, the server may
use <span class="ID">ResultMajor=Receiver</span> and 
<span class="ID">ResultMinor=OptionalElementNotSupported</span> code. 
In some cases, depending on the context, the server may use
the <span class="ID">Failure</span> or 
<span class="ID">MessageNotSupported</span> <span class="ID">ResultMinor</span>
codes. In any of these cases, the client should check the server's supported
features, for example by reading a WSDL <a href="#WSDL" shape="rect">[WSDL]</a> or metadata file. The resource
discovery mechanism is out of scope for this specification.</p>

<p dir="ltr"><a name="XKMS_2_0_Paragraph_353" id="XKMS_2_0_Paragraph_353" class="markParagraph" shape="rect">[353]</a>Implementers should note that these
requirements may change in future versions of the XKMS specification. For
example it is likely that future versions of the XKMS specification will make
the then current version of the SOAP specification a requirement.</p>

<div class="Table">
<p><a name="XKMS_2_0_Paragraph_354a" class="markParagraph" shape="rect" id="XKMS_2_0_Paragraph_354a">[354a]</a></p>
<table border="1" cellpadding="3" cellspacing="0" width="100%" id="AutoNumber3" dir="ltr">
  <caption>
  <strong>XKMS operations</strong>
  </caption>
  <thead>
    <tr>
      <th valign="top" dir="ltr">Feature</th>
      <th valign="top" dir="ltr">Operations</th>
      <th valign="top" dir="ltr">Requirement Level</th>
      <th valign="top" dir="ltr">Comments</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td valign="top" rowspan="4" dir="ltr">Operation Support</td>
      <td valign="top" dir="ltr">Locate</td>
      <td valign="top" dir="ltr">RECOMMENDED</td>
      <td valign="top" dir="ltr">Services SHOULD support retrieval of their
        own credential by means of the Locate operation with the XKMS
        protocol URI.</td>
    </tr>
    <tr>
      <td valign="top" dir="ltr">All</td>
      <td valign="top" dir="ltr">One Operation REQUIRED</td>
      <td valign="top" dir="ltr">A conforming XKMS service MUST support at
        least one XKMS operation, that is there MUST be at least one possible
        input that results in the result <span class="ID">Success</span>.</td>
    </tr>
    <tr>
      <td valign="top" dir="ltr">Compound</td>
      <td valign="top" dir="ltr">OPTIONAL</td>
      <td valign="top" dir="ltr">See note for Status operation support.</td>
    </tr>
    <tr>
      <td valign="top" dir="ltr">Status</td>
      <td valign="top" dir="ltr">RECOMMENDED*</td>
      <td valign="top" dir="ltr">Services SHOULD support status operations if
        asynchronous processing and compound requests are also supported.</td>
    </tr>
    <tr>
      <td valign="top" dir="ltr">Operation Response</td>
      <td valign="top" dir="ltr">All</td>
      <td valign="top" dir="ltr">REQUIRED</td>
      <td valign="top" dir="ltr">A conforming XKMS service MUST accept any
        valid XKMS request sent to it and be capable of responding to the
        request with a correctly formatted XKMS result. If a service does not
        support an operation it MUST respond to all requests for a particular
        operation with the result <span class="ID">Sender.MessageNotSupported</span>.</td>
    </tr>
  </tbody>
</table>
</div>

<div class="Table">
<p><a name="XKMS_2_0_Paragraph_354b" class="markParagraph" shape="rect" id="XKMS_2_0_Paragraph_354b">[354b]</a></p>
<table border="1" cellpadding="3" cellspacing="0" width="100%" id="AutoNumber4" dir="ltr">
  <caption>
      <strong>Response Mechanisms</strong>
  </caption>
  <thead>
    <tr>
      <th valign="top" dir="ltr">Feature</th>
      <th valign="top" dir="ltr">Operations</th>
      <th valign="top" dir="ltr">Requirement Level</th>
      <th valign="top" dir="ltr">Comments</th>
    </tr>
    </thead>
    <tbody>
    <tr>
      <td valign="top" dir="ltr">Synchronous Response</td>
      <td valign="top" dir="ltr">All</td>
      <td valign="top" dir="ltr">REQUIRED</td>
      <td valign="top" dir="ltr">A conforming XKMS service MUST be capable of
        returning an immediate response to any XKMS request.</td>
    </tr>
    <tr>
      <td valign="top" rowspan="4" dir="ltr">Asynchronous Response 
      </td>
      <td valign="top" dir="ltr">Register, Reissue, Recover</td>
      <td valign="top" dir="ltr">RECOMMENDED+</td>
      <td valign="top" dir="ltr">Processing of certain X-KRSS operations may
        require manual intervention by an operator in certain circumstances.
        It is therefore recommended that clients support the use of
        asynchronous processing with these operations unless it is known that
        all requests will be serviced immediately.</td>
    </tr>
    <tr>
      <td valign="top" dir="ltr">Compound</td>
      <td valign="top" dir="ltr">RECOMMENDED</td>
      <td valign="top" dir="ltr">Services that support Compound Operations
        SHOULD support compound requests.</td>
    </tr>
    <tr>
      <td valign="top" dir="ltr">Locate, Validate,<br clear="none" />
        Revoke</td>
      <td valign="top" dir="ltr">OPTIONAL</td>
      <td valign="top" dir="ltr">Services MAY support Asynchronous responses
        be supported on these operations.</td>
    </tr>
    <tr>
      <td valign="top" dir="ltr">Pending,<br clear="none" />
        Status</td>
      <td valign="top" dir="ltr">PROHIBITED</td>
      <td valign="top" dir="ltr">A client MAY offer asynchronous processing
        of Pending and Status operations however a service MUST NOT return a
        pending response.</td>
    </tr>
    <tr>
      <td valign="top" dir="ltr">Two-Phase Request</td>
      <td valign="top" dir="ltr">All</td>
      <td valign="top" dir="ltr">RECOMMENDED+</td>
      <td valign="top" dir="ltr">Clients SHOULD support use of the two-phase
        request protocol. The additional complexity of implementing the two
        phase protocol is not high and allows a service to provide a response
        even in cases where it is under a denial of service attack.</td>
    </tr>
   </tbody>
</table>
</div>

<div class="Table">
<p><a name="XKMS_2_0_Paragraph_354c" class="markParagraph" shape="rect" id="XKMS_2_0_Paragraph_354c">[354c]</a></p>
<table border="1" cellpadding="3" cellspacing="0" width="100%" id="AutoNumber5" dir="ltr">
  <caption>
  <strong>Protocol Encapsulation</strong>
  </caption>
  <thead>
    <tr>
      <th valign="top" dir="ltr">Feature</th>
      <th valign="top" dir="ltr">Operations</th>
      <th valign="top" dir="ltr">Requirement Level</th>
      <th valign="top" dir="ltr">Comments</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td valign="top" dir="ltr">HTTP Transport</td>
      <td valign="top" dir="ltr">All</td>
      <td valign="top" dir="ltr">REQUIRED</td>
      <td valign="top" dir="ltr">Services MUST support the use of HTTP
        transport.</td>
    </tr>
    <tr>
      <td valign="top" dir="ltr">SOAP 1.2 Transport</td>
      <td valign="top" dir="ltr">All</td>
      <td valign="top" dir="ltr">REQUIRED</td>
      <td valign="top" dir="ltr">Services MUST support the use of SOAP 1.2
        encapsulation.</td>
    </tr>
    <tr>
      <td valign="top" dir="ltr">SOAP 1.1 Transport</td>
      <td valign="top" dir="ltr">All</td>
      <td valign="top" dir="ltr">RECOMMENDED</td>
      <td valign="top" dir="ltr">Services MAY support the use of SOAP 1.1
        encapsulation.</td>
    </tr>
   </tbody>
</table>
</div>

<div class="Table">
<p><a name="XKMS_2_0_Paragraph_354d" class="markParagraph" shape="rect" id="XKMS_2_0_Paragraph_354d">[354d]</a></p>
<table border="1" cellpadding="3" cellspacing="0" width="100%" id="AutoNumber6" dir="ltr">
  <caption>
  <strong>Security Bindings</strong>
  </caption>
  <thead>
    <tr>
      <th valign="top" dir="ltr">Feature</th>
      <th valign="top" dir="ltr">Operations</th>
      <th valign="top" dir="ltr">Requirement Level</th>
      <th valign="top" dir="ltr">Comments</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td valign="top" rowspan="2" dir="ltr">No Security Binding</td>
      <td valign="top" dir="ltr">Locate</td>
      <td valign="top" dir="ltr">REQUIRED</td>
      <td valign="top" dir="ltr">An XKMS Service MUST be capable of supporting Locate operations without requiring any authentication or protocol security mechanisms.</td>
    </tr>
    <tr>
      <td valign="top" dir="ltr">[Others]</td>
      <td valign="top" dir="ltr">RECOMMENDED</td>
      <td valign="top" dir="ltr">&nbsp;</td>
    </tr>
    <tr>
      <td valign="top" dir="ltr">Payload Authentication Binding</td>
      <td valign="top" dir="ltr">All</td>
      <td valign="top" dir="ltr">RECOMMENDED</td>
      <td valign="top" dir="ltr">If XML Signature is used, Exclusive
        Canonicalization MUST be supported.</td>
    </tr>

    <tr>
      <td valign="top" dir="ltr">TLS Binding</td>
      <td valign="top" dir="ltr">All</td>
      <td valign="top" dir="ltr">RECOMMENDED</td>
      <td valign="top" dir="ltr">&#xA0;</td>
    </tr>
  </tbody>
</table>
</div>

<h1><a name="XKMS_2_0_Section_10" id="XKMS_2_0_Section_10" shape="rect">10</a> <a name="SecurityConsiderations" id="SecurityConsiderations" shape="rect">Security
Considerations</a></h1>

<p><a name="XKMS_2_0_Paragraph_355" id="XKMS_2_0_Paragraph_355" class="markParagraph" shape="rect">[355]</a>Implementations SHOULD consider the following
security issues.</p>

<h2><a name="XKMS_2_0_Section_10_1" id="XKMS_2_0_Section_10_1" shape="rect">10.1</a> <a name="ReplayAttacks" id="ReplayAttacks" shape="rect">Replay Attacks</a></h2>

<p><a name="XKMS_2_0_Paragraph_356" id="XKMS_2_0_Paragraph_356" class="markParagraph" shape="rect">[356]</a>Implementations SHOULD ensure that replay of a
previous XKMS response is not possible.</p>

<p><a name="XKMS_2_0_Paragraph_357" id="XKMS_2_0_Paragraph_357" class="markParagraph" shape="rect">[357]</a>The precise mechanism by which replay attacks
are prevented is left to the implementation. For example generic mechanism
built into the object exchange protocol if specified MAY be used.</p>

<p><a name="XKMS_2_0_Paragraph_358" id="XKMS_2_0_Paragraph_358" class="markParagraph" shape="rect">[358]</a>A generally applicable means of preventing a
replay attack is to place a token in each message that demonstrates to the
recipient that the message is 'fresh', for example:</p>
<ul type="disc">
  <li>A message origination time that the recipient verifies by checking that
    it is sufficiently recent.</li>
  <li>A nonce, that is a piece of random data that was previously issued by
    the user.</li>
  <li>A message serial number.</li>
</ul>

<h2><a name="XKMS_2_0_Section_10_2" id="XKMS_2_0_Section_10_2" shape="rect">10.2</a> <a name="DenialofService" id="DenialofService" shape="rect">Denial of Service</a></h2>

<p><a name="XKMS_2_0_Paragraph_359" id="XKMS_2_0_Paragraph_359" class="markParagraph" shape="rect">[359]</a>XKMS Services SHOULD take measures to prevent
or mitigate denial of service attacks. In particular XKMS Services SHOULD NOT
perform an unlimited number of resource intensive operations unless the
request comes from an authenticated source. Potentially resource intensive
operations include:</p>
<ul>
  <li>CPU intensive cryptographic operations, including signature
    verification and key exchange.</li>
  <li>Resolution of URLs.</li>
</ul>

<h2><a name="XKMS_2_0_Section_10_3" id="XKMS_2_0_Section_10_3" shape="rect">10.3</a> <a name="RecoveryPolicy" id="RecoveryPolicy" shape="rect">Recovery Policy</a></h2>

<p><a name="XKMS_2_0_Paragraph_360" id="XKMS_2_0_Paragraph_360" class="markParagraph" shape="rect">[360]</a>Key recovery policy is left as an
implementation decision.</p>

<p><a name="XKMS_2_0_Paragraph_361" id="XKMS_2_0_Paragraph_361" class="markParagraph" shape="rect">[361]</a>Depending on the implementation and
application, a key recovery operation might involve an unacceptable loss of
confidence in the security of a private key component. This may lead to the
possibility of repudiation of a signed document or of accountability in the
case of an encrypted document.</p>

<p><a name="XKMS_2_0_Paragraph_362" id="XKMS_2_0_Paragraph_362" class="markParagraph" shape="rect">[362]</a>Services SHOULD carefully assess the extent to
which a recovery operation compromises a private key and apply sufficient
controls such as the revocation of the underlying key binding as
appropriate.</p>

<h2><a name="XKMS_2_0_Section_10_4" id="XKMS_2_0_Section_10_4" shape="rect">10.4</a> <a name="limitedusesecurity" id="limitedusesecurity" shape="rect">Security of Limited Use
Shared Secret</a></h2>

<p><a name="XKMS_2_0_Paragraph_363" id="XKMS_2_0_Paragraph_363" class="markParagraph" shape="rect">[363]</a>If a limited use shared secret is used care
must be taken to ensure that the secret has sufficient entropy that the
probability of guessing by an attacker is tolerably low. Particular care must
be taken if a limited use shared secret is used to encrypt a service
generated private key since the transported private key might be subject to a
dictionary attack. Implementations should not re-use revocation codes
across different key bindings (regardless of the amount of entropy used when
generating them). Note that strong confidentiality protection of
RevocationCodeIdentifier and RevocationCode elements would also help against
this problem. Applications SHOULD enforce the following minimum entropy
values for the shared secret:</p>

<blockquote>
  <dl>
    <dt>Registration of Client Generated Key</dt>
      <dd>The shared secret SHOULD contain a minimum of 32 bits of entropy if
        the service implements measures to prevent guessing of the shared
        secret (which MAY include strong confidentiality protections for
        revocation code identifiers and revocation codes, providing
        safeguards against the dictionary attacks, and to protect against
        attackers recognizing deliberate or accidental collisions of
        revocation codes) and a minimum of 128 bits of entropy
      otherwise.</dd>
    <dt>Registration of Service Generated Key</dt>
      <dd>The shared secret SHOULD have a minimum of 128 bits of entropy.</dd>
  </dl>
</blockquote>

<h2><a name="XKMS_2_0_Section_10_5" id="XKMS_2_0_Section_10_5" shape="rect">10.5</a> <a name="ConfidentialityofOpaqueClientData" id="ConfidentialityofOpaqueClientData" shape="rect">Confidentiality of Opaque Client
Data</a></h2>

<p><a name="XKMS_2_0_Paragraph_364" id="XKMS_2_0_Paragraph_364" class="markParagraph" shape="rect">[364]</a>Clients SHOULD NOT send confidential or
privacy sensitive data to an XKMS Service as Opaque Data unless it is
encrypted such that it is not disclosed to the service.</p>

<p><a name="XKMS_2_0_Paragraph_365" id="XKMS_2_0_Paragraph_365" class="markParagraph" shape="rect">[365]</a>Examples of confidential data include internal
program indices such as pointers which might permit a malicious party with
access to an XKMS service or its audit logs to perform an attack based on
knowledge of the internal state of the client.</p>

<h2><a name="XKMS_2_0_Section_10_6" id="XKMS_2_0_Section_10_6" shape="rect">10.6</a> <a name="SecurityofNotBoundAuthenticationData" id="SecurityofNotBoundAuthenticationData" shape="rect">Security of Not Bound
Authentication Data</a></h2>

<p><a name="XKMS_2_0_Paragraph_366" id="XKMS_2_0_Paragraph_366" class="markParagraph" shape="rect">[366]</a>If a service supports the use of
authentication using the &lt;NotBoundAuthentication&gt; element, controls
MUST be employed to ensure the confidentiality of the authentication data and
to ensure that the &lt;NotBoundAuthentication&gt; is bound to the request.</p>

<p><a name="XKMS_2_0_Paragraph_367" id="XKMS_2_0_Paragraph_367" class="markParagraph" shape="rect">[367]</a>This MAY be a message level or transport level
protocol that protects <i>both</i> encryption <i>and integrity</i> such as
TLS [RFC-2246].</p>

<h2><a name="XKMS_2_0_Section_10_7" id="XKMS_2_0_Section_10_7" shape="rect">10.7</a> <a name="SignatureOracle" id="SignatureOracle" shape="rect">Signature Oracle</a></h2>

<p><a name="XKMS_2_0_Paragraph_368" id="XKMS_2_0_Paragraph_368" class="markParagraph" shape="rect">[368]</a>XKMS services that provide signed responses
SHOULD ensure that the requestor cannot solicit a predicted response, thus
providing a signing oracle. Such a signing oracle might provide a direct
compromise for the key under a different protocol or allow a weakness in the
signature or digest algorithm employed to be exploited.</p>

<p><a name="XKMS_2_0_Paragraph_369" id="XKMS_2_0_Paragraph_369" class="markParagraph" shape="rect">[369]</a>Response messages should include at least as
much randomly chosen data as the output of the digest algorithm used to
create the signature. For example a message signed using RSA and SHA-1 should
contain at least 160 bits of random data.</p>

<h2><a name="XKMS_2_0_Section_10_8" id="XKMS_2_0_Section_10_8" shape="rect">10.8</a> <a name="Privacy" id="Privacy" shape="rect">Privacy</a></h2>

<p><a name="XKMS_2_0_Paragraph_370" id="XKMS_2_0_Paragraph_370" class="markParagraph" shape="rect">[370]</a>An XKMS service MAY solicit data which is
subject to privacy concerns. In certain circumstances management of such data
MAY be subject to government regulation, corporate policies or contractual
obligations. Deployments SHOULD consider whether the information they collect
is subject to such concerns and if necessary deploy a privacy notification
mechanism such as P3P <a href="#P3P" shape="rect">[P3P]</a>.</p>

<h2><a name="XKMS_2_0_Section_10_9" id="XKMS_2_0_Section_10_9" shape="rect">10.9</a> <a name="SecurityofthePrivateKey" id="SecurityofthePrivateKey" shape="rect">Security of the
Private Key</a></h2>

<p><a name="XKMS_2_0_Paragraph_371" id="XKMS_2_0_Paragraph_371" class="markParagraph" shape="rect">[371]</a>Implementations MUST ensure that in cases
where a private key is generated by the service, the information used to
encrypt the private key data is adequately protected. In particular if an
authentication pass phrase exchanged out of band is used to encrypt the
private key the implementation MUST ensure that the out of band communication
mechanism adequately protects the confidentiality of the pass phrase.</p>

<p><a name="XKMS_2_0_Paragraph_372" id="XKMS_2_0_Paragraph_372" class="markParagraph" shape="rect">[372]</a>It is recommended that implementations make
use of TLS or an in-band key exchange mechanism to protect the private key in
the case that the authentication pass phrase is disclosed.</p>

<p><a name="XKMS_2_0_Paragraph_372a" id="XKMS_2_0_Paragraph_372a" class="markParagraph" shape="rect">[372a]</a>Implementations supporting encryption of
Private Key Data MUST support Shared Secret. Use of Shared Secret is detailed
in section 8.1.</p>

<h2><a name="XKMS_2_0_Section_10_10" id="XKMS_2_0_Section_10_10" shape="rect">10.10</a> <a name="MessageLengthDisclosureVulnerabilities" id="MessageLengthDisclosureVulnerabilities" shape="rect">Message Length Disclosure
Vulnerabilities</a></h2>

<p><a name="XKMS_2_0_Paragraph_373" id="XKMS_2_0_Paragraph_373" class="markParagraph" shape="rect">[373]</a>In certain circumstances the length of an
encrypted response MAY reveal information that is useful to an attacker. For
example a short message might indicate that a request was refused.
Deployments SHOULD consider whether such disclosures might result in
compromise of confidential information.</p>

<h2><a name="XKMS_2_0_Section_10_11" id="XKMS_2_0_Section_10_11" shape="rect">10.11</a> <a name="CheckForSignatureValueInSignedSOAPMessage" id="CheckForSignatureValueInSignedSOAPMessage" shape="rect">Check for Signature Value in a
Signed SOAP Message</a></h2>

<p><a name="XKMS_2_0_Paragraph_373a" id="XKMS_2_0_Paragraph_373a" class="markParagraph" shape="rect">[373a]</a> The Implementation of XKMS MUST check for
a signature value reference in the to-be-signed data when using a Signed SOAP
message. Also, implementations MUST ensure that all the bytes in the XKMS messages,
e.g., from <code>&lt;LocateRequest&gt; .... &lt;/LocateRequest&gt;</code>, be included in 
hashing and in the resulting signature value of the message.</p>

<h1 class="appendix"><a name="XKMS_2_0_Section_Appendix_A" id="XKMS_2_0_Section_Appendix_A" shape="rect">Appendix A</a> <a name="Schemas" id="Schemas" shape="rect">Schemas</a></h1>

<h2><a name="XKMS_2_0_Section_A_1" id="XKMS_2_0_Section_A_1" shape="rect">A.1</a> <a name="XKMSSchema" id="XKMSSchema" shape="rect">XKMS Schema</a></h2>
The collected schema is available <a href="Schemas/xkms.xsd" shape="rect">here</a><!-- include class="Code" source="Schemas/xkms.xsd"></include -->
 

<h1 class="appendix"><a name="XKMS_2_0_Section_Appendix_B" id="XKMS_2_0_Section_Appendix_B" shape="rect">Appendix B</a> <a name="ServiceLocationConfiguration" id="ServiceLocationConfiguration" shape="rect">Service
Location Configuration (Non-Normative)</a></h1>

<p><a name="XKMS_2_0_Paragraph_374" id="XKMS_2_0_Paragraph_374" class="markParagraph" shape="rect">[374]</a>In many instances it is desirable to advertise
the existence of an XKMS service in some form of discovery protocol. This
appendix describes specific means of advertising the existence of XKMS
services in the Internet Domain Name Service (DNS).</p>

<h2><a name="XKMS_2_0_Section_B_1" id="XKMS_2_0_Section_B_1" shape="rect">B.1</a> <a name="DomainNameService" id="DomainNameService" shape="rect">Domain Name Service</a>
(DNS)</h2>

<p class="appendix"><a name="XKMS_2_0_Paragraph_375" id="XKMS_2_0_Paragraph_375" class="markParagraph" shape="rect">[375]</a>The provision of
an XKMS service that provides information on key information bound to DNS
addresses in a specified DNS zone MAY be advertised by means of the DNS SRV
record <a href="#RFC-2782" shape="rect">[RFC 2782]</a>. An SRV record contains the
following data fields:</p>

<p class="appendix"><a name="XKMS_2_0_Paragraph_376" id="XKMS_2_0_Paragraph_376" class="markParagraph" shape="rect">[376]</a><span class="ID">_<i>Service</i>._<i>Protocol</i>.<i>Name</i><i>TTL</i><i>Class</i><i>SRV</i><i>Priority</i><i>Weight</i><i>Port</i><i>Target</i></span></p>
<dl>
  <dt>Service</dt>
    <dd>The symbolic name of the desired service, as defined in Assigned
      Numbers [STD 2] or locally.&#xA0; An underscore (_) is prepended to the
      service identifier to avoid collisions with DNS labels that occur in
      nature.</dd>
  <dt>Protocol</dt>
    <dd>The symbolic name of the desired protocol, with an underscore (_)
      prepended to prevent collisions with DNS labels that occur in
    nature.</dd>
  <dt>Name</dt>
    <dd>The domain this RR refers to. The SRV RR is unique in that the name
      one searches for is not this name.</dd>
  <dt>TTL</dt>
    <dd>Standard DNS meaning [RFC 1035].</dd>
  <dt>Class</dt>
    <dd>Standard DNS meaning [RFC 1035]. SRV records occur in the IN
    Class.</dd>
  <dt>Priority</dt>
    <dd>The priority of this target host. A client MUST attempt to contact
      the target host with the lowest-numbered priority it can reach; target
      hosts with the same priority SHOULD be tried in an order defined by the
      weight field.</dd>
  <dt>Weight</dt>
    <dd>A server selection mechanism. The weight field specifies a relative
      weight for entries with the same priority. Larger weights SHOULD be
      given a proportionately higher probability of being selected. The range
      of this number is 0-65535.</dd>
  <dt>Port</dt>
    <dd>The port on this target host of this service. The range is 0-65535.
      This is a 16 bit unsigned integer in network byte order. This is often
      as specified in Assigned Numbers but need not be.</dd>
  <dt>Target</dt>
    <dd>The domain name of the target host. There MUST be one or more address
      records for this name, the name MUST NOT be an alias (in the sense of
      RFC 1034 or RFC 2181). Implementors are urged, but not required, to
      return the address record(s) in the Additional Data section. Unless and
      until permitted by future standards action, name compression is not to
      be used for this field.</dd>
</dl>

<p><a name="XKMS_2_0_Paragraph_377" id="XKMS_2_0_Paragraph_377" class="markParagraph" shape="rect">[377]</a>The following service values are defined:</p>
<dl>
  <dt>_XKMS_XKISS_SOAP_HTTP</dt>
    <dd>An XKMS service supporting the X-KISS protocol in the SOAP binding
      using HTTP as the application layer transport. The Protocol value for
      this service is TCP.</dd>
  <dt>_XKMS_XKRSS_SOAP_HTTP</dt>
    <dd>An XKMS service supporting the X-KRSS protocol in the SOAP binding
      using HTTP as the application layer transport. The Protocol value for
      this service is TCP.</dd>
</dl>

<p><a name="XKMS_2_0_Paragraph_378" id="XKMS_2_0_Paragraph_378" class="markParagraph" shape="rect">[378]</a>The publication of an SRV record in a DNS zone
that advertises an XKMS service is an affirmative statement by the operator
of the zone that the XKMS service indicated MAY be queried for information
concerning key information bound to protocol addresses within that zone. The
publication of an SRV record does not imply any undertaking on the part of
the part of the publisher to ensure that the information provided by the XKMS
service is accurate or trustworthy. Relying parties MUST therefore establish
the trustworthiness of any information they may receive from an XKMS service
discovered by means of an SRV record by other means, for example by
forwarding the data to an XKMS Validate service.</p>

<h3><a name="XKMS_2_0_Section_B_1_1" id="XKMS_2_0_Section_B_1_1" shape="rect">B.1.1</a>
Examples</h3>

<p><a name="XKMS_2_0_Paragraph_379" id="XKMS_2_0_Paragraph_379" class="markParagraph" shape="rect">[379]</a>The following SRV record advertises an XKMS
X-KISS service on port 80 of border-xkms.example.com:</p>

<p><a name="XKMS_2_0_Paragraph_380" id="XKMS_2_0_Paragraph_380" class="markParagraph" shape="rect">[380]</a><span class="ID">_XKMS_XKISS_SOAP_HTTP._TCP.example.com - IN 0 1 80
border-xkms.example.com</span></p>

<p><a name="XKMS_2_0_Paragraph_381" id="XKMS_2_0_Paragraph_381" class="markParagraph" shape="rect">[381]</a>The following SRV record advertises three XKMS
X-KISS services, main1, main2 and backup. Clients should direct requests to
main1 and main2 with equal priority. The service backup should only be
accessed if neither main1 or main2 is available:</p>

<p><a name="XKMS_2_0_Paragraph_382" id="XKMS_2_0_Paragraph_382" class="markParagraph" shape="rect">[382]</a><span class="ID">_XKMS_XKISS_SOAP_HTTP._TCP.example.com - IN 0 50 80
main1.example.com<br clear="none" />
_XKMS_XKISS_SOAP_HTTP._TCP.example.com - IN 0 50 80 main2.example.com<br clear="none" />
_XKMS_XKISS_SOAP_HTTP._TCP.example.com - IN 1 1 80
backup.example.com</span></p>

<h1 class="appendix"><a name="XKMS_2_0_Section_Appendix_C" id="XKMS_2_0_Section_Appendix_C" shape="rect">Appendix C</a> <a id="SampleProtocolExchanges" name="SampleProtocolExchanges" shape="rect">Sample Protocol
Exchanges (Non-Normative)</a></h1>

<p><a name="XKMS_2_0_Paragraph_383" id="XKMS_2_0_Paragraph_383" class="markParagraph" shape="rect">[383]</a>For clarity the examples in the running text
omit certain details such as the message authentication signatures and SOAP
binding information. This section provides these messages in full
to facilitate interoperability testing.</p>

<h2><a name="XKMS_2_0_Section_C_1" id="XKMS_2_0_Section_C_1" shape="rect">C.1</a> <a name="AuthenticationComputation" id="AuthenticationComputation" shape="rect">Authentication Computation</a></h2>

<p><a name="XKMS_2_0_Paragraph_384" id="XKMS_2_0_Paragraph_384" class="markParagraph" shape="rect">[384]</a>The calculation of the authentication values
used in the examples.</p>

<h3><a name="XKMS_2_0_Section_C_1_1" id="XKMS_2_0_Section_C_1_1" shape="rect">C.1.1</a> <a name="AliceRegistrationAuthenticationKey" id="AliceRegistrationAuthenticationKey" shape="rect">Alice Registration Authentication
Key</a></h3>
<dl>
  <dt>Authentication Data</dt>
    <dd><span class="ID">024837</span></dd>
  <dt>Converted Authentication Data</dt>
    <dd><span class="ID">[30][32][34][38][33][37]</span></dd>
  <dt>Key = HMAC-SHA1 (Converted Authentication Data, 0x1)</dt>
    <dd><span class="ID">[d6][cc][34][cb][83][fa][e2][99]
      [3a][39][3a][a8][e7][de][9a][06] [c7][fa][2c][92]</span></dd>
</dl>

<h3><a name="XKMS_2_0_Section_C_1_2" id="XKMS_2_0_Section_C_1_2" shape="rect">C.1.2</a> <a name="BobRegistrationAuthenticationKey" id="BobRegistrationAuthenticationKey" shape="rect">Bob Registration Authentication
Key</a></h3>
<dl>
  <dt>Authentication Data</dt>
    <dd><span class="ID">3N9CJ-JK4JK-S04JF-W0934-JSR09-JWIK4</span></dd>
  <dt>Converted Authentication Data</dt>
    
    <dd><span class="ID">[33][4e][39][43][4a][2d][4a][4b]
      [34][4a][4b][2d][53][30][34][4a] [46][2d][57][30][39][33][34][2d]
      [4a][53][52][30][39][2d][4a][57] [49][4b][34]</span></dd>
  <dt>Key = HMAC-SHA1 (Converted Authentication Data, 0x1)</dt>
    
    <dd><span class="ID">[3f][9a][5d][33][62][96][78][87]
      [eb][ce][55][37][b7][40][13][e8] [cd][40][b0][3f]</span></dd>
</dl>

<h3><a name="XKMS_2_0_Section_C_1_3" id="XKMS_2_0_Section_C_1_3" shape="rect">C.1.3</a> <a name="BobRegistrationPrivateKeyEncryption" id="BobRegistrationPrivateKeyEncryption" shape="rect">Bob Registration Private Key
Encryption</a></h3>
<dl>
  <dt>Authentication Data</dt>
    <dd><span class="ID">3N9CJ-K4JKS-04JWF-0934J-SR09JW-IK4</span></dd>
  <dt>Converted Authentication Data</dt>
    
    <dd><span class="ID">[33][4e][39][43][4a][2d][4b][34]
      [4a][4b][53][2d][30][34][4a][57] [46][2d][30][39][33][34][4a][2d]
      [53][52][30][39][4a][57][2d][49] [4b][34]</span></dd>
  <dt>First Block = HMAC-SHA1 (Converted Authentication Data, 0x4)</dt>
    
    <dd><span class="ID">[78][e8][bb][f5][32][d0][1d][ec]
      [e3][8a][a9][d2][a4][a4][09][db] [ff][1a][26][5c]</span></dd>
  <dt>Key = First Block XOR 0x4</dt>
    
    <dd><span class="ID">[7c][e8][bb][f5][32][d0][1d][ec]
      [e3][8a][a9][d2][a4][a4][09][db] [ff][1a][26][5c]</span></dd>
  <dt>Second Block = HMAC-SHA1 (Converted Authentication Data, Key)</dt>
    
    <dd><span class="ID">[db][ae][1b][95][7a][48][46][b7]
      [f3][6e][36][ef][0b][44][62][d0] [fe][8a][9a][7b]</span></dd>
  <dt>Final Secret Key</dt>
    
    <dd><span class="ID">[78][e8][bb][f5][32][d0][1d][ec]
      [e3][8a][a9][d2][a4][a4][09][db]
      [ff][1a][26][5c][db][ae][1b][95]</span></dd>
</dl>

<p><a name="XKMS_2_0_Paragraph_385" id="XKMS_2_0_Paragraph_385" class="markParagraph" shape="rect">[385]</a>The secret key
is used to encrypt Bob's private key as follows:</p>
<dl>
  <dt>Initialization Vector</dt>
    <dd><span class="ID">
      [12][6e][b1][10][8b][e3][8e][5a]</span></dd>
  <dt>PlainText</dt>
    <dd><code>&lt;?xml version="1.0"
      encoding="utf-8"?&gt;<br clear="none" />
      &lt;RSAKeyPair xmlns="http://www.w3.org/2002/03/xkms#"&gt; ...<br clear="none" />
      </code></dd>
  <dt>Plain Text</dt>
    <dd><span class="ID">
      [3c][3f][78][6d][6c][20][76][65] [72][73][69][6f][6e][3d][22][31]
      [2e][30][22][20][65][6e][63][6f] [64][69][6e][67][3d][22][75][74]
      [66][2d][38][22][3f][3e][0a][3c] [52][53][41][4b][65][79][50][61]
      [69][72][20][78][6d][6c][6e][73] [3d][22][68][74][74][70][3a][2f]
      [2f][77][77][77][2e][77][33][2e] [6f][72][67][2f][32][30][30][32]
      [2f][30][33][2f][78][6b][6d][73] ...<br clear="none" />
      [69][72][3e][ba][cb][c1][59][05]</span></dd>
  <dt>Cipher Text (with pre-pended Initialization Vector)</dt>
    <dd><span class="ID"><br clear="none" />
      [12][6e][b1][10][8b][e3][8e][5a] [aa][78][45][4e][75][ff][45][ab]
      [61][3a][c9][cc][f9][39][9a][d4] [53][78][f0][ed][f0][4c][86][23]
      [3c][05][c8][92][0b][7a][ab][cb] [b1][80][96][f4][45][a7][f0][e2]
      [0f][9c][d9][76][e4][9a][0e][b8] [83][db][b1][c6][3a][e5][a8][d5]
      [f2][e2][86][03][9c][c3][9b][30] [f8][6f][67][ca][17][f1][2a][8e]
      [c8][67][60][c4][b2][cd][03][0f] [91][f7][00][06][67][4d][6a][de]
      ...<br clear="none" />
      [75][7d][60][53][7c][03][e7][f0]</span></dd>
</dl>

<h3><a name="XKMS_2_0_Section_C_1_4" id="XKMS_2_0_Section_C_1_4" shape="rect">C.1.4</a> <a name="BobRecoveryPrivateKeyEncryption" id="BobRecoveryPrivateKeyEncryption" shape="rect">Bob Recovery Private Key
Encryption</a></h3>
<dl>
  <dt>Authentication Data</dt>
    <dd><span class="ID">A8YUT vuhhu c9h29 8y43u h9j3i 23</span></dd>
  <dt>Converted Authentication Data</dt>
    <dd><span class="ID">
      [41][38][59][55][54][20][76][75] [68][68][75][20][63][39][68][32]
      [39][20][38][79][34][33][75][20]
      [68][39][6a][33][69][20][32][33]</span></dd>
  <dt>Secret Key</dt>
    <dd><span class="ID"><br clear="none" />
      [21][02][af][d9][e4][7a][88][0b] [57][d8][80][04][4b][9e][ef][11]
      [77][b8][01][25][85][02][b7][4c]</span></dd>
</dl>

<h2><a name="XKMS_2_0_Section_C_2" id="XKMS_2_0_Section_C_2" shape="rect">C.2</a> <a name="PassPhraseComputation" id="PassPhraseComputation" shape="rect">Pass Phrase
Computation</a></h2>

<p><a name="XKMS_2_0_Paragraph_386" id="XKMS_2_0_Paragraph_386" class="markParagraph" shape="rect">[386]</a>The calculation of the pass phrase values used
in the examples.</p>

<h3><a name="XKMS_2_0_Section_C_2_1" id="XKMS_2_0_Section_C_2_1" shape="rect">C.2.1</a> <a name="AlicePassPhraseComputation" id="AlicePassPhraseComputation" shape="rect">Alice Pass
Phrase Computation</a></h3>
<dl>
  <dt>Pass Phrase</dt>
    <dd><span class="ID">"Help I Have Revealed My Key"</span></dd>
  <dt>Converted Pass Phrase</dt>
    <dd><span class="ID">
      
      [48][65][6c][70][20][49][20][48] [61][76][65][20][52][65][76][65]
      [61][6c][65][64][20][4d][79][20] [4b][65][79]</span></dd>
  <dt>Pass Phrase Pass 1 HMAC-SHA1 (Converted Authentication Data,
   0x2)</dt>
    <dd><span class="ID">
      
      [1c][08][57][c9][54][58][c2][6f] [44][32][7e][fd][0e][f0][55][b0]
      [8c][ad][5c][78]</span></dd>
  <dt>Pass Phrase Pass 2 = HMAC-SHA1 (Pass Phrase Pass 1 , 
  0x3)</dt>
    <dd><span class="ID">
      
      [e6][b4][4d][d9][c3][99][88][c9] [5c][88][9c][41][a9][a7][a5][ad]
      [90][c2][cd][21]</span></dd>
  <dt>Base 64 Encoding of Pass Phrase</dt>
    <dd><span class="ID"> 
      5rRN2cOZiMlciJxBqaelrZDCzSE=</span></dd>
</dl>

<h3><a name="XKMS_2_0_Section_C_2_2" id="XKMS_2_0_Section_C_2_2" shape="rect">C.2.2</a> <a name="BobPassPhraseComputation" id="BobPassPhraseComputation" shape="rect">Bob Pass Phrase
Computation</a></h3>
<dl>
  <dt>Pass Phrase</dt>
    <dd><span class="ID">"Have A Banana"</span></dd>
  <dt>Converted Pass Phrase</dt>
    <dd><span class="ID">
      
      [48][61][76][65][20][41][20][42] [61][6e][61][6e][61]</span></dd>
  <dt>Pass Phrase Pass 1 = HMAC-SHA1 (Converted Authentication
  Data, 0x2)</dt>
    <dd><span class="ID">
      
      [2b][62][13][bd][55][9d][c7][99] [f1][4e][d0][24][7c][4c][60][af]
      [42][0b][b1][76]</span></dd>
  <dt>Base 64 Encoding of Pass Phrase Stage 1</dt>
    <dd><span class="ID"> 
      K2ITvVWdx5nxTtAkfExgr0ILsXY=</span></dd>
  <dt>Pass Phrase Pass 2 = HMAC-SHA1 (Pass Phrase Pass 1, 
  0x3)</dt>
    <dd><span class="ID">
      [5b][57][bf][7b][13][63][65][23] [e9][52][e3][62][2e][35][95][e5]
      [6b][a0][30][cc]</span></dd>
  <dt>Base 64 Encoding of Pass Phrase Stage 2</dt>
    <dd><span class="ID">
      W1e/exNjZSPpUuNiLjWV5WugMMw=</span></dd>
</dl>

<h2><a name="XKMS_2_0_Section_C_3" id="XKMS_2_0_Section_C_3" shape="rect">C.3</a> Private
Key Parameters</h2>

<p><a name="XKMS_2_0_Paragraph_387" id="XKMS_2_0_Paragraph_387" class="markParagraph" shape="rect">[387]</a>The parameters of the parties RSA key pairs
are as follows:</p>

<h3><a name="XKMS_2_0_Section_C_3_1" id="XKMS_2_0_Section_C_3_1" shape="rect">C.3.1</a> <a name="AlicePrivateKeyParameters" id="AlicePrivateKeyParameters" shape="rect">Alice Private
Key Parameters</a></h3>
<!-- Include file -->
<pre class="Example" xml:space="preserve">

&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;RSAKeyPair xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
      xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;Modulus&gt;
    0nIsmR+aVW2egl5MIfOKy4HuMKkk9AZ/IQuDLVPlhzOfgngjVQCjr8uvmnqtNu8HBupui8LgG
    thO6U9D0CNT5mbmhIAErRADUMIAFsi7LzBarUvNWTqYNEJmcHsAUZdrdcDrkNnG7SzbuJx+GD
    NiHKVDQggPBLc1XagW20RMvok=
  &lt;/Modulus&gt;
  &lt;Exponent&gt;AQAB&lt;/Exponent&gt;
  &lt;P&gt;
    7p05u5P4BO+aXdyD/6n31a4Dk9kC4Tv5fMbE15/ioPii9JwPU2J29qhO1QEqvgNwxv67w4jrC
    025Yz5LXgjziw==
  &lt;/P&gt;
  &lt;Q&gt;
    4ceKAtGgSJg8ddRxwz8OESXVOd1tlSHFu7Gqona3VxbrOONLZEbsnYA4dv4nI+pxl8PmUe5CP
    gggGElx30OIuw==
  &lt;/Q&gt;
  &lt;DP&gt;
    ve9rEDQVfaBYCRTKAY2DGJT+hgZ881qxGjCCaXz8gdPIqts6m85KEcchkQ3vvvawI8aLIXdwW
    TwSMLxac8y+Rw==
  &lt;/DP&gt;
  &lt;DQ&gt;
    jW/x3ggx76gmn+3hAl3a0xUvORukjTrl4snOyg2ylsUNv8prrTrc+WGcfbaDEHXKiTc4bnTiX
    He8m1pPEnz9Bw==
  &lt;/DQ&gt;
  &lt;InverseQ&gt;
    yxCo+k0v8n80Qeo2QAGKiwltLF+1ObyZ1TQg4chISWdfLD+j1nIKIs1miELdszjO/szLWMx5k
    A3kOLi6jXsByw==
  &lt;/InverseQ&gt;
  &lt;D&gt;
    aeLWu8jh75/zRGdL6T1QFatvfH5uwHXQW4EeZJ00/P0lghEOvgNPWPGkjpaxNtW39GvaaWoJN
    pilw9CFL2HHIVn1OVZyw5BDbotQty3lm66KL7qtrjqlqyPu5ARglGqTZIaRyP8LW6NAbkyxLP
    npADVfHJuEePmooCmHbTValP0=
  &lt;/D&gt;
&lt;/RSAKeyPair&gt;</pre>

<h3><a name="XKMS_2_0_Section_C_3_2" id="XKMS_2_0_Section_C_3_2" shape="rect">C.3.2</a> <a name="BobPrivateKeyParameters" id="BobPrivateKeyParameters" shape="rect">Bob Private Key
Parameters</a></h3>
<!-- Include file -->
<pre class="Example" xml:space="preserve">

&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;RSAKeyPair xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
      xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;Modulus&gt;
    3FFtWUsvEajQt2SeSF+RvAxWdPPh5GSlQnp8SDvvqvCwE6PXcRWrIGmV7twNf2TUXCxYuztUU
    ClMIy14B0Q+k1ej2nekmYL7+Ic3DDGVFVaYPoxaRY0Y2lV8tOreynWegpFbITXc8V6Y02QfR5
    O7Pn1/10ElslaF/TF8MQGqYE8=
  &lt;/Modulus&gt;
  &lt;Exponent&gt;AQAB&lt;/Exponent&gt;
  &lt;P&gt;
    8dnXAObQvcKL0Rr/A+5Ufp1yJgLpH+uohFcJV2kUDCzv5VWKcN+LTq2mciKlnFbAQXKa5dNPO
    x4qi3An/4NSMQ==
  &lt;/P&gt;
  &lt;Q&gt;
    6TUX4d9+enb/aLHtck39x7cPQWlKkNFFJAqXaaRScDhjf4d8b009uW/pu3O2BdIJPY8M/QnUR
    lqXGLqGGl26fw==
  &lt;/Q&gt;
  &lt;DP&gt;
    LVEcMFcPlf72I+BjGGF4A6GM2gKBnDGUCfglD/Pohb+F0/sLTcsVV1DCd3B2h6zZqWnIDHhjy
    DgG0MnbNM1ugQ==
  &lt;/DP&gt;
  &lt;DQ&gt;
    0DWm7PMtaQl1X3P8G2Gmgvjdlfj7qfAtWtBZ/ufG8oplyyab4oOD6FwSwlm82dV8iol9fy2Xa
    HjZDir6L/Ae4Q==
  &lt;/DQ&gt;
  &lt;InverseQ&gt;
    sD2Vl/CCVTDbhhLwdfc4IQDBOh8xpBUV7PPM5LFGjiLetlfwaYi7Bp2ol8WF1MX88iCV2E3xO
    PCNfbMhvEB5dA==
  &lt;/InverseQ&gt;
  &lt;D&gt;
    REUnMUhO6ZX6NxoCwkJ7El5wXAVGtlNJsnPqFygbeEjlBvD6TZx9TqnpP/8IX7WK6JUFWd9kn
    QJvCWeJjhbjnImSS/3xc+v+m4glnnebZbaghvfunbI++fQaNAFRVT1hLvEGknqC/7zsrUM04o
    gU7hP+XgdFTJ1QYGfGHl5c0IE=
  &lt;/D&gt;
&lt;/RSAKeyPair&gt;</pre>

<h3><a name="XKMS_2_0_Section_C_3_3" id="XKMS_2_0_Section_C_3_3" shape="rect">C.3.3</a> <a name="XKMSServicePrivateKeyParameters" id="XKMSServicePrivateKeyParameters" shape="rect">XKMS Service Private Key
Parameters</a></h3>
<!-- Include file -->
<pre class="Example" xml:space="preserve">

&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;RSAKeyPair xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
      xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
      xmlns="http://www.w3.org/2002/03/xkms#"&gt;
  &lt;Modulus&gt;
    189VeX3+tAcwQPGMtYm8/CEKRfe6DtBFZ11SAREHhMIqf68/dsmbes0q0dnxWQcKfQtVDfp6R
    f0ulk5rZZ3j2vHHK9OFXMfaF+zJdATJ3KkXd5myjNf2clYWqKZp7K8/7Wo/qIiL8EsCT7yihR
    QvkYfYprFbF9GjKJPs4ng+zE8=
  &lt;/Modulus&gt;
  &lt;Exponent&gt;AQAB&lt;/Exponent&gt;
  &lt;P&gt;
    6+mJu5c75rQ2D0NjjZVgpzwHC2Rqcz+Dqs8E+f6yN2cYH5DTRKk08YGWSJanxwkNHCRSOC8KZ
    spLzmnVUyKavw==
  &lt;/P&gt;
  &lt;Q&gt;
    6i+ZxJX3FDz8SwIvFEp+Vzu2C+N3USgOWGghrZuYzxKSoawpmIU0+22IVug1H3w0c7ae+5d35
    8O8APR+7v0CcQ==
  &lt;/Q&gt;
  &lt;DP&gt;
    Wizzy/P8HqyF+YGd3THbNzGX07/3fMQrdTAay+CSiODsdKxsRVOUfDg3lNmZmlgYXch4cSdyB
    2aOYYFM3LFeiw==
  &lt;/DP&gt;
  &lt;DQ&gt;
    0GAuiHeP9FgXfX6h+YIXTPN6lrV9k576tLtjTCCpJYe3JVgVYvsUG6xopjvUGQHhghy69c7fC
    EBn5smmsGw8YQ==
  &lt;/DQ&gt;
  &lt;InverseQ&gt;
    phQH0GiKxdQnq7xj+5z69zLL6cI/53STn/XXZz9A/XRPUJecJxUguJHgbrKAI1aylLBZB0CfS
    +UVkIkoF/nP2g==
  &lt;/InverseQ&gt;
  &lt;D&gt;
    ybPx+oRlO1QAqKJa1g2vgaNL28tGrbPBOnPBQlftRArJ998OnPKfi+4YWFyvs3reNbMSwubZw
    3J4SWlv/WDN5Ux2ozdqjl8DShZfhpeRhVIkygg8tDqqbkVmuzQyUbDR5NncMiEPX5errlrCyd
    wsc2OgUDHYXslORPsRFh/Fk6E=
  &lt;/D&gt;
&lt;/RSAKeyPair&gt;</pre>

<h1 class="appendix"><a name="XKMS_2_0_Section_Appendix_D" id="XKMS_2_0_Section_Appendix_D" shape="rect">Appendix D</a> <a name="References" id="References" shape="rect">References (Non-Normative)</a></h1>

<p class="Ref"><a name="XKMS_2_0_Paragraph_388" id="XKMS_2_0_Paragraph_388" class="markParagraph" shape="rect">[388]</a><a name="CSP" id="CSP" shape="rect"><b>[CSP]</b></a> C. A.
R. Hoare, Communicating Sequential Processes, Prentice Hall, 1985, <a href="http://www.usingcsp.com/" shape="rect">http://www.usingcsp.com/</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_389" id="XKMS_2_0_Paragraph_389" class="markParagraph" shape="rect">[389]</a><b><a name="P3P" id="P3P" shape="rect">[P3P]</a></b>&#xA0;L. Cranor, M. Langheinrich, M.
Marchiori, M. Presler-Marshall, J. Reagle, <i>&#xA0;The Platform for
Privacy Preferences 1.0 (P3P1.0) Specification</i>, W3C Recommendation 16
April 2002, <a href="http://www.w3.org/TR/2002/REC-P3P-20020416/" shape="rect">http://www.w3.org/TR/2002/REC-P3P-20020416/</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_390" id="XKMS_2_0_Paragraph_390" class="markParagraph" shape="rect">[390]</a><b><a name="pkix" id="pkix" shape="rect">[PKIX]</a>&#xA0;</b> R. Housley, W. Ford, W. Polk, D. Solo, Internet
X.509 Public Key Infrastructure Certificate and CRL Profile, IETF RFC 2459,
January 1999, <a href="http://www.ietf.org/rfc/rfc2459.txt" shape="rect">http://www.ietf.org/rfc/rfc2459.txt</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_391" id="XKMS_2_0_Paragraph_391" class="markParagraph" shape="rect">[391]</a><b>[<a id="PKCS1" name="PKCS1" shape="rect">PKCS1</a>]</b>
B. Kaliski, <i>PKCS #1: RSA Encryption Version 2.</i>0, RSA Laboratories,
also IETF RFC 2437, October 1998. <a href="http://www.ietf.org/rfc/rfc2437.txt" shape="rect">http://www.ietf.org/rfc/rfc2437.txt</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_392" id="XKMS_2_0_Paragraph_392" class="markParagraph" shape="rect">[392]</a><b><a name="ref-KEYWORDS" id="ref-KEYWORDS" shape="rect">[RFC2119]</a></b> S. Bradner, <i>Key words for use in RFCs
to Indicate Requirement Levels</i>, IETF RFC 2119, March 1997, <a href="http://www.ietf.org/rfc/rfc2119.txt" shape="rect">http://www.ietf.org/rfc/rfc2119.txt</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_393" id="XKMS_2_0_Paragraph_393" class="markParagraph" shape="rect">[393]</a><b><a name="RFC2459" id="RFC2459" shape="rect">[RFC2459]</a></b> R. Housley, W. Ford, W. Polk, D. Solo,
<i>Internet X.509 Public Key Infrastructure Certificate and CRL Profile</i>,
IETF&#xA0; RFC 2459, January 1999. <a href="http://www.ietf.org/rfc/rfc2459.txt" shape="rect">http://www.ietf.org/rfc/rfc2459.txt</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_394" id="XKMS_2_0_Paragraph_394" class="markParagraph" shape="rect">[394]</a><b>[<a id="RFC-2104" name="RFC-2104" shape="rect">RFC-2104</a>]</b> H. Krawczyk,, M. Bellare, and
R. Canetti, <i>HMAC: Keyed Hashing for Message Authentication</i>, IETF&#xA0;
RFC 2104, February 1997. <a href="http://www.ietf.org/rfc/rfc2104.txt" shape="rect">http://www.ietf.org/rfc/rfc2104.txt</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_395" id="XKMS_2_0_Paragraph_395" class="markParagraph" shape="rect">[395]</a><b><a id="TLS" name="TLS" shape="rect">[RFC-2246]</a></b>
T. Dierks, C. Allen., <i>The TLS Protocol Version, 1.0.</i>&#xA0;IETF RFC
2246 January 1999. <a href="http://www.ietf.org/rfc/rfc2246.txt" shape="rect">http://www.ietf.org/rfc/rfc2246.txt</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_396" id="XKMS_2_0_Paragraph_396" class="markParagraph" shape="rect">[396]</a><b><a name="RFC-2373" id="RFC-2373" shape="rect">[RFC-2373]</a></b>
 R. Hinden, S. Deering,<i>IP Version 6 Addressing Architecture</i>, <i>&#xA0;</i>&#xA0;IETF
RFC 2373 July 1998., <a href="http://www.ietf.org/rfc/rfc2373.txt" shape="rect">http://www.ietf.org/rfc/rfc2373.txt</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_397" id="XKMS_2_0_Paragraph_397" class="markParagraph" shape="rect">[397]</a><b><a name="RFC-2782" id="RFC-2782" shape="rect">[RFC-2782]</a></b> A. Gulbrandsen, P. Vixie, L. Esibov, <i>A DNS
RR for specifying the location of services (DNS SRV)</i>. IETF RFC 2782,
February 2000. <a href="http://www.ietf.org/rfc/rfc2782.txt" shape="rect">http://www.ietf.org/rfc/rfc2782.txt</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_397b" id="XKMS_2_0_Paragraph_397b" class="markParagraph" shape="rect">[397b]</a><b><a name="SASLPREP" id="SASLPREP" shape="rect">[SASLPREP]</a></b> K. D. Zeilenga,
<i>SASLprep: Stringprep profile for user names and passwords</i>, IETF RFC 4013, February 2005, <a href="http://www.ietf.org/rfc/rfc4013.txt" shape="rect">http://www.ietf.org/rfc/rfc4013.txt</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_398" id="XKMS_2_0_Paragraph_398" class="markParagraph" shape="rect">[398]</a><b>[<a id="SOAP" name="SOAP" shape="rect">SOAP</a>]</b>
M. Gudgin, et al. <i>SOAP Version 1.2 Part 1: Messaging Framework</i>,
W3C Recommendation 24 June 2003, <a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/" shape="rect">http://www.w3.org/TR/2003/REC-soap12-part1-20030624/</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_399" id="XKMS_2_0_Paragraph_399" class="markParagraph" shape="rect">[399]</a><b><a name="XMLP" id="XMLP" shape="rect">[XMLP]</a></b> XML
Protocol Working Group, <a href="http://www.w3.org/2000/xp/Group/" shape="rect">http://www.w3.org/2000/xp/Group/</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_400" id="XKMS_2_0_Paragraph_400" class="markParagraph" shape="rect">[400]</a><b>[<a id="WSDL" name="WSDL" shape="rect">WSDL</a>]</b> R. Chinnici, M. Gudgin, J.-J. Moreau, J. Schlimmer, S. Weerawarana, <i>Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language</i>, W3C Working Draft, 3 August, 2004, latest draft at <a href="http://www.w3.org/TR/wsdl20/" shape="rect"> http://www.w3.org/TR/wsdl20</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_401" id="XKMS_2_0_Paragraph_401" class="markParagraph" shape="rect">[401]</a><b><a name="x509" id="x509" shape="rect">[X509]</a>&#xA0;</b>ITU-T Recommendation X.509 (1997 E):
Information Technology - <i>Open Systems Interconnection - The Directory:
Authentication Framework</i>, June 1997.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_402" id="XKMS_2_0_Paragraph_402" class="markParagraph" shape="rect">[402]</a><b>[<a id="ref-XML" name="ref-XML" shape="rect">XML</a>]</b> T. Bray, E. Maler, J. Paoli, C. M.
Sperberg-McQueen. <i>Extensible Markup Language (XML) 1.0 (Second
Edition).</i> W3C Recommendation.&#xA0; October 2000. <a href="http://www.w3.org/TR/2000/REC-xml-20001006" shape="rect">http://www.w3.org/TR/2000/REC-xml-20001006</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_403" id="XKMS_2_0_Paragraph_403" class="markParagraph" shape="rect">[403]</a><b>[<a id="XML-SIG" name="XML-SIG" shape="rect">XML-SIG</a>]</b>  D. Eastlake, J. R., D. Solo, M. Bartel,
J. Boyer , B. Fox , E. Simon. <i>XML-Signature Syntax and Processing</i>, W3C
Recommendation, 12 February 2002. <a href="http://www.w3.org/TR/xmldsig-core/" shape="rect">http://www.w3.org/TR/xmldsig-core/</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_404" id="XKMS_2_0_Paragraph_404" class="markParagraph" shape="rect">[404]</a><b>[<a id="XML-SIG-XSD" name="XML-SIG-XSD" shape="rect">XML-SIG-XSD</a>]</b> XML Signature Schema available from <a href="http://www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd" shape="rect">http://www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_405" id="XKMS_2_0_Paragraph_405" class="markParagraph" shape="rect">[405]</a><b>[<a id="XML-Enc" name="XML-Enc" shape="rect">XML-Enc</a>]</b> D. Eastlake, J. Reagle, T.
Imamura, B. Dillaway, E. Simon, <i>XML Encryption Syntax and
Processing</i>, W3C Recommendation, 10 December 2002, <a href="http://www.w3.org/TR/xmlenc-core/" shape="rect">http://www.w3.org/TR/xmlenc-core/</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_406" id="XKMS_2_0_Paragraph_406" class="markParagraph" shape="rect">[406]</a><b>[<a id="ref-XML-NS" name="ref-XML-NS" shape="rect">XML-NS</a>]</b> T. Bray, D. Hollander, A. Layman.
<i>Namespaces in XML. W3C Recommendation.</i> January 1999. <a href="http://www.w3.org/TR/1999/REC-xml-names-19990114/" shape="rect">http://www.w3.org/TR/1999/REC-xml-names-19990114</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_407" id="XKMS_2_0_Paragraph_407" class="markParagraph" shape="rect">[407]</a><b>[<a id="XML-Schema1" name="XML-Schema1" shape="rect">XML-Schema1</a>]</b> H. S. Thompson, D. Beech, M. Maloney,
N. Mendelsohn. <i>XML Schema Part 1: Structures Second Edition</i>W3C Recommendation 28 October 2004.
2001. <a href="http://www.w3.org/TR/xmlschema-1/" shape="rect">http://www.w3.org/TR/xmlschema-1/</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_408" id="XKMS_2_0_Paragraph_408" class="markParagraph" shape="rect">[408]</a><b>[<a id="XML-Schema2" name="XML-Schema2" shape="rect">XML-Schema2</a>]</b> P. V. Biron, A. Malhotra, <i>XML
Schema Part 2: Datatypes Second Edition</i>; W3C Recommendation 28 October 2004. <a href="http://www.w3.org/TR/xmlschema-2/" shape="rect">http://www.w3.org/TR/xmlschema-2/</a>.</p>

<p class="Ref"><a name="XKMS_2_0_Paragraph_409" id="XKMS_2_0_Paragraph_409" class="markParagraph" shape="rect">[409]</a><b>[<a id="XAdES" name="XAdES" shape="rect">XAdES</a>]</b>
J.C. Cruellas, G. Karlinger, K. Sankar <i>XML Advanced Electronic
Signatures</i>, W3C Note 20 February 2003. <a href=" http://www.w3.org/TR/XAdES/" shape="rect">http://www.w3.org/TR/XAdES/</a>.</p>

<h1 class="appendix"><a name="XKMS_2_0_Section_Appendix_E" id="XKMS_2_0_Section_Appendix_E" shape="rect">Appendix E</a> <a name="Acknowledgments" id="Acknowledgments" shape="rect">Acknowledgments (Non-Normative)</a></h1>

<p><a name="XKMS_2_0_Paragraph_410" id="XKMS_2_0_Paragraph_410" class="markParagraph" 
shape="rect">[410]</a>This specification is the work of the W3C XML Key Management
Working Group.  The contributions of the following Working Group
members to this specification are gratefully acknowledged in
accordance with the <a
href="http://www.w3.org/2001/XKMS/Contributor.html"
shape="rect">contributor policies</a> and the active <a
href="http://www.w3.org/2001/XKMS/Participants.html" shape="rect">WG
roster</a>.</p>

<p><a name="XKMS_2_0_Paragraph_411" id="XKMS_2_0_Paragraph_411" class="markParagraph" 
shape="rect">[411]</a>Participants in the Working Group are (at the time of writing, and
 by alphabetical order): Guillermo Alvaro Rey (Trinity College
 Dublin), Stephen Farrell (Trinity College Dublin, Co-Chair),
 Jos&eacute; Kahan (W3C, staff contact), Berin Lautenbach (Apache
 Software Foundation), Tommy Lindberg (Markup Security), Roland
 Lockhart (Entrust, Inc.), Vamsi Motukuru (Oracle Corp.), Shivaram
 Mysore (Co-Chair; Editor since 13 Apr 2004), Rich Salz (DataPower
 Technology, Inc.), Yunhao Zhang (SQLData Systems).</p>

<p><a name="XKMS_2_0_Paragraph_412" id="XKMS_2_0_Paragraph_412" class="markParagraph" 
shape="rect">[412]</a>Previous participants
 were (by alphabetical order): Daniel Ash (Identrus), 
Blair Dillaway (Microsoft), Donald 
Eastlake 3rd (Motorola), Yassir Elley (Sun Microsystems), Jeremy Epstein (webMethods), 
Slava Galperin (Sun Microsystems), Phillip Hallam-Baker (VeriSign Inc, Editor until 13 Apr 2004),
Loren Hart (VeriSign Inc.), Mack Hicks (Bank of America), Merlin Hughes (Baltimore), 
Frederick Hirsch (Nokia Mobile Phones), Mike Just (Treasury Board of Canada Secretariat),
Brian LaMacchia (Microsoft), Pradeep Lamsal,
Joseph Reagle (W3C, previous staff contact), Dave Remy (GeoTrust, Inc.), Peter 
Rostin (RSA Security Inc.), Ed Simon (XMLsec Inc.)</p>


<p><a name="XKMS_2_0_Paragraph_413" id="XKMS_2_0_Paragraph_413" class="markParagraph" 
shape="rect">[413]</a>The authors also acknowledge 
the extensive assistance provided in
the design stage of this specification by David Solo (CitiGroup) and
Barbara Fox (Microsoft), and the contributions of (by alphabetical
order) Dr. Paul Boisen (NSA), Alex Deacon, Dan Guinan, Marc Hayes,
Jeremy Epstein (webMethods), Andrew Layman (Microsoft), Mingliang Pei
(VeriSign).</p>

<p><a name="XKMS_2_0_Paragraph_414" id="XKMS_2_0_Paragraph_414" class="markParagraph" 
shape="rect">[414]</a>The people who have contributed to discussions 
on <a href="mailto:www-xkms@w3.org">www-xkms@w3.org</a> are also gratefully acknowledged.</p>

<h1 class="appendix"><a name="XKMS_2_0_Section_Appendix_F" id="XKMS_2_0_Section_Appendix_F" shape="rect">Appendix F Changes (Non-Normative)</a></h1>

<p>This appendix documents changes (other than very minor editorial changes)
from the <a href="http://www.w3.org/TR/2005/PR-xkms2-20050502/">Proposed Recommendation of 
2 May 2005</a> that were made to accommodate the <a href="http://www.w3.org/2001/XKMS/Drafts/pr-issues/issues.html">comments</a>. Each entry contains:</p>
<ul>
  <li>a change number</li>
  <li>a brief description and, where appropriate, what has been done about
  it</li>
  <li>a link to the message causing the change (if the message is public)</li>
</ul>

<h2><a name="XKMS_2_0_Section_Appendix_F_1" id="XKMS_2_0_Section_Appendix_F_1">Changes in the XKMS Schema between PR and Recommendation</a></h2>
<p>None.</p>

<h2><a name="XKMS_2_0_Section_Appendix_F_2" id="XKMS_2_0_Section_Appendix_F_2">Changes in the XKMS Specification between PR and Recommendation</a></h2>
    <ol>

      <li>Correction. Removed a definition of Web Service in Section 1.2  as it wass not used in the document and was not compatible with current usage. (<a href="http://www.w3.org/2001/XKMS/Drafts/pr-issues/issues.html#337-phb">337-phb</a>)</li>

      <li>Correction. The UseKeyWith with application "urn:ietf:rdf:2459" examples in pp. 246 and 252 was not properly escaped. (<a href="http://www.w3.org/2001/XKMS/Drafts/pr-issues/issues.html#342-ml">342-ml</a>)</li>

     <li>Correction. Made pp. 102 and 103 clearer by adding more RFC 2119 terminology,
     substituting the term "strings" by "URI" and specifying which XKMS elements include
      &lt;RespondWith&gt;. (<a
href="http://www.w3.org/2001/XKMS/Drafts/pr-issues/issues.html#344-ml">344-ml</a>)</li>

     <li>Correction. p. 218 ended with: "The 
&lt;UnverifiedKeyBinding&gt; returned are specified by the Respond
element in the request.", but it should say "by the RespondWith
element in the request".  (<a
href="http://www.w3.org/2001/XKMS/Drafts/pr-issues/issues.html#347-kj">347-kj</a>)</li>

    </ol>


<p></p>
</body>
</html>