Network Working Group C. Norris
Internet-Draft Eventful
Expires: August 3, 2007 McCullough
UC Berkeley
January 30, 2007
Internet Calendaring and Scheduling Venue Component Specification
draft-norris-ical-venue-00
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 August 3, 2007.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Norris & McCullough Expires August 3, 2007 [Page 1]
Internet-Draft ical-venue January 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 the working group's
mailing list at ietf-ical-extensions@eventful.com and/or the authors.
Note: This document depends on RFC2445bis, currently in draft status,
and should not proceed without RFC2445bis.
Norris & McCullough Expires August 3, 2007 [Page 2]
Internet-Draft ical-venue January 2007
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. An Example . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Venue Identifier Parameter . . . . . . . . . . . . . . . . . . 7
4. Venue Component . . . . . . . . . . . . . . . . . . . . . . . 8
4.1. UID Property Use Within Venue Component . . . . . . . . . 9
4.2. Venue Name Property . . . . . . . . . . . . . . . . . . . 9
4.3. Description Property Use Within Venue Component . . . . . 10
4.4. Venue Street Address Property . . . . . . . . . . . . . . 10
4.5. Venue Extended Address Property . . . . . . . . . . . . . 10
4.6. Venue Locality Property . . . . . . . . . . . . . . . . . 11
4.7. Venue Region Property . . . . . . . . . . . . . . . . . . 11
4.8. Venue Country Property . . . . . . . . . . . . . . . . . . 12
4.9. Venue Postal Code Property . . . . . . . . . . . . . . . . 12
4.10. TZID Use Within Venue Component . . . . . . . . . . . . . 13
4.11. GEO Property Use Within Venue Component . . . . . . . . . 13
4.12. Telephone Property . . . . . . . . . . . . . . . . . . . . 13
4.13. Location Type Property . . . . . . . . . . . . . . . . . . 14
4.14. CATEGORIES Use Within Location Component . . . . . . . . . 14
4.15. URL Use Within Location Component . . . . . . . . . . . . 14
4.16. Related To Use Within Location Component . . . . . . . . . 15
4.17. Date/Time Created Use Within Location Component . . . . . 15
4.18. Date/Time Stamp Use Within Location Component . . . . . . 15
4.19. Last Modified Use Within Location Component . . . . . . . 15
4.20. Abbreviation Parameter . . . . . . . . . . . . . . . . . . 15
4.21. Type Parameter . . . . . . . . . . . . . . . . . . . . . . 15
4.22. Example . . . . . . . . . . . . . . . . . . . . . . . . . 16
5. Internationalization Considerations . . . . . . . . . . . . . 18
6. Security Considerations . . . . . . . . . . . . . . . . . . . 19
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
9.1. Normative References . . . . . . . . . . . . . . . . . . . 22
9.2. Informative References . . . . . . . . . . . . . . . . . . 22
Appendix A. Change Log (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . 23
A.1. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24
Intellectual Property and Copyright Statements . . . . . . . . . . 25
Norris & McCullough Expires August 3, 2007 [Page 3]
Internet-Draft ical-venue January 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) provides 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 August 3, 2007 [Page 4]
Internet-Draft ical-venue January 2007
2. 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:-//Eventful//Eventful 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
LOCATION;VVENUE=V0-001-000153774-0@eventful.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
Simon & Garfunkle stuff to his latest album. Not to be
missed!
END:VEVENT
BEGIN:VVENUE
UID:V0-001-000153774-0@eventful.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
REGION;ABBREV=CA:California
Norris & McCullough Expires August 3, 2007 [Page 5]
Internet-Draft ical-venue January 2007
COUNTRY;ABBREV=US;ABBREV=USA:United States
POSTAL-CODE:92101
TZID=US/Pacific
GEO:32.716220;-117.160156
URL;TYPE=Map:http://maps.google.com/maps?q=1055%20Fifth
%20Avenue%2C%20San%20Diego%2C%20California%20&hl=en
URL;TYPE=Eventful Listing:http://eventful.com/venues/
V0-001-000153774-0
URL;TYPE=Official Site:http://www.example.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 August 3, 2007 [Page 6]
Internet-Draft ical-venue January 2007
3. 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@eventful.com:Novell\, Inc.\n1860
South Novell Place\nBuilding H\, Executive Briefing Center\nProvo\,
Utah
Norris & McCullough Expires August 3, 2007 [Page 7]
Internet-Draft ical-venue January 2007
4. 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 August 3, 2007 [Page 8]
Internet-Draft ical-venue January 2007
BEGIN:VVENUE
UID:V0-001-000153774-0@eventful.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.google.com/maps?q=1055%20Fifth%20Avenue%
2C%20San%20Diego%2C%20California%20&hl=en
URL;TYPE=Eventful Listing:http://eventful.com/venues/V0-001-00015
3774-0
URL;TYPE=Official Site:http://www.example.com/venues/clubvenues/sandi
ego/
TEL;TYPE=Box Office:619.299.2583
CATEGORIES:music concert
END:VVENUE
4.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.
4.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 August 3, 2007 [Page 9]
Internet-Draft ical-venue January 2007
name = "NAME" ":" text CRLF
Example: The following is an example of a venue identifier property:
NAME:The Venue
4.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.
4.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
4.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 August 3, 2007 [Page 10]
Internet-Draft ical-venue January 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
4.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
4.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 August 3, 2007 [Page 11]
Internet-Draft ical-venue January 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
4.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
4.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 August 3, 2007 [Page 12]
Internet-Draft ical-venue January 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 = "POSTALCODE" ":" text CRLF
Example: The following is an example of a location identifier
property:
POSTALCODE:92101
4.10. 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.
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.
4.11. 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.
4.12. Telephone Property
Property Name: "TEL"
Purpose: This property specifies a telephone number for a location.
Value Type: TEXT
Norris & McCullough Expires August 3, 2007 [Page 13]
Internet-Draft ical-venue January 2007
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
4.13. 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
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.
4.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.
4.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.
Norris & McCullough Expires August 3, 2007 [Page 14]
Internet-Draft ical-venue January 2007
4.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.
4.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.
4.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.
4.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.
4.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
4.21. Type Parameter
Parameter Name: "TYPE"
Purpose: To specify a type string for a URL or TEL property.
Format Definition:
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
Norris & McCullough Expires August 3, 2007 [Page 15]
Internet-Draft ical-venue January 2007
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.google.com/
maps?q=1055%20Fifth%20Avenue%2C%20San%20Diego%2C%20California
%20&hl=en
4.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@eventful.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
CITY: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.google.com/maps?q=1055%20Fifth%20Avenue%2C%20
San%20Diego%2C%20California%20&hl=en
URL;TYPE=Eventful Listing:http://eventful.com/venues/V0-001-000153774-0
URL;TYPE=Official Site:http://www.example.com/venues/clubvenues/sandieg
o/
TEL;TYPE=Box Office:619.299.2583
CATEGORIES:music concert
NOTES:Limited free parking is around back. Paid parking is available a
t the local Ace Parking lot.
RELATED-TO;RELTYPE=CHILD;UID=:V0-001-00004135h1-0@eventful.com
END:VVENUE
BEGIN:VVENUE
VENUE-ID:V0-001-000041351-0@eventful.com
NAME:Ace Parking Fifth Street
Norris & McCullough Expires August 3, 2007 [Page 16]
Internet-Draft ical-venue January 2007
DESCRIPTION: Public parking lot on the corner of Fifth and A.
ROOM:Stage 2
ADDRESS:1042 Fifth Avenue\nSuite 4
CITY: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.google.com/maps?q=1042%20Fifth%20Avenue%2C%20
San%20Diego%2C%20California%20&hl=en
URL;TYPE=Eventful Listing:http://eventful.com/venues/V0-001-000014351-0
CATEGORIES:parking
NOTES:$2/hour, $15/day
RELATED-TO;RELTYPE=PARENT;UID=:V0-001-000153774-0@eventful.com
END:VVENUE
Norris & McCullough Expires August 3, 2007 [Page 17]
Internet-Draft ical-venue January 2007
5. 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 August 3, 2007 [Page 18]
Internet-Draft ical-venue January 2007
6. 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 August 3, 2007 [Page 19]
Internet-Draft ical-venue January 2007
7. IANA Considerations
TBD
Norris & McCullough Expires August 3, 2007 [Page 20]
Internet-Draft ical-venue January 2007
8. 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 August 3, 2007 [Page 21]
Internet-Draft ical-venue January 2007
9. References
9.1. Normative References
[RFC2445] Dawson, F. and D. Stenerson, "Internet Calendaring and
Scheduling Core Object Specification (iCalendar)",
RFC 2445, November 1998.
9.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 4119, July 2006.
Norris & McCullough Expires August 3, 2007 [Page 22]
Internet-Draft ical-venue January 2007
Appendix A. Change Log (to be removed by RFC Editor before publication)
A.1. Changes in -00
Placeholder
Norris & McCullough Expires August 3, 2007 [Page 23]
Internet-Draft ical-venue January 2007
Authors' Addresses
Charles Norris
Eventful, Inc.
9191 Towne Centre Drive
Suite 125
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 August 3, 2007 [Page 24]
Internet-Draft ical-venue January 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 August 3, 2007 [Page 25]