discontinued / server · Files

index.html 167 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 
<?xml version="1.0" encoding="iso-8859-1"?>
<!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=iso-8859-1" />
  <title>XML Key Management Specification (XKMS 2.0)</title>
  <style type="text/css">
<!--
/*<![CDATA[*/
P.Code {
FONT-SIZE: 10pt; BACKGROUND: #ffffa7; MARGIN: 0in 0.5in 0pt; FONT-FAMILY: Courier
}
P.Example {
FONT-SIZE: 10pt; BACKGROUND: #d2e9ff; MARGIN: 0in 0.5in 0pt; FONT-FAMILY: Courier
}

/*]]>*/
-->

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

<body xml:lang="EN-US" lang="EN-US" vlink="purple" link="blue">

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

<h1>XML Key Management Specification (XKMS 2.0)</h1>

<h2>W3C Working Draft 18 March 2002</h2>
<dl>
  <dt>This version:</dt>
    <dd><a
      href="http://www.w3.org/TR/2002/WD-xkms2-20020318/">http://www.w3.org/TR/2002/WD-xkms2-20020318/</a> </dd>
  <dt>Latest version:</dt>
    <dd><a
    href="http://www.w3.org/TR/xkms2/">http://www.w3.org/TR/xkms2/</a></dd>
  <dt>Previous version:</dt>
    <dd>n/a</dd>
  <dt>Editor:</dt>
    <dd><a href="mailto:pbaker@verisign.com">Phillip Hallam-Baker</a>
    VeriSign</dd>
  <dt>Contributors:</dt>
    <dd>See the WG <a
      href="http://www.w3.org/2001/XKMS/Participants.html">participants</a>
      list.</dd>
</dl>

<p class="copyright"><a
href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612#Copyright">Copyright</a>
©2002 <a href="http://www.w3.org/"><abbr
title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a
href="http://www.lcs.mit.edu/"><abbr
title="Massachusetts Institute of Technology">MIT</abbr></a>, <a
href="http://www.inria.fr/"><abbr xml:lang="fr" lang="fr"
title="Institut National de Recherche en Informatique et Automatique">INRIA</abbr></a>,
<a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a
href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612#Legal_Disclaimer">liability</a>,
<a
href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612#W3C_Trademarks">trademark</a>,
<a
href="http://www.w3.org/Consortium/Legal/copyright-documents-19990405">document
use</a> and <a
href="http://www.w3.org/Consortium/Legal/copyright-software-19980720">software
licensing</a> rules apply.</p>
<hr title="Separator from Header" />
</div>

<div>
<h2><a id="abstract" name="abstract">Abstract</a></h2>

<p>This document specifies protocols for distributing and registering public
keys, suitable for use in conjunction with the proposed standard for XML
Signature [XML-SIG] developed by the World Wide Web Consortium (W3C) and the
Internet Engineering Task Force (IETF) and an anticipated companion standard
for XML encryption.  <a href="http://www.w3.org/2001/XKMS/Drafts/XKMS/">The
XML Key Management Specification (XKMS)</a> comprises two parts -- the XML
Key Information Service Specification (X-KISS) and the XML Key Registration
Service Specification (X-KRSS).</p>

<h2><a id="status" name="status">Status of this document</a></h2>

<p>This is the first draft of the "XML Key Management Specification (XKMS)"
specification from the <a href="http://www.w3.org/2001/XKMS/Drafts/">XML Key
Management Working Group</a> (<a
href="http://www.w3.org/2001/XKMS/Activity.html">Activity Statement</a>).</p>

<p>This specification contains points which are still under discussion, do
not yet satisfy the XKMS Requirements, or are not well specified.</p>

<p>The Working Group will try to <a
href="http://www.w3.org/1999/10/nsuri">use a new namespace</a> when changes
in its syntax or processing are substantive. However, this namespace might be
reused (prior to reaching Candidate Recommendation) by subsequent drafts in
such a way as to cause instances using the namespace to become invalid or to
change in meaning or affect the operation of existing software. Requests for
a more stringent level of namespace stability should be made to the Working
Group.</p>

<p>Publication of this document does not imply endorsement by the W3C
membership. This is a draft document and may be updated, replaced or
obsoleted by other documents at any time. It is inappropriate to cite a W3C
Working Draft as anything other than a "work in progress." A list of current
W3C working drafts can be found at <a
href="http://www.w3.org/TR/">http://www.w3.org/TR/</a>.</p>

<p>Please send comments to the editor (&lt;<a
href="mailto:pbaker@verisign.com">pbaker@verisign.com</a>&gt;) and cc: the
working group mailing list <a
href="mailto:www-xkms@w3c.org">www-xkms@w3c.org</a> (publicly <a
href="http://lists.w3.org/Archives/Public/www-xkms/">archived</a>)</p>

<p>Patent disclosures relevant to this specification may be found on the
Working Group's <a href="http://www.w3.org/2001/XKMS/Disclosures.html">patent
disclosure page</a> in conformance with W3C policy.</p>
<hr title="Separator from Header" />
</div>

<h2>Table Of Contents</h2>

<p>To be generated</p>

<h2>Table of Figures</h2>

<p>To be generated</p>

<h2>Executive Summary</h2>

<p>This document specifies protocols for distributing and registering public
keys, suitable for use in conjunction with the proposed standard for XML
Signature [XML-SIG] developed by the World Wide Web Consortium (W3C) and the
Internet Engineering Task Force (IETF) and an anticipated companion standard
for XML encryption.  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>The X-KISS specification defines a protocol for a <em>Trust service</em>
that resolves public key information contained in XML-SIG elements. The
X-KISS protocol allows a client of such a service to delegate part or all of
the tasks required to process <span
style="FONT-FAMILY: 'Courier New'">&lt;ds:KeyInfo&gt;</span> elements. A key
objective of the protocol design is to minimize the complexity of application
implementations by allowing them to become clients and thereby to be shielded
from the complexity and syntax of the underlying PKI used to establish trust
relationships. The underlying PKI may be based upon a different specification
such as X.509/PKIX, SPKI or PGP.</p>

<p>The X-KRSS specification defines a protocol for a web service that accepts
registration of public key information. Once registered, the public key may
be used in conjunction with other web services including X-KISS.</p>

<p>Both protocols are defined in terms of structures expressed in the XML
Schema Language, protocols employing the Simple Object Access Protocol (SOAP)
v1.1 [SOAP] and relationships among messages defined by the Web Services
Definition Language v1.0 [WSDL]. Expression of XKMS in other compatible
object encoding schemes is also possible.</p>

<h1 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Introduction</h1>

<p>This document specifies protocols for distributing and registering public
keys, suitable for use in conjunction with the proposed standard for XML
Signatures [XML-SIG] developed by the World Wide Web Consortium (W3C) and the
Internet Engineering Task Force (IETF) and an anticipated companion standard
for XML encryption.  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>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>This document comprises the following service specifications:</p>
<ul style="MARGIN-TOP: 0in" type="disc">
  <li>XML Key Information Service Specification:  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
    public key.  Its functions include the location of required public keys
    and describing the binding of such keys to identification
  information.</li>
  <li>XML Key Registration Service Specification:  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 higher level trust assertion service
    such as XML Trust Assertion Service Specification [XTASS].</li>
</ul>

<h3><a id="sec-Editorial" name="sec-Editorial">Editorial</a> and Conformance
Conventions</h3>

<p>This specification uses XML Schemas [<a
href="#ref-XML-schema">XML-schema</a>] to describe the content model.</p>

<p>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="http://www.ietf.org/rfc/rfc2119.txt">RFC2119</a> [<a
href="#ref-KEYWORDS">KEYWORDS</a>]:</p>

<blockquote>
  <p>"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>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">XML-NS</a>] is
described as "REQUIRED."</p>

<h3><a id="sec-Design" name="sec-Design">Design</a> Philosophy</h3>

<p>Design criteria include:</p>
<ul style="MARGIN-TOP: 0in" type="disc">
  <li>Compatibility with the XML Signature Specification (currently a
    standards proposal to the W3C and IETF) and with an anticipated
    specification on XML Encryption. However, its use is not restricted to
    these grammars.</li>
  <li>Implementation should be as simple as possible using standard XML tools
    while remaining consistent with the entirety of relevant specifications;
    the only cryptographic functions required by an application are those
    needed to support XML Signature or Encryption;</li>
  <li>Implementation should not require ASN.1 tools;</li>
  <li>Management of status information (e.g. "revocation") is transparent to
    a public-key using application in an online environment;</li>
  <li>Minimize client code and configuration complexity through use of
    standard protocols and message grammars and also by delegating tasks that
    may require complex configuration to web services.</li>
</ul>

<p>To meet these design criteria, the specifications in this family are
layered, separating the protocol semantics from the implementation syntax.</p>

<p>The message syntax presented in this document is based on XML and is
designed to allow use of the Simple Object Access Protocol (SOAP) and the Web
Service Definition Language (WSDL) specifications. From these, it is possible
to generate APIs in common programming languages such as the C family of
programming languages. </p>

<p>It is also possible to express the messages in syntax other than XML, over
protocols other than SOAP and through a definition language other than WSDL,
though such expression is outside the scope of this specification except to
note that SOAP and WSDL are proposals currently or potentially considered by
the World Wide Web Consortium XML Protocol Activity. If XML and SOAP are not
adopted by this Activity, we anticipate that the protocol would be
expressible in any specification recommended by the Activity.</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Definition of Terms</h2>

<p>The following terms are used within this document with the particular
meaning indicated below:</p>

<blockquote>
  <p class="Ref"><strong>Service<br />
     </strong> 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"><strong>Web service<br />
     </strong> A service that is accessible by means of messages sent using
  standard web protocols, notations and naming conventions</p>

  <p class="Ref"><strong>Client<br />
     </strong> An application that makes requests of a service.  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>
</blockquote>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Namepaces</h2>

<p style="MARGIN: 5pt 0in">For clarity, some examples of XML are not complete
documents and namespace declarations may be omitted from XML fragments. In
this document, certain namespace prefixes represent certain namespaces.</p>

<p style="MARGIN: 5pt 0in">All XMKMS protocol elements are defined using XML
schema [XML-Schema1][XML-Schema2]. For clarity unqualified elements in schema
definitions are in the XML schema namespace:</p>

<p style="MARGIN: 5pt 0in">      xmlns="<code><span
style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier New'"><a
href="http://www.w3.org/2000/10/XMLSchema">http://www.w3.org/2000/10/XMLSchema</a></span></code>"</p>

<p style="MARGIN: 5pt 0in">References to XML Key Management Specification
schema defined herein use the prefix "xkms" and are in the namespace:</p>

<p style="MARGIN: 5pt 0in 5pt 0.25in">xmlns:xkms="<span
style="FONT-SIZE: 10pt; FONT-FAMILY: Courier New"><a
href="http://www.w3.org/2002/03/xkms">http://www.w3.org/2002/03/xkms</a></span>"</p>

<p style="MARGIN: 5pt 0in">This namespace is also used for unqualified
elements in message protocol examples.</p>

<p style="MARGIN: 5pt 0in">The XKMS schema specification uses the elements
already defined in the XML Signature namespace.   The "XML Signature
namespace" is represented by the prefix <span class="ID"><span
style="FONT-FAMILY: Courier">ds</span></span> and is declared as:</p>

<p style="MARGIN: 5pt 0in; TEXT-INDENT: 0.25in">xmlns:ds="<span
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"><a
href="http://www.w3.org/2000/09/xmldsig#">http://www.w3.org/2000/09/xmldsig#</a></span>"</p>

<p style="MARGIN: 5pt 0in">The "XML Signature schema" is defined in
[XML-SIG-XSD] and the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:KeyInfo&gt;</span></span> element (and
all of its contents) are defined in [XML-SIG §4.4].</p>

<blockquote>
  <p class="Code" style="MARGIN: 5pt 0in">&lt;?xml version="1.0"?&gt;<br />
  &lt;schema targetNamespace="http://www.w3.org/2002/03/xkms"<br />
      xmlns="http://www.w3.org/2001/XMLSchema" <br />
      xmlns:ds="http://www.w3.org/2000/09/xmldsig#"<br />
      xmlns:xkms="http://www.w3.org/2002/03/xkms"    <br />
      elementFormDefault="qualified"
  attributeFormDefault="unqualified"&gt;<br />
      &lt;import namespace="http://www.w3.org/2000/09/xmldsig#"<br />
           schemaLocation="xmldsig-core-schema.xsd"/&gt;</p>
</blockquote>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Key Information Service
Specification Overview (Non-Normative)</h2>

<p>X-KISS allows a client to delegate part or all of the tasks required to
process XML Signature <span
style="FONT-FAMILY: 'Courier New'">&lt;ds:KeyInfo&gt;</span> elements to a
<em>Trust service</em>. A key objective of the protocol design is to minimize
the complexity of applications using XML Signature. By becoming a client of
the trust 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>By design, the XML Signature Specification 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
style="FONT-FAMILY: 'Courier New'">&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
style="FONT-FAMILY: Courier">&lt;ds:KeyInfo&gt;</span> information may be
found.</p>

<p>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 style="MARGIN-TOP: 0in" 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>In the case of an encryption operation:</p>
<ul style="MARGIN-TOP: 0in" type="disc">
  <li>The client may not know the public key of the recipient.</li>
</ul>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Key Registration Service
Specification Overview (Non-Normative)</h2>

<p>X-KRSS describes a protocol for registration 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>The key pair to which the information is bound may be generated in advance
by the client or, to support key recovery, may be generated on request by the
service. The Registration protocol may also be used for subsequent recovery
of a private key.</p>

<p>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>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-Helleman and Elliptic Curve variants.</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Tiered Service Model</h2>

<p>Different applications require different levels of PKI service. To support
this need a tiered implementation model is defined in which applications may
select the precise level of processing that meets their requirements.</p>

<p style="MARGIN-LEFT: 81pt; TEXT-INDENT: -63pt"><strong>Tier 0</strong>    
Processing of the <span
style="FONT-FAMILY: 'Courier New'">&lt;ds:RetrievalMethod&gt;</span> element
of the <span style="FONT-FAMILY: 'Courier New'">&lt;ds:KeyInfo&gt;</span>
element is by the application.  Processing is as defined by the XML Signature
specification [XML-SIG §4.4.3] and without assistance of a trust service.</p>

<p style="MARGIN-LEFT: 81pt; TEXT-INDENT: -63pt"><strong>Tier 1</strong>    
Processing of the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:KeyInfo&gt;</span></span> element by the
application is delegated to a service. The service returns a <span
style="FONT-FAMILY: 'Courier New'">&lt;ds:KeyInfo&gt;</span> element that
describes a public key meeting the criteria specified by the client
application. Validation of the <span
style="FONT-FAMILY: 'Courier New'">&lt;ds:KeyInfo&gt;</span> is performed by
the client.</p>

<p style="MARGIN-LEFT: 81pt; TEXT-INDENT: -63pt"><strong>Tier 2</strong>    
Validation Service<br />
As in tier 1, but in addition, the service reports further information
concerning the data specified in a <span
style="FONT-FAMILY: 'Courier New'">&lt;ds:KeyInfo&gt;</span> block.</p>

<p>In each case, the trust service shields the client application from the
complexities of the underlying PKI such as:</p>
<ul style="MARGIN-TOP: 0in" type="disc">
  <li>Handling of complex syntax and semantics (e.g. X.509v3).</li>
  <li>Retrieval of information from directory and data repository
    infrastructure.</li>
  <li>Revocation status verification.</li>
  <li>Construction and processing of trust chains.</li>
</ul>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Structure of this document</h2>

<p>The remainder of this document describes the XML Key Information Service
Specification and XML Key Registration Service Specification.</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><strong>Section
2</strong>: X-KISS Protocol Overview.<br />
The functional behavior of the X-KISS protocol is described.</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><strong>Section
3</strong>: X-KISS Message Set.<br />
The semantics of the X-KISS protocol messages are defined.</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><strong>Section
4</strong>: X-KRSS Protocol Overview.<br />
The functional behavior of the X-KRSS protocol is described.</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><strong>Section
5</strong>: X-KRSS Message Set.<br />
The semantics of the X-KRSS protocol messages is defined.</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><strong>Section
6</strong>: Cryptographic Algorithm support<br />
Data formats to support use of the cryptographic algorithms RSA and DSA are
defined.</p>

