[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000. Author's Address Bernard Desruisseaux (editor) Oracle Corporation 600 blvd.
Berners- Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Howes, "Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator", RFC 4516, June 2006. Dusseault, "Calendaring Extensions to Web DAV (Cal DAV)", RFC 4791, March 2007. x-param can be used on RECUR value type properties instead.
[RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397, August 1998. Dawson, "A MIME Content-Type for Directory Information", RFC 2425, September 1998. [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. The "DTSTART" property SHOULD be synchronized with the recurrence rule, if specified. The "RRULE" property SHOULD NOT occur more than once in a component. The BYHOUR, BYMINUTE, and BYSECOND rule parts MUST NOT be specified in the "RRULE" property when the "DTSTART" property is specified as a DATE value. The value type of the "DTEND" or "DUE" properties MUST match the value type of "DTSTART" property. The "DURATION" property can no longer appear in "VFREEBUSY" components. The "EXRULE" property can no longer be specified in a component. The "THISANDPRIOR" value can no longer be used with the "RANGE" parameter. The "PROCEDURE" value can no longer be used with the "ACTION" property. The value type RECUR no longer allows multiple values to be specified by a COMMA-separated list of values. x-name rule parts can no longer be specified in properties of RECUR value type (e.g., "RRULE").
- dating88 net
- dating usinsk
- bria myles dating
- dating someone with schizophrenia
- www eroprofiledating compchat
- dating millionaire model
- dating services professiona
Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the BSD License.
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008.
The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
[ANSI INCITS 61-1986] International Committee for Information Technology, "Representation of Geographic Point Locations for Information Interchange (formerly ANSI X3.61-1986 (R1997))", ANSI INCITS 61-1986 (R2007), 2007. Mc Cahill, "Uniform Resource Locators (URL)", RFC 1738, December 1994.
[2447bis] Melnikov, A., "i Calendar Message-Based Interoperability Protocol (i MIP)", Work in Progress, June 2008.
[2446bis] Daboo, C., "i Calendar Transport-Independent Interoperability Protocol (i TIP)", Work in Progress, April 2009.
Abstract This document defines the i Calendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol.
Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements.