Network Working Group C. Norris Internet-Draft Eventful Expires: February 2, 2008 McCullough UC Berkeley August 1, 2007 Internet Calendaring and Scheduling Venue Component Specification draft-norris-ical-venue-01 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on February 2, 2008. Copyright Notice Copyright (C) The IETF Trust (2007). Norris & McCullough Expires February 2, 2008 [Page 1] Internet-Draft ical-venue August 2007 Abstract The currently existing iCalendar standard (RFC 2445) provides only a simple text field ("LOCATION" property) for specifying the location where an event (or "TODO" item) will occur. While this may be adequate for human readers, it is difficult for automated systems to make use of. With the recent advent of tools and services (event aggregators, for example) which would benefit greatly from structured location data, the need to specify detailed venue information has become apparent. This document describes a proposed method for addressing this need. Comments are solicited and should be addressed to ietf-calsify@osafoundation.org and/or the authors. Note: This document depends on RFC2445bis, currently in draft status, and should not proceed without RFC2445bis. Norris & McCullough Expires February 2, 2008 [Page 2] Internet-Draft ical-venue August 2007 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 5 3. An Example . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Venue Identifier Parameter . . . . . . . . . . . . . . . . . . 8 5. Venue Component . . . . . . . . . . . . . . . . . . . . . . . 9 5.1. UID Property Use Within Venue Component . . . . . . . . . 10 5.2. Venue Name Property . . . . . . . . . . . . . . . . . . . 10 5.3. Description Property Use Within Venue Component . . . . . 11 5.4. Venue Street Address Property . . . . . . . . . . . . . . 11 5.5. Venue Extended Address Property . . . . . . . . . . . . . 11 5.6. Venue Locality Property . . . . . . . . . . . . . . . . . 12 5.7. Venue Region Property . . . . . . . . . . . . . . . . . . 12 5.8. Venue Country Property . . . . . . . . . . . . . . . . . . 13 5.9. Venue Postal Code Property . . . . . . . . . . . . . . . . 13 5.10. Telephone Property . . . . . . . . . . . . . . . . . . . . 14 5.11. Location Type Property . . . . . . . . . . . . . . . . . . 14 5.12. TZID Use Within Venue Component . . . . . . . . . . . . . 15 5.13. GEO Property Use Within Venue Component . . . . . . . . . 15 5.14. CATEGORIES Use Within Location Component . . . . . . . . . 15 5.15. URL Use Within Location Component . . . . . . . . . . . . 16 5.16. Related To Use Within Location Component . . . . . . . . . 16 5.17. Date/Time Created Use Within Location Component . . . . . 16 5.18. Date/Time Stamp Use Within Location Component . . . . . . 16 5.19. Last Modified Use Within Location Component . . . . . . . 16 5.20. Abbreviation Parameter . . . . . . . . . . . . . . . . . . 16 5.21. Type Parameter . . . . . . . . . . . . . . . . . . . . . . 16 5.22. Example . . . . . . . . . . . . . . . . . . . . . . . . . 17 6. Internationalization Considerations . . . . . . . . . . . . . 19 7. Security Considerations . . . . . . . . . . . . . . . . . . . 20 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 10.1. Normative References . . . . . . . . . . . . . . . . . . . 23 10.2. Informative References . . . . . . . . . . . . . . . . . . 23 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 24 A.1. Changes in -01 . . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25 Intellectual Property and Copyright Statements . . . . . . . . . . 26 Norris & McCullough Expires February 2, 2008 [Page 3] Internet-Draft ical-venue August 2007 1. Introduction This specification introduces a new iCalendar [RFC2445] component VVENUE to provide detailed venue information for an event. The currently existing iCalendar standard (RFC 2445), and its proposed successor (RFC 2445bis) provide only a simple text field ("LOCATION" property) for specifying the location where an event (or "TODO" item) will occur. This is inadequate for use cases where structured location information (e.g. address, region, country, postal code) is required or preferred, and limits widespread adoption of iCalendar in those settings. This specification is targeted at communicating detailed information about venues at which events occur; it is not intended to provide the level of location information necessary for resource scheduling. Norris & McCullough Expires February 2, 2008 [Page 4] Internet-Draft ical-venue August 2007 2. Notational Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. Norris & McCullough Expires February 2, 2008 [Page 5] Internet-Draft ical-venue August 2007 3. An Example To facilitate understanding the detailed descriptions below, here is an example iCalendar file including the proposed venue component. This example is for a Joe Bloggs concert occuring at The Venue in San Diego, CA. BEGIN:VCALENDAR PRODID:-//Example Co.//Example 2.0//EN VERSION:2.0 BEGIN:VTIMEZONE TZID:US/Pacific LAST-MODIFIED:20060110T171418Z BEGIN:STANDARD DTSTART:20051030T080000 TZOFFSETTO:-0700 TZOFFSETFROM:+0000 TZNAME:MST END:STANDARD BEGIN:DAYLIGHT DTSTART:20060402T020000 TZOFFSETTO:-0600 TZOFFSETFROM:-0700 TZNAME:MDT END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:E0-001-000233571-3@events.example.com LOCATION;VVENUE=V0-001-000153774-0@events.example.com:The Venu e\n1055 Fifth Avenue\nSan Diego, CA 92101 DTSTAMP:20060110T171344Z DTSTART;TZID=US/Pacific:20060717T200000 SUMMARY:Joe Bloggs in concert DTEND;TZID=US/Pacific:20060717T2300000 DESCRIPTION:Joe Bloggs plays everything from the old Pieman & Garfunkie stuff to his latest album. Not to be missed! END:VEVENT BEGIN:VVENUE VENUE-ID:V0-001-000153774-0@events.example.com NAME:The Venue DESCRIPTION: The Venues is a home for live music and southern-inspired cuisine in an environment celebrating the Afric an American cultural contributions of blues music and folk art. STREET-ADDRESS:1055 Fifth Avenue\nSuite 4 EXTENDED-ADDRESS:Stage 2 LOCALITY:San Diego Norris & McCullough Expires February 2, 2008 [Page 6] Internet-Draft ical-venue August 2007 REGION;ABBREV=CA:California COUNTRY;ABBREV=US;ABBREV=USA:United States POSTAL-CODE:92101 TZID=US/Pacific GEO:32.716220;-117.160156 URL;TYPE=Map:http://maps.example.com/maps?q=1055%20Fifth %20Avenue%2C%20San%20Diego%2C%20California%20&hl=en URL;TYPE=Event Listing:http://events.example.com/venues/ V0-001-000153774-0 URL;TYPE=Official Site:http://thevenue.com/venues/clubvenues /sandiego/ TEL;TYPE=Box Office:619.299.2583 CATEGORIES:music concert END:VVENUE END:VCALENDAR The "VVENUE" component works similarly to "VTIMEZONE". It is referenced by parameter from the "LOCATION" property of a "VEVENT". Norris & McCullough Expires February 2, 2008 [Page 7] Internet-Draft ical-venue August 2007 4. Venue Identifier Parameter Parameter Name: "VVENUE" Purpose: To specify the identifier for the venue definition for a venue component in the property value. Format Definition: venueparam = "VVENUE" "=" paramtext Description: The parameter MAY be specified on the "LOCATION" property when detailed information about the venue is available. Example: The following is an example of this property parameter as part of a LOCATION property in a VEVENT: LOCATION;VVENUE=1234@events.example.com:Novell\, Inc.\n1860 South Novell Place\nBuilding H\, Executive Briefing Center\nProvo\, Utah Norris & McCullough Expires February 2, 2008 [Page 8] Internet-Draft ical-venue August 2007 5. Venue Component Component Name: "VVENUE" Purpose: Provide a grouping of component properties that describe an event venue. Format Definition: A "VVENUE" calendar component is defined by the following notation: venuec = "BEGIN" ":" "VVENUE" CRLF venueprop "END" ":" "VVENUE" CRLF venueprop = *( ; the following are all REQUIRED, ; but MUST NOT occur more than once uid ; the following are optional, ; but MUST NOT occur more than once name / description / street-address / extended-address / locality / region / country / postal-code / tzid / geo / location-type / categories ; the following are optional, ; and MAY occur more than once tel / url ) Description: A "VVENUE" calendar component is a grouping of component properties that represent a venue where an event occurs. This extends the "LOCATION" property of "VEVENT" and "TODO" components, providing the ability to specify detailed information about the event venue. Example: The following is an example of the "VVENUE" calendar component used to represent the The Venue in San Diego, California. Norris & McCullough Expires February 2, 2008 [Page 9] Internet-Draft ical-venue August 2007 BEGIN:VVENUE VENUE-ID:V0-001-000153774-0@events.example.com NAME:The Venue DESCRIPTION: The Venue is a home for live music and southern-inspired cuisine in an environment celebrating the African American cultural contributions of blues music and folk art. STREET-ADDRESS:1055 Fifth Avenue\nSuite 4 EXTENDED-ADDRESS:Stage 2 LOCALITY:San Diego REGION;ABBREV=CA:California COUNTRY;ABBREV=US;ABBREV=USA:United States POSTAL-CODE:92101 TZID=US/Pacific GEO:32.716220;-117.160156 URL;TYPE=map:http://maps.example.com/maps?q=1055%20Fifth%20Avenue% 2C%20San%20Diego%2C%20California%20&hl=en URL;TYPE=Event Listing:http://events.example.com/venues/V0-001-00015 3774-0 URL;TYPE=Official Site:http://thevenue.com/venues/clubvenues/sandi ego/ TEL;TYPE=Box Office:619.299.2583 CATEGORIES:music concert END:VVENUE 5.1. UID Property Use Within Venue Component The use of the UID component within VVENUE is identical to that specified in RFC 2445 (iCalendar), extended simply to VVENUE. 5.2. Venue Name Property Property Name: "NAME" Purpose: This property specifies the name of a venue. Value Type: TEXT Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property SHOULD be specified in a "VVENUE" calendar component. Description: This is the commonly used name for the venue. Format Definition: This property is defined by the following notation: Norris & McCullough Expires February 2, 2008 [Page 10] Internet-Draft ical-venue August 2007 name = "NAME" ":" text CRLF Example: The following is an example of a venue identifier property: NAME:The Venue 5.3. Description Property Use Within Venue Component The use of the Description property within VVENUE is identical to that specified in RFC 2445 (iCalendar), extended simply to VVENUE. 5.4. Venue Street Address Property Property Name: "STREET-ADDRESS" Purpose: This property specifies the street address of a location. Value Type: TEXT Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property MAY be specified in a "VVENUE" calendar component. Description: This specifies the street address of a location. If the location requires a multiple-line address, they may be separated by an encoded newline "\n". Format Definition: street-address = "STREET-ADDRESS" ":" text CRLF Example: The following is an example of a location identifier property: STREET-ADDRESS:1055 Fifth Avenue\nSuite 4 5.5. Venue Extended Address Property Property Name: "EXTENDED-ADDRESS" Purpose: This property provides the opportunity to include extended address information for a location. Value Type: TEXT Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property MAY be specified in a "VVENUE" calendar Norris & McCullough Expires February 2, 2008 [Page 11] Internet-Draft ical-venue August 2007 component. Description: This property provides the opportunity to include extended address information for a location. This property may be used to give additional information about an address that is not usually considered part of the street address. If the location requires a multiple-line address, they may be separated by an encoded newline "\n". Format Definition: extended-address = "EXTENDED-ADDRESS" ":" text CRLF Example: The following is an example of a location identifier property: EXTENDED-ADDRESS:Conference Room B 5.6. Venue Locality Property Property Name: "LOCALITY" Purpose: This property specifies the locality in which a venue is found. Value Type: TEXT Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property MAY be specified in a "VVENUE" calendar component. Description: This specifies the city or locality of a venue. Format Definition: locality = "LOCALITY" ":" text CRLF Example: The following is an example of a locality property: LOCALITY:San Diego 5.7. Venue Region Property Property Name: "REGION" Purpose: This property specifies the region (state, province, canton, etc.) in which a location is found. Value Type: TEXT Norris & McCullough Expires February 2, 2008 [Page 12] Internet-Draft ical-venue August 2007 Property Parameters: Non-standard, including ABBREV property parameters can be specified on this property. Conformance: This property MAY be specified in a "VVENUE" calendar component. Description: This specifies the region (state, province, canton, etc.) of a location. Format Definition: region = "REGION" ":" text CRLF Example: The following is an example of a location identifier property: REGION;ABBREV=CA:California 5.8. Venue Country Property Property Name: "COUNTRY" Purpose: This property specifies the country in which a location is found. Value Type: TEXT Property Parameters: Non-standard, including ABBREV property parameters can be specified on this property. Conformance: This property MAY be specified in a "VVENUE" calendar component. Description: This specifies the country of a location. Format Definition: country = "COUNTRY" ":" text CRLF Example: The following is an example of a location identifier property: COUNTRY;ABBREV=US;ABBREV=USA:United States 5.9. Venue Postal Code Property Property Name: "POSTAL-CODE" Purpose: This property specifies the postal code for a location. Value Type: TEXT Norris & McCullough Expires February 2, 2008 [Page 13] Internet-Draft ical-venue August 2007 Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property MAY be specified in a "VVENUE" calendar component. Description: This specifies the postal code of a location. Format Definition: postalcode = "POSTAL-CODE" ":" text CRLF Example: The following is an example of a location identifier property: POSTAL-CODE:92101 5.10. Telephone Property Property Name: "TEL" Purpose: This property specifies a telephone number for a location. Value Type: TEXT Property Parameters: Non-standard property parameters, including the TYPE parameter, can be specified on this property. Conformance: This property MAY be specified in a "VVENUE" calendar component. Description: This specifies the telephone number of a location. Format Definition: telephone = "TEL" ":" text CRLF Example: The following is an example of a telephone property: TEL;TYPE=Box Office:619.299.2583 5.11. Location Type Property Property Name: "LOCATION-TYPE" Purpose: To specify the IANA location-type [RFC4589] designator for a VVENUE component. Format Definition: location-type = "LOCATION-TYPE" "=" text CRLF Description: The parameter MAY be specified on a "VVENUE" component Norris & McCullough Expires February 2, 2008 [Page 14] Internet-Draft ical-venue August 2007 when the IANA location-type designation is available. Example: The following is an example of this property: LOCATION-TYPE:club, bar, restaurant Although categories and location type tokens are perhaps similar, they serve rather different purposes. Location type tokens serve to categorize a VVENUE using a well-defined, finite list of possibilities (the IANA Location Type Registry). Categories on the other hand are user-provided and user defined and have both a richness and "messiness" that allows user-created taxonomies to arise and evolve. 5.12. TZID Use Within Venue Component Property Name: TZID Purpose: To specify the identifier for the time zone definition for a venue component. Description: The use of the TZID property within VVENUE is substantially similar to the use of the TZID parameter specified in RFC 2445 (iCalendar), extended to specify the time zone of a venue component. Where the TZID parameter specifies the identifier for the time zone definition for a time component, the TZID property conveys the same information for a venue component. An individual "VTIMEZONE" calendar component MUST be specified for each unique "TZID" parameter value specified in the iCalendar object. Time zone calendar components may be shared between venue components and other components. For instance, a venue component and an event component may both point to the same timezone component. 5.13. GEO Property Use Within Venue Component The use of the GEO property within VVENUE is identical to that specified in RFC 2445 (iCalendar), extended simply to VVENUE. 5.14. CATEGORIES Use Within Location Component The use of the CATEGORIES property within VVENUE is identical to that specified in RFC 2445 (iCalendar), extended simply to VVENUE. Norris & McCullough Expires February 2, 2008 [Page 15] Internet-Draft ical-venue August 2007 5.15. URL Use Within Location Component The use of the URL property within VVENUE is identical to that specified in RFC 2445 (iCalendar), extended simply to VVENUE. 5.16. Related To Use Within Location Component The use of the RELATED-TO property within VVENUE is identical to that specified in RFC 2445 (iCalendar), extended simply to VVENUE. 5.17. Date/Time Created Use Within Location Component The use of the CREATED property within VVENUE is identical to that specified in RFC 2445 (iCalendar), extended simply to VVENUE. 5.18. Date/Time Stamp Use Within Location Component The use of the DTSTAMP property within VVENUE is identical to that specified in RFC 2445 (iCalendar), extended simply to VVENUE. 5.19. Last Modified Use Within Location Component The use of the LAST-MODIFIED property within VVENUE is identical to that specified in RFC 2445 (iCalendar), extended simply to VVENUE. 5.20. Abbreviation Parameter Parameter Name: "ABBREV" Purpose: To specify an abbreviated version of a REGION or COUNTRY. Format Definition: abbreviation = "ABBREV" "=" paramtext CRLF Description: The parameter MAY be specified on the "REGION" and "COUNTRY" properties when abbreviated versions are available and may be useful. Example: The following is an example of this property parameter: COUNTRY;ABBREV=US;ABBREV=USA:United States 5.21. Type Parameter Parameter Name: "TYPE" Purpose: To specify a type string for a URL or TEL property. Format Definition: Norris & McCullough Expires February 2, 2008 [Page 16] Internet-Draft ical-venue August 2007 type = "TYPE" "=" paramtext CRLF Description: The parameter MAY be specified on the "URL" and "TEL" properties when information about the type of these resources is available and may be useful. For example, identifying the box office phone number, or fax number may be useful for phone numbers, or identifying a tickets URL, official site, or other URL types may be useful for URL property. Example: The following is an example of this property parameter: URL;TYPE=map:http://maps.example.com/ maps?q=1055%20Fifth%20Avenue%2C%20San%20Diego%2C%20California %20&hl=en 5.22. Example Here's an example of two related venues, one representing the venue at which an event occurs, and another representing a suggested parking facility. BEGIN:VVENUE VENUE-ID:V0-001-000153774-0@events.example.com NAME:The Venue DESCRIPTION: The Venue is a home for live music and southern-insp ired cuisine in an environment celebrating the African American cult ural contributions of blues music and folk art. In 1992, our company converted a historical house in Cambridge, Massachusetts into the o riginal The Venue. The original The Venue opened its door on Thanksgiving Day, 1992 feeding the homeless before opening to th e public. Our commitment to serving the community will always be a p riority. ROOM:Stage 2 ADDRESS:1055 Fifth Avenue\nSuite 4 LOCALITY:San Diego REGION;ABBREV=CA:California COUNTRY;ABBREV=US;ABBREV=USA:United States POSTAL-CODE:92101 TZID=US/Pacific GEO:32.716220;-117.160156 URL;TYPE=map:http://maps.example.com/maps?q=1055%20Fifth%20Avenue%2C%20 San%20Diego%2C%20California%20&hl=en URL;TYPE=Event Listing:http://events.example.com/venues/V0-001-00015 3774-0 URL;TYPE=Official Site:http://thevenue.com/venues/clubvenues/sand iego/ TEL;TYPE=Box Office:619.299.2583 CATEGORIES:music concert t the local Ace Parking lot. Norris & McCullough Expires February 2, 2008 [Page 17] Internet-Draft ical-venue August 2007 RELATED-TO;RELTYPE=CHILD;VENUE-ID=:V0-001-000041351-0@events.example.com END:VVENUE BEGIN:VVENUE VENUE-ID:V0-001-000041351-0@events.example.com NAME:Ace Parking Fifth Street DESCRIPTION: Public parking lot on the corner of Fifth and A. ROOM:Stage 2 ADDRESS:1042 Fifth Avenue\nSuite 4 LOCALITY:San Diego REGION;ABBREV=CA:California COUNTRY;ABBREV=US;ABBREV=USA:United States POSTAL-CODE:92101 TZID=US/Pacific GEO:32.716224;-117.160167 URL;TYPE=map:http://maps.example.com/maps?q=1042%20Fifth%20Avenue%2C%20 San%20Diego%2C%20California%20&hl=en URL;TYPE=Event Listing:http://events.example.com/venues/V0-001-00001 4351-0 CATEGORIES:parking RELATED-TO;RELTYPE=PARENT;VENUE-ID=:V0-001-000153774-0@events.example.co m END:VVENUE Norris & McCullough Expires February 2, 2008 [Page 18] Internet-Draft ical-venue August 2007 6. Internationalization Considerations This draft proposes changes to the iCalendar format (RFC 2445) and the internationationalization issues are the same as in the larger iCalendar context. Norris & McCullough Expires February 2, 2008 [Page 19] Internet-Draft ical-venue August 2007 7. Security Considerations This draft proposes changes to the iCalendar format (RFC 2445) and the security issues are the same as in the larger iCalendar context. Norris & McCullough Expires February 2, 2008 [Page 20] Internet-Draft ical-venue August 2007 8. IANA Considerations TBD Norris & McCullough Expires February 2, 2008 [Page 21] Internet-Draft ical-venue August 2007 9. Acknowledgements The editors of this document would like to thank the Calendaring and Scheduling Consortium (CalConnect) for advice with this specification, and specifically thanks to Cyrus Daboo and Lisa Dusseault for their help and guidance. Norris & McCullough Expires February 2, 2008 [Page 22] Internet-Draft ical-venue August 2007 10. References 10.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997. [RFC2445] Dawson, F. and D. Stenerson, "Internet Calendaring and Scheduling Core Object Specification (iCalendar)", RFC 2445, November 1998. 10.2. Informative References [RFC2426] Dawson, F. and T. Howes, "vCard MIME Directory Profile", RFC 2426, September 1998. [RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and J. Polk, "Geopriv Requirements", RFC 3693, February 2004. [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object Format", RFC 4119, December 2005. [RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types Registry", RFC 4589, July 2006. Norris & McCullough Expires February 2, 2008 [Page 23] Internet-Draft ical-venue August 2007 Appendix A. Change History A.1. Changes in -01 1. Cleaned up VVENUE identifier. Still had a few instances where "UID" was used - now using "VENUE-ID" throughout. 2. Anonymized examples to remove references to specific companies and/or individuals. 3. Added note that timezone component must be provided to match any TZID property in a VVENUE. 4. Corrected "CITY" to "LOCALITY" in a few examples. 5. Removed references to NOTES in examples. 6. Change of one author's address. 7. Mailing list changed to ietf-calsify@osafoundation.org. 8. Corrected inconsistent use of POSTAL-CODE in examples. 9. Shuffled section order to group like items. 10. Corrected incorrected referenced RFC number. Norris & McCullough Expires February 2, 2008 [Page 24] Internet-Draft ical-venue August 2007 Authors' Addresses Charles Norris Eventful, Inc. 9171 Towne Centre Drive Suite 180 San Diego, CA 92131 US Email: chuck@eventful.com Jeff McCullough University of California, Berkeley 2195 Hearst 2nd Floor Berkeley, CA 94720-3808 US Email: jeffmc@berkeley.edu Norris & McCullough Expires February 2, 2008 [Page 25] Internet-Draft ical-venue August 2007 Full Copyright Statement Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Norris & McCullough Expires February 2, 2008 [Page 26]