<h1 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Key Information Service
Protocol Overview</h1>

<p>In the XML Signature Specification, a signer may optionally include
information about his public signing key ("<span
style="FONT-FAMILY: Courier">&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 key to select.</p>

<p>Another important property of <span
style="FONT-FAMILY: Courier">&lt;ds:KeyInfo&gt;</span> is that it may or may
not be cryptographically bound to the signature itself.  This allows the
<span style="FONT-FAMILY: Courier">&lt;ds:KeyInfo&gt;</span> to be
substituted or supplemented without "breaking" the digital signature.</p>

<p>For example Alice signs a document and sends it to Bob with a <span
style="FONT-FAMILY: Courier">&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 style="FONT-FAMILY: Courier">&lt;ds:KeyInfo&gt;</span> element when
he passes the document on to Carol (see Figure 1below).</p>

<p class="Caption" align="center"><img height="372"
alt="Substitution of the &lt;ds:KeyInfo&gt; element as a message is passed amongst processors."
src="./image002.gif" width="420" /></p>

<p class="Caption" align="center"><a id="Figure1" name="Figure1">Figure 1:
Substitution of the <span
style="FONT-FAMILY: Courier">&lt;ds:KeyInfo&gt;</span> element as a message
is passed amongst processors</a></p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Tier 0:
&lt;ds:RetrievalMethod&gt; Processing</h2>

<p>A <span style="FONT-FAMILY: Courier">&lt;ds:KeyInfo&gt;</span> element may
include a <em>&lt;ds:RetrievalMethod&gt;</em> element which is a means to
convey information available from a remote location. The <span
class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:RetrievalMethod</span></span>&gt; element
is a feature of and is defined by the XML Signature Specification. Since it
is the most basic means of resolving a <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:KeyInfo&gt;</span></span> element it is
described here as the 'Tier 0' Key Information service.</p>

<p>For example, the signer of a document may wish to refer verifiers to a
chain of X.509 certificates without having to attach them. <span
class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:RetrievalMethod&gt;</span></span>
consists of a location which in this case, would refer to a location on the
web from which the certificate chain may be retrieved, a method, and a
type. </p>

<p>The XML Signature Specification defines the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> <span
class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:RetrievalMethod&gt;</span></span> as
follows:</p>

<p style="MARGIN: 6pt 0.25in"><em>A</em> <code><em><span
style="FONT-FAMILY: 'Courier New'">RetrievalMethod</span></em></code>
<em>element within</em> <code><em><span
style="FONT-FAMILY: 'Courier New'">Keyinfo</span></em></code> <em>is used to
convey a reference to</em> <code><em><span
style="FONT-FAMILY: 'Courier New'">Keyinfo</span></em></code> <em>information
that is stored at another location. For example, several signatures in a
document might use a key verified by an X.509v3 certificate chain appearing
once in the document or remotely outside the document; each signature's</em>
<code><em><span style="FONT-FAMILY: 'Courier New'">Keyinfo</span></em></code>
<em>can reference this chain using a single</em> <code><em><span
style="FONT-FAMILY: 'Courier New'">ds:RetrievalMethod</span></em></code>
<em>element instead of including the entire chain with a sequence of</em>
<code><em><span
style="FONT-FAMILY: 'Courier New'">X509Certificate</span></em></code>
<em>elements.</em></p>

<p style="MARGIN: 6pt 0.25in"><span class="ID"><em><span
style="FONT-FAMILY: Courier">RetrievalMethod</span></em></span><em><span
style="COLOR: black">uses the same syntax and dereferencing behavior
as</span> Reference's <span style="COLOR: black">URI (section 4.3.3.1 [of
[XML-SIG]]) and <u>The Reference Processing Model</u> (section 4.3.3.2 [of
[XML-SIG]]) except that there is no</span></em> <span class="ID"><em><span
style="FONT-FAMILY: Courier">DigestMethod</span></em></span><em><span
style="COLOR: black">or</span></em> <span class="ID"><em><span
style="FONT-FAMILY: Courier">DigestValue</span></em></span><em><span
style="COLOR: black">child elements and presence of the URI is mandatory.
Note, if the result of dereferencing and transforming the specified URI  is a
node set, then it may need to be to be canonicalized. All of the</span></em>
<span class="ID"><em><span
style="FONT-FAMILY: Courier">KeyInfo</span></em></span><span
class="ID"><em>types defined by this specification</em></span><em><span
style="COLOR: black">(section 4.4 [of [XML-SIG]]) represent octets,
consequently the Signature application is expected to attempt to canonicalize
the nodeset via the <u>The Reference Processing Model</u> (section 4.3.3.2
[of [XML-SIG]])</span></em></p>

<p>Schema Definition:</p>
<pre class="Example">&lt;element name="RetrievalMethod"&gt;
   &lt;complexType&gt;
      &lt;sequence&gt;
         &lt;element ref="ds:Transforms" minOccurs="0"/&gt;
      &lt;/sequence&gt;
      &lt;attribute name="URI" type="uriReference"/&gt;
      &lt;attribute name="Type" type="uriReference" use="optional"/&gt;
   &lt;/complexType&gt;
&lt;/element&gt;
</pre>

<p>In the following example, the signer indicates a web-resident directory
service (www.PkeyDir.test) where they have published information about their
public key. </p>

<p class="Example">&lt;ds:KeyInfo&gt;<br />
   &lt;ds:RetrievalMethod URI="http://www.PKeyDir.test/CheckKey"</p>

<p class="Example">           
Type="http://www.w3.org/2000/09/xmldsig#X509Certificate"/&gt;<br />
&lt;/ds:KeyInfo&gt;</p>

<p class="BodyTextKeep"
style="PAGE-BREAK-AFTER: auto; LINE-HEIGHT: normal">The relying party
retrieves the additional Key Information by resolving the specified URL
(Figure 2).</p>

<p style="TEXT-ALIGN: center" align="center"><img height="216"
alt="Tier 0 Protocol allows a &lt;ds:Keyinfo&gt; element to reference external data"
src="./image004.gif" width="480" border="0" /></p>

<p class="Caption" align="center">Figure 2: Tier 0 Protocol allows a <span
class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> element to
reference external data</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Tier 1 <span class="ID"><span
style="FONT-FAMILY: Courier">Locate</span></span> Service</h2>

<p>The Tier 1 <span class="ID"><span
style="FONT-FAMILY: Courier">Locate</span></span> service resolves a <span
class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></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"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> element.</p>

<p>The Trust service MAY resolve the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> element using
local data or MAY relay request to other servers. For example the Trust
service might resolve a <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:RetrievalMethod&gt;</span></span> element
(Figure 3) or act as a gateway to an underlying PKI based on a non-XML
syntax.</p>

<p style="TEXT-ALIGN: center" align="center"><img height="244"
alt="Diagram shows protocol exchange between a client, a trust service and a remote server (Server A). "
src="./image006.gif" width="576" border="0" /></p>

<p class="Caption" align="center">Figure 3: Tier 1 Protocol Provides Name
Resolution Service</p>

<p>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.</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Example: Document
Signature</h3>

<p>The client receives a signed XML document. The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> element
specifies a <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:RetrievalMethod&gt;</span></span> for an
X.509 certificate that contains the public key. The client sends the <span
class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> element to the
location service requesting that the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyName&gt;</span></span> and <span
class="ID"><span style="FONT-FAMILY: Courier">&lt;KeyValue&gt;</span></span>
elements be returned.</p>

<p>Request:</p>

<p class="Example">&lt;Locate&gt;</p>

<p class="Example">   &lt;Query&gt;</p>

<p class="Example">      &lt;ds:KeyInfo&gt;</p>

<p class="Example">         &lt;ds:RetrievalMethod</p>

<p class="Example">          
URI="http://www.PKeyDir.test/Certificates/01293122"</p>

<p class="Example">           Type="<a
href="http://www.w3.org/2000/09/xmldsig#SPKIData"><span
style="COLOR: windowtext; TEXT-DECORATION: none">http://www.w3.org/2000/09/xmldsig#X509Data</span></a>"/&gt;</p>

<p class="Example">      &lt;/ds:KeyInfo&gt;</p>

<p class="Example">   &lt;/Query&gt;</p>

<p class="Example">   &lt;Respond&gt;</p>

<p class="Example">      &lt;string&gt;KeyName&lt;/string&gt;</p>

<p class="Example">      &lt;string&gt;KeyValue&lt;/string&gt;</p>

<p class="Example">   &lt;/Respond&gt;</p>

<p class="Example">&lt;/Locate&gt;</p>

<p>The location service resolves the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:RetrievalMethod&gt;</span></span>,
obtaining an X.509v3 certificate. The certificate is parsed to obtain the
public key value that is returned to the client.</p>

<p>The location service DOES NOT report the revocation status or the
trustworthiness of the certificate. The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyName&gt;</span></span> returned is
obtained from the certificate.</p>

<p>Response:</p>

<p class="Example">&lt;LocateResult&gt;</p>

<p class="Example">   &lt;Result&gt;Success&lt;/Result&gt;</p>

<p class="Example">   &lt;Answer&gt;</p>

<p class="Example">      &lt;ds:KeyInfo&gt;</p>

<p class="Example">         &lt;ds:KeyName&gt;O=XMLTrustCernter.org
OU="Crypto"</p>

<p class="Example">                        CN="Alice"&lt;/ds:KeyName&gt;</p>

<p class="Example">         &lt;ds:KeyValue&gt;...&lt;/ds:KeyValue&gt;</p>

<p class="Example">      &lt;/ds:KeyInfo&gt;</p>

<p class="Example">   &lt;/Answer&gt;</p>

<p class="Example">&lt;/LocateResult&gt;</p>

<p>(For readability, the contents of the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyValue&gt;</span></span>element are
omitted from the example above.  Full examples are shown in appendices. )</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Example: Data Encryption</h3>

<p>The client is attempting to send an encrypted XML document and requires
the public key encryption parameters of the recipient.</p>

<p>Request:</p>

<p class="Example">&lt;Locate&gt;</p>

<p class="Example">   &lt;Query&gt;</p>

<p class="Example">      &lt;ds:KeyInfo&gt;</p>

<p class="Example">         &lt;ds:KeyName&gt;Alice
Cryptographer&lt;/ds:KeyName&gt;</p>

<p class="Example">      &lt;/ds:KeyInfo&gt;</p>

<p class="Example">   &lt;/Query&gt;</p>

<p class="Example">   &lt;Respond&gt;</p>

<p class="Example">      &lt;string&gt;KeyName&lt;/string&gt;</p>

<p class="Example">      &lt;string&gt;KeyValue&lt;/string&gt;</p>

<p class="Example">   &lt;/Respond&gt;</p>

<p class="Example">&lt;/Locate&gt;</p>

<p>Response:</p>

<p class="Example">&lt;LocateResult&gt;</p>

<p class="Example">   &lt;Result&gt;Success&lt;/Result&gt;</p>

<p class="Example">   &lt;Answer&gt;</p>

<p class="Example">      &lt;ds:KeyInfo&gt;</p>

<p class="Example">         &lt;ds:KeyName&gt;Alice
Cryptographer&lt;/ds:KeyName&gt;</p>

<p class="Example">         &lt;ds:KeyValue&gt;...&lt;/ds:KeyValue&gt;</p>

<p class="Example">      &lt;/ds:KeyInfo&gt;</p>

<p class="Example">   &lt;/Answer&gt;</p>

<p class="Example">&lt;/LocateResult&gt;</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Tier 2: Validate Service</h2>

<p>The Tier 2 Validate Service allows all that tier one 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 trust service a prototype containing
some or all of the elements for which the status of the trust binding is
required. If the information in the prototype is incomplete, the trust
service MAY obtain additional data required from an underlying PKI Service.
Once the validity of the Key Binding has been determined the Trust service
returns the status result to the client (Figure 4).</p>

<p style="TEXT-ALIGN: center" align="center"><img height="265"
alt="Diagram shows a trust service acting as a gateway to 'PKI services'"
src="./image008.gif" width="532" border="0" /></p>

<p class="Caption" align="center"><a id="Figure-Tier2"
name="Figure-Tier2">Figure 4: Tier2 Protocol Provides Key Validation
Service</a></p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Example: Document
Signature</h3>

<p>The client of the example in section 2.2.1 has verified the document
signature. The client now needs to determine whether the binding between the
name and the public key is both trustworthy and valid.</p>

<p>Request:</p>

<p class="Example">&lt;Validate&gt;</p>

<p class="Example">   &lt;Query&gt;</p>

<p class="Example">      &lt;Status&gt;Valid&lt;/Status&gt;</p>

<p class="Example">      &lt;ds:KeyInfo&gt;</p>

<p class="Example">         &lt;ds:KeyName&gt;...&lt;/ds:KeyName&gt;</p>

<p class="Example">         &lt;ds:KeyValue&gt;...&lt;/ds:KeyValue&gt;</p>

<p class="Example">      &lt;/ds:KeyInfo&gt;</p>

<p class="Example">   &lt;/Query&gt;</p>

<p class="Example">   &lt;Respond&gt;</p>

<p class="Example">      &lt;string&gt;KeyName&lt;/string&gt;</p>

<p class="Example">      &lt;string&gt;KeyValue&lt;/string&gt;</p>

<p class="Example">   &lt;/Respond&gt;</p>

<p class="Example">&lt;/Validate&gt;</p>

<p>Response:</p>

<p class="Example">&lt;ValidateResult&gt;</p>

<p class="Example">   &lt;Result&gt;Success&lt;/Result&gt;</p>

<p class="Example">   &lt;Answer&gt;</p>

<p class="Example">      &lt;KeyBinding&gt;</p>

<p class="Example">         &lt;Status&gt;Valid&lt;/Status&gt;</p>

<p class="Example">        
&lt;KeyID&gt;http://www.xmltrustcenter.org/assert/20010120-39&lt;/KeyID&gt;</p>

<p class="Example">         &lt;ds:KeyInfo&gt;</p>

<p class="Example">            &lt;ds:KeyName&gt;...&lt;/ds:KeyName&gt;</p>

<p class="Example">            &lt;ds:KeyValue&gt;...&lt;/ds:KeyValue&gt;</p>

<p class="Example">         &lt;/ds:KeyInfo&gt;</p>

<p class="Example">         &lt;ValidityInterval&gt;</p>

<p class="Example">           
&lt;NotBefore&gt;2000-09-20T12:00:00&lt;/NotBefore&gt;</p>

<p class="Example">           
&lt;NotAfter&gt;2000-10-20T12:00:00&lt;/NotAfter&gt;</p>

<p class="Example">         &lt;/ValidityInterval&gt;</p>

<p class="Example">      &lt;/KeyBinding&gt;</p>

<p class="Example">   &lt;/Answer&gt;</p>

<p class="Example">&lt;/ValidateResult&gt;</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Validity of the Service
Response</h2>

<p>Clients SHOULD ensure that the response from the service to a Locate or
Validate operation is valid, meaning that the following criteria are met.</p>

<p style="MARGIN-LEFT: 0.25in"><strong>Authenticity</strong>: That the
response message was issued by a trusted Trust service</p>

<p style="MARGIN-LEFT: 0.25in"><strong>Integrity</strong>: That the response
message has not been modified</p>

<p style="MARGIN-LEFT: 0.25in"><strong>Correspondence</strong>: The response
from the Trust service corresponds to the request that was made to the
client.</p>

<p>The appropriate means of validating the service response is dependent on
the application. It is not necessary for the requests to be authenticated
with a digital signature if the client supports some other secure means of
communicating with the Trust service.</p>

<p>The authenticity, integrity and correspondence of the response SHOULD be
ensured using one or more of the following methods:</p>
<ul style="MARGIN-TOP: 0in" type="disc">
  <li>Authenticating the response messages using the XML Signature
    Specification.</li>
  <li>Transport layer security (e.g. SSL, TLS, WTLS)</li>
  <li>Packet layer security (e.g. IPSEC)</li>
</ul>

<p>In the case that signed response messages are employed, the means by which
the client determines that the signing key is trustworthy is outside the
scope of this specification. Possible mechanisms include:</p>
<ul style="MARGIN-TOP: 0in" type="disc">
  <li>A root key embedded in the client application</li>
  <li>A trustworthy signing key exchanged using mechanisms described in the
    Tier 3 Trust Assertion Service Specification.</li>
  <li>A signing key obtained using some other retrieval mechanism such as
    DNSSEC, PKIX or SPKI.</li>
</ul>

<h1 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Key Information Service
Message Set</h1>

<p>The protocol consists of pairs of messages, with an application sending a
request message to a trust service and the service responding with another
message. </p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Common Data Elements</h2>

<p>The content and format of messages are defined using the W3C XML Schema
specification [XML-Schema1][XML-Schema2].  All values are encoded as element
data. The XKMS specification itself uses only a restricted set of types, but
element values may potentially use any type definable within XML Schemas. 
XKMS is compatible with the object serialization format defined within SOAP
(see Appendix A ) but does not use some aspects of that format.  In
particular, sequences of elements are expressed as sequences of elements
without reference to the SOAP array encoding.</p>

<p>The following common data elements are used in the message set:</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Imported Elements</h3>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> element is
defined in the XML Signature Specification schema and that specification
governs its format and use.</p>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> element
communicates data using both attributes and elements. Arbitrary extension
elements are permitted.</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">AssertionStatus</h3>

<p>The enumerated type <span
style="FONT-FAMILY: Courier">AssertionStatus</span> is used to report the
status of an assertion such as a key binding. The following values are
defined:</p>
<dl>
  <dt>Valid</dt>
    <dd>The binding is definitively valid.</dd>
  <dt>Invalid</dt>
    <dd>The binding is definitively invalid.</dd>
  <dt>Indeterminate</dt>
    <dd>The status of the assertion cannot be determined.</dd>
</dl>

<p>The <span style="FONT-FAMILY: Courier">AssertionStatus</span> type is
defined by the following schema:</p>

<p class="Code">&lt;simpleType name="AssertionStatus"&gt;</p>

<p class="Code">    &lt;restriction base="string"&gt;</p>

<p class="Code">        &lt;enumeration value="Valid"/&gt;</p>

<p class="Code">        &lt;enumeration value="Invalid"/&gt;</p>

<p class="Code">        &lt;enumeration value="Indeterminate"/&gt;</p>

<p class="Code">    &lt;/restriction&gt;</p>

<p class="Code">&lt;/simpleType&gt;</p>

<p>The <span style="FONT-FAMILY: Courier">&lt;status&gt;</span> element of
the <span style="FONT-FAMILY: Courier">&lt;KeyBinding&gt;</span> element has
the type <span style="FONT-FAMILY: Courier">AssertionStatus</span>.</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">RequestAbstractType</h3>

<blockquote>
  <p class="Code" style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">&lt;complexType
  name="RequestAbstractType" abstract="true"&gt;<br />
      &lt;sequence&gt;<br />
          &lt;element ref="xkms:Respond" minOccurs="0"
  maxOccurs="unbounded"/&gt;<br />
      &lt;/sequence&gt;<br />
      &lt;attribute name="MajorVersion" type="integer" use="required"/&gt;<br
  />
      &lt;attribute name="MinorVersion" type="integer" use="required"/&gt;<br
  />
  &lt;/complexType&gt;</p>
</blockquote>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Respond</h3>

<p>The <span style="FONT-FAMILY: Courier">&lt;Respond&gt;</span> element in
the request specifies one or more strings included in the request that
specify data elements to be provided in the <span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span> element of the
response. Each string is a single identifier corresponding to a sub-element
of the XML Signature Specification <span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span> element [XML-SIG] or
the private key information defined in section 6.3.2. The XML Signature
elements are described here for convenience. The normative reference is the
specification [XML-SIG].</p>

<p>The Service SHOULD return a requested data element if it is available. The
Service MAY return additional data elements that were not requested. In
particular, the service MAY return data elements specified in the request
with the response.</p>

<p>Defined identifiers include:</p>

<div align="center">

<table summary="Structures and their Identifiers"
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 3.65pt; BORDER-LEFT: medium none; WIDTH: 450.1pt; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse"
cellpadding="0" width="600" border="1">
  <tbody>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.65in; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="top" width="158"><p class="BodyTextKeep"
        style="PAGE-BREAK-AFTER: auto; LINE-HEIGHT: normal"><strong>Identifier</strong></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 2.15in; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="top" width="206"><p><span class="ID"><strong><span
        style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></strong></span>
        <strong>Element</strong></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 176.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="top" width="235"><p><strong>Description</strong></p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.65in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="158"><p><span
        style="FONT-FAMILY: Courier">KeyName</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 2.15in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="206"><p><span
        style="FONT-FAMILY: Courier">&lt;ds:KeyName&gt;</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 176.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="235"><p>Key Name</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.65in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="158"><p><span
        style="FONT-FAMILY: Courier">KeyValue</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 2.15in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="206"><p><span
        style="FONT-FAMILY: Courier">&lt;ds:KeyValue&gt;</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 176.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="235"><p>Public key parameters</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.65in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="158"><p><span
        style="FONT-FAMILY: Courier">X509Cert</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 2.15in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="206"><p><span
        style="FONT-FAMILY: Courier">&lt;ds:X509Data&gt;</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 176.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="235"><p class="BodyTextKeep"
        style="PAGE-BREAK-AFTER: auto; LINE-HEIGHT: normal">X509 Certificate
        v3 that authenticates the specified key</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.65in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="158"><p><span
        style="FONT-FAMILY: Courier">X509Chain</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 2.15in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="206"><p><span
        style="FONT-FAMILY: Courier">&lt;ds:X509Data&gt;*</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 176.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="235"><p>X509 Certificate v3 chain that
        authenticates the specified key</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.65in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="158"><p><span
        style="FONT-FAMILY: Courier">X509CRL</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 2.15in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="206"><p><span
        style="FONT-FAMILY: Courier">&lt;ds:X509Data&gt;</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 176.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="235"><p>X509 Certificate Revocation List v2</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.65in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="158"><p><span
        style="FONT-FAMILY: Courier">OCSP</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 2.15in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="206"><p><span
        style="FONT-FAMILY: Courier">&lt;ds:X509Data&gt;</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 176.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="235"><p>PKIX OCSP token that validates an X509v3
        certificate that authenticates the key</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.65in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="158"><p><span
        style="FONT-FAMILY: Courier">RetrievalMethod</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 2.15in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="206"><p><span
        style="FONT-FAMILY: Courier">&lt;ds:RetrievalMethod&gt;</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 176.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="235"><p>Retrieval Method data</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.65in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="158"><p><span
        style="FONT-FAMILY: Courier">MgmtData</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 2.15in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="206"><p><span
        style="FONT-FAMILY: Courier">&lt;ds:MgmtData&gt;</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 176.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="235"><p>Management Data</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.65in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="158"><p><span
        style="FONT-FAMILY: Courier">PGP</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 2.15in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="206"><p><span
        style="FONT-FAMILY: Courier">&lt;ds:PGPData&gt;</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 176.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="235"><p>PGP key signing data</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.65in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="158"><p><span
        style="FONT-FAMILY: Courier">PGPWeb</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 2.15in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="206"><p><span
        style="FONT-FAMILY: Courier">&lt;ds:PGPData&gt;*</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 176.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="235"><p>Collection of PGP key signing data</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.65in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="158"><p><span
        style="FONT-FAMILY: Courier">SPKI</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 2.15in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="206"><p><span
        style="FONT-FAMILY: Courier">&lt;ds:SPKIData&gt;*</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 176.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="235"><p class="BodyTextKeep"
        style="PAGE-BREAK-AFTER: auto; LINE-HEIGHT: normal">SPKI key
        signing</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.65in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="158"><p><span
        style="FONT-FAMILY: Courier">Multiple</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 2.15in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="206"><p> </p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 176.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="235"><p class="BodyTextKeep"
        style="PAGE-BREAK-AFTER: auto; LINE-HEIGHT: normal">Specifies that
        the Trust Service SHOULD return multiple answers to the client if
        more than one valid answer is available.</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.65in; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="158"><p><span
        style="FONT-FAMILY: Courier">Private</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 2.15in; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="206"><p> </p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 176.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="235"><p class="BodyTextKeep"
        style="PAGE-BREAK-AFTER: auto; LINE-HEIGHT: normal">Request that the
        encrypted private key be returned in the response. [Used in the
        X-KRSS protocol]</p>
      </td>
    </tr>
  </tbody>
</table>
</div>

<p>For example, a client that has no X.509 processing capability might
perform a <span style="FONT-FAMILY: Courier">Locate</span> operation to
obtain the public key parameters and name information from a <span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span> element that specifies
only a certificate. The <span style="FONT-FAMILY: Courier">Respond</span>
element values in this case would be "<span
style="FONT-FAMILY: Courier">KeyName</span>" and "<span
style="FONT-FAMILY: Courier">KeyValue</span>".</p>

<p>The <span style="FONT-FAMILY: Courier">&lt;Respond&gt;</span> element is
defined by the following schema:</p>

<p class="Code">&lt;element name="Respond" type="string"/&gt;</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">ResultAbstractType</h3>

<blockquote>
  <p class="Code" style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">&lt;complexType
  name="ResultAbstractType" abstract="true"&gt;<br />
      &lt;sequence&gt;<br />
          &lt;element ref="xkms:Result"/&gt;<br />
      &lt;/sequence&gt;<br />
      &lt;attribute name="MajorVersion" type="integer" use="required"/&gt;<br
  />
      &lt;attribute name="MinorVersion" type="integer" use="required"/&gt;<br
  />
  &lt;/complexType&gt;</p>
</blockquote>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Element &lt;<span
class="ID">Result&gt;</span></h3>

<p>The enumerated type ResultCode is used to return result codes from each
interface. It has the following possible values:</p>
<dl>
  <dt>Success</dt>
    <dd>The operation succeeded.</dd>
  <dt>NoMatch</dt>
    <dd>No match was found for the search prototype provided.</dd>
  <dt>Incomplete</dt>
    <dd>Only part of the information requested could be provided.</dd>
  <dt>Failure</dt>
    <dd>The operation failed for unspecified reasons.</dd>
  <dt>Refused</dt>
    <dd>The operation was refused.</dd>
  <dt>Pending</dt>
    <dd>The operation was queued for future processing.</dd>
</dl>

<p>ResultCode is defined by the following schema:</p>

<p class="Code">&lt;element name="Result" type="xkms:ResultCode"/&gt;</p>

<p class="Code">&lt;simpleType name="ResultCode"&gt;<br />
    &lt;restriction base="string"&gt;<br />
        &lt;enumeration value="Success"/&gt;<br />
        &lt;enumeration value="NoMatch"/&gt;<br />
        &lt;enumeration value="NotFound"/&gt;<br />
        &lt;enumeration value="Incomplete"/&gt;<br />
        &lt;enumeration value="Failure"/&gt;<br />
        &lt;enumeration value="Refused"/&gt;<br />
        &lt;enumeration value="Pending"/&gt;<br />
    &lt;/restriction&gt;<br />
&lt;/simpleType&gt;</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Element &lt;Reason&gt;</h3>

<p>One or more strings that specify the reason(s) for a particular assertion
status.</p>

<p>If the Trust service returns the <span class="ID"><span
style="FONT-FAMILY: Courier">AssertionStatus</span></span> value <span
class="ID"><span style="FONT-FAMILY: Courier">Valid</span></span>, the <span
class="ID">&lt;Reason&gt;</span> element lists the status aspects that have
been affirmatively verified to be <span class="ID"><span
style="FONT-FAMILY: Courier">Valid</span></span>. If the service returns the
<span class="ID"><span
style="FONT-FAMILY: Courier">AssertionStatus</span></span> value <span
class="ID"><span style="FONT-FAMILY: Courier">Invalid</span></span> the
Reason element lists the aspects of status that have been determined to be
either <span class="ID"><span
style="FONT-FAMILY: Courier">Invalid</span></span> or <span class="ID"><span
style="FONT-FAMILY: Courier">Indeterminate</span></span>. If the service
returns the <span class="ID"><span
style="FONT-FAMILY: Courier">AssertionStatus</span></span> value <span
class="ID"><span style="FONT-FAMILY: Courier">Indeterminate</span></span> the
Reason element lists the aspects of status that have been determined to be
<span class="ID"><span
style="FONT-FAMILY: Courier">Indeterminate</span></span>.</p>

<p>[TBS use this in the schema!]</p>

<p>The status aspects are defined in the table below. For convenience the
equivalent X509 processing steps are given:</p>

<div align="center">

<center>

<table summary="Status and Description"
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; WIDTH: 438pt; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse"
cellspacing="0" cellpadding="0" width="584" border="1">
  <tbody>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.75in; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="top" width="168"><p><strong>Aspect</strong></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 153.9pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="top" width="205"><p><strong>Description</strong></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 158.1pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="top" width="211"><p><strong>X.509 Equivalent</strong></p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.75in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="168"><p><span class="ID"><span
        style="FONT-FAMILY: Courier">IssuerTrust</span></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 153.9pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="205"><p>The assertion issuer is considered to be
        trustworthy by the Trust service.</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 158.1pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="211"><p class="BodyTextKeep"
        style="PAGE-BREAK-AFTER: auto; LINE-HEIGHT: normal">Certificate path
        anchored by trusted root successfully constructed</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.75in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="168"><p><span class="ID"><span
        style="FONT-FAMILY: Courier">Status</span></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 153.9pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="205"><p>The Trust service has affirmatively
        verified the status of the assertion with an authoritative source</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 158.1pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="211"><p>Certificate status validated using CRL or
        OCSP</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.75in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="168"><p><span class="ID"><span
        style="FONT-FAMILY: Courier">ValidityInterval</span></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 153.9pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="205"><p>The request was made within the validity
        interval of the assertion</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 158.1pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="211"><p>The request was made at a time when the
        certificate chain was valid</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.75in; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="168"><p><span class="ID"><span
        style="FONT-FAMILY: Courier">Signature</span></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 153.9pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="205"><p>Signature on signed data provided by the
        client in the <span class="ID"><span
        style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> element
        (e.g. <span class="ID"><span
        style="FONT-FAMILY: Courier">X509Data</span></span> element) was
        successfully verified.</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 158.1pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="211"><p>Certificate Signature verified</p>
      </td>
    </tr>
  </tbody>
</table>
</center>
</div>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Locate Service</h3>

<p>The Locate service accepts as input a <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> element that
specifies a public key and returns one or more <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> elements that
relate to the same public key. The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> elements
returned are specified by the <span class="ID"><span
style="FONT-FAMILY: Courier">Respond</span></span> element in the request.</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Request Message</h3>

<p>The request message consists of the <span class="ID"><span
style="FONT-FAMILY: Courier">Locate</span></span> element defined by the
following schema:</p>

<p class="Code">&lt;element name="LocateRequest"
type="xkms:LocateRequestType"/&gt;<br />
&lt;complexType name="LocateRequestType"&gt;<br />
    &lt;complexContent&gt;<br />
        &lt;extension base="xkms:RequestAbstractType"&gt;<br />
            &lt;sequence&gt;<br />
                &lt;element ref="xkms:TransactionID" minOccurs="0"/&gt;<br />
                &lt;element ref="xkms:KeyInfoQuery"/&gt;<br />
            &lt;/sequence&gt;<br />
        &lt;/extension&gt;<br />
    &lt;/complexContent&gt;<br />
&lt;/complexType&gt;<br />
&lt;element name="TransactionID" type="string"/&gt;<br />
&lt;element name="KeyInfoQuery" type="ds:KeyInfoType"/&gt;</p>

