discontinued / server · Files

rfc2445.html 313 KB
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 2566 2567 2568 2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 2582 2583 2584 2585 2586 2587 2588 2589 2590 2591 2592 2593 2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751 2752 2753 2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942 2943 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3000 3001 3002 3003 3004 3005 3006 3007 3008 3009 3010 3011 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 3069 3070 3071 3072 3073 3074 3075 3076 3077 3078 3079 3080 3081 3082 3083 3084 3085 3086 3087 3088 3089 3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 3129 3130 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3482 3483 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3972 3973 3974 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390 4391 4392 4393 4394 4395 4396 4397 4398 4399 4400 4401 4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 4418 4419 4420 4421 4422 4423 4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4450 4451 4452 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510 4511 4512 4513 4514 4515 4516 4517 4518 4519 4520 4521 4522 4523 4524 4525 4526 4527 4528 4529 4530 4531 4532 4533 4534 4535 4536 4537 4538 4539 4540 4541 4542 4543 4544 4545 4546 4547 4548 4549 4550 4551 4552 4553 4554 4555 4556 4557 4558 4559 4560 4561 4562 4563 4564 4565 4566 4567 4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 4610 4611 4612 4613 4614 4615 4616 4617 4618 4619 4620 4621 4622 4623 4624 4625 4626 4627 4628 4629 4630 4631 4632 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644 4645 4646 4647 4648 4649 4650 4651 4652 4653 4654 4655 4656 4657 4658 4659 4660 4661 4662 4663 4664 4665 4666 4667 4668 4669 4670 4671 4672 4673 4674 4675 4676 4677 4678 4679 4680 4681 4682 4683 4684 4685 4686 4687 4688 4689 4690 4691 4692 4693 4694 4695 4696 4697 4698 4699 4700 4701 4702 4703 4704 4705 4706 4707 4708 4709 4710 4711 4712 4713 4714 4715 4716 4717 4718 4719 4720 4721 4722 4723 4724 4725 4726 4727 4728 4729 4730 4731 4732 4733 4734 4735 4736 4737 4738 4739 4740 4741 4742 4743 4744 4745 4746 4747 4748 4749 4750 4751 4752 4753 4754 4755 4756 4757 4758 4759 4760 4761 4762 4763 4764 4765 4766 4767 4768 4769 4770 4771 4772 4773 4774 4775 4776 4777 4778 4779 4780 4781 4782 4783 4784 4785 4786 4787 4788 4789 4790 4791 4792 4793 4794 4795 4796 4797 4798 4799 4800 4801 4802 4803 4804 4805 4806 4807 4808 4809 4810 4811 4812 4813 4814 4815 4816 4817 4818 4819 4820 4821 4822 4823 4824 4825 4826 4827 4828 4829 4830 4831 4832 4833 4834 4835 4836 4837 4838 4839 4840 4841 4842 4843 4844 4845 4846 4847 4848 4849 4850 4851 4852 4853 4854 4855 4856 4857 4858 4859 4860 4861 4862 4863 4864 4865 4866 4867 4868 4869 4870 4871 4872 4873 4874 4875 4876 4877 4878 4879 4880 4881 4882 4883 4884 4885 4886 4887 4888 4889 4890 4891 4892 4893 4894 4895 4896 4897 4898 4899 4900 4901 4902 4903 4904 4905 4906 4907 4908 4909 4910 4911 4912 4913 4914 4915 4916 4917 4918 4919 4920 4921 4922 4923 4924 4925 4926 4927 4928 4929 4930 4931 4932 4933 4934 4935 4936 4937 4938 4939 4940 4941 4942 4943 4944 4945 4946 4947 4948 4949 4950 4951 4952 4953 4954 4955 4956 4957 4958 4959 4960 4961 4962 4963 4964 4965 4966 4967 4968 4969 4970 4971 4972 4973 4974 4975 4976 4977 4978 4979 4980 4981 4982 4983 4984 4985 4986 4987 4988 4989 4990 4991 4992 4993 4994 4995 4996 4997 4998 4999 5000 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020 5021 5022 5023 5024 5025 5026 5027 5028 5029 5030 5031 5032 5033 5034 5035 5036 5037 5038 5039 5040 5041 5042 5043 5044 5045 5046 5047 5048 5049 5050 5051 5052 5053 5054 5055 5056 5057 5058 5059 5060 5061 5062 5063 5064 5065 5066 5067 5068 5069 5070 5071 5072 5073 5074 5075 5076 5077 5078 5079 5080 5081 5082 5083 5084 5085 5086 5087 5088 5089 5090 5091 5092 5093 5094 5095 5096 5097 5098 5099 5100 5101 5102 5103 5104 5105 5106 5107 5108 5109 5110 5111 5112 5113 5114 5115 5116 5117 5118 5119 5120 5121 5122 5123 5124 5125 5126 5127 5128 5129 5130 5131 5132 5133 5134 5135 5136 5137 5138 5139 5140 5141 5142 5143 5144 5145 5146 5147 5148 5149 5150 5151 5152 5153 5154 5155 5156 5157 5158 5159 5160 5161 5162 5163 5164 5165 5166 5167 5168 5169 5170 5171 5172 5173 5174 5175 5176 5177 5178 5179 5180 5181 5182 5183 5184 5185 5186 5187 5188 5189 5190 5191 5192 5193 5194 5195 5196 5197 5198 5199 5200 5201 5202 5203 5204 5205 5206 5207 5208 5209 5210 5211 5212 5213 5214 5215 5216 5217 5218 5219 5220 5221 5222 5223 5224 5225 5226 5227 5228 5229 5230 5231 5232 5233 5234 5235 5236 5237 5238 5239 5240 5241 5242 5243 5244 5245 5246 5247 5248 5249 5250 5251 5252 5253 5254 5255 5256 5257 5258 5259 5260 5261 5262 5263 5264 5265 5266 5267 5268 5269 5270 5271 5272 5273 5274 5275 5276 5277 5278 5279 5280 5281 5282 5283 5284 5285 5286 5287 5288 5289 5290 5291 5292 5293 5294 5295 5296 5297 5298 5299 5300 5301 5302 5303 5304 5305 5306 5307 5308 5309 5310 5311 5312 5313 5314 5315 5316 5317 5318 5319 5320 5321 5322 5323 5324 5325 5326 5327 5328 5329 5330 5331 5332 5333 5334 5335 5336 5337 5338 5339 5340 5341 5342 5343 5344 5345 5346 5347 5348 5349 5350 5351 5352 5353 5354 5355 5356 5357 5358 5359 5360 5361 5362 5363 5364 5365 5366 5367 5368 5369 5370 5371 5372 5373 5374 5375 5376 5377 5378 5379 5380 5381 5382 5383 5384 5385 5386 5387 5388 5389 5390 5391 5392 5393 5394 5395 5396 5397 5398 5399 5400 5401 5402 5403 5404 5405 5406 5407 5408 5409 5410 5411 5412 5413 5414 5415 5416 5417 5418 5419 5420 5421 5422 5423 5424 5425 5426 5427 5428 5429 5430 5431 5432 5433 5434 5435 5436 5437 5438 5439 5440 5441 5442 5443 5444 5445 5446 5447 5448 5449 5450 5451 5452 5453 5454 5455 5456 5457 5458 5459 5460 5461 5462 5463 5464 5465 5466 5467 5468 5469 5470 5471 5472 5473 5474 5475 5476 5477 5478 5479 5480 5481 5482 5483 5484 5485 5486 5487 5488 5489 5490 5491 5492 5493 5494 5495 5496 5497 5498 5499 5500 5501 5502 5503 5504 5505 5506 5507 5508 5509 5510 5511 5512 5513 5514 5515 5516 5517 5518 5519 5520 5521 5522 5523 5524 5525 5526 5527 5528 5529 5530 5531 5532 5533 5534 5535 5536 5537 5538 5539 5540 5541 5542 5543 5544 5545 5546 5547 5548 5549 5550 5551 5552 5553 5554 5555 5556 5557 5558 5559 5560 5561 5562 5563 5564 5565 5566 5567 5568 5569 5570 5571 5572 5573 5574 5575 5576 5577 5578 5579 5580 5581 5582 5583 5584 5585 5586 5587 5588 5589 5590 5591 5592 5593 5594 5595 5596 5597 5598 5599 5600 5601 5602 5603 5604 5605 5606 5607 5608 5609 5610 5611 5612 5613 5614 5615 5616 5617 5618 5619 5620 5621 5622 5623 5624 5625 5626 5627 5628 5629 5630 5631 5632 5633 5634 5635 5636 5637 5638 5639 5640 5641 5642 5643 5644 5645 5646 5647 5648 5649 5650 5651 5652 5653 5654 5655 5656 5657 5658 5659 5660 5661 5662 5663 5664 5665 5666 5667 5668 5669 5670 5671 5672 5673 5674 5675 5676 5677 5678 5679 5680 5681 5682 5683 5684 5685 5686 5687 5688 5689 5690 5691 5692 5693 5694 5695 5696 5697 5698 5699 5700 5701 5702 5703 5704 5705 5706 5707 5708 5709 5710 5711 5712 5713 5714 5715 5716 5717 5718 5719 5720 5721 5722 5723 5724 5725 5726 5727 5728 5729 5730 5731 5732 5733 5734 5735 5736 5737 5738 5739 5740 5741 5742 5743 5744 5745 5746 5747 5748 5749 5750 5751 5752 5753 5754 5755 5756 5757 5758 5759 5760 5761 5762 5763 5764 5765 5766 5767 5768 5769 5770 5771 5772 5773 5774 5775 5776 5777 5778 5779 5780 5781 5782 5783 5784 5785 5786 5787 5788 5789 5790 5791 5792 5793 5794 5795 5796 5797 5798 5799 5800 5801 5802 5803 5804 5805 5806 5807 5808 5809 5810 5811 5812 5813 5814 5815 5816 5817 5818 5819 5820 5821 5822 5823 5824 5825 5826 5827 5828 5829 5830 5831 5832 5833 5834 5835 5836 5837 5838 5839 5840 5841 5842 5843 5844 5845 5846 5847 5848 5849 5850 5851 5852 5853 5854 5855 5856 5857 5858 5859 5860 5861 5862 5863 5864 5865 5866 5867 5868 5869 5870 5871 5872 5873 5874 5875 5876 5877 5878 5879 5880 5881 5882 5883 5884 5885 5886 5887 5888 5889 5890 5891 5892 5893 5894 5895 5896 5897 5898 5899 5900 5901 5902 5903 5904 5905 5906 5907 5908 5909 5910 5911 5912 5913 5914 5915 5916 5917 5918 5919 5920 5921 5922 5923 5924 5925 5926 5927 5928 5929 5930 5931 5932 5933 5934 5935 5936 5937 5938 5939 5940 5941 5942 5943 5944 5945 5946 5947 5948 5949 5950 5951 5952 5953 5954 5955 5956 5957 5958 5959 5960 5961 5962 5963 5964 5965 5966 5967 5968 5969 5970 5971 5972 5973 5974 5975 5976 5977 5978 5979 5980 5981 5982 5983 5984 5985 5986 5987 5988 5989 5990 5991 5992 5993 5994 5995 5996 5997 5998 5999 6000 6001 6002 6003 6004 6005 6006 6007 6008 6009 6010 6011 6012 6013 6014 6015 6016 6017 6018 6019 6020 6021 6022 6023 6024 6025 6026 6027 6028 6029 6030 6031 6032 6033 6034 6035 6036 6037 6038 6039 6040 6041 6042 6043 6044 6045 6046 6047 6048 6049 6050 6051 6052 6053 6054 6055 6056 6057 6058 6059 6060 6061 6062 6063 6064 6065 6066 6067 6068 6069 6070 6071 6072 6073 6074 6075 6076 6077 6078 6079 6080 6081 6082 6083 6084 6085 6086 6087 6088 6089 6090 6091 6092 6093 6094 6095 6096 6097 6098 6099 6100 6101 6102 6103 6104 6105 6106 6107 6108 6109 6110 6111 6112 6113 6114 6115 6116 6117 6118 6119 6120 6121 6122 6123 6124 6125 6126 6127 6128 6129 6130 6131 6132 6133 6134 6135 6136 6137 6138 6139 6140 6141 6142 6143 6144 6145 6146 6147 6148 6149 6150 6151 6152 6153 6154 6155 6156 6157 6158 6159 6160 6161 6162 6163 6164 6165 6166 6167 6168 6169 6170 6171 6172 6173 6174 6175 6176 6177 6178 6179 6180 6181 6182 6183 6184 6185 6186 6187 6188 6189 6190 6191 6192 6193 6194 6195 6196 6197 6198 6199 6200 6201 6202 6203 6204 6205 6206 6207 6208 6209 6210 6211 6212 6213 6214 6215 6216 6217 6218 6219 6220 6221 6222 6223 6224 6225 6226 6227 6228 6229 6230 6231 6232 6233 6234 6235 6236 6237 6238 6239 6240 6241 6242 6243 6244 6245 6246 6247 6248 6249 6250 6251 6252 6253 6254 6255 6256 6257 6258 6259 6260 6261 6262 6263 6264 6265 6266 6267 6268 6269 6270 6271 6272 6273 6274 6275 6276 6277 6278 6279 6280 6281 6282 6283 6284 6285 6286 6287 6288 6289 6290 6291 6292 6293 6294 6295 6296 6297 6298 6299 6300 6301 6302 6303 6304 6305 6306 6307 6308 6309 6310 6311 6312 6313 6314 6315 6316 6317 6318 6319 6320 6321 6322 6323 6324 6325 6326 6327 6328 6329 6330 6331 6332 6333 6334 6335 6336 6337 6338 6339 6340 6341 6342 6343 6344 6345 6346 6347 6348 6349 6350 6351 6352 6353 6354 6355 6356 6357 6358 6359 6360 6361 6362 6363 6364 6365 6366 6367 6368 6369 6370 6371 6372 6373 6374 6375 6376 6377 6378 6379 6380 6381 6382 6383 6384 6385 6386 6387 6388 6389 6390 6391 6392 6393 6394 6395 6396 6397 6398 6399 6400 6401 6402 6403 6404 6405 6406 6407 6408 6409 6410 6411 6412 6413 6414 6415 6416 6417 6418 6419 6420 6421 6422 6423 6424 6425 6426 6427 6428 6429 6430 6431 6432 6433 6434 6435 6436 6437 6438 6439 6440 6441 6442 6443 6444 6445 6446 6447 6448 6449 6450 6451 6452 6453 6454 6455 6456 6457 6458 6459 6460 6461 6462 6463 6464 6465 6466 6467 6468 6469 6470 6471 6472 6473 6474 6475 6476 6477 6478 6479 6480 6481 6482 6483 6484 6485 6486 6487 6488 6489 6490 6491 6492 6493 6494 6495 6496 6497 6498 6499 6500 6501 6502 6503 6504 6505 6506 6507 6508 6509 6510 6511 6512 6513 6514 6515 6516 6517 6518 6519 6520 6521 6522 6523 6524 6525 6526 6527 6528 6529 6530 6531 6532 6533 6534 6535 6536 6537 6538 6539 6540 6541 6542 6543 6544 6545 6546 6547 6548 6549 6550 6551 6552 6553 6554 6555 6556 6557 6558 6559 6560 6561 6562 6563 6564 6565 6566 6567 6568 6569 6570 6571 6572 6573 6574 6575 6576 6577 6578 6579 6580 6581 6582 6583 6584 6585 6586 6587 6588 6589 6590 6591 6592 6593 6594 6595 6596 6597 6598 6599 6600 6601 6602 6603 6604 6605 6606 6607 6608 6609 6610 6611 6612 6613 6614 6615 6616 6617 6618 6619 6620 6621 6622 6623 6624 6625 6626 6627 6628 6629 6630 6631 6632 6633 6634 6635 6636 6637 6638 6639 6640 6641 6642 6643 6644 6645 6646 6647 6648 6649 6650 6651 6652 6653 6654 6655 6656 6657 6658 6659 6660 6661 6662 6663 6664 6665 6666 6667 6668 6669 6670 6671 6672 6673 6674 6675 6676 6677 6678 6679 6680 6681 6682 6683 6684 6685 6686 6687 6688 6689 6690 6691 6692 6693 6694 6695 6696 6697 6698 6699 6700 6701 6702 6703 6704 6705 6706 6707 6708 6709 6710 6711 6712 6713 6714 6715 6716 6717 6718 6719 6720 6721 6722 6723 6724 6725 6726 6727 6728 6729 6730 6731 6732 6733 6734 6735 6736 6737 6738 6739 6740 6741 6742 6743 6744 6745 6746 6747 6748 6749 6750 6751 6752 6753 6754 6755 6756 6757 6758 6759 6760 6761 6762 6763 6764 6765 6766 6767 6768 6769 6770 6771 6772 6773 6774 6775 6776 6777 6778 6779 6780 6781 6782 6783 6784 6785 6786 6787 6788 6789 6790 6791 6792 6793 6794 6795 6796 6797 6798 6799 6800 6801 6802 6803 6804 6805 6806 6807 6808 6809 6810 6811 6812 6813 6814 6815 6816 6817 6818 6819 6820 6821 6822 6823 6824 6825 6826 6827 6828 6829 6830 6831 6832 6833 6834 6835 6836 6837 6838 6839 6840 6841 6842 6843 6844 6845 6846 6847 6848 6849 6850 6851 6852 6853 6854 6855 6856 6857 6858 6859 6860 6861 6862 6863 6864 6865 6866 6867 6868 6869 6870 6871 6872 6873 6874 6875 6876 6877 6878 6879 6880 6881 6882 6883 6884 6885 6886 6887 6888 6889 6890 6891 6892 6893 6894 6895 6896 6897 6898 6899 6900 6901 6902 6903 6904 6905 6906 6907 6908 6909 6910 6911 6912 6913 6914 6915 6916 6917 6918 6919 6920 6921 6922 6923 6924 6925 6926 6927 6928 6929 6930 6931 6932 6933 6934 6935 6936 6937 6938 6939 6940 6941 6942 6943 6944 6945 6946 6947 6948 6949 6950 6951 6952 6953 6954 6955 6956 6957 6958 6959 6960 6961 6962 6963 6964 6965 6966 6967 6968 6969 6970 6971 6972 6973 6974 6975 6976 6977 6978 6979 6980 6981 6982 6983 6984 6985 6986 6987 6988 6989 6990 6991 6992 6993 6994 6995 6996 6997 6998 6999 7000 7001 7002 7003 7004 7005 7006 7007 7008 7009 7010 7011 7012 7013 7014 7015 7016 7017 7018 7019 7020 7021 7022 7023 7024 7025 7026 7027 7028 7029 7030 7031 7032 7033 7034 7035 7036 7037 7038 7039 7040 7041 7042 7043 7044 7045 7046 7047 7048 7049 7050 7051 7052 7053 7054 7055 7056 7057 7058 7059 7060 7061 7062 7063 7064 7065 7066 7067 7068 7069 7070 7071 7072 7073 7074 7075 7076 7077 7078 7079 7080 7081 7082 7083 7084 7085 7086 7087 7088 7089 7090 7091 7092 7093 7094 7095 7096 7097 7098 7099 7100 7101 7102 7103 7104 7105 7106 7107 7108 7109 7110 7111 7112 7113 7114 7115 7116 7117 7118 7119 7120 7121 7122 7123 7124 7125 7126 7127 7128 7129 7130 7131 7132 7133 7134 7135 7136 7137 7138 7139 7140 7141 7142 7143 7144 7145 7146 7147 7148 7149 7150 7151 7152 7153 7154 7155 7156 7157 7158 7159 7160 7161 7162 7163 7164 7165 7166 7167 7168 7169 7170 7171 7172 7173 7174 7175 7176 7177 7178 7179 7180 7181 7182 7183 7184 7185 7186 7187 7188 7189 7190 7191 7192 7193 7194 7195 7196 7197 7198 7199 7200 7201 7202 7203 7204 7205 7206 7207 7208 7209 7210 7211 7212 7213 7214 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226 7227 7228 7229 7230 7231 7232 7233 7234 7235 7236 7237 7238 7239 7240 7241 7242 7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 7253 7254 7255 7256 7257 7258 7259 7260 7261 7262 7263 7264 7265 7266 7267 7268 7269 7270 7271 7272 7273 7274 7275 7276 7277 7278 7279 7280 7281 7282 7283 7284 7285 7286 7287 7288 7289 7290 7291 7292 7293 7294 7295 7296 7297 7298 7299 7300 7301 7302 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7319 7320 7321 7322 7323 7324 7325 7326 7327 7328 7329 7330 7331 7332 7333 7334 7335 7336 7337 7338 7339 7340 7341 7342 7343 7344 7345 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7357 7358 7359 7360 7361 7362 7363 7364 7365 7366 7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7378 7379 7380 7381 7382 7383 7384 7385 7386 7387 7388 7389 7390 7391 7392 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7403 7404 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7424 7425 7426 7427 7428 7429 7430 7431 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7443 7444 7445 7446 7447 7448 7449 7450 7451 7452 7453 7454 7455 7456 7457 7458 7459 7460 7461 7462 7463 7464 7465 7466 7467 7468 7469 7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 7490 7491 7492 7493 7494 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7505 7506 7507 7508 7509 7510 7511 7512 7513 7514 7515 7516 7517 7518 7519 7520 7521 7522 7523 7524 7525 7526 7527 7528 7529 7530 7531 7532 7533 7534 7535 7536 7537 7538 7539 7540 7541 7542 7543 7544 7545 7546 7547 7548 7549 7550 7551 7552 7553 7554 7555 7556 7557 7558 7559 7560 7561 7562 7563 7564 7565 7566 7567 7568 7569 7570 7571 7572 7573 7574 7575 7576 7577 7578 7579 7580 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597 7598 7599 7600 7601 7602 7603 7604 7605 7606 7607 7608 7609 7610 7611 7612 7613 7614 7615 7616 7617 7618 7619 7620 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7632 7633 7634 7635 7636 7637 7638 7639 7640 7641 7642 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7659 7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7680 7681 7682 7683 7684 7685 7686 7687 7688 7689 7690 7691 7692 7693 7694 7695 7696 7697 7698 7699 7700 7701 7702 7703 7704 7705 7706 7707 7708 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720 7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7744 7745 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7765 7766 7767 7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782 7783 7784 7785 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795 7796 7797 7798 7799 7800 7801 7802 7803 7804 7805 7806 7807 7808 7809 7810 7811 7812 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7836 7837 7838 7839 7840 7841 7842 7843 7844 7845 7846 7847 7848 7849 7850 7851 7852 7853 7854 7855 7856 7857 7858 7859 7860 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 7874 7875 7876 7877 7878 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7896 7897 7898 7899 7900 7901 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7918 7919 7920 7921 7922 7923 7924 7925 7926 7927 7928 7929 7930 7931 7932 7933 7934 7935 7936 7937 7938 7939 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7957 7958 7959 7960 7961 7962 7963 7964 7965 7966 7967 7968 7969 7970 7971 7972 7973 7974 7975 7976 7977 7978 7979 7980 7981 7982 7983 7984 7985 7986 7987 7988 7989 7990 7991 7992 7993 7994 7995 7996 7997 7998 7999 8000 8001 8002 8003 8004 8005 8006 8007 8008 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8023 8024 8025 8026 8027 8028 8029 8030 8031 8032 8033 8034 8035 8036 8037 8038 8039 8040 8041 8042 8043 8044 8045 8046 8047 8048 8049 8050 8051 8052 8053 8054 8055 8056 8057 8058 8059 8060 8061 8062 8063 8064 8065 8066 8067 8068 8069 8070 8071 8072 8073 8074 8075 8076 8077 8078 8079 8080 8081 8082 8083 8084 8085 8086 8087 8088 8089 8090 8091 8092 8093 8094 8095 8096 8097 8098 8099 8100 8101 8102 8103 8104 8105 8106 8107 8108 8109 8110 8111 8112 8113 8114 8115 8116 8117 8118 8119 8120 8121 8122 8123 8124 8125 8126 8127 8128 8129 8130 8131 8132 8133 8134 8135 8136 8137 8138 8139 8140 8141 8142 8143 8144 8145 8146 8147 8148 8149 8150 8151 8152 8153 8154 8155 8156 8157 8158 8159 8160 8161 8162 8163 8164 8165 8166 8167 8168 8169 8170 8171 8172 8173 8174 8175 8176 8177 8178 8179 8180 8181 8182 8183 8184 8185 8186 8187 8188 8189 8190 8191 8192 8193 8194 8195 8196 8197 8198 8199 8200 8201 8202 8203 8204 8205 8206 8207 8208 8209 8210 8211 8212 8213 8214 8215 8216 8217 8218 8219 8220 8221 8222 8223 8224 8225 8226 8227 8228 8229 8230 8231 8232 8233 8234 8235 8236 8237 8238 8239 8240 8241 8242 8243 8244 8245 8246 8247 8248 8249 8250 8251 8252 8253 8254 8255 8256 8257 8258 8259 8260 8261 8262 8263 8264 8265 8266 8267 8268 8269 8270 8271 8272 8273 8274 8275 8276 8277 8278 8279 8280 8281 8282 8283 8284 8285 8286 8287 8288 8289 8290 8291 8292 8293 8294 8295 8296 8297 8298 8299 8300 8301 8302 8303 8304 8305 8306 8307 8308 8309 8310 8311 8312 8313 8314 8315 8316 8317 8318 8319 8320 8321 8322 8323 8324 8325 8326 8327 8328 8329 8330 8331 8332 8333 8334 8335 8336 8337 8338 8339 8340 8341 8342 8343 8344 8345 8346 8347 8348 8349 8350 8351 8352 8353 8354 8355 8356 8357 8358 8359 8360 8361 8362 8363 8364 8365 8366 8367 8368 8369 8370 8371 8372 8373 8374 8375 8376 8377 8378 8379 8380 8381 8382 8383 8384 8385 8386 8387 8388 8389 8390 8391 8392 8393 8394 8395 8396 8397 8398 8399 8400 8401 8402 8403 8404 8405 8406 8407 8408 8409 8410 8411 8412 8413 8414 8415 8416 8417 8418 8419 8420 8421 8422 8423 8424 8425 8426 8427 8428 8429 8430 8431 8432 8433 8434 8435 8436 8437 8438 8439 8440 8441 8442 8443 8444 8445 8446 8447 8448 8449 8450 8451 8452 8453 8454 8455 8456 8457 8458 8459 8460 8461 8462 8463 8464 8465 8466 8467 8468 8469 8470 8471 8472 8473 8474 8475 8476 8477 8478 8479 8480 8481 8482 8483 8484 8485 8486 8487 8488 8489 8490 8491 8492 8493 8494 8495 8496 8497 8498 8499 8500 8501 8502 8503 8504 8505 8506 8507 8508 8509 8510 8511 8512 8513 8514 8515 8516 8517 8518 8519 8520 8521 8522 8523 8524 8525 8526 8527 8528 8529 8530 8531 8532 8533 8534 8535 8536 8537 8538 8539 8540 8541 8542 8543 8544 8545 8546 8547 8548 8549 8550 8551 8552 8553 8554 8555 8556 8557 8558 8559 8560 8561 8562 8563 8564 8565 8566 8567 8568 8569 8570 8571 8572 8573 8574 8575 8576 8577 8578 8579 8580 8581 8582 8583 8584 8585 8586 8587 8588 8589 8590 8591 8592 8593 8594 8595 8596 8597 8598 8599 8600 8601 8602 8603 8604 8605 8606 8607 8608 8609 8610 8611 8612 8613 8614 8615 8616 8617 8618 8619 8620 8621 8622 8623 8624 8625 8626 8627 8628 8629 8630 8631 8632 8633 8634 8635 8636 8637 8638 8639 8640 8641 8642 8643 8644 8645 8646 8647 8648 8649 8650 8651 8652 8653 8654 8655 8656 8657 8658 8659 8660 8661 8662 8663 8664 8665 8666 8667 8668 8669 8670 8671 8672 8673 8674 8675 8676 8677 8678 8679 8680 8681 8682 8683 8684 8685 8686 8687 8688 8689 8690 8691 8692 8693 8694 8695 8696 8697 8698 8699 8700 8701 8702 8703 8704 8705 8706 8707 8708 8709 8710 8711 8712 8713 8714 8715 8716 8717 8718 8719 8720 8721 8722 8723 8724 8725 8726 8727 8728 8729 8730 8731 8732 8733 8734 8735 8736 8737 8738 8739 8740 8741 8742 8743 8744 8745 8746 8747 8748 8749 8750 8751 8752 8753 8754 8755 8756 8757 8758 8759 8760 8761 8762 8763 8764 8765 8766 8767 8768 8769 8770 8771 8772 8773 8774 8775 8776 8777 8778 8779 8780 8781 8782 8783 8784 8785 8786 8787 8788 8789 8790 8791 8792 8793 8794 8795 8796 8797 8798 8799 8800 8801 8802 8803 8804 8805 8806 8807 8808 8809 8810 8811 8812 8813 8814 8815 8816 8817 8818 8819 8820 8821 8822 8823 8824 8825 8826 8827 8828 8829 8830 8831 8832 8833 8834 8835 8836 8837 8838 8839 8840 8841 8842 8843 8844 8845 8846 8847 8848 8849 8850 8851 8852 8853 8854 8855 8856 8857 8858 8859 8860 8861 8862 8863 8864 8865 8866 8867 8868 8869 8870 8871 8872 8873 8874 8875 8876 8877 8878 8879 8880 8881 8882 8883 8884 8885 8886 8887 8888 8889 8890 8891 8892 8893 8894 8895 8896 8897 8898 8899 8900 8901 8902 8903 8904 8905 8906 8907 8908 8909 8910 8911 8912 8913 8914 8915 8916 8917 8918 8919 8920 8921 8922 8923 8924 8925 8926 8927 8928 8929 8930 8931 8932 8933 8934 8935 8936 8937 8938 8939 8940 8941 8942 8943 8944 8945 8946 8947 8948 8949 8950 8951 8952 8953 8954 8955 8956 8957 8958 8959 8960 8961 8962 8963 8964 8965 8966 8967 8968 8969 8970 8971 8972 8973 8974 8975 8976 8977 8978 8979 8980 8981 8982 8983 8984 8985 8986 8987 8988 8989 8990 8991 8992 8993 8994 8995 8996 8997 8998 8999 9000 9001 9002 9003 9004 9005 9006 9007 9008 9009 9010 9011 9012 9013 9014 9015 9016 9017 9018 9019 9020 9021 9022 9023 9024 9025 9026 9027 9028 9029 9030 9031 9032 9033 9034 9035 9036 9037 9038 9039 9040 9041 9042 9043 9044 9045 9046 9047 9048 9049 9050 9051 9052 9053 9054 9055 9056 9057 9058 9059 9060 9061 9062 9063 9064 9065 9066 9067 9068 9069 9070 9071 9072 9073 9074 9075 9076 9077 9078 9079 9080 9081 9082 9083 9084 9085 9086 9087 9088 9089 9090 9091 9092 9093 9094 9095 9096 9097 9098 9099 9100 9101 9102 9103 9104 9105 9106 9107 9108 9109 9110 9111 9112 9113 9114 9115 9116 9117 

