idnits 2.17.1 draft-norris-ical-venue-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 726. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 737. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 744. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 750. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 190: '...n: The parameter MAY be specified on t...' RFC 2119 keyword, line 215: '... ; the following are all REQUIRED,...' RFC 2119 keyword, line 216: '... ; but MUST NOT occur more t...' RFC 2119 keyword, line 221: '... ; but MUST NOT occur more t...' RFC 2119 keyword, line 228: '... ; and MAY occur more than o...' (11 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 30, 2007) is 6295 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2426' is defined on line 674, but no explicit reference was found in the text == Unused Reference: 'RFC3693' is defined on line 677, but no explicit reference was found in the text == Unused Reference: 'RFC4119' is defined on line 680, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2445 (Obsoleted by RFC 5545) -- Obsolete informational reference (is this intentional?): RFC 2426 (Obsoleted by RFC 6350) -- Duplicate reference: RFC4119, mentioned in 'RFC4589', was also mentioned in 'RFC4119'. Summary: 3 errors (**), 0 flaws (~~), 5 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group C. Norris 3 Internet-Draft Eventful 4 Expires: August 3, 2007 McCullough 5 UC Berkeley 6 January 30, 2007 8 Internet Calendaring and Scheduling Venue Component Specification 9 draft-norris-ical-venue-00 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on August 3, 2007. 36 Copyright Notice 38 Copyright (C) The IETF Trust (2007). 40 Abstract 42 The currently existing iCalendar standard (RFC 2445) provides only a 43 simple text field ("LOCATION" property) for specifying the location 44 where an event (or "TODO" item) will occur. While this may be 45 adequate for human readers, it is difficult for automated systems to 46 make use of. With the recent advent of tools and services (event 47 aggregators, for example) which would benefit greatly from structured 48 location data, the need to specify detailed venue information has 49 become apparent. This document describes a proposed method for 50 addressing this need. 52 Comments are solicited and should be addressed to the working group's 53 mailing list at ietf-ical-extensions@eventful.com and/or the authors. 55 Note: This document depends on RFC2445bis, currently in draft status, 56 and should not proceed without RFC2445bis. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 2. An Example . . . . . . . . . . . . . . . . . . . . . . . . . . 5 62 3. Venue Identifier Parameter . . . . . . . . . . . . . . . . . . 7 63 4. Venue Component . . . . . . . . . . . . . . . . . . . . . . . 8 64 4.1. UID Property Use Within Venue Component . . . . . . . . . 9 65 4.2. Venue Name Property . . . . . . . . . . . . . . . . . . . 9 66 4.3. Description Property Use Within Venue Component . . . . . 10 67 4.4. Venue Street Address Property . . . . . . . . . . . . . . 10 68 4.5. Venue Extended Address Property . . . . . . . . . . . . . 10 69 4.6. Venue Locality Property . . . . . . . . . . . . . . . . . 11 70 4.7. Venue Region Property . . . . . . . . . . . . . . . . . . 11 71 4.8. Venue Country Property . . . . . . . . . . . . . . . . . . 12 72 4.9. Venue Postal Code Property . . . . . . . . . . . . . . . . 12 73 4.10. TZID Use Within Venue Component . . . . . . . . . . . . . 13 74 4.11. GEO Property Use Within Venue Component . . . . . . . . . 13 75 4.12. Telephone Property . . . . . . . . . . . . . . . . . . . . 13 76 4.13. Location Type Property . . . . . . . . . . . . . . . . . . 14 77 4.14. CATEGORIES Use Within Location Component . . . . . . . . . 14 78 4.15. URL Use Within Location Component . . . . . . . . . . . . 14 79 4.16. Related To Use Within Location Component . . . . . . . . . 15 80 4.17. Date/Time Created Use Within Location Component . . . . . 15 81 4.18. Date/Time Stamp Use Within Location Component . . . . . . 15 82 4.19. Last Modified Use Within Location Component . . . . . . . 15 83 4.20. Abbreviation Parameter . . . . . . . . . . . . . . . . . . 15 84 4.21. Type Parameter . . . . . . . . . . . . . . . . . . . . . . 15 85 4.22. Example . . . . . . . . . . . . . . . . . . . . . . . . . 16 86 5. Internationalization Considerations . . . . . . . . . . . . . 18 87 6. Security Considerations . . . . . . . . . . . . . . . . . . . 19 88 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 89 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21 90 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22 91 9.1. Normative References . . . . . . . . . . . . . . . . . . . 22 92 9.2. Informative References . . . . . . . . . . . . . . . . . . 22 93 Appendix A. Change Log (to be removed by RFC Editor before 94 publication) . . . . . . . . . . . . . . . . . . . . 23 95 A.1. Changes in -00 . . . . . . . . . . . . . . . . . . . . . . 23 96 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24 97 Intellectual Property and Copyright Statements . . . . . . . . . . 25 99 1. Introduction 101 This specification introduces a new iCalendar [RFC2445] component 102 VVENUE to provide detailed venue information for an event. The 103 currently existing iCalendar standard (RFC 2445) provides only a 104 simple text field ("LOCATION" property) for specifying the location 105 where an event (or "TODO" item) will occur. This is inadequate for 106 use cases where structured location information (e.g. address, 107 region, country, postal code) is required or preferred, and limits 108 widespread adoption of iCalendar in those settings. 110 This specification is targeted at communicating detailed information 111 about venues at which events occur; it is not intended to provide the 112 level of location information necessary for resource scheduling. 114 2. An Example 116 To facilitate understanding the detailed descriptions below, here is 117 an example iCalendar file including the proposed venue component. 118 This example is for a Joe Bloggs concert occuring at The Venue in San 119 Diego, CA. 121 BEGIN:VCALENDAR 122 PRODID:-//Eventful//Eventful 2.0//EN 123 VERSION:2.0 124 BEGIN:VTIMEZONE 125 TZID:US/Pacific 126 LAST-MODIFIED:20060110T171418Z 127 BEGIN:STANDARD 128 DTSTART:20051030T080000 129 TZOFFSETTO:-0700 130 TZOFFSETFROM:+0000 131 TZNAME:MST 132 END:STANDARD 133 BEGIN:DAYLIGHT 134 DTSTART:20060402T020000 135 TZOFFSETTO:-0600 136 TZOFFSETFROM:-0700 137 TZNAME:MDT 138 END:DAYLIGHT 139 END:VTIMEZONE 140 BEGIN:VEVENT 141 LOCATION;VVENUE=V0-001-000153774-0@eventful.com:The Venu 142 e\n1055 Fifth Avenue\nSan Diego, CA 92101 143 DTSTAMP:20060110T171344Z 144 DTSTART;TZID=US/Pacific:20060717T200000 145 SUMMARY:Joe Bloggs in concert 146 DTEND;TZID=US/Pacific:20060717T2300000 147 DESCRIPTION:Joe Bloggs plays everything from the old 148 Simon & Garfunkle stuff to his latest album. Not to be 149 missed! 150 END:VEVENT 151 BEGIN:VVENUE 152 UID:V0-001-000153774-0@eventful.com 153 NAME:The Venue 154 DESCRIPTION: The Venues is a home for live music and 155 southern-inspired cuisine in an environment celebrating 156 the Afric an American cultural contributions of blues 157 music and folk art. 158 STREET-ADDRESS:1055 Fifth Avenue\nSuite 4 159 EXTENDED-ADDRESS:Stage 2 160 LOCALITY:San Diego 161 REGION;ABBREV=CA:California 162 COUNTRY;ABBREV=US;ABBREV=USA:United States 163 POSTAL-CODE:92101 164 TZID=US/Pacific 165 GEO:32.716220;-117.160156 166 URL;TYPE=Map:http://maps.google.com/maps?q=1055%20Fifth 167 %20Avenue%2C%20San%20Diego%2C%20California%20&hl=en 168 URL;TYPE=Eventful Listing:http://eventful.com/venues/ 169 V0-001-000153774-0 170 URL;TYPE=Official Site:http://www.example.com/venues/clubvenues 171 /sandiego/ 172 TEL;TYPE=Box Office:619.299.2583 173 CATEGORIES:music concert 174 END:VVENUE 175 END:VCALENDAR 177 The "VVENUE" component works similarly to "VTIMEZONE". It is 178 referenced by parameter from the "LOCATION" property of a "VEVENT". 180 3. Venue Identifier Parameter 182 Parameter Name: "VVENUE" 184 Purpose: To specify the identifier for the venue definition for a 185 venue component in the property value. 187 Format Definition: 188 venueparam = "VVENUE" "=" paramtext 190 Description: The parameter MAY be specified on the "LOCATION" 191 property when detailed information about the venue is available. 193 Example: The following is an example of this property parameter as 194 part of a LOCATION property in a VEVENT: 196 LOCATION;VVENUE=1234@eventful.com:Novell\, Inc.\n1860 197 South Novell Place\nBuilding H\, Executive Briefing Center\nProvo\, 198 Utah 200 4. Venue Component 202 Component Name: "VVENUE" 204 Purpose: Provide a grouping of component properties that describe an 205 event venue. 207 Format Definition: A "VVENUE" calendar component is defined by the 208 following notation: 209 venuec = "BEGIN" ":" "VVENUE" CRLF 210 venueprop 211 "END" ":" "VVENUE" CRLF 213 venueprop = *( 215 ; the following are all REQUIRED, 216 ; but MUST NOT occur more than once 218 uid 220 ; the following are optional, 221 ; but MUST NOT occur more than once 223 name / description / street-address / extended-address / 224 locality / region / country / postal-code / tzid / geo / 225 location-type / categories 227 ; the following are optional, 228 ; and MAY occur more than once 230 tel / url 231 ) 233 Description: A "VVENUE" calendar component is a grouping of component 234 properties that represent a venue where an event occurs. This 235 extends the "LOCATION" property of "VEVENT" and "TODO" components, 236 providing the ability to specify detailed information about the event 237 venue. 239 Example: The following is an example of the "VVENUE" calendar 240 component used to represent the The Venue in San Diego, California. 242 BEGIN:VVENUE 243 UID:V0-001-000153774-0@eventful.com 244 NAME:The Venue 245 DESCRIPTION: The Venue is a home for live music 246 and southern-inspired cuisine in an environment celebrating the 247 African American cultural contributions of blues music and folk 248 art. 249 STREET-ADDRESS:1055 Fifth Avenue\nSuite 4 250 EXTENDED-ADDRESS:Stage 2 251 LOCALITY:San Diego 252 REGION;ABBREV=CA:California 253 COUNTRY;ABBREV=US;ABBREV=USA:United States 254 POSTAL-CODE:92101 255 TZID=US/Pacific 256 GEO:32.716220;-117.160156 257 URL;TYPE=map:http://maps.google.com/maps?q=1055%20Fifth%20Avenue% 258 2C%20San%20Diego%2C%20California%20&hl=en 259 URL;TYPE=Eventful Listing:http://eventful.com/venues/V0-001-00015 260 3774-0 261 URL;TYPE=Official Site:http://www.example.com/venues/clubvenues/sandi 262 ego/ 263 TEL;TYPE=Box Office:619.299.2583 264 CATEGORIES:music concert 265 END:VVENUE 267 4.1. UID Property Use Within Venue Component 269 The use of the UID component within VVENUE is identical to that 270 specified in RFC 2445 (iCalendar), extended simply to VVENUE. 272 4.2. Venue Name Property 274 Property Name: "NAME" 276 Purpose: This property specifies the name of a venue. 278 Value Type: TEXT 280 Property Parameters: Non-standard property parameters can be 281 specified on this property. 283 Conformance: This property SHOULD be specified in a "VVENUE" calendar 284 component. 286 Description: This is the commonly used name for the venue. 288 Format Definition: This property is defined by the following 289 notation: 291 name = "NAME" ":" text CRLF 293 Example: The following is an example of a venue identifier property: 294 NAME:The Venue 296 4.3. Description Property Use Within Venue Component 298 The use of the Description property within VVENUE is identical to 299 that specified in RFC 2445 (iCalendar), extended simply to VVENUE. 301 4.4. Venue Street Address Property 303 Property Name: "STREET-ADDRESS" 305 Purpose: This property specifies the street address of a location. 307 Value Type: TEXT 309 Property Parameters: Non-standard property parameters can be 310 specified on this property. 312 Conformance: This property MAY be specified in a "VVENUE" calendar 313 component. 315 Description: This specifies the street address of a location. If the 316 location requires a multiple-line address, they may be separated by 317 an encoded newline "\n". 319 Format Definition: 320 street-address = "STREET-ADDRESS" ":" text CRLF 322 Example: The following is an example of a location identifier 323 property: 324 STREET-ADDRESS:1055 Fifth Avenue\nSuite 4 326 4.5. Venue Extended Address Property 328 Property Name: "EXTENDED-ADDRESS" 330 Purpose: This property provides the opportunity to include extended 331 address information for a location. 333 Value Type: TEXT 335 Property Parameters: Non-standard property parameters can be 336 specified on this property. 338 Conformance: This property MAY be specified in a "VVENUE" calendar 339 component. 341 Description: This property provides the opportunity to include 342 extended address information for a location. This property may be 343 used to give additional information about an address that is not 344 usually considered part of the street address. If the location 345 requires a multiple-line address, they may be separated by an encoded 346 newline "\n". 348 Format Definition: 349 extended-address = "EXTENDED-ADDRESS" ":" text CRLF 351 Example: The following is an example of a location identifier 352 property: 354 EXTENDED-ADDRESS:Conference Room B 356 4.6. Venue Locality Property 358 Property Name: "LOCALITY" 360 Purpose: This property specifies the locality in which a venue is 361 found. 363 Value Type: TEXT 365 Property Parameters: Non-standard property parameters can be 366 specified on this property. 368 Conformance: This property MAY be specified in a "VVENUE" calendar 369 component. 371 Description: This specifies the city or locality of a venue. 373 Format Definition: 374 locality = "LOCALITY" ":" text CRLF 376 Example: The following is an example of a locality property: 377 LOCALITY:San Diego 379 4.7. Venue Region Property 381 Property Name: "REGION" 383 Purpose: This property specifies the region (state, province, canton, 384 etc.) in which a location is found. 386 Value Type: TEXT 387 Property Parameters: Non-standard, including ABBREV property 388 parameters can be specified on this property. 390 Conformance: This property MAY be specified in a "VVENUE" calendar 391 component. 393 Description: This specifies the region (state, province, canton, 394 etc.) of a location. 396 Format Definition: 397 region = "REGION" ":" text CRLF 399 Example: The following is an example of a location identifier 400 property: 401 REGION;ABBREV=CA:California 403 4.8. Venue Country Property 405 Property Name: "COUNTRY" 407 Purpose: This property specifies the country in which a location is 408 found. 410 Value Type: TEXT 412 Property Parameters: Non-standard, including ABBREV property 413 parameters can be specified on this property. 415 Conformance: This property MAY be specified in a "VVENUE" calendar 416 component. 418 Description: This specifies the country of a location. 420 Format Definition: 421 country = "COUNTRY" ":" text CRLF 423 Example: The following is an example of a location identifier 424 property: 425 COUNTRY;ABBREV=US;ABBREV=USA:United States 427 4.9. Venue Postal Code Property 429 Property Name: "POSTAL-CODE" 431 Purpose: This property specifies the postal code for a location. 433 Value Type: TEXT 434 Property Parameters: Non-standard property parameters can be 435 specified on this property. 437 Conformance: This property MAY be specified in a "VVENUE" calendar 438 component. 440 Description: This specifies the postal code of a location. 442 Format Definition: 443 postalcode = "POSTALCODE" ":" text CRLF 445 Example: The following is an example of a location identifier 446 property: 447 POSTALCODE:92101 449 4.10. TZID Use Within Venue Component 451 Property Name: TZID 453 Purpose: To specify the identifier for the time zone definition for a 454 venue component. 456 Description: The use of the TZID property within VVENUE is 457 substantially similar to the use of the TZID parameter specified in 458 RFC 2445 (iCalendar), extended to specify the time zone of a venue 459 component. 461 Where the TZID parameter specifies the identifier for the time zone 462 definition for a time component, the TZID property conveys the same 463 information for a venue component. 465 Time zone calendar components may be shared between venue components 466 and other components. For instance, a venue component and an event 467 component may both point to the same timezone component. 469 4.11. GEO Property Use Within Venue Component 471 The use of the GEO property within VVENUE is identical to that 472 specified in RFC 2445 (iCalendar), extended simply to VVENUE. 474 4.12. Telephone Property 476 Property Name: "TEL" 478 Purpose: This property specifies a telephone number for a location. 480 Value Type: TEXT 481 Property Parameters: Non-standard property parameters, including the 482 TYPE parameter, can be specified on this property. 484 Conformance: This property MAY be specified in a "VVENUE" calendar 485 component. 487 Description: This specifies the telephone number of a location. 489 Format Definition: 490 telephone = "TEL" ":" text CRLF 492 Example: The following is an example of a telephone property: 493 TEL;TYPE=Box Office:619.299.2583 495 4.13. Location Type Property 497 Property Name: "LOCATION-TYPE" 499 Purpose: To specify the IANA location-type [RFC4589] designator for a 500 VVENUE component. 502 Format Definition: 503 location-type = "LOCATION-TYPE" "=" text CRLF 505 Description: The parameter MAY be specified on a "VVENUE" component 506 when the IANA location-type designation is available. 508 Example: The following is an example of this property: 509 LOCATION-TYPE:club, bar, restaurant 511 Although categories and location type tokens are perhaps similar, 512 they serve rather different purposes. Location type tokens serve to 513 categorize a VVENUE using a well-defined, finite list of 514 possibilities (the IANA Location Type Registry). Categories on the 515 other hand are user-provided and user defined and have both a 516 richness and "messiness" that allows user-created taxonomies to arise 517 and evolve. 519 4.14. CATEGORIES Use Within Location Component 521 The use of the CATEGORIES property within VVENUE is identical to that 522 specified in RFC 2445 (iCalendar), extended simply to VVENUE. 524 4.15. URL Use Within Location Component 526 The use of the URL property within VVENUE is identical to that 527 specified in RFC 2445 (iCalendar), extended simply to VVENUE. 529 4.16. Related To Use Within Location Component 531 The use of the RELATED-TO property within VVENUE is identical to that 532 specified in RFC 2445 (iCalendar), extended simply to VVENUE. 534 4.17. Date/Time Created Use Within Location Component 536 The use of the CREATED property within VVENUE is identical to that 537 specified in RFC 2445 (iCalendar), extended simply to VVENUE. 539 4.18. Date/Time Stamp Use Within Location Component 541 The use of the DTSTAMP property within VVENUE is identical to that 542 specified in RFC 2445 (iCalendar), extended simply to VVENUE. 544 4.19. Last Modified Use Within Location Component 546 The use of the LAST-MODIFIED property within VVENUE is identical to 547 that specified in RFC 2445 (iCalendar), extended simply to VVENUE. 549 4.20. Abbreviation Parameter 551 Parameter Name: "ABBREV" 553 Purpose: To specify an abbreviated version of a REGION or COUNTRY. 555 Format Definition: 556 abbreviation = "ABBREV" "=" paramtext CRLF 558 Description: The parameter MAY be specified on the "REGION" and 559 "COUNTRY" properties when abbreviated versions are available and may 560 be useful. 562 Example: The following is an example of this property parameter: 563 COUNTRY;ABBREV=US;ABBREV=USA:United States 565 4.21. Type Parameter 567 Parameter Name: "TYPE" 569 Purpose: To specify a type string for a URL or TEL property. 571 Format Definition: 572 type = "TYPE" "=" paramtext CRLF 574 Description: The parameter MAY be specified on the "URL" and "TEL" 575 properties when information about the type of these resources is 576 available and may be useful. For example, identifying the box office 577 phone number, or fax number may be useful for phone numbers, or 578 identifying a tickets URL, official site, or other URL types may be 579 useful for URL property. 581 Example: The following is an example of this property parameter: 582 URL;TYPE=map:http://maps.google.com/ 583 maps?q=1055%20Fifth%20Avenue%2C%20San%20Diego%2C%20California 584 %20&hl=en 586 4.22. Example 588 Here's an example of two related venues, one representing the venue 589 at which an event occurs, and another representing a suggested 590 parking facility. 592 BEGIN:VVENUE 593 VENUE-ID:V0-001-000153774-0@eventful.com 594 NAME:The Venue 595 DESCRIPTION: The Venue is a home for live music and southern-insp 596 ired cuisine in an environment celebrating the African American cult 597 ural contributions of blues music and folk art. In 1992, our company 598 converted a historical house in Cambridge, Massachusetts into the o 599 riginal The Venue. The original The Venue opened its door 600 on Thanksgiving Day, 1992 feeding the homeless before opening to th 601 e public. Our commitment to serving the community will always be a p 602 riority. 603 ROOM:Stage 2 604 ADDRESS:1055 Fifth Avenue\nSuite 4 605 CITY:San Diego 606 REGION;ABBREV=CA:California 607 COUNTRY;ABBREV=US;ABBREV=USA:United States 608 POSTAL-CODE:92101 609 TZID=US/Pacific 610 GEO:32.716220;-117.160156 611 URL;TYPE=map:http://maps.google.com/maps?q=1055%20Fifth%20Avenue%2C%20 612 San%20Diego%2C%20California%20&hl=en 613 URL;TYPE=Eventful Listing:http://eventful.com/venues/V0-001-000153774-0 614 URL;TYPE=Official Site:http://www.example.com/venues/clubvenues/sandieg 615 o/ 616 TEL;TYPE=Box Office:619.299.2583 617 CATEGORIES:music concert 618 NOTES:Limited free parking is around back. Paid parking is available a 619 t the local Ace Parking lot. 620 RELATED-TO;RELTYPE=CHILD;UID=:V0-001-00004135h1-0@eventful.com 621 END:VVENUE 622 BEGIN:VVENUE 623 VENUE-ID:V0-001-000041351-0@eventful.com 624 NAME:Ace Parking Fifth Street 625 DESCRIPTION: Public parking lot on the corner of Fifth and A. 626 ROOM:Stage 2 627 ADDRESS:1042 Fifth Avenue\nSuite 4 628 CITY:San Diego 629 REGION;ABBREV=CA:California 630 COUNTRY;ABBREV=US;ABBREV=USA:United States 631 POSTAL-CODE:92101 632 TZID=US/Pacific 633 GEO:32.716224;-117.160167 634 URL;TYPE=map:http://maps.google.com/maps?q=1042%20Fifth%20Avenue%2C%20 635 San%20Diego%2C%20California%20&hl=en 636 URL;TYPE=Eventful Listing:http://eventful.com/venues/V0-001-000014351-0 637 CATEGORIES:parking 638 NOTES:$2/hour, $15/day 639 RELATED-TO;RELTYPE=PARENT;UID=:V0-001-000153774-0@eventful.com 640 END:VVENUE 642 5. Internationalization Considerations 644 This draft proposes changes to the iCalendar format (RFC 2445) and 645 the internationationalization issues are the same as in the larger 646 iCalendar context. 648 6. Security Considerations 650 This draft proposes changes to the iCalendar format (RFC 2445) and 651 the security issues are the same as in the larger iCalendar context. 653 7. IANA Considerations 655 TBD 657 8. Acknowledgements 659 The editors of this document would like to thank the Calendaring and 660 Scheduling Consortium (CalConnect) for advice with this 661 specification, and specifically thanks to Cyrus Daboo and Lisa 662 Dusseault for their help and guidance. 664 9. References 666 9.1. Normative References 668 [RFC2445] Dawson, F. and D. Stenerson, "Internet Calendaring and 669 Scheduling Core Object Specification (iCalendar)", 670 RFC 2445, November 1998. 672 9.2. Informative References 674 [RFC2426] Dawson, F. and T. Howes, "vCard MIME Directory Profile", 675 RFC 2426, September 1998. 677 [RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and 678 J. Polk, "Geopriv Requirements", RFC 3693, February 2004. 680 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 681 Format", RFC 4119, December 2005. 683 [RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types 684 Registry", RFC 4119, July 2006. 686 Appendix A. Change Log (to be removed by RFC Editor before publication) 688 A.1. Changes in -00 690 Placeholder 692 Authors' Addresses 694 Charles Norris 695 Eventful, Inc. 696 9191 Towne Centre Drive 697 Suite 125 698 San Diego, CA 92131 699 US 701 Email: chuck@eventful.com 703 Jeff McCullough 704 University of California, Berkeley 705 2195 Hearst 706 2nd Floor 707 Berkeley, CA 94720-3808 708 US 710 Email: jeffmc@berkeley.edu 712 Full Copyright Statement 714 Copyright (C) The IETF Trust (2007). 716 This document is subject to the rights, licenses and restrictions 717 contained in BCP 78, and except as set forth therein, the authors 718 retain all their rights. 720 This document and the information contained herein are provided on an 721 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 722 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 723 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 724 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 725 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 726 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 728 Intellectual Property 730 The IETF takes no position regarding the validity or scope of any 731 Intellectual Property Rights or other rights that might be claimed to 732 pertain to the implementation or use of the technology described in 733 this document or the extent to which any license under such rights 734 might or might not be available; nor does it represent that it has 735 made any independent effort to identify any such rights. Information 736 on the procedures with respect to rights in RFC documents can be 737 found in BCP 78 and BCP 79. 739 Copies of IPR disclosures made to the IETF Secretariat and any 740 assurances of licenses to be made available, or the result of an 741 attempt made to obtain a general license or permission for the use of 742 such proprietary rights by implementers or users of this 743 specification can be obtained from the IETF on-line IPR repository at 744 http://www.ietf.org/ipr. 746 The IETF invites any interested party to bring to its attention any 747 copyrights, patents or patent applications, or other proprietary 748 rights that may cover technology that may be required to implement 749 this standard. Please address the information to the IETF at 750 ietf-ipr@ietf.org. 752 Acknowledgment 754 Funding for the RFC Editor function is provided by the IETF 755 Administrative Support Activity (IASA).