<p>The following elements are defined:</p>

<p class="Label"><span class="ID"><strong><span
style="FONT-FAMILY: Courier">Query</span></strong></span><br />
A single complex structure containing a <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> element that
specifies the public key for which additional data is requested.</p>

<p class="Label"><span class="ID"><strong><span
style="FONT-FAMILY: Courier">Respond</span></strong></span><br />
A sequence of identifiers that specify data elements that the client requests
returned in the response.</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Response Message</h3>

<p>The Response Message consists of a <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;LocateResult&gt;</span></span> element
defined by the following schema:</p>

<p class="Code">&lt;element name="LocateResult"
type="xkms:LocateResultType"/&gt;<br />
&lt;complexType name="LocateResultType"&gt;<br />
    &lt;complexContent&gt;<br />
        &lt;extension base="xkms:ResultAbstractType"&gt;<br />
            &lt;sequence&gt;<br />
                &lt;element ref="xkms:TransactionID" minOccurs="0"/&gt;<br />
                &lt;element ref="ds:KeyInfo" minOccurs="0"
maxOccurs="unbounded"/&gt;<br />
            &lt;/sequence&gt;<br />
        &lt;/extension&gt;<br />
    &lt;/complexContent&gt;<br />
&lt;/complexType&gt;</p>

<p>The following elements are defined:</p>

<p class="Label"><span class="ID"><strong><span
style="FONT-FAMILY: Courier">Answer</span></strong></span><br />
A sequence of <span class="ID"><span
style="FONT-FAMILY: Courier">strings</span></span> that contain <span
class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> elements that
provide the information specified by the <span class="ID"><span
style="FONT-FAMILY: Courier">Respond</span></span> attribute, for the public
key identified by the <span class="ID"><span
style="FONT-FAMILY: Courier">Query</span></span> element.</p>

<p>The response message returns a <span class="ID"><span
style="FONT-FAMILY: Courier">ResultCode</span></span> depending on the
success of the <span class="ID"><span
style="FONT-FAMILY: Courier">Locate</span></span> operation as follows:</p>

<div align="center">

<table summary="Result Codes"
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse"
cellpadding="0" border="1">
  <tbody>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.15in; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="bottom" width="110"><p><span class="ID"><strong><span
        style="FONT-FAMILY: Courier">ResultCode</span></strong></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 121.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="bottom" width="162"><p><strong>Number of Elements</strong></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 210.25pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="bottom" width="280"><p><strong>Description</strong></p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.15in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="110"><p><span class="ID"><span
        style="FONT-FAMILY: Courier">Success</span></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 121.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="162"><p>At least one element</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 210.25pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="280"><p class="BodyTextKeep"
        style="PAGE-BREAK-AFTER: auto; LINE-HEIGHT: normal">The locate
        operation succeeded. All the information requested was available.</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.15in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="110"><p><span class="ID"><span
        style="FONT-FAMILY: Courier">NoMatch</span></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 121.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="162"><p>No elements</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 210.25pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="280"><p>The locate operation succeeded but returned
        no matches.</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.15in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="110"><p><span class="ID"><span
        style="FONT-FAMILY: Courier">Incomplete</span></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 121.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="162"><p>At least one element</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 210.25pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="280"><p class="BodyTextKeep"
        style="PAGE-BREAK-AFTER: auto; LINE-HEIGHT: normal">The locate
        operation succeeded. Some of the information requested was not
        available.</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.15in; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="110"><p><span class="ID"><span
        style="FONT-FAMILY: Courier">Failure</span></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 121.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="162"><p>No elements</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 210.25pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="280"><p>The locate operation failed.</p>
      </td>
    </tr>
  </tbody>
</table>
</div>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Faults</h3>

<p>TBS</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Validate Service</h2>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">Validate</span></span> service allows the client
to query the binding between a <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> element and
other data such as an identifier. The client supplies a prototype for the
<span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyBinding&gt;</span></span> assertion
requested. The prototype may specify either a <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyId&gt;</span></span> or a <span
class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> element or
both. The server returns one or more <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyBinding&gt;</span></span> assertions that
meet the criteria specified in the request.</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Element <span
style="FONT-FAMILY: Courier">&lt;KeyBinding&gt;</span></h3>

<p>The <span style="FONT-FAMILY: Courier">&lt;KeyBinding&gt;</span> element
asserts a binding between data elements that relate to a public key including
<span style="FONT-FAMILY: Courier">&lt;KeyName&gt;</span>, <span
style="FONT-FAMILY: Courier">&lt;KeyID&gt;</span>, <span
style="FONT-FAMILY: Courier">&lt;KeyValue&gt;</span> and <span
style="FONT-FAMILY: Courier">&lt;X509Data&gt;</span>. Furthermore, the
Service represents <em>to the client accessing the service and to that client
alone</em> that the binding between the data elements is <em>valid</em> under
whatever trust policy the service offers to that client.</p>

<p>The <span style="FONT-FAMILY: Courier">&lt;Query&gt;</span> and <span
style="FONT-FAMILY: Courier">&lt;Prototype&gt;</span> elements share the same
type definition as <span
style="FONT-FAMILY: Courier">&lt;KeyBinding&gt;</span> which is defined by
the following schema:</p>

<p class="Code">&lt;element name="KeyBinding"
type="xkms:KeyBindingType"/&gt;<br />
&lt;complexType name="KeyBindingType"&gt;<br />
    &lt;sequence&gt;<br />
        &lt;element ref="xkms:TransactionID" minOccurs="0"/&gt;<br />
        &lt;element ref="xkms:Status"/&gt;<br />
        &lt;element ref="xkms:KeyID" minOccurs="0"/&gt;<br />
        &lt;element ref="ds:KeyInfo" minOccurs="0"/&gt;<br />
        &lt;element ref="xkms:PassPhrase" minOccurs="0"/&gt;<br />
        &lt;element ref="xkms:ProcessInfo" minOccurs="0"/&gt;<br />
        &lt;element ref="xkms:ValidityInterval" minOccurs="0"/&gt;<br />
        &lt;element ref="xkms:KeyUsage" minOccurs="0"
maxOccurs="unbounded"/&gt;<br />
    &lt;/sequence&gt;<br />
    &lt;attribute name="Id" type="ID" use="optional"/&gt;<br />
&lt;/complexType&gt;</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Element <font
face="Courier">&lt;Status&gt;</font></h3>

<blockquote>
  <p class="Code" style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">&lt;element
  name="Status" type="xkms:AssertionStatus"/&gt;</p>
</blockquote>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Element <font
face="Courier">&lt;KeyId&gt;</font></h3>

<p>The <span style="FONT-FAMILY: Courier">&lt;KeyId&gt;</span> element
specifies a URI identifier for the key. The URI MAY be a name (URN), a
locator (URL) or anything else permitted by the URI specification. The <span
style="FONT-FAMILY: Courier">&lt;KeyId&gt;</span> element is distinct from
the <span style="FONT-FAMILY: Courier">&lt;ds:KeyName&gt;</span> element of
<span style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span> in that the
<span style="FONT-FAMILY: Courier">&lt;KeyName&gt;</span> element is not
required to be a URI.</p>

<p>When the <span style="FONT-FAMILY: Courier">&lt;KeyId&gt;</span> element
in a <span style="FONT-FAMILY: Courier">&lt;KeyBinding&gt;</span> specifies a
URL a binding is asserted to the specified address and protocol. For example
if the URL specifies an email address it is asserted that the specified key
MAY be used by a security enhancement. Similarly a <span
style="FONT-FAMILY: Courier">&lt;KeyId&gt;</span> contained in a <span
style="FONT-FAMILY: Courier">&lt;Prototype&gt;</span> or <span
style="FONT-FAMILY: Courier">&lt;Query&gt;</span> specifies an intention to
use the specified key with the protocol indicated.</p>

<p>The following table shows the correspondence between commonly used URL
prefixes and security bindings:</p>

<div align="center">

<table summary="URI Methods"
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse"
cellpadding="0" border="1">
  <tbody>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.95in; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="top" width="187"><p><strong>Method</strong></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 290.7pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="top" width="388"><p><strong>Security Enhancement</strong></p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.95in; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="187"><p><span
        style="FONT-FAMILY: Courier">https://<em>host</em>/<em>data</em></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 290.7pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="388"><p>SSL / TLS. Key is bound to the host name
        <span class="ID"><em><span
        style="FONT-FAMILY: Courier">host</span></em></span>.</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 1.95in; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="187"><p><span
        style="FONT-FAMILY: Courier">mailto://<em>user</em>@<em>host</em></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 290.7pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="388"><p>S/MIME email security, Key is bound to the
        username <span class="ID"><em><span
        style="FONT-FAMILY: Courier">user</span></em><span
        style="FONT-FAMILY: Courier">@<em>host</em></span></span></p>
      </td>
    </tr>
  </tbody>
</table>
</div>

<p>The <span style="FONT-FAMILY: Courier">&lt;KeyId&gt;</span> element is
defined by the following schema:</p>

<p class="Code">&lt;element name="KeyID" type="anyURI"/&gt;</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Element <span
style="FONT-FAMILY: Courier">&lt;PassPhrase&gt;</span></h3>

<p>The <span style="FONT-FAMILY: Courier">&lt;PassPhrase&gt;</span> element
contains a MAC output value encoded as a base64 string.</p>

<p>On initial registration the <span
style="FONT-FAMILY: Courier">&lt;PassPhrase&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>To prove knowledge of the pass phrase in a subsequent revocation request
the <span style="FONT-FAMILY: Courier">&lt;PassPhrase&gt;</span> value is
obtained by performing the MAC calculation on the pass phrase value.</p>

<p>Details of the MAC output value calculation are provided in section 6 
below.</p>

<p class="Code">&lt;element name="PassPhrase" type="string"/&gt;</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Element <span
style="FONT-FAMILY: Courier">&lt;ProcessInfo&gt;</span></h3>

<p>The <span style="FONT-FAMILY: Courier">&lt;ProcessInfo&gt;</span> element
MAY be used to specify processing information associated with a key binding
that end clients SHOULD treat as opaque data. The element is defined by the
following schema:</p>

<p class="Code">&lt;element name="ProcessInfo"
type="xkms:ProcessInfoType"/&gt;</p>

<p class="Code">&lt;complexType name="ProcessInfoType"&gt;<br />
    &lt;sequence minOccurs="0" maxOccurs="unbounded"&gt;<br />
        &lt;any namespace="##other"/&gt;<br />
    &lt;/sequence&gt;<br />
&lt;/complexType&gt;</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Element <span
style="FONT-FAMILY: Courier">&lt;ValidityInterval&gt;</span></h3>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ValidityInterval&gt;</span></span> element
specifies limits on the validity of the assertion. It is defined by the
following schema:</p>

<p class="Code">&lt;element name="ValidityInterval"
type="xkms:ValidityIntervalType"/&gt;<br />
&lt;complexType name="ValidityIntervalType"&gt;<br />
    &lt;attribute name="xkms:NotBefore" type="dateTime"/&gt;<br />
    &lt;attribute name="xkms:NotOnOrAfter" type="dateTime"/&gt;<br />
&lt;/complexType&gt;</p>

<p>The <span style="FONT-FAMILY: Courier">&lt;ValidityInterval&gt;</span>
element contains the following attributes.</p>

<div align="center">

<table summary="Validity Interval Attributes"
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; WIDTH: 83.62%; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse"
cellpadding="0" width="83%" border="1">
  <tbody>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 20.42%; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="top" width="20%"><p>Attribute</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 18.68%; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="top" width="18%"><p>Type</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 60.9%; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="top" width="60%"><p>Description</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 20.42%; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="20%"><p><span
        style="FONT-FAMILY: Courier">NotBefore</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 18.68%; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="18%"><p><span
        style="FONT-FAMILY: Courier">dateTime</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 60.9%; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="60%"><p>Time instant at which the validity interval
        begins</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 20.42%; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="20%"><p><span
        style="FONT-FAMILY: Courier">NotOnOrAfter</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 18.68%; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="18%"><p><span
        style="FONT-FAMILY: Courier">dateTime</span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 60.9%; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="60%"><p>Time instant at which the validity interval
        has ended</p>
      </td>
    </tr>
  </tbody>
</table>
</div>

<p>All dateTime values MUST fully specify the date.</p>

<p>The <span style="FONT-FAMILY: Courier">NotBefore</span> and <span
style="FONT-FAMILY: Courier">NotAfter</span> attributes are optional. If the
value is omitted it is unspecified. If the <span
style="FONT-FAMILY: Courier">NotBefore</span> attribute is unspecified the
assertion is valid on any date up to but excluding the date specified in the
<span style="FONT-FAMILY: Courier">NotAfter</span> attribute . If the <span
style="FONT-FAMILY: Courier">NotAfter</span> attribute is unspecified the
assertion is valid from the <span
style="FONT-FAMILY: Courier">NotBefore</span> attribute with no expiry. If
neither element is specified the assertion is valid at any time.</p>

<p>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>Implementations MUST NOT generate time instances that specify leap
seconds.</p>

<p>For purposes of comparison, the time interval <span
style="FONT-FAMILY: Courier">NotBefore</span> to <span
style="FONT-FAMILY: Courier">NotAfter</span> begins at the earliest time
instant compatible with the specification of <span
style="FONT-FAMILY: Courier">NotBefore</span> and <em><u>has ended</u></em>
at the <em><u>earliest</u></em> time instant compatible with the
specification of <span style="FONT-FAMILY: Courier">NotAfter</span></p>

<p>For example if the time interval specified is <span class="ID"><em><span
style="FONT-FAMILY: Courier">day</span></em></span><span class="ID"><span
style="FONT-FAMILY: Courier">T12:03:02</span></span> to <span
class="ID"><em><span style="FONT-FAMILY: Courier">day</span></em></span><span
class="ID"><span style="FONT-FAMILY: Courier">T12:05:12</span></span> the
times <span class="ID"><span
style="FONT-FAMILY: Courier">12:03:02.00</span></span> and <span
class="ID"><span style="FONT-FAMILY: Courier">12:05:11.9999</span></span> are
within the time interval. The time <span class="ID"><span
style="FONT-FAMILY: Courier">12:05:12.0000</span></span> is outside the time
interval.</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Element <span
style="FONT-FAMILY: Courier">&lt;KeyUsage&gt;</span></h3>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyUsage&gt;</span></span> element specifies
one or more intended uses of the key. If no <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyUsage&gt;</span></span> is specified all
uses are permitted. The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyUsage&gt;</span></span> element is
defined by the following schema:</p>

<p class="Code">&lt;element name="KeyUsage" type="xkms:KeyUsageType"/&gt;<br
/>
&lt;simpleType name="KeyUsageType"&gt;<br />
    &lt;restriction base="string"&gt;<br />
        &lt;enumeration value="Encryption"/&gt;<br />
        &lt;enumeration value="Signature"/&gt;<br />
        &lt;enumeration value="Exchange"/&gt;<br />
    &lt;/restriction&gt;<br />
&lt;/simpleType&gt;</p>

<p>If a key usage is specified that the algorithm does not support (e.g. use
of a DSA key for encryption) the element MUST be ignored.</p>

<p>The following identifiers are defined:</p>

<div align="center">

<table summary="Key Usage Identifiers"
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; WIDTH: 82.38%; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse"
cellpadding="0" width="82%" border="1">
  <tbody>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 22.7%; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="top" width="22%"><p><strong>Identifier</strong></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 77.3%; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="top" width="77%"><p><strong>Description</strong></p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 22.7%; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="22%"><p><span class="ID"><span
        style="FONT-FAMILY: Courier">Encryption</span></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 77.3%; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="77%"><p>The key pair may be used for encryption and
        decryption</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 22.7%; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="22%"><p><span class="ID"><span
        style="FONT-FAMILY: Courier">Signature</span></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 77.3%; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="77%"><p>The key pair may be used for signature and
        verification</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 22.7%; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="22%"><p><span class="ID"><span
        style="FONT-FAMILY: Courier">Exchange</span></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 77.3%; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="77%"><p>The key pair may be used for key
        exchange</p>
      </td>
    </tr>
  </tbody>