<html xmlns='http://www.w3.org/1999/xhtml'>
<head profile='http://www.w3.org/2003/g/data-view'>
  <title>Internet Calendaring and Scheduling Core Object Specification (iCalendar)</title>
  <link rel="transformation"
    href="http://www.w3.org/2002/12/cal/webize2445.xsl"/>
  <style type="text/css">
  dd.Example {   border-style: solid;  border-color: #d0dbe7;  border-width: 0 0 0 .25em;  padding-left: 0.5em;

  </style>
</head>
<body>
<table>
<tr><td>Network Working Group<br />
Request for Comments: 2445<br />
Category: Standards Track<br />
</td>
<td>F. Dawson<br />Lotus<br />D. Stenerson<br />Microsoft</td>
</tr>
<tr><td>&#160;</td><td>November 1998</td></tr>
</table>
<h1>Internet Calendaring and Scheduling Core Object Specification (iCalendar)</h1>
<address>
$Revision: 1.20 $ of $Date: 2005/11/09 23:10:48 $
derived from <a href="http://www.ietf.org/rfc/rfc2445.txt">rfc2445.txt</a>
and enhanced
for <a href="http://www.w3.org/2004/01/rdxh/spec">gleaning formal description</a>
using <a href="slurpIcalSpec.py">slurpIcalSpec.py</a>
by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a>
</address>


<div><h2>Status of this Memo</h2>
<p>
   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.
</p>
</div><div><h2>Copyright Notice</h2>
<p>
   Copyright (C) The Internet Society (1998).  All Rights Reserved.
</p>
</div><div><h2>Abstract</h2>
<p>
   There is a clear need to provide and deploy interoperable calendaring
   and scheduling services for the Internet. Current group scheduling
   and Personal Information Management (PIM) products are being extended
   for use across the Internet, today, in proprietary ways. This memo
   has been defined to provide the definition of a common format for
   openly exchanging calendaring and scheduling information across the
   Internet.
</p>
<p>
   This memo is formatted as a registration for a MIME media type per
   <a href='#ref_RFC_2048'>[RFC 2048]</a>. However, the format in this memo is equally applicable
   for use outside of a MIME message content type.
</p>
<p>
   The proposed media type value is 'text/calendar'. This string would
   label a media type containing calendaring and scheduling information
   encoded as text characters formatted in a manner outlined below.
</p>
<p>
   This MIME media type provides a standard content type for capturing
   calendar event, to-do and journal entry information. It also can be
   used to convey free/busy time information. The content type is
   suitable as a MIME message entity that can be transferred over MIME
   based email systems, using HTTP or some other Internet transport. In
</p>
<p>
   addition, the content type is useful as an object for interactions
   between desktop applications using the operating system clipboard,
   drag/drop or file systems capabilities.
</p>
<p>
   This memo is based on the earlier work of the vCalendar specification
   for the exchange of personal calendaring and scheduling information.
   In order to avoid confusion with this referenced work, this memo is
   to be known as the iCalendar specification.
</p>
<p>
   This memo defines the format for specifying iCalendar object methods.
   An iCalendar object method is a set of usage constraints for the
   iCalendar object. For example, these methods might define scheduling
   messages that request an event be scheduled, reply to an event
   request, send a cancellation notice for an event, modify or replace
   the definition of an event, provide a counter proposal for an
   original event request, delegate an event request to another
   individual, request free or busy time, reply to a free or busy time
   request, or provide similar scheduling messages for a to-do or
   journal entry calendar component. The iCalendar Transport-indendent
   Interoperability Protocol (iTIP) defined in <a href='#ref_ITIP'>[ITIP]</a> is one such
   scheduling protocol.
</p>
</div><div><h2>Table of Contents</h2>
<ul type='none'>
<li><a href='#sec1'>1 Introduction</a></li>
<li><a href='#sec2'>2 Basic Grammar and Conventions</a></li>
<li><a href='#sec2.1'>2.1 Formatting Conventions </a></li>
<li><a href='#sec2.2'>2.2 Related Memos </a></li>
<li><a href='#sec2.3'>2.3 International Considerations </a></li>
<li><a href='#sec3'>3 Registration Information</a></li>
<li><a href='#sec3.1'>3.1 Content Type </a></li>
<li><a href='#sec3.2'>3.2 Parameters </a></li>
<li><a href='#sec3.3'>3.3 Content Header Fields </a></li>
<li><a href='#sec3.4'>3.4 Encoding Considerations </a></li>
<li><a href='#sec3.5'>3.5 Security Considerations </a></li>
<li><a href='#sec3.6'>3.6 Interoperability Considerations </a></li>
<li><a href='#sec3.7'>3.7 Applications Which Use This Media Type </a></li>
<li><a href='#sec3.8'>3.8 Additional Information </a></li>
<li><a href='#sec3.9'>3.9 Magic Numbers </a></li>
<li><a href='#sec3.10'>3.10 File Extensions </a></li>
<li><a href='#sec3.11'>3.11 Contact for Further Information </a></li>
<li><a href='#sec3.12'>3.12 Intended Usage </a></li>
<li><a href='#sec3.13'>3.13 Authors/Change Controllers </a></li>
<li><a href='#sec4'>4 iCalendar Object Specification</a></li>
<li><a href='#sec4.1'>4.1 Content Lines </a></li>
<li><a href='#sec4.1.1'>4.1.1 List and Field Separators </a></li>
<li><a href='#sec4.1.2'>4.1.2 Multiple Values </a></li>
<li><a href='#sec4.1.3'>4.1.3 Binary Content </a></li>
<li><a href='#sec4.1.4'>4.1.4 Character Set </a></li>
<li><a href='#sec4.2'>4.2 Property Parameters </a></li>
<li><a href='#sec4.2.1'>4.2.1 Alternate Text Representation </a></li>
<li><a href='#sec4.2.2'>4.2.2 Common Name </a></li>
<li><a href='#sec4.2.3'>4.2.3 Calendar User Type </a></li>
<li><a href='#sec4.2.4'>4.2.4 Delegators </a></li>
<li><a href='#sec4.2.5'>4.2.5 Delegatees </a></li>
<li><a href='#sec4.2.6'>4.2.6 Directory Entry Reference </a></li>
<li><a href='#sec4.2.7'>4.2.7 Inline Encoding </a></li>
<li><a href='#sec4.2.8'>4.2.8 Format Type </a></li>
<li><a href='#sec4.2.9'>4.2.9 Free/Busy Time Type </a></li>
<li><a href='#sec4.2.10'>4.2.10 Language </a></li>
<li><a href='#sec4.2.11'>4.2.11 Group or List Membership </a></li>
<li><a href='#sec4.2.12'>4.2.12 Participation Status </a></li>
<li><a href='#sec4.2.13'>4.2.13 Recurrence Identifier Range </a></li>
<li><a href='#sec4.2.14'>4.2.14 Alarm Trigger Relationship </a></li>
<li><a href='#sec4.2.15'>4.2.15 Relationship Type </a></li>
<li><a href='#sec4.2.16'>4.2.16 Participation Role </a></li>
<li><a href='#sec4.2.17'>4.2.17 RSVP Expectation </a></li>
<li><a href='#sec4.2.18'>4.2.18 Sent By </a></li>
<li><a href='#sec4.2.19'>4.2.19 Time Zone Identifier </a></li>
<li><a href='#sec4.2.20'>4.2.20 Value Data Types </a></li>
<li><a href='#sec4.3'>4.3 Property Value Data Types </a></li>
<li><a href='#sec4.3.1'>4.3.1 Binary </a></li>
<li><a href='#sec4.3.2'>4.3.2 Boolean </a></li>
<li><a href='#sec4.3.3'>4.3.3 Calendar User Address </a></li>
<li><a href='#sec4.3.4'>4.3.4 Date </a></li>
<li><a href='#sec4.3.5'>4.3.5 Date-Time </a></li>
<li><a href='#sec4.3.6'>4.3.6 Duration </a></li>
<li><a href='#sec4.3.7'>4.3.7 Float </a></li>
<li><a href='#sec4.3.8'>4.3.8 Integer </a></li>
<li><a href='#sec4.3.9'>4.3.9 Period of Time </a></li>
<li><a href='#sec4.3.10'>4.3.10 Recurrence Rule </a></li>
<li><a href='#sec4.3.11'>4.3.11 Text </a></li>
<li><a href='#sec4.3.12'>4.3.12 Time </a></li>
<li><a href='#sec4.3.13'>4.3.13 URI </a></li>
<li><a href='#sec4.3.14'>4.3.14 UTC Offset </a></li>
<li><a href='#sec4.4'>4.4 iCalendar Object </a></li>
<li><a href='#sec4.5'>4.5 Property </a></li>
<li><a href='#sec4.6'>4.6 Calendar Components </a></li>
<li><a href='#sec4.6.1'>4.6.1 Event Component </a></li>
<li><a href='#sec4.6.2'>4.6.2 To-do Component </a></li>
<li><a href='#sec4.6.3'>4.6.3 Journal Component </a></li>
<li><a href='#sec4.6.4'>4.6.4 Free/Busy Component </a></li>
<li><a href='#sec4.6.5'>4.6.5 Time Zone Component </a></li>
<li><a href='#sec4.6.6'>4.6.6 Alarm Component </a></li>
<li><a href='#sec4.7'>4.7 Calendar Properties </a></li>
<li><a href='#sec4.7.1'>4.7.1 Calendar Scale </a></li>
<li><a href='#sec4.7.2'>4.7.2 Method </a></li>
<li><a href='#sec4.7.3'>4.7.3 Product Identifier </a></li>
<li><a href='#sec4.7.4'>4.7.4 Version </a></li>
<li><a href='#sec4.8'>4.8 Component Properties </a></li>
<li><a href='#sec4.8.1'>4.8.1 Descriptive Component Properties </a></li>
<li><a href='#sec4.8.1.1'>4.8.1.1 Attachment </a></li>
<li><a href='#sec4.8.1.2'>4.8.1.2 Categories </a></li>
<li><a href='#sec4.8.1.3'>4.8.1.3 Classification </a></li>
<li><a href='#sec4.8.1.4'>4.8.1.4 Comment </a></li>
<li><a href='#sec4.8.1.5'>4.8.1.5 Description </a></li>
<li><a href='#sec4.8.1.6'>4.8.1.6 Geographic Position </a></li>
<li><a href='#sec4.8.1.7'>4.8.1.7 Location </a></li>
<li><a href='#sec4.8.1.8'>4.8.1.8 Percent Complete </a></li>
<li><a href='#sec4.8.1.9'>4.8.1.9 Priority </a></li>
<li><a href='#sec4.8.1.10'>4.8.1.10 Resources </a></li>
<li><a href='#sec4.8.1.11'>4.8.1.11 Status </a></li>
<li><a href='#sec4.8.1.12'>4.8.1.12 Summary </a></li>
<li><a href='#sec4.8.2'>4.8.2 Date and Time Component Properties </a></li>
<li><a href='#sec4.8.2.1'>4.8.2.1 Date/Time Completed </a></li>
<li><a href='#sec4.8.2.2'>4.8.2.2 Date/Time End </a></li>
<li><a href='#sec4.8.2.3'>4.8.2.3 Date/Time Due </a></li>
<li><a href='#sec4.8.2.4'>4.8.2.4 Date/Time Start </a></li>
<li><a href='#sec4.8.2.5'>4.8.2.5 Duration </a></li>
<li><a href='#sec4.8.2.6'>4.8.2.6 Free/Busy Time </a></li>
<li><a href='#sec4.8.2.7'>4.8.2.7 Time Transparency </a></li>
<li><a href='#sec4.8.3'>4.8.3 Time Zone Component Properties </a></li>
<li><a href='#sec4.8.3.1'>4.8.3.1 Time Zone Identifier </a></li>
<li><a href='#sec4.8.3.2'>4.8.3.2 Time Zone Name </a></li>
<li><a href='#sec4.8.3.3'>4.8.3.3 Time Zone Offset From </a></li>
<li><a href='#sec4.8.3.4'>4.8.3.4 Time Zone Offset To </a></li>
<li><a href='#sec4.8.3.5'>4.8.3.5 Time Zone URL </a></li>
<li><a href='#sec4.8.4'>4.8.4 Relationship Component Properties </a></li>
<li><a href='#sec4.8.4.1'>4.8.4.1 Attendee </a></li>
<li><a href='#sec4.8.4.2'>4.8.4.2 Contact </a></li>
<li><a href='#sec4.8.4.3'>4.8.4.3 Organizer </a></li>
<li><a href='#sec4.8.4.4'>4.8.4.4 Recurrence ID </a></li>
<li><a href='#sec4.8.4.5'>4.8.4.5 Related To </a></li>
<li><a href='#sec4.8.4.6'>4.8.4.6 Uniform Resource Locator </a></li>
<li><a href='#sec4.8.4.7'>4.8.4.7 Unique Identifier </a></li>
<li><a href='#sec4.8.5'>4.8.5 Recurrence Component Properties </a></li>
<li><a href='#sec4.8.5.1'>4.8.5.1 Exception Date/Times </a></li>
<li><a href='#sec4.8.5.2'>4.8.5.2 Exception Rule </a></li>
<li><a href='#sec4.8.5.3'>4.8.5.3 Recurrence Date/Times </a></li>
<li><a href='#sec4.8.5.4'>4.8.5.4 Recurrence Rule </a></li>
<li><a href='#sec4.8.6'>4.8.6 Alarm Component Properties </a></li>
<li><a href='#sec4.8.6.1'>4.8.6.1 Action </a></li>
<li><a href='#sec4.8.6.2'>4.8.6.2 Repeat Count </a></li>
<li><a href='#sec4.8.6.3'>4.8.6.3 Trigger </a></li>
<li><a href='#sec4.8.7'>4.8.7 Change Management Component Properties </a></li>
<li><a href='#sec4.8.7.1'>4.8.7.1 Date/Time Created </a></li>
<li><a href='#sec4.8.7.2'>4.8.7.2 Date/Time Stamp </a></li>
<li><a href='#sec4.8.7.3'>4.8.7.3 Last Modified </a></li>
<li><a href='#sec4.8.7.4'>4.8.7.4 Sequence Number </a></li>
<li><a href='#sec4.8.8'>4.8.8 Miscellaneous Component Properties </a></li>
<li><a href='#sec4.8.8.1'>4.8.8.1 Non-standard Properties </a></li>
<li><a href='#sec4.8.8.2'>4.8.8.2 Request Status </a></li>
<li><a href='#sec5'>5 iCalendar Object Examples</a></li>
<li><a href='#sec6'>6 Recommended Practices</a></li>
<li><a href='#sec7'>7 Registration of Content Type Elements</a></li>
<li><a href='#sec7.1'>7.1 Registration of New and Modified iCalendar Object Methods </a></li>
<li><a href='#sec7.2'>7.2 Registration of New Properties </a></li>
<li><a href='#sec7.2.1'>7.2.1 Define the property </a></li>
<li><a href='#sec7.2.2'>7.2.2 Post the Property definition </a></li>
<li><a href='#sec7.2.3'>7.2.3 Allow a comment period </a></li>
<li><a href='#sec7.2.4'>7.2.4 Submit the property for approval </a></li>
<li><a href='#sec7.3'>7.3 Property Change Control </a></li>
<li><a href='#sec8'>8 References</a></li>
<li><a href='#sec9'>9 Acknowledgments</a></li>
<li><a href='#sec10'>10 Authors' and Chairs' Addresses</a></li>
<li><a href='#sec11'>11 Full Copyright Statement</a></li>
</ul></div><div><h2 id='sec1'>1 Introduction</h2>
<pre>
   The use of calendaring and scheduling has grown considerably in the
   last decade. Enterprise and inter-enterprise business has become
   dependent on rapid scheduling of events and actions using this
   information technology. However, the longer term growth of
   calendaring and scheduling, is currently limited by the lack of
   Internet standards for the message content types that are central to
   these knowledgeware applications. This memo is intended to progress
   the level of interoperability possible between dissimilar calendaring
   and scheduling applications. This memo defines a MIME content type
   for exchanging electronic calendaring and scheduling information. The
   Internet Calendaring and Scheduling Core Object Specification, or
   iCalendar, allows for the capture and exchange of information
   normally stored within a calendaring and scheduling application; such
   as a Personal Information Manager (PIM) or a Group Scheduling
   product.

   The iCalendar format is suitable as an exchange format between
   applications or systems. The format is defined in terms of a MIME
   content type. This will enable the object to be exchanged using
   several transports, including but not limited to SMTP, HTTP, a file
   system, desktop interactive protocols such as the use of a memory-
   based clipboard or drag/drop interactions, point-to-point
   asynchronous communication, wired-network transport, or some form of

   unwired transport such as infrared might also be used.

   The memo also provides for the definition of iCalendar object methods
   that will map this content type to a set of messages for supporting
   calendaring and scheduling operations such as requesting, replying
   to, modifying, and canceling meetings or appointments, to-dos and
   journal entries. The iCalendar object methods can be used to define
   other calendaring and scheduling operations such a requesting for and
   replying with free/busy time data. Such a scheduling protocol is
   defined in the iCalendar Transport-independent Interoperability
   Protocol (iTIP) defined in <a href='#ref_ITIP'>[ITIP]</a>.

   The memo also includes a formal grammar for the content type based on
   the Internet ABNF defined in <a href='#ref_RFC_2234'>[RFC 2234]</a>. This ABNF is required for
   the implementation of parsers and to serve as the definitive
   reference when ambiguities or questions arise in interpreting the
   descriptive prose definition of the memo.

</pre>
</div>
<div><h2 id='sec2'>2 Basic Grammar and Conventions</h2>
<pre>
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY" and
   "OPTIONAL" in this document are to be interoperated as described in
   <a href='#ref_RFC_2119'>[RFC 2119]</a>.

   This memo makes use of both a descriptive prose and a more formal
   notation for defining the calendaring and scheduling format.

   The notation used in this memo is the ABNF notation of <a href='#ref_RFC_2234'>[RFC 2234]</a>.
   Readers intending on implementing this format defined in this memo
   should be familiar with this notation in order to properly interpret
   the specifications of this memo.

   All numeric and hexadecimal values used in this memo are given in
   decimal notation.

   All names of properties, property parameters, enumerated property
   values and property parameter values are case-insensitive. However,
   all other property values are case-sensitive, unless otherwise
   stated.

        Note: All indented editorial notes, such as this one, are
        intended to provide the reader with additional information. The
        information is not essential to the building of an
        implementation conformant with this memo. The information is
        provided to highlight a particular feature or characteristic of
        the memo.

   The format for the iCalendar object is based on the syntax of the
   <a href='#ref_RFC_2425'>[RFC 2425]</a> content type. While the iCalendar object is not a profile
   of the <a href='#ref_RFC_2425'>[RFC 2425]</a> content type, it does reuse a number of the
   elements from the <a href='#ref_RFC_2425'>[RFC 2425]</a> specification.

</pre>
</div>
<div><h2 id='sec2.1'>2.1 Formatting Conventions</h2>
<pre>
   The mechanisms defined in this memo are defined in prose. Many of the
   terms used to describe these have common usage that is different than
   the standards usage of this memo. In order to reference within this
   memo elements of the calendaring and scheduling model, core object
   (this memo) or interoperability protocol <a href='#ref_ITIP'>[ITIP]</a> some formatting
   conventions have been used. Calendaring and scheduling roles are
   referred to in quoted-strings of text with the first character of
   each word in upper case. For example, "Organizer" refers to a role of
   a "Calendar User" within the scheduling protocol defined by <a href='#ref_ITIP'>[ITIP]</a>.
   Calendar components defined by this memo are referred to with
   capitalized, quoted-strings of text. All calendar components start
   with the letter "V". For example, "VEVENT" refers to the event
   calendar component, "VTODO" refers to the to-do calendar component
   and "VJOURNAL" refers to the daily journal calendar component.
   Scheduling methods defined by <a href='#ref_ITIP'>[ITIP]</a> are referred to with
   capitalized, quoted-strings of text. For example, "REQUEST" refers to
   the method for requesting a scheduling calendar component be created
   or modified, "REPLY" refers to the method a recipient of a request
   uses to update their status with the "Organizer" of the calendar
   component.

   The properties defined by this memo are referred to with capitalized,
   quoted-strings of text, followed by the word "property". For example,
   "ATTENDEE" property refers to the iCalendar property used to convey
   the calendar address of a calendar user. Property parameters defined
   by this memo are referred to with lowercase, quoted-strings of text,
   followed by the word "parameter". For example, "value" parameter
   refers to the iCalendar property parameter used to override the
   default data type for a property value. Enumerated values defined by
   this memo are referred to with capitalized text, either alone or
   followed by the word "value". For example, the "MINUTELY" value can
   be used with the "FREQ" component of the "RECUR" data type to specify
   repeating components based on an interval of one minute or more.

</pre>
</div>
<div><h2 id='sec2.2'>2.2 Related Memos</h2>
<pre>
   Implementers will need to be familiar with several other memos that,
   along with this memo, form a framework for Internet calendaring and
   scheduling standards. This memo, ICAL], specifies a core
   specification of objects, data types, properties and property
   parameters.

   <a href='#ref_ITIP'>[ITIP]</a> - specifies an interoperability protocol for scheduling
   between different implementations;

   <a href='#ref_IMIP'>[IMIP]</a> specifies an Internet email binding for <a href='#ref_ITIP'>[ITIP]</a>.

   This memo does not attempt to repeat the specification of concepts or
   definitions from these other memos. Where possible, references are
   made to the memo that provides for the specification of these
   concepts or definitions.

</pre>
</div>
<div><h2 id='sec2.3'>2.3 International Considerations</h2>
<pre>
   In the rest of this document, descriptions of characters are of the
   form "character name (codepoint)", where "codepoint" is from the US-
   ASCII character set. The "character name" is the authoritative
   description; (codepoint) is a reference to that character in US-ASCII
   or US-ASCII compatible sets (for example the ISO-8859-x family, UTF-
   8, ISO-2022-xx, KOI8-R). If a non-US-ASCII compatible character set
   is used, appropriate code-point from that character set MUST be
   chosen instead. Use of non-US-ASCII-compatible character sets is NOT
   recommended.

</pre>
</div>
<div><h2 id='sec3'>3 Registration Information</h2>
<pre>
   The Calendaring and Scheduling Core Object Specification is intended
   for use as a MIME content type. However, the implementation of the
   memo is in no way limited solely as a MIME content type.

</pre>
</div>
<div><h2 id='sec3.1'>3.1 Content Type</h2>
<pre>
   The following text is intended to register this memo as the MIME
   content type "text/calendar".

     To: ietf-types@uninett.no

     Subject: Registration of MIME content type text/calendar.

     MIME media type name: text

     MIME subtype name: calendar

</pre>
</div>
<div><h2 id='sec3.2'>3.2 Parameters</h2>
<pre>
   Required parameters: none

   Optional parameters: charset, method, component and optinfo

   The "charset" parameter is defined in <a href='#ref_RFC_2046'>[RFC 2046]</a> for other body
   parts. It is used to identify the default character set used within
   the body part.

   The "method" parameter is used to convey the iCalendar object method
   or transaction semantics for the calendaring and scheduling
   information. It also is an identifier for the restricted set of
   properties and values that the iCalendar object consists of. The
   parameter is to be used as a guide for applications interpreting the
   information contained within the body part. It SHOULD NOT be used to
   exclude or require particular pieces of information unless the
   identified method definition specifically calls for this behavior.
   Unless specifically forbidden by a particular method definition, a
   text/calendar content type can contain any set of properties
   permitted by the Calendaring and Scheduling Core Object
   Specification. The "method" parameter MUST be the same value as that
   specified in the "METHOD" component property in the iCalendar object.
   If one is present, the other MUST also be present.

   The value for the "method" parameter is defined as follows:

        method  = 1*(ALPHA / DIGIT / "-")
        ; IANA registered iCalendar object method

   The "component" parameter conveys the type of iCalendar calendar
   component within the body part. If the iCalendar object contains more
   than one calendar component type, then multiple component parameters
   MUST be specified.

   The value for the "component" parameter is defined as follows:

        component       = ("VEVENT" / "VTODO" / "VJOURNAL" / "VFREEBUSY"
                        / "VTIMEZONE" / x-name / iana-token)

   The "optinfo" parameter conveys optional information about the
   iCalendar object within the body part. This parameter can only
   specify semantics already specified by the iCalendar object and that
   can be otherwise determined by parsing the body part. In addition,
   the optional information specified by this parameter MUST be
   consistent with that information specified by the iCalendar object.
   For example, it can be used to convey the "Attendee" response status
   to a meeting request. The parameter value consists of a string value.

   The parameter can be specified multiple times.

   This parameter MAY only specify semantics already specified by the
   iCalendar object and that can be otherwise determined by parsing the
   body part.

   The value for the "optinfo" parameter is defined as follows:

        optinfo = infovalue / qinfovalue

        infovalue       = iana-token / x-name

        qinfovalue      = DQUOTE (infovalue) DQUOTE

</pre>
</div>
<div><h2 id='sec3.3'>3.3 Content Header Fields</h2>
<pre>
   Optional content header fields: Any header fields defined by RFC
   2045].

</pre>
</div>
<div><h2 id='sec3.4'>3.4 Encoding Considerations</h2>
<pre>
   This MIME content type can contain 8bit characters, so the use of
   quoted-printable or BASE64 MIME content-transfer-encodings might be
   necessary when iCalendar objects are transferred across protocols
   restricted to the 7bit repertoire. Note that a text valued property
   in the content entity can also have content encoding of special
   characters using a BACKSLASH character (US-ASCII decimal 92)
   escapement technique. This means that content values can end up
   encoded twice.

</pre>
</div>
<div><h2 id='sec3.5'>3.5 Security Considerations</h2>
<pre>
   SPOOFING - - In this memo, the "Organizer" is the only person
   authorized to make changes to an existing "VEVENT", "VTODO",
   "VJOURNAL" calendar component and redistribute the updates to the
   "Attendees". An iCalendar object that maliciously changes or cancels
   an existing "VEVENT", "VTODO" or "VJOURNAL" or "VFREEBUSY" calendar
   component might be constructed by someone other than the "Organizer"
   and sent to the "Attendees". In addition in this memo, other than the
   "Organizer", an "Attendee" of a "VEVENT", "VTODO", "VJOURNAL"
   calendar component is the only other person authorized to update any
   parameter associated with their "ATTENDEE" property and send it to
   the "Organizer". An iCalendar object that maliciously changes the
   "ATTENDEE" parameters can be constructed by someone other than the
   real "Attendee" and sent to the "Organizer".

   PROCEDURAL ALARMS - - An iCalendar object can be created that
   contains a "VEVENT" and "VTODO" calendar component with "VALARM"
   calendar components. The "VALARM" calendar component can be of type
   PROCEDURE and can have an attachment containing some sort of
   executable program. Implementations that incorporate these types of
   alarms are subject to any virus or malicious attack that might occur
   as a result of executing the attachment.

   ATTACHMENTS - - An iCalendar object can include references to Uniform
   Resource Locators that can be programmed resources.

   Implementers and users of this memo should be aware of the network
   security implications of accepting and parsing such information. In
   addition, the security considerations observed by implementations of
   electronic mail systems should be followed for this memo.

</pre>
</div>
<div><h2 id='sec3.6'>3.6 Interoperability Considerations</h2>
<pre>
   This MIME content type is intended to define a common format for
   conveying calendaring and scheduling information between different
   systems. It is heavily based on the earlier <a href='#ref_VCAL'>[VCAL]</a> industry
   specification.

</pre>
</div>
<div><h2 id='sec3.7'>3.7 Applications Which Use This Media Type</h2>
<pre>
   This content-type is designed for widespread use by Internet
   calendaring and scheduling applications. In addition, applications in
   the workflow and document management area might find this content-
   type applicable. The <a href='#ref_ITIP'>[ITIP]</a> and <a href='#ref_IMIP'>[IMIP]</a> Internet protocols directly
   use this content-type also. Future work on an Internet calendar
   access protocol will utilize this content-type too.

</pre>
</div>
<div><h2 id='sec3.8'>3.8 Additional Information</h2>
<pre>
   This memo defines this content-type.

</pre>
</div>
<div><h2 id='sec3.9'>3.9 Magic Numbers</h2>
<pre>
   None.

</pre>
</div>
<div><h2 id='sec3.10'>3.10 File Extensions</h2>
<pre>
   The file extension of "ics" is to be used to designate a file
   containing (an arbitrary set of) calendaring and scheduling
   information consistent with this MIME content type.

   The file extension of "ifb" is to be used to designate a file
   containing free or busy time information consistent with this MIME
   content type.

   Macintosh file type codes: The file type code of "iCal" is to be used
   in Apple MacIntosh operating system environments to designate a file
   containing calendaring and scheduling information consistent with
   this MIME media type.

   The file type code of "iFBf" is to be used in Apple MacIntosh
   operating system environments to designate a file containing free or
   busy time information consistent with this MIME media type.

</pre>
</div>
<div><h2 id='sec3.11'>3.11 Contact for Further Information</h2>
<pre>
   Frank Dawson
   6544 Battleford Drive
   Raleigh, NC 27613-3502
   919-676-9515 (Telephone)
   919-676-9564 (Data/Facsimile)
   Frank_Dawson@Lotus.com (Internet Mail)

   Derik Stenerson
   One Microsoft Way
   Redmond, WA  98052-6399
   425-936-5522 (Telephone)
   425-936-7329 (Facsimile)
   deriks@microsoft.com (Internet Mail)

</pre>
</div>
<div><h2 id='sec3.12'>3.12 Intended Usage</h2>
<pre>
   COMMON

</pre>
</div>
<div><h2 id='sec3.13'>3.13 Authors/Change Controllers</h2>
<pre>
   Frank Dawson
   6544 Battleford Drive
   Raleigh, NC 27613-3502
   919-676-9515 (Telephone)
   919-676-9564 (Data/Facsimile)
   Frank_Dawson@Lotus.com (Internet Mail)

   Derik Stenerson
   One Microsoft Way
   Redmond, WA  98052-6399
   425-936-5522 (Telephone)
   425-936-7329 (Facsimile)
   deriks@microsoft.com (Internet Mail)

</pre>
</div>
<div><h2 id='sec4'>4 iCalendar Object Specification</h2>
<pre>
   The following sections define the details of a Calendaring and
   Scheduling Core Object Specification. This information is intended to
   be an integral part of the MIME content type registration. In
   addition, this information can be used independent of such content
   registration. In particular, this memo has direct applicability for
   use as a calendaring and scheduling exchange format in file-, memory-
   or network-based transport mechanisms.

</pre>
</div>
<div><h2 id='sec4.1'>4.1 Content Lines</h2>
<pre>
   The iCalendar object is organized into individual lines of text,
   called content lines. Content lines are delimited by a line break,
   which is a CRLF sequence (US-ASCII decimal 13, followed by US-ASCII
   decimal 10).

   Lines of text SHOULD NOT be longer than 75 octets, excluding the line
   break. Long content lines SHOULD be split into a multiple line
   representations using a line "folding" technique. That is, a long
   line can be split between any two characters by inserting a CRLF
   immediately followed by a single linear white space character (i.e.,
   SPACE, US-ASCII decimal 32 or HTAB, US-ASCII decimal 9). Any sequence
   of CRLF followed immediately by a single linear white space character
   is ignored (i.e., removed) when processing the content type.

   For example the line:

     DESCRIPTION:This is a long description that exists on a long line.

   Can be represented as:

     DESCRIPTION:This is a lo
      ng description
       that exists on a long line.

   The process of moving from this folded multiple line representation
   to its single line representation is called "unfolding". Unfolding is
   accomplished by removing the CRLF character and the linear white
   space character that immediately follows.

   When parsing a content line, folded lines MUST first be unfolded
   according to the unfolding procedure described above. When generating
   a content line, lines longer than 75 octets SHOULD be folded
   according to the folding procedure described above.

   The content information associated with an iCalendar object is
   formatted using a syntax similar to that defined by <a href='#ref_RFC_2425'>[RFC 2425]</a>. That
   is, the content information consists of CRLF-separated content lines.

   The following notation defines the lines of content in an iCalendar
   object:

     contentline        = name *(";" param ) ":" value CRLF
        ; This ABNF is just a general definition for an initial parsing
        ; of the content line into its property name, parameter list,
        ; and value string

     ; When parsing a content line, folded lines MUST first
        ; be unfolded according to the unfolding procedure
        ; described above. When generating a content line, lines
        ; longer than 75 octets SHOULD be folded according to
        ; the folding procedure described above.

     name               = x-name / iana-token

     iana-token = 1*(ALPHA / DIGIT / "-")
     ; iCalendar identifier registered with IANA

     x-name             = "X-" vendorid "-"] 1*(ALPHA / DIGIT / "-")
     ; Reservered for experimental use. Not intended for use in
     ; released products.

     vendorid   = 3*(ALPHA / DIGIT)     ;Vendor identification

     param              = param-name "=" param-value
                          *("," param-value)
        ; Each property defines the specific ABNF for the parameters
        ; allowed on the property. Refer to specific properties for
        ; precise parameter ABNF.

     param-name = iana-token / x-token

     param-value        = paramtext / quoted-string

     paramtext  = *SAFE-CHAR

     value      = *VALUE-CHAR

     quoted-string      = DQUOTE *QSAFE-CHAR DQUOTE

     NON-US-ASCII       = %x80-F8
     ; Use restricted by charset parameter
     ; on outer MIME object (UTF-8 preferred)

     QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-US-ASCII
     ; Any character except CTLs and DQUOTE

     SAFE-CHAR  = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E
                / NON-US-ASCII
     ; Any character except CTLs, DQUOTE, ";", ":", ","

     VALUE-CHAR = WSP / %x21-7E / NON-US-ASCII
     ; Any textual character

     CR = %x0D
     ; carriage return

     LF = %x0A
     ; line feed

     CRLF       = CR LF
     ; Internet standard newline

     CTL        = %x00-08 / %x0A-1F / %x7F
        ; Controls

     ALPHA      = %x41-5A / %x61-7A   ; A-Z / a-z

     DIGIT      = %x30-39
        ; 0-9

     DQUOTE     = %x22
        ; Quotation Mark

     WSP        = SPACE / HTAB

     SPACE      = %x20

     HTAB       = %x09

   The property value component of a content line has a format that is
   property specific. Refer to the section describing each property for
   a definition of this format.

   All names of properties, property parameters, enumerated property
   values and property parameter values are case-insensitive. However,
   all other property values are case-sensitive, unless otherwise
   stated.

</pre>
</div>
<div><h2 id='sec4.1.1'>4.1.1 List and Field Separators</h2>
<pre>
   Some properties and parameters allow a list of values. Values in a
   list of values MUST be separated by a COMMA character (US-ASCII
   decimal 44). There is no significance to the order of values in a
   list. For those parameter values (such as those that specify URI
   values) that are specified in quoted-strings, the individual quoted-
   strings are separated by a COMMA character (US-ASCII decimal 44).

   Some property values are defined in terms of multiple parts. These
   structured property values MUST have their value parts separated by a
   SEMICOLON character (US-ASCII decimal 59).

   Some properties allow a list of parameters. Each property parameter
   in a list of property parameters MUST be separated by a SEMICOLON
   character (US-ASCII decimal 59).

   Property parameters with values containing a COLON, a SEMICOLON or a
   COMMA character MUST be placed in quoted text.

   For example, in the following properties a SEMICOLON is used to
   separate property parameters from each other, and a COMMA is used to
   separate property values in a value list.

     ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT:MAILTO:
      jsmith@host.com

     RDATE;VALUE=DATE:19970304,19970504,19970704,19970904

</pre>
</div>
<div><h2 id='sec4.1.2'>4.1.2 Multiple Values</h2>
<pre>
   Some properties defined in the iCalendar object can have multiple
   values. The general rule for encoding multi-valued items is to simply
   create a new content line for each value, including the property
   name. However, it should be noted that some properties support
   encoding multiple values in a single property by separating the
   values with a COMMA character (US-ASCII decimal 44). Individual
   property definitions should be consulted for determining whether a
   specific property allows multiple values and in which of these two
   forms.

</pre>
</div>
<div><h2 id='sec4.1.3'>4.1.3 Binary Content</h2>
<pre>
   Binary content information in an iCalendar object SHOULD be
   referenced using a URI within a property value. That is the binary
   content information SHOULD be placed in an external MIME entity that
   can be referenced by a URI from within the iCalendar object. In
   applications where this is not feasible, binary content information

   can be included within an iCalendar object, but only after first
   encoding it into text using the "BASE64" encoding method defined in
   <a href='#ref_RFC_2045'>[RFC 2045]</a>. Inline binary contact SHOULD only be used in applications
   whose special circumstances demand that an iCalendar object be
   expressed as a single entity. A property containing inline binary
   content information MUST specify the "ENCODING" property parameter.
   Binary content information placed external to the iCalendar object
   MUST be referenced by a uniform resource identifier (URI).

   The following example specifies an "ATTACH" property that references
   an attachment external to the iCalendar object with a URI reference:

     ATTACH:http://xyz.com/public/quarterly-report.doc

   The following example specifies an "ATTACH" property with inline
   binary encoded content information:

     ATTACH;FMTTYPE=image/basic;ENCODING=BASE64;VALUE=BINARY:
      MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1U
      EBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bmljYXRpb25zIE
        &lt;...remainder of "BASE64" encoded binary data...>

</pre>
</div>
<div><h2 id='sec4.1.4'>4.1.4 Character Set</h2>
<pre>
   There is not a property parameter to declare the character set used
   in a property value. The default character set for an iCalendar
   object is UTF-8 as defined in <a href='#ref_RFC_2279'>[RFC 2279]</a>.

   The "charset" Content-Type parameter can be used in MIME transports
   to specify any other IANA registered character set.

</pre>
</div>
<div><h2 id='sec4.2'>4.2 Property Parameters</h2>
<pre>
   A property can have attributes associated with it. These "property
   parameters" contain meta-information about the property or the
   property value. Property parameters are provided to specify such
   information as the location of an alternate text representation for a
   property value, the language of a text property value, the data type
   of the property value and other attributes.

   Property parameter values that contain the COLON (US-ASCII decimal
   58), SEMICOLON (US-ASCII decimal 59) or COMMA (US-ASCII decimal 44)
   character separators MUST be specified as quoted-string text values.
   Property parameter values MUST NOT contain the DOUBLE-QUOTE (US-ASCII
   decimal 22) character. The DOUBLE-QUOTE (US-ASCII decimal 22)
   character is used as a delimiter for parameter values that contain
   restricted characters or URI text. For example:

     DESCRIPTION;ALTREP="http://www.wiz.org":The Fall'98 Wild Wizards
       Conference - - Las Vegas, NV, USA

   Property parameter values that are not in quoted strings are case
   insensitive.

   The general property parameters defined by this memo are defined by
   the following notation:

     parameter  = altrepparam           ; Alternate text representation
                / cnparam               ; Common name
                / cutypeparam           ; Calendar user type
                / delfromparam          ; Delegator
                / deltoparam            ; Delegatee
                / dirparam              ; Directory entry
                / encodingparam         ; Inline encoding
                / fmttypeparam          ; Format type
                / fbtypeparam           ; Free/busy time type
                / languageparam         ; Language for text
                / memberparam           ; Group or list membership
                / partstatparam         ; Participation status
                / rangeparam            ; Recurrence identifier range
                / trigrelparam          ; Alarm trigger relationship
                / reltypeparam          ; Relationship type
                / roleparam             ; Participation role
                / rsvpparam             ; RSVP expectation
                / sentbyparam           ; Sent by
                / tzidparam             ; Reference to time zone object
                / valuetypeparam        ; Property value data type
                / ianaparam
        ; Some other IANA registered iCalendar parameter.
                / xparam
        ; A non-standard, experimental parameter.

     ianaparam  = iana-token "=" param-value *("," param-value)

     xparam     =x-name "=" param-value *("," param-value)

