Maintenance Notification Improvements Using iCalendar
draft-gunter-calext-maintenance-notifications-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Ryan Gunter | ||
Last updated | 2020-01-04 (Latest revision 2019-07-03) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document proposes a maintenance notification convention that requires the use an iCalendar file augmented with standarzied and machine parseable metadata. The metadata is constructed by using the x-name property in the iCalendar file in compliance with [RFC 5545] [RFC5545]. This specification substantially reduces automation efforts, and still provides easy calendaring for manual processing.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)