</table>
</div>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Request Message</h3>

<p>The request message consists of the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;Validate&gt;</span></span> element defined
by the following schema:</p>

<p class="Code">&lt;element name="ValidateRequest"
type="xkms:ValidateRequestType"/&gt;<br />
&lt;complexType name="ValidateRequestType"&gt;<br />
    &lt;complexContent&gt;<br />
        &lt;extension base="xkms:RequestAbstractType"&gt;<br />
            &lt;sequence&gt;<br />
                &lt;element ref="xkms:KeyBindingQuery"/&gt;<br />
            &lt;/sequence&gt;<br />
        &lt;/extension&gt;<br />
    &lt;/complexContent&gt;<br />
&lt;/complexType&gt;<br />
&lt;element name="KeyBindingQuery" type="xkms:KeyBindingType"/&gt;</p>

<p>The following elements are defined:</p>

<p class="Label"><span class="ID"><strong><span
style="FONT-FAMILY: Courier">Query</span></strong></span><br />
A single <span class="ID"><span
style="FONT-FAMILY: Courier">KeyBinding</span></span> structure that is to be
completed and validated.</p>

<p class="Label"><span class="ID"><strong><span
style="FONT-FAMILY: Courier">Respond</span></strong></span><br />
A sequence of identifiers that specify data elements that the client requests
be returned in the response.</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Response Message</h3>

<p>The Response Message consists of a <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ValidateResult&gt;</span></span> element
defined by the following schema:</p>

<p class="Code">&lt;element name="ValidateResult"
type="xkms:ValidateResultType"/&gt;<br />
&lt;complexType name="ValidateResultType"&gt;<br />
    &lt;complexContent&gt;<br />
        &lt;extension base="xkms:ResultAbstractType"&gt;<br />
            &lt;sequence&gt;<br />
                &lt;element ref="xkms:KeyBinding" minOccurs="0"
maxOccurs="unbounded"/&gt;<br />
            &lt;/sequence&gt;<br />
        &lt;/extension&gt;<br />
    &lt;/complexContent&gt;<br />
&lt;/complexType&gt;</p>

<p>The following elements are defined:</p>

<p class="Label"><span class="ID"><strong><span
style="FONT-FAMILY: Courier">Answer</span></strong></span><br />
A sequence of <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyBinding&gt;</span></span> structures that
contain the results of the validation. If no results are found the sequence
is empty and the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ResultCode&gt;</span></span><span
class="ID"><span style="FONT-FAMILY: Courier">NoMatch</span></span> returned.
In some circumstances a <span class="ID"><span
style="FONT-FAMILY: Courier">Locate</span></span> operation MAY return
multiple matching results.</p>

<p>The response message returns a <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ResultCode&gt;</span></span> depending on
the success of the <span class="ID"><span
style="FONT-FAMILY: Courier">Validate</span></span> operation as follows:</p>

<div align="center">

<table summary="Result Codes"
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-LEFT: 2.9pt; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse">
  <tbody>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 86.55pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="bottom" width="115"><p><span class="ID"><strong><span
        style="FONT-FAMILY: Courier">ResultCode</span></strong></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 121.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="bottom" width="162"><p><strong>Number of Elements</strong></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 175.75pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="bottom" width="234"><p><strong>Description</strong></p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 86.55pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="115"><p><span class="ID"><span
        style="FONT-FAMILY: Courier">Success</span></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 121.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="162"><p>At least one element</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 175.75pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="234"><p>The validate operation succeeded. all the
        information requested was available.</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 86.55pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="115"><p><span class="ID"><span
        style="FONT-FAMILY: Courier">NoMatch</span></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 121.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="162"><p>No elements</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 175.75pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="234"><p>The validate operation succeeded but
        returned no matches.</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 86.55pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="115"><p><span class="ID"><span
        style="FONT-FAMILY: Courier">Incomplete</span></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 121.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="162"><p>At least one element</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 175.75pt; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="234"><p>The validate operation succeeded. Some of
        the information requested was not available.</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 86.55pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="115"><p><span class="ID"><span
        style="FONT-FAMILY: Courier">Failure</span></span></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 121.5pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="162"><p>No elements</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 175.75pt; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="234"><p>The validate operation failed.</p>
      </td>
    </tr>
  </tbody>
</table>
</div>

<p>Note that the <span class="ID"><span
style="FONT-FAMILY: Courier">Validate</span></span> operation returns the
<span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ResultCode&gt;</span></span><span
class="ID"><span style="FONT-FAMILY: Courier">Success</span></span> even if
the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyBinding&gt;</span></span> assertion was
found to be <span class="ID"><span
style="FONT-FAMILY: Courier">Invalid</span></span> or <span class="ID"><span
style="FONT-FAMILY: Courier">Indeterminate</span></span>. The &lt;<span
class="ID"><span style="FONT-FAMILY: Courier">ResultCode&gt;</span></span>
reflects the success or failure of the service query and not the information
returned by that query.</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Faults</h3>

<p>When the protocol is expressed in SOAP, all <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ResultCode&gt;</span></span> <span
class="ID">values</span> other than <span class="ID"><span
style="FONT-FAMILY: Courier">Success</span></span>, <span class="ID"><span
style="FONT-FAMILY: Courier">Incomplete</span></span> and <span
class="ID"><span style="FONT-FAMILY: Courier">NoMatch</span></span> are
expressed using the SOAP <span class="ID"><span
style="FONT-FAMILY: Courier">Fault</span></span> element <span
class="ID">with a</span> <span class="ID"><span
style="FONT-FAMILY: Courier">faultcode</span></span> <span
class="ID">of</span> <span class="ID"><span
style="FONT-FAMILY: Courier">soap:Server</span></span><span class="ID">.  See
the [SOAP] specification for further details.</span> The service MAY return
the descriptive text set out in section 3.3.8 above.</p>

<h1 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Key Registration Service
Protocol Overview</h1>

<p>The XML Key Registration Service Specification permits management of
information that is bound to a public key pair.</p>

<p>The service specification supports the following operation:</p>

<p class="Label"><span class="ID"><strong><span
style="FONT-FAMILY: Courier">Register</span></strong></span><br />
Information is bound to a public key pair through a XKMS <span
class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyBinding&gt;</span></span> element.
Generation of the public key pair by either the client or the server is
supported.</p>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">Register</span></span> request does not in
itself place any requirement on the Registration Service to communicate that
information to any other party.</p>

<p>In most applications, however, a Registration Service will provide key
information to other trust services such as those described in the XKMS
specification or a separate underlying PKI such as PKIX.</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Linkage to an Underlying
PKI</h2>

<p>Linkage to such an underlying PKI is considered to be an intrinsic
property of the Registration Service rather than a parameter that the client
application may negotiate. To be useful such a negotiation service would need
to express more than the syntax of the credentials issued.</p>

<p>If necessary, Registration Services may offer links to multiple underlying
PKIs through separate service address URIs. For example:</p>

<p
style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in">http://register.xmltrustcenter.org/pgp<br
/>
Obtain a PGP credential</p>

<p
style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in">http://register.xmltrustcenter.org/x509/public_class2<br
/>
Obtain an X.509v3 credential in the "Trust Center Public Class 2"
hierarchy</p>

<p
style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in">http://register.xmltrustcenter.org/private/AKEHJQ<br
/>
Obtain an X.509v3 credential in a private hierarchy, the details of which the
client application does not understand</p>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:Keyinfo&gt;</span></span> elements <span
class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:X509Data&gt;</span></span>, <span
class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:PGPData&gt;</span></span> and <span
class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:SPKIData&gt;</span></span> MAY be used to
return credentials issued in an underlying PKI. Alternatively the client may
request that a <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ds:RetrievalMethod&gt;</span></span> element
be returned in the response to allow retrieval of the credential to be
generated (e.g. an X.509v3 certificate).</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Registration</h2>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">Register</span></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>The Registration request message consists of a prototype of the requested
assertion. 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>The Registration service MAY accept the name specified in the prototype or
MAY substitute its own name.</p>

<p>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 an assertion is registered. This assertion MAY
include some, all or none of the information provided by the prototype
assertion and MAY include additional information.</p>

<p>The Registration Service MAY return part or all of the registered
assertion to the client.</p>

<p style="TEXT-ALIGN: center" align="center"><img height="216"
alt="Diagram shows the data passed from the client to the server for registration"
src="./image010.gif" width="480" border="0" /></p>

<p class="Caption" align="center">Figure 5: Registration of a KeyBinding</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Example: Registration of
Client-Generated Key Pair</h3>

<p class="BodyTextKeep"
style="PAGE-BREAK-AFTER: auto; LINE-HEIGHT: normal">Alice requests
registration of an RSA key pair for her email address <span class="ID"><span
style="FONT-FAMILY: Courier">Alice@cryptographer.test</span></span>. Alice
has previously received from the trust 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 class="BodyTextKeep"
style="PAGE-BREAK-AFTER: auto; LINE-HEIGHT: normal">The X-KRSS request
message consists of the following <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;Register&gt;</span></span> element:</p>

<p class="Example">&lt;Register&gt;</p>

<p class="Example">   &lt;Prototype Id="keybinding"&gt;</p>

<p class="Example">      &lt;Status&gt;Valid&lt;/Status&gt;</p>

<p class="Example">     
&lt;KeyID&gt;mailto:Alice@cryptographer.test&lt;/KeyID&gt;</p>

<p class="Example">      &lt;ds:KeyInfo&gt;</p>

<p class="Example">         &lt;ds:KeyValue&gt;</p>

<p class="Example">            &lt;ds:RSAKeyValue&gt;</p>

<p class="Example">               &lt;ds:Modulus&gt;</p>

<p class="Example">              
998/T2PUN8HQlnhf9YIKdMHHGM7HkJwA56UD0a1oYq7E</p>

<p class="Example">              
fdxSXAidruAszNqBoOqfarJIsfcVKLob1hGnQ/l6xw</p>

<p class="Example">               &lt;/ds:Modulus&gt;</p>

<p class="Example">              
&lt;ds:Exponent&gt;AQAB&lt;/ds:Exponent&gt;</p>

<p class="Example">            &lt;/ds:RSAKeyValue&gt;</p>

<p class="Example">         &lt;/ds:KeyValue&gt;</p>

<p class="Example">        
&lt;ds:KeyName&gt;mailto:Alice@cryptographer.test&lt;/ds:KeyName&gt;</p>

<p class="Example">      &lt;/ds:KeyInfo&gt;</p>

<p class="Example">      &lt;PassPhrase&gt;<em><span
style="COLOR: red">Pass</span></em>&lt;/PassPhrase&gt;</p>

<p class="Example">   &lt;/Prototype&gt;</p>

<p class="Example">   &lt;AuthInfo&gt;</p>

<p class="Example">      &lt;AuthUserInfo&gt;</p>

<p class="Example">         &lt;ProofOfPossession&gt;</p>

<p class="Example">            &lt;ds:Signature URI="#keybinding"</p>

<p class="Example">                  [RSA-Sign (KeyBinding, Private)]
/&gt;</p>

<p class="Example">         &lt;/ProofOfPossession&gt;</p>

<p class="Example">         &lt;KeyBindingAuth&gt;</p>

<p class="Example">            &lt;ds:Signature  URI="#keybinding"</p>

<p class="Example">                  [HMAC-SHA1 (KeyBinding, Auth)] /&gt;</p>

<p class="Example">         &lt;/KeyBindingAuth&gt;</p>

<p class="Example">      &lt;/AuthUserInfo&gt;</p>

<p class="Example">   &lt;/AuthInfo&gt;</p>

<p class="Example">   &lt;Respond&gt;</p>

<p class="Example">      &lt;string&gt;KeyName&lt;string&gt;</p>

<p class="Example">      &lt;string&gt;KeyValue&lt;/string&gt;</p>

<p class="Example">      &lt;string&gt;RetrievalMethod&lt;/string&gt;</p>

<p class="Example">   &lt;/Respond&gt;</p>

<p class="Example">&lt;/Register&gt;</p>

<p>Where:</p>