</pre>
</div>
<div><h2 id='sec4.2.1'>4.2.1 Alternate Text Representation</h2>
<dl>
<dt id='altrep'>Parameter Name</dt>
<dd class='ParameterName'><pre>    ALTREP

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify an alternate text representation for the property
   value.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     altrepparam        = "ALTREP" "=" DQUOTE uri DQUOTE

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The parameter specifies a URI that points to an
   alternate representation for a textual property value. A property
   specifying this parameter MUST also include a value that reflects the
   default representation of the text value. The individual URI
   parameter values MUST each be specified in a quoted-string.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     DESCRIPTION;ALTREP="CID:&lt;part3.msg.970415T083000@host.com>":Project
       XYZ Review Meeting will include the following agenda items: (a)
       Market Overview, (b) Finances, (c) Project Management

   The "ALTREP" property parameter value might point to a "text/html"
   content portion.

     Content-Type:text/html
     Content-Id:&lt;part3.msg.970415T083000@host.com>

     &lt;html>&lt;body>
     &lt;p>&lt;b>Project XYZ Review Meeting&lt;/b> will include the following
     agenda items:&lt;ol>&lt;li>Market
     Overview&lt;/li>&lt;li>Finances&lt;/li>&lt;li>Project Management&lt;/li>&lt;/ol>&lt;/p>
     &lt;/body>&lt;/html>

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.2'>4.2.2 Common Name</h2>
<dl>
<dt id='cn'>Parameter Name</dt>
<dd class='ParameterName'><pre>    CN

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify the common name to be associated with the
   calendar user specified by the property.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     cnparam    = "CN" "=" param-value

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This parameter can be specified on properties with a
   CAL-ADDRESS value type. The parameter specifies the common name to be
   associated with the calendar user specified by the property. The
   parameter value is text. The parameter value can be used for display
   text to be associated with the calendar address specified by the
   property.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     ORGANIZER;CN="John Smith":MAILTO:jsmith@host.com

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.3'>4.2.3 Calendar User Type</h2>
<dl>
<dt id='cutype'>Parameter Name</dt>
<dd class='ParameterName'><pre>    CUTYPE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify the type of calendar user specified by the
   property.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     cutypeparam        = "CUTYPE" "="
                         ("INDIVIDUAL"          ; An individual
                        / "GROUP"               ; A group of individuals
                        / "RESOURCE"            ; A physical resource
                        / "ROOM"                ; A room resource
                        / "UNKNOWN"             ; Otherwise not known
                        / x-name                ; Experimental type
                        / iana-token)           ; Other IANA registered
                                                ; type
     ; Default is INDIVIDUAL

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This parameter can be specified on properties with a
   CAL-ADDRESS value type. The parameter identifies the type of calendar
   user specified by the property. If not specified on a property that
   allows this parameter, the default is INDIVIDUAL.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     ATTENDEE;CUTYPE=GROUP:MAILTO:ietf-calsch@imc.org

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.4'>4.2.4 Delegators</h2>
<dl>
<dt id='delegatedFrom'>Parameter Name</dt>
<dd class='ParameterName'><pre>    DELEGATED-FROM

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify the calendar users that have delegated their
   participation to the calendar user specified by the property.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     delfromparam       = "DELEGATED-FROM" "=" DQUOTE cal-address DQUOTE
                          *("," DQUOTE cal-address DQUOTE)

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This parameter can be specified on properties with a
   CAL-ADDRESS value type. This parameter can be specified on a property
   that has a value type of calendar address. This parameter specifies
   those calendar uses that have delegated their participation in a
   group scheduled event or to-do to the calendar user specified by the
   property. The value MUST be a MAILTO URI as defined in <a href='#ref_RFC_1738'>[RFC 1738]</a>.
   The individual calendar address parameter values MUST each be
   specified in a quoted-string.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     ATTENDEE;DELEGATED-FROM="MAILTO:jsmith@host.com":MAILTO:
      jdoe@host.com

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.5'>4.2.5 Delegatees</h2>
<dl>
<dt id='delegatedTo'>Parameter Name</dt>
<dd class='ParameterName'><pre>    DELEGATED-TO

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify the calendar users to whom the calendar user
   specified by the property has delegated participation.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     deltoparam = "DELEGATED-TO" "=" DQUOTE cal-address DQUOTE
                  *("," DQUOTE cal-address DQUOTE)

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This parameter can be specified on properties with a
   CAL-ADDRESS value type. This parameter specifies those calendar users
   whom have been delegated participation in a group scheduled event or
   to-do by the calendar user specified by the property. The value MUST
   be a MAILTO URI as defined in <a href='#ref_RFC_1738'>[RFC 1738]</a>. The individual calendar
   address parameter values MUST each be specified in a quoted-string.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     ATTENDEE;DELEGATED-TO="MAILTO:jdoe@host.com","MAILTO:jqpublic@
      host.com":MAILTO:jsmith@host.com

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.6'>4.2.6 Directory Entry Reference</h2>
<dl>
<dt id='dir'>Parameter Name</dt>
<dd class='ParameterName'><pre>    DIR

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify reference to a directory entry associated with
   the calendar user specified by the property.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     dirparam   = "DIR" "=" DQUOTE uri DQUOTE

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This parameter can be specified on properties with a
   CAL-ADDRESS value type. The parameter specifies a reference to the
   directory entry associated with the calendar user specified by the
   property. The parameter value is a URI. The individual URI parameter
   values MUST each be specified in a quoted-string.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     ORGANIZER;DIR="ldap://host.com:6666/o=eDABC%20Industries,c=3DUS??
      (cn=3DBJim%20Dolittle)":MAILTO:jimdo@host1.com

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.7'>4.2.7 Inline Encoding</h2>
<dl>
<dt id='encoding'>Parameter Name</dt>
<dd class='ParameterName'><pre>    ENCODING

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify an alternate inline encoding for the property
   value.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     encodingparam      = "ENCODING" "="
                          ("8BIT"
        ; "8bit" text encoding is defined in <a href='#ref_RFC_2045'>[RFC 2045]</a>
                        / "BASE64"
        ; "BASE64" binary encoding format is defined in <a href='#ref_RFC_2045'>[RFC 2045]</a>
                        / iana-token
        ; Some other IANA registered iCalendar encoding type
                        / x-name)
        ; A non-standard, experimental encoding type

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The property parameter identifies the inline encoding
   used in a property value. The default encoding is "8BIT",
   corresponding to a property value consisting of text. The "BASE64"
   encoding type corresponds to a property value encoded using the
   "BASE64" encoding defined in <a href='#ref_RFC_2045'>[RFC 2045]</a>.

   If the value type parameter is ";VALUE=BINARY", then the inline
   encoding parameter MUST be specified with the value
   ";ENCODING=BASE64".

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     ATTACH;FMTYPE=IMAGE/JPEG;ENCODING=BASE64;VALUE=BINARY:MIICajC
      CAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDA
      qBgNVBAoTI05ldHNjYXBlIENvbW11bmljYXRpb25zIENvcnBvcmF0aW9uMRw
      &lt;...remainder of "BASE64" encoded binary data...>

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.8'>4.2.8 Format Type</h2>
<dl>
<dt id='fmttype'>Parameter Name</dt>
<dd class='ParameterName'><pre>    FMTTYPE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify the content type of a referenced object.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     fmttypeparam       = "FMTTYPE" "=" iana-token
                                        ; A IANA registered content type
                                     / x-name
                                        ; A non-standard content type

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This parameter can be specified on properties that are
   used to reference an object. The parameter specifies the content type
   of the referenced object. For example, on the "ATTACH" property, a
   FTP type URI value does not, by itself, necessarily convey the type
   of content associated with the resource. The parameter value MUST be
   the TEXT for either an IANA registered content type or a non-standard
   content type.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

      ATTACH;FMTTYPE=application/binary:ftp://domain.com/pub/docs/
       agenda.doc

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.9'>4.2.9 Free/Busy Time Type</h2>
<dl>
<dt id='fbtype'>Parameter Name</dt>
<dd class='ParameterName'><pre>    FBTYPE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify the free or busy time type.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     fbtypeparam        = "FBTYPE" "=" ("FREE" / "BUSY"
                        / "BUSY-UNAVAILABLE" / "BUSY-TENTATIVE"
                        / x-name
        ; Some experimental iCalendar data type.
                        / iana-token)

        ; Some other IANA registered iCalendar data type.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The parameter specifies the free or busy time type. The
   value FREE indicates that the time interval is free for scheduling.
   The value BUSY indicates that the time interval is busy because one
   or more events have been scheduled for that interval. The value
   BUSY-UNAVAILABLE indicates that the time interval is busy and that
   the interval can not be scheduled. The value BUSY-TENTATIVE indicates
   that the time interval is busy because one or more events have been
   tentatively scheduled for that interval. If not specified on a
   property that allows this parameter, the default is BUSY.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this parameter on a FREEBUSY
   property.

     FREEBUSY;FBTYPE=BUSY:19980415T133000Z/19980415T170000Z

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.10'>4.2.10 Language</h2>
<dl>
<dt id='language'>Parameter Name</dt>
<dd class='ParameterName'><pre>    LANGUAGE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify the language for text values in a property or
   property parameter.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     languageparam =    "LANGUAGE" "=" language

     language = &lt;Text identifying a language, as defined in <a href='#ref_RFC_1766'>[RFC 1766]</a>>

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This parameter can be specified on properties with a
   text value type. The parameter identifies the language of the text in
   the property or property parameter value. The value of the "language"
   property parameter is that defined in <a href='#ref_RFC_1766'>[RFC 1766]</a>.

   For transport in a MIME entity, the Content-Language header field can
   be used to set the default language for the entire body part.
   Otherwise, no default language is assumed.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     SUMMARY;LANGUAGE=us-EN:Company Holiday Party

     LOCATION;LANGUAGE=en:Germany
     LOCATION;LANGUAGE=no:Tyskland

   The following example makes use of the Quoted-Printable encoding in
   order to represent non-ASCII characters.

     LOCATION;LANGUAGE=da:K=F8benhavn
     LOCATION;LANGUAGE=en:Copenhagen

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.11'>4.2.11 Group or List Membership</h2>
<dl>
<dt id='member'>Parameter Name</dt>
<dd class='ParameterName'><pre>    MEMBER

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify the group or list membership of the calendar user
   specified by the property.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     memberparam        = "MEMBER" "=" DQUOTE cal-address DQUOTE
                          *("," DQUOTE cal-address DQUOTE)

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This parameter can be specified on properties with a
   CAL-ADDRESS value type. The parameter identifies the groups or list
   membership for the calendar user specified by the property. The
   parameter value either a single calendar address in a quoted-string
   or a COMMA character (US-ASCII decimal 44) list of calendar
   addresses, each in a quoted-string. The individual calendar address
   parameter values MUST each be specified in a quoted-string.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     ATTENDEE;MEMBER="MAILTO:ietf-calsch@imc.org":MAILTO:jsmith@host.com

     ATTENDEE;MEMBER="MAILTO:projectA@host.com","MAILTO:projectB@host.
      com":MAILTO:janedoe@host.com

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.12'>4.2.12 Participation Status</h2>
<dl>
<dt id='partstat'>Parameter Name</dt>
<dd class='ParameterName'><pre>    PARTSTAT

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify the participation status for the calendar user
   specified by the property.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     partstatparam      = "PARTSTAT" "="
                         ("NEEDS-ACTION"        ; Event needs action
                        / "ACCEPTED"            ; Event accepted
                        / "DECLINED"            ; Event declined

                        / "TENTATIVE"           ; Event tentatively
                                                ; accepted
                        / "DELEGATED"           ; Event delegated
                        / x-name                ; Experimental status
                        / iana-token)           ; Other IANA registered
                                                ; status
     ; These are the participation statuses for a "VEVENT". Default is
     ; NEEDS-ACTION
     partstatparam      /= "PARTSTAT" "="
                         ("NEEDS-ACTION"        ; To-do needs action
                        / "ACCEPTED"            ; To-do accepted
                        / "DECLINED"            ; To-do declined
                        / "TENTATIVE"           ; To-do tentatively
                                                ; accepted
                        / "DELEGATED"           ; To-do delegated
                        / "COMPLETED"           ; To-do completed.
                                                ; COMPLETED property has
                                                ;date/time completed.
                        / "IN-PROCESS"          ; To-do in process of
                                                ; being completed
                        / x-name                ; Experimental status
                        / iana-token)           ; Other IANA registered
                                                ; status
     ; These are the participation statuses for a "VTODO". Default is
     ; NEEDS-ACTION

     partstatparam      /= "PARTSTAT" "="
                         ("NEEDS-ACTION"        ; Journal needs action
                        / "ACCEPTED"            ; Journal accepted
                        / "DECLINED"            ; Journal declined
                        / x-name                ; Experimental status
                        / iana-token)           ; Other IANA registered
                                                ; status
     ; These are the participation statuses for a "VJOURNAL". Default is
     ; NEEDS-ACTION

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This parameter can be specified on properties with a
   CAL-ADDRESS value type. The parameter identifies the participation
   status for the calendar user specified by the property value. The
   parameter values differ depending on whether they are associated with
   a group scheduled "VEVENT", "VTODO" or "VJOURNAL". The values MUST
   match one of the values allowed for the given calendar component. If
   not specified on a property that allows this parameter, the default
   value is NEEDS-ACTION.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     ATTENDEE;PARTSTAT=DECLINED:MAILTO:jsmith@host.com

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.13'>4.2.13 Recurrence Identifier Range</h2>
<dl>
<dt id='range'>Parameter Name</dt>
<dd class='ParameterName'><pre>    RANGE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify the effective range of recurrence instances from
   the instance specified by the recurrence identifier specified by the
   property.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     rangeparam = "RANGE" "=" ("THISANDPRIOR"
        ; To specify all instances prior to the recurrence identifier
                / "THISANDFUTURE")
        ; To specify the instance specified by the recurrence identifier
        ; and all subsequent recurrence instances

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The parameter can be specified on a property that
   specifies a recurrence identifier. The parameter specifies the
   effective range of recurrence instances that is specified by the
   property. The effective range is from the recurrence identified
   specified by the property. If this parameter is not specified an
   allowed property, then the default range is the single instance
   specified by the recurrence identifier value of the property. The
   parameter value can be "THISANDPRIOR" to indicate a range defined by
   the recurrence identified value of the property and all prior
   instances. The parameter value can also be "THISANDFUTURE" to
   indicate a range defined by the recurrence identifier and all
   subsequent instances.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     RECURRENCE-ID;RANGE=THISANDPRIOR:19980401T133000Z

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.14'>4.2.14 Alarm Trigger Relationship</h2>
<dl>
<dt id='related'>Parameter Name</dt>
<dd class='ParameterName'><pre>    RELATED

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify the relationship of the alarm trigger with
   respect to the start or end of the calendar component.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     trigrelparam       = "RELATED" "="
                         ("START"       ; Trigger off of start
                        / "END")        ; Trigger off of end

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The parameter can be specified on properties that
   specify an alarm trigger with a DURATION value type. The parameter
   specifies whether the alarm will trigger relative to the start or end
   of the calendar component. The parameter value START will set the
   alarm to trigger off the start of the calendar component; the
   parameter value END will set the alarm to trigger off the end of the
   calendar component. If the parameter is not specified on an allowable
   property, then the default is START.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     TRIGGER;RELATED=END:PT5M

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.15'>4.2.15 Relationship Type</h2>
<dl>
<dt id='reltype'>Parameter Name</dt>
<dd class='ParameterName'><pre>    RELTYPE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify the type of hierarchical relationship associated
   with the calendar component specified by the property.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     reltypeparam       = "RELTYPE" "="
                         ("PARENT"      ; Parent relationship. Default.
                        / "CHILD"       ; Child relationship
                        / "SIBLING      ; Sibling relationship
                        / iana-token    ; Some other IANA registered
                                        ; iCalendar relationship type
                        / x-name)       ; A non-standard, experimental
                                        ; relationship type

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This parameter can be specified on a property that
   references another related calendar. The parameter specifies the
   hierarchical relationship type of the calendar component referenced
   by the property. The parameter value can be PARENT, to indicate that
   the referenced calendar component is a superior of calendar
   component; CHILD to indicate that the referenced calendar component
   is a subordinate of the calendar component; SIBLING to indicate that
   the referenced calendar component is a peer of the calendar
   component. If this parameter is not specified on an allowable
   property, the default relationship type is PARENT.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     RELATED-TO;RELTYPE=SIBLING:&lt;19960401-080045-4000F192713@host.com>

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.16'>4.2.16 Participation Role</h2>
<dl>
<dt id='role'>Parameter Name</dt>
<dd class='ParameterName'><pre>    ROLE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify the participation role for the calendar user
   specified by the property.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     roleparam  = "ROLE" "="
                 ("CHAIR"               ; Indicates chair of the
                                        ; calendar entity
                / "REQ-PARTICIPANT"     ; Indicates a participant whose
                                        ; participation is required
                / "OPT-PARTICIPANT"     ; Indicates a participant whose
                                        ; participation is optional
                / "NON-PARTICIPANT"     ; Indicates a participant who is
                                        ; copied for information
                                        ; purposes only
                / x-name                ; Experimental role
                / iana-token)           ; Other IANA role
     ; Default is REQ-PARTICIPANT

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This parameter can be specified on properties with a
   CAL-ADDRESS value type. The parameter specifies the participation
   role for the calendar user specified by the property in the group
   schedule calendar component. If not specified on a property that
   allows this parameter, the default value is REQ-PARTICIPANT.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     ATTENDEE;ROLE=CHAIR:MAILTO:mrbig@host.com

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.17'>4.2.17 RSVP Expectation</h2>
<dl>
<dt id='rsvp'>Parameter Name</dt>
<dd class='ParameterName'><pre>    RSVP

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify whether there is an expectation of a favor of a
   reply from the calendar user specified by the property value.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     rsvpparam = "RSVP" "=" ("TRUE" / "FALSE")
     ; Default is FALSE

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This parameter can be specified on properties with a
   CAL-ADDRESS value type. The parameter identifies the expectation of a
   reply from the calendar user specified by the property value. This
   parameter is used by the "Organizer" to request a participation
   status reply from an "Attendee" of a group scheduled event or to-do.
   If not specified on a property that allows this parameter, the
   default value is FALSE.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     ATTENDEE;RSVP=TRUE:MAILTO:jsmith@host.com

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.18'>4.2.18 Sent By</h2>
<dl>
<dt id='sentBy'>Parameter Name</dt>
<dd class='ParameterName'><pre>    SENT-BY

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify the calendar user that is acting on behalf of the
   calendar user specified by the property.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property parameter is defined by the following
   notation:

     sentbyparam        = "SENT-BY" "=" DQUOTE cal-address DQUOTE

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This parameter can be specified on properties with a
   CAL-ADDRESS value type. The parameter specifies the calendar user
   that is acting on behalf of the calendar user specified by the
   property. The parameter value MUST be a MAILTO URI as defined in RFC
   1738]. The individual calendar address parameter values MUST each be
   specified in a quoted-string.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     ORGANIZER;SENT-BY:"MAILTO:sray@host.com":MAILTO:jsmith@host.com

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.19'>4.2.19 Time Zone Identifier</h2>
<dl>
<dt id='tzid'>Parameter Name</dt>
<dd class='ParameterName'><pre>    TZID

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To specify the identifier for the time zone definition for a
   time component in the property value.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    This property parameter is defined by the
   following notation:

     tzidparam  = "TZID" "=" tzidprefix] paramtext CRLF

     tzidprefix = "/"

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The parameter MUST be specified on the "DTSTART",
   "DTEND", "DUE", "EXDATE" and "RDATE" properties when either a DATE-
   TIME or TIME value type is specified and when the value is not either
   a UTC or a "floating" time. Refer to the DATE-TIME or TIME value type
   definition for a description of UTC and "floating time" formats. This
   property parameter specifies a text value which uniquely identifies
   the "VTIMEZONE" calendar component to be used when evaluating the
   time portion of the property. The value of the TZID property
   parameter will be equal to the value of the TZID property for the
   matching time zone definition. An individual "VTIMEZONE" calendar
   component MUST be specified for each unique "TZID" parameter value
   specified in the iCalendar object.

   The parameter MUST be specified on properties with a DATE-TIME value
   if the DATE-TIME is not either a UTC or a "floating" time.

   The presence of the SOLIDUS character (US-ASCII decimal 47) as a
   prefix, indicates that this TZID represents a unique ID in a globally
   defined time zone registry (when such registry is defined).

        Note: This document does not define a naming convention for time
        zone identifiers. Implementers may want to use the naming
        conventions defined in existing time zone specifications such as
        the public-domain Olson database <a href='#ref_TZ'>[TZ]</a>. The specification of
        globally unique time zone identifiers is not addressed by this
        document and is left for future study.

   The following are examples of this property parameter:

     DTSTART;TZID=US-Eastern:19980119T020000

     DTEND;TZID=US-Eastern:19980119T030000

   The TZID property parameter MUST NOT be applied to DATE-TIME or TIME
   properties whose time values are specified in UTC.

   The use of local time in a DATE-TIME or TIME value without the TZID
   property parameter is to be interpreted as a local time value,
   regardless of the existence of "VTIMEZONE" calendar components in the
   iCalendar object.

   For more information see the sections on the data types DATE-TIME and
   TIME.

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.2.20'>4.2.20 Value Data Types</h2>
<dl>
<dt id='value'>Parameter Name</dt>
<dd class='ParameterName'><pre>    VALUE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    To explicitly specify the data type format for a property
   value.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The "VALUE" property parameter is defined by the
   following notation:

     valuetypeparam = "VALUE" "=" valuetype

     valuetype  = ("BINARY"
                / "BOOLEAN"
                / "CAL-ADDRESS"
                / "DATE"
                / "DATE-TIME"
                / "DURATION"
                / "FLOAT"
                / "INTEGER"
                / "PERIOD"
                / "RECUR"
                / "TEXT"
                / "TIME"
                / "URI"
                / "UTC-OFFSET"
                / x-name
                ; Some experimental iCalendar data type.
                / iana-token)
                ; Some other IANA registered iCalendar data type.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The parameter specifies the data type and format of the
   property value. The property values MUST be of a single value type.
   For example, a "RDATE" property cannot have a combination of DATE-
   TIME and TIME value types.

   If the property's value is the default value type, then this
   parameter need not be specified. However, if the property's default
   value type is overridden by some other allowable value type, then
   this parameter MUST be specified.

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.3'>4.3 Property Value Data Types</h2>
<pre>
   The properties in an iCalendar object are strongly typed. The
   definition of each property restricts the value to be one of the
   value data types, or simply value types, defined in this section. The
   value type for a property will either be specified implicitly as the
   default value type or will be explicitly specified with the "VALUE"

   parameter. If the value type of a property is one of the alternate
   valid types, then it MUST be explicitly specified with the "VALUE"
   parameter.

