| < draft-ietf-calext-ical-relations-10.txt | draft-ietf-calext-ical-relations-11.txt > | |||
|---|---|---|---|---|
| Network Working Group M. Douglass | Network Working Group M. Douglass | |||
| Internet-Draft Bedework | Internet-Draft Bedework | |||
| Updates: 5545 (if approved) 27 February 2022 | Updates: 5545 (if approved) 22 March 2022 | |||
| Intended status: Standards Track | Intended status: Standards Track | |||
| Expires: 31 August 2022 | Expires: 23 September 2022 | |||
| Support for iCalendar Relationships | Support for iCalendar Relationships | |||
| draft-ietf-calext-ical-relations-10 | draft-ietf-calext-ical-relations-11 | |||
| Abstract | Abstract | |||
| This specification updates the iCalendar RELATED-TO property defined | This specification updates the iCalendar RELATED-TO property defined | |||
| in RFC5545 by adding new relation types and introduces new iCalendar | in RFC5545 by adding new relation types and introduces new iCalendar | |||
| properties LINK, CONCEPT and REFID to allow better linking and | properties LINK, CONCEPT and REFID to allow better linking and | |||
| grouping of iCalendar components and related data. | grouping of iCalendar components and related data. | |||
| Status of This Memo | Status of This Memo | |||
| skipping to change at page 1, line 34 ¶ | skipping to change at page 1, line 34 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on 31 August 2022. | This Internet-Draft will expire on 23 September 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2022 IETF Trust and the persons identified as the | Copyright (c) 2022 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents (https://trustee.ietf.org/ | Provisions Relating to IETF Documents (https://trustee.ietf.org/ | |||
| license-info) in effect on the date of publication of this document. | license-info) in effect on the date of publication of this document. | |||
| Please review these documents carefully, as they describe your rights | Please review these documents carefully, as they describe your rights | |||
| skipping to change at page 2, line 25 ¶ | skipping to change at page 2, line 25 ¶ | |||
| 3. Link Relation Types . . . . . . . . . . . . . . . . . . . . . 6 | 3. Link Relation Types . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 4. New temporal RELTYPE Parameter values . . . . . . . . . . . . 6 | 4. New temporal RELTYPE Parameter values . . . . . . . . . . . . 6 | |||
| 5. Additional New RELTYPE Parameter Values . . . . . . . . . . . 8 | 5. Additional New RELTYPE Parameter Values . . . . . . . . . . . 8 | |||
| 6. New Property Parameters . . . . . . . . . . . . . . . . . . . 8 | 6. New Property Parameters . . . . . . . . . . . . . . . . . . . 8 | |||
| 6.1. Link Relation . . . . . . . . . . . . . . . . . . . . . . 9 | 6.1. Link Relation . . . . . . . . . . . . . . . . . . . . . . 9 | |||
| 6.2. Gap . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 | 6.2. Gap . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 | |||
| 7. New Value Data Types . . . . . . . . . . . . . . . . . . . . 10 | 7. New Value Data Types . . . . . . . . . . . . . . . . . . . . 10 | |||
| 8. New Properties . . . . . . . . . . . . . . . . . . . . . . . 11 | 8. New Properties . . . . . . . . . . . . . . . . . . . . . . . 11 | |||
| 8.1. Concept . . . . . . . . . . . . . . . . . . . . . . . . . 11 | 8.1. Concept . . . . . . . . . . . . . . . . . . . . . . . . . 11 | |||
| 8.2. Link . . . . . . . . . . . . . . . . . . . . . . . . . . 12 | 8.2. Link . . . . . . . . . . . . . . . . . . . . . . . . . . 12 | |||
| 8.3. Refid . . . . . . . . . . . . . . . . . . . . . . . . . . 13 | 8.3. Refid . . . . . . . . . . . . . . . . . . . . . . . . . . 14 | |||
| 9. Updates to RFC 5545 . . . . . . . . . . . . . . . . . . . . . 14 | 9. Updates to RFC 5545 . . . . . . . . . . . . . . . . . . . . . 14 | |||
| 9.1. RELATED-TO . . . . . . . . . . . . . . . . . . . . . . . 14 | 9.1. RELATED-TO . . . . . . . . . . . . . . . . . . . . . . . 15 | |||
| 10. Security Considerations . . . . . . . . . . . . . . . . . . . 17 | 10. Security Considerations . . . . . . . . . . . . . . . . . . . 17 | |||
| 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 | 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 | |||
| 11.1. iCalendar Property Registrations . . . . . . . . . . . . 17 | 11.1. iCalendar Property Registrations . . . . . . . . . . . . 17 | |||
| 11.2. iCalendar Property Parameter Registrations . . . . . . . 18 | 11.2. iCalendar Property Parameter Registrations . . . . . . . 18 | |||
| 11.3. iCalendar Value Data Type Registrations . . . . . . . . 18 | 11.3. iCalendar Value Data Type Registrations . . . . . . . . 18 | |||
| 11.4. iCalendar RELTYPE Value Registrations . . . . . . . . . 18 | 11.4. iCalendar RELTYPE Value Registrations . . . . . . . . . 19 | |||
| 11.5. New Reference Type Registration . . . . . . . . . . . . 19 | 11.5. New Reference Type Registration . . . . . . . . . . . . 19 | |||
| 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 | 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 | |||
| 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 | 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 | |||
| 13.1. Informative References . . . . . . . . . . . . . . . . . 20 | 13.1. Informative References . . . . . . . . . . . . . . . . . 20 | |||
| 13.2. Normative References . . . . . . . . . . . . . . . . . . 20 | 13.2. Normative References . . . . . . . . . . . . . . . . . . 20 | |||
| Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 21 | Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 21 | |||
| 1. Introduction | 1. Introduction | |||
| iCalendar entities defined in [RFC5545] often need to be related to | iCalendar entities defined in [RFC5545] often need to be related to | |||
| each other or to associated meta-data. The specifications below | each other or to associated meta-data. The specifications below | |||
| support relationships of the following forms: | support relationships of the following forms: | |||
| skipping to change at page 9, line 28 ¶ | skipping to change at page 9, line 28 ¶ | |||
| Description: This parameter MUST be specified on all LINK | Description: This parameter MUST be specified on all LINK | |||
| properties, and defines the type of reference. This allows | properties, and defines the type of reference. This allows | |||
| programs consuming this data to automatically scan for references | programs consuming this data to automatically scan for references | |||
| they support. There is no default relation type. | they support. There is no default relation type. | |||
| In addition to the value defined here any link relation in the | In addition to the value defined here any link relation in the | |||
| link registry established by [RFC8288], or new link relations, may | link registry established by [RFC8288], or new link relations, may | |||
| be used. | be used. | |||
| It is expected that link relation types seeing significant usage | ||||
| in calendaring will have the calendaring usage described in an | ||||
| RFC. | ||||
| LINKREL=SOURCE: identifies the source of the event information. | LINKREL=SOURCE: identifies the source of the event information. | |||
| Registration: These relation types are registered in [RFC8288] | Registration: These relation types are registered in [RFC8288] | |||
| 6.2. Gap | 6.2. Gap | |||
| Parameter name: GAP | Parameter name: GAP | |||
| Purpose: To specify the length of the gap, positive or negative, | Purpose: To specify the length of the gap, positive or negative, | |||
| between two components with a temporal relationship. | between two components with a temporal relationship. | |||
| End of changes. 9 change blocks. | ||||
| 8 lines changed or deleted | 12 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||