Maintenance Notification Improvements Using iCalendar
draft-gunter-calext-maintenance-notifications-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-03
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Calendaring Extensions                                    R. Gunter, Ed.
Internet-Draft                                                    Twitch
Intended status: Experimental                               July 3, 2019
Expires: January 4, 2020

         Maintenance Notification Improvements Using iCalendar
            draft-gunter-calext-maintenance-notifications-00

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on January 4, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Gunter                   Expires January 4, 2020                [Page 1]
Internet-Draft              Abbreviated Title                  July 2019

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Specification . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  iCalendar Object  . . . . . . . . . . . . . . . . . . . .   4
     2.3.  iCalendar Properties  . . . . . . . . . . . . . . . . . .   4
       2.3.1.  Method Calendar Property  . . . . . . . . . . . . . .   4
     2.4.  Event Component and Associated Properties . . . . . . . .   5
     2.5.  Descriptive Component Properties  . . . . . . . . . . . .   6
       2.5.1.  Provider  . . . . . . . . . . . . . . . . . . . . . .   6
       2.5.2.  Account . . . . . . . . . . . . . . . . . . . . . . .   7
       2.5.3.  Maintenance ID  . . . . . . . . . . . . . . . . . . .   8
       2.5.4.  Object ID . . . . . . . . . . . . . . . . . . . . . .   8
       2.5.5.  Impact  . . . . . . . . . . . . . . . . . . . . . . .  10
       2.5.6.  Status  . . . . . . . . . . . . . . . . . . . . . . .  11
   3.  Workflow  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     3.1.  Initial Maintenance Notification  . . . . . . . . . . . .  12
       3.1.1.  Example Provider  . . . . . . . . . . . . . . . . . .  12
       3.1.2.  Example Consumer  . . . . . . . . . . . . . . . . . .  13
     3.2.  Updated Maintenance Notification Window . . . . . . . . .  13
       3.2.1.  Example Provider  . . . . . . . . . . . . . . . . . .  14
       3.2.2.  Example Consumer  . . . . . . . . . . . . . . . . . .  14
     3.3.  Canceled Maintenance Notification Window  . . . . . . . .  14
       3.3.1.  Example Provider  . . . . . . . . . . . . . . . . . .  14
       3.3.2.  Example Consumer  . . . . . . . . . . . . . . . . . .  15
     3.4.  Open Maintenance Notification Window  . . . . . . . . . .  15
       3.4.1.  Example Provider  . . . . . . . . . . . . . . . . . .  15
       3.4.2.  Example Consumer  . . . . . . . . . . . . . . . . . .  16
     3.5.  Closed Maintenance Notification Window  . . . . . . . . .  16
       3.5.1.  Example Provider  . . . . . . . . . . . . . . . . . .  16
       3.5.2.  Example Consumer  . . . . . . . . . . . . . . . . . .  16
   4.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  17
     4.1.  Initial Maintenance Notification  . . . . . . . . . . . .  17
     4.2.  Updated Maintenance Notification  . . . . . . . . . . . .  17
     4.3.  Cancelled Maintenance Notification  . . . . . . . . . . .  18
     4.4.  Open Maintenance Notification . . . . . . . . . . . . . .  19
Show full document text