</pre>
</div>
<div><h2 id='sec4.3.1'>4.3.1 Binary</h2>
<dl>
<dt id='Value_BINARY'>Value Name</dt>
<dd class='ValueName'><pre>    BINARY

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This value type is used to identify properties that contain
   a character encoding of inline binary data. For example, an inline
   attachment of an object code might be included in an iCalendar
   object.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    The value type is defined by the following
   notation:

     binary     = *(4b-char) b-end]
     ; A "BASE64" encoded character string, as defined by <a href='#ref_RFC_2045'>[RFC 2045]</a>.

     b-end      = (2b-char "==") / (3b-char "=")

     b-char = ALPHA / DIGIT / "+" / "/"

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    Property values with this value type MUST also include
   the inline encoding parameter sequence of ";ENCODING=BASE64". That
   is, all inline binary data MUST first be character encoded using the
   "BASE64" encoding method defined in <a href='#ref_RFC_2045'>[RFC 2045]</a>. No additional content
   value encoding (i.e., BACKSLASH character encoding) is defined for
   this value type.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an abridged example of a "BASE64" encoded
   binary value data.

     ATTACH;VALUE=BINARY;ENCODING=BASE64:MIICajCCAdOgAwIBAgICBEUwDQY
      JKoZIhvcNAQEEBQAwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlI
      ENvbW11bmljYXRpb25zIENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZv
        &lt;...remainder of "BASE64" encoded binary data...>

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.3.2'>4.3.2 Boolean</h2>
<dl>
<dt id='Value_BOOLEAN'>Value Name</dt>
<dd class='ValueName'><pre>    BOOLEAN

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This value type is used to identify properties that contain
   either a "TRUE" or "FALSE" Boolean value.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    The value type is defined by the following
   notation:

     boolean    = "TRUE" / "FALSE"

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    These values are case insensitive text. No additional
   content value encoding (i.e., BACKSLASH character encoding) is
   defined for this value type.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of a hypothetical property that
   has a BOOLEAN value type:

   GIBBERISH:TRUE

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.3.3'>4.3.3 Calendar User Address</h2>
<dl>
<dt id='Value_CAL-ADDRESS'>Value Name</dt>
<dd class='ValueName'><pre>    CAL-ADDRESS

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This value type is used to identify properties that contain
   a calendar user address.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    The value type is as defined by the following
   notation:

     cal-address        = uri

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The value is a URI as defined by <a href='#ref_RFC_1738'>[RFC 1738]</a> or any other
   IANA registered form for a URI. When used to address an Internet
   email transport address for a calendar user, the value MUST be a
   MAILTO URI, as defined by <a href='#ref_RFC_1738'>[RFC 1738]</a>. No additional content value
   encoding (i.e., BACKSLASH character encoding) is defined for this
   value type.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     ATTENDEE:MAILTO:jane_doe@host.com

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.3.4'>4.3.4 Date</h2>
<dl>
<dt id='Value_DATE'>Value Name</dt>
<dd class='ValueName'><pre>    DATE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This value type is used to identify values that contain a
   calendar date.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    The value type is defined by the following
   notation:

     date               = date-value

     date-value         = date-fullyear date-month date-mday
     date-fullyear      = 4DIGIT

     date-month         = 2DIGIT        ;01-12
     date-mday          = 2DIGIT        ;01-28, 01-29, 01-30, 01-31
                                        ;based on month/year

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    If the property permits, multiple "date" values are
   specified as a COMMA character (US-ASCII decimal 44) separated list
   of values. The format for the value type is expressed as the ISO
   8601] complete representation, basic format for a calendar date. The
   textual format specifies a four-digit year, two-digit month, and
   two-digit day of the month. There are no separator characters between
   the year, month and day component text.

   No additional content value encoding (i.e., BACKSLASH character
   encoding) is defined for this value type.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following represents July 14, 1997:

     19970714

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.3.5'>4.3.5 Date-Time</h2>
<dl>
<dt id='Value_DATE-TIME'>Value Name</dt>
<dd class='ValueName'><pre>    DATE-TIME

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This value type is used to identify values that specify a
   precise calendar date and time of day.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    The value type is defined by the following
   notation:

     date-time  = date "T" time ;As specified in the date and time
                                ;value definitions

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    If the property permits, multiple "date-time" values are
   specified as a COMMA character (US-ASCII decimal 44) separated list
   of values. No additional content value encoding (i.e., BACKSLASH
   character encoding) is defined for this value type.

   The "DATE-TIME" data type is used to identify values that contain a
   precise calendar date and time of day. The format is based on the
   <a href='#ref_ISO_8601'>[ISO 8601]</a> complete representation, basic format for a calendar date
   and time of day. The text format is a concatenation of the "date",
   followed by the LATIN CAPITAL LETTER T character (US-ASCII decimal
   84) time designator, followed by the "time" format.

   The "DATE-TIME" data type expresses time values in three forms:

   The form of date and time with UTC offset MUST NOT be used. For
   example, the following is not valid for a date-time value:

     DTSTART:19980119T230000-0800       ;Invalid time format

   FORM #1: DATE WITH LOCAL TIME

   The date with local time form is simply a date-time value that does
   not contain the UTC designator nor does it reference a time zone. For
   example, the following represents Janurary 18, 1998, at 11 PM:

     DTSTART:19980118T230000

   Date-time values of this type are said to be "floating" and are not
   bound to any time zone in particular. They are used to represent the
   same hour, minute, and second value regardless of which time zone is
   currently being observed. For example, an event can be defined that
   indicates that an individual will be busy from 11:00 AM to 1:00 PM
   every day, no matter which time zone the person is in. In these
   cases, a local time can be specified. The recipient of an iCalendar
   object with a property value consisting of a local time, without any
   relative time zone information, SHOULD interpret the value as being
   fixed to whatever time zone the ATTENDEE is in at any given moment.
   This means that two ATTENDEEs, in different time zones, receiving the
   same event definition as a floating time, may be participating in the
   event at different actual times. Floating time SHOULD only be used
   where that is the reasonable behavior.

   In most cases, a fixed time is desired. To properly communicate a
   fixed time in a property value, either UTC time or local time with
   time zone reference MUST be specified.

   The use of local time in a DATE-TIME value without the TZID property
   parameter is to be interpreted as floating time, regardless of the
   existence of "VTIMEZONE" calendar components in the iCalendar object.

   FORM #2: DATE WITH UTC TIME

   The date with UTC time, or absolute time, is identified by a LATIN
   CAPITAL LETTER Z suffix character (US-ASCII decimal 90), the UTC
   designator, appended to the time value. For example, the following
   represents January 19, 1998, at 0700 UTC:

     DTSTART:19980119T070000Z

   The TZID property parameter MUST NOT be applied to DATE-TIME
   properties whose time values are specified in UTC.

   FORM #3: DATE WITH LOCAL TIME AND TIME ZONE REFERENCE

   The date and local time with reference to time zone information is
   identified by the use the TZID property parameter to reference the
   appropriate time zone definition. TZID is discussed in detail in the
   section on Time Zone. For example, the following represents 2 AM in
   New York on Janurary 19, 1998:

          DTSTART;TZID=US-Eastern:19980119T020000

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following represents July 14, 1997, at 1:30 PM in New
   York City in each of the three time formats, using the "DTSTART"
   property.

     DTSTART:19970714T133000            ;Local time
     DTSTART:19970714T173000Z           ;UTC time
     DTSTART;TZID=US-Eastern:19970714T133000    ;Local time and time
                        ; zone reference

   A time value MUST ONLY specify 60 seconds when specifying the
   periodic "leap second" in the time value. For example:

     COMPLETED:19970630T235960Z

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.3.6'>4.3.6 Duration</h2>
<dl>
<dt id='Value_DURATION'>Value Name</dt>
<dd class='ValueName'><pre>    DURATION

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This value type is used to identify properties that contain
   a duration of time.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    The value type is defined by the following
   notation:

     dur-value  = ("+"] / "-") "P" (dur-date / dur-time / dur-week)

     dur-date   = dur-day dur-time]
     dur-time   = "T" (dur-hour / dur-minute / dur-second)
     dur-week   = 1*DIGIT "W"
     dur-hour   = 1*DIGIT "H" dur-minute]
     dur-minute = 1*DIGIT "M" dur-second]
     dur-second = 1*DIGIT "S"
     dur-day    = 1*DIGIT "D"

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    If the property permits, multiple "duration" values are
   specified by a COMMA character (US-ASCII decimal 44) separated list
   of values. The format is expressed as the <a href='#ref_ISO_8601'>[ISO 8601]</a> basic format for
   the duration of time. The format can represent durations in terms of
   weeks, days, hours, minutes, and seconds.

   No additional content value encoding (i.e., BACKSLASH character
   encoding) are defined for this value type.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    A duration of 15 days, 5 hours and 20 seconds would be:

     P15DT5H0M20S

   A duration of 7 weeks would be:

     P7W

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.3.7'>4.3.7 Float</h2>
<dl>
<dt id='Value_FLOAT'>Value Name</dt>
<dd class='ValueName'><pre>    FLOAT

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This value type is used to identify properties that contain
   a real number value.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    The value type is defined by the following
   notation:

     float      = ("+"] / "-") 1*DIGIT "." 1*DIGIT]

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    If the property permits, multiple "float" values are
   specified by a COMMA character (US-ASCII decimal 44) separated list
   of values.

   No additional content value encoding (i.e., BACKSLASH character
   encoding) is defined for this value type.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     1000000.0000001
     1.333
     -3.14

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.3.8'>4.3.8 Integer</h2>
<dl>
<dt id='Value_INTEGER'>Value Name</dt>
<dd class='ValueName'><pre>   INTEGER

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This value type is used to identify properties that contain
     a signed integer value.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    The value type is defined by the following
     notation:

     integer    = ("+"] / "-") 1*DIGIT

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    If the property permits, multiple "integer" values are
     specified by a COMMA character (US-ASCII decimal 44) separated list
     of values. The valid range for "integer" is -2147483648 to
     2147483647. If the sign is not specified, then the value is assumed
     to be positive.

     No additional content value encoding (i.e., BACKSLASH character
     encoding) is defined for this value type.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     1234567890
     -1234567890
     +1234567890
     432109876

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.3.9'>4.3.9 Period of Time</h2>
<dl>
<dt id='Value_PERIOD'>Value Name</dt>
<dd class='ValueName'><pre>    PERIOD

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This value type is used to identify values that contain a
   precise period of time.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    The data type is defined by the following
   notation:

     period     = period-explicit / period-start

     period-explicit = date-time "/" date-time
     ; <a href='#ref_ISO_8601'>[ISO 8601]</a> complete representation basic format for a period of
     ; time consisting of a start and end. The start MUST be before the
     ; end.

     period-start = date-time "/" dur-value
     ; <a href='#ref_ISO_8601'>[ISO 8601]</a> complete representation basic format for a period of
     ; time consisting of a start and positive duration of time.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    If the property permits, multiple "period" values are
   specified by a COMMA character (US-ASCII decimal 44) separated list
   of values. There are two forms of a period of time. First, a period
   of time is identified by its start and its end. This format is
   expressed as the <a href='#ref_ISO_8601'>[ISO 8601]</a> complete representation, basic format for
   "DATE-TIME" start of the period, followed by a SOLIDUS character
   (US-ASCII decimal 47), followed by the "DATE-TIME" of the end of the
   period. The start of the period MUST be before the end of the period.
   Second, a period of time can also be defined by a start and a
   positive duration of time. The format is expressed as the <a href='#ref_ISO_8601'>[ISO 8601]</a>
   complete representation, basic format for the "DATE-TIME" start of

   the period, followed by a SOLIDUS character (US-ASCII decimal 47),
   followed by the <a href='#ref_ISO_8601'>[ISO 8601]</a> basic format for "DURATION" of the period.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The period starting at 18:00:00 UTC, on January 1, 1997 and
   ending at 07:00:00 UTC on January 2, 1997 would be:

     19970101T180000Z/19970102T070000Z

   The period start at 18:00:00 on January 1, 1997 and lasting 5 hours
   and 30 minutes would be:

     19970101T180000Z/PT5H30M

   No additional content value encoding (i.e., BACKSLASH character
   encoding) is defined for this value type.

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.3.10'>4.3.10 Recurrence Rule</h2>
<dl>
<dt id='Value_RECUR'>Value Name</dt>
<dd class='ValueName'><pre>    RECUR

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This value type is used to identify properties that contain
   a recurrence rule specification.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    The value type is defined by the following
   notation:

     recur      = "FREQ"=freq *(

                ; either UNTIL or COUNT may appear in a 'recur',
                ; but UNTIL and COUNT MUST NOT occur in the same 'recur'

                ( ";" "UNTIL" "=" enddate ) /
                ( ";" "COUNT" "=" 1*DIGIT ) /

                ; the rest of these keywords are optional,
                ; but MUST NOT occur more than once

                ( ";" "INTERVAL" "=" 1*DIGIT )          /
                ( ";" "BYSECOND" "=" byseclist )        /
                ( ";" "BYMINUTE" "=" byminlist )        /
                ( ";" "BYHOUR" "=" byhrlist )           /
                ( ";" "BYDAY" "=" bywdaylist )          /
                ( ";" "BYMONTHDAY" "=" bymodaylist )    /
                ( ";" "BYYEARDAY" "=" byyrdaylist )     /
                ( ";" "BYWEEKNO" "=" bywknolist )       /
                ( ";" "BYMONTH" "=" bymolist )          /
                ( ";" "BYSETPOS" "=" bysplist )         /
                ( ";" "WKST" "=" weekday )              /

                ( ";" x-name "=" text )
                )

     freq       = "SECONDLY" / "MINUTELY" / "HOURLY" / "DAILY"
                / "WEEKLY" / "MONTHLY" / "YEARLY"

     enddate    = date
     enddate    =/ date-time            ;An UTC value

     byseclist  = seconds / ( seconds *("," seconds) )

     seconds    = 1DIGIT / 2DIGIT       ;0 to 59

     byminlist  = minutes / ( minutes *("," minutes) )

     minutes    = 1DIGIT / 2DIGIT       ;0 to 59

     byhrlist   = hour / ( hour *("," hour) )

     hour       = 1DIGIT / 2DIGIT       ;0 to 23

     bywdaylist = weekdaynum / ( weekdaynum *("," weekdaynum) )

     weekdaynum = (plus] ordwk / minus ordwk)] weekday

     plus       = "+"

     minus      = "-"

     ordwk      = 1DIGIT / 2DIGIT       ;1 to 53

     weekday    = "SU" / "MO" / "TU" / "WE" / "TH" / "FR" / "SA"
     ;Corresponding to SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY,
     ;FRIDAY, SATURDAY and SUNDAY days of the week.

     bymodaylist = monthdaynum / ( monthdaynum *("," monthdaynum) )

     monthdaynum = (plus] ordmoday) / (minus ordmoday)

     ordmoday   = 1DIGIT / 2DIGIT       ;1 to 31

     byyrdaylist = yeardaynum / ( yeardaynum *("," yeardaynum) )

     yeardaynum = (plus] ordyrday) / (minus ordyrday)

     ordyrday   = 1DIGIT / 2DIGIT / 3DIGIT      ;1 to 366

     bywknolist = weeknum / ( weeknum *("," weeknum) )

     weeknum    = (plus] ordwk) / (minus ordwk)

     bymolist   = monthnum / ( monthnum *("," monthnum) )

     monthnum   = 1DIGIT / 2DIGIT       ;1 to 12

     bysplist   = setposday / ( setposday *("," setposday) )

     setposday  = yeardaynum

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    If the property permits, multiple "recur" values are
   specified by a COMMA character (US-ASCII decimal 44) separated list
   of values. The value type is a structured value consisting of a list
   of one or more recurrence grammar parts. Each rule part is defined by
   a NAME=VALUE pair. The rule parts are separated from each other by
   the SEMICOLON character (US-ASCII decimal 59). The rule parts are not
   ordered in any particular sequence. Individual rule parts MUST only
   be specified once.

   The <a id="freq" rel="def" href="#freq">FREQ</a> rule part identifies the type of recurrence rule. This rule
   part MUST be specified in the recurrence rule. Valid values include
   SECONDLY, to specify repeating events based on an interval of a
   second or more; MINUTELY, to specify repeating events based on an
   interval of a minute or more; HOURLY, to specify repeating events
   based on an interval of an hour or more; DAILY, to specify repeating
   events based on an interval of a day or more; WEEKLY, to specify
   repeating events based on an interval of a week or more; MONTHLY, to
   specify repeating events based on an interval of a month or more; and
   YEARLY, to specify repeating events based on an interval of a year or
   more.

   The <a id="interval" rel="def" href="#interval">INTERVAL</a> rule part contains a positive integer representing how
   often the recurrence rule repeats. The default value is "1", meaning
   every second for a SECONDLY rule, or every minute for a MINUTELY
   rule, every hour for an HOURLY rule, every day for a DAILY rule,
   every week for a WEEKLY rule, every month for a MONTHLY rule and
   every year for a YEARLY rule.

   The <a id="until" rel="def" href="#until">UNTIL</a> rule part defines a date-time value which bounds the
   recurrence rule in an inclusive manner. If the value specified by
   <a id="until" rel="def" href="#until">UNTIL</a> is synchronized with the specified recurrence, this date or
   date-time becomes the last instance of the recurrence. If specified
   as a date-time value, then it MUST be specified in an UTC time
   format. If not present, and the <a id="count" rel="def" href="#count">COUNT</a> rule part is also not present,
   the RRULE is considered to repeat forever.

   The <a id="count" rel="def" href="#count">COUNT</a> rule part defines the number of occurrences at which to
   range-bound the recurrence. The "DTSTART" property value, if

   specified, counts as the first occurrence.

   The <a id="bysecond" rel="def" href="#bysecond">BYSECOND</a> rule part specifies a COMMA character (US-ASCII decimal
   44) separated list of seconds within a minute. Valid values are 0 to
   59. The <a id="byminute" rel="def" href="#byminute">BYMINUTE</a> rule part specifies a COMMA character (US-ASCII
   decimal 44) separated list of minutes within an hour. Valid values
   are 0 to 59. The <a id="byhour" rel="def" href="#byhour">BYHOUR</a> rule part specifies a COMMA character (US-
   ASCII decimal 44) separated list of hours of the day. Valid values
   are 0 to 23.

   The <a id="byday" rel="def" href="#byday">BYDAY</a> rule part specifies a COMMA character (US-ASCII decimal 44)
   separated list of days of the week; MO indicates Monday; TU indicates
   Tuesday; WE indicates Wednesday; TH indicates Thursday; FR indicates
   Friday; SA indicates Saturday; SU indicates Sunday.

   Each <a id="byday" rel="def" href="#byday">BYDAY</a> value can also be preceded by a positive (+n) or negative
   (-n) integer. If present, this indicates the nth occurrence of the
   specific day within the MONTHLY or YEARLY RRULE. For example, within
   a MONTHLY rule, +1MO (or simply 1MO) represents the first Monday
   within the month, whereas -1MO represents the last Monday of the
   month. If an integer modifier is not present, it means all days of
   this type within the specified frequency. For example, within a
   MONTHLY rule, MO represents all Mondays within the month.

   The <a id="bymonth" rel="def" href="#bymonth">BYMONTH</a>DAY rule part specifies a COMMA character (ASCII decimal
   44) separated list of days of the month. Valid values are 1 to 31 or
   -31 to -1. For example, -10 represents the tenth to the last day of
   the month.

   The <a id="byyearday" rel="def" href="#byyearday">BYYEARDAY</a> rule part specifies a COMMA character (US-ASCII decimal
   44) separated list of days of the year. Valid values are 1 to 366 or
   -366 to -1. For example, -1 represents the last day of the year
   (December 31st) and -306 represents the 306th to the last day of the
   year (March 1st).

   The <a id="byweekno" rel="def" href="#byweekno">BYWEEKNO</a> rule part specifies a COMMA character (US-ASCII decimal
   44) separated list of ordinals specifying weeks of the year. Valid
   values are 1 to 53 or -53 to -1. This corresponds to weeks according
   to week numbering as defined in <a href='#ref_ISO_8601'>[ISO 8601]</a>. A week is defined as a
   seven day period, starting on the day of the week defined to be the
   week start (see <a id="wkst" rel="def" href="#wkst">WKST</a>). Week number one of the calendar year is the
   first week which contains at least four (4) days in that calendar
   year. This rule part is only valid for YEARLY rules. For example, 3
   represents the third week of the year.

        Note: Assuming a Monday week start, week 53 can only occur when
        Thursday is January 1 or if it is a leap year and Wednesday is
        January 1.

   The <a id="bymonth" rel="def" href="#bymonth">BYMONTH</a> rule part specifies a COMMA character (US-ASCII decimal
   44) separated list of months of the year. Valid values are 1 to 12.

   The <a id="wkst" rel="def" href="#wkst">WKST</a> rule part specifies the day on which the workweek starts.
   Valid values are MO, TU, WE, TH, FR, SA and SU. This is significant
   when a WEEKLY RRULE has an interval greater than 1, and a <a id="byday" rel="def" href="#byday">BYDAY</a> rule
   part is specified. This is also significant when in a YEARLY RRULE
   when a <a id="byweekno" rel="def" href="#byweekno">BYWEEKNO</a> rule part is specified. The default value is MO.

   The <a id="bysetpos" rel="def" href="#bysetpos">BYSETPOS</a> rule part specifies a COMMA character (US-ASCII decimal
   44) separated list of values which corresponds to the nth occurrence
   within the set of events specified by the rule. Valid values are 1 to
   366 or -366 to -1. It MUST only be used in conjunction with another
   BYxxx rule part. For example "the last work day of the month" could
   be represented as:

     RRULE:<a id="freq" rel="def" href="#freq">FREQ</a>=MONTHLY;<a id="byday" rel="def" href="#byday">BYDAY</a>=MO,TU,WE,TH,FR;<a id="bysetpos" rel="def" href="#bysetpos">BYSETPOS</a>=-1

   Each <a id="bysetpos" rel="def" href="#bysetpos">BYSETPOS</a> value can include a positive (+n) or negative (-n)
   integer. If present, this indicates the nth occurrence of the
   specific occurrence within the set of events specified by the rule.

   If BYxxx rule part values are found which are beyond the available
   scope (ie, <a id="bymonth" rel="def" href="#bymonth">BYMONTH</a>DAY=30 in February), they are simply ignored.

   Information, not contained in the rule, necessary to determine the
   various recurrence instance start time and dates are derived from the
   Start Time (DTSTART) entry attribute. For example,
   "<a id="freq" rel="def" href="#freq">FREQ</a>=YEARLY;<a id="bymonth" rel="def" href="#bymonth">BYMONTH</a>=1" doesn't specify a specific day within the
   month or a time. This information would be the same as what is
   specified for DTSTART.

   BYxxx rule parts modify the recurrence in some manner. BYxxx rule
   parts for a period of time which is the same or greater than the
   frequency generally reduce or limit the number of occurrences of the
   recurrence generated. For example, "<a id="freq" rel="def" href="#freq">FREQ</a>=DAILY;<a id="bymonth" rel="def" href="#bymonth">BYMONTH</a>=1" reduces the
   number of recurrence instances from all days (if <a id="bymonth" rel="def" href="#bymonth">BYMONTH</a> tag is not
   present) to all days in January. BYxxx rule parts for a period of
   time less than the frequency generally increase or expand the number
   of occurrences of the recurrence. For example,
   "<a id="freq" rel="def" href="#freq">FREQ</a>=YEARLY;<a id="bymonth" rel="def" href="#bymonth">BYMONTH</a>=1,2" increases the number of days within the
   yearly recurrence set from 1 (if <a id="bymonth" rel="def" href="#bymonth">BYMONTH</a> tag is not present) to 2.

   If multiple BYxxx rule parts are specified, then after evaluating the
   specified <a id="freq" rel="def" href="#freq">FREQ</a> and <a id="interval" rel="def" href="#interval">INTERVAL</a> rule parts, the BYxxx rule parts are
   applied to the current set of evaluated occurrences in the following
   order: <a id="bymonth" rel="def" href="#bymonth">BYMONTH</a>, <a id="byweekno" rel="def" href="#byweekno">BYWEEKNO</a>, <a id="byyearday" rel="def" href="#byyearday">BYYEARDAY</a>, <a rel="def" href="#bymonth">BYMONTH</a>DAY, <a id="byday" rel="def" href="#byday">BYDAY</a>, <a id="byhour" rel="def" href="#byhour">BYHOUR</a>,
   <a id="byminute" rel="def" href="#byminute">BYMINUTE</a>, <a id="bysecond" rel="def" href="#bysecond">BYSECOND</a> and <a id="bysetpos" rel="def" href="#bysetpos">BYSETPOS</a>; then <a id="count" rel="def" href="#count">COUNT</a> and <a id="until" rel="def" href="#until">UNTIL</a> are evaluated.

   Here is an example of evaluating multiple BYxxx rule parts.

     DTSTART;TZID=US-Eastern:19970105T083000
     RRULE:<a id="freq" rel="def" href="#freq">FREQ</a>=YEARLY;<a id="interval" rel="def" href="#interval">INTERVAL</a>=2;<a id="bymonth" rel="def" href="#bymonth">BYMONTH</a>=1;<a id="byday" rel="def" href="#byday">BYDAY</a>=SU;<a id="byhour" rel="def" href="#byhour">BYHOUR</a>=8,9;
      <a id="byminute" rel="def" href="#byminute">BYMINUTE</a>=30

   First, the "<a id="interval" rel="def" href="#interval">INTERVAL</a>=2" would be applied to "<a id="freq" rel="def" href="#freq">FREQ</a>=YEARLY" to arrive
   at "every other year". Then, "<a id="bymonth" rel="def" href="#bymonth">BYMONTH</a>=1" would be applied to arrive
   at "every January, every other year". Then, "<a id="byday" rel="def" href="#byday">BYDAY</a>=SU" would be
   applied to arrive at "every Sunday in January, every other year".
   Then, "<a id="byhour" rel="def" href="#byhour">BYHOUR</a>=8,9" would be applied to arrive at "every Sunday in
   January at 8 AM and 9 AM, every other year". Then, "<a id="byminute" rel="def" href="#byminute">BYMINUTE</a>=30"
   would be applied to arrive at "every Sunday in January at 8:30 AM and
   9:30 AM, every other year". Then, lacking information from RRULE, the
   second is derived from DTSTART, to end up in "every Sunday in January
   at 8:30:00 AM and 9:30:00 AM, every other year". Similarly, if the
   <a id="byminute" rel="def" href="#byminute">BYMINUTE</a>, <a id="byhour" rel="def" href="#byhour">BYHOUR</a>, <a id="byday" rel="def" href="#byday">BYDAY</a>, <a id="bymonth" rel="def" href="#bymonth">BYMONTH</a>DAY or <a rel="def" href="#bymonth">BYMONTH</a> rule part were
   missing, the appropriate minute, hour, day or month would have been
   retrieved from the "DTSTART" property.

   No additional content value encoding (i.e., BACKSLASH character
   encoding) is defined for this value type.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is a rule which specifies 10 meetings which
   occur every other day:

     FREQ=DAILY;COUNT=10;INTERVAL=2

   There are other examples specified in the "RRULE" specification.

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.3.11'>4.3.11 Text</h2>
<dl>
<dt id='Value_TEXT'>Value Name</dt>
<dd class='ValueName'><pre>    TEXT

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This value type is used to identify values that contain human
   readable text.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    The character sets supported by this revision of
   iCalendar are UTF-8 and US ASCII thereof. The applicability to other
   character sets is for future work. The value type is defined by the
   following notation.

     text       = *(TSAFE-CHAR / ":" / DQUOTE / ESCAPED-CHAR)
     ; Folded according to description above

     ESCAPED-CHAR = "\\" / "\;" / "\," / "\N" / "\n")
        ; \\ encodes \, \N or \n encodes newline
        ; \; encodes ;, \, encodes ,

     TSAFE-CHAR = %x20-21 / %x23-2B / %x2D-39 / %x3C-5B
                  %x5D-7E / NON-US-ASCII
        ; Any character except CTLs not needed by the current
        ; character set, DQUOTE, ";", ":", "\", ","

     Note: Certain other character sets may require modification of the
     above definitions, but this is beyond the scope of this document.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    If the property permits, multiple "text" values are
   specified by a COMMA character (US-ASCII decimal 44) separated list
   of values.

   The language in which the text is represented can be controlled by
   the "LANGUAGE" property parameter.

   An intentional formatted text line break MUST only be included in a
   "TEXT" property value by representing the line break with the
   character sequence of BACKSLASH (US-ASCII decimal 92), followed by a
   LATIN SMALL LETTER N (US-ASCII decimal 110) or a LATIN CAPITAL LETTER
   N (US-ASCII decimal 78), that is "\n" or "\N".

   The "TEXT" property values may also contain special characters that
   are used to signify delimiters, such as a COMMA character for lists
   of values or a SEMICOLON character for structured values. In order to
   support the inclusion of these special characters in "TEXT" property
   values, they MUST be escaped with a BACKSLASH character. A BACKSLASH
   character (US-ASCII decimal 92) in a "TEXT" property value MUST be
   escaped with another BACKSLASH character. A COMMA character in a
   "TEXT" property value MUST be escaped with a BACKSLASH character
   (US-ASCII decimal 92). A SEMICOLON character in a "TEXT" property
   value MUST be escaped with a BACKSLASH character (US-ASCII decimal
   92).  However, a COLON character in a "TEXT" property value SHALL NOT
   be escaped with a BACKSLASH character.Example: A multiple line value
   of:

     Project XYZ Final Review
     Conference Room - 3B
     Come Prepared.

   would be represented as:

     Project XYZ Final Review\nConference Room - 3B\nCome Prepared.

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.3.12'>4.3.12 Time</h2>
<dl>
<dt id='Value_TIME'>Value Name</dt>
<dd class='ValueName'><pre>    TIME

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This value type is used to identify values that contain a
   time of day.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    The data type is defined by the following
   notation:

     time               = time-hour time-minute time-second time-utc]

     time-hour          = 2DIGIT        ;00-23
     time-minute        = 2DIGIT        ;00-59
     time-second        = 2DIGIT        ;00-60
     ;The "60" value is used to account for "leap" seconds.

     time-utc   = "Z"

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    If the property permits, multiple "time" values are
   specified by a COMMA character (US-ASCII decimal 44) separated list
   of values. No additional content value encoding (i.e., BACKSLASH
   character encoding) is defined for this value type.

   The "TIME" data type is used to identify values that contain a time
   of day. The format is based on the <a href='#ref_ISO_8601'>[ISO 8601]</a> complete
   representation, basic format for a time of day. The text format
   consists of a two-digit 24-hour of the day (i.e., values 0-23), two-
   digit minute in the hour (i.e., values 0-59), and two-digit seconds
   in the minute (i.e., values 0-60). The seconds value of 60 MUST only
   to be used to account for "leap" seconds. Fractions of a second are
   not supported by this format.

   In parallel to the "DATE-TIME" definition above, the "TIME" data type
   expresses time values in three forms:

   The form of time with UTC offset MUST NOT be used. For example, the
   following is NOT VALID for a time value:

     230000-0800        ;Invalid time format

   FORM #1 LOCAL TIME

   The local time form is simply a time value that does not contain the
   UTC designator nor does it reference a time zone. For example, 11:00
   PM:

     230000

   Time values of this type are said to be "floating" and are not bound
   to any time zone in particular. They are used to represent the same
   hour, minute, and second value regardless of which time zone is
   currently being observed. For example, an event can be defined that
   indicates that an individual will be busy from 11:00 AM to 1:00 PM
   every day, no matter which time zone the person is in. In these
   cases, a local time can be specified. The recipient of an iCalendar
   object with a property value consisting of a local time, without any
   relative time zone information, SHOULD interpret the value as being
   fixed to whatever time zone the ATTENDEE is in at any given moment.
   This means that two ATTENDEEs may participate in the same event at
   different UTC times; floating time SHOULD only be used where that is
   reasonable behavior.

   In most cases, a fixed time is desired. To properly communicate a
   fixed time in a property value, either UTC time or local time with
   time zone reference MUST be specified.

   The use of local time in a TIME value without the TZID property
   parameter is to be interpreted as a local time value, regardless of
   the existence of "VTIMEZONE" calendar components in the iCalendar
   object.

   FORM #2: UTC TIME

   UTC time, or absolute time, is identified by a LATIN CAPITAL LETTER Z
   suffix character (US-ASCII decimal 90), the UTC designator, appended
   to the time value. For example, the following represents 07:00 AM
   UTC:

     070000Z

   The TZID property parameter MUST NOT be applied to TIME properties
   whose time values are specified in UTC.

   FORM #3: LOCAL TIME AND TIME ZONE REFERENCE

   The local time with reference to time zone information form is
   identified by the use the TZID property parameter to reference the
   appropriate time zone definition. TZID is discussed in detail in the
   section on Time Zone.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following represents 8:30 AM in New York in Winter, five
   hours behind UTC, in each of the three formats using the "X-
   TIMEOFDAY" non-standard property:

     X-TIMEOFDAY:083000

     X-TIMEOFDAY:133000Z

     X-TIMEOFDAY;TZID=US-Eastern:083000

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.3.13'>4.3.13 URI</h2>
<dl>
<dt id='Value_URI'>Value Name</dt>
<dd class='ValueName'><pre>    URI

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This value type is used to identify values that contain a
   uniform resource identifier (URI) type of reference to the property
   value.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    The data type is defined by the following
   notation:

     uri        = &lt;As defined by any IETF RFC>

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This data type might be used to reference binary
   information, for values that are large, or otherwise undesirable to
   include directly in the iCalendar object.

   The URI value formats in RFC 1738, RFC 2111 and any other IETF
   registered value format can be specified.

   Any IANA registered URI format can be used. These include, but are
   not limited to, those defined in RFC 1738 and RFC 2111.

   When a property parameter value is a URI value type, the URI MUST be
   specified as a quoted-string value.

   No additional content value encoding (i.e., BACKSLASH character
   encoding) is defined for this value type.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is a URI for a network file:

     http://host1.com/my-report.txt

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.3.14'>4.3.14 UTC Offset</h2>
<dl>
<dt id='Value_UTC-OFFSET'>Value Name</dt>
<dd class='ValueName'><pre>    UTC-OFFSET

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This value type is used to identify properties that contain
   an offset from UTC to local time.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    The data type is defined by the following
   notation:

     utc-offset = time-numzone  ;As defined above in time data type

     time-numzone       = ("+" / "-") time-hour time-minute time-
     second]

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The PLUS SIGN character MUST be specified for positive
   UTC offsets (i.e., ahead of UTC). The value of "-0000" and "-000000"
   are not allowed. The time-second, if present, may not be 60; if
   absent, it defaults to zero.

   No additional content value encoding (i.e., BACKSLASH character
   encoding) is defined for this value type.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following UTC offsets are given for standard time for
   New York (five hours behind UTC) and Geneva (one hour ahead of UTC):

     -0500

     +0100

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.4'>4.4 iCalendar Object</h2>
<pre>
   The Calendaring and Scheduling Core Object is a collection of
   calendaring and scheduling information. Typically, this information
   will consist of a single iCalendar object. However, multiple
   iCalendar objects can be sequentially grouped together. The first
   line and last line of the iCalendar object MUST contain a pair of
   iCalendar object delimiter strings. The syntax for an iCalendar
   object is as follows:

     icalobject = 1*("BEGIN" ":" "VCALENDAR" CRLF
                  icalbody
                  "END" ":" "VCALENDAR" CRLF)

   The following is a simple example of an iCalendar object:

     BEGIN:VCALENDAR
     VERSION:2.0
     PRODID:-//hacksw/handcal//NONSGML v1.0//EN
     BEGIN:VEVENT
     DTSTART:19970714T170000Z
     DTEND:19970715T035959Z
     SUMMARY:Bastille Day Party
     END:VEVENT
     END:VCALENDAR

</pre>
</div>
<div><h2 id='sec4.5'>4.5 Property</h2>
<pre>
   A property is the definition of an individual attribute describing a
   calendar or a calendar component. A property takes the form defined
   by the "contentline" notation defined in section 4.1.1.

   The following is an example of a property:

     DTSTART:19960415T133000Z

   This memo imposes no ordering of properties within an iCalendar
   object.

   Property names, parameter names and enumerated parameter values are
   case insensitive. For example, the property name "DUE" is the same as
   "due" and "Due", DTSTART;TZID=US-Eastern:19980714T120000 is the same
   as DtStart;TzID=US-Eastern:19980714T120000.

</pre>
</div>
<div><h2 id='sec4.6'>4.6 Calendar Components</h2>
<pre>
   The body of the iCalendar object consists of a sequence of calendar
   properties and one or more calendar components. The calendar
   properties are attributes that apply to the calendar as a whole. The
   calendar components are collections of properties that express a
   particular calendar semantic. For example, the calendar component can
   specify an event, a to-do, a journal entry, time zone information, or
   free/busy time information, or an alarm.

   The body of the iCalendar object is defined by the following
   notation:

     icalbody   = calprops component

     calprops   = 2*(

                ; 'prodid' and 'version' are both REQUIRED,
                ; but MUST NOT occur more than once

                prodid /version /

                ; 'calscale' and 'method' are optional,
                ; but MUST NOT occur more than once

                calscale        /
                method          /

                x-prop

                )

     component  = 1*(eventc / todoc / journalc / freebusyc /
                / timezonec / iana-comp / x-comp)

     iana-comp  = "BEGIN" ":" iana-token CRLF

                  1*contentline

                  "END" ":" iana-token CRLF

     x-comp     = "BEGIN" ":" x-name CRLF

                  1*contentline

                  "END" ":" x-name CRLF

   An iCalendar object MUST include the "PRODID" and "VERSION" calendar
   properties. In addition, it MUST include at least one calendar
   component. Special forms of iCalendar objects are possible to publish
   just busy time (i.e., only a "VFREEBUSY" calendar component) or time
   zone (i.e., only a "VTIMEZONE" calendar component) information. In
   addition, a complex iCalendar object is possible that is used to
   capture a complete snapshot of the contents of a calendar (e.g.,
   composite of many different calendar components). More commonly, an
   iCalendar object will consist of just a single "VEVENT", "VTODO" or
   "VJOURNAL" calendar component.