<p style="MARGIN-LEFT: 0.25in"><em>Auth</em> = HMAC-SHA1 ("024837", 0x1)<br />
<em>Pass</em> = HMAC-SHA1 (HMAC-SHA1 ("<span class="ID"><span
style="FONT-FAMILY: Courier">helpihaverevealedmykey</span></span>", 0x2),
0x3)</p>

<p>For clarity, the details of the signature elements are omitted. In each
case the signature scope is the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyBinding&gt;</span></span> element and the
signature scope is specified by reference. The MAC function used in this case
is HMAC-SHA1 as defined in [RFC-2104]. The notation <em>f(m, k)</em> is used
to indicate the message <em>m</em> signed under the key <em>k</em>. Further
details are provided in section 6.1 .</p>

<p>The service accepts the registration and returns the following
response:</p>

<p class="Example">&lt;RegisterResult&gt;</p>

<p class="Example">   &lt;Result&gt;Success&lt;/Result&gt;</p>

<p class="Example">   &lt;Answer&gt;</p>

<p class="Example">      &lt;Status&gt;Valid&lt;/Status&gt;</p>

<p class="Example">     
&lt;KeyID&gt;mailto:Alice@cryptographer.test&lt;/KeyID&gt;</p>

<p class="Example">      &lt;ds:KeyInfo&gt;</p>

<p class="Example">         &lt;ds:RetrievalMethod</p>

<p class="Example">             
URI="http://www.PKeyDir.test/Certificates/01293122"</p>

<p class="Example">              Type="<a
href="http://www.w3.org/2000/09/xmldsig#SPKIData"><span
style="COLOR: windowtext; TEXT-DECORATION: none">http://www.w3.org/2000/09/xmldsig#X509Data</span></a>"/&gt;</p>

<p class="Example">         &lt;ds:KeyValue&gt;</p>

<p class="Example">            &lt;ds:RSAKeyValue&gt;</p>

<p class="Example">              
&lt;ds:Modulus&gt;998/T2PUN8HQlnhf9YIKdMHHGM7HkJwA56UD0a1oYq7Ef</p>

<p class="Example">              
dxSXAidruAszNqBoOqfarJIsfcVKLob1hGnQ/l6xw&lt;/ds:Modulus&gt;</p>

<p class="Example">              
&lt;ds:Exponent&gt;AQAB&lt;/ds:Exponent&gt;</p>

<p class="Example">            &lt;/ds:RSAKeyValue&gt;</p>

<p class="Example">         &lt;/ds:KeyValue&gt;</p>

<p class="Example">        
&lt;ds:KeyName&gt;mailto:Alice@cryptographer.test&lt;/ds:KeyName&gt;</p>

<p class="Example">      &lt;/ds:KeyInfo&gt;</p>

<p class="Example">   &lt;/Answer&gt;</p>

<p class="Example">&lt;/RegisterResult&gt;</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Example: Registration of
Service-Generated Key Pair</h3>

<p>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 class="Example">&lt;Register&gt;</p>

<p class="Example">   &lt;Prototype Id="keybinding"&gt;</p>

<p class="Example">      &lt;Status&gt;Valid&lt;/Status&gt;</p>

<p class="Example">     
&lt;KeyID&gt;mailto:Alice@cryptographer.test&lt;/KeyID&gt;</p>

<p class="Example">      &lt;KeyInfo&gt;</p>

<p class="Example">         &lt;ds:KeyInfo&gt;</p>

<p class="Example">           
&lt;ds:KeyName&gt;mailto:Alice@cryptographer.test&lt;/ds:KeyName&gt;</p>

<p class="Example">         &lt;/ds:KeyInfo&gt;</p>

<p class="Example">      &lt;/KeyInfo&gt;</p>

<p class="Example">      &lt;PassPhrase&gt;<em><span
style="COLOR: red">Pass</span></em>&lt;/PassPhrase&gt;</p>

<p class="Example">   &lt;/Prototype&gt;</p>

<p class="Example">   &lt;AuthInfo&gt;</p>

<p class="Example">      &lt;AuthServerInfo&gt;</p>

<p class="Example">         &lt;KeyBindingAuth&gt;</p>

<p class="Example">            &lt;ds:Signature  URI="#keybinding"</p>

<p class="Example">               <em>[HMAC-SHA1 (Prototype, Auth)]</em>
/&gt;</p>

<p class="Example">         &lt;/KeyBindingAuth&gt;</p>

<p class="Example">      &lt;/AuthServerInfo&gt;</p>

<p class="Example">   &lt;/AuthInfo&gt;</p>

<p class="Example">   &lt;Respond&gt;</p>

<p class="Example">      &lt;string&gt;KeyName&lt;/string&gt;</p>

<p class="Example">      &lt;string&gt;KeyValue&lt;/string&gt;</p>

<p class="Example">      &lt;string&gt;Private&lt;/string&gt;</p>

<p class="Example">   &lt;/Respond&gt;</p>

<p class="Example">&lt;/Register&gt;</p>

<p>Where</p>

<p style="MARGIN-LEFT: 0.25in"><em>Auth</em> = HMAC-SHA1 ("<span
class="ID"><span style="FONT-FAMILY: Courier">024837</span></span>", 0x1)<br
/>
<em>Pass</em> = HMAC-SHA1 (HMAC-SHA1 ("<span class="ID"><span
style="FONT-FAMILY: Courier">helpihaverevealedmykey</span></span>", 0x2),
0x3)</p>

<p>The response includes both the public key data and the encrypted private
key:</p>

<p class="Example">&lt;RegisterResult&gt;</p>

<p class="Example">   &lt;Result&gt;Success&lt;/Result&gt;</p>

<p class="Example">   &lt;Answer&gt;</p>

<p class="Example">      &lt;KeyBinding&gt;</p>

<p class="Example">         &lt;Status&gt;Valid&lt;/Status&gt;</p>

<p class="Example">        
&lt;KeyID&gt;mailto:Alice@cryptographer.test&lt;/KeyID&gt;</p>

<p class="Example">         &lt;ds:KeyInfo&gt;</p>

<p class="Example">            &lt;ds:KeyValue&gt;</p>

<p class="Example">               &lt;ds:RSAKeyValue&gt;</p>

<p class="Example">                 
&lt;ds:Modulus&gt;998/T2PUN8HQlnhf9YIKdMHHGM7HkJwA56UD0a1oY</p>

<p class="Example">                 
q7EfdxSXAidruAszNqBoOqfarJIsfcVKLob1hGnQ/l6xw</p>

<p class="Example">                  &lt;/ds:Modulus&gt;</p>

<p class="Example">                 
&lt;ds:Exponent&gt;AQAB&lt;/ds:Exponent&gt;</p>

<p class="Example">               &lt;/ds:RSAKeyValue&gt;</p>

<p class="Example">            &lt;/ds:KeyValue&gt;</p>

<p class="Example">           
&lt;ds:KeyName&gt;mailto:Alice@cryptographer.test&lt;/ds:KeyName&gt;</p>

<p class="Example">         &lt;/ds:KeyInfo&gt;</p>

<p class="Example">      &lt;KeyBinding&gt;</p>

<p class="Example">   &lt;/Answer&gt;</p>

<p class="Example">   &lt;Private&gt; Base64 ( 3DES ( <em>RSAPrivate</em>,
<em>Enc</em>)) &lt;/Private&gt;</p>

<p class="Example">&lt;/RegisterResult&gt;</p>

<p>Where:</p>

<p style="MARGIN-LEFT: 0.25in"><em>Enc</em> = HMAC-SHA1 ("<span
class="ID"><span style="FONT-FAMILY: Courier">024837</span></span>", 0x4)<br
/>
<em>RSAPrivate</em> =</p>

<p class="Example">&lt;RSAKeyPair&gt;</p>

<p class="Example">  
&lt;ds:Modulus&gt;998/T2PUN8HQlnhf9YIKdMHHGM7HkJwA56UD0a1oYq7EfdxSXAidr</p>

<p class="Example">   uAszNqBoOqfarJIsfcVKLob1hGnQ/l6xw
&lt;/ds:Modulus&gt;</p>

<p class="Example">   &lt;PublicExponent&gt;AQAB&lt;/PublicExponent&gt;</p>

<p class="Example">  
&lt;PrivateExponent&gt;<em>whatever</em>&lt;/PrivateExponent&gt;</p>

<p class="Example">   &lt;P&gt;<em>whatever</em>&lt;/P&gt;</p>

<p class="Example">   &lt;Q&gt;<em>whatever</em>&lt;/Q&gt;</p>

<p class="Example">&lt;/RSAKeyPair&gt;</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Revocation</h2>

<p>A Registration service MAY permit clients to revoke previously issued
assertions. A revocation request is made in the same manner as the initial
registration of a key except that:</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> The status of the
<span class="ID"><span style="FONT-FAMILY: Courier">KeyBinding</span></span>
or <span class="ID"><span
style="FONT-FAMILY: Courier">KeyAssertion</span></span> prototype is <span
class="ID"><span style="FONT-FAMILY: Courier">Invalid</span></span>.</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> If the Registration
service has no record of the assertion the result code <span class="ID"><span
style="FONT-FAMILY: Courier">NotFound</span></span> is returned.</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Example: Revocation</h3>

<p>For some reason Alice requests the Registration Service revoke the binding
for her public key. Alice authenticates herself using by signing her request
with the corresponding private key. Alice could have used the pass phrase she
established during registration instead.</p>

<p>The request message is:</p>

<p class="Example">&lt;Register&gt;</p>

<p class="Example">   &lt;Prototype Id="keybinding"&gt;</p>

<p class="Example">      &lt;Status&gt;Invalid&lt;/Status&gt;</p>

<p class="Example">     
&lt;KeyID&gt;mailto:Alice@cryptographer.test&lt;/KeyId&gt;</p>

<p class="Example">      &lt;ds:KeyInfo&gt;</p>

<p class="Example">         &lt;ds:KeyValue&gt;</p>

<p class="Example">            &lt;ds:RSAKeyValue&gt;</p>

<p class="Example">              
&lt;ds:Modulus&gt;998/T2PUN8HQlnhf9YIKdMHHGM7HkJwA56UD0a1oYq7E</p>

<p class="Example">              
fdxSXAidruAszNqBoOqfarJIsfcVKLob1hGnQ/l6xw&lt;/ds:Modulus&gt;</p>

<p class="Example">              
&lt;ds:Exponent&gt;AQAB&lt;/ds:Exponent&gt;</p>

<p class="Example">            &lt;/ds:RSAKeyValue&gt;</p>

<p class="Example">         &lt;/ds:KeyValue&gt;</p>

<p class="Example">        
&lt;ds:KeyName&gt;mailto:Alice@cryptographer.test&lt;/ds:KeyName&gt;</p>

<p class="Example">      &lt;/ds:KeyInfo&gt;</p>

<p class="Example">   &lt;/Prototype&gt;</p>

<p class="Example">   &lt;AuthInfo&gt;</p>

<p class="Example">      &lt;AuthUserInfo&gt;</p>

<p class="Example">         &lt;ProofOfPossession&gt;</p>

<p class="Example">            &lt;ds:Signature  URI="#keybinding"</p>

<p class="Example">                  [RSA-Sign (KeyBinding, Private)]
/&gt;</p>

<p class="Example">         &lt;/ProofOfPossession&gt;</p>

<p class="Example">      &lt;/AuthUserInfo&gt;</p>

<p class="Example">   &lt;/AuthInfo&gt;</p>

<p class="Example">   &lt;Respond&gt;</p>

<p class="Example">      &lt;string&gt;KeyName&lt;/string&gt;</p>

<p class="Example">      &lt;string&gt;KeyValue&lt;/string&gt;</p>

<p class="Example">   &lt;/Respond&gt;</p>

<p class="Example">&lt;/Register&gt;</p>

<p>The service responds that the key binding has been revoked:</p>

<p class="Example">&lt;RequestResult&gt;</p>

<p class="Example">   &lt;Result&gt;Success&lt;/Result&gt;</p>

<p class="Example">   &lt;Answer&gt;</p>

<p class="Example">      &lt;Status&gt;Invalid&lt;/Status&gt;</p>

<p class="Example">     
&lt;KeyID&gt;mailto:Alice@cryptographer.test&lt;/KeyID&gt;</p>

<p class="Example">      &lt;ds:KeyInfo&gt;</p>

<p class="Example">         &lt;ds:KeyValue&gt;</p>

<p class="Example">            &lt;ds:RSAKeyValue&gt;</p>

<p class="Example">              
&lt;ds:Modulus&gt;998/T2PUN8HQlnhf9YIKdMHHGM7HkJwA56UD0a1oYq7E</p>

<p class="Example">              
fdxSXAidruAszNqBoOqfarJIsfcVKLob1hGnQ/l6xw&lt;/ds:Modulus&gt;</p>

<p class="Example">              
&lt;ds:Exponent&gt;AQAB&lt;/ds:Exponent&gt;</p>

<p class="Example">            &lt;/ds:RSAKeyValue&gt;</p>

<p class="Example">         &lt;/ds:KeyValue&gt;</p>

<p class="Example">        
&lt;ds:KeyName&gt;mailto:Alice@cryptographer.test&lt;/ds:KeyName&gt;</p>

<p class="Example">      &lt;/ds:KeyInfo&gt;</p>

<p class="Example">   &lt;/Answer&gt;</p>

<p class="Example">&lt;/RegisterResult&gt;</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Key Recovery</h2>

<p>A Registration service MAY permit clients to request key recovery. A key
recovery request is made in the same manner as the initial registration of a
key except that:</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> The key recovery
service is likely to require time to respond to the recovery request and MAY
return a &lt;<span class="ID"><span
style="FONT-FAMILY: Courier">ResultCode&gt;</span></span> of <span
class="ID"><span style="FONT-FAMILY: Courier">Pending</span></span>.</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> If the Registration
service has no record of the assertion the result code <span class="ID"><span
style="FONT-FAMILY: Courier">NotFound</span></span> is returned.</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Example: Key Recovery</h3>

<p>Alice has forgotten the private key she registered earlier. She 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 Alice (using an out of band method) the key recovery
authorization code "A8C8S H93HU C9H29 8Y43U H9J3 I23". 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>The request parameters for the key recovery are:</p>

<p class="Example">&lt;Register&gt;</p>

<p class="Example">   &lt;Prototype&gt;</p>

<p class="Example">      &lt;Status&gt;Indeterminate&lt;/Status&gt;</p>

<p class="Example">     
&lt;KeyID&gt;mailto:Alice@cryptographer.test&lt;/KeyId&gt;</p>

<p class="Example">      &lt;ds:KeyInfo&gt;</p>

<p class="Example">        
&lt;ds:KeyName&gt;mailto:Alice@cryptographer.test&lt;/ds:KeyName&gt;</p>

<p class="Example">      &lt;/ds:KeyInfo&gt;</p>

<p class="Example">   &lt;/Prototype&gt;</p>

<p class="Example">   &lt;AuthInfo&gt;</p>

<p class="Example">      &lt;PassPhraseAuth&gt;<em><span
style="COLOR: red">Auth</span></em>&lt;/PassPhraseAuth&gt;</p>

<p class="Example">   &lt;/AuthInfo&gt;</p>

<p class="Example">   &lt;Respond&gt;</p>

<p class="Example">      &lt;string&gt;KeyName&lt;/string&gt;</p>

<p class="Example">      &lt;string&gt;KeyValue&lt;/string&gt;</p>

<p class="Example">      &lt;string&gt;Private&lt;/string&gt;</p>

<p class="Example">   &lt;/Respond&gt;</p>

<p class="Example">&lt;/Register&gt;</p>

<p>Where</p>

<p>   <em>Auth</em> = HMAC-SHA1 ("<span class="ID"><span
style="FONT-FAMILY: Courier">a8c8sh93huc9h298y43uh9j3i23</span></span>",
0x1)</p>

<p>The registration service policy is to revoke a private key whenever key
recovery is performed. The service returns the revoked key binding and the
private key parameters:</p>

<p class="Example">&lt;RegisterResult&gt;</p>

<p class="Example">   &lt;Answer&gt;</p>

<p class="Example">      &lt;Status&gt;Invalid&lt;/Status&gt;</p>

<p class="Example">     
&lt;KeyID&gt;mailto:Alice@cryptographer.test&lt;/KeyID&gt;</p>

<p class="Example">      &lt;ds:KeyInfo&gt;</p>

<p class="Example">         &lt;ds:KeyValue&gt;</p>

<p class="Example">            &lt;ds:RSAKeyValue&gt;</p>

<p class="Example">              
&lt;ds:Modulus&gt;998/T2PUN8HQlnhf9YIKdMHHGM7HkJwA56UD0a1oYq7E</p>

<p class="Example">  
            fdxSXAidruAszNqBoOqfarJIsfcVKLob1hGnQ/l6xw&lt;/ds:Modulus&gt;</p>

<p class="Example">              
&lt;ds:Exponent&gt;AQAB&lt;/ds:Exponent&gt;</p>

<p class="Example">            &lt;/ds:RSAKeyValue&gt;</p>

<p class="Example">         &lt;/ds:KeyValue&gt;</p>

<p class="Example">        
&lt;ds:KeyName&gt;mailto:Alice@cryptographer.test&lt;/ds:KeyName&gt;</p>

<p class="Example">      &lt;/ds:KeyInfo&gt;</p>

<p class="Example">   &lt;/Answer&gt;</p>

<p class="Example">   &lt;Private&gt; Base64 ( 3DES ( <em>RSAPrivate</em>,
<em>Enc</em>)) &lt;/Private&gt;</p>

<p class="Example">&lt;/RegisterResult&gt;</p>

<p>Where:</p>

<p style="MARGIN-LEFT: 0.25in"><em>Enc</em> = HMAC-SHA1 ("<span
class="ID"><span
style="FONT-FAMILY: Courier">a8c8sh93huc9h298y43uh9j3i23</span></span>",
0x4)<br />
<em>RSAPrivate</em> = "</p>

<p class="Example">&lt;RSAKeyPair&gt;</p>

<p class="Example">  
&lt;ds:Modulus&gt;998/T2PUN8HQlnhf9YIKdMHHGM7HkJwA56UD0a1oYq7EfdxSXAidr</p>

<p class="Example">   uAszNqBoOqfarJIsfcVKLob1hGnQ/l6xw&lt;/ds:Modulus&gt;</p>

<p class="Example">   &lt;PublicExponent&gt;AQAB&lt;/PublicExponent&gt;</p>

<p class="Example">  
&lt;PrivateExponent&gt;<em>whatever</em>&lt;/PrivateExponent&gt;</p>

<p class="Example">   &lt;P&gt;<em>whatever</em>&lt;/P&gt;</p>

<p class="Example">   &lt;Q&gt;<em>whatever</em>&lt;/Q&gt;</p>

<p class="Example">&lt;/RSAKeyPair&gt;"</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Request Authentication</h2>

<p>The Service SHOULD ensure that all requests are valid.</p>

<p style="MARGIN-LEFT: 0.25in"><strong>Authenticity</strong>: The request
message originated from the specified party.</p>

<p style="MARGIN-LEFT: 0.25in"><strong>Integrity</strong>: The request
message has not been modified.</p>

<p style="MARGIN-LEFT: 0.25in"><strong>Possession</strong>: 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>

<p>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>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 assertion bound to that public key.</p>

<p>Services SHOULD accept Proof of Possession of the private key component of
a public key to effect revocation of any assertion bound to that key.</p>

<h1 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Key Registration Service
Message Set</h1>

<p>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. </p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Registration</h2>

<p>The Request message specifies a <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;Prototype&gt;</span></span> element that has
the type <span class="ID"><span
style="FONT-FAMILY: Courier">KeyBinding</span></span> and provides the
prototype for the key binding to be registered.</p>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;Prototype&gt;</span></span> element 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.</p>

<p>For example, the client may not specify the public key parameters because
the public and private key pair is to be generated by the Registration
Service.</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Element <span
style="FONT-FAMILY: Courier">&lt;Auth</span><span class="ID"><span
style="FONT-FAMILY: Courier">Info&gt;</span></span></h3>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;AuthInfo&gt;</span></span> element contains
data that authenticates the request. The form of the authentication data
depends upon:</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> The means of
authentication used;</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> The public key
algorithm used; and</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> The party that
generates the key pair (client or service).</p>

<p>The information MAY include a proof of possession for a public key that is
registered and MAY include information that authenticates the request through
a cryptographic binding to the <span class="ID"><span
style="FONT-FAMILY: Courier">Prototype</span></span> element.</p>

<p>If the private key is generated by the user the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;AuthInfo&gt;</span></span> element contains
an <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;AuthUserInfo&gt;</span></span> element. If
the private key is generated by the Trust Service the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;AuthInfo&gt;</span></span> element contains
an <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;AuthServerInfo&gt;</span></span> element as
described in the following schema:</p>

<p class="Code">&lt;element name="AuthInfo" type="xkms:AuthInfoType"/&gt;<br
/>
&lt;complexType name="AuthInfoType"&gt;<br />
    &lt;choice&gt;<br />
        &lt;element ref="xkms:AuthUserInfo"/&gt;<br />
        &lt;element ref="xkms:AuthServerInfo"/&gt;<br />
    &lt;/choice&gt;<br />
&lt;/complexType&gt;</p>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;AuthUserInfo&gt;</span></span> and <span
class="ID"><span
style="FONT-FAMILY: Courier">&lt;AuthServerInfo&gt;</span></span> elements
are defined in section 6  below.</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Register Request Message</h3>

<p>The request message consists of the <span
style="FONT-FAMILY: Courier">&lt;RegisterRequest&gt;</span> element defined
by the following schema:</p>

<p class="Code">&lt;element name="RegisterRequest"
type="xkms:RegisterRequestType"/&gt;<br />
&lt;complexType name="RegisterRequestType"&gt;<br />
    &lt;complexContent&gt;<br />
        &lt;extension base="xkms:RequestAbstractType"&gt;<br />
            &lt;sequence&gt;<br />
                &lt;element ref="xkms:Prototype"/&gt;<br />
                &lt;element ref="xkms:AuthInfo"/&gt;<br />
            &lt;/sequence&gt;<br />
        &lt;/extension&gt;<br />
    &lt;/complexContent&gt;<br />
&lt;/complexType&gt;</p>

<p>The following elements are defined:</p>
<dl>
  <dt><span class="ID"><strong><span
  style="FONT-FAMILY: Courier">Prototype</span></strong></span></dt>
    <dd>A single <span class="ID"><span
      style="FONT-FAMILY: Courier">KeyBinding</span></span> structure that
      specifies elements that the client requests be registered.</dd>
  <dt><span class="ID"><strong><span
  style="FONT-FAMILY: Courier">AuthInfo</span></strong></span></dt>
    <dd>An XML document node that provides information that authenticates the
      request.</dd>
</dl>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Register Response Message</h3>

<p>The Response Message consists of a <span
style="FONT-FAMILY: Courier">&lt;RegisterResult&gt;</span> element defined by
the following schema:</p>

<p class="Code">&lt;element name="RegisterResult"
type="xkms:RegisterResultType"/&gt;<br />
&lt;complexType name="RegisterResultType"&gt;<br />
    &lt;complexContent&gt;<br />
        &lt;extension base="xkms:ResultAbstractType"&gt;<br />
            &lt;sequence&gt;<br />
                &lt;element ref="xkms:KeyBinding" minOccurs="0"
maxOccurs="unbounded"/&gt;<br />
                &lt;element ref="xkms:Private" minOccurs="0"/&gt;<br />
            &lt;/sequence&gt;<br />
        &lt;/extension&gt;<br />
    &lt;/complexContent&gt;<br />
&lt;/complexType&gt;<br />
&lt;element name="Prototype" type="xkms:KeyBindingType"/&gt;</p>

<p>The following elements are defined:</p>
<dl>
  <dt><span class="ID"><strong><span
  style="FONT-FAMILY: Courier">KeyBinding</span></strong></span>
  (Optional)</dt>
    <dd>If present specifies the key binding that was registered by the
      service</dd>
  <dt><span class="ID"><strong><span
  style="FONT-FAMILY: Courier">Private</span></strong></span> (Optional)</dt>
    <dd>Additional information provided by the server that MAY provide values
      for private key parameters generated by the Registration Service</dd>
</dl>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Reissue Request Message</h3>

<p>The request message consists of the <span
style="FONT-FAMILY: Courier">&lt;ReissueRequest&gt;</span> element defined by
the following schema:</p>

<p class="Code">&lt;element name="ReissueRequest"
type="xkms:ReissueRequestType"/&gt;<br />
&lt;complexType name="ReissueRequestType"&gt;<br />
    &lt;complexContent&gt;<br />
        &lt;extension base="xkms:RequestAbstractType"&gt;<br />
            &lt;sequence&gt;<br />
                &lt;element ref="xkms:KeyBinding"/&gt;<br />
                &lt;element ref="xkms:AuthUserInfo"/&gt;<br />
            &lt;/sequence&gt;<br />
        &lt;/extension&gt;<br />
    &lt;/complexContent&gt;<br />
&lt;/complexType&gt;</p>

<p>The following elements are defined:</p>
<dl>
  <dt><span class="ID"><strong><span
  style="FONT-FAMILY: Courier">Prototype</span></strong></span></dt>
    <dd>A single <span style="FONT-FAMILY: Courier">KeyBinding</span>
      structure that specifies elements that the client requests be
      registered.</dd>
  <dt><span class="ID"><strong><span
  style="FONT-FAMILY: Courier">AuthInfo</span></strong></span></dt>
    <dd>An XML document node that provides information that authenticates the
      request.</dd>
</dl>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Reissue Response Message</h3>

<p>The Response Message consists of a <span
style="FONT-FAMILY: Courier">RegisterResult</span> element defined by the
following schema:</p>

<p class="Code">&lt;element name="ReissueResult"
type="xkms:ReissueResultType"/&gt;<br />
&lt;complexType name="ReissueResultType"&gt;<br />
    &lt;complexContent&gt;<br />
        &lt;extension base="xkms:ResultAbstractType"&gt;<br />
            &lt;sequence&gt;<br />
                &lt;element ref="xkms:KeyBinding" minOccurs="0"
maxOccurs="unbounded"/&gt;<br />
            &lt;/sequence&gt;<br />
        &lt;/extension&gt;<br />
    &lt;/complexContent&gt;<br />
&lt;/complexType&gt;</p>

<p>The following elements are defined:</p>
<dl>
  <dt><span class="ID"><span
  style="FONT-FAMILY: Courier"><strong>KeyBinding</strong></span></span>
  <strong>(Optional)</strong></dt>
    <dd>If present specifies the key binding that was registered by the
      service</dd>
</dl>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Revoke Request Message</h3>

<p>The request message consists of the <span
style="FONT-FAMILY: Courier">&lt;RevokeRequest&gt;</span> element defined by
the following schema:</p>

<p class="Code">&lt;element name="RevokeRequest"
type="xkms:RevokeRequestType"/&gt;<br />
&lt;complexType name="RevokeRequestType"&gt;<br />
    &lt;complexContent&gt;<br />
        &lt;extension base="xkms:RequestAbstractType"&gt;<br />
            &lt;sequence&gt;<br />
                &lt;element ref="xkms:KeyBinding"/&gt;<br />
                &lt;element ref="xkms:AuthUserInfo"/&gt;<br />
            &lt;/sequence&gt;<br />
        &lt;/extension&gt;<br />
    &lt;/complexContent&gt;<br />
&lt;/complexType&gt;</p>

<p>The following elements are defined:</p>
<dl>
  <dt><span class="ID"><strong><span
  style="FONT-FAMILY: Courier">Prototype</span></strong></span></dt>
    <dd>A single <span style="FONT-FAMILY: Courier">KeyBinding</span>
      structure that specifies elements that the client requests be
      registered.</dd>
  <dt><span class="ID"><strong><span
  style="FONT-FAMILY: Courier">AuthInfo</span></strong></span></dt>
    <dd>An XML document node that provides information that authenticates the
      request.</dd>
</dl>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Revoke Response Message</h3>

<p>The Response Message consists of a <span
style="FONT-FAMILY: Courier">&lt;Revoke</span><span
style="FONT-FAMILY: Courier">Result&gt;</span> element defined by the
following schema:</p>

<p class="Code">&lt;element name="RevokeResult"
type="xkms:RevokeResultType"/&gt;<br />
&lt;complexType name="RevokeResultType"&gt;<br />
    &lt;complexContent&gt;<br />
        &lt;extension base="xkms:ResultAbstractType"&gt;<br />
            &lt;sequence&gt;<br />
                &lt;element ref="xkms:KeyBinding" minOccurs="0"
maxOccurs="unbounded"/&gt;<br />
            &lt;/sequence&gt;<br />
        &lt;/extension&gt;<br />
    &lt;/complexContent&gt;<br />
&lt;/complexType&gt;</p>

<p>The following elements are defined:</p>
<dl>
  <dt><span class="ID"><strong><span
  style="FONT-FAMILY: Courier">KeyBinding</span></strong></span>
  (Optional)</dt>
    <dd>If present specifies the key binding that was registered by the
      service</dd>
  <dt><span class="ID"><strong><span
  style="FONT-FAMILY: Courier">Private</span></strong></span> (Optional)</dt>
    <dd>Additional information provided by the server that MAY provide values
      for private key parameters generated by the Registration Service</dd>
</dl>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Recover Request Message</h3>

<p>The request message consists of the <span
style="FONT-FAMILY: Courier">&lt;RecoverRequest&gt;</span> element defined by
the following schema:</p>

<p class="Code">&lt;element name="RecoverRequest"
type="xkms:RecoverRequestType"/&gt;<br />
&lt;complexType name="RecoverRequestType"&gt;<br />
    &lt;complexContent&gt;<br />
        &lt;extension base="xkms:RequestAbstractType"&gt;<br />
            &lt;sequence&gt;<br />
                &lt;element ref="xkms:KeyBinding"/&gt;<br />
                &lt;element ref="xkms:AuthUserInfo"/&gt;<br />
            &lt;/sequence&gt;<br />
        &lt;/extension&gt;<br />
    &lt;/complexContent&gt;<br />
&lt;/complexType&gt;</p>

<p>The following elements are defined:</p>
<dl>
  <dt><span class="ID"><strong><span
  style="FONT-FAMILY: Courier">Prototype</span></strong></span></dt>
    <dd>A single <span style="FONT-FAMILY: Courier">KeyBinding</span>
      structure that specifies elements that the client requests be
      registered.</dd>
  <dt><span class="ID"><strong><span
  style="FONT-FAMILY: Courier">AuthInfo</span></strong></span></dt>
    <dd>An XML document node that provides information that authenticates the
      request.</dd>
</dl>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Recover Response Message</h3>

<p>The Response Message consists of a <span
style="FONT-FAMILY: Courier">RecoverResult</span> element defined by the
following schema:</p>

<p class="Code">&lt;element name="RecoverResult"
type="xkms:RecoverResultType"/&gt;<br />
&lt;complexType name="RecoverResultType"&gt;<br />
    &lt;complexContent&gt;<br />
        &lt;extension base="xkms:ResultAbstractType"&gt;<br />
            &lt;sequence&gt;<br />
                &lt;element ref="xkms:KeyBinding" minOccurs="0"
maxOccurs="unbounded"/&gt;<br />
                &lt;element ref="xkms:Private" minOccurs="0"/&gt;<br />
            &lt;/sequence&gt;<br />
        &lt;/extension&gt;<br />
    &lt;/complexContent&gt;<br />
&lt;/complexType&gt;</p>

<p>The following elements are defined:</p>
<dl>
  <dt><span class="ID"><strong><span
  style="FONT-FAMILY: Courier">KeyBinding</span></strong></span>
  (Optional)</dt>
    <dd>If present specifies the key binding that was registered by the
      service</dd>
  <dt><span class="ID"><strong><span
  style="FONT-FAMILY: Courier">Private</span></strong></span> (Optional)</dt>
    <dd>Additional information provided by the server that MAY provide values
      for private key parameters generated by the Registration Service</dd>
</dl>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Faults</h3>

<p>When the protocol is expressed in SOAP, all <span class="ID"><span
style="FONT-FAMILY: Courier">ResultCode</span></span> <span
class="ID">values</span> other than <span class="ID"><span
style="FONT-FAMILY: Courier">Success</span></span>, <span class="ID"><span
style="FONT-FAMILY: Courier">Incomplete</span></span> and <span
class="ID"><span style="FONT-FAMILY: Courier">NoMatch</span></span> are
expressed using the SOAP <span class="ID"><span
style="FONT-FAMILY: Courier">Fault</span></span> element <span
class="ID">with a</span> <span class="ID"><span
style="FONT-FAMILY: Courier">faultcode</span></span> <span
class="ID">of</span> <span class="ID"><span
style="FONT-FAMILY: Courier">soap:Server</span></span><span class="ID">.  See
the [SOAP] specification for further details.</span> The service MAY return
the descriptive text set out in section 3.2.2 above.</p>

<h1 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Cryptographic Algorithm
Specific Parameters</h1>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Use of Limited-Use Shared
Secret Data</h2>

<p>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>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>Since human users are the most demanding in terms of interface
requirements the handling of symmetric key data is designed for the needs of
clients supporting human users directly. Symmetric keying data is typically
issued to a human user in the form of a text string which may in some
circumstances be read over a telephone line. The authentication data itself
MAY be randomly generated and represent an underlying numeric value, or MAY
be a password or phrase. In either case it is most convenient to present the
value to the human user as a string of characters in a character set the
particular user understands.</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> All shared string
values are encoded as XML</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> All space and
control characters are removed.</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> All upper case
characters in the Latin-1 alphabet (A-Z) are converted to lower case.</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> No other
characters, including accented characters are converted</p>

<p>Keying material is derived from the shared string using a MAC function.
Different MAC keying values are used according to the use of the symmetric
key derived as follows:</p>

<div align="center">

<table summary="MAC Keyring Values"
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; BORDER-LEFT: medium none; WIDTH: 73.38%; BORDER-BOTTOM: medium none; BORDER-COLLAPSE: collapse"
cellspacing="0" cellpadding="0" width="73%" border="1">
  <tbody>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 18.28%; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="top" width="18%"><p style="TEXT-ALIGN: center"
        align="center"><strong>Value</strong></p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: green 1.5pt solid; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 81.72%; PADDING-TOP: 0in; BORDER-BOTTOM: green 0.75pt solid"
      valign="top" width="81%"><p style="TEXT-ALIGN: center"
        align="center"><strong>Application</strong></p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 18.28%; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="18%"><p style="TEXT-ALIGN: center"
        align="center">0x1</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 81.72%; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="81%"><p>Authentication</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 18.28%; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="18%"><p style="TEXT-ALIGN: center"
        align="center">0x2</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 81.72%; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="81%"><p>Encoding of Pass Phrase - Pass 1</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 18.28%; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="18%"><p style="TEXT-ALIGN: center"
        align="center">0x3</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 81.72%; PADDING-TOP: 0in; BORDER-BOTTOM: medium none"
      valign="top" width="81%"><p>Encoding of Pass Phrase - Pass 2</p>
      </td>
    </tr>
    <tr>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 18.28%; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="18%"><p style="TEXT-ALIGN: center"
        align="center">0x4</p>
      </td>
      <td
      style="BORDER-RIGHT: medium none; PADDING-RIGHT: 5.4pt; BORDER-TOP: medium none; PADDING-LEFT: 5.4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; WIDTH: 81.72%; PADDING-TOP: 0in; BORDER-BOTTOM: green 1.5pt solid"
      valign="top" width="81%"><p>Encryption of private key data</p>
      </td>
    </tr>
  </tbody>
</table>
</div>

<p>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>If the output of the MAC function provides less keying material than is
required the first MAC output value is used to supply the least significant
160 bits of keying material. A second MAC output value is then obtained by
applying the MAC function to the shared 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>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Element <span
style="FONT-FAMILY: Courier">&lt;PassPhraseAuth&gt;</span></h3>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;PassPhraseAuth&gt;</span></span> element
contains a plaintext limited use shared secret that is used to authenticate
the request.</p>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;PassPhraseAuth&gt;</span></span> element is
defined by the following schema:</p>

<p class="Code">&lt;element name="PassPhraseAuth" type="string"/&gt;</p>

<p><strong>NB: 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. See section 7.3  below for more
details.</strong></p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Element <span class="ID"
style="FONT-FAMILY: Courier">&lt;KeyBindingAuth</span><span class="ID"><span
style="FONT-FAMILY: Courier">&gt;</span></span></h3>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyBindingAuth&gt;</span></span> element
contains a XML Signature element that is used to authenticate the <span
class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyBinding&gt;</span></span> request using a
previously established key. The signature scope is the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyBinding&gt;</span></span> prototype using
the public key that is to be registered.</p>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyBindingAuth&gt;</span></span> element is
defined by the following schema:</p>

<p class="Code">&lt;element name="KeyBindingAuth"
type="xkms:KeyBindingAuthType"/&gt;<br />
&lt;complexType name="KeyBindingAuthType"&gt;<br />
    &lt;sequence&gt;<br />
        &lt;element ref="ds:Signature" minOccurs="0"/&gt;<br />
    &lt;/sequence&gt;<br />
&lt;/complexType&gt;</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Element <span
style="FONT-FAMILY: Courier">&lt;ProofOfPossession&gt;</span></h3>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ProofOfPossession&gt;</span></span> element
contains a XML Signature element. The signature scope is the <span
class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyBinding&gt;</span></span> prototype using
the public key that is to be registered. The private key component of the
public key contained within the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;KeyBinding&gt;</span></span> is used to
generate the signature.</p>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;ProofOfPossession&gt;</span></span> element
is defined by the following schema:</p>

<p class="Code">&lt;element name="ProofOfPossession"
type="xkms:ProofOfPossessionType"/&gt;<br />
&lt;complexType name="ProofOfPossessionType"&gt;<br />
    &lt;sequence&gt;<br />
        &lt;element ref="ds:Signature" minOccurs="0"/&gt;<br />
    &lt;/sequence&gt;<br />
&lt;/complexType&gt;</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Registration of User-Generated
RSA or DSA Keys</h2>

<p>If an RSA or DSA key pair generated by the user is to be registered, the
registration service MAY be required by its registration policy to ensure
that:</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> The party that made
the request has possession of the specified private key</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> The party that made
the request is authorized to assert the specified binding to a public key.</p>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;AuthUserInfoType&gt;</span></span> element
type has the following schema definition:</p>

<p class="Code">&lt;element name="AuthUserInfo"
type="xkms:AuthUserInfoType"/&gt;<br />
&lt;complexType name="AuthUserInfoType"&gt;<br />
    &lt;sequence&gt;<br />
        &lt;element ref="xkms:ProofOfPossession" minOccurs="0"/&gt;<br />
        &lt;element ref="xkms:KeyBindingAuth" minOccurs="0"/&gt;<br />
        &lt;element ref="xkms:PassPhraseAuth" minOccurs="0"/&gt;<br />
    &lt;/sequence&gt;<br />
&lt;/complexType&gt;</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Registration of
Service-Generated RSA Keys</h2>

<p>If the RSA key pair is generated by the registration service the
registration MAY be required by its registration policy to ensure that:</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> The party that made
the request is authorized to assert the specified binding to a public key.</p>

<p>In addition the Registration Service MUST communicate the private key
parameters to the user. The Registration Service SHOULD ensure that the
confidentiality of the private key is protected.</p>

<p>The <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;AuthServerInfo&gt;</span></span> element is
used for this request as defined by the following schema:</p>

<p class="Code">&lt;element name="AuthServerInfo"
type="xkms:AuthServerInfoType"/&gt;<br />
&lt;complexType name="AuthServerInfoType"&gt;<br />
    &lt;sequence&gt;<br />
        &lt;element ref="xkms:KeyBindingAuth" minOccurs="0"/&gt;<br />
        &lt;element ref="xkms:PassPhraseAuth" minOccurs="0"/&gt;<br />
    &lt;/sequence&gt;<br />
&lt;/complexType&gt;</p>

<p>Registration of service-generated DSA keys is not supported. A DSA key can
only be used for signature. Key recovery of signature keys has only limited
application. The principal reason to perform server generation of key pairs
is to support Key Recovery. </p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Encoding of RSA Private Key
Parameters</h3>

<p>The service MAY return the RSA public and private key parameters to the
client.</p>

<p>The public and private parameters for the RSA algorithm are generated from
the parameters <em>p</em> and <em>q</em>. Although private key operations may
be performed using the private modulus alone knowledge of the generator
parameters permits optimizations such as the Chinese Remainder Theorem to be
applied. Accordingly the private key element permits these to be
specified.</p>

<p>The XML schema for this structure is:</p>

<p class="Code">&lt;element name="Private" type="ds:CryptoBinary"/&gt;<br />
&lt;element name="RSAKeyPair" type="xkms:RSAKeyPairType"/&gt;<br />
&lt;complexType name="RSAKeyPairType"&gt;<br />
    &lt;sequence&gt;<br />
        &lt;element name="Modulus" type="ds:CryptoBinary"/&gt;<br />
        &lt;element name="PublicExponent" type="ds:CryptoBinary"/&gt;<br />
        &lt;element name="PrivateExponent" type="ds:CryptoBinary"/&gt;<br />
        &lt;element name="P" type="ds:CryptoBinary" minOccurs="0"/&gt;<br />
        &lt;element name="Q" type="ds:CryptoBinary" minOccurs="0"/&gt;<br />
    &lt;/sequence&gt;<br />
&lt;/complexType&gt;</p>

<h3 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Encryption of Private Key
Parameters</h3>

<p style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">The Private Key Parameters are
encrypted using the XML Encryption specification [XML-ENC].</p>

<p style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">[TBS give examples, specify
keying arrangements]</p>

<h1 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Security Considerations</h1>

<p>Implementations SHOULD consider the following security issues.</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Replay Attacks</h2>

<p>Implementations SHOULD ensure that replay of a previous XKMS response is
not possible.</p>

<p>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 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 style="MARGIN-TOP: 0in" 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>

<p>Freshness tokens MAY be encoded as XML Signature Properties.</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Denial of Service</h2>

<p>Trust Services SHOULD take measures to prevent or mitigate denial of
service attacks. In particular Trust 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>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> CPU intensive
cryptographic operations, including signature verification and key
exchange.</p>

<p style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in"><span
style="FONT-FAMILY: Symbol">·<span
style="FONT: 7pt 'Times New Roman'">       </span></span> Resolution of
URLs.</p>

<h2 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Recovery Policy</h2>

<p>Key recovery policy is left as an implementation decision.</p>

<p>Depending on the implementation and application a key recovery operation
MAY 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>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 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Security of Limited Use Shared
Secret</h2>

<p>If a limited use shared secret is used care must be taken to ensure that
the secret is not revealed to an attacker. A means of protecting the
confidentiality of the shared secret SHOULD be employed. This MAY be a
message level or transport level protocol that protects <em>both</em>
encryption <em>and integrity</em> such as SSL.</p>

<p>Note that merely encrypting the shared secret <em>does not provide
adequate security</em> since the <span class="ID"><span
style="FONT-FAMILY: Courier">&lt;PassPhraseAuth&gt;</span></span> element is
not cryptographically bound to the message.</p>

<h1 style="MARGIN-LEFT: 0in; TEXT-INDENT: 0in">Acknowledgments</h1>

<p>The authors also acknowledge the extensive assistance provided in the
design stage of this specification by David Solo (CitiGroup), and the
contributions of Steve Farrell (Baltimore), Mack Hicks (Bank of America),
Andrew Layman  (Microsoft), Dr Paul Boisen (NSA),  Dan Guinan, Marc Hayes,
Alex Deacon, Mingliang Pei (VeriSign).</p>

<h1 style="PAGE-BREAK-BEFORE: always">Appendix A Schema and Web Service
Contract</h1>

<p>This appendix describes specific instructions for use of the SOAP binding.
Ideally the means of authenticating SOAP messages will be specified in the
SOAP specification.</p>

<p>If an XML Signature is used the scope of the signature is the <font
face="Courier">&lt;SOAP-ENV:Envelope&gt;</font> element.</p>

<h2><a id="A.1-XKMS-Schema" name="A.1-XKMS-Schema">A.1 XKMS Schema</a></h2>

<p class="Code">TBS</p>

<h2><a id="A.2-Web-Service-Definition" name="A.2-Web-Service-Definition">A.2
Web Service Definition</a></h2>

<p>The following Web Service Definition Language definitions are
<em>normative</em>.  The Service, and associated Port, elements define a
specific implementation and are exemplary only.  In this case, a service is
located at http://service.xmltrustcenter.org/Test/KeySrvc.asmx.</p>

<p class="code">TBS</p>

<h1><a id="SampleProtocolExchanges" name="SampleProtocolExchanges">Appendix B
Sample Protocol Exchanges</a></h1>

<h2><a id="Tier1Example1" name="Tier1Example1">B.1 Tier 1 Example 1</a></h2>

<p>This example shows the formatting of the X-KISS request and response for
the first example in section 2.2  above.</p>

<p><strong>Request Message</strong></p>

<p class="Example">TBS</p>

<p
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-TOP: 6pt; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none"><strong>Server
Response</strong></p>

<p class="Example"
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-TOP: 6pt; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none">TBS</p>

<h3><a id="Tier1Example2" name="Tier1Example2">B.2    Tier 1 Example
2</a></h3>

<p>This example shows the formatting of the X-KISS request and response for
the second example in section 2.2  above.</p>

<p><strong>Request Message</strong></p>

<p class="Example">TBS</p>

<p
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-TOP: 6pt; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none"><strong>Server
Response</strong></p>

<p class="Example"
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-TOP: 6pt; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none">TBS</p>

<h2><a id="Tier2" name="Tier2">B.3    Tier 2</a></h2>

<p>This example shows the formatting of the X-KISS request and response for
the example in section 2.2.1 above.</p>

<p><strong>Request Message</strong></p>

<p class="Example">TBS</p>

<p
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-TOP: 6pt; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none"><strong>Server
Response</strong></p>

<p class="Example"
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-TOP: 6pt; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none">TBS</p>

<h2>B.4 Registration of Client Generated Key Pair</h2>

<p><strong>Request Message</strong></p>

<p class="Example">TBS</p>

<p
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-TOP: 6pt; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none"><strong>Server
Response</strong></p>

<p class="Example"
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-TOP: 6pt; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none">TBS</p>

<h2><a id="RegistrationServerKey" name="RegistrationServerKey">B.5
Registration of server generated key</a></h2>

<p><strong>Request Message</strong></p>

<p class="Example">TBS</p>

<p
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-TOP: 6pt; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none"><strong>Server
Response</strong></p>

<p class="Example"
style="BORDER-RIGHT: medium none; BORDER-TOP: medium none; MARGIN-TOP: 6pt; BORDER-LEFT: medium none; BORDER-BOTTOM: medium none">TBS</p>

<h1 style="PAGE-BREAK-BEFORE: always">Appendix D References</h1>

<p class="Ref"><strong>[<a id="ref-KEYWORDS"
name="ref-KEYWORDS">KEYWORDS</a>]</strong> <a
href="http://www.ietf.org/rfc/rfc2119.txt">RFC 2119: Key words for use in
RFCs to Indicate Requirement Levels.</a> Best Current Practice. S. Bradner.
March 1997.</p>

<p class="Ref"><strong>[<a id="PKCS1" name="PKCS1">PKCS1</a>]</strong>
Kaliski, B., <em>PKCS #1: RSA Encryption Version 2.</em>0, RSA Laboratories,
also IETF RFC 2437, October 1998.</p>

<p class="Ref"><strong>[<a id="RFC-2104"
name="RFC-2104">RFC-2104</a>]</strong>   Krawczyk, H., Bellare, M. and R.
Canetti, <em>HMAC: Keyed Hashing for Message Authentication</em>, IETF  RFC
2104, February 1997.</p>

<p class="Ref"><strong>[<a id="SOAP" name="SOAP">SOAP</a>]</strong> D. Box, D
Ehnebuske, G. Kakivaya, A. Layman, N. Mendelsohn, H. Frystyk Nielsen, S
Thatte, D. Winer. <em>Simple Object Access Protocol (SOAP) 1.1</em>, W3C Note
08 May 2000, <a
href="http://www.w3.org/TR/SOAP/">http://www.w3.org/TR/SOAP/</a></p>

<p class="Ref"><strong>[<a id="WSDL" name="WSDL">WSDL</a>]</strong> E.
Christensen, F. Curbera, G. Meredith, S. Weerawarana, <em>Web Services
Description Language 1.1 (WSDL) 1.0</em>. W3C Note 15 March 2001, <a
href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a></p>

<p class="Ref"><strong>[<a id="XTASS" name="XTASS">XTASS</a>]</strong> P.
Hallam-Baker, <em>XML Trust Assertion Service Specification</em>, To Be
Published, January 2001</p>

<p class="Ref"><strong>[<a id="XML-SIG" name="XML-SIG">XML-SIG</a>]</strong> 
D. Eastlake, J. R., D. Solo, M. Bartel, J. Boyer , B. Fox , E. Simon.
<em>XML-Signature Syntax and Processing</em>, World Wide Web Consortium. <a
href="http://www.w3.org/TR/xmldsig-core/">http://www.w3.org/TR/xmldsig-core/</a></p>

<p class="Ref"><strong>[<a id="XML-SIG-XSD"
name="XML-SIG-XSD">XML-SIG-XSD</a>]</strong> XML Signature Schema available
from <a
href="http://www.w3.org/TR/2000/CR-xmldsig-core-20001031/xmldsig-core-schema.xsd">http://www.w3.org/TR/2000/CR-xmldsig-core-20001031/xmldsig-core-schema.xsd</a>.</p>

<p class="Ref"><strong>[<a id="XML-Enc" name="XML-Enc">XML-Enc</a>]</strong>
<em>XML Encryption Specification</em>, In development.</p>

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

<p class="Ref"><strong>[<a id="ref-XML-schema"
name="ref-XML-schema">XML-schema</a>]</strong> <a
href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/">XML Schema Part 1:
Structures</a> D. Beech, M. Maloney, N. Mendelsohn. W3C Recommendation, May
2001.</p>

<p class="Ref"><strong>[<a id="XML-Schema1"
name="XML-Schema1">XML-Schema1</a>]</strong> H. S. Thompson, D. Beech, M.
Maloney, N. Mendelsohn. <em>XML Schema Part 1: Structures</em>, W3C Working
Draft 22 September 2000, <a
href="http://www.w3.org/TR/2000/WD-xmlschema-1-20000922/">http://www.w3.org/TR/2000/WD-xmlschema-1-20000922/</a>,
latest draft at <a
href="http://www.w3.org/TR/xmlschema-1/">http://www.w3.org/TR/xmlschema-1/</a></p>

<p class="Ref"><strong>[<a id="XML-Schema2"
name="XML-Schema2">XML-Schema2</a>]</strong> P. V. Biron, A. Malhotra,
<em>XML Schema Part 2: Datatypes</em>; W3C Working Draft 22 September 2000,
<span style="COLOR: black"><a
href="http://www.w3.org/TR/2000/WD-xmlschema-2-20000922/">http://www.w3.org/TR/2000/WD-xmlschema-2-20000922/</a></span>,
latest draft at <a
href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a></p>
</body>
</html>