</pre>
</div>
<div><h2 id='sec4.6.1'>4.6.1 Event Component</h2>
<dl>
<dt id='Vevent'>Component Name</dt>
<dd class='ComponentName'><pre>   VEVENT

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    Provide a grouping of component properties that describe an
   event.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    A "VEVENT" calendar component is defined by the
   following notation:

     eventc     = "BEGIN" ":" "VEVENT" CRLF
                  eventprop *alarmc
                  "END" ":" "VEVENT" CRLF

     eventprop  = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                class / created / description / dtstart / geo /

                last-mod / location / organizer / priority /
                dtstamp / seq / status / summary / transp /
                uid / url / recurid /

                ; either 'dtend' or 'duration' may appear in
                ; a 'eventprop', but 'dtend' and 'duration'
                ; MUST NOT occur in the same 'eventprop'

                dtend / duration /

                ; the following are optional,
                ; and MAY occur more than once

                attach / attendee / categories / comment /
                contact / exdate / exrule / rstatus / related /
                resources / rdate / rrule / x-prop

                )

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    A "VEVENT" calendar component is a grouping of component
   properties, and possibly including "VALARM" calendar components, that
   represents a scheduled amount of time on a calendar. For example, it
   can be an activity; such as a one-hour long, department meeting from
   8:00 AM to 9:00 AM, tomorrow. Generally, an event will take up time
   on an individual calendar. Hence, the event will appear as an opaque
   interval in a search for busy time. Alternately, the event can have
   its Time Transparency set to "TRANSPARENT" in order to prevent
   blocking of the event in searches for busy time.

   The "VEVENT" is also the calendar component used to specify an
   anniversary or daily reminder within a calendar. These events have a
   DATE value type for the "DTSTART" property instead of the default
   data type of DATE-TIME. If such a "VEVENT" has a "DTEND" property, it
   MUST be specified as a DATE value also. The anniversary type of
   "VEVENT" can span more than one date (i.e, "DTEND" property value is
   set to a calendar date after the "DTSTART" property value).

   The "DTSTART" property for a "VEVENT" specifies the inclusive start
   of the event. For recurring events, it also specifies the very first
   instance in the recurrence set. The "DTEND" property for a "VEVENT"
   calendar component specifies the non-inclusive end of the event. For
   cases where a "VEVENT" calendar component specifies a "DTSTART"
   property with a DATE data type but no "DTEND" property, the events
   non-inclusive end is the end of the calendar date specified by the
   "DTSTART" property. For cases where a "VEVENT" calendar component
   specifies a "DTSTART" property with a DATE-TIME data type but no
   "DTEND" property, the event ends on the same calendar date and time
   of day specified by the "DTSTART" property.

   The "VEVENT" calendar component cannot be nested within another
   calendar component. However, "VEVENT" calendar components can be
   related to each other or to a "VTODO" or to a "VJOURNAL" calendar
   component with the "RELATED-TO" property.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of the "VEVENT" calendar
   component used to represent a meeting that will also be opaque to
   searches for busy time:

     BEGIN:VEVENT
     UID:19970901T130000Z-123401@host.com
     DTSTAMP:19970901T1300Z
     DTSTART:19970903T163000Z
     DTEND:19970903T190000Z
     SUMMARY:Annual Employee Review
     CLASS:PRIVATE
     CATEGORIES:BUSINESS,HUMAN RESOURCES
     END:VEVENT

   The following is an example of the "VEVENT" calendar component used
   to represent a reminder that will not be opaque, but rather
   transparent, to searches for busy time:

     BEGIN:VEVENT
     UID:19970901T130000Z-123402@host.com
     DTSTAMP:19970901T1300Z
     DTSTART:19970401T163000Z
     DTEND:19970402T010000Z
     SUMMARY:Laurel is in sensitivity awareness class.
     CLASS:PUBLIC
     CATEGORIES:BUSINESS,HUMAN RESOURCES
     TRANSP:TRANSPARENT
     END:VEVENT

   The following is an example of the "VEVENT" calendar component used
   to represent an anniversary that will occur annually. Since it takes
   up no time, it will not appear as opaque in a search for busy time;
   no matter what the value of the "TRANSP" property indicates:

     BEGIN:VEVENT
     UID:19970901T130000Z-123403@host.com
     DTSTAMP:19970901T1300Z
     DTSTART:19971102
     SUMMARY:Our Blissful Anniversary
     CLASS:CONFIDENTIAL
     CATEGORIES:ANNIVERSARY,PERSONAL,SPECIAL OCCASION
     RRULE:FREQ=YEARLY
     END:VEVENT

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.6.2'>4.6.2 To-do Component</h2>
<dl>
<dt id='Vtodo'>Component Name</dt>
<dd class='ComponentName'><pre>    VTODO

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    Provide a grouping of calendar properties that describe a
   to-do.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    A "VTODO" calendar component is defined by the
   following notation:

     todoc      = "BEGIN" ":" "VTODO" CRLF
                  todoprop *alarmc
                  "END" ":" "VTODO" CRLF

     todoprop   = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                class / completed / created / description / dtstamp /
                dtstart / geo / last-mod / location / organizer /
                percent / priority / recurid / seq / status /
                summary / uid / url /

                ; either 'due' or 'duration' may appear in
                ; a 'todoprop', but 'due' and 'duration'
                ; MUST NOT occur in the same 'todoprop'

                due / duration /

                ; the following are optional,
                ; and MAY occur more than once
                attach / attendee / categories / comment / contact /
                exdate / exrule / rstatus / related / resources /
                rdate / rrule / x-prop

                )

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    A "VTODO" calendar component is a grouping of component
   properties and possibly "VALARM" calendar components that represent
   an action-item or assignment. For example, it can be used to
   represent an item of work assigned to an individual; such as "turn in
   travel expense today".

   The "VTODO" calendar component cannot be nested within another
   calendar component. However, "VTODO" calendar components can be
   related to each other or to a "VTODO" or to a "VJOURNAL" calendar
   component with the "RELATED-TO" property.

   A "VTODO" calendar component without the "DTSTART" and "DUE" (or
   "DURATION") properties specifies a to-do that will be associated with
   each successive calendar date, until it is completed.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of a "VTODO" calendar component:

     BEGIN:VTODO
     UID:19970901T130000Z-123404@host.com
     DTSTAMP:19970901T1300Z
     DTSTART:19970415T133000Z
     DUE:19970416T045959Z
     SUMMARY:1996 Income Tax Preparation
     CLASS:CONFIDENTIAL
     CATEGORIES:FAMILY,FINANCE
     PRIORITY:1
     STATUS:NEEDS-ACTION
     END:VTODO

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.6.3'>4.6.3 Journal Component</h2>
<dl>
<dt id='Vjournal'>Component Name</dt>
<dd class='ComponentName'><pre>    VJOURNAL

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    Provide a grouping of component properties that describe a
   journal entry.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    A "VJOURNAL" calendar component is defined by the
   following notation:

     journalc   = "BEGIN" ":" "VJOURNAL" CRLF
                  jourprop
                  "END" ":" "VJOURNAL" CRLF

     jourprop   = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                class / created / description / dtstart / dtstamp /
                last-mod / organizer / recurid / seq / status /
                summary / uid / url /

                ; the following are optional,
                ; and MAY occur more than once

                attach / attendee / categories / comment /
                contact / exdate / exrule / related / rdate /
                rrule / rstatus / x-prop

                )

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    A "VJOURNAL" calendar component is a grouping of
   component properties that represent one or more descriptive text
   notes associated with a particular calendar date. The "DTSTART"
   property is used to specify the calendar date that the journal entry
   is associated with. Generally, it will have a DATE value data type,
   but it can also be used to specify a DATE-TIME value data type.
   Examples of a journal entry include a daily record of a legislative
   body or a journal entry of individual telephone contacts for the day
   or an ordered list of accomplishments for the day. The "VJOURNAL"
   calendar component can also be used to associate a document with a
   calendar date.

   The "VJOURNAL" calendar component does not take up time on a
   calendar. Hence, it does not play a role in free or busy time
   searches - - it is as though it has a time transparency value of
   TRANSPARENT. It is transparent to any such searches.

   The "VJOURNAL" calendar component cannot be nested within another
   calendar component. However, "VJOURNAL" calendar components can be
   related to each other or to a "VEVENT" or to a "VTODO" calendar
   component, with the "RELATED-TO" property.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of the "VJOURNAL" calendar
   component:

     BEGIN:VJOURNAL
     UID:19970901T130000Z-123405@host.com
     DTSTAMP:19970901T1300Z
     DTSTART;VALUE=DATE:19970317
     SUMMARY:Staff meeting minutes
     DESCRIPTION:1. Staff meeting: Participants include Joe\, Lisa
       and Bob. Aurora project plans were reviewed. There is currently
       no budget reserves for this project. Lisa will escalate to
       management. Next meeting on Tuesday.\n
       2. Telephone Conference: ABC Corp. sales representative called
       to discuss new printer. Promised to get us a demo by Friday.\n
       3. Henry Miller (Handsoff Insurance): Car was totaled by tree.
       Is looking into a loaner car. 654-2323 (tel).
     END:VJOURNAL

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.6.4'>4.6.4 Free/Busy Component</h2>
<dl>
<dt id='Vfreebusy'>Component Name</dt>
<dd class='ComponentName'><pre>    VFREEBUSY

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    Provide a grouping of component properties that describe
   either a request for free/busy time, describe a response to a request
   for free/busy time or describe a published set of busy time.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    A "VFREEBUSY" calendar component is defined by the
   following notation:

     freebusyc  = "BEGIN" ":" "VFREEBUSY" CRLF
                  fbprop
                  "END" ":" "VFREEBUSY" CRLF

     fbprop     = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                contact / dtstart / dtend / duration / dtstamp /
                organizer / uid / url /

                ; the following are optional,
                ; and MAY occur more than once

                attendee / comment / freebusy / rstatus / x-prop

                )

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    A "VFREEBUSY" calendar component is a grouping of
   component properties that represents either a request for, a reply to
   a request for free or busy time information or a published set of
   busy time information.

   When used to request free/busy time information, the "ATTENDEE"
   property specifies the calendar users whose free/busy time is being
   requested; the "ORGANIZER" property specifies the calendar user who
   is requesting the free/busy time; the "DTSTART" and "DTEND"
   properties specify the window of time for which the free/busy time is
   being requested; the "UID" and "DTSTAMP" properties are specified to
   assist in proper sequencing of multiple free/busy time requests.

   When used to reply to a request for free/busy time, the "ATTENDEE"
   property specifies the calendar user responding to the free/busy time
   request; the "ORGANIZER" property specifies the calendar user that
   originally requested the free/busy time; the "FREEBUSY" property
   specifies the free/busy time information (if it exists); and the

   "UID" and "DTSTAMP" properties are specified to assist in proper
   sequencing of multiple free/busy time replies.

   When used to publish busy time, the "ORGANIZER" property specifies
   the calendar user associated with the published busy time; the
   "DTSTART" and "DTEND" properties specify an inclusive time window
   that surrounds the busy time information; the "FREEBUSY" property
   specifies the published busy time information; and the "DTSTAMP"
   property specifies the date/time that iCalendar object was created.

   The "VFREEBUSY" calendar component cannot be nested within another
   calendar component. Multiple "VFREEBUSY" calendar components can be
   specified within an iCalendar object. This permits the grouping of
   Free/Busy information into logical collections, such as monthly
   groups of busy time information.

   The "VFREEBUSY" calendar component is intended for use in iCalendar
   object methods involving requests for free time, requests for busy
   time, requests for both free and busy, and the associated replies.

   Free/Busy information is represented with the "FREEBUSY" property.
   This property provides a terse representation of time periods. One or
   more "FREEBUSY" properties can be specified in the "VFREEBUSY"
   calendar component.

   When present in a "VFREEBUSY" calendar component, the "DTSTART" and
   "DTEND" properties SHOULD be specified prior to any "FREEBUSY"
   properties. In a free time request, these properties can be used in
   combination with the "DURATION" property to represent a request for a
   duration of free time within a specified window of time.

   The recurrence properties ("RRULE", "EXRULE", "RDATE", "EXDATE") are
   not permitted within a "VFREEBUSY" calendar component. Any recurring
   events are resolved into their individual busy time periods using the
   "FREEBUSY" property.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of a "VFREEBUSY" calendar
   component used to request free or busy time information:

     BEGIN:VFREEBUSY
     ORGANIZER:MAILTO:jane_doe@host1.com
     ATTENDEE:MAILTO:john_public@host2.com
     DTSTART:19971015T050000Z
     DTEND:19971016T050000Z
     DTSTAMP:19970901T083000Z
     END:VFREEBUSY

   The following is an example of a "VFREEBUSY" calendar component used
   to reply to the request with busy time information:

     BEGIN:VFREEBUSY
     ORGANIZER:MAILTO:jane_doe@host1.com
     ATTENDEE:MAILTO:john_public@host2.com
     DTSTAMP:19970901T100000Z
     FREEBUSY;VALUE=PERIOD:19971015T050000Z/PT8H30M,
      19971015T160000Z/PT5H30M,19971015T223000Z/PT6H30M
     URL:http://host2.com/pub/busy/jpublic-01.ifb
     COMMENT:This iCalendar file contains busy time information for
       the next three months.
     END:VFREEBUSY

   The following is an example of a "VFREEBUSY" calendar component used
   to publish busy time information.

     BEGIN:VFREEBUSY
     ORGANIZER:jsmith@host.com
     DTSTART:19980313T141711Z
     DTEND:19980410T141711Z
     FREEBUSY:19980314T233000Z/19980315T003000Z
     FREEBUSY:19980316T153000Z/19980316T163000Z
     FREEBUSY:19980318T030000Z/19980318T040000Z
     URL:http://www.host.com/calendar/busytime/jsmith.ifb
     END:VFREEBUSY

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.6.5'>4.6.5 Time Zone Component</h2>
<dl>
<dt id='Vtimezone'>Component Name</dt>
<dd class='ComponentName'><pre>    VTIMEZONE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    Provide a grouping of component properties that defines a
   time zone.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    A "VTIMEZONE" calendar component is defined by the
   following notation:

     timezonec  = "BEGIN" ":" "VTIMEZONE" CRLF

                  2*(

                  ; 'tzid' is required, but MUST NOT occur more
                  ; than once

                tzid /

                  ; 'last-mod' and 'tzurl' are optional,
                but MUST NOT occur more than once

                last-mod / tzurl /

                  ; one of 'standardc' or 'daylightc' MUST occur
                ..; and each MAY occur more than once.

                standardc / daylightc /

                ; the following is optional,
                ; and MAY occur more than once

                  x-prop

                  )

                  "END" ":" "VTIMEZONE" CRLF

     standardc  = "BEGIN" ":" "STANDARD" CRLF

                  tzprop

                  "END" ":" "STANDARD" CRLF

     daylightc  = "BEGIN" ":" "DAYLIGHT" CRLF

                  tzprop

                  "END" ":" "DAYLIGHT" CRLF

     tzprop     = 3*(

                ; the following are each REQUIRED,
                ; but MUST NOT occur more than once

                dtstart / tzoffsetto / tzoffsetfrom /

                ; the following are optional,
                ; and MAY occur more than once

                comment / rdate / rrule / tzname / x-prop

                )

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    A time zone is unambiguously defined by the set of time
   measurement rules determined by the governing body for a given
   geographic area. These rules describe at a minimum the base  offset
   from UTC for the time zone, often referred to as the Standard Time
   offset. Many locations adjust their Standard Time forward or backward
   by one hour, in order to accommodate seasonal changes in number of

   daylight hours, often referred to as Daylight  Saving Time. Some
   locations adjust their time by a fraction of an hour. Standard Time
   is also known as Winter Time. Daylight Saving Time is also known as
   Advanced Time, Summer Time, or Legal Time in certain countries. The
   following table shows the changes in time zone rules in effect for
   New York City starting from 1967. Each line represents a description
   or rule for a particular observance.

     Effective Observance Rule

     Date       (Date/Time)             Offset  Abbreviation

     1967-*     last Sun in Oct, 02:00  -0500   EST

     1967-1973  last Sun in Apr, 02:00  -0400   EDT

     1974-1974  Jan 6,  02:00           -0400   EDT

     1975-1975  Feb 23, 02:00           -0400   EDT

     1976-1986  last Sun in Apr, 02:00  -0400   EDT

     1987-*     first Sun in Apr, 02:00 -0400   EDT

        Note: The specification of a global time zone registry is not
        addressed by this document and is left for future study.
        However, implementers may find the Olson time zone database <a href='#ref_TZ'>[TZ]</a>
        a useful reference. It is an informal, public-domain collection
        of time zone information, which is currently being maintained by
        volunteer Internet participants, and is used in several
        operating systems. This database contains current and historical
        time zone information for a wide variety of locations around the
        globe; it provides a time zone identifier for every unique time
        zone rule set in actual use since 1970, with historical data
        going back to the introduction of standard time.

   Interoperability between two calendaring and scheduling applications,
   especially for recurring events, to-dos or journal entries, is
   dependent on the ability to capture and convey date and time
   information in an unambiguous format. The specification of current
   time zone information is integral to this behavior.

   If present, the "VTIMEZONE" calendar component defines the set of
   Standard Time and Daylight Saving Time observances (or rules) for a
   particular time zone for a given interval of time. The "VTIMEZONE"
   calendar component cannot be nested within other calendar components.
   Multiple "VTIMEZONE" calendar components can exist in an iCalendar
   object. In this situation, each "VTIMEZONE" MUST represent a unique

   time zone definition. This is necessary for some classes of events,
   such as airline flights, that start in one time zone and end in
   another.

   The "VTIMEZONE" calendar component MUST be present if the iCalendar
   object contains an RRULE that generates dates on both sides of a time
   zone shift (e.g. both in Standard Time and Daylight Saving Time)
   unless the iCalendar object intends to convey a floating time (See
   the section "4.1.10.11 Time" for proper interpretation of floating
   time). It can be present if the iCalendar object does not contain
   such a RRULE. In addition, if a RRULE is present, there MUST be valid
   time zone information for all recurrence instances.

   The "VTIMEZONE" calendar component MUST include the "TZID" property
   and at least one definition of a standard or daylight component. The
   standard or daylight component MUST include the "DTSTART",
   "TZOFFSETFROM" and "TZOFFSETTO" properties.

   An individual "VTIMEZONE" calendar component MUST be specified for
   each unique "TZID" parameter value specified in the iCalendar object.

   Each "VTIMEZONE" calendar component consists of a collection of one
   or more sub-components that describe the rule for a particular
   observance (either a Standard Time or a Daylight Saving Time
   observance). The "<a id="standard" rel="def" href="#standard">STANDARD</a>" sub-component consists of a collection of
   properties that describe Standard Time. The "<a id="daylight" rel="def" href="#daylight">DAYLIGHT</a>" sub-component
   consists of a collection of properties that describe Daylight Saving
   Time. In general this collection of properties consists of:

        - the first onset date-time for the observance

        - the last onset date-time for the observance, if a last onset
          is known.

        - the offset to be applied for the observance

        - a rule that describes the day and time when the observance
          takes effect

        - an optional name for the observance

   For a given time zone, there may be multiple unique definitions of
   the observances over a period of time. Each observance is described
   using either a "<a id="standard" rel="def" href="#standard">STANDARD</a>" or "<a id="daylight" rel="def" href="#daylight">DAYLIGHT</a>" sub-component. The collection
   of these sub-components is used to describe the time zone for a given
   period of time. The offset to apply at any given time is found by
   locating the observance that has the last onset date and time before
   the time in question, and using the offset value from that

   observance.

   The top-level properties in a "VTIMEZONE" calendar component are:

   The mandatory "TZID" property is a text value that uniquely
   identifies the VTIMZONE calendar component within the scope of an
   iCalendar object.

   The optional "LAST-MODIFIED" property is a UTC value that specifies
   the date and time that this time zone definition was last updated.

   The optional "TZURL" property is url value that points to a published
   VTIMEZONE definition. TZURL SHOULD refer to a resource that is
   accessible by anyone who might need to interpret the object. This
   SHOULD NOT normally be a file: URL or other URL that is not widely-
   accessible.

   The collection of properties that are used to define the <a id="standard" rel="def" href="#standard">STANDARD</a> and
   <a id="daylight" rel="def" href="#daylight">DAYLIGHT</a> sub-components include:

   The mandatory "DTSTART" property gives the effective onset date and
   local time for the time zone sub-component definition. "DTSTART" in
   this usage MUST be specified as a local DATE-TIME value.

   The mandatory "TZOFFSETFROM" property gives the UTC offset which is
   in use when the onset of this time zone observance begins.
   "TZOFFSETFROM" is combined with "DTSTART" to define the effective
   onset for the time zone sub-component definition. For example, the
   following represents the time at which the observance of Standard
   Time took effect in Fall 1967 for New York City:

     DTSTART:19671029T020000

     TZOFFSETFROM:-0400

   The mandatory "TZOFFSETTO " property gives the UTC offset for the
   time zone sub-component (Standard Time or Daylight Saving Time) when
   this observance is in use.

   The optional "TZNAME" property is the customary name for the time
   zone. It may be specified multiple times, to allow for specifying
   multiple language variants of the time zone names. This could be used
   for displaying dates.

   If specified, the onset for the observance defined by the time zone
   sub-component is defined by either the "RRULE" or "RDATE" property.
   If neither is specified, only one sub-component can be specified in
   the "VTIMEZONE" calendar component and it is assumed that the single

   observance specified is always in effect.

   The "RRULE" property defines the recurrence rule for the onset of the
   observance defined by this time zone sub-component. Some specific
   requirements for the usage of RRULE for this purpose include:

        - If observance is known to have an effective end date, the
        "UNTIL" recurrence rule parameter MUST be used to specify the
        last valid onset of this observance (i.e., the UNTIL date-time
        will be equal to the last instance generated by the recurrence
        pattern). It MUST be specified in UTC time.

        - The "DTSTART" and the "TZOFFSETTO" properties MUST be used
        when generating the onset date-time values (instances) from the
        RRULE.

   Alternatively, the "RDATE" property can be used to define the onset
   of the observance by giving the individual onset date and times.
   "RDATE" in this usage MUST be specified as a local DATE-TIME value in
   UTC time.

   The optional "COMMENT" property is also allowed for descriptive
   explanatory text.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following are examples of the "VTIMEZONE" calendar
   component:

   This is an example showing time zone information for the Eastern
   United States using "RDATE" property. Note that this is only suitable
   for a recurring event that starts on or later than April 6, 1997 at
   03:00:00 EDT (i.e., the earliest effective transition date and time)
   and ends no later than April 7, 1998 02:00:00 EST (i.e., latest valid
   date and time for EST in this scenario). For example, this can be
   used for a recurring event that occurs every Friday, 8am-9:00 AM,
   starting June 1, 1997, ending December 31, 1997.

     BEGIN:VTIMEZONE
     TZID:US-Eastern
     LAST-MODIFIED:19870101T000000Z
     BEGIN:STANDARD
     DTSTART:19971026T020000
     RDATE:19971026T020000
     TZOFFSETFROM:-0400
     TZOFFSETTO:-0500
     TZNAME:EST
     END:STANDARD
     BEGIN:DAYLIGHT
     DTSTART:19971026T020000

     RDATE:19970406T020000
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     END:VTIMEZONE

   This is a simple example showing the current time zone rules for the
   Eastern United States using a RRULE recurrence pattern. Note that
   there is no effective end date to either of the Standard Time or
   Daylight Time rules. This information would be valid for a recurring
   event starting today and continuing indefinitely.

     BEGIN:VTIMEZONE
     TZID:US-Eastern
     LAST-MODIFIED:19870101T000000Z
     TZURL:http://zones.stds_r_us.net/tz/US-Eastern
     BEGIN:STANDARD
     DTSTART:19671029T020000
     RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
     TZOFFSETFROM:-0400
     TZOFFSETTO:-0500
     TZNAME:EST
     END:STANDARD
     BEGIN:DAYLIGHT
     DTSTART:19870405T020000
     RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     END:VTIMEZONE

   This is an example showing a fictitious set of rules for the Eastern
   United States, where the Daylight Time rule has an effective end date
   (i.e., after that date, Daylight Time is no longer observed).

     BEGIN:VTIMEZONE
     TZID:US--Fictitious-Eastern
     LAST-MODIFIED:19870101T000000Z
     BEGIN:STANDARD
     DTSTART:19671029T020000
     RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
     TZOFFSETFROM:-0400
     TZOFFSETTO:-0500
     TZNAME:EST
     END:STANDARD

     BEGIN:DAYLIGHT
     DTSTART:19870405T020000
     RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=19980404T070000Z
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     END:VTIMEZONE

   This is an example showing a fictitious set of rules for the Eastern
   United States, where the first Daylight Time rule has an effective
   end date. There is a second Daylight Time rule that picks up where
   the other left off.

     BEGIN:VTIMEZONE
     TZID:US--Fictitious-Eastern
     LAST-MODIFIED:19870101T000000Z
     BEGIN:STANDARD
     DTSTART:19671029T020000
     RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
     TZOFFSETFROM:-0400
     TZOFFSETTO:-0500
     TZNAME:EST
     END:STANDARD
     BEGIN:DAYLIGHT
     DTSTART:19870405T020000
     RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=19980404T070000Z
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     BEGIN:DAYLIGHT
     DTSTART:19990424T020000
     RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=4
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     END:VTIMEZONE

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.6.6'>4.6.6 Alarm Component</h2>
<dl>
<dt id='Valarm'>Component Name</dt>
<dd class='ComponentName'><pre>    VALARM

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    Provide a grouping of component properties that define an
   alarm.

</pre>
</dd>
<dt>Formal Definition</dt>
<dd class='FormalDefinition'><pre>    A "VALARM" calendar component is defined by the
   following notation:

          alarmc     = "BEGIN" ":" "VALARM" CRLF
                       (audioprop / dispprop / emailprop / procprop)
                       "END" ":" "VALARM" CRLF

     audioprop  = 2*(

                ; 'action' and 'trigger' are both REQUIRED,
                ; but MUST NOT occur more than once

                action / trigger /

                ; 'duration' and 'repeat' are both optional,
                ; and MUST NOT occur more than once each,
                ; but if one occurs, so MUST the other

                duration / repeat /

                ; the following is optional,
                ; but MUST NOT occur more than once

                attach /

                ; the following is optional,
                ; and MAY occur more than once

                x-prop

                )



     dispprop   = 3*(

                ; the following are all REQUIRED,
                ; but MUST NOT occur more than once

                action / description / trigger /

                ; 'duration' and 'repeat' are both optional,
                ; and MUST NOT occur more than once each,
                ; but if one occurs, so MUST the other

                duration / repeat /

                ; the following is optional,

                ; and MAY occur more than once

                *x-prop

                )



     emailprop  = 5*(

                ; the following are all REQUIRED,
                ; but MUST NOT occur more than once

                action / description / trigger / summary

                ; the following is REQUIRED,
                ; and MAY occur more than once

                attendee /

                ; 'duration' and 'repeat' are both optional,
                ; and MUST NOT occur more than once each,
                ; but if one occurs, so MUST the other

                duration / repeat /

                ; the following are optional,
                ; and MAY occur more than once

                attach / x-prop

                )



     procprop   = 3*(

                ; the following are all REQUIRED,
                ; but MUST NOT occur more than once

                action / attach / trigger /

                ; 'duration' and 'repeat' are both optional,
                ; and MUST NOT occur more than once each,
                ; but if one occurs, so MUST the other

                duration / repeat /

                ; 'description' is optional,
                ; and MUST NOT occur more than once

                description /

                ; the following is optional,
                ; and MAY occur more than once

                x-prop

                )

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    A "VALARM" calendar component is a grouping of component
   properties that is a reminder or alarm for an event or a to-do. For
   example, it may be used to define a reminder for a pending event or
   an overdue to-do.

   The "VALARM" calendar component MUST include the "ACTION" and
   "TRIGGER" properties. The "ACTION" property further constrains the
   "VALARM" calendar component in the following ways:

   When the action is "AUDIO", the alarm can also include one and only
   one "ATTACH" property, which MUST point to a sound resource, which is
   rendered when the alarm is triggered.

   When the action is "DISPLAY", the alarm MUST also include a
   "DESCRIPTION" property, which contains the text to be displayed when
   the alarm is triggered.

   When the action is "EMAIL", the alarm MUST include a "DESCRIPTION"
   property, which contains the text to be used as the message body, a
   "SUMMARY" property, which contains the text to be used as the message
   subject, and one or more "ATTENDEE" properties, which contain the
   email address of attendees to receive the message. It can also
   include one or more "ATTACH" properties, which are intended to be
   sent as message attachments. When the alarm is triggered, the email
   message is sent.

   When the action is "PROCEDURE", the alarm MUST include one and only
   one "ATTACH" property, which MUST point to a procedure resource,
   which is invoked when the alarm is triggered.

   The "VALARM" calendar component MUST only appear within either a
   "VEVENT" or "VTODO" calendar component. "VALARM" calendar components
   cannot be nested. Multiple mutually independent "VALARM" calendar
   components can be specified for a single "VEVENT" or "VTODO" calendar
   component.

   The "TRIGGER" property specifies when the alarm will be triggered.
   The "TRIGGER" property specifies a duration prior to the start of an
   event or a to-do. The "TRIGGER" edge may be explicitly set to be
   relative to the "START" or "END" of the event or to-do with the
   "RELATED" parameter of the "TRIGGER" property. The "TRIGGER" property
   value type can alternatively be set to an absolute calendar date and
   time of day value.

   In an alarm set to trigger on the "START" of an event or to-do, the
   "DTSTART" property MUST be present in the associated event or to-do.
   In an alarm in a "VEVENT" calendar component set to trigger on the
   "END" of the event, either the "DTEND" property MUST be present, or
   the "DTSTART" and "DURATION" properties MUST both be present. In an
   alarm in a "VTODO" calendar component set to trigger on the "END" of
   the to-do, either the "DUE" property MUST be present, or the
   "DTSTART" and "DURATION" properties MUST both be present.

   The alarm can be defined such that it triggers repeatedly. A
   definition of an alarm with a repeating trigger MUST include both the
   "DURATION" and "REPEAT" properties. The "DURATION" property specifies
   the delay period, after which the alarm will repeat. The "REPEAT"
   property specifies the number of additional repetitions that the
   alarm will triggered. This repitition count is in addition to the
   initial triggering of the alarm. Both of these properties MUST be
   present in order to specify a repeating alarm. If one of these two
   properties is absent, then the alarm will not repeat beyond the
   initial trigger.

   The "ACTION" property is used within the "VALARM" calendar component
   to specify the type of action invoked when the alarm is triggered.
   The "VALARM" properties provide enough information for a specific
   action to be invoked. It is typically the responsibility of a
   "Calendar User Agent" (CUA) to deliver the alarm in the specified
   fashion. An "ACTION" property value of AUDIO specifies an alarm that
   causes a sound to be played to alert the user; DISPLAY specifies an
   alarm that causes a text message to be displayed to the user; EMAIL
   specifies an alarm that causes an electronic email message to be
   delivered to one or more email addresses; and PROCEDURE specifies an
   alarm that causes a procedure to be executed. The "ACTION" property
   MUST specify one and only one of these values.

   In an AUDIO alarm, if the optional "ATTACH" property is included, it
   MUST specify an audio sound resource. The intention is that the sound
   will be played as the alarm effect. If an "ATTACH" property is
   specified that does not refer to a sound resource, or if the
   specified sound resource cannot be rendered (because its format is
   unsupported, or because it cannot be retrieved), then the CUA or
   other entity responsible for playing the sound may choose a fallback

   action, such as playing a built-in default sound, or playing no sound
   at all.

   In a DISPLAY alarm, the intended alarm effect is for the text value
   of the "DESCRIPTION" property to be displayed to the user.

   In an EMAIL alarm, the intended alarm effect is for an email message
   to be composed and delivered to all the addresses specified by the
   "ATTENDEE" properties in the "VALARM" calendar component. The
   "DESCRIPTION" property of the "VALARM" calendar component MUST be
   used as the body text of the message, and the "SUMMARY" property MUST
   be used as the subject text. Any "ATTACH" properties in the "VALARM"
   calendar component SHOULD be sent as attachments to the message.

   In a PROCEDURE alarm, the "ATTACH" property in the "VALARM" calendar
   component MUST specify a procedure or program that is intended to be
   invoked as the alarm effect. If the procedure or program is in a
   format that cannot be rendered, then no procedure alarm will be
   invoked. If the "DESCRIPTION" property is present, its value
   specifies the argument string to be passed to the procedure or
   program. "Calendar User Agents" that receive an iCalendar object with
   this category of alarm, can disable or allow the "Calendar User" to
   disable, or otherwise ignore this type of alarm. While a very useful
   alarm capability, the PROCEDURE type of alarm SHOULD be treated by
   the "Calendar User Agent" as a potential security risk.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following example is for a "VALARM" calendar component
   that specifies an audio alarm that will sound at a precise time and
   repeat 4 more times at 15 minute intervals:

     BEGIN:VALARM
     TRIGGER;VALUE=DATE-TIME:19970317T133000Z
     REPEAT:4
     DURATION:PT15M
     ACTION:AUDIO
     ATTACH;FMTTYPE=audio/basic:ftp://host.com/pub/sounds/bell-01.aud
     END:VALARM

   The following example is for a "VALARM" calendar component that
   specifies a display alarm that will trigger 30 minutes before the
   scheduled start of the event or the due date/time of the to-do it is
   associated with and will repeat 2 more times at 15 minute intervals:

     BEGIN:VALARM
     TRIGGER:-PT30M
     REPEAT:2
     DURATION:PT15M
     ACTION:DISPLAY

     DESCRIPTION:Breakfast meeting with executive\n
      team at 8:30 AM EST.
     END:VALARM

   The following example is for a "VALARM" calendar component that
   specifies an email alarm that will trigger 2 days before the
   scheduled due date/time of a to-do it is associated with. It does not
   repeat. The email has a subject, body and attachment link.

     BEGIN:VALARM
     TRIGGER:-P2D
     ACTION:EMAIL
     ATTENDEE:MAILTO:john_doe@host.com
     SUMMARY:*** REMINDER: SEND AGENDA FOR WEEKLY STAFF MEETING ***
     DESCRIPTION:A draft agenda needs to be sent out to the attendees
       to the weekly managers meeting (MGR-LIST). Attached is a
       pointer the document template for the agenda file.
     ATTACH;FMTTYPE=application/binary:http://host.com/templates/agen
      da.doc
     END:VALARM

   The following example is for a "VALARM" calendar component that
   specifies a procedural alarm that will trigger at a precise date/time
   and will repeat 23 more times at one hour intervals. The alarm will
   invoke a procedure file.

     BEGIN:VALARM
     TRIGGER;VALUE=DATE-TIME:19980101T050000Z
     REPEAT:23
     DURATION:PT1H
     ACTION:PROCEDURE
     ATTACH;FMTTYPE=application/binary:ftp://host.com/novo-
      procs/felizano.exe
     END:VALARM

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.7'>4.7 Calendar Properties</h2>
<pre>
   The Calendar Properties are attributes that apply to the iCalendar
   object, as a whole. These properties do not appear within a calendar
   component. They SHOULD be specified after the "BEGIN:VCALENDAR"
   property and prior to any calendar component.

</pre>
</div>
<div><h2 id='sec4.7.1'>4.7.1 Calendar Scale</h2>
<dl>
<dt id='calscale'>Property Name</dt>
<dd class='PropertyName'><pre>    CALSCALE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines the calendar scale used for the
   calendar information specified in the iCalendar object.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    Property can be specified in an iCalendar object. The
   default value is "GREGORIAN".

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This memo is based on the Gregorian calendar scale. The
   Gregorian calendar scale is assumed if this property is not specified
   in the iCalendar object. It is expected that other calendar scales
   will be defined in other specifications or by future versions of this
   memo.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     calscale   = "CALSCALE" calparam ":" calvalue CRLF

     calparam   = *(";" xparam)

     calvalue   = "GREGORIAN" / iana-token

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     CALSCALE:GREGORIAN

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.7.2'>4.7.2 Method</h2>
<dl>
<dt id='method'>Property Name</dt>
<dd class='PropertyName'><pre>    METHOD

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines the iCalendar object method associated
   with the calendar object.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified in an iCalendar object.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    When used in a MIME message entity, the value of this
   property MUST be the same as the Content-Type "method" parameter
   value. This property can only appear once within the iCalendar
   object. If either the "METHOD" property or the Content-Type "method"
   parameter is specified, then the other MUST also be specified.

   No methods are defined by this specification. This is the subject of
   other specifications, such as the iCalendar Transport-independent

   Interoperability Protocol (iTIP) defined by <a href='#ref_ITIP'>[ITIP]</a>.

   If this property is not present in the iCalendar object, then a
   scheduling transaction MUST NOT be assumed. In such cases, the
   iCalendar object is merely being used to transport a snapshot of some
   calendar information; without the intention of conveying a scheduling
   semantic.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     method     = "METHOD" metparam ":" metvalue CRLF

     metparam   = *(";" xparam)

     metvalue   = iana-token

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is a hypothetical example of this property to
   convey that the iCalendar object is a request for a meeting:

     METHOD:REQUEST

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.7.3'>4.7.3 Product Identifier</h2>
<dl>
<dt id='prodid'>Property Name</dt>
<dd class='PropertyName'><pre>    PRODID

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property specifies the identifier for the product that
   created the iCalendar object.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property MUST be specified once in an iCalendar
   object.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The vendor of the implementation SHOULD assure that this
   is a globally unique identifier; using some technique such as an FPI
   value, as defined in <a href='#ref_ISO_9070'>[ISO 9070]</a>.

   This property SHOULD not be used to alter the interpretation of an
   iCalendar object beyond the semantics specified in this memo. For
   example, it is not to be used to further the understanding of non-
   standard properties.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     prodid     = "PRODID" pidparam ":" pidvalue CRLF

     pidparam   = *(";" xparam)

     pidvalue   = text
     ;Any text that describes the product and version
     ;and that is generally assured of being unique.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property. It does not
   imply that English is the default language.

     PRODID:-//ABC Corporation//NONSGML My Product//EN

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.7.4'>4.7.4 Version</h2>
<dl>
<dt id='version'>Property Name</dt>
<dd class='PropertyName'><pre>    VERSION

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property specifies the identifier corresponding to the
   highest version number or the minimum and maximum range of the
   iCalendar specification that is required in order to interpret the
   iCalendar object.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property MUST be specified by an iCalendar object,
   but MUST only be specified once.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    A value of "2.0" corresponds to this memo.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     version    = "VERSION" verparam ":" vervalue CRLF

     verparam   = *(";" xparam)

     vervalue   = "2.0"         ;This memo
                / maxver
                / (minver ";" maxver)

     minver     = &lt;A IANA registered iCalendar version identifier>
     ;Minimum iCalendar version needed to parse the iCalendar object

     maxver     = &lt;A IANA registered iCalendar version identifier>
     ;Maximum iCalendar version needed to parse the iCalendar object

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     VERSION:2.0

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8'>4.8 Component Properties</h2>
<pre>
   The following properties can appear within calendar components, as
   specified by each component property definition.

</pre>
</div>
<div><h2 id='sec4.8.1'>4.8.1 Descriptive Component Properties</h2>
<pre>
   The following properties specify descriptive information about
   calendar components.

</pre>
</div>
<div><h2 id='sec4.8.1.1'>4.8.1.1 Attachment</h2>
<dl>
<dt id='attach'>Property Name</dt>
<dd class='PropertyName'><pre>    ATTACH

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    The property provides the capability to associate a document
   object with a calendar component.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'>The default value type for this property is <a rel='default-value-type' href='#Value_URI'>URI</a> <pre>   . The
   value type can also be set to <a rel="allowed-type" href="#Value_BINARY">BINARY</a> to indicate inline binary
   encoded content information.

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard, inline encoding, format type and
   value data type property parameters can be specified on this
   property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified in a "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>",
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" or "<a rel="applies-to" href="#Valarm">VALARM</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The property can be specified within "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>",
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>", or "<a rel="applies-to" href="#Valarm">VALARM</a>" calendar components. This property can be
   specified multiple times within an iCalendar object.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     attach     = "ATTACH" attparam ":" uri  CRLF

     attach     =/ "ATTACH" attparam ";" "ENCODING" "=" "BASE64"
                   ";" "VALUE" "=" "BINARY" ":" binary

     attparam   = *(

                ; the following is optional,
                ; but MUST NOT occur more than once

                (";" fmttypeparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following are examples of this property:

     ATTACH:CID:jsmith.part3.960817T083000.xyzMail@host1.com

     ATTACH;FMTTYPE=application/postscript:ftp://xyzCorp.com/pub/
      reports/r-960812.ps

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.1.2'>4.8.1.2 Categories</h2>
<dl>
<dt id='categories'>Property Name</dt>
<dd class='PropertyName'><pre>    CATEGORIES

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines the categories for a calendar
   component.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard and language property parameters
   can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified within "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>"
   or "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This property is used to specify categories or subtypes
   of the calendar component. The categories are useful in searching for
   a calendar component of a particular type and category. Within the
   "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>" or "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" calendar components, more than one
   category can be specified as a list of categories separated by the
   COMMA character (US-ASCII decimal 44).

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     categories = "CATEGORIES" catparam ":" text *("," text)
                  CRLF

     catparam   = *(

                ; the following is optional,
                ; but MUST NOT occur more than once

                (";" languageparam ) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following are examples of this property:

     CATEGORIES:APPOINTMENT,EDUCATION

     CATEGORIES:MEETING

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.1.3'>4.8.1.3 Classification</h2>
<dl>
<dt id='class'>Property Name</dt>
<dd class='PropertyName'><pre>    CLASS

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines the access classification for a
   calendar component.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified once in a "<a rel="applies-to" href="#Vevent">VEVENT</a>",
   "<a rel="applies-to" href="#Vtodo">VTODO</a>" or "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    An access classification is only one component of the
   general security system within a calendar application. It provides a
   method of capturing the scope of the access the calendar owner
   intends for information within an individual calendar entry. The
   access classification of an individual iCalendar component is useful
   when measured along with the other security components of a calendar
   system (e.g., calendar user authentication, authorization, access
   rights, access role, etc.). Hence, the semantics of the individual
   access classifications cannot be completely defined by this memo
   alone. Additionally, due to the "blind" nature of most exchange
   processes using this memo, these access classifications cannot serve
   as an enforcement statement for a system receiving an iCalendar
   object. Rather, they provide a method for capturing the intention of
   the calendar owner for the access to the calendar component.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     class      = "CLASS" classparam ":" classvalue CRLF

     classparam = *(";" xparam)

     classvalue = "PUBLIC" / "PRIVATE" / "CONFIDENTIAL" / iana-token
                / x-name
     ;Default is PUBLIC

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     CLASS:PUBLIC

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.1.4'>4.8.1.4 Comment</h2>
<dl>
<dt id='comment'>Property Name</dt>
<dd class='PropertyName'><pre>    COMMENT

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property specifies non-processing information intended
   to provide a comment to the calendar user.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard, alternate text representation and
   language property parameters can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>",
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>", "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>" or "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The property can be specified multiple times.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     comment    = "COMMENT" commparam ":" text CRLF

     commparam  = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                (";" altrepparam) / (";" languageparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     COMMENT:The meeting really needs to include both ourselves
       and the customer. We can't hold this  meeting without them.
       As a matter of fact\, the venue for the meeting ought to be at

       their site. - - John

   The data type for this property is TEXT.

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.1.5'>4.8.1.5 Description</h2>
<dl>
<dt id='description'>Property Name</dt>
<dd class='PropertyName'><pre>    DESCRIPTION

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property provides a more complete description of the
   calendar component, than that provided by the "SUMMARY" property.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard, alternate text representation and
   language property parameters can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified in the "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>",
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" or "<a rel="applies-to" href="#Valarm">VALARM</a>" calendar components. The property can be
   specified multiple times only within a "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" calendar component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This property is used in the "<a rel="applies-to" href="#Vevent">VEVENT</a>" and "<a rel="applies-to" href="#Vtodo">VTODO</a>" to
   capture lengthy textual decriptions associated with the activity.

   This property is used in the "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" calendar component to capture
   one more textual journal entries.

   This property is used in the "<a rel="applies-to" href="#Valarm">VALARM</a>" calendar component to capture
   the display text for a DISPLAY category of alarm, to capture the body
   text for an EMAIL category of alarm and to capture the argument
   string for a PROCEDURE category of alarm.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     description        = "DESCRIPTION" descparam ":" text CRLF

     descparam  = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                (";" altrepparam) / (";" languageparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of the property with formatted
   line breaks in the property value:

     DESCRIPTION:Meeting to provide technical review for "Phoenix"
       design.\n Happy Face Conference Room. Phoenix design team
       MUST attend this meeting.\n RSVP to team leader.

   The following is an example of the property with folding of long
   lines:

     DESCRIPTION:Last draft of the new novel is to be completed
       for the editor's proof today.

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.1.6'>4.8.1.6 Geographic Position</h2>
<dl>
<dt id='geo'>Property Name</dt>
<dd class='PropertyName'><pre>    GEO

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property specifies information related to the global
   position for the activity specified by a calendar component.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='list-of' href='#Value_FLOAT'>FLOAT</a> <pre>   . The value MUST be two SEMICOLON separated FLOAT
   values.

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in  "<a rel="applies-to" href="#Vevent">VEVENT</a>" or "<a rel="applies-to" href="#Vtodo">VTODO</a>"
   calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The property value specifies latitude and longitude, in
   that order (i.e., "LAT LON" ordering). The longitude represents the
   location east or west of the prime meridian as a positive or negative
   real number, respectively. The longitude and latitude values MAY be
   specified up to six decimal places, which will allow for accuracy to
   within one meter of geographical position. Receiving applications
   MUST accept values of this precision and MAY truncate values of
   greater precision.

   Values for latitude and longitude shall be expressed as decimal
   fractions of degrees. Whole degrees of latitude shall be represented
   by a two-digit decimal number ranging from 0 through 90. Whole
   degrees of longitude shall be represented by a decimal number ranging
   from 0 through 180. When a decimal fraction of a degree is specified,
   it shall be separated from the whole number of degrees by a decimal
   point.

   Latitudes north of the equator shall be specified by a plus sign (+),
   or by the absence of a minus sign (-), preceding the digits
   designating degrees. Latitudes south of the Equator shall be
   designated by a minus sign (-) preceding the digits designating
   degrees. A point on the Equator shall be assigned to the Northern
   Hemisphere.

   Longitudes east of the prime meridian shall be specified by a plus
   sign (+), or by the absence of a minus sign (-), preceding the digits
   designating degrees. Longitudes west of the meridian shall be
   designated by minus sign (-) preceding the digits designating
   degrees. A point on the prime meridian shall be assigned to the
   Eastern Hemisphere. A point on the 180th meridian shall be assigned
   to the Western Hemisphere. One exception to this last convention is
   permitted. For the special condition of describing a band of latitude
   around the earth, the East Bounding Coordinate data element shall be
   assigned the value +180 (180) degrees.

   Any spatial address with a latitude of +90 (90) or -90 degrees will
   specify the position at the North or South Pole, respectively. The
   component for longitude may have any legal value.

   With the exception of the special condition described above, this
   form is specified in Department of Commerce, 1986, Representation of
   geographic point locations for information interchange (Federal
   Information Processing Standard 70-1):  Washington,  Department of
   Commerce, National Institute of Standards and Technology.

   The simple formula for converting degrees-minutes-seconds into
   decimal degrees is:

     decimal = degrees + minutes/60 + seconds/3600.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     geo        = "GEO" geoparam ":" geovalue CRLF

     geoparam   = *(";" xparam)

     geovalue   = float ";" float
     ;Latitude and Longitude components

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     GEO:37.386013;-122.082932

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.1.7'>4.8.1.7 Location</h2>
<dl>
<dt id='location'>Property Name</dt>
<dd class='PropertyName'><pre>    LOCATION

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    The property defines the intended venue for the activity
   defined by a calendar component.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard, alternate text representation and
   language property parameters can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in "<a rel="applies-to" href="#Vevent">VEVENT</a>" or "<a rel="applies-to" href="#Vtodo">VTODO</a>"
   calendar component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    Specific venues such as conference or meeting rooms may
   be explicitly specified using this property. An alternate
   representation may be specified that is a URI that points to
   directory information with more structured specification of the
   location. For example, the alternate representation may specify
   either an LDAP URI pointing to an LDAP server entry or a CID URI
   pointing to a MIME body part containing a vCard <a href='#ref_RFC_2426'>[RFC 2426]</a> for the
   location.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     location   = "LOCATION locparam ":" text CRLF

     locparam   = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                (";" altrepparam) / (";" languageparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following are some examples of this property:

     LOCATION:Conference Room - F123, Bldg. 002

     LOCATION;ALTREP="http://xyzcorp.com/conf-rooms/f123.vcf":
      Conference Room - F123, Bldg. 002

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.1.8'>4.8.1.8 Percent Complete</h2>
<dl>
<dt id='percentComplete'>Property Name</dt>
<dd class='PropertyName'><pre>    PERCENT-COMPLETE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property is used by an assignee or delegatee of a to-do
   to convey the percent completion of a to-do to the Organizer.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_INTEGER'>INTEGER</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in a "<a rel="applies-to" href="#Vtodo">VTODO</a>" calendar
   component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The property value is a positive integer between zero
   and one hundred. A value of "0" indicates the to-do has not yet been
   started. A value of "100" indicates that the to-do has been
   completed. Integer values in between indicate the percent partially
   complete.

   When a to-do is assigned to multiple individuals, the property value
   indicates the percent complete for that portion of the to-do assigned
   to the assignee or delegatee. For example, if a to-do is assigned to
   both individuals "A" and "B". A reply from "A" with a percent
   complete of "70" indicates that "A" has completed 70% of the to-do
   assigned to them. A reply from "B" with a percent complete of "50"
   indicates "B" has completed 50% of the to-do assigned to them.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     percent = "PERCENT-COMPLETE" pctparam ":" integer CRLF

     pctparam   = *(";" xparam)

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property to show 39%
   completion:

     PERCENT-COMPLETE:39

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.1.9'>4.8.1.9 Priority</h2>
<dl>
<dt id='priority'>Property Name</dt>
<dd class='PropertyName'><pre>    PRIORITY

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    The property defines the relative priority for a calendar
   component.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_INTEGER'>INTEGER</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified in a "<a rel="applies-to" href="#Vevent">VEVENT</a>" or "<a rel="applies-to" href="#Vtodo">VTODO</a>"
   calendar component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The priority is specified as an integer in the range
   zero to nine. A value of zero (US-ASCII decimal 48) specifies an
   undefined priority. A value of one (US-ASCII decimal 49) is the
   highest priority. A value of two (US-ASCII decimal 50) is the second
   highest priority. Subsequent numbers specify a decreasing ordinal
   priority. A value of nine (US-ASCII decimal 58) is the lowest
   priority.

   A CUA with a three-level priority scheme of "HIGH", "MEDIUM" and
   "LOW" is mapped into this property such that a property value in the
   range of one (US-ASCII decimal 49) to four (US-ASCII decimal 52)
   specifies "HIGH" priority. A value of five (US-ASCII decimal 53) is
   the normal or "MEDIUM" priority. A value in the range of six (US-
   ASCII decimal 54) to nine (US-ASCII decimal 58) is "LOW" priority.

   A CUA with a priority schema of "A1", "A2", "A3", "B1", "B2", ...,
   "C3" is mapped into this property such that a property value of one
   (US-ASCII decimal 49) specifies "A1", a property value of two (US-
   ASCII decimal 50) specifies "A2", a property value of three (US-ASCII
   decimal 51) specifies "A3", and so forth up to a property value of 9
   (US-ASCII decimal 58) specifies "C3".

   Other integer values are reserved for future use.

   Within a "<a rel="applies-to" href="#Vevent">VEVENT</a>" calendar component, this property specifies a
   priority for the event. This property may be useful when more than
   one event is scheduled for a given time period.

   Within a "<a rel="applies-to" href="#Vtodo">VTODO</a>" calendar component, this property specified a
   priority for the to-do. This property is useful in prioritizing
   multiple action items for a given time period.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is specified by the following
   notation:

     priority   = "PRIORITY" prioparam ":" privalue CRLF
     ;Default is zero

     prioparam  = *(";" xparam)

     privalue   = integer       ;Must be in the range 0..9]
        ; All other values are reserved for future use

   The following is an example of a property with the highest priority:

     PRIORITY:1

   The following is an example of a property with a next highest
   priority:

     PRIORITY:2

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of a property with no priority.
   This is equivalent to not specifying the "PRIORITY" property:

     PRIORITY:0

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.1.10'>4.8.1.10 Resources</h2>
<dl>
<dt id='resources'>Property Name</dt>
<dd class='PropertyName'><pre>    RESOURCES

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines the equipment or resources anticipated
   for an activity specified by a calendar entity..

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard, alternate text representation and
   language property parameters can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in "<a rel="applies-to" href="#Vevent">VEVENT</a>" or "<a rel="applies-to" href="#Vtodo">VTODO</a>"
   calendar component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The property value is an arbitrary text. More than one
   resource can be specified as a list of resources separated by the
   COMMA character (US-ASCII decimal 44).

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     resources  = "RESOURCES" resrcparam ":" text *("," text) CRLF

     resrcparam = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                (";" altrepparam) / (";" languageparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     RESOURCES:EASEL,PROJECTOR,VCR

     RESOURCES;LANGUAGE=fr:1 raton-laveur

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.1.11'>4.8.1.11 Status</h2>
<dl>
<dt id='status'>Property Name</dt>
<dd class='PropertyName'><pre>    STATUS

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines the overall status or confirmation for
   the calendar component.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>" or
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    In a group scheduled calendar component, the property is
   used by the "Organizer" to provide a confirmation of the event to the
   "Attendees". For example in a "<a rel="applies-to" href="#Vevent">VEVENT</a>" calendar component, the
   "Organizer" can indicate that a meeting is tentative, confirmed or
   cancelled. In a "<a rel="applies-to" href="#Vtodo">VTODO</a>" calendar component, the "Organizer" can
   indicate that an action item needs action, is completed, is in
   process or being worked on, or has been cancelled. In a "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>"
   calendar component, the "Organizer" can indicate that a journal entry
   is draft, final or has been cancelled or removed.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     status     = "STATUS" statparam] ":" statvalue CRLF

     statparam  = *(";" xparam)

     statvalue  = "TENTATIVE"           ;Indicates event is
                                        ;tentative.
                / "CONFIRMED"           ;Indicates event is
                                        ;definite.
                / "CANCELLED"           ;Indicates event was
                                        ;cancelled.
        ;Status values for a "VEVENT"

     statvalue  =/ "NEEDS-ACTION"       ;Indicates to-do needs action.
                / "COMPLETED"           ;Indicates to-do completed.
                / "IN-PROCESS"          ;Indicates to-do in process of
                / "CANCELLED"           ;Indicates to-do was cancelled.
        ;Status values for "VTODO".

     statvalue  =/ "DRAFT"              ;Indicates journal is draft.
                / "FINAL"               ;Indicates journal is final.
                / "CANCELLED"           ;Indicates journal is removed.
        ;Status values for "VJOURNAL".

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property for a "VEVENT"
   calendar component:

     STATUS:TENTATIVE

   The following is an example of this property for a "VTODO" calendar
   component:

     STATUS:NEEDS-ACTION

   The following is an example of this property for a "VJOURNAL"
   calendar component:

     STATUS:DRAFT

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.1.12'>4.8.1.12 Summary</h2>
<dl>
<dt id='summary'>Property Name</dt>
<dd class='PropertyName'><pre>    SUMMARY

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines a short summary or subject for the
   calendar component.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard, alternate text representation and
   language property parameters can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified in "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>",
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" or "<a rel="applies-to" href="#Valarm">VALARM</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This property is used in the "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>" and
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" calendar components to capture a short, one line summary
   about the activity or journal entry.

   This property is used in the "<a rel="applies-to" href="#Valarm">VALARM</a>" calendar component to capture
   the subject of an EMAIL category of alarm.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     summary    = "SUMMARY" summparam ":" text CRLF

     summparam  = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                (";" altrepparam) / (";" languageparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     SUMMARY:Department Party

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.2'>4.8.2 Date and Time Component Properties</h2>
<pre>
   The following properties specify date and time related information in
   calendar components.

</pre>
</div>
<div><h2 id='sec4.8.2.1'>4.8.2.1 Date/Time Completed</h2>
<dl>
<dt id='completed'>Property Name</dt>
<dd class='PropertyName'><pre>    COMPLETED

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines the date and time that a to-do was
   actually completed.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_DATE-TIME'>DATE-TIME</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified in a "<a rel="applies-to" href="#Vtodo">VTODO</a>" calendar
   component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The date and time MUST be in a UTC format.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     completed  = "COMPLETED" compparam ":" date-time CRLF

     compparam  = *(";" xparam)

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     COMPLETED:19960401T235959Z

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.2.2'>4.8.2.2 Date/Time End</h2>
<dl>
<dt id='dtend'>Property Name</dt>
<dd class='PropertyName'><pre>    DTEND

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property specifies the date and time that a calendar
   component ends.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'>The default value type is <a rel='default-value-type' href='#Value_DATE-TIME'>DATE-TIME</a> <pre>   . The value type can
   be set to a <a rel="allowed-type" href="#Value_DATE">DATE</a> value type.

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard, value data type, time zone
   identifier property parameters can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in "<a rel="applies-to" href="#Vevent">VEVENT</a>" or
   "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    Within the "<a rel="applies-to" href="#Vevent">VEVENT</a>" calendar component, this property
   defines the date and time by which the event ends. The value MUST be
   later in time than the value of the "DTSTART" property.

   Within the "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>" calendar component, this property defines the
   end date and time for the free or busy time information. The time
   MUST be specified in the UTC time format. The value MUST be later in
   time than the value of the "DTSTART" property.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     dtend      = "DTEND" dtendparam":" dtendval CRLF

     dtendparam = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                (";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
                (";" tzidparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )



     dtendval   = date-time / date
     ;Value MUST match value type

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     DTEND:19960401T235959Z

     DTEND;VALUE=DATE:19980704

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.2.3'>4.8.2.3 Date/Time Due</h2>
<dl>
<dt id='due'>Property Name</dt>
<dd class='PropertyName'><pre>    DUE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines the date and time that a to-do is
   expected to be completed.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'>The default value type is <a rel='default-value-type' href='#Value_DATE-TIME'>DATE-TIME</a> <pre>   . The value type can
   be set to a <a rel="allowed-type" href="#Value_DATE">DATE</a> value type.

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard, value data type, time zone
   identifier property parameters can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified once in a "<a rel="applies-to" href="#Vtodo">VTODO</a>" calendar
   component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The value MUST be a date/time equal to or after the
   DTSTART value, if specified.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     due        = "DUE" dueparam":" dueval CRLF

     dueparam   = *(
                ; the following are optional,
                ; but MUST NOT occur more than once

                (";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
                (";" tzidparam) /

                ; the following is optional,
                ; and MAY occur more than once

                  *(";" xparam)

                )



     dueval     = date-time / date
     ;Value MUST match value type

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     DUE:19980430T235959Z

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.2.4'>4.8.2.4 Date/Time Start</h2>
<dl>
<dt id='dtstart'>Property Name</dt>
<dd class='PropertyName'><pre>    DTSTART

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property specifies when the calendar component begins.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'>The default value type is <a rel='default-value-type' href='#Value_DATE-TIME'>DATE-TIME</a> <pre>   . The time value MUST
   be one of the forms defined for the <a rel="allowed-type" href="#Value_DATE">DATE</a>-TIME value type. The value
   type can be set to a <a rel="allowed-type" href="#Value_DATE">DATE</a> value type.

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard, value data type, time zone
   identifier property parameters can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in the "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>",
   "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>", or "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    Within the "<a rel="applies-to" href="#Vevent">VEVENT</a>" calendar component, this property
   defines the start date and time for the event. The property is
   REQUIRED in "<a rel="applies-to" href="#Vevent">VEVENT</a>" calendar components. Events can have a start
   date/time but no end date/time. In that case, the event does not take
   up any time.

   Within the "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>" calendar component, this property defines the
   start date and time for the free or busy time information. The time
   MUST be specified in UTC time.

   Within the "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>" calendar component, this property defines the
   effective start date and time for a time zone specification. This
   property is REQUIRED within each STANDARD and DAYLIGHT part included
   in "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>" calendar components and MUST be specified as a local
   DATE-TIME without the "TZID" property parameter.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     dtstart    = "DTSTART" dtstparam ":" dtstval CRLF

     dtstparam  = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                (";" "VALUE" "=" ("DATE-TIME" / "DATE")) /
                (";" tzidparam) /

                ; the following is optional,
                ; and MAY occur more than once

                  *(";" xparam)

                )



     dtstval    = date-time / date
     ;Value MUST match value type

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     DTSTART:19980118T073000Z

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.2.5'>4.8.2.5 Duration</h2>
<dl>
<dt id='duration'>Property Name</dt>
<dd class='PropertyName'><pre>    DURATION

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    The property specifies a positive duration of time.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_DURATION'>DURATION</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified in "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>",
   "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>" or "<a rel="applies-to" href="#Valarm">VALARM</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    In a "<a rel="applies-to" href="#Vevent">VEVENT</a>" calendar component the property may be
   used to specify a duration of the event, instead of an explicit end
   date/time. In a "<a rel="applies-to" href="#Vtodo">VTODO</a>" calendar component the property may be used
   to specify a duration for the to-do, instead of an explicit due
   date/time. In a "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>" calendar component the property may be
   used to specify the interval of free time being requested. In a
   "<a rel="applies-to" href="#Valarm">VALARM</a>" calendar component the property may be used to specify the
   delay period prior to repeating an alarm.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     duration   = "DURATION" durparam ":" dur-value CRLF
                  ;consisting of a positive duration of time.

     durparam   = *(";" xparam)

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property that specifies
   an interval of time of 1 hour and zero minutes and zero seconds:

     DURATION:PT1H0M0S

   The following is an example of this property that specifies an
   interval of time of 15 minutes.

     DURATION:PT15M

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.2.6'>4.8.2.6 Free/Busy Time</h2>
<dl>
<dt id='freebusy'>Property Name</dt>
<dd class='PropertyName'><pre>    FREEBUSY

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    The property defines one or more free or busy time
   intervals.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_PERIOD'>PERIOD</a> <pre>   . The date and time values MUST be in an UTC time
   format.

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard or free/busy time type property
   parameters can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified in a "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>" calendar
   component.

</pre>
</dd>
<dt>Property Parameter</dt>
<dd class='PropertyParameter'><pre>    "FBTYPE" and non-standard parameters can be
   specified on this property.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    These time periods can be specified as either a start
   and end date-time or a start date-time and duration. The date and
   time MUST be a UTC time format.

   "FREEBUSY" properties within the "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>" calendar component
   SHOULD be sorted in ascending order, based on start time and then end
   time, with the earliest periods first.

   The "FREEBUSY" property can specify more than one value, separated by
   the COMMA character (US-ASCII decimal 44). In such cases, the
   "FREEBUSY" property values SHOULD all be of the same "FBTYPE"
   property parameter type (e.g., all values of a particular "FBTYPE"
   listed together in a single property).

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     freebusy   = "FREEBUSY" fbparam ":" fbvalue
                  CRLF

     fbparam    = *(
                ; the following is optional,
                ; but MUST NOT occur more than once

                (";" fbtypeparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

     fbvalue    = period *"," period]
     ;Time value MUST be in the UTC time format.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following are some examples of this property:

     FREEBUSY;FBTYPE=BUSY-UNAVAILABLE:19970308T160000Z/PT8H30M

     FREEBUSY;FBTYPE=FREE:19970308T160000Z/PT3H,19970308T200000Z/PT1H

     FREEBUSY;FBTYPE=FREE:19970308T160000Z/PT3H,19970308T200000Z/PT1H,
      19970308T230000Z/19970309T000000Z

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.2.7'>4.8.2.7 Time Transparency</h2>
<dl>
<dt id='transp'>Property Name</dt>
<dd class='PropertyName'><pre>    TRANSP

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines whether an event is transparent or not
   to busy time searches.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified once in a "<a rel="applies-to" href="#Vevent">VEVENT</a>"
   calendar component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    Time Transparency is the characteristic of an event that
   determines whether it appears to consume time on a calendar. Events
   that consume actual time for the individual or resource associated

   with the calendar SHOULD be recorded as OPAQUE, allowing them to be
   detected by free-busy time searches. Other events, which do not take
   up the individual's (or resource's) time SHOULD be recorded as
   TRANSPARENT, making them invisible to free-busy time searches.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is specified by the following
   notation:

     transp     = "TRANSP" tranparam ":" transvalue CRLF

     tranparam  = *(";" xparam)

     transvalue = "OPAQUE"      ;Blocks or opaque on busy time searches.
                / "TRANSPARENT" ;Transparent on busy time searches.
        ;Default value is OPAQUE

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property for an event
   that is transparent or does not block on free/busy time searches:

     TRANSP:TRANSPARENT

   The following is an example of this property for an event that is
   opaque or blocks on free/busy time searches:

     TRANSP:OPAQUE

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.3'>4.8.3 Time Zone Component Properties</h2>
<pre>
   The following properties specify time zone information in calendar
   components.

</pre>
</div>
<div><h2 id='sec4.8.3.1'>4.8.3.1 Time Zone Identifier</h2>
<dl>
<dt id='tzid'>Property Name</dt>
<dd class='PropertyName'><pre>    TZID

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property specifies the text value that uniquely
   identifies the "VTIMEZONE" calendar component.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property MUST be specified in a "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>"
   calendar component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This is the label by which a time zone calendar
   component is referenced by any iCalendar properties whose data type
   is either DATE-TIME or TIME and not intended to specify a UTC or a
   "floating" time. The presence of the SOLIDUS character (US-ASCII
   decimal 47) as a prefix, indicates that this TZID represents an
   unique ID in a globally defined time zone registry (when such
   registry is defined).

        Note: This document does not define a naming convention for time
        zone identifiers. Implementers may want to use the naming
        conventions defined in existing time zone specifications such as
        the public-domain Olson database <a href='#ref_TZ'>[TZ]</a>. The specification of
        globally unique time zone identifiers is not addressed by this
        document and is left for future study.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    This property is defined by the following
   notation:

     tzid       = "TZID" tzidpropparam ":" tzidprefix] text CRLF

     tzidpropparam      = *(";" xparam)

     ;tzidprefix        = "/"
     ; Defined previously. Just listed here for reader convenience.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following are examples of non-globally unique time zone
   identifiers:

     TZID:US-Eastern

     TZID:California-Los_Angeles

   The following is an example of a fictitious globally unique time zone
   identifier:

     TZID:/US-New_York-New_York

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.3.2'>4.8.3.2 Time Zone Name</h2>
<dl>
<dt id='tzname'>Property Name</dt>
<dd class='PropertyName'><pre>    TZNAME

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property specifies the customary designation for a time
   zone description.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard and language property parameters
   can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in a "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>" calendar
   component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This property may be specified in multiple languages; in
   order to provide for different language requirements.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    This property is defined by the following
   notation:

     tzname     = "TZNAME" tznparam ":" text CRLF

     tznparam   = *(

                ; the following is optional,
                ; but MUST NOT occur more than once

                (";" languageparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following are example of this property:

     TZNAME:EST

   The following is an example of this property when two different
   languages for the time zone name are specified:

     TZNAME;LANGUAGE=en:EST
     TZNAME;LANGUAGE=fr-CA:HNE

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.3.3'>4.8.3.3 Time Zone Offset From</h2>
<dl>
<dt id='tzoffsetfrom'>Property Name</dt>
<dd class='PropertyName'><pre>    TZOFFSETFROM

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property specifies the offset which is in use prior to
   this time zone observance.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_UTC-OFFSET'>UTC-OFFSET</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property MUST be specified in a "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>"
   calendar component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This property specifies the offset which is in use prior
   to this time observance. It is used to calculate the absolute time at
   which the transition to a given observance takes place. This property
   MUST only be specified in a "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>" calendar component. A
   "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>" calendar component MUST include this property. The
   property value is a signed numeric indicating the number of hours and
   possibly minutes from UTC. Positive numbers represent time zones east
   of the prime meridian, or ahead of UTC. Negative numbers represent
   time zones west of the prime meridian, or behind UTC.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     tzoffsetfrom       = "TZOFFSETFROM" frmparam ":" utc-offset
                          CRLF

     frmparam   = *(";" xparam)

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following are examples of this property:

     TZOFFSETFROM:-0500

     TZOFFSETFROM:+1345

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.3.4'>4.8.3.4 Time Zone Offset To</h2>
<dl>
<dt id='tzoffsetto'>Property Name</dt>
<dd class='PropertyName'><pre>    TZOFFSETTO

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property specifies the offset which is in use in this
   time zone observance.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_UTC-OFFSET'>UTC-OFFSET</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property MUST be specified in a "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>"
   calendar component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This property specifies the offset which is in use in
   this time zone observance. It is used to calculate the absolute time
   for the new observance. The property value is a signed numeric
   indicating the number of hours and possibly minutes from UTC.
   Positive numbers represent time zones east of the prime meridian, or
   ahead of UTC. Negative numbers represent time zones west of the prime
   meridian, or behind UTC.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     tzoffsetto = "TZOFFSETTO" toparam ":" utc-offset CRLF

     toparam    = *(";" xparam)

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following are examples of this property:

     TZOFFSETTO:-0400

     TZOFFSETTO:+1245

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.3.5'>4.8.3.5 Time Zone URL</h2>
<dl>
<dt id='tzurl'>Property Name</dt>
<dd class='PropertyName'><pre>    TZURL

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    The TZURL provides a means for a VTIMEZONE component to
   point to a network location that can be used to retrieve an up-to-
   date version of itself.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_URI'>URI</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in a "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>" calendar
   component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The TZURL provides a means for a <a rel="applies-to" href="#Vtimezone">VTIMEZONE</a> component to
   point to a network location that can be used to retrieve an up-to-
   date version of itself. This provides a hook to handle changes
   government bodies impose upon time zone definitions. Retrieval of
   this resource results in an iCalendar object containing a single
   <a rel="applies-to" href="#Vtimezone">VTIMEZONE</a> component and a METHOD property set to PUBLISH.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     tzurl      = "TZURL" tzurlparam ":" uri CRLF

     tzurlparam = *(";" xparam)

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     TZURL:http://timezones.r.us.net/tz/US-California-Los_Angeles

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.4'>4.8.4 Relationship Component Properties</h2>
<pre>
   The following properties specify relationship information in calendar
   components.

</pre>
</div>
<div><h2 id='sec4.8.4.1'>4.8.4.1 Attendee</h2>
<dl>
<dt id='attendee'>Property Name</dt>
<dd class='PropertyName'><pre>    ATTENDEE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    The property defines an "Attendee" within a calendar
   component.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_CAL-ADDRESS'>CAL-ADDRESS</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard, language, calendar user type,
   group or list membership, participation role, participation status,
   RSVP expectation, delegatee, delegator, sent by, common name or
   directory entry reference property parameters can be specified on
   this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property MUST be specified in an iCalendar object
   that specifies a group scheduled calendar entity. This property MUST
   NOT be specified in an iCalendar object when publishing the calendar
   information (e.g., NOT in an iCalendar object that specifies the
   publication of a calendar user's busy time, event, to-do or journal).
   This property is not specified in an iCalendar object that specifies
   only a time zone definition or that defines calendar entities that
   are not group scheduled entities, but are entities only on a single
   user's calendar.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The property MUST only be specified within calendar
   components to specify participants, non-participants and the chair of
   a group scheduled calendar entity. The property is specified within
   an "EMAIL" category of the "<a rel="applies-to" href="#Valarm">VALARM</a>" calendar component to specify an
   email address that is to receive the email type of iCalendar alarm.

   The property parameter CN is for the common or displayable name
   associated with the calendar address; ROLE, for the intended role
   that the attendee will have in the calendar component; PARTSTAT, for
   the status of the attendee's participation; RSVP, for indicating
   whether the favor of a reply is requested; CUTYPE, to indicate the
   type of calendar user; MEMBER, to indicate the groups that the
   attendee belongs to; DELEGATED-TO, to indicate the calendar users
   that the original request was delegated to; and DELEGATED-FROM, to
   indicate whom the request was delegated from; SENT-BY, to indicate
   whom is acting on behalf of the ATTENDEE; and DIR, to indicate the
   URI that points to the directory information corresponding to the
   attendee. These property parameters can be specified on an "ATTENDEE"

   property in either a "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>" or "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" calendar
   component. They MUST not be specified in an "ATTENDEE" property in a
   "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>" or "<a rel="applies-to" href="#Valarm">VALARM</a>" calendar component. If the LANGUAGE property
   parameter is specified, the identified language applies to the CN
   parameter.

   A recipient delegated a request MUST inherit the RSVP and ROLE values
   from the attendee that delegated the request to them.

   Multiple attendees can be specified by including multiple "ATTENDEE"
   properties within the calendar component.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     attendee   = "ATTENDEE" attparam ":" cal-address CRLF

     attparam   = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                (";" cutypeparam) / (";"memberparam) /
                (";" roleparam) / (";" partstatparam) /
                (";" rsvpparam) / (";" deltoparam) /
                (";" delfromparam) / (";" sentbyparam) /
                (";"cnparam) / (";" dirparam) /
                (";" languageparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following are examples of this property's use for a to-
   do:

     ORGANIZER:MAILTO:jsmith@host1.com
     ATTENDEE;MEMBER="MAILTO:DEV-GROUP@host2.com":
      MAILTO:joecool@host2.com
     ATTENDEE;DELEGATED-FROM="MAILTO:immud@host3.com":
      MAILTO:ildoit@host1.com

   The following is an example of this property used for specifying
   multiple attendees to an event:

     ORGANIZER:MAILTO:jsmith@host1.com
     ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;CN=Henry Cabot
      :MAILTO:hcabot@host2.com
     ATTENDEE;ROLE=REQ-PARTICIPANT;DELEGATED-FROM="MAILTO:bob@host.com"
      ;PARTSTAT=ACCEPTED;CN=Jane Doe:MAILTO:jdoe@host1.com

   The following is an example of this property with a URI to the
   directory information associated with the attendee:

     ATTENDEE;CN=John Smith;DIR="ldap://host.com:6666/o=eDABC%
      20Industries,c=3DUS??(cn=3DBJim%20Dolittle)":MAILTO:jimdo@
      host1.com

   The following is an example of this property with "delegatee" and
   "delegator" information for an event:

     ORGANIZER;CN=John Smith:MAILTO:jsmith@host.com
     ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=TENTATIVE;DELEGATED-FROM=
      "MAILTO:iamboss@host2.com";CN=Henry Cabot:MAILTO:hcabot@
      host2.com
     ATTENDEE;ROLE=NON-PARTICIPANT;PARTSTAT=DELEGATED;DELEGATED-TO=
      "MAILTO:hcabot@host2.com";CN=The Big Cheese:MAILTO:iamboss
      @host2.com
     ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=Jane Doe
      :MAILTO:jdoe@host1.com

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property's use when
   another calendar user is acting on behalf of the "Attendee":

     ATTENDEE;SENT-BY=MAILTO:jan_doe@host1.com;CN=John Smith:MAILTO:
      jsmith@host1.com

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.4.2'>4.8.4.2 Contact</h2>
<dl>
<dt id='contact'>Property Name</dt>
<dd class='PropertyName'><pre>    CONTACT

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    The property is used to represent contact information or
   alternately a reference to contact information associated with the
   calendar component.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard, alternate text representation and
   language property parameters can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified in a "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>",
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" or "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>" calendar component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The property value consists of textual contact
   information. An alternative representation for the property value can
   also be specified that refers to a URI pointing to an alternate form,
   such as a vCard <a href='#ref_RFC_2426'>[RFC 2426]</a>, for the contact information.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     contact    = "CONTACT" contparam ":" text CRLF

     contparam  = *(
                ; the following are optional,
                ; but MUST NOT occur more than once

                (";" altrepparam) / (";" languageparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property referencing
   textual contact information:

     CONTACT:Jim Dolittle\, ABC Industries\, +1-919-555-1234

   The following is an example of this property with an alternate
   representation of a LDAP URI to a directory entry containing the
   contact information:

     CONTACT;ALTREP="ldap://host.com:6666/o=3DABC%20Industries\,
      c=3DUS??(cn=3DBJim%20Dolittle)":Jim Dolittle\, ABC Industries\,
      +1-919-555-1234

   The following is an example of this property with an alternate
   representation of a MIME body part containing the contact
   information, such as a vCard <a href='#ref_RFC_2426'>[RFC 2426]</a> embedded in a MIME-DIR]
   content-type:

     CONTACT;ALTREP="CID=&lt;part3.msg970930T083000SILVER@host.com>":Jim
       Dolittle\, ABC Industries\, +1-919-555-1234

   The following is an example of this property referencing a network
   resource, such as a vCard <a href='#ref_RFC_2426'>[RFC 2426]</a> object containing the contact
   information:

     CONTACT;ALTREP="http://host.com/pdi/jdoe.vcf":Jim
       Dolittle\, ABC Industries\, +1-919-555-1234

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.4.3'>4.8.4.3 Organizer</h2>
<dl>
<dt id='organizer'>Property Name</dt>
<dd class='PropertyName'><pre>    ORGANIZER

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    The property defines the organizer for a calendar component.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_CAL-ADDRESS'>CAL-ADDRESS</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard, language, common name, directory
   entry reference, sent by property parameters can be specified on this
   property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property MUST be specified in an iCalendar object
   that specifies a group scheduled calendar entity. This property MUST
   be specified in an iCalendar object that specifies the publication of
   a calendar user's busy time. This property MUST NOT be specified in
   an iCalendar object that specifies only a time zone definition or
   that defines calendar entities that are not group scheduled entities,
   but are entities only on a single user's calendar.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The property is specified within the "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>",
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a> calendar components to specify the organizer of a group
   scheduled calendar entity. The property is specified within the
   "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>" calendar component to specify the calendar user
   requesting the free or busy time. When publishing a "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>"
   calendar component, the property is used to specify the calendar that
   the published busy time came from.

   The property has the property parameters CN, for specifying the
   common or display name associated with the "Organizer", DIR, for
   specifying a pointer to the directory information associated with the
   "Organizer", SENT-BY, for specifying another calendar user that is
   acting on behalf of the "Organizer". The non-standard parameters may
   also be specified on this property. If the LANGUAGE property
   parameter is specified, the identified language applies to the CN
   parameter value.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     organizer  = "ORGANIZER" orgparam ":"
                  cal-address CRLF

     orgparam   = *(

                ; the following are optional,

                ; but MUST NOT occur more than once

                (";" cnparam) / (";" dirparam) / (";" sentbyparam) /
                (";" languageparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     ORGANIZER;CN=John Smith:MAILTO:jsmith@host1.com

   The following is an example of this property with a pointer to the
   directory information associated with the organizer:

     ORGANIZER;CN=JohnSmith;DIR="ldap://host.com:6666/o=3DDC%20Associ
      ates,c=3DUS??(cn=3DJohn%20Smith)":MAILTO:jsmith@host1.com

   The following is an example of this property used by another calendar
   user who is acting on behalf of the organizer, with responses
   intended to be sent back to the organizer, not the other calendar
   user:

     ORGANIZER;SENT-BY="MAILTO:jane_doe@host.com":
      MAILTO:jsmith@host1.com

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.4.4'>4.8.4.4 Recurrence ID</h2>
<dl>
<dt id='recurrenceId'>Property Name</dt>
<dd class='PropertyName'><pre>    RECURRENCE-ID

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property is used in conjunction with the "UID" and
   "SEQUENCE" property to identify a specific instance of a recurring
   "VEVENT", "VTODO" or "VJOURNAL" calendar component. The property
   value is the effective value of the "DTSTART" property of the
   recurrence instance.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'>The default value type for this property is <a rel='default-value-type' href='#Value_DATE-TIME'>DATE-TIME</a> <pre>   .
   The time format can be any of the valid forms defined for a <a rel="allowed-type" href="#Value_DATE">DATE</a>-TIME
   value type. See <a rel="allowed-type" href="#Value_DATE">DATE</a>-TIME value type definition for specific
   interpretations of the various forms. The value type can be set to
   <a rel="allowed-type" href="#Value_DATE">DATE</a>.

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property, value data type, time
   zone identifier and recurrence identifier range parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in an iCalendar object
   containing a recurring calendar component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The full range of calendar components specified by a
   recurrence set is referenced by referring to just the "UID" property
   value corresponding to the calendar component. The "RECURRENCE-ID"
   property allows the reference to an individual instance within the
   recurrence set.

   If the value of the "DTSTART" property is a DATE type value, then the
   value MUST be the calendar date for the recurrence instance.

   The date/time value is set to the time when the original recurrence
   instance would occur; meaning that if the intent is to change a
   Friday meeting to Thursday, the date/time is still set to the
   original Friday meeting.

   The "RECURRENCE-ID" property is used in conjunction with the "UID"
   and "SEQUENCE" property to identify a particular instance of a
   recurring event, to-do or journal. For a given pair of "UID" and
   "SEQUENCE" property values, the "RECURRENCE-ID" value for a
   recurrence instance is fixed. When the definition of the recurrence
   set for a calendar component changes, and hence the "SEQUENCE"
   property value changes, the "RECURRENCE-ID" for a given recurrence
   instance might also change.The "RANGE" parameter is used to specify
   the effective range of recurrence instances from the instance
   specified by the "RECURRENCE-ID" property value. The default value
   for the range parameter is the single recurrence instance only. The
   value can also be "THISANDPRIOR" to indicate a range defined by the
   given recurrence instance and all prior instances or the value can be
   "THISANDFUTURE" to indicate a range defined by the given recurrence
   instance and all subsequent instances.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     recurid    = "RECURRENCE-ID" ridparam ":" ridval CRLF

     ridparam   = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                (";" "VALUE" "=" ("DATE-TIME" / "DATE)) /
                (";" tzidparam) / (";" rangeparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

     ridval     = date-time / date
     ;Value MUST match value type

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following are examples of this property:

     RECURRENCE-ID;VALUE=DATE:19960401

     RECURRENCE-ID;RANGE=THISANDFUTURE:19960120T120000Z

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.4.5'>4.8.4.5 Related To</h2>
<dl>
<dt id='relatedTo'>Property Name</dt>
<dd class='PropertyName'><pre>    RELATED-TO

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    The property is used to represent a relationship or
   reference between one calendar component and another.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard and relationship type property
   parameters can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified one or more times in the
   "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>" or "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The property value consists of the persistent, globally
   unique identifier of another calendar component. This value would be
   represented in a calendar component by the "UID" property.

   By default, the property value points to another calendar component
   that has a PARENT relationship to the referencing object. The
   "RELTYPE" property parameter is used to either explicitly state the
   default PARENT relationship type to the referenced calendar component
   or to override the default PARENT relationship type and specify
   either a CHILD or SIBLING relationship. The PARENT relationship
   indicates that the calendar component is a subordinate of the
   referenced calendar component. The CHILD relationship indicates that
   the calendar component is a superior of the referenced calendar
   component. The SIBLING relationship indicates that the calendar
   component is a peer of the referenced calendar component.

   Changes to a calendar component referenced by this property can have
   an implicit impact on the related calendar component. For example, if
   a group event changes its start or end date or time, then the
   related, dependent events will need to have their start and end dates
   changed in a corresponding way. Similarly, if a PARENT calendar
   component is canceled or deleted, then there is an implied impact to
   the related CHILD calendar components. This property is intended only
   to provide information on the relationship of calendar components. It
   is up to the target calendar system to maintain any property
   implications of this relationship.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     related    = "RELATED-TO" relparam] ":" text CRLF

     relparam   = *(

                ; the following is optional,
                ; but MUST NOT occur more than once

                (";" reltypeparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparm)

                )

   The following is an example of this property:

     RELATED-TO:&lt;jsmith.part7.19960817T083000.xyzMail@host3.com>

     RELATED-TO:&lt;19960401-080045-4000F192713-0052@host1.com>

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.4.6'>4.8.4.6 Uniform Resource Locator</h2>
<dl>
<dt id='url'>Property Name</dt>
<dd class='PropertyName'><pre>    URL

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines a Uniform Resource Locator (URL)
   associated with the iCalendar object.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_URI'>URI</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified once in the "<a rel="applies-to" href="#Vevent">VEVENT</a>",
   "<a rel="applies-to" href="#Vtodo">VTODO</a>", "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" or "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This property may be used in a calendar component to
   convey a location where a more dynamic rendition of the calendar
   information associated with the calendar component can be found. This
   memo does not attempt to standardize the form of the URI, nor the
   format of the resource pointed to by the property value. If the URL
   property and Content-Location MIME header are both specified, they
   MUST point to the same resource.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     url        = "URL" urlparam ":" uri CRLF

     urlparam   = *(";" xparam)

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     URL:http://abc.com/pub/calendars/jsmith/mytime.ics

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.4.7'>4.8.4.7 Unique Identifier</h2>
<dl>
<dt id='uid'>Property Name</dt>
<dd class='PropertyName'><pre>    UID

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines the persistent, globally unique
   identifier for the calendar component.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property MUST be specified in the "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>",
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" or "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The UID itself MUST be a globally unique identifier. The
   generator of the identifier MUST guarantee that the identifier is
   unique. There are several algorithms that can be used to accomplish
   this. The identifier is RECOMMENDED to be the identical syntax to the
   <a href='#ref_RFC_822'>[RFC 822]</a> addr-spec. A good method to assure uniqueness is to put the
   domain name or a domain literal IP address of the host on which the
   identifier was created on the right hand side of the "@", and on the
   left hand side, put a combination of the current calendar date and
   time of day (i.e., formatted in as a DATE-TIME value) along with some
   other currently unique (perhaps sequential) identifier available on
   the system (for example, a process id number). Using a date/time
   value on the left hand side and a domain name or domain literal on

   the right hand side makes it possible to guarantee uniqueness since
   no two hosts should be using the same domain name or IP address at
   the same time. Though other algorithms will work, it is RECOMMENDED
   that the right hand side contain some domain identifier (either of
   the host itself or otherwise) such that the generator of the message
   identifier can guarantee the uniqueness of the left hand side within
   the scope of that domain.

   This is the method for correlating scheduling messages with the
   referenced "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>", or "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" calendar component.

   The full range of calendar components specified by a recurrence set
   is referenced by referring to just the "UID" property value
   corresponding to the calendar component. The "RECURRENCE-ID" property
   allows the reference to an individual instance within the recurrence
   set.

   This property is an important method for group scheduling
   applications to match requests with later replies, modifications or
   deletion requests. Calendaring and scheduling applications MUST
   generate this property in "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>" and "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" calendar
   components to assure interoperability with other group scheduling
   applications. This identifier is created by the calendar system that
   generates an iCalendar object.

   Implementations MUST be able to receive and persist values of at
   least 255 characters for this property.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     uid        = "UID" uidparam ":" text CRLF

     uidparam   = *(";" xparam)

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     UID:19960401T080045Z-4000F192713-0052@host1.com

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.5'>4.8.5 Recurrence Component Properties</h2>
<pre>
   The following properties specify recurrence information in calendar
   components.

</pre>
</div>
<div><h2 id='sec4.8.5.1'>4.8.5.1 Exception Date/Times</h2>
<dl>
<dt id='exdate'>Property Name</dt>
<dd class='PropertyName'><pre>    EXDATE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines the list of date/time exceptions for a
   recurring calendar component.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'>The default value type for this property is <a rel='default-value-type' href='#Value_DATE-TIME'>DATE-TIME</a> <pre>   .
   The value type can be set to <a rel="allowed-type" href="#Value_DATE">DATE</a>.

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard, value data type and time zone
   identifier property parameters can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in an iCalendar object
   that includes a recurring calendar component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The exception dates, if specified, are used in computing
   the recurrence set. The recurrence set is the complete set of
   recurrence instances for a calendar component. The recurrence set is
   generated by considering the initial "DTSTART" property along with
   the "RRULE", "RDATE", "EXDATE" and "EXRULE" properties contained
   within the iCalendar object. The "DTSTART" property defines the first
   instance in the recurrence set. Multiple instances of the "RRULE" and
   "EXRULE" properties can also be specified to define more
   sophisticated recurrence sets. The final recurrence set is generated
   by gathering all of the start date-times generated by any of the
   specified "RRULE" and "RDATE" properties, and then excluding any
   start date and times which fall within the union of start date and
   times generated by any specified "EXRULE" and "EXDATE" properties.
   This implies that start date and times within exclusion related
   properties (i.e., "EXDATE" and "EXRULE") take precedence over those
   specified by inclusion properties (i.e., "RDATE" and "RRULE"). Where
   duplicate instances are generated by the "RRULE" and "RDATE"
   properties, only one recurrence is considered. Duplicate instances
   are ignored.

   The "EXDATE" property can be used to exclude the value specified in
   "DTSTART". However, in such cases the original "DTSTART" date MUST
   still be maintained by the calendaring and scheduling system because
   the original "DTSTART" value has inherent usage dependencies by other
   properties such as the "RECURRENCE-ID".

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     exdate     = "EXDATE" exdtparam ":" exdtval *("," exdtval) CRLF

     exdtparam  = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                (";" "VALUE" "=" ("DATE-TIME" / "DATE")) /

                (";" tzidparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

     exdtval    = date-time / date
     ;Value MUST match value type

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     EXDATE:19960402T010000Z,19960403T010000Z,19960404T010000Z

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.5.2'>4.8.5.2 Exception Rule</h2>
<dl>
<dt id='exrule'>Property Name</dt>
<dd class='PropertyName'><pre>    EXRULE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines a rule or repeating pattern for an
   exception to a recurrence set.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_RECUR'>RECUR</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>" or
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The exception rule, if specified, is used in computing
   the recurrence set. The recurrence set is the complete set of
   recurrence instances for a calendar component. The recurrence set is
   generated by considering the initial "DTSTART" property along with
   the "RRULE", "RDATE", "EXDATE" and "EXRULE" properties contained
   within the iCalendar object. The "DTSTART" defines the first instance
   in the recurrence set. Multiple instances of the "RRULE" and "EXRULE"
   properties can also be specified to define more sophisticated
   recurrence sets. The final recurrence set is generated by gathering
   all of the start date-times generated by any of the specified "RRULE"
   and "RDATE" properties, and excluding any start date and times which
   fall within the union of start date and times generated by any
   specified "EXRULE" and "EXDATE" properties. This implies that start
   date and times within exclusion related properties (i.e., "EXDATE"
   and "EXRULE") take precedence over those specified by inclusion

   properties (i.e., "RDATE" and "RRULE"). Where duplicate instances are
   generated by the "RRULE" and "RDATE" properties, only one recurrence
   is considered. Duplicate instances are ignored.

   The "EXRULE" property can be used to exclude the value specified in
   "DTSTART". However, in such cases the original "DTSTART" date MUST
   still be maintained by the calendaring and scheduling system because
   the original "DTSTART" value has inherent usage dependencies by other
   properties such as the "RECURRENCE-ID".

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     exrule     = "EXRULE" exrparam ":" recur CRLF

     exrparam   = *(";" xparam)

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following are examples of this property. Except every
   other week, on Tuesday and Thursday for 4 occurrences:

     EXRULE:FREQ=WEEKLY;COUNT=4;INTERVAL=2;BYDAY=TU,TH

   Except daily for 10 occurrences:

     EXRULE:FREQ=DAILY;COUNT=10

   Except yearly in June and July for 8 occurrences:

     EXRULE:FREQ=YEARLY;COUNT=8;BYMONTH=6,7

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.5.3'>4.8.5.3 Recurrence Date/Times</h2>
<dl>
<dt id='rdate'>Property Name</dt>
<dd class='PropertyName'><pre>    RDATE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines the list of date/times for a
   recurrence set.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'>The default value type for this property is <a rel='default-value-type' href='#Value_DATE-TIME'>DATE-TIME</a> <pre>   .
   The value type can be set to <a rel="allowed-type" href="#Value_DATE">DATE</a> or <a rel="allowed-type" href="#Value_PERIOD">PERIOD</a>.

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard, value data type and time zone
   identifier property parameters can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified in "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>",
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" or "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This property can appear along with the "RRULE" property
   to define an aggregate set of repeating occurrences. When they both
   appear in an iCalendar object, the recurring events are defined by
   the union of occurrences defined by both the "RDATE" and "RRULE".

   The recurrence dates, if specified, are used in computing the
   recurrence set. The recurrence set is the complete set of recurrence
   instances for a calendar component. The recurrence set is generated
   by considering the initial "DTSTART" property along with the "RRULE",
   "RDATE", "EXDATE" and "EXRULE" properties contained within the
   iCalendar object. The "DTSTART" property defines the first instance
   in the recurrence set. Multiple instances of the "RRULE" and "EXRULE"
   properties can also be specified to define more sophisticated
   recurrence sets. The final recurrence set is generated by gathering
   all of the start date/times generated by any of the specified "RRULE"
   and "RDATE" properties, and excluding any start date/times which fall
   within the union of start date/times generated by any specified
   "EXRULE" and "EXDATE" properties. This implies that start date/times
   within exclusion related properties (i.e., "EXDATE" and "EXRULE")
   take precedence over those specified by inclusion properties (i.e.,
   "RDATE" and "RRULE"). Where duplicate instances are generated by the
   "RRULE" and "RDATE" properties, only one recurrence is considered.
   Duplicate instances are ignored.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     rdate      = "RDATE" rdtparam ":" rdtval *("," rdtval) CRLF

     rdtparam   = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                (";" "VALUE" "=" ("DATE-TIME" / "DATE" / "PERIOD")) /
                (";" tzidparam) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

     rdtval     = date-time / date / period
     ;Value MUST match value type

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following are examples of this property:

     RDATE:19970714T123000Z

     RDATE;TZID=US-EASTERN:19970714T083000

     RDATE;VALUE=PERIOD:19960403T020000Z/19960403T040000Z,
      19960404T010000Z/PT3H

     RDATE;VALUE=DATE:19970101,19970120,19970217,19970421
      19970526,19970704,19970901,19971014,19971128,19971129,19971225

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.5.4'>4.8.5.4 Recurrence Rule</h2>
<dl>
<dt id='rrule'>Property Name</dt>
<dd class='PropertyName'><pre>    RRULE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines a rule or repeating pattern for
   recurring events, to-dos, or time zone definitions.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_RECUR'>RECUR</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified one or more times in
   recurring "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>" and "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" calendar components. It
   can also be specified once in each STANDARD or DAYLIGHT sub-component
   of the "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>" calendar component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The recurrence rule, if specified, is used in computing
   the recurrence set. The recurrence set is the complete set of
   recurrence instances for a calendar component. The recurrence set is
   generated by considering the initial "DTSTART" property along with
   the "RRULE", "RDATE", "EXDATE" and "EXRULE" properties contained
   within the iCalendar object. The "DTSTART" property defines the first
   instance in the recurrence set. Multiple instances of the "RRULE" and
   "EXRULE" properties can also be specified to define more
   sophisticated recurrence sets. The final recurrence set is generated
   by gathering all of the start date/times generated by any of the
   specified "RRULE" and "RDATE" properties, and excluding any start
   date/times which fall within the union of start date/times generated
   by any specified "EXRULE" and "EXDATE" properties. This implies that
   start date/times within exclusion related properties (i.e., "EXDATE"
   and "EXRULE") take precedence over those specified by inclusion
   properties (i.e., "RDATE" and "RRULE"). Where duplicate instances are
   generated by the "RRULE" and "RDATE" properties, only one recurrence
   is considered. Duplicate instances are ignored.

   The "DTSTART" and "DTEND" property pair or "DTSTART" and "DURATION"
   property pair, specified within the iCalendar object defines the
   first instance of the recurrence. When used with a recurrence rule,
   the "DTSTART" and "DTEND" properties MUST be specified in local time
   and the appropriate set of "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>" calendar components MUST be
   included. For detail on the usage of the "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>" calendar
   component, see the "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>" calendar component definition.

   Any duration associated with the iCalendar object applies to all
   members of the generated recurrence set. Any modified duration for
   specific recurrences MUST be explicitly specified using the "RDATE"
   property.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    This property is defined by the following
   notation:

     rrule      = "RRULE" rrulparam ":" recur CRLF

     rrulparam  = *(";" xparam)

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    All examples assume the Eastern United States time zone.

   Daily for 10 occurrences:

     DTSTART;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=DAILY;COUNT=10

     ==> (1997 9:00 AM EDT)September 2-11

   Daily until December 24, 1997:

     DTSTART;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=DAILY;UNTIL=19971224T000000Z

     ==> (1997 9:00 AM EDT)September 2-30;October 1-25
         (1997 9:00 AM EST)October 26-31;November 1-30;December 1-23

   Every other day - forever:

     DTSTART;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=DAILY;INTERVAL=2
     ==> (1997 9:00 AM EDT)September2,4,6,8...24,26,28,30;
          October 2,4,6...20,22,24
         (1997 9:00 AM EST)October 26,28,30;November 1,3,5,7...25,27,29;
          Dec 1,3,...

   Every 10 days, 5 occurrences:

     DTSTART;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=DAILY;INTERVAL=10;COUNT=5

     ==> (1997 9:00 AM EDT)September 2,12,22;October 2,12

   Everyday in January, for 3 years:

     DTSTART;TZID=US-Eastern:19980101T090000
     RRULE:FREQ=YEARLY;UNTIL=20000131T090000Z;
      BYMONTH=1;BYDAY=SU,MO,TU,WE,TH,FR,SA
     or
     RRULE:FREQ=DAILY;UNTIL=20000131T090000Z;BYMONTH=1

     ==> (1998 9:00 AM EDT)January 1-31
         (1999 9:00 AM EDT)January 1-31
         (2000 9:00 AM EDT)January 1-31

   Weekly for 10 occurrences

     DTSTART;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=WEEKLY;COUNT=10

     ==> (1997 9:00 AM EDT)September 2,9,16,23,30;October 7,14,21
         (1997 9:00 AM EST)October 28;November 4

   Weekly until December 24, 1997

     DTSTART;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=WEEKLY;UNTIL=19971224T000000Z

     ==> (1997 9:00 AM EDT)September 2,9,16,23,30;October 7,14,21
         (1997 9:00 AM EST)October 28;November 4,11,18,25;
                           December 2,9,16,23
   Every other week - forever:

     DTSTART;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=WEEKLY;INTERVAL=2;WKST=SU

     ==> (1997 9:00 AM EDT)September 2,16,30;October 14
         (1997 9:00 AM EST)October 28;November 11,25;December 9,23
         (1998 9:00 AM EST)January 6,20;February
     ...

   Weekly on Tuesday and Thursday for 5 weeks:

    DTSTART;TZID=US-Eastern:19970902T090000
    RRULE:FREQ=WEEKLY;UNTIL=19971007T000000Z;WKST=SU;BYDAY=TU,TH
    or

    RRULE:FREQ=WEEKLY;COUNT=10;WKST=SU;BYDAY=TU,TH

    ==> (1997 9:00 AM EDT)September 2,4,9,11,16,18,23,25,30;October 2

   Every other week on Monday, Wednesday and Friday until December 24,
   1997, but starting on Tuesday, September 2, 1997:

     DTSTART;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=WEEKLY;INTERVAL=2;UNTIL=19971224T000000Z;WKST=SU;
      BYDAY=MO,WE,FR
     ==> (1997 9:00 AM EDT)September 2,3,5,15,17,19,29;October
     1,3,13,15,17
         (1997 9:00 AM EST)October 27,29,31;November 10,12,14,24,26,28;
                           December 8,10,12,22

   Every other week on Tuesday and Thursday, for 8 occurrences:

     DTSTART;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=8;WKST=SU;BYDAY=TU,TH

     ==> (1997 9:00 AM EDT)September 2,4,16,18,30;October 2,14,16

   Monthly on the 1st Friday for ten occurrences:

     DTSTART;TZID=US-Eastern:19970905T090000
     RRULE:FREQ=MONTHLY;COUNT=10;BYDAY=1FR

     ==> (1997 9:00 AM EDT)September 5;October 3
         (1997 9:00 AM EST)November 7;Dec 5
         (1998 9:00 AM EST)January 2;February 6;March 6;April 3
         (1998 9:00 AM EDT)May 1;June 5

   Monthly on the 1st Friday until December 24, 1997:

     DTSTART;TZID=US-Eastern:19970905T090000
     RRULE:FREQ=MONTHLY;UNTIL=19971224T000000Z;BYDAY=1FR

     ==> (1997 9:00 AM EDT)September 5;October 3
         (1997 9:00 AM EST)November 7;December 5

   Every other month on the 1st and last Sunday of the month for 10
   occurrences:

     DTSTART;TZID=US-Eastern:19970907T090000
     RRULE:FREQ=MONTHLY;INTERVAL=2;COUNT=10;BYDAY=1SU,-1SU

     ==> (1997 9:00 AM EDT)September 7,28
         (1997 9:00 AM EST)November 2,30

         (1998 9:00 AM EST)January 4,25;March 1,29
         (1998 9:00 AM EDT)May 3,31

   Monthly on the second to last Monday of the month for 6 months:

     DTSTART;TZID=US-Eastern:19970922T090000
     RRULE:FREQ=MONTHLY;COUNT=6;BYDAY=-2MO

     ==> (1997 9:00 AM EDT)September 22;October 20
         (1997 9:00 AM EST)November 17;December 22
         (1998 9:00 AM EST)January 19;February 16

   Monthly on the third to the last day of the month, forever:

     DTSTART;TZID=US-Eastern:19970928T090000
     RRULE:FREQ=MONTHLY;BYMONTHDAY=-3

     ==> (1997 9:00 AM EDT)September 28
         (1997 9:00 AM EST)October 29;November 28;December 29
         (1998 9:00 AM EST)January 29;February 26
     ...

   Monthly on the 2nd and 15th of the month for 10 occurrences:

     DTSTART;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=MONTHLY;COUNT=10;BYMONTHDAY=2,15

     ==> (1997 9:00 AM EDT)September 2,15;October 2,15
         (1997 9:00 AM EST)November 2,15;December 2,15
         (1998 9:00 AM EST)January 2,15

   Monthly on the first and last day of the month for 10 occurrences:

     DTSTART;TZID=US-Eastern:19970930T090000
     RRULE:FREQ=MONTHLY;COUNT=10;BYMONTHDAY=1,-1

     ==> (1997 9:00 AM EDT)September 30;October 1
         (1997 9:00 AM EST)October 31;November 1,30;December 1,31
         (1998 9:00 AM EST)January 1,31;February 1

   Every 18 months on the 10th thru 15th of the month for 10
   occurrences:

     DTSTART;TZID=US-Eastern:19970910T090000
     RRULE:FREQ=MONTHLY;INTERVAL=18;COUNT=10;BYMONTHDAY=10,11,12,13,14,
      15

     ==> (1997 9:00 AM EDT)September 10,11,12,13,14,15

         (1999 9:00 AM EST)March 10,11,12,13

   Every Tuesday, every other month:

     DTSTART;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=MONTHLY;INTERVAL=2;BYDAY=TU

     ==> (1997 9:00 AM EDT)September 2,9,16,23,30
         (1997 9:00 AM EST)November 4,11,18,25
         (1998 9:00 AM EST)January 6,13,20,27;March 3,10,17,24,31
     ...

   Yearly in June and July for 10 occurrences:

     DTSTART;TZID=US-Eastern:19970610T090000
     RRULE:FREQ=YEARLY;COUNT=10;BYMONTH=6,7
     ==> (1997 9:00 AM EDT)June 10;July 10
         (1998 9:00 AM EDT)June 10;July 10
         (1999 9:00 AM EDT)June 10;July 10
         (2000 9:00 AM EDT)June 10;July 10
         (2001 9:00 AM EDT)June 10;July 10
     Note: Since none of the BYDAY, BYMONTHDAY or BYYEARDAY components
     are specified, the day is gotten from DTSTART

   Every other year on January, February, and March for 10 occurrences:

     DTSTART;TZID=US-Eastern:19970310T090000
     RRULE:FREQ=YEARLY;INTERVAL=2;COUNT=10;BYMONTH=1,2,3

     ==> (1997 9:00 AM EST)March 10
         (1999 9:00 AM EST)January 10;February 10;March 10
         (2001 9:00 AM EST)January 10;February 10;March 10
         (2003 9:00 AM EST)January 10;February 10;March 10

   Every 3rd year on the 1st, 100th and 200th day for 10 occurrences:

     DTSTART;TZID=US-Eastern:19970101T090000
     RRULE:FREQ=YEARLY;INTERVAL=3;COUNT=10;BYYEARDAY=1,100,200

     ==> (1997 9:00 AM EST)January 1
         (1997 9:00 AM EDT)April 10;July 19
         (2000 9:00 AM EST)January 1
         (2000 9:00 AM EDT)April 9;July 18
         (2003 9:00 AM EST)January 1
         (2003 9:00 AM EDT)April 10;July 19
         (2006 9:00 AM EST)January 1

   Every 20th Monday of the year, forever:

     DTSTART;TZID=US-Eastern:19970519T090000
     RRULE:FREQ=YEARLY;BYDAY=20MO

     ==> (1997 9:00 AM EDT)May 19
         (1998 9:00 AM EDT)May 18
         (1999 9:00 AM EDT)May 17
     ...

   Monday of week number 20 (where the default start of the week is
   Monday), forever:

     DTSTART;TZID=US-Eastern:19970512T090000
     RRULE:FREQ=YEARLY;BYWEEKNO=20;BYDAY=MO

     ==> (1997 9:00 AM EDT)May 12
         (1998 9:00 AM EDT)May 11
         (1999 9:00 AM EDT)May 17
     ...

   Every Thursday in March, forever:

     DTSTART;TZID=US-Eastern:19970313T090000
     RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=TH

     ==> (1997 9:00 AM EST)March 13,20,27
         (1998 9:00 AM EST)March 5,12,19,26
         (1999 9:00 AM EST)March 4,11,18,25
     ...

   Every Thursday, but only during June, July, and August, forever:

     DTSTART;TZID=US-Eastern:19970605T090000
     RRULE:FREQ=YEARLY;BYDAY=TH;BYMONTH=6,7,8

     ==> (1997 9:00 AM EDT)June 5,12,19,26;July 3,10,17,24,31;
                       August 7,14,21,28
         (1998 9:00 AM EDT)June 4,11,18,25;July 2,9,16,23,30;
                       August 6,13,20,27
         (1999 9:00 AM EDT)June 3,10,17,24;July 1,8,15,22,29;
                       August 5,12,19,26
     ...

   Every Friday the 13th, forever:

     DTSTART;TZID=US-Eastern:19970902T090000
     EXDATE;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=MONTHLY;BYDAY=FR;BYMONTHDAY=13

     ==> (1998 9:00 AM EST)February 13;March 13;November 13
         (1999 9:00 AM EDT)August 13
         (2000 9:00 AM EDT)October 13
     ...

   The first Saturday that follows the first Sunday of the month,
    forever:

     DTSTART;TZID=US-Eastern:19970913T090000
     RRULE:FREQ=MONTHLY;BYDAY=SA;BYMONTHDAY=7,8,9,10,11,12,13

     ==> (1997 9:00 AM EDT)September 13;October 11
         (1997 9:00 AM EST)November 8;December 13
         (1998 9:00 AM EST)January 10;February 7;March 7
         (1998 9:00 AM EDT)April 11;May 9;June 13...
     ...

   Every four years, the first Tuesday after a Monday in November,
   forever (U.S. Presidential Election day):

     DTSTART;TZID=US-Eastern:19961105T090000
     RRULE:FREQ=YEARLY;INTERVAL=4;BYMONTH=11;BYDAY=TU;BYMONTHDAY=2,3,4,
      5,6,7,8

     ==> (1996 9:00 AM EST)November 5
         (2000 9:00 AM EST)November 7
         (2004 9:00 AM EST)November 2
     ...

   The 3rd instance into the month of one of Tuesday, Wednesday or
   Thursday, for the next 3 months:

     DTSTART;TZID=US-Eastern:19970904T090000
     RRULE:FREQ=MONTHLY;COUNT=3;BYDAY=TU,WE,TH;BYSETPOS=3

     ==> (1997 9:00 AM EDT)September 4;October 7
         (1997 9:00 AM EST)November 6

   The 2nd to last weekday of the month:

     DTSTART;TZID=US-Eastern:19970929T090000
     RRULE:FREQ=MONTHLY;BYDAY=MO,TU,WE,TH,FR;BYSETPOS=-2

     ==> (1997 9:00 AM EDT)September 29
         (1997 9:00 AM EST)October 30;November 27;December 30
         (1998 9:00 AM EST)January 29;February 26;March 30
     ...

   Every 3 hours from 9:00 AM to 5:00 PM on a specific day:

     DTSTART;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=HOURLY;INTERVAL=3;UNTIL=19970902T170000Z

     ==> (September 2, 1997 EDT)09:00,12:00,15:00

   Every 15 minutes for 6 occurrences:

     DTSTART;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=MINUTELY;INTERVAL=15;COUNT=6

     ==> (September 2, 1997 EDT)09:00,09:15,09:30,09:45,10:00,10:15

   Every hour and a half for 4 occurrences:

     DTSTART;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=MINUTELY;INTERVAL=90;COUNT=4

     ==> (September 2, 1997 EDT)09:00,10:30;12:00;13:30

   Every 20 minutes from 9:00 AM to 4:40 PM every day:

     DTSTART;TZID=US-Eastern:19970902T090000
     RRULE:FREQ=DAILY;BYHOUR=9,10,11,12,13,14,15,16;BYMINUTE=0,20,40
     or
     RRULE:FREQ=MINUTELY;INTERVAL=20;BYHOUR=9,10,11,12,13,14,15,16

     ==> (September 2, 1997 EDT)9:00,9:20,9:40,10:00,10:20,
                                ... 16:00,16:20,16:40
         (September 3, 1997 EDT)9:00,9:20,9:40,10:00,10:20,
                               ...16:00,16:20,16:40
     ...

   An example where the days generated makes a difference because of
   WKST:

     DTSTART;TZID=US-Eastern:19970805T090000
     RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=4;BYDAY=TU,SU;WKST=MO

     ==> (1997 EDT)Aug 5,10,19,24

     changing only WKST from MO to SU, yields different results...

     DTSTART;TZID=US-Eastern:19970805T090000
     RRULE:FREQ=WEEKLY;INTERVAL=2;COUNT=4;BYDAY=TU,SU;WKST=SU
     ==> (1997 EDT)August 5,17,19,31

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.6'>4.8.6 Alarm Component Properties</h2>
<pre>
   The following properties specify alarm information in calendar
   components.

</pre>
</div>
<div><h2 id='sec4.8.6.1'>4.8.6.1 Action</h2>
<dl>
<dt id='action'>Property Name</dt>
<dd class='PropertyName'><pre>    ACTION

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines the action to be invoked when an alarm
   is triggered.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property MUST be specified once in a "<a rel="applies-to" href="#Valarm">VALARM</a>"
   calendar component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    Each "<a rel="applies-to" href="#Valarm">VALARM</a>" calendar component has a particular type
   of action associated with it. This property specifies the type of
   action

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     action     = "ACTION" actionparam ":" actionvalue CRLF

     actionparam        = *(";" xparam)

     actionvalue        = "AUDIO" / "DISPLAY" / "EMAIL" / "PROCEDURE"
                        / iana-token / x-name

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following are examples of this property in a "VALARM"
   calendar component:

     ACTION:AUDIO

     ACTION:DISPLAY

     ACTION:PROCEDURE

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.6.2'>4.8.6.2 Repeat Count</h2>
<dl>
<dt id='repeat'>Property Name</dt>
<dd class='PropertyName'><pre>    REPEAT

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines the number of time the alarm should be
   repeated, after the initial trigger.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_INTEGER'>INTEGER</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in a "<a rel="applies-to" href="#Valarm">VALARM</a>" calendar
   component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    If the alarm triggers more than once, then this property
   MUST be specified along with the "DURATION" property.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     repeatcnt  = "REPEAT" repparam ":" integer CRLF
     ;Default is "0", zero.

     repparam   = *(";" xparam)

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property for an alarm
   that repeats 4 additional times with a 5 minute delay after the
   initial triggering of the alarm:

     REPEAT:4
     DURATION:PT5M

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.6.3'>4.8.6.3 Trigger</h2>
<dl>
<dt id='trigger'>Property Name</dt>
<dd class='PropertyName'><pre>    TRIGGER

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property specifies when an alarm will trigger.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'>The default value type is <a rel='default-value-type' href='#Value_DURATION'>DURATION</a> <pre>   . The value type can be
   set to a <a rel="allowed-type" href="#Value_DATE">DATE</a>-TIME value type, in which case the value MUST specify a
   UTC formatted <a rel="allowed-type" href="#Value_DATE">DATE</a>-TIME value.

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard, value data type, time zone
   identifier or trigger relationship property parameters can be
   specified on this property. The trigger relationship property
   parameter MUST only be specified when the value type is DURATION.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property MUST be specified in the "<a rel="applies-to" href="#Valarm">VALARM</a>" calendar
   component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    Within the "<a rel="applies-to" href="#Valarm">VALARM</a>" calendar component, this property
   defines when the alarm will trigger. The default value type is
   DURATION, specifying a relative time for the trigger of the alarm.
   The default duration is relative to the start of an event or to-do
   that the alarm is associated with. The duration can be explicitly set

   to trigger from either the end or the start of the associated event
   or to-do with the "RELATED" parameter. A value of START will set the
   alarm to trigger off the start of the associated event or to-do. A
   value of END will set the alarm to trigger off the end of the
   associated event or to-do.

   Either a positive or negative duration may be specified for the
   "TRIGGER" property. An alarm with a positive duration is triggered
   after the associated start or end of the event or to-do. An alarm
   with a negative duration is triggered before the associated start or
   end of the event or to-do.

   The "RELATED" property parameter is not valid if the value type of
   the property is set to DATE-TIME (i.e., for an absolute date and time
   alarm trigger). If a value type of DATE-TIME is specified, then the
   property value MUST be specified in the UTC time format. If an
   absolute trigger is specified on an alarm for a recurring event or
   to-do, then the alarm will only trigger for the specified absolute
   date/time, along with any specified repeating instances.

   If the trigger is set relative to START, then the "DTSTART" property
   MUST be present in the associated "<a rel="applies-to" href="#Vevent">VEVENT</a>" or "<a rel="applies-to" href="#Vtodo">VTODO</a>" calendar
   component. If an alarm is specified for an event with the trigger set
   relative to the END, then the "DTEND" property or the "DSTART" and
   "DURATION' properties MUST be present in the associated "<a rel="applies-to" href="#Vevent">VEVENT</a>"
   calendar component. If the alarm is specified for a to-do with a
   trigger set relative to the END, then either the "DUE" property or
   the "DSTART" and "DURATION' properties MUST be present in the
   associated "<a rel="applies-to" href="#Vtodo">VTODO</a>" calendar component.

   Alarms specified in an event or to-do which is defined in terms of a
   DATE value type will be triggered relative to 00:00:00 UTC on the
   specified date. For example, if "DTSTART:19980205, then the duration
   trigger will be relative to19980205T000000Z.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     trigger    = "TRIGGER" (trigrel / trigabs)

     trigrel    = *(

                ; the following are optional,
                ; but MUST NOT occur more than once

                  (";" "VALUE" "=" "DURATION") /
                  (";" trigrelparam) /

                ; the following is optional,

                ; and MAY occur more than once

                  (";" xparam)
                  ) ":"  dur-value

     trigabs    = 1*(

                ; the following is REQUIRED,
                ; but MUST NOT occur more than once

                  (";" "VALUE" "=" "DATE-TIME") /

                ; the following is optional,
                ; and MAY occur more than once

                  (";" xparam)

                  ) ":" date-time

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    A trigger set 15 minutes prior to the start of the event or
   to-do.

     TRIGGER:-P15M

   A trigger set 5 minutes after the end of the event or to-do.

     TRIGGER;RELATED=END:P5M

   A trigger set to an absolute date/time.

     TRIGGER;VALUE=DATE-TIME:19980101T050000Z

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.7'>4.8.7 Change Management Component Properties</h2>
<pre>
   The following properties specify change management information in
   calendar components.

</pre>
</div>
<div><h2 id='sec4.8.7.1'>4.8.7.1 Date/Time Created</h2>
<dl>
<dt id='created'>Property Name</dt>
<dd class='PropertyName'><pre>    CREATED

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property specifies the date and time that the calendar
   information was created by the calendar user agent in the calendar
   store.

        Note: This is analogous to the creation date and time for a file
        in the file system.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_DATE-TIME'>DATE-TIME</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified once in "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>"
   or "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The date and time is a UTC value.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     created    = "CREATED" creaparam ":" date-time CRLF

     creaparam  = *(";" xparam)

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property:

     CREATED:19960329T133000Z

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.7.2'>4.8.7.2 Date/Time Stamp</h2>
<dl>
<dt id='dtstamp'>Property Name</dt>
<dd class='PropertyName'><pre>    DTSTAMP

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    The property indicates the date/time that the instance of
   the iCalendar object was created.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_DATE-TIME'>DATE-TIME</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property MUST be included in the "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>",
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" or "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The value MUST be specified in the UTC time format.

   This property is also useful to protocols such as <a href='#ref_IMIP'>[IMIP]</a> that have
   inherent latency issues with the delivery of content. This property
   will assist in the proper sequencing of messages containing iCalendar
   objects.

   This property is different than the "CREATED" and "LAST-MODIFIED"
   properties. These two properties are used to specify when the
   particular calendar data in the calendar store was created and last
   modified. This is different than when the iCalendar object
   representation of the calendar service information was created or
   last modified.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     dtstamp    = "DTSTAMP" stmparam ":" date-time CRLF

     stmparam   = *(";" xparam)

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>   

     DTSTAMP:19971210T080000Z

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.7.3'>4.8.7.3 Last Modified</h2>
<dl>
<dt id='lastModified'>Property Name</dt>
<dd class='PropertyName'><pre>    LAST-MODIFIED

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    The property specifies the date and time that the
   information associated with the calendar component was last revised
   in the calendar store.

        Note: This is analogous to the modification date and time for a
        file in the file system.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_DATE-TIME'>DATE-TIME</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in the "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>",
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" or "<a rel="applies-to" href="#Vtimezone">VTIMEZONE</a>" calendar components.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The property value MUST be specified in the UTC time
   format.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     last-mod   = "LAST-MODIFIED" lstparam ":" date-time CRLF

     lstparam   = *(";" xparam)

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is are examples of this property:

     LAST-MODIFIED:19960817T133000Z

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.7.4'>4.8.7.4 Sequence Number</h2>
<dl>
<dt id='sequence'>Property Name</dt>
<dd class='PropertyName'><pre>    SEQUENCE

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines the revision sequence number of the
   calendar component within a sequence of revisions.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_integer'>integer</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard property parameters can be
   specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified in "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>" or
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" calendar component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    When a calendar component is created, its sequence
   number is zero (US-ASCII decimal 48). It is monotonically incremented
   by the "Organizer's" CUA each time the "Organizer" makes a
   significant revision to the calendar component. When the "Organizer"
   makes changes to one of the following properties, the sequence number
   MUST be incremented:

     .  "DTSTART"

     .  "DTEND"

     .  "DUE"

     .  "RDATE"

     .  "RRULE"

     .  "EXDATE"

     .  "EXRULE"

     .  "STATUS"

   In addition, changes made by the "Organizer" to other properties can
   also force the sequence number to be incremented. The "Organizer" CUA
   MUST increment the sequence number when ever it makes changes to
   properties in the calendar component that the "Organizer" deems will
   jeopardize the validity of the participation status of the
   "Attendees". For example, changing the location of a meeting from one
   locale to another distant locale could effectively impact the
   participation status of the "Attendees".

   The "Organizer" includes this property in an iCalendar object that it
   sends to an "Attendee" to specify the current version of the calendar
   component.

   The "Attendee" includes this property in an iCalendar object that it
   sends to the "Organizer" to specify the version of the calendar
   component that the "Attendee" is referring to.

   A change to the sequence number is not the mechanism that an
   "Organizer" uses to request a response from the "Attendees". The
   "RSVP" parameter on the "ATTENDEE" property is used by the
   "Organizer" to indicate that a response from the "Attendees" is
   requested.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    This property is defined by the following
   notation:

     seq = "SEQUENCE" seqparam ":" integer CRLF
     ; Default is "0"

     seqparam   = *(";" xparam)

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following is an example of this property for a calendar
   component that was just created by the "Organizer".

     SEQUENCE:0

   The following is an example of this property for a calendar component
   that has been revised two different times by the "Organizer".

     SEQUENCE:2

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.8'>4.8.8 Miscellaneous Component Properties</h2>
<pre>
   The following properties specify information about a number of
   miscellaneous features of calendar components.

</pre>
</div>
<div><h2 id='sec4.8.8.1'>4.8.8.1 Non-standard Properties</h2>
<dl>
<dt id='X-'>Property Name</dt>
<dd class='PropertyName'><pre>    Any property name with a "X-" prefix

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This class of property provides a framework for defining
   non-standard properties.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard and language property parameters
   can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    This property can be specified in any calendar
   component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    The MIME Calendaring and Scheduling Content Type
   provides a "standard mechanism for doing non-standard things". This
   extension support is provided for implementers to "push the envelope"
   on the existing version of the memo. Extension properties are

   specified by property and/or property parameter names that have the
   prefix text of "X-" (the two character sequence: LATIN CAPITAL LETTER
   X character followed by the HYPEN-MINUS character). It is recommended
   that vendors concatenate onto this sentinel another short prefix text
   to identify the vendor. This will facilitate readability of the
   extensions and minimize possible collision of names between different
   vendors. User agents that support this content type are expected to
   be able to parse the extension properties and property parameters but
   can ignore them.

   At present, there is no registration authority for names of extension
   properties and property parameters. The data type for this property
   is TEXT. Optionally, the data type can be any of the other valid data
   types.

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     x-prop     = x-name *(";" xparam) ";" languageparam] ":" text CRLF
        ; Lines longer than 75 octets should be folded

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following might be the ABC vendor's extension for an
   audio-clip form of subject property:

     X-ABC-MMSUBJ;X-ABC-MMSUBJTYPE=wave:http://load.noise.org/mysubj.wav

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec4.8.8.2'>4.8.8.2 Request Status</h2>
<dl>
<dt id='requestStatus'>Property Name</dt>
<dd class='PropertyName'><pre>    REQUEST-STATUS

</pre>
</dd>
<dt>Purpose</dt>
<dd class='Purpose'><pre>    This property defines the status code returned for a
   scheduling request.

</pre>
</dd>
<dt>Value Type</dt>
<dd class='ValueType'><a rel='value-type' href='#Value_TEXT'>TEXT</a> <pre>   

</pre>
</dd>
<dt>Property Parameters</dt>
<dd class='PropertyParameters'><pre>    Non-standard and language property parameters
   can be specified on this property.

</pre>
</dd>
<dt>Conformance</dt>
<dd class='Conformance'><pre>    The property can be specified in "<a rel="applies-to" href="#Vevent">VEVENT</a>", "<a rel="applies-to" href="#Vtodo">VTODO</a>",
   "<a rel="applies-to" href="#Vjournal">VJOURNAL</a>" or "<a rel="applies-to" href="#Vfreebusy">VFREEBUSY</a>" calendar component.

</pre>
</dd>
<dt>Description</dt>
<dd class='Description'><pre>    This property is used to return status code information
   related to the processing of an associated iCalendar object. The data
   type for this property is TEXT.

   The value consists of a short return status component, a longer
   return status description component, and optionally a status-specific
   data component. The components of the value are separated by the
   SEMICOLON character (US-ASCII decimal 59).

   The short return status is a PERIOD character (US-ASCII decimal 46)
   separated 3-tuple of integers. For example, "3.1.1". The successive
   levels of integers provide for a successive level of status code
   granularity.

   The following are initial classes for the return status code.
   Individual iCalendar object methods will define specific return
   status codes for these classes. In addition, other classes for the
   return status code may be defined using the registration process
   defined later in this memo.

     |==============+===============================================|
     | Short Return | Longer Return Status Description              |
     | Status Code  |                                               |
     |==============+===============================================|
     |    1.xx      | Preliminary success. This class of status     |
     |              | of status code indicates that the request has |
     |              | request has been initially processed but that |
     |              | completion is pending.                        |
     |==============+===============================================|
     |    2.xx      | Successful. This class of status code         |
     |              | indicates that the request was completed      |
     |              | successfuly. However, the exact status code   |
     |              | can indicate that a fallback has been taken.  |
     |==============+===============================================|
     |    3.xx      | Client Error. This class of status code       |
     |              | indicates that the request was not successful.|
     |              | The error is the result of either a syntax or |
     |              | a semantic error in the client formatted      |
     |              | request. Request should not be retried until  |
     |              | the condition in the request is corrected.    |
     |==============+===============================================|
     |    4.xx      | Scheduling Error. This class of status code   |
     |              | indicates that the request was not successful.|
     |              | Some sort of error occurred within the        |
     |              | calendaring and scheduling service, not       |
     |              | directly related to the request itself.       |
     |==============+===============================================|

</pre>
</dd>
<dt>Format Definition</dt>
<dd class='FormatDefinition'><pre>    The property is defined by the following notation:

     rstatus    = "REQUEST-STATUS" rstatparam ":"
                  statcode ";" statdesc ";" extdata]

     rstatparam = *(

                ; the following is optional,
                ; but MUST NOT occur more than once

                (";" languageparm) /

                ; the following is optional,
                ; and MAY occur more than once

                (";" xparam)

                )

     statcode   = 1*DIGIT *("." 1*DIGIT)
     ;Hierarchical, numeric return status code

     statdesc   = text
     ;Textual status description

     extdata    = text
     ;Textual exception data. For example, the offending property
     ;name and value or complete property line.

</pre>
</dd>
<dt>Example</dt>
<dd class='Example'><pre>    The following are some possible examples of this property.
   The COMMA and SEMICOLON separator characters in the property value
   are BACKSLASH character escaped because they appear in a  text value.

     REQUEST-STATUS:2.0;Success

     REQUEST-STATUS:3.1;Invalid property value;DTSTART:96-Apr-01

     REQUEST-STATUS:2.8; Success\, repeating event ignored. Scheduled
      as a single event.;RRULE:FREQ=WEEKLY\;INTERVAL=2

     REQUEST-STATUS:4.1;Event conflict. Date/time is busy.

     REQUEST-STATUS:3.7;Invalid calendar user;ATTENDEE:
      MAILTO:jsmith@host.com

</pre>
</dd>
</dl>
</div>
<div><h2 id='sec5'>5 iCalendar Object Examples</h2>
<pre>
   The following examples are provided as an informational source of
   illustrative iCalendar objects consistent with this content type.

   The following example specifies a three-day conference that begins at
   8:00 AM EDT, September 18, 1996 and end at 6:00 PM EDT, September 20,
   1996.

     BEGIN:VCALENDAR PRODID:-//xyz Corp//NONSGML PDA Calendar Verson
     1.0//EN VERSION:2.0 BEGIN:VEVENT DTSTAMP:19960704T120000Z
     UID:uid1@host.com ORGANIZER:MAILTO:jsmith@host.com
     DTSTART:19960918T143000Z DTEND:19960920T220000Z STATUS:CONFIRMED

     CATEGORIES:CONFERENCE SUMMARY:Networld+Interop Conference
     DESCRIPTION:Networld+Interop Conference
       and Exhibit\nAtlanta World Congress Center\n
      Atlanta, Georgia END:VEVENT END:VCALENDAR

   The following example specifies a group scheduled meeting that begin
   at 8:30 AM EST on March 12, 1998 and end at 9:30 AM EST on March 12,
   1998. The "Organizer" has scheduled the meeting with one or more
   calendar users in a group. A time zone specification for Eastern
   United States has been specified.

     BEGIN:VCALENDAR
     PRODID:-//RDU Software//NONSGML HandCal//EN
     VERSION:2.0
     BEGIN:VTIMEZONE
     TZID:US-Eastern
     BEGIN:STANDARD
     DTSTART:19981025T020000
     RDATE:19981025T020000
     TZOFFSETFROM:-0400
     TZOFFSETTO:-0500
     TZNAME:EST
     END:STANDARD
     BEGIN:DAYLIGHT
     DTSTART:19990404T020000
     RDATE:19990404T020000
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     END:DAYLIGHT
     END:VTIMEZONE
     BEGIN:VEVENT
     DTSTAMP:19980309T231000Z
     UID:guid-1.host1.com
     ORGANIZER;ROLE=CHAIR:MAILTO:mrbig@host.com
     ATTENDEE;RSVP=TRUE;ROLE=REQ-PARTICIPANT;CUTYPE=GROUP:
      MAILTO:employee-A@host.com
     DESCRIPTION:Project XYZ Review Meeting
     CATEGORIES:MEETING
     CLASS:PUBLIC
     CREATED:19980309T130000Z
     SUMMARY:XYZ Project Review
     DTSTART;TZID=US-Eastern:19980312T083000
     DTEND;TZID=US-Eastern:19980312T093000
     LOCATION:1CP Conference Room 4350
     END:VEVENT
     END:VCALENDAR

   The following is an example of an iCalendar object passed in a MIME
   message with a single body part consisting of a "text/calendar"
   Content Type.

     TO:jsmith@host1.com
     FROM:jdoe@host1.com
     MIME-VERSION:1.0
     MESSAGE-ID:&lt;id3@host1.com>
     CONTENT-TYPE:text/calendar

     BEGIN:VCALENDAR
     METHOD:xyz
     VERSION:2.0
     PRODID:-//ABC Corporation//NONSGML My Product//EN
     BEGIN:VEVENT
     DTSTAMP:19970324T1200Z
     SEQUENCE:0
     UID:uid3@host1.com
     ORGANIZER:MAILTO:jdoe@host1.com
     ATTENDEE;RSVP=TRUE:MAILTO:jsmith@host1.com
     DTSTART:19970324T123000Z
     DTEND:19970324T210000Z
     CATEGORIES:MEETING,PROJECT
     CLASS:PUBLIC
     SUMMARY:Calendaring Interoperability Planning Meeting
     DESCRIPTION:Discuss how we can test c&amp;s interoperability\n
      using iCalendar and other IETF standards.
     LOCATION:LDB Lobby
     ATTACH;FMTTYPE=application/postscript:ftp://xyzCorp.com/pub/
      conf/bkgrnd.ps
     END:VEVENT
     END:VCALENDAR

   The following is an example of a to-do due on April 15, 1998. An
   audio alarm has been specified to remind the calendar user at noon,
   the day before the to-do is expected to be completed and repeat
   hourly, four additional times. The to-do definition has been modified
   twice since it was initially created.

     BEGIN:VCALENDAR
     VERSION:2.0
     PRODID:-//ABC Corporation//NONSGML My Product//EN
     BEGIN:VTODO
     DTSTAMP:19980130T134500Z
     SEQUENCE:2
     UID:uid4@host1.com
     ORGANIZER:MAILTO:unclesam@us.gov
     ATTENDEE;PARTSTAT=ACCEPTED:MAILTO:jqpublic@host.com

     DUE:19980415T235959
     STATUS:NEEDS-ACTION
     SUMMARY:Submit Income Taxes
     BEGIN:VALARM
     ACTION:AUDIO
     TRIGGER:19980403T120000
     ATTACH;FMTTYPE=audio/basic:http://host.com/pub/audio-
      files/ssbanner.aud
     REPEAT:4
     DURATION:PT1H
     END:VALARM
     END:VTODO
     END:VCALENDAR

   The following is an example of a journal entry.

     BEGIN:VCALENDAR
     VERSION:2.0
     PRODID:-//ABC Corporation//NONSGML My Product//EN
     BEGIN:VJOURNAL
     DTSTAMP:19970324T120000Z
     UID:uid5@host1.com
     ORGANIZER:MAILTO:jsmith@host.com
     STATUS:DRAFT
     CLASS:PUBLIC
     CATEGORY:Project Report, XYZ, Weekly Meeting
     DESCRIPTION:Project xyz Review Meeting Minutes\n
      Agenda\n1. Review of project version 1.0 requirements.\n2.
     Definition
      of project processes.\n3. Review of project schedule.\n
      Participants: John Smith, Jane Doe, Jim Dandy\n-It was
       decided that the requirements need to be signed off by
       product marketing.\n-Project processes were accepted.\n
      -Project schedule needs to account for scheduled holidays
       and employee vacation time. Check with HR for specific
       dates.\n-New schedule will be distributed by Friday.\n-
      Next weeks meeting is cancelled. No meeting until 3/23.
     END:VJOURNAL
     END:VCALENDAR

   The following is an example of published busy time information. The
   iCalendar object might be placed in the network resource
   www.host.com/calendar/busytime/jsmith.ifb.

     BEGIN:VCALENDAR
     VERSION:2.0
     PRODID:-//RDU Software//NONSGML HandCal//EN
     BEGIN:VFREEBUSY

     ORGANIZER:MAILTO:jsmith@host.com
     DTSTART:19980313T141711Z
     DTEND:19980410T141711Z
     FREEBUSY:19980314T233000Z/19980315T003000Z
     FREEBUSY:19980316T153000Z/19980316T163000Z
     FREEBUSY:19980318T030000Z/19980318T040000Z
     URL:http://www.host.com/calendar/busytime/jsmith.ifb
     END:VFREEBUSY
     END:VCALENDAR

</pre>
</div>
<div><h2 id='sec6'>6 Recommended Practices</h2>
<pre>
   These recommended practices should be followed in order to assure
   consistent handling of the following cases for an iCalendar object.

   1.  Content lines longer than 75 octets SHOULD be folded.

   2.  A calendar entry with a "DTSTART" property but no "DTEND"
       property does not take up any time. It is intended to represent
       an event that is associated with a given calendar date and time
       of day, such as an anniversary. Since the event does not take up
       any time, it MUST NOT be used to record busy time no matter what
       the value for the "TRANSP" property.

   3.  When the "DTSTART" and "DTEND", for "VEVENT", "VJOURNAL" and
       "VFREEBUSY" calendar components, and "DTSTART" and "DUE", for
       "VTODO" calendar components, have the same value data type (e.g.,
       DATE-TIME), they SHOULD specify values in the same time format
       (e.g., UTC time format).

   4.  When the combination of the "RRULE" and "RDATE" properties on an
       iCalendar object produces multiple instances having the same
       start date/time, they should be collapsed to, and considered as,
       a single instance.

   5.  When a calendar user receives multiple requests for the same
       calendar component (e.g., REQUEST for a "VEVENT" calendar
       component) as a result of being on multiple mailing lists
       specified by "ATTENDEE" properties in the request, they SHOULD
       respond to only one of the requests. The calendar user SHOULD
       also specify (using the "MEMBER" parameter of the "ATTENDEE"
       property) which mailing list they are a member of.

   6.  An implementation can truncate a "SUMMARY" property value to 255
       characters.

   7.  If seconds of the minute are not supported by an implementation,
       then a value of "00" SHOULD be specified for the seconds
       component in a time value.

   8.  If the value type parameter (VALUE=) contains an unknown value
       type, it SHOULD be treated as TEXT.

   9.  TZURL values SHOULD NOT be specified as a FILE URI type. This URI
       form can be useful within an organization, but is problematic in
       the Internet.

   10.  Some possible English values for CATEGORIES property include
        "ANNIVERSARY", "APPOINTMENT", "BUSINESS", "EDUCATION",
        "HOLIDAY", "MEETING", "MISCELLANEOUS", "NON-WORKING HOURS", "NOT
        IN OFFICE", "PERSONAL", "PHONE CALL", "SICK DAY", "SPECIAL
        OCCASION", "TRAVEL", "VACATION". Categories can be specified in
        any registered language.

   11.  Some possible English values for RESOURCES property include
        "CATERING", "CHAIRS", "COMPUTER PROJECTOR", "EASEL", "OVERHEAD
        PROJECTOR", "SPEAKER PHONE", "TABLE", "TV", "VCR", "VIDEO
        PHONE", "VEHICLE". Resources can be specified in any registered
        language.

</pre>
</div>
<div><h2 id='sec7'>7 Registration of Content Type Elements</h2>
<pre>
   This section provides the process for registration of MIME
   Calendaring and Scheduling Content Type iCalendar object methods and
   new or modified properties.

</pre>
</div>
<div><h2 id='sec7.1'>7.1 Registration of New and Modified iCalendar Object Methods</h2>
<pre>
   New MIME Calendaring and Scheduling Content Type iCalendar object
   methods are registered by the publication of an IETF Request for
   Comments (RFC). Changes to an iCalendar object method are registered
   by the publication of a revision of the RFC defining the method.

</pre>
</div>
<div><h2 id='sec7.2'>7.2 Registration of New Properties</h2>
<pre>
   This section defines procedures by which new properties or enumerated
   property values for the MIME Calendaring and Scheduling Content Type
   can be registered with the IANA. Non-IANA properties can be used by
   bilateral agreement, provided the associated properties names follow
   the "X-" convention.

   The procedures defined here are designed to allow public comment and
   review of new properties, while posing only a small impediment to the
   definition of new properties.

   Registration of a new property is accomplished by the following
   steps.

</pre>
</div>
<div><h2 id='sec7.2.1'>7.2.1 Define the property</h2>
<pre>
   A property is defined by completing the following template.

     To: ietf-calendar@imc.org

     Subject: Registration of text/calendar MIME property XXX

     Property name:

     Property purpose:

     Property value type(s):

     Property parameter (s):

     Conformance:

     Description:

     Format definition:

     Examples:

   The meaning of each field in the template is as follows.

   Property name: The name of the property, as it will appear in the
   body of an text/calendar MIME Content-Type "property: value" line to
   the left of the colon ":".

   Property purpose: The purpose of the property (e.g., to indicate a
   delegate for the event or to-do, etc.). Give a short but clear
   description.

   Property value type (s): Any of the valid value types for the
   property value needs to be specified. The default value type also
   needs to be specified. If a new value type is specified, it needs to
   be declared in this section.

   Property parameter (s): Any of the valid property parameters for the
   property needs to be specified.

   Conformance: The calendar components that the property can appear in
   needs to be specified.

   Description: Any special notes about the property, how it is to be
   used, etc.

   Format definition: The ABNF for the property definition needs to be
   specified.

   Examples: One or more examples of instances of the property needs to
   be specified.

</pre>
</div>
<div><h2 id='sec7.2.2'>7.2.2 Post the Property definition</h2>
<pre>
   The property description MUST be posted to the new property
   discussion list, ietf-calendar@imc.org.

</pre>
</div>
<div><h2 id='sec7.2.3'>7.2.3 Allow a comment period</h2>
<pre>
   Discussion on the new property MUST be allowed to take place on the
   list for a minimum of two weeks. Consensus MUST be reached on the
   property before proceeding to the next step.

</pre>
</div>
<div><h2 id='sec7.2.4'>7.2.4 Submit the property for approval</h2>
<pre>
   Once the two-week comment period has elapsed, and the proposer is
   convinced consensus has been reached on the property, the
   registration application should be submitted to the Method Reviewer
   for approval. The Method Reviewer is appointed to the Application
   Area Directors and can either accept or reject the property
   registration. An accepted registration should be passed on by the
   Method Reviewer to the IANA for inclusion in the official IANA method
   registry. The registration can be rejected for any of the following
   reasons. 1) Insufficient comment period; 2) Consensus not reached; 3)
   Technical deficiencies raised on the list or elsewhere have not been
   addressed. The Method Reviewer's decision to reject a property can be
   appealed by the proposer to the IESG, or the objections raised can be
   addressed by the proposer and the property resubmitted.

</pre>
</div>
<div><h2 id='sec7.3'>7.3 Property Change Control</h2>
<pre>
   Existing properties can be changed using the same process by which
   they were registered.

        1.           Define the change

        2.           Post the change

        3.           Allow a comment period

        4.           Submit the property for approval

   Note that the original author or any other interested party can
   propose a change to an existing property, but that such changes
   should only be proposed when there are serious omissions or errors in
   the published memo. The Method Reviewer can object to a change if it
   is not backward compatible, but is not required to do so.

   Property definitions can never be deleted from the IANA registry, but
   properties which are no longer believed to be useful can be declared
   OBSOLETE by a change to their "intended use" field.

</pre>
</div>
<div><h2 id='sec8'>8 References</h2>
<dl>
<dt id='ref_IMIP'>[IMIP]</dt>
<dd>     Dawson, F., Mansour, S. and S. Silverberg, <cite><a href='http://www.ietf.org/rfc/rfc2447'>iCalendar
Message-based Interoperability Protocol (IMIP)</a></cite>, RFC 2447,
November 1998.
</dd>
<dt id='ref_ITIP'>[ITIP]</dt>
<dd>     Silverberg, S., Mansour, S., Dawson, F. and R. Hopson,
<cite><a href='http://www.ietf.org/rfc/rfc2446'>iCalendar Transport-Independent Interoperability Protocol
(iTIP) : Scheduling Events, Busy Time, To-dos and Journal
Entries</a></cite>, RFC 2446, November 1998.
</dd>
<dt id='ref_ISO_8601'>[ISO 8601]</dt>
<dd> ISO 8601, <cite>Data elements and interchange formats-
Information interchange--Representation of dates and
times</cite>, International Organization for Standardization,
June, 1988.
</dd>
<dt id='ref_ISO_9070'>[ISO 9070]</dt>
<dd> ISO/IEC 9070, <cite>Information Technology_SGML Support
Facilities--Registration Procedures for Public Text Owner
Identifiers</cite>, Second Edition, International Organization
for Standardization, April 1991.
</dd>
<dt id='ref_RFC_822'>[RFC 822]</dt>
<dd>  Crocker, D., <cite><a href='http://www.ietf.org/rfc/rfc822'>Standard for the Format of ARPA Internet
Text Messages</a></cite>, STD 11, RFC 822, August 1982.
</dd>
<dt id='ref_RFC_1738'>[RFC 1738]</dt>
<dd> Berners-Lee, T., Masinter, L. and M. McCahill, <cite><a href='http://www.ietf.org/rfc/rfc1738'>Uniform
Resource Locators (URL)</a></cite>, RFC 1738, December 1994.
</dd>
<dt id='ref_RFC_1766'>[RFC 1766]</dt>
<dd> Alvestrand, H., <cite><a href='http://www.ietf.org/rfc/rfc1766'>Tags for the Identification of
Languages</a></cite>, RFC 1766, March 1995.
</dd>
<dt id='ref_RFC_2045'>[RFC 2045]</dt>
<dd> Freed, N. and N. Borenstein, <cite><a href='http://www.ietf.org/rfc/rfc2045'> Multipurpose Internet Mail
Extensions (MIME) - Part One: Format of Internet Message
Bodies</a></cite>, RFC 2045, November 1996.
</dd>
<dt id='ref_RFC_2046'>[RFC 2046]</dt>
<dd> Freed, N. and N. Borenstein, <cite><a href='http://www.ietf.org/rfc/rfc2046'> Multipurpose Internet Mail
Extensions (MIME) - Part Two: Media Types</a></cite>, RFC 2046,
November 1996.
</dd>
<dt id='ref_RFC_2048'>[RFC 2048]</dt>
<dd> Freed, N., Klensin, J. and J. Postel, <cite><a href='http://www.ietf.org/rfc/rfc2048'>Multipurpose
Internet Mail Extensions (MIME) - Part Four: Registration
Procedures</a></cite>, RFC 2048, January 1997.
</dd>
<dt id='ref_RFC_2119'>[RFC 2119]</dt>
<dd> Bradner, S., <cite><a href='http://www.ietf.org/rfc/rfc2119'>Key words for use in RFCs to Indicate
Requirement Levels</a></cite>, BCP 14, RFC 2119, March 1997.
</dd>
<dt id='ref_RFC_2234'>[RFC 2234]</dt>
<dd> Crocker, D. and P. Overell, <cite><a href='http://www.ietf.org/rfc/rfc2234'>Augmented BNF for Syntax
Specifications: ABNF</a></cite>, RFC 2234, November 1997.
</dd>
<dt id='ref_RFC_2279'>[RFC 2279]</dt>
<dd> Yergeau, F., <cite><a href='http://www.ietf.org/rfc/rfc2279'>UTF-8, a transformation format of ISO
10646</a></cite>, RFC 2279, January 1998.
</dd>
<dt id='ref_RFC_2425'>[RFC 2425]</dt>
<dd> Howes, T., Smith, M. and F. Dawson, <cite><a href='http://www.ietf.org/rfc/rfc2425'>A MIME Content-Type
for Directory Information</a></cite>, RFC 2425, September 1998.
</dd>
<dt id='ref_RFC_2426'>[RFC 2426]</dt>
<dd> Dawson, F. and T. Howes, <cite><a href='http://www.ietf.org/rfc/rfc2426'>vCard MIME Directory Profile</a></cite>,
RFC 2426, September 1998.
</dd>
<dt id='ref_TZ'>[TZ]</dt>
<dd>       Olson, A.D., et al, Time zone code and data,
ftp://elsie.nci.nih.gov/pub/, updated periodically.
</dd>
<dt id='ref_VCAL'>[VCAL]</dt>
<dd>     Internet Mail Consortium, <cite><a href='http://www.imc.org/pdi/vcal-10.txt'>vCalendar - The Electronic
Calendaring and Scheduling Exchange Format</a></cite>,
http://www.imc.org/pdi/vcal-10.txt, September 18, 1996.
</dd>
<dt id='ref_VCAL'>[VCAL]</dt>
<dd>     Internet Mail Consortium, <cite><a href='http://www.imc.org/pdi/vcal-10.txt'>vCalendar - The Electronic
Calendaring and Scheduling Exchange Format</a></cite>,
http://www.imc.org/pdi/vcal-10.txt, September 18, 1996.
</dd>
</dl>
</div>
<div><h2 id='sec9'>9 Acknowledgments</h2>
<p>
   A hearty thanks to the IETF Calendaring and Scheduling Working Group
   and also the following individuals who have participated in the
   drafting, review and discussion of this memo:
</p>
<p>
   Roland Alden, Harald T. Alvestrand, Eric Berman, Denis Bigorgne, John
   Binici, Bill Bliss, Philippe Boucher, Steve Carter, Andre
   Courtemanche, Dave Crocker, David Curley, Alec Dun, John Evans, Ross
   Finlayson, Randell Flint, Ned Freed, Patrik Faltstrom, Chuck
   Grandgent, Mark Handley, Steve Hanna, Paul B. Hill, Paul Hoffman,
   Ross Hopson, Mark Horton, Daryl Huff, Bruce Kahn, C. Harald Koch,
   Ryan Jansen, Don Lavange, Antoine Leca, Theodore Lorek, Steve
   Mansour, Skip Montanaro, Keith Moore, Cecil Murray, Chris Newman,
   John Noerenberg, Ralph Patterson, Pete Resnick, Keith Rhodes, Robert
   Ripberger, John Rose, Doug Royer, Andras Salamar, Ted Schuh, Vinod
   Seraphin, Derrick Shadel, Ken Shan, Andrew Shuman, Steve Silverberg,
   William P. Spencer, John Sun, Mark Towfiq, Yvonne Tso, Robert Visnov,
   James L. Weiner, Mike Weston, William Wyatt.
</p>
</div><div><h2 id='sec10'>10 Authors' and Chairs' Addresses</h2>
<pre>
   The following address information is provided in a MIME-VCARD,
   Electronic Business Card, format.

   The authors of this memo are:

   BEGIN:VCARD
   VERSION:3.0
   N:Dawson;Frank
   FN:Frank Dawson
   ORG:Lotus Development Corporation
   ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive;
    Raleigh;NC;27613-3502;USA
   TEL;TYPE=WORK,MSG:+1-919-676-9515
   TEL;TYPE=WORK,FAX:+1-919-676-9564
   EMAIL;TYPE=PREF,INTERNET:Frank_Dawson@Lotus.com
   EMAIL;TYPE=INTERNET:fdawson@earthlink.net
   URL:http://home.earthlink.net/~fdawson
   END:VCARD

   BEGIN:VCARD
   VERSION:3.0
   N:Stenerson;Derik
   FN:Derik Stenerson
   ORG:Microsoft Corporation
   ADR;TYPE=WORK,POSTAL,PARCEL:;;One Microsoft Way;
    Redmond;WA;98052-6399;USA
   TEL;TYPE=WORK,MSG:+1-425-936-5522
   TEL;TYPE=WORK,FAX:+1-425-936-7329
   EMAIL;TYPE=INTERNET:deriks@Microsoft.com
   END:VCARD

   The iCalendar object is a result of the work of the Internet
   Engineering Task Force Calendaring and Scheduling Working Group. The
   chairmen of that working group are:

   BEGIN:VCARD
   VERSION:3.0
   N:Ganguly;Anik
   FN:Anik Ganguly
   ORG: Open Text Inc.
   ADR;TYPE=WORK,POSTAL,PARCEL:;Suite 101;38777 West Six Mile Road;
    Livonia;MI;48152;USA
   TEL;TYPE=WORK,MSG:+1-734-542-5955
   EMAIL;TYPE=INTERNET:ganguly@acm.org
   END:VCARD

   The co-chairman of that working group is:

   BEGIN:VCARD
   VERSION:3.0
   N:Moskowitz;Robert
   FN:Robert Moskowitz
   EMAIL;TYPE=INTERNET:rgm-ietf@htt-consult.com
   END:VCARD

</pre>
</div>
<div><h2 id='sec11'>11 Full Copyright Statement</h2>
<p>
   Copyright (C) The Internet Society (1998).  All Rights Reserved.
</p>
<p>
   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.
</p>
<p>
   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.
</p>
<p>
   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
</p>
</div></body></html>