
From nobody Sun Jan  3 13:15:31 2021
Return-Path: <mikeadouglass@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69D8B3A1348 for <calsify@ietfa.amsl.com>; Sun,  3 Jan 2021 13:15:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.459
X-Spam-Level: 
X-Spam-Status: No, score=-0.459 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W7ZIWXLlcq_w for <calsify@ietfa.amsl.com>; Sun,  3 Jan 2021 13:15:26 -0800 (PST)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF2853A1347 for <calsify@ietf.org>; Sun,  3 Jan 2021 13:15:25 -0800 (PST)
Received: by mail-qt1-x830.google.com with SMTP id g24so17276808qtq.12 for <calsify@ietf.org>; Sun, 03 Jan 2021 13:15:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:from:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=yl39bL5XFTYULl0+gOcDvRrcYWPojaKGK7fxGS14zoA=; b=jtpgu7XMnBOR+/wTN5tXuO45qymgWqoQk5Esavx5/1DaXVZsv/d+DtoJE7gstlUN9I sONPYZvKl8is0/ZyWnmv5aXzYiLG1Ms/6jmp4g/ufpgbXsNdHMrgFnEZZ7oOxCcA9nNB Fwx6kFd8upC2ZyGUIjdldAfYaAhp7zIoZaRfJqzjMhddDQ2eiH66QW1bozOWpA+JpztT o9rP59cEn1Mr9lWjoaZXmkv8ugdCv0MY4At9LjOMHNP1H0qbj/I8aLfKoMbW8g5SNS91 AztbSKIaB0Caga9+zl5InnkiI94LRLEigHkbionkfyBCFLE5qPZnswMew+4jmNpIfgNc AFsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=yl39bL5XFTYULl0+gOcDvRrcYWPojaKGK7fxGS14zoA=; b=S8YyhnuvnYCEphsqWFRpbdedVS563L9cLExetkiF+nr3AhUFPQYuQmv6isDWJJ/RUV dN31ZmZsDROVtGVlvPWnwO0aDBmLX+N8MfVSSeWmjc7NW8b2rGbhbUYBu6wB1QlSS1DJ zy3Cmrr0f/yLMC4rP+1SEujLBRe+7T4HeHMafjvSVHMf7UnyyBQr13goWX8Ja3MxJSd6 +5kUqrMFL/f1vcm/ADagBwn1GyqlgNPa/AjhIkbzN89WRDfM3cBbKvnSuZKY9wOtc1iV x1ll3yERAYmRJNoWn4/0XPI9rKxoqvLxapbW5uuxm8NTN0IqHYJjQHV/x9aUzL90pciD aEFA==
X-Gm-Message-State: AOAM530M57v02CPCO897hJVwaeI/bQEdTZ6bPnN5WSOlbR9Az8ebBZQ2 oUK2ccsxbiGnZ8q2vvI8Ls5Qo2TeiSMw4w==
X-Google-Smtp-Source: ABdhPJxRGMJfNH5RMHWxIelOS6iYjwWZJO7XF5Nu+vwI5QFewWY39krq7Xp5q+VJqemT4vminxdWKw==
X-Received: by 2002:ac8:5d53:: with SMTP id g19mr68170564qtx.354.1609708524501;  Sun, 03 Jan 2021 13:15:24 -0800 (PST)
Received: from [192.168.1.151] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id 136sm36157141qkn.79.2021.01.03.13.15.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 03 Jan 2021 13:15:23 -0800 (PST)
From: Michael Douglass <mikeadouglass@gmail.com>
To: =?UTF-8?B?0JTQuNC70Y/QvSDQn9Cw0LvQsNGD0LfQvtCy?= <dilyan.palauzov@aegee.org>, calsify@ietf.org
References: <160287329801.13575.6476139980278266084@ietfa.amsl.com> <79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org> <9dc03462-7fd0-9fc1-faa1-33883a91a1c9@gmail.com>
Message-ID: <fd92c62f-596e-06df-3763-9e02635ed99a@gmail.com>
Date: Sun, 3 Jan 2021 16:15:22 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <9dc03462-7fd0-9fc1-faa1-33883a91a1c9@gmail.com>
Content-Type: multipart/alternative; boundary="------------45EF20E418EDADA277D6EF29"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/DkVMrlh-1Tr-2kEvMYQAo3b5Slo>
Subject: Re: [calsify] I-D Action: draft-ietf-calext-eventpub-extensions-16.txt
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jan 2021 21:15:29 -0000

This is a multi-part message in MIME format.
--------------45EF20E418EDADA277D6EF29
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

I'm about to submit an updated version 17

I made some changes both as a result of points raised here and also as a 
result of the call during the IETF 109 virtual meeting.

To summarize the main points:

There was concern expressed about relating start/end to a location. This 
was partially in response to jscalendar but I think as it stood it has 
too many problems. I'm removing that. I suspect in the jscalendar 
mapping we'll add back a relation but it will only be to allow 
round-tripping.

As discussed in the IETF 109 meeting I've changed the 
STRUCTURED-LOCATION property into a VLOCATION component. This allows 
that component to contain a STRCTURED-DATA property providing the 
information - possibly as a data-url to avoid downloads. It's 
essentially what I was trying to do with STRUCTURED-LOCATION. Similarly 
for STRUCTURED-RESOURCE. These changes also make it a closer match to 
what's happening with jscalendar.

Some PARTICIPANT examples were missing the UID

Additionally I've revised the abnf along the lines suggested by Barry 
Leiba for other drafts.

On 11/11/20 23:10, Michael Douglass wrote:
>
> Thank you for the time you put into this. I've attempted to cover all 
> of it below. Some points lead to further questions.
>
> On 10/17/20 16:42, Дилян Палаузов wrote:
>> Hello,
>>
>> 10.  Privacy Considerations
>> 10.1.  Tracking
>>
>>     Properties with a "URI" value type can expose their users to privacy
>>     leaks as any network access of the URI data can be tracked.  Clients
>>     SHOULD NOT automatically download data referenced by the URI without
>>     explicit instruction from users.
>>
>>
>> How about using data: uris, and fmttype parameter for the content-type,
>> that contain vCard, instead of having STRUCTURED-
>> LOCATION;VALUE=URI:https://example.example/abc.vcf?
>>
>>
>> What is the way to download the referenced vCard simultaneously with
>> the iCalendar, apart from the data: uri?  I have now a bright idea: the
>> STRUCTURED-DATA is changed from PROPERTY to COMPONENT with UID and is
>> unencoded (as far as possible) blob.  Then instead of
>> VALUE=URI:https:// one can write VALUE=URI:attachment: or
>> VALUE=URI:cid: (which is supposed to mean the URI within STRUCTURED-
>> DATA).  This basically unifies (base64 decoded) attachments and
>> structured-data.
>
> I'm not sure this gains us much. As a property there are a number of 
> ways to represent the value (including a data uri. And doesn't 
> uri::cid only work for mail?
>
> This has got me thinking about the other structured-xxx properties. 
> Making the location a component would make sense
>
> BEGIN:VLOCATION
>
> STRUCTURED-DATA:...
>
> DESCRIPTION:...
>
> UID:...
>
> END:VLOCATION
>
>
> makes a lot of sense. It also allows us to populate the location with 
> properties describe it. Which does take us almost back to where we 
> started with VVENUE. However, I've avoided trying to duplicate vcard 
> in the location - embedding it as structured data using a vcard (or 
> other contacts) schema seems to make much more sense.
>
>
>> 1.2.  Terms Used in This Document
>>    Event:  When the word 'event' is used (perhaps with a capitalised 'E'
>>    we are referring to gatherings, formal or informal.  For example a
>>    sports event, a party or a concert.
>>
>> The square braket is not closed.
> Done
>> What is the puropose of a PARTICIPANT in a VFREEBUSY component?  Can
>> you give a use-case?
>
> Much the same as elsewhere - to provide further information about the 
> attendee/organizer.
>
> I guess it might help to know the timezone or location of the 
> participants as that might affect what you report as free.
>
>> 6.2.  Calendar Address
>>        The CALENDAR-ADDRESS property if present will provide a cal-
>>        address.  If an ATTENDEE property has the same value the
>>        participant is considered schedulable.  The PARTICIPANT component
>>        can be used to contain additional meta-data related to the
>>        attendee.
>>
>>        If there is a related ATTENDEE proeprty then all parameters must
>>        be applied in that property.
>>
>>        This property is defined by the following notation:
>>           caladdressparam   = *(
>>                       (";" schedulestatusparam)
>>           )
>>
>>
>> proeprty ⇒ property
> Done
>> schedulestatusparam exists only for scheduled ATTENDEEs, probably only
>> for CalDAV-scheduled (as opposed to iMIP scheduled by the CUA)
>> attendees.  A PARTICIPANT/CALENDAR-ADDRESS is only scheduled, if there
>> is a corresponding ATTENDEE with the same value, in which case the
>> ATTENDEE gets the schedulestatusparam.  What does PARTICIPANT/CALENDAR-
>> ADDRESS do with schedulestatusparam?
>
> I can't remember now why I added all the attendee parameters to the 
> calendar address. I'm going to remove them.
>
>
>> 3.  Typed References
>>     Using STRUCTURED-LOCATION, rich information about multiple locations
>>     can be communicated, for example, address, region, country, postal
>>     code as well as other information such as parking availability.
>>
>> Can you provide an example, that communicates postal code, address and
>> region for a STRUCTURED-LOCATION?
> I meant in a vcard reference - I'll say so.
>> 5.3.  Order
>>
>>    orderparam = "ORDER" "=" integer ;Must be greater than or equal to 1
>>    
>> space after semi-colon
> Done
>> .
>>
>> 6.3.  Styled-Description
>>     Property Parameters:  IANA, non-standard, id, alternate text
>>        representation, format type, derived and language property
>>        parameters can be specified on this property.
>>
>>
>> https://www.iana.org/assignments/icalendar/icalendar.xhtml  does not
>> contain id property, neither does ABNF for styleddescparam.  It would
>> be good if the above Property Parameters are enumerated in the same
>> order, that is used in the subsequent Formal Definition for
>> styleddescparam.
>>
>> When RFC 5545 defines Property Parameters for a Property it puts AND
>> before the last value.  draft-ietf-calext-eventpub-extensions uses
>> three times OR, twice AND before the last Property Parameter in the
>> enumeration.  The usage of the Oxford comma is inconsistent.
> Fixed.
>> 6.4.  Structured-Location
>>
>>     Value type:  There is no default value type for this property.  The
>>        value type can be set to URI or TEXT.
>>
>> Please provide an example for VALUE=TEXT, that uses all parameters.  I
>> want to see how LABEL and the TEXT value differ.
>>        
>>     Description:
>>        When a LABEL parameter is supplied the language of the label
>>        SHOULD match that of the content and of the LANGUAGE parameter if
>>        present.
>>
>> My understanding is that, apart from NAME at VCALENDAR-level and
>> DESCRIPTION, but e.g. not for SUMMARY, any property/parameter can have
>> up to one LANGUAGE and there is no way to specify the same information
>> alternating in different languages in the same iCalendar object.  This
>> forces the user to read the information in whatever language it is
>> provided, or skip it based on visual scan, as there is no alternative.
>> LANGUAGE cannot be presented to the user.  Does anybody have use cases
>> for LANGUAGE in iCalendar?
>
> 5545 has this text (Section 3.1.2):
>
> Multi-valued properties MUST NOT be used to specify multiple language variants of
>     the same value.
>
> To my mind this does make the parameter pretty useless - however I 
> guess you can auto translate it - which might work a lot better now 
> but still be inadequate.
>
> Interestingly rfc7986 says for NAME and DESCRIPTION:
>
> This property can be specified multiple times in an iCalendar object.
> However, each property MUST represent the name of the calendar in a different language.
> I talked over the issue and we think this is possibly on oversight on 
> the part of Cyrus. We may need an errata.
>
> My wording as regards the LABEL parameter is only to ensure that the 
> label and content match.
>
>
>> If elaborating on LANGUAGE is done here, it shall specify that multiple
>> LABELs can be set, each for a different language.
> I'm not intending to introduce proper localization of iCalendar - at 
> least with this spec.
>
> Jscalendar introduces the idea of localization which I hope will do a 
> better job of handling languages than 5545 does. We probably need an 
> iCalendar extension for this so we can map them.
>
>
>>     Use of the related parameter:  This allows a location to define the
>>        start and/or end timezone of the associated component.  If a
>>        location is specified with a RELATED parameter then the affected
>>        DTSTART or DTEND properties MUST be specified as floating DATE-
>>        TIME value.
>>
>> STRUCTURED-LOCATION has no TZID property and can, but does not have to,
>> point to vCard URI that may, but has not to, contain TZ.  The draft
>> does not spell that the URI behing structloc can be a vCard.  How does
>> STRUCTURED-LOCATION substitute the time zone information, if DTSTART is
>> floating DATE-TIME?  The current way to specify different timezones for
>> a trip is to use different TZID parameters for DTSTART and DTEND.  Why
>> does the current way need to be changed?  Lets say a CUA(server)
>> implements eventspub and it uses floating times in DTSTART/DTEND with
>> STRUCTURED-LOCATION to signal that the timezones of the start/end are
>> different.  The CUA creates an iCalendar objects and sends it to a
>> different CUA.  The recipient implements RFC 5545 correctly.  It would
>> understand, that the start/end timezones are different, if TZID in
>> DTSTART/DTEND said so.  But the received DTSTART/DTEND are floating
>> time and the recipient does not understand STRUCTURED-LOCATION, or for
>> privacy reasons the recipient does not want to download the data
>> pointed by STRUCTURED-DATA;VALUE=URI: . Shall users disclose their IP
>> address to get the timezone of DTSTART from now on?
> I will probably drop this. I think it started off as an attempt to 
> align with jscalendar but it doesn't make much sense I think.
>> 6.6.  Structured-Data
>>     Value Type:  TEXT, BINARY or URI
>>
>> For the other properties is spelled explicitly, that there is no
>> default value type, but for this one and the other properties the same
>> is implied byhttps://tools.ietf.org/html/rfc7986#section-3  .
> Done
>> 5.4.  Schema
>> Example:
>>
>>       STRUCTURED-DATA;FMTTYPE=application/ld+json;
>>        SCHEMA="https://schema.org/FlightReservation";
>>        ENCODING=BASE64;VALUE=BINARY:ICAgIDxzY3JpcHQgdHlwZT0iYXBwb
>>
>> This is a very good idea.  ld+json provides means to communicate from
>> the CUA, over a publisher to search engines information about an event,
>> that is not mapped in iCalendar.  E.g. if there are fees.  Is it
>> possible to not-base64 encode json, and use something like
>>
>>       STRUCTURED-DATA;FMTTYPE=application/ld+json;VALUE=TEXT;
>>        SCHEMA="https://schema.org/FlightReservation":{"brum":"
>>        wups","zz":true}
>>        
>> ?
>>
>> schema.org can define e.g name (corresponding to SUMMARY).  SUMMARY can
>> be present only once (in one language).  STRUCTURED-DATA can be
>> specified many times, but has no LANGUAGE property.  What is the way to
>> write SUMMARY⇔NAME for an event in three languages and put this in a
>> single iCalendar object?
> That will happen with localization  - no way at the moment.
>> What does it mean to have many STRUCTURED-DATA?
> I guess I need to add text to specify that multiple STRUCTURED-DATA 
> MUST represent different information - NOT the same information in 
> different languages. However, woudl it make sense to have the same 
> information in a different representation - e.g. json and html? One 
> for processing and one for display.
>> Greetings
>>    Дилян
>>
>> В 11:34 -0700 на 16.10.2020 (пт),internet-drafts@ietf.org  написа:
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories.
>>> This draft is a work item of the Calendaring Extensions WG of the
>>> IETF.
>>>
>>>          Title           : Event Publishing Extensions to iCalendar
>>>          Author          : Michael Douglass
>>>          Filename        : draft-ietf-calext-eventpub-extensions-
>>> 16.txt
>>>          Pages           : 36
>>>          Date            : 2020-10-16
>>>
>>> Abstract:
>>>     This specification updates RFC5545 by introducing a number of new
>>>     iCalendar properties and components which are of particular use
>>> for
>>>     event publishers and in social networking.
>>>
>>>     This specification also defines a new STRUCTURED-DATA property for
>>>     iCalendar RFC5545 to allow for data that is directly pertinent to
>>> an
>>>     event or task to be included with the calendar data.
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/
>>>
>>> There are also htmlized versions available at:
>>> https://tools.ietf.org/html/draft-ietf-calext-eventpub-extensions-16
>>> https://datatracker.ietf.org/doc/html/draft-ietf-calext-eventpub-extensions-16
>>>
>>> A diff from the previous version is available at:
>>> https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-eventpub-extensions-16
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of
>>> submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>>
>>> _______________________________________________
>>> calsify mailing list
>>> calsify@ietf.org
>>> https://www.ietf.org/mailman/listinfo/calsify
>> _______________________________________________
>> calsify mailing list
>> calsify@ietf.org
>> https://www.ietf.org/mailman/listinfo/calsify

--------------45EF20E418EDADA277D6EF29
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>I'm about to submit an updated version 17<br>
    </p>
    <p>I made some changes both as a result of points raised here and
      also as a result of the call during the IETF 109 virtual meeting.</p>
    <p>To summarize the main points:</p>
    <p>There was concern expressed about relating start/end to a
      location. This was partially in response to jscalendar but I think
      as it stood it has too many problems. I'm removing that. I suspect
      in the jscalendar mapping we'll add back a relation but it will
      only be to allow round-tripping.</p>
    <p>As discussed in the IETF 109 meeting I've changed the
      STRUCTURED-LOCATION property into a VLOCATION component. This
      allows that component to contain a STRCTURED-DATA property
      providing the information - possibly as a data-url to avoid
      downloads. It's essentially what I was trying to do with
      STRUCTURED-LOCATION. Similarly for STRUCTURED-RESOURCE. These
      changes also make it a closer match to what's happening with
      jscalendar.</p>
    <p>Some PARTICIPANT examples were missing the UID<br>
    </p>
    <p>Additionally I've revised the abnf along the lines suggested by
      Barry Leiba for other drafts.<br>
    </p>
    <div class="moz-cite-prefix">On 11/11/20 23:10, Michael Douglass
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:9dc03462-7fd0-9fc1-faa1-33883a91a1c9@gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <p>Thank you for the time you put into this. I've attempted to
        cover all of it below. Some points lead to further questions.<br>
      </p>
      <div class="moz-cite-prefix">On 10/17/20 16:42, Дилян Палаузов
        wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
        <pre class="moz-quote-pre" wrap="">Hello,

10.  Privacy Considerations
10.1.  Tracking

   Properties with a "URI" value type can expose their users to privacy
   leaks as any network access of the URI data can be tracked.  Clients
   SHOULD NOT automatically download data referenced by the URI without
   explicit instruction from users.


How about using data: uris, and fmttype parameter for the content-type,
that contain vCard, instead of having STRUCTURED-
LOCATION;VALUE=URI:<a class="moz-txt-link-freetext" href="https://example.example/abc.vcf" moz-do-not-send="true">https://example.example/abc.vcf</a>?


What is the way to download the referenced vCard simultaneously with
the iCalendar, apart from the data: uri?  I have now a bright idea: the
STRUCTURED-DATA is changed from PROPERTY to COMPONENT with UID and is
unencoded (as far as possible) blob.  Then instead of
VALUE=URI:https:// one can write VALUE=URI:attachment: or
VALUE=URI:cid: (which is supposed to mean the URI within STRUCTURED-
DATA).  This basically unifies (base64 decoded) attachments and
structured-data.</pre>
      </blockquote>
      <p>I'm not sure this gains us much. As a property there are a
        number of ways to represent the value (including a data uri. And
        doesn't uri::cid only work for mail?</p>
      <p>This has got me thinking about the other structured-xxx
        properties. Making the location a component would make sense</p>
      <p>BEGIN:VLOCATION</p>
      <p>STRUCTURED-DATA:...</p>
      <p>DESCRIPTION:...</p>
      <p>UID:...<br>
      </p>
      <p>END:VLOCATION</p>
      <p><br>
      </p>
      <p>makes a lot of sense. It also allows us to populate the
        location with properties describe it. Which does take us almost
        back to where we started with VVENUE. However, I've avoided
        trying to duplicate vcard in the location - embedding it as
        structured data using a vcard (or other contacts) schema seems
        to make much more sense. <br>
      </p>
      <br>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
        <pre class="moz-quote-pre" wrap="">1.2.  Terms Used in This Document
  Event:  When the word 'event' is used (perhaps with a capitalised 'E'
  we are referring to gatherings, formal or informal.  For example a
  sports event, a party or a concert.

The square braket is not closed.</pre>
      </blockquote>
      Done<br>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
        <pre class="moz-quote-pre" wrap="">What is the puropose of a PARTICIPANT in a VFREEBUSY component?  Can
you give a use-case?</pre>
      </blockquote>
      <p>Much the same as elsewhere - to provide further information
        about the attendee/organizer. <br>
      </p>
      <p>I guess it might help to know the timezone or location of the
        participants as that might affect what you report as free.<br>
      </p>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
        <pre class="moz-quote-pre" wrap="">6.2.  Calendar Address
      The CALENDAR-ADDRESS property if present will provide a cal-
      address.  If an ATTENDEE property has the same value the
      participant is considered schedulable.  The PARTICIPANT component
      can be used to contain additional meta-data related to the
      attendee.

      If there is a related ATTENDEE proeprty then all parameters must
      be applied in that property.

      This property is defined by the following notation:
         caladdressparam   = *(
                     (";" schedulestatusparam)
         )


proeprty ⇒ property</pre>
      </blockquote>
      Done<br>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
        <pre class="moz-quote-pre" wrap="">schedulestatusparam exists only for scheduled ATTENDEEs, probably only
for CalDAV-scheduled (as opposed to iMIP scheduled by the CUA)
attendees.  A PARTICIPANT/CALENDAR-ADDRESS is only scheduled, if there
is a corresponding ATTENDEE with the same value, in which case the
ATTENDEE gets the schedulestatusparam.  What does PARTICIPANT/CALENDAR-
ADDRESS do with schedulestatusparam?</pre>
      </blockquote>
      <p>I can't remember now why I added all the attendee parameters to
        the calendar address. I'm going to remove them.<br>
      </p>
      <p><br>
      </p>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
        <pre class="moz-quote-pre" wrap="">
3.  Typed References
   Using STRUCTURED-LOCATION, rich information about multiple locations
   can be communicated, for example, address, region, country, postal
   code as well as other information such as parking availability.

Can you provide an example, that communicates postal code, address and
region for a STRUCTURED-LOCATION?</pre>
      </blockquote>
      I meant in a vcard reference - I'll say so.<br>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
        <pre class="moz-quote-pre" wrap="">5.3.  Order

  orderparam = "ORDER" "=" integer ;Must be greater than or equal to 1
  
space after semi-colon</pre>
      </blockquote>
      Done<br>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
        <pre class="moz-quote-pre" wrap="">.

6.3.  Styled-Description
   Property Parameters:  IANA, non-standard, id, alternate text
      representation, format type, derived and language property
      parameters can be specified on this property.


<a class="moz-txt-link-freetext" href="https://www.iana.org/assignments/icalendar/icalendar.xhtml" moz-do-not-send="true">https://www.iana.org/assignments/icalendar/icalendar.xhtml</a> does not
contain id property, neither does ABNF for styleddescparam.  It would
be good if the above Property Parameters are enumerated in the same
order, that is used in the subsequent Formal Definition for
styleddescparam.

When RFC 5545 defines Property Parameters for a Property it puts AND
before the last value.  draft-ietf-calext-eventpub-extensions uses
three times OR, twice AND before the last Property Parameter in the
enumeration.  The usage of the Oxford comma is inconsistent.</pre>
      </blockquote>
      Fixed.<br>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
        <pre class="moz-quote-pre" wrap="">6.4.  Structured-Location

   Value type:  There is no default value type for this property.  The
      value type can be set to URI or TEXT.

Please provide an example for VALUE=TEXT, that uses all parameters.  I
want to see how LABEL and the TEXT value differ.
      
   Description:
      When a LABEL parameter is supplied the language of the label
      SHOULD match that of the content and of the LANGUAGE parameter if
      present.

My understanding is that, apart from NAME at VCALENDAR-level and
DESCRIPTION, but e.g. not for SUMMARY, any property/parameter can have
up to one LANGUAGE and there is no way to specify the same information
alternating in different languages in the same iCalendar object.  This
forces the user to read the information in whatever language it is
provided, or skip it based on visual scan, as there is no alternative.
LANGUAGE cannot be presented to the user.  Does anybody have use cases
for LANGUAGE in iCalendar?</pre>
      </blockquote>
      <p>5545 has this text (Section 3.1.2):</p>
      <pre class="newpage">Multi-valued properties MUST NOT be used to specify multiple language variants of
   the same value.
</pre>
      <p>To my mind this does make the parameter pretty useless -
        however I guess you can auto translate it - which might work a
        lot better now but still be inadequate.</p>
      <p>Interestingly rfc7986 says for NAME and DESCRIPTION:</p>
      <pre class="newpage">This property can be specified multiple times in an iCalendar object.  
However, each property MUST represent the name of the calendar in a different language.</pre>
      I talked over the issue and we think this is possibly on oversight
      on the part of Cyrus. We may need an errata. <br>
      <p>My wording as regards the LABEL parameter is only to ensure
        that the label and content match.</p>
      <br>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
        <pre class="moz-quote-pre" wrap="">If elaborating on LANGUAGE is done here, it shall specify that multiple
LABELs can be set, each for a different language.
</pre>
      </blockquote>
      I'm not intending to introduce proper localization of iCalendar -
      at least with this spec. <br>
      <p>Jscalendar introduces the idea of localization which I hope
        will do a better job of handling languages than 5545 does. We
        probably need an iCalendar extension for this so we can map
        them. <br>
      </p>
      <br>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
      </blockquote>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
        <pre class="moz-quote-pre" wrap="">   Use of the related parameter:  This allows a location to define the
      start and/or end timezone of the associated component.  If a
      location is specified with a RELATED parameter then the affected
      DTSTART or DTEND properties MUST be specified as floating DATE-
      TIME value.

STRUCTURED-LOCATION has no TZID property and can, but does not have to,
point to vCard URI that may, but has not to, contain TZ.  The draft
does not spell that the URI behing structloc can be a vCard.  How does
STRUCTURED-LOCATION substitute the time zone information, if DTSTART is
floating DATE-TIME?  The current way to specify different timezones for
a trip is to use different TZID parameters for DTSTART and DTEND.  Why
does the current way need to be changed?  Lets say a CUA(server)
implements eventspub and it uses floating times in DTSTART/DTEND with
STRUCTURED-LOCATION to signal that the timezones of the start/end are
different.  The CUA creates an iCalendar objects and sends it to a
different CUA.  The recipient implements RFC 5545 correctly.  It would
understand, that the start/end timezones are different, if TZID in
DTSTART/DTEND said so.  But the received DTSTART/DTEND are floating
time and the recipient does not understand STRUCTURED-LOCATION, or for
privacy reasons the recipient does not want to download the data
pointed by STRUCTURED-DATA;VALUE=URI: . Shall users disclose their IP
address to get the timezone of DTSTART from now on?</pre>
      </blockquote>
      I will probably drop this. I think it started off as an attempt to
      align with jscalendar but it doesn't make much sense I think. <br>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
        <pre class="moz-quote-pre" wrap="">6.6.  Structured-Data
   Value Type:  TEXT, BINARY or URI

For the other properties is spelled explicitly, that there is no
default value type, but for this one and the other properties the same
is implied by <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/rfc7986#section-3" moz-do-not-send="true">https://tools.ietf.org/html/rfc7986#section-3</a> .</pre>
      </blockquote>
      Done<br>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
        <pre class="moz-quote-pre" wrap="">5.4.  Schema
Example:

     STRUCTURED-DATA;FMTTYPE=application/ld+json;
      SCHEMA=<a class="moz-txt-link-rfc2396E" href="https://schema.org/FlightReservation" moz-do-not-send="true">"https://schema.org/FlightReservation"</a>;
      ENCODING=BASE64;VALUE=BINARY:ICAgIDxzY3JpcHQgdHlwZT0iYXBwb

This is a very good idea.  ld+json provides means to communicate from
the CUA, over a publisher to search engines information about an event,
that is not mapped in iCalendar.  E.g. if there are fees.  Is it
possible to not-base64 encode json, and use something like

     STRUCTURED-DATA;FMTTYPE=application/ld+json;VALUE=TEXT;
      SCHEMA=<a class="moz-txt-link-rfc2396E" href="https://schema.org/FlightReservation" moz-do-not-send="true">"https://schema.org/FlightReservation"</a>:{"brum":"
      wups","zz":true}
      
?

schema.org can define e.g name (corresponding to SUMMARY).  SUMMARY can
be present only once (in one language).  STRUCTURED-DATA can be
specified many times, but has no LANGUAGE property.  What is the way to
write SUMMARY⇔NAME for an event in three languages and put this in a
single iCalendar object?</pre>
      </blockquote>
      That will happen with localization  - no way at the moment.<br>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
        <pre class="moz-quote-pre" wrap="">What does it mean to have many STRUCTURED-DATA?</pre>
      </blockquote>
      I guess I need to add text to specify that multiple
      STRUCTURED-DATA MUST represent different information - NOT the
      same information in different languages. However, woudl it make
      sense to have the same information in a different representation -
      e.g. json and html? One for processing and one for display. <br>
      <blockquote type="cite"
        cite="mid:79daa7a2a7518f9ab26060be943538f266ec92ea.camel@aegee.org">
        <pre class="moz-quote-pre" wrap="">Greetings
  Дилян

В 11:34 -0700 на 16.10.2020 (пт), <a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org" moz-do-not-send="true">internet-drafts@ietf.org</a> написа:
</pre>
        <blockquote type="cite">
          <pre class="moz-quote-pre" wrap="">A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Calendaring Extensions WG of the
IETF.

        Title           : Event Publishing Extensions to iCalendar
        Author          : Michael Douglass
        Filename        : draft-ietf-calext-eventpub-extensions-
16.txt
        Pages           : 36
        Date            : 2020-10-16

Abstract:
   This specification updates RFC5545 by introducing a number of new
   iCalendar properties and components which are of particular use
for
   event publishers and in social networking.

   This specification also defines a new STRUCTURED-DATA property for
   iCalendar RFC5545 to allow for data that is directly pertinent to
an
   event or task to be included with the calendar data.


The IETF datatracker status page for this draft is:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/" moz-do-not-send="true">https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/</a>

There are also htmlized versions available at:
<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-calext-eventpub-extensions-16" moz-do-not-send="true">https://tools.ietf.org/html/draft-ietf-calext-eventpub-extensions-16</a>
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-ietf-calext-eventpub-extensions-16" moz-do-not-send="true">https://datatracker.ietf.org/doc/html/draft-ietf-calext-eventpub-extensions-16</a>

A diff from the previous version is available at:
<a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-eventpub-extensions-16" moz-do-not-send="true">https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-eventpub-extensions-16</a>


Please note that it may take a couple of minutes from the time of
submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
<a class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/internet-drafts/" moz-do-not-send="true">ftp://ftp.ietf.org/internet-drafts/</a>


_______________________________________________
calsify mailing list
<a class="moz-txt-link-abbreviated" href="mailto:calsify@ietf.org" moz-do-not-send="true">calsify@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/calsify" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/calsify</a>
</pre>
        </blockquote>
        <pre class="moz-quote-pre" wrap="">_______________________________________________
calsify mailing list
<a class="moz-txt-link-abbreviated" href="mailto:calsify@ietf.org" moz-do-not-send="true">calsify@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/calsify" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/calsify</a>
</pre>
      </blockquote>
    </blockquote>
  </body>
</html>

--------------45EF20E418EDADA277D6EF29--


From nobody Sun Jan  3 13:17:42 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 596E43A1336; Sun,  3 Jan 2021 13:17:41 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: calsify@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: calsify@ietf.org
Message-ID: <160970866130.15038.14322884764391875718@ietfa.amsl.com>
Date: Sun, 03 Jan 2021 13:17:41 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/pq3Ad3P7ZoFkxGGZ715BIoemOjY>
Subject: [calsify] I-D Action: draft-ietf-calext-eventpub-extensions-17.txt
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jan 2021 21:17:41 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Calendaring Extensions WG of the IETF.

        Title           : Event Publishing Extensions to iCalendar
        Author          : Michael Douglass
	Filename        : draft-ietf-calext-eventpub-extensions-17.txt
	Pages           : 34
	Date            : 2021-01-03

Abstract:
   This specification updates RFC5545 by introducing a number of new
   iCalendar properties and components which are of particular use for
   event publishers and in social networking.

   This specification also defines a new STRUCTURED-DATA property for
   iCalendar RFC5545 to allow for data that is directly pertinent to an
   event or task to be included with the calendar data.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-calext-eventpub-extensions-17
https://datatracker.ietf.org/doc/html/draft-ietf-calext-eventpub-extensions-17

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-eventpub-extensions-17


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Sun Jan  3 13:58:05 2021
Return-Path: <mikeadouglass@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CA663A1388 for <calsify@ietfa.amsl.com>; Sun,  3 Jan 2021 13:58:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.459
X-Spam-Level: 
X-Spam-Status: No, score=-0.459 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QDM9UMwE_ess for <calsify@ietfa.amsl.com>; Sun,  3 Jan 2021 13:58:02 -0800 (PST)
Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com [IPv6:2607:f8b0:4864:20::f29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0AF53A1386 for <calsify@ietf.org>; Sun,  3 Jan 2021 13:58:01 -0800 (PST)
Received: by mail-qv1-xf29.google.com with SMTP id l14so12210827qvh.2 for <calsify@ietf.org>; Sun, 03 Jan 2021 13:58:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=pO3Xb5bjQIOVPvf8rN6cjTEJPXSYXxXv1RbxcV1SySI=; b=q/yXC+TB3NwEc8rzeV55w7i/zmwT6rQjy84J3BFBqwSH2+A8QI1ce18KPmXqb2qD3v fMaK9c8A67Bc1euIDXoUAClAimIfg3iyF9+rPhYsjhRlxR7y4e6l7RM2APKAy0/Jcb3u 8R/U3VeDnjh9hf3Zcq/gDyK0p2NLYhH3DETO6oIV5UYgJfO4JzigvitLv9bfxp6I15z2 huALjMhd6HnWYXhLOBRfGRWOAH2b5/7xeF5jgsNAYQrFflffKd924w9YKyB7ArHoiI7B RT/Zk5st58rayVFMITddxVAMG+oBYTAJJWB+Ky2ExbwAGHv7uxF5OaYBDrOLd0p43mDt jx8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=pO3Xb5bjQIOVPvf8rN6cjTEJPXSYXxXv1RbxcV1SySI=; b=aZejo8WkFeRNOtRj6Ty2SbrVhMsM+nBa5kKRWFmbXCwrEreZt5WmVF6EZam+k89O8c /hYGoSZ+CY2Kpo47PeKBBAOZtsf5XRH1ZuuCnqvF5wGDyfJaKqLjkR20YZQoUGgKSdHc x27uV0wItFNpNaoNFLpYhQmUICss8LwpqXfS0f+1Quks/8nA5rLee55RaDzmTxGl8Nyk pr8B3EhPL6qaz0EpbZ5KPuB+g3pxezT8bl6qX6+g7vFpk6NRt3hiuBmKpXGnGKFmuQqd 5dv8cS5LWsyMSz8vZ2FOwQjIXMD57T14KFbS/jPC03wXp6MYYO4gfCt55VnZzGpbsJLg MHww==
X-Gm-Message-State: AOAM531VzQ02AVaigWqoi/23hF5iOzlsO93Brc5LMpZXs5H+J3xcZ+tC EFJc2Wu7JQTqn8YwP0nC26TBUcD4H1WiVw==
X-Google-Smtp-Source: ABdhPJxDRPs0Vg7Mdi4ss6/ynZHPcGQSSrAqvN0EIllQMvCRLV5bd8RuBIgueyL1ybvP0/X2Rz6+/w==
X-Received: by 2002:a0c:8c87:: with SMTP id p7mr74239992qvb.46.1609711080682;  Sun, 03 Jan 2021 13:58:00 -0800 (PST)
Received: from [192.168.1.151] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id x134sm34331030qka.1.2021.01.03.13.57.59 for <calsify@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 03 Jan 2021 13:57:59 -0800 (PST)
To: calsify@ietf.org
References: <160970866130.15038.14322884764391875718@ietfa.amsl.com>
From: Michael Douglass <mikeadouglass@gmail.com>
Message-ID: <126cb34c-8883-3893-a747-1259d111bd2e@gmail.com>
Date: Sun, 3 Jan 2021 16:57:58 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <160970866130.15038.14322884764391875718@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------F4CDB2AB220DE4F53DC896D0"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/qB1Lnewioi4VxBkWSgCnrvzY2Qg>
Subject: Re: [calsify] I-D Action: draft-ietf-calext-eventpub-extensions-17.txt
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jan 2021 21:58:04 -0000

This is a multi-part message in MIME format.
--------------F4CDB2AB220DE4F53DC896D0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

And just after I submit this I notice that there is an error in the 
PARTICIPANT component text.

Current:

Note:  When the PRIORITY is supplied it defines the ordering of
    PARTICIPANT components with the same value for the TYPE parameter.

New:

Note:  When the PRIORITY is supplied it defines the ordering of
    PARTICIPANT components with the same value for the PARTICIPANT-TYPE property.

End


I'll wait for comments and resubmit later

On 1/3/21 16:17, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Calendaring Extensions WG of the IETF.
>
>          Title           : Event Publishing Extensions to iCalendar
>          Author          : Michael Douglass
> 	Filename        : draft-ietf-calext-eventpub-extensions-17.txt
> 	Pages           : 34
> 	Date            : 2021-01-03
>
> Abstract:
>     This specification updates RFC5545 by introducing a number of new
>     iCalendar properties and components which are of particular use for
>     event publishers and in social networking.
>
>     This specification also defines a new STRUCTURED-DATA property for
>     iCalendar RFC5545 to allow for data that is directly pertinent to an
>     event or task to be included with the calendar data.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-calext-eventpub-extensions-17
> https://datatracker.ietf.org/doc/html/draft-ietf-calext-eventpub-extensions-17
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-eventpub-extensions-17
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify

--------------F4CDB2AB220DE4F53DC896D0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>And just after I submit this I notice that there is an error in
      the PARTICIPANT component text. <br>
    </p>
    <p>Current:</p>
    <pre style="background-color:#ffffff;color:#080808;font-family:'JetBrains Mono',monospace;font-size:9.8pt;">Note:  When the PRIORITY is supplied it defines the ordering of
   PARTICIPANT components with the same value for the TYPE parameter.
</pre>
    <p>New:</p>
    <pre style="background-color:#ffffff;color:#080808;font-family:'JetBrains Mono',monospace;font-size:9.8pt;">Note:  When the PRIORITY is supplied it defines the ordering of
   PARTICIPANT components with the same value for the PARTICIPANT-TYPE property.
</pre>
    <p>End<br>
    </p>
    <p><br>
    </p>
    <p>I'll wait for comments and resubmit later<br>
    </p>
    <div class="moz-cite-prefix">On 1/3/21 16:17,
      <a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a> wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:160970866130.15038.14322884764391875718@ietfa.amsl.com">
      <pre class="moz-quote-pre" wrap="">
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Calendaring Extensions WG of the IETF.

        Title           : Event Publishing Extensions to iCalendar
        Author          : Michael Douglass
	Filename        : draft-ietf-calext-eventpub-extensions-17.txt
	Pages           : 34
	Date            : 2021-01-03

Abstract:
   This specification updates RFC5545 by introducing a number of new
   iCalendar properties and components which are of particular use for
   event publishers and in social networking.

   This specification also defines a new STRUCTURED-DATA property for
   iCalendar RFC5545 to allow for data that is directly pertinent to an
   event or task to be included with the calendar data.


The IETF datatracker status page for this draft is:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/">https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/</a>

There are also htmlized versions available at:
<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-calext-eventpub-extensions-17">https://tools.ietf.org/html/draft-ietf-calext-eventpub-extensions-17</a>
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-ietf-calext-eventpub-extensions-17">https://datatracker.ietf.org/doc/html/draft-ietf-calext-eventpub-extensions-17</a>

A diff from the previous version is available at:
<a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-eventpub-extensions-17">https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-eventpub-extensions-17</a>


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
<a class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</a>


_______________________________________________
calsify mailing list
<a class="moz-txt-link-abbreviated" href="mailto:calsify@ietf.org">calsify@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/calsify">https://www.ietf.org/mailman/listinfo/calsify</a>
</pre>
    </blockquote>
  </body>
</html>

--------------F4CDB2AB220DE4F53DC896D0--


From nobody Mon Jan  4 11:44:09 2021
Return-Path: <noreply@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 310973A0FF4; Mon,  4 Jan 2021 11:44:03 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Murray Kucherawy via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-calext-eventpub-extensions@ietf.org, calext-chairs@ietf.org, calsify@ietf.org, Daniel Migault <daniel.migault@ericsson.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Murray Kucherawy <superuser@gmail.com>
Message-ID: <160978944264.1715.14149807055782718055@ietfa.amsl.com>
Date: Mon, 04 Jan 2021 11:44:03 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/hZf05y6s2s4dKLxM_Tc83o7ElAg>
Subject: [calsify] Murray Kucherawy's No Objection on draft-ietf-calext-eventpub-extensions-17: (with COMMENT)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2021 19:44:03 -0000

Murray Kucherawy has entered the following ballot position for
draft-ietf-calext-eventpub-extensions-17: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Section 1.2 says "For example, we may want to record who is participating in a
public event", but the Privacy Considerations section doesn't say anything
about the fact that this could collect data about people who are interested in
the event, even if they don't go (though the location issue is mentioned). 
Also, especially since 2020, the public event could be a purely online event,
where location data isn't part of the issue.  (Alternatively, if this is meant
to address in-person events only, that would be useful to say up front.)

Section 6.2 (and other sections, but I noticed it here): ABNF literal strings
are case-insensitive.  That means, for example, that the ABNF here would allow
"ACTIVE" for a "partvalue", but would also allow "active", "AcTiVe", etc.  Is
that acceptable?  (This probably applies to lots of prior CALEXT documents -- I
admittedly didn't check -- so it may not be worth fixing here.)

Section 6.4:

   Property Parameters:  IANA, or non-standard property parameters can
      be specified on this property.

I think that should be "IANA-registered"?  Same issue in Sections 6.5 and 6.6.

Section 7: I believe the ABNF here needs a once-over.

Section 9.2: For the threat described in the first paragraph, are there any
possible mitigations to suggest?

Section 10.2: In "without that participants express permission", that should be
"participant's".  There's also a period missing at the end of the second last
paragraph, though as it reads, it's possible there's even some intended text
missing.

Section 11.2: The rules for making registrations into both the existing
registries and these new ones are striking.  RFC 8126 doesn't even create a
category that is a combination of Expert Review and Standards Action, but
that's what this spells out.  And I wonder what would happen if we were to
publish a Standards Track RFC (which has IETF consensus) with which the
Designated Expert disagreed.  I'm not asking for anything to change here given
that consistency with the existing registries is probably desirable, but it
does set an unusually high bar for registrations.




From nobody Mon Jan  4 13:55:38 2021
Return-Path: <noreply@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A0F233A005C; Mon,  4 Jan 2021 13:55:35 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-calext-eventpub-extensions@ietf.org, calext-chairs@ietf.org, calsify@ietf.org, Daniel Migault <daniel.migault@ericsson.com>, daniel.migault@ericsson.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <160979733556.18901.5326788661603760785@ietfa.amsl.com>
Date: Mon, 04 Jan 2021 13:55:35 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/dqiRsNFp2c7FS7fzjzFGka2ptQU>
Subject: [calsify] Barry Leiba's Discuss on draft-ietf-calext-eventpub-extensions-17: (with DISCUSS)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2021 21:55:36 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-calext-eventpub-extensions-17: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Thanks very much for the changes in Section 9.1, and I think we're now at the
best place we can reasonable be here.  Well done.

Thanks also for the changes to clarify the ABNF.  They're mostly good, and we
should be able to clean these last bits up pretty easily:

— Section 6.6 —

The new ABNF doesn’t correctly specify what the old was trying to say.  I think
this is correct and concise, but please check it over:

NEW

sdataprop    = "STRUCTURED-DATA" sdataparam ":"
                     sdataval CRLF

      sdataparam     = ; all parameter elements may appear in any order,
                       ; and the order is not significant.
                       (sdataparamtext / sdataparambin / sdataparamuri)
                       *(";" other-param)

      sdataparamtext = ";VALUE=TEXT"
                       ";" fmttypeparam
                       ";" schemaparam

      sdataparambin  = ";VALUE=BINARY"
                       ";ENCODING=BASE64"
                       ";" fmttypeparam
                       ";" schemaparam

      sdataparamuri  = ";VALUE=URI"
                       [";" fmttypeparam]
                       [";" schemaparam]

      sdataval       = ( binary / text /uri )
                       ; value MUST match value type

END

— Section 7.1 —

      participantc = "BEGIN" ":" "PARTICIPANT" CRLF
                     *( partprop / locationc / resourcec )
                     "END" ":" "PARTICIPANT" CRLF

This allows multiple instances of partprop (or none), which is not what you
mean.  The “*” isn’t right.  Also, do you really mean to have locationc and
resourcec here?  Those are blocks that are peers of participantc within eventc,
todoc, journalc, and freebusyc… are they also meant to be nested within
participantc?  If so, it would be good to have an example or two that shows
that.  In any case, that bit of ABNF still needs some work.

                     (calendaraddress)
                     (created)
                     (description)
                     (dtstamp)
                     (geo)
                     (last-mod)
                     (priority)
                     (seq)
                     (status)
                     (summary)
                     (url)

All of these are meant to be optional, so they should be in square brackets,
rather than in parentheses.  The same is true in Sections 7.2 and 7.3.






From nobody Tue Jan  5 15:16:16 2021
Return-Path: <mikeadouglass@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51BFD3A08B1 for <calsify@ietfa.amsl.com>; Tue,  5 Jan 2021 15:16:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.359
X-Spam-Level: 
X-Spam-Status: No, score=-2.359 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tp4X8aYrNOMP for <calsify@ietfa.amsl.com>; Tue,  5 Jan 2021 15:16:12 -0800 (PST)
Received: from mail-qv1-xf31.google.com (mail-qv1-xf31.google.com [IPv6:2607:f8b0:4864:20::f31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56DB53A0BED for <calsify@ietf.org>; Tue,  5 Jan 2021 15:16:12 -0800 (PST)
Received: by mail-qv1-xf31.google.com with SMTP id p5so527829qvs.7 for <calsify@ietf.org>; Tue, 05 Jan 2021 15:16:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=E2LYb1goNjRLgLTSmEnx5yH85INkv8ClFUk1iJb1/uQ=; b=IdPFVJ/47NfdXGPkhjbcMhE4yqIYpuSiJHGvAm5rGfq2N1ZAIGM+dTtrKTw7pKIvuW m0UosHx/nL48zD38fcucDQAZMyAjyTrMFoymxg2w920v5gYrqXj0LXVNfMHb7UOmmrtt FfUH4e87M5q7aDK2oxxTSDbj7jj4kjnAlItjrpbxOAfEmKHD03TU3WJhwo4lvPEEzIPw faanOxIT2CJL5rYe3lYtH2JsRZxDbWOHC6vD7MUI9hiuBL3mo8rVdchoG8cLCDud+9ye 1jkcR+fThZxFUNQVVCuVNnhPr3agerB+C2fS6fELpg4V0rvYJBTshShCf5MW4JSinnd9 2f2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=E2LYb1goNjRLgLTSmEnx5yH85INkv8ClFUk1iJb1/uQ=; b=NbhGl+4Cm3e0XAS9bPQPFaklcFMPp9GvBp3A/CgWqtuEWS07BseCiQeBIa21eB60Un ZYDow/T3/WKxVv0FvPWFtMtchJLHCp2Qs7UAWh4aul7EqA4OFm2kiiCyjHzMfebPjciT XmXmcRf2pN55dtx5lfwLXfIFqsYamtVEw4wemKxYm/BOHQsVk5Gw29VeedgS7Wv847dT M11c2Za4EuofuByHa+0apXnZNvE/KHT0OyEPRcqM9NqP93FghkhUWSwefGeU1aNhynPF CW5o9aT1jVqTONhFQn2XIJqJpynBuixC4Af3Lgiqbwp3sHWKv/FCN9mtGGXIsCd+MTe1 pU8Q==
X-Gm-Message-State: AOAM5309PkDEoFxYtEj0mAxsTcKY29rlEGB0ZFil+B6l0qj1Q6ti4SCD CwfzIZCcNRoHdhxxSbin5PHqvLxnQIzYtQ==
X-Google-Smtp-Source: ABdhPJyWrBIxLW1/Oc4nOWJppcDv8x2yM/yN5N98DE63zpcQ+/2qq092OqTf47q5HT4S8lZLoPL5lA==
X-Received: by 2002:a0c:ea34:: with SMTP id t20mr1658472qvp.5.1609888571018; Tue, 05 Jan 2021 15:16:11 -0800 (PST)
Received: from [192.168.1.151] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id a77sm499179qkg.77.2021.01.05.15.16.10 for <calsify@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 05 Jan 2021 15:16:10 -0800 (PST)
To: calsify@ietf.org
References: <160945196930.22062.1265221056603729215@ietfa.amsl.com>
From: Michael Douglass <mikeadouglass@gmail.com>
Message-ID: <2d83576f-0577-734a-ab9b-aaa691d9d44d@gmail.com>
Date: Tue, 5 Jan 2021 18:16:09 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <160945196930.22062.1265221056603729215@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------A35A58032CCEF9C416E04FD2"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/93_MVvARNznNbS9O5Zk7NqZxMJk>
Subject: Re: [calsify] I-D Action: draft-ietf-calext-ical-relations-06.txt
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2021 23:16:14 -0000

This is a multi-part message in MIME format.
--------------A35A58032CCEF9C416E04FD2
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

I do have a follow up related to Murray Kucherawy's comments on case 
sensitivity for the eventpub draft:

For linkrelparam we have this:

linkrelparam = "REL" "="
                ("SOURCE"      ; Link to source of this component
                / DQUOTE uri DQUOTE
                / iana-token)   ; Other IANA registered type

First the abnf is wrong - it should be "LINKREL" not "REL"

The values (other than the uri) should case-insensitive strings from the 
link relations registry in rfc 8288

Given that shouldn't the abnf be something like:

linkrelparam = "LINKREL" "=" param-value

with a paragraph specifying that a value can be "source" along with a 
description.

param-value is defined in 5545:

      param-value   = paramtext / quoted-string

      paramtext     = *SAFE-CHAR

The quoted string MAY be a URI representing an extension relation type 
as defined in rfc8288 section 2.1.2

I guess iana-token can look the same but it's semantics are different

      iana-token    = 1*(ALPHA / DIGIT / "-")
      ; iCalendar identifier registered with IANA

The value will be registered with IANA (we hope) but it won't be an 
iCalendar identifier.

On 12/31/20 16:59, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Calendaring Extensions WG of the IETF.
>
>          Title           : Support for iCalendar Relationships
>          Author          : Michael Douglass
> 	Filename        : draft-ietf-calext-ical-relations-06.txt
> 	Pages           : 17
> 	Date            : 2020-12-31
>
> Abstract:
>     This specification updates RELATED-TO defined in [RFC5545] and
>     introduces new iCalendar properties LINK, CONCEPT and REFID to allow
>     better linking and grouping of iCalendar components and related data.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-calext-ical-relations/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-calext-ical-relations-06
> https://datatracker.ietf.org/doc/html/draft-ietf-calext-ical-relations-06
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-ical-relations-06
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify

--------------A35A58032CCEF9C416E04FD2
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>I do have a follow up related to Murray Kucherawy's comments on
      case sensitivity for the eventpub draft:</p>
    <p>For linkrelparam we have this:</p>
    <pre style="background-color:#ffffff;color:#080808;font-family:'JetBrains Mono',monospace;font-size:9.8pt;">linkrelparam = "REL" "="
               ("SOURCE"      ; Link to source of this component
               / DQUOTE uri DQUOTE
               / iana-token)   ; Other IANA registered type
</pre>
    <p>First the abnf is wrong - it should be "LINKREL" not "REL"<br>
    </p>
    <p>The values (other than the uri) should case-insensitive strings
      from the link relations registry in rfc 8288</p>
    <p>Given that shouldn't the abnf be something like:<br>
    </p>
    <pre style="background-color:#ffffff;color:#080808;font-family:'JetBrains Mono',monospace;font-size:9.8pt;">linkrelparam = "LINKREL" "=" param-value</pre>
    <p>with a paragraph specifying that a value can be "source" along
      with a description.</p>
    <p>param-value is defined in 5545:</p>
    <pre class="newpage">     param-value   = paramtext / quoted-string

     paramtext     = *SAFE-CHAR

</pre>
    <p>The quoted string MAY be a URI representing an extension relation
      type as defined in rfc8288 section 2.1.2<br>
    </p>
    <p>I guess iana-token can look the same but it's semantics are
      different  <br>
    </p>
    <pre class="newpage">     iana-token    = 1*(ALPHA / DIGIT / "-")
     ; iCalendar identifier registered with IANA
</pre>
    <div class="moz-cite-prefix">The value will be registered with IANA
      (we hope) but it won't be an iCalendar identifier.<br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">On 12/31/20 16:59,
      <a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a> wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:160945196930.22062.1265221056603729215@ietfa.amsl.com">
      <pre class="moz-quote-pre" wrap="">
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Calendaring Extensions WG of the IETF.

        Title           : Support for iCalendar Relationships
        Author          : Michael Douglass
	Filename        : draft-ietf-calext-ical-relations-06.txt
	Pages           : 17
	Date            : 2020-12-31

Abstract:
   This specification updates RELATED-TO defined in [RFC5545] and
   introduces new iCalendar properties LINK, CONCEPT and REFID to allow
   better linking and grouping of iCalendar components and related data.


The IETF datatracker status page for this draft is:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-calext-ical-relations/">https://datatracker.ietf.org/doc/draft-ietf-calext-ical-relations/</a>

There are also htmlized versions available at:
<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-calext-ical-relations-06">https://tools.ietf.org/html/draft-ietf-calext-ical-relations-06</a>
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-ietf-calext-ical-relations-06">https://datatracker.ietf.org/doc/html/draft-ietf-calext-ical-relations-06</a>

A diff from the previous version is available at:
<a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-ical-relations-06">https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-ical-relations-06</a>


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
<a class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</a>


_______________________________________________
calsify mailing list
<a class="moz-txt-link-abbreviated" href="mailto:calsify@ietf.org">calsify@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/calsify">https://www.ietf.org/mailman/listinfo/calsify</a>
</pre>
    </blockquote>
  </body>
</html>

--------------A35A58032CCEF9C416E04FD2--


From nobody Mon Jan 11 13:43:55 2021
Return-Path: <justingrant.ietf.public@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 671F03A1301 for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 13:43:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CEy0UW8jYgq5 for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 13:43:53 -0800 (PST)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E23C3A1300 for <calsify@ietf.org>; Mon, 11 Jan 2021 13:43:53 -0800 (PST)
Received: by mail-ed1-x52a.google.com with SMTP id cw27so51669edb.5 for <calsify@ietf.org>; Mon, 11 Jan 2021 13:43:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=DN8YYLtbMySFHt5CU83CC8t+SysQgX9/5mm2NjGi7QE=; b=u9tVNrkLWb3LCOLXdBdmD9fOy37uXGRDAT7SXzp23hrBLdbjGjE/3xlF/J6qtnV8Ie vVP23opQMfAziE1fvIERy8E08wKpJOrHrxF4hjJgmKkku05Ounnfehw/9B9RwHI3wjis XwQ6Yl/PiqkIO0xK74l6kxUTEgxadmE3iVIphMcnrvo6+CE0EeO1BXgfqNkQJCpR5oAY G7w39UzwCF6qZ8f8ptxL/BIJ6vQk/g07plisa0o6Aa+WnbfIaU0EixifiXGrIp/mm4Nd ifCQKveH9akXf1U3IfHkuxy5AxgpetzZAbc5U6APFe3VT/2ZSqp5nrlmT285xt9UD00W r10g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=DN8YYLtbMySFHt5CU83CC8t+SysQgX9/5mm2NjGi7QE=; b=X+4c/eRpqrpJj3zMaoNmJ5HRy3qX1qLLeg2+SsUhPPWLcWDwtmyjG6QqHNew8iTHFv LcY8hP9PSjtcByHNxFDE3AjqRTnGXvvluMC6PPFna7xBfsBxD0lrNneHrMDps/fMqb3f M2nPVT3PLnTPSia3gw+staV7oAlASYhZHaI3KqY+AfQZxVsuNqXl74Y7E4mPLyCOpIQ8 pSBQ9Cd6AcGrSFb5z6cSa8hWMUyLCh7rcpu4+dViH0HqQAunbzdbsTBgvf7IhFIOd5EU 0iA+fgflm35E9eEahlPUClaMqqH+1ZzlWQ9I6KyAzu3/ui3dJyXYO1vfaMMrb63hbHWx 3UnQ==
X-Gm-Message-State: AOAM532mhIcgA4Rky2omd+MlkBkI6DkyC3WmNym6ocepe6M9p/Ns1zyw zgbFhPkkhBp/SdW30VJu4pVGOZ2OmTTqAa2i/76DKpd7
X-Google-Smtp-Source: ABdhPJwtkc71YVx118AdL7Ww+gVf3ZAZWkRcAVL9Bv1xAuxHZVtS24wyI5Lf5ErVqt7EZ47UjxTlqTiIL/v60JArqd4=
X-Received: by 2002:a05:6402:797:: with SMTP id d23mr967022edy.302.1610401431260;  Mon, 11 Jan 2021 13:43:51 -0800 (PST)
MIME-Version: 1.0
From: Justin Grant <justingrant.ietf.public@gmail.com>
Date: Mon, 11 Jan 2021 13:43:40 -0800
Message-ID: <CACy7Cfhb0kBdcyF+mpSd=cvRBoCzFBneB3V7r9vvasfNJwv6FA@mail.gmail.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary="00000000000041904a05b8a6cda2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/DAcErKEFCNxLoKXf9w1a3aGJ7Hs>
Subject: [calsify] Hebrew Adar II - "6L" or "6" ?
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2021 21:43:54 -0000

--00000000000041904a05b8a6cda2
Content-Type: text/plain; charset="UTF-8"

The Temporal team has a quick question about RFC 7529: is Hebrew month Adar
II (Adar in a leap year) referred to using "6L" or "6" according to the
spec?  I assume the latter (because they're the same month, just with a
different name) but wanted to make sure.

Cheers,
Justin

--00000000000041904a05b8a6cda2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The Temporal team has a quick question about RFC 7529: is =
Hebrew month Adar II (Adar in a leap year) referred=C2=A0to using &quot;6L&=
quot; or &quot;6&quot; according to the spec?=C2=A0 I assume the latter (be=
cause they&#39;re the same month, just with a different name) but wanted to=
 make sure.<div><br></div><div>Cheers,</div><div>Justin</div><div><br></div=
></div>

--00000000000041904a05b8a6cda2--


From nobody Mon Jan 11 13:50:34 2021
Return-Path: <sffc@google.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78EDF3A130D for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 13:50:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.971
X-Spam-Level: 
X-Spam-Status: No, score=-17.971 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96a4u3ciqd6z for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 13:50:31 -0800 (PST)
Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5D9D3A1306 for <calsify@ietf.org>; Mon, 11 Jan 2021 13:50:30 -0800 (PST)
Received: by mail-ot1-x335.google.com with SMTP id b24so370221otj.0 for <calsify@ietf.org>; Mon, 11 Jan 2021 13:50:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8Qb6hZR9iHHqYLyFxfgw8ExUenR94vJdvLS2/iUuGek=; b=YW+Jh7PwKcPfVx6rN37luw/ivoQQf+IwOxn8bHr8tCQ+1Q67WyInM9HSmaq3rb2/Nn 3BintkreFBMHjpsCmMZCRLahHC8T4adASkOim2WyncjlVS0E337AZNSM98cscsBKKhg/ Nf7lPNzlY/UISoFN/FKr3r2bHeG1p/CKzs+Rre1bOdArkY7F1jl7lck/AxZLdTCHxpNL yLy0hGmKB0If8LPU9KFxAp3LI6IbDrGk5MoBvDhbH/3wF4sBaWSP29oPEydvpyvhH/iz uFq7jP0Ac+tMhvehus4IJZWMM2UhxMuV+XZfrLFSMLhDp4ZJG1Ll5CVY3fUhHrLyIKMp ttsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8Qb6hZR9iHHqYLyFxfgw8ExUenR94vJdvLS2/iUuGek=; b=qyZhYxjlqK1USUILH8blnnpxNGX0lWt9GdRCWdKkOXswyRjpIJdCcj7YbgDItkzzLF MuUjL10BgAIv8rjF9JcRFu6+YoIiZgk8UAObzUX7GtBDYIRUsyKfoWI2azB+YSrirhyx KVA3MN2BFuEw+D3ciu1MuIIP3Tur61vy10GlvNMHJEQVAG9yDi2IZTgdE0JmYgc8SPNA X4qdZn0wJ/IPFqjqHihFbhBrBrpFaAxM3RIxiKaE3hgnpyRBkMShZTwIfcz9VK5bPnhC EIQvq8BbQbNvcb9BUtJ5IO1xztgtXRXLQFA/ypFp/cLR9wbQDTOh83ViqFv9kqs0mJnK RcHg==
X-Gm-Message-State: AOAM532ecJCZt+cfM8VVx9AJ5WRsmGcOi3mJtTIMI1QyU4YF7rQ1NFkv ozekh1e1fexd5V2+WpcqCluMxehzICMUNIrHa9RY2A==
X-Google-Smtp-Source: ABdhPJzvqQe/GfYBQU2+IhVIoUCXhOM+MHnrHOS8Cy8HGQKtTWIn0SRbeM6alPiPnb3XLyFXQorh32ki8ft/fcztQ0c=
X-Received: by 2002:a05:6830:578:: with SMTP id f24mr765359otc.36.1610401829846;  Mon, 11 Jan 2021 13:50:29 -0800 (PST)
MIME-Version: 1.0
References: <CACy7Cfhb0kBdcyF+mpSd=cvRBoCzFBneB3V7r9vvasfNJwv6FA@mail.gmail.com>
In-Reply-To: <CACy7Cfhb0kBdcyF+mpSd=cvRBoCzFBneB3V7r9vvasfNJwv6FA@mail.gmail.com>
From: Shane Carr <sffc@google.com>
Date: Mon, 11 Jan 2021 15:50:17 -0600
Message-ID: <CABxsp=ko+e+L7+=BFS8OxGQaPdq+N0uqL=X_4bvrNOEmd6edRw@mail.gmail.com>
To: Justin Grant <justingrant.ietf.public@gmail.com>
Cc: calsify@ietf.org
Content-Type: multipart/alternative; boundary="00000000000003f23605b8a6e55d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/cIuXNbRxHQbeBTcftOYesYBGQ-I>
Subject: Re: [calsify] Hebrew Adar II - "6L" or "6" ?
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2021 21:50:33 -0000

--00000000000003f23605b8a6e55d
Content-Type: text/plain; charset="UTF-8"

Additional context: for the purposes of date *formatting*, it is useful for
interchange to distinguish between Adar and Adar II.

On Mon, Jan 11, 2021 at 3:44 PM Justin Grant <
justingrant.ietf.public@gmail.com> wrote:

> The Temporal team has a quick question about RFC 7529: is Hebrew month
> Adar II (Adar in a leap year) referred to using "6L" or "6" according to
> the spec?  I assume the latter (because they're the same month, just with a
> different name) but wanted to make sure.
>
> Cheers,
> Justin
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>

--00000000000003f23605b8a6e55d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Additional context: for the purposes of date <i>formatting=
</i>, it is useful for interchange to distinguish between Adar and Adar II.=
</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=
On Mon, Jan 11, 2021 at 3:44 PM Justin Grant &lt;<a href=3D"mailto:justingr=
ant.ietf.public@gmail.com">justingrant.ietf.public@gmail.com</a>&gt; wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr=
">The Temporal team has a quick question about RFC 7529: is Hebrew month Ad=
ar II (Adar in a leap year) referred=C2=A0to using &quot;6L&quot; or &quot;=
6&quot; according to the spec?=C2=A0 I assume the latter (because they&#39;=
re the same month, just with a different name) but wanted to make sure.<div=
><br></div><div>Cheers,</div><div>Justin</div><div><br></div></div>
_______________________________________________<br>
calsify mailing list<br>
<a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/calsify" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/calsify</a><br>
</blockquote></div>

--00000000000003f23605b8a6e55d--


From nobody Mon Jan 11 13:55:01 2021
Return-Path: <murch@fastmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8664E3A1340 for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 13:55:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.38
X-Spam-Level: 
X-Spam-Status: No, score=-1.38 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=Ox9Qjxty; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=PXhK70xe
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7g4pCx935IGt for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 13:54:59 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AB3C3A133D for <calsify@ietf.org>; Mon, 11 Jan 2021 13:54:59 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 57AD05C01F2 for <calsify@ietf.org>; Mon, 11 Jan 2021 16:54:58 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 11 Jan 2021 16:54:58 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm1; bh=pzhejFBFC/ZQFYY/9N2zHi8TwKN cpBL4UdIjKg4mZ1E=; b=Ox9QjxtyOX5U2jEhYVT+1G8nKCoXvmqCQKK68Mahu+Q DOF0dI6trC0KBUoJSQ5cvJhyK2cJPOO/X0VXalZUy7dlV0tPTcoVB6x/MzBf1nKD 60ELMnfEWi5Yi27l7V2M1G0RFYZZwt1DF4KMk8Y1X64sFZPQNCRQBim3wlmuRBNi kSMauT+s2UYVci80VTGSN0aELZlaa6/+OaEEr6UCuiRsq2Ms04qaRw4/OSUPkaWI HeXULSg/kmz3Muxes56tODGLZoltQawlT86xo92F5iTOIygJMVqLCl+nHzXE1IO4 GR3Okz3PiTlqGR+i6ia1it/wrZq3AljmI4MPzVWn+8w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=pzhejF BFC/ZQFYY/9N2zHi8TwKNcpBL4UdIjKg4mZ1E=; b=PXhK70xeEmlaM6mSW7NU/T tMSF1OxU3/ylyCWIBTzK5XjCrNryTiB1eDX4kgBP+510+0voDnIkdVCsb5WOyQR3 IVlXhsCg7jQOnNnsd+HUc81cpZ3DYpIv3IHAwIz7PmiSIy6E80T/44MLiDTEYd99 SA5ZHajttGLBFKVmCyS2JQJGCTPna92bLYou3JcndYLghX5B5w5RYonUIufZ51+s XOYYjkm9l2wCzZfXDqoUYMfEKSa6MHNW0fsoNZuqSLDWlTRrdp9noIGGGfYP3Pau kMM7tCXyaXp/j2TRW8tfgxBJjEIswCFDS4qJXX1dCjLLPtQBp3vO8uoS9w2fNlXQ ==
X-ME-Sender: <xms:Mcn8X84oklY8DWReOI1WGnyEdVvpQ29Q-I-c41UEmd00LN1Vy9YZCQ> <xme:Mcn8X-nhe_0WCZ-cfNa6Bd4LzQp4y4QZkn2vbubfDb5TdTCY17gXvwzhDb1_llKKl oCHoHwcJ85tpQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrvdehuddgudehhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtsegrtd erredtfeejnecuhfhrohhmpefmvghnucfouhhrtghhihhsohhnuceomhhurhgthhesfhgr shhtmhgrihhlrdgtohhmqeenucggtffrrghtthgvrhhnpeffuefhvefggfdvudeuvdetie ejuedvvdekudeggedvffevgfduffeuieelgeeggeenucffohhmrghinhepihgvthhfrdho rhhgnecukfhppeejgedrjeejrdekhedrvdehtdenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehmuhhrtghhsehfrghsthhmrghilhdrtghomh
X-ME-Proxy: <xmx:Mcn8X5paN9MixVSCbAoRdCKCxCcG4xED80-NfjuRxon0yfv7Oq75qA> <xmx:Mcn8X1tPPQ4MiT5o_vBaBOapf6XKh3BTT5NDgWzT47F7LrXLZaW4Dg> <xmx:Mcn8X2HnJKvvZ91y_7ViIT41DPMrFD07IYZ9FZjH8m4vesldv_478g> <xmx:Msn8XxCG1nDspb-6E4zAECGXr6E6RbN42lBBx3wx2M0ekebIxADfIQ>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 4E97F1080064 for <calsify@ietf.org>; Mon, 11 Jan 2021 16:54:57 -0500 (EST)
To: calsify@ietf.org
References: <CACy7Cfhb0kBdcyF+mpSd=cvRBoCzFBneB3V7r9vvasfNJwv6FA@mail.gmail.com> <CABxsp=ko+e+L7+=BFS8OxGQaPdq+N0uqL=X_4bvrNOEmd6edRw@mail.gmail.com>
From: Ken Murchison <murch@fastmail.com>
Message-ID: <3eea351a-9cc4-541b-6110-9889d8d1715a@fastmail.com>
Date: Mon, 11 Jan 2021 16:54:56 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CABxsp=ko+e+L7+=BFS8OxGQaPdq+N0uqL=X_4bvrNOEmd6edRw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------7FB1E571ABCF70CE1316FB34"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/EMa7mYpcCCsvhqR7a9yX2cj-WqE>
Subject: Re: [calsify] Hebrew Adar II - "6L" or "6" ?
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2021 21:55:01 -0000

This is a multi-part message in MIME format.
--------------7FB1E571ABCF70CE1316FB34
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Adar (or Adar II in a leap year) is always month "6".  Adar I is "5L" 
since its inserted between "5" and "6".


On 1/11/21 4:50 PM, Shane Carr wrote:
> Additional context: for the purposes of date /formatting/, it is 
> useful for interchange to distinguish between Adar and Adar II.
>
> On Mon, Jan 11, 2021 at 3:44 PM Justin Grant 
> <justingrant.ietf.public@gmail.com 
> <mailto:justingrant.ietf.public@gmail.com>> wrote:
>
>     The Temporal team has a quick question about RFC 7529: is Hebrew
>     month Adar II (Adar in a leap year) referred to using "6L" or "6"
>     according to the spec?  I assume the latter (because they're the
>     same month, just with a different name) but wanted to make sure.
>
>     Cheers,
>     Justin
>
>     _______________________________________________
>     calsify mailing list
>     calsify@ietf.org <mailto:calsify@ietf.org>
>     https://www.ietf.org/mailman/listinfo/calsify
>     <https://www.ietf.org/mailman/listinfo/calsify>
>
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify

-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


--------------7FB1E571ABCF70CE1316FB34
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Adar (or Adar II in a leap year) is always month "6".  Adar I is
      "5L" since its inserted between "5" and "6".</p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/11/21 4:50 PM, Shane Carr wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CABxsp=ko+e+L7+=BFS8OxGQaPdq+N0uqL=X_4bvrNOEmd6edRw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Additional context: for the purposes of date <i>formatting</i>,
        it is useful for interchange to distinguish between Adar and
        Adar II.</div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Mon, Jan 11, 2021 at 3:44
          PM Justin Grant &lt;<a
            href="mailto:justingrant.ietf.public@gmail.com"
            moz-do-not-send="true">justingrant.ietf.public@gmail.com</a>&gt;
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div dir="ltr">The Temporal team has a quick question about
            RFC 7529: is Hebrew month Adar II (Adar in a leap year)
            referred to using "6L" or "6" according to the spec?  I
            assume the latter (because they're the same month, just with
            a different name) but wanted to make sure.
            <div><br>
            </div>
            <div>Cheers,</div>
            <div>Justin</div>
            <div><br>
            </div>
          </div>
          _______________________________________________<br>
          calsify mailing list<br>
          <a href="mailto:calsify@ietf.org" target="_blank"
            moz-do-not-send="true">calsify@ietf.org</a><br>
          <a href="https://www.ietf.org/mailman/listinfo/calsify"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/calsify</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
calsify mailing list
<a class="moz-txt-link-abbreviated" href="mailto:calsify@ietf.org">calsify@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/calsify">https://www.ietf.org/mailman/listinfo/calsify</a>
</pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC</pre>
  </body>
</html>

--------------7FB1E571ABCF70CE1316FB34--


From nobody Mon Jan 11 14:21:55 2021
Return-Path: <sffc@google.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 669FC3A13B4 for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 14:21:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.971
X-Spam-Level: 
X-Spam-Status: No, score=-17.971 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IDhIvXdLrx10 for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 14:21:52 -0800 (PST)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1CCE3A1318 for <calsify@ietf.org>; Mon, 11 Jan 2021 14:21:52 -0800 (PST)
Received: by mail-ot1-x32a.google.com with SMTP id o11so429454ote.4 for <calsify@ietf.org>; Mon, 11 Jan 2021 14:21:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=T7Mkz3DoAHqv0wYMJhjm1+2D/tJSiPpFffx9Sk8e/4c=; b=u1tU70h/I+k5201KbwXXVsJ/+xWZ+od5ecxfVlytcA5l0dvzgvY9hLOik2vPPRkN/x h97DsZTryjbvvvpIZ9/tHOB8Mauisc4vmsa+R8GrNRZp2tsRJ9lu3sAS1wnGcfJDqRmM c/maGBVeoic8d/ZM0OHEvMHP2nvxzqBU8hoO5IjJjWXjaBzwAiwnYemAC/23dWyO2aOz f5r3sC4ZPVSEh8K++c3omg7hrxlUtOb4gUlqvO4hchH9Gm7X0AhZ1CT/YxoaIIlr1/Ue cQXui6R+/Fe0OxHfFeHelJgs0RnPBN0kSrL1l9x+O3lzV9T7i1lva3yO6+BuBy0rz0ba nmQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=T7Mkz3DoAHqv0wYMJhjm1+2D/tJSiPpFffx9Sk8e/4c=; b=Tjm/vfI3JTOqozCfCASVqKoPOnSN8nPw1rnbskRcuJi34xo9tNCyTtTFDtADi6yyk4 nT1heSdzR9dfAfl5dJ6tSJrCLzrM5pHUqEZHDYA1yqSEgTyW9yT8lBG5LOaR6WvjFQP4 axjF0F+TqgCcd4dh2YGusqqyZb8UsAWiaW6mTd5zVYtP4omVHHqjItQ8M2ATtaH6ZJHq Y6LUhumxlK0HQ7u6aVoqu5Mh541hknKQNOelUVQUzLpUX6XdDl91jep1iyF3PcTK+Mpg JIP1BTT2dccO0jKzYvjRbl48i9XMopjBWdXmJkSjZbUgc4C0Mq/mOaTryC8ALgWWIBJr m8cQ==
X-Gm-Message-State: AOAM533KihUK+S2naCjdAHc+3S4L51pAKOKsRECd/FhHz73Lf0bXXSIX e2+yrpKd9RWUp0dvSCjhuFGVHLgPycFUQ0M2BBKadQ==
X-Google-Smtp-Source: ABdhPJw+PN2dfB9o8UgX4p25MOGSrsma7McS3WY6WwpH8Avv28G+LNaOSPk8LbnDGc3XciVVSnskSgBvnPVIKkVqvt0=
X-Received: by 2002:a9d:6c11:: with SMTP id f17mr860308otq.83.1610403711893; Mon, 11 Jan 2021 14:21:51 -0800 (PST)
MIME-Version: 1.0
References: <CACy7Cfhb0kBdcyF+mpSd=cvRBoCzFBneB3V7r9vvasfNJwv6FA@mail.gmail.com> <CABxsp=ko+e+L7+=BFS8OxGQaPdq+N0uqL=X_4bvrNOEmd6edRw@mail.gmail.com> <3eea351a-9cc4-541b-6110-9889d8d1715a@fastmail.com>
In-Reply-To: <3eea351a-9cc4-541b-6110-9889d8d1715a@fastmail.com>
From: Shane Carr <sffc@google.com>
Date: Mon, 11 Jan 2021 16:21:40 -0600
Message-ID: <CABxsp==y9f6+1gWvN2gnT+x6vSo3zW2TWQ135TwQt86S=4XvNg@mail.gmail.com>
To: Ken Murchison <murch@fastmail.com>
Cc: calsify@ietf.org
Content-Type: multipart/alternative; boundary="00000000000031956905b8a7558c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/cbyY1G95vUTrtgQTI_UNmCt5Z64>
Subject: Re: [calsify] Hebrew Adar II - "6L" or "6" ?
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2021 22:21:54 -0000

--00000000000031956905b8a7558c
Content-Type: text/plain; charset="UTF-8"

Does RFC 7529 offer a solution to the date *formatting* use case mentioned
above, or is this problem considered out of scope?

For example, if I am asked to present a localized string representing RFC
7529 Hebrew month "6", I do not have enough context to distinguish Adar
from Adar II.

On Mon, Jan 11, 2021 at 3:55 PM Ken Murchison <murch@fastmail.com> wrote:

> Adar (or Adar II in a leap year) is always month "6".  Adar I is "5L"
> since its inserted between "5" and "6".
>
>
> On 1/11/21 4:50 PM, Shane Carr wrote:
>
> Additional context: for the purposes of date *formatting*, it is useful
> for interchange to distinguish between Adar and Adar II.
>
> On Mon, Jan 11, 2021 at 3:44 PM Justin Grant <
> justingrant.ietf.public@gmail.com> wrote:
>
>> The Temporal team has a quick question about RFC 7529: is Hebrew month
>> Adar II (Adar in a leap year) referred to using "6L" or "6" according to
>> the spec?  I assume the latter (because they're the same month, just with a
>> different name) but wanted to make sure.
>>
>> Cheers,
>> Justin
>>
>> _______________________________________________
>> calsify mailing list
>> calsify@ietf.org
>> https://www.ietf.org/mailman/listinfo/calsify
>>
>
> _______________________________________________
> calsify mailing listcalsify@ietf.orghttps://www.ietf.org/mailman/listinfo/calsify
>
> --
> Kenneth Murchison
> Senior Software Developer
> Fastmail US LLC
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>

--00000000000031956905b8a7558c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Does RFC 7529 offer a solution to the date <i>formatting</=
i>=C2=A0use case mentioned above, or is this problem considered out of scop=
e?<div><br></div><div>For example, if I am asked to present a localized str=
ing representing RFC 7529 Hebrew month &quot;6&quot;, I do not have enough =
context to distinguish Adar from Adar II.</div></div><br><div class=3D"gmai=
l_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 11, 2021 at 3:55=
 PM Ken Murchison &lt;<a href=3D"mailto:murch@fastmail.com">murch@fastmail.=
com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x">
 =20
   =20
 =20
  <div>
    <p>Adar (or Adar II in a leap year) is always month &quot;6&quot;.=C2=
=A0 Adar I is
      &quot;5L&quot; since its inserted between &quot;5&quot; and &quot;6&q=
uot;.</p>
    <p><br>
    </p>
    <div>On 1/11/21 4:50 PM, Shane Carr wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">Additional context: for the purposes of date <i>form=
atting</i>,
        it is useful for interchange to distinguish between Adar and
        Adar II.</div>
      <br>
      <div class=3D"gmail_quote">
        <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 11, 2021 at 3:44
          PM Justin Grant &lt;<a href=3D"mailto:justingrant.ietf.public@gma=
il.com" target=3D"_blank">justingrant.ietf.public@gmail.com</a>&gt;
          wrote:<br>
        </div>
        <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div dir=3D"ltr">The Temporal team has a quick question about
            RFC 7529: is Hebrew month Adar II (Adar in a leap year)
            referred=C2=A0to using &quot;6L&quot; or &quot;6&quot; accordin=
g to the spec?=C2=A0 I
            assume the latter (because they&#39;re the same month, just wit=
h
            a different name) but wanted to make sure.
            <div><br>
            </div>
            <div>Cheers,</div>
            <div>Justin</div>
            <div><br>
            </div>
          </div>
          _______________________________________________<br>
          calsify mailing list<br>
          <a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify@iet=
f.org</a><br>
          <a href=3D"https://www.ietf.org/mailman/listinfo/calsify" rel=3D"=
noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/calsify=
</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset></fieldset>
      <pre>_______________________________________________
calsify mailing list
<a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/calsify" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/calsify</a>
</pre>
    </blockquote>
    <pre cols=3D"72">--=20
Kenneth Murchison
Senior Software Developer
Fastmail US LLC</pre>
  </div>

_______________________________________________<br>
calsify mailing list<br>
<a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/calsify" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/calsify</a><br>
</blockquote></div>

--00000000000031956905b8a7558c--


From nobody Mon Jan 11 14:30:39 2021
Return-Path: <murch@fastmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 346163A13F8 for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 14:30:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=FsJV+Bib; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=nD7oIolX
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tCfBwBq-1GMu for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 14:30:36 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50E613A137B for <calsify@ietf.org>; Mon, 11 Jan 2021 14:30:36 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 952B45C01DD; Mon, 11 Jan 2021 17:30:34 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Mon, 11 Jan 2021 17:30:34 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm1; bh=q6efXHi4zbB586faElBWlBJqldx gtz06B3d99Jyw6Z8=; b=FsJV+Bib7uTT4LTvipn4d7ZX5coOGrq0YLBi6Nns5Mp IvRoLZwn2ZEdkT8sWz9lCdtbKNEivtLl0p+74NGVnir7/8paX4zeJD2VaIM35ZOy r52mjsNzqqc8aT5ywI2xT0zp6WDB4kPZxT35tNfxhBmKIxSwCtG5v2mipQ/C/DAM 5c+HWCUCX0z3pyAY9ZQpdsIZuOr3tdT8BCegWsRPpCjQtNhnFG69pvRadhI3+402 JlBXktgZdze415D8S2BE9nq6oqKPlOLE82GY88H4FoBxgsFLk6fEHXFZ5ehW3L/m Kahp8UUQ2ex/MGPlK1WjjXpsM9gBRxeXEsfgL3gD6Zw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=q6efXH i4zbB586faElBWlBJqldxgtz06B3d99Jyw6Z8=; b=nD7oIolXQLT2Ms84AY338C Tz06WZh1pRmCdG4xzqc9NEYmstgjmyzJ+ihm41ih9pbp8P/LAb18NOBivcpGxid1 ZRXs6SKBqlaandXrtd8nQapW9J1sIfU/J4y/Ij6RVb0jB/NtroO1rW/QugxZdudr 64V8MjX3Eoe8sbRHbwwf7CjhWGm0Slpgn08dnPaPI7OgzXNNVSmBUYcA2knGniGu aVLm7b6sOQb9pSNxFpwTlnqW0+uf46Q9yr9n3lqhXlRgzqdpkNCROkN+Qqilecuh 66EEkJaX62pHe1jWJbNcg13AZ1GHkY3UiHOcwYNY9W8YbyfXYF3xRo7RpSszd1zQ ==
X-ME-Sender: <xms:itH8XxOwtqWTcU_cMRI5Xc_2T6dC3hj_IS8Ik6SHY3lxZr-TwixwPA> <xme:itH8XwT3KD5-skQEG_j7C5bgcVvV8J_ZGjUdA1sLB4xd_wrWnoT-w32S2RjfxCx0G tYSDEg2847CKg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrvdehuddgudeivdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhohfkffgfgggjtgesrg dtreertdefjeenucfhrhhomhepmfgvnhcuofhurhgthhhishhonhcuoehmuhhrtghhsehf rghsthhmrghilhdrtghomheqnecuggftrfgrthhtvghrnhepfffhvdekfeelvdeggfethe ffjeeuvdfgtdelvdehgeffgedvkeeukeelueehgeeinecuffhomhgrihhnpehivghtfhdr ohhrghenucfkphepjeegrdejjedrkeehrddvhedtnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepmhhurhgthhesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:itH8XzDODYSZjc4Pe435RKsR7QUg40St2sPigf08YAbMySdXkI0RoQ> <xmx:itH8X_iJ8y0R7P3k58E4DuMmO4aU2V-EQUrkJsoD_vmv9kZqWYDuzA> <xmx:itH8X8OEj9NQByQl5bAzPGwNpe_hGriJM2vAfdg6jCyDK_xJpy-1pA> <xmx:itH8Xz-F7yspMjo8bJcbZiog9vrLGoBr2Ms0vw0ZU76K99znoVUs0w>
Received: from localhost.localdomain (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 2EBF3108005F; Mon, 11 Jan 2021 17:30:34 -0500 (EST)
To: Shane Carr <sffc@google.com>
Cc: calsify@ietf.org
References: <CACy7Cfhb0kBdcyF+mpSd=cvRBoCzFBneB3V7r9vvasfNJwv6FA@mail.gmail.com> <CABxsp=ko+e+L7+=BFS8OxGQaPdq+N0uqL=X_4bvrNOEmd6edRw@mail.gmail.com> <3eea351a-9cc4-541b-6110-9889d8d1715a@fastmail.com> <CABxsp==y9f6+1gWvN2gnT+x6vSo3zW2TWQ135TwQt86S=4XvNg@mail.gmail.com>
From: Ken Murchison <murch@fastmail.com>
Organization: FastMail US LLC
Message-ID: <cabc2747-e7de-e2df-3002-d2e9983533b2@fastmail.com>
Date: Mon, 11 Jan 2021 17:30:33 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CABxsp==y9f6+1gWvN2gnT+x6vSo3zW2TWQ135TwQt86S=4XvNg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------5A8BA920F190F9136A25A819"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/e5pGX5QhV3KlotEvX9egJDeZh5g>
Subject: Re: [calsify] Hebrew Adar II - "6L" or "6" ?
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2021 22:30:38 -0000

This is a multi-part message in MIME format.
--------------5A8BA920F190F9136A25A819
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

RFC 7529 only addresses how to specify non-Gregorian calendar date parts 
for iCalendar recurrence rules.  All full dates are still specified in 
the Gregorian calendar using the ISO-like format specified in RFC 5545.

If you're looking for extensions to ISO 8601 or RFC 3339 date formats, 
RFC 7529 doesn't do that.


On 1/11/21 5:21 PM, Shane Carr wrote:
> Does RFC 7529 offer a solution to the date /formatting/ use case 
> mentioned above, or is this problem considered out of scope?
>
> For example, if I am asked to present a localized string representing 
> RFC 7529 Hebrew month "6", I do not have enough context to distinguish 
> Adar from Adar II.
>
> On Mon, Jan 11, 2021 at 3:55 PM Ken Murchison <murch@fastmail.com 
> <mailto:murch@fastmail.com>> wrote:
>
>     Adar (or Adar II in a leap year) is always month "6". Adar I is
>     "5L" since its inserted between "5" and "6".
>
>
>     On 1/11/21 4:50 PM, Shane Carr wrote:
>>     Additional context: for the purposes of date /formatting/, it is
>>     useful for interchange to distinguish between Adar and Adar II.
>>
>>     On Mon, Jan 11, 2021 at 3:44 PM Justin Grant
>>     <justingrant.ietf.public@gmail.com
>>     <mailto:justingrant.ietf.public@gmail.com>> wrote:
>>
>>         The Temporal team has a quick question about RFC 7529: is
>>         Hebrew month Adar II (Adar in a leap year) referred to using
>>         "6L" or "6" according to the spec?  I assume the latter
>>         (because they're the same month, just with a different name)
>>         but wanted to make sure.
>>
>>         Cheers,
>>         Justin
>>
>>         _______________________________________________
>>         calsify mailing list
>>         calsify@ietf.org <mailto:calsify@ietf.org>
>>         https://www.ietf.org/mailman/listinfo/calsify
>>         <https://www.ietf.org/mailman/listinfo/calsify>
>>
>>
>>     _______________________________________________
>>     calsify mailing list
>>     calsify@ietf.org  <mailto:calsify@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/calsify  <https://www.ietf.org/mailman/listinfo/calsify>
>
>     -- 
>     Kenneth Murchison
>     Senior Software Developer
>     Fastmail US LLC
>
>     _______________________________________________
>     calsify mailing list
>     calsify@ietf.org <mailto:calsify@ietf.org>
>     https://www.ietf.org/mailman/listinfo/calsify
>     <https://www.ietf.org/mailman/listinfo/calsify>
>
-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


--------------5A8BA920F190F9136A25A819
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>RFC 7529 only addresses how to specify non-Gregorian calendar
      date parts for iCalendar recurrence rules.  All full dates are
      still specified in the Gregorian calendar using the ISO-like
      format specified in RFC 5545.<br>
    </p>
    <p>If you're looking for extensions to ISO 8601 or RFC 3339 date
      formats, RFC 7529 doesn't do that.<br>
    </p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/11/21 5:21 PM, Shane Carr wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CABxsp==y9f6+1gWvN2gnT+x6vSo3zW2TWQ135TwQt86S=4XvNg@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Does RFC 7529 offer a solution to the date <i>formatting</i> use
        case mentioned above, or is this problem considered out of
        scope?
        <div><br>
        </div>
        <div>For example, if I am asked to present a localized string
          representing RFC 7529 Hebrew month "6", I do not have enough
          context to distinguish Adar from Adar II.</div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Mon, Jan 11, 2021 at 3:55
          PM Ken Murchison &lt;<a href="mailto:murch@fastmail.com"
            moz-do-not-send="true">murch@fastmail.com</a>&gt; wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div>
            <p>Adar (or Adar II in a leap year) is always month "6". 
              Adar I is "5L" since its inserted between "5" and "6".</p>
            <p><br>
            </p>
            <div>On 1/11/21 4:50 PM, Shane Carr wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="ltr">Additional context: for the purposes of
                date <i>formatting</i>, it is useful for interchange to
                distinguish between Adar and Adar II.</div>
              <br>
              <div class="gmail_quote">
                <div dir="ltr" class="gmail_attr">On Mon, Jan 11, 2021
                  at 3:44 PM Justin Grant &lt;<a
                    href="mailto:justingrant.ietf.public@gmail.com"
                    target="_blank" moz-do-not-send="true">justingrant.ietf.public@gmail.com</a>&gt;
                  wrote:<br>
                </div>
                <blockquote class="gmail_quote" style="margin:0px 0px
                  0px 0.8ex;border-left:1px solid
                  rgb(204,204,204);padding-left:1ex">
                  <div dir="ltr">The Temporal team has a quick question
                    about RFC 7529: is Hebrew month Adar II (Adar in a
                    leap year) referred to using "6L" or "6" according
                    to the spec?  I assume the latter (because they're
                    the same month, just with a different name) but
                    wanted to make sure.
                    <div><br>
                    </div>
                    <div>Cheers,</div>
                    <div>Justin</div>
                    <div><br>
                    </div>
                  </div>
                  _______________________________________________<br>
                  calsify mailing list<br>
                  <a href="mailto:calsify@ietf.org" target="_blank"
                    moz-do-not-send="true">calsify@ietf.org</a><br>
                  <a
                    href="https://www.ietf.org/mailman/listinfo/calsify"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/calsify</a><br>
                </blockquote>
              </div>
              <br>
              <fieldset></fieldset>
              <pre>_______________________________________________
calsify mailing list
<a href="mailto:calsify@ietf.org" target="_blank" moz-do-not-send="true">calsify@ietf.org</a>
<a href="https://www.ietf.org/mailman/listinfo/calsify" target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/calsify</a>
</pre>
            </blockquote>
            <pre cols="72">-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC</pre>
          </div>
          _______________________________________________<br>
          calsify mailing list<br>
          <a href="mailto:calsify@ietf.org" target="_blank"
            moz-do-not-send="true">calsify@ietf.org</a><br>
          <a href="https://www.ietf.org/mailman/listinfo/calsify"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/calsify</a><br>
        </blockquote>
      </div>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC</pre>
  </body>
</html>

--------------5A8BA920F190F9136A25A819--


From nobody Mon Jan 11 14:33:54 2021
Return-Path: <ryzokuken@igalia.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 584713A1405 for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 14:33:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=igalia.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ejwMxhNhipGG for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 14:33:42 -0800 (PST)
Received: from fanzine.igalia.com (fanzine.igalia.com [178.60.130.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25C8A3A1402 for <calsify@ietf.org>; Mon, 11 Jan 2021 14:33:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com;  s=20170329;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date:Message-ID:Subject:From:To; bh=1S/k4YJS5eAfSfEEwgMzO7fOOpDILiuRQZsAMkljM20=;  b=rd8Ju4BphtRHCM1RlM3axT7+qz2HvXOMqoJztWbBTXCRV1eYHVRaXa/zTkk5LkK+TIFvpQxyLbctaunmNKPbcGkrkR+JauYOy3YpVHZUXDdFEeCk6fmBY8Fc3NxhFXvBJpscwpL5ZsnoPCc2LkWFG2oB3iHc0t/6Zwi96JHalxDv0gbAWIU8Y/jSvvIGK3zjvrMVRCap6+0sJn7BRTl9itOccrgig5d3JtT+ZATRTZNLYMs+dlDgnVyW8WrNe2Ve5+O4o8CKtnjynIPUvlYF8XoKzcfJWON2S2IUJ3QfuJWzmYfQXY/oBW5JSQPKSvbkTIvvhlKPtwFnH4FK5xdrOQ==;
Received: from [183.83.211.77] (helo=[192.168.0.190]) by fanzine.igalia.com with esmtpsa  (Cipher TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim) id 1kz5ko-0006sp-S2 for <calsify@ietf.org>; Mon, 11 Jan 2021 23:33:39 +0100
To: "calsify@ietf.org" <calsify@ietf.org>
From: Ujjwal Sharma <ryzokuken@igalia.com>
Organization: Igalia S.L.
Message-ID: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com>
Date: Tue, 12 Jan 2021 04:03:26 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/Ys_THxv4HDloJaEBqGSicCk06V8>
Subject: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2021 22:33:45 -0000

Hi Calsify folks!

I am sorry for the long delay, I got a little sidetracked working on
other things, but I'm happy to inform you all that I have something that
resembles a first draft for the updated timestamps RFC.

Here's where you can find it:

Datatracker:
https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
GitHub: https://github.com/ryzokuken/draft-ryzokuken-datetime-extended

I would request you all to take a look at it when you can and let me
know what you think. You can file a GitHub issue or email me directly.

There's a few open discussions regarding the exact format and how the
interaction with bodies like the Unicode consortium work, so please feel
free to send me your thoughts regarding that as well.

Also, some references/bibliography is not perfectly functional yet
because I am still relatively new to authoring RFCs using Metanorma but
I'm actively looking into it.

Thanks and looking forward to hear from you,
Ujjwal

-- 
Ujjwal "Ryzokuken" Sharma (he/him)

Compilers Hacker, Node.js Core Collaborator and Speaker


From nobody Mon Jan 11 14:43:20 2021
Return-Path: <sla@ucolick.org>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B4223A141A for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 14:43:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.106
X-Spam-Level: 
X-Spam-Status: No, score=-1.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HD0Gzj4RScmv for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 14:43:17 -0800 (PST)
Received: from smtp.ucolick.org (unknown [128.114.23.234]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5485A3A141B for <calsify@ietf.org>; Mon, 11 Jan 2021 14:43:17 -0800 (PST)
Received: from smtp.ucolick.org (localhost [127.0.0.1]) by smtp.ucolick.org (Postfix) with ESMTP id 40DDF2A8F for <calsify@ietf.org>; Mon, 11 Jan 2021 14:43:16 -0800 (PST)
Received: from geneva.ucolick.org (geneva.ucolick.org [128.114.23.183]) by smtp.ucolick.org (Postfix) with ESMTP id 3D6A22744 for <calsify@ietf.org>; Mon, 11 Jan 2021 14:43:16 -0800 (PST)
Received: from geneva.ucolick.org (localhost [127.0.0.1]) by geneva.ucolick.org (Postfix) with ESMTP id 1E2286BE for <calsify@ietf.org>; Mon, 11 Jan 2021 14:43:16 -0800 (PST)
Received: (from sla@localhost) by geneva.ucolick.org (8.14.7/8.14.7/Submit) id 10BMhFB7020642 for calsify@ietf.org; Mon, 11 Jan 2021 14:43:15 -0800
Resent-From: Steve Allen <sla@ucolick.org>
Resent-Date: Mon, 11 Jan 2021 14:43:15 -0800
Resent-Message-ID: <20210111224315.GA20639@ucolick.org>
Resent-To: "calsify@ietf.org" <calsify@ietf.org>
X-Original-To: sla@ucolick.org
Delivered-To: sla@ucolick.org
Received: from smtp.ucolick.org (hunan.ucolick.org [128.114.23.233]) by delivery.ucolick.org (Postfix) with ESMTP id 0D36E1DEB5 for <sla@ucolick.org>; Mon, 11 Jan 2021 14:42:44 -0800 (PST)
Received: from smtp.ucolick.org (localhost [127.0.0.1]) by smtp.ucolick.org (Postfix) with ESMTP id 022142781; Mon, 11 Jan 2021 14:42:44 -0800 (PST)
Received: from geneva.ucolick.org (geneva.ucolick.org [128.114.23.183]) by smtp.ucolick.org (Postfix) with ESMTP id F37932732; Mon, 11 Jan 2021 14:42:43 -0800 (PST)
Received: from geneva.ucolick.org (localhost [127.0.0.1]) by geneva.ucolick.org (Postfix) with ESMTP id DE2FC6BE; Mon, 11 Jan 2021 14:42:43 -0800 (PST)
Received: (from sla@localhost) by geneva.ucolick.org (8.14.7/8.14.7/Submit) id 10BMggE8020626; Mon, 11 Jan 2021 14:42:42 -0800
Date: Mon, 11 Jan 2021 14:42:42 -0800
From: Steve Allen <sla@ucolick.org>
To: Ujjwal Sharma <ryzokuken@igalia.com>
Message-ID: <20210111224242.GA20167@ucolick.org>
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com>
User-Agent: Mutt/1.9.2 (2017-12-15)
X-DSPAM-Result: Whitelisted
X-DSPAM-Processed: Mon Jan 11 14:42:44 2021
X-DSPAM-Confidence: 0.9997
X-DSPAM-Probability: 0.0000
X-DSPAM-Signature: 191,5ffcd46412617673529933
X-DSPAM-Factors: 27, hath+writ, 0.00010, WGS+84, 0.00010, Received*(from+sla, 0.00010, Allen+<sla, 0.00010, 84+(GPS), 0.00010, UCO/Lick, 0.00010, User-Agent*12, 0.00010, 165+Lat, 0.00010, Lng, 0.00010, Received*geneva.ucolick.org, 0.00010, Received*geneva.ucolick.org, 0.00010, 831+459, 0.00010, Cruz+CA, 0.00010, Room+165, 0.00010, 99855, 0.00010, Received*(from, 0.00010, Url*org/~sla/, 0.00010, 36+99855, 0.00010, From*Allen+<sla, 0.00010, Received*by+geneva.ucolick.org, 0.00010, Received*by+geneva.ucolick.org, 0.00010, User-Agent*12+15), 0.00010, ISB+260, 0.00010, User-Agent*15), 0.00010, 459+3046, 0.00010, Natural+Sciences, 0.00010, (GPS)+UCO/Lick, 0.00010
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/jlgI3Sa2xM7e_8vmincAJUgghPk>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2021 22:43:18 -0000

On Tue 2021-01-12T04:03:26+0530 Ujjwal Sharma hath writ:
> Datatracker:
> https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
> GitHub: https://github.com/ryzokuken/draft-ryzokuken-datetime-extended

The term "UTC" was not in use and has no defined meaning prior to 1960.
No radio broadcast time signals were coordinated until April of 1960.
Before 1960 there can only be UT; there cannot be UTC.

This document needs to define the meaning of time using a term other
than UTC for any date prior to 1960.

--
Steve Allen                    <sla@ucolick.org>              WGS-84 (GPS)
UCO/Lick Observatory--ISB 260  Natural Sciences II, Room 165  Lat  +36.99855
1156 High Street               Voice: +1 831 459 3046         Lng -122.06015
Santa Cruz, CA 95064           https://www.ucolick.org/~sla/  Hgt +250 m


From nobody Mon Jan 11 14:56:30 2021
Return-Path: <sla@ucolick.org>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4E213A14F3 for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 14:56:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.126
X-Spam-Level: 
X-Spam-Status: No, score=-1.126 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SErXvUmVAbgM for <calsify@ietfa.amsl.com>; Mon, 11 Jan 2021 14:56:28 -0800 (PST)
Received: from smtp.ucolick.org (unknown [128.114.23.233]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A83FC3A14F0 for <calsify@ietf.org>; Mon, 11 Jan 2021 14:56:28 -0800 (PST)
Received: from smtp.ucolick.org (localhost [127.0.0.1]) by smtp.ucolick.org (Postfix) with ESMTP id 85E932781 for <calsify@ietf.org>; Mon, 11 Jan 2021 14:56:27 -0800 (PST)
Received: from geneva.ucolick.org (geneva.ucolick.org [128.114.23.183]) by smtp.ucolick.org (Postfix) with ESMTP id 830DD2732 for <calsify@ietf.org>; Mon, 11 Jan 2021 14:56:27 -0800 (PST)
Received: from geneva.ucolick.org (localhost [127.0.0.1]) by geneva.ucolick.org (Postfix) with ESMTP id 6B26F6BE for <calsify@ietf.org>; Mon, 11 Jan 2021 14:56:27 -0800 (PST)
Received: (from sla@localhost) by geneva.ucolick.org (8.14.7/8.14.7/Submit) id 10BMuRNS020935 for calsify@ietf.org; Mon, 11 Jan 2021 14:56:27 -0800
Date: Mon, 11 Jan 2021 14:56:27 -0800
From: Steve Allen <sla@ucolick.org>
To: "calsify@ietf.org" <calsify@ietf.org>
Message-ID: <20210111225627.GA20807@ucolick.org>
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com>
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/spaTKn4z-WY90q4utDKa-fOP3Mg>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2021 22:56:30 -0000

On Tue 2021-01-12T04:03:26+0530 Ujjwal Sharma hath writ:
> Datatracker:
> https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
> GitHub: https://github.com/ryzokuken/draft-ryzokuken-datetime-extended

The term "UTC" was not in use and has no defined meaning prior to 1960.
No radio broadcast time signals were coordinated until April of 1960.
Before 1960 there can only be UT; there cannot be UTC.

This document needs to define the meaning of time using a term other
than UTC for any date prior to 1960.

--
Steve Allen                    <sla@ucolick.org>              WGS-84 (GPS)
UCO/Lick Observatory--ISB 260  Natural Sciences II, Room 165  Lat  +36.99855
1156 High Street               Voice: +1 831 459 3046         Lng -122.06015
Santa Cruz, CA 95064           https://www.ucolick.org/~sla/  Hgt +250 m


From nobody Wed Jan 13 08:54:28 2021
Return-Path: <mikeadouglass@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31D493A11D3; Wed, 13 Jan 2021 08:54:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.359
X-Spam-Level: 
X-Spam-Status: No, score=-2.359 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eu4mSni5Tdds; Wed, 13 Jan 2021 08:54:23 -0800 (PST)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F01923A11CA; Wed, 13 Jan 2021 08:54:22 -0800 (PST)
Received: by mail-qt1-x830.google.com with SMTP id z9so1538287qtn.4; Wed, 13 Jan 2021 08:54:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=kR1SXpNsSt2QNE2L4F74t+K1IPrCMP0ZXgkVFqFOD5U=; b=kmaQ3hHILaysrY2BfTnDN+RNBdQpIugnWJO8AS3WTYgx9hdwdFojyB/AB2lKtXX+4B /bE+CGJ0a7JsxmdPqaStErFiEtYzCI8f8Mfann986T4V+Vp7EtywdnBLLfzQf+tDtLsD hZsfJgl2eRpb2zstWQkIGGYHdBywWvme7xr1bo52h3gC0dGsPxuWrhM6N5APnnpW2mRZ 1WwmgdPOznLbWGfhIKjakquFFCwE6L6VLGt0xM/DkWYZIxyM14EY4g0B6wWAPN2jH2Np SjtEyl9C19atWCvygIN+8HnKfWQjGWZC2sZivP25kHDMciavBxMBZV9wp3zLhOotB0gK SNow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=kR1SXpNsSt2QNE2L4F74t+K1IPrCMP0ZXgkVFqFOD5U=; b=qHTe6Vj4FQZTVrno97nAkw5l4FO0mNGZNEzlSTBadCbHlQYxJu5h+lRCgdIIbd7+0R L/dhm5jKuNBK/x1FvkAqLsRMjXFQmAh4HzxR4+1JKi0lzNxA0mfRAlhP16TzJtYIb2vF 31srY8G+6jIarj2x7tg0M3jy/ZnmxgDMTJnjXWw4rK0cdcd9iIpJUdEICGURGS3GBk+Z q/HwAXL2vLJs14im/H5lntXieMhZdNh6+eftF85C9CcAkdTF5RDrYT4vOfR6kX6asWqf XxqTMafJQULiugdx1PUfkSW+ewdmrPQxpc86W79veZatc7bmx5XV4Sgg+rgBakCeWcSD gTQw==
X-Gm-Message-State: AOAM530I+fbf26zouFyzjA4t0tEms6TGXpDqgpQmHMAe5SQbOyxeppdL E13dOWtqeNzVyCbFoSr2uKGmwAXa70JKaA==
X-Google-Smtp-Source: ABdhPJxUNqoOA9SVYnAoGpqQtDftlIRZkY6i4ySlclpF9PxVL5+26UGn3zQoUmmoDGC1sqYNgvvbqQ==
X-Received: by 2002:ac8:47da:: with SMTP id d26mr3074411qtr.4.1610556861303; Wed, 13 Jan 2021 08:54:21 -0800 (PST)
Received: from [192.168.1.151] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id c2sm1344761qke.109.2021.01.13.08.54.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 13 Jan 2021 08:54:20 -0800 (PST)
From: Michael Douglass <mikeadouglass@gmail.com>
To: Murray Kucherawy <superuser@gmail.com>, The IESG <iesg@ietf.org>
Cc: draft-ietf-calext-eventpub-extensions@ietf.org, calext-chairs@ietf.org, calsify@ietf.org
References: <160978944264.1715.14149807055782718055@ietfa.amsl.com>
Message-ID: <96f3b03b-fae9-0b90-8980-46c81c9b0bf5@gmail.com>
Date: Wed, 13 Jan 2021 11:54:19 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <160978944264.1715.14149807055782718055@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------4143E2BAD0BDC49360C3AC5B"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/rRtgX_wbnaUMFgOaDgGvxsF9b1Y>
Subject: Re: [calsify] Murray Kucherawy's No Objection on draft-ietf-calext-eventpub-extensions-17: (with COMMENT)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 16:54:26 -0000

This is a multi-part message in MIME format.
--------------4143E2BAD0BDC49360C3AC5B
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


On 1/4/21 14:44, Murray Kucherawy via Datatracker wrote:
> Murray Kucherawy has entered the following ballot position for
> draft-ietf-calext-eventpub-extensions-17: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer tohttps://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Section 1.2 says "For example, we may want to record who is participating in a
> public event", but the Privacy Considerations section doesn't say anything
> about the fact that this could collect data about people who are interested in
> the event, even if they don't go (though the location issue is mentioned).
> Also, especially since 2020, the public event could be a purely online event,
> where location data isn't part of the issue.  (Alternatively, if this is meant
> to address in-person events only, that would be useful to say up front.)

I'll add some extra text- Something like:

OLD

The addition of location information to the new participant component
provides information about the location of participants at a given
time.  This information MUST NOT be distributed to other participants
without that participants express permission.  Agents processing and
distributing calendar data must be aware that it has the property of
providing information about a future time when a given individual may
be at a particular location, which could enable targeted attacks
against that individual.

NEW

   The addition of location information to the new participant
   component provides information about the location of
   participants at a given time. This information MUST NOT be
   distributed to other participants without those participants
   express permission. Note that there may be a number of
   participants who may be unaware of their inclusion in the
   data.

   Agents processing and distributing
   calendar data must be aware that it has the property of
   providing information about a future time when a given
   individual may be at a particular location, which could
   enable targeted attacks against that individual.

END

> Section 6.2 (and other sections, but I noticed it here): ABNF literal strings
> are case-insensitive.  That means, for example, that the ABNF here would allow
> "ACTIVE" for a "partvalue", but would also allow "active", "AcTiVe", etc.  Is
> that acceptable?  (This probably applies to lots of prior CALEXT documents -- I
> admittedly didn't check -- so it may not be worth fixing here.)

I've been working on my ical4j implementation of this and I was having 
the same thoughts.

I looked at rfc4589 - the location types registry - and all the values 
are lower case. There doesn't appear to be any text to specify whether 
or not they are case sensitive values.

5545 says in section 2 "enumerated property values, and property 
parameter values are case-insensitive." - thus ACTIVE and aCtIvE are 
intended to be the same.

However, jscalendar - which we need to be able to map to and from 
says:(Section 3) "Property names and values are case-sensitive."

So 4589 doesn't say anything, 5545 says insensitive jscalendar says 
sensitive.

I'm inclined to at least redo the participant and resource types in 
lower case. jscalendar has a lot of places where it uses the icalendar 
converted to lower case.


> Section 6.4:
>
>     Property Parameters:  IANA, or non-standard property parameters can
>        be specified on this property.
>
> I think that should be "IANA-registered"?  Same issue in Sections 6.5 and 6.6.
Fixed
> Section 7: I believe the ABNF here needs a once-over.
Barry had some fixes I will apply
> Section 9.2: For the threat described in the first paragraph, are there any
> possible mitigations to suggest?
Added some text
> Section 10.2: In "without that participants express permission", that should be
> "participant's".  There's also a period missing at the end of the second last
> paragraph, though as it reads, it's possible there's even some intended text
> missing.
Fixed
> Section 11.2: The rules for making registrations into both the existing
> registries and these new ones are striking.  RFC 8126 doesn't even create a
> category that is a combination of Expert Review and Standards Action, but
> that's what this spells out.  And I wonder what would happen if we were to
> publish a Standards Track RFC (which has IETF consensus) with which the
> Designated Expert disagreed.  I'm not asking for anything to change here given
> that consistency with the existing registries is probably desirable, but it
> does set an unusually high bar for registrations.

I'm inclined to agree - with all the points. If the general feeling is I 
should come up with more manageable constraints I can do that.

>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify

--------------4143E2BAD0BDC49360C3AC5B
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/4/21 14:44, Murray Kucherawy via
      Datatracker wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:160978944264.1715.14149807055782718055@ietfa.amsl.com">
      <pre class="moz-quote-pre" wrap="">Murray Kucherawy has entered the following ballot position for
draft-ietf-calext-eventpub-extensions-17: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to <a class="moz-txt-link-freetext" href="https://www.ietf.org/iesg/statement/discuss-criteria.html">https://www.ietf.org/iesg/statement/discuss-criteria.html</a>
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/">https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/</a>



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Section 1.2 says "For example, we may want to record who is participating in a
public event", but the Privacy Considerations section doesn't say anything
about the fact that this could collect data about people who are interested in
the event, even if they don't go (though the location issue is mentioned). 
Also, especially since 2020, the public event could be a purely online event,
where location data isn't part of the issue.  (Alternatively, if this is meant
to address in-person events only, that would be useful to say up front.)</pre>
    </blockquote>
    <p>I'll add some extra text- Something like:</p>
    <p>OLD</p>
    <pre style="background-color:#ffffff;color:#080808;font-family:'JetBrains Mono',monospace;font-size:9.8pt;">The addition of location information to the new participant component
provides information about the location of participants at a given
time.  This information MUST NOT be distributed to other participants
without that participants express permission.  Agents processing and
distributing calendar data must be aware that it has the property of
providing information about a future time when a given individual may
be at a particular location, which could enable targeted attacks
against that individual.
</pre>
    <p>NEW</p>
    <pre style="background-color:#ffffff;color:#080808;font-family:'JetBrains Mono',monospace;font-size:9.8pt;">  The addition of location information to the new participant
  component provides information about the location of
  participants at a given time. This information MUST NOT be
  distributed to other participants without those participants
  express permission. Note that there may be a number of
  participants who may be unaware of their inclusion in the
  data.

  Agents processing and distributing
  calendar data must be aware that it has the property of
  providing information about a future time when a given
  individual may be at a particular location, which could
  enable targeted attacks against that individual.
</pre>
    <p>END<br>
    </p>
    <blockquote type="cite"
      cite="mid:160978944264.1715.14149807055782718055@ietfa.amsl.com">
      <pre class="moz-quote-pre" wrap="">Section 6.2 (and other sections, but I noticed it here): ABNF literal strings
are case-insensitive.  That means, for example, that the ABNF here would allow
"ACTIVE" for a "partvalue", but would also allow "active", "AcTiVe", etc.  Is
that acceptable?  (This probably applies to lots of prior CALEXT documents -- I
admittedly didn't check -- so it may not be worth fixing here.)</pre>
    </blockquote>
    <p>I've been working on my ical4j implementation of this and I was
      having the same thoughts.</p>
    <p>I looked at rfc4589 - the location types registry - and all the
      values are lower case. There doesn't appear to be any text to
      specify whether or not they are case sensitive values.</p>
    <p>5545 says in section 2 "enumerated property values, and property
      parameter values are case-insensitive." - thus ACTIVE and aCtIvE
      are intended to be the same.</p>
    <p>However, jscalendar - which we need to be able to map to and from
      says:(Section 3) "Property names and values are case-sensitive."</p>
    <p>So 4589 doesn't say anything, 5545 says insensitive jscalendar
      says sensitive.</p>
    <p>I'm inclined to at least redo the participant and resource types
      in lower case. jscalendar has a lot of places where it uses the
      icalendar converted to lower case.  <br>
    </p>
    <p><br>
    </p>
    <blockquote type="cite"
      cite="mid:160978944264.1715.14149807055782718055@ietfa.amsl.com">
      <pre class="moz-quote-pre" wrap="">Section 6.4:

   Property Parameters:  IANA, or non-standard property parameters can
      be specified on this property.

I think that should be "IANA-registered"?  Same issue in Sections 6.5 and 6.6.</pre>
    </blockquote>
    Fixed<br>
    <blockquote type="cite"
      cite="mid:160978944264.1715.14149807055782718055@ietfa.amsl.com">
      <pre class="moz-quote-pre" wrap="">Section 7: I believe the ABNF here needs a once-over.</pre>
    </blockquote>
    Barry had some fixes I will apply<br>
    <blockquote type="cite"
      cite="mid:160978944264.1715.14149807055782718055@ietfa.amsl.com">
      <pre class="moz-quote-pre" wrap="">Section 9.2: For the threat described in the first paragraph, are there any
possible mitigations to suggest?</pre>
    </blockquote>
    Added some text<br>
    <blockquote type="cite"
      cite="mid:160978944264.1715.14149807055782718055@ietfa.amsl.com">
      <pre class="moz-quote-pre" wrap="">Section 10.2: In "without that participants express permission", that should be
"participant's".  There's also a period missing at the end of the second last
paragraph, though as it reads, it's possible there's even some intended text
missing.</pre>
    </blockquote>
    Fixed<br>
    <blockquote type="cite"
      cite="mid:160978944264.1715.14149807055782718055@ietfa.amsl.com">
      <pre class="moz-quote-pre" wrap="">Section 11.2: The rules for making registrations into both the existing
registries and these new ones are striking.  RFC 8126 doesn't even create a
category that is a combination of Expert Review and Standards Action, but
that's what this spells out.  And I wonder what would happen if we were to
publish a Standards Track RFC (which has IETF consensus) with which the
Designated Expert disagreed.  I'm not asking for anything to change here given
that consistency with the existing registries is probably desirable, but it
does set an unusually high bar for registrations.</pre>
    </blockquote>
    <p>I'm inclined to agree - with all the points. If the general
      feeling is I should come up with more manageable constraints I can
      do that.<br>
    </p>
    <blockquote type="cite"
      cite="mid:160978944264.1715.14149807055782718055@ietfa.amsl.com">
      <pre class="moz-quote-pre" wrap="">

_______________________________________________
calsify mailing list
<a class="moz-txt-link-abbreviated" href="mailto:calsify@ietf.org">calsify@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/calsify">https://www.ietf.org/mailman/listinfo/calsify</a>
</pre>
    </blockquote>
  </body>
</html>

--------------4143E2BAD0BDC49360C3AC5B--


From nobody Wed Jan 13 09:13:55 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 435CA3A1215; Wed, 13 Jan 2021 09:13:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.403
X-Spam-Level: 
X-Spam-Status: No, score=-1.403 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AvTyS2nGu0Tt; Wed, 13 Jan 2021 09:13:52 -0800 (PST)
Received: from mail-lf1-f43.google.com (mail-lf1-f43.google.com [209.85.167.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD30C3A1208; Wed, 13 Jan 2021 09:13:51 -0800 (PST)
Received: by mail-lf1-f43.google.com with SMTP id s26so3846817lfc.8; Wed, 13 Jan 2021 09:13:51 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=vjZw6XVNh43r3EtmFkGIGPD3BlAGkqKk68Y3/1qoAfg=; b=ZPYGgy30RltQh/MU2Qe+u20U5DrmdPV9jflD/NPxmGWzGXOhbUsL/rcmRlLhCVfHiW IrD5RaujxBv1JwmgahlqYpS4FZ/IMwr7HpWE/7L9h18fbyEApRx9XciIJFsuutx3GZ2Z NravmhtYlB7JV5eYgXaEkI5PyDN896rAzefhdzkKNG4RyxJ+A9kSF78rwMSUhgCdvsu7 42XqJEq7Ac5lrqJLCa7Cn6ojnpcU9DtJEhcNrhObcskN/c9PwEcUJsbg4St63+VT1eHX ig8ghjctMEGKxL2KfUYXf06zJa8AkDgPZ3jUHjJ2P9vkk7E/BNXUKXLJQ4/iaTwlgF2E SAtA==
X-Gm-Message-State: AOAM532KMShGdXcx9WAfEBXaQsvGgl83+swrpa8pca78mNZBN1DHlTy9 Y/XFNGeuNNjO2KThO++ndO9j1wcdQ6T7M3/LJGSBpk9w
X-Google-Smtp-Source: ABdhPJxtk3GmVlPpkHhmY0s3lqe5B5lCI3IweRG44IQg4+s9MPX477SbbwNzX0Y0Dqha5w9sLq5FyWlMRRH7MqAZUr4=
X-Received: by 2002:ac2:454e:: with SMTP id j14mr1261979lfm.123.1610558029569;  Wed, 13 Jan 2021 09:13:49 -0800 (PST)
MIME-Version: 1.0
References: <160978944264.1715.14149807055782718055@ietfa.amsl.com> <96f3b03b-fae9-0b90-8980-46c81c9b0bf5@gmail.com>
In-Reply-To: <96f3b03b-fae9-0b90-8980-46c81c9b0bf5@gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Wed, 13 Jan 2021 12:13:38 -0500
Message-ID: <CALaySJ+KOwORu8gTZaRTdDWE+MDefFqZz03pHYtGL6r0=TvQKA@mail.gmail.com>
To: Michael Douglass <mikeadouglass@gmail.com>
Cc: Murray Kucherawy <superuser@gmail.com>, The IESG <iesg@ietf.org>,  draft-ietf-calext-eventpub-extensions@ietf.org, calext-chairs@ietf.org,  calsify@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/9Xa7HJ-IMi7x9_ibLkKxIalKMjE>
Subject: Re: [calsify] Murray Kucherawy's No Objection on draft-ietf-calext-eventpub-extensions-17: (with COMMENT)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 17:13:53 -0000

> 5545 says in section 2 "enumerated property values, and property parameter values are case-insensitive."
> - thus ACTIVE and aCtIvE are intended to be the same.
>
> However, jscalendar - which we need to be able to map to and from says:(Section 3) "Property names and
> values are case-sensitive."

I don't see a problem here: clearly, mapping from iCalendar to
jsCalendar will fold to lower case, and mapping from jsCalendar to
iCalendar will preserve lower case.  Do you see a problem (as opposed
to a "Gee, why did we make them different?" question)?

> Section 11.2: The rules for making registrations into both the existing
> registries and these new ones are striking.  RFC 8126 doesn't even create a
> category that is a combination of Expert Review and Standards Action, but
> that's what this spells out.  And I wonder what would happen if we were to
> publish a Standards Track RFC (which has IETF consensus) with which the
> Designated Expert disagreed.  I'm not asking for anything to change here given
> that consistency with the existing registries is probably desirable, but it
> does set an unusually high bar for registrations.
>
> I'm inclined to agree - with all the points. If the general feeling is I should come up with more manageable
> constraints I can do that.

As I've said to Murray off list, I think this is a broader issue that
we should fix in an update of 5545, rather than trying to fix it here.
You aren't actually specifying registration policies in this document,
but are instead using the registration policies in the base iCalendar
by reference.  I think that's the right way to go for now.

Barry


From nobody Wed Jan 13 09:32:08 2021
Return-Path: <mikeadouglass@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDDC43A1234; Wed, 13 Jan 2021 09:32:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0hXi468ruUGm; Wed, 13 Jan 2021 09:32:00 -0800 (PST)
Received: from mail-qv1-xf36.google.com (mail-qv1-xf36.google.com [IPv6:2607:f8b0:4864:20::f36]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAE893A1220; Wed, 13 Jan 2021 09:31:59 -0800 (PST)
Received: by mail-qv1-xf36.google.com with SMTP id p5so1117882qvs.7; Wed, 13 Jan 2021 09:31:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=UtZ/dN2Xck155CGi+ehylQgwIieowPov8KbZVEldkG8=; b=QeI3hDP1FqtcZSMIR1T61TaFEa85p2kNP29vDRejiPx9fSMxFFP20bb6nUvbfDTZsj 0TQ4L7rWvbo9lT3iAiJC9TA59EHlj5xzOdNNcogfEChJrjKEp4WBG5o2HrSM53WS3lzG kJ2azmgdNNCLiwNf+zMu9H1klSri3006crTSm7NSpZPOX7x1wkKadZ9V5sw8Rhjp+fdI irRVaUYGLLNWSqG/AG7NEWFfvODudcYRJip2wVoXUdTdpXcHfQdZUQ55OXJL/PwnSjk4 4Fq8+g360A2CWRuWMO2xQrDlltINpfin89OTtQmsMZerYyUgGVY+tN+87xIajWo4lEXD XmKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=UtZ/dN2Xck155CGi+ehylQgwIieowPov8KbZVEldkG8=; b=DOFUC9Y3ow6Bb3xW5hIm6op7cYYTF1aZ7hYFMxwfyyIqThKyK9xjR2uJVgXfRq6PzU 0uzU3oWdBGViBEV9+m79b3ysxSMR+PC97cTbZv5tU4kf7FPlhgyAoS5aLfMNqEdAwy1H keou2b7//N6XahPOFPPaDAgCRCHkGS4ZvJHfIdoyd9iB9rwmgAJ8f8jaOPPQyQQ2WfbF lt4OMHMmQ4EvLqajm5BNeell7FPPWQ6cmZ5nSXI1TvoD/vMn0IJBYKoNnTX5xNe/055H bA00rda/dkCX+560kQ0dwfMBuD3jEHJ9RCZfSdfCg1BVqDTq39yDMo/G4ntyXCNv3UXj WwTg==
X-Gm-Message-State: AOAM5321A1DoE8BUTavTqlQRy5/AcDN5+1kRxRFBlQgrnZBpJCZGK6Is j85JJMo5HNsunTzMiGH8K0i/TrBKqlUveA==
X-Google-Smtp-Source: ABdhPJwIhXwSO3DoGHmo99g39rNhw8JRs6VBjrPUK2dv9DtZHOgNvKEAyvGyD0YtA/a2Va2cxzDuRA==
X-Received: by 2002:ad4:4e09:: with SMTP id dl9mr3154362qvb.44.1610559118180;  Wed, 13 Jan 2021 09:31:58 -0800 (PST)
Received: from [192.168.1.151] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id q70sm1412698qka.107.2021.01.13.09.31.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 13 Jan 2021 09:31:57 -0800 (PST)
To: Barry Leiba <barryleiba@computer.org>
Cc: Murray Kucherawy <superuser@gmail.com>, The IESG <iesg@ietf.org>, draft-ietf-calext-eventpub-extensions@ietf.org, calext-chairs@ietf.org, calsify@ietf.org
References: <160978944264.1715.14149807055782718055@ietfa.amsl.com> <96f3b03b-fae9-0b90-8980-46c81c9b0bf5@gmail.com> <CALaySJ+KOwORu8gTZaRTdDWE+MDefFqZz03pHYtGL6r0=TvQKA@mail.gmail.com>
From: Michael Douglass <mikeadouglass@gmail.com>
Message-ID: <a79c4db0-c137-caa4-5335-13185f1ed6d9@gmail.com>
Date: Wed, 13 Jan 2021 12:31:56 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CALaySJ+KOwORu8gTZaRTdDWE+MDefFqZz03pHYtGL6r0=TvQKA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/cNfIeYyz6ydmCEPf2vXXd8ZBA-c>
Subject: Re: [calsify] Murray Kucherawy's No Objection on draft-ietf-calext-eventpub-extensions-17: (with COMMENT)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 17:32:03 -0000

On 1/13/21 12:13, Barry Leiba wrote:
>> 5545 says in section 2 "enumerated property values, and property parameter values are case-insensitive."
>> - thus ACTIVE and aCtIvE are intended to be the same.
>>
>> However, jscalendar - which we need to be able to map to and from says:(Section 3) "Property names and
>> values are case-sensitive."
> I don't see a problem here: clearly, mapping from iCalendar to
> jsCalendar will fold to lower case, and mapping from jsCalendar to
> iCalendar will preserve lower case.  Do you see a problem (as opposed
> to a "Gee, why did we make them different?" question)?

I think it was an uncompleted thought. The relations draft uses link 
relations and it turns out they are specified to be case-insensitive 
(https://tools.ietf.org/html/rfc8288 section 2.1.1) so we have values 
like (from 
https://www.iana.org/assignments/link-relations/link-relations.xhtml) 
"convertedFrom".

It just feels like we have no consistency across standards in how values 
like these should be matched. I'm inclined to think case-insensitivity 
is the only safe option.


>
>> Section 11.2: The rules for making registrations into both the existing
>> registries and these new ones are striking.  RFC 8126 doesn't even create a
>> category that is a combination of Expert Review and Standards Action, but
>> that's what this spells out.  And I wonder what would happen if we were to
>> publish a Standards Track RFC (which has IETF consensus) with which the
>> Designated Expert disagreed.  I'm not asking for anything to change here given
>> that consistency with the existing registries is probably desirable, but it
>> does set an unusually high bar for registrations.
>>
>> I'm inclined to agree - with all the points. If the general feeling is I should come up with more manageable
>> constraints I can do that.
> As I've said to Murray off list, I think this is a broader issue that
> we should fix in an update of 5545, rather than trying to fix it here.
> You aren't actually specifying registration policies in this document,
> but are instead using the registration policies in the base iCalendar
> by reference.  I think that's the right way to go for now.
Good.
>
> Barry


From nobody Wed Jan 13 10:25:30 2021
Return-Path: <ryzokuken@igalia.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40C493A12DA for <calsify@ietfa.amsl.com>; Wed, 13 Jan 2021 10:25:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level: 
X-Spam-Status: No, score=-2.361 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=igalia.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H767U2WuSUXt for <calsify@ietfa.amsl.com>; Wed, 13 Jan 2021 10:25:19 -0800 (PST)
Received: from fanzine.igalia.com (fanzine.igalia.com [178.60.130.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A725F3A12E5 for <calsify@ietf.org>; Wed, 13 Jan 2021 10:25:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com;  s=20170329;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:References:To:From:Subject; bh=kTbMDGsI1jDPB4bFnr8Qd11B7ltCMvQNv7nus95E8Sw=;  b=VntnFogxsAIYDaK6khZKFpy15gx8mvh8/lDzliaBmd/iU/mfybIUOZ1mAGeYpl8uZVvHryL1TXrQf+RekWvbdkugeOAfr8jvpx9mqJJ44PAy3IKmdy9B85gn8JWDTucIhCysiZnFKamnKj++boIaox4TGtiXFR9Al/9cBYR6Gi0xFn9CvwGER52kCxqRcO6jzo0BacqbgOLo1fPDOQmo1fPbdN6jmrVqcTLv/zR11fu8m/pu85HGYI+fHQMm4MxbnEuWTkXFpaLbjLWbO8knBUBuGX4+QQkmSyRfSx9Nj6ddZ+2oDwCVsPc9uNqW+xIzg1AHTX2pUNRHwrBrme3AyA==;
Received: from [45.122.44.244] (helo=[192.168.0.110]) by fanzine.igalia.com with esmtpsa  (Cipher TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim) id 1kzkpS-0005kQ-9m for <calsify@ietf.org>; Wed, 13 Jan 2021 19:25:10 +0100
From: Ujjwal Sharma <ryzokuken@igalia.com>
To: "calsify@ietf.org" <calsify@ietf.org>
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com>
Organization: Igalia S.L.
Message-ID: <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com>
Date: Wed, 13 Jan 2021 23:54:39 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/ozRSwkz5Y-qppdYS_0VNc82iIBM>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 18:25:28 -0000

One question: given things move forward smoothly, how do I proceed?
Should I apply for this document to be adopted by the calext WG? I
suppose the fastest way to proceed is to present it at the next IETF
meeting?



Ujjwal

On 12/01/2021 4.03 am, Ujjwal Sharma wrote:
> Hi Calsify folks!
> 
> I am sorry for the long delay, I got a little sidetracked working on
> other things, but I'm happy to inform you all that I have something that
> resembles a first draft for the updated timestamps RFC.
> 
> Here's where you can find it:
> 
> Datatracker:
> https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
> GitHub: https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
> 
> I would request you all to take a look at it when you can and let me
> know what you think. You can file a GitHub issue or email me directly.
> 
> There's a few open discussions regarding the exact format and how the
> interaction with bodies like the Unicode consortium work, so please feel
> free to send me your thoughts regarding that as well.
> 
> Also, some references/bibliography is not perfectly functional yet
> because I am still relatively new to authoring RFCs using Metanorma but
> I'm actively looking into it.
> 
> Thanks and looking forward to hear from you,
> Ujjwal
> 

-- 
Ujjwal "Ryzokuken" Sharma (he/him)

Compilers Hacker, Node.js Core Collaborator and Speaker


From nobody Wed Jan 13 12:52:54 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 51EC53A1375; Wed, 13 Jan 2021 12:52:49 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: calsify@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: calsify@ietf.org
Message-ID: <161057116929.23741.13475991130748875904@ietfa.amsl.com>
Date: Wed, 13 Jan 2021 12:52:49 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/2BGTTabUnGRt5m9-8p77tkc8PY4>
Subject: [calsify] I-D Action: draft-ietf-calext-eventpub-extensions-18.txt
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 20:52:49 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Calendaring Extensions WG of the IETF.

        Title           : Event Publishing Extensions to iCalendar
        Author          : Michael Douglass
	Filename        : draft-ietf-calext-eventpub-extensions-18.txt
	Pages           : 36
	Date            : 2021-01-13

Abstract:
   This specification updates RFC5545 by introducing a number of new
   iCalendar properties and components which are of particular use for
   event publishers and in social networking.

   This specification also defines a new STRUCTURED-DATA property for
   iCalendar RFC5545 to allow for data that is directly pertinent to an
   event or task to be included with the calendar data.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-calext-eventpub-extensions-18
https://datatracker.ietf.org/doc/html/draft-ietf-calext-eventpub-extensions-18

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-eventpub-extensions-18


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Wed Jan 13 12:54:02 2021
Return-Path: <mikeadouglass@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8327C3A1377; Wed, 13 Jan 2021 12:54:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.359
X-Spam-Level: 
X-Spam-Status: No, score=-2.359 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bne9cqLTnVTo; Wed, 13 Jan 2021 12:53:58 -0800 (PST)
Received: from mail-qv1-xf32.google.com (mail-qv1-xf32.google.com [IPv6:2607:f8b0:4864:20::f32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BF453A1378; Wed, 13 Jan 2021 12:53:58 -0800 (PST)
Received: by mail-qv1-xf32.google.com with SMTP id p5so1443121qvs.7; Wed, 13 Jan 2021 12:53:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=d9m2qqhV1//Dze8yRmUDotbCKEn2EIxdlJg+T5v2UUY=; b=h5ZQBn1exGiOikMrLMz0ERuoVN5JMl7eax9Z4Ijb8KU8Nc4KnplWXsUocJ4egt2XK7 jc103u8i0g6qbhMEf/qJhj+MR2Xgk4cFUtLLXsvIhDmORcdrNgjfESgt47f/4FnoanLc 8dPayZ331+zOGVUYV9hYKVyN4t3RFBo30BtFD4ULKoDPBdqLQGU4SVTyQJ67n7mDSJVZ V2cdC8dHoezCK7b5sSn7yY3ygKfsvoVZrdSuOh+8WwiqPqN/KHx0Y9bLzr83gyLV2Q3k OHUtnJdfDnfU3XJgTvd9WINWo1DK+MFtVMB9sH7fuM2tN74lL84R1xZINAhH1DN0dc4s yYYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=d9m2qqhV1//Dze8yRmUDotbCKEn2EIxdlJg+T5v2UUY=; b=TnJNvD1cLn5QtetNgXmdsFzBZ7v8tnmw3eXaH8ENSpAWqwPaJX3pcpgQJ4cyWFIlLE vYhvHQbgl2WPtoA/jL1MrQOBiM2i2hCXzjsnnObohccw3HLYWDS+mkzTkEHSywtJNHG6 Q+U/OUYN+M6SvEaT6qxVuDzCEehyOUtbpN00uF6bndXV9OuCC54bzKDc9SQbO4+mj2M3 +wrAE6PgSOzNveoW9Xo/Qcpdfg2Gejhg2gDdbWI691jLjkzxg7h4Gs4K9a5Tk3x8Vaa8 Z+PhgNucObj0eV3M6c94TjEsG4gObyACGHLJQt/9DWUF4mwt28DZRbEImYGBgFQADxWL SF4g==
X-Gm-Message-State: AOAM530k3j9kx7Kyp/A3cUfuLFho1myjvKc18DD1ZYjrymQbTn7QEoUU OeTeIsgTS+n/+nRsiU+a33Kj4+ij4qabZA==
X-Google-Smtp-Source: ABdhPJziwRsmyztmyQ2C5cRw6HXFz7tPLcgSYYl0vlkPvUoU14TZGhvlfKNclFXe1LRW6f6iWYEPJQ==
X-Received: by 2002:a05:6214:80d:: with SMTP id df13mr4325699qvb.10.1610571237312;  Wed, 13 Jan 2021 12:53:57 -0800 (PST)
Received: from [192.168.1.151] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id i17sm1725719qtg.77.2021.01.13.12.53.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 13 Jan 2021 12:53:56 -0800 (PST)
From: Michael Douglass <mikeadouglass@gmail.com>
To: Barry Leiba <barryleiba@computer.org>, The IESG <iesg@ietf.org>
Cc: draft-ietf-calext-eventpub-extensions@ietf.org, calext-chairs@ietf.org, calsify@ietf.org
References: <160979733556.18901.5326788661603760785@ietfa.amsl.com>
Message-ID: <31e49aaa-f781-505d-e41a-8c1fcd56ed2d@gmail.com>
Date: Wed, 13 Jan 2021 15:53:55 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <160979733556.18901.5326788661603760785@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------3AA00849D2D7D819B1A1A596"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/4sTchar6ksGNuR-PoNVn9jZgQLs>
Subject: Re: [calsify] Barry Leiba's Discuss on draft-ietf-calext-eventpub-extensions-17: (with DISCUSS)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 20:54:01 -0000

This is a multi-part message in MIME format.
--------------3AA00849D2D7D819B1A1A596
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Thanks for this,

Comments below - just posted a version 18

On 1/4/21 16:55, Barry Leiba via Datatracker wrote:
> Barry Leiba has entered the following ballot position for
> draft-ietf-calext-eventpub-extensions-17: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer tohttps://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Thanks very much for the changes in Section 9.1, and I think we're now at the
> best place we can reasonable be here.  Well done.
>
> Thanks also for the changes to clarify the ABNF.  They're mostly good, and we
> should be able to clean these last bits up pretty easily:
>
> — Section 6.6 —
>
> The new ABNF doesn’t correctly specify what the old was trying to say.  I think
> this is correct and concise, but please check it over:
>
> NEW
>
> sdataprop    = "STRUCTURED-DATA" sdataparam ":"
>                       sdataval CRLF
>
>        sdataparam     = ; all parameter elements may appear in any order,
>                         ; and the order is not significant.
>                         (sdataparamtext / sdataparambin / sdataparamuri)
>                         *(";" other-param)
>
>        sdataparamtext = ";VALUE=TEXT"
>                         ";" fmttypeparam
>                         ";" schemaparam
>
>        sdataparambin  = ";VALUE=BINARY"
>                         ";ENCODING=BASE64"
>                         ";" fmttypeparam
>                         ";" schemaparam
>
>        sdataparamuri  = ";VALUE=URI"
>                         [";" fmttypeparam]
>                         [";" schemaparam]
>
>        sdataval       = ( binary / text /uri )
>                         ; value MUST match value type
>
> END
Thanks - that seems much better.
>
> — Section 7.1 —
>
>        participantc = "BEGIN" ":" "PARTICIPANT" CRLF
>                       *( partprop / locationc / resourcec )
>                       "END" ":" "PARTICIPANT" CRLF
>
> This allows multiple instances of partprop (or none), which is not what you
> mean.  The “*” isn’t right.  Also, do you really mean to have locationc and
> resourcec here?  Those are blocks that are peers of participantc within eventc,
> todoc, journalc, and freebusyc… are they also meant to be nested within
> participantc?  If so, it would be good to have an example or two that shows
> that.  In any case, that bit of ABNF still needs some work.

Replaced with

participantc = "BEGIN" ":" "PARTICIPANT" CRLF
                partprop *locationc *resourcec
                "END" ":" "PARTICIPANT" CRLF

location and resources are allowed as properties, locationc and 
resourcec allow the eventpub style components. I'll add an example

>
>                       (calendaraddress)
>                       (created)
>                       (description)
>                       (dtstamp)
>                       (geo)
>                       (last-mod)
>                       (priority)
>                       (seq)
>                       (status)
>                       (summary)
>                       (url)
>
> All of these are meant to be optional, so they should be in square brackets,
> rather than in parentheses.  The same is true in Sections 7.2 and 7.3.
All fixed.
>
>
>
>
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify

--------------3AA00849D2D7D819B1A1A596
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Thanks for this,</p>
    <p>Comments below - just posted a version 18<br>
    </p>
    <div class="moz-cite-prefix">On 1/4/21 16:55, Barry Leiba via
      Datatracker wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:160979733556.18901.5326788661603760785@ietfa.amsl.com">
      <pre class="moz-quote-pre" wrap="">Barry Leiba has entered the following ballot position for
draft-ietf-calext-eventpub-extensions-17: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to <a class="moz-txt-link-freetext" href="https://www.ietf.org/iesg/statement/discuss-criteria.html">https://www.ietf.org/iesg/statement/discuss-criteria.html</a>
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/">https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/</a>



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Thanks very much for the changes in Section 9.1, and I think we're now at the
best place we can reasonable be here.  Well done.

Thanks also for the changes to clarify the ABNF.  They're mostly good, and we
should be able to clean these last bits up pretty easily:

— Section 6.6 —

The new ABNF doesn’t correctly specify what the old was trying to say.  I think
this is correct and concise, but please check it over:

NEW

sdataprop    = "STRUCTURED-DATA" sdataparam ":"
                     sdataval CRLF

      sdataparam     = ; all parameter elements may appear in any order,
                       ; and the order is not significant.
                       (sdataparamtext / sdataparambin / sdataparamuri)
                       *(";" other-param)

      sdataparamtext = ";VALUE=TEXT"
                       ";" fmttypeparam
                       ";" schemaparam

      sdataparambin  = ";VALUE=BINARY"
                       ";ENCODING=BASE64"
                       ";" fmttypeparam
                       ";" schemaparam

      sdataparamuri  = ";VALUE=URI"
                       [";" fmttypeparam]
                       [";" schemaparam]

      sdataval       = ( binary / text /uri )
                       ; value MUST match value type

END</pre>
    </blockquote>
    Thanks - that seems much better.<br>
    <blockquote type="cite"
      cite="mid:160979733556.18901.5326788661603760785@ietfa.amsl.com">
      <pre class="moz-quote-pre" wrap="">

— Section 7.1 —

      participantc = "BEGIN" ":" "PARTICIPANT" CRLF
                     *( partprop / locationc / resourcec )
                     "END" ":" "PARTICIPANT" CRLF

This allows multiple instances of partprop (or none), which is not what you
mean.  The “*” isn’t right.  Also, do you really mean to have locationc and
resourcec here?  Those are blocks that are peers of participantc within eventc,
todoc, journalc, and freebusyc… are they also meant to be nested within
participantc?  If so, it would be good to have an example or two that shows
that.  In any case, that bit of ABNF still needs some work.</pre>
    </blockquote>
    <p>Replaced with <br>
    </p>
    <pre style="background-color:#ffffff;color:#080808;font-family:'JetBrains Mono',monospace;font-size:9.8pt;">participantc = "BEGIN" ":" "PARTICIPANT" CRLF
               partprop *locationc *resourcec
               "END" ":" "PARTICIPANT" CRLF
</pre>
    <p>location and resources are allowed as properties, locationc and
      resourcec allow the eventpub style components. I'll add an example
      <br>
    </p>
    <blockquote type="cite"
      cite="mid:160979733556.18901.5326788661603760785@ietfa.amsl.com">
      <pre class="moz-quote-pre" wrap="">

                     (calendaraddress)
                     (created)
                     (description)
                     (dtstamp)
                     (geo)
                     (last-mod)
                     (priority)
                     (seq)
                     (status)
                     (summary)
                     (url)

All of these are meant to be optional, so they should be in square brackets,
rather than in parentheses.  The same is true in Sections 7.2 and 7.3.</pre>
    </blockquote>
    All fixed.<br>
    <blockquote type="cite"
      cite="mid:160979733556.18901.5326788661603760785@ietfa.amsl.com">
      <pre class="moz-quote-pre" wrap="">





_______________________________________________
calsify mailing list
<a class="moz-txt-link-abbreviated" href="mailto:calsify@ietf.org">calsify@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/calsify">https://www.ietf.org/mailman/listinfo/calsify</a>
</pre>
    </blockquote>
  </body>
</html>

--------------3AA00849D2D7D819B1A1A596--


From nobody Wed Jan 13 17:33:29 2021
Return-Path: <brong@fastmailteam.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DD193A0CF1 for <calsify@ietfa.amsl.com>; Wed, 13 Jan 2021 17:33:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=IJNpKLB1; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=GaDibc6b
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wb7L1elp83fy for <calsify@ietfa.amsl.com>; Wed, 13 Jan 2021 17:33:25 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0E5A3A0CEF for <calsify@ietf.org>; Wed, 13 Jan 2021 17:33:25 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 7D8CA5C0154 for <calsify@ietf.org>; Wed, 13 Jan 2021 20:33:24 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Wed, 13 Jan 2021 20:33:24 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm1; bh=yndIDec /9fRab7Wkp0pHZECxoflz4g8s87szWM9EL/s=; b=IJNpKLB1U2QKeOOE3ftfk4d CbwwGmPzYi6M5wfL4pDTjEWDS5fdrW7btCvpfW9vr1NJAPoHJzoV6Kx29PA+itAU sW74P2wH58DmbP4GHIBljHM9mhTl23OomqTtOhmSTgXKNzdoEh69EJSgEFQtZO7I zIAcIf100SaRcMjDYTla/bC9Nc+vIjL0ksTzrcm2Igx2qJTipb3+OYRYUvKBeurr lskoQbEF7pc50VS5v5jGe++yHber5I2+bpHHFvH+KPyesSZb5UMb5XkxLbSKSlgN lNYJiQH8HTHb1BLmE0e2I0KRuoYCacX8SseuI2SyuthZm+tQlAraQ41Jw9ztpOg= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=yndIDe c/9fRab7Wkp0pHZECxoflz4g8s87szWM9EL/s=; b=GaDibc6b30LvZ9Xn1Nl7PB IbKBMFRShVmAQjP2dWKWwZ2Vg5GmYqTXXGr3E5fxRCYGt7u28Dg3oGw5FCWhDZ29 fXt8vOfhs4umtWv+tY+MvpQWrVc7fWqwE9BKHL0zCneoEc/dw+Vra3R3EsLCeJXn Xu9zj7XBGdSWtH4l1zL4wbOa8HUR/QGF0jFKBbdLCMfuIM4lk1UbRLAr6NfDJU84 wosOtph8D+Nkr9mKfqsSPkWlpth9lroqlow+lb8oUvRTGLax9VBUYUXOs1QTlYYi JjR6YjzG+jeamNxaCdOiNEDKPXG4jPR2UvK40ejNMxezWQ5m4x7VAQ1EpGP5kTiA ==
X-ME-Sender: <xms:Y5__XzVCjejRpHFIGNoVkdNxMTur603PHenIEX9ZJMURBASrqwelXQ> <xme:Y5__X7nqcjQpC_FtpdXwpFr7NjyCgZgwOGWvBzG4QD3gU6A0NPPyfjD6ZNh8F7Lj1 aG3PE7lxpk>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedukedrtdeggdefhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreertdenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehf rghsthhmrghilhhtvggrmhdrtghomheqnecuggftrfgrthhtvghrnhepgfduvefgffdvve ethfeiteehteduhfeltddujeehffektdevleeileeiheevkeegnecuffhomhgrihhnpehi vghtfhdrohhrghdpghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgt ohhm
X-ME-Proxy: <xmx:Y5__X_Z-vFuYtd6oWYvRsBLHWt98dNEFmj-8Sh4omorFiD_hGzpDWg> <xmx:Y5__X-V-_gywA36O2NgrT3uchcxpFE37h4-eXEBXrvs0rjAwb5enHA> <xmx:Y5__X9mJvfvKoo6kwzMT68AD-f8BiTdfBY_ocVlMFQWCSoqjqmgmrg> <xmx:ZJ__X5zeTb8k1VSs-YJ2J_JYdeGfDLKCoajQPw0YXMLCe8jCyX7p2w>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 9E94B180093; Wed, 13 Jan 2021 20:33:23 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-45-g4839256-fm-20210104.001-g48392560
Mime-Version: 1.0
Message-Id: <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com>
In-Reply-To: <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com>
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com>
Date: Thu, 14 Jan 2021 12:33:03 +1100
From: "Bron Gondwana" <brong@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary=c3bb48530bd443f5959972aa5b19b5ca
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/MouMwT5zLRh0yebun_y7VCTP_j4>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2021 01:33:28 -0000

--c3bb48530bd443f5959972aa5b19b5ca
Content-Type: text/plain

I can do a call for adoption straight away if you like - the next meeting isn't for a couple of months.

Bron.

On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:
> One question: given things move forward smoothly, how do I proceed?
> Should I apply for this document to be adopted by the calext WG? I
> suppose the fastest way to proceed is to present it at the next IETF
> meeting?
> 
> 
> 
> Ujjwal
> 
> On 12/01/2021 4.03 am, Ujjwal Sharma wrote:
> > Hi Calsify folks!
> > 
> > I am sorry for the long delay, I got a little sidetracked working on
> > other things, but I'm happy to inform you all that I have something that
> > resembles a first draft for the updated timestamps RFC.
> > 
> > Here's where you can find it:
> > 
> > Datatracker:
> > https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
> > GitHub: https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
> > 
> > I would request you all to take a look at it when you can and let me
> > know what you think. You can file a GitHub issue or email me directly.
> > 
> > There's a few open discussions regarding the exact format and how the
> > interaction with bodies like the Unicode consortium work, so please feel
> > free to send me your thoughts regarding that as well.
> > 
> > Also, some references/bibliography is not perfectly functional yet
> > because I am still relatively new to authoring RFCs using Metanorma but
> > I'm actively looking into it.
> > 
> > Thanks and looking forward to hear from you,
> > Ujjwal
> > 
> 
> -- 
> Ujjwal "Ryzokuken" Sharma (he/him)
> 
> Compilers Hacker, Node.js Core Collaborator and Speaker
> 
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
> 

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com

--c3bb48530bd443f5959972aa5b19b5ca
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"font-f=
amily:Arial;">I can do a call for adoption straight away if you like - t=
he next meeting isn't for a couple of months.<br></div><div style=3D"fon=
t-family:Arial;"><br>Bron.<br></div><div style=3D"font-family:Arial;"><b=
r></div><div>On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:<br></d=
iv><blockquote type=3D"cite" id=3D"qt" style=3D""><div style=3D"font-fam=
ily:Arial;">One question: given things move forward smoothly, how do I p=
roceed?<br></div><div style=3D"font-family:Arial;">Should I apply for th=
is document to be adopted by the calext WG? I<br></div><div style=3D"fon=
t-family:Arial;">suppose the fastest way to proceed is to present it at =
the next IETF<br></div><div style=3D"font-family:Arial;">meeting?<br></d=
iv><div style=3D"font-family:Arial;"><br></div><div style=3D"font-family=
:Arial;"><br></div><div style=3D"font-family:Arial;"><br></div><div styl=
e=3D"font-family:Arial;">Ujjwal<br></div><div style=3D"font-family:Arial=
;"><br></div><div style=3D"font-family:Arial;">On 12/01/2021 4.03 am, Uj=
jwal Sharma wrote:<br></div><div style=3D"font-family:Arial;">&gt; Hi Ca=
lsify folks!<br></div><div style=3D"font-family:Arial;">&gt;&nbsp;<br></=
div><div style=3D"font-family:Arial;">&gt; I am sorry for the long delay=
, I got a little sidetracked working on<br></div><div style=3D"font-fami=
ly:Arial;">&gt; other things, but I'm happy to inform you all that I hav=
e something that<br></div><div style=3D"font-family:Arial;">&gt; resembl=
es a first draft for the updated timestamps RFC.<br></div><div style=3D"=
font-family:Arial;">&gt;&nbsp;<br></div><div style=3D"font-family:Arial;=
">&gt; Here's where you can find it:<br></div><div style=3D"font-family:=
Arial;">&gt;&nbsp;<br></div><div style=3D"font-family:Arial;">&gt; Datat=
racker:<br></div><div style=3D"font-family:Arial;">&gt;&nbsp;<a href=3D"=
https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/">htt=
ps://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/</a><br>=
</div><div style=3D"font-family:Arial;">&gt; GitHub:&nbsp;<a href=3D"htt=
ps://github.com/ryzokuken/draft-ryzokuken-datetime-extended">https://git=
hub.com/ryzokuken/draft-ryzokuken-datetime-extended</a><br></div><div st=
yle=3D"font-family:Arial;">&gt;&nbsp;<br></div><div style=3D"font-family=
:Arial;">&gt; I would request you all to take a look at it when you can =
and let me<br></div><div style=3D"font-family:Arial;">&gt; know what you=
 think. You can file a GitHub issue or email me directly.<br></div><div =
style=3D"font-family:Arial;">&gt;&nbsp;<br></div><div style=3D"font-fami=
ly:Arial;">&gt; There's a few open discussions regarding the exact forma=
t and how the<br></div><div style=3D"font-family:Arial;">&gt; interactio=
n with bodies like the Unicode consortium work, so please feel<br></div>=
<div style=3D"font-family:Arial;">&gt; free to send me your thoughts reg=
arding that as well.<br></div><div style=3D"font-family:Arial;">&gt;&nbs=
p;<br></div><div style=3D"font-family:Arial;">&gt; Also, some references=
/bibliography is not perfectly functional yet<br></div><div style=3D"fon=
t-family:Arial;">&gt; because I am still relatively new to authoring RFC=
s using Metanorma but<br></div><div style=3D"font-family:Arial;">&gt; I'=
m actively looking into it.<br></div><div style=3D"font-family:Arial;">&=
gt;&nbsp;<br></div><div style=3D"font-family:Arial;">&gt; Thanks and loo=
king forward to hear from you,<br></div><div style=3D"font-family:Arial;=
">&gt; Ujjwal<br></div><div style=3D"font-family:Arial;">&gt;&nbsp;<br><=
/div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-fami=
ly:Arial;">--&nbsp;<br></div><div style=3D"font-family:Arial;">Ujjwal "R=
yzokuken" Sharma (he/him)<br></div><div style=3D"font-family:Arial;"><br=
></div><div style=3D"font-family:Arial;">Compilers Hacker, Node.js Core =
Collaborator and Speaker<br></div><div style=3D"font-family:Arial;"><br>=
</div><div style=3D"font-family:Arial;">________________________________=
_______________<br></div><div style=3D"font-family:Arial;">calsify maili=
ng list<br></div><div style=3D"font-family:Arial;"><a href=3D"mailto:cal=
sify@ietf.org">calsify@ietf.org</a><br></div><div style=3D"font-family:A=
rial;"><a href=3D"https://www.ietf.org/mailman/listinfo/calsify">https:/=
/www.ietf.org/mailman/listinfo/calsify</a><br></div><div style=3D"font-f=
amily:Arial;"><br></div></blockquote><div style=3D"font-family:Arial;"><=
br></div><div id=3D"sig56629417"><div class=3D"signature">--<br></div><d=
iv class=3D"signature">&nbsp; Bron Gondwana, CEO, Fastmail Pty Ltd<br></=
div><div class=3D"signature">&nbsp; brong@fastmailteam.com<br></div><div=
 class=3D"signature"><br></div></div></body></html>
--c3bb48530bd443f5959972aa5b19b5ca--


From nobody Wed Jan 13 18:49:01 2021
Return-Path: <ryzokuken@igalia.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF1473A0E80 for <calsify@ietfa.amsl.com>; Wed, 13 Jan 2021 18:48:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level: 
X-Spam-Status: No, score=-2.361 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=igalia.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ktiCD7a3UCDk for <calsify@ietfa.amsl.com>; Wed, 13 Jan 2021 18:48:55 -0800 (PST)
Received: from fanzine.igalia.com (fanzine.igalia.com [178.60.130.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6FBE3A0CF8 for <calsify@ietf.org>; Wed, 13 Jan 2021 18:48:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com;  s=20170329;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject; bh=vZsN7fWpYxYljpjCNRyPjyV75bLpJzJ8Nuv23I0fOoU=;  b=WXFj0N7e8QIJUnw/93MkRQvXI4SHILSLZ1F4WAfUZ5ZsZGR7k/kI/dsatNkHli5Mz6oYykblemUCjHn/fT3moQaf5zGD+oTf8gmwAmFF0pe3gNopbMgCjk+NkgIMSq5mjnKRcfR/bl+nMFaQ7N2w5ih0aFBwpPNKED6ETyX/M19j+Db35j+zTJrao352wxuLx3piP3IGxYs3tQyru8fTF5RmDpcu4bdjVjQnZjWhEiylphfrSMXBrWWm4FUFIzpJr2g7FnD4sqDBS3La9YXoveyDBq9gBHmmUhU/jZC+sASPI6IMXTtwR02XFkoFyubtFJbKbneRzXzr2BvRgXdg8A==;
Received: from [45.122.44.244] (helo=[192.168.0.110]) by fanzine.igalia.com with esmtpsa  (Cipher TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim) id 1kzsgt-0003oB-Gu for <calsify@ietf.org>; Thu, 14 Jan 2021 03:48:51 +0100
To: calsify@ietf.org
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com>
From: Ujjwal Sharma <ryzokuken@igalia.com>
Organization: Igalia S.L.
Message-ID: <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com>
Date: Thu, 14 Jan 2021 08:18:20 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/VaqMiWboXNh__ZZXMteGcGXpAI0>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2021 02:48:59 -0000

Thanks Bron!

I'll make a few more changes, release a 01 version, ask for more
feedback and then let you know, hopefully by the end of this week.

Ujjwal

On 14/01/2021 7.03 am, Bron Gondwana wrote:
> I can do a call for adoption straight away if you like - the next
> meeting isn't for a couple of months.
> 
> Bron.
> 
> On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:
>> One question: given things move forward smoothly, how do I proceed?
>> Should I apply for this document to be adopted by the calext WG? I
>> suppose the fastest way to proceed is to present it at the next IETF
>> meeting?
>>
>>
>>
>> Ujjwal
>>
>> On 12/01/2021 4.03 am, Ujjwal Sharma wrote:
>> > Hi Calsify folks!
>> > 
>> > I am sorry for the long delay, I got a little sidetracked working on
>> > other things, but I'm happy to inform you all that I have something that
>> > resembles a first draft for the updated timestamps RFC.
>> > 
>> > Here's where you can find it:
>> > 
>> > Datatracker:
>> > https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
>> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/>
>> >
>> GitHub: https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
>> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>
>> > 
>> > I would request you all to take a look at it when you can and let me
>> > know what you think. You can file a GitHub issue or email me directly.
>> > 
>> > There's a few open discussions regarding the exact format and how the
>> > interaction with bodies like the Unicode consortium work, so please feel
>> > free to send me your thoughts regarding that as well.
>> > 
>> > Also, some references/bibliography is not perfectly functional yet
>> > because I am still relatively new to authoring RFCs using Metanorma but
>> > I'm actively looking into it.
>> > 
>> > Thanks and looking forward to hear from you,
>> > Ujjwal
>> > 
>>
>> -- 
>> Ujjwal "Ryzokuken" Sharma (he/him)
>>
>> Compilers Hacker, Node.js Core Collaborator and Speaker
>>
>> _______________________________________________
>> calsify mailing list
>> calsify@ietf.org <mailto:calsify@ietf.org>
>> https://www.ietf.org/mailman/listinfo/calsify
>> <https://www.ietf.org/mailman/listinfo/calsify>
>>
> 
> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd
>   brong@fastmailteam.com
> 
> 
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
> 

-- 
Ujjwal "Ryzokuken" Sharma (he/him)

Compilers Hacker, Node.js Core Collaborator and Speaker


From nobody Wed Jan 13 19:05:17 2021
Return-Path: <brong@fastmailteam.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C98D33A0FCB for <calsify@ietfa.amsl.com>; Wed, 13 Jan 2021 19:05:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=dNM9bH/W; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=oksh5rpL
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AetKGpLbXAQR for <calsify@ietfa.amsl.com>; Wed, 13 Jan 2021 19:05:13 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9A6D3A0FC7 for <calsify@ietf.org>; Wed, 13 Jan 2021 19:05:13 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 01CBF5C01D3 for <calsify@ietf.org>; Wed, 13 Jan 2021 22:05:13 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Wed, 13 Jan 2021 22:05:13 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm1; bh=2ySuMlJ el/pQuqINN/FBGxUIta8ZB5nISBPm5do8+vc=; b=dNM9bH/WdDbU4BVK3L+Bd0s bks8bWuYX239TVYlPEdgBQjzsf7i57htFEvWGE8WsOSWWOPfdUoMtKSJno+tPurH 7J+ocgViKyoPuh/DN3tyjtlZCk9QCprHAtfaB1X4RJsnWMSI4G4tB/51BtUAKLSO ysWbMx1b3/9xNk9Bk1LxUsx/7dNQye+x3chbUGMdtckxkyrczWUuHNxIL1wPSfo1 9EzlPA/PEAhGW9YDJg3Ob2PvzD6mne/GYWSplMCaynhPL3hyNGr23epcosSsUgwW iGocILfF2mC8NP3lnvmq3Gm7vnyhTpW++7uaOEriLLWooulyuCWEGCeR2pomNrQ= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=2ySuMl Jel/pQuqINN/FBGxUIta8ZB5nISBPm5do8+vc=; b=oksh5rpLs3vrk7XarfaZMP kQCbcvzJuoVsxY9FkDF/qtjmX2S5M+dgwFMGq6tO3kVSxB05K7RUwPIyxBFfYqRH Rh906XfJwgch5Tc+JX9F32pzPhbBhiJtJrVVynBwmZ1D1qqnMf6g9iV7T1hdWuQl QSe0nuEx1O7mUN9FagXLuSs0GlZiUUOdR23QjcsU6jB3x+WZWuFqrJ2XExp2VAKk lszoDaVKUsQefRa6KADHXZ0vtUMve2avl6/jv8XQfv366EYXZoVCojkJoy+h62Su Tqzlh1E2WzzgxAhiaQjPAbEYyHAq9LGzphQ3yxTsVIZX8ODFgxjR6hlpYGVRuOuQ ==
X-ME-Sender: <xms:6LT_X3aOmsjCrcBFejBKg0iBliAh4Fjbo0nv0bR4FmN529pOraK3-A> <xme:6LT_X2bIijbDPcb2zk_Gpty0rH9nOek8GuWAtp4puAOCoV4Cl74HLg3vloGUdRUta fk6h_mSGd0>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedukedrtdeggdehgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreertdenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehf rghsthhmrghilhhtvggrmhdrtghomheqnecuggftrfgrthhtvghrnhepgfduvefgffdvve ethfeiteehteduhfeltddujeehffektdevleeileeiheevkeegnecuffhomhgrihhnpehi vghtfhdrohhrghdpghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgt ohhm
X-ME-Proxy: <xmx:6LT_X59PixLZ3QhQdW7r25n6pVzWMxu8H8xif0Ay5wK3ZoSNsJ6fpw> <xmx:6LT_X9osUZybwuAR33Znzhq49YItnUiwCzSdGy_iA2JnKRzQPeyZJw> <xmx:6LT_Xyq5Fx4NGyS6X8hz9WYUxNbv3guaBkz2W9OOCkb9y2Iwoxhjiw> <xmx:6LT_X_0Rxkfq3XirqznybAqmeFcvM8zVZtgxDR_9GTND41I6o3AQNQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id A0E091800C5; Wed, 13 Jan 2021 22:05:12 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-45-g4839256-fm-20210104.001-g48392560
Mime-Version: 1.0
Message-Id: <0275d5af-6eea-4608-913e-c96d59c0abea@dogfood.fastmail.com>
In-Reply-To: <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com>
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com>
Date: Thu, 14 Jan 2021 14:04:51 +1100
From: "Bron Gondwana" <brong@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary=02f9bf61dd3943b2ad4b9510a5097a5d
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/xgVq0m-N0AXdx6ZED4T4QaPcHJE>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2021 03:05:16 -0000

--02f9bf61dd3943b2ad4b9510a5097a5d
Content-Type: text/plain

Sounds great.  Let me know :)

When we do the call for adoption I'll also advertise the fact over to the wider IETF - probably dispatch and tzdata lists at least.

Cheers,

Bron.


On Thu, Jan 14, 2021, at 13:48, Ujjwal Sharma wrote:
> Thanks Bron!
> 
> I'll make a few more changes, release a 01 version, ask for more
> feedback and then let you know, hopefully by the end of this week.
> 
> Ujjwal
> 
> On 14/01/2021 7.03 am, Bron Gondwana wrote:
> > I can do a call for adoption straight away if you like - the next
> > meeting isn't for a couple of months.
> > 
> > Bron.
> > 
> > On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:
> >> One question: given things move forward smoothly, how do I proceed?
> >> Should I apply for this document to be adopted by the calext WG? I
> >> suppose the fastest way to proceed is to present it at the next IETF
> >> meeting?
> >>
> >>
> >>
> >> Ujjwal
> >>
> >> On 12/01/2021 4.03 am, Ujjwal Sharma wrote:
> >> > Hi Calsify folks!
> >> > 
> >> > I am sorry for the long delay, I got a little sidetracked working on
> >> > other things, but I'm happy to inform you all that I have something that
> >> > resembles a first draft for the updated timestamps RFC.
> >> > 
> >> > Here's where you can find it:
> >> > 
> >> > Datatracker:
> >> > https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
> >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/>
> >> >
> >> GitHub: https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>
> >> > 
> >> > I would request you all to take a look at it when you can and let me
> >> > know what you think. You can file a GitHub issue or email me directly.
> >> > 
> >> > There's a few open discussions regarding the exact format and how the
> >> > interaction with bodies like the Unicode consortium work, so please feel
> >> > free to send me your thoughts regarding that as well.
> >> > 
> >> > Also, some references/bibliography is not perfectly functional yet
> >> > because I am still relatively new to authoring RFCs using Metanorma but
> >> > I'm actively looking into it.
> >> > 
> >> > Thanks and looking forward to hear from you,
> >> > Ujjwal
> >> > 
> >>
> >> -- 
> >> Ujjwal "Ryzokuken" Sharma (he/him)
> >>
> >> Compilers Hacker, Node.js Core Collaborator and Speaker
> >>
> >> _______________________________________________
> >> calsify mailing list
> >> calsify@ietf.org <mailto:calsify@ietf.org>
> >> https://www.ietf.org/mailman/listinfo/calsify
> >> <https://www.ietf.org/mailman/listinfo/calsify>
> >>
> > 
> > --
> >   Bron Gondwana, CEO, Fastmail Pty Ltd
> >   brong@fastmailteam.com
> > 
> > 
> > _______________________________________________
> > calsify mailing list
> > calsify@ietf.org
> > https://www.ietf.org/mailman/listinfo/calsify
> > 
> 
> -- 
> Ujjwal "Ryzokuken" Sharma (he/him)
> 
> Compilers Hacker, Node.js Core Collaborator and Speaker
> 
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
> 

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com


--02f9bf61dd3943b2ad4b9510a5097a5d
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"font-f=
amily:Arial;">Sounds great.&nbsp; Let me know :)<br></div><div style=3D"=
font-family:Arial;"><br></div><div style=3D"font-family:Arial;">When we =
do the call for adoption I'll also advertise the fact over to the wider =
IETF - probably dispatch and tzdata lists at least.<br></div><div style=3D=
"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">Cheers,=
<br></div><div style=3D"font-family:Arial;"><br>Bron.<br><br></div><div =
style=3D"font-family:Arial;"><br></div><div>On Thu, Jan 14, 2021, at 13:=
48, Ujjwal Sharma wrote:<br></div><blockquote type=3D"cite" id=3D"qt" st=
yle=3D""><div style=3D"font-family:Arial;">Thanks Bron!<br></div><div st=
yle=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">I=
'll make a few more changes, release a 01 version, ask for more<br></div=
><div style=3D"font-family:Arial;">feedback and then let you know, hopef=
ully by the end of this week.<br></div><div style=3D"font-family:Arial;"=
><br></div><div style=3D"font-family:Arial;">Ujjwal<br></div><div style=3D=
"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">On 14/0=
1/2021 7.03 am, Bron Gondwana wrote:<br></div><div style=3D"font-family:=
Arial;">&gt; I can do a call for adoption straight away if you like - th=
e next<br></div><div style=3D"font-family:Arial;">&gt; meeting isn't for=
 a couple of months.<br></div><div style=3D"font-family:Arial;">&gt;&nbs=
p;<br></div><div style=3D"font-family:Arial;">&gt; Bron.<br></div><div s=
tyle=3D"font-family:Arial;">&gt;&nbsp;<br></div><div style=3D"font-famil=
y:Arial;">&gt; On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:<br><=
/div><div style=3D"font-family:Arial;">&gt;&gt; One question: given thin=
gs move forward smoothly, how do I proceed?<br></div><div style=3D"font-=
family:Arial;">&gt;&gt; Should I apply for this document to be adopted b=
y the calext WG? I<br></div><div style=3D"font-family:Arial;">&gt;&gt; s=
uppose the fastest way to proceed is to present it at the next IETF<br><=
/div><div style=3D"font-family:Arial;">&gt;&gt; meeting?<br></div><div s=
tyle=3D"font-family:Arial;">&gt;&gt;<br></div><div style=3D"font-family:=
Arial;">&gt;&gt;<br></div><div style=3D"font-family:Arial;">&gt;&gt;<br>=
</div><div style=3D"font-family:Arial;">&gt;&gt; Ujjwal<br></div><div st=
yle=3D"font-family:Arial;">&gt;&gt;<br></div><div style=3D"font-family:A=
rial;">&gt;&gt; On 12/01/2021 4.03 am, Ujjwal Sharma wrote:<br></div><di=
v style=3D"font-family:Arial;">&gt;&gt; &gt; Hi Calsify folks!<br></div>=
<div style=3D"font-family:Arial;">&gt;&gt; &gt;&nbsp;<br></div><div styl=
e=3D"font-family:Arial;">&gt;&gt; &gt; I am sorry for the long delay, I =
got a little sidetracked working on<br></div><div style=3D"font-family:A=
rial;">&gt;&gt; &gt; other things, but I'm happy to inform you all that =
I have something that<br></div><div style=3D"font-family:Arial;">&gt;&gt=
; &gt; resembles a first draft for the updated timestamps RFC.<br></div>=
<div style=3D"font-family:Arial;">&gt;&gt; &gt;&nbsp;<br></div><div styl=
e=3D"font-family:Arial;">&gt;&gt; &gt; Here's where you can find it:<br>=
</div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&nbsp;<br></div><di=
v style=3D"font-family:Arial;">&gt;&gt; &gt; Datatracker:<br></div><div =
style=3D"font-family:Arial;">&gt;&gt; &gt;&nbsp;<a href=3D"https://datat=
racker.ietf.org/doc/draft-ryzokuken-datetime-extended/">https://datatrac=
ker.ietf.org/doc/draft-ryzokuken-datetime-extended/</a><br></div><div st=
yle=3D"font-family:Arial;">&gt;&gt; &lt;<a href=3D"https://datatracker.i=
etf.org/doc/draft-ryzokuken-datetime-extended/">https://datatracker.ietf=
.org/doc/draft-ryzokuken-datetime-extended/</a>&gt;<br></div><div style=3D=
"font-family:Arial;">&gt;&gt; &gt;<br></div><div style=3D"font-family:Ar=
ial;">&gt;&gt; GitHub:&nbsp;<a href=3D"https://github.com/ryzokuken/draf=
t-ryzokuken-datetime-extended">https://github.com/ryzokuken/draft-ryzoku=
ken-datetime-extended</a><br></div><div style=3D"font-family:Arial;">&gt=
;&gt; &lt;<a href=3D"https://github.com/ryzokuken/draft-ryzokuken-dateti=
me-extended">https://github.com/ryzokuken/draft-ryzokuken-datetime-exten=
ded</a>&gt;<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&nbs=
p;<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt; I would requ=
est you all to take a look at it when you can and let me<br></div><div s=
tyle=3D"font-family:Arial;">&gt;&gt; &gt; know what you think. You can f=
ile a GitHub issue or email me directly.<br></div><div style=3D"font-fam=
ily:Arial;">&gt;&gt; &gt;&nbsp;<br></div><div style=3D"font-family:Arial=
;">&gt;&gt; &gt; There's a few open discussions regarding the exact form=
at and how the<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt; =
interaction with bodies like the Unicode consortium work, so please feel=
<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt; free to send m=
e your thoughts regarding that as well.<br></div><div style=3D"font-fami=
ly:Arial;">&gt;&gt; &gt;&nbsp;<br></div><div style=3D"font-family:Arial;=
">&gt;&gt; &gt; Also, some references/bibliography is not perfectly func=
tional yet<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt; beca=
use I am still relatively new to authoring RFCs using Metanorma but<br><=
/div><div style=3D"font-family:Arial;">&gt;&gt; &gt; I'm actively lookin=
g into it.<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&nbsp=
;<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt; Thanks and lo=
oking forward to hear from you,<br></div><div style=3D"font-family:Arial=
;">&gt;&gt; &gt; Ujjwal<br></div><div style=3D"font-family:Arial;">&gt;&=
gt; &gt;&nbsp;<br></div><div style=3D"font-family:Arial;">&gt;&gt;<br></=
div><div style=3D"font-family:Arial;">&gt;&gt; --&nbsp;<br></div><div st=
yle=3D"font-family:Arial;">&gt;&gt; Ujjwal "Ryzokuken" Sharma (he/him)<b=
r></div><div style=3D"font-family:Arial;">&gt;&gt;<br></div><div style=3D=
"font-family:Arial;">&gt;&gt; Compilers Hacker, Node.js Core Collaborato=
r and Speaker<br></div><div style=3D"font-family:Arial;">&gt;&gt;<br></d=
iv><div style=3D"font-family:Arial;">&gt;&gt; __________________________=
_____________________<br></div><div style=3D"font-family:Arial;">&gt;&gt=
; calsify mailing list<br></div><div style=3D"font-family:Arial;">&gt;&g=
t;&nbsp;<a href=3D"mailto:calsify@ietf.org">calsify@ietf.org</a> &lt;mai=
lto:<a href=3D"mailto:calsify@ietf.org">calsify@ietf.org</a>&gt;<br></di=
v><div style=3D"font-family:Arial;">&gt;&gt;&nbsp;<a href=3D"https://www=
.ietf.org/mailman/listinfo/calsify">https://www.ietf.org/mailman/listinf=
o/calsify</a><br></div><div style=3D"font-family:Arial;">&gt;&gt; &lt;<a=
 href=3D"https://www.ietf.org/mailman/listinfo/calsify">https://www.ietf=
.org/mailman/listinfo/calsify</a>&gt;<br></div><div style=3D"font-family=
:Arial;">&gt;&gt;<br></div><div style=3D"font-family:Arial;">&gt;&nbsp;<=
br></div><div style=3D"font-family:Arial;">&gt; --<br></div><div style=3D=
"font-family:Arial;">&gt; &nbsp; Bron Gondwana, CEO, Fastmail Pty Ltd<br=
></div><div style=3D"font-family:Arial;">&gt; &nbsp;&nbsp;<a href=3D"mai=
lto:brong@fastmailteam.com">brong@fastmailteam.com</a><br></div><div sty=
le=3D"font-family:Arial;">&gt;&nbsp;<br></div><div style=3D"font-family:=
Arial;">&gt;&nbsp;<br></div><div style=3D"font-family:Arial;">&gt; _____=
__________________________________________<br></div><div style=3D"font-f=
amily:Arial;">&gt; calsify mailing list<br></div><div style=3D"font-fami=
ly:Arial;">&gt;&nbsp;<a href=3D"mailto:calsify@ietf.org">calsify@ietf.or=
g</a><br></div><div style=3D"font-family:Arial;">&gt;&nbsp;<a href=3D"ht=
tps://www.ietf.org/mailman/listinfo/calsify">https://www.ietf.org/mailma=
n/listinfo/calsify</a><br></div><div style=3D"font-family:Arial;">&gt;&n=
bsp;<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"=
font-family:Arial;">--&nbsp;<br></div><div style=3D"font-family:Arial;">=
Ujjwal "Ryzokuken" Sharma (he/him)<br></div><div style=3D"font-family:Ar=
ial;"><br></div><div style=3D"font-family:Arial;">Compilers Hacker, Node=
.js Core Collaborator and Speaker<br></div><div style=3D"font-family:Ari=
al;"><br></div><div style=3D"font-family:Arial;">_______________________=
________________________<br></div><div style=3D"font-family:Arial;">cals=
ify mailing list<br></div><div style=3D"font-family:Arial;"><a href=3D"m=
ailto:calsify@ietf.org">calsify@ietf.org</a><br></div><div style=3D"font=
-family:Arial;"><a href=3D"https://www.ietf.org/mailman/listinfo/calsify=
">https://www.ietf.org/mailman/listinfo/calsify</a><br></div><div style=3D=
"font-family:Arial;"><br></div></blockquote><div style=3D"font-family:Ar=
ial;"><br></div><div id=3D"sig56629417"><div class=3D"signature">--<br><=
/div><div class=3D"signature">&nbsp; Bron Gondwana, CEO, Fastmail Pty Lt=
d<br></div><div class=3D"signature">&nbsp; brong@fastmailteam.com<br></d=
iv><div class=3D"signature"><br></div></div><div style=3D"font-family:Ar=
ial;"><br></div></body></html>
--02f9bf61dd3943b2ad4b9510a5097a5d--


From nobody Thu Jan 14 08:46:51 2021
Return-Path: <sla@ucolick.org>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 927473A14FD for <calsify@ietfa.amsl.com>; Thu, 14 Jan 2021 08:46:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GPK1DeF8U304 for <calsify@ietfa.amsl.com>; Thu, 14 Jan 2021 08:46:48 -0800 (PST)
Received: from smtp.ucolick.org (zilan.ucolick.org [128.114.23.234]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84FA63A137B for <calsify@ietf.org>; Thu, 14 Jan 2021 08:46:48 -0800 (PST)
Received: from smtp.ucolick.org (localhost [127.0.0.1]) by smtp.ucolick.org (Postfix) with ESMTP id 1AEA12A81; Thu, 14 Jan 2021 08:46:47 -0800 (PST)
Received: from geneva.ucolick.org (geneva.ucolick.org [128.114.23.183]) by smtp.ucolick.org (Postfix) with ESMTP id 1773B2744; Thu, 14 Jan 2021 08:46:47 -0800 (PST)
Received: from geneva.ucolick.org (localhost [127.0.0.1]) by geneva.ucolick.org (Postfix) with ESMTP id EBDF671A; Thu, 14 Jan 2021 08:46:46 -0800 (PST)
Received: (from sla@localhost) by geneva.ucolick.org (8.14.7/8.14.7/Submit) id 10EGkkn1005311; Thu, 14 Jan 2021 08:46:46 -0800
Date: Thu, 14 Jan 2021 08:46:46 -0800
From: Steve Allen <sla@ucolick.org>
To: Ujjwal Sharma <ryzokuken@igalia.com>
Cc: calsify@ietf.org
Message-ID: <20210114164646.GA4932@ucolick.org>
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com>
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/HK_LKPro1bLnIKgb6hQNMuSpzjA>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2021 16:46:50 -0000

On Thu 2021-01-14T08:18:20+0530 Ujjwal Sharma hath writ:
> I'll make a few more changes, release a 01 version, ask for more
> feedback and then let you know, hopefully by the end of this week.

Also note that cesium hyperfine frequency of 9192631770 had
not been measured until 1958, therefore that cannot be the
definition of a second before that year.  That cesium second
was not adopted by the SI until 1967 August.

Before 1970 the only second which was broadly available was the mean
solar second.  The mean solar second was the basis of available civil
time since the 18th century and the official basis of civil time
from 1884 until 1972.

In order to give meaning to civil timestamps before 1972
the document must mention the mean solar second.

--
Steve Allen                    <sla@ucolick.org>              WGS-84 (GPS)
UCO/Lick Observatory--ISB 260  Natural Sciences II, Room 165  Lat  +36.99855
1156 High Street               Voice: +1 831 459 3046         Lng -122.06015
Santa Cruz, CA 95064           https://www.ucolick.org/~sla/  Hgt +250 m


From nobody Thu Jan 14 09:49:11 2021
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DD98A3A149D; Thu, 14 Jan 2021 09:49:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: Daniel Migault <daniel.migault@ericsson.com>, The IESG <iesg@ietf.org>, barryleiba@gmail.com, calext-chairs@ietf.org, calsify@ietf.org, daniel.migault@ericsson.com, draft-ietf-calext-eventpub-extensions@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <161064654587.26242.17852707050677457873@ietfa.amsl.com>
Date: Thu, 14 Jan 2021 09:49:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/m8z8irkWyoOFiU0nyNcQxcsXeDM>
Subject: [calsify] Protocol Action: 'Event Publishing Extensions to iCalendar' to Proposed Standard (draft-ietf-calext-eventpub-extensions-18.txt)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2021 17:49:06 -0000

The IESG has approved the following document:
- 'Event Publishing Extensions to iCalendar'
  (draft-ietf-calext-eventpub-extensions-18.txt) as Proposed Standard

This document is the product of the Calendaring Extensions Working Group.

The IESG contact persons are Murray Kucherawy and Barry Leiba.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/




Technical Summary

   This specification updates [RFC5545]  and [RFC5546] by introducing a
   number of new iCalendar properties and components which are of
   particular use for event publishers and in social networking.

   This specification also defines a new STRUCTURED-DATA property for
   iCalendar [RFC5545] to allow for data that is directly pertinent to
   an event or task to be included with the calendar data.

Working Group Summary

   The document did not raised any controversy, but in my opinion
   the document would need some more feed backs from the community.
   At this point we mostly rely on the experience of the author as well as
   his own implementation.  

Document Quality

   Michael has a partial implementation.

Personnel

   Daniel Migault is the document shepherd and Barry Leiba is the responsible AD. 


RFC Editor Notes

There's one minor issue in Section 10.2 that needs correction during editing:

OLD
without those participant's express permission.
NEW
without the express permission of the participants whose location would be exposed.
END


From nobody Fri Jan 22 04:19:52 2021
Return-Path: <ryzokuken@igalia.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8B7B3A127B for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 04:19:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.861
X-Spam-Level: 
X-Spam-Status: No, score=-0.861 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.262, RCVD_IN_SORBS_WEB=1.5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=igalia.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aaJ9TPmQbR5W for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 04:19:39 -0800 (PST)
Received: from fanzine.igalia.com (fanzine.igalia.com [178.60.130.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D30C83A1299 for <calsify@ietf.org>; Fri, 22 Jan 2021 04:19:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com;  s=20170329;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject; bh=ywZEbSfB0tTn7yK1IC1VqAuWljnchnv36KObVw7SdSM=;  b=b0WLltHYzPWQvcNnA6xqYrLA8R94/SHbp1ZlQAL7f1PFbh4HIDZaQeLzdpB32nd8UF7WtrxI3JhaSd5ejzNTvvYCoVBB/usypChCY69Td8cu3YqDVctTFqPFb5KJGkTtrVs/PYsZw3OLZ60zCGwZ9VO0y8ejRuGCl54P2I6Jm8LFKV6sUWEhUbYYxfO3zQt6S5ldt9Zh5qV3zLUmkPU+WJq+5vNdORmy6NUL6rZQ/FI6gq6a2SiUXe6/kscqTNaMgSd1ba0tnnTsgq71/BCcRNimEIS/XdZuGz5pXIN9Ykg6J4pfMnlGcDvF611IOakgDrFbiWWksBh+FW7YkRrlJg==;
Received: from [183.83.210.210] (helo=[192.168.0.190]) by fanzine.igalia.com with esmtpsa  (Cipher TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim) id 1l2vPX-00074f-C5 for <calsify@ietf.org>; Fri, 22 Jan 2021 13:19:31 +0100
To: calsify@ietf.org
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <0275d5af-6eea-4608-913e-c96d59c0abea@dogfood.fastmail.com>
From: Ujjwal Sharma <ryzokuken@igalia.com>
Organization: Igalia S.L.
Message-ID: <c87c068b-02f1-913a-64ef-497f827fc3ea@igalia.com>
Date: Fri, 22 Jan 2021 17:49:19 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <0275d5af-6eea-4608-913e-c96d59c0abea@dogfood.fastmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/EJbldGGCTgBKPvlCYE2bjBpfCxQ>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 12:19:51 -0000

Hi Bron, CalExt Friends!

I made a new revision of the draft, which shifts the focus to defining
the syntax/format and defers the standardization of the actual key-value
pairs to sibling organizations like IANA and Unicode Consortium.

I'd love to hear your opinions on this version, which you can find at
https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/,
which can be filed as issues on the GitHub repository or emailed to me
directly. In the meantime, I will address the remaining concerns/polish
issues like fixing the references section.

How "complete" does the document need to be in order to initiate the
call for adoption? If the current version works, can we start it as soon
as possible? Of course, if my understanding of "adoption" is correct,
I'd be happy to iterate on the document further after the adoption by
the WG.

Best,
Ujjwal

On 14/01/2021 8.34 am, Bron Gondwana wrote:
> Sounds great.  Let me know :)
> 
> When we do the call for adoption I'll also advertise the fact over to
> the wider IETF - probably dispatch and tzdata lists at least.
> 
> Cheers,
> 
> Bron.
> 
> 
> On Thu, Jan 14, 2021, at 13:48, Ujjwal Sharma wrote:
>> Thanks Bron!
>>
>> I'll make a few more changes, release a 01 version, ask for more
>> feedback and then let you know, hopefully by the end of this week.
>>
>> Ujjwal
>>
>> On 14/01/2021 7.03 am, Bron Gondwana wrote:
>> > I can do a call for adoption straight away if you like - the next
>> > meeting isn't for a couple of months.
>> > 
>> > Bron.
>> > 
>> > On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:
>> >> One question: given things move forward smoothly, how do I proceed?
>> >> Should I apply for this document to be adopted by the calext WG? I
>> >> suppose the fastest way to proceed is to present it at the next IETF
>> >> meeting?
>> >>
>> >>
>> >>
>> >> Ujjwal
>> >>
>> >> On 12/01/2021 4.03 am, Ujjwal Sharma wrote:
>> >> > Hi Calsify folks!
>> >> > 
>> >> > I am sorry for the long delay, I got a little sidetracked working on
>> >> > other things, but I'm happy to inform you all that I have
>> something that
>> >> > resembles a first draft for the updated timestamps RFC.
>> >> > 
>> >> > Here's where you can find it:
>> >> > 
>> >> > Datatracker:
>> >>
>> > https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
>> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/>
>> >>
>> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
>> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/>>
>> >> >
>> >>
>> GitHub: https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
>> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>
>> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
>> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>>
>> >> > 
>> >> > I would request you all to take a look at it when you can and let me
>> >> > know what you think. You can file a GitHub issue or email me
>> directly.
>> >> > 
>> >> > There's a few open discussions regarding the exact format and how the
>> >> > interaction with bodies like the Unicode consortium work, so
>> please feel
>> >> > free to send me your thoughts regarding that as well.
>> >> > 
>> >> > Also, some references/bibliography is not perfectly functional yet
>> >> > because I am still relatively new to authoring RFCs using
>> Metanorma but
>> >> > I'm actively looking into it.
>> >> > 
>> >> > Thanks and looking forward to hear from you,
>> >> > Ujjwal
>> >> > 
>> >>
>> >> -- 
>> >> Ujjwal "Ryzokuken" Sharma (he/him)
>> >>
>> >> Compilers Hacker, Node.js Core Collaborator and Speaker
>> >>
>> >> _______________________________________________
>> >> calsify mailing list
>> >> calsify@ietf.org <mailto:calsify@ietf.org> <mailto:calsify@ietf.org
>> <mailto:calsify@ietf.org>>
>> >> https://www.ietf.org/mailman/listinfo/calsify
>> <https://www.ietf.org/mailman/listinfo/calsify>
>> >> <https://www.ietf.org/mailman/listinfo/calsify
>> <https://www.ietf.org/mailman/listinfo/calsify>>
>> >>
>> > 
>> > --
>> >   Bron Gondwana, CEO, Fastmail Pty Ltd
>> >   brong@fastmailteam.com <mailto:brong@fastmailteam.com>
>> > 
>> > 
>> > _______________________________________________
>> > calsify mailing list
>> > calsify@ietf.org <mailto:calsify@ietf.org>
>> > https://www.ietf.org/mailman/listinfo/calsify
>> <https://www.ietf.org/mailman/listinfo/calsify>
>> > 
>>
>> -- 
>> Ujjwal "Ryzokuken" Sharma (he/him)
>>
>> Compilers Hacker, Node.js Core Collaborator and Speaker
>>
>> _______________________________________________
>> calsify mailing list
>> calsify@ietf.org <mailto:calsify@ietf.org>
>> https://www.ietf.org/mailman/listinfo/calsify
>> <https://www.ietf.org/mailman/listinfo/calsify>
>>
> 
> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd
>   brong@fastmailteam.com
> 
> 
> 
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
> 

-- 
Ujjwal "Ryzokuken" Sharma (he/him)

Compilers Hacker, Node.js Core Collaborator and Speaker


From nobody Fri Jan 22 08:16:25 2021
Return-Path: <ryzokuken@igalia.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 781D23A12B9 for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 08:16:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.861
X-Spam-Level: 
X-Spam-Status: No, score=-0.861 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.262, RCVD_IN_SORBS_WEB=1.5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=igalia.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sHTJaacBuJQh for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 08:16:17 -0800 (PST)
Received: from fanzine.igalia.com (fanzine.igalia.com [178.60.130.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F13EC3A12B7 for <calsify@ietf.org>; Fri, 22 Jan 2021 08:16:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com;  s=20170329;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject; bh=cJwsORnd7eyDJVejJXLB5DM5c1tiMWEWcrq97SXquk4=;  b=HxuPI6ny3MQ8Rutbak9jxFAlfdMnagsXi/jQZRtH5vMMGU7JIr2dwvduSlhPxLdWkfNLFuzsduI1+J/J4zJ51eH0xjm37px+ItqTYuumzI5dZwpeu/2XW6Gdo7LMPHTJZZWOH+iEP44/UFMnGWkH7vZ39b/Y3trcwuCT5xDJJvyedKmRYz7SfJo3m73Yv+BKlqZ8tmMr2dri4i/MXwkKqhxvsikoERElJAAj9HvkaNcvblyiKLSjIIJQ3umnpm83Y/PQEHrCvyh62LujCakke+drfkHcPOi5XfXCSmtEal8dD6MNiH00XYAx4pbBc4tqdUwwnoQu3buDo9clo6QUMw==;
Received: from [183.83.210.210] (helo=[192.168.0.190]) by fanzine.igalia.com with esmtpsa  (Cipher TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim) id 1l2z6b-00028Y-74; Fri, 22 Jan 2021 17:16:13 +0100
To: Steve Allen <sla@ucolick.org>
Cc: calsify@ietf.org
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <20210114164646.GA4932@ucolick.org>
From: Ujjwal Sharma <ryzokuken@igalia.com>
Organization: Igalia S.L.
Message-ID: <8ae850cd-3d62-0834-5532-5f5ef14f7185@igalia.com>
Date: Fri, 22 Jan 2021 21:46:02 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <20210114164646.GA4932@ucolick.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/43a7gJyPb2-GOsO7RMlDWvYrbDA>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 16:16:23 -0000

Hi Steve!

Sorry for taking a while before responding to your emails.

Talking specifically about your concerns:

> This document needs to define the meaning of time using a term other
> than UTC for any date prior to 1960.


and

> Also note that cesium hyperfine frequency ... cesium second

> was not adopted by the SI until 1967 August.

For both of these, I like have to point out that none of these
definitions were added in this update and belong to the original RFC
(RFC 3339). That said, if folks agree that the original RFC incorrectly
defines these terms and they need to be updated, I'd be happy to correct
them in the next revision of the draft.

That said, I would have to point out that my knowledge in this space is
rather limited and therefore it would be best if you recommended exactly
what the replacement should be. To take things further, you could also
make a pull request to the project at
https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
or email me a git patch if you prefer that.

Thanks,
Ujjwal

-- 
Ujjwal "Ryzokuken" Sharma (he/him)

Compilers Hacker, Node.js Core Collaborator and Speaker


From nobody Fri Jan 22 08:39:20 2021
Return-Path: <lear@cisco.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6BDD3A1360 for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 08:39:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.973
X-Spam-Level: 
X-Spam-Status: No, score=-9.973 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PouCOvEk27Hj for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 08:39:16 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E145B3A12D8 for <calsify@ietf.org>; Fri, 22 Jan 2021 08:39:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3093; q=dns/txt; s=iport; t=1611333556; x=1612543156; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=YnSVV+vsbQuNZ1hV6U96DzCdwmXqZ8sIGtM6+ERCCpU=; b=KnoYv7CgdBCao4bu530BKV5R/7wYW1CMr7oRh3UgDaod1MIL6g+eH3pd Mx6JuFqDrJFBEho6yi/SZOWh8mmCsBSzUsTD7fp+yWoX+69JpI6lAvbXy Oyk2Y/lvcia6h2GaDUSuKoD2U6m1cDqefOxxjsBOCZh4OhxbFoygymhLG s=;
X-Files: signature.asc : 488
X-IPAS-Result: =?us-ascii?q?A0DGBAAI/wpg/xbLJq1iHQEBAQEJARIBBQUBgg+DIVcBI?= =?us-ascii?q?BIvhECJBIhTA5pZgWgEBwEBAQoDAQEYCwwEAQGEBkQCgXkmOBMCAwEBAQMCA?= =?us-ascii?q?wEBAQEFAQEBAgEGBHGFYQyFcwEBAQMBAQEhSwsFCwsOCioCAicwBhODJgGCZ?= =?us-ascii?q?iAPsjB2gTKFWYRyCgaBOIFTi2hBggCBOByBWH4+gl0BAYEqAQsHAYM6NIIsB?= =?us-ascii?q?IFlX2QEU08HBT1FDIEJm3acMoMBgymBN4RQkjsDFgmDK49rj16WJYkXkX9Gg?= =?us-ascii?q?3ACBAYFAhaBbSMqPXAzGggbFTsqAYI+PhIZDY4tF4NOhRSFRUADMDcCBgEJA?= =?us-ascii?q?QEDCYlAgkYBAQ?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.79,367,1602547200";  d="asc'?scan'208";a="30433851"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 22 Jan 2021 16:39:11 +0000
Received: from [10.61.238.30] ([10.61.238.30]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 10MGdBQo002872 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 22 Jan 2021 16:39:11 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <EF6610AB-2A2B-485F-B3F2-E91F8751C21F@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_CF5F5B72-CCCC-43D8-B0EE-77D39569DAAD"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Fri, 22 Jan 2021 17:39:10 +0100
In-Reply-To: <8ae850cd-3d62-0834-5532-5f5ef14f7185@igalia.com>
Cc: Steve Allen <sla@ucolick.org>, calsify@ietf.org
To: Ujjwal Sharma <ryzokuken@igalia.com>
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <20210114164646.GA4932@ucolick.org> <8ae850cd-3d62-0834-5532-5f5ef14f7185@igalia.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
X-Outbound-SMTP-Client: 10.61.238.30, [10.61.238.30]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/Llo7vnwRD3VcOAU-vCjRV6E5RnU>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 16:39:20 -0000

--Apple-Mail=_CF5F5B72-CCCC-43D8-B0EE-77D39569DAAD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

RFC 3339 or ISO 8601 is used all over the place.  It=E2=80=99s used in =
logging, email, and a great many other things.  Before the IETF goes =
monkeying with it, could the authors discuss what is driving this =
change?  What do you want people to do that they didn=E2=80=99t do =
before, and what do you want them to stop doing, and why?

Also, I suggest that this work should go through DISPATCH.  There are a =
lot of other questions.  Here=E2=80=99s one: is the IETF really the =
right organization to do this work in? ISO wrote the underlying spec.  =
They presumably thought about it a lot.

Eliot



> On 22 Jan 2021, at 17:16, Ujjwal Sharma <ryzokuken@igalia.com> wrote:
>=20
> Hi Steve!
>=20
> Sorry for taking a while before responding to your emails.
>=20
> Talking specifically about your concerns:
>=20
>> This document needs to define the meaning of time using a term other
>> than UTC for any date prior to 1960.
>=20
>=20
> and
>=20
>> Also note that cesium hyperfine frequency ... cesium second
>=20
>> was not adopted by the SI until 1967 August.
>=20
> For both of these, I like have to point out that none of these
> definitions were added in this update and belong to the original RFC
> (RFC 3339). That said, if folks agree that the original RFC =
incorrectly
> defines these terms and they need to be updated, I'd be happy to =
correct
> them in the next revision of the draft.
>=20
> That said, I would have to point out that my knowledge in this space =
is
> rather limited and therefore it would be best if you recommended =
exactly
> what the replacement should be. To take things further, you could also
> make a pull request to the project at
> https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
> or email me a git patch if you prefer that.
>=20
> Thanks,
> Ujjwal
>=20
> --
> Ujjwal "Ryzokuken" Sharma (he/him)
>=20
> Compilers Hacker, Node.js Core Collaborator and Speaker
>=20
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify


--Apple-Mail=_CF5F5B72-CCCC-43D8-B0EE-77D39569DAAD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAmAK/64ACgkQh7ZrRtnS
ejNemAf/VjIXCmCAyiZUfPs4zctAjRl/oANYAoeJqtvVOLmteXhHNrGfsRj1Ocpn
JsSFepuO7B4P/oTJGeTwWcWgcSOUAPrmgNE9zQn/2my9FUzv3vW4gxgSaEeIM5SF
fOL4QsA5yYTIJa7mKnrhm3WbwLDZZyi2cJuh1OvmxC6t9NJ/f1ScbKXhMOO5ZQH9
+I3Wb4UEUwbkwm/DDN7n+7p6v5uH/j6hlhUXb2R3th688l2uYQg+7Xv9bKW8cIHG
6GjTCABmSvuNcf6q74+agBZ98Q6trrmwTUoVdHryQHGJeu1y1gsonIgzlj0PqWet
ut5sb4k532ikvQGZCNVtNaoCLQi5/A==
=Q9R7
-----END PGP SIGNATURE-----

--Apple-Mail=_CF5F5B72-CCCC-43D8-B0EE-77D39569DAAD--


From nobody Fri Jan 22 10:54:15 2021
Return-Path: <ned.freed@mrochek.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 064463A13FE for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 10:54:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TMrf9TNta1jQ for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 10:54:11 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [98.153.82.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A62A63A13FC for <calsify@ietf.org>; Fri, 22 Jan 2021 10:54:11 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RUOD5H23U800EZ4C@mauve.mrochek.com> for calsify@ietf.org; Fri, 22 Jan 2021 10:49:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712;  t=1611341347; bh=zNX692zqpdhthr+o4AufFc9I2dMgsmf8u0/SpIvggUo=;  h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=mHbqcOXdUKieGvWLoG9sNBpjujQl7LoN9N+FRnXsq+4ivu3ZVrg/uBzXlqmjAyq4/ +S/1n6yIJjXFFBUPKrJzcdIqtXwE4L7c7Rn0mmVGqEdjFtYsNpHeN4CWyM2eYKFYOY m8kM+5o48NmZ2W0BTUQ8vB/ShZaQATt9pdCK8do8=
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-type: TEXT/PLAIN; charset=utf-8
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RUAOXM63XS005PTU@mauve.mrochek.com>; Fri, 22 Jan 2021 10:49:04 -0800 (PST)
Cc: Ujjwal Sharma <ryzokuken@igalia.com>, calsify@ietf.org
Message-id: <01RUOD5EF5WO005PTU@mauve.mrochek.com>
Date: Fri, 22 Jan 2021 10:47:18 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Fri, 22 Jan 2021 17:39:10 +0100" <EF6610AB-2A2B-485F-B3F2-E91F8751C21F@cisco.com>
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <20210114164646.GA4932@ucolick.org> <8ae850cd-3d62-0834-5532-5f5ef14f7185@igalia.com> <EF6610AB-2A2B-485F-B3F2-E91F8751C21F@cisco.com>
To: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/B_dT1fWoKpa711zDZORaWD1IAc0>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 18:54:13 -0000

> RFC 3339 or ISO 8601 is used all over the place.  It’s used in logging,
> email, and a great many other things.  Before the IETF goes monkeying with it,
> could the authors discuss what is driving this change?  What do you want people
> to do that they didn’t do before, and what do you want them to stop doing,
> and why?

+1. The stability of this specification has been invaluable.

> Also, I suggest that this work should go through DISPATCH.  There are a lot
> of other questions.  Here’s one: is the IETF really the right organization to
> do this work in? ISO wrote the underlying spec.  They presumably thought about
> it a lot.

+1. And if there's some sort of liason with ISO or whoever is responsible 
for this, they should be engaged.

				Ned




> > On 22 Jan 2021, at 17:16, Ujjwal Sharma <ryzokuken@igalia.com> wrote:
> >
> > Hi Steve!
> >
> > Sorry for taking a while before responding to your emails.
> >
> > Talking specifically about your concerns:
> >
> >> This document needs to define the meaning of time using a term other
> >> than UTC for any date prior to 1960.
> >
> >
> > and
> >
> >> Also note that cesium hyperfine frequency ... cesium second
> >
> >> was not adopted by the SI until 1967 August.
> >
> > For both of these, I like have to point out that none of these
> > definitions were added in this update and belong to the original RFC
> > (RFC 3339). That said, if folks agree that the original RFC incorrectly
> > defines these terms and they need to be updated, I'd be happy to correct
> > them in the next revision of the draft.
> >
> > That said, I would have to point out that my knowledge in this space is
> > rather limited and therefore it would be best if you recommended exactly
> > what the replacement should be. To take things further, you could also
> > make a pull request to the project at
> > https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
> > or email me a git patch if you prefer that.
> >
> > Thanks,
> > Ujjwal
> >
> > --
> > Ujjwal "Ryzokuken" Sharma (he/him)
> >
> > Compilers Hacker, Node.js Core Collaborator and Speaker
> >
> > _______________________________________________
> > calsify mailing list
> > calsify@ietf.org
> > https://www.ietf.org/mailman/listinfo/calsify



From nobody Fri Jan 22 11:33:42 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E90D3A14BE; Fri, 22 Jan 2021 11:33:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level: 
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nQxlDKNVCpUo; Fri, 22 Jan 2021 11:33:32 -0800 (PST)
Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com [209.85.208.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6D233A14CA; Fri, 22 Jan 2021 11:33:28 -0800 (PST)
Received: by mail-lj1-f182.google.com with SMTP id l12so5294303ljc.3; Fri, 22 Jan 2021 11:33:28 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=kXlVSx72RjGxQpYMayLmQXrY8DS6OcKtBPJfEKsGZEE=; b=grdyL3u2tCHM96MqwnjXLuarDpfFNlK3wpSMFDFuPm9f43FSmc/uJmz5O1IVNf878T llSInOrp3GrmiEV4d9r8D5gvK2FxSYtpkCmbyuJbaiVbXbQ78ImQEHJxGpPDFlKNtuUG v/hFWMj+mD7w98LNTkmgdKc8aYaRXOI0Kj5MPW+3kKkF62tIAXniBOdIQcWk1HDaIjqG 3kPfBJY2HtStyb0jEjl53WdL0KD76aJ9T0/Cu+HSZepB4tkcz1wfx6WRad3ufbQaJTD3 UeNH0SoU9cfcf/wmgk49ZYcnViMpOGruX2NQ0Dy+F7JhjTaAda4sa/QPZWfWcXkJLAoo uucQ==
X-Gm-Message-State: AOAM532gAkzqVlgqcDwYrcrxTRLwHWJ3fN3quL0OK63hGHYMhtsq0Mma 69pXXZQk0qSTHZvvrzQhJpLClfExTbERpz8QqlwxUGg8
X-Google-Smtp-Source: ABdhPJwdwgjq3THrQDPeM44yVEWe8UmlA45qwhWexA2AqdR7m5WpNLS170CkWoN5cY0hMwSRYfp0rbEb+qQQJnsxWYQ=
X-Received: by 2002:a2e:959a:: with SMTP id w26mr1012610ljh.113.1611344001424;  Fri, 22 Jan 2021 11:33:21 -0800 (PST)
MIME-Version: 1.0
References: <CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com>
In-Reply-To: <CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 22 Jan 2021 14:33:09 -0500
Message-ID: <CALaySJLUOqiVbi1GSA6YXa4CZd9kwop8mkNdMGTOjEYS6NLXsw@mail.gmail.com>
To: draft-ietf-calext-valarm-extensions.all@ietf.org
Cc: calsify@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/4s-7R5vTQponuHGhb7v8ASgSMWA>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 19:33:41 -0000

It's been about a month and a half, and I haven't seen any response to
this review.  What's the status, please?

Barry

On Thu, Dec 3, 2020 at 4:15 PM Barry Leiba <barryleiba@computer.org> wrote:
>
> Most of my comments are minor, but there are a couple of things to
> discuss (particularly how to handle the ABNF).  I'm going to put this
> in "revised I-D needed", but let's talk about the things that need
> discussion before submitting a revision for the others.
>
> =E2=80=94 Section 2 =E2=80=94
> There=E2=80=99s no need for the =E2=80=9C[1]=E2=80=9D citation, and it on=
ly messes up idnits.
> Please remove it and the =E2=80=9CURLs=E2=80=9D section at the end.
>
> =E2=80=94 Section 3 =E2=80=94
>
> My biggest issue here is with the ABNF, so let=E2=80=99s please have a
> discussion about it.
>
> First, some minor things:
>
> 1. This is probably a good time to pay attention to BCP 178 (RFC 6648) by
> removing the x-prop construction (and x-name elsewhere in the draft).
>
> 2. Why is there a need to define new constructs (=E2=80=9Calarmcext=E2=80=
=9D,
> =E2=80=9Caudiopropext=E2=80=9D, and so on), rather than just re-defining =
the base ones
> (=E2=80=9Calarmc=E2=80=9D, =E2=80=9Caudioprop=E2=80=9D, =E2=80=A6)?  It s=
eems to me that this just confuses
> things, and the point here is to make changes that are compatible, but
> more readily extensible.
>
> Now, the big one:
>
> 3. I have never liked the way iCalendar did its ABNF, to the point
> where I think it=E2=80=99s wrong and harmful, causing confusion and not
> permitting automated processing of the ABNF.  It relies on normative
> comments where that=E2=80=99s not necessary, and ABNF was never intended =
to be
> usef that way.  Comments are meant to be explanatory, and normative
> comments are meant to be used only as a last resort, when you can=E2=80=
=99t
> express what you need in the formal language.  I would much rather
> limit the comments to a statment that elements can appear in any
> order, and then use the ABNF to convey whether the elements are
> required and how many times they can appear.
>
> Taking =E2=80=9Calarmprop=E2=80=9D as an example, here=E2=80=99s a re-wri=
te of it in the way
> ABNF should be representing it:
>
> OLD
>    alarmprop  =3D *(
>
>                 ; the following are REQUIRED,
>                 ; but MUST NOT occur more than once
>
>                 action / trigger /
>
>                 ; one set of action properties MUST be
>                 ; present and MUST match the action specified
>                 ; in the ACTION property
>
>                 actionprops /
>
>                 ; the following is OPTIONAL,
>                 ; and MAY occur more than once
>
>                 x-prop / iana-prop
>
>                 )
> NEW
>    alarmprop  =3D ; the elements herein may appear in any order,
>                 ; and the order is not significant.
>
>                 action
>                 trigger
>
>                 actionprops ; MUST match the action specified
>                             ; in the ACTION property
>
>                 [*iana-prop]
> END
>
> For =E2=80=9Caudiopropext=E2=80=9D:
>
> OLD
>    audiopropext  =3D *(
>
>                    ; 'duration' and 'repeat' are both OPTIONAL,
>                    ; and MUST NOT occur more than once each,
>                    ; but if one occurs, so MUST the other
>
>                    duration / repeat /
>
>                    ; the following is OPTIONAL,
>                    ; but MUST NOT occur more than once
>
>                    attach
>
>                    )
> NEW
>    audiopropext  =3D ; the elements herein may appear in any order,
>                    ; and the order is not significant.
>                    [duration repeat]
>                    [attach]
>                    )
> END
>
> Is there really a good reason not to move in this direction?  The
> mechanism of saying that everything can appear zero or more times, and
> then limiting that with comments seems very poor.
>
> =E2=80=94 Section 6.1 =E2=80=94
>
>       Certain
>       kinds of alarm may not provide feedback as to when the calendar
>       user sees them, for example email based alerts.
>
> Nit: This sentence isn=E2=80=99t properly ordered (and has a couple of ot=
her
> nit-level errors).
>
> NEW
>       Certain
>       kinds of alarms, such as email-based alerts, might not provide
>       feedback as to when the calendar user sees them.
> END
>
> =E2=80=94 Section 7 =E2=80=94
>
>    Clients SHOULD add a "RELATED-TO" property to the new "VALARM"
>    component with a value set to the "UID" property value of the
>    "VALARM" component being snoozed.  If the "VALARM" component being
>    snoozed does not already have a "UID" property, the client SHOULD add
>    one.  The "RELATED-TO" property added to the new "VALARM" component
>    SHOULD include a "RELTYPE" property parameter with a value set to
>    "SNOOZE".
>
> Why the SHOULDs?  This is new function; why are these not MUSTs?
>
>    When the "snooze" alarm is triggered and dismissed the client SHOULD
>    remove the corresponding "VALARM" component, or set the
>    "ACKNOWLEDGED" property (see Section 6.1).  Alternatively, if the
>    "snooze" alarm is itself "snoozed", the client SHOULD remove the
>    original "snooze" alarm and create a new one, with the appropriate
>    trigger time and relationship set.
>
> Same here about the SHOULDs.  Also, it=E2=80=99s not clear to me how this
> relates to the original alarm.  It would be good to say, explicitly,
> that the original VALARM is not removed.  But also, is the
> =E2=80=9CACKNOWLEDGED=E2=80=9D time on the original alarm changed to show=
 the time
> that the snooze was dismissed?  If not, why not?  And is there a
> reason to choose between the apparently equal alternatives presented
> in the first sentence?  Or is the choice entirely up to the
> implementation?
>
> =E2=80=94 Section 7.1 =E2=80=94
>
>    This specification adds the "SNOOZE" relationship type for use with
>    the "RELTYPE" property defined in Section 3.2.15 of [RFC5545].  This
>    is used to relate a "snoozed" "VALARM" component to the original
>    alarm that the "snooze" was generated for.
>
> Maybe I=E2=80=99m being too picky here, but I don=E2=80=99t think the REL=
TYPE of
> SNOOZE is used to relate the alarms: the UID property is used for
> that.  Maybe =E2=80=9CThis is used when relating=E2=80=9D is better wordi=
ng?
>
> =E2=80=94 Section 8.1 =E2=80=94
>
>       When the property value is set to "ARRIVE", the alarm is triggered
>       when the calendar user agent arrives in the vicinity of any of the
>       specified locations.  When set to "DEPART", the alarm is triggered
>       when the calendar user agent departs from the vicinity of any
>       specified locations.
>
> I think we need to more clearly specify =E2=80=9Cvicinity=E2=80=9D here, =
even if it=E2=80=99s
> just to say that the definition is up to the implementation.  As it
> is, I don=E2=80=99t know whether I need to depart from my kitchen, from m=
y
> house, from my street, from my town, or whatever.
>
>       When the property value is set to "CONNECT", the alarm is
>       triggered when the calendar user agent connects to a Bluetooth(R)
>       [BTcore]-enabled automobile.  When set to "DISCONNECT", the alarm
>       is triggered when the calendar user agent disconnects from a
>       Bluetooth(R)-enabled automobile.
>
> Nit: It=E2=80=99s odd to have the citation in the middle of the compound
> modifier.  I suggest rewriting to avoid the problem:
>
> NEW
>       When the property value is set to "CONNECT", the alarm is
>       triggered when the calendar user agent connects to an automobile
>       that is enabled for Bluetooth(R) [BTcore].  When set to
>       "DISCONNECT", the alarm is triggered when the calendar user agent
>       disconnects from a Bluetooth(R)-enabled automobile.
> END
>
>    Example:  The following is an example of this property:
>    PROXIMITY:ARRIVE
>
> I think this example is useless, as it=E2=80=99s incomplete without the g=
eo
> location.  And you have Section 8.2 immediately after, so why not just
> remove this?
>
> =E2=80=94 Section 11 =E2=80=94
> Throughout this section, please specify the names and/or URIs of the
> registries, to make it easier for both IANA and other readers to find
> them.  For example, in Section 11.1:
>
> NEW
>    This document defines the following new iCalendar properties to be
>    added to the Properties registry defined in Section 8.2.3 of [RFC5545]
>    and located here:
>    <https://www.iana.org/assignments/icalendar#properties>
> END
>
> --
> Barry


From nobody Fri Jan 22 11:34:47 2021
Return-Path: <murch@fastmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F8453A1474; Fri, 22 Jan 2021 11:34:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.381
X-Spam-Level: 
X-Spam-Status: No, score=-2.381 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=MoLk6ERu; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CilJhX/a
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HftAXDu39Yxe; Fri, 22 Jan 2021 11:34:43 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E2553A146E; Fri, 22 Jan 2021 11:34:43 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id A62DC5C0044; Fri, 22 Jan 2021 14:34:42 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 22 Jan 2021 14:34:42 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=c bOn0vA37jHOoysmoYg1RASdEhG0xEQaFNZ85/2SDnk=; b=MoLk6ERusqU0X1NHo A0wOFk8iLgcRriCUyZgTBeDH3+b6UW3MqmWPak/xfLhPng5/r8sswRkiPjUp47VE cMOJWOgGwxSEFBbI9kEymx3Jcf61KDM+lLkl0vOhJNRqAmbyW55CAZ+zRaQHRPbv 8cAy74Z3yRbpLq4u6O3NUOq8+w18LON2Xsoj1yaEW1ZPr+Eepx+OVVJEdWhZk4Cg 2UjdkGjAdBru+W7EsAsdFRGibEXdilJ8aBPVLTV6IHpGb5pBysr4LA3nuDXZRg/Z JROllCyxsQB4AQSf1YlCoTEqpSxe6vdajDnXk2mNph95SARuYOquwOjlcYFyUkah Xd3vw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=cbOn0vA37jHOoysmoYg1RASdEhG0xEQaFNZ85/2SD nk=; b=CilJhX/ab1Kvhj5pT0dwMxJiP7cQuPUSgypiuK80187QhwsoP/tyITIYk 6jWWGXAaXEemiEoDKIX56U42SgHoo78+vW54qPHTGWKZuAAMwViQ/qu8lngYi1Gh 46AHbEiXxZJKD8PB8RWBfyG49OgYi7xEY0+UTZDtKdyAYv6evpHd0egzULFMVIVC A6/WWEIytbkldzc+Xv7iZ0GWf1bO3pAgDx32GIclJRZAk7OHMAZL2UShx/VgT7ez ur4KZU2VaLJzNXwqw/GedRtBtqr22x9zrzeoK/9DQFFxHWxo0DNCsw6jXU646rKA w9eeHvNZ0KTMrdb7xcWYsJDqRiisg==
X-ME-Sender: <xms:0SgLYJCwHyJ94c6kiD3hjIFA3AkW6xdnpao6Tfrx0PadRj9W9VsQiA> <xme:0SgLYHip1ew7wYmI2CSetbIKDZ41uon8RN9I22g9gocdy73fR2hx_oTkAWLthtz1Y kwrDP357u2wcg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudeigddufedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomhepmfgvnhcu ofhurhgthhhishhonhcuoehmuhhrtghhsehfrghsthhmrghilhdrtghomheqnecuggftrf grthhtvghrnhepjeejveffvdffgedufeegteevlefhvefffedutefhgfeigfefgfekvedv tddvudehnecuffhomhgrihhnpehirghnrgdrohhrghenucfkphepjeegrdejjedrkeehrd dvhedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep mhhurhgthhesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:0SgLYElQOw8Nq5c6n2aGKGiVczDqdX3Wkws4k9u3XHpKESR0U8aLfA> <xmx:0SgLYDwxklydAMjuHisxwlAHvPHaKwxTwQYs0ozcYd-ljQHRzf9OfQ> <xmx:0SgLYOSiDmqyFA4XM2FBHIZyGlWOq6K3HKFkqYvR0HTLbA7YUmE-Jg> <xmx:0igLYH7NXOcWPt85-3w-vwV6e9VxAvwo_ELrWjRe8VehTyTQLQMLJQ>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 3581B24005D; Fri, 22 Jan 2021 14:34:41 -0500 (EST)
To: Barry Leiba <barryleiba@computer.org>, draft-ietf-calext-valarm-extensions.all@ietf.org
Cc: calsify@ietf.org
References: <CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com> <CALaySJLUOqiVbi1GSA6YXa4CZd9kwop8mkNdMGTOjEYS6NLXsw@mail.gmail.com>
From: Ken Murchison <murch@fastmail.com>
Message-ID: <5ff2e26c-ef9e-f577-805e-fafcdbfa81e2@fastmail.com>
Date: Fri, 22 Jan 2021 14:34:40 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CALaySJLUOqiVbi1GSA6YXa4CZd9kwop8mkNdMGTOjEYS6NLXsw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/3lrD_xfeeQItqbCVmp2iWMbO8V0>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 19:34:46 -0000

Hi Barry,

Sorry, its been in my queue.  I will try to get to it shortly.


On 1/22/21 2:33 PM, Barry Leiba wrote:
> It's been about a month and a half, and I haven't seen any response to
> this review.  What's the status, please?
>
> Barry
>
> On Thu, Dec 3, 2020 at 4:15 PM Barry Leiba <barryleiba@computer.org> wrote:
>> Most of my comments are minor, but there are a couple of things to
>> discuss (particularly how to handle the ABNF).  I'm going to put this
>> in "revised I-D needed", but let's talk about the things that need
>> discussion before submitting a revision for the others.
>>
>> — Section 2 —
>> There’s no need for the “[1]” citation, and it only messes up idnits.
>> Please remove it and the “URLs” section at the end.
>>
>> — Section 3 —
>>
>> My biggest issue here is with the ABNF, so let’s please have a
>> discussion about it.
>>
>> First, some minor things:
>>
>> 1. This is probably a good time to pay attention to BCP 178 (RFC 6648) by
>> removing the x-prop construction (and x-name elsewhere in the draft).
>>
>> 2. Why is there a need to define new constructs (“alarmcext”,
>> “audiopropext”, and so on), rather than just re-defining the base ones
>> (“alarmc”, “audioprop”, …)?  It seems to me that this just confuses
>> things, and the point here is to make changes that are compatible, but
>> more readily extensible.
>>
>> Now, the big one:
>>
>> 3. I have never liked the way iCalendar did its ABNF, to the point
>> where I think it’s wrong and harmful, causing confusion and not
>> permitting automated processing of the ABNF.  It relies on normative
>> comments where that’s not necessary, and ABNF was never intended to be
>> usef that way.  Comments are meant to be explanatory, and normative
>> comments are meant to be used only as a last resort, when you can’t
>> express what you need in the formal language.  I would much rather
>> limit the comments to a statment that elements can appear in any
>> order, and then use the ABNF to convey whether the elements are
>> required and how many times they can appear.
>>
>> Taking “alarmprop” as an example, here’s a re-write of it in the way
>> ABNF should be representing it:
>>
>> OLD
>>     alarmprop  = *(
>>
>>                  ; the following are REQUIRED,
>>                  ; but MUST NOT occur more than once
>>
>>                  action / trigger /
>>
>>                  ; one set of action properties MUST be
>>                  ; present and MUST match the action specified
>>                  ; in the ACTION property
>>
>>                  actionprops /
>>
>>                  ; the following is OPTIONAL,
>>                  ; and MAY occur more than once
>>
>>                  x-prop / iana-prop
>>
>>                  )
>> NEW
>>     alarmprop  = ; the elements herein may appear in any order,
>>                  ; and the order is not significant.
>>
>>                  action
>>                  trigger
>>
>>                  actionprops ; MUST match the action specified
>>                              ; in the ACTION property
>>
>>                  [*iana-prop]
>> END
>>
>> For “audiopropext”:
>>
>> OLD
>>     audiopropext  = *(
>>
>>                     ; 'duration' and 'repeat' are both OPTIONAL,
>>                     ; and MUST NOT occur more than once each,
>>                     ; but if one occurs, so MUST the other
>>
>>                     duration / repeat /
>>
>>                     ; the following is OPTIONAL,
>>                     ; but MUST NOT occur more than once
>>
>>                     attach
>>
>>                     )
>> NEW
>>     audiopropext  = ; the elements herein may appear in any order,
>>                     ; and the order is not significant.
>>                     [duration repeat]
>>                     [attach]
>>                     )
>> END
>>
>> Is there really a good reason not to move in this direction?  The
>> mechanism of saying that everything can appear zero or more times, and
>> then limiting that with comments seems very poor.
>>
>> — Section 6.1 —
>>
>>        Certain
>>        kinds of alarm may not provide feedback as to when the calendar
>>        user sees them, for example email based alerts.
>>
>> Nit: This sentence isn’t properly ordered (and has a couple of other
>> nit-level errors).
>>
>> NEW
>>        Certain
>>        kinds of alarms, such as email-based alerts, might not provide
>>        feedback as to when the calendar user sees them.
>> END
>>
>> — Section 7 —
>>
>>     Clients SHOULD add a "RELATED-TO" property to the new "VALARM"
>>     component with a value set to the "UID" property value of the
>>     "VALARM" component being snoozed.  If the "VALARM" component being
>>     snoozed does not already have a "UID" property, the client SHOULD add
>>     one.  The "RELATED-TO" property added to the new "VALARM" component
>>     SHOULD include a "RELTYPE" property parameter with a value set to
>>     "SNOOZE".
>>
>> Why the SHOULDs?  This is new function; why are these not MUSTs?
>>
>>     When the "snooze" alarm is triggered and dismissed the client SHOULD
>>     remove the corresponding "VALARM" component, or set the
>>     "ACKNOWLEDGED" property (see Section 6.1).  Alternatively, if the
>>     "snooze" alarm is itself "snoozed", the client SHOULD remove the
>>     original "snooze" alarm and create a new one, with the appropriate
>>     trigger time and relationship set.
>>
>> Same here about the SHOULDs.  Also, it’s not clear to me how this
>> relates to the original alarm.  It would be good to say, explicitly,
>> that the original VALARM is not removed.  But also, is the
>> “ACKNOWLEDGED” time on the original alarm changed to show the time
>> that the snooze was dismissed?  If not, why not?  And is there a
>> reason to choose between the apparently equal alternatives presented
>> in the first sentence?  Or is the choice entirely up to the
>> implementation?
>>
>> — Section 7.1 —
>>
>>     This specification adds the "SNOOZE" relationship type for use with
>>     the "RELTYPE" property defined in Section 3.2.15 of [RFC5545].  This
>>     is used to relate a "snoozed" "VALARM" component to the original
>>     alarm that the "snooze" was generated for.
>>
>> Maybe I’m being too picky here, but I don’t think the RELTYPE of
>> SNOOZE is used to relate the alarms: the UID property is used for
>> that.  Maybe “This is used when relating” is better wording?
>>
>> — Section 8.1 —
>>
>>        When the property value is set to "ARRIVE", the alarm is triggered
>>        when the calendar user agent arrives in the vicinity of any of the
>>        specified locations.  When set to "DEPART", the alarm is triggered
>>        when the calendar user agent departs from the vicinity of any
>>        specified locations.
>>
>> I think we need to more clearly specify “vicinity” here, even if it’s
>> just to say that the definition is up to the implementation.  As it
>> is, I don’t know whether I need to depart from my kitchen, from my
>> house, from my street, from my town, or whatever.
>>
>>        When the property value is set to "CONNECT", the alarm is
>>        triggered when the calendar user agent connects to a Bluetooth(R)
>>        [BTcore]-enabled automobile.  When set to "DISCONNECT", the alarm
>>        is triggered when the calendar user agent disconnects from a
>>        Bluetooth(R)-enabled automobile.
>>
>> Nit: It’s odd to have the citation in the middle of the compound
>> modifier.  I suggest rewriting to avoid the problem:
>>
>> NEW
>>        When the property value is set to "CONNECT", the alarm is
>>        triggered when the calendar user agent connects to an automobile
>>        that is enabled for Bluetooth(R) [BTcore].  When set to
>>        "DISCONNECT", the alarm is triggered when the calendar user agent
>>        disconnects from a Bluetooth(R)-enabled automobile.
>> END
>>
>>     Example:  The following is an example of this property:
>>     PROXIMITY:ARRIVE
>>
>> I think this example is useless, as it’s incomplete without the geo
>> location.  And you have Section 8.2 immediately after, so why not just
>> remove this?
>>
>> — Section 11 —
>> Throughout this section, please specify the names and/or URIs of the
>> registries, to make it easier for both IANA and other readers to find
>> them.  For example, in Section 11.1:
>>
>> NEW
>>     This document defines the following new iCalendar properties to be
>>     added to the Properties registry defined in Section 8.2.3 of [RFC5545]
>>     and located here:
>>     <https://www.iana.org/assignments/icalendar#properties>
>> END
>>
>> --
>> Barry

-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


From nobody Fri Jan 22 13:08:56 2021
Return-Path: <ryzokuken@igalia.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 108ED3A0A1C for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 13:08:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.861
X-Spam-Level: 
X-Spam-Status: No, score=-0.861 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.262, RCVD_IN_SORBS_WEB=1.5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=igalia.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DIl_-oqdCF9W for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 13:08:53 -0800 (PST)
Received: from fanzine.igalia.com (fanzine.igalia.com [178.60.130.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C7633A14FE for <calsify@ietf.org>; Fri, 22 Jan 2021 13:08:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com;  s=20170329;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject; bh=RBkExbl+dEnbcIGpEEnUs4nc2Bjav9myks9gPBDNivI=;  b=DFKvLjIdbmtLJws3/uVUia1B6EjfT4d+FguG8VPN9m0sUw8rWGz8WwkL4onEPWfB0rWdkFv3JktpBXuMx7aYQKRlkfvv42DFd4aBsrDaGzDY9KE3KDrSjwn+e9UqvOgtJWWY6Y/WT+TuLTpRw876tGmRw/GcvD5O8BrE73xtLGXfMLWmRoVSUE1Xf1wryo64rlxtVjnUOf1HYgneS6gLimhDd6a1T+LrKQCBmeH/y6sMDSqkSt0gC2sichUIw/xVT9OHg1hs+xHMsQKlV/hfoU7t8yzWbrMA4zG71d5QTtVpuyjWZIy8ZFdmK+NGqnLaYRxQfho9p1T1fTcWrDbhrg==;
Received: from [183.83.210.210] (helo=[192.168.0.190]) by fanzine.igalia.com with esmtpsa  (Cipher TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim) id 1l33fl-0006it-4a; Fri, 22 Jan 2021 22:08:49 +0100
To: Eliot Lear <lear@cisco.com>
Cc: Steve Allen <sla@ucolick.org>, calsify@ietf.org
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <20210114164646.GA4932@ucolick.org> <8ae850cd-3d62-0834-5532-5f5ef14f7185@igalia.com> <EF6610AB-2A2B-485F-B3F2-E91F8751C21F@cisco.com>
From: Ujjwal Sharma <ryzokuken@igalia.com>
Organization: Igalia S.L.
Message-ID: <4c9b5edf-93fb-d211-ff41-f7ecc4d5b8ab@igalia.com>
Date: Sat, 23 Jan 2021 02:38:36 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <EF6610AB-2A2B-485F-B3F2-E91F8751C21F@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/-YgpHVbP34F_VQUnayZQwoN_AkQ>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 21:08:55 -0000

Hey Elliot!

I answered a couple of these questions in a previous CalExt meeting, but
here goes another attempt at getting them out in writing:

On 22/01/2021 10.09 pm, Eliot Lear wrote:

> RFC 3339 or ISO 8601 is used all over the place.  It’s used in logging, email, and a great many other things.  Before the IETF goes monkeying with it, could the authors discuss what is driving this change?  What do you want people to do that they didn’t do before, and what do you want them to stop doing, and why?

There are many cases in which the information stored within a timestamp
is not enough and implementations need to include additional information
for various reasons. It is common knowledge that Java and Linux among
other implementations include an IANA timezone id suffixed to the
regular timestamp, but I think of it as an unfortunate situation that
this format is not standardized. The aim of this proposal is to:

1. Standardize the existing format.

2. Expand the format to include more information (in case of us, ECMA
TC39, this includes the calendar information which is the biggest reason
that drives us to expand the currently existing format).

3. Make the expansions generalizable enough to allow any additional
future information to be included.

4. Make certain parts of the RFC further future-proof, for example
remove the 2/3-year deprecated format and allow the expanded 6-year
format, which makes this RFC up to date with the newer versions of ISO8601.

> Also, I suggest that this work should go through DISPATCH.  There are a lot of other questions.  Here’s one: is the IETF really the right organization to do this work in? ISO wrote the underlying spec.  They presumably thought about it a lot.

We are already collaborating with the folks over at CalConnect, to
ensure that formats like ISO8601 end up adopting these additions as
well, but the IETF RFC would need to be updated as well, and it helps
ECMA TC39 refer to the RFC when using this format.

I hope these answers help clarify our positions. Feel free to ask me for
any further clarifications.

Thanks,
Ujjwal

-- 
Ujjwal "Ryzokuken" Sharma (he/him)

Compilers Hacker, Node.js Core Collaborator and Speaker


From nobody Fri Jan 22 13:23:52 2021
Return-Path: <ryzokuken@igalia.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BDBC3A150C for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 13:23:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.599
X-Spam-Level: 
X-Spam-Status: No, score=-0.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_SORBS_WEB=1.5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=igalia.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dqe0MYTbtzsd for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 13:23:48 -0800 (PST)
Received: from fanzine.igalia.com (fanzine.igalia.com [178.60.130.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC7C73A150D for <calsify@ietf.org>; Fri, 22 Jan 2021 13:23:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com;  s=20170329;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:To:References:Subject; bh=kt1vVx7UZR/6LbvB+VjaNrRDE6QeD8KHkaodkZJf0H4=;  b=g4HtD/7C1Cfvg8ZFlK1Z479pSfNpQROTjY/gBr/n5lkQyrnTlj7NzDKqSpsyyDNXAT+0RI0inYE5YQNFRWrtSNwdQCS1uEMjtY0hnmTWeHTzp97xE4ZPEMrLU7xqzUdg2Q3mWqXSfuNGGKiHwsgdTDkBm2G82KvMRUvwk8Iv9SSPcXVsbvaaysveLSI+PPPXDpOEC1stPVYirrpQaq9xV8+U24a87WkidK8avcvl5Bxl82cBBOWebBVmbnUWOq+MnZBHDeHf+wjr4gg3yQkIdt5WfQhqHZwNDKYUpCIvNBVW45cszNqrQagbzT7UNx08Ouo2LPVx+XI6PttpnSjySQ==;
Received: from [183.83.210.210] (helo=[192.168.0.190]) by fanzine.igalia.com with esmtpsa  (Cipher TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim) id 1l33uD-00014L-OP; Fri, 22 Jan 2021 22:23:45 +0100
References: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com>
To: "calsify@ietf.org" <calsify@ietf.org>
Cc: Ned Freed <ned.freed@mrochek.com>
From: Ujjwal Sharma <ryzokuken@igalia.com>
Organization: Igalia S.L.
X-Forwarded-Message-Id: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com>
Message-ID: <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com>
Date: Sat, 23 Jan 2021 02:53:34 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/L7JzzyKTBrBml-I30xQ_arpK7dM>
Subject: [calsify] Fwd:  New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 21:23:52 -0000

CCing the Calsify ML because I didn't include it in the original email
by mistake.

-------- Forwarded Message --------
Subject: Re: [calsify] New Timestamp Draft
Date: Sat, 23 Jan 2021 02:51:00 +0530
From: Ujjwal Sharma <ryzokuken@igalia.com>
Organization: Igalia S.L.
To: Ned Freed <ned.freed@mrochek.com>

Hi Ned!

I could not agree with you more on the different matters. Here's the
response to the specific points raised by you.

On 23/01/2021 12.17 am, Ned Freed wrote:
> +1. The stability of this specification has been invaluable.

Please refer to my email to Eliot for more clarification on this.
Overall, this is a goal that I share wholeheartedy, and the whole idea
behind the new draft is to design it in a way that is very generalized
and that allows us to avoid any further additions to it and keep a
similar level of stability. Note for example the deferring of key
selection and standardization to bodies like IANA and Unicode consortium.

> +1. And if there's some sort of liason with ISO or whoever is responsible 
> for this, they should be engaged.

My understanding of the situation has been that this liason would be
CalConnect. By all means, we have been collaborating quite closely with
them, thanks to the amazing efforts of Ronald Tse and have plans to work
with them further to enable greater adoption.

Hope this helps, please feel free to ask for further clarifications.

Best,
Ujjwal

-- 
Ujjwal "Ryzokuken" Sharma (he/him)

Compilers Hacker, Node.js Core Collaborator and Speaker


From nobody Fri Jan 22 15:00:00 2021
Return-Path: <sffc@google.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEEDD3A1532 for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 14:59:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.971
X-Spam-Level: 
X-Spam-Status: No, score=-17.971 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gtF5_jdC4EJb for <calsify@ietfa.amsl.com>; Fri, 22 Jan 2021 14:59:56 -0800 (PST)
Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B5053A1547 for <calsify@ietf.org>; Fri, 22 Jan 2021 14:59:56 -0800 (PST)
Received: by mail-ot1-x32d.google.com with SMTP id 36so6747980otp.2 for <calsify@ietf.org>; Fri, 22 Jan 2021 14:59:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+RL6MyMk+yteWflRlZEngecNdTKo9wn6+DJhC7nLZPg=; b=lj+VyVQqUFUhlmOqDmebXaYJQMPvS50xebMEOvA0NCRaaMxs30lWuTMSMogEWbvHbQ lw3XZZcOR8Sst7uFRG5zRjEF0EEolvOjXHfwoLxv3twgQ8K1rK7uovPh2qpj5KmfsiaP TyfN/2gy/p0UoO6ZI8443BD+P5k4qGajgT1zTqPGriZM75tyjM5IIeS7InWfMbcVTyQW aOJnMOIM1DwY1dX8LkGkCfXaTaAAS5miN1nUJdgmi/mYCcxs5ILmf5X6vCF/wTDlIs+X HTGm+sZS45voE+sj1RA9za3naHQupUJry62/ZKFCFdtZoOI5nHSVSGWjIGJkPkFuresl elew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+RL6MyMk+yteWflRlZEngecNdTKo9wn6+DJhC7nLZPg=; b=L/1JAQ2qCsGm0SltZMebgVol3c/glWYq93x/9wlFlVTmc4OjQ1sotMUjXqpG2M77bY 6xREXaD5N7Ck0LaofUZfgwzxdsA+dMVjtHOEKEoJ+yK400FmURJ6m4uUstt437F3WRSN PMM6t6T7tG5ckBSMpm/rS8JX66twwqVZA4y64qgXhdQwyulBz18Pao6Q9WLXBjWlJn9T vAHH12rzonZCl7lZjCkKhD45lUtejfVZOjOEKq7CzhwGUPXyecn3yF5B5HUCGADZQyH7 7LlxCAWpNz3IDoh06CRUsfzNEx19BgC3gzjVUeKD/ZApnC+vnsUMzEajVNeTTahIjvym h+fg==
X-Gm-Message-State: AOAM531QXQqWcThBBrDk0HTW0aRWe78Tc7eGfhjWbaKOSTFHKHcnPIoh Fm3uQibdV/p6t641Me+Xd5sFHX1RyY30HvM2HhJwAA==
X-Google-Smtp-Source: ABdhPJw7nyI8f+xyquVjUNb2ZZtYrH1DZ9HJlt7gb5vILxdFGLNu6BlUnTvtb8lsGe95vnfOFIzsUt+oGUfV89AI6WM=
X-Received: by 2002:a9d:406:: with SMTP id 6mr4840127otc.36.1611356395602; Fri, 22 Jan 2021 14:59:55 -0800 (PST)
MIME-Version: 1.0
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <20210114164646.GA4932@ucolick.org> <8ae850cd-3d62-0834-5532-5f5ef14f7185@igalia.com> <EF6610AB-2A2B-485F-B3F2-E91F8751C21F@cisco.com> <4c9b5edf-93fb-d211-ff41-f7ecc4d5b8ab@igalia.com>
In-Reply-To: <4c9b5edf-93fb-d211-ff41-f7ecc4d5b8ab@igalia.com>
From: Shane Carr <sffc@google.com>
Date: Fri, 22 Jan 2021 16:59:44 -0600
Message-ID: <CABxsp=mp48hRpfr8o3zPdUYhbredaxc4rKyHPBsgmwcjhiV8XA@mail.gmail.com>
To: Ujjwal Sharma <ryzokuken@igalia.com>
Cc: Eliot Lear <lear@cisco.com>, calsify@ietf.org
Content-Type: multipart/alternative; boundary="00000000000091a0c005b985252c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/YjuSfxN8pqEbi8_2yFguxoShXMU>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 23:00:00 -0000

--00000000000091a0c005b985252c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi all,

I also wanted to point out that this proposed revision to RFC 3339 makes
the syntax a bit more flexible without sacrificing backwards
compatibility.  Implementations that do not concern themselves with IANA
time zones or Unicode extensions can simply ignore those annotations, which
occur at the end of the string.  Since the IANA time zone suffix is already
in common use, and this proposal leverages that existing syntax, we expect
that the impact on the ecosystem will be small.

Shane


On Fri, Jan 22, 2021 at 3:09 PM Ujjwal Sharma <ryzokuken@igalia.com> wrote:

> Hey Elliot!
>
> I answered a couple of these questions in a previous CalExt meeting, but
> here goes another attempt at getting them out in writing:
>
> On 22/01/2021 10.09 pm, Eliot Lear wrote:
>
> > RFC 3339 or ISO 8601 is used all over the place.  It=E2=80=99s used in =
logging,
> email, and a great many other things.  Before the IETF goes monkeying wit=
h
> it, could the authors discuss what is driving this change?  What do you
> want people to do that they didn=E2=80=99t do before, and what do you wan=
t them to
> stop doing, and why?
>
> There are many cases in which the information stored within a timestamp
> is not enough and implementations need to include additional information
> for various reasons. It is common knowledge that Java and Linux among
> other implementations include an IANA timezone id suffixed to the
> regular timestamp, but I think of it as an unfortunate situation that
> this format is not standardized. The aim of this proposal is to:
>
> 1. Standardize the existing format.
>
> 2. Expand the format to include more information (in case of us, ECMA
> TC39, this includes the calendar information which is the biggest reason
> that drives us to expand the currently existing format).
>
> 3. Make the expansions generalizable enough to allow any additional
> future information to be included.
>
> 4. Make certain parts of the RFC further future-proof, for example
> remove the 2/3-year deprecated format and allow the expanded 6-year
> format, which makes this RFC up to date with the newer versions of ISO860=
1.
>
> > Also, I suggest that this work should go through DISPATCH.  There are a
> lot of other questions.  Here=E2=80=99s one: is the IETF really the right
> organization to do this work in? ISO wrote the underlying spec.  They
> presumably thought about it a lot.
>
> We are already collaborating with the folks over at CalConnect, to
> ensure that formats like ISO8601 end up adopting these additions as
> well, but the IETF RFC would need to be updated as well, and it helps
> ECMA TC39 refer to the RFC when using this format.
>
> I hope these answers help clarify our positions. Feel free to ask me for
> any further clarifications.
>
> Thanks,
> Ujjwal
>
> --
> Ujjwal "Ryzokuken" Sharma (he/him)
>
> Compilers Hacker, Node.js Core Collaborator and Speaker
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>

--00000000000091a0c005b985252c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>I also wanted to point out that=
 this proposed revision to RFC 3339 makes the syntax a bit more flexible wi=
thout sacrificing backwards compatibility.=C2=A0 Implementations that do no=
t concern themselves with IANA time zones or Unicode extensions can simply =
ignore those annotations, which occur at the end of the string.=C2=A0 Since=
 the IANA time zone suffix is already in common use, and this proposal leve=
rages that existing syntax, we expect that the impact on the ecosystem will=
 be small.</div><div><br></div><div>Shane</div><div><br></div></div><br><di=
v class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 2=
2, 2021 at 3:09 PM Ujjwal Sharma &lt;<a href=3D"mailto:ryzokuken@igalia.com=
">ryzokuken@igalia.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">Hey Elliot!<br>
<br>
I answered a couple of these questions in a previous CalExt meeting, but<br=
>
here goes another attempt at getting them out in writing:<br>
<br>
On 22/01/2021 10.09 pm, Eliot Lear wrote:<br>
<br>
&gt; RFC 3339 or ISO 8601 is used all over the place.=C2=A0 It=E2=80=99s us=
ed in logging, email, and a great many other things.=C2=A0 Before the IETF =
goes monkeying with it, could the authors discuss what is driving this chan=
ge?=C2=A0 What do you want people to do that they didn=E2=80=99t do before,=
 and what do you want them to stop doing, and why?<br>
<br>
There are many cases in which the information stored within a timestamp<br>
is not enough and implementations need to include additional information<br=
>
for various reasons. It is common knowledge that Java and Linux among<br>
other implementations include an IANA timezone id suffixed to the<br>
regular timestamp, but I think of it as an unfortunate situation that<br>
this format is not standardized. The aim of this proposal is to:<br>
<br>
1. Standardize the existing format.<br>
<br>
2. Expand the format to include more information (in case of us, ECMA<br>
TC39, this includes the calendar information which is the biggest reason<br=
>
that drives us to expand the currently existing format).<br>
<br>
3. Make the expansions generalizable enough to allow any additional<br>
future information to be included.<br>
<br>
4. Make certain parts of the RFC further future-proof, for example<br>
remove the 2/3-year deprecated format and allow the expanded 6-year<br>
format, which makes this RFC up to date with the newer versions of ISO8601.=
<br>
<br>
&gt; Also, I suggest that this work should go through DISPATCH.=C2=A0 There=
 are a lot of other questions.=C2=A0 Here=E2=80=99s one: is the IETF really=
 the right organization to do this work in? ISO wrote the underlying spec.=
=C2=A0 They presumably thought about it a lot.<br>
<br>
We are already collaborating with the folks over at CalConnect, to<br>
ensure that formats like ISO8601 end up adopting these additions as<br>
well, but the IETF RFC would need to be updated as well, and it helps<br>
ECMA TC39 refer to the RFC when using this format.<br>
<br>
I hope these answers help clarify our positions. Feel free to ask me for<br=
>
any further clarifications.<br>
<br>
Thanks,<br>
Ujjwal<br>
<br>
-- <br>
Ujjwal &quot;Ryzokuken&quot; Sharma (he/him)<br>
<br>
Compilers Hacker, Node.js Core Collaborator and Speaker<br>
<br>
_______________________________________________<br>
calsify mailing list<br>
<a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/calsify" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/calsify</a><br>
</blockquote></div>

--00000000000091a0c005b985252c--


From nobody Sat Jan 23 15:27:48 2021
Return-Path: <ned.freed@mrochek.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 464293A0D76 for <calsify@ietfa.amsl.com>; Sat, 23 Jan 2021 15:27:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RNgzFr2kayi6 for <calsify@ietfa.amsl.com>; Sat, 23 Jan 2021 15:27:44 -0800 (PST)
Received: from plum.mrochek.com (plum.mrochek.com [172.95.64.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3DFC3A0D63 for <calsify@ietf.org>; Sat, 23 Jan 2021 15:27:43 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RUQ0ZYNU8G00EIP4@mauve.mrochek.com> for calsify@ietf.org; Sat, 23 Jan 2021 15:22:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712;  t=1611444160; bh=DLMeOXHBrp0l/f5pQKbQ/NfNdEubNbHrN+a294Q49+4=;  h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=JXOZhvt+q/NydKU663hs8ftTxNtur6z4oWoGYlfWBJswaVISh7K12+u9+OG+6ZRAw Rac0MSJ0GZxJuHinXu9zT/ceHyzz6abu+Js/c+hZNARlwmu9gq4lVOLH2hV5ecWL1I XhU+MNFGzV9dmKjmfczbtSw2z5CrbnOYTGGe5xEs=
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RUAOXM63XS005PTU@mauve.mrochek.com>; Sat, 23 Jan 2021 15:22:37 -0800 (PST)
Cc: "calsify@ietf.org" <calsify@ietf.org>, Ned Freed <ned.freed@mrochek.com>
Message-id: <01RUQ0ZW4L3U005PTU@mauve.mrochek.com>
Date: Sat, 23 Jan 2021 15:17:01 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Sat, 23 Jan 2021 02:53:34 +0530" <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com>
References: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com> <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com>
To: Ujjwal Sharma <ryzokuken@igalia.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/fhiQBDkW5vqVqTnr3rq4-VjfnwI>
Subject: Re: [calsify] Fwd:  New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jan 2021 23:27:47 -0000

Generality has real costs. To name the obvious example, I don't want to
*ever* see a timezone rule in a log file timestamp, or a field in an
email message.

I wouldn't have a problem with any of this if all you were proposing a new
format for calendar usage. Calendars are unusual in that they routinely deal
with dates in the future, and worse, dates in the future that are subject to
the vagarities of human behavior - so a given value does NOT, in general,
specify a fixed point in time.

But you're proposing a replacement for ISO 8601/RFC 3339, with the implication
that absent per-application profiling you have to accept the gamut. That IMO
goes too far.

				Ned


> CCing the Calsify ML because I didn't include it in the original email
> by mistake.

> -------- Forwarded Message --------
> Subject: Re: [calsify] New Timestamp Draft
> Date: Sat, 23 Jan 2021 02:51:00 +0530
> From: Ujjwal Sharma <ryzokuken@igalia.com>
> Organization: Igalia S.L.
> To: Ned Freed <ned.freed@mrochek.com>

> Hi Ned!

> I could not agree with you more on the different matters. Here's the
> response to the specific points raised by you.

> On 23/01/2021 12.17 am, Ned Freed wrote:
> > +1. The stability of this specification has been invaluable.

> Please refer to my email to Eliot for more clarification on this.
> Overall, this is a goal that I share wholeheartedy, and the whole idea
> behind the new draft is to design it in a way that is very generalized
> and that allows us to avoid any further additions to it and keep a
> similar level of stability. Note for example the deferring of key
> selection and standardization to bodies like IANA and Unicode consortium.

> > +1. And if there's some sort of liason with ISO or whoever is responsible
> > for this, they should be engaged.

> My understanding of the situation has been that this liason would be
> CalConnect. By all means, we have been collaborating quite closely with
> them, thanks to the amazing efforts of Ronald Tse and have plans to work
> with them further to enable greater adoption.

> Hope this helps, please feel free to ask for further clarifications.

> Best,
> Ujjwal

> --
> Ujjwal "Ryzokuken" Sharma (he/him)

> Compilers Hacker, Node.js Core Collaborator and Speaker


From nobody Sat Jan 23 15:43:05 2021
Return-Path: <mikeadouglass@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D0293A0DE0 for <calsify@ietfa.amsl.com>; Sat, 23 Jan 2021 15:43:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oMuGWAwGE9ft for <calsify@ietfa.amsl.com>; Sat, 23 Jan 2021 15:43:01 -0800 (PST)
Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 322133A0DDF for <calsify@ietf.org>; Sat, 23 Jan 2021 15:43:01 -0800 (PST)
Received: by mail-qk1-x72f.google.com with SMTP id c7so9128806qke.1 for <calsify@ietf.org>; Sat, 23 Jan 2021 15:43:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=HfT7Gd9tisl63XsGIJb7R/WW9gRWMxa7iu0obs5Pj88=; b=Ir0vffMx0udqfWBgVzBIuL4v3Gp06eoWSFxilckbfmvznTlPSVDH8gufvbIbQ5O0Ce Tk6duL6BQxhKuIzwTWi4IjWh6uMoeihaNDvSrMaP2zPjgoTEyFPCD+afBRXicrbjoZWj H/WwPCiL+GDlH7m0W3X3dDkzMaJdCDFbw26fElmWrq0a+sRVpAuk7+pzYso4EhziJhGz xjikPjzfagEAqyHByLRVIrTSNAEoaQX9FuA/m2OpMPQ7EvzYZTE4qhOrhy6n/4ONqR+D LAEmTCRBLOprVZdWvsonsqgbOPAW6VtJiGUDCZoT/QDPG+9ikDMsE3J2aMq6d1Nmb720 JkSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=HfT7Gd9tisl63XsGIJb7R/WW9gRWMxa7iu0obs5Pj88=; b=Og2Ed+wiM4iHO2YKONIBYTXO0t1LmkBfQvIdYNmjIwpWxU8r6oDVxCm2LgQwLfM4Ud u1RT6iqDzAvaDtOMkcPVyyFvBO0R2AJ29iZCVhkmGw9g1qDW5+wMJBtMvCZIggHpaKJt +RYp3dxYp/aNAp+BDaicTd4vdtHkM5e+IfzpcJi+UUR6vwI5PfqPJo0h3MEl6fp5xMxE SdS6vDEVLxphoXLfNcfSb6Rsjhn5774uJks62daadltGEr052HQNwulGdL9vkH4Hz+oq qgz04KhUcKyCGbDLdtwXM+0j1ecdaMn5EO3aW4/Yq63BQiO7WtvTNi+sK1TmYzdtXiYK T18g==
X-Gm-Message-State: AOAM533GY9ACa5bPftSfbILvSA2RJmTZ9WuJNSUaGEq2jI5g2gkwy0CZ 7EdASa5wcb9r1hVjZYYcfyiWR3jdXx8=
X-Google-Smtp-Source: ABdhPJzLmESec1t2bsmDQBVDKxYoHOzBJORd7hxg0v+luNTPKG8uxgRueS9IqEkyIDAdq0lluhL61g==
X-Received: by 2002:a05:620a:158e:: with SMTP id d14mr2524908qkk.358.1611445379784;  Sat, 23 Jan 2021 15:42:59 -0800 (PST)
Received: from MacBook-Pro-2019.local (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id 7sm9210290qka.122.2021.01.23.15.42.58 for <calsify@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 23 Jan 2021 15:42:59 -0800 (PST)
To: calsify@ietf.org
References: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com> <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com> <01RUQ0ZW4L3U005PTU@mauve.mrochek.com>
From: Michael Douglass <mikeadouglass@gmail.com>
Message-ID: <d17b75e7-9720-6bd3-dd23-349e8ceac4a3@gmail.com>
Date: Sat, 23 Jan 2021 18:42:57 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <01RUQ0ZW4L3U005PTU@mauve.mrochek.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/S0S2rCScdIYrO--CIimUoeB4qPQ>
Subject: Re: [calsify] Fwd: New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jan 2021 23:43:04 -0000

On 1/23/21 18:17, Ned Freed wrote:
> Generality has real costs. To name the obvious example, I don't want to
> *ever* see a timezone rule in a log file timestamp, or a field in an
> email message.

I have had a number of conversations with people tasked with auditing 
log records bemoaning the lack of a timezone id in logs. Without the id 
how do we know how an offset or UTC date was calculated?

Accurately recording the date/time that an event occurred is as 
important for logging as it is for future events.

{and I don't think we're talking about rules - just ids]

>
> I wouldn't have a problem with any of this if all you were proposing a new
> format for calendar usage. Calendars are unusual in that they routinely deal
> with dates in the future, and worse, dates in the future that are subject to
> the vagarities of human behavior - so a given value does NOT, in general,
> specify a fixed point in time.
>
> But you're proposing a replacement for ISO 8601/RFC 3339, with the implication
> that absent per-application profiling you have to accept the gamut. That IMO
> goes too far.
>
> 				Ned

>
>> CCing the Calsify ML because I didn't include it in the original email
>> by mistake.
>> -------- Forwarded Message --------
>> Subject: Re: [calsify] New Timestamp Draft
>> Date: Sat, 23 Jan 2021 02:51:00 +0530
>> From: Ujjwal Sharma <ryzokuken@igalia.com>
>> Organization: Igalia S.L.
>> To: Ned Freed <ned.freed@mrochek.com>
>> Hi Ned!
>> I could not agree with you more on the different matters. Here's the
>> response to the specific points raised by you.
>> On 23/01/2021 12.17 am, Ned Freed wrote:
>>> +1. The stability of this specification has been invaluable.
>> Please refer to my email to Eliot for more clarification on this.
>> Overall, this is a goal that I share wholeheartedy, and the whole idea
>> behind the new draft is to design it in a way that is very generalized
>> and that allows us to avoid any further additions to it and keep a
>> similar level of stability. Note for example the deferring of key
>> selection and standardization to bodies like IANA and Unicode consortium.
>>> +1. And if there's some sort of liason with ISO or whoever is responsible
>>> for this, they should be engaged.
>> My understanding of the situation has been that this liason would be
>> CalConnect. By all means, we have been collaborating quite closely with
>> them, thanks to the amazing efforts of Ronald Tse and have plans to work
>> with them further to enable greater adoption.
>> Hope this helps, please feel free to ask for further clarifications.
>> Best,
>> Ujjwal
>> --
>> Ujjwal "Ryzokuken" Sharma (he/him)
>> Compilers Hacker, Node.js Core Collaborator and Speaker
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify


From nobody Sat Jan 23 17:09:39 2021
Return-Path: <ned.freed@mrochek.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FA8E3A0EB2 for <calsify@ietfa.amsl.com>; Sat, 23 Jan 2021 17:09:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UDYldcQyp5EB for <calsify@ietfa.amsl.com>; Sat, 23 Jan 2021 17:09:36 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [98.153.82.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CF473A0EAF for <calsify@ietf.org>; Sat, 23 Jan 2021 17:09:36 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RUQ4KA3D8G00EYN1@mauve.mrochek.com> for calsify@ietf.org; Sat, 23 Jan 2021 17:04:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712;  t=1611450273; bh=F2E9G4Kwjw1cCxOBaHmArFqC4ZMcbeaUkYQ3XQTIDtI=;  h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=XycsJu3zXtRJ9GnM40RmF20UvsaJ4J37wUBjdKZ8JSh4rsD50gg1LuzaGhM6YAGzJ 9VmYquO0NII2o8DsihjQQcaTrONJGwGqTjEvjxtYEM5S5aluzLgHV8xZcTrfr6Xnad JeV96j8KVElxBHSVZhYe6MYZ0Lw96HpJ71qX7WKY=
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii; Format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RUAOXM63XS005PTU@mauve.mrochek.com>; Sat, 23 Jan 2021 17:04:31 -0800 (PST)
Cc: calsify@ietf.org
Message-id: <01RUQ4K8M1RQ005PTU@mauve.mrochek.com>
Date: Sat, 23 Jan 2021 16:00:53 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Sat, 23 Jan 2021 18:42:57 -0500" <d17b75e7-9720-6bd3-dd23-349e8ceac4a3@gmail.com>
References: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com> <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com> <01RUQ0ZW4L3U005PTU@mauve.mrochek.com> <d17b75e7-9720-6bd3-dd23-349e8ceac4a3@gmail.com>
To: Michael Douglass <mikeadouglass@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/U3oetXCoc-0tYtMt54AeSqxNl4I>
Subject: Re: [calsify] Fwd: New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jan 2021 01:09:38 -0000

> On 1/23/21 18:17, Ned Freed wrote:
> > Generality has real costs. To name the obvious example, I don't want to
> > *ever* see a timezone rule in a log file timestamp, or a field in an
> > email message.

> I have had a number of conversations with people tasked with auditing
> log records bemoaning the lack of a timezone id in logs. Without the id
> how do we know how an offset or UTC date was calculated?

The purpose of a time value in the sorts of logs I'm talking about is to
accurately describe the moment in time when something happened. Nothing more,
nothing less. The RFC 3339/ISO 8601 format gives you this along with the
ability to specify the value as an offset from GMT.

If you really want more information along the lines of what this draft
provides, like what timezone rules were in effect somewhere or what calendar it
should be "projected to" (to use the draft's terminology), then by all
means include that in a separate field in the log.

With computers increasingly going back to being shared resources in some random
data center some place other than anyone involved in generating the log entry,
figuring out the right "somewhere" is a highly nontrivial problem. This
is  true even for time zone offsets, and the further you go the harder it gets.
(Of course this doesn't stop people from using offsets in their logs even when
they have nothing to do with anything other than the location of some random
piece of hardware.)

And of course there can be multiple somewheres, which means these values need
to have additional semantics attached in order to be interpreted properly.

All of which argues strongly for not combining what are in fact separate
pieces of information.

Given all this, my advice to your auditor pals is, "Be careful what you wish
for, because you're likely to end up with useless garbage."

There's also very strong trend in the logging world to try and avoid complex
field values because they hugely complicate aggregation, searching and sorting
operations. In this world the use of RFC 3339 may be profiled to GMT only, or
replaced entirely by a UNIX epoch or milliepoch values.

> it's simply an offset showing what's considered to be local time.

? Offsets are a standard part of ISO 8601/RFC 3339.

> Accurately recording the date/time that an event occurred is as
> important for logging as it is for future events.

?? None of this has anything to do with accuracy. If you're not putting
in the correct offset for your time values you're doing it wrong.

> {and I don't think we're talking about rules - just ids]

??? We most certainly are talking about rules. If you think otherwise you
need to reread the draft.

				Ned


From nobody Sat Jan 23 19:16:03 2021
Return-Path: <brong@fastmailteam.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9969D3A1117 for <calsify@ietfa.amsl.com>; Sat, 23 Jan 2021 19:16:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=YDua2ELB; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=rOXHaNh4
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L4uzwS4BQN_f for <calsify@ietfa.amsl.com>; Sat, 23 Jan 2021 19:15:59 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37B4A3A1116 for <calsify@ietf.org>; Sat, 23 Jan 2021 19:15:59 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 69D2C5C0116 for <calsify@ietf.org>; Sat, 23 Jan 2021 22:15:57 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Sat, 23 Jan 2021 22:15:57 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm1; bh=VM2bdDF Q8/FVtlkS/Aujbrwr1h8+yXyKKg48lhgwHp8=; b=YDua2ELBdCqNIF2bvdtewUs 9oVVPtlX0pV0aUGjcYoEWjJ49eMBuuGr65rdlUWShBZaqDcaC0PLooSjo5j4uKiv w4OUJ2o+XXYzmtvcufBPMYO0x9V5KI8+aK5eg7KuDoudmv03K1a/vAq73ycQ1Uht 0A3FZd77/5TtqPLb2VBBoW1XumtuTXYyyHVB6b68u5ILpZeqxOY6/iFkRP1/iUZ/ fIjl0c+IoBis7V9XgZOsprD8WITBtD6/LTTYCGGiTzwxDdyh1CAdWJTFdnIItAJW 0Y7442bg4QhlNcLslLo8Vks6x47U9lnySoRZb4pzJSuX6XOyPqkj+CTMNF+wACg= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=VM2bdD FQ8/FVtlkS/Aujbrwr1h8+yXyKKg48lhgwHp8=; b=rOXHaNh4J9MvtHdN1za9hH XWOGIWO9c9YZm0a4C04yqDwVuiKd1jlbEqXOAFDulTIdGANjuCzSpLj0gtS0eWYA VnbcAq/wlugcTKVQUQ9z6kh9vuQfcNpgLHFLET+JSISGN8H4dbTH9dU0EdCmEOsu hdtl7sUVvDg4R9lRgsfwb+DOK1+8ulx6OLfPjhNj4NmRQir3a4oCicBHYNK/GKLg 4QVzomnTkwc4dhGv9U4tgbJJie81Ss5ltb0Hjucph0YmZ++nzDP69AEB8rvjcVti upAsrEClSO7deRnUL0raTcTvrzdUDoVEhBOuEuUM3wBqf5ojaM9jfI0HgBCkFoXw ==
X-ME-Sender: <xms:beYMYPEOxx0qbHBn59f0Nvh0pE8wpXeDKfpPfY85uGvc2iUankbtrg> <xme:beYMYMX-T5F_6_24iBdtHPE00z_iSw4xmN6ZY7okdiKpaOtRc45Hy5CfjXOdbM1kz YDkek3_z64>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudelgdehiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreertdenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehf rghsthhmrghilhhtvggrmhdrtghomheqnecuggftrfgrthhtvghrnhepgfduvefgffdvve ethfeiteehteduhfeltddujeehffektdevleeileeiheevkeegnecuffhomhgrihhnpehi vghtfhdrohhrghdpghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgt ohhm
X-ME-Proxy: <xmx:beYMYBLQ8Gh9F1C6FvumaYJl4jpzG84Ryv36BnY2HnpCRssPpOEYAw> <xmx:beYMYNEv9LqXspfZL5beZV4kmEwekmcI_ezTq0EfwFn4lI_DFuiFZw> <xmx:beYMYFXm3YtM0ylLoTly4GGBMmu-pXII6PnMAbnX5WRRT_qm3MLBTQ> <xmx:beYMYNgGFt0ixNSJKfSa4W_WP87a5jh5jMR_UWfvG4wE4AHKdYGNPw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 4538836005C; Sat, 23 Jan 2021 22:15:57 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-78-g36b56e88ef-fm-20210120.001-g36b56e88
Mime-Version: 1.0
Message-Id: <27ae33c7-d5cf-428b-99fa-7b974be85e70@dogfood.fastmail.com>
In-Reply-To: <c87c068b-02f1-913a-64ef-497f827fc3ea@igalia.com>
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <0275d5af-6eea-4608-913e-c96d59c0abea@dogfood.fastmail.com> <c87c068b-02f1-913a-64ef-497f827fc3ea@igalia.com>
Date: Sun, 24 Jan 2021 14:15:35 +1100
From: "Bron Gondwana" <brong@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary=73aa9aae31c1451fa05c35f5582b5fd6
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/2hX1bI_5Ke6T7Uy7WjPA6yhCjwg>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jan 2021 03:16:02 -0000

--73aa9aae31c1451fa05c35f5582b5fd6
Content-Type: text/plain

The document is plenty complete enough for a call for adoption!  I shall do so now.

You are exactly correct that it's possible to do further iteration after adoption.

Thanks,

Bron.

On Fri, Jan 22, 2021, at 23:19, Ujjwal Sharma wrote:
> Hi Bron, CalExt Friends!
> 
> I made a new revision of the draft, which shifts the focus to defining
> the syntax/format and defers the standardization of the actual key-value
> pairs to sibling organizations like IANA and Unicode Consortium.
> 
> I'd love to hear your opinions on this version, which you can find at
> https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/,
> which can be filed as issues on the GitHub repository or emailed to me
> directly. In the meantime, I will address the remaining concerns/polish
> issues like fixing the references section.
> 
> How "complete" does the document need to be in order to initiate the
> call for adoption? If the current version works, can we start it as soon
> as possible? Of course, if my understanding of "adoption" is correct,
> I'd be happy to iterate on the document further after the adoption by
> the WG.
> 
> Best,
> Ujjwal
> 
> On 14/01/2021 8.34 am, Bron Gondwana wrote:
> > Sounds great.  Let me know :)
> > 
> > When we do the call for adoption I'll also advertise the fact over to
> > the wider IETF - probably dispatch and tzdata lists at least.
> > 
> > Cheers,
> > 
> > Bron.
> > 
> > 
> > On Thu, Jan 14, 2021, at 13:48, Ujjwal Sharma wrote:
> >> Thanks Bron!
> >>
> >> I'll make a few more changes, release a 01 version, ask for more
> >> feedback and then let you know, hopefully by the end of this week.
> >>
> >> Ujjwal
> >>
> >> On 14/01/2021 7.03 am, Bron Gondwana wrote:
> >> > I can do a call for adoption straight away if you like - the next
> >> > meeting isn't for a couple of months.
> >> > 
> >> > Bron.
> >> > 
> >> > On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:
> >> >> One question: given things move forward smoothly, how do I proceed?
> >> >> Should I apply for this document to be adopted by the calext WG? I
> >> >> suppose the fastest way to proceed is to present it at the next IETF
> >> >> meeting?
> >> >>
> >> >>
> >> >>
> >> >> Ujjwal
> >> >>
> >> >> On 12/01/2021 4.03 am, Ujjwal Sharma wrote:
> >> >> > Hi Calsify folks!
> >> >> > 
> >> >> > I am sorry for the long delay, I got a little sidetracked working on
> >> >> > other things, but I'm happy to inform you all that I have
> >> something that
> >> >> > resembles a first draft for the updated timestamps RFC.
> >> >> > 
> >> >> > Here's where you can find it:
> >> >> > 
> >> >> > Datatracker:
> >> >>
> >> > https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
> >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/>
> >> >>
> >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
> >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/>>
> >> >> >
> >> >>
> >> GitHub: https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>
> >> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>>
> >> >> > 
> >> >> > I would request you all to take a look at it when you can and let me
> >> >> > know what you think. You can file a GitHub issue or email me
> >> directly.
> >> >> > 
> >> >> > There's a few open discussions regarding the exact format and how the
> >> >> > interaction with bodies like the Unicode consortium work, so
> >> please feel
> >> >> > free to send me your thoughts regarding that as well.
> >> >> > 
> >> >> > Also, some references/bibliography is not perfectly functional yet
> >> >> > because I am still relatively new to authoring RFCs using
> >> Metanorma but
> >> >> > I'm actively looking into it.
> >> >> > 
> >> >> > Thanks and looking forward to hear from you,
> >> >> > Ujjwal
> >> >> > 
> >> >>
> >> >> -- 
> >> >> Ujjwal "Ryzokuken" Sharma (he/him)
> >> >>
> >> >> Compilers Hacker, Node.js Core Collaborator and Speaker
> >> >>
> >> >> _______________________________________________
> >> >> calsify mailing list
> >> >> calsify@ietf.org <mailto:calsify@ietf.org> <mailto:calsify@ietf.org
> >> <mailto:calsify@ietf.org>>
> >> >> https://www.ietf.org/mailman/listinfo/calsify
> >> <https://www.ietf.org/mailman/listinfo/calsify>
> >> >> <https://www.ietf.org/mailman/listinfo/calsify
> >> <https://www.ietf.org/mailman/listinfo/calsify>>
> >> >>
> >> > 
> >> > --
> >> >   Bron Gondwana, CEO, Fastmail Pty Ltd
> >> >   brong@fastmailteam.com <mailto:brong@fastmailteam.com>
> >> > 
> >> > 
> >> > _______________________________________________
> >> > calsify mailing list
> >> > calsify@ietf.org <mailto:calsify@ietf.org>
> >> > https://www.ietf.org/mailman/listinfo/calsify
> >> <https://www.ietf.org/mailman/listinfo/calsify>
> >> > 
> >>
> >> -- 
> >> Ujjwal "Ryzokuken" Sharma (he/him)
> >>
> >> Compilers Hacker, Node.js Core Collaborator and Speaker
> >>
> >> _______________________________________________
> >> calsify mailing list
> >> calsify@ietf.org <mailto:calsify@ietf.org>
> >> https://www.ietf.org/mailman/listinfo/calsify
> >> <https://www.ietf.org/mailman/listinfo/calsify>
> >>
> > 
> > --
> >   Bron Gondwana, CEO, Fastmail Pty Ltd
> >   brong@fastmailteam.com
> > 
> > 
> > 
> > _______________________________________________
> > calsify mailing list
> > calsify@ietf.org
> > https://www.ietf.org/mailman/listinfo/calsify
> > 
> 
> -- 
> Ujjwal "Ryzokuken" Sharma (he/him)
> 
> Compilers Hacker, Node.js Core Collaborator and Speaker
> 
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
> 

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com


--73aa9aae31c1451fa05c35f5582b5fd6
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"font-f=
amily:Arial;">The document is plenty complete enough for a call for adop=
tion!&nbsp; I shall do so now.<br></div><div style=3D"font-family:Arial;=
"><br></div><div style=3D"font-family:Arial;">You are exactly correct th=
at it's possible to do further iteration after adoption.<br></div><div s=
tyle=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">=
Thanks,<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D=
"font-family:Arial;">Bron.<br></div><div style=3D"font-family:Arial;"><b=
r></div><div>On Fri, Jan 22, 2021, at 23:19, Ujjwal Sharma wrote:<br></d=
iv><blockquote type=3D"cite" id=3D"qt" style=3D""><div style=3D"font-fam=
ily:Arial;">Hi Bron, CalExt Friends!<br></div><div style=3D"font-family:=
Arial;"><br></div><div style=3D"font-family:Arial;">I made a new revisio=
n of the draft, which shifts the focus to defining<br></div><div style=3D=
"font-family:Arial;">the syntax/format and defers the standardization of=
 the actual key-value<br></div><div style=3D"font-family:Arial;">pairs t=
o sibling organizations like IANA and Unicode Consortium.<br></div><div =
style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;"=
>I'd love to hear your opinions on this version, which you can find at<b=
r></div><div style=3D"font-family:Arial;"><a href=3D"https://datatracker=
.ietf.org/doc/draft-ryzokuken-datetime-extended/">https://datatracker.ie=
tf.org/doc/draft-ryzokuken-datetime-extended/</a>,<br></div><div style=3D=
"font-family:Arial;">which can be filed as issues on the GitHub reposito=
ry or emailed to me<br></div><div style=3D"font-family:Arial;">directly.=
 In the meantime, I will address the remaining concerns/polish<br></div>=
<div style=3D"font-family:Arial;">issues like fixing the references sect=
ion.<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"=
font-family:Arial;">How "complete" does the document need to be in order=
 to initiate the<br></div><div style=3D"font-family:Arial;">call for ado=
ption? If the current version works, can we start it as soon<br></div><d=
iv style=3D"font-family:Arial;">as possible? Of course, if my understand=
ing of "adoption" is correct,<br></div><div style=3D"font-family:Arial;"=
>I'd be happy to iterate on the document further after the adoption by<b=
r></div><div style=3D"font-family:Arial;">the WG.<br></div><div style=3D=
"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">Best,<b=
r></div><div style=3D"font-family:Arial;">Ujjwal<br></div><div style=3D"=
font-family:Arial;"><br></div><div style=3D"font-family:Arial;">On 14/01=
/2021 8.34 am, Bron Gondwana wrote:<br></div><div style=3D"font-family:A=
rial;">&gt; Sounds great.&nbsp; Let me know :)<br></div><div style=3D"fo=
nt-family:Arial;">&gt;&nbsp;<br></div><div style=3D"font-family:Arial;">=
&gt; When we do the call for adoption I'll also advertise the fact over =
to<br></div><div style=3D"font-family:Arial;">&gt; the wider IETF - prob=
ably dispatch and tzdata lists at least.<br></div><div style=3D"font-fam=
ily:Arial;">&gt;&nbsp;<br></div><div style=3D"font-family:Arial;">&gt; C=
heers,<br></div><div style=3D"font-family:Arial;">&gt;&nbsp;<br></div><d=
iv style=3D"font-family:Arial;">&gt; Bron.<br></div><div style=3D"font-f=
amily:Arial;">&gt;&nbsp;<br></div><div style=3D"font-family:Arial;">&gt;=
&nbsp;<br></div><div style=3D"font-family:Arial;">&gt; On Thu, Jan 14, 2=
021, at 13:48, Ujjwal Sharma wrote:<br></div><div style=3D"font-family:A=
rial;">&gt;&gt; Thanks Bron!<br></div><div style=3D"font-family:Arial;">=
&gt;&gt;<br></div><div style=3D"font-family:Arial;">&gt;&gt; I'll make a=
 few more changes, release a 01 version, ask for more<br></div><div styl=
e=3D"font-family:Arial;">&gt;&gt; feedback and then let you know, hopefu=
lly by the end of this week.<br></div><div style=3D"font-family:Arial;">=
&gt;&gt;<br></div><div style=3D"font-family:Arial;">&gt;&gt; Ujjwal<br><=
/div><div style=3D"font-family:Arial;">&gt;&gt;<br></div><div style=3D"f=
ont-family:Arial;">&gt;&gt; On 14/01/2021 7.03 am, Bron Gondwana wrote:<=
br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt; I can do a call=
 for adoption straight away if you like - the next<br></div><div style=3D=
"font-family:Arial;">&gt;&gt; &gt; meeting isn't for a couple of months.=
<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&nbsp;<br></div=
><div style=3D"font-family:Arial;">&gt;&gt; &gt; Bron.<br></div><div sty=
le=3D"font-family:Arial;">&gt;&gt; &gt;&nbsp;<br></div><div style=3D"fon=
t-family:Arial;">&gt;&gt; &gt; On Thu, Jan 14, 2021, at 05:24, Ujjwal Sh=
arma wrote:<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt;=
 One question: given things move forward smoothly, how do I proceed?<br>=
</div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt; Should I apply=
 for this document to be adopted by the calext WG? I<br></div><div style=
=3D"font-family:Arial;">&gt;&gt; &gt;&gt; suppose the fastest way to pro=
ceed is to present it at the next IETF<br></div><div style=3D"font-famil=
y:Arial;">&gt;&gt; &gt;&gt; meeting?<br></div><div style=3D"font-family:=
Arial;">&gt;&gt; &gt;&gt;<br></div><div style=3D"font-family:Arial;">&gt=
;&gt; &gt;&gt;<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&=
gt;<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt; Ujjwal<=
br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt;<br></div><d=
iv style=3D"font-family:Arial;">&gt;&gt; &gt;&gt; On 12/01/2021 4.03 am,=
 Ujjwal Sharma wrote:<br></div><div style=3D"font-family:Arial;">&gt;&gt=
; &gt;&gt; &gt; Hi Calsify folks!<br></div><div style=3D"font-family:Ari=
al;">&gt;&gt; &gt;&gt; &gt;&nbsp;<br></div><div style=3D"font-family:Ari=
al;">&gt;&gt; &gt;&gt; &gt; I am sorry for the long delay, I got a littl=
e sidetracked working on<br></div><div style=3D"font-family:Arial;">&gt;=
&gt; &gt;&gt; &gt; other things, but I'm happy to inform you all that I =
have<br></div><div style=3D"font-family:Arial;">&gt;&gt; something that<=
br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt; &gt; resemb=
les a first draft for the updated timestamps RFC.<br></div><div style=3D=
"font-family:Arial;">&gt;&gt; &gt;&gt; &gt;&nbsp;<br></div><div style=3D=
"font-family:Arial;">&gt;&gt; &gt;&gt; &gt; Here's where you can find it=
:<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt; &gt;&nbsp=
;<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt; &gt; Data=
tracker:<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt;<br=
></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&nbsp;<a href=3D"h=
ttps://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/">http=
s://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/</a><br><=
/div><div style=3D"font-family:Arial;">&gt;&gt; &lt;<a href=3D"https://d=
atatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/">https://data=
tracker.ietf.org/doc/draft-ryzokuken-datetime-extended/</a>&gt;<br></div=
><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt;<br></div><div style=
=3D"font-family:Arial;">&gt;&gt; &lt;<a href=3D"https://datatracker.ietf=
.org/doc/draft-ryzokuken-datetime-extended/">https://datatracker.ietf.or=
g/doc/draft-ryzokuken-datetime-extended/</a><br></div><div style=3D"font=
-family:Arial;">&gt;&gt; &lt;<a href=3D"https://datatracker.ietf.org/doc=
/draft-ryzokuken-datetime-extended/">https://datatracker.ietf.org/doc/dr=
aft-ryzokuken-datetime-extended/</a>&gt;&gt;<br></div><div style=3D"font=
-family:Arial;">&gt;&gt; &gt;&gt; &gt;<br></div><div style=3D"font-famil=
y:Arial;">&gt;&gt; &gt;&gt;<br></div><div style=3D"font-family:Arial;">&=
gt;&gt; GitHub:&nbsp;<a href=3D"https://github.com/ryzokuken/draft-ryzok=
uken-datetime-extended">https://github.com/ryzokuken/draft-ryzokuken-dat=
etime-extended</a><br></div><div style=3D"font-family:Arial;">&gt;&gt; &=
lt;<a href=3D"https://github.com/ryzokuken/draft-ryzokuken-datetime-exte=
nded">https://github.com/ryzokuken/draft-ryzokuken-datetime-extended</a>=
&gt;<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt; &lt;<a=
 href=3D"https://github.com/ryzokuken/draft-ryzokuken-datetime-extended"=
>https://github.com/ryzokuken/draft-ryzokuken-datetime-extended</a><br><=
/div><div style=3D"font-family:Arial;">&gt;&gt; &lt;<a href=3D"https://g=
ithub.com/ryzokuken/draft-ryzokuken-datetime-extended">https://github.co=
m/ryzokuken/draft-ryzokuken-datetime-extended</a>&gt;&gt;<br></div><div =
style=3D"font-family:Arial;">&gt;&gt; &gt;&gt; &gt;&nbsp;<br></div><div =
style=3D"font-family:Arial;">&gt;&gt; &gt;&gt; &gt; I would request you =
all to take a look at it when you can and let me<br></div><div style=3D"=
font-family:Arial;">&gt;&gt; &gt;&gt; &gt; know what you think. You can =
file a GitHub issue or email me<br></div><div style=3D"font-family:Arial=
;">&gt;&gt; directly.<br></div><div style=3D"font-family:Arial;">&gt;&gt=
; &gt;&gt; &gt;&nbsp;<br></div><div style=3D"font-family:Arial;">&gt;&gt=
; &gt;&gt; &gt; There's a few open discussions regarding the exact forma=
t and how the<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&g=
t; &gt; interaction with bodies like the Unicode consortium work, so<br>=
</div><div style=3D"font-family:Arial;">&gt;&gt; please feel<br></div><d=
iv style=3D"font-family:Arial;">&gt;&gt; &gt;&gt; &gt; free to send me y=
our thoughts regarding that as well.<br></div><div style=3D"font-family:=
Arial;">&gt;&gt; &gt;&gt; &gt;&nbsp;<br></div><div style=3D"font-family:=
Arial;">&gt;&gt; &gt;&gt; &gt; Also, some references/bibliography is not=
 perfectly functional yet<br></div><div style=3D"font-family:Arial;">&gt=
;&gt; &gt;&gt; &gt; because I am still relatively new to authoring RFCs =
using<br></div><div style=3D"font-family:Arial;">&gt;&gt; Metanorma but<=
br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt; &gt; I'm ac=
tively looking into it.<br></div><div style=3D"font-family:Arial;">&gt;&=
gt; &gt;&gt; &gt;&nbsp;<br></div><div style=3D"font-family:Arial;">&gt;&=
gt; &gt;&gt; &gt; Thanks and looking forward to hear from you,<br></div>=
<div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt; &gt; Ujjwal<br></div=
><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt; &gt;&nbsp;<br></div=
><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt;<br></div><div style=
=3D"font-family:Arial;">&gt;&gt; &gt;&gt; --&nbsp;<br></div><div style=3D=
"font-family:Arial;">&gt;&gt; &gt;&gt; Ujjwal "Ryzokuken" Sharma (he/him=
)<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt;<br></div>=
<div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt; Compilers Hacker, No=
de.js Core Collaborator and Speaker<br></div><div style=3D"font-family:A=
rial;">&gt;&gt; &gt;&gt;<br></div><div style=3D"font-family:Arial;">&gt;=
&gt; &gt;&gt; _______________________________________________<br></div><=
div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt; calsify mailing list<=
br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt;&nbsp;<a hre=
f=3D"mailto:calsify@ietf.org">calsify@ietf.org</a> &lt;mailto:<a href=3D=
"mailto:calsify@ietf.org">calsify@ietf.org</a>&gt; &lt;mailto:<a href=3D=
"mailto:calsify@ietf.org">calsify@ietf.org</a><br></div><div style=3D"fo=
nt-family:Arial;">&gt;&gt; &lt;mailto:<a href=3D"mailto:calsify@ietf.org=
">calsify@ietf.org</a>&gt;&gt;<br></div><div style=3D"font-family:Arial;=
">&gt;&gt; &gt;&gt;&nbsp;<a href=3D"https://www.ietf.org/mailman/listinf=
o/calsify">https://www.ietf.org/mailman/listinfo/calsify</a><br></div><d=
iv style=3D"font-family:Arial;">&gt;&gt; &lt;<a href=3D"https://www.ietf=
.org/mailman/listinfo/calsify">https://www.ietf.org/mailman/listinfo/cal=
sify</a>&gt;<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt=
; &lt;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify">https://=
www.ietf.org/mailman/listinfo/calsify</a><br></div><div style=3D"font-fa=
mily:Arial;">&gt;&gt; &lt;<a href=3D"https://www.ietf.org/mailman/listin=
fo/calsify">https://www.ietf.org/mailman/listinfo/calsify</a>&gt;&gt;<br=
></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&gt;<br></div><div=
 style=3D"font-family:Arial;">&gt;&gt; &gt;&nbsp;<br></div><div style=3D=
"font-family:Arial;">&gt;&gt; &gt; --<br></div><div style=3D"font-family=
:Arial;">&gt;&gt; &gt; &nbsp; Bron Gondwana, CEO, Fastmail Pty Ltd<br></=
div><div style=3D"font-family:Arial;">&gt;&gt; &gt; &nbsp;&nbsp;<a href=3D=
"mailto:brong@fastmailteam.com">brong@fastmailteam.com</a> &lt;mailto:<a=
 href=3D"mailto:brong@fastmailteam.com">brong@fastmailteam.com</a>&gt;<b=
r></div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&nbsp;<br></div><=
div style=3D"font-family:Arial;">&gt;&gt; &gt;&nbsp;<br></div><div style=
=3D"font-family:Arial;">&gt;&gt; &gt; __________________________________=
_____________<br></div><div style=3D"font-family:Arial;">&gt;&gt; &gt; c=
alsify mailing list<br></div><div style=3D"font-family:Arial;">&gt;&gt; =
&gt;&nbsp;<a href=3D"mailto:calsify@ietf.org">calsify@ietf.org</a> &lt;m=
ailto:<a href=3D"mailto:calsify@ietf.org">calsify@ietf.org</a>&gt;<br></=
div><div style=3D"font-family:Arial;">&gt;&gt; &gt;&nbsp;<a href=3D"http=
s://www.ietf.org/mailman/listinfo/calsify">https://www.ietf.org/mailman/=
listinfo/calsify</a><br></div><div style=3D"font-family:Arial;">&gt;&gt;=
 &lt;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify">https://w=
ww.ietf.org/mailman/listinfo/calsify</a>&gt;<br></div><div style=3D"font=
-family:Arial;">&gt;&gt; &gt;&nbsp;<br></div><div style=3D"font-family:A=
rial;">&gt;&gt;<br></div><div style=3D"font-family:Arial;">&gt;&gt; --&n=
bsp;<br></div><div style=3D"font-family:Arial;">&gt;&gt; Ujjwal "Ryzokuk=
en" Sharma (he/him)<br></div><div style=3D"font-family:Arial;">&gt;&gt;<=
br></div><div style=3D"font-family:Arial;">&gt;&gt; Compilers Hacker, No=
de.js Core Collaborator and Speaker<br></div><div style=3D"font-family:A=
rial;">&gt;&gt;<br></div><div style=3D"font-family:Arial;">&gt;&gt; ____=
___________________________________________<br></div><div style=3D"font-=
family:Arial;">&gt;&gt; calsify mailing list<br></div><div style=3D"font=
-family:Arial;">&gt;&gt;&nbsp;<a href=3D"mailto:calsify@ietf.org">calsif=
y@ietf.org</a> &lt;mailto:<a href=3D"mailto:calsify@ietf.org">calsify@ie=
tf.org</a>&gt;<br></div><div style=3D"font-family:Arial;">&gt;&gt;&nbsp;=
<a href=3D"https://www.ietf.org/mailman/listinfo/calsify">https://www.ie=
tf.org/mailman/listinfo/calsify</a><br></div><div style=3D"font-family:A=
rial;">&gt;&gt; &lt;<a href=3D"https://www.ietf.org/mailman/listinfo/cal=
sify">https://www.ietf.org/mailman/listinfo/calsify</a>&gt;<br></div><di=
v style=3D"font-family:Arial;">&gt;&gt;<br></div><div style=3D"font-fami=
ly:Arial;">&gt;&nbsp;<br></div><div style=3D"font-family:Arial;">&gt; --=
<br></div><div style=3D"font-family:Arial;">&gt; &nbsp; Bron Gondwana, C=
EO, Fastmail Pty Ltd<br></div><div style=3D"font-family:Arial;">&gt; &nb=
sp;&nbsp;<a href=3D"mailto:brong@fastmailteam.com">brong@fastmailteam.co=
m</a><br></div><div style=3D"font-family:Arial;">&gt;&nbsp;<br></div><di=
v style=3D"font-family:Arial;">&gt;&nbsp;<br></div><div style=3D"font-fa=
mily:Arial;">&gt;&nbsp;<br></div><div style=3D"font-family:Arial;">&gt; =
_______________________________________________<br></div><div style=3D"f=
ont-family:Arial;">&gt; calsify mailing list<br></div><div style=3D"font=
-family:Arial;">&gt;&nbsp;<a href=3D"mailto:calsify@ietf.org">calsify@ie=
tf.org</a><br></div><div style=3D"font-family:Arial;">&gt;&nbsp;<a href=3D=
"https://www.ietf.org/mailman/listinfo/calsify">https://www.ietf.org/mai=
lman/listinfo/calsify</a><br></div><div style=3D"font-family:Arial;">&gt=
;&nbsp;<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D=
"font-family:Arial;">--&nbsp;<br></div><div style=3D"font-family:Arial;"=
>Ujjwal "Ryzokuken" Sharma (he/him)<br></div><div style=3D"font-family:A=
rial;"><br></div><div style=3D"font-family:Arial;">Compilers Hacker, Nod=
e.js Core Collaborator and Speaker<br></div><div style=3D"font-family:Ar=
ial;"><br></div><div style=3D"font-family:Arial;">______________________=
_________________________<br></div><div style=3D"font-family:Arial;">cal=
sify mailing list<br></div><div style=3D"font-family:Arial;"><a href=3D"=
mailto:calsify@ietf.org">calsify@ietf.org</a><br></div><div style=3D"fon=
t-family:Arial;"><a href=3D"https://www.ietf.org/mailman/listinfo/calsif=
y">https://www.ietf.org/mailman/listinfo/calsify</a><br></div><div style=
=3D"font-family:Arial;"><br></div></blockquote><div style=3D"font-family=
:Arial;"><br></div><div id=3D"sig56629417"><div class=3D"signature">--<b=
r></div><div class=3D"signature">&nbsp; Bron Gondwana, CEO, Fastmail Pty=
 Ltd<br></div><div class=3D"signature">&nbsp; brong@fastmailteam.com<br>=
</div><div class=3D"signature"><br></div></div><div style=3D"font-family=
:Arial;"><br></div></body></html>
--73aa9aae31c1451fa05c35f5582b5fd6--


From nobody Sat Jan 23 19:24:23 2021
Return-Path: <brong@fastmailteam.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45EB83A1139 for <calsify@ietfa.amsl.com>; Sat, 23 Jan 2021 19:24:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=q57jJmzV; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=jLwQdy/S
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RS_VEFPTp6kn for <calsify@ietfa.amsl.com>; Sat, 23 Jan 2021 19:24:20 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31CA33A1138 for <calsify@ietf.org>; Sat, 23 Jan 2021 19:24:20 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 31E2C5C00A1; Sat, 23 Jan 2021 22:24:19 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Sat, 23 Jan 2021 22:24:19 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:cc:subject:content-type; s=fm1; bh=Qj3u /wQXN3tXZHyRs5i+QcuZ0vs7Bra0rWnS3dYnh00=; b=q57jJmzVgRGHg4PMdvJb mCYsfi4hbT9K4udaKVh6Q3DYdTqgOgIVF03dShx//NfMmA1Qwv68DGTle+Qu5dwA F+S7ozX9mrnNFYzmMdkidGmCH3tK5Ryb2IB+uX+ZBfkyatMHnG7GPeeNaSmofsgf CpKKmjDsvMMONlOoFJzD/fLOUSPxHpXyGwqtmWHn4jPPJn32YRmKSblrFRyx/VsP Y/8p2dm1ad5QzhpW4AOahhSSc6n7215F5pLgg5j01Iy7D7JaUkh+aYNbCFDrsd6Q eG1/+/5gufsJNirJkpCN+H+f7KYctEt2K8m32IApnemfq+JCcEfPOPtT9KJUXsSC fg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=Qj3u/w QXN3tXZHyRs5i+QcuZ0vs7Bra0rWnS3dYnh00=; b=jLwQdy/Sb3ryk/DTWOzNLW I0U4X/T+ilUNofJWU4lkAVlgZJybeThd493FfLPsEBK4LXtKNzigyOrniLTG/ZnM qNspznG85rimYyCocBWLUTQPSF/QgIA8rLbiS9Avj28Y+Z3Ey2IS5DHBH+iAxD/7 8rASJQWKGsTuuHuGOb3RoikqPQqyh+WgIQV1sMXLTQ5igTlRX8jxMtd6rMVAFdWt NBnlSP+Q3fa12teMUknxalDB6Iy4Y+xpoDCVNfEdn7HwCYCRlQdYklaWIcQBJWJ6 d2sw4S/KHhSp9INQWIbMmxLpD9FPivzzRCmtcRzMd9pb0X4mDAbVENHFtXxTLXyQ ==
X-ME-Sender: <xms:YegMYKGRDP3cUFwZp3EFo166X2q_JDnd7neNaeCPomUPRFwbzMDKxQ> <xme:YegMYLXDki8X7U47uFpMs-eaChIBuC3veXi8B8hadDQsYi2nr0BM9kCZjJX68T7Y2 GPiyGdgin8>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudelgdehkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerredtnecuhfhrohhmpedfuehrohhn ucfiohhnugifrghnrgdfuceosghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucggtffrrghtthgvrhhnpeffveefiefgjeevteehheelgeetleetveeguedthfehgffh tdejhfdvhefhtdekgfenucffohhmrghinhepihgvthhfrdhorhhgnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgr ihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:YegMYEJKjnVx4QZtY9FMRDTsEX7HVapY5Jbjl_s5NO5OkQTtKIg7xw> <xmx:YegMYEFWCNoVH2EQjNiQ4IiDYpmb7v31QJn6hpwLWrSx9CDhgb3QmA> <xmx:YegMYAXkOnHVObcSCd2DM8UkXXRNFDiu9jGzkebjR91aG7YMSK0DTQ> <xmx:Y-gMYJetTWlm_ZqXBZxcTIrBbD85coZB-OieVxqGAvUWpKHu72Wu7Q>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id E254736005C; Sat, 23 Jan 2021 22:24:17 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-78-g36b56e88ef-fm-20210120.001-g36b56e88
Mime-Version: 1.0
Message-Id: <34839106-de11-41fe-96d6-33f95c30524d@dogfood.fastmail.com>
In-Reply-To: <01RUQ4K8M1RQ005PTU@mauve.mrochek.com>
References: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com> <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com> <01RUQ0ZW4L3U005PTU@mauve.mrochek.com> <d17b75e7-9720-6bd3-dd23-349e8ceac4a3@gmail.com> <01RUQ4K8M1RQ005PTU@mauve.mrochek.com>
Date: Sun, 24 Jan 2021 14:23:57 +1100
From: "Bron Gondwana" <brong@fastmailteam.com>
To: calsify@ietf.org
Cc: "Ned Freed" <ned.freed@mrochek.com>, "Ujjwal Sharma" <ryzokuken@igalia.com>
Content-Type: multipart/alternative; boundary=5e3b41691e9d4803a64c1bba44d2bcde
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/sWILlLNh8GLmw4mRzwZorrlltmY>
Subject: Re: [calsify] Fwd: New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jan 2021 03:24:22 -0000

--5e3b41691e9d4803a64c1bba44d2bcde
Content-Type: text/plain

Ned,

Would your concern here be resolved by having this draft define a "point in time" profile which was RFC3339 minus the 2-digit-year option, and a "full date" profile which includes all the rest of the details - such that logging software could be defined to use the "point in time" profile.

I'm really keen for there to be an RFC which can be referenced by both new calendaring drafts and by other IETF documents, which is developed by this group of people who are already involved in both the ISO work (via Ronald and CalConnect) and the ECMA standardisation effort.

Generality has real costs, but so does excess simplicity - if there's not a standard way to describe things that people really need, then they all develop their own extensions.  This effort is to capture the extensions that have been needed in the real world already, and standardise them to encourage everyone to extend the same way!

Cheers,

Bron.

On Sun, Jan 24, 2021, at 11:00, Ned Freed wrote:
> 
> > On 1/23/21 18:17, Ned Freed wrote:
> > > Generality has real costs. To name the obvious example, I don't want to
> > > *ever* see a timezone rule in a log file timestamp, or a field in an
> > > email message.
> 
> > I have had a number of conversations with people tasked with auditing
> > log records bemoaning the lack of a timezone id in logs. Without the id
> > how do we know how an offset or UTC date was calculated?
> 
> The purpose of a time value in the sorts of logs I'm talking about is to
> accurately describe the moment in time when something happened. Nothing more,
> nothing less. The RFC 3339/ISO 8601 format gives you this along with the
> ability to specify the value as an offset from GMT.
> 
> If you really want more information along the lines of what this draft
> provides, like what timezone rules were in effect somewhere or what calendar it
> should be "projected to" (to use the draft's terminology), then by all
> means include that in a separate field in the log.
> 
> With computers increasingly going back to being shared resources in some random
> data center some place other than anyone involved in generating the log entry,
> figuring out the right "somewhere" is a highly nontrivial problem. This
> is  true even for time zone offsets, and the further you go the harder it gets.
> (Of course this doesn't stop people from using offsets in their logs even when
> they have nothing to do with anything other than the location of some random
> piece of hardware.)
> 
> And of course there can be multiple somewheres, which means these values need
> to have additional semantics attached in order to be interpreted properly.
> 
> All of which argues strongly for not combining what are in fact separate
> pieces of information.
> 
> Given all this, my advice to your auditor pals is, "Be careful what you wish
> for, because you're likely to end up with useless garbage."
> 
> There's also very strong trend in the logging world to try and avoid complex
> field values because they hugely complicate aggregation, searching and sorting
> operations. In this world the use of RFC 3339 may be profiled to GMT only, or
> replaced entirely by a UNIX epoch or milliepoch values.
> 
> > it's simply an offset showing what's considered to be local time.
> 
> ? Offsets are a standard part of ISO 8601/RFC 3339.
> 
> > Accurately recording the date/time that an event occurred is as
> > important for logging as it is for future events.
> 
> ?? None of this has anything to do with accuracy. If you're not putting
> in the correct offset for your time values you're doing it wrong.
> 
> > {and I don't think we're talking about rules - just ids]
> 
> ??? We most certainly are talking about rules. If you think otherwise you
> need to reread the draft.
> 
> Ned
> 
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
> 

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com


--5e3b41691e9d4803a64c1bba44d2bcde
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"font-f=
amily:Arial;">Ned,<br></div><div style=3D"font-family:Arial;"><br></div>=
<div style=3D"font-family:Arial;">Would your concern here be resolved by=
 having this draft define a "point in time" profile which was RFC3339 mi=
nus the 2-digit-year option, and a "full date" profile which includes al=
l the rest of the details - such that logging software could be defined =
to use the "point in time" profile.<br></div><div style=3D"font-family:A=
rial;"><br></div><div style=3D"font-family:Arial;">I'm really keen for t=
here to be an RFC which can be referenced by both new calendaring drafts=
 and by other IETF documents, which is developed by this group of people=
 who are already involved in both the ISO work (via Ronald and CalConnec=
t) and the ECMA standardisation effort.<br></div><div style=3D"font-fami=
ly:Arial;"><br></div><div style=3D"font-family:Arial;">Generality has re=
al costs, but so does excess simplicity - if there's not a standard way =
to describe things that people really need, then they all develop their =
own extensions.&nbsp; This effort is to capture the extensions that have=
 been needed in the real world already, and standardise them to encourag=
e everyone to extend the same way!<br></div><div style=3D"font-family:Ar=
ial;"><br></div><div style=3D"font-family:Arial;">Cheers,<br></div><div =
style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;"=
>Bron.<br></div><div style=3D"font-family:Arial;"><br></div><div>On Sun,=
 Jan 24, 2021, at 11:00, Ned Freed wrote:<br></div><blockquote type=3D"c=
ite" id=3D"qt" style=3D""><div style=3D"font-family:Arial;"><br></div><d=
iv style=3D"font-family:Arial;">&gt; On 1/23/21 18:17, Ned Freed wrote:<=
br></div><div style=3D"font-family:Arial;">&gt; &gt; Generality has real=
 costs. To name the obvious example, I don't want to<br></div><div style=
=3D"font-family:Arial;">&gt; &gt; *ever* see a timezone rule in a log fi=
le timestamp, or a field in an<br></div><div style=3D"font-family:Arial;=
">&gt; &gt; email message.<br></div><div style=3D"font-family:Arial;"><b=
r></div><div style=3D"font-family:Arial;">&gt; I have had a number of co=
nversations with people tasked with auditing<br></div><div style=3D"font=
-family:Arial;">&gt; log records bemoaning the lack of a timezone id in =
logs. Without the id<br></div><div style=3D"font-family:Arial;">&gt; how=
 do we know how an offset or UTC date was calculated?<br></div><div styl=
e=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">The=
 purpose of a time value in the sorts of logs I'm talking about is to<br=
></div><div style=3D"font-family:Arial;">accurately describe the moment =
in time when something happened. Nothing more,<br></div><div style=3D"fo=
nt-family:Arial;">nothing less. The RFC 3339/ISO 8601 format gives you t=
his along with the<br></div><div style=3D"font-family:Arial;">ability to=
 specify the value as an offset from GMT.<br></div><div style=3D"font-fa=
mily:Arial;"><br></div><div style=3D"font-family:Arial;">If you really w=
ant more information along the lines of what this draft<br></div><div st=
yle=3D"font-family:Arial;">provides, like what timezone rules were in ef=
fect somewhere or what calendar it<br></div><div style=3D"font-family:Ar=
ial;">should be "projected to" (to use the draft's terminology), then by=
 all<br></div><div style=3D"font-family:Arial;">means include that in a =
separate field in the log.<br></div><div style=3D"font-family:Arial;"><b=
r></div><div style=3D"font-family:Arial;">With computers increasingly go=
ing back to being shared resources in some random<br></div><div style=3D=
"font-family:Arial;">data center some place other than anyone involved i=
n generating the log entry,<br></div><div style=3D"font-family:Arial;">f=
iguring out the right "somewhere" is a highly nontrivial problem. This<b=
r></div><div style=3D"font-family:Arial;">is&nbsp; true even for time zo=
ne offsets, and the further you go the harder it gets.<br></div><div sty=
le=3D"font-family:Arial;">(Of course this doesn't stop people from using=
 offsets in their logs even when<br></div><div style=3D"font-family:Aria=
l;">they have nothing to do with anything other than the location of som=
e random<br></div><div style=3D"font-family:Arial;">piece of hardware.)<=
br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-=
family:Arial;">And of course there can be multiple somewheres, which mea=
ns these values need<br></div><div style=3D"font-family:Arial;">to have =
additional semantics attached in order to be interpreted properly.<br></=
div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-famil=
y:Arial;">All of which argues strongly for not combining what are in fac=
t separate<br></div><div style=3D"font-family:Arial;">pieces of informat=
ion.<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"=
font-family:Arial;">Given all this, my advice to your auditor pals is, "=
Be careful what you wish<br></div><div style=3D"font-family:Arial;">for,=
 because you're likely to end up with useless garbage."<br></div><div st=
yle=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">T=
here's also very strong trend in the logging world to try and avoid comp=
lex<br></div><div style=3D"font-family:Arial;">field values because they=
 hugely complicate aggregation, searching and sorting<br></div><div styl=
e=3D"font-family:Arial;">operations. In this world the use of RFC 3339 m=
ay be profiled to GMT only, or<br></div><div style=3D"font-family:Arial;=
">replaced entirely by a UNIX epoch or milliepoch values.<br></div><div =
style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;"=
>&gt; it's simply an offset showing what's considered to be local time.<=
br></div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-=
family:Arial;">? Offsets are a standard part of ISO 8601/RFC 3339.<br></=
div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-famil=
y:Arial;">&gt; Accurately recording the date/time that an event occurred=
 is as<br></div><div style=3D"font-family:Arial;">&gt; important for log=
ging as it is for future events.<br></div><div style=3D"font-family:Aria=
l;"><br></div><div style=3D"font-family:Arial;">?? None of this has anyt=
hing to do with accuracy. If you're not putting<br></div><div style=3D"f=
ont-family:Arial;">in the correct offset for your time values you're doi=
ng it wrong.<br></div><div style=3D"font-family:Arial;"><br></div><div s=
tyle=3D"font-family:Arial;">&gt; {and I don't think we're talking about =
rules - just ids]<br></div><div style=3D"font-family:Arial;"><br></div><=
div style=3D"font-family:Arial;">??? We most certainly are talking about=
 rules. If you think otherwise you<br></div><div style=3D"font-family:Ar=
ial;">need to reread the draft.<br></div><div style=3D"font-family:Arial=
;"><br></div><div style=3D"font-family:Arial;">Ned<br></div><div style=3D=
"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">_______=
________________________________________<br></div><div style=3D"font-fam=
ily:Arial;">calsify mailing list<br></div><div style=3D"font-family:Aria=
l;"><a href=3D"mailto:calsify@ietf.org">calsify@ietf.org</a><br></div><d=
iv style=3D"font-family:Arial;"><a href=3D"https://www.ietf.org/mailman/=
listinfo/calsify">https://www.ietf.org/mailman/listinfo/calsify</a><br><=
/div><div style=3D"font-family:Arial;"><br></div></blockquote><div style=
=3D"font-family:Arial;"><br></div><div id=3D"sig56629417"><div class=3D"=
signature">--<br></div><div class=3D"signature">&nbsp; Bron Gondwana, CE=
O, Fastmail Pty Ltd<br></div><div class=3D"signature">&nbsp; brong@fastm=
ailteam.com<br></div><div class=3D"signature"><br></div></div><div style=
=3D"font-family:Arial;"><br></div></body></html>
--5e3b41691e9d4803a64c1bba44d2bcde--


From nobody Sat Jan 23 23:05:12 2021
Return-Path: <sla@ucolick.org>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 047923A0E5F for <calsify@ietfa.amsl.com>; Sat, 23 Jan 2021 23:05:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6R8ubwM9mMyk for <calsify@ietfa.amsl.com>; Sat, 23 Jan 2021 23:05:09 -0800 (PST)
Received: from smtp.ucolick.org (zilan.ucolick.org [128.114.23.234]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B2B03A0E5B for <calsify@ietf.org>; Sat, 23 Jan 2021 23:05:09 -0800 (PST)
Received: from smtp.ucolick.org (localhost [127.0.0.1]) by smtp.ucolick.org (Postfix) with ESMTP id 43A722A7E; Sat, 23 Jan 2021 23:05:08 -0800 (PST)
Received: from geneva.ucolick.org (geneva.ucolick.org [128.114.23.183]) by smtp.ucolick.org (Postfix) with ESMTP id 9F3C929BC; Sat, 23 Jan 2021 23:05:07 -0800 (PST)
Received: from geneva.ucolick.org (localhost [127.0.0.1]) by geneva.ucolick.org (Postfix) with ESMTP id 8A0E4775; Sat, 23 Jan 2021 23:05:07 -0800 (PST)
Received: (from sla@localhost) by geneva.ucolick.org (8.14.7/8.14.7/Submit) id 10O755Xa025811; Sat, 23 Jan 2021 23:05:05 -0800
Date: Sat, 23 Jan 2021 23:05:05 -0800
From: Steve Allen <sla@ucolick.org>
To: Ujjwal Sharma <ryzokuken@igalia.com>
Cc: calsify@ietf.org
Message-ID: <20210124070505.GA25744@ucolick.org>
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <20210114164646.GA4932@ucolick.org> <8ae850cd-3d62-0834-5532-5f5ef14f7185@igalia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <8ae850cd-3d62-0834-5532-5f5ef14f7185@igalia.com>
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/UTPH7f-X1KXyDCf1-dr00DbpoOg>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jan 2021 07:05:11 -0000

On Fri 2021-01-22T21:46:02+0530 Ujjwal Sharma hath writ:
> For both of these, I like have to point out that none of these
> definitions were added in this update and belong to the original RFC
> (RFC 3339). That said, if folks agree that the original RFC incorrectly
> defines these terms and they need to be updated, I'd be happy to correct
> them in the next revision of the draft.

Yes, I see.

> That said, I would have to point out that my knowledge in this space is
> rather limited and therefore it would be best if you recommended exactly
> what the replacement should be. To take things further, you could also
> make a pull request to the project at
> https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
> or email me a git patch if you prefer that.

A lot of history has to be condensed for this, but I have attempted to
add enough clarification to make it clear that timestamps before 1972
are defined entirely differently than after 1972.
I believe that I have made a fork and requested a pull.

--
Steve Allen                    <sla@ucolick.org>              WGS-84 (GPS)
UCO/Lick Observatory--ISB 260  Natural Sciences II, Room 165  Lat  +36.99855
1156 High Street               Voice: +1 831 459 3046         Lng -122.06015
Santa Cruz, CA 95064           https://www.ucolick.org/~sla/  Hgt +250 m


From nobody Sun Jan 24 00:04:07 2021
Return-Path: <ned.freed@mrochek.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C4513A1056 for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 00:04:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m0wabrvvMcX3 for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 00:04:04 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [98.153.82.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64F9D3A1053 for <calsify@ietf.org>; Sun, 24 Jan 2021 00:04:04 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RUQJ13KN4000DV80@mauve.mrochek.com> for calsify@ietf.org; Sat, 23 Jan 2021 23:58:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712;  t=1611475139; bh=93H4vQ/2s3xWkNnGQffyDT0kGz2Q3UV7ScQKWtDfR9k=;  h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=FVlf6kf7bqg4CtFZomZPsYKoIy3QSKAN5N0+4ZVabob5EXonjYqtuAZUfinHJ+RoB 1kPVDwoswVbjnvdGRCQ3M5StSHXQgatT5q8Ots1K9foKK8uC2xgSt3DZ19qhQySx/D SImJkN1Y4eVAOcjKUu23eASdPJVymz0IqeGS633g=
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RUAOXM63XS005PTU@mauve.mrochek.com>; Sat, 23 Jan 2021 23:58:55 -0800 (PST)
Cc: calsify@ietf.org, Ned Freed <ned.freed@mrochek.com>, Ujjwal Sharma <ryzokuken@igalia.com>
Message-id: <01RUQJ104Y3C005PTU@mauve.mrochek.com>
Date: Sat, 23 Jan 2021 23:32:57 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Sun, 24 Jan 2021 14:23:57 +1100" <34839106-de11-41fe-96d6-33f95c30524d@dogfood.fastmail.com>
References: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com> <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com> <01RUQ0ZW4L3U005PTU@mauve.mrochek.com> <d17b75e7-9720-6bd3-dd23-349e8ceac4a3@gmail.com> <01RUQ4K8M1RQ005PTU@mauve.mrochek.com> <34839106-de11-41fe-96d6-33f95c30524d@dogfood.fastmail.com>
To: Bron Gondwana <brong@fastmailteam.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/LbF_c9mppPEWzmR2Vg8hQrcexvw>
Subject: Re: [calsify] Fwd: New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jan 2021 08:04:06 -0000

> Ned,

> Would your concern here be resolved by having this draft define a "point in
> time" profile which was RFC3339 minus the 2-digit-year option, and a "full
> date" profile which includes all the rest of the details - such that logging
> software could be defined to use the "point in time" profile.

Maybe. I don't have any objection to deprecating features of RFC 3339 that
experience has shown we don't want or need.

However, I don't think you've really made the case that the full date stuff is
best addressed by packing all kinds of stuff in a single field value. It's not
like JSON, XML, and so on have no mechanism for specifying a group of related
values. As such, I question the need to define an additional syntax to do this,
one that's considerably less flexible.

There's also the issue of what constraints are applied to the additional stuff.
The obvious one is that it MUST NOT be allowed to move the point in time
of the timestamp around - I don't see this stated anywhere.

> I'm really keen for there to be an RFC which can be referenced by both new
> calendaring drafts and by other IETF documents, which is developed by this
> group of people who are already involved in both the ISO work (via Ronald and
> CalConnect) and the ECMA standardisation effort.

> Generality has real costs, but so does excess simplicity - if there's not a
> standard way to describe things that people really need, then they all develop
> their own extensions.

Actualy, it's this draft that engages in excess simplicity - the simplicity,
for example, of assuming that it never makes sense to associate more than
one set of time zone rules with a timestamp.

And there's no missing standard here. We have no shortage of standardized
grouping syntaxes.

> This effort is to capture the extensions that have been needed in the real
> world already, and standardise them to encourage everyone to extend the same
> way!

I'm a very long way from being convinced of this.

				Ned

> Cheers,

> Bron.

> On Sun, Jan 24, 2021, at 11:00, Ned Freed wrote:
> >
> > > On 1/23/21 18:17, Ned Freed wrote:
> > > > Generality has real costs. To name the obvious example, I don't want to
> > > > *ever* see a timezone rule in a log file timestamp, or a field in an
> > > > email message.
> >
> > > I have had a number of conversations with people tasked with auditing
> > > log records bemoaning the lack of a timezone id in logs. Without the id
> > > how do we know how an offset or UTC date was calculated?
> >
> > The purpose of a time value in the sorts of logs I'm talking about is to
> > accurately describe the moment in time when something happened. Nothing more,
> > nothing less. The RFC 3339/ISO 8601 format gives you this along with the
> > ability to specify the value as an offset from GMT.
> >
> > If you really want more information along the lines of what this draft
> > provides, like what timezone rules were in effect somewhere or what calendar it
> > should be "projected to" (to use the draft's terminology), then by all
> > means include that in a separate field in the log.
> >
> > With computers increasingly going back to being shared resources in some random
> > data center some place other than anyone involved in generating the log entry,
> > figuring out the right "somewhere" is a highly nontrivial problem. This
> > is  true even for time zone offsets, and the further you go the harder it gets.
> > (Of course this doesn't stop people from using offsets in their logs even when
> > they have nothing to do with anything other than the location of some random
> > piece of hardware.)
> >
> > And of course there can be multiple somewheres, which means these values need
> > to have additional semantics attached in order to be interpreted properly.
> >
> > All of which argues strongly for not combining what are in fact separate
> > pieces of information.
> >
> > Given all this, my advice to your auditor pals is, "Be careful what you wish
> > for, because you're likely to end up with useless garbage."
> >
> > There's also very strong trend in the logging world to try and avoid complex
> > field values because they hugely complicate aggregation, searching and sorting
> > operations. In this world the use of RFC 3339 may be profiled to GMT only, or
> > replaced entirely by a UNIX epoch or milliepoch values.
> >
> > > it's simply an offset showing what's considered to be local time.
> >
> > ? Offsets are a standard part of ISO 8601/RFC 3339.
> >
> > > Accurately recording the date/time that an event occurred is as
> > > important for logging as it is for future events.
> >
> > ?? None of this has anything to do with accuracy. If you're not putting
> > in the correct offset for your time values you're doing it wrong.
> >
> > > {and I don't think we're talking about rules - just ids]
> >
> > ??? We most certainly are talking about rules. If you think otherwise you
> > need to reread the draft.
> >
> > Ned
> >
> > _______________________________________________
> > calsify mailing list
> > calsify@ietf.org
> > https://www.ietf.org/mailman/listinfo/calsify
> >

> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd
>   brong@fastmailteam.com




From nobody Sun Jan 24 00:37:12 2021
Return-Path: <brong@fastmailteam.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 577A33A10F3 for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 00:37:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level: 
X-Spam-Status: No, score=-2.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=az9Qo3yW; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=jruoofSt
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VipiZvPNbrrF for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 00:37:08 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8196E3A10F2 for <calsify@ietf.org>; Sun, 24 Jan 2021 00:37:08 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id D40DD5C00F4; Sun, 24 Jan 2021 03:37:07 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Sun, 24 Jan 2021 03:37:07 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:cc:subject:content-type; s=fm1; bh=c3G9 Ti8B13rzc/bROIldyspeQgkLbFpIMVEwoIxsTpg=; b=az9Qo3yWbUIIo4XiWuI8 s8mQE1aYiYHi3PNNpBpqN9wczOSeWPMXACewJiOV4N0op4tWv+q/wtGNz0UcuDlm 9rKgb1nUXe7bGuiH+hQ36mxe+f1RtVBNq0SWtFT4ukFreaOMqUx2XNlFKh6q8JEG ymVc29PLZyK3CMjUHkCPQmcgb3kn4fvNNVkN6WsQLU0RtJ8RP9x2vQLhDxfj63WE o/4bFO+RWBrEZZaSWV3XKviIinOmLsk8vqfcv75zoAjCPKN+lKJekqpqAD8JEwBp esbXcCYz8pOB5fqjbWZftpQSAn/pvUmmMaeUo5PsaGr2PyMGCKa/NOmmvQSfQZlj 9g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=c3G9Ti 8B13rzc/bROIldyspeQgkLbFpIMVEwoIxsTpg=; b=jruoofStQWLQRUUnUWEsK/ APv1H3vu0LATteMJtky2gVLatryrX/3qDoC0vtQoWxponVcWVYzYQNz93TjxDKfo bols20HQWhGL5OWDvw/H7LmjZ64/F1N2DyUZ0b5y9T9Ywz7DZ6dmseR9hc0su3LS HhpQeDR3x0ZCNOtJw9S5uDkTGbO3YQ04SkvZL1M8FiAqI+jTz+FJKLrUj8bB3y3h JDtvRT4/AX3BfxE165+XDEdLhMclc39b/urlBjkVFB/MNEHi9vDRRcQ82+q4ZOTQ UbJ075OUI6mYnXTmQev3E9oUNZ+J95StAnHQpwbkoa04oPLI3pQzY7/niNG43tUQ ==
X-ME-Sender: <xms:sjENYHaRbpGQV1M8Bx6neQmZ5hmlk2h2aMF6gFz5sKV_-cqnpTB44A> <xme:sjENYGYPgvcvdR_B-306saIgsM2eFY_k6zA1FPKW-A5wSLgF6FGOnbtOAq7hScOX7 Xep8j5q6xU>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddtgddvvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerredtnecuhfhrohhmpedfuehrohhn ucfiohhnugifrghnrgdfuceosghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucggtffrrghtthgvrhhnpedvudeuieehgfdvheeuueejjeeuudfgiefgveetfeelteef fffgtdejjefgueduvdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:sjENYJ-KntljOpK_2nXmB9kFJgK7D7dytzmYu_5TOo_p8HYjzC5Z3g> <xmx:sjENYNpLgwpYhqIeutgO4wjZP3ba4I3USx16KEcJg74--QK0WdlYTA> <xmx:sjENYCrsSKVLS5OeABDUH1le_RR8WjNRiXpxpE88jvKkH4Hzoj6Efw> <xmx:szENYJS80HcOoU8DCeqxcOtWVnvLnLgYS-xvu9QGKA1n3LaoM2lzZA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 86DAB360068; Sun, 24 Jan 2021 03:37:06 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-78-g36b56e88ef-fm-20210120.001-g36b56e88
Mime-Version: 1.0
Message-Id: <da7c1ee0-a8cc-4310-81ac-4d9b8afb672d@dogfood.fastmail.com>
In-Reply-To: <01RUQJ104Y3C005PTU@mauve.mrochek.com>
References: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com> <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com> <01RUQ0ZW4L3U005PTU@mauve.mrochek.com> <d17b75e7-9720-6bd3-dd23-349e8ceac4a3@gmail.com> <01RUQ4K8M1RQ005PTU@mauve.mrochek.com> <34839106-de11-41fe-96d6-33f95c30524d@dogfood.fastmail.com> <01RUQJ104Y3C005PTU@mauve.mrochek.com>
Date: Sun, 24 Jan 2021 19:36:46 +1100
From: "Bron Gondwana" <brong@fastmailteam.com>
To: "Ned Freed" <ned.freed@mrochek.com>
Cc: calsify@ietf.org, "Ujjwal Sharma" <ryzokuken@igalia.com>
Content-Type: multipart/alternative; boundary=81a9a1a582ba478db1c55d8b5d05d52e
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/8qX89pZKkJHLqZ6bD6vBdkvfbno>
Subject: Re: [calsify] Fwd: New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jan 2021 08:37:10 -0000

--81a9a1a582ba478db1c55d8b5d05d52e
Content-Type: text/plain

On Sun, Jan 24, 2021, at 18:32, Ned Freed wrote:
> However, I don't think you've really made the case that the full date stuff is
> best addressed by packing all kinds of stuff in a single field value. It's not
> like JSON, XML, and so on have no mechanism for specifying a group of related
> values. As such, I question the need to define an additional syntax to do this,
> one that's considerably less flexible.

This idea has been "reinvented" more than once, which suggests that there is demand for it.

> There's also the issue of what constraints are applied to the additional stuff.
> The obvious one is that it MUST NOT be allowed to move the point in time
> of the timestamp around - I don't see this stated anywhere.

For sure you would then need to have both a [+-] and a zone name.  That's an interesting idea, and it does raise the question of what you do if the zone and the fixed offset no longer match by the time you process the date (or indeed, are incorrect immediately).  If the time is a floating value (no Z and no [+-]) then the point in time is also floating.

> > I'm really keen for there to be an RFC which can be referenced by both new
> > calendaring drafts and by other IETF documents, which is developed by this
> > group of people who are already involved in both the ISO work (via Ronald and
> > CalConnect) and the ECMA standardisation effort.
> 
> > Generality has real costs, but so does excess simplicity - if there's not a
> > standard way to describe things that people really need, then they all develop
> > their own extensions.
> 
> Actualy, it's this draft that engages in excess simplicity - the simplicity,
> for example, of assuming that it never makes sense to associate more than
> one set of time zone rules with a timestamp.
> 
> And there's no missing standard here. We have no shortage of standardized
> grouping syntaxes.

The initial justification for this was very much "this is true but said grouping syntaxes don't tend to survived round trips through different systems very well, so we want to capture all the important details in a serialised form".

> > This effort is to capture the extensions that have been needed in the real
> > world already, and standardise them to encourage everyone to extend the same
> > way!
> 
> I'm a very long way from being convinced of this.

I do have one more question (I'm going to do a call for adoption anyway, but I'll take this email thread as a voice against adoption from you unless I hear otherwise)...

Would you be happy if this was either "extends RFC3339" or an entirely separate piece of work that's "only for calendaring systems" - or do you object to the entire principle of doing any work in this space at all?

Thanks,

Bron.
--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com


--81a9a1a582ba478db1c55d8b5d05d52e
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"font-f=
amily:Arial;">On Sun, Jan 24, 2021, at 18:32, Ned Freed wrote:<br></div>=
<blockquote type=3D"cite" id=3D"qt" style=3D""><div style=3D"font-family=
:Arial;">However, I don't think you've really made the case that the ful=
l date stuff is<br></div><div style=3D"font-family:Arial;">best addresse=
d by packing all kinds of stuff in a single field value. It's not<br></d=
iv><div style=3D"font-family:Arial;">like JSON, XML, and so on have no m=
echanism for specifying a group of related<br></div><div style=3D"font-f=
amily:Arial;">values. As such, I question the need to define an addition=
al syntax to do this,<br></div><div style=3D"font-family:Arial;">one tha=
t's considerably less flexible.<br></div></blockquote><div style=3D"font=
-family:Arial;"><br></div><div style=3D"font-family:Arial;">This idea ha=
s been "reinvented" more than once, which suggests that there is demand =
for it.<br></div><div style=3D"font-family:Arial;"><br></div><blockquote=
 type=3D"cite" id=3D"qt" style=3D""><div style=3D"font-family:Arial;">Th=
ere's also the issue of what constraints are applied to the additional s=
tuff.<br></div><div style=3D"font-family:Arial;">The obvious one is that=
 it MUST NOT be allowed to move the point in time<br></div><div style=3D=
"font-family:Arial;">of the timestamp around - I don't see this stated a=
nywhere.<br></div></blockquote><div style=3D"font-family:Arial;"><br></d=
iv><div style=3D"font-family:Arial;">For sure you would then need to hav=
e both a [+-] and a zone name.&nbsp; That's an interesting idea, and it =
does raise the question of what you do if the zone and the fixed offset =
no longer match by the time you process the date (or indeed, are incorre=
ct immediately).&nbsp; If the time is a floating value (no Z and no [+-]=
) then the point in time is also floating.<br></div><div style=3D"font-f=
amily:Arial;"><br></div><blockquote type=3D"cite" id=3D"qt" style=3D""><=
div style=3D"font-family:Arial;">&gt; I'm really keen for there to be an=
 RFC which can be referenced by both new<br></div><div style=3D"font-fam=
ily:Arial;">&gt; calendaring drafts and by other IETF documents, which i=
s developed by this<br></div><div style=3D"font-family:Arial;">&gt; grou=
p of people who are already involved in both the ISO work (via Ronald an=
d<br></div><div style=3D"font-family:Arial;">&gt; CalConnect) and the EC=
MA standardisation effort.<br></div><div style=3D"font-family:Arial;"><b=
r></div><div style=3D"font-family:Arial;">&gt; Generality has real costs=
, but so does excess simplicity - if there's not a<br></div><div style=3D=
"font-family:Arial;">&gt; standard way to describe things that people re=
ally need, then they all develop<br></div><div style=3D"font-family:Aria=
l;">&gt; their own extensions.<br></div><div style=3D"font-family:Arial;=
"><br></div><div style=3D"font-family:Arial;">Actualy, it's this draft t=
hat engages in excess simplicity - the simplicity,<br></div><div style=3D=
"font-family:Arial;">for example, of assuming that it never makes sense =
to associate more than<br></div><div style=3D"font-family:Arial;">one se=
t of time zone rules with a timestamp.<br></div><div style=3D"font-famil=
y:Arial;"><br></div><div style=3D"font-family:Arial;">And there's no mis=
sing standard here. We have no shortage of standardized<br></div><div st=
yle=3D"font-family:Arial;">grouping syntaxes.<br></div></blockquote><div=
 style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;=
">The initial justification for this was very much "this is true but sai=
d grouping syntaxes don't tend to survived round trips through different=
 systems very well, so we want to capture all the important details in a=
 serialised form".<br></div><div style=3D"font-family:Arial;"><br></div>=
<blockquote type=3D"cite" id=3D"qt" style=3D""><div style=3D"font-family=
:Arial;">&gt; This effort is to capture the extensions that have been ne=
eded in the real<br></div><div style=3D"font-family:Arial;">&gt; world a=
lready, and standardise them to encourage everyone to extend the same<br=
></div><div style=3D"font-family:Arial;">&gt; way!<br></div><div style=3D=
"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">I'm a v=
ery long way from being convinced of this.<br></div></blockquote><div st=
yle=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">I=
 do have one more question (I'm going to do a call for adoption anyway, =
but I'll take this email thread as a voice against adoption from you unl=
ess I hear otherwise)...<br></div><div style=3D"font-family:Arial;"><br>=
</div><div style=3D"font-family:Arial;">Would you be happy if this was e=
ither "extends RFC3339" or an entirely separate piece of work that's "on=
ly for calendaring systems" - or do you object to the entire principle o=
f doing any work in this space at all?<br></div><div style=3D"font-famil=
y:Arial;"><br></div><div style=3D"font-family:Arial;">Thanks,<br></div><=
div style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Ari=
al;">Bron.<br></div><div id=3D"sig56629417"><div class=3D"signature">--<=
br></div><div class=3D"signature">&nbsp; Bron Gondwana, CEO, Fastmail Pt=
y Ltd<br></div><div class=3D"signature">&nbsp; brong@fastmailteam.com<br=
></div><div class=3D"signature"><br></div></div><div style=3D"font-famil=
y:Arial;"><br></div></body></html>
--81a9a1a582ba478db1c55d8b5d05d52e--


From nobody Sun Jan 24 02:32:59 2021
Return-Path: <lear@cisco.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10B793A129C for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 02:32:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.971
X-Spam-Level: 
X-Spam-Status: No, score=-9.971 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C_VuquO2ldUq for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 02:32:55 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F5F83A1299 for <calsify@ietf.org>; Sun, 24 Jan 2021 02:32:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=43018; q=dns/txt; s=iport; t=1611484374; x=1612693974; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=p2HBwYNKkHj0mM3NckczQq6vH9FwykoWMKR7G3fYu9s=; b=Dj90Zo+XfGCKEK3q8kh9sbFyYI9evCOmob02oMp3XAHyINh8fLHEStYF vjCY1jSv7Zl3s/Bc3CSYBTa7jxxAeFbVk5D82omNX74mzGF9glqgmP92D w7KLPpu1/qrPV4pT3XaqlvavMSpPIdjvT1ZCnAFYndw+a1l9bSf//YOKx M=;
X-Files: signature.asc : 488
X-IPAS-Result: =?us-ascii?q?A0DaAQD8Sw1glxbLJq1iHQEBAQEJARIBBQUBgg+BI4F+V?= =?us-ascii?q?wEgEi+EQIkEiFUDh26Sa4FjBQQHAQEBCgMBARgBCgwEAQGBVYIxRAKBeSY4E?= =?us-ascii?q?wIDAQEBAwIDAQEBAQUBAQECAQYEFAEBAQEBAQEBhjYMhXMBAQEDAQEBGwZLC?= =?us-ascii?q?wULCxggAQYDAgInHxEGE4MmAYJmIA+yNXaBMoRUQUSEdwoGgTiBU2GER4ZDQ?= =?us-ascii?q?YIAgREnHIFYfj6CXQEBAwGBJgESAVeCYzSCLASBVW8XJyYEIgUUGCACNAULK?= =?us-ascii?q?zkSVEKbd4pzkT+DAYMpgTeEUIImhFiLQQMfgyuKNIU7j16fPZIBRoNwAgQGB?= =?us-ascii?q?QIWgW0haXAzGggbFTsqAYI+PhIZDY47g1eFFIVFQAMwNwIGAQkBAQMJjBUBA?= =?us-ascii?q?Q?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.79,371,1602547200";  d="asc'?scan'208,217";a="32835552"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 24 Jan 2021 10:32:50 +0000
Received: from [10.61.248.209] ([10.61.248.209]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 10OAWnQ7026124 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 24 Jan 2021 10:32:49 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <AAD5976B-A601-45AC-9E43-CEB24D57BD1E@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E090BAAA-43CB-471E-B6DD-DCD75E4C3AD8"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Sun, 24 Jan 2021 11:32:48 +0100
In-Reply-To: <27ae33c7-d5cf-428b-99fa-7b974be85e70@dogfood.fastmail.com>
Cc: Barry Leiba <barryleiba@computer.org>, calsify@ietf.org
To: Bron Gondwana <brong@fastmailteam.com>
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <0275d5af-6eea-4608-913e-c96d59c0abea@dogfood.fastmail.com> <c87c068b-02f1-913a-64ef-497f827fc3ea@igalia.com> <27ae33c7-d5cf-428b-99fa-7b974be85e70@dogfood.fastmail.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
X-Outbound-SMTP-Client: 10.61.248.209, [10.61.248.209]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/yvuhdd70M0asRjfKLxnVY_EIyik>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jan 2021 10:32:58 -0000

--Apple-Mail=_E090BAAA-43CB-471E-B6DD-DCD75E4C3AD8
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_DAE2E5B3-DB36-4BD7-89A9-634607592028"


--Apple-Mail=_DAE2E5B3-DB36-4BD7-89A9-634607592028
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Bron,

I=E2=80=99m sorry, but I have both substantive and procedural problems =
with you moving forward like this.  Let me start with the procedural.  =
This work isn=E2=80=99t in calext=E2=80=99s charter.  You are =
specifically chartered to tackle several extensions to the iCalendar =
format, and that is it.  This is not an extension to that format.  This =
is a change to a standard that is used extremely broadly.

And this leads me to the substantive concern: this change is backward =
incompatible with  3339.  The ABNF in 3339 is clear: the stamp ends =
"time-offset" ("Z" / time-numoffset).  Adding =E2=80=9Csuffix" blow up =
in any yacc/bison-based parser and who knows what else.  Just imagine =
all the perl, awk, php, and python that whacks this stuff.

In a great many cases, there is no means to negotiate the extension.  =
Let me give you two examples:

Logging software commonly uses 3339 both for generation and for parsing, =
and the parsers themselves are notoriously fragile to the point that I =
do not believe any of them would entertain any changes to 3339.  The =
ecosystem is so vast that there is no hope of enumerating it.  To test =
this, imagine what damage changing any other field to syslog would =
cause.
Calendaring software, though in a smaller ecosystem, will have older =
versions that may well fail to parse.

I am not saying that 3339 can never be updated, but before it is, it =
should be clear that (a) it is broadly needed, not just by calendaring, =
and (b) that there is reason to believe that the change will be broadly =
adopted, again not just by calendaring.  If it=E2=80=99s just the =
calendaring ecosystem, you have properties and parameters to use.

Eliot


> On 24 Jan 2021, at 04:15, Bron Gondwana <brong@fastmailteam.com> =
wrote:
>=20
> The document is plenty complete enough for a call for adoption!  I =
shall do so now.
>=20
> You are exactly correct that it's possible to do further iteration =
after adoption.
>=20
> Thanks,
>=20
> Bron.
>=20
> On Fri, Jan 22, 2021, at 23:19, Ujjwal Sharma wrote:
>> Hi Bron, CalExt Friends!
>>=20
>> I made a new revision of the draft, which shifts the focus to =
defining
>> the syntax/format and defers the standardization of the actual =
key-value
>> pairs to sibling organizations like IANA and Unicode Consortium.
>>=20
>> I'd love to hear your opinions on this version, which you can find at
>> https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/ =
<https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/>,
>> which can be filed as issues on the GitHub repository or emailed to =
me
>> directly. In the meantime, I will address the remaining =
concerns/polish
>> issues like fixing the references section.
>>=20
>> How "complete" does the document need to be in order to initiate the
>> call for adoption? If the current version works, can we start it as =
soon
>> as possible? Of course, if my understanding of "adoption" is correct,
>> I'd be happy to iterate on the document further after the adoption by
>> the WG.
>>=20
>> Best,
>> Ujjwal
>>=20
>> On 14/01/2021 8.34 am, Bron Gondwana wrote:
>> > Sounds great.  Let me know :)
>> >
>> > When we do the call for adoption I'll also advertise the fact over =
to
>> > the wider IETF - probably dispatch and tzdata lists at least.
>> >
>> > Cheers,
>> >
>> > Bron.
>> >
>> >
>> > On Thu, Jan 14, 2021, at 13:48, Ujjwal Sharma wrote:
>> >> Thanks Bron!
>> >>
>> >> I'll make a few more changes, release a 01 version, ask for more
>> >> feedback and then let you know, hopefully by the end of this week.
>> >>
>> >> Ujjwal
>> >>
>> >> On 14/01/2021 7.03 am, Bron Gondwana wrote:
>> >> > I can do a call for adoption straight away if you like - the =
next
>> >> > meeting isn't for a couple of months.
>> >> >
>> >> > Bron.
>> >> >
>> >> > On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:
>> >> >> One question: given things move forward smoothly, how do I =
proceed?
>> >> >> Should I apply for this document to be adopted by the calext =
WG? I
>> >> >> suppose the fastest way to proceed is to present it at the next =
IETF
>> >> >> meeting?
>> >> >>
>> >> >>
>> >> >>
>> >> >> Ujjwal
>> >> >>
>> >> >> On 12/01/2021 4.03 am, Ujjwal Sharma wrote:
>> >> >> > Hi Calsify folks!
>> >> >> >
>> >> >> > I am sorry for the long delay, I got a little sidetracked =
working on
>> >> >> > other things, but I'm happy to inform you all that I have
>> >> something that
>> >> >> > resembles a first draft for the updated timestamps RFC.
>> >> >> >
>> >> >> > Here's where you can find it:
>> >> >> >
>> >> >> > Datatracker:
>> >> >>
>> >> > =
https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/ =
<https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/>
>> >> =
<https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/ =
<https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/>>
>> >> >>
>> >> =
<https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/ =
<https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/>
>> >> =
<https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/ =
<https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/>>>
>> >> >> >
>> >> >>
>> >> GitHub: =
https://github.com/ryzokuken/draft-ryzokuken-datetime-extended =
<https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>
>> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended =
<https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>>
>> >> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended =
<https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>
>> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended =
<https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>>>
>> >> >> >
>> >> >> > I would request you all to take a look at it when you can and =
let me
>> >> >> > know what you think. You can file a GitHub issue or email me
>> >> directly.
>> >> >> >
>> >> >> > There's a few open discussions regarding the exact format and =
how the
>> >> >> > interaction with bodies like the Unicode consortium work, so
>> >> please feel
>> >> >> > free to send me your thoughts regarding that as well.
>> >> >> >
>> >> >> > Also, some references/bibliography is not perfectly =
functional yet
>> >> >> > because I am still relatively new to authoring RFCs using
>> >> Metanorma but
>> >> >> > I'm actively looking into it.
>> >> >> >
>> >> >> > Thanks and looking forward to hear from you,
>> >> >> > Ujjwal
>> >> >> >
>> >> >>
>> >> >> --
>> >> >> Ujjwal "Ryzokuken" Sharma (he/him)
>> >> >>
>> >> >> Compilers Hacker, Node.js Core Collaborator and Speaker
>> >> >>
>> >> >> _______________________________________________
>> >> >> calsify mailing list
>> >> >> calsify@ietf.org <mailto:calsify@ietf.org> =
<mailto:calsify@ietf.org <mailto:calsify@ietf.org>> =
<mailto:calsify@ietf.org <mailto:calsify@ietf.org>
>> >> <mailto:calsify@ietf.org <mailto:calsify@ietf.org>>>
>> >> >> https://www.ietf.org/mailman/listinfo/calsify =
<https://www.ietf.org/mailman/listinfo/calsify>
>> >> <https://www.ietf.org/mailman/listinfo/calsify =
<https://www.ietf.org/mailman/listinfo/calsify>>
>> >> >> <https://www.ietf.org/mailman/listinfo/calsify =
<https://www.ietf.org/mailman/listinfo/calsify>
>> >> <https://www.ietf.org/mailman/listinfo/calsify =
<https://www.ietf.org/mailman/listinfo/calsify>>>
>> >> >>
>> >> >
>> >> > --
>> >> >   Bron Gondwana, CEO, Fastmail Pty Ltd
>> >> >   brong@fastmailteam.com <mailto:brong@fastmailteam.com> =
<mailto:brong@fastmailteam.com <mailto:brong@fastmailteam.com>>
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > calsify mailing list
>> >> > calsify@ietf.org <mailto:calsify@ietf.org> =
<mailto:calsify@ietf.org <mailto:calsify@ietf.org>>
>> >> > https://www.ietf.org/mailman/listinfo/calsify =
<https://www.ietf.org/mailman/listinfo/calsify>
>> >> <https://www.ietf.org/mailman/listinfo/calsify =
<https://www.ietf.org/mailman/listinfo/calsify>>
>> >> >
>> >>
>> >> --
>> >> Ujjwal "Ryzokuken" Sharma (he/him)
>> >>
>> >> Compilers Hacker, Node.js Core Collaborator and Speaker
>> >>
>> >> _______________________________________________
>> >> calsify mailing list
>> >> calsify@ietf.org <mailto:calsify@ietf.org> =
<mailto:calsify@ietf.org <mailto:calsify@ietf.org>>
>> >> https://www.ietf.org/mailman/listinfo/calsify =
<https://www.ietf.org/mailman/listinfo/calsify>
>> >> <https://www.ietf.org/mailman/listinfo/calsify =
<https://www.ietf.org/mailman/listinfo/calsify>>
>> >>
>> >
>> > --
>> >   Bron Gondwana, CEO, Fastmail Pty Ltd
>> >   brong@fastmailteam.com <mailto:brong@fastmailteam.com>
>> >
>> >
>> >
>> > _______________________________________________
>> > calsify mailing list
>> > calsify@ietf.org <mailto:calsify@ietf.org>
>> > https://www.ietf.org/mailman/listinfo/calsify =
<https://www.ietf.org/mailman/listinfo/calsify>
>> >
>>=20
>> --
>> Ujjwal "Ryzokuken" Sharma (he/him)
>>=20
>> Compilers Hacker, Node.js Core Collaborator and Speaker
>>=20
>> _______________________________________________
>> calsify mailing list
>> calsify@ietf.org <mailto:calsify@ietf.org>
>> https://www.ietf.org/mailman/listinfo/calsify =
<https://www.ietf.org/mailman/listinfo/calsify>
>>=20
>=20
> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd
>   brong@fastmailteam.com <mailto:brong@fastmailteam.com>
>=20
>=20
> _______________________________________________
> calsify mailing list
> calsify@ietf.org <mailto:calsify@ietf.org>
> https://www.ietf.org/mailman/listinfo/calsify =
<https://www.ietf.org/mailman/listinfo/calsify>

--Apple-Mail=_DAE2E5B3-DB36-4BD7-89A9-634607592028
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Bron,<div class=3D""><br class=3D""></div><div class=3D"">I=E2=80=
=99m sorry, but I have both substantive and procedural problems with you =
moving forward like this. &nbsp;Let me start with the procedural. =
&nbsp;This work isn=E2=80=99t in calext=E2=80=99s charter. &nbsp;You are =
specifically chartered to tackle several extensions to the iCalendar =
format, and that is it. &nbsp;This is not an extension to that format. =
&nbsp;This is a change to a standard that is used extremely =
broadly.</div><div class=3D""><br class=3D""></div><div class=3D"">And =
this leads me to the substantive concern: this change <b =
class=3D"">is&nbsp;</b>backward incompatible with &nbsp;3339. &nbsp;The =
ABNF in 3339 is clear: the stamp ends "time-offset" ("Z" / =
time-numoffset). &nbsp;Adding =E2=80=9Csuffix" blow up in any =
yacc/bison-based parser and who knows what else. &nbsp;Just imagine all =
the perl, awk, php, and python that whacks this stuff.</div><div =
class=3D""><br class=3D""></div><div class=3D"">In a great many cases, =
there is no means to negotiate the extension. &nbsp;Let me give you two =
examples:</div><div class=3D""><br class=3D""></div><div class=3D""><ul =
class=3D"MailOutline"><li class=3D"">Logging software commonly uses 3339 =
both for generation and for parsing, and the parsers themselves are =
notoriously fragile to the point that I do not believe any of them would =
entertain any changes to 3339. &nbsp;The ecosystem is so vast that there =
is no hope of enumerating it. &nbsp;To test this, imagine what damage =
changing any <b class=3D"">other</b>&nbsp;field to syslog would =
cause.</li><li class=3D"">Calendaring software, though in a smaller =
ecosystem, will have older versions that may well fail to =
parse.</li></ul></div><div class=3D""><div><br class=3D""></div><div>I =
am not saying that 3339 can never be updated, but before it is, it =
should be clear that (a) it is broadly needed, not just by calendaring, =
and (b) that there is reason to believe that the change will be broadly =
adopted, again not just by calendaring. &nbsp;If it=E2=80=99s just the =
calendaring ecosystem, you have properties and parameters to =
use.</div><div><br class=3D""></div><div>Eliot</div><div><br =
class=3D""></div><div><br class=3D""></div><div><blockquote type=3D"cite" =
class=3D""><div class=3D"">On 24 Jan 2021, at 04:15, Bron Gondwana =
&lt;<a href=3D"mailto:brong@fastmailteam.com" =
class=3D"">brong@fastmailteam.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" class=3D""><div style=3D"caret-color: rgb(0, 0, 0); =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; font-family: Arial;" class=3D"">The document is plenty complete =
enough for a call for adoption!&nbsp; I shall do so now.<br =
class=3D""></div><div style=3D"caret-color: rgb(0, 0, 0); font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; font-family: =
Arial;" class=3D""><br class=3D""></div><div style=3D"caret-color: =
rgb(0, 0, 0); font-size: 16px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; font-family: Arial;" class=3D"">You are exactly correct that it's =
possible to do further iteration after adoption.<br class=3D""></div><div =
style=3D"caret-color: rgb(0, 0, 0); font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Arial;" class=3D""><br =
class=3D""></div><div style=3D"caret-color: rgb(0, 0, 0); font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; font-family: =
Arial;" class=3D"">Thanks,<br class=3D""></div><div style=3D"caret-color: =
rgb(0, 0, 0); font-size: 16px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; font-family: Arial;" class=3D""><br class=3D""></div><div =
style=3D"caret-color: rgb(0, 0, 0); font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Arial;" class=3D"">Bron.<br =
class=3D""></div><div style=3D"caret-color: rgb(0, 0, 0); font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; font-family: =
Arial;" class=3D""><br class=3D""></div><div style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 16px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D"">On Fri, Jan 22, 2021, at 23:19, =
Ujjwal Sharma wrote:<br class=3D""></div><blockquote type=3D"cite" =
id=3D"qt" style=3D"font-family: Helvetica; font-size: 16px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><div style=3D"font-family: Arial;" =
class=3D"">Hi Bron, CalExt Friends!<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D""><br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">I made a new revision of the =
draft, which shifts the focus to defining<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">the syntax/format and defers =
the standardization of the actual key-value<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">pairs to sibling organizations =
like IANA and Unicode Consortium.<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D""><br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">I'd love to hear your opinions =
on this version, which you can find at<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended=
/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-exten=
ded/</a>,<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">which can be filed as issues on the GitHub repository or =
emailed to me<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">directly. In the meantime, I will address the remaining =
concerns/polish<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">issues like fixing the references section.<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D""><br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">How =
"complete" does the document need to be in order to initiate the<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">call for =
adoption? If the current version works, can we start it as soon<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">as =
possible? Of course, if my understanding of "adoption" is correct,<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">I'd be =
happy to iterate on the document further after the adoption by<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">the =
WG.<br class=3D""></div><div style=3D"font-family: Arial;" class=3D""><br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">Best,<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">Ujjwal<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D""><br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">On =
14/01/2021 8.34 am, Bron Gondwana wrote:<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt; Sounds great.&nbsp; Let me =
know :)<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&nbsp;<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">&gt; When we do the call for adoption I'll also =
advertise the fact over to<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">&gt; the wider IETF - probably dispatch and tzdata =
lists at least.<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&nbsp;<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">&gt; Cheers,<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&nbsp;<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt; =
Bron.<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&nbsp;<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">&gt;&nbsp;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt; On Thu, Jan 14, 2021, at =
13:48, Ujjwal Sharma wrote:<br class=3D""></div><div style=3D"font-family:=
 Arial;" class=3D"">&gt;&gt; Thanks Bron!<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt;<br class=3D""></div><div=
 style=3D"font-family: Arial;" class=3D"">&gt;&gt; I'll make a few more =
changes, release a 01 version, ask for more<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; feedback and then let =
you know, hopefully by the end of this week.<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt;<br class=3D""></div><div=
 style=3D"font-family: Arial;" class=3D"">&gt;&gt; Ujjwal<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt;<br=
 class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
On 14/01/2021 7.03 am, Bron Gondwana wrote:<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt; I can do a call =
for adoption straight away if you like - the next<br class=3D""></div><div=
 style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt; meeting isn't =
for a couple of months.<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">&gt;&gt; &gt;&nbsp;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt; Bron.<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&nbsp;<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt; On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma =
wrote:<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt; One question: given things move forward =
smoothly, how do I proceed?<br class=3D""></div><div style=3D"font-family:=
 Arial;" class=3D"">&gt;&gt; &gt;&gt; Should I apply for this document =
to be adopted by the calext WG? I<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt; suppose the =
fastest way to proceed is to present it at the next IETF<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&gt; meeting?<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt;<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&gt;<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt; Ujjwal<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt;<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&gt; On 12/01/2021 4.03 am, Ujjwal Sharma wrote:<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&gt; &gt; Hi Calsify folks!<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt; &gt;&nbsp;<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&gt; &gt; I am sorry for the long delay, I got a little sidetracked =
working on<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt; &gt; other things, but I'm happy to inform =
you all that I have<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">&gt;&gt; something that<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt; &gt; =
resembles a first draft for the updated timestamps RFC.<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&gt; &gt;&nbsp;<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">&gt;&gt; &gt;&gt; &gt; Here's where you can find =
it:<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt; &gt;&nbsp;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt; &gt; =
Datatracker:<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended=
/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-exten=
ded/</a><br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &lt;<a =
href=3D"https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended=
/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-exten=
ded/</a>&gt;<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &lt;<a =
href=3D"https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended=
/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-exten=
ded/</a><br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &lt;<a =
href=3D"https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended=
/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-exten=
ded/</a>&gt;&gt;<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt; &gt;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt;<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
GitHub:&nbsp;<a =
href=3D"https://github.com/ryzokuken/draft-ryzokuken-datetime-extended" =
class=3D"">https://github.com/ryzokuken/draft-ryzokuken-datetime-extended<=
/a><br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &lt;<a =
href=3D"https://github.com/ryzokuken/draft-ryzokuken-datetime-extended" =
class=3D"">https://github.com/ryzokuken/draft-ryzokuken-datetime-extended<=
/a>&gt;<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt; &lt;<a =
href=3D"https://github.com/ryzokuken/draft-ryzokuken-datetime-extended" =
class=3D"">https://github.com/ryzokuken/draft-ryzokuken-datetime-extended<=
/a><br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &lt;<a =
href=3D"https://github.com/ryzokuken/draft-ryzokuken-datetime-extended" =
class=3D"">https://github.com/ryzokuken/draft-ryzokuken-datetime-extended<=
/a>&gt;&gt;<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt; &gt;&nbsp;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt; &gt; I would =
request you all to take a look at it when you can and let me<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&gt; &gt; know what you think. You can file a GitHub issue or email =
me<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; directly.<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt; &gt;&nbsp;<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&gt; &gt; There's a few open discussions regarding the exact format =
and how the<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt; &gt; interaction with bodies like the =
Unicode consortium work, so<br class=3D""></div><div style=3D"font-family:=
 Arial;" class=3D"">&gt;&gt; please feel<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt; &gt; free to =
send me your thoughts regarding that as well.<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt; &gt;&nbsp;<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&gt; &gt; Also, some references/bibliography is not perfectly =
functional yet<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt; &gt; because I am still relatively new to =
authoring RFCs using<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">&gt;&gt; Metanorma but<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt; &gt; I'm =
actively looking into it.<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">&gt;&gt; &gt;&gt; &gt;&nbsp;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt; &gt; Thanks =
and looking forward to hear from you,<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt; &gt; =
Ujjwal<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt; &gt;&nbsp;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt;<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&gt; --&nbsp;<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt; Ujjwal "Ryzokuken" Sharma (he/him)<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&gt;<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt; Compilers Hacker, Node.js Core Collaborator =
and Speaker<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt; =
_______________________________________________<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt; calsify =
mailing list<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&gt;&nbsp;<a href=3D"mailto:calsify@ietf.org" =
class=3D"">calsify@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>&lt;mailto:<a =
href=3D"mailto:calsify@ietf.org" class=3D"">calsify@ietf.org</a>&gt; =
&lt;mailto:<a href=3D"mailto:calsify@ietf.org" =
class=3D"">calsify@ietf.org</a><br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &lt;mailto:<a =
href=3D"mailto:calsify@ietf.org" =
class=3D"">calsify@ietf.org</a>&gt;&gt;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&gt;&nbsp;<a =
href=3D"https://www.ietf.org/mailman/listinfo/calsify" =
class=3D"">https://www.ietf.org/mailman/listinfo/calsify</a><br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&lt;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify" =
class=3D"">https://www.ietf.org/mailman/listinfo/calsify</a>&gt;<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&gt; &lt;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify" =
class=3D"">https://www.ietf.org/mailman/listinfo/calsify</a><br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&lt;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify" =
class=3D"">https://www.ietf.org/mailman/listinfo/calsify</a>&gt;&gt;<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&gt;<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&nbsp;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt; --<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt; &nbsp; Bron Gondwana, CEO, Fastmail Pty Ltd<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt; &nbsp;&nbsp;<a =
href=3D"mailto:brong@fastmailteam.com" =
class=3D"">brong@fastmailteam.com</a><span =
class=3D"Apple-converted-space">&nbsp;</span>&lt;mailto:<a =
href=3D"mailto:brong@fastmailteam.com" =
class=3D"">brong@fastmailteam.com</a>&gt;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt;&nbsp;<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&nbsp;<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt; =
_______________________________________________<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; &gt; calsify mailing =
list<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt; &gt;&nbsp;<a href=3D"mailto:calsify@ietf.org" =
class=3D"">calsify@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>&lt;mailto:<a =
href=3D"mailto:calsify@ietf.org" class=3D"">calsify@ietf.org</a>&gt;<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&nbsp;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify" =
class=3D"">https://www.ietf.org/mailman/listinfo/calsify</a><br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&lt;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify" =
class=3D"">https://www.ietf.org/mailman/listinfo/calsify</a>&gt;<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&gt;&nbsp;<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt;<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">&gt;&gt; --&nbsp;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; Ujjwal "Ryzokuken" =
Sharma (he/him)<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt;<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">&gt;&gt; Compilers Hacker, Node.js Core Collaborator =
and Speaker<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt;<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">&gt;&gt; =
_______________________________________________<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&gt; calsify mailing =
list<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt;&nbsp;<a href=3D"mailto:calsify@ietf.org" =
class=3D"">calsify@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>&lt;mailto:<a =
href=3D"mailto:calsify@ietf.org" class=3D"">calsify@ietf.org</a>&gt;<br =
class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&gt;&nbsp;<a =
href=3D"https://www.ietf.org/mailman/listinfo/calsify" =
class=3D"">https://www.ietf.org/mailman/listinfo/calsify</a><br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt; =
&lt;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify" =
class=3D"">https://www.ietf.org/mailman/listinfo/calsify</a>&gt;<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt;&gt;<br=
 class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&nbsp;<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">&gt; --<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">&gt; &nbsp; Bron Gondwana, CEO, Fastmail Pty Ltd<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">&gt; =
&nbsp;&nbsp;<a href=3D"mailto:brong@fastmailteam.com" =
class=3D"">brong@fastmailteam.com</a><br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&nbsp;<br =
class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&nbsp;<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">&gt;&nbsp;<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt; =
_______________________________________________<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt; calsify mailing list<br =
class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&nbsp;<a href=3D"mailto:calsify@ietf.org" =
class=3D"">calsify@ietf.org</a><br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D"">&gt;&nbsp;<a =
href=3D"https://www.ietf.org/mailman/listinfo/calsify" =
class=3D"">https://www.ietf.org/mailman/listinfo/calsify</a><br =
class=3D""></div><div style=3D"font-family: Arial;" =
class=3D"">&gt;&nbsp;<br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D""><br class=3D""></div><div style=3D"font-family: =
Arial;" class=3D"">--&nbsp;<br class=3D""></div><div style=3D"font-family:=
 Arial;" class=3D"">Ujjwal "Ryzokuken" Sharma (he/him)<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D""><br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">Compilers =
Hacker, Node.js Core Collaborator and Speaker<br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D""><br class=3D""></div><div =
style=3D"font-family: Arial;" =
class=3D"">_______________________________________________<br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D"">calsify =
mailing list<br class=3D""></div><div style=3D"font-family: Arial;" =
class=3D""><a href=3D"mailto:calsify@ietf.org" =
class=3D"">calsify@ietf.org</a><br class=3D""></div><div =
style=3D"font-family: Arial;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/calsify" =
class=3D"">https://www.ietf.org/mailman/listinfo/calsify</a><br =
class=3D""></div><div style=3D"font-family: Arial;" class=3D""><br =
class=3D""></div></blockquote><div style=3D"caret-color: rgb(0, 0, 0); =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; font-family: Arial;" class=3D""><br class=3D""></div><div =
id=3D"sig56629417" style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 16px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><div class=3D"signature">--<br class=3D""></div><div =
class=3D"signature">&nbsp; Bron Gondwana, CEO, Fastmail Pty Ltd<br =
class=3D""></div><div class=3D"signature">&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:brong@fastmailteam.com" =
class=3D"">brong@fastmailteam.com</a><br class=3D""></div><div =
class=3D"signature"><br class=3D""></div></div><div style=3D"caret-color: =
rgb(0, 0, 0); font-size: 16px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; font-family: Arial;" class=3D""><br class=3D""></div><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">calsify mailing list</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"mailto:calsify@ietf.org" style=3D"font-family: Helvetica; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">calsify@ietf.org</a><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/calsify" =
style=3D"font-family: Helvetica; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/calsify</a></div></blockq=
uote></div><br class=3D""></div></body></html>=

--Apple-Mail=_DAE2E5B3-DB36-4BD7-89A9-634607592028--

--Apple-Mail=_E090BAAA-43CB-471E-B6DD-DCD75E4C3AD8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAmANTNAACgkQh7ZrRtnS
ejPuJAgAgVSQsNGlJBxBd9cW8v4W40OhTai5twM/FwrRIXOJ9Ei+D3EhslWI/zdk
lPiY5McRzIq+ij/0H2fXeGuH+26Eho4LHIwzTTdmYr5+NfnuYxPyllLOe42Q0LsH
dPAWg1wPa1q/K1pihLxFuUwwjK8PQs82a+hDWa5zU1EeXFRPekb2BwodUL3ANUC3
RDQvyGVUz+TvsjQx1gaz2uYtctsaBV4W7RmYo7mK2+dhCeM8FQB21CxO9Tq7gBJI
TUcjb14BRLvbk/jXpoFRzfYBQrcZQpO7la+Xvw391zS/tVxVjn5b5mUTIHKgeB/7
h+4Gukj1LRBy3h75X+9naYp1a6Ts+g==
=J71M
-----END PGP SIGNATURE-----

--Apple-Mail=_E090BAAA-43CB-471E-B6DD-DCD75E4C3AD8--


From nobody Sun Jan 24 02:53:33 2021
Return-Path: <brong@fastmailteam.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24AEB3A12D5 for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 02:53:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.296
X-Spam-Level: 
X-Spam-Status: No, score=-1.296 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SHORTENED_URL_HREF=0.822, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=ToEH4Tbb; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=LuM+L9Sp
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50UcSuHwGCBf for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 02:53:28 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 519033A12D4 for <calsify@ietf.org>; Sun, 24 Jan 2021 02:53:28 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 89D985C00BA; Sun, 24 Jan 2021 05:53:27 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Sun, 24 Jan 2021 05:53:27 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:cc:subject:content-type; s=fm1; bh=jmsN hgztW/ZlO+kki3Oh44KudTe/HZgMPFVvxXbB0jM=; b=ToEH4TbbCa0p1GSMHgy6 HY0gsISijB1WYITTEpi5ybzu3WIYdnn8krR8bWoNO+6E+QQ0cTwjKfonTtm5knfk v5az9aIuyZpHgDX4QCJMnh2w55S7gBTtDhOrmDagbfvup55LEsAoQdeupBq8fYtZ adPFhgD+DDMhgsM7O72qeRVFAXbfTCoINmhbSFKrwlyhU9Qv62FN08D1RUfSglwp ki84vHFPpdOKFlKJ2jEIDLLuQuMzJUqSd/KllVJfR1VF2CWxMbi19Gdk4vPQhDA5 JjhWWtKUqGTQXTEuLj6VHVt7QsKS3JD1Cl58D15eZl5sz/q4xxJ7e3OR4dtryrjW WA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=jmsNhg ztW/ZlO+kki3Oh44KudTe/HZgMPFVvxXbB0jM=; b=LuM+L9SptEXzkxehGuTApI 34duR6WyuzUfvT/edTmAKfbsahCRb3uXkRf4IlUgiIlPtuX860FChKgNkPQiLGny uReGp+3+pEHZbAP5v3M6gezwENdWSYeYUyFPYsyub65q849dVk+sX2iAbM4KCO9y Bj2rlvHemKU4HqjNIUWWpUBptxVp0tWrRTY9FfQ/1dU++zgTX4QdWFkic8InVK0u S688J35LgsHaUDfL1qBoc3+UpodxIbH6OpYgTUygSIVWJxgANvVeQe9vpWTxkxBs rZ1mZ9JbvMmjFN+3Khe7AVQF4pMnet1FXWFHYNrEsbCP35bU/jnMpFRJpl2Qaj3w ==
X-ME-Sender: <xms:plENYLfWRa8GZG_1oRnIId0bOogUS01qBI8fs5gYZFGDf5xwVrucVw> <xme:plENYBPyTkrEE8olM45AAedoZYxV6yGmf4mQudrkwslo9btZy4TxnzdQXeny-EP4d hCdA-j-BgM>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddugddvvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerreejnecuhfhrohhmpedfuehrohhn ucfiohhnugifrghnrgdfuceosghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucggtffrrghtthgvrhhnpeekveejlefggfdtkefggedukeffhfeltdduueeftdeggfdt ieeuueeufeetgeekgfenucffohhmrghinhephihouhhtuhdrsggvpdhivghtfhdrohhrgh dpghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:plENYEh8_ivE24nEJ5g7o3a-1Bom28CEQ-Gpi2F4IxOcXmqlFuCHvA> <xmx:plENYM8GR6YK-BvpAG_ju42xv5yqhA33UUDWVIIOrR-jNG3riwhfxQ> <xmx:plENYHukc6EiIqDy2JJcvWlQFXbTm2J_Nj3vQxko9QveRzqsanhpEA> <xmx:p1ENYF3as5E7qcmoIEh2aSGNI2-FQTpbj13iyRXkuspTbI1EDqH5kQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 18469360068; Sun, 24 Jan 2021 05:53:26 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-78-g36b56e88ef-fm-20210120.001-g36b56e88
Mime-Version: 1.0
Message-Id: <fd342b5e-d998-487e-8fa2-5dd949b517e8@dogfood.fastmail.com>
In-Reply-To: <AAD5976B-A601-45AC-9E43-CEB24D57BD1E@cisco.com>
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <0275d5af-6eea-4608-913e-c96d59c0abea@dogfood.fastmail.com> <c87c068b-02f1-913a-64ef-497f827fc3ea@igalia.com> <27ae33c7-d5cf-428b-99fa-7b974be85e70@dogfood.fastmail.com> <AAD5976B-A601-45AC-9E43-CEB24D57BD1E@cisco.com>
Date: Sun, 24 Jan 2021 21:53:05 +1100
From: "Bron Gondwana" <brong@fastmailteam.com>
To: "Eliot Lear" <lear@cisco.com>
Cc: "Barry Leiba" <barryleiba@computer.org>, calsify@ietf.org
Content-Type: multipart/alternative; boundary=58924dfd5a5d4a919c01ccf88f84c759
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/GZbaggnMYGvFg-GCUZIvDQJF23o>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jan 2021 10:53:31 -0000

--58924dfd5a5d4a919c01ccf88f84c759
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable

I'll ask you the same question I asked Ned, which is "do you object to t=
his work being taken up by the IETF at all, or just to it obsoleting 333=
9?"

I will also point out that for all that we've talked about making the IE=
TF more welcoming to newcomers, this has been a really unfriendly experi=
ence for Ujjwal.  Maybe that's my fault, but I'm sorry Ujjwal for mislea=
ding you if so.  I did raise that this work was coming in the "any other=
 business" at IETF110's DISPATCH, but without a draft there was very lit=
tle guidance.  Indeed the minutes of last dispatch say:

Bron Gondwana: RFC3339 extension
* Javascript notation format is looking for a standard serialisation.

Harald Alvestrand:
* We should have done this in the 90s!  It was a mistake not to do it th=
en.

Neil Jenkins:
* we do need a serialisation format

Where to discuss: calsify or tzdata lists, but probably calsify is best.=


You can watch a video of the exact discussion here: https://youtu.be/d87=
1MoUgAKU?t=3D6418

...

Regardless, it appears that the right next venue for this document is DI=
SPATCH at IETF110.

Regards,

Bron.

On Sun, Jan 24, 2021, at 21:32, Eliot Lear wrote:
> Bron,
>=20
> I=E2=80=99m sorry, but I have both substantive and procedural problems=
 with you moving forward like this.  Let me start with the procedural.  =
This work isn=E2=80=99t in calext=E2=80=99s charter.  You are specifical=
ly chartered to tackle several extensions to the iCalendar format, and t=
hat is it.  This is not an extension to that format.  This is a change t=
o a standard that is used extremely broadly.
>=20
> And this leads me to the substantive concern: this change *is *backwar=
d incompatible with  3339.  The ABNF in 3339 is clear: the stamp ends "t=
ime-offset" ("Z" / time-numoffset).  Adding =E2=80=9Csuffix" blow up in =
any yacc/bison-based parser and who knows what else.  Just imagine all t=
he perl, awk, php, and python that whacks this stuff.
>=20
> In a great many cases, there is no means to negotiate the extension.  =
Let me give you two examples:
>=20
>  * Logging software commonly uses 3339 both for generation and for par=
sing, and the parsers themselves are notoriously fragile to the point th=
at I do not believe any of them would entertain any changes to 3339.  Th=
e ecosystem is so vast that there is no hope of enumerating it.  To test=
 this, imagine what damage changing any *other* field to syslog would ca=
use.
>  * Calendaring software, though in a smaller ecosystem, will have olde=
r versions that may well fail to parse.
>=20
> I am not saying that 3339 can never be updated, but before it is, it s=
hould be clear that (a) it is broadly needed, not just by calendaring, a=
nd (b) that there is reason to believe that the change will be broadly a=
dopted, again not just by calendaring.  If it=E2=80=99s just the calenda=
ring ecosystem, you have properties and parameters to use.
>=20
> Eliot
>=20
>=20
>> On 24 Jan 2021, at 04:15, Bron Gondwana <brong@fastmailteam.com> wrot=
e:
>>=20
>> The document is plenty complete enough for a call for adoption!  I sh=
all do so now.
>>=20
>> You are exactly correct that it's possible to do further iteration af=
ter adoption.
>>=20
>> Thanks,
>>=20
>> Bron.
>>=20
>> On Fri, Jan 22, 2021, at 23:19, Ujjwal Sharma wrote:
>>> Hi Bron, CalExt Friends!
>>>=20
>>> I made a new revision of the draft, which shifts the focus to defini=
ng
>>> the syntax/format and defers the standardization of the actual key-v=
alue
>>> pairs to sibling organizations like IANA and Unicode Consortium.
>>>=20
>>> I'd love to hear your opinions on this version, which you can find a=
t
>>> https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/,=

>>> which can be filed as issues on the GitHub repository or emailed to =
me
>>> directly. In the meantime, I will address the remaining concerns/pol=
ish
>>> issues like fixing the references section.
>>>=20
>>> How "complete" does the document need to be in order to initiate the=

>>> call for adoption? If the current version works, can we start it as =
soon
>>> as possible? Of course, if my understanding of "adoption" is correct=
,
>>> I'd be happy to iterate on the document further after the adoption b=
y
>>> the WG.
>>>=20
>>> Best,
>>> Ujjwal
>>>=20
>>> On 14/01/2021 8.34 am, Bron Gondwana wrote:
>>> > Sounds great.  Let me know :)
>>> >=20
>>> > When we do the call for adoption I'll also advertise the fact over=
 to
>>> > the wider IETF - probably dispatch and tzdata lists at least.
>>> >=20
>>> > Cheers,
>>> >=20
>>> > Bron.
>>> >=20
>>> >=20
>>> > On Thu, Jan 14, 2021, at 13:48, Ujjwal Sharma wrote:
>>> >> Thanks Bron!
>>> >>
>>> >> I'll make a few more changes, release a 01 version, ask for more
>>> >> feedback and then let you know, hopefully by the end of this week=
.
>>> >>
>>> >> Ujjwal
>>> >>
>>> >> On 14/01/2021 7.03 am, Bron Gondwana wrote:
>>> >> > I can do a call for adoption straight away if you like - the ne=
xt
>>> >> > meeting isn't for a couple of months.
>>> >> >=20
>>> >> > Bron.
>>> >> >=20
>>> >> > On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:
>>> >> >> One question: given things move forward smoothly, how do I pro=
ceed?
>>> >> >> Should I apply for this document to be adopted by the calext W=
G? I
>>> >> >> suppose the fastest way to proceed is to present it at the nex=
t IETF
>>> >> >> meeting?
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> Ujjwal
>>> >> >>
>>> >> >> On 12/01/2021 4.03 am, Ujjwal Sharma wrote:
>>> >> >> > Hi Calsify folks!
>>> >> >> >=20
>>> >> >> > I am sorry for the long delay, I got a little sidetracked wo=
rking on
>>> >> >> > other things, but I'm happy to inform you all that I have
>>> >> something that
>>> >> >> > resembles a first draft for the updated timestamps RFC.
>>> >> >> >=20
>>> >> >> > Here's where you can find it:
>>> >> >> >=20
>>> >> >> > Datatracker:
>>> >> >>
>>> >> > https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-exten=
ded/
>>> >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extend=
ed/>
>>> >> >>
>>> >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extend=
ed/
>>> >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extend=
ed/>>
>>> >> >> >
>>> >> >>
>>> >> GitHub: https://github.com/ryzokuken/draft-ryzokuken-datetime-ext=
ended
>>> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>
>>> >> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extende=
d
>>> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>>=

>>> >> >> >=20
>>> >> >> > I would request you all to take a look at it when you can an=
d let me
>>> >> >> > know what you think. You can file a GitHub issue or email me=

>>> >> directly.
>>> >> >> >=20
>>> >> >> > There's a few open discussions regarding the exact format an=
d how the
>>> >> >> > interaction with bodies like the Unicode consortium work, so=

>>> >> please feel
>>> >> >> > free to send me your thoughts regarding that as well.
>>> >> >> >=20
>>> >> >> > Also, some references/bibliography is not perfectly function=
al yet
>>> >> >> > because I am still relatively new to authoring RFCs using
>>> >> Metanorma but
>>> >> >> > I'm actively looking into it.
>>> >> >> >=20
>>> >> >> > Thanks and looking forward to hear from you,
>>> >> >> > Ujjwal
>>> >> >> >=20
>>> >> >>
>>> >> >> --=20
>>> >> >> Ujjwal "Ryzokuken" Sharma (he/him)
>>> >> >>
>>> >> >> Compilers Hacker, Node.js Core Collaborator and Speaker
>>> >> >>
>>> >> >> _______________________________________________
>>> >> >> calsify mailing list
>>> >> >> calsify@ietf.org <mailto:calsify@ietf.org> <mailto:calsify@iet=
f.org
>>> >> <mailto:calsify@ietf.org>>
>>> >> >> https://www.ietf.org/mailman/listinfo/calsify
>>> >> <https://www.ietf.org/mailman/listinfo/calsify>
>>> >> >> <https://www.ietf.org/mailman/listinfo/calsify
>>> >> <https://www.ietf.org/mailman/listinfo/calsify>>
>>> >> >>
>>> >> >=20
>>> >> > --
>>> >> >   Bron Gondwana, CEO, Fastmail Pty Ltd
>>> >> >   brong@fastmailteam.com <mailto:brong@fastmailteam.com>
>>> >> >=20
>>> >> >=20
>>> >> > _______________________________________________
>>> >> > calsify mailing list
>>> >> > calsify@ietf.org <mailto:calsify@ietf.org>
>>> >> > https://www.ietf.org/mailman/listinfo/calsify
>>> >> <https://www.ietf.org/mailman/listinfo/calsify>
>>> >> >=20
>>> >>
>>> >> --=20
>>> >> Ujjwal "Ryzokuken" Sharma (he/him)
>>> >>
>>> >> Compilers Hacker, Node.js Core Collaborator and Speaker
>>> >>
>>> >> _______________________________________________
>>> >> calsify mailing list
>>> >> calsify@ietf.org <mailto:calsify@ietf.org>
>>> >> https://www.ietf.org/mailman/listinfo/calsify
>>> >> <https://www.ietf.org/mailman/listinfo/calsify>
>>> >>
>>> >=20
>>> > --
>>> >   Bron Gondwana, CEO, Fastmail Pty Ltd
>>> >   brong@fastmailteam.com
>>> >=20
>>> >=20
>>> >=20
>>> > _______________________________________________
>>> > calsify mailing list
>>> > calsify@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/calsify
>>> >=20
>>>=20
>>> --=20
>>> Ujjwal "Ryzokuken" Sharma (he/him)
>>>=20
>>> Compilers Hacker, Node.js Core Collaborator and Speaker
>>>=20
>>> _______________________________________________
>>> calsify mailing list
>>> calsify@ietf.org
>>> https://www.ietf.org/mailman/listinfo/calsify
>>>=20
>>=20
>> --
>>   Bron Gondwana, CEO, Fastmail Pty Ltd
>>   brong@fastmailteam.com
>>=20
>>=20
>> _______________________________________________
>> calsify mailing list
>> calsify@ietf.org
>> https://www.ietf.org/mailman/listinfo/calsify
>=20
> *Attachments:*
>  * signature.asc

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com


--58924dfd5a5d4a919c01ccf88f84c759
Content-Type: text/html;charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"font-f=
amily:Arial;">I'll ask you the same question I asked Ned, which is "do y=
ou object to this work being taken up by the IETF at all, or just to it =
obsoleting 3339?"<br></div><div style=3D"font-family:Arial;"><br></div><=
div style=3D"font-family:Arial;">I will also point out that for all that=
 we've talked about making the IETF more welcoming to newcomers, this ha=
s been a really unfriendly experience for Ujjwal.&nbsp; Maybe that's my =
fault, but I'm sorry Ujjwal for misleading you if so.&nbsp; I did raise =
that this work was coming in the "any other business" at IETF110's DISPA=
TCH, but without a draft there was very little guidance.&nbsp; Indeed th=
e minutes of last dispatch say:<br></div><div style=3D"font-family:Arial=
;"><br></div><pre>Bron Gondwana: RFC3339 extension
* Javascript notation format is looking for a standard serialisation.

Harald Alvestrand:
* We should have done this in the 90s!  It was a mistake not to do it th=
en.

Neil Jenkins:
* we do need a serialisation format

Where to discuss: calsify or tzdata lists, but probably calsify is best.=
<br></pre><div style=3D"font-family:Arial;"><br></div><div style=3D"font=
-family:Arial;">You can watch a video of the exact discussion here: <a h=
ref=3D"https://youtu.be/d871MoUgAKU?t=3D6418">https://youtu.be/d871MoUgA=
KU?t=3D6418</a><br></div><div style=3D"font-family:Arial;"><br></div><di=
v style=3D"font-family:Arial;">...<br></div><div style=3D"font-family:Ar=
ial;"><br></div><div style=3D"font-family:Arial;">Regardless, it appears=
 that the right next venue for this document is DISPATCH at IETF110.<br>=
</div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-fam=
ily:Arial;">Regards,<br></div><div style=3D"font-family:Arial;"><br></di=
v><div style=3D"font-family:Arial;">Bron.<br></div><div style=3D"font-fa=
mily:Arial;"><br></div><div>On Sun, Jan 24, 2021, at 21:32, Eliot Lear w=
rote:<br></div><blockquote type=3D"cite" id=3D"qt" style=3D"overflow-wra=
p:break-word;"><div>Bron,<br></div><div class=3D"qt-"><br></div><div cla=
ss=3D"qt-">I=E2=80=99m sorry, but I have both substantive and procedural=
 problems with you moving forward like this. &nbsp;Let me start with the=
 procedural. &nbsp;This work isn=E2=80=99t in calext=E2=80=99s charter. =
&nbsp;You are specifically chartered to tackle several extensions to the=
 iCalendar format, and that is it. &nbsp;This is not an extension to tha=
t format. &nbsp;This is a change to a standard that is used extremely br=
oadly.<br></div><div class=3D"qt-"><br></div><div class=3D"qt-">And this=
 leads me to the substantive concern: this change <b class=3D"qt-">is&nb=
sp;</b>backward incompatible with &nbsp;3339. &nbsp;The ABNF in 3339 is =
clear: the stamp ends "time-offset" ("Z" / time-numoffset). &nbsp;Adding=
 =E2=80=9Csuffix" blow up in any yacc/bison-based parser and who knows w=
hat else. &nbsp;Just imagine all the perl, awk, php, and python that wha=
cks this stuff.<br></div><div class=3D"qt-"><br></div><div class=3D"qt-"=
>In a great many cases, there is no means to negotiate the extension. &n=
bsp;Let me give you two examples:<br></div><div class=3D"qt-"><br></div>=
<div class=3D"qt-"><ul class=3D"qt-MailOutline"><li class=3D"qt-">Loggin=
g software commonly uses 3339 both for generation and for parsing, and t=
he parsers themselves are notoriously fragile to the point that I do not=
 believe any of them would entertain any changes to 3339. &nbsp;The ecos=
ystem is so vast that there is no hope of enumerating it. &nbsp;To test =
this, imagine what damage changing any <b class=3D"qt-">other</b>&nbsp;f=
ield to syslog would cause.<br></li><li class=3D"qt-">Calendaring softwa=
re, though in a smaller ecosystem, will have older versions that may wel=
l fail to parse.<br></li></ul></div><div class=3D"qt-"><div><br></div><d=
iv>I am not saying that 3339 can never be updated, but before it is, it =
should be clear that (a) it is broadly needed, not just by calendaring, =
and (b) that there is reason to believe that the change will be broadly =
adopted, again not just by calendaring. &nbsp;If it=E2=80=99s just the c=
alendaring ecosystem, you have properties and parameters to use.<br></di=
v><div><br></div><div>Eliot<br></div><div><br></div><div><br></div><div>=
<blockquote type=3D"cite" class=3D"qt-"><div class=3D"qt-">On 24 Jan 202=
1, at 04:15, Bron Gondwana &lt;<a href=3D"mailto:brong@fastmailteam.com"=
 class=3D"qt-">brong@fastmailteam.com</a>&gt; wrote:<br></div><div><br><=
/div><div class=3D"qt-"><div style=3D"font-size:16px;font-style:normal;f=
ont-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-al=
ign:start;text-indent:0px;text-transform:none;white-space:normal;word-sp=
acing:0px;-webkit-text-stroke-width:0px;text-decoration-line:none;text-d=
ecoration-style:solid;text-decoration-color:currentcolor;text-decoration=
-thickness:auto;font-family:Arial;" class=3D"qt-">The document is plenty=
 complete enough for a call for adoption!&nbsp; I shall do so now.<br></=
div><div style=3D"font-size:16px;font-style:normal;font-variant-caps:nor=
mal;font-weight:normal;letter-spacing:normal;text-align:start;text-inden=
t:0px;text-transform:none;white-space:normal;word-spacing:0px;-webkit-te=
xt-stroke-width:0px;text-decoration-line:none;text-decoration-style:soli=
d;text-decoration-color:currentcolor;text-decoration-thickness:auto;font=
-family:Arial;" class=3D"qt-"><br></div><div style=3D"font-size:16px;fon=
t-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacin=
g:normal;text-align:start;text-indent:0px;text-transform:none;white-spac=
e:normal;word-spacing:0px;-webkit-text-stroke-width:0px;text-decoration-=
line:none;text-decoration-style:solid;text-decoration-color:currentcolor=
;text-decoration-thickness:auto;font-family:Arial;" class=3D"qt-">You ar=
e exactly correct that it's possible to do further iteration after adopt=
ion.<br></div><div style=3D"font-size:16px;font-style:normal;font-varian=
t-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;=
text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;=
-webkit-text-stroke-width:0px;text-decoration-line:none;text-decoration-=
style:solid;text-decoration-color:currentcolor;text-decoration-thickness=
:auto;font-family:Arial;" class=3D"qt-"><br></div><div style=3D"font-siz=
e:16px;font-style:normal;font-variant-caps:normal;font-weight:normal;let=
ter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;=
white-space:normal;word-spacing:0px;-webkit-text-stroke-width:0px;text-d=
ecoration-line:none;text-decoration-style:solid;text-decoration-color:cu=
rrentcolor;text-decoration-thickness:auto;font-family:Arial;" class=3D"q=
t-">Thanks,<br></div><div style=3D"font-size:16px;font-style:normal;font=
-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align=
:start;text-indent:0px;text-transform:none;white-space:normal;word-spaci=
ng:0px;-webkit-text-stroke-width:0px;text-decoration-line:none;text-deco=
ration-style:solid;text-decoration-color:currentcolor;text-decoration-th=
ickness:auto;font-family:Arial;" class=3D"qt-"><br></div><div style=3D"f=
ont-size:16px;font-style:normal;font-variant-caps:normal;font-weight:nor=
mal;letter-spacing:normal;text-align:start;text-indent:0px;text-transfor=
m:none;white-space:normal;word-spacing:0px;-webkit-text-stroke-width:0px=
;text-decoration-line:none;text-decoration-style:solid;text-decoration-c=
olor:currentcolor;text-decoration-thickness:auto;font-family:Arial;" cla=
ss=3D"qt-">Bron.<br></div><div style=3D"font-size:16px;font-style:normal=
;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-=
align:start;text-indent:0px;text-transform:none;white-space:normal;word-=
spacing:0px;-webkit-text-stroke-width:0px;text-decoration-line:none;text=
-decoration-style:solid;text-decoration-color:currentcolor;text-decorati=
on-thickness:auto;font-family:Arial;" class=3D"qt-"><br></div><div style=
=3D"font-family:Helvetica;font-size:16px;font-style:normal;font-variant-=
caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;te=
xt-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;-w=
ebkit-text-stroke-width:0px;text-decoration-line:none;text-decoration-st=
yle:solid;text-decoration-color:currentcolor;text-decoration-thickness:a=
uto;" class=3D"qt-">On Fri, Jan 22, 2021, at 23:19, Ujjwal Sharma wrote:=
<br></div><blockquote type=3D"cite" id=3D"qt-qt" style=3D"font-family:He=
lvetica;font-size:16px;font-style:normal;font-variant-caps:normal;font-w=
eight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text=
-transform:none;white-space:normal;word-spacing:0px;-moz-text-size-adjus=
t:auto;-webkit-text-stroke-width:0px;text-decoration-line:none;text-deco=
ration-style:solid;text-decoration-color:currentcolor;text-decoration-th=
ickness:auto;" class=3D"qt-"><div style=3D"font-family:Arial;" class=3D"=
qt-">Hi Bron, CalExt Friends!<br></div><div style=3D"font-family:Arial;"=
 class=3D"qt-"><br></div><div style=3D"font-family:Arial;" class=3D"qt-"=
>I made a new revision of the draft, which shifts the focus to defining<=
br></div><div style=3D"font-family:Arial;" class=3D"qt-">the syntax/form=
at and defers the standardization of the actual key-value<br></div><div =
style=3D"font-family:Arial;" class=3D"qt-">pairs to sibling organization=
s like IANA and Unicode Consortium.<br></div><div style=3D"font-family:A=
rial;" class=3D"qt-"><br></div><div style=3D"font-family:Arial;" class=3D=
"qt-">I'd love to hear your opinions on this version, which you can find=
 at<br></div><div style=3D"font-family:Arial;" class=3D"qt-"><a href=3D"=
https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/" cla=
ss=3D"qt-">https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-ext=
ended/</a>,<br></div><div style=3D"font-family:Arial;" class=3D"qt-">whi=
ch can be filed as issues on the GitHub repository or emailed to me<br><=
/div><div style=3D"font-family:Arial;" class=3D"qt-">directly. In the me=
antime, I will address the remaining concerns/polish<br></div><div style=
=3D"font-family:Arial;" class=3D"qt-">issues like fixing the references =
section.<br></div><div style=3D"font-family:Arial;" class=3D"qt-"><br></=
div><div style=3D"font-family:Arial;" class=3D"qt-">How "complete" does =
the document need to be in order to initiate the<br></div><div style=3D"=
font-family:Arial;" class=3D"qt-">call for adoption? If the current vers=
ion works, can we start it as soon<br></div><div style=3D"font-family:Ar=
ial;" class=3D"qt-">as possible? Of course, if my understanding of "adop=
tion" is correct,<br></div><div style=3D"font-family:Arial;" class=3D"qt=
-">I'd be happy to iterate on the document further after the adoption by=
<br></div><div style=3D"font-family:Arial;" class=3D"qt-">the WG.<br></d=
iv><div style=3D"font-family:Arial;" class=3D"qt-"><br></div><div style=3D=
"font-family:Arial;" class=3D"qt-">Best,<br></div><div style=3D"font-fam=
ily:Arial;" class=3D"qt-">Ujjwal<br></div><div style=3D"font-family:Aria=
l;" class=3D"qt-"><br></div><div style=3D"font-family:Arial;" class=3D"q=
t-">On 14/01/2021 8.34 am, Bron Gondwana wrote:<br></div><div style=3D"f=
ont-family:Arial;" class=3D"qt-">&gt; Sounds great.&nbsp; Let me know :)=
<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&nbsp;<br>=
</div><div style=3D"font-family:Arial;" class=3D"qt-">&gt; When we do th=
e call for adoption I'll also advertise the fact over to<br></div><div s=
tyle=3D"font-family:Arial;" class=3D"qt-">&gt; the wider IETF - probably=
 dispatch and tzdata lists at least.<br></div><div style=3D"font-family:=
Arial;" class=3D"qt-">&gt;&nbsp;<br></div><div style=3D"font-family:Aria=
l;" class=3D"qt-">&gt; Cheers,<br></div><div style=3D"font-family:Arial;=
" class=3D"qt-">&gt;&nbsp;<br></div><div style=3D"font-family:Arial;" cl=
ass=3D"qt-">&gt; Bron.<br></div><div style=3D"font-family:Arial;" class=3D=
"qt-">&gt;&nbsp;<br></div><div style=3D"font-family:Arial;" class=3D"qt-=
">&gt;&nbsp;<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&g=
t; On Thu, Jan 14, 2021, at 13:48, Ujjwal Sharma wrote:<br></div><div st=
yle=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; Thanks Bron!<br></div>=
<div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt;<br></div><div s=
tyle=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; I'll make a few more =
changes, release a 01 version, ask for more<br></div><div style=3D"font-=
family:Arial;" class=3D"qt-">&gt;&gt; feedback and then let you know, ho=
pefully by the end of this week.<br></div><div style=3D"font-family:Aria=
l;" class=3D"qt-">&gt;&gt;<br></div><div style=3D"font-family:Arial;" cl=
ass=3D"qt-">&gt;&gt; Ujjwal<br></div><div style=3D"font-family:Arial;" c=
lass=3D"qt-">&gt;&gt;<br></div><div style=3D"font-family:Arial;" class=3D=
"qt-">&gt;&gt; On 14/01/2021 7.03 am, Bron Gondwana wrote:<br></div><div=
 style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt; I can do a cal=
l for adoption straight away if you like - the next<br></div><div style=3D=
"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt; meeting isn't for a cou=
ple of months.<br></div><div style=3D"font-family:Arial;" class=3D"qt-">=
&gt;&gt; &gt;&nbsp;<br></div><div style=3D"font-family:Arial;" class=3D"=
qt-">&gt;&gt; &gt; Bron.<br></div><div style=3D"font-family:Arial;" clas=
s=3D"qt-">&gt;&gt; &gt;&nbsp;<br></div><div style=3D"font-family:Arial;"=
 class=3D"qt-">&gt;&gt; &gt; On Thu, Jan 14, 2021, at 05:24, Ujjwal Shar=
ma wrote:<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&=
gt; &gt;&gt; One question: given things move forward smoothly, how do I =
proceed?<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&g=
t; &gt;&gt; Should I apply for this document to be adopted by the calext=
 WG? I<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt;=
 &gt;&gt; suppose the fastest way to proceed is to present it at the nex=
t IETF<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt;=
 &gt;&gt; meeting?<br></div><div style=3D"font-family:Arial;" class=3D"q=
t-">&gt;&gt; &gt;&gt;<br></div><div style=3D"font-family:Arial;" class=3D=
"qt-">&gt;&gt; &gt;&gt;<br></div><div style=3D"font-family:Arial;" class=
=3D"qt-">&gt;&gt; &gt;&gt;<br></div><div style=3D"font-family:Arial;" cl=
ass=3D"qt-">&gt;&gt; &gt;&gt; Ujjwal<br></div><div style=3D"font-family:=
Arial;" class=3D"qt-">&gt;&gt; &gt;&gt;<br></div><div style=3D"font-fami=
ly:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; On 12/01/2021 4.03 am, Ujjwal=
 Sharma wrote:<br></div><div style=3D"font-family:Arial;" class=3D"qt-">=
&gt;&gt; &gt;&gt; &gt; Hi Calsify folks!<br></div><div style=3D"font-fam=
ily:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &gt;&nbsp;<br></div><div sty=
le=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &gt; I am sorr=
y for the long delay, I got a little sidetracked working on<br></div><di=
v style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &gt; othe=
r things, but I'm happy to inform you all that I have<br></div><div styl=
e=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; something that<br></div>=
<div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &gt; r=
esembles a first draft for the updated timestamps RFC.<br></div><div sty=
le=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &gt;&nbsp;<br>=
</div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; =
&gt; Here's where you can find it:<br></div><div style=3D"font-family:Ar=
ial;" class=3D"qt-">&gt;&gt; &gt;&gt; &gt;&nbsp;<br></div><div style=3D"=
font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &gt; Datatracker:<br=
></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt;=
<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&=
nbsp;<a href=3D"https://datatracker.ietf.org/doc/draft-ryzokuken-datetim=
e-extended/" class=3D"qt-">https://datatracker.ietf.org/doc/draft-ryzoku=
ken-datetime-extended/</a><br></div><div style=3D"font-family:Arial;" cl=
ass=3D"qt-">&gt;&gt; &lt;<a href=3D"https://datatracker.ietf.org/doc/dra=
ft-ryzokuken-datetime-extended/" class=3D"qt-">https://datatracker.ietf.=
org/doc/draft-ryzokuken-datetime-extended/</a>&gt;<br></div><div style=3D=
"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt;<br></div><div style=
=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &lt;<a href=3D"https://da=
tatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/" class=3D"qt-"=
>https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/</a>=
<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &lt;<=
a href=3D"https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-exte=
nded/" class=3D"qt-">https://datatracker.ietf.org/doc/draft-ryzokuken-da=
tetime-extended/</a>&gt;&gt;<br></div><div style=3D"font-family:Arial;" =
class=3D"qt-">&gt;&gt; &gt;&gt; &gt;<br></div><div style=3D"font-family:=
Arial;" class=3D"qt-">&gt;&gt; &gt;&gt;<br></div><div style=3D"font-fami=
ly:Arial;" class=3D"qt-">&gt;&gt; GitHub:&nbsp;<a href=3D"https://github=
.com/ryzokuken/draft-ryzokuken-datetime-extended" class=3D"qt-">https://=
github.com/ryzokuken/draft-ryzokuken-datetime-extended</a><br></div><div=
 style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &lt;<a href=3D"http=
s://github.com/ryzokuken/draft-ryzokuken-datetime-extended" class=3D"qt-=
">https://github.com/ryzokuken/draft-ryzokuken-datetime-extended</a>&gt;=
<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&=
gt; &lt;<a href=3D"https://github.com/ryzokuken/draft-ryzokuken-datetime=
-extended" class=3D"qt-">https://github.com/ryzokuken/draft-ryzokuken-da=
tetime-extended</a><br></div><div style=3D"font-family:Arial;" class=3D"=
qt-">&gt;&gt; &lt;<a href=3D"https://github.com/ryzokuken/draft-ryzokuke=
n-datetime-extended" class=3D"qt-">https://github.com/ryzokuken/draft-ry=
zokuken-datetime-extended</a>&gt;&gt;<br></div><div style=3D"font-family=
:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &gt;&nbsp;<br></div><div style=3D=
"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &gt; I would reques=
t you all to take a look at it when you can and let me<br></div><div sty=
le=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &gt; know what=
 you think. You can file a GitHub issue or email me<br></div><div style=3D=
"font-family:Arial;" class=3D"qt-">&gt;&gt; directly.<br></div><div styl=
e=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &gt;&nbsp;<br><=
/div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &=
gt; There's a few open discussions regarding the exact format and how th=
e<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;=
&gt; &gt; interaction with bodies like the Unicode consortium work, so<b=
r></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; please =
feel<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &=
gt;&gt; &gt; free to send me your thoughts regarding that as well.<br></=
div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &g=
t;&nbsp;<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&g=
t; &gt;&gt; &gt; Also, some references/bibliography is not perfectly fun=
ctional yet<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt=
;&gt; &gt;&gt; &gt; because I am still relatively new to authoring RFCs =
using<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; =
Metanorma but<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&=
gt;&gt; &gt;&gt; &gt; I'm actively looking into it.<br></div><div style=3D=
"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &gt;&nbsp;<br></div=
><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &gt; =
Thanks and looking forward to hear from you,<br></div><div style=3D"font=
-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &gt; Ujjwal<br></div><di=
v style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &gt;&nbsp=
;<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;=
&gt;<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &=
gt;&gt; --&nbsp;<br></div><div style=3D"font-family:Arial;" class=3D"qt-=
">&gt;&gt; &gt;&gt; Ujjwal "Ryzokuken" Sharma (he/him)<br></div><div sty=
le=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt;<br></div><div =
style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; Compilers H=
acker, Node.js Core Collaborator and Speaker<br></div><div style=3D"font=
-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt;<br></div><div style=3D"f=
ont-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; _____________________=
__________________________<br></div><div style=3D"font-family:Arial;" cl=
ass=3D"qt-">&gt;&gt; &gt;&gt; calsify mailing list<br></div><div style=3D=
"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt;&nbsp;<a href=3D"mai=
lto:calsify@ietf.org" class=3D"qt-">calsify@ietf.org</a><span class=3D"q=
t-Apple-converted-space">&nbsp;</span>&lt;mailto:<a href=3D"mailto:calsi=
fy@ietf.org" class=3D"qt-">calsify@ietf.org</a>&gt; &lt;mailto:<a href=3D=
"mailto:calsify@ietf.org" class=3D"qt-">calsify@ietf.org</a><br></div><d=
iv style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &lt;mailto:<a hre=
f=3D"mailto:calsify@ietf.org" class=3D"qt-">calsify@ietf.org</a>&gt;&gt;=
<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&=
gt;&nbsp;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify" class=
=3D"qt-">https://www.ietf.org/mailman/listinfo/calsify</a><br></div><div=
 style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &lt;<a href=3D"http=
s://www.ietf.org/mailman/listinfo/calsify" class=3D"qt-">https://www.iet=
f.org/mailman/listinfo/calsify</a>&gt;<br></div><div style=3D"font-famil=
y:Arial;" class=3D"qt-">&gt;&gt; &gt;&gt; &lt;<a href=3D"https://www.iet=
f.org/mailman/listinfo/calsify" class=3D"qt-">https://www.ietf.org/mailm=
an/listinfo/calsify</a><br></div><div style=3D"font-family:Arial;" class=
=3D"qt-">&gt;&gt; &lt;<a href=3D"https://www.ietf.org/mailman/listinfo/c=
alsify" class=3D"qt-">https://www.ietf.org/mailman/listinfo/calsify</a>&=
gt;&gt;<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt=
; &gt;&gt;<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;=
&gt; &gt;&nbsp;<br></div><div style=3D"font-family:Arial;" class=3D"qt-"=
>&gt;&gt; &gt; --<br></div><div style=3D"font-family:Arial;" class=3D"qt=
-">&gt;&gt; &gt; &nbsp; Bron Gondwana, CEO, Fastmail Pty Ltd<br></div><d=
iv style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt; &nbsp;&nbsp;=
<a href=3D"mailto:brong@fastmailteam.com" class=3D"qt-">brong@fastmailte=
am.com</a><span class=3D"qt-Apple-converted-space">&nbsp;</span>&lt;mail=
to:<a href=3D"mailto:brong@fastmailteam.com" class=3D"qt-">brong@fastmai=
lteam.com</a>&gt;<br></div><div style=3D"font-family:Arial;" class=3D"qt=
-">&gt;&gt; &gt;&nbsp;<br></div><div style=3D"font-family:Arial;" class=3D=
"qt-">&gt;&gt; &gt;&nbsp;<br></div><div style=3D"font-family:Arial;" cla=
ss=3D"qt-">&gt;&gt; &gt; _______________________________________________=
<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt; =
calsify mailing list<br></div><div style=3D"font-family:Arial;" class=3D=
"qt-">&gt;&gt; &gt;&nbsp;<a href=3D"mailto:calsify@ietf.org" class=3D"qt=
-">calsify@ietf.org</a><span class=3D"qt-Apple-converted-space">&nbsp;</=
span>&lt;mailto:<a href=3D"mailto:calsify@ietf.org" class=3D"qt-">calsif=
y@ietf.org</a>&gt;<br></div><div style=3D"font-family:Arial;" class=3D"q=
t-">&gt;&gt; &gt;&nbsp;<a href=3D"https://www.ietf.org/mailman/listinfo/=
calsify" class=3D"qt-">https://www.ietf.org/mailman/listinfo/calsify</a>=
<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &lt;<=
a href=3D"https://www.ietf.org/mailman/listinfo/calsify" class=3D"qt-">h=
ttps://www.ietf.org/mailman/listinfo/calsify</a>&gt;<br></div><div style=
=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &gt;&nbsp;<br></div><div =
style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt;<br></div><div style=3D=
"font-family:Arial;" class=3D"qt-">&gt;&gt; --&nbsp;<br></div><div style=
=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; Ujjwal "Ryzokuken" Sharma=
 (he/him)<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&=
gt;<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; Co=
mpilers Hacker, Node.js Core Collaborator and Speaker<br></div><div styl=
e=3D"font-family:Arial;" class=3D"qt-">&gt;&gt;<br></div><div style=3D"f=
ont-family:Arial;" class=3D"qt-">&gt;&gt; ______________________________=
_________________<br></div><div style=3D"font-family:Arial;" class=3D"qt=
-">&gt;&gt; calsify mailing list<br></div><div style=3D"font-family:Aria=
l;" class=3D"qt-">&gt;&gt;&nbsp;<a href=3D"mailto:calsify@ietf.org" clas=
s=3D"qt-">calsify@ietf.org</a><span class=3D"qt-Apple-converted-space">&=
nbsp;</span>&lt;mailto:<a href=3D"mailto:calsify@ietf.org" class=3D"qt-"=
>calsify@ietf.org</a>&gt;<br></div><div style=3D"font-family:Arial;" cla=
ss=3D"qt-">&gt;&gt;&nbsp;<a href=3D"https://www.ietf.org/mailman/listinf=
o/calsify" class=3D"qt-">https://www.ietf.org/mailman/listinfo/calsify</=
a><br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&gt; &lt=
;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify" class=3D"qt-"=
>https://www.ietf.org/mailman/listinfo/calsify</a>&gt;<br></div><div sty=
le=3D"font-family:Arial;" class=3D"qt-">&gt;&gt;<br></div><div style=3D"=
font-family:Arial;" class=3D"qt-">&gt;&nbsp;<br></div><div style=3D"font=
-family:Arial;" class=3D"qt-">&gt; --<br></div><div style=3D"font-family=
:Arial;" class=3D"qt-">&gt; &nbsp; Bron Gondwana, CEO, Fastmail Pty Ltd<=
br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt; &nbsp;&nbs=
p;<a href=3D"mailto:brong@fastmailteam.com" class=3D"qt-">brong@fastmail=
team.com</a><br></div><div style=3D"font-family:Arial;" class=3D"qt-">&g=
t;&nbsp;<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&n=
bsp;<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt;&nbsp;=
<br></div><div style=3D"font-family:Arial;" class=3D"qt-">&gt; _________=
______________________________________<br></div><div style=3D"font-famil=
y:Arial;" class=3D"qt-">&gt; calsify mailing list<br></div><div style=3D=
"font-family:Arial;" class=3D"qt-">&gt;&nbsp;<a href=3D"mailto:calsify@i=
etf.org" class=3D"qt-">calsify@ietf.org</a><br></div><div style=3D"font-=
family:Arial;" class=3D"qt-">&gt;&nbsp;<a href=3D"https://www.ietf.org/m=
ailman/listinfo/calsify" class=3D"qt-">https://www.ietf.org/mailman/list=
info/calsify</a><br></div><div style=3D"font-family:Arial;" class=3D"qt-=
">&gt;&nbsp;<br></div><div style=3D"font-family:Arial;" class=3D"qt-"><b=
r></div><div style=3D"font-family:Arial;" class=3D"qt-">--&nbsp;<br></di=
v><div style=3D"font-family:Arial;" class=3D"qt-">Ujjwal "Ryzokuken" Sha=
rma (he/him)<br></div><div style=3D"font-family:Arial;" class=3D"qt-"><b=
r></div><div style=3D"font-family:Arial;" class=3D"qt-">Compilers Hacker=
, Node.js Core Collaborator and Speaker<br></div><div style=3D"font-fami=
ly:Arial;" class=3D"qt-"><br></div><div style=3D"font-family:Arial;" cla=
ss=3D"qt-">_______________________________________________<br></div><div=
 style=3D"font-family:Arial;" class=3D"qt-">calsify mailing list<br></di=
v><div style=3D"font-family:Arial;" class=3D"qt-"><a href=3D"mailto:cals=
ify@ietf.org" class=3D"qt-">calsify@ietf.org</a><br></div><div style=3D"=
font-family:Arial;" class=3D"qt-"><a href=3D"https://www.ietf.org/mailma=
n/listinfo/calsify" class=3D"qt-">https://www.ietf.org/mailman/listinfo/=
calsify</a><br></div><div style=3D"font-family:Arial;" class=3D"qt-"><br=
></div></blockquote><div style=3D"font-size:16px;font-style:normal;font-=
variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:=
start;text-indent:0px;text-transform:none;white-space:normal;word-spacin=
g:0px;-webkit-text-stroke-width:0px;text-decoration-line:none;text-decor=
ation-style:solid;text-decoration-color:currentcolor;text-decoration-thi=
ckness:auto;font-family:Arial;" class=3D"qt-"><br></div><div id=3D"qt-si=
g56629417" style=3D"font-family:Helvetica;font-size:16px;font-style:norm=
al;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;tex=
t-align:start;text-indent:0px;text-transform:none;white-space:normal;wor=
d-spacing:0px;-webkit-text-stroke-width:0px;text-decoration-line:none;te=
xt-decoration-style:solid;text-decoration-color:currentcolor;text-decora=
tion-thickness:auto;" class=3D"qt-"><div class=3D"qt-signature">--<br></=
div><div class=3D"qt-signature">&nbsp; Bron Gondwana, CEO, Fastmail Pty =
Ltd<br></div><div class=3D"qt-signature">&nbsp;<span class=3D"qt-Apple-c=
onverted-space">&nbsp;</span><a href=3D"mailto:brong@fastmailteam.com" c=
lass=3D"qt-">brong@fastmailteam.com</a><br></div><div class=3D"qt-signat=
ure"><br></div></div><div style=3D"font-size:16px;font-style:normal;font=
-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align=
:start;text-indent:0px;text-transform:none;white-space:normal;word-spaci=
ng:0px;-webkit-text-stroke-width:0px;text-decoration-line:none;text-deco=
ration-style:solid;text-decoration-color:currentcolor;text-decoration-th=
ickness:auto;font-family:Arial;" class=3D"qt-"><br></div><div><span styl=
e=3D"font-style:normal;font-variant-caps:normal;font-weight:normal;lette=
r-spacing:normal;text-align:start;text-indent:0px;text-transform:none;wh=
ite-space:normal;word-spacing:0px;-webkit-text-stroke-width:0px;text-dec=
oration-line:none;text-decoration-style:solid;text-decoration-color:curr=
entcolor;text-decoration-thickness:auto;float:none;display:inline !impor=
tant;" class=3D"qt-"><span class=3D"font" style=3D"font-family:Helvetica=
;"><span class=3D"size" style=3D"font-size:16px;">______________________=
_________________________</span></span></span><br></div><div><span style=
=3D"font-style:normal;font-variant-caps:normal;font-weight:normal;letter=
-spacing:normal;text-align:start;text-indent:0px;text-transform:none;whi=
te-space:normal;word-spacing:0px;-webkit-text-stroke-width:0px;text-deco=
ration-line:none;text-decoration-style:solid;text-decoration-color:curre=
ntcolor;text-decoration-thickness:auto;float:none;display:inline !import=
ant;" class=3D"qt-"><span class=3D"font" style=3D"font-family:Helvetica;=
"><span class=3D"size" style=3D"font-size:16px;">calsify mailing list</s=
pan></span></span><br></div><div><a href=3D"mailto:calsify@ietf.org" sty=
le=3D"font-family:Helvetica;font-size:16px;font-style:normal;font-varian=
t-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;=
text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;=
-moz-text-size-adjust:auto;-webkit-text-stroke-width:0px;" class=3D"qt-"=
>calsify@ietf.org</a><br></div><div><a href=3D"https://www.ietf.org/mail=
man/listinfo/calsify" style=3D"font-family:Helvetica;font-size:16px;font=
-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing=
:normal;text-align:start;text-indent:0px;text-transform:none;white-space=
:normal;word-spacing:0px;-moz-text-size-adjust:auto;-webkit-text-stroke-=
width:0px;" class=3D"qt-">https://www.ietf.org/mailman/listinfo/calsify<=
/a><br></div></div></blockquote></div></div><div><br></div><div><b>Attac=
hments:</b><br></div><ul><li>signature.asc<br></li></ul></blockquote><di=
v style=3D"font-family:Arial;"><br></div><div id=3D"sig56629417"><div cl=
ass=3D"signature">--<br></div><div class=3D"signature">&nbsp; Bron Gondw=
ana, CEO, Fastmail Pty Ltd<br></div><div class=3D"signature">&nbsp; bron=
g@fastmailteam.com<br></div><div class=3D"signature"><br></div></div><di=
v style=3D"font-family:Arial;"><br></div></body></html>
--58924dfd5a5d4a919c01ccf88f84c759--


From nobody Sun Jan 24 04:47:49 2021
Return-Path: <lear@cisco.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 891263A084A for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 04:47:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.15
X-Spam-Level: 
X-Spam-Status: No, score=-9.15 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.373, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SHORTENED_URL_HREF=0.822, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PrCC3x9xCFHJ for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 04:47:45 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DEA43A083E for <calsify@ietf.org>; Sun, 24 Jan 2021 04:47:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15647; q=dns/txt; s=iport; t=1611492465; x=1612702065; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=uCtLOXlP805io6EpkCFqsYvWKcRaEW7QtN6/e++vQJ4=; b=NsSVDGyI88+tyjGg0OE95p9330a+fYRfnRts6zCT8RsD0IDr9tq3vYaH 50wkIVZzD2fP83drPC8xxP/srlWpuIgK1UC2a84MoexTt15LRVLlrEv0m w54iH+mJSG65FnP22UPnyoGD/xp6Cg1EMCOQzydRu3OE5f90zebZEHxGx Q=;
X-Files: signature.asc : 488
X-IPAS-Result: =?us-ascii?q?A0DVAQA1bA1glxbLJq1iHQEBAQEJARIBBQUBgg+BI4F+V?= =?us-ascii?q?wEgEi+EQIkEiFUDh26MNoY1gWgEBwEBAQoDAQEfEAQBAYRKAoF5JjgTAgMBA?= =?us-ascii?q?QEDAgMBAQEBBQEBAQIBBgQUAQEBAQEBAQGGNgyFcwEBAQMBI1YFCwsYFRUCA?= =?us-ascii?q?lcGE4MmAYJmIA+yM3aBMoRAAYEYhHcKBoE4gVOFKIZDQYIAgREnHIFYfj6CX?= =?us-ascii?q?QICF3+BBoJaNIIsBIFULiNdJgQ7GHFnBA1ROI9JNot4nDKDAYMpgTeEUJI/A?= =?us-ascii?q?x+DK4o0hTuJboVwliWJGJJHg3ACBAYFAhaBbSGBRA4HMxoIGxVlAYI+PhIZD?= =?us-ascii?q?Y4tDgmCMIt3QAMwNwIGAQkBAQMJjBUBAQ?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.79,371,1602547200";  d="asc'?scan'208,217";a="32899048"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 24 Jan 2021 12:47:19 +0000
Received: from [10.61.248.209] ([10.61.248.209]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 10OClIiF032535 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 24 Jan 2021 12:47:19 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <7571A862-F132-4A4D-BD88-922367EEC8AC@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E31509B8-AD92-4BB1-95AA-0F68D60602C9"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Sun, 24 Jan 2021 13:47:17 +0100
In-Reply-To: <fd342b5e-d998-487e-8fa2-5dd949b517e8@dogfood.fastmail.com>
Cc: Barry Leiba <barryleiba@computer.org>, calsify@ietf.org
To: Bron Gondwana <brong@fastmailteam.com>
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <0275d5af-6eea-4608-913e-c96d59c0abea@dogfood.fastmail.com> <c87c068b-02f1-913a-64ef-497f827fc3ea@igalia.com> <27ae33c7-d5cf-428b-99fa-7b974be85e70@dogfood.fastmail.com> <AAD5976B-A601-45AC-9E43-CEB24D57BD1E@cisco.com> <fd342b5e-d998-487e-8fa2-5dd949b517e8@dogfood.fastmail.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
X-Outbound-SMTP-Client: 10.61.248.209, [10.61.248.209]
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/1SawuKdcWJqI_biuI5q5OmmkLW8>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jan 2021 12:47:48 -0000

--Apple-Mail=_E31509B8-AD92-4BB1-95AA-0F68D60602C9
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_DE373848-8E25-4D3B-9FA1-1963A5398336"


--Apple-Mail=_DE373848-8E25-4D3B-9FA1-1963A5398336
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Bron,

Thanks for taking my views into account.  Please see below.

> On 24 Jan 2021, at 11:53, Bron Gondwana <brong@fastmailteam.com> =
wrote:
>=20
> I'll ask you the same question I asked Ned, which is "do you object to =
this work being taken up by the IETF at all, or just to it obsoleting =
3339?"

I think it depends on what you mean by =E2=80=9Cthis=E2=80=9D.  If =
=E2=80=9Cthis=E2=80=9D means modifying the 3339 timestamp format =
directly, then yes, I would object - at this point (maybe not later, but =
see below).  If =E2=80=9Cthis=E2=80=9D means finding a means to provide =
additional information to a consumer relating to the context of =
timestamp, then no I would not object to the IETF taking it on.  In =
other words, I am not convinced that the current draft is the correct =
starting point, which is why I recommended that this be aired in =
DISPATCH.

I hinted above at a potential way forward for Ujjwal: if we take a step =
back and separate the information model from its representation I think =
things would go a little better.  For instance, the draft defines two =
new information elements: time zone and a calendar tag. Discussing those =
two extensions (or any others) and their value constraints may be =
helpful.  Then discussing how to represent them in different =
environments may be helpful as well.  In this way, you make use of at =
least one existing architectural building block while creating one of =
your own.

You have a lot of tools in your toolbox.  You could easily create a JSON =
array that represents that model that includes a 3339 timestamp and =
whatever additional information you believe appropriate.  You could use =
YANG or your favorite way to do that.  If you use YANG, you get an XML =
serialization for free as well.  And once you=E2=80=99ve done that for =
JSON you=E2=80=99ve also pretty much picked up CBOR, which is nice.  =
Pick your own favorite representation.  The nice thing about YANG is =
that all the O&M people will give you love for that.

If people want to add that object to logs, I imagine that some day =
SYSLOG will get around to being =E2=80=9CJSONified=E2=80=9D and/or =
=E2=80=9CCBORified=E2=80=9D (there were already attempts at XML=E2=80=A6 =
sigh).  And if people using the existing SYSLOG format want to include =
that information today using the existing format, they can just pick up =
the information elements and represent them in the log components that =
they control.

You could do all of this without updating 3339.  Still, there may be a =
need to update 3339, but it has to be done quite carefully, with all =
ramifications, side effects, and alternatives being considered.  Also, I =
could easily imagine both an update to 3339 to do things like obsoleting =
two-digit years and a new draft to handle extensions a=E2=80=99la the =
above.


>=20
> I will also point out that for all that we've talked about making the =
IETF more welcoming to newcomers, this has been a really unfriendly =
experience for Ujjwal.  Maybe that's my fault, but I'm sorry Ujjwal for =
misleading you if so.

I apologize too if my comments are late, but this is pretty =
foundational.


> I did raise that this work was coming in the "any other business" at =
IETF110's DISPATCH, but without a draft there was very little guidance.  =
Indeed the minutes of last dispatch say:
>=20
> Bron Gondwana: RFC3339 extension
> * Javascript notation format is looking for a standard serialisation.
>=20
> Harald Alvestrand:
> * We should have done this in the 90s!  It was a mistake not to do it =
then.
>=20
> Neil Jenkins:
> * we do need a serialisation format
>=20
> Where to discuss: calsify or tzdata lists, but probably calsify is =
best.
>=20
> You can watch a video of the exact discussion here: =
https://youtu.be/d871MoUgAKU?t=3D6418 =
<https://youtu.be/d871MoUgAKU?t=3D6418>
>=20
> ...
>=20
> Regardless, it appears that the right next venue for this document is =
DISPATCH at IETF110.

Yes, please.  Not that I object to this being discussed here prior to =
adoption, so long as the chairs don=E2=80=99t mind (that=E2=80=99s =
entirely your call and entirely not mine).

Eliot



--Apple-Mail=_DE373848-8E25-4D3B-9FA1-1963A5398336
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Bron,<br class=3D""><div><br class=3D""></div><div>Thanks for taking my =
views into account. &nbsp;Please see below.</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On 24 =
Jan 2021, at 11:53, Bron Gondwana &lt;<a =
href=3D"mailto:brong@fastmailteam.com" =
class=3D"">brong@fastmailteam.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" class=3D""><div style=3D"caret-color: rgb(0, 0, 0); =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; font-family: Arial;" class=3D"">I'll ask you the same question I =
asked Ned, which is "do you object to this work being taken up by the =
IETF at all, or just to it obsoleting 3339?"<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>I =
think it depends on what you mean by =E2=80=9Cthis=E2=80=9D. &nbsp;If =
=E2=80=9Cthis=E2=80=9D means modifying the 3339 timestamp format =
directly, then yes, I would object - <b class=3D"">at this =
point</b>&nbsp;(maybe not later, but see below). &nbsp;If =E2=80=9Cthis=E2=
=80=9D means finding a means to provide additional information to a =
consumer relating to the context of timestamp, then no I would not =
object to the IETF taking it on. &nbsp;In other words, I am not =
convinced that the current draft is the correct starting point, which is =
why I recommended that this be aired in DISPATCH.</div><div><br =
class=3D""></div><div>I hinted above at a potential way forward =
for&nbsp;<span style=3D"font-family: Arial;" =
class=3D"">Ujjwal:</span>&nbsp;if we take a step back and separate the =
information model from its representation I think things would go a =
little better. &nbsp;For instance, the draft defines two new information =
elements: time zone and a calendar tag. Discussing those two extensions =
(or any others) and their value constraints may be helpful. &nbsp;Then =
discussing how to represent them in different environments may be =
helpful as well. &nbsp;In this way, you make use of at least one =
existing architectural building block while creating one of your =
own.</div><div><br class=3D""></div><div>You have a lot of tools in your =
toolbox. &nbsp;You could easily create a JSON array that represents that =
model that includes a 3339 timestamp and whatever additional information =
you believe appropriate. &nbsp;You could use YANG or your favorite way =
to do that. &nbsp;If you use YANG, you get an XML serialization for free =
as well. &nbsp;And once you=E2=80=99ve done that for JSON you=E2=80=99ve =
also pretty much picked up CBOR, which is nice. &nbsp;Pick your own =
favorite representation. &nbsp;The nice thing about YANG is that all the =
O&amp;M people will give you love for that.</div><div><br =
class=3D""></div><div>If people want to add that object to logs, I =
imagine that some day SYSLOG will get around to being =E2=80=9CJSONified=E2=
=80=9D and/or =E2=80=9CCBORified=E2=80=9D (there were already attempts =
at XML=E2=80=A6 sigh). &nbsp;And if people using the existing SYSLOG =
format want to include that information today using the existing format, =
they can just pick up the information elements and represent them in the =
log components that they control.</div><div><br class=3D""></div><div>You =
could do all of this without updating 3339. &nbsp;Still, there may be a =
need to update 3339, but it has to be done quite carefully, with all =
ramifications, side effects, and alternatives being considered. =
&nbsp;Also, I could easily imagine <b class=3D"">both</b>&nbsp;an update =
to 3339 to do things like obsoleting two-digit years&nbsp;<b =
class=3D"">and</b>&nbsp;a new draft to handle extensions a=E2=80=99la =
the above.</div><div><br class=3D""></div></div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
style=3D"caret-color: rgb(0, 0, 0); font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Arial;" class=3D""><br =
class=3D""></div><div style=3D"caret-color: rgb(0, 0, 0); font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; font-family: =
Arial;" class=3D"">I will also point out that for all that we've talked =
about making the IETF more welcoming to newcomers, this has been a =
really unfriendly experience for Ujjwal.&nbsp; Maybe that's my fault, =
but I'm sorry Ujjwal for misleading you if so.&nbsp; =
</div></div></blockquote><div><br class=3D""></div>I apologize too if my =
comments are late, but this is pretty foundational.</div><div><br =
class=3D""></div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div style=3D"caret-color: rgb(0, 0, 0); =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; font-family: Arial;" class=3D"">I did raise that this work was =
coming in the "any other business" at IETF110's DISPATCH, but without a =
draft there was very little guidance.&nbsp; Indeed the minutes of last =
dispatch say:<br class=3D""></div><div style=3D"caret-color: rgb(0, 0, =
0); font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; font-family: Arial;" class=3D""><br class=3D""></div><pre =
style=3D"caret-color: rgb(0, 0, 0); font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; word-spacing: =
0px; -webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D"">Bron Gondwana: RFC3339 extension
* Javascript notation format is looking for a standard serialisation.

Harald Alvestrand:
* We should have done this in the 90s!  It was a mistake not to do it =
then.

Neil Jenkins:
* we do need a serialisation format

Where to discuss: calsify or tzdata lists, but probably calsify is =
best.<br class=3D""></pre><div style=3D"caret-color: rgb(0, 0, 0); =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; font-family: Arial;" class=3D""><br class=3D""></div><div =
style=3D"caret-color: rgb(0, 0, 0); font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Arial;" class=3D"">You can watch a =
video of the exact discussion here:<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://youtu.be/d871MoUgAKU?t=3D6418" =
class=3D"">https://youtu.be/d871MoUgAKU?t=3D6418</a><br =
class=3D""></div><div style=3D"caret-color: rgb(0, 0, 0); font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; font-family: =
Arial;" class=3D""><br class=3D""></div><div style=3D"caret-color: =
rgb(0, 0, 0); font-size: 16px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; font-family: Arial;" class=3D"">...<br class=3D""></div><div =
style=3D"caret-color: rgb(0, 0, 0); font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Arial;" class=3D""><br =
class=3D""></div><div style=3D"caret-color: rgb(0, 0, 0); font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; font-family: =
Arial;" class=3D"">Regardless, it appears that the right next venue for =
this document is DISPATCH at IETF110.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div>Yes, =
please. &nbsp;Not that I object to this being <b class=3D"">discussed</b> =
here prior to adoption, so long as the chairs don=E2=80=99t mind =
(that=E2=80=99s entirely your call and entirely <b =
class=3D"">not</b>&nbsp;mine).</div><div><br =
class=3D""></div><div>Eliot</div><div><br class=3D""></div><br =
class=3D""></body></html>=

--Apple-Mail=_DE373848-8E25-4D3B-9FA1-1963A5398336--

--Apple-Mail=_E31509B8-AD92-4BB1-95AA-0F68D60602C9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAmANbFUACgkQh7ZrRtnS
ejNOgwf9HdSMP4FThHPJcm4bnI4HcIiyYsyVRx8lir8+vaSGBXgKuABNzQZIaSsV
Gy/s8ErosHehYrYNn3CsOui/rEmcOpyrOPiF80L3K4uGutXAJtibMD/CKc/jEeee
MRvMd84vuAsg6o/6sZEUppu53lULb5OHH9/bEuEsou/MXGwC/JZVqBE/jyuIrMPt
QO97YgBJRvnkeo04dRSLpbYf0NYl0n2EU4hi1OybcVYA0nyS2WHoMMa6vJ59Z2t+
DcGdM2Ob5d8K2tFJBKZ5bPUfjl2zmKllzDTqoXbgYqPlYZzdb5DVbKMirLZX4Mu3
glWCGAOHuivwNSDTRS9nc5IzrneMlQ==
=bLUv
-----END PGP SIGNATURE-----

--Apple-Mail=_E31509B8-AD92-4BB1-95AA-0F68D60602C9--


From nobody Sun Jan 24 06:04:30 2021
Return-Path: <ned.freed@mrochek.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 934203A0C80 for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 06:04:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6CjKtya60MBi for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 06:04:27 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [98.153.82.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D5F83A0C7E for <calsify@ietf.org>; Sun, 24 Jan 2021 06:04:26 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RUQVLYB00W0095GI@mauve.mrochek.com> for calsify@ietf.org; Sun, 24 Jan 2021 05:59:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712;  t=1611496763; bh=sxiYA+D+7JFCx2iexpVWz91zGpB1MsyR6yvOVxlBQKc=;  h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=AVXVPwNy3PRRi3RyoBWGG4s2jLvEFtyXCJOz/8yn7I+Np4z0rCJAE9VCiwu92N1RG LfP6k/fFdNpNY9UQxe1A48V0QloTsRDBlkTJcECTehnLNSxIO+1N3J5OqqGRdsNeNX i1H3gFjA7eAHNhSutBR/wRsI29YrPpvdx4c2bIXA=
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RUAOXM63XS005PTU@mauve.mrochek.com>; Sun, 24 Jan 2021 05:59:20 -0800 (PST)
Cc: Bron Gondwana <brong@fastmailteam.com>, Ned Freed <ned.freed@mrochek.com>,  calsify@ietf.org
Message-id: <01RUQVLVFX6K005PTU@mauve.mrochek.com>
Date: Sun, 24 Jan 2021 05:55:38 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Sat, 23 Jan 2021 23:32:57 -0800 (PST)" <01RUQJ104Y3C005PTU@mauve.mrochek.com>
References: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com> <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com> <01RUQ0ZW4L3U005PTU@mauve.mrochek.com> <d17b75e7-9720-6bd3-dd23-349e8ceac4a3@gmail.com> <01RUQ4K8M1RQ005PTU@mauve.mrochek.com> <34839106-de11-41fe-96d6-33f95c30524d@dogfood.fastmail.com> <01RUQJ104Y3C005PTU@mauve.mrochek.com>
To: Ned Freed <ned.freed@mrochek.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/RlJahMrfgcsiUYSZNoizlNSwLWA>
Subject: Re: [calsify] Fwd: New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jan 2021 14:04:29 -0000

Of course the other way to solve all of these problems is to leave RFC 3339 and
ISO 8601 alone, and instead specify a new format that incorporates RFC 3339  as
a component, the same way you're incorporating time zone rule names, calendar
names, and on.

Then implementors can choose on a case by case basis which format best
meets their needs.

Almost all of the issues here revolve around the fact that you're updating
an existing format.

				Ned




> > Ned,

> > Would your concern here be resolved by having this draft define a "point in
> > time" profile which was RFC3339 minus the 2-digit-year option, and a "full
> > date" profile which includes all the rest of the details - such that logging
> > software could be defined to use the "point in time" profile.

> Maybe. I don't have any objection to deprecating features of RFC 3339 that
> experience has shown we don't want or need.

> However, I don't think you've really made the case that the full date stuff is
> best addressed by packing all kinds of stuff in a single field value. It's not
> like JSON, XML, and so on have no mechanism for specifying a group of related
> values. As such, I question the need to define an additional syntax to do this,
> one that's considerably less flexible.

> There's also the issue of what constraints are applied to the additional stuff.
> The obvious one is that it MUST NOT be allowed to move the point in time
> of the timestamp around - I don't see this stated anywhere.

> > I'm really keen for there to be an RFC which can be referenced by both new
> > calendaring drafts and by other IETF documents, which is developed by this
> > group of people who are already involved in both the ISO work (via Ronald and
> > CalConnect) and the ECMA standardisation effort.

> > Generality has real costs, but so does excess simplicity - if there's not a
> > standard way to describe things that people really need, then they all develop
> > their own extensions.

> Actualy, it's this draft that engages in excess simplicity - the simplicity,
> for example, of assuming that it never makes sense to associate more than
> one set of time zone rules with a timestamp.

> And there's no missing standard here. We have no shortage of standardized
> grouping syntaxes.

> > This effort is to capture the extensions that have been needed in the real
> > world already, and standardise them to encourage everyone to extend the same
> > way!

> I'm a very long way from being convinced of this.

> 				Ned

> > Cheers,

> > Bron.

> > On Sun, Jan 24, 2021, at 11:00, Ned Freed wrote:
> > >
> > > > On 1/23/21 18:17, Ned Freed wrote:
> > > > > Generality has real costs. To name the obvious example, I don't want to
> > > > > *ever* see a timezone rule in a log file timestamp, or a field in an
> > > > > email message.
> > >
> > > > I have had a number of conversations with people tasked with auditing
> > > > log records bemoaning the lack of a timezone id in logs. Without the id
> > > > how do we know how an offset or UTC date was calculated?
> > >
> > > The purpose of a time value in the sorts of logs I'm talking about is to
> > > accurately describe the moment in time when something happened. Nothing more,
> > > nothing less. The RFC 3339/ISO 8601 format gives you this along with the
> > > ability to specify the value as an offset from GMT.
> > >
> > > If you really want more information along the lines of what this draft
> > > provides, like what timezone rules were in effect somewhere or what calendar it
> > > should be "projected to" (to use the draft's terminology), then by all
> > > means include that in a separate field in the log.
> > >
> > > With computers increasingly going back to being shared resources in some random
> > > data center some place other than anyone involved in generating the log entry,
> > > figuring out the right "somewhere" is a highly nontrivial problem. This
> > > is  true even for time zone offsets, and the further you go the harder it gets.
> > > (Of course this doesn't stop people from using offsets in their logs even when
> > > they have nothing to do with anything other than the location of some random
> > > piece of hardware.)
> > >
> > > And of course there can be multiple somewheres, which means these values need
> > > to have additional semantics attached in order to be interpreted properly.
> > >
> > > All of which argues strongly for not combining what are in fact separate
> > > pieces of information.
> > >
> > > Given all this, my advice to your auditor pals is, "Be careful what you wish
> > > for, because you're likely to end up with useless garbage."
> > >
> > > There's also very strong trend in the logging world to try and avoid complex
> > > field values because they hugely complicate aggregation, searching and sorting
> > > operations. In this world the use of RFC 3339 may be profiled to GMT only, or
> > > replaced entirely by a UNIX epoch or milliepoch values.
> > >
> > > > it's simply an offset showing what's considered to be local time.
> > >
> > > ? Offsets are a standard part of ISO 8601/RFC 3339.
> > >
> > > > Accurately recording the date/time that an event occurred is as
> > > > important for logging as it is for future events.
> > >
> > > ?? None of this has anything to do with accuracy. If you're not putting
> > > in the correct offset for your time values you're doing it wrong.
> > >
> > > > {and I don't think we're talking about rules - just ids]
> > >
> > > ??? We most certainly are talking about rules. If you think otherwise you
> > > need to reread the draft.
> > >
> > > Ned
> > >
> > > _______________________________________________
> > > calsify mailing list
> > > calsify@ietf.org
> > > https://www.ietf.org/mailman/listinfo/calsify
> > >

> > --
> >   Bron Gondwana, CEO, Fastmail Pty Ltd
> >   brong@fastmailteam.com



> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify


From nobody Sun Jan 24 06:29:35 2021
Return-Path: <ned.freed@mrochek.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 332CD3A0CF9 for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 06:29:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oIQPrtwQkIJ0 for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 06:29:31 -0800 (PST)
Received: from plum.mrochek.com (plum.mrochek.com [172.95.64.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1B583A0CF5 for <calsify@ietf.org>; Sun, 24 Jan 2021 06:29:31 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RUQWHWFC2O005JTD@mauve.mrochek.com> for calsify@ietf.org; Sun, 24 Jan 2021 06:24:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712;  t=1611498262; bh=2PVtmpge/dPJjK8LHrFJNphczeIZqOGPKJZiHmRgj2g=;  h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=QRaL6dBzYP/hiLUGRCfHvIg+jf0no2v8VaRk8UbNYtL6PidEofuszi8cvFjI10aGK 1qF4+aRrerjxrUkC4dfkPaV+KZZnnPicfES+dLjAI6INbGUWuhw1VEfHP3V9+NYFPW KlIOqei36PLWz+oteSbzC1lW51DfLJNui0hpOv+Q=
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RUAOXM63XS005PTU@mauve.mrochek.com>; Sun, 24 Jan 2021 06:24:18 -0800 (PST)
Cc: Ned Freed <ned.freed@mrochek.com>, calsify@ietf.org, Ujjwal Sharma <ryzokuken@igalia.com>
Message-id: <01RUQWHT375M005PTU@mauve.mrochek.com>
Date: Sun, 24 Jan 2021 06:00:04 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Sun, 24 Jan 2021 19:36:46 +1100" <da7c1ee0-a8cc-4310-81ac-4d9b8afb672d@dogfood.fastmail.com>
References: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com> <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com> <01RUQ0ZW4L3U005PTU@mauve.mrochek.com> <d17b75e7-9720-6bd3-dd23-349e8ceac4a3@gmail.com> <01RUQ4K8M1RQ005PTU@mauve.mrochek.com> <34839106-de11-41fe-96d6-33f95c30524d@dogfood.fastmail.com> <01RUQJ104Y3C005PTU@mauve.mrochek.com> <da7c1ee0-a8cc-4310-81ac-4d9b8afb672d@dogfood.fastmail.com>
To: Bron Gondwana <brong@fastmailteam.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/F2lKg_yHhFd6cduVRhsAoLddgk0>
Subject: Re: [calsify] Fwd: New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jan 2021 14:29:33 -0000

> On Sun, Jan 24, 2021, at 18:32, Ned Freed wrote:
> > However, I don't think you've really made the case that the full date stuff is
> > best addressed by packing all kinds of stuff in a single field value. It's not
> > like JSON, XML, and so on have no mechanism for specifying a group of related
> > values. As such, I question the need to define an additional syntax to do this,
> > one that's considerably less flexible.

> This idea has been "reinvented" more than once, which suggests that there is
> demand for it.

No, what it demonstrates is that there is demand for a way to combine a set of
pieces into a composite. It doesn't demonstate any need to revise the format we
use for specifying a point in time in a readable form, nor does it make the
case that a new syntax is needed.

> > There's also the issue of what constraints are applied to the additional stuff.
> > The obvious one is that it MUST NOT be allowed to move the point in time
> > of the timestamp around - I don't see this stated anywhere.

> For sure you would then need to have both a [+-] and a zone name.  That's an
> interesting idea, and it does raise the question of what you do if the zone and
> the fixed offset no longer match by the time you process the date (or indeed,
> are incorrect immediately).  If the time is a floating value (no Z and no [+-])
> then the point in time is also floating.

Well, now we have a problem, because now you have a situation where you have to
understand the meaning of all the pieces in order to be sure you know what time
is being specified. (Saying "this needs further adjustment in some way" is very
different than saying "display the value using this type of calendar".)

This essentially makes the format non-extensible unless you include some sort
of "mandatory/optional" label, never mind what the specification says about
extensibiity.

> > > I'm really keen for there to be an RFC which can be referenced by both new
> > > calendaring drafts and by other IETF documents, which is developed by this
> > > group of people who are already involved in both the ISO work (via Ronald and
> > > CalConnect) and the ECMA standardisation effort.

> > > Generality has real costs, but so does excess simplicity - if there's not a
> > > standard way to describe things that people really need, then they all develop
> > > their own extensions.

> > Actualy, it's this draft that engages in excess simplicity - the simplicity,
> > for example, of assuming that it never makes sense to associate more than
> > one set of time zone rules with a timestamp.
> >
> > And there's no missing standard here. We have no shortage of standardized
> > grouping syntaxes.

> The initial justification for this was very much "this is true but said
> grouping syntaxes don't tend to survived round trips through different systems
> very well, so we want to capture all the important details in a serialised
> form".

Really? JSON and XML don't survive round trips through different systems? 

If you have found this to be the case, you are operating in a different
universe than the one I occupy. Mind you, there's no shortage of problems with
JSON, XML, and ASN.1 for sure (and probably CBOR, although I lack experience in
that area), but I don't tnink surviving transport is one of them. (Well, OK,
the fact that JSON has to be treated as binary is sometimes missed, but this is
a generic JSON issue.)

That said, I think you're talking about semantics, not syntax, here. People
uncover a need to specify the timezone rules or display calendar or whatever
and the base format doesn't support that, and rather than agree on a single
mechanism for grouping this stuff they have instead extended the base
format in different and incompatible ways.

This ia valid argument for standardizing a grouping mechanism. But again, it
falls far, far short of making the case for revising or extending the time
stamp format. That's a different layer.

> > > This effort is to capture the extensions that have been needed in the real
> > > world already, and standardise them to encourage everyone to extend the same
> > > way!
> >
> > I'm a very long way from being convinced of this.

> I do have one more question (I'm going to do a call for adoption anyway, but
> I'll take this email thread as a voice against adoption from you unless I hear
> otherwise)...

> Would you be happy if this was either "extends RFC3339" or an entirely
> separate piece of work that's "only for calendaring systems" - or do you object
> to the entire principle of doing any work in this space at all?

Having this be a separate piece of work that uses RFC 3339 as a component
rather than obsoleting or extening it removes my objection to pursuing the
work. Of course the result still needs to interoperate, and this conversation
has convinced me that there's work to do in that regard.

				Ned


From nobody Sun Jan 24 15:15:31 2021
Return-Path: <brong@fastmailteam.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4F8E3A0CF5 for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 15:15:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level: 
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=Lh37VHQV; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=GlYij4eZ
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4X9jA5vB9QCB for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 15:15:27 -0800 (PST)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37C913A0CF4 for <calsify@ietf.org>; Sun, 24 Jan 2021 15:15:27 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 944B371C; Sun, 24 Jan 2021 18:15:24 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Sun, 24 Jan 2021 18:15:24 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:cc:subject:content-type; s=fm1; bh=iaOD k7BwKz6YacQSAVWYGJBl8DHPPNj3FuaHRciGxQs=; b=Lh37VHQVMwXxoNI3mgIS Gtwp7yWDmCbWYgS6OaXb3exPEUIlFpZzve+8a6dP28LFwUAxP2+zotUEN+B/zu/f I94q+iTOo04tM+jlrDh98pyGMmYYMsCMtQpPCnBCQnJCw6oHwKv73FvBEaPiVsz3 YCv1eMMH1Dcyo/sue9k15WyYInb8UqoCVDmGDXzz8q8dU22IE0mjaTEDv+jOymcR quia4KWYafPv61d1AoSzE5Qq0QEdQYwrbAxnhcU6jS9jXkX89NPAhfvYxypZLsMa 8NPj7YfeWzenpmOS0zJtWkuYVnQ9jBmxJ3BhPW4wfS1hg8Bk7D7FL81Rk7FaFPOY ZQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=iaODk7 BwKz6YacQSAVWYGJBl8DHPPNj3FuaHRciGxQs=; b=GlYij4eZB6DInjl6vw6Umy HAVemU2oIEh9Vfl++kB2OiOnIFjt3A5y/HVUO0tDQZY2/WF17x6/YLCOeKHBLMgv wDqtWxMlZOE3KKDqGM1I3SOSwVRX2kTKnKwK5qX6fgcQLFmNrqwihdrHnOE4Glwu L4feplAw6QYndpJBSiXuPqhP30Nk8losu/GJ1bgxJlFuAEnxKjDFGPJ5H71dijdP ZThtSCgxLW52qqeTImmMKa+tOz6UKC4Jv0tD8slSmisgx9+LXTB9hAxPfZECCDYr 9A2oPI+W2mh2fXXt8xIUocHb77tPlI/GSDMWxapDGMd1cnORF/cUaFiGd/GPjHpw ==
X-ME-Sender: <xms:i_8NYOQLsJ5s4UAHbuWPKgPfPR5ISATmxxxJMyXeP3Ob-sQ4EkbZuA> <xme:i_8NYDwEyrGD3jDXL6_fMb2jqpOpVHykefwxGRPKACtTWN4XBIxfgs41VeZstW7O3 hRw4Kz9uuA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddvgddtjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerredtnecuhfhrohhmpedfuehrohhn ucfiohhnugifrghnrgdfuceosghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucggtffrrghtthgvrhhnpeffveefiefgjeevteehheelgeetleetveeguedthfehgffh tdejhfdvhefhtdekgfenucffohhmrghinhepihgvthhfrdhorhhgnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgr ihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:i_8NYL0NghnWd9pwRUT1wL_kSMJ4DQoT8eLi5GE6TTGbieUJwiauxA> <xmx:i_8NYKAT14lwhFmxu8TzDj6Gdx7yx6yfp3LnqV9s5AOxTrsAMGB96A> <xmx:i_8NYHjf-P9bKfqYpsIlVRgtjCBajiUZL8hWRxdgvZkPGBNPADUCdw> <xmx:jP8NYJcCHLQtqf6Y7k4FgEyzc9FGHtcHLvbKvIZGuaB-9bZt6eh7mg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id C0CE1360068; Sun, 24 Jan 2021 18:15:23 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-78-g36b56e88ef-fm-20210120.001-g36b56e88
Mime-Version: 1.0
Message-Id: <8f821d46-6cbd-4a11-8098-1d9bb3ac28e7@beta.fastmail.com>
In-Reply-To: <01RUQVLVFX6K005PTU@mauve.mrochek.com>
References: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com> <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com> <01RUQ0ZW4L3U005PTU@mauve.mrochek.com> <d17b75e7-9720-6bd3-dd23-349e8ceac4a3@gmail.com> <01RUQ4K8M1RQ005PTU@mauve.mrochek.com> <34839106-de11-41fe-96d6-33f95c30524d@dogfood.fastmail.com> <01RUQJ104Y3C005PTU@mauve.mrochek.com> <01RUQVLVFX6K005PTU@mauve.mrochek.com>
Date: Mon, 25 Jan 2021 10:15:02 +1100
From: "Bron Gondwana" <brong@fastmailteam.com>
To: "Ned Freed" <ned.freed@mrochek.com>
Cc: calsify@ietf.org
Content-Type: multipart/alternative; boundary=20ac3763972743ecb075252cc5137e73
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/1GoNSpcQkzp6m8_rA7ICbqbMAV0>
Subject: Re: [calsify] Fwd: New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jan 2021 23:15:30 -0000

--20ac3763972743ecb075252cc5137e73
Content-Type: text/plain

ISO8601 had a major update in 2019, due to there being demand to be able to represent additional types of date information.

But this does sound like everyone would be a lot happier with a small update to 3339 to remove 2 digit years, allow 6 digits years, and otherwise leave pretty well enough alone - and then define a new format for everything else.  I expect that would be acceptable.

Cheers,

Bron.

On Mon, Jan 25, 2021, at 00:55, Ned Freed wrote:
> Of course the other way to solve all of these problems is to leave RFC 3339 and
> ISO 8601 alone, and instead specify a new format that incorporates RFC 3339  as
> a component, the same way you're incorporating time zone rule names, calendar
> names, and on.
> 
> Then implementors can choose on a case by case basis which format best
> meets their needs.
> 
> Almost all of the issues here revolve around the fact that you're updating
> an existing format.
> 
> Ned
> 
> 
> 
> 
> > > Ned,
> 
> > > Would your concern here be resolved by having this draft define a "point in
> > > time" profile which was RFC3339 minus the 2-digit-year option, and a "full
> > > date" profile which includes all the rest of the details - such that logging
> > > software could be defined to use the "point in time" profile.
> 
> > Maybe. I don't have any objection to deprecating features of RFC 3339 that
> > experience has shown we don't want or need.
> 
> > However, I don't think you've really made the case that the full date stuff is
> > best addressed by packing all kinds of stuff in a single field value. It's not
> > like JSON, XML, and so on have no mechanism for specifying a group of related
> > values. As such, I question the need to define an additional syntax to do this,
> > one that's considerably less flexible.
> 
> > There's also the issue of what constraints are applied to the additional stuff.
> > The obvious one is that it MUST NOT be allowed to move the point in time
> > of the timestamp around - I don't see this stated anywhere.
> 
> > > I'm really keen for there to be an RFC which can be referenced by both new
> > > calendaring drafts and by other IETF documents, which is developed by this
> > > group of people who are already involved in both the ISO work (via Ronald and
> > > CalConnect) and the ECMA standardisation effort.
> 
> > > Generality has real costs, but so does excess simplicity - if there's not a
> > > standard way to describe things that people really need, then they all develop
> > > their own extensions.
> 
> > Actualy, it's this draft that engages in excess simplicity - the simplicity,
> > for example, of assuming that it never makes sense to associate more than
> > one set of time zone rules with a timestamp.
> 
> > And there's no missing standard here. We have no shortage of standardized
> > grouping syntaxes.
> 
> > > This effort is to capture the extensions that have been needed in the real
> > > world already, and standardise them to encourage everyone to extend the same
> > > way!
> 
> > I'm a very long way from being convinced of this.
> 
> > Ned
> 
> > > Cheers,
> 
> > > Bron.
> 
> > > On Sun, Jan 24, 2021, at 11:00, Ned Freed wrote:
> > > >
> > > > > On 1/23/21 18:17, Ned Freed wrote:
> > > > > > Generality has real costs. To name the obvious example, I don't want to
> > > > > > *ever* see a timezone rule in a log file timestamp, or a field in an
> > > > > > email message.
> > > >
> > > > > I have had a number of conversations with people tasked with auditing
> > > > > log records bemoaning the lack of a timezone id in logs. Without the id
> > > > > how do we know how an offset or UTC date was calculated?
> > > >
> > > > The purpose of a time value in the sorts of logs I'm talking about is to
> > > > accurately describe the moment in time when something happened. Nothing more,
> > > > nothing less. The RFC 3339/ISO 8601 format gives you this along with the
> > > > ability to specify the value as an offset from GMT.
> > > >
> > > > If you really want more information along the lines of what this draft
> > > > provides, like what timezone rules were in effect somewhere or what calendar it
> > > > should be "projected to" (to use the draft's terminology), then by all
> > > > means include that in a separate field in the log.
> > > >
> > > > With computers increasingly going back to being shared resources in some random
> > > > data center some place other than anyone involved in generating the log entry,
> > > > figuring out the right "somewhere" is a highly nontrivial problem. This
> > > > is  true even for time zone offsets, and the further you go the harder it gets.
> > > > (Of course this doesn't stop people from using offsets in their logs even when
> > > > they have nothing to do with anything other than the location of some random
> > > > piece of hardware.)
> > > >
> > > > And of course there can be multiple somewheres, which means these values need
> > > > to have additional semantics attached in order to be interpreted properly.
> > > >
> > > > All of which argues strongly for not combining what are in fact separate
> > > > pieces of information.
> > > >
> > > > Given all this, my advice to your auditor pals is, "Be careful what you wish
> > > > for, because you're likely to end up with useless garbage."
> > > >
> > > > There's also very strong trend in the logging world to try and avoid complex
> > > > field values because they hugely complicate aggregation, searching and sorting
> > > > operations. In this world the use of RFC 3339 may be profiled to GMT only, or
> > > > replaced entirely by a UNIX epoch or milliepoch values.
> > > >
> > > > > it's simply an offset showing what's considered to be local time.
> > > >
> > > > ? Offsets are a standard part of ISO 8601/RFC 3339.
> > > >
> > > > > Accurately recording the date/time that an event occurred is as
> > > > > important for logging as it is for future events.
> > > >
> > > > ?? None of this has anything to do with accuracy. If you're not putting
> > > > in the correct offset for your time values you're doing it wrong.
> > > >
> > > > > {and I don't think we're talking about rules - just ids]
> > > >
> > > > ??? We most certainly are talking about rules. If you think otherwise you
> > > > need to reread the draft.
> > > >
> > > > Ned
> > > >
> > > > _______________________________________________
> > > > calsify mailing list
> > > > calsify@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/calsify
> > > >
> 
> > > --
> > >   Bron Gondwana, CEO, Fastmail Pty Ltd
> > >   brong@fastmailteam.com
> 
> 
> 
> > _______________________________________________
> > calsify mailing list
> > calsify@ietf.org
> > https://www.ietf.org/mailman/listinfo/calsify
> 

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com


--20ac3763972743ecb075252cc5137e73
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div style=3D"f=
ont-family:Arial;">ISO8601 had a major update in 2019, due to there bein=
g demand to be able to represent additional types of date information.<b=
r></div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-f=
amily:Arial;">But this does sound like everyone would be a lot happier w=
ith a small update to 3339 to remove 2 digit years, allow 6 digits years=
, and otherwise leave pretty well enough alone - and then define a new f=
ormat for everything else.&nbsp; I expect that would be acceptable.<br><=
/div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-fami=
ly:Arial;">Cheers,<br></div><div style=3D"font-family:Arial;"><br>Bron.<=
br></div><div style=3D"font-family:Arial;"><br></div><div>On Mon, Jan 25=
, 2021, at 00:55, Ned Freed wrote:<br></div><blockquote type=3D"cite" id=
=3D"qt" style=3D""><div style=3D"font-family:Arial;">Of course the other=
 way to solve all of these problems is to leave RFC 3339 and<br></div><d=
iv style=3D"font-family:Arial;">ISO 8601 alone, and instead specify a ne=
w format that incorporates RFC 3339&nbsp; as<br></div><div style=3D"font=
-family:Arial;">a component, the same way you're incorporating time zone=
 rule names, calendar<br></div><div style=3D"font-family:Arial;">names, =
and on.<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D=
"font-family:Arial;">Then implementors can choose on a case by case basi=
s which format best<br></div><div style=3D"font-family:Arial;">meets the=
ir needs.<br></div><div style=3D"font-family:Arial;"><br></div><div styl=
e=3D"font-family:Arial;">Almost all of the issues here revolve around th=
e fact that you're updating<br></div><div style=3D"font-family:Arial;">a=
n existing format.<br></div><div style=3D"font-family:Arial;"><br></div>=
<div style=3D"font-family:Arial;">Ned<br></div><div style=3D"font-family=
:Arial;"><br></div><div style=3D"font-family:Arial;"><br></div><div styl=
e=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;"><br=
></div><div style=3D"font-family:Arial;">&gt; &gt; Ned,<br></div><div st=
yle=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;">&=
gt; &gt; Would your concern here be resolved by having this draft define=
 a "point in<br></div><div style=3D"font-family:Arial;">&gt; &gt; time" =
profile which was RFC3339 minus the 2-digit-year option, and a "full<br>=
</div><div style=3D"font-family:Arial;">&gt; &gt; date" profile which in=
cludes all the rest of the details - such that logging<br></div><div sty=
le=3D"font-family:Arial;">&gt; &gt; software could be defined to use the=
 "point in time" profile.<br></div><div style=3D"font-family:Arial;"><br=
></div><div style=3D"font-family:Arial;">&gt; Maybe. I don't have any ob=
jection to deprecating features of RFC 3339 that<br></div><div style=3D"=
font-family:Arial;">&gt; experience has shown we don't want or need.<br>=
</div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-fam=
ily:Arial;">&gt; However, I don't think you've really made the case that=
 the full date stuff is<br></div><div style=3D"font-family:Arial;">&gt; =
best addressed by packing all kinds of stuff in a single field value. It=
's not<br></div><div style=3D"font-family:Arial;">&gt; like JSON, XML, a=
nd so on have no mechanism for specifying a group of related<br></div><d=
iv style=3D"font-family:Arial;">&gt; values. As such, I question the nee=
d to define an additional syntax to do this,<br></div><div style=3D"font=
-family:Arial;">&gt; one that's considerably less flexible.<br></div><di=
v style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial=
;">&gt; There's also the issue of what constraints are applied to the ad=
ditional stuff.<br></div><div style=3D"font-family:Arial;">&gt; The obvi=
ous one is that it MUST NOT be allowed to move the point in time<br></di=
v><div style=3D"font-family:Arial;">&gt; of the timestamp around - I don=
't see this stated anywhere.<br></div><div style=3D"font-family:Arial;">=
<br></div><div style=3D"font-family:Arial;">&gt; &gt; I'm really keen fo=
r there to be an RFC which can be referenced by both new<br></div><div s=
tyle=3D"font-family:Arial;">&gt; &gt; calendaring drafts and by other IE=
TF documents, which is developed by this<br></div><div style=3D"font-fam=
ily:Arial;">&gt; &gt; group of people who are already involved in both t=
he ISO work (via Ronald and<br></div><div style=3D"font-family:Arial;">&=
gt; &gt; CalConnect) and the ECMA standardisation effort.<br></div><div =
style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;"=
>&gt; &gt; Generality has real costs, but so does excess simplicity - if=
 there's not a<br></div><div style=3D"font-family:Arial;">&gt; &gt; stan=
dard way to describe things that people really need, then they all devel=
op<br></div><div style=3D"font-family:Arial;">&gt; &gt; their own extens=
ions.<br></div><div style=3D"font-family:Arial;"><br></div><div style=3D=
"font-family:Arial;">&gt; Actualy, it's this draft that engages in exces=
s simplicity - the simplicity,<br></div><div style=3D"font-family:Arial;=
">&gt; for example, of assuming that it never makes sense to associate m=
ore than<br></div><div style=3D"font-family:Arial;">&gt; one set of time=
 zone rules with a timestamp.<br></div><div style=3D"font-family:Arial;"=
><br></div><div style=3D"font-family:Arial;">&gt; And there's no missing=
 standard here. We have no shortage of standardized<br></div><div style=3D=
"font-family:Arial;">&gt; grouping syntaxes.<br></div><div style=3D"font=
-family:Arial;"><br></div><div style=3D"font-family:Arial;">&gt; &gt; Th=
is effort is to capture the extensions that have been needed in the real=
<br></div><div style=3D"font-family:Arial;">&gt; &gt; world already, and=
 standardise them to encourage everyone to extend the same<br></div><div=
 style=3D"font-family:Arial;">&gt; &gt; way!<br></div><div style=3D"font=
-family:Arial;"><br></div><div style=3D"font-family:Arial;">&gt; I'm a v=
ery long way from being convinced of this.<br></div><div style=3D"font-f=
amily:Arial;"><br></div><div style=3D"font-family:Arial;">&gt; 				Ned<b=
r></div><div style=3D"font-family:Arial;"><br></div><div style=3D"font-f=
amily:Arial;">&gt; &gt; Cheers,<br></div><div style=3D"font-family:Arial=
;"><br></div><div style=3D"font-family:Arial;">&gt; &gt; Bron.<br></div>=
<div style=3D"font-family:Arial;"><br></div><div style=3D"font-family:Ar=
ial;">&gt; &gt; On Sun, Jan 24, 2021, at 11:00, Ned Freed wrote:<br></di=
v><div style=3D"font-family:Arial;">&gt; &gt; &gt;<br></div><div style=3D=
"font-family:Arial;">&gt; &gt; &gt; &gt; On 1/23/21 18:17, Ned Freed wro=
te:<br></div><div style=3D"font-family:Arial;">&gt; &gt; &gt; &gt; &gt; =
Generality has real costs. To name the obvious example, I don't want to<=
br></div><div style=3D"font-family:Arial;">&gt; &gt; &gt; &gt; &gt; *eve=
r* see a timezone rule in a log file timestamp, or a field in an<br></di=
v><div style=3D"font-family:Arial;">&gt; &gt; &gt; &gt; &gt; email messa=
ge.<br></div><div style=3D"font-family:Arial;">&gt; &gt; &gt;<br></div><=
div style=3D"font-family:Arial;">&gt; &gt; &gt; &gt; I have had a number=
 of conversations with people tasked with auditing<br></div><div style=3D=
"font-family:Arial;">&gt; &gt; &gt; &gt; log records bemoaning the lack =
of a timezone id in logs. Without the id<br></div><div style=3D"font-fam=
ily:Arial;">&gt; &gt; &gt; &gt; how do we know how an offset or UTC date=
 was calculated?<br></div><div style=3D"font-family:Arial;">&gt; &gt; &g=
t;<br></div><div style=3D"font-family:Arial;">&gt; &gt; &gt; The purpose=
 of a time value in the sorts of logs I'm talking about is to<br></div><=
div style=3D"font-family:Arial;">&gt; &gt; &gt; accurately describe the =
moment in time when something happened. Nothing more,<br></div><div styl=
e=3D"font-family:Arial;">&gt; &gt; &gt; nothing less. The RFC 3339/ISO 8=
601 format gives you this along with the<br></div><div style=3D"font-fam=
ily:Arial;">&gt; &gt; &gt; ability to specify the value as an offset fro=
m GMT.<br></div><div style=3D"font-family:Arial;">&gt; &gt; &gt;<br></di=
v><div style=3D"font-family:Arial;">&gt; &gt; &gt; If you really want mo=
re information along the lines of what this draft<br></div><div style=3D=
"font-family:Arial;">&gt; &gt; &gt; provides, like what timezone rules w=
ere in effect somewhere or what calendar it<br></div><div style=3D"font-=
family:Arial;">&gt; &gt; &gt; should be "projected to" (to use the draft=
's terminology), then by all<br></div><div style=3D"font-family:Arial;">=
&gt; &gt; &gt; means include that in a separate field in the log.<br></d=
iv><div style=3D"font-family:Arial;">&gt; &gt; &gt;<br></div><div style=3D=
"font-family:Arial;">&gt; &gt; &gt; With computers increasingly going ba=
ck to being shared resources in some random<br></div><div style=3D"font-=
family:Arial;">&gt; &gt; &gt; data center some place other than anyone i=
nvolved in generating the log entry,<br></div><div style=3D"font-family:=
Arial;">&gt; &gt; &gt; figuring out the right "somewhere" is a highly no=
ntrivial problem. This<br></div><div style=3D"font-family:Arial;">&gt; &=
gt; &gt; is&nbsp; true even for time zone offsets, and the further you g=
o the harder it gets.<br></div><div style=3D"font-family:Arial;">&gt; &g=
t; &gt; (Of course this doesn't stop people from using offsets in their =
logs even when<br></div><div style=3D"font-family:Arial;">&gt; &gt; &gt;=
 they have nothing to do with anything other than the location of some r=
andom<br></div><div style=3D"font-family:Arial;">&gt; &gt; &gt; piece of=
 hardware.)<br></div><div style=3D"font-family:Arial;">&gt; &gt; &gt;<br=
></div><div style=3D"font-family:Arial;">&gt; &gt; &gt; And of course th=
ere can be multiple somewheres, which means these values need<br></div><=
div style=3D"font-family:Arial;">&gt; &gt; &gt; to have additional seman=
tics attached in order to be interpreted properly.<br></div><div style=3D=
"font-family:Arial;">&gt; &gt; &gt;<br></div><div style=3D"font-family:A=
rial;">&gt; &gt; &gt; All of which argues strongly for not combining wha=
t are in fact separate<br></div><div style=3D"font-family:Arial;">&gt; &=
gt; &gt; pieces of information.<br></div><div style=3D"font-family:Arial=
;">&gt; &gt; &gt;<br></div><div style=3D"font-family:Arial;">&gt; &gt; &=
gt; Given all this, my advice to your auditor pals is, "Be careful what =
you wish<br></div><div style=3D"font-family:Arial;">&gt; &gt; &gt; for, =
because you're likely to end up with useless garbage."<br></div><div sty=
le=3D"font-family:Arial;">&gt; &gt; &gt;<br></div><div style=3D"font-fam=
ily:Arial;">&gt; &gt; &gt; There's also very strong trend in the logging=
 world to try and avoid complex<br></div><div style=3D"font-family:Arial=
;">&gt; &gt; &gt; field values because they hugely complicate aggregatio=
n, searching and sorting<br></div><div style=3D"font-family:Arial;">&gt;=
 &gt; &gt; operations. In this world the use of RFC 3339 may be profiled=
 to GMT only, or<br></div><div style=3D"font-family:Arial;">&gt; &gt; &g=
t; replaced entirely by a UNIX epoch or milliepoch values.<br></div><div=
 style=3D"font-family:Arial;">&gt; &gt; &gt;<br></div><div style=3D"font=
-family:Arial;">&gt; &gt; &gt; &gt; it's simply an offset showing what's=
 considered to be local time.<br></div><div style=3D"font-family:Arial;"=
>&gt; &gt; &gt;<br></div><div style=3D"font-family:Arial;">&gt; &gt; &gt=
; ? Offsets are a standard part of ISO 8601/RFC 3339.<br></div><div styl=
e=3D"font-family:Arial;">&gt; &gt; &gt;<br></div><div style=3D"font-fami=
ly:Arial;">&gt; &gt; &gt; &gt; Accurately recording the date/time that a=
n event occurred is as<br></div><div style=3D"font-family:Arial;">&gt; &=
gt; &gt; &gt; important for logging as it is for future events.<br></div=
><div style=3D"font-family:Arial;">&gt; &gt; &gt;<br></div><div style=3D=
"font-family:Arial;">&gt; &gt; &gt; ?? None of this has anything to do w=
ith accuracy. If you're not putting<br></div><div style=3D"font-family:A=
rial;">&gt; &gt; &gt; in the correct offset for your time values you're =
doing it wrong.<br></div><div style=3D"font-family:Arial;">&gt; &gt; &gt=
;<br></div><div style=3D"font-family:Arial;">&gt; &gt; &gt; &gt; {and I =
don't think we're talking about rules - just ids]<br></div><div style=3D=
"font-family:Arial;">&gt; &gt; &gt;<br></div><div style=3D"font-family:A=
rial;">&gt; &gt; &gt; ??? We most certainly are talking about rules. If =
you think otherwise you<br></div><div style=3D"font-family:Arial;">&gt; =
&gt; &gt; need to reread the draft.<br></div><div style=3D"font-family:A=
rial;">&gt; &gt; &gt;<br></div><div style=3D"font-family:Arial;">&gt; &g=
t; &gt; Ned<br></div><div style=3D"font-family:Arial;">&gt; &gt; &gt;<br=
></div><div style=3D"font-family:Arial;">&gt; &gt; &gt; ________________=
_______________________________<br></div><div style=3D"font-family:Arial=
;">&gt; &gt; &gt; calsify mailing list<br></div><div style=3D"font-famil=
y:Arial;">&gt; &gt; &gt;&nbsp;<a href=3D"mailto:calsify@ietf.org">calsif=
y@ietf.org</a><br></div><div style=3D"font-family:Arial;">&gt; &gt; &gt;=
&nbsp;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify">https://=
www.ietf.org/mailman/listinfo/calsify</a><br></div><div style=3D"font-fa=
mily:Arial;">&gt; &gt; &gt;<br></div><div style=3D"font-family:Arial;"><=
br></div><div style=3D"font-family:Arial;">&gt; &gt; --<br></div><div st=
yle=3D"font-family:Arial;">&gt; &gt;&nbsp;&nbsp; Bron Gondwana, CEO, Fas=
tmail Pty Ltd<br></div><div style=3D"font-family:Arial;">&gt; &gt;&nbsp;=
&nbsp;&nbsp;<a href=3D"mailto:brong@fastmailteam.com">brong@fastmailteam=
.com</a><br></div><div style=3D"font-family:Arial;"><br></div><div style=
=3D"font-family:Arial;"><br></div><div style=3D"font-family:Arial;"><br>=
</div><div style=3D"font-family:Arial;">&gt; ___________________________=
____________________<br></div><div style=3D"font-family:Arial;">&gt; cal=
sify mailing list<br></div><div style=3D"font-family:Arial;">&gt;&nbsp;<=
a href=3D"mailto:calsify@ietf.org">calsify@ietf.org</a><br></div><div st=
yle=3D"font-family:Arial;">&gt;&nbsp;<a href=3D"https://www.ietf.org/mai=
lman/listinfo/calsify">https://www.ietf.org/mailman/listinfo/calsify</a>=
<br></div><div style=3D"font-family:Arial;"><br></div></blockquote><div =
style=3D"font-family:Arial;"><br></div><div id=3D"sig56629417"><div clas=
s=3D"signature">--<br></div><div class=3D"signature">&nbsp; Bron Gondwan=
a, CEO, Fastmail Pty Ltd<br></div><div class=3D"signature">&nbsp; brong@=
fastmailteam.com<br></div><div class=3D"signature"><br></div></div><div =
style=3D"font-family:Arial;"><br></div></body></html>
--20ac3763972743ecb075252cc5137e73--


From nobody Sun Jan 24 17:18:51 2021
Return-Path: <neilj@fastmailteam.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96DCF3A0ABE for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 17:18:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level: 
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=KEEYMHdO; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=gNH/jXNy
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CgS_4DSduiDR for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 17:18:49 -0800 (PST)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 443573A0ABB for <calsify@ietf.org>; Sun, 24 Jan 2021 17:18:49 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 390FD6BB for <calsify@ietf.org>; Sun, 24 Jan 2021 20:18:48 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute3.internal (MEProxy); Sun, 24 Jan 2021 20:18:48 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm1; bh=nvHhMRJ crCMAwCnCRDeIfnn+0ztqvAoDc0/VQ3vo/Ek=; b=KEEYMHdOIcHT9n34Y+jtgX4 dv0IDj+p9uU3ZsFx3t9x1HKnB4CgfL0esdJF+49kenQ4GcPXSvBZ0VgmnKbwvjj7 3CWvHXHXoONEEdMhvgLh8n1aPSjRET2nym1GX+QCv59QmNow4iIXH7Y9cDAZIGGD TjSU+xVinEaGnGHp9ZBfpCu+BptVo2Svaz0i/T6bdg3O+FmE0BAtMkZ2kyLYLqcD vNnsIMRNddMVMnivhrk9B6fvSRa6dVBcALAIi8/oQyxtAvm45k1MxW3MmT38X70c V5ljLWy5y+MoZM/E5t699/Nn/tLQc/cGyDYG1fCb+G3lfEAuJIs/dbUS1YqdC0A= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=nvHhMR JcrCMAwCnCRDeIfnn+0ztqvAoDc0/VQ3vo/Ek=; b=gNH/jXNyFbXMezS9ipgB4M fJwoqxBorCJDS0TK2zhBpAnEsQRaYsipFqL6cud2VLSntqD4Yym2J5ULxfJL0QPR pBtU9O0sFirf0dpIwRpozvMlBkQpkGbHuMTO0JtY9vMpUSg9+gO8HbjMZu8FiZJf 0Y2cVqHabPMQWf0AnLyhm5k/5FnpwVaWJea6d7shav/pMlUoCu3VKkm9BNeYH22j ATwLVs+GawveGT0BBCpEPMZsJ84NAjcUZkJtzCyDA95nLdbXsk3nWFsRvf90gLSS lGgFxvDWsd1+yeAxKYpfi0j6O9bj4fv3IcHTSNMouFeKO7b0wDIm8EAVTs8Ggs0A ==
X-ME-Sender: <xms:dxwOYOxCkSZp7S0Vak2XB5XGFYaTbwUwlxKBSi_vWcJ6qezH1Nrc1w> <xme:dxwOYKSif4-TlN2u9miA-Wm3Wcl1jevP_0jft-LMTz7hx_uvT_wByLyUfIuaqBv4z xcwXd9gBsaG-g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddvgdefvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreertdenucfhrhhomhepfdfpvghilhculfgvnhhkihhnshdfuceonhgvihhljhesfhgr shhtmhgrihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpeevvdetvdduleekhf eghfetfeettdelhfehfeevffevleekuddtudffieevjeevhfenucevlhhushhtvghrufhi iigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehnvghilhhjsehfrghsthhmrghilh htvggrmhdrtghomh
X-ME-Proxy: <xmx:dxwOYAXwB-SLHn_PP4Rt8m6qSEEokQlNHlPKgay9V_8ddnAnmc_-Ug> <xmx:dxwOYEgchRjHefF5tKi3lkyW5G7ispnQEDQixNlwvQkIvIJAjmccrA> <xmx:dxwOYAB_ucaF9rYuSRN3BHEjK-pmsNooSRtGAcnHJB6O6KxTKGZEEA> <xmx:dxwOYDOftv0jIm0aHFGIAqwo5NISwsge69ZdQSvvA4bNS7Gu2jn53w>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 6518D360068; Sun, 24 Jan 2021 20:18:47 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-78-g36b56e88ef-fm-20210120.001-g36b56e88
Mime-Version: 1.0
Message-Id: <3288fdaf-28a9-45a9-bf50-c9de9e2c3486@dogfood.fastmail.com>
In-Reply-To: <8f821d46-6cbd-4a11-8098-1d9bb3ac28e7@beta.fastmail.com>
References: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com> <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com> <01RUQ0ZW4L3U005PTU@mauve.mrochek.com> <d17b75e7-9720-6bd3-dd23-349e8ceac4a3@gmail.com> <01RUQ4K8M1RQ005PTU@mauve.mrochek.com> <34839106-de11-41fe-96d6-33f95c30524d@dogfood.fastmail.com> <01RUQJ104Y3C005PTU@mauve.mrochek.com> <01RUQVLVFX6K005PTU@mauve.mrochek.com> <8f821d46-6cbd-4a11-8098-1d9bb3ac28e7@beta.fastmail.com>
Date: Mon, 25 Jan 2021 12:18:28 +1100
From: "Neil Jenkins" <neilj@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary=3a9ea51913e54d9894de3af3c29aac8f
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/4C-5stY41-djwC7WzkYFhqEYJW8>
Subject: Re: [calsify] Fwd: New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2021 01:18:51 -0000

--3a9ea51913e54d9894de3af3c29aac8f
Content-Type: text/plain

I think the disagreement here stems from two viewpoints on what RFC3339 is. Ned is looking at it from the viewpoint that it defines a format for (log) timestamps only. The other side is viewing it as simply a standard serialisation format for dates in internet protocols without restriction on use case.

Having looked at the document's introduction again, Ned is technically correct:

   There are many ways in which date and time values might appear in
   Internet protocols:  this document focuses on just one common usage,
   viz. timestamps for Internet protocol events

However, I would assert that in my experience, many view RFC3339 as just a standardised serialisation format for all dates in contexts that go beyond this. I think there is a clear demand for a serialisation format that *can* incorporate a time zone or calendar identifier, and standardising this within the IETF is more likely to lead to interoperability. I also agree that you would never want to use such a time-zone variant in log files. 

So I think it comes down to two options:
 * A single RFC that replaces 3339 containing all the variants. The benefit is you have one place to reference for how to serialise a date-time.
 * A new adjunct RFC for how to serialise date-times with IANA time zones, or without an absolute time at all (local "wall clock" date-times). This would not overlap 3339, which would continue to define how to serialise UTC and fixed-offset date-times.
I am not too fussed which of these paths we go down.  I was originally advocating for the first option, but looking at it again, I can see good arguments for the second instead.

Neil.
--3a9ea51913e54d9894de3af3c29aac8f
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>I think th=
e disagreement here stems from two viewpoints on what RFC3339 is. Ned is=
 looking at it from the viewpoint that it defines a format for (log) tim=
estamps only. The other side is viewing it as simply a standard serialis=
ation format for dates in internet protocols without restriction on use =
case.<br></div><div><br></div><div>Having looked at the document's intro=
duction again, Ned is technically correct:<br></div><div><br></div><pre =
style=3D"border-top-color:rgb(204, 204, 204);border-top-style:solid;bord=
er-top-width:1px;border-right-color:rgb(204, 204, 204);border-right-styl=
e:solid;border-right-width:1px;border-bottom-color:rgb(204, 204, 204);bo=
rder-bottom-style:solid;border-bottom-width:1px;border-left-color:rgb(20=
4, 204, 204);border-left-style:solid;border-left-width:1px;border-image-=
outset:0;border-image-repeat:stretch;border-image-slice:100%;border-imag=
e-source:none;border-image-width:1;border-top-left-radius:3px;border-top=
-right-radius:3px;border-bottom-right-radius:3px;border-bottom-left-radi=
us:3px;background-color:rgb(246, 246, 246);background-position-x:0%;back=
ground-position-y:0%;background-repeat:repeat;background-attachment:scro=
ll;background-image:none;background-size:auto;background-origin:padding-=
box;background-clip:border-box;font-family:menlo, consolas, monospace;fo=
nt-size:90%;margin-top:7px;margin-right:0px;margin-bottom:7px;margin-lef=
t:0px;padding-top:7px;padding-right:10px;padding-bottom:7px;padding-left=
:10px;white-space:pre-wrap;overflow-wrap:break-word;">   There are many =
ways in which date and time values might appear in
   Internet protocols:  this document focuses on just one common usage,
   viz. timestamps for Internet protocol events<br></pre><div><br></div>=
<div>However, I would assert that in my experience, many view RFC3339 as=
 just a standardised serialisation format for all dates in contexts that=
 go beyond this. I think there is a clear demand for a serialisation for=
mat that <i>can</i> incorporate a time zone or calendar identifier, and =
standardising this within the IETF is more likely to lead to interoperab=
ility. I also agree that you would never want to use such a time-zone va=
riant in log files. <br></div><div><br></div><div>So I think it comes do=
wn to two options:<br></div><ul><li>A single RFC that replaces 3339 cont=
aining all the variants. The benefit is you have one place to reference =
for how to serialise a date-time.<br></li><li>A new adjunct RFC for how =
to serialise date-times with IANA time zones, or without an absolute tim=
e at all (local "wall clock" date-times). This would not overlap 3339, w=
hich would continue to define how to serialise UTC and fixed-offset date=
-times.<br></li></ul><div>I am not too fussed which of these paths we go=
 down.&nbsp; I was originally advocating for the first option, but looki=
ng at it again, I can see good arguments for the second instead.<br></di=
v><div><br></div><div>Neil.<br></div></body></html>
--3a9ea51913e54d9894de3af3c29aac8f--


From nobody Sun Jan 24 20:22:06 2021
Return-Path: <ned.freed@mrochek.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D94B03A0DEE for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 20:22:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level: 
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mUqVd68UUc57 for <calsify@ietfa.amsl.com>; Sun, 24 Jan 2021 20:22:02 -0800 (PST)
Received: from plum.mrochek.com (plum.mrochek.com [172.95.64.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27B023A0DED for <calsify@ietf.org>; Sun, 24 Jan 2021 20:22:02 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RURPK7P2N400D2SG@mauve.mrochek.com> for calsify@ietf.org; Sun, 24 Jan 2021 20:16:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712;  t=1611548218; bh=yq319TlT2gaxWi5slrrdGrT7RS895xJlebilxH6+Ll0=;  h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=bgUOuVTvdykIe9jovvAgW/iZX+lnL+yEEggsQp+IlG60z60XtGH/M3hGx7VU3fY4d eAFHD5+oo5Sxjc0waF1NozK1xwYJ3g/0Up+YNCnexbtvp//VpwmHk0itB3sbUYNUK6 ExDx+efJdiVC019+QvEE3hAMD4Zqpgoo9E7RsK0U=
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RUAOXM63XS005PTU@mauve.mrochek.com>; Sun, 24 Jan 2021 20:16:56 -0800 (PST)
Cc: calsify@ietf.org
Message-id: <01RURPK5VO1U005PTU@mauve.mrochek.com>
Date: Sun, 24 Jan 2021 19:50:18 -0800 (PST)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Mon, 25 Jan 2021 12:18:28 +1100" <3288fdaf-28a9-45a9-bf50-c9de9e2c3486@dogfood.fastmail.com>
References: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com> <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com> <01RUQ0ZW4L3U005PTU@mauve.mrochek.com> <d17b75e7-9720-6bd3-dd23-349e8ceac4a3@gmail.com> <01RUQ4K8M1RQ005PTU@mauve.mrochek.com> <34839106-de11-41fe-96d6-33f95c30524d@dogfood.fastmail.com> <01RUQJ104Y3C005PTU@mauve.mrochek.com> <01RUQVLVFX6K005PTU@mauve.mrochek.com> <8f821d46-6cbd-4a11-8098-1d9bb3ac28e7@beta.fastmail.com> <3288fdaf-28a9-45a9-bf50-c9de9e2c3486@dogfood.fastmail.com>
To: Neil Jenkins <neilj@fastmailteam.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/4EIRw9ymcp1k8Tnxt2wx3c5fM7Q>
Subject: Re: [calsify] Fwd: New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2021 04:22:04 -0000

> I think the disagreement here stems from two viewpoints on what RFC3339 is.
> Ned is looking at it from the viewpoint that it defines a format for (log)
> timestamps only.

Not quite. I pointed out that RFC 3339 was and is used for timestamps in logs.
I never said, or even implied, that it doesn't have (many) other uses, either
by itself or in combination with other information.

However, the more important point, as you note below, is that RFC 3339
specifies a timestamp format. It's entirely self-contained, and aside from
allowing specification of a time zone offset, it provides no information about
presentation or anything else.

> The other side is viewing it as simply a standard serialisation format for
> dates in internet protocols without restriction on use case.

That may be true but I question the relevance. There are a myriad of use cases
for RFC 3339. There are also a myriad of use cases for RFC 3339 combined with
other information. I don't think anyone is claiming otherwise.

The issue here isn't that these other cases aren't worthy of consideration -
they are - it's that addressing them by changing the core semantics of a widely
used timestamp format isn't the right way to go about it.

> Having looked at the document's introduction again, Ned is technically
> correct:

>    There are many ways in which date and time values might appear in
>    Internet protocols:  this document focuses on just one common usage,
>    viz. timestamps for Internet protocol events

Exactly.

> However, I would assert that in my experience, many view RFC3339 as just a
> standardised serialisation format for all dates in contexts that go beyond
> this.

I don't know what this means. RFC 3339's semantics are clear, and the syntax
only allows for the expression of those semantics. If you "go beyond" those
semantics, you either have to extend the syntax, in which case you're not
talking about RFC 3339 format any more, or you have to create some sort of
grouping of RFC 3339 with additional information. In either case you have
extended RFC 339, and that's not a matter of how you view it.

> I think there is a clear demand for a serialisation format that *can*
> incorporate a time zone or calendar identifier, and standardising this within
> the IETF is more likely to lead to interoperability. I also agree that you
> would never want to use such a time-zone variant in log files.

OK... so it sounds to me like we're in agreement that RFC 3339's
semantics need to be retained. Good.

> So I think it comes down to two options:

>  * A single RFC that replaces 3339 containing all the variants. The benefit
>    is you have one place to reference for how to serialise a date-time.

Eliot already explained why this is a really bad idea.

>  * A new adjunct RFC for how to serialise date-times with IANA time zones, or
>    without an absolute time at all (local "wall clock" date-times).

A convention for this is already provided by RFC 3339, actually. Section 4.2.

>    This
>    would not overlap 3339, which would continue to define how to serialise
>    UTC and fixed-offset date-times.

This is a little confusing: Adjunct implies that you're extending RFC 3339, "no
overlap" implies you're not. In any case, I would recommend building on the
existing syntax of RFC 3339 if possible.

> I am not too fussed which of these paths we go down.  I was originally
> advocating for the first option, but looking at it again, I can see good
> arguments for the second instead.

Exactly.

				Ned


From nobody Mon Jan 25 00:02:13 2021
Return-Path: <sffc@google.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC1033A0C66 for <calsify@ietfa.amsl.com>; Mon, 25 Jan 2021 00:02:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.699
X-Spam-Level: 
X-Spam-Status: No, score=-15.699 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d2kxRdfC4frm for <calsify@ietfa.amsl.com>; Mon, 25 Jan 2021 00:02:09 -0800 (PST)
Received: from mail-ot1-x331.google.com (mail-ot1-x331.google.com [IPv6:2607:f8b0:4864:20::331]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA9CB3A0B08 for <calsify@ietf.org>; Mon, 25 Jan 2021 00:02:09 -0800 (PST)
Received: by mail-ot1-x331.google.com with SMTP id v1so11933792ott.10 for <calsify@ietf.org>; Mon, 25 Jan 2021 00:02:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mJz42fD0aGBk9rrZ1YG9x9/if4SAbtWUXBeZSzJonao=; b=lQJiCG8n7FvXdx3Dmo9m9BgNlvsbRs33/E3/h4yvy0dxSAXp1Usoxhx61UZGdK2W5/ f/oEUmgfNnP99sYir/N5t235RbkPNNiV/QNrAJ9oh7+If03Jq/rzbP7HmackG8nQxIE6 7pGAaFNoaP8aR1St6BQF4QIrnGXEF/kUsNdCjN/JTorf1rdYNU0/mu8uNsVCXHccvgQT BFBrQO58vMI5V28ooeb92o3Ld56ks2J6ZzzktfRxFzU/u/zhrBKz/tMwmEBPOAOB2XxX 3n9TSkQS9vM2CyTJbvU96X16y2zBW+lQOnxK2O2GXsnJjQzF+3TmGIX3XK9XLU7Ik3O0 Sw/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mJz42fD0aGBk9rrZ1YG9x9/if4SAbtWUXBeZSzJonao=; b=JMll512hg3jcwwEtS6D50qLtu7WkJTF/84m0U+dCXeFhTPtkZyJMi6QiEFxnmu8Ffh S//kADW5y/JWvbtWtDSLgdAgQU/dkRmnGsYs68eWEm2itGRZjl18N4uvT437+CXullpM 6vrx4vu50+WS8Y1MeM9VJRBP7kHcuW0qSBf031wEBfCtTxb5yQjdocxaiE5PGqRefxOy VSw4h2DT5nRfvCf5D9TKRaVkao5vGOaAYHD1tKbH76XKnjcpaTHQwtbnUdjrGYtBHk82 Lyp73/dQTPoK594UaEl2zObvBIwZWNdR8LBKIZpH7iQvawNpTEjbOaSOjfs4FVl2L1JD LyIQ==
X-Gm-Message-State: AOAM531UCKtp7SLvhgv2mxF4h5gG7i6Ib74TojmRU1AoYJK+VHOtwMAL XKHWpj0t9/9J65dfiKjlcf5O4tPJROeA8GEh/qBKRA==
X-Google-Smtp-Source: ABdhPJyslz9Z6znSdlgrmswomovEt0mfmQGdqipLDhu9oIKBs0yMfPqzSXogUsp7J6nSK14BDX0GAxSxrai6PDr8uVg=
X-Received: by 2002:a9d:7f88:: with SMTP id t8mr1069550otp.134.1611561728371;  Mon, 25 Jan 2021 00:02:08 -0800 (PST)
MIME-Version: 1.0
References: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com> <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com> <01RUQ0ZW4L3U005PTU@mauve.mrochek.com> <d17b75e7-9720-6bd3-dd23-349e8ceac4a3@gmail.com> <01RUQ4K8M1RQ005PTU@mauve.mrochek.com> <34839106-de11-41fe-96d6-33f95c30524d@dogfood.fastmail.com> <01RUQJ104Y3C005PTU@mauve.mrochek.com> <01RUQVLVFX6K005PTU@mauve.mrochek.com> <8f821d46-6cbd-4a11-8098-1d9bb3ac28e7@beta.fastmail.com> <3288fdaf-28a9-45a9-bf50-c9de9e2c3486@dogfood.fastmail.com> <01RURPK5VO1U005PTU@mauve.mrochek.com>
In-Reply-To: <01RURPK5VO1U005PTU@mauve.mrochek.com>
From: Shane Carr <sffc@google.com>
Date: Mon, 25 Jan 2021 02:01:56 -0600
Message-ID: <CABxsp=mX3h9nfPX7y2m-zNqDqgF8G3Pm9n0XerdcdBOAnAk2Lg@mail.gmail.com>
To: Ned Freed <ned.freed@mrochek.com>
Cc: Neil Jenkins <neilj@fastmailteam.com>, calsify@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005ab3c805b9b4f4d9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/q-csS1gUoXa3sP1L9MbU13tqSkA>
Subject: Re: [calsify] Fwd: New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2021 08:02:12 -0000

--0000000000005ab3c805b9b4f4d9
Content-Type: text/plain; charset="UTF-8"

A few things:

- 3339 and 8601-1 are good as a timestamp format.  The extension Ujjwal
proposed generalizes those formats based on the demonstrated needs of the
ecosystem when dealing with "human dates" as opposed to "computer dates".
It's an interesting observation that timestamps (e.g. log files) are
typically used for contemporary events, so the extended 6-digit year format
may not really be necessary.  Therefore, I think it would be a reasonable
option to keep 3339 unmodified and alive as the timestamp format, and
consider the new proposal to be a peer.

- I see a thread with Eliot Lear, but I don't see where the pros and cons
of a combined RFC versus separate RFCs are discussed.  (But this is moot if
we were to decide to keep RFC 3339 alive in its current state.)

- The key question solved by this RFC is the data model.  What Ujjwal is
proposing is to use a timestamp paired with information about the time zone
and calendar system.  Once we agree on the data model (I do), then we can
talk about how to package the data.  Could we use JSON?  Sure, but we still
need to specify the structure of the JSON and what form the keys/values can
take.  Ujjwal is proposing a string syntax with bracketed annotations
because (a) it is already used in the wild, and (b) compared with JSON,
strings are more compact [no keys], more compatible [byte array rather than
struct/map], and easier to deal with [no need to format/stringify].  I hope
not to get into a debate on point (b), but if there are people here who
believe that we should stop defining new string syntaxes and instead let
JSON (ECMA-404) rule all, then we may need to engage on that topic.

Shane


On Sun, Jan 24, 2021 at 10:22 PM Ned Freed <ned.freed@mrochek.com> wrote:

> > I think the disagreement here stems from two viewpoints on what RFC3339
> is.
> > Ned is looking at it from the viewpoint that it defines a format for
> (log)
> > timestamps only.
>
> Not quite. I pointed out that RFC 3339 was and is used for timestamps in
> logs.
> I never said, or even implied, that it doesn't have (many) other uses,
> either
> by itself or in combination with other information.
>
> However, the more important point, as you note below, is that RFC 3339
> specifies a timestamp format. It's entirely self-contained, and aside from
> allowing specification of a time zone offset, it provides no information
> about
> presentation or anything else.
>
> > The other side is viewing it as simply a standard serialisation format
> for
> > dates in internet protocols without restriction on use case.
>
> That may be true but I question the relevance. There are a myriad of use
> cases
> for RFC 3339. There are also a myriad of use cases for RFC 3339 combined
> with
> other information. I don't think anyone is claiming otherwise.
>
> The issue here isn't that these other cases aren't worthy of consideration
> -
> they are - it's that addressing them by changing the core semantics of a
> widely
> used timestamp format isn't the right way to go about it.
>
> > Having looked at the document's introduction again, Ned is technically
> > correct:
>
> >    There are many ways in which date and time values might appear in
> >    Internet protocols:  this document focuses on just one common usage,
> >    viz. timestamps for Internet protocol events
>
> Exactly.
>
> > However, I would assert that in my experience, many view RFC3339 as just
> a
> > standardised serialisation format for all dates in contexts that go
> beyond
> > this.
>
> I don't know what this means. RFC 3339's semantics are clear, and the
> syntax
> only allows for the expression of those semantics. If you "go beyond" those
> semantics, you either have to extend the syntax, in which case you're not
> talking about RFC 3339 format any more, or you have to create some sort of
> grouping of RFC 3339 with additional information. In either case you have
> extended RFC 339, and that's not a matter of how you view it.
>
> > I think there is a clear demand for a serialisation format that *can*
> > incorporate a time zone or calendar identifier, and standardising this
> within
> > the IETF is more likely to lead to interoperability. I also agree that
> you
> > would never want to use such a time-zone variant in log files.
>
> OK... so it sounds to me like we're in agreement that RFC 3339's
> semantics need to be retained. Good.
>
> > So I think it comes down to two options:
>
> >  * A single RFC that replaces 3339 containing all the variants. The
> benefit
> >    is you have one place to reference for how to serialise a date-time.
>
> Eliot already explained why this is a really bad idea.
>
> >  * A new adjunct RFC for how to serialise date-times with IANA time
> zones, or
> >    without an absolute time at all (local "wall clock" date-times).
>
> A convention for this is already provided by RFC 3339, actually. Section
> 4.2.
>
> >    This
> >    would not overlap 3339, which would continue to define how to
> serialise
> >    UTC and fixed-offset date-times.
>
> This is a little confusing: Adjunct implies that you're extending RFC
> 3339, "no
> overlap" implies you're not. In any case, I would recommend building on the
> existing syntax of RFC 3339 if possible.
>
> > I am not too fussed which of these paths we go down.  I was originally
> > advocating for the first option, but looking at it again, I can see good
> > arguments for the second instead.
>
> Exactly.
>
>                                 Ned
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>

--0000000000005ab3c805b9b4f4d9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">A few things:<div><br></div><div>- 3339 and 8601-1 are goo=
d as a timestamp format.=C2=A0 The extension Ujjwal proposed generalizes th=
ose formats based on the demonstrated needs of the ecosystem=C2=A0when deal=
ing with &quot;human dates&quot; as opposed to &quot;computer dates&quot;.=
=C2=A0 It&#39;s an interesting observation that timestamps (e.g. log files)=
 are typically used for contemporary events,=C2=A0so the extended 6-digit y=
ear format may not really be necessary.=C2=A0 Therefore, I think it would b=
e a reasonable option to keep 3339 unmodified and alive as the timestamp fo=
rmat, and consider the new proposal to be a peer.</div><div><br></div><div>=
- I see a thread with Eliot Lear, but I don&#39;t see where the pros and co=
ns of a combined RFC versus separate RFCs are discussed.=C2=A0 (But this is=
 moot if we were to decide to keep RFC 3339 alive in its current state.)</d=
iv><div><br></div><div>- The key question solved by this RFC is the data mo=
del.=C2=A0 What Ujjwal is proposing is to use a timestamp paired with infor=
mation about the time zone and calendar system.=C2=A0 Once we agree on the =
data model (I do), then we can talk about how to package the data.=C2=A0 Co=
uld we use JSON?=C2=A0 Sure, but we still need to specify the structure of =
the JSON and what form the keys/values can take.=C2=A0 Ujjwal is proposing =
a string syntax with bracketed annotations because (a) it is already used i=
n the wild, and (b) compared with JSON, strings are more compact [no keys],=
 more compatible [byte array rather than struct/map], and easier to deal wi=
th [no need to format/stringify].=C2=A0 I hope not to get into a debate on =
point (b), but if there are people here who believe that we should stop def=
ining new string syntaxes and instead let JSON (ECMA-404) rule all, then we=
 may need to engage on that topic.</div><div><br></div><div>Shane</div><div=
><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Sun, Jan 24, 2021 at 10:22 PM Ned Freed &lt;<a href=3D"mailto=
:ned.freed@mrochek.com">ned.freed@mrochek.com</a>&gt; wrote:<br></div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex">&gt; I think the disagreement =
here stems from two viewpoints on what RFC3339 is.<br>
&gt; Ned is looking at it from the viewpoint that it defines a format for (=
log)<br>
&gt; timestamps only.<br>
<br>
Not quite. I pointed out that RFC 3339 was and is used for timestamps in lo=
gs.<br>
I never said, or even implied, that it doesn&#39;t have (many) other uses, =
either<br>
by itself or in combination with other information.<br>
<br>
However, the more important point, as you note below, is that RFC 3339<br>
specifies a timestamp format. It&#39;s entirely self-contained, and aside f=
rom<br>
allowing specification of a time zone offset, it provides no information ab=
out<br>
presentation or anything else.<br>
<br>
&gt; The other side is viewing it as simply a standard serialisation format=
 for<br>
&gt; dates in internet protocols without restriction on use case.<br>
<br>
That may be true but I question the relevance. There are a myriad of use ca=
ses<br>
for RFC 3339. There are also a myriad of use cases for RFC 3339 combined wi=
th<br>
other information. I don&#39;t think anyone is claiming otherwise.<br>
<br>
The issue here isn&#39;t that these other cases aren&#39;t worthy of consid=
eration -<br>
they are - it&#39;s that addressing them by changing the core semantics of =
a widely<br>
used timestamp format isn&#39;t the right way to go about it.<br>
<br>
&gt; Having looked at the document&#39;s introduction again, Ned is technic=
ally<br>
&gt; correct:<br>
<br>
&gt;=C2=A0 =C2=A0 There are many ways in which date and time values might a=
ppear in<br>
&gt;=C2=A0 =C2=A0 Internet protocols:=C2=A0 this document focuses on just o=
ne common usage,<br>
&gt;=C2=A0 =C2=A0 viz. timestamps for Internet protocol events<br>
<br>
Exactly.<br>
<br>
&gt; However, I would assert that in my experience, many view RFC3339 as ju=
st a<br>
&gt; standardised serialisation format for all dates in contexts that go be=
yond<br>
&gt; this.<br>
<br>
I don&#39;t know what this means. RFC 3339&#39;s semantics are clear, and t=
he syntax<br>
only allows for the expression of those semantics. If you &quot;go beyond&q=
uot; those<br>
semantics, you either have to extend the syntax, in which case you&#39;re n=
ot<br>
talking about RFC 3339 format any more, or you have to create some sort of<=
br>
grouping of RFC 3339 with additional information. In either case you have<b=
r>
extended RFC 339, and that&#39;s not a matter of how you view it.<br>
<br>
&gt; I think there is a clear demand for a serialisation format that *can*<=
br>
&gt; incorporate a time zone or calendar identifier, and standardising this=
 within<br>
&gt; the IETF is more likely to lead to interoperability. I also agree that=
 you<br>
&gt; would never want to use such a time-zone variant in log files.<br>
<br>
OK... so it sounds to me like we&#39;re in agreement that RFC 3339&#39;s<br=
>
semantics need to be retained. Good.<br>
<br>
&gt; So I think it comes down to two options:<br>
<br>
&gt;=C2=A0 * A single RFC that replaces 3339 containing all the variants. T=
he benefit<br>
&gt;=C2=A0 =C2=A0 is you have one place to reference for how to serialise a=
 date-time.<br>
<br>
Eliot already explained why this is a really bad idea.<br>
<br>
&gt;=C2=A0 * A new adjunct RFC for how to serialise date-times with IANA ti=
me zones, or<br>
&gt;=C2=A0 =C2=A0 without an absolute time at all (local &quot;wall clock&q=
uot; date-times).<br>
<br>
A convention for this is already provided by RFC 3339, actually. Section 4.=
2.<br>
<br>
&gt;=C2=A0 =C2=A0 This<br>
&gt;=C2=A0 =C2=A0 would not overlap 3339, which would continue to define ho=
w to serialise<br>
&gt;=C2=A0 =C2=A0 UTC and fixed-offset date-times.<br>
<br>
This is a little confusing: Adjunct implies that you&#39;re extending RFC 3=
339, &quot;no<br>
overlap&quot; implies you&#39;re not. In any case, I would recommend buildi=
ng on the<br>
existing syntax of RFC 3339 if possible.<br>
<br>
&gt; I am not too fussed which of these paths we go down.=C2=A0 I was origi=
nally<br>
&gt; advocating for the first option, but looking at it again, I can see go=
od<br>
&gt; arguments for the second instead.<br>
<br>
Exactly.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Ned<br>
<br>
_______________________________________________<br>
calsify mailing list<br>
<a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/calsify" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/calsify</a><br>
</blockquote></div>

--0000000000005ab3c805b9b4f4d9--


From nobody Mon Jan 25 02:36:33 2021
Return-Path: <lear@cisco.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 995393A0E63 for <calsify@ietfa.amsl.com>; Mon, 25 Jan 2021 02:36:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.701
X-Spam-Level: 
X-Spam-Status: No, score=-7.701 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IojOolT47i5R for <calsify@ietfa.amsl.com>; Mon, 25 Jan 2021 02:36:30 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 783A33A0E62 for <calsify@ietf.org>; Mon, 25 Jan 2021 02:36:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4275; q=dns/txt; s=iport; t=1611570990; x=1612780590; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=ou25TfPqnvXGERxGTrWhkS9wtn65FehENoqYgexsPBQ=; b=gop4okEEfysnCsaTEqraT+wHwW/RRSh9FJ+R+Wu8fyO204BVrNga/qeh O6IbFTNkqzjEJXX/v0iGzqc2hYmECyhtp3MvSSc5LeIiXw/q22pF6EbLW 0wQhfBpXuvhIsLGck5hd8zEj2MOmkxQ6yP7Ax4arIqOHhKx6MmTb/BTf3 w=;
X-Files: signature.asc : 488
X-IPAS-Result: =?us-ascii?q?A0D0AgDMnQ5gjBbLJq1iHAEBAQEBAQcBARIBAQQEAQGCD?= =?us-ascii?q?4N4ASASL4RAiQSILyUDnEEEBwEBAQoDAQEvBAEBhEoCgXkmOBMCAwEBAQMCA?= =?us-ascii?q?wEBAQEFAQEBAgEGBBQBAQEBhkaFcwEBAQMBI0gOBQsLDgoqAgJXBhMUgxIBg?= =?us-ascii?q?mYgsWd2gTKFWYRoEIE4gVOLa0GCAIERJwwQglY+gl0EhHY0giwEgVUFC4EdK?= =?us-ascii?q?igKEYErKBlBVZt3nDKDAYMpgTeXDwMfglCaOIVwsSIEXoNwAgQGBQIWgW0hg?= =?us-ascii?q?VkzGggbFWUBgj4+EhkNji0OCY4nQAMwAjUCBgEJAQEDCYwVAQE?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.79,373,1602547200";  d="asc'?scan'208";a="32921630"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 25 Jan 2021 10:36:26 +0000
Received: from dhcp-10-61-106-207.cisco.com (dhcp-10-61-106-207.cisco.com [10.61.106.207]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 10PAaO1D016086 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 25 Jan 2021 10:36:25 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <F2E74752-8499-4B1E-BAA5-EAF65216F8D1@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_C648C3D8-3CB3-4C49-B7C1-A13352CF63BA"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Mon, 25 Jan 2021 11:36:23 +0100
In-Reply-To: <CABxsp=mX3h9nfPX7y2m-zNqDqgF8G3Pm9n0XerdcdBOAnAk2Lg@mail.gmail.com>
Cc: Ned Freed <ned.freed@mrochek.com>, calsify@ietf.org
To: Shane Carr <sffc@google.com>
References: <5927c3a3-9539-553d-598a-18d8bdadb244@igalia.com> <c9a1caed-829a-2339-21c1-5f0970110863@igalia.com> <01RUQ0ZW4L3U005PTU@mauve.mrochek.com> <d17b75e7-9720-6bd3-dd23-349e8ceac4a3@gmail.com> <01RUQ4K8M1RQ005PTU@mauve.mrochek.com> <34839106-de11-41fe-96d6-33f95c30524d@dogfood.fastmail.com> <01RUQJ104Y3C005PTU@mauve.mrochek.com> <01RUQVLVFX6K005PTU@mauve.mrochek.com> <8f821d46-6cbd-4a11-8098-1d9bb3ac28e7@beta.fastmail.com> <3288fdaf-28a9-45a9-bf50-c9de9e2c3486@dogfood.fastmail.com> <01RURPK5VO1U005PTU@mauve.mrochek.com> <CABxsp=mX3h9nfPX7y2m-zNqDqgF8G3Pm9n0XerdcdBOAnAk2Lg@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
X-Outbound-SMTP-Client: 10.61.106.207, dhcp-10-61-106-207.cisco.com
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/4qQg2HBWS829eB4TifMravGKwoY>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2021 10:36:33 -0000

--Apple-Mail=_C648C3D8-3CB3-4C49-B7C1-A13352CF63BA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Shane,


> On 25 Jan 2021, at 09:01, Shane Carr =
<sffc=3D40google.com@dmarc.ietf.org> wrote:
>=20
> A few things:
>=20
> - 3339 and 8601-1 are good as a timestamp format.  The extension =
Ujjwal proposed generalizes those formats based on the demonstrated =
needs of the ecosystem when dealing with "human dates" as opposed to =
"computer dates".  It's an interesting observation that timestamps (e.g. =
log files) are typically used for contemporary events, so the extended =
6-digit year format may not really be necessary.  Therefore, I think it =
would be a reasonable option to keep 3339 unmodified and alive as the =
timestamp format, and consider the new proposal to be a peer.

Yes, though I really have no problem now obsoleting 2 digit dates, and =
giving advice for applications to warn of their use (for instance).

>=20
> - I see a thread with Eliot Lear, but I don't see where the pros and =
cons of a combined RFC versus separate RFCs are discussed.  (But this is =
moot if we were to decide to keep RFC 3339 alive in its current state.)

I only have cons, but see below.

>=20
> - The key question solved by this RFC is the data model.  What Ujjwal =
is proposing is to use a timestamp paired with information about the =
time zone and calendar system.  Once we agree on the data model (I do), =
then we can talk about how to package the data.

Yes.  When considering this, let=E2=80=99s be sure that we have live use =
cases that are important for at least one community to address.  Oddly I =
don=E2=80=99t think that=E2=80=99s the TZ community, because much of =
what is being offered is already in iCal.  That being said, there are =
people more expert here than me, and I am quite happy to be proved =
wrong.


> Could we use JSON?  Sure, but we still need to specify the structure =
of the JSON and what form the keys/values can take.  Ujjwal is proposing =
a string syntax with bracketed annotations because (a) it is already =
used in the wild, and (b) compared with JSON, strings are more compact =
[no keys], more compatible [byte array rather than struct/map], and =
easier to deal with [no need to format/stringify].  I hope not to get =
into a debate on point (b), but if there are people here who believe =
that we should stop defining new string syntaxes and instead let JSON =
(ECMA-404) rule all, then we may need to engage on that topic.

The nice thing about defining the data model is that you can serialize =
it however you like, and there certainly needn=E2=80=99t be only one =
way.  This having been said, my only suggestion here is that you start =
in a way that leverages toolsets that are commonly used for at least the =
applications that are envisioned.  The nice thing about JSON and XML is =
that you can=E2=80=99t shake a stick without hitting such a thing =
(though if you have to lift the XML results, be sure to bend your knees =
so as not to break your back ;-).  FWIW YANG can help, and I would =
encourage its use as a description language, even if you have others, =
simply so that the work can be adopted more broadly by the O&M =
community.  YANG isn=E2=80=99t very popular with apps people, but what =
we=E2=80=99re talking about here is so small that maybe one could skate =
by.

Eliot

--Apple-Mail=_C648C3D8-3CB3-4C49-B7C1-A13352CF63BA
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAmAOnycACgkQh7ZrRtnS
ejPxmwgAgDUUwnzj6i40u9K7TTtv1F5zxhMAG466Ex2UqUkaW9/1xy5DsYqJaXUG
kFGqDOJPQkO4Jy2QzboARUuKlRwW7lCgZY5D4jsIIFSp7pn6nTLEMsrc34Y+TDuD
kck83PcWK8A12wHUsk8Txu9p5MmQCvZKKCOn6tf22iigWe2dNwRtuDgRrn8oqBC8
Dt8IoJzrIPcvOBlsQ+gCABNaUwRKwd7m9N7IEReQ44g9/uCfUzdMtKYNKyFKBwjg
6apW8SFU08b0KMKUTpY2d1CsGDM1XXVcaOCWK862w4kujhcFuQAXP8I0YwVxkZ9Z
EFSuRCB+3e3RWM2L+m/7fhk8X1LLUA==
=AgVB
-----END PGP SIGNATURE-----

--Apple-Mail=_C648C3D8-3CB3-4C49-B7C1-A13352CF63BA--


From nobody Mon Jan 25 07:47:36 2021
Return-Path: <mglt.ietf@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32B953A14AD for <calsify@ietfa.amsl.com>; Mon, 25 Jan 2021 07:47:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level: 
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lL--IFYMrhgh for <calsify@ietfa.amsl.com>; Mon, 25 Jan 2021 07:47:30 -0800 (PST)
Received: from mail-ua1-x931.google.com (mail-ua1-x931.google.com [IPv6:2607:f8b0:4864:20::931]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08AB63A14B2 for <calsify@ietf.org>; Mon, 25 Jan 2021 07:47:14 -0800 (PST)
Received: by mail-ua1-x931.google.com with SMTP id k47so4580328uad.1 for <calsify@ietf.org>; Mon, 25 Jan 2021 07:47:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=DhrcKMzQ9JMbHOim03Lw1+FJc3oTWzsbwOZs5risQco=; b=WMSBxCgAMeQKaDwJjei8gvLqZjEmHw/b9rozS7XF03iQYGsNjiHfP6AUvhNHRTMq0R WHI/50vcROtiRxB9OQygYNFYGs2HTXIyfaBn4pEW2qciWfvjnh5ViVQ5uTtEkUHpMk4U ka2ghGUxT/GD7i4C/h36K+++xKc5C5u+UYH8MlwbxrxA84C73bEVAquo28akluCaj+2h 9Snn0GEUtWYHHHpaWFGawS4NM0l7jUdvZskMmJRMy5SERqiPLnvfmKbcka1hhLK275tG neDsD81WVvfrYeJmm7v/1zocRix1Q2OlHyqQRJp856RV1fhehi4cbH6Ux6zRb7/BCFnF 32gw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=DhrcKMzQ9JMbHOim03Lw1+FJc3oTWzsbwOZs5risQco=; b=m1RetiONHsjgwyWPOu4XQ/EN9IAyrxem2DSL8eIXIx51aiHDH78uFW2366rmDAHZeg wY8oyt+fkJL8IRpgstZB9NNJ7Gif/9K1+atbzGYxxQLEznBLi1P4Vr90yU87CexnRBt8 Hl8/HBxqLmOvlyHbadD+sE8GWXxGnl6tEAaqhtaWpHZFnRDW0W5LloyQoq5D1273YuGi qiJYn80ZRfwO5eyuFrX5PTQ4384XdRGJcud2RSr6nT5p4PcFfq0mfocTcxc/EN0t5/qH N+8BRUQgDPEgVyVsnIm5iEtYd6xw5KbOAQ+++KC4W/eZkNtzVqrsXQqs7xUfYhPx9mC4 jLwQ==
X-Gm-Message-State: AOAM533GC9iVbAPcFWttc2KrXmnuMKUEUfDZy3gD5wNe3FD0HgoN6hsu MbRAqHxMLX37vgV/fMec3bdn81tnFeCebKpIG2ClK+T1SfQ=
X-Google-Smtp-Source: ABdhPJyx0UzNLquEoVB8gXoIpZAID8kYCgKifLLYz+nu1Krm3yzknry532YiWJWc57jccr38YrH6GlSvNfpQDVmnTQQ=
X-Received: by 2002:a9f:24af:: with SMTP id 44mr938133uar.68.1611589633896; Mon, 25 Jan 2021 07:47:13 -0800 (PST)
MIME-Version: 1.0
From: Daniel Migault <mglt.ietf@gmail.com>
Date: Mon, 25 Jan 2021 10:47:03 -0500
Message-ID: <CADZyTknZyV6KWDqZiWf6xWfyYUDhELZ5F37smJgEfO0GQnk5Ow@mail.gmail.com>
To: IETF-Calsify <calsify@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a6f5c305b9bb732a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/sj1vD1fmoJTR0htU2PPV4mv6x7c>
Subject: [calsify] expiring drafts heads-up
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2021 15:47:35 -0000

--000000000000a6f5c305b9bb732a
Content-Type: text/plain; charset="UTF-8"

Hi,

This is just a heads-up that some drafts are about to expire. Please at
least upload them, so we can see they are still on track.

* draft-ietf-calext-jscalendar-icalendar
* draft-ietf-calext-serverside-subscriptions
* draft-ietf-calext-subscription-upgrade

Yours,
Bron and Daniel

-- 
Daniel Migault
Ericsson

--000000000000a6f5c305b9bb732a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,=C2=A0<div><br></div><div>This is just a heads-up that =
some drafts are about to expire. Please at least upload them, so we can see=
 they are still on track.=C2=A0</div><div>=C2=A0</div><div>* draft-ietf-cal=
ext-jscalendar-icalendar<br>* draft-ietf-calext-serverside-subscriptions<br=
>* draft-ietf-calext-subscription-upgrade<br><div><br></div><div><div>Yours=
,=C2=A0</div><div>Bron and Daniel</div><div><br></div>-- <br><div dir=3D"lt=
r" class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D=
"ltr"><div>Daniel Migault<br></div><div>Ericsson</div></div></div></div></d=
iv></div>

--000000000000a6f5c305b9bb732a--


From nobody Mon Jan 25 08:53:42 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BC683A1501; Mon, 25 Jan 2021 08:53:41 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: calsify@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: calsify@ietf.org
Message-ID: <161159362152.8735.272221874023153231@ietfa.amsl.com>
Date: Mon, 25 Jan 2021 08:53:41 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/lktVU88N9AHmtHThLzaq-DAoCcc>
Subject: [calsify] I-D Action: draft-ietf-calext-jscalendar-icalendar-03.txt
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2021 16:53:42 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Calendaring Extensions WG of the IETF.

        Title           : JSCalendar: Converting from and to iCalendar
        Authors         : Neil Jenkins
                          Robert Stepanek
                          Michael Douglass
	Filename        : draft-ietf-calext-jscalendar-icalendar-03.txt
	Pages           : 54
	Date            : 2021-01-25

Abstract:
   This document provides the required methods for converting JSCalendar
   from and to iCalendar.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-calext-jscalendar-icalendar/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-calext-jscalendar-icalendar-03
https://datatracker.ietf.org/doc/html/draft-ietf-calext-jscalendar-icalendar-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-calext-jscalendar-icalendar-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Mon Jan 25 13:07:34 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD9483A18E4 for <calsify@ietfa.amsl.com>; Mon, 25 Jan 2021 13:07:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.499
X-Spam-Level: 
X-Spam-Status: No, score=0.499 tagged_above=-999 required=5 tests=[FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8J5y0S1-CUzO for <calsify@ietfa.amsl.com>; Mon, 25 Jan 2021 13:07:30 -0800 (PST)
Received: from mail-lf1-f41.google.com (mail-lf1-f41.google.com [209.85.167.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 632993A18E3 for <calsify@ietf.org>; Mon, 25 Jan 2021 13:07:30 -0800 (PST)
Received: by mail-lf1-f41.google.com with SMTP id f1so10021859lfu.3 for <calsify@ietf.org>; Mon, 25 Jan 2021 13:07:30 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=kmPWk5PH+meaDpNGx7SHgRpb+vY04xcBVoQLhPdx2kU=; b=i2c+5wWZ8eNSsrUMlZrm8NNziA0zFon5DPZ4KeyLlV8USnHAY+N7BW8VB50kMrpGf+ rsdsgoUii3/ef1KFmevq28l/mh7cw9+UI7Nc6aB89QVzJmphgwlVtET6KQKJrQBhoLqS zuKH4FAUknmcR8RP1RVm6j/0gkoTE+JEYXymDogVc0oG879mxwCM7yX4WnusBT+L3Buh TF0y+ZHFzmL6jokhZCtpk84LsE+ed2k+qkA+wp7Xo3XJhKoJrWkQ/0u9ci7I8KWzWeTh e3JhBY8bpF5w/Gt0gibhZNjvcB9sR+eQkRaSlUKDYIIYvEnpP6XROG1OcUR++8oRLjrN H3nw==
X-Gm-Message-State: AOAM5306PHE77agwJ+pNTGxMAGZaObZp6zZ/C39+foBZYunz3Oz1+jfT ER0BTJLykKLoczr3zeFlTvit7i+zWimkxlexVos=
X-Google-Smtp-Source: ABdhPJwB07W7oatWA4tDsbsm6LvV4/XVFc4jJdmcTXRc8lKTMU4GfR9db6CyyRsYWbV6T1/wo5n9h0a6UqDyZOP0hTc=
X-Received: by 2002:ac2:592a:: with SMTP id v10mr1079111lfi.123.1611608848086;  Mon, 25 Jan 2021 13:07:28 -0800 (PST)
MIME-Version: 1.0
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <0275d5af-6eea-4608-913e-c96d59c0abea@dogfood.fastmail.com> <c87c068b-02f1-913a-64ef-497f827fc3ea@igalia.com> <27ae33c7-d5cf-428b-99fa-7b974be85e70@dogfood.fastmail.com> <AAD5976B-A601-45AC-9E43-CEB24D57BD1E@cisco.com> <fd342b5e-d998-487e-8fa2-5dd949b517e8@dogfood.fastmail.com>
In-Reply-To: <fd342b5e-d998-487e-8fa2-5dd949b517e8@dogfood.fastmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 25 Jan 2021 16:07:16 -0500
Message-ID: <CALaySJJPQ0zENWrd-JfthujCjPNcq7aNoDaxtFV7pehAOi5CjQ@mail.gmail.com>
To: Bron Gondwana <brong@fastmailteam.com>
Cc: Eliot Lear <lear@cisco.com>, calsify@ietf.org,  Francesca Palombini <francesca.palombini@ericsson.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/-mWDnzqI3640k0maLhGqHlHdFH8>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2021 21:07:33 -0000

First, everyone, meet Francesca Palombini (added on CC), who will be
your new AD starting in March.

I do have to agree with Eliot that obsoleting 3339 is well out of
charter for calext.  What you quote below from what you said in
dispatch, "Javascript notation format is looking for a standard
serialisation", is not the same thing as "revising and obsoleting RFC
3339".  As Eliot points out, there are ways to include extra
information in jCalendar, for example, without changing the basic
date/time strings that are used in many places.  Changes to the 3339
date/time strings will have ramifications all over the Internet, and I
think that needs its own working group and a lot of publicity to make
sure we're getting "everyone" who cares about it, rather than doing it
where people think we're only dealing with calendaring protocols.

I *am* sorry if this has been frustrating, unfriendly, or otherwise
unpleasant for Ujjwal, and I'm quite sensitive to that.  I'm happy to
help in any way I can, as I know Bron and Eliot (and Francesca) are.
But we can't just handle this document in an inappropriately light
way... the effect will be too far-reaching, even if exactly the
changes that Ujjwal's draft suggests should turn out to be perfect.

Do we think we should be chartering a working group to revise and
obsolete RFC 3339?  If so, let's get a draft charter for that and get
the process started.  Do we need a standard JSON wrapper around what
3339 specifies, either as a stop-gap or as a permanent solution?  Then
maybe calext is the place to do that, and let's shift to working on
that.

Barry, ART AD

On Sun, Jan 24, 2021 at 5:53 AM Bron Gondwana <brong@fastmailteam.com> wrot=
e:
>
> I'll ask you the same question I asked Ned, which is "do you object to th=
is work being taken up by the IETF at all, or just to it obsoleting 3339?"
>
> I will also point out that for all that we've talked about making the IET=
F more welcoming to newcomers, this has been a really unfriendly experience=
 for Ujjwal.  Maybe that's my fault, but I'm sorry Ujjwal for misleading yo=
u if so.  I did raise that this work was coming in the "any other business"=
 at IETF110's DISPATCH, but without a draft there was very little guidance.=
  Indeed the minutes of last dispatch say:
>
> Bron Gondwana: RFC3339 extension
> * Javascript notation format is looking for a standard serialisation.
>
> Harald Alvestrand:
> * We should have done this in the 90s!  It was a mistake not to do it the=
n.
>
> Neil Jenkins:
> * we do need a serialisation format
>
> Where to discuss: calsify or tzdata lists, but probably calsify is best.
>
>
> You can watch a video of the exact discussion here: https://youtu.be/d871=
MoUgAKU?t=3D6418
>
> ...
>
> Regardless, it appears that the right next venue for this document is DIS=
PATCH at IETF110.
>
> Regards,
>
> Bron.
>
> On Sun, Jan 24, 2021, at 21:32, Eliot Lear wrote:
>
> Bron,
>
> I=E2=80=99m sorry, but I have both substantive and procedural problems wi=
th you moving forward like this.  Let me start with the procedural.  This w=
ork isn=E2=80=99t in calext=E2=80=99s charter.  You are specifically charte=
red to tackle several extensions to the iCalendar format, and that is it.  =
This is not an extension to that format.  This is a change to a standard th=
at is used extremely broadly.
>
> And this leads me to the substantive concern: this change is backward inc=
ompatible with  3339.  The ABNF in 3339 is clear: the stamp ends "time-offs=
et" ("Z" / time-numoffset).  Adding =E2=80=9Csuffix" blow up in any yacc/bi=
son-based parser and who knows what else.  Just imagine all the perl, awk, =
php, and python that whacks this stuff.
>
> In a great many cases, there is no means to negotiate the extension.  Let=
 me give you two examples:
>
> Logging software commonly uses 3339 both for generation and for parsing, =
and the parsers themselves are notoriously fragile to the point that I do n=
ot believe any of them would entertain any changes to 3339.  The ecosystem =
is so vast that there is no hope of enumerating it.  To test this, imagine =
what damage changing any other field to syslog would cause.
> Calendaring software, though in a smaller ecosystem, will have older vers=
ions that may well fail to parse.
>
>
> I am not saying that 3339 can never be updated, but before it is, it shou=
ld be clear that (a) it is broadly needed, not just by calendaring, and (b)=
 that there is reason to believe that the change will be broadly adopted, a=
gain not just by calendaring.  If it=E2=80=99s just the calendaring ecosyst=
em, you have properties and parameters to use.
>
> Eliot
>
>
> On 24 Jan 2021, at 04:15, Bron Gondwana <brong@fastmailteam.com> wrote:
>
> The document is plenty complete enough for a call for adoption!  I shall =
do so now.
>
> You are exactly correct that it's possible to do further iteration after =
adoption.
>
> Thanks,
>
> Bron.
>
> On Fri, Jan 22, 2021, at 23:19, Ujjwal Sharma wrote:
>
> Hi Bron, CalExt Friends!
>
> I made a new revision of the draft, which shifts the focus to defining
> the syntax/format and defers the standardization of the actual key-value
> pairs to sibling organizations like IANA and Unicode Consortium.
>
> I'd love to hear your opinions on this version, which you can find at
> https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/,
> which can be filed as issues on the GitHub repository or emailed to me
> directly. In the meantime, I will address the remaining concerns/polish
> issues like fixing the references section.
>
> How "complete" does the document need to be in order to initiate the
> call for adoption? If the current version works, can we start it as soon
> as possible? Of course, if my understanding of "adoption" is correct,
> I'd be happy to iterate on the document further after the adoption by
> the WG.
>
> Best,
> Ujjwal
>
> On 14/01/2021 8.34 am, Bron Gondwana wrote:
> > Sounds great.  Let me know :)
> >
> > When we do the call for adoption I'll also advertise the fact over to
> > the wider IETF - probably dispatch and tzdata lists at least.
> >
> > Cheers,
> >
> > Bron.
> >
> >
> > On Thu, Jan 14, 2021, at 13:48, Ujjwal Sharma wrote:
> >> Thanks Bron!
> >>
> >> I'll make a few more changes, release a 01 version, ask for more
> >> feedback and then let you know, hopefully by the end of this week.
> >>
> >> Ujjwal
> >>
> >> On 14/01/2021 7.03 am, Bron Gondwana wrote:
> >> > I can do a call for adoption straight away if you like - the next
> >> > meeting isn't for a couple of months.
> >> >
> >> > Bron.
> >> >
> >> > On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:
> >> >> One question: given things move forward smoothly, how do I proceed?
> >> >> Should I apply for this document to be adopted by the calext WG? I
> >> >> suppose the fastest way to proceed is to present it at the next IET=
F
> >> >> meeting?
> >> >>
> >> >>
> >> >>
> >> >> Ujjwal
> >> >>
> >> >> On 12/01/2021 4.03 am, Ujjwal Sharma wrote:
> >> >> > Hi Calsify folks!
> >> >> >
> >> >> > I am sorry for the long delay, I got a little sidetracked working=
 on
> >> >> > other things, but I'm happy to inform you all that I have
> >> something that
> >> >> > resembles a first draft for the updated timestamps RFC.
> >> >> >
> >> >> > Here's where you can find it:
> >> >> >
> >> >> > Datatracker:
> >> >>
> >> > https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
> >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/>
> >> >>
> >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
> >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/>>
> >> >> >
> >> >>
> >> GitHub: https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>
> >> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>>
> >> >> >
> >> >> > I would request you all to take a look at it when you can and let=
 me
> >> >> > know what you think. You can file a GitHub issue or email me
> >> directly.
> >> >> >
> >> >> > There's a few open discussions regarding the exact format and how=
 the
> >> >> > interaction with bodies like the Unicode consortium work, so
> >> please feel
> >> >> > free to send me your thoughts regarding that as well.
> >> >> >
> >> >> > Also, some references/bibliography is not perfectly functional ye=
t
> >> >> > because I am still relatively new to authoring RFCs using
> >> Metanorma but
> >> >> > I'm actively looking into it.
> >> >> >
> >> >> > Thanks and looking forward to hear from you,
> >> >> > Ujjwal
> >> >> >
> >> >>
> >> >> --
> >> >> Ujjwal "Ryzokuken" Sharma (he/him)
> >> >>
> >> >> Compilers Hacker, Node.js Core Collaborator and Speaker
> >> >>
> >> >> _______________________________________________
> >> >> calsify mailing list
> >> >> calsify@ietf.org <mailto:calsify@ietf.org> <mailto:calsify@ietf.org
> >> <mailto:calsify@ietf.org>>
> >> >> https://www.ietf.org/mailman/listinfo/calsify
> >> <https://www.ietf.org/mailman/listinfo/calsify>
> >> >> <https://www.ietf.org/mailman/listinfo/calsify
> >> <https://www.ietf.org/mailman/listinfo/calsify>>
> >> >>
> >> >
> >> > --
> >> >   Bron Gondwana, CEO, Fastmail Pty Ltd
> >> >   brong@fastmailteam.com <mailto:brong@fastmailteam.com>
> >> >
> >> >
> >> > _______________________________________________
> >> > calsify mailing list
> >> > calsify@ietf.org <mailto:calsify@ietf.org>
> >> > https://www.ietf.org/mailman/listinfo/calsify
> >> <https://www.ietf.org/mailman/listinfo/calsify>
> >> >
> >>
> >> --
> >> Ujjwal "Ryzokuken" Sharma (he/him)
> >>
> >> Compilers Hacker, Node.js Core Collaborator and Speaker
> >>
> >> _______________________________________________
> >> calsify mailing list
> >> calsify@ietf.org <mailto:calsify@ietf.org>
> >> https://www.ietf.org/mailman/listinfo/calsify
> >> <https://www.ietf.org/mailman/listinfo/calsify>
> >>
> >
> > --
> >   Bron Gondwana, CEO, Fastmail Pty Ltd
> >   brong@fastmailteam.com
> >
> >
> >
> > _______________________________________________
> > calsify mailing list
> > calsify@ietf.org
> > https://www.ietf.org/mailman/listinfo/calsify
> >
>
> --
> Ujjwal "Ryzokuken" Sharma (he/him)
>
> Compilers Hacker, Node.js Core Collaborator and Speaker
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>
>
> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd
>   brong@fastmailteam.com
>
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>
>
> Attachments:
>
> signature.asc
>
>
> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd
>   brong@fastmailteam.com
>
>


From nobody Mon Jan 25 21:29:58 2021
Return-Path: <sffc@google.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5A273A1C09 for <calsify@ietfa.amsl.com>; Mon, 25 Jan 2021 21:29:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.699
X-Spam-Level: 
X-Spam-Status: No, score=-15.699 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t9F0jUdUu0RY for <calsify@ietfa.amsl.com>; Mon, 25 Jan 2021 21:29:52 -0800 (PST)
Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 955033A1C07 for <calsify@ietf.org>; Mon, 25 Jan 2021 21:29:52 -0800 (PST)
Received: by mail-oi1-x231.google.com with SMTP id h192so17413408oib.1 for <calsify@ietf.org>; Mon, 25 Jan 2021 21:29:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8WTs7GU51NUhsCMFRB+zkr9ChA5UxoTMbouvA9pT/No=; b=FifXu/dC4oSBxjRs77zEsNdlR839yi9/AYEvAmLNxnH+cOpi1ApSi5CO0cI729FUUM 70mZU4CocNFMngxaXTvwddCdW9/7SdVZTE8Ap5pcRxj/RxV9jpjIXFT8ZpQzRBBuYgU4 Pi96gXCBCD/kUOcup18iOcGypcAQTjHtgyKJzNJ9JtqS1If6Alb1hY7NEwqyIqW2A838 xjK0yStyBQKxA9t54v8QsptRbXnA581a+MuytA2UMgEh89ODbrWDsfalqlWi/vpYQbFi b7K0jHl46LB2OBLLFiXfP/3g+XuNCUbnX/R91fU1gyiCKMZGD1D/9AREGSXEFe41SXla cCvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8WTs7GU51NUhsCMFRB+zkr9ChA5UxoTMbouvA9pT/No=; b=Ae7gtHkl/eH0Aj7JlDehVSbtkINThw9e9f/MJyVa/nHnFYP6BaEWpETiLtAQn0yzul GBraXdAdlLlMKrwhl+Esq/FJOidCbIun+ic4i7Nd797hIIITT7LvzxG742CbUtlUUJ+o R2Zi3/gTspLEO8bsQZEY9PsHK9c7pdiUBHXK8jbG6yT882YM8qSAfepFeyV17AdSH+mt BEic46msmePuqrTl4wtTjKyybMnwr3QjcI6eQl0lRW7t8MDWjWkxchfeHBzeapDMQu5N uEOpap4B2qgvVEb9DTlgcdDpunQFXP+Au4EhAB0b5uXcKCaMn8corBSjT18BQSD97SX+ PQFA==
X-Gm-Message-State: AOAM533jSyKXSlPbeyUrF0h92Xjqp/IPFnnVolyNqX8jzwocXIZBdpXw ibLcy2l7WOU/kYNPcER2XBEmFd0G6eKV8RuNFg806w==
X-Google-Smtp-Source: ABdhPJxI9x1eauqpBklw6GC1qQ6RA0it5mJoP6AVO0rB9b2sdBMum+EpFwS+dPDiq1gGHWMz+XO3xc00JrvnKZzJsMI=
X-Received: by 2002:aca:d417:: with SMTP id l23mr2190430oig.145.1611638991181;  Mon, 25 Jan 2021 21:29:51 -0800 (PST)
MIME-Version: 1.0
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <0275d5af-6eea-4608-913e-c96d59c0abea@dogfood.fastmail.com> <c87c068b-02f1-913a-64ef-497f827fc3ea@igalia.com> <27ae33c7-d5cf-428b-99fa-7b974be85e70@dogfood.fastmail.com> <AAD5976B-A601-45AC-9E43-CEB24D57BD1E@cisco.com> <fd342b5e-d998-487e-8fa2-5dd949b517e8@dogfood.fastmail.com> <CALaySJJPQ0zENWrd-JfthujCjPNcq7aNoDaxtFV7pehAOi5CjQ@mail.gmail.com>
In-Reply-To: <CALaySJJPQ0zENWrd-JfthujCjPNcq7aNoDaxtFV7pehAOi5CjQ@mail.gmail.com>
From: Shane Carr <sffc@google.com>
Date: Mon, 25 Jan 2021 23:29:39 -0600
Message-ID: <CABxsp==sPd3Uj45caWojyp=WEng5_DGTnjFzJ7x0enXWFjp4+w@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: Bron Gondwana <brong@fastmailteam.com>,  Francesca Palombini <francesca.palombini@ericsson.com>, calsify@ietf.org
Content-Type: multipart/alternative; boundary="00000000000093af2205b9c6f1e7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/YuJDRQT-8heqrhejCNY3vWXmetI>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2021 05:29:56 -0000

--00000000000093af2205b9c6f1e7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks everyone for the thoughtful responses.

At this point, I have seen three general types of concerns over
Ujjwal's proposal:

1) Concerns that we need to spend more time exploring the space before
jumping into a solution
2) Concerns over compatibility with systems that want a standalone timezone
syntax without Ujjwal's annotations
3) Proposition that we should standardize a JSON/YANG schema before a
string syntax

My responses:

1) Ujjwal's proposal is the result of quite a bit of work within ECMA-TC39
and liaising with some folks in the Unicode Consortium.  I worry that
chartering a new working group would duplicate much of the work that has
already gone into this proposal (not to mention setting ECMA back further).

2) Two very clear paths forward have been presented: publish the proposal
as a new RFC, and then either keep 3339 the way it is, or publish a
successor to 3339 with 6-digit years but no annotations.

3) I discussed earlier why I feel a string syntax is warranted.  I'm happy
to continue this discussion if we can narrow it down to this point of
contention.

Shane


On Mon, Jan 25, 2021 at 3:07 PM Barry Leiba <barryleiba@computer.org> wrote=
:

> First, everyone, meet Francesca Palombini (added on CC), who will be
> your new AD starting in March.
>
> I do have to agree with Eliot that obsoleting 3339 is well out of
> charter for calext.  What you quote below from what you said in
> dispatch, "Javascript notation format is looking for a standard
> serialisation", is not the same thing as "revising and obsoleting RFC
> 3339".  As Eliot points out, there are ways to include extra
> information in jCalendar, for example, without changing the basic
> date/time strings that are used in many places.  Changes to the 3339
> date/time strings will have ramifications all over the Internet, and I
> think that needs its own working group and a lot of publicity to make
> sure we're getting "everyone" who cares about it, rather than doing it
> where people think we're only dealing with calendaring protocols.
>
> I *am* sorry if this has been frustrating, unfriendly, or otherwise
> unpleasant for Ujjwal, and I'm quite sensitive to that.  I'm happy to
> help in any way I can, as I know Bron and Eliot (and Francesca) are.
> But we can't just handle this document in an inappropriately light
> way... the effect will be too far-reaching, even if exactly the
> changes that Ujjwal's draft suggests should turn out to be perfect.
>
> Do we think we should be chartering a working group to revise and
> obsolete RFC 3339?  If so, let's get a draft charter for that and get
> the process started.  Do we need a standard JSON wrapper around what
> 3339 specifies, either as a stop-gap or as a permanent solution?  Then
> maybe calext is the place to do that, and let's shift to working on
> that.
>
> Barry, ART AD
>
> On Sun, Jan 24, 2021 at 5:53 AM Bron Gondwana <brong@fastmailteam.com>
> wrote:
> >
> > I'll ask you the same question I asked Ned, which is "do you object to
> this work being taken up by the IETF at all, or just to it obsoleting 333=
9?"
> >
> > I will also point out that for all that we've talked about making the
> IETF more welcoming to newcomers, this has been a really unfriendly
> experience for Ujjwal.  Maybe that's my fault, but I'm sorry Ujjwal for
> misleading you if so.  I did raise that this work was coming in the "any
> other business" at IETF110's DISPATCH, but without a draft there was very
> little guidance.  Indeed the minutes of last dispatch say:
> >
> > Bron Gondwana: RFC3339 extension
> > * Javascript notation format is looking for a standard serialisation.
> >
> > Harald Alvestrand:
> > * We should have done this in the 90s!  It was a mistake not to do it
> then.
> >
> > Neil Jenkins:
> > * we do need a serialisation format
> >
> > Where to discuss: calsify or tzdata lists, but probably calsify is best=
.
> >
> >
> > You can watch a video of the exact discussion here:
> https://youtu.be/d871MoUgAKU?t=3D6418
> >
> > ...
> >
> > Regardless, it appears that the right next venue for this document is
> DISPATCH at IETF110.
> >
> > Regards,
> >
> > Bron.
> >
> > On Sun, Jan 24, 2021, at 21:32, Eliot Lear wrote:
> >
> > Bron,
> >
> > I=E2=80=99m sorry, but I have both substantive and procedural problems =
with you
> moving forward like this.  Let me start with the procedural.  This work
> isn=E2=80=99t in calext=E2=80=99s charter.  You are specifically chartere=
d to tackle
> several extensions to the iCalendar format, and that is it.  This is not =
an
> extension to that format.  This is a change to a standard that is used
> extremely broadly.
> >
> > And this leads me to the substantive concern: this change is backward
> incompatible with  3339.  The ABNF in 3339 is clear: the stamp ends
> "time-offset" ("Z" / time-numoffset).  Adding =E2=80=9Csuffix" blow up in=
 any
> yacc/bison-based parser and who knows what else.  Just imagine all the
> perl, awk, php, and python that whacks this stuff.
> >
> > In a great many cases, there is no means to negotiate the extension.
> Let me give you two examples:
> >
> > Logging software commonly uses 3339 both for generation and for parsing=
,
> and the parsers themselves are notoriously fragile to the point that I do
> not believe any of them would entertain any changes to 3339.  The ecosyst=
em
> is so vast that there is no hope of enumerating it.  To test this, imagin=
e
> what damage changing any other field to syslog would cause.
> > Calendaring software, though in a smaller ecosystem, will have older
> versions that may well fail to parse.
> >
> >
> > I am not saying that 3339 can never be updated, but before it is, it
> should be clear that (a) it is broadly needed, not just by calendaring, a=
nd
> (b) that there is reason to believe that the change will be broadly
> adopted, again not just by calendaring.  If it=E2=80=99s just the calenda=
ring
> ecosystem, you have properties and parameters to use.
> >
> > Eliot
> >
> >
> > On 24 Jan 2021, at 04:15, Bron Gondwana <brong@fastmailteam.com> wrote:
> >
> > The document is plenty complete enough for a call for adoption!  I shal=
l
> do so now.
> >
> > You are exactly correct that it's possible to do further iteration afte=
r
> adoption.
> >
> > Thanks,
> >
> > Bron.
> >
> > On Fri, Jan 22, 2021, at 23:19, Ujjwal Sharma wrote:
> >
> > Hi Bron, CalExt Friends!
> >
> > I made a new revision of the draft, which shifts the focus to defining
> > the syntax/format and defers the standardization of the actual key-valu=
e
> > pairs to sibling organizations like IANA and Unicode Consortium.
> >
> > I'd love to hear your opinions on this version, which you can find at
> > https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/,
> > which can be filed as issues on the GitHub repository or emailed to me
> > directly. In the meantime, I will address the remaining concerns/polish
> > issues like fixing the references section.
> >
> > How "complete" does the document need to be in order to initiate the
> > call for adoption? If the current version works, can we start it as soo=
n
> > as possible? Of course, if my understanding of "adoption" is correct,
> > I'd be happy to iterate on the document further after the adoption by
> > the WG.
> >
> > Best,
> > Ujjwal
> >
> > On 14/01/2021 8.34 am, Bron Gondwana wrote:
> > > Sounds great.  Let me know :)
> > >
> > > When we do the call for adoption I'll also advertise the fact over to
> > > the wider IETF - probably dispatch and tzdata lists at least.
> > >
> > > Cheers,
> > >
> > > Bron.
> > >
> > >
> > > On Thu, Jan 14, 2021, at 13:48, Ujjwal Sharma wrote:
> > >> Thanks Bron!
> > >>
> > >> I'll make a few more changes, release a 01 version, ask for more
> > >> feedback and then let you know, hopefully by the end of this week.
> > >>
> > >> Ujjwal
> > >>
> > >> On 14/01/2021 7.03 am, Bron Gondwana wrote:
> > >> > I can do a call for adoption straight away if you like - the next
> > >> > meeting isn't for a couple of months.
> > >> >
> > >> > Bron.
> > >> >
> > >> > On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:
> > >> >> One question: given things move forward smoothly, how do I procee=
d?
> > >> >> Should I apply for this document to be adopted by the calext WG? =
I
> > >> >> suppose the fastest way to proceed is to present it at the next
> IETF
> > >> >> meeting?
> > >> >>
> > >> >>
> > >> >>
> > >> >> Ujjwal
> > >> >>
> > >> >> On 12/01/2021 4.03 am, Ujjwal Sharma wrote:
> > >> >> > Hi Calsify folks!
> > >> >> >
> > >> >> > I am sorry for the long delay, I got a little sidetracked
> working on
> > >> >> > other things, but I'm happy to inform you all that I have
> > >> something that
> > >> >> > resembles a first draft for the updated timestamps RFC.
> > >> >> >
> > >> >> > Here's where you can find it:
> > >> >> >
> > >> >> > Datatracker:
> > >> >>
> > >> > https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended=
/
> > >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/=
>
> > >> >>
> > >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
> > >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
> >>
> > >> >> >
> > >> >>
> > >> GitHub:
> https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
> > >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>
> > >> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
> > >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>>
> > >> >> >
> > >> >> > I would request you all to take a look at it when you can and
> let me
> > >> >> > know what you think. You can file a GitHub issue or email me
> > >> directly.
> > >> >> >
> > >> >> > There's a few open discussions regarding the exact format and
> how the
> > >> >> > interaction with bodies like the Unicode consortium work, so
> > >> please feel
> > >> >> > free to send me your thoughts regarding that as well.
> > >> >> >
> > >> >> > Also, some references/bibliography is not perfectly functional
> yet
> > >> >> > because I am still relatively new to authoring RFCs using
> > >> Metanorma but
> > >> >> > I'm actively looking into it.
> > >> >> >
> > >> >> > Thanks and looking forward to hear from you,
> > >> >> > Ujjwal
> > >> >> >
> > >> >>
> > >> >> --
> > >> >> Ujjwal "Ryzokuken" Sharma (he/him)
> > >> >>
> > >> >> Compilers Hacker, Node.js Core Collaborator and Speaker
> > >> >>
> > >> >> _______________________________________________
> > >> >> calsify mailing list
> > >> >> calsify@ietf.org <mailto:calsify@ietf.org> <mailto:
> calsify@ietf.org
> > >> <mailto:calsify@ietf.org>>
> > >> >> https://www.ietf.org/mailman/listinfo/calsify
> > >> <https://www.ietf.org/mailman/listinfo/calsify>
> > >> >> <https://www.ietf.org/mailman/listinfo/calsify
> > >> <https://www.ietf.org/mailman/listinfo/calsify>>
> > >> >>
> > >> >
> > >> > --
> > >> >   Bron Gondwana, CEO, Fastmail Pty Ltd
> > >> >   brong@fastmailteam.com <mailto:brong@fastmailteam.com>
> > >> >
> > >> >
> > >> > _______________________________________________
> > >> > calsify mailing list
> > >> > calsify@ietf.org <mailto:calsify@ietf.org>
> > >> > https://www.ietf.org/mailman/listinfo/calsify
> > >> <https://www.ietf.org/mailman/listinfo/calsify>
> > >> >
> > >>
> > >> --
> > >> Ujjwal "Ryzokuken" Sharma (he/him)
> > >>
> > >> Compilers Hacker, Node.js Core Collaborator and Speaker
> > >>
> > >> _______________________________________________
> > >> calsify mailing list
> > >> calsify@ietf.org <mailto:calsify@ietf.org>
> > >> https://www.ietf.org/mailman/listinfo/calsify
> > >> <https://www.ietf.org/mailman/listinfo/calsify>
> > >>
> > >
> > > --
> > >   Bron Gondwana, CEO, Fastmail Pty Ltd
> > >   brong@fastmailteam.com
> > >
> > >
> > >
> > > _______________________________________________
> > > calsify mailing list
> > > calsify@ietf.org
> > > https://www.ietf.org/mailman/listinfo/calsify
> > >
> >
> > --
> > Ujjwal "Ryzokuken" Sharma (he/him)
> >
> > Compilers Hacker, Node.js Core Collaborator and Speaker
> >
> > _______________________________________________
> > calsify mailing list
> > calsify@ietf.org
> > https://www.ietf.org/mailman/listinfo/calsify
> >
> >
> > --
> >   Bron Gondwana, CEO, Fastmail Pty Ltd
> >   brong@fastmailteam.com
> >
> >
> > _______________________________________________
> > calsify mailing list
> > calsify@ietf.org
> > https://www.ietf.org/mailman/listinfo/calsify
> >
> >
> > Attachments:
> >
> > signature.asc
> >
> >
> > --
> >   Bron Gondwana, CEO, Fastmail Pty Ltd
> >   brong@fastmailteam.com
> >
> >
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>

--00000000000093af2205b9c6f1e7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thanks everyone for the thoughtful responses.</div><d=
iv><br></div><div>At this point, I have seen three general types of concern=
s over Ujjwal&#39;s=C2=A0proposal:</div><div><br></div><div>1) Concerns tha=
t we need to spend more time exploring the space before jumping into a solu=
tion</div><div>2) Concerns over compatibility with systems that want a stan=
dalone timezone syntax without Ujjwal&#39;s annotations</div><div>3) Propos=
ition that we should standardize a JSON/YANG schema before a string syntax<=
/div><div><br></div><div>My responses:</div><div><br></div><div>1)=C2=A0Ujj=
wal&#39;s=C2=A0proposal is the result of quite a bit of work within ECMA-TC=
39 and=C2=A0liaising=C2=A0with some folks in the Unicode Consortium.=C2=A0 =
I worry that chartering a new working group would duplicate much of the wor=
k that has already gone into this proposal (not to mention setting ECMA bac=
k further).</div><div><br></div><div>2) Two very clear paths forward have b=
een presented: publish the proposal as a new RFC, and then either keep 3339=
 the way it is, or publish a successor to 3339 with 6-digit years but no an=
notations.</div><div><br></div><div>3) I discussed earlier why I feel a str=
ing syntax is warranted.=C2=A0 I&#39;m happy to continue this discussion if=
 we can narrow it down to this point of contention.</div><div><br></div><di=
v>Shane</div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021 at 3:07 PM Barry Leiba &=
lt;<a href=3D"mailto:barryleiba@computer.org">barryleiba@computer.org</a>&g=
t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">First,=
 everyone, meet Francesca Palombini (added on CC), who will be<br>
your new AD starting in March.<br>
<br>
I do have to agree with Eliot that obsoleting 3339 is well out of<br>
charter for calext.=C2=A0 What you quote below from what you said in<br>
dispatch, &quot;Javascript notation format is looking for a standard<br>
serialisation&quot;, is not the same thing as &quot;revising and obsoleting=
 RFC<br>
3339&quot;.=C2=A0 As Eliot points out, there are ways to include extra<br>
information in jCalendar, for example, without changing the basic<br>
date/time strings that are used in many places.=C2=A0 Changes to the 3339<b=
r>
date/time strings will have ramifications all over the Internet, and I<br>
think that needs its own working group and a lot of publicity to make<br>
sure we&#39;re getting &quot;everyone&quot; who cares about it, rather than=
 doing it<br>
where people think we&#39;re only dealing with calendaring protocols.<br>
<br>
I *am* sorry if this has been frustrating, unfriendly, or otherwise<br>
unpleasant for Ujjwal, and I&#39;m quite sensitive to that.=C2=A0 I&#39;m h=
appy to<br>
help in any way I can, as I know Bron and Eliot (and Francesca) are.<br>
But we can&#39;t just handle this document in an inappropriately light<br>
way... the effect will be too far-reaching, even if exactly the<br>
changes that Ujjwal&#39;s draft suggests should turn out to be perfect.<br>
<br>
Do we think we should be chartering a working group to revise and<br>
obsolete RFC 3339?=C2=A0 If so, let&#39;s get a draft charter for that and =
get<br>
the process started.=C2=A0 Do we need a standard JSON wrapper around what<b=
r>
3339 specifies, either as a stop-gap or as a permanent solution?=C2=A0 Then=
<br>
maybe calext is the place to do that, and let&#39;s shift to working on<br>
that.<br>
<br>
Barry, ART AD<br>
<br>
On Sun, Jan 24, 2021 at 5:53 AM Bron Gondwana &lt;<a href=3D"mailto:brong@f=
astmailteam.com" target=3D"_blank">brong@fastmailteam.com</a>&gt; wrote:<br=
>
&gt;<br>
&gt; I&#39;ll ask you the same question I asked Ned, which is &quot;do you =
object to this work being taken up by the IETF at all, or just to it obsole=
ting 3339?&quot;<br>
&gt;<br>
&gt; I will also point out that for all that we&#39;ve talked about making =
the IETF more welcoming to newcomers, this has been a really unfriendly exp=
erience for Ujjwal.=C2=A0 Maybe that&#39;s my fault, but I&#39;m sorry Ujjw=
al for misleading you if so.=C2=A0 I did raise that this work was coming in=
 the &quot;any other business&quot; at IETF110&#39;s DISPATCH, but without =
a draft there was very little guidance.=C2=A0 Indeed the minutes of last di=
spatch say:<br>
&gt;<br>
&gt; Bron Gondwana: RFC3339 extension<br>
&gt; * Javascript notation format is looking for a standard serialisation.<=
br>
&gt;<br>
&gt; Harald Alvestrand:<br>
&gt; * We should have done this in the 90s!=C2=A0 It was a mistake not to d=
o it then.<br>
&gt;<br>
&gt; Neil Jenkins:<br>
&gt; * we do need a serialisation format<br>
&gt;<br>
&gt; Where to discuss: calsify or tzdata lists, but probably calsify is bes=
t.<br>
&gt;<br>
&gt;<br>
&gt; You can watch a video of the exact discussion here: <a href=3D"https:/=
/youtu.be/d871MoUgAKU?t=3D6418" rel=3D"noreferrer" target=3D"_blank">https:=
//youtu.be/d871MoUgAKU?t=3D6418</a><br>
&gt;<br>
&gt; ...<br>
&gt;<br>
&gt; Regardless, it appears that the right next venue for this document is =
DISPATCH at IETF110.<br>
&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt; Bron.<br>
&gt;<br>
&gt; On Sun, Jan 24, 2021, at 21:32, Eliot Lear wrote:<br>
&gt;<br>
&gt; Bron,<br>
&gt;<br>
&gt; I=E2=80=99m sorry, but I have both substantive and procedural problems=
 with you moving forward like this.=C2=A0 Let me start with the procedural.=
=C2=A0 This work isn=E2=80=99t in calext=E2=80=99s charter.=C2=A0 You are s=
pecifically chartered to tackle several extensions to the iCalendar format,=
 and that is it.=C2=A0 This is not an extension to that format.=C2=A0 This =
is a change to a standard that is used extremely broadly.<br>
&gt;<br>
&gt; And this leads me to the substantive concern: this change is backward =
incompatible with=C2=A0 3339.=C2=A0 The ABNF in 3339 is clear: the stamp en=
ds &quot;time-offset&quot; (&quot;Z&quot; / time-numoffset).=C2=A0 Adding =
=E2=80=9Csuffix&quot; blow up in any yacc/bison-based parser and who knows =
what else.=C2=A0 Just imagine all the perl, awk, php, and python that whack=
s this stuff.<br>
&gt;<br>
&gt; In a great many cases, there is no means to negotiate the extension.=
=C2=A0 Let me give you two examples:<br>
&gt;<br>
&gt; Logging software commonly uses 3339 both for generation and for parsin=
g, and the parsers themselves are notoriously fragile to the point that I d=
o not believe any of them would entertain any changes to 3339.=C2=A0 The ec=
osystem is so vast that there is no hope of enumerating it.=C2=A0 To test t=
his, imagine what damage changing any other field to syslog would cause.<br=
>
&gt; Calendaring software, though in a smaller ecosystem, will have older v=
ersions that may well fail to parse.<br>
&gt;<br>
&gt;<br>
&gt; I am not saying that 3339 can never be updated, but before it is, it s=
hould be clear that (a) it is broadly needed, not just by calendaring, and =
(b) that there is reason to believe that the change will be broadly adopted=
, again not just by calendaring.=C2=A0 If it=E2=80=99s just the calendaring=
 ecosystem, you have properties and parameters to use.<br>
&gt;<br>
&gt; Eliot<br>
&gt;<br>
&gt;<br>
&gt; On 24 Jan 2021, at 04:15, Bron Gondwana &lt;<a href=3D"mailto:brong@fa=
stmailteam.com" target=3D"_blank">brong@fastmailteam.com</a>&gt; wrote:<br>
&gt;<br>
&gt; The document is plenty complete enough for a call for adoption!=C2=A0 =
I shall do so now.<br>
&gt;<br>
&gt; You are exactly correct that it&#39;s possible to do further iteration=
 after adoption.<br>
&gt;<br>
&gt; Thanks,<br>
&gt;<br>
&gt; Bron.<br>
&gt;<br>
&gt; On Fri, Jan 22, 2021, at 23:19, Ujjwal Sharma wrote:<br>
&gt;<br>
&gt; Hi Bron, CalExt Friends!<br>
&gt;<br>
&gt; I made a new revision of the draft, which shifts the focus to defining=
<br>
&gt; the syntax/format and defers the standardization of the actual key-val=
ue<br>
&gt; pairs to sibling organizations like IANA and Unicode Consortium.<br>
&gt;<br>
&gt; I&#39;d love to hear your opinions on this version, which you can find=
 at<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-e=
xtended/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org=
/doc/draft-ryzokuken-datetime-extended/</a>,<br>
&gt; which can be filed as issues on the GitHub repository or emailed to me=
<br>
&gt; directly. In the meantime, I will address the remaining concerns/polis=
h<br>
&gt; issues like fixing the references section.<br>
&gt;<br>
&gt; How &quot;complete&quot; does the document need to be in order to init=
iate the<br>
&gt; call for adoption? If the current version works, can we start it as so=
on<br>
&gt; as possible? Of course, if my understanding of &quot;adoption&quot; is=
 correct,<br>
&gt; I&#39;d be happy to iterate on the document further after the adoption=
 by<br>
&gt; the WG.<br>
&gt;<br>
&gt; Best,<br>
&gt; Ujjwal<br>
&gt;<br>
&gt; On 14/01/2021 8.34 am, Bron Gondwana wrote:<br>
&gt; &gt; Sounds great.=C2=A0 Let me know :)<br>
&gt; &gt;<br>
&gt; &gt; When we do the call for adoption I&#39;ll also advertise the fact=
 over to<br>
&gt; &gt; the wider IETF - probably dispatch and tzdata lists at least.<br>
&gt; &gt;<br>
&gt; &gt; Cheers,<br>
&gt; &gt;<br>
&gt; &gt; Bron.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On Thu, Jan 14, 2021, at 13:48, Ujjwal Sharma wrote:<br>
&gt; &gt;&gt; Thanks Bron!<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; I&#39;ll make a few more changes, release a 01 version, ask f=
or more<br>
&gt; &gt;&gt; feedback and then let you know, hopefully by the end of this =
week.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Ujjwal<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; On 14/01/2021 7.03 am, Bron Gondwana wrote:<br>
&gt; &gt;&gt; &gt; I can do a call for adoption straight away if you like -=
 the next<br>
&gt; &gt;&gt; &gt; meeting isn&#39;t for a couple of months.<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; Bron.<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:<br>
&gt; &gt;&gt; &gt;&gt; One question: given things move forward smoothly, ho=
w do I proceed?<br>
&gt; &gt;&gt; &gt;&gt; Should I apply for this document to be adopted by th=
e calext WG? I<br>
&gt; &gt;&gt; &gt;&gt; suppose the fastest way to proceed is to present it =
at the next IETF<br>
&gt; &gt;&gt; &gt;&gt; meeting?<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; Ujjwal<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; On 12/01/2021 4.03 am, Ujjwal Sharma wrote:<br>
&gt; &gt;&gt; &gt;&gt; &gt; Hi Calsify folks!<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt; I am sorry for the long delay, I got a little s=
idetracked working on<br>
&gt; &gt;&gt; &gt;&gt; &gt; other things, but I&#39;m happy to inform you a=
ll that I have<br>
&gt; &gt;&gt; something that<br>
&gt; &gt;&gt; &gt;&gt; &gt; resembles a first draft for the updated timesta=
mps RFC.<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt; Here&#39;s where you can find it:<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt; Datatracker:<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ryzoku=
ken-datetime-extended/" rel=3D"noreferrer" target=3D"_blank">https://datatr=
acker.ietf.org/doc/draft-ryzokuken-datetime-extended/</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://datatracker.ietf.org/doc/draft-ryzokuk=
en-datetime-extended/" rel=3D"noreferrer" target=3D"_blank">https://datatra=
cker.ietf.org/doc/draft-ryzokuken-datetime-extended/</a>&gt;<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &lt;<a href=3D"https://datatracker.ietf.org/doc/draft-ryzokuk=
en-datetime-extended/" rel=3D"noreferrer" target=3D"_blank">https://datatra=
cker.ietf.org/doc/draft-ryzokuken-datetime-extended/</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://datatracker.ietf.org/doc/draft-ryzokuk=
en-datetime-extended/" rel=3D"noreferrer" target=3D"_blank">https://datatra=
cker.ietf.org/doc/draft-ryzokuken-datetime-extended/</a>&gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; GitHub: <a href=3D"https://github.com/ryzokuken/draft-ryzokuk=
en-datetime-extended" rel=3D"noreferrer" target=3D"_blank">https://github.c=
om/ryzokuken/draft-ryzokuken-datetime-extended</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://github.com/ryzokuken/draft-ryzokuken-d=
atetime-extended" rel=3D"noreferrer" target=3D"_blank">https://github.com/r=
yzokuken/draft-ryzokuken-datetime-extended</a>&gt;<br>
&gt; &gt;&gt; &gt;&gt; &lt;<a href=3D"https://github.com/ryzokuken/draft-ry=
zokuken-datetime-extended" rel=3D"noreferrer" target=3D"_blank">https://git=
hub.com/ryzokuken/draft-ryzokuken-datetime-extended</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://github.com/ryzokuken/draft-ryzokuken-d=
atetime-extended" rel=3D"noreferrer" target=3D"_blank">https://github.com/r=
yzokuken/draft-ryzokuken-datetime-extended</a>&gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt; I would request you all to take a look at it wh=
en you can and let me<br>
&gt; &gt;&gt; &gt;&gt; &gt; know what you think. You can file a GitHub issu=
e or email me<br>
&gt; &gt;&gt; directly.<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt; There&#39;s a few open discussions regarding th=
e exact format and how the<br>
&gt; &gt;&gt; &gt;&gt; &gt; interaction with bodies like the Unicode consor=
tium work, so<br>
&gt; &gt;&gt; please feel<br>
&gt; &gt;&gt; &gt;&gt; &gt; free to send me your thoughts regarding that as=
 well.<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt; Also, some references/bibliography is not perfe=
ctly functional yet<br>
&gt; &gt;&gt; &gt;&gt; &gt; because I am still relatively new to authoring =
RFCs using<br>
&gt; &gt;&gt; Metanorma but<br>
&gt; &gt;&gt; &gt;&gt; &gt; I&#39;m actively looking into it.<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt; Thanks and looking forward to hear from you,<br=
>
&gt; &gt;&gt; &gt;&gt; &gt; Ujjwal<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; --<br>
&gt; &gt;&gt; &gt;&gt; Ujjwal &quot;Ryzokuken&quot; Sharma (he/him)<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; Compilers Hacker, Node.js Core Collaborator and Spea=
ker<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; _______________________________________________<br>
&gt; &gt;&gt; &gt;&gt; calsify mailing list<br>
&gt; &gt;&gt; &gt;&gt; <a href=3D"mailto:calsify@ietf.org" target=3D"_blank=
">calsify@ietf.org</a> &lt;mailto:<a href=3D"mailto:calsify@ietf.org" targe=
t=3D"_blank">calsify@ietf.org</a>&gt; &lt;mailto:<a href=3D"mailto:calsify@=
ietf.org" target=3D"_blank">calsify@ietf.org</a><br>
&gt; &gt;&gt; &lt;mailto:<a href=3D"mailto:calsify@ietf.org" target=3D"_bla=
nk">calsify@ietf.org</a>&gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/cal=
sify" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/lis=
tinfo/calsify</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify"=
 rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo=
/calsify</a>&gt;<br>
&gt; &gt;&gt; &gt;&gt; &lt;<a href=3D"https://www.ietf.org/mailman/listinfo=
/calsify" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman=
/listinfo/calsify</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify"=
 rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo=
/calsify</a>&gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; --<br>
&gt; &gt;&gt; &gt;=C2=A0 =C2=A0Bron Gondwana, CEO, Fastmail Pty Ltd<br>
&gt; &gt;&gt; &gt;=C2=A0 =C2=A0<a href=3D"mailto:brong@fastmailteam.com" ta=
rget=3D"_blank">brong@fastmailteam.com</a> &lt;mailto:<a href=3D"mailto:bro=
ng@fastmailteam.com" target=3D"_blank">brong@fastmailteam.com</a>&gt;<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; _______________________________________________<br>
&gt; &gt;&gt; &gt; calsify mailing list<br>
&gt; &gt;&gt; &gt; <a href=3D"mailto:calsify@ietf.org" target=3D"_blank">ca=
lsify@ietf.org</a> &lt;mailto:<a href=3D"mailto:calsify@ietf.org" target=3D=
"_blank">calsify@ietf.org</a>&gt;<br>
&gt; &gt;&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/calsify=
" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinf=
o/calsify</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify"=
 rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo=
/calsify</a>&gt;<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; --<br>
&gt; &gt;&gt; Ujjwal &quot;Ryzokuken&quot; Sharma (he/him)<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Compilers Hacker, Node.js Core Collaborator and Speaker<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; _______________________________________________<br>
&gt; &gt;&gt; calsify mailing list<br>
&gt; &gt;&gt; <a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify=
@ietf.org</a> &lt;mailto:<a href=3D"mailto:calsify@ietf.org" target=3D"_bla=
nk">calsify@ietf.org</a>&gt;<br>
&gt; &gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/calsify" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/cal=
sify</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify"=
 rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo=
/calsify</a>&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt;=C2=A0 =C2=A0Bron Gondwana, CEO, Fastmail Pty Ltd<br>
&gt; &gt;=C2=A0 =C2=A0<a href=3D"mailto:brong@fastmailteam.com" target=3D"_=
blank">brong@fastmailteam.com</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; calsify mailing list<br>
&gt; &gt; <a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify@iet=
f.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/calsify" rel=3D"=
noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/calsify=
</a><br>
&gt; &gt;<br>
&gt;<br>
&gt; --<br>
&gt; Ujjwal &quot;Ryzokuken&quot; Sharma (he/him)<br>
&gt;<br>
&gt; Compilers Hacker, Node.js Core Collaborator and Speaker<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; calsify mailing list<br>
&gt; <a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify@ietf.org=
</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/calsify" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/calsify</a><=
br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt;=C2=A0 =C2=A0Bron Gondwana, CEO, Fastmail Pty Ltd<br>
&gt;=C2=A0 =C2=A0<a href=3D"mailto:brong@fastmailteam.com" target=3D"_blank=
">brong@fastmailteam.com</a><br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; calsify mailing list<br>
&gt; <a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify@ietf.org=
</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/calsify" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/calsify</a><=
br>
&gt;<br>
&gt;<br>
&gt; Attachments:<br>
&gt;<br>
&gt; signature.asc<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt;=C2=A0 =C2=A0Bron Gondwana, CEO, Fastmail Pty Ltd<br>
&gt;=C2=A0 =C2=A0<a href=3D"mailto:brong@fastmailteam.com" target=3D"_blank=
">brong@fastmailteam.com</a><br>
&gt;<br>
&gt;<br>
<br>
_______________________________________________<br>
calsify mailing list<br>
<a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/calsify" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/calsify</a><br>
</blockquote></div>

--00000000000093af2205b9c6f1e7--


From nobody Mon Jan 25 23:04:39 2021
Return-Path: <lear@cisco.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DD543A1C34 for <calsify@ietfa.amsl.com>; Mon, 25 Jan 2021 23:04:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.701
X-Spam-Level: 
X-Spam-Status: No, score=-7.701 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PN8hnzEE9WLj for <calsify@ietfa.amsl.com>; Mon, 25 Jan 2021 23:04:35 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 755913A097E for <calsify@ietf.org>; Mon, 25 Jan 2021 23:04:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1235; q=dns/txt; s=iport; t=1611644674; x=1612854274; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=/+i0tQ+CRwHrBREGF+U4zuKAdEhR6o4IJsl+9G6Ln48=; b=JiRENDb70sa+hcFyO/1KvJQkP55Emj0gFrUGb86hN+PVNsGomEUHhMIc fA+rE54RR75/OrEAHFEuIGb2FlSPGXJ7wZPTPJBbjejTRxwuOyAl6DNXx Zxt0vvwzmWdwhYDJgMCYAhrO+zK6aOL4KpVdcSDQI2gsc8JPfClyCSx1M Q=;
X-Files: signature.asc : 488
X-IPAS-Result: =?us-ascii?q?A0D0AgDZvQ9gjBbLJq1iHAEBAQEBAQcBARIBAQQEAQFAg?= =?us-ascii?q?U+DeAEgEo1ziDAokFKLbwQHAQEBCgMBAS8EAQGESgKBeSY4EwIDAQEBAwIDA?= =?us-ascii?q?QEBAQUBAQECAQYEFAEBAQGGRoV0AQQBeRALRlcGgzkBgmYgsW50gTSFWYR6E?= =?us-ascii?q?IE4gVOLa0GCAIE4DBCCVj6IC4IsBIMsnzycMoMBgymBN5cPAxYJgxkBn16yB?= =?us-ascii?q?INwAgQGBQIWgW0hgVkzGggbFWUBgj89EhkNjjuOMEADZwIGCgEBAwmMFQEB?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.79,375,1602547200";  d="asc'?scan'208";a="32946405"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Jan 2021 07:04:30 +0000
Received: from dhcp-10-61-106-5.cisco.com (dhcp-10-61-106-5.cisco.com [10.61.106.5]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 10Q74Tnd032210 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 26 Jan 2021 07:04:30 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <E5D7F7C1-D54C-4DD6-8337-83F8E196E283@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_D3A1E657-A101-4CAF-A1F2-EF61DD3A1ECD"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Tue, 26 Jan 2021 08:04:28 +0100
In-Reply-To: <CALaySJJPQ0zENWrd-JfthujCjPNcq7aNoDaxtFV7pehAOi5CjQ@mail.gmail.com>
Cc: Bron Gondwana <brong@fastmailteam.com>, calsify@ietf.org, Francesca Palombini <francesca.palombini@ericsson.com>
To: Barry Leiba <barryleiba@computer.org>
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <0275d5af-6eea-4608-913e-c96d59c0abea@dogfood.fastmail.com> <c87c068b-02f1-913a-64ef-497f827fc3ea@igalia.com> <27ae33c7-d5cf-428b-99fa-7b974be85e70@dogfood.fastmail.com> <AAD5976B-A601-45AC-9E43-CEB24D57BD1E@cisco.com> <fd342b5e-d998-487e-8fa2-5dd949b517e8@dogfood.fastmail.com> <CALaySJJPQ0zENWrd-JfthujCjPNcq7aNoDaxtFV7pehAOi5CjQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
X-Outbound-SMTP-Client: 10.61.106.5, dhcp-10-61-106-5.cisco.com
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/a8YykLG_Bi6e9wbv4r5QEOF_TgQ>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2021 07:04:38 -0000

--Apple-Mail=_D3A1E657-A101-4CAF-A1F2-EF61DD3A1ECD
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Just to add...

> 
> I *am* sorry if this has been frustrating, unfriendly, or otherwise
> unpleasant for Ujjwal, and I'm quite sensitive to that.  I'm happy to
> help in any way I can, as I know Bron and Eliot (and Francesca) are.

^^^
Absolutely, for my part.

Eliot



--Apple-Mail=_D3A1E657-A101-4CAF-A1F2-EF61DD3A1ECD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAmAPvvwACgkQh7ZrRtnS
ejPS8ggAkJMcsAtRDORzXkAxhVR9rSFBnZ5X7+m0UZKzqscAOauVU34rejaRRo8y
U/oPkqKLUUl2PUMpLmApVAZGD2NEqsUNWiw897hihRLy41eIX5B96XB1h8DK5JJl
XouxkYpsuqlonyJEY5dWNdHiaOo19x9iTvbOc93uRamlOz0Alnraqr52zV3oZQIk
NFxG0MF35usiAoxdGGOTYOUvS4osb/PH9/UTtWQ/Jb8ljqKAP4rO5z1ELKgni2e5
QG/j0X1NgH57b8Xqan0KDL3PWQDCQ2zRYVdwgRBeodPiEmrn7/J9mYnJ2q73bDC4
DDRiTpoD+xmGnG7YxtDI2OPqe3mCxA==
=FnpH
-----END PGP SIGNATURE-----

--Apple-Mail=_D3A1E657-A101-4CAF-A1F2-EF61DD3A1ECD--


From nobody Mon Jan 25 23:06:46 2021
Return-Path: <sffc@google.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A22A53A1C9F for <calsify@ietfa.amsl.com>; Mon, 25 Jan 2021 23:06:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.699
X-Spam-Level: 
X-Spam-Status: No, score=-15.699 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id seAWUsdptMKW for <calsify@ietfa.amsl.com>; Mon, 25 Jan 2021 23:06:42 -0800 (PST)
Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 363DD3A1C34 for <calsify@ietf.org>; Mon, 25 Jan 2021 23:06:42 -0800 (PST)
Received: by mail-ot1-x32d.google.com with SMTP id s2so13154409otp.5 for <calsify@ietf.org>; Mon, 25 Jan 2021 23:06:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sryQFS38w2RoFMW4Tv4aDFEzNBPA9VduveqXMs1h2iA=; b=hTpF8rBzhy7ZjjmfMPA24Awbl2Ytx89km1Bd2ufnHlDpRu9N3vrZZrr2HeprGvAhsh NVggUpDyqY1nQ9g5AJFk6TC4kE+IKAI11/k9rclMU/0NfHrIw0auOxLY0zEvJSZbIf8T PWqAtcOmS/eA8OOiGmeQZuA1KupNiRFYbGWFy80LEKxuf4ApzeLGDU/vg41oH4KKAa6h dqxtGp2C0E+VVXLrq0iCYo/gajzTk7NG/GJI3mZIlgZ6KkflQZYMW4mYEyc6jW6mxzO6 UULfNVNaKuM9M9hZUTf6VdQnLeXobydGGy82iPD0TpaQjl2smMnXFkOFGnwIAO7LzhzY 863A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sryQFS38w2RoFMW4Tv4aDFEzNBPA9VduveqXMs1h2iA=; b=MLCpB6IAJE9XQrI0Uf/8CE+n/8jiE6+JR7V9RIksNUsEz4+OkS1SXGnAAzIeSRPstt c2dmEt3hQ/MY9gGUcp6wt9OKdEt1BAGe9mXGtaO9ZK1n7ZEAs/If4ASkbeCfzv/JXoUH QFLMTYknzM3YTtne9+JXW0/JdVIB7S5NWsxr99aqGJ+66NTzutfL75qTh+AKbc89oSsG mvffywa3aOWHLWsHbm9PCI735/t/KfanLoBPKy+bmT2/HUUz+h7KV2T8TCKTdsQF+DSs OqxlbvobiB8gk0tUQhk96c/rX6XfTwJC63pFm1QV9rgRAK4pLpn88CPTG5IL7QRkjWaM zjsQ==
X-Gm-Message-State: AOAM5326jLj6nipJcDErw+sfmeI53I+1AFtBH/o8n3yvPdRmx2tdW6RN ayrn7uyEktr3oV+FsSBV0j7Sdj6IyXdPeAn7hxECTg==
X-Google-Smtp-Source: ABdhPJzb5680NC3HWYkWNpPhMAiEB/YNP+KuP0Vwo2sxxelAz3ip0fbx3RO5Wo1NWLevOYh6AVAIy9gZ+Vq/zZSKNg4=
X-Received: by 2002:a9d:4d8f:: with SMTP id u15mr3110736otk.83.1611644801018;  Mon, 25 Jan 2021 23:06:41 -0800 (PST)
MIME-Version: 1.0
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <0275d5af-6eea-4608-913e-c96d59c0abea@dogfood.fastmail.com> <c87c068b-02f1-913a-64ef-497f827fc3ea@igalia.com> <27ae33c7-d5cf-428b-99fa-7b974be85e70@dogfood.fastmail.com> <AAD5976B-A601-45AC-9E43-CEB24D57BD1E@cisco.com> <fd342b5e-d998-487e-8fa2-5dd949b517e8@dogfood.fastmail.com> <CALaySJJPQ0zENWrd-JfthujCjPNcq7aNoDaxtFV7pehAOi5CjQ@mail.gmail.com> <CABxsp==sPd3Uj45caWojyp=WEng5_DGTnjFzJ7x0enXWFjp4+w@mail.gmail.com>
In-Reply-To: <CABxsp==sPd3Uj45caWojyp=WEng5_DGTnjFzJ7x0enXWFjp4+w@mail.gmail.com>
From: Shane Carr <sffc@google.com>
Date: Tue, 26 Jan 2021 01:06:28 -0600
Message-ID: <CABxsp=nN3W3pTe91_iKkhsk4ATy+r9YaZbhxDWbPb+e0rDA_Uw@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: Bron Gondwana <brong@fastmailteam.com>,  Francesca Palombini <francesca.palombini@ericsson.com>, calsify@ietf.org
Content-Type: multipart/alternative; boundary="000000000000dec68705b9c84b6e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/MTtzJPhO2Ztq_z-lA_cVZISd8Nk>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2021 07:06:46 -0000

--000000000000dec68705b9c84b6e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Correction: item 2 should say "standalone timestamp syntax", not
"standalone timezone syntax".

On Mon, Jan 25, 2021 at 11:29 PM Shane Carr <sffc@google.com> wrote:

> Thanks everyone for the thoughtful responses.
>
> At this point, I have seen three general types of concerns over
> Ujjwal's proposal:
>
> 1) Concerns that we need to spend more time exploring the space before
> jumping into a solution
> 2) Concerns over compatibility with systems that want a standalone
> timezone syntax without Ujjwal's annotations
> 3) Proposition that we should standardize a JSON/YANG schema before a
> string syntax
>
> My responses:
>
> 1) Ujjwal's proposal is the result of quite a bit of work within ECMA-TC3=
9
> and liaising with some folks in the Unicode Consortium.  I worry that
> chartering a new working group would duplicate much of the work that has
> already gone into this proposal (not to mention setting ECMA back further=
).
>
> 2) Two very clear paths forward have been presented: publish the proposal
> as a new RFC, and then either keep 3339 the way it is, or publish a
> successor to 3339 with 6-digit years but no annotations.
>
> 3) I discussed earlier why I feel a string syntax is warranted.  I'm happ=
y
> to continue this discussion if we can narrow it down to this point of
> contention.
>
> Shane
>
>
> On Mon, Jan 25, 2021 at 3:07 PM Barry Leiba <barryleiba@computer.org>
> wrote:
>
>> First, everyone, meet Francesca Palombini (added on CC), who will be
>> your new AD starting in March.
>>
>> I do have to agree with Eliot that obsoleting 3339 is well out of
>> charter for calext.  What you quote below from what you said in
>> dispatch, "Javascript notation format is looking for a standard
>> serialisation", is not the same thing as "revising and obsoleting RFC
>> 3339".  As Eliot points out, there are ways to include extra
>> information in jCalendar, for example, without changing the basic
>> date/time strings that are used in many places.  Changes to the 3339
>> date/time strings will have ramifications all over the Internet, and I
>> think that needs its own working group and a lot of publicity to make
>> sure we're getting "everyone" who cares about it, rather than doing it
>> where people think we're only dealing with calendaring protocols.
>>
>> I *am* sorry if this has been frustrating, unfriendly, or otherwise
>> unpleasant for Ujjwal, and I'm quite sensitive to that.  I'm happy to
>> help in any way I can, as I know Bron and Eliot (and Francesca) are.
>> But we can't just handle this document in an inappropriately light
>> way... the effect will be too far-reaching, even if exactly the
>> changes that Ujjwal's draft suggests should turn out to be perfect.
>>
>> Do we think we should be chartering a working group to revise and
>> obsolete RFC 3339?  If so, let's get a draft charter for that and get
>> the process started.  Do we need a standard JSON wrapper around what
>> 3339 specifies, either as a stop-gap or as a permanent solution?  Then
>> maybe calext is the place to do that, and let's shift to working on
>> that.
>>
>> Barry, ART AD
>>
>> On Sun, Jan 24, 2021 at 5:53 AM Bron Gondwana <brong@fastmailteam.com>
>> wrote:
>> >
>> > I'll ask you the same question I asked Ned, which is "do you object to
>> this work being taken up by the IETF at all, or just to it obsoleting 33=
39?"
>> >
>> > I will also point out that for all that we've talked about making the
>> IETF more welcoming to newcomers, this has been a really unfriendly
>> experience for Ujjwal.  Maybe that's my fault, but I'm sorry Ujjwal for
>> misleading you if so.  I did raise that this work was coming in the "any
>> other business" at IETF110's DISPATCH, but without a draft there was ver=
y
>> little guidance.  Indeed the minutes of last dispatch say:
>> >
>> > Bron Gondwana: RFC3339 extension
>> > * Javascript notation format is looking for a standard serialisation.
>> >
>> > Harald Alvestrand:
>> > * We should have done this in the 90s!  It was a mistake not to do it
>> then.
>> >
>> > Neil Jenkins:
>> > * we do need a serialisation format
>> >
>> > Where to discuss: calsify or tzdata lists, but probably calsify is bes=
t.
>> >
>> >
>> > You can watch a video of the exact discussion here:
>> https://youtu.be/d871MoUgAKU?t=3D6418
>> >
>> > ...
>> >
>> > Regardless, it appears that the right next venue for this document is
>> DISPATCH at IETF110.
>> >
>> > Regards,
>> >
>> > Bron.
>> >
>> > On Sun, Jan 24, 2021, at 21:32, Eliot Lear wrote:
>> >
>> > Bron,
>> >
>> > I=E2=80=99m sorry, but I have both substantive and procedural problems=
 with you
>> moving forward like this.  Let me start with the procedural.  This work
>> isn=E2=80=99t in calext=E2=80=99s charter.  You are specifically charter=
ed to tackle
>> several extensions to the iCalendar format, and that is it.  This is not=
 an
>> extension to that format.  This is a change to a standard that is used
>> extremely broadly.
>> >
>> > And this leads me to the substantive concern: this change is backward
>> incompatible with  3339.  The ABNF in 3339 is clear: the stamp ends
>> "time-offset" ("Z" / time-numoffset).  Adding =E2=80=9Csuffix" blow up i=
n any
>> yacc/bison-based parser and who knows what else.  Just imagine all the
>> perl, awk, php, and python that whacks this stuff.
>> >
>> > In a great many cases, there is no means to negotiate the extension.
>> Let me give you two examples:
>> >
>> > Logging software commonly uses 3339 both for generation and for
>> parsing, and the parsers themselves are notoriously fragile to the point
>> that I do not believe any of them would entertain any changes to 3339.  =
The
>> ecosystem is so vast that there is no hope of enumerating it.  To test
>> this, imagine what damage changing any other field to syslog would cause=
.
>> > Calendaring software, though in a smaller ecosystem, will have older
>> versions that may well fail to parse.
>> >
>> >
>> > I am not saying that 3339 can never be updated, but before it is, it
>> should be clear that (a) it is broadly needed, not just by calendaring, =
and
>> (b) that there is reason to believe that the change will be broadly
>> adopted, again not just by calendaring.  If it=E2=80=99s just the calend=
aring
>> ecosystem, you have properties and parameters to use.
>> >
>> > Eliot
>> >
>> >
>> > On 24 Jan 2021, at 04:15, Bron Gondwana <brong@fastmailteam.com> wrote=
:
>> >
>> > The document is plenty complete enough for a call for adoption!  I
>> shall do so now.
>> >
>> > You are exactly correct that it's possible to do further iteration
>> after adoption.
>> >
>> > Thanks,
>> >
>> > Bron.
>> >
>> > On Fri, Jan 22, 2021, at 23:19, Ujjwal Sharma wrote:
>> >
>> > Hi Bron, CalExt Friends!
>> >
>> > I made a new revision of the draft, which shifts the focus to defining
>> > the syntax/format and defers the standardization of the actual key-val=
ue
>> > pairs to sibling organizations like IANA and Unicode Consortium.
>> >
>> > I'd love to hear your opinions on this version, which you can find at
>> > https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/,
>> > which can be filed as issues on the GitHub repository or emailed to me
>> > directly. In the meantime, I will address the remaining concerns/polis=
h
>> > issues like fixing the references section.
>> >
>> > How "complete" does the document need to be in order to initiate the
>> > call for adoption? If the current version works, can we start it as so=
on
>> > as possible? Of course, if my understanding of "adoption" is correct,
>> > I'd be happy to iterate on the document further after the adoption by
>> > the WG.
>> >
>> > Best,
>> > Ujjwal
>> >
>> > On 14/01/2021 8.34 am, Bron Gondwana wrote:
>> > > Sounds great.  Let me know :)
>> > >
>> > > When we do the call for adoption I'll also advertise the fact over t=
o
>> > > the wider IETF - probably dispatch and tzdata lists at least.
>> > >
>> > > Cheers,
>> > >
>> > > Bron.
>> > >
>> > >
>> > > On Thu, Jan 14, 2021, at 13:48, Ujjwal Sharma wrote:
>> > >> Thanks Bron!
>> > >>
>> > >> I'll make a few more changes, release a 01 version, ask for more
>> > >> feedback and then let you know, hopefully by the end of this week.
>> > >>
>> > >> Ujjwal
>> > >>
>> > >> On 14/01/2021 7.03 am, Bron Gondwana wrote:
>> > >> > I can do a call for adoption straight away if you like - the next
>> > >> > meeting isn't for a couple of months.
>> > >> >
>> > >> > Bron.
>> > >> >
>> > >> > On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:
>> > >> >> One question: given things move forward smoothly, how do I
>> proceed?
>> > >> >> Should I apply for this document to be adopted by the calext WG?=
 I
>> > >> >> suppose the fastest way to proceed is to present it at the next
>> IETF
>> > >> >> meeting?
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >> Ujjwal
>> > >> >>
>> > >> >> On 12/01/2021 4.03 am, Ujjwal Sharma wrote:
>> > >> >> > Hi Calsify folks!
>> > >> >> >
>> > >> >> > I am sorry for the long delay, I got a little sidetracked
>> working on
>> > >> >> > other things, but I'm happy to inform you all that I have
>> > >> something that
>> > >> >> > resembles a first draft for the updated timestamps RFC.
>> > >> >> >
>> > >> >> > Here's where you can find it:
>> > >> >> >
>> > >> >> > Datatracker:
>> > >> >>
>> > >> >
>> https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
>> > >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended=
/
>> >
>> > >> >>
>> > >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended=
/
>> > >> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended=
/
>> >>
>> > >> >> >
>> > >> >>
>> > >> GitHub:
>> https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
>> > >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>
>> > >> >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
>> > >> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>>
>> > >> >> >
>> > >> >> > I would request you all to take a look at it when you can and
>> let me
>> > >> >> > know what you think. You can file a GitHub issue or email me
>> > >> directly.
>> > >> >> >
>> > >> >> > There's a few open discussions regarding the exact format and
>> how the
>> > >> >> > interaction with bodies like the Unicode consortium work, so
>> > >> please feel
>> > >> >> > free to send me your thoughts regarding that as well.
>> > >> >> >
>> > >> >> > Also, some references/bibliography is not perfectly functional
>> yet
>> > >> >> > because I am still relatively new to authoring RFCs using
>> > >> Metanorma but
>> > >> >> > I'm actively looking into it.
>> > >> >> >
>> > >> >> > Thanks and looking forward to hear from you,
>> > >> >> > Ujjwal
>> > >> >> >
>> > >> >>
>> > >> >> --
>> > >> >> Ujjwal "Ryzokuken" Sharma (he/him)
>> > >> >>
>> > >> >> Compilers Hacker, Node.js Core Collaborator and Speaker
>> > >> >>
>> > >> >> _______________________________________________
>> > >> >> calsify mailing list
>> > >> >> calsify@ietf.org <mailto:calsify@ietf.org> <mailto:
>> calsify@ietf.org
>> > >> <mailto:calsify@ietf.org>>
>> > >> >> https://www.ietf.org/mailman/listinfo/calsify
>> > >> <https://www.ietf.org/mailman/listinfo/calsify>
>> > >> >> <https://www.ietf.org/mailman/listinfo/calsify
>> > >> <https://www.ietf.org/mailman/listinfo/calsify>>
>> > >> >>
>> > >> >
>> > >> > --
>> > >> >   Bron Gondwana, CEO, Fastmail Pty Ltd
>> > >> >   brong@fastmailteam.com <mailto:brong@fastmailteam.com>
>> > >> >
>> > >> >
>> > >> > _______________________________________________
>> > >> > calsify mailing list
>> > >> > calsify@ietf.org <mailto:calsify@ietf.org>
>> > >> > https://www.ietf.org/mailman/listinfo/calsify
>> > >> <https://www.ietf.org/mailman/listinfo/calsify>
>> > >> >
>> > >>
>> > >> --
>> > >> Ujjwal "Ryzokuken" Sharma (he/him)
>> > >>
>> > >> Compilers Hacker, Node.js Core Collaborator and Speaker
>> > >>
>> > >> _______________________________________________
>> > >> calsify mailing list
>> > >> calsify@ietf.org <mailto:calsify@ietf.org>
>> > >> https://www.ietf.org/mailman/listinfo/calsify
>> > >> <https://www.ietf.org/mailman/listinfo/calsify>
>> > >>
>> > >
>> > > --
>> > >   Bron Gondwana, CEO, Fastmail Pty Ltd
>> > >   brong@fastmailteam.com
>> > >
>> > >
>> > >
>> > > _______________________________________________
>> > > calsify mailing list
>> > > calsify@ietf.org
>> > > https://www.ietf.org/mailman/listinfo/calsify
>> > >
>> >
>> > --
>> > Ujjwal "Ryzokuken" Sharma (he/him)
>> >
>> > Compilers Hacker, Node.js Core Collaborator and Speaker
>> >
>> > _______________________________________________
>> > calsify mailing list
>> > calsify@ietf.org
>> > https://www.ietf.org/mailman/listinfo/calsify
>> >
>> >
>> > --
>> >   Bron Gondwana, CEO, Fastmail Pty Ltd
>> >   brong@fastmailteam.com
>> >
>> >
>> > _______________________________________________
>> > calsify mailing list
>> > calsify@ietf.org
>> > https://www.ietf.org/mailman/listinfo/calsify
>> >
>> >
>> > Attachments:
>> >
>> > signature.asc
>> >
>> >
>> > --
>> >   Bron Gondwana, CEO, Fastmail Pty Ltd
>> >   brong@fastmailteam.com
>> >
>> >
>>
>> _______________________________________________
>> calsify mailing list
>> calsify@ietf.org
>> https://www.ietf.org/mailman/listinfo/calsify
>>
>

--000000000000dec68705b9c84b6e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Correction: item 2 should say &quot;standalone timestamp s=
yntax&quot;, not &quot;standalone timezone syntax&quot;.</div><br><div clas=
s=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 202=
1 at 11:29 PM Shane Carr &lt;<a href=3D"mailto:sffc@google.com">sffc@google=
.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex"><div dir=3D"ltr"><div>Thanks everyone for the thoughtful responses.</di=
v><div><br></div><div>At this point, I have seen three general types of con=
cerns over Ujjwal&#39;s=C2=A0proposal:</div><div><br></div><div>1) Concerns=
 that we need to spend more time exploring the space before jumping into a =
solution</div><div>2) Concerns over compatibility with systems that want a =
standalone timezone syntax without Ujjwal&#39;s annotations</div><div>3) Pr=
oposition that we should standardize a JSON/YANG schema before a string syn=
tax</div><div><br></div><div>My responses:</div><div><br></div><div>1)=C2=
=A0Ujjwal&#39;s=C2=A0proposal is the result of quite a bit of work within E=
CMA-TC39 and=C2=A0liaising=C2=A0with some folks in the Unicode Consortium.=
=C2=A0 I worry that chartering a new working group would duplicate much of =
the work that has already gone into this proposal (not to mention setting E=
CMA back further).</div><div><br></div><div>2) Two very clear paths forward=
 have been presented: publish the proposal as a new RFC, and then either ke=
ep 3339 the way it is, or publish a successor to 3339 with 6-digit years bu=
t no annotations.</div><div><br></div><div>3) I discussed earlier why I fee=
l a string syntax is warranted.=C2=A0 I&#39;m happy to continue this discus=
sion if we can narrow it down to this point of contention.</div><div><br></=
div><div>Shane</div><div><br></div></div><br><div class=3D"gmail_quote"><di=
v dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021 at 3:07 PM Barry Le=
iba &lt;<a href=3D"mailto:barryleiba@computer.org" target=3D"_blank">barryl=
eiba@computer.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex">First, everyone, meet Francesca Palombini (added on CC), w=
ho will be<br>
your new AD starting in March.<br>
<br>
I do have to agree with Eliot that obsoleting 3339 is well out of<br>
charter for calext.=C2=A0 What you quote below from what you said in<br>
dispatch, &quot;Javascript notation format is looking for a standard<br>
serialisation&quot;, is not the same thing as &quot;revising and obsoleting=
 RFC<br>
3339&quot;.=C2=A0 As Eliot points out, there are ways to include extra<br>
information in jCalendar, for example, without changing the basic<br>
date/time strings that are used in many places.=C2=A0 Changes to the 3339<b=
r>
date/time strings will have ramifications all over the Internet, and I<br>
think that needs its own working group and a lot of publicity to make<br>
sure we&#39;re getting &quot;everyone&quot; who cares about it, rather than=
 doing it<br>
where people think we&#39;re only dealing with calendaring protocols.<br>
<br>
I *am* sorry if this has been frustrating, unfriendly, or otherwise<br>
unpleasant for Ujjwal, and I&#39;m quite sensitive to that.=C2=A0 I&#39;m h=
appy to<br>
help in any way I can, as I know Bron and Eliot (and Francesca) are.<br>
But we can&#39;t just handle this document in an inappropriately light<br>
way... the effect will be too far-reaching, even if exactly the<br>
changes that Ujjwal&#39;s draft suggests should turn out to be perfect.<br>
<br>
Do we think we should be chartering a working group to revise and<br>
obsolete RFC 3339?=C2=A0 If so, let&#39;s get a draft charter for that and =
get<br>
the process started.=C2=A0 Do we need a standard JSON wrapper around what<b=
r>
3339 specifies, either as a stop-gap or as a permanent solution?=C2=A0 Then=
<br>
maybe calext is the place to do that, and let&#39;s shift to working on<br>
that.<br>
<br>
Barry, ART AD<br>
<br>
On Sun, Jan 24, 2021 at 5:53 AM Bron Gondwana &lt;<a href=3D"mailto:brong@f=
astmailteam.com" target=3D"_blank">brong@fastmailteam.com</a>&gt; wrote:<br=
>
&gt;<br>
&gt; I&#39;ll ask you the same question I asked Ned, which is &quot;do you =
object to this work being taken up by the IETF at all, or just to it obsole=
ting 3339?&quot;<br>
&gt;<br>
&gt; I will also point out that for all that we&#39;ve talked about making =
the IETF more welcoming to newcomers, this has been a really unfriendly exp=
erience for Ujjwal.=C2=A0 Maybe that&#39;s my fault, but I&#39;m sorry Ujjw=
al for misleading you if so.=C2=A0 I did raise that this work was coming in=
 the &quot;any other business&quot; at IETF110&#39;s DISPATCH, but without =
a draft there was very little guidance.=C2=A0 Indeed the minutes of last di=
spatch say:<br>
&gt;<br>
&gt; Bron Gondwana: RFC3339 extension<br>
&gt; * Javascript notation format is looking for a standard serialisation.<=
br>
&gt;<br>
&gt; Harald Alvestrand:<br>
&gt; * We should have done this in the 90s!=C2=A0 It was a mistake not to d=
o it then.<br>
&gt;<br>
&gt; Neil Jenkins:<br>
&gt; * we do need a serialisation format<br>
&gt;<br>
&gt; Where to discuss: calsify or tzdata lists, but probably calsify is bes=
t.<br>
&gt;<br>
&gt;<br>
&gt; You can watch a video of the exact discussion here: <a href=3D"https:/=
/youtu.be/d871MoUgAKU?t=3D6418" rel=3D"noreferrer" target=3D"_blank">https:=
//youtu.be/d871MoUgAKU?t=3D6418</a><br>
&gt;<br>
&gt; ...<br>
&gt;<br>
&gt; Regardless, it appears that the right next venue for this document is =
DISPATCH at IETF110.<br>
&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt; Bron.<br>
&gt;<br>
&gt; On Sun, Jan 24, 2021, at 21:32, Eliot Lear wrote:<br>
&gt;<br>
&gt; Bron,<br>
&gt;<br>
&gt; I=E2=80=99m sorry, but I have both substantive and procedural problems=
 with you moving forward like this.=C2=A0 Let me start with the procedural.=
=C2=A0 This work isn=E2=80=99t in calext=E2=80=99s charter.=C2=A0 You are s=
pecifically chartered to tackle several extensions to the iCalendar format,=
 and that is it.=C2=A0 This is not an extension to that format.=C2=A0 This =
is a change to a standard that is used extremely broadly.<br>
&gt;<br>
&gt; And this leads me to the substantive concern: this change is backward =
incompatible with=C2=A0 3339.=C2=A0 The ABNF in 3339 is clear: the stamp en=
ds &quot;time-offset&quot; (&quot;Z&quot; / time-numoffset).=C2=A0 Adding =
=E2=80=9Csuffix&quot; blow up in any yacc/bison-based parser and who knows =
what else.=C2=A0 Just imagine all the perl, awk, php, and python that whack=
s this stuff.<br>
&gt;<br>
&gt; In a great many cases, there is no means to negotiate the extension.=
=C2=A0 Let me give you two examples:<br>
&gt;<br>
&gt; Logging software commonly uses 3339 both for generation and for parsin=
g, and the parsers themselves are notoriously fragile to the point that I d=
o not believe any of them would entertain any changes to 3339.=C2=A0 The ec=
osystem is so vast that there is no hope of enumerating it.=C2=A0 To test t=
his, imagine what damage changing any other field to syslog would cause.<br=
>
&gt; Calendaring software, though in a smaller ecosystem, will have older v=
ersions that may well fail to parse.<br>
&gt;<br>
&gt;<br>
&gt; I am not saying that 3339 can never be updated, but before it is, it s=
hould be clear that (a) it is broadly needed, not just by calendaring, and =
(b) that there is reason to believe that the change will be broadly adopted=
, again not just by calendaring.=C2=A0 If it=E2=80=99s just the calendaring=
 ecosystem, you have properties and parameters to use.<br>
&gt;<br>
&gt; Eliot<br>
&gt;<br>
&gt;<br>
&gt; On 24 Jan 2021, at 04:15, Bron Gondwana &lt;<a href=3D"mailto:brong@fa=
stmailteam.com" target=3D"_blank">brong@fastmailteam.com</a>&gt; wrote:<br>
&gt;<br>
&gt; The document is plenty complete enough for a call for adoption!=C2=A0 =
I shall do so now.<br>
&gt;<br>
&gt; You are exactly correct that it&#39;s possible to do further iteration=
 after adoption.<br>
&gt;<br>
&gt; Thanks,<br>
&gt;<br>
&gt; Bron.<br>
&gt;<br>
&gt; On Fri, Jan 22, 2021, at 23:19, Ujjwal Sharma wrote:<br>
&gt;<br>
&gt; Hi Bron, CalExt Friends!<br>
&gt;<br>
&gt; I made a new revision of the draft, which shifts the focus to defining=
<br>
&gt; the syntax/format and defers the standardization of the actual key-val=
ue<br>
&gt; pairs to sibling organizations like IANA and Unicode Consortium.<br>
&gt;<br>
&gt; I&#39;d love to hear your opinions on this version, which you can find=
 at<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-e=
xtended/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org=
/doc/draft-ryzokuken-datetime-extended/</a>,<br>
&gt; which can be filed as issues on the GitHub repository or emailed to me=
<br>
&gt; directly. In the meantime, I will address the remaining concerns/polis=
h<br>
&gt; issues like fixing the references section.<br>
&gt;<br>
&gt; How &quot;complete&quot; does the document need to be in order to init=
iate the<br>
&gt; call for adoption? If the current version works, can we start it as so=
on<br>
&gt; as possible? Of course, if my understanding of &quot;adoption&quot; is=
 correct,<br>
&gt; I&#39;d be happy to iterate on the document further after the adoption=
 by<br>
&gt; the WG.<br>
&gt;<br>
&gt; Best,<br>
&gt; Ujjwal<br>
&gt;<br>
&gt; On 14/01/2021 8.34 am, Bron Gondwana wrote:<br>
&gt; &gt; Sounds great.=C2=A0 Let me know :)<br>
&gt; &gt;<br>
&gt; &gt; When we do the call for adoption I&#39;ll also advertise the fact=
 over to<br>
&gt; &gt; the wider IETF - probably dispatch and tzdata lists at least.<br>
&gt; &gt;<br>
&gt; &gt; Cheers,<br>
&gt; &gt;<br>
&gt; &gt; Bron.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On Thu, Jan 14, 2021, at 13:48, Ujjwal Sharma wrote:<br>
&gt; &gt;&gt; Thanks Bron!<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; I&#39;ll make a few more changes, release a 01 version, ask f=
or more<br>
&gt; &gt;&gt; feedback and then let you know, hopefully by the end of this =
week.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Ujjwal<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; On 14/01/2021 7.03 am, Bron Gondwana wrote:<br>
&gt; &gt;&gt; &gt; I can do a call for adoption straight away if you like -=
 the next<br>
&gt; &gt;&gt; &gt; meeting isn&#39;t for a couple of months.<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; Bron.<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:<br>
&gt; &gt;&gt; &gt;&gt; One question: given things move forward smoothly, ho=
w do I proceed?<br>
&gt; &gt;&gt; &gt;&gt; Should I apply for this document to be adopted by th=
e calext WG? I<br>
&gt; &gt;&gt; &gt;&gt; suppose the fastest way to proceed is to present it =
at the next IETF<br>
&gt; &gt;&gt; &gt;&gt; meeting?<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; Ujjwal<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; On 12/01/2021 4.03 am, Ujjwal Sharma wrote:<br>
&gt; &gt;&gt; &gt;&gt; &gt; Hi Calsify folks!<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt; I am sorry for the long delay, I got a little s=
idetracked working on<br>
&gt; &gt;&gt; &gt;&gt; &gt; other things, but I&#39;m happy to inform you a=
ll that I have<br>
&gt; &gt;&gt; something that<br>
&gt; &gt;&gt; &gt;&gt; &gt; resembles a first draft for the updated timesta=
mps RFC.<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt; Here&#39;s where you can find it:<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt; Datatracker:<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ryzoku=
ken-datetime-extended/" rel=3D"noreferrer" target=3D"_blank">https://datatr=
acker.ietf.org/doc/draft-ryzokuken-datetime-extended/</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://datatracker.ietf.org/doc/draft-ryzokuk=
en-datetime-extended/" rel=3D"noreferrer" target=3D"_blank">https://datatra=
cker.ietf.org/doc/draft-ryzokuken-datetime-extended/</a>&gt;<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &lt;<a href=3D"https://datatracker.ietf.org/doc/draft-ryzokuk=
en-datetime-extended/" rel=3D"noreferrer" target=3D"_blank">https://datatra=
cker.ietf.org/doc/draft-ryzokuken-datetime-extended/</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://datatracker.ietf.org/doc/draft-ryzokuk=
en-datetime-extended/" rel=3D"noreferrer" target=3D"_blank">https://datatra=
cker.ietf.org/doc/draft-ryzokuken-datetime-extended/</a>&gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; GitHub: <a href=3D"https://github.com/ryzokuken/draft-ryzokuk=
en-datetime-extended" rel=3D"noreferrer" target=3D"_blank">https://github.c=
om/ryzokuken/draft-ryzokuken-datetime-extended</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://github.com/ryzokuken/draft-ryzokuken-d=
atetime-extended" rel=3D"noreferrer" target=3D"_blank">https://github.com/r=
yzokuken/draft-ryzokuken-datetime-extended</a>&gt;<br>
&gt; &gt;&gt; &gt;&gt; &lt;<a href=3D"https://github.com/ryzokuken/draft-ry=
zokuken-datetime-extended" rel=3D"noreferrer" target=3D"_blank">https://git=
hub.com/ryzokuken/draft-ryzokuken-datetime-extended</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://github.com/ryzokuken/draft-ryzokuken-d=
atetime-extended" rel=3D"noreferrer" target=3D"_blank">https://github.com/r=
yzokuken/draft-ryzokuken-datetime-extended</a>&gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt; I would request you all to take a look at it wh=
en you can and let me<br>
&gt; &gt;&gt; &gt;&gt; &gt; know what you think. You can file a GitHub issu=
e or email me<br>
&gt; &gt;&gt; directly.<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt; There&#39;s a few open discussions regarding th=
e exact format and how the<br>
&gt; &gt;&gt; &gt;&gt; &gt; interaction with bodies like the Unicode consor=
tium work, so<br>
&gt; &gt;&gt; please feel<br>
&gt; &gt;&gt; &gt;&gt; &gt; free to send me your thoughts regarding that as=
 well.<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt; Also, some references/bibliography is not perfe=
ctly functional yet<br>
&gt; &gt;&gt; &gt;&gt; &gt; because I am still relatively new to authoring =
RFCs using<br>
&gt; &gt;&gt; Metanorma but<br>
&gt; &gt;&gt; &gt;&gt; &gt; I&#39;m actively looking into it.<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt; &gt; Thanks and looking forward to hear from you,<br=
>
&gt; &gt;&gt; &gt;&gt; &gt; Ujjwal<br>
&gt; &gt;&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; --<br>
&gt; &gt;&gt; &gt;&gt; Ujjwal &quot;Ryzokuken&quot; Sharma (he/him)<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; Compilers Hacker, Node.js Core Collaborator and Spea=
ker<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; _______________________________________________<br>
&gt; &gt;&gt; &gt;&gt; calsify mailing list<br>
&gt; &gt;&gt; &gt;&gt; <a href=3D"mailto:calsify@ietf.org" target=3D"_blank=
">calsify@ietf.org</a> &lt;mailto:<a href=3D"mailto:calsify@ietf.org" targe=
t=3D"_blank">calsify@ietf.org</a>&gt; &lt;mailto:<a href=3D"mailto:calsify@=
ietf.org" target=3D"_blank">calsify@ietf.org</a><br>
&gt; &gt;&gt; &lt;mailto:<a href=3D"mailto:calsify@ietf.org" target=3D"_bla=
nk">calsify@ietf.org</a>&gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/cal=
sify" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/lis=
tinfo/calsify</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify"=
 rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo=
/calsify</a>&gt;<br>
&gt; &gt;&gt; &gt;&gt; &lt;<a href=3D"https://www.ietf.org/mailman/listinfo=
/calsify" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman=
/listinfo/calsify</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify"=
 rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo=
/calsify</a>&gt;&gt;<br>
&gt; &gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; --<br>
&gt; &gt;&gt; &gt;=C2=A0 =C2=A0Bron Gondwana, CEO, Fastmail Pty Ltd<br>
&gt; &gt;&gt; &gt;=C2=A0 =C2=A0<a href=3D"mailto:brong@fastmailteam.com" ta=
rget=3D"_blank">brong@fastmailteam.com</a> &lt;mailto:<a href=3D"mailto:bro=
ng@fastmailteam.com" target=3D"_blank">brong@fastmailteam.com</a>&gt;<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; _______________________________________________<br>
&gt; &gt;&gt; &gt; calsify mailing list<br>
&gt; &gt;&gt; &gt; <a href=3D"mailto:calsify@ietf.org" target=3D"_blank">ca=
lsify@ietf.org</a> &lt;mailto:<a href=3D"mailto:calsify@ietf.org" target=3D=
"_blank">calsify@ietf.org</a>&gt;<br>
&gt; &gt;&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/calsify=
" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinf=
o/calsify</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify"=
 rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo=
/calsify</a>&gt;<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; --<br>
&gt; &gt;&gt; Ujjwal &quot;Ryzokuken&quot; Sharma (he/him)<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Compilers Hacker, Node.js Core Collaborator and Speaker<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; _______________________________________________<br>
&gt; &gt;&gt; calsify mailing list<br>
&gt; &gt;&gt; <a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify=
@ietf.org</a> &lt;mailto:<a href=3D"mailto:calsify@ietf.org" target=3D"_bla=
nk">calsify@ietf.org</a>&gt;<br>
&gt; &gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/calsify" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/cal=
sify</a><br>
&gt; &gt;&gt; &lt;<a href=3D"https://www.ietf.org/mailman/listinfo/calsify"=
 rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo=
/calsify</a>&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt;=C2=A0 =C2=A0Bron Gondwana, CEO, Fastmail Pty Ltd<br>
&gt; &gt;=C2=A0 =C2=A0<a href=3D"mailto:brong@fastmailteam.com" target=3D"_=
blank">brong@fastmailteam.com</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; calsify mailing list<br>
&gt; &gt; <a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify@iet=
f.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/calsify" rel=3D"=
noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/calsify=
</a><br>
&gt; &gt;<br>
&gt;<br>
&gt; --<br>
&gt; Ujjwal &quot;Ryzokuken&quot; Sharma (he/him)<br>
&gt;<br>
&gt; Compilers Hacker, Node.js Core Collaborator and Speaker<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; calsify mailing list<br>
&gt; <a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify@ietf.org=
</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/calsify" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/calsify</a><=
br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt;=C2=A0 =C2=A0Bron Gondwana, CEO, Fastmail Pty Ltd<br>
&gt;=C2=A0 =C2=A0<a href=3D"mailto:brong@fastmailteam.com" target=3D"_blank=
">brong@fastmailteam.com</a><br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; calsify mailing list<br>
&gt; <a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify@ietf.org=
</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/calsify" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/calsify</a><=
br>
&gt;<br>
&gt;<br>
&gt; Attachments:<br>
&gt;<br>
&gt; signature.asc<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt;=C2=A0 =C2=A0Bron Gondwana, CEO, Fastmail Pty Ltd<br>
&gt;=C2=A0 =C2=A0<a href=3D"mailto:brong@fastmailteam.com" target=3D"_blank=
">brong@fastmailteam.com</a><br>
&gt;<br>
&gt;<br>
<br>
_______________________________________________<br>
calsify mailing list<br>
<a href=3D"mailto:calsify@ietf.org" target=3D"_blank">calsify@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/calsify" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/calsify</a><br>
</blockquote></div>
</blockquote></div>

--000000000000dec68705b9c84b6e--


From nobody Tue Jan 26 02:53:31 2021
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD3933A03FB for <calsify@ietfa.amsl.com>; Tue, 26 Jan 2021 02:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wAeXoi9df37C for <calsify@ietfa.amsl.com>; Tue, 26 Jan 2021 02:53:26 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id B1FB43A03EC for <calsify@ietf.org>; Tue, 26 Jan 2021 02:53:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1611658405; d=isode.com; s=june2016; i=@isode.com; bh=OjOD9yLEag5n0OJ/jzS0NpKRkUJ0BIHAbFQc0nUR73E=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=hyRmLsshWikuNjp+K2DXJeMSQSsd0x78NPauz1i5uY7e5aaZq+VaHmnp/hDMK08I7jIoCQ KVZcgjN072qXLqbXvFm8kypNPFi+iJyQQIgcQKmer7bn5k2rDv3w7UrNhF+/VoAkOCdh7p gtaI1/+mIB4zM2weD0/t4DvMA0B2wms=;
Received: from [172.27.251.227] (connect.isode.net [172.20.0.72])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <YA=0pABqmmip@statler.isode.com>; Tue, 26 Jan 2021 10:53:25 +0000
To: Barry Leiba <barryleiba@computer.org>, Bron Gondwana <brong@fastmailteam.com>
Cc: Francesca Palombini <francesca.palombini@ericsson.com>, calsify@ietf.org
References: <36725ce1-307a-945e-63bf-af98f4b85338@igalia.com> <a78e1a49-de7b-d2ed-c112-0bbd0cb62399@igalia.com> <da1b1dce-c4ce-49f2-b802-2bcbe00445c4@dogfood.fastmail.com> <23769d32-0a9b-6a8d-5f23-045f79a25fc6@igalia.com> <0275d5af-6eea-4608-913e-c96d59c0abea@dogfood.fastmail.com> <c87c068b-02f1-913a-64ef-497f827fc3ea@igalia.com> <27ae33c7-d5cf-428b-99fa-7b974be85e70@dogfood.fastmail.com> <AAD5976B-A601-45AC-9E43-CEB24D57BD1E@cisco.com> <fd342b5e-d998-487e-8fa2-5dd949b517e8@dogfood.fastmail.com> <CALaySJJPQ0zENWrd-JfthujCjPNcq7aNoDaxtFV7pehAOi5CjQ@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <280a8656-ba8c-7c18-e6d9-c745985eade1@isode.com>
Date: Tue, 26 Jan 2021 10:53:24 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
In-Reply-To: <CALaySJJPQ0zENWrd-JfthujCjPNcq7aNoDaxtFV7pehAOi5CjQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/p9Y2iXpvaaWsyvRgf49_Wa8vs3U>
Subject: Re: [calsify] New Timestamp Draft
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2021 10:53:29 -0000

Hi,

On 25/01/2021 21:07, Barry Leiba wrote:

> First, everyone, meet Francesca Palombini (added on CC), who will be
> your new AD starting in March.
Wellcome Francesca!
> I do have to agree with Eliot that obsoleting 3339 is well out of
> charter for calext.  What you quote below from what you said in
> dispatch, "Javascript notation format is looking for a standard
> serialisation", is not the same thing as "revising and obsoleting RFC
> 3339".  As Eliot points out, there are ways to include extra
> information in jCalendar, for example, without changing the basic
> date/time strings that are used in many places.  Changes to the 3339
> date/time strings will have ramifications all over the Internet, and I
> think that needs its own working group and a lot of publicity to make
> sure we're getting "everyone" who cares about it, rather than doing it
> where people think we're only dealing with calendaring protocols.
>
> I *am* sorry if this has been frustrating, unfriendly, or otherwise
> unpleasant for Ujjwal, and I'm quite sensitive to that.  I'm happy to
> help in any way I can, as I know Bron and Eliot (and Francesca) are.
> But we can't just handle this document in an inappropriately light
> way... the effect will be too far-reaching, even if exactly the
> changes that Ujjwal's draft suggests should turn out to be perfect.
I am sorry I was not paying enough attention to this topic earlier, but=20
if you are looking for more feedback, this is my 2p:
> Do we think we should be chartering a working group to revise and
> obsolete RFC 3339?  If so, let's get a draft charter for that and get
> the process started.
No. I would rather leave RFC 3339 as is, for reasons that Ned and Eliot=20
have stated.
> Do we need a standard JSON wrapper around what
> 3339 specifies, either as a stop-gap or as a permanent solution?

Yes, I can see this work as being useful. But I don't think we need to=20
replace RFC 3339, an extension (or wrapper) which just defines extra=20
stuff is going to be much quicker to complete and will have less resistence.

I think draft-ryzokuken-datetime-extended is a good starting point for=20
this effort, once a lot of original RFC 3339 text is deleted from it.

Best Regards,

Alexey

> Then
> maybe calext is the place to do that, and let's shift to working on
> that.
>
> Barry, ART AD
>
> On Sun, Jan 24, 2021 at 5:53 AM Bron Gondwana <brong@fastmailteam.com> wro=
te:
>> I'll ask you the same question I asked Ned, which is "do you object to th=
is work being taken up by the IETF at all, or just to it obsoleting 3339?"
>>
>> I will also point out that for all that we've talked about making the IET=
F more welcoming to newcomers, this has been a really unfriendly experience =
for Ujjwal.  Maybe that's my fault, but I'm sorry Ujjwal for misleading you =
if so.  I did raise that this work was coming in the "any other business" at=
 IETF110's DISPATCH, but without a draft there was very little guidance.  In=
deed the minutes of last dispatch say:
>>
>> Bron Gondwana: RFC3339 extension
>> * Javascript notation format is looking for a standard serialisation.
>>
>> Harald Alvestrand:
>> * We should have done this in the 90s!  It was a mistake not to do it the=
n.
>>
>> Neil Jenkins:
>> * we do need a serialisation format
>>
>> Where to discuss: calsify or tzdata lists, but probably calsify is best.
>>
>>
>> You can watch a video of the exact discussion here: https://youtu.be/d871=
MoUgAKU?t=3D6418
>>
>> ...
>>
>> Regardless, it appears that the right next venue for this document is DIS=
PATCH at IETF110.
>>
>> Regards,
>>
>> Bron.
>>
>> On Sun, Jan 24, 2021, at 21:32, Eliot Lear wrote:
>>
>> Bron,
>>
>> I=E2=80=99m sorry, but I have both substantive and procedural problems wi=
th you moving forward like this.  Let me start with the procedural.  This wo=
rk isn=E2=80=99t in calext=E2=80=99s charter.  You are specifically chartere=
d to tackle several extensions to the iCalendar format, and that is it.  Thi=
s is not an extension to that format.  This is a change to a standard that i=
s used extremely broadly.
>>
>> And this leads me to the substantive concern: this change is backward inc=
ompatible with  3339.  The ABNF in 3339 is clear: the stamp ends "time-offse=
t" ("Z" / time-numoffset).  Adding =E2=80=9Csuffix" blow up in any yacc/biso=
n-based parser and who knows what else.  Just imagine all the perl, awk, php=
, and python that whacks this stuff.
>>
>> In a great many cases, there is no means to negotiate the extension.  Let=
 me give you two examples:
>>
>> Logging software commonly uses 3339 both for generation and for parsing, =
and the parsers themselves are notoriously fragile to the point that I do no=
t believe any of them would entertain any changes to 3339.  The ecosystem is=
 so vast that there is no hope of enumerating it.  To test this, imagine wha=
t damage changing any other field to syslog would cause.
>> Calendaring software, though in a smaller ecosystem, will have older vers=
ions that may well fail to parse.
>>
>>
>> I am not saying that 3339 can never be updated, but before it is, it shou=
ld be clear that (a) it is broadly needed, not just by calendaring, and (b) =
that there is reason to believe that the change will be broadly adopted, aga=
in not just by calendaring.  If it=E2=80=99s just the calendaring ecosystem,=
 you have properties and parameters to use.
>>
>> Eliot
>>
>>
>> On 24 Jan 2021, at 04:15, Bron Gondwana <brong@fastmailteam.com> wrote:
>>
>> The document is plenty complete enough for a call for adoption!  I shall =
do so now.
>>
>> You are exactly correct that it's possible to do further iteration after =
adoption.
>>
>> Thanks,
>>
>> Bron.
>>
>> On Fri, Jan 22, 2021, at 23:19, Ujjwal Sharma wrote:
>>
>> Hi Bron, CalExt Friends!
>>
>> I made a new revision of the draft, which shifts the focus to defining
>> the syntax/format and defers the standardization of the actual key-value
>> pairs to sibling organizations like IANA and Unicode Consortium.
>>
>> I'd love to hear your opinions on this version, which you can find at
>> https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/,
>> which can be filed as issues on the GitHub repository or emailed to me
>> directly. In the meantime, I will address the remaining concerns/polish
>> issues like fixing the references section.
>>
>> How "complete" does the document need to be in order to initiate the
>> call for adoption? If the current version works, can we start it as soon
>> as possible? Of course, if my understanding of "adoption" is correct,
>> I'd be happy to iterate on the document further after the adoption by
>> the WG.
>>
>> Best,
>> Ujjwal
>>
>> On 14/01/2021 8.34 am, Bron Gondwana wrote:
>>> Sounds great.  Let me know :)
>>>
>>> When we do the call for adoption I'll also advertise the fact over to
>>> the wider IETF - probably dispatch and tzdata lists at least.
>>>
>>> Cheers,
>>>
>>> Bron.
>>>
>>>
>>> On Thu, Jan 14, 2021, at 13:48, Ujjwal Sharma wrote:
>>>> Thanks Bron!
>>>>
>>>> I'll make a few more changes, release a 01 version, ask for more
>>>> feedback and then let you know, hopefully by the end of this week.
>>>>
>>>> Ujjwal
>>>>
>>>> On 14/01/2021 7.03 am, Bron Gondwana wrote:
>>>>> I can do a call for adoption straight away if you like - the next
>>>>> meeting isn't for a couple of months.
>>>>>
>>>>> Bron.
>>>>>
>>>>> On Thu, Jan 14, 2021, at 05:24, Ujjwal Sharma wrote:
>>>>>> One question: given things move forward smoothly, how do I proceed?
>>>>>> Should I apply for this document to be adopted by the calext WG? I
>>>>>> suppose the fastest way to proceed is to present it at the next IETF
>>>>>> meeting?
>>>>>>
>>>>>>
>>>>>>
>>>>>> Ujjwal
>>>>>>
>>>>>> On 12/01/2021 4.03 am, Ujjwal Sharma wrote:
>>>>>>> Hi Calsify folks!
>>>>>>>
>>>>>>> I am sorry for the long delay, I got a little sidetracked working on
>>>>>>> other things, but I'm happy to inform you all that I have
>>>> something that
>>>>>>> resembles a first draft for the updated timestamps RFC.
>>>>>>>
>>>>>>> Here's where you can find it:
>>>>>>>
>>>>>>> Datatracker:
>>>>> https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
>>>> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/>
>>>> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/
>>>> <https://datatracker.ietf.org/doc/draft-ryzokuken-datetime-extended/>>
>>>> GitHub: https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
>>>> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>
>>>>>> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended
>>>> <https://github.com/ryzokuken/draft-ryzokuken-datetime-extended>>
>>>>>>> I would request you all to take a look at it when you can and let me
>>>>>>> know what you think. You can file a GitHub issue or email me
>>>> directly.
>>>>>>> There's a few open discussions regarding the exact format and how th=
e
>>>>>>> interaction with bodies like the Unicode consortium work, so
>>>> please feel
>>>>>>> free to send me your thoughts regarding that as well.
>>>>>>>
>>>>>>> Also, some references/bibliography is not perfectly functional yet
>>>>>>> because I am still relatively new to authoring RFCs using
>>>> Metanorma but
>>>>>>> I'm actively looking into it.
>>>>>>>
>>>>>>> Thanks and looking forward to hear from you,
>>>>>>> Ujjwal
>>>>>>>
>>>>>> --
>>>>>> Ujjwal "Ryzokuken" Sharma (he/him)
>>>>>>
>>>>>> Compilers Hacker, Node.js Core Collaborator and Speaker
>>>>>>
>>>>>> _______________________________________________
>>>>>> calsify mailing list
>>>>>> calsify@ietf.org <mailto:calsify@ietf.org> <mailto:calsify@ietf.org
>>>> <mailto:calsify@ietf.org>>
>>>>>> https://www.ietf.org/mailman/listinfo/calsify
>>>> <https://www.ietf.org/mailman/listinfo/calsify>
>>>>>> <https://www.ietf.org/mailman/listinfo/calsify
>>>> <https://www.ietf.org/mailman/listinfo/calsify>>
>>>>> --
>>>>>    Bron Gondwana, CEO, Fastmail Pty Ltd
>>>>>    brong@fastmailteam.com <mailto:brong@fastmailteam.com>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> calsify mailing list
>>>>> calsify@ietf.org <mailto:calsify@ietf.org>
>>>>> https://www.ietf.org/mailman/listinfo/calsify
>>>> <https://www.ietf.org/mailman/listinfo/calsify>
>>>> --
>>>> Ujjwal "Ryzokuken" Sharma (he/him)
>>>>
>>>> Compilers Hacker, Node.js Core Collaborator and Speaker
>>>>
>>>> _______________________________________________
>>>> calsify mailing list
>>>> calsify@ietf.org <mailto:calsify@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/calsify
>>>> <https://www.ietf.org/mailman/listinfo/calsify>
>>>>
>>> --
>>>    Bron Gondwana, CEO, Fastmail Pty Ltd
>>>    brong@fastmailteam.com
>>>
>>>
>>>
>>> _______________________________________________
>>> calsify mailing list
>>> calsify@ietf.org
>>> https://www.ietf.org/mailman/listinfo/calsify
>>>
>> --
>> Ujjwal "Ryzokuken" Sharma (he/him)
>>
>> Compilers Hacker, Node.js Core Collaborator and Speaker
>>
>> _______________________________________________
>> calsify mailing list
>> calsify@ietf.org
>> https://www.ietf.org/mailman/listinfo/calsify
>>
>>
>> --
>>    Bron Gondwana, CEO, Fastmail Pty Ltd
>>    brong@fastmailteam.com
>>
>>
>> _______________________________________________
>> calsify mailing list
>> calsify@ietf.org
>> https://www.ietf.org/mailman/listinfo/calsify
>>
>>
>> Attachments:
>>
>> signature.asc
>>
>>
>> --
>>    Bron Gondwana, CEO, Fastmail Pty Ltd
>>    brong@fastmailteam.com
>>
>>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify


From nobody Thu Jan 28 12:37:52 2021
Return-Path: <murch@fastmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27D303A1717; Thu, 28 Jan 2021 12:37:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=S36kuCYs; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=FAbFzgCA
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Iwqber9hc8X; Thu, 28 Jan 2021 12:37:47 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C9C93A1716; Thu, 28 Jan 2021 12:37:47 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 4707D5C00FF; Thu, 28 Jan 2021 15:37:46 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 28 Jan 2021 15:37:46 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm2; bh=FS4HZso4MnZHK7/q7XaQ5fniTNf w7JzIIYnbd5l/QAc=; b=S36kuCYsYeT4B0cdiXpc9+tjDd6uqP6VK4EHXkZwJRK MUSkHvtvBNQ1Wuxerjmd4Fj31J1qwZfzAYMB3ZF4MQxRkQpHfH8+Rj0qmiO6VA+m IGcWPDylQIKPpkrmQ3Zu3wQ0J9ltJ6vekXfB5RIwGMZ28ppgS022+blgWxPr3Q/Y 8rGaIio4s54fEOr2aInE3li/UYQmsYtGEXkAZuLWCT9oh0CkOyrNqoLgTmRL8t4c JpHzkPyK+b5Kq3FTaazTIpHXLiOz/YGQYcAr2jYxWF1sDQBDVtZIw9RhBKl8+qqS qCQloN3gMwaQPH8u3antPnbhDObcmoK/F/pujMTeVtg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=FS4HZs o4MnZHK7/q7XaQ5fniTNfw7JzIIYnbd5l/QAc=; b=FAbFzgCAEDp5sgPLm/rKhN NCofBwoaSmxlnMnUDswE89oaT9KKzscpZ1GHnEI3du9UWeMeooxTs2BjuxLJTj5s G5EUjgwAXeBUaSDOAci6i+pwqLl0ccvXmfH0vCTPKzu8Gc5xR5fqi1yjpV/2WwcW uYdPTBP3SkR49cZTpd66PD3Dv97zakbu3nzxyveIAyncXueu3DGeDo8IOmFCy34M pxizZu5DcGrWlKjw6vlh+z2Bk+ht7/2FYo4NC2pyxIvJ2VBtiz8G0qFkC2xD7/Jm Wxzj+NljbZfWm5ALYP90EQHfjzgL6sy+lfDTew44/2k31vMaQBIK8LNQLF7vMdkA ==
X-ME-Sender: <xms:mSATYIb_wGDvO384AMbCSUjwmjCR2qLSMVMUjLF6op-aZZeEHOEeRA> <xme:mSATYDZMPaPbTduXe5cpZO6iQIWJq7umDSvzm5j1ZW5LRPI2aFoHyUhIfvZpuEX_n CExvDHEXaFYog>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedtgddufeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtsegrtderredtfeejnecuhfhrohhmpefmvghnucfo uhhrtghhihhsohhnuceomhhurhgthhesfhgrshhtmhgrihhlrdgtohhmqeenucggtffrrg htthgvrhhnpeeugeefjeegffelheekteefgeeiveegvdekfeejgfdvfeetjeefffejieev gfehvdenucffohhmrghinhepihgrnhgrrdhorhhgnecukfhppeejgedrjeejrdekhedrvd ehtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehm uhhrtghhsehfrghsthhmrghilhdrtghomh
X-ME-Proxy: <xmx:mSATYC9PuqDGNNJ1fpkZMbc_t1TW3MBCBksOJ_AZK8rdAJXP9KkxRw> <xmx:mSATYCpdr9jZAFi6VPj8Z_t626JA2N_EuDqpZlHHDCgTc0jGW_Rb5A> <xmx:mSATYDorWlvBTFrd-d-TDGP9GUDw-IJNrZ2UrlvfLTzddw8pS5YYXQ> <xmx:miATYMAj4YGKPTOBZlZVEyS93ED3Fds8E01ZRUC8DOQgpjNhmCt0ag>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 850D324005C; Thu, 28 Jan 2021 15:37:45 -0500 (EST)
To: Barry Leiba <barryleiba@computer.org>, draft-ietf-calext-valarm-extensions.all@ietf.org
Cc: calsify@ietf.org
References: <CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com>
From: Ken Murchison <murch@fastmail.com>
Message-ID: <414b33de-c68a-5cbf-0f31-3b1b574f9e58@fastmail.com>
Date: Thu, 28 Jan 2021 15:37:44 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------280CDC7BBEBC7C71ACEF67D0"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/0HX5-1wF5rOXD3_5do9Bjv5_u7Q>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 20:37:50 -0000

This is a multi-part message in MIME format.
--------------280CDC7BBEBC7C71ACEF67D0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Barry,

Thanks for the review.  I *think* I hit all of your points inline.


On 12/3/20 4:15 PM, Barry Leiba wrote:
> Most of my comments are minor, but there are a couple of things to
> discuss (particularly how to handle the ABNF).  I'm going to put this
> in "revised I-D needed", but let's talk about the things that need
> discussion before submitting a revision for the others.
>
> — Section 2 —
> There’s no need for the “[1]” citation, and it only messes up idnits.
> Please remove it and the “URLs” section at the end.

Fixed.


> — Section 3 —
>
> My biggest issue here is with the ABNF, so let’s please have a
> discussion about it.
>
> First, some minor things:
>
> 1. This is probably a good time to pay attention to BCP 178 (RFC 6648) by
> removing the x-prop construction (and x-name elsewhere in the draft).

I have no problem removing these.  Anyone care to disagree?


> 2. Why is there a need to define new constructs (“alarmcext”,
> “audiopropext”, and so on), rather than just re-defining the base ones
> (“alarmc”, “audioprop”, …)?  It seems to me that this just confuses
> things, and the point here is to make changes that are compatible, but
> more readily extensible.
>
> Now, the big one:
>
> 3. I have never liked the way iCalendar did its ABNF, to the point
> where I think it’s wrong and harmful, causing confusion and not
> permitting automated processing of the ABNF.  It relies on normative
> comments where that’s not necessary, and ABNF was never intended to be
> usef that way.  Comments are meant to be explanatory, and normative
> comments are meant to be used only as a last resort, when you can’t
> express what you need in the formal language.  I would much rather
> limit the comments to a statment that elements can appear in any
> order, and then use the ABNF to convey whether the elements are
> required and how many times they can appear.
>
> Taking “alarmprop” as an example, here’s a re-write of it in the way
> ABNF should be representing it:
>
> OLD
>     alarmprop  = *(
>
>                  ; the following are REQUIRED,
>                  ; but MUST NOT occur more than once
>
>                  action / trigger /
>
>                  ; one set of action properties MUST be
>                  ; present and MUST match the action specified
>                  ; in the ACTION property
>
>                  actionprops /
>
>                  ; the following is OPTIONAL,
>                  ; and MAY occur more than once
>
>                  x-prop / iana-prop
>
>                  )
> NEW
>     alarmprop  = ; the elements herein may appear in any order,
>                  ; and the order is not significant.
>
>                  action
>                  trigger
>
>                  actionprops ; MUST match the action specified
>                              ; in the ACTION property
>
>                  [*iana-prop]
> END
>
> For “audiopropext”:
>
> OLD
>     audiopropext  = *(
>
>                     ; 'duration' and 'repeat' are both OPTIONAL,
>                     ; and MUST NOT occur more than once each,
>                     ; but if one occurs, so MUST the other
>
>                     duration / repeat /
>
>                     ; the following is OPTIONAL,
>                     ; but MUST NOT occur more than once
>
>                     attach
>
>                     )
> NEW
>     audiopropext  = ; the elements herein may appear in any order,
>                     ; and the order is not significant.
>                     [duration repeat]
>                     [attach]
>                     )
> END
>
> Is there really a good reason not to move in this direction?  The
> mechanism of saying that everything can appear zero or more times, and
> then limiting that with comments seems very poor.

I agree and don't have any good reason to not just redefine existing 
constructs and use the ABNF as proposed above, especially since this is 
what was done in draft-ietf-calext-valarm-extensions.  If there are no 
objections I will go ahead and do this and post a diff.


> — Section 6.1 —
>
>        Certain
>        kinds of alarm may not provide feedback as to when the calendar
>        user sees them, for example email based alerts.
>
> Nit: This sentence isn’t properly ordered (and has a couple of other
> nit-level errors).
>
> NEW
>        Certain
>        kinds of alarms, such as email-based alerts, might not provide
>        feedback as to when the calendar user sees them.
> END

Fixed.


> — Section 7 —
>
>     Clients SHOULD add a "RELATED-TO" property to the new "VALARM"
>     component with a value set to the "UID" property value of the
>     "VALARM" component being snoozed.  If the "VALARM" component being
>     snoozed does not already have a "UID" property, the client SHOULD add
>     one.  The "RELATED-TO" property added to the new "VALARM" component
>     SHOULD include a "RELTYPE" property parameter with a value set to
>     "SNOOZE".
>
> Why the SHOULDs?  This is new function; why are these not MUSTs?

I agree, the client is adding a new VALARM component for a specific 
purpose so we should standardize what it looks like.


>     When the "snooze" alarm is triggered and dismissed the client SHOULD
>     remove the corresponding "VALARM" component, or set the
>     "ACKNOWLEDGED" property (see Section 6.1).  Alternatively, if the
>     "snooze" alarm is itself "snoozed", the client SHOULD remove the
>     original "snooze" alarm and create a new one, with the appropriate
>     trigger time and relationship set.
>
> Same here about the SHOULDs.  Also, it’s not clear to me how this
> relates to the original alarm.  It would be good to say, explicitly,
> that the original VALARM is not removed.  But also, is the
> “ACKNOWLEDGED” time on the original alarm changed to show the time
> that the snooze was dismissed?  If not, why not?  And is there a
> reason to choose between the apparently equal alternatives presented
> in the first sentence?  Or is the choice entirely up to the
> implementation?


I'm leaning towards changing this text to the following:

    When the "snooze" alarm is triggered and dismissed the client MUST do
    one of the following with the corresponding "VALARM" component:

    o  Set the "ACKNOWLEDGED" property (see Section 6.1)

    o  Remove the component


    Alternatively, if the "snooze" alarm is itself "snoozed", the client
    MUST remove the original "snooze" alarm and create a new one, with
    the appropriate trigger time and relationship set.

    Note that regardless of the final disposition of the "snooze" alarm
    when triggered, the original "VALARM" component is left unchanged.


Is this any better?


> — Section 7.1 —
>
>     This specification adds the "SNOOZE" relationship type for use with
>     the "RELTYPE" property defined in Section 3.2.15 of [RFC5545].  This
>     is used to relate a "snoozed" "VALARM" component to the original
>     alarm that the "snooze" was generated for.
>
> Maybe I’m being too picky here, but I don’t think the RELTYPE of
> SNOOZE is used to relate the alarms: the UID property is used for
> that.  Maybe “This is used when relating” is better wording?

Yes, Fixed.


> — Section 8.1 —
>
>        When the property value is set to "ARRIVE", the alarm is triggered
>        when the calendar user agent arrives in the vicinity of any of the
>        specified locations.  When set to "DEPART", the alarm is triggered
>        when the calendar user agent departs from the vicinity of any
>        specified locations.
>
> I think we need to more clearly specify “vicinity” here, even if it’s
> just to say that the definition is up to the implementation.  As it
> is, I don’t know whether I need to depart from my kitchen, from my
> house, from my street, from my town, or whatever.

Punted this as implementation defined.


>        When the property value is set to "CONNECT", the alarm is
>        triggered when the calendar user agent connects to a Bluetooth(R)
>        [BTcore]-enabled automobile.  When set to "DISCONNECT", the alarm
>        is triggered when the calendar user agent disconnects from a
>        Bluetooth(R)-enabled automobile.
>
> Nit: It’s odd to have the citation in the middle of the compound
> modifier.  I suggest rewriting to avoid the problem:
>
> NEW
>        When the property value is set to "CONNECT", the alarm is
>        triggered when the calendar user agent connects to an automobile
>        that is enabled for Bluetooth(R) [BTcore].  When set to
>        "DISCONNECT", the alarm is triggered when the calendar user agent
>        disconnects from a Bluetooth(R)-enabled automobile.
> END

Fixed.


>     Example:  The following is an example of this property:
>     PROXIMITY:ARRIVE
>
> I think this example is useless, as it’s incomplete without the geo
> location.  And you have Section 8.2 immediately after, so why not just
> remove this?

Removed.


> — Section 11 —
> Throughout this section, please specify the names and/or URIs of the
> registries, to make it easier for both IANA and other readers to find
> them.  For example, in Section 11.1:
>
> NEW
>     This document defines the following new iCalendar properties to be
>     added to the Properties registry defined in Section 8.2.3 of [RFC5545]
>     and located here:
>     <https://www.iana.org/assignments/icalendar#properties>
> END

Added.


-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


--------------280CDC7BBEBC7C71ACEF67D0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi Barry,</p>
    <p>Thanks for the review.  I *think* I hit all of your points
      inline.</p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 12/3/20 4:15 PM, Barry Leiba wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com">
      <pre class="moz-quote-pre" wrap="">Most of my comments are minor, but there are a couple of things to
discuss (particularly how to handle the ABNF).  I'm going to put this
in "revised I-D needed", but let's talk about the things that need
discussion before submitting a revision for the others.

— Section 2 —
There’s no need for the “[1]” citation, and it only messes up idnits.
Please remove it and the “URLs” section at the end.</pre>
    </blockquote>
    <p>Fixed.</p>
    <p><br>
    </p>
    <p>
    </p>
    <blockquote type="cite"
cite="mid:CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com">
      <pre class="moz-quote-pre" wrap="">— Section 3 —

My biggest issue here is with the ABNF, so let’s please have a
discussion about it.

First, some minor things:

1. This is probably a good time to pay attention to BCP 178 (RFC 6648) by
removing the x-prop construction (and x-name elsewhere in the draft).</pre>
    </blockquote>
    <p>I have no problem removing these.  Anyone care to disagree?</p>
    <p><br>
    </p>
    <p>
    </p>
    <blockquote type="cite"
cite="mid:CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com">
      <pre class="moz-quote-pre" wrap="">2. Why is there a need to define new constructs (“alarmcext”,
“audiopropext”, and so on), rather than just re-defining the base ones
(“alarmc”, “audioprop”, …)?  It seems to me that this just confuses
things, and the point here is to make changes that are compatible, but
more readily extensible.

Now, the big one:

3. I have never liked the way iCalendar did its ABNF, to the point
where I think it’s wrong and harmful, causing confusion and not
permitting automated processing of the ABNF.  It relies on normative
comments where that’s not necessary, and ABNF was never intended to be
usef that way.  Comments are meant to be explanatory, and normative
comments are meant to be used only as a last resort, when you can’t
express what you need in the formal language.  I would much rather
limit the comments to a statment that elements can appear in any
order, and then use the ABNF to convey whether the elements are
required and how many times they can appear.

Taking “alarmprop” as an example, here’s a re-write of it in the way
ABNF should be representing it:

OLD
   alarmprop  = *(

                ; the following are REQUIRED,
                ; but MUST NOT occur more than once

                action / trigger /

                ; one set of action properties MUST be
                ; present and MUST match the action specified
                ; in the ACTION property

                actionprops /

                ; the following is OPTIONAL,
                ; and MAY occur more than once

                x-prop / iana-prop

                )
NEW
   alarmprop  = ; the elements herein may appear in any order,
                ; and the order is not significant.

                action
                trigger

                actionprops ; MUST match the action specified
                            ; in the ACTION property

                [*iana-prop]
END

For “audiopropext”:

OLD
   audiopropext  = *(

                   ; 'duration' and 'repeat' are both OPTIONAL,
                   ; and MUST NOT occur more than once each,
                   ; but if one occurs, so MUST the other

                   duration / repeat /

                   ; the following is OPTIONAL,
                   ; but MUST NOT occur more than once

                   attach

                   )
NEW
   audiopropext  = ; the elements herein may appear in any order,
                   ; and the order is not significant.
                   [duration repeat]
                   [attach]
                   )
END

Is there really a good reason not to move in this direction?  The
mechanism of saying that everything can appear zero or more times, and
then limiting that with comments seems very poor.</pre>
    </blockquote>
    <p>I agree and don't have any good reason to not just redefine
      existing constructs and use the ABNF as proposed above, especially
      since this is what was done in
      draft-ietf-calext-valarm-extensions.  If there are no objections I
      will go ahead and do this and post a diff.<br>
    </p>
    <p><br>
    </p>
    <p>
    </p>
    <blockquote type="cite"
cite="mid:CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com">
      <pre class="moz-quote-pre" wrap="">— Section 6.1 —

      Certain
      kinds of alarm may not provide feedback as to when the calendar
      user sees them, for example email based alerts.

Nit: This sentence isn’t properly ordered (and has a couple of other
nit-level errors).

NEW
      Certain
      kinds of alarms, such as email-based alerts, might not provide
      feedback as to when the calendar user sees them.
END</pre>
    </blockquote>
    <p>Fixed.</p>
    <p><br>
    </p>
    <p>
    </p>
    <blockquote type="cite"
cite="mid:CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com">
      <pre class="moz-quote-pre" wrap="">— Section 7 —

   Clients SHOULD add a "RELATED-TO" property to the new "VALARM"
   component with a value set to the "UID" property value of the
   "VALARM" component being snoozed.  If the "VALARM" component being
   snoozed does not already have a "UID" property, the client SHOULD add
   one.  The "RELATED-TO" property added to the new "VALARM" component
   SHOULD include a "RELTYPE" property parameter with a value set to
   "SNOOZE".

Why the SHOULDs?  This is new function; why are these not MUSTs?</pre>
    </blockquote>
    <p>I agree, the client is adding a new VALARM component for a
      specific purpose so we should standardize what it looks like.<br>
    </p>
    <p><br>
    </p>
    <p>
    </p>
    <blockquote type="cite"
cite="mid:CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com">
      <pre class="moz-quote-pre" wrap="">   When the "snooze" alarm is triggered and dismissed the client SHOULD
   remove the corresponding "VALARM" component, or set the
   "ACKNOWLEDGED" property (see Section 6.1).  Alternatively, if the
   "snooze" alarm is itself "snoozed", the client SHOULD remove the
   original "snooze" alarm and create a new one, with the appropriate
   trigger time and relationship set.

Same here about the SHOULDs.  Also, it’s not clear to me how this
relates to the original alarm.  It would be good to say, explicitly,
that the original VALARM is not removed.  But also, is the
“ACKNOWLEDGED” time on the original alarm changed to show the time
that the snooze was dismissed?  If not, why not?  And is there a
reason to choose between the apparently equal alternatives presented
in the first sentence?  Or is the choice entirely up to the
implementation?</pre>
    </blockquote>
    <p><br>
    </p>
    <p>I'm leaning towards changing this text to the following:</p>
    <pre>   When the "snooze" alarm is triggered and dismissed the client MUST do
   one of the following with the corresponding "VALARM" component:

   o  Set the "ACKNOWLEDGED" property (see Section 6.1)

   o  Remove the component


   Alternatively, if the "snooze" alarm is itself "snoozed", the client
   MUST remove the original "snooze" alarm and create a new one, with
   the appropriate trigger time and relationship set.

   Note that regardless of the final disposition of the "snooze" alarm
   when triggered, the original "VALARM" component is left unchanged.
</pre>
    <p><br>
    </p>
    <p>Is this any better?</p>
    <p><br>
    </p>
    <p>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">— Section 7.1 —

   This specification adds the "SNOOZE" relationship type for use with
   the "RELTYPE" property defined in Section 3.2.15 of [RFC5545].  This
   is used to relate a "snoozed" "VALARM" component to the original
   alarm that the "snooze" was generated for.

Maybe I’m being too picky here, but I don’t think the RELTYPE of
SNOOZE is used to relate the alarms: the UID property is used for
that.  Maybe “This is used when relating” is better wording?
</pre>
      </blockquote>
      <br>
    </p>
    <p>Yes, Fixed.</p>
    <p><br>
    </p>
    <p>
    </p>
    <blockquote type="cite"
cite="mid:CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com">
      <pre class="moz-quote-pre" wrap="">— Section 8.1 —

      When the property value is set to "ARRIVE", the alarm is triggered
      when the calendar user agent arrives in the vicinity of any of the
      specified locations.  When set to "DEPART", the alarm is triggered
      when the calendar user agent departs from the vicinity of any
      specified locations.

I think we need to more clearly specify “vicinity” here, even if it’s
just to say that the definition is up to the implementation.  As it
is, I don’t know whether I need to depart from my kitchen, from my
house, from my street, from my town, or whatever.</pre>
    </blockquote>
    <p>Punted this as implementation defined.</p>
    <p><br>
    </p>
    <p>
    </p>
    <blockquote type="cite"
cite="mid:CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com">
      <pre class="moz-quote-pre" wrap="">      When the property value is set to "CONNECT", the alarm is
      triggered when the calendar user agent connects to a Bluetooth(R)
      [BTcore]-enabled automobile.  When set to "DISCONNECT", the alarm
      is triggered when the calendar user agent disconnects from a
      Bluetooth(R)-enabled automobile.

Nit: It’s odd to have the citation in the middle of the compound
modifier.  I suggest rewriting to avoid the problem:

NEW
      When the property value is set to "CONNECT", the alarm is
      triggered when the calendar user agent connects to an automobile
      that is enabled for Bluetooth(R) [BTcore].  When set to
      "DISCONNECT", the alarm is triggered when the calendar user agent
      disconnects from a Bluetooth(R)-enabled automobile.
END</pre>
    </blockquote>
    <p>Fixed.</p>
    <p><br>
    </p>
    <p>
    </p>
    <blockquote type="cite"
cite="mid:CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com">
      <pre class="moz-quote-pre" wrap="">   Example:  The following is an example of this property:
   PROXIMITY:ARRIVE

I think this example is useless, as it’s incomplete without the geo
location.  And you have Section 8.2 immediately after, so why not just
remove this?</pre>
    </blockquote>
    <p>Removed.</p>
    <p><br>
    </p>
    <p>
    </p>
    <blockquote type="cite"
cite="mid:CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com">
      <pre class="moz-quote-pre" wrap="">— Section 11 —
Throughout this section, please specify the names and/or URIs of the
registries, to make it easier for both IANA and other readers to find
them.  For example, in Section 11.1:

NEW
   This document defines the following new iCalendar properties to be
   added to the Properties registry defined in Section 8.2.3 of [RFC5545]
   and located here:
   <a class="moz-txt-link-rfc2396E" href="https://www.iana.org/assignments/icalendar#properties">&lt;https://www.iana.org/assignments/icalendar#properties&gt;</a>
END</pre>
    </blockquote>
    <p>Added.</p>
    <p><br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC</pre>
  </body>
</html>

--------------280CDC7BBEBC7C71ACEF67D0--


From nobody Thu Jan 28 13:09:36 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 810EE3A175C; Thu, 28 Jan 2021 13:09:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-bO7NCzY_wR; Thu, 28 Jan 2021 13:09:32 -0800 (PST)
Received: from mail-lj1-f171.google.com (mail-lj1-f171.google.com [209.85.208.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4713B3A175B; Thu, 28 Jan 2021 13:09:32 -0800 (PST)
Received: by mail-lj1-f171.google.com with SMTP id e18so8054955lja.12; Thu, 28 Jan 2021 13:09:32 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=LChQ9M8rmau15OuvBt+DcWgVuZz1N1YJZsKPzKq3oxg=; b=PDTuMJNEC9LFe0sX9/qa9UI4hm1n0f+vK3moGiOItZCHWiU8oB8r1t/T3u6rFX+y+C jYX7he05Dan/i7nrlpTGdmnWwl3Cz37WHFjsPlEo1u94tSDVi1+YC/kEusFAcUoGQxoZ sFQDKFeBB+ZhCBaSzEmnktDUJlEo3PnaLUXo3ezp0MnkLj9DKn4eGV+dBL3t2lCanimo zXUoegmoHaMqo62rgc9iJmv0iPHZbE+QEEXq7Ryo18tQrqHLUVbMs+RusHzmPtR+xeW1 tBxcu+ZULRTZM+Zhp9KrR4fxrs9JoOB7TSP4zAN4yhboFbu1Tno3ZIYDN+9+mItleMDm UHOg==
X-Gm-Message-State: AOAM532bXceOsbEWcHT5yb94jR6JIXAY032RCFJRfVbbZk5K0lAuExMS vX5yo3EAJxxWgVXEaacZBxMXPDSMQwYitpcpIWU=
X-Google-Smtp-Source: ABdhPJyyDbg9tVNO9PhaeoL1hoaacXTxXUxg6Il+ZkYmSMLxIb22nvjBK+YMDJfQYCAKtWftpKEET0mXExUWsja18nU=
X-Received: by 2002:a2e:824b:: with SMTP id j11mr623667ljh.473.1611868170116;  Thu, 28 Jan 2021 13:09:30 -0800 (PST)
MIME-Version: 1.0
References: <CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com> <414b33de-c68a-5cbf-0f31-3b1b574f9e58@fastmail.com>
In-Reply-To: <414b33de-c68a-5cbf-0f31-3b1b574f9e58@fastmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 28 Jan 2021 16:09:18 -0500
Message-ID: <CALaySJJ87t5Ju7jF2chAXrevhg=rgANgkGUwwr_ocf7HpATozw@mail.gmail.com>
To: Ken Murchison <murch@fastmail.com>
Cc: draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/1jKoIW9xm8d9ovlBGIFoV-_qHG4>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jan 2021 21:09:35 -0000

Thanks, Ken; this all looks good.  I'll wait for a revised I-D and
move forward from there.

Barry

On Thu, Jan 28, 2021 at 3:37 PM Ken Murchison <murch@fastmail.com> wrote:
>
> Hi Barry,
>
> Thanks for the review.  I *think* I hit all of your points inline.
>
>
> On 12/3/20 4:15 PM, Barry Leiba wrote:
>
> Most of my comments are minor, but there are a couple of things to
> discuss (particularly how to handle the ABNF).  I'm going to put this
> in "revised I-D needed", but let's talk about the things that need
> discussion before submitting a revision for the others.
>
> =E2=80=94 Section 2 =E2=80=94
> There=E2=80=99s no need for the =E2=80=9C[1]=E2=80=9D citation, and it on=
ly messes up idnits.
> Please remove it and the =E2=80=9CURLs=E2=80=9D section at the end.
>
> Fixed.
>
>
> =E2=80=94 Section 3 =E2=80=94
>
> My biggest issue here is with the ABNF, so let=E2=80=99s please have a
> discussion about it.
>
> First, some minor things:
>
> 1. This is probably a good time to pay attention to BCP 178 (RFC 6648) by
> removing the x-prop construction (and x-name elsewhere in the draft).
>
> I have no problem removing these.  Anyone care to disagree?
>
>
> 2. Why is there a need to define new constructs (=E2=80=9Calarmcext=E2=80=
=9D,
> =E2=80=9Caudiopropext=E2=80=9D, and so on), rather than just re-defining =
the base ones
> (=E2=80=9Calarmc=E2=80=9D, =E2=80=9Caudioprop=E2=80=9D, =E2=80=A6)?  It s=
eems to me that this just confuses
> things, and the point here is to make changes that are compatible, but
> more readily extensible.
>
> Now, the big one:
>
> 3. I have never liked the way iCalendar did its ABNF, to the point
> where I think it=E2=80=99s wrong and harmful, causing confusion and not
> permitting automated processing of the ABNF.  It relies on normative
> comments where that=E2=80=99s not necessary, and ABNF was never intended =
to be
> usef that way.  Comments are meant to be explanatory, and normative
> comments are meant to be used only as a last resort, when you can=E2=80=
=99t
> express what you need in the formal language.  I would much rather
> limit the comments to a statment that elements can appear in any
> order, and then use the ABNF to convey whether the elements are
> required and how many times they can appear.
>
> Taking =E2=80=9Calarmprop=E2=80=9D as an example, here=E2=80=99s a re-wri=
te of it in the way
> ABNF should be representing it:
>
> OLD
>    alarmprop  =3D *(
>
>                 ; the following are REQUIRED,
>                 ; but MUST NOT occur more than once
>
>                 action / trigger /
>
>                 ; one set of action properties MUST be
>                 ; present and MUST match the action specified
>                 ; in the ACTION property
>
>                 actionprops /
>
>                 ; the following is OPTIONAL,
>                 ; and MAY occur more than once
>
>                 x-prop / iana-prop
>
>                 )
> NEW
>    alarmprop  =3D ; the elements herein may appear in any order,
>                 ; and the order is not significant.
>
>                 action
>                 trigger
>
>                 actionprops ; MUST match the action specified
>                             ; in the ACTION property
>
>                 [*iana-prop]
> END
>
> For =E2=80=9Caudiopropext=E2=80=9D:
>
> OLD
>    audiopropext  =3D *(
>
>                    ; 'duration' and 'repeat' are both OPTIONAL,
>                    ; and MUST NOT occur more than once each,
>                    ; but if one occurs, so MUST the other
>
>                    duration / repeat /
>
>                    ; the following is OPTIONAL,
>                    ; but MUST NOT occur more than once
>
>                    attach
>
>                    )
> NEW
>    audiopropext  =3D ; the elements herein may appear in any order,
>                    ; and the order is not significant.
>                    [duration repeat]
>                    [attach]
>                    )
> END
>
> Is there really a good reason not to move in this direction?  The
> mechanism of saying that everything can appear zero or more times, and
> then limiting that with comments seems very poor.
>
> I agree and don't have any good reason to not just redefine existing cons=
tructs and use the ABNF as proposed above, especially since this is what wa=
s done in draft-ietf-calext-valarm-extensions.  If there are no objections =
I will go ahead and do this and post a diff.
>
>
> =E2=80=94 Section 6.1 =E2=80=94
>
>       Certain
>       kinds of alarm may not provide feedback as to when the calendar
>       user sees them, for example email based alerts.
>
> Nit: This sentence isn=E2=80=99t properly ordered (and has a couple of ot=
her
> nit-level errors).
>
> NEW
>       Certain
>       kinds of alarms, such as email-based alerts, might not provide
>       feedback as to when the calendar user sees them.
> END
>
> Fixed.
>
>
> =E2=80=94 Section 7 =E2=80=94
>
>    Clients SHOULD add a "RELATED-TO" property to the new "VALARM"
>    component with a value set to the "UID" property value of the
>    "VALARM" component being snoozed.  If the "VALARM" component being
>    snoozed does not already have a "UID" property, the client SHOULD add
>    one.  The "RELATED-TO" property added to the new "VALARM" component
>    SHOULD include a "RELTYPE" property parameter with a value set to
>    "SNOOZE".
>
> Why the SHOULDs?  This is new function; why are these not MUSTs?
>
> I agree, the client is adding a new VALARM component for a specific purpo=
se so we should standardize what it looks like.
>
>
>    When the "snooze" alarm is triggered and dismissed the client SHOULD
>    remove the corresponding "VALARM" component, or set the
>    "ACKNOWLEDGED" property (see Section 6.1).  Alternatively, if the
>    "snooze" alarm is itself "snoozed", the client SHOULD remove the
>    original "snooze" alarm and create a new one, with the appropriate
>    trigger time and relationship set.
>
> Same here about the SHOULDs.  Also, it=E2=80=99s not clear to me how this
> relates to the original alarm.  It would be good to say, explicitly,
> that the original VALARM is not removed.  But also, is the
> =E2=80=9CACKNOWLEDGED=E2=80=9D time on the original alarm changed to show=
 the time
> that the snooze was dismissed?  If not, why not?  And is there a
> reason to choose between the apparently equal alternatives presented
> in the first sentence?  Or is the choice entirely up to the
> implementation?
>
>
> I'm leaning towards changing this text to the following:
>
>    When the "snooze" alarm is triggered and dismissed the client MUST do
>    one of the following with the corresponding "VALARM" component:
>
>    o  Set the "ACKNOWLEDGED" property (see Section 6.1)
>
>    o  Remove the component
>
>
>    Alternatively, if the "snooze" alarm is itself "snoozed", the client
>    MUST remove the original "snooze" alarm and create a new one, with
>    the appropriate trigger time and relationship set.
>
>    Note that regardless of the final disposition of the "snooze" alarm
>    when triggered, the original "VALARM" component is left unchanged.
>
>
> Is this any better?
>
>
> =E2=80=94 Section 7.1 =E2=80=94
>
>    This specification adds the "SNOOZE" relationship type for use with
>    the "RELTYPE" property defined in Section 3.2.15 of [RFC5545].  This
>    is used to relate a "snoozed" "VALARM" component to the original
>    alarm that the "snooze" was generated for.
>
> Maybe I=E2=80=99m being too picky here, but I don=E2=80=99t think the REL=
TYPE of
> SNOOZE is used to relate the alarms: the UID property is used for
> that.  Maybe =E2=80=9CThis is used when relating=E2=80=9D is better wordi=
ng?
>
>
> Yes, Fixed.
>
>
> =E2=80=94 Section 8.1 =E2=80=94
>
>       When the property value is set to "ARRIVE", the alarm is triggered
>       when the calendar user agent arrives in the vicinity of any of the
>       specified locations.  When set to "DEPART", the alarm is triggered
>       when the calendar user agent departs from the vicinity of any
>       specified locations.
>
> I think we need to more clearly specify =E2=80=9Cvicinity=E2=80=9D here, =
even if it=E2=80=99s
> just to say that the definition is up to the implementation.  As it
> is, I don=E2=80=99t know whether I need to depart from my kitchen, from m=
y
> house, from my street, from my town, or whatever.
>
> Punted this as implementation defined.
>
>
>       When the property value is set to "CONNECT", the alarm is
>       triggered when the calendar user agent connects to a Bluetooth(R)
>       [BTcore]-enabled automobile.  When set to "DISCONNECT", the alarm
>       is triggered when the calendar user agent disconnects from a
>       Bluetooth(R)-enabled automobile.
>
> Nit: It=E2=80=99s odd to have the citation in the middle of the compound
> modifier.  I suggest rewriting to avoid the problem:
>
> NEW
>       When the property value is set to "CONNECT", the alarm is
>       triggered when the calendar user agent connects to an automobile
>       that is enabled for Bluetooth(R) [BTcore].  When set to
>       "DISCONNECT", the alarm is triggered when the calendar user agent
>       disconnects from a Bluetooth(R)-enabled automobile.
> END
>
> Fixed.
>
>
>    Example:  The following is an example of this property:
>    PROXIMITY:ARRIVE
>
> I think this example is useless, as it=E2=80=99s incomplete without the g=
eo
> location.  And you have Section 8.2 immediately after, so why not just
> remove this?
>
> Removed.
>
>
> =E2=80=94 Section 11 =E2=80=94
> Throughout this section, please specify the names and/or URIs of the
> registries, to make it easier for both IANA and other readers to find
> them.  For example, in Section 11.1:
>
> NEW
>    This document defines the following new iCalendar properties to be
>    added to the Properties registry defined in Section 8.2.3 of [RFC5545]
>    and located here:
>    <https://www.iana.org/assignments/icalendar#properties>
> END
>
> Added.
>
>
> --
> Kenneth Murchison
> Senior Software Developer
> Fastmail US LLC


From nobody Fri Jan 29 06:07:58 2021
Return-Path: <mglt.ietf@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE8673A0D24; Fri, 29 Jan 2021 06:07:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gy_zX6zIaYGQ; Fri, 29 Jan 2021 06:07:53 -0800 (PST)
Received: from mail-vk1-xa2e.google.com (mail-vk1-xa2e.google.com [IPv6:2607:f8b0:4864:20::a2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F344A3A0D18; Fri, 29 Jan 2021 06:07:52 -0800 (PST)
Received: by mail-vk1-xa2e.google.com with SMTP id e10so2183334vkm.2; Fri, 29 Jan 2021 06:07:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0DjzXAVerCfn1Vg9br/D72L2+HkiKvye6ogNBwkZV3w=; b=kh4Y1Kjy71wzsmAZQar6V48OwWdkAVyB7m/QMZivqAUVMmoDne1B7+EV4kXHVyIjhW V3gKIjfqpbd84O2bejlERrRvCRQ/9zgJltkJys2bVaxDfgCMafhPQVEZRAO3en5RjXKK CKawQR4PgXv5UcO2ajPtkEHRPW1Dg4BP4z8VqzfQu/0YtXb/xKXLb9uqjU3bKphGjpoB LPSTiB+qksVQKKUP/4VdVhp30snUmAV4BaH+JpQyvJa0X8Nm1Hs3B5qCnmP3GXeghVvS bhDuJGSVAPm0AheQWMIB0soPVQL1sb46g+eRd1RrTod2QfcbhM6r0fWyRZMZrn1JY9PO lxNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0DjzXAVerCfn1Vg9br/D72L2+HkiKvye6ogNBwkZV3w=; b=j3bCMbVjR5Zl2LRNuAbkMPJWDYWVRSTi6cewd8DofWxxECiX7aqvAFL9B6yNCBIki9 g9O/Yth+KO67Y71uuT5itd1lUfptyOMR2OCBhMdzjwttEMZJ9r9afRpYgtfVJn+BlI8L 2LL8WrZFs1QymxrXuzfEVeh4l5R2OezATPdMzxTjiu+6Fo1fP558RvCAnzwxSNYwDn62 zXrrUBIr6vUgqYXYYCBq2NZx++RkCaBlw1P+PF7Hqvv/npSYMNM3jxrxsRs2O2VCSnaY yU6GUwIe2oUIpXe4tEuNJkTTXXzbLOWvtG6B3lo0DKsm41nfhvsAIpmvL26wj96Te7fW OAaQ==
X-Gm-Message-State: AOAM532TewKzJDnAOK17znBANx1PJ2zEnHIg4Xpad3iIcGzxzJjnKv1d uncHoq5ASYCkdkp1Rfe4FrB7rY7eYp6uU+RgE4g=
X-Google-Smtp-Source: ABdhPJytVOjD+Ipq+af/hnwh/hP1IGpjPKgd1ZOHIp1e+mHYd8taxutdmSPB3cvERlwjjPnR7dLKjYhAcP5ow3leXSg=
X-Received: by 2002:a1f:9004:: with SMTP id s4mr2924264vkd.6.1611929270465; Fri, 29 Jan 2021 06:07:50 -0800 (PST)
MIME-Version: 1.0
References: <CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com> <414b33de-c68a-5cbf-0f31-3b1b574f9e58@fastmail.com> <CALaySJJ87t5Ju7jF2chAXrevhg=rgANgkGUwwr_ocf7HpATozw@mail.gmail.com>
In-Reply-To: <CALaySJJ87t5Ju7jF2chAXrevhg=rgANgkGUwwr_ocf7HpATozw@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
Date: Fri, 29 Jan 2021 09:07:39 -0500
Message-ID: <CADZyTknyFrUX821wV_aKH1HSteXbK8fO_UHU9rjYABbTWFWu2g@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: Ken Murchison <murch@fastmail.com>, draft-ietf-calext-valarm-extensions.all@ietf.org,  IETF-Calsify <calsify@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000091b9d805ba0a8726"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/dDv4eMczbbyEpjpsEBbB5EwMESs>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 14:07:56 -0000

--00000000000091b9d805ba0a8726
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks Barry and Ken for the follow-up. I am happy to see the draft being
moved forward.
Yours,
Daniel

On Thu, Jan 28, 2021 at 4:09 PM Barry Leiba <barryleiba@computer.org> wrote=
:

> Thanks, Ken; this all looks good.  I'll wait for a revised I-D and
> move forward from there.
>
> Barry
>
> On Thu, Jan 28, 2021 at 3:37 PM Ken Murchison <murch@fastmail.com> wrote:
> >
> > Hi Barry,
> >
> > Thanks for the review.  I *think* I hit all of your points inline.
> >
> >
> > On 12/3/20 4:15 PM, Barry Leiba wrote:
> >
> > Most of my comments are minor, but there are a couple of things to
> > discuss (particularly how to handle the ABNF).  I'm going to put this
> > in "revised I-D needed", but let's talk about the things that need
> > discussion before submitting a revision for the others.
> >
> > =E2=80=94 Section 2 =E2=80=94
> > There=E2=80=99s no need for the =E2=80=9C[1]=E2=80=9D citation, and it =
only messes up idnits.
> > Please remove it and the =E2=80=9CURLs=E2=80=9D section at the end.
> >
> > Fixed.
> >
> >
> > =E2=80=94 Section 3 =E2=80=94
> >
> > My biggest issue here is with the ABNF, so let=E2=80=99s please have a
> > discussion about it.
> >
> > First, some minor things:
> >
> > 1. This is probably a good time to pay attention to BCP 178 (RFC 6648) =
by
> > removing the x-prop construction (and x-name elsewhere in the draft).
> >
> > I have no problem removing these.  Anyone care to disagree?
> >
> >
> > 2. Why is there a need to define new constructs (=E2=80=9Calarmcext=E2=
=80=9D,
> > =E2=80=9Caudiopropext=E2=80=9D, and so on), rather than just re-definin=
g the base ones
> > (=E2=80=9Calarmc=E2=80=9D, =E2=80=9Caudioprop=E2=80=9D, =E2=80=A6)?  It=
 seems to me that this just confuses
> > things, and the point here is to make changes that are compatible, but
> > more readily extensible.
> >
> > Now, the big one:
> >
> > 3. I have never liked the way iCalendar did its ABNF, to the point
> > where I think it=E2=80=99s wrong and harmful, causing confusion and not
> > permitting automated processing of the ABNF.  It relies on normative
> > comments where that=E2=80=99s not necessary, and ABNF was never intende=
d to be
> > usef that way.  Comments are meant to be explanatory, and normative
> > comments are meant to be used only as a last resort, when you can=E2=80=
=99t
> > express what you need in the formal language.  I would much rather
> > limit the comments to a statment that elements can appear in any
> > order, and then use the ABNF to convey whether the elements are
> > required and how many times they can appear.
> >
> > Taking =E2=80=9Calarmprop=E2=80=9D as an example, here=E2=80=99s a re-w=
rite of it in the way
> > ABNF should be representing it:
> >
> > OLD
> >    alarmprop  =3D *(
> >
> >                 ; the following are REQUIRED,
> >                 ; but MUST NOT occur more than once
> >
> >                 action / trigger /
> >
> >                 ; one set of action properties MUST be
> >                 ; present and MUST match the action specified
> >                 ; in the ACTION property
> >
> >                 actionprops /
> >
> >                 ; the following is OPTIONAL,
> >                 ; and MAY occur more than once
> >
> >                 x-prop / iana-prop
> >
> >                 )
> > NEW
> >    alarmprop  =3D ; the elements herein may appear in any order,
> >                 ; and the order is not significant.
> >
> >                 action
> >                 trigger
> >
> >                 actionprops ; MUST match the action specified
> >                             ; in the ACTION property
> >
> >                 [*iana-prop]
> > END
> >
> > For =E2=80=9Caudiopropext=E2=80=9D:
> >
> > OLD
> >    audiopropext  =3D *(
> >
> >                    ; 'duration' and 'repeat' are both OPTIONAL,
> >                    ; and MUST NOT occur more than once each,
> >                    ; but if one occurs, so MUST the other
> >
> >                    duration / repeat /
> >
> >                    ; the following is OPTIONAL,
> >                    ; but MUST NOT occur more than once
> >
> >                    attach
> >
> >                    )
> > NEW
> >    audiopropext  =3D ; the elements herein may appear in any order,
> >                    ; and the order is not significant.
> >                    [duration repeat]
> >                    [attach]
> >                    )
> > END
> >
> > Is there really a good reason not to move in this direction?  The
> > mechanism of saying that everything can appear zero or more times, and
> > then limiting that with comments seems very poor.
> >
> > I agree and don't have any good reason to not just redefine existing
> constructs and use the ABNF as proposed above, especially since this is
> what was done in draft-ietf-calext-valarm-extensions.  If there are no
> objections I will go ahead and do this and post a diff.
> >
> >
> > =E2=80=94 Section 6.1 =E2=80=94
> >
> >       Certain
> >       kinds of alarm may not provide feedback as to when the calendar
> >       user sees them, for example email based alerts.
> >
> > Nit: This sentence isn=E2=80=99t properly ordered (and has a couple of =
other
> > nit-level errors).
> >
> > NEW
> >       Certain
> >       kinds of alarms, such as email-based alerts, might not provide
> >       feedback as to when the calendar user sees them.
> > END
> >
> > Fixed.
> >
> >
> > =E2=80=94 Section 7 =E2=80=94
> >
> >    Clients SHOULD add a "RELATED-TO" property to the new "VALARM"
> >    component with a value set to the "UID" property value of the
> >    "VALARM" component being snoozed.  If the "VALARM" component being
> >    snoozed does not already have a "UID" property, the client SHOULD ad=
d
> >    one.  The "RELATED-TO" property added to the new "VALARM" component
> >    SHOULD include a "RELTYPE" property parameter with a value set to
> >    "SNOOZE".
> >
> > Why the SHOULDs?  This is new function; why are these not MUSTs?
> >
> > I agree, the client is adding a new VALARM component for a specific
> purpose so we should standardize what it looks like.
> >
> >
> >    When the "snooze" alarm is triggered and dismissed the client SHOULD
> >    remove the corresponding "VALARM" component, or set the
> >    "ACKNOWLEDGED" property (see Section 6.1).  Alternatively, if the
> >    "snooze" alarm is itself "snoozed", the client SHOULD remove the
> >    original "snooze" alarm and create a new one, with the appropriate
> >    trigger time and relationship set.
> >
> > Same here about the SHOULDs.  Also, it=E2=80=99s not clear to me how th=
is
> > relates to the original alarm.  It would be good to say, explicitly,
> > that the original VALARM is not removed.  But also, is the
> > =E2=80=9CACKNOWLEDGED=E2=80=9D time on the original alarm changed to sh=
ow the time
> > that the snooze was dismissed?  If not, why not?  And is there a
> > reason to choose between the apparently equal alternatives presented
> > in the first sentence?  Or is the choice entirely up to the
> > implementation?
> >
> >
> > I'm leaning towards changing this text to the following:
> >
> >    When the "snooze" alarm is triggered and dismissed the client MUST d=
o
> >    one of the following with the corresponding "VALARM" component:
> >
> >    o  Set the "ACKNOWLEDGED" property (see Section 6.1)
> >
> >    o  Remove the component
> >
> >
> >    Alternatively, if the "snooze" alarm is itself "snoozed", the client
> >    MUST remove the original "snooze" alarm and create a new one, with
> >    the appropriate trigger time and relationship set.
> >
> >    Note that regardless of the final disposition of the "snooze" alarm
> >    when triggered, the original "VALARM" component is left unchanged.
> >
> >
> > Is this any better?
> >
> >
> > =E2=80=94 Section 7.1 =E2=80=94
> >
> >    This specification adds the "SNOOZE" relationship type for use with
> >    the "RELTYPE" property defined in Section 3.2.15 of [RFC5545].  This
> >    is used to relate a "snoozed" "VALARM" component to the original
> >    alarm that the "snooze" was generated for.
> >
> > Maybe I=E2=80=99m being too picky here, but I don=E2=80=99t think the R=
ELTYPE of
> > SNOOZE is used to relate the alarms: the UID property is used for
> > that.  Maybe =E2=80=9CThis is used when relating=E2=80=9D is better wor=
ding?
> >
> >
> > Yes, Fixed.
> >
> >
> > =E2=80=94 Section 8.1 =E2=80=94
> >
> >       When the property value is set to "ARRIVE", the alarm is triggere=
d
> >       when the calendar user agent arrives in the vicinity of any of th=
e
> >       specified locations.  When set to "DEPART", the alarm is triggere=
d
> >       when the calendar user agent departs from the vicinity of any
> >       specified locations.
> >
> > I think we need to more clearly specify =E2=80=9Cvicinity=E2=80=9D here=
, even if it=E2=80=99s
> > just to say that the definition is up to the implementation.  As it
> > is, I don=E2=80=99t know whether I need to depart from my kitchen, from=
 my
> > house, from my street, from my town, or whatever.
> >
> > Punted this as implementation defined.
> >
> >
> >       When the property value is set to "CONNECT", the alarm is
> >       triggered when the calendar user agent connects to a Bluetooth(R)
> >       [BTcore]-enabled automobile.  When set to "DISCONNECT", the alarm
> >       is triggered when the calendar user agent disconnects from a
> >       Bluetooth(R)-enabled automobile.
> >
> > Nit: It=E2=80=99s odd to have the citation in the middle of the compoun=
d
> > modifier.  I suggest rewriting to avoid the problem:
> >
> > NEW
> >       When the property value is set to "CONNECT", the alarm is
> >       triggered when the calendar user agent connects to an automobile
> >       that is enabled for Bluetooth(R) [BTcore].  When set to
> >       "DISCONNECT", the alarm is triggered when the calendar user agent
> >       disconnects from a Bluetooth(R)-enabled automobile.
> > END
> >
> > Fixed.
> >
> >
> >    Example:  The following is an example of this property:
> >    PROXIMITY:ARRIVE
> >
> > I think this example is useless, as it=E2=80=99s incomplete without the=
 geo
> > location.  And you have Section 8.2 immediately after, so why not just
> > remove this?
> >
> > Removed.
> >
> >
> > =E2=80=94 Section 11 =E2=80=94
> > Throughout this section, please specify the names and/or URIs of the
> > registries, to make it easier for both IANA and other readers to find
> > them.  For example, in Section 11.1:
> >
> > NEW
> >    This document defines the following new iCalendar properties to be
> >    added to the Properties registry defined in Section 8.2.3 of [RFC554=
5]
> >    and located here:
> >    <https://www.iana.org/assignments/icalendar#properties>
> > END
> >
> > Added.
> >
> >
> > --
> > Kenneth Murchison
> > Senior Software Developer
> > Fastmail US LLC
>


--=20
Daniel Migault
Ericsson

--00000000000091b9d805ba0a8726
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks Barry and Ken for the follow-up. I am happy to see =
the draft being moved forward.<div>Yours,=C2=A0<br>Daniel=C2=A0</div></div>=
<br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu=
, Jan 28, 2021 at 4:09 PM Barry Leiba &lt;<a href=3D"mailto:barryleiba@comp=
uter.org">barryleiba@computer.org</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">Thanks, Ken; this all looks good.=C2=A0 I&=
#39;ll wait for a revised I-D and<br>
move forward from there.<br>
<br>
Barry<br>
<br>
On Thu, Jan 28, 2021 at 3:37 PM Ken Murchison &lt;<a href=3D"mailto:murch@f=
astmail.com" target=3D"_blank">murch@fastmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Barry,<br>
&gt;<br>
&gt; Thanks for the review.=C2=A0 I *think* I hit all of your points inline=
.<br>
&gt;<br>
&gt;<br>
&gt; On 12/3/20 4:15 PM, Barry Leiba wrote:<br>
&gt;<br>
&gt; Most of my comments are minor, but there are a couple of things to<br>
&gt; discuss (particularly how to handle the ABNF).=C2=A0 I&#39;m going to =
put this<br>
&gt; in &quot;revised I-D needed&quot;, but let&#39;s talk about the things=
 that need<br>
&gt; discussion before submitting a revision for the others.<br>
&gt;<br>
&gt; =E2=80=94 Section 2 =E2=80=94<br>
&gt; There=E2=80=99s no need for the =E2=80=9C[1]=E2=80=9D citation, and it=
 only messes up idnits.<br>
&gt; Please remove it and the =E2=80=9CURLs=E2=80=9D section at the end.<br=
>
&gt;<br>
&gt; Fixed.<br>
&gt;<br>
&gt;<br>
&gt; =E2=80=94 Section 3 =E2=80=94<br>
&gt;<br>
&gt; My biggest issue here is with the ABNF, so let=E2=80=99s please have a=
<br>
&gt; discussion about it.<br>
&gt;<br>
&gt; First, some minor things:<br>
&gt;<br>
&gt; 1. This is probably a good time to pay attention to BCP 178 (RFC 6648)=
 by<br>
&gt; removing the x-prop construction (and x-name elsewhere in the draft).<=
br>
&gt;<br>
&gt; I have no problem removing these.=C2=A0 Anyone care to disagree?<br>
&gt;<br>
&gt;<br>
&gt; 2. Why is there a need to define new constructs (=E2=80=9Calarmcext=E2=
=80=9D,<br>
&gt; =E2=80=9Caudiopropext=E2=80=9D, and so on), rather than just re-defini=
ng the base ones<br>
&gt; (=E2=80=9Calarmc=E2=80=9D, =E2=80=9Caudioprop=E2=80=9D, =E2=80=A6)?=C2=
=A0 It seems to me that this just confuses<br>
&gt; things, and the point here is to make changes that are compatible, but=
<br>
&gt; more readily extensible.<br>
&gt;<br>
&gt; Now, the big one:<br>
&gt;<br>
&gt; 3. I have never liked the way iCalendar did its ABNF, to the point<br>
&gt; where I think it=E2=80=99s wrong and harmful, causing confusion and no=
t<br>
&gt; permitting automated processing of the ABNF.=C2=A0 It relies on normat=
ive<br>
&gt; comments where that=E2=80=99s not necessary, and ABNF was never intend=
ed to be<br>
&gt; usef that way.=C2=A0 Comments are meant to be explanatory, and normati=
ve<br>
&gt; comments are meant to be used only as a last resort, when you can=E2=
=80=99t<br>
&gt; express what you need in the formal language.=C2=A0 I would much rathe=
r<br>
&gt; limit the comments to a statment that elements can appear in any<br>
&gt; order, and then use the ABNF to convey whether the elements are<br>
&gt; required and how many times they can appear.<br>
&gt;<br>
&gt; Taking =E2=80=9Calarmprop=E2=80=9D as an example, here=E2=80=99s a re-=
write of it in the way<br>
&gt; ABNF should be representing it:<br>
&gt;<br>
&gt; OLD<br>
&gt;=C2=A0 =C2=A0 alarmprop=C2=A0 =3D *(<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0; the fol=
lowing are REQUIRED,<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0; but MUS=
T NOT occur more than once<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0action / =
trigger /<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0; one set=
 of action properties MUST be<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0; present=
 and MUST match the action specified<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0; in the =
ACTION property<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0actionpro=
ps /<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0; the fol=
lowing is OPTIONAL,<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0; and MAY=
 occur more than once<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0x-prop / =
iana-prop<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0)<br>
&gt; NEW<br>
&gt;=C2=A0 =C2=A0 alarmprop=C2=A0 =3D ; the elements herein may appear in a=
ny order,<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0; and the=
 order is not significant.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0action<br=
>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0trigger<b=
r>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0actionpro=
ps ; MUST match the action specified<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0; in the ACTION property<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[*iana-pr=
op]<br>
&gt; END<br>
&gt;<br>
&gt; For =E2=80=9Caudiopropext=E2=80=9D:<br>
&gt;<br>
&gt; OLD<br>
&gt;=C2=A0 =C2=A0 audiopropext=C2=A0 =3D *(<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ;=
 &#39;duration&#39; and &#39;repeat&#39; are both OPTIONAL,<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ;=
 and MUST NOT occur more than once each,<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ;=
 but if one occurs, so MUST the other<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 d=
uration / repeat /<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ;=
 the following is OPTIONAL,<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ;=
 but MUST NOT occur more than once<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 a=
ttach<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 )=
<br>
&gt; NEW<br>
&gt;=C2=A0 =C2=A0 audiopropext=C2=A0 =3D ; the elements herein may appear i=
n any order,<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ;=
 and the order is not significant.<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [=
duration repeat]<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [=
attach]<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 )=
<br>
&gt; END<br>
&gt;<br>
&gt; Is there really a good reason not to move in this direction?=C2=A0 The=
<br>
&gt; mechanism of saying that everything can appear zero or more times, and=
<br>
&gt; then limiting that with comments seems very poor.<br>
&gt;<br>
&gt; I agree and don&#39;t have any good reason to not just redefine existi=
ng constructs and use the ABNF as proposed above, especially since this is =
what was done in draft-ietf-calext-valarm-extensions.=C2=A0 If there are no=
 objections I will go ahead and do this and post a diff.<br>
&gt;<br>
&gt;<br>
&gt; =E2=80=94 Section 6.1 =E2=80=94<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Certain<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0kinds of alarm may not provide feedback as t=
o when the calendar<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0user sees them, for example email based aler=
ts.<br>
&gt;<br>
&gt; Nit: This sentence isn=E2=80=99t properly ordered (and has a couple of=
 other<br>
&gt; nit-level errors).<br>
&gt;<br>
&gt; NEW<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Certain<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0kinds of alarms, such as email-based alerts,=
 might not provide<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0feedback as to when the calendar user sees t=
hem.<br>
&gt; END<br>
&gt;<br>
&gt; Fixed.<br>
&gt;<br>
&gt;<br>
&gt; =E2=80=94 Section 7 =E2=80=94<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Clients SHOULD add a &quot;RELATED-TO&quot; property to t=
he new &quot;VALARM&quot;<br>
&gt;=C2=A0 =C2=A0 component with a value set to the &quot;UID&quot; propert=
y value of the<br>
&gt;=C2=A0 =C2=A0 &quot;VALARM&quot; component being snoozed.=C2=A0 If the =
&quot;VALARM&quot; component being<br>
&gt;=C2=A0 =C2=A0 snoozed does not already have a &quot;UID&quot; property,=
 the client SHOULD add<br>
&gt;=C2=A0 =C2=A0 one.=C2=A0 The &quot;RELATED-TO&quot; property added to t=
he new &quot;VALARM&quot; component<br>
&gt;=C2=A0 =C2=A0 SHOULD include a &quot;RELTYPE&quot; property parameter w=
ith a value set to<br>
&gt;=C2=A0 =C2=A0 &quot;SNOOZE&quot;.<br>
&gt;<br>
&gt; Why the SHOULDs?=C2=A0 This is new function; why are these not MUSTs?<=
br>
&gt;<br>
&gt; I agree, the client is adding a new VALARM component for a specific pu=
rpose so we should standardize what it looks like.<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 When the &quot;snooze&quot; alarm is triggered and dismis=
sed the client SHOULD<br>
&gt;=C2=A0 =C2=A0 remove the corresponding &quot;VALARM&quot; component, or=
 set the<br>
&gt;=C2=A0 =C2=A0 &quot;ACKNOWLEDGED&quot; property (see Section 6.1).=C2=
=A0 Alternatively, if the<br>
&gt;=C2=A0 =C2=A0 &quot;snooze&quot; alarm is itself &quot;snoozed&quot;, t=
he client SHOULD remove the<br>
&gt;=C2=A0 =C2=A0 original &quot;snooze&quot; alarm and create a new one, w=
ith the appropriate<br>
&gt;=C2=A0 =C2=A0 trigger time and relationship set.<br>
&gt;<br>
&gt; Same here about the SHOULDs.=C2=A0 Also, it=E2=80=99s not clear to me =
how this<br>
&gt; relates to the original alarm.=C2=A0 It would be good to say, explicit=
ly,<br>
&gt; that the original VALARM is not removed.=C2=A0 But also, is the<br>
&gt; =E2=80=9CACKNOWLEDGED=E2=80=9D time on the original alarm changed to s=
how the time<br>
&gt; that the snooze was dismissed?=C2=A0 If not, why not?=C2=A0 And is the=
re a<br>
&gt; reason to choose between the apparently equal alternatives presented<b=
r>
&gt; in the first sentence?=C2=A0 Or is the choice entirely up to the<br>
&gt; implementation?<br>
&gt;<br>
&gt;<br>
&gt; I&#39;m leaning towards changing this text to the following:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 When the &quot;snooze&quot; alarm is triggered and dismis=
sed the client MUST do<br>
&gt;=C2=A0 =C2=A0 one of the following with the corresponding &quot;VALARM&=
quot; component:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 o=C2=A0 Set the &quot;ACKNOWLEDGED&quot; property (see Se=
ction 6.1)<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 o=C2=A0 Remove the component<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Alternatively, if the &quot;snooze&quot; alarm is itself =
&quot;snoozed&quot;, the client<br>
&gt;=C2=A0 =C2=A0 MUST remove the original &quot;snooze&quot; alarm and cre=
ate a new one, with<br>
&gt;=C2=A0 =C2=A0 the appropriate trigger time and relationship set.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Note that regardless of the final disposition of the &quo=
t;snooze&quot; alarm<br>
&gt;=C2=A0 =C2=A0 when triggered, the original &quot;VALARM&quot; component=
 is left unchanged.<br>
&gt;<br>
&gt;<br>
&gt; Is this any better?<br>
&gt;<br>
&gt;<br>
&gt; =E2=80=94 Section 7.1 =E2=80=94<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 This specification adds the &quot;SNOOZE&quot; relationsh=
ip type for use with<br>
&gt;=C2=A0 =C2=A0 the &quot;RELTYPE&quot; property defined in Section 3.2.1=
5 of [RFC5545].=C2=A0 This<br>
&gt;=C2=A0 =C2=A0 is used to relate a &quot;snoozed&quot; &quot;VALARM&quot=
; component to the original<br>
&gt;=C2=A0 =C2=A0 alarm that the &quot;snooze&quot; was generated for.<br>
&gt;<br>
&gt; Maybe I=E2=80=99m being too picky here, but I don=E2=80=99t think the =
RELTYPE of<br>
&gt; SNOOZE is used to relate the alarms: the UID property is used for<br>
&gt; that.=C2=A0 Maybe =E2=80=9CThis is used when relating=E2=80=9D is bett=
er wording?<br>
&gt;<br>
&gt;<br>
&gt; Yes, Fixed.<br>
&gt;<br>
&gt;<br>
&gt; =E2=80=94 Section 8.1 =E2=80=94<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0When the property value is set to &quot;ARRI=
VE&quot;, the alarm is triggered<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0when the calendar user agent arrives in the =
vicinity of any of the<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0specified locations.=C2=A0 When set to &quot=
;DEPART&quot;, the alarm is triggered<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0when the calendar user agent departs from th=
e vicinity of any<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0specified locations.<br>
&gt;<br>
&gt; I think we need to more clearly specify =E2=80=9Cvicinity=E2=80=9D her=
e, even if it=E2=80=99s<br>
&gt; just to say that the definition is up to the implementation.=C2=A0 As =
it<br>
&gt; is, I don=E2=80=99t know whether I need to depart from my kitchen, fro=
m my<br>
&gt; house, from my street, from my town, or whatever.<br>
&gt;<br>
&gt; Punted this as implementation defined.<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0When the property value is set to &quot;CONN=
ECT&quot;, the alarm is<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0triggered when the calendar user agent conne=
cts to a Bluetooth(R)<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0[BTcore]-enabled automobile.=C2=A0 When set =
to &quot;DISCONNECT&quot;, the alarm<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0is triggered when the calendar user agent di=
sconnects from a<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0Bluetooth(R)-enabled automobile.<br>
&gt;<br>
&gt; Nit: It=E2=80=99s odd to have the citation in the middle of the compou=
nd<br>
&gt; modifier.=C2=A0 I suggest rewriting to avoid the problem:<br>
&gt;<br>
&gt; NEW<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0When the property value is set to &quot;CONN=
ECT&quot;, the alarm is<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0triggered when the calendar user agent conne=
cts to an automobile<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0that is enabled for Bluetooth(R) [BTcore].=
=C2=A0 When set to<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;DISCONNECT&quot;, the alarm is trigger=
ed when the calendar user agent<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0disconnects from a Bluetooth(R)-enabled auto=
mobile.<br>
&gt; END<br>
&gt;<br>
&gt; Fixed.<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Example:=C2=A0 The following is an example of this proper=
ty:<br>
&gt;=C2=A0 =C2=A0 PROXIMITY:ARRIVE<br>
&gt;<br>
&gt; I think this example is useless, as it=E2=80=99s incomplete without th=
e geo<br>
&gt; location.=C2=A0 And you have Section 8.2 immediately after, so why not=
 just<br>
&gt; remove this?<br>
&gt;<br>
&gt; Removed.<br>
&gt;<br>
&gt;<br>
&gt; =E2=80=94 Section 11 =E2=80=94<br>
&gt; Throughout this section, please specify the names and/or URIs of the<b=
r>
&gt; registries, to make it easier for both IANA and other readers to find<=
br>
&gt; them.=C2=A0 For example, in Section 11.1:<br>
&gt;<br>
&gt; NEW<br>
&gt;=C2=A0 =C2=A0 This document defines the following new iCalendar propert=
ies to be<br>
&gt;=C2=A0 =C2=A0 added to the Properties registry defined in Section 8.2.3=
 of [RFC5545]<br>
&gt;=C2=A0 =C2=A0 and located here:<br>
&gt;=C2=A0 =C2=A0 &lt;<a href=3D"https://www.iana.org/assignments/icalendar=
#properties" rel=3D"noreferrer" target=3D"_blank">https://www.iana.org/assi=
gnments/icalendar#properties</a>&gt;<br>
&gt; END<br>
&gt;<br>
&gt; Added.<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Kenneth Murchison<br>
&gt; Senior Software Developer<br>
&gt; Fastmail US LLC<br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><div dir=3D"ltr"><div>Daniel Migault<br></div><d=
iv>Ericsson</div></div></div>

--00000000000091b9d805ba0a8726--


From nobody Fri Jan 29 08:00:47 2021
Return-Path: <murch@fastmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EB883A1102; Fri, 29 Jan 2021 08:00:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=lPtBGswh; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=jAGDgl2k
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XQMiMGDmvGoZ; Fri, 29 Jan 2021 08:00:44 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36DD93A1101; Fri, 29 Jan 2021 08:00:44 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id B46AC5C037F; Fri, 29 Jan 2021 11:00:42 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Fri, 29 Jan 2021 11:00:42 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=b ISDRz9lG6VI8dT7ZExk0vl8jn/t/j9u8GnklyRZazA=; b=lPtBGswh3Fh2y2kbS LGtrBNl4MavqNJuQAexDMTEgV2B6vSLNan0EXgoaNNugj19GBUU9/mg+5kFq6CKJ o3WjXbVun1vqJdbMWNf02nYBUgkio2NpRb+mfFGJMJ3EqCXK7lLDiObdpvyrft7c j2ZO74j+BNz2HSmwh6a3J7id1h4eSypbEB/6XAmu+AbYv/qIPDCA2mW9t3KtrWvq 2ubEy/9KNeKTMl1cBtAbXimBl9hl3GrCDjBD0GqIgxPcGD81r4+dBNkMGcFufxm4 wf1JOfkR7EURBE2WCM9NxvY9O6s1cR+twwWax0k/EhKOF6o0Z+4+0tKU2WGBuuKz sA1mg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=bISDRz9lG6VI8dT7ZExk0vl8jn/t/j9u8GnklyRZa zA=; b=jAGDgl2kWSpeEtagpnlJ/xtnjfALimzJoLrSARf6eJ1dKXH0exnq2VkSw /yx3hVUAxEJ/aqBQDXU70NmRBGu5cljr88KTyymXjR9vMgAzJ8NVdnqEFMReSlxM lMdJCvCueGmpfU3AGDY/KiCZYbMvIwBAWRXi6a39HYav6dQYf3177aXHP+fQxO0h 00MK62kD8jUnRJMjSGJGGqTqxDl7w88AFdyA8ibt3YkHj+DjwHyL/qLr97jybDb6 dZlcW7e1xMO6hDF2OuVVsW5EletdeKLSV2m5blLrbqumKWMokARqGOX689COrA4b ZXONAiQGmZtgOXOa5UHB60klxK/Fw==
X-ME-Sender: <xms:KjEUYAvh7XXDIHCxsv8OhdPBYX3wxYPkmnlPnQunOkXe3XMc-ogx2Q> <xme:KjEUYBL1DebUSU4z3CdYZnNvP3cc4qJFgKNw_tde3HUUdZohuD-KE_Tiw8hGMvSyL dXFkE-I_P8HIQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedvgdekgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefmvghnucfo uhhrtghhihhsohhnuceomhhurhgthhesfhgrshhtmhgrihhlrdgtohhmqeenucggtffrrg htthgvrhhnpeehhffgteelueevuedthfefuedvueekgfekjeeuuefhtdelheetfffgvdet ueeujeenucfkphepjeegrdejjedrkeehrddvhedtnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepmhhurhgthhesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:KjEUYFnfek_97IW1EKScxhA_U1jPtc7Cd_lBXcIbq2f8Y0RNsItVaQ> <xmx:KjEUYKJ-9DPpNrViKyVCUKWkBhQq2TkP7rgQm2uboa-E7Gmwg6xv8w> <xmx:KjEUYC5GrWi6f76xfe0ctDdpi_KYE7uxUyA7UB-jk2kwWZrVU0wWuw> <xmx:KjEUYLhyCHmESWBVA3864uzxQ0Nup0HirVFW4-b5_AKpr5UYNujksw>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 30DD424005B; Fri, 29 Jan 2021 11:00:42 -0500 (EST)
To: Barry Leiba <barryleiba@computer.org>
Cc: draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
References: <CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com> <414b33de-c68a-5cbf-0f31-3b1b574f9e58@fastmail.com> <CALaySJJ87t5Ju7jF2chAXrevhg=rgANgkGUwwr_ocf7HpATozw@mail.gmail.com>
From: Ken Murchison <murch@fastmail.com>
Message-ID: <c409ceda-11ec-6cca-ca93-3e5e1d129c8c@fastmail.com>
Date: Fri, 29 Jan 2021 11:00:40 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CALaySJJ87t5Ju7jF2chAXrevhg=rgANgkGUwwr_ocf7HpATozw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/Cl1zsi-O1vtk7gRss9RaGSFA_Gc>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 16:00:45 -0000

Hi Barry,

On 1/28/21 4:09 PM, Barry Leiba wrote:
> 3. I have never liked the way iCalendar did its ABNF, to the point
>> where I think it’s wrong and harmful, causing confusion and not
>> permitting automated processing of the ABNF.  It relies on normative
>> comments where that’s not necessary, and ABNF was never intended to be
>> usef that way.  Comments are meant to be explanatory, and normative
>> comments are meant to be used only as a last resort, when you can’t
>> express what you need in the formal language.  I would much rather
>> limit the comments to a statment that elements can appear in any
>> order, and then use the ABNF to convey whether the elements are
>> required and how many times they can appear.
>>
>> Taking “alarmprop” as an example, here’s a re-write of it in the way
>> ABNF should be representing it:
>>
>> OLD
>>     alarmprop  = *(
>>
>>                  ; the following are REQUIRED,
>>                  ; but MUST NOT occur more than once
>>
>>                  action / trigger /
>>
>>                  ; one set of action properties MUST be
>>                  ; present and MUST match the action specified
>>                  ; in the ACTION property
>>
>>                  actionprops /
>>
>>                  ; the following is OPTIONAL,
>>                  ; and MAY occur more than once
>>
>>                  x-prop / iana-prop
>>
>>                  )
>> NEW
>>     alarmprop  = ; the elements herein may appear in any order,
>>                  ; and the order is not significant.
>>
>>                  action
>>                  trigger
>>
>>                  actionprops ; MUST match the action specified
>>                              ; in the ACTION property
>>
>>                  [*iana-prop]
>> END
>>
>> For “audiopropext”:
>>
>> OLD
>>     audiopropext  = *(
>>
>>                     ; 'duration' and 'repeat' are both OPTIONAL,
>>                     ; and MUST NOT occur more than once each,
>>                     ; but if one occurs, so MUST the other
>>
>>                     duration / repeat /
>>
>>                     ; the following is OPTIONAL,
>>                     ; but MUST NOT occur more than once
>>
>>                     attach
>>
>>                     )
>> NEW
>>     audiopropext  = ; the elements herein may appear in any order,
>>                     ; and the order is not significant.
>>                     [duration repeat]
>>                     [attach]
>>                     )
>> END
>>
>> Is there really a good reason not to move in this direction?  The
>> mechanism of saying that everything can appear zero or more times, and
>> then limiting that with comments seems very poor.


I started making these changes and then ran into what I think is the 
reason for the "ugly" ABNF.  With the above definition of alarmprop, how 
do we add the new properties defined in the later sections?  We have the 
incremental alternatives syntax in ABNF, but no incremental 
concatenation syntax.  So,

alarmprop =/ [uid]

Is incorrect.  I'd like to be able to do:

alarmprop =+ [uid]

Does the following make sense and is it allowed?

alarmprop = alarmprop [uid]

-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


From nobody Fri Jan 29 08:04:36 2021
Return-Path: <murch@fastmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E72263A1270; Fri, 29 Jan 2021 08:04:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=ncoyJA8p; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CQ0cl3Eg
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nSxE5lLSzClT; Fri, 29 Jan 2021 08:04:24 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 464393A1104; Fri, 29 Jan 2021 08:04:11 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 2F01A5C02D2; Fri, 29 Jan 2021 11:04:10 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 29 Jan 2021 11:04:10 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:from:to:cc:references:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=+ +k8VFCLxiZkxidC6aMB0upa9hU34mD5Sh8mfT4yGJk=; b=ncoyJA8pID90y/Zet O7/T4GM22/icr8gxXHoUYdtmayDqP6X3c3/ecSzEEF1rS9IIPWJRNhx9HGaxnmF8 a2faC/LAWszgomzXiJ4uURzRV9kpzQDnCviWYE3A2W+ah0i8HJwXV5s+liux370X kr4wt48UH7RTYjZL7H9yQ+8b/v7toptOalozzzPLH+FP1p6FHe4xZ2r3uJNEkqcX nXjCHrBDyz94oCyuSrOipH3DJYPyzWTZRYT2RsXVFR9clLHcH9jLyH9AQhVn6UbE YQVOrMpmO3iv86ElfGbQu6aZFgB5h8aCH9eRi1/Cp/4dJ3g0WzIXQMa5nv2cGdSW W09uQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=++k8VFCLxiZkxidC6aMB0upa9hU34mD5Sh8mfT4yG Jk=; b=CQ0cl3Eg4J4pcCTIWlFnfi/N9N7jcd/qb/RyRzby/qv27gc+oBKChk54g 5psHsn6GE1EYMCKj7SpRcXFsRlfnt5v11SVb7vyTXOEUtwahdM2/B0KrYcXcNH3V OwlKWylKvhpD8vvkmuZFp5SXsuj7OFLQjFjzJvU1aMhk9f53EQI6fb4ntPlKSH+Z ZYJdKqH9o4rDal2ERv5dAGCI5NeFwlUm4V9HXw/RU7DFeAmlVZuNP14qMDm4L+eT LYKOrBEw7henwv55Wn8iTWZ97YyvnImWOubAfYbVpIS/8YhDfAnie34407OJDds8 KswsOFi4+NxWK2IxBJWypMu7Kr2Mg==
X-ME-Sender: <xms:-TEUYPHsJ5Lf8Xc1B4Foc3zVOa6Bglm0Ceqkrutoto9UGmBE_cAyzQ> <xme:-TEUYMWEAs4JZHLMCoPgV3chPTrM3u-CIYdAIYz-5Hxlw3WAeoXYngAe2KzCyYv3W NK5GKAGiTVNHg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedvgdekgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuhffvfhfkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefmvghnucfo uhhrtghhihhsohhnuceomhhurhgthhesfhgrshhtmhgrihhlrdgtohhmqeenucggtffrrg htthgvrhhnpeefvdeuffeggfdugfehueegudefgeevuddtvdffgeevheeileevhfevffeu vdegvdenucfkphepjeegrdejjedrkeehrddvhedtnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepmhhurhgthhesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:-TEUYBLeVy0PfZPtflroQPvuKxepJ1eOpdyYOI0c84FEK0b0W8rgsg> <xmx:-TEUYNEladlNxH3X9Voah_AMhSWjX3SkObjEEZixzdi_399c5GWYqA> <xmx:-TEUYFWkrmB6WLq051P56-jyXJB_Iq7qsOiMYBWuheL7xLwwDwYHBg> <xmx:-jEUYGfrJ9ppypoxWPyaDwwXUxnIppeq79G3bBbTxqmvhvi5R12K5w>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id B25DC24005D; Fri, 29 Jan 2021 11:04:09 -0500 (EST)
From: Ken Murchison <murch@fastmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
References: <CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com> <414b33de-c68a-5cbf-0f31-3b1b574f9e58@fastmail.com> <CALaySJJ87t5Ju7jF2chAXrevhg=rgANgkGUwwr_ocf7HpATozw@mail.gmail.com> <c409ceda-11ec-6cca-ca93-3e5e1d129c8c@fastmail.com>
Message-ID: <ddaf10ca-7da9-2c36-9fdb-d15a9d35ef93@fastmail.com>
Date: Fri, 29 Jan 2021 11:04:09 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <c409ceda-11ec-6cca-ca93-3e5e1d129c8c@fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/XuTWYhwcRZJK6niY3ybmIyaMwaQ>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 16:04:34 -0000

On 1/29/21 11:00 AM, Ken Murchison wrote:
> Hi Barry,
>
> On 1/28/21 4:09 PM, Barry Leiba wrote:
>> 3. I have never liked the way iCalendar did its ABNF, to the point
>>> where I think it’s wrong and harmful, causing confusion and not
>>> permitting automated processing of the ABNF.  It relies on normative
>>> comments where that’s not necessary, and ABNF was never intended to be
>>> usef that way.  Comments are meant to be explanatory, and normative
>>> comments are meant to be used only as a last resort, when you can’t
>>> express what you need in the formal language.  I would much rather
>>> limit the comments to a statment that elements can appear in any
>>> order, and then use the ABNF to convey whether the elements are
>>> required and how many times they can appear.
>>>
>>> Taking “alarmprop” as an example, here’s a re-write of it in the way
>>> ABNF should be representing it:
>>>
>>> OLD
>>>     alarmprop  = *(
>>>
>>>                  ; the following are REQUIRED,
>>>                  ; but MUST NOT occur more than once
>>>
>>>                  action / trigger /
>>>
>>>                  ; one set of action properties MUST be
>>>                  ; present and MUST match the action specified
>>>                  ; in the ACTION property
>>>
>>>                  actionprops /
>>>
>>>                  ; the following is OPTIONAL,
>>>                  ; and MAY occur more than once
>>>
>>>                  x-prop / iana-prop
>>>
>>>                  )
>>> NEW
>>>     alarmprop  = ; the elements herein may appear in any order,
>>>                  ; and the order is not significant.
>>>
>>>                  action
>>>                  trigger
>>>
>>>                  actionprops ; MUST match the action specified
>>>                              ; in the ACTION property
>>>
>>>                  [*iana-prop]
>>> END
>>>
>>> For “audiopropext”:
>>>
>>> OLD
>>>     audiopropext  = *(
>>>
>>>                     ; 'duration' and 'repeat' are both OPTIONAL,
>>>                     ; and MUST NOT occur more than once each,
>>>                     ; but if one occurs, so MUST the other
>>>
>>>                     duration / repeat /
>>>
>>>                     ; the following is OPTIONAL,
>>>                     ; but MUST NOT occur more than once
>>>
>>>                     attach
>>>
>>>                     )
>>> NEW
>>>     audiopropext  = ; the elements herein may appear in any order,
>>>                     ; and the order is not significant.
>>>                     [duration repeat]
>>>                     [attach]
>>>                     )
>>> END
>>>
>>> Is there really a good reason not to move in this direction? The
>>> mechanism of saying that everything can appear zero or more times, and
>>> then limiting that with comments seems very poor.
>
>
> I started making these changes and then ran into what I think is the 
> reason for the "ugly" ABNF.  With the above definition of alarmprop, 
> how do we add the new properties defined in the later sections?  We 
> have the incremental alternatives syntax in ABNF, but no incremental 
> concatenation syntax.  So,
>
> alarmprop =/ [uid]
>
> Is incorrect.  I'd like to be able to do:
>
> alarmprop =+ [uid]
>
> Does the following make sense and is it allowed?
>
> alarmprop = alarmprop [uid]
>

Another alternative is to add the newly defined properties to the 
initial definition of alarmprop with a comment pointing to the relevant 
section in this document.  But that doesn't solve the problem of a 
future spec adding to alarmprop.

-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


From nobody Fri Jan 29 08:13:19 2021
Return-Path: <cyrus@daboo.name>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC4A13A110F; Fri, 29 Jan 2021 08:13:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yfmnTzY7MwCC; Fri, 29 Jan 2021 08:13:15 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 065B23A110E; Fri, 29 Jan 2021 08:13:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 608223040A1343; Fri, 29 Jan 2021 11:13:14 -0500 (EST)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FRGuDBwuWlAS; Fri, 29 Jan 2021 11:13:13 -0500 (EST)
Received: from cyrus.local (unknown [173.13.55.49]) by daboo.name (Postfix) with ESMTPSA id BF3DA3040A1331; Fri, 29 Jan 2021 11:13:13 -0500 (EST)
Date: Fri, 29 Jan 2021 11:13:13 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Ken Murchison <murch@fastmail.com>, Barry Leiba <barryleiba@computer.org>
cc: draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
Message-ID: <3c467b04-ac2e-416e-a3e1-317da196520d@cyrus.local>
In-Reply-To: <c409ceda-11ec-6cca-ca93-3e5e1d129c8c@fastmail.com>
References: <c409ceda-11ec-6cca-ca93-3e5e1d129c8c@fastmail.com>
X-Mailer: Mulberry/5.0.0a1 (macOS/10.16)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; size=1695
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/TC4BEGnPV-nL5zaib5s4Jh04-DQ>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 16:13:18 -0000

Hi Ken,

--On Fri, 29 Jan 2021 11:00:40 -0500 Ken Murchison <murch@fastmail.com>=20
wrote:


> I started making these changes and then ran into what I think is the reas=
on
> for the "ugly" ABNF.=C2=A0 With the above definition of alarmprop, how do=
 we add
> the new properties defined in the later sections?=C2=A0 We have the incre=
mental
> alternatives syntax in ABNF, but no incremental concatenation syntax.=C2=
=A0 So,
>
> alarmprop =3D/ [uid]
>
> Is incorrect.=C2=A0 I'd like to be able to do:
>
> alarmprop =3D+ [uid]
>
> Does the following make sense and is it allowed?
>
> alarmprop =3D alarmprop [uid]

I recall thinking about how to improve the ABNF in the past and not coming =

up with a feasible solution. My preference is to leave this alone as anyone=
=20
who is familiar with 5545 knows how to cope with the current "awkward"=20
syntax. Plus changing it here would mean we should do the same for all=20
pending calext drafts.

Whilst I think Barry's proposed changes are a step in the right direction, =
I=20
do not believe they really manage the stated goal of allowing the ABNF to b=
e=20
machine parsed because there are still "normative comments" present to deal=
=20
with the fact that ABNF itself does not have an "unordered list of elements=
"=20
construct. Plus ABNF does not have anything to say about the concept of=20
"normative comments".

If we want to solve this properly then we should do something similar to=20
HTTP (https://tools.ietf.org/html/rfc7230#section-7), and create our own=20
ABNF rule for unordered list. That way ABNF parsers can be extended to=20
understand the new rule (and not comments) and deal with it. Of course such=
=20
a change should really be done as an update to 5545 and not this spec.

--=20
Cyrus Daboo


From nobody Fri Jan 29 08:15:21 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D96C23A110E; Fri, 29 Jan 2021 08:15:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IVZFV1apEgh1; Fri, 29 Jan 2021 08:15:18 -0800 (PST)
Received: from mail-lj1-f174.google.com (mail-lj1-f174.google.com [209.85.208.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 218473A1106; Fri, 29 Jan 2021 08:15:18 -0800 (PST)
Received: by mail-lj1-f174.google.com with SMTP id l12so11090421ljc.3; Fri, 29 Jan 2021 08:15:17 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=KVmw1zl+niTKl2D5Kf9X9lmj3pA9cy3A8hVDmpwH4wY=; b=loy6PqHnk6Lx3UvAROuDmxPjh76IGkrokZac8RvHBakGdN9je0mDXFYQ8GyWC2b1lH NaqHqoowftz1kqjs1hN35DBoNi+IQIepvJnDprGPdiXt7TzomTIkXEm2VmEYP/ckH8jf ga8MkrCIUT1fk+PEjCuQTVGnF0i851c831fXOqueeunOLTgi9VG1m1BNjOrtG0ehqWEI I3a0TyJ4MOSyXLrFQD5y4gbdVkB++A8VfFBNA3QuMyyD5ABIFc5Tqs9v9bSwOVnjY/wd ENA5l8mw9vIX8xcACsjxrLhpAjZNsfn5mH/PjcKX844aG9Ef5hg+LBvIAUthyefRvBb3 z/7g==
X-Gm-Message-State: AOAM532eAEB+cFHmkYMuXGro6ooXPQh7RMW0K9wYFfCxEjWXDBQsCuiR p0xPP3Xzc/9iuFcddKOGAjaNG4gmmk8xZ7mEKhE=
X-Google-Smtp-Source: ABdhPJxgamJ/jdyeyiYIoXtDXwTiymxdLxUeNRI1ni/o9rE99ZDZgECZG9eleiMQUeUWUMuctK0P6ek/jnrWhannaNU=
X-Received: by 2002:a2e:959a:: with SMTP id w26mr2753671ljh.113.1611936916150;  Fri, 29 Jan 2021 08:15:16 -0800 (PST)
MIME-Version: 1.0
References: <CALaySJL4QA2WcahDb=dO0uO1yOqc3AtRx0RYGMCSLCeC=xk9Jw@mail.gmail.com> <414b33de-c68a-5cbf-0f31-3b1b574f9e58@fastmail.com> <CALaySJJ87t5Ju7jF2chAXrevhg=rgANgkGUwwr_ocf7HpATozw@mail.gmail.com> <c409ceda-11ec-6cca-ca93-3e5e1d129c8c@fastmail.com> <ddaf10ca-7da9-2c36-9fdb-d15a9d35ef93@fastmail.com>
In-Reply-To: <ddaf10ca-7da9-2c36-9fdb-d15a9d35ef93@fastmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 29 Jan 2021 11:15:04 -0500
Message-ID: <CALaySJ+F05D9WCQ7JS4oChm-oiOkBVYaNrXr7Ru=13650TAPoQ@mail.gmail.com>
To: Ken Murchison <murch@fastmail.com>
Cc: draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/TlyZGhn847xKUNlqi1YFVoOeQpA>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 16:15:20 -0000

On Fri, Jan 29, 2021 at 11:04 AM Ken Murchison <murch@fastmail.com> wrote:
>
>
> On 1/29/21 11:00 AM, Ken Murchison wrote:
> > Hi Barry,
> >
> > On 1/28/21 4:09 PM, Barry Leiba wrote:
> >> 3. I have never liked the way iCalendar did its ABNF, to the point
> >>> where I think it=E2=80=99s wrong and harmful, causing confusion and n=
ot
> >>> permitting automated processing of the ABNF.  It relies on normative
> >>> comments where that=E2=80=99s not necessary, and ABNF was never inten=
ded to be
> >>> usef that way.  Comments are meant to be explanatory, and normative
> >>> comments are meant to be used only as a last resort, when you can=E2=
=80=99t
> >>> express what you need in the formal language.  I would much rather
> >>> limit the comments to a statment that elements can appear in any
> >>> order, and then use the ABNF to convey whether the elements are
> >>> required and how many times they can appear.
> >>>
> >>> Taking =E2=80=9Calarmprop=E2=80=9D as an example, here=E2=80=99s a re=
-write of it in the way
> >>> ABNF should be representing it:
> >>>
> >>> OLD
> >>>     alarmprop  =3D *(
> >>>
> >>>                  ; the following are REQUIRED,
> >>>                  ; but MUST NOT occur more than once
> >>>
> >>>                  action / trigger /
> >>>
> >>>                  ; one set of action properties MUST be
> >>>                  ; present and MUST match the action specified
> >>>                  ; in the ACTION property
> >>>
> >>>                  actionprops /
> >>>
> >>>                  ; the following is OPTIONAL,
> >>>                  ; and MAY occur more than once
> >>>
> >>>                  x-prop / iana-prop
> >>>
> >>>                  )
> >>> NEW
> >>>     alarmprop  =3D ; the elements herein may appear in any order,
> >>>                  ; and the order is not significant.
> >>>
> >>>                  action
> >>>                  trigger
> >>>
> >>>                  actionprops ; MUST match the action specified
> >>>                              ; in the ACTION property
> >>>
> >>>                  [*iana-prop]
> >>> END
> >>>
> >>> For =E2=80=9Caudiopropext=E2=80=9D:
> >>>
> >>> OLD
> >>>     audiopropext  =3D *(
> >>>
> >>>                     ; 'duration' and 'repeat' are both OPTIONAL,
> >>>                     ; and MUST NOT occur more than once each,
> >>>                     ; but if one occurs, so MUST the other
> >>>
> >>>                     duration / repeat /
> >>>
> >>>                     ; the following is OPTIONAL,
> >>>                     ; but MUST NOT occur more than once
> >>>
> >>>                     attach
> >>>
> >>>                     )
> >>> NEW
> >>>     audiopropext  =3D ; the elements herein may appear in any order,
> >>>                     ; and the order is not significant.
> >>>                     [duration repeat]
> >>>                     [attach]
> >>>                     )
> >>> END
> >>>
> >>> Is there really a good reason not to move in this direction? The
> >>> mechanism of saying that everything can appear zero or more times, an=
d
> >>> then limiting that with comments seems very poor.
> >
> >
> > I started making these changes and then ran into what I think is the
> > reason for the "ugly" ABNF.  With the above definition of alarmprop,
> > how do we add the new properties defined in the later sections?  We
> > have the incremental alternatives syntax in ABNF, but no incremental
> > concatenation syntax.  So,
> >
> > alarmprop =3D/ [uid]
> >
> > Is incorrect.  I'd like to be able to do:
> >
> > alarmprop =3D+ [uid]
> >
> > Does the following make sense and is it allowed?
> >
> > alarmprop =3D alarmprop [uid]
> >
>
> Another alternative is to add the newly defined properties to the
> initial definition of alarmprop with a comment pointing to the relevant
> section in this document.  But that doesn't solve the problem of a
> future spec adding to alarmprop.

The usual way to do this is, indeed, to put all of the properties
defined in this document into the initial definition... and to add an
extension element to allow other documents to add more, like this:

   alarmprop  =3D ; the elements herein may appear in any order,
                ; and the order is not significant.

                action
                trigger
                [uid]
                [*related]
                [acknowledged]
                [proximity [*structured-location] ]

                actionprops ; MUST match the action specified
                            ; in the ACTION property
                [*alarmprop-ext]
                [*iana-prop]

   alarmprop-ext =3D token ; extension point for future additions

--=20
Barry


From nobody Fri Jan 29 08:18:46 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A19A3A1114; Fri, 29 Jan 2021 08:18:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JnpgbFMUzkaA; Fri, 29 Jan 2021 08:18:43 -0800 (PST)
Received: from mail-lf1-f43.google.com (mail-lf1-f43.google.com [209.85.167.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8D253A1113; Fri, 29 Jan 2021 08:18:42 -0800 (PST)
Received: by mail-lf1-f43.google.com with SMTP id u25so13238372lfc.2; Fri, 29 Jan 2021 08:18:42 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=alELMElEyKAFWxsDrc/GDH/seNbUhTkfSO/eRoGUda0=; b=dwQi6Aws0LHiKjQsIsS0HlxEYzc3abfnpolGL8ClOp/icjV05CgULDn8uLXueLw/er +ZOUaReCUSr/iV7S//ipFVaLZ+AseGPhEs0//C+Pf5fhOCHySaT1wIkHnj+Fw58ESIjx VQ9mvNdPEZe7nBlr+va6DKOgCeQ87t223ZqQ0zOUDRz5iMYI11UcelJpht8VQd3IP86q PtxY7UUhbhCU2ktZxQ4ipNvLhNS68Dhau4DhWnPZs157fr57sTttVH2frgTdDJdcc3HK Ni41pofVWeMBQCQWExg9o9H2Drl/xgTbHzAO3LYl+qwXTLcYI1qf3ulWMmM1ibU+WX9Z KsbQ==
X-Gm-Message-State: AOAM532YK5ZmxAlp2nlg9QxyZO9iK714tzkji91Aig3F528qR8u6Nk7S uxI66l8uWt7ej+u31uw+Xl6Ip0KkCQOYllMGJ7Q=
X-Google-Smtp-Source: ABdhPJyKKXCNaZjcieQhUpTzpoPgDq7Nk7fpr70zjw6XnB8AGoijhsoAeJsgHeVicOKBKDYLoKlYBc9q9gaTh3hB8ek=
X-Received: by 2002:ac2:420a:: with SMTP id y10mr2428001lfh.377.1611937120436;  Fri, 29 Jan 2021 08:18:40 -0800 (PST)
MIME-Version: 1.0
References: <c409ceda-11ec-6cca-ca93-3e5e1d129c8c@fastmail.com> <3c467b04-ac2e-416e-a3e1-317da196520d@cyrus.local>
In-Reply-To: <3c467b04-ac2e-416e-a3e1-317da196520d@cyrus.local>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 29 Jan 2021 11:18:29 -0500
Message-ID: <CALaySJLNip6_vQHDcnEQpo90k27ppmiS8cTS-8-shTMKhBeMww@mail.gmail.com>
To: Cyrus Daboo <cyrus@daboo.name>
Cc: Ken Murchison <murch@fastmail.com>, draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/IHyDpFAAB_bq7o425sO57_3bkDs>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 16:18:45 -0000

Apart from my response just now, which proposes a way to handle this,
Cyrus might be right that it's not worth doing surgery on the ABNF,
bad though it be.  It's certainly true that anyone who'd been dealing
with 5545 already deals with the mess we have, and the right way to
fix it is in a 5545bis.

On the other hand, I'm torn, because if we *do* update 5545 to deal
with the ABNF, all the extensions that do things the same way will
need to be similarly updated.

In any case, please do as you (collectively) think best here, and I'm
not going to block the document if the consensus is that we should
leave it be for now.

Barry

On Fri, Jan 29, 2021 at 11:13 AM Cyrus Daboo <cyrus@daboo.name> wrote:
>
> Hi Ken,
>
> --On Fri, 29 Jan 2021 11:00:40 -0500 Ken Murchison <murch@fastmail.com>
> wrote:
>
>
> > I started making these changes and then ran into what I think is the reason
> > for the "ugly" ABNF.  With the above definition of alarmprop, how do we add
> > the new properties defined in the later sections?  We have the incremental
> > alternatives syntax in ABNF, but no incremental concatenation syntax.  So,
> >
> > alarmprop =/ [uid]
> >
> > Is incorrect.  I'd like to be able to do:
> >
> > alarmprop =+ [uid]
> >
> > Does the following make sense and is it allowed?
> >
> > alarmprop = alarmprop [uid]
>
> I recall thinking about how to improve the ABNF in the past and not coming
> up with a feasible solution. My preference is to leave this alone as anyone
> who is familiar with 5545 knows how to cope with the current "awkward"
> syntax. Plus changing it here would mean we should do the same for all
> pending calext drafts.
>
> Whilst I think Barry's proposed changes are a step in the right direction, I
> do not believe they really manage the stated goal of allowing the ABNF to be
> machine parsed because there are still "normative comments" present to deal
> with the fact that ABNF itself does not have an "unordered list of elements"
> construct. Plus ABNF does not have anything to say about the concept of
> "normative comments".
>
> If we want to solve this properly then we should do something similar to
> HTTP (https://tools.ietf.org/html/rfc7230#section-7), and create our own
> ABNF rule for unordered list. That way ABNF parsers can be extended to
> understand the new rule (and not comments) and deal with it. Of course such
> a change should really be done as an update to 5545 and not this spec.
>
> --
> Cyrus Daboo


From nobody Fri Jan 29 08:22:23 2021
Return-Path: <cyrus@daboo.name>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D6893A118C; Fri, 29 Jan 2021 08:22:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K6luYXT7Gmkj; Fri, 29 Jan 2021 08:22:14 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 57FA83A117B; Fri, 29 Jan 2021 08:22:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id AA7353040A15DD; Fri, 29 Jan 2021 11:22:13 -0500 (EST)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yPKjPgMzevzg; Fri, 29 Jan 2021 11:22:12 -0500 (EST)
Received: from cyrus.local (unknown [173.13.55.49]) by daboo.name (Postfix) with ESMTPSA id C7A883040A15CB; Fri, 29 Jan 2021 11:22:12 -0500 (EST)
Date: Fri, 29 Jan 2021 11:22:12 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Ken Murchison <murch@fastmail.com>, Barry Leiba <barryleiba@computer.org>,  draft-ietf-calext-valarm-extensions.all@ietf.org
cc: calsify@ietf.org
Message-ID: <e18328db-8dc0-439b-bb1d-800edeaf8d3b@cyrus.local>
In-Reply-To: <414b33de-c68a-5cbf-0f31-3b1b574f9e58@fastmail.com>
References: <414b33de-c68a-5cbf-0f31-3b1b574f9e58@fastmail.com>
X-Mailer: Mulberry/5.0.0a1 (macOS/10.16)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; size=896
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/GVP4RSl_9tm8kOSKhbqpsN1t_LU>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 16:22:22 -0000

Hi Ken,

--On Thu, 28 Jan 2021 15:37:44 -0500 Ken Murchison <murch@fastmail.com>=20
wrote:


>> =E2=80=94 Section 3 =E2=80=94
>>
>> My biggest issue here is with the ABNF, so let=E2=80=99s please have a
>> discussion about it.
>>
>> First, some minor things:
>>
>> 1. This is probably a good time to pay attention to BCP 178 (RFC 6648) by
>> removing the x-prop construction (and x-name elsewhere in the draft).
>
> I have no problem removing these.=C2=A0 Anyone care to disagree?

Technically this prevents anyone from extending the new items with=20
custom/vendor properties etc. So I am not in favor of removing the x- items=
=20
without some other form of vendor items being supported (e.g., I would like=
=20
to see us adopt the same scheme we used for vCard4 with a `VND-<PEN>-`=20
prefix: https://www.rfc-editor.org/rfc/rfc6350.html#section-10.2.2). But I =

don't think that is appropriate to do in this spec.

--=20
Cyrus Daboo


From nobody Fri Jan 29 08:35:18 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ACC33A11E7; Fri, 29 Jan 2021 08:35:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bgBz1T80KX3s; Fri, 29 Jan 2021 08:35:10 -0800 (PST)
Received: from mail-lf1-f54.google.com (mail-lf1-f54.google.com [209.85.167.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 358283A11C8; Fri, 29 Jan 2021 08:35:07 -0800 (PST)
Received: by mail-lf1-f54.google.com with SMTP id p21so13322176lfu.11; Fri, 29 Jan 2021 08:35:06 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=AAj/hwWUFkcvj2MAOxzZ4zWzxjajBP2vKmdIlxa+Zsc=; b=jFfBCTN8Z3zA6HelWUUUkZbz2fxX2na6Gjne6yKuYE2gH9VMl3ioTU0eVtnzmUpFu1 QbNoqwUbLiUwI1IivikDctDznta+LRGCaaDr5AKyvZDxDHo+OCqaBUcaPhtkKIvqttHK wzGZLAxUH+kRi4KV25tilkVuxkXlseUZJztSAA9mYfoeGrNbwSZVkeKyDKMBKD+6MoLi jFkxaH/vf1ucI+gBhVPvLgkprBzrORfTM8pIp6pKAqvhNFoxcGsT4OXUdeb1A/bgOZK9 37qeAwKDvg14upz8udcjcPsYSchumkPYTYHHJlBJrA1YhL1iJ5bQYsmR29NIf0cZcuOQ ph6Q==
X-Gm-Message-State: AOAM532UTf6wBAvkoA0LV0MwrWdo9Y+ebzV0NRJPrxAMmz7eH9pbq2PD htWHg9YashmtUjrufYgIZjVFu/0EJbJcFmfqns+dvQTL
X-Google-Smtp-Source: ABdhPJzP/S1j2ErDDhqmWg/VKtoJHBSJF7G+D05N1CGIq2i9Bftl/ORTTbrvm8BJdJADsnOgNpYRZRqahPSEwN2vqBE=
X-Received: by 2002:ac2:592a:: with SMTP id v10mr2534049lfi.123.1611938105089;  Fri, 29 Jan 2021 08:35:05 -0800 (PST)
MIME-Version: 1.0
References: <414b33de-c68a-5cbf-0f31-3b1b574f9e58@fastmail.com> <e18328db-8dc0-439b-bb1d-800edeaf8d3b@cyrus.local>
In-Reply-To: <e18328db-8dc0-439b-bb1d-800edeaf8d3b@cyrus.local>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 29 Jan 2021 11:34:53 -0500
Message-ID: <CALaySJLZEaOhXrG3Ho9UV051NS_zNOdJj1vk1vnbEuFqGBbzAQ@mail.gmail.com>
To: Cyrus Daboo <cyrus@daboo.name>
Cc: Ken Murchison <murch@fastmail.com>, draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/l1A2vDZDfjJ_ieR0qZZ6I_5YpCM>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 16:35:18 -0000

Sigh.  I guess this is true also.  If we leave the "x-" items in,
let's make sure the shepherd writeup calls out the BCP 178 issue and
explains why we're leaving them here.

Barry

On Fri, Jan 29, 2021 at 11:22 AM Cyrus Daboo <cyrus@daboo.name> wrote:
>
> Hi Ken,
>
> --On Thu, 28 Jan 2021 15:37:44 -0500 Ken Murchison <murch@fastmail.com>
> wrote:
>
>
> >> =E2=80=94 Section 3 =E2=80=94
> >>
> >> My biggest issue here is with the ABNF, so let=E2=80=99s please have a
> >> discussion about it.
> >>
> >> First, some minor things:
> >>
> >> 1. This is probably a good time to pay attention to BCP 178 (RFC 6648)=
 by
> >> removing the x-prop construction (and x-name elsewhere in the draft).
> >
> > I have no problem removing these.  Anyone care to disagree?
>
> Technically this prevents anyone from extending the new items with
> custom/vendor properties etc. So I am not in favor of removing the x- ite=
ms
> without some other form of vendor items being supported (e.g., I would li=
ke
> to see us adopt the same scheme we used for vCard4 with a `VND-<PEN>-`
> prefix: https://www.rfc-editor.org/rfc/rfc6350.html#section-10.2.2). But =
I
> don't think that is appropriate to do in this spec.
>
> --
> Cyrus Daboo


From nobody Fri Jan 29 08:54:23 2021
Return-Path: <murch@fastmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46AFC3A1164; Fri, 29 Jan 2021 08:54:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=Z8rTTTMT; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Nfr9mxiq
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pJGVEwkPGaGU; Fri, 29 Jan 2021 08:54:20 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CE1B3A1165; Fri, 29 Jan 2021 08:54:20 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id A74205C026B; Fri, 29 Jan 2021 11:54:19 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 29 Jan 2021 11:54:19 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=J 3vWVKPRXQ+38w1X/KumGBfiXHGbZ/mCU8A5/BNXzEE=; b=Z8rTTTMT2b220VS7C qakrx7Q8PHY0DWeATd/fwtK3mtM+Sa+I52x52JrBcY3oqqGm8c9ghuAukPPZkogs D2vqa3ID5Ve0BYfnKXh64Q9z9G+ZBffWd3S7svARmjqzLimh7jsINACX8rsDZIsF VVpYCSJziU1diPnLckme4ew3bA8Rhm6TBJwottuU0f3yNTxUjvWsdMj8PRWpQs9v Haxj+c+z6WrZ4etDXOVYx4aNcE3DZo6E5In0WLBuDIBZ6rRXJyVFIbu0Y5U5Co7y ewhg00lgFhHTGyfiSFsevaMsx7gcJP7lAAMM5688W2ck0j5psdKxwSjINFMTmy/t NqVNg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=J3vWVKPRXQ+38w1X/KumGBfiXHGbZ/mCU8A5/BNXz EE=; b=Nfr9mxiqB6c3DyVo8+Ts3BkIZHkAt40xELRGd4EH4zZm2/GD43UFhoUAc o4BevFewqV5i+aj1v9cNrM9xjQ3oE7cYnnDmPRSak4LJFaBFAZ4xN03eHbXSGNl/ LQBkaaoIds1e0/zk8JGMCUmpB2PmfUb6ot1KJYEQNMvrzBt07pQw1XTnZZ8yGiQv g3p3zMBwueGbtq96hkPfZj6xiBZPPhB+LTjDHGDaIMuKSjF9fJ5tNQKnfTqWsChK O0MbU0sdcGqmp6omHITTD5baM6f/jBL4w0YzZdcj3oGevBZcfLMg96/FduDBIoUB zcib3rs5tE9UnckzFCwNRJQ1ZRtfw==
X-ME-Sender: <xms:uz0UYOTMpAc0XpDMj8qzx-G3JhXj1sdIflh1ZeLOKW9Ame3S4bTtxw> <xme:uz0UYDwxZjNNjOQ9PdJoHcSOPe6XLv2m0GUz4SJGQlPlqcqBIdEMWIMI6ka5dk5Yt mcWqou0t40cbA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedvgdelhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpefmvghnucfo uhhrtghhihhsohhnuceomhhurhgthhesfhgrshhtmhgrihhlrdgtohhmqeenucggtffrrg htthgvrhhnpedvueetudegieffieetvdfhiedutedvgeejkeekudetvddvvdduteejvefg hfdvkeenucffohhmrghinhepihgvthhfrdhorhhgnecukfhppeejgedrjeejrdekhedrvd ehtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehm uhhrtghhsehfrghsthhmrghilhdrtghomh
X-ME-Proxy: <xmx:uz0UYL02bxVRH4NMuwfvi30iYEe3cPXHaB4RgFuSPCx6cpSAdhFGqQ> <xmx:uz0UYKCIp6yFtjeHcatdaVF2NI1j75vWc800lOAAe5iqnCAX5yV0sA> <xmx:uz0UYHiw2PcQNglB_iSSb7OzD_tuNRUPEM7E4dyslXm83hgsuyBkAA> <xmx:uz0UYPYH64kHAkidWMl7Evj38V1tdU6R_ks84b8WPO3TLg4gWP1xDw>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 2818A24005B; Fri, 29 Jan 2021 11:54:19 -0500 (EST)
To: Cyrus Daboo <cyrus@daboo.name>, Barry Leiba <barryleiba@computer.org>
Cc: draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
References: <c409ceda-11ec-6cca-ca93-3e5e1d129c8c@fastmail.com> <3c467b04-ac2e-416e-a3e1-317da196520d@cyrus.local>
From: Ken Murchison <murch@fastmail.com>
Message-ID: <95d74648-c855-1e7f-f0f1-f4384c45e52c@fastmail.com>
Date: Fri, 29 Jan 2021 11:54:18 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <3c467b04-ac2e-416e-a3e1-317da196520d@cyrus.local>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/YD_Wb7gVQH9fGh0f0zDifh2GHlM>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 16:54:22 -0000

On 1/29/21 11:13 AM, Cyrus Daboo wrote:
> Hi Ken,
>
> --On Fri, 29 Jan 2021 11:00:40 -0500 Ken Murchison 
> <murch@fastmail.com> wrote:
>
>
>> I started making these changes and then ran into what I think is the 
>> reason
>> for the "ugly" ABNF.  With the above definition of alarmprop, how do 
>> we add
>> the new properties defined in the later sections?  We have the 
>> incremental
>> alternatives syntax in ABNF, but no incremental concatenation 
>> syntax.  So,
>>
>> alarmprop =/ [uid]
>>
>> Is incorrect.  I'd like to be able to do:
>>
>> alarmprop =+ [uid]
>>
>> Does the following make sense and is it allowed?
>>
>> alarmprop = alarmprop [uid]
>
> I recall thinking about how to improve the ABNF in the past and not 
> coming up with a feasible solution. My preference is to leave this 
> alone as anyone who is familiar with 5545 knows how to cope with the 
> current "awkward" syntax. Plus changing it here would mean we should 
> do the same for all pending calext drafts.
>
> Whilst I think Barry's proposed changes are a step in the right 
> direction, I do not believe they really manage the stated goal of 
> allowing the ABNF to be machine parsed because there are still 
> "normative comments" present to deal with the fact that ABNF itself 
> does not have an "unordered list of elements" construct. Plus ABNF 
> does not have anything to say about the concept of "normative comments".
>
> If we want to solve this properly then we should do something similar 
> to HTTP (https://tools.ietf.org/html/rfc7230#section-7), and create 
> our own ABNF rule for unordered list. That way ABNF parsers can be 
> extended to understand the new rule (and not comments) and deal with 
> it. Of course such a change should really be done as an update to 5545 
> and not this spec.


So, I went and took a look at what we have done in the past to extend 
the list of properties for a given component.  E.g., 
https://tools.ietf.org/html/rfc7986#section-4 
<https://tools.ietf.org/html/rfc7986#section-4>

Is what is done there to extend calprops, eventprop, etc technically 
correct?  Doesn't the use of the incremental alternative syntax mean 
that calprops can be the existing calprops OR the newly defined 
properties?  Or have I completely lost my ABNF bearings?

-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


From nobody Fri Jan 29 09:15:42 2021
Return-Path: <murch@fastmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D45213A1193; Fri, 29 Jan 2021 09:15:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=BPEcqFTj; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=D/WiQIYr
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2AWCVqKgR9RQ; Fri, 29 Jan 2021 09:15:39 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D78073A1191; Fri, 29 Jan 2021 09:15:38 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 30E8F5C00A2; Fri, 29 Jan 2021 12:15:37 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 29 Jan 2021 12:15:37 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:from:to:cc:references:message-id:date:mime-version :in-reply-to:content-type; s=fm2; bh=eB8GtS7OR35iVdB6+H20n7IN1K+ 2HBOp6Z1tsB9hmfU=; b=BPEcqFTjQ8wf9ACQo0U6wSwB/IS1n+H4+gdPLIFY78Y VDEWTEy2z4ZRc2QI1ablTENJXdCImBEa8U7PT6OXC024e4wpaTiXmagbecN8RLja S8whHC8pyL4p2OoyIrYNwKNM4IUxdx3TLIeVROHXcpO4MP6gBfr1VVSqRTCZ6Svi ZEI1nA8+wDTbGhs/yTMQ4aUvlpKkMizm6FsHRamIJmcb8r7FyMYVFCATaYoyb7lY jLNt2ii9MvHdOj3udAUyJXVnJ0ErHPoktnKaLuJS3qNadY1iT28BrHylrwLVCGAY gwTkCAS06s4IdP3KHRxv693sgC9L5ZgHnHM2zH17bUw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=eB8GtS 7OR35iVdB6+H20n7IN1K+2HBOp6Z1tsB9hmfU=; b=D/WiQIYrYNm9/RZ9yKqzal W0OzR6KeeCWooiigAxY48mI/1qTWLXYX1j1+NEISi4QDTqN7ifnvqPtslmplN1v/ pe6Qnlfj8h4Q96QuAEygat1R4cB7RKjGh+ZF2B/MmqqSiGlWmc6vJDCoA9IiHMo1 TNsby6TrNpGp28uVSq74WoDBfv7wLdrskUbrLaHSo8gWPVIwH6udOxVUq1ZFcN0g 6O2eZPots0PtX942IbnQEJdANRRmma+nHxovnxPmE0S+R0LCpmbvpiY+G6YS1gLN uhT3gDbZLBn96SUl5CREdW0rZ/HrvQJNtDwXEXAoyxwYcfd4Ft+mlG4yTB6KmWuw ==
X-ME-Sender: <xms:uEIUYE19g6LvrDwVKds8i42QOTWQ81x4dsP2FDaasI-Q1Kn6eNVZmg> <xme:uEIUYPGjgeUNUoApC6lfdMKzGyTMZmSmUs7jZJ88g-U-YPsrFkIpR26cduQ9DpGgt 8Io5xneua3t8A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedvgdellecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuhffvfhfkffgfgggjtgesrgdtreertdefjeenucfhrhhomhepmfgvnhcuofhu rhgthhhishhonhcuoehmuhhrtghhsehfrghsthhmrghilhdrtghomheqnecuggftrfgrth htvghrnhepvdefueejffdukedtfffhjeejtdffudejhfdvkeeujeffjeevgeekffelgefg vddvnecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepjeegrdejjedrkeehrddvhe dtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhu rhgthhesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:uEIUYM6rCUmUoBgIn5-AfzWqU0MKXRKesamiomW_pl8mxA6pgPxO_Q> <xmx:uEIUYN2mRBTYMAoPchtFAv6TTXLug2Xh_2ewsvmE4U-sZuoP-CYAnQ> <xmx:uEIUYHFeJQUy_aDHynBxlGla60jMhmgQ71YVSBvMSkIDBy5Ax6oghw> <xmx:uUIUYNPQxLxLJi6DkL56eE58nEx0LyPteVISfwA2gSoYwlF5gVGUUA>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 46E1824005B; Fri, 29 Jan 2021 12:15:36 -0500 (EST)
From: Ken Murchison <murch@fastmail.com>
To: Cyrus Daboo <cyrus@daboo.name>, Barry Leiba <barryleiba@computer.org>
Cc: draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
References: <c409ceda-11ec-6cca-ca93-3e5e1d129c8c@fastmail.com> <3c467b04-ac2e-416e-a3e1-317da196520d@cyrus.local> <95d74648-c855-1e7f-f0f1-f4384c45e52c@fastmail.com>
Message-ID: <5ef5dc43-72e1-6a90-0bce-79f854629d73@fastmail.com>
Date: Fri, 29 Jan 2021 12:15:35 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <95d74648-c855-1e7f-f0f1-f4384c45e52c@fastmail.com>
Content-Type: multipart/alternative; boundary="------------F542F175A9878E3050F202F4"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/SileU_2YRgVGGTz7DWd7vREJteQ>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 17:15:41 -0000

This is a multi-part message in MIME format.
--------------F542F175A9878E3050F202F4
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit


On 1/29/21 11:54 AM, Ken Murchison wrote:
>
> On 1/29/21 11:13 AM, Cyrus Daboo wrote:
>> Hi Ken,
>>
>> --On Fri, 29 Jan 2021 11:00:40 -0500 Ken Murchison 
>> <murch@fastmail.com> wrote:
>>
>>
>>> I started making these changes and then ran into what I think is the 
>>> reason
>>> for the "ugly" ABNF.  With the above definition of alarmprop, how do 
>>> we add
>>> the new properties defined in the later sections?  We have the 
>>> incremental
>>> alternatives syntax in ABNF, but no incremental concatenation 
>>> syntax.  So,
>>>
>>> alarmprop =/ [uid]
>>>
>>> Is incorrect.  I'd like to be able to do:
>>>
>>> alarmprop =+ [uid]
>>>
>>> Does the following make sense and is it allowed?
>>>
>>> alarmprop = alarmprop [uid]
>>
>> I recall thinking about how to improve the ABNF in the past and not 
>> coming up with a feasible solution. My preference is to leave this 
>> alone as anyone who is familiar with 5545 knows how to cope with the 
>> current "awkward" syntax. Plus changing it here would mean we should 
>> do the same for all pending calext drafts.
>>
>> Whilst I think Barry's proposed changes are a step in the right 
>> direction, I do not believe they really manage the stated goal of 
>> allowing the ABNF to be machine parsed because there are still 
>> "normative comments" present to deal with the fact that ABNF itself 
>> does not have an "unordered list of elements" construct. Plus ABNF 
>> does not have anything to say about the concept of "normative comments".
>>
>> If we want to solve this properly then we should do something similar 
>> to HTTP (https://tools.ietf.org/html/rfc7230#section-7), and create 
>> our own ABNF rule for unordered list. That way ABNF parsers can be 
>> extended to understand the new rule (and not comments) and deal with 
>> it. Of course such a change should really be done as an update to 
>> 5545 and not this spec.
>
>
> So, I went and took a look at what we have done in the past to extend 
> the list of properties for a given component.  E.g., 
> https://tools.ietf.org/html/rfc7986#section-4 
> <https://tools.ietf.org/html/rfc7986#section-4>
>
> Is what is done there to extend calprops, eventprop, etc technically 
> correct?  Doesn't the use of the incremental alternative syntax mean 
> that calprops can be the existing calprops OR the newly defined 
> properties?  Or have I completely lost my ABNF bearings?


The problem as I see it is in RFC 5545.  Its defines:

        icalbody   = calprops component

        calprops   = *(
                   ;
                   ; The following are REQUIRED,
                   ; but MUST NOT occur more than once.
                   ;
                   prodid / version /
                   ;
                   ; The following are OPTIONAL,
                   ; but MUST NOT occur more than once.
                   ;
                   calscale / method /
                   ;
                   ; The following are OPTIONAL,
                   ; and MAY occur more than once.
                   ;

                   x-prop / iana-prop
                   ;
                   )

        component  = 1*(eventc / todoc / journalc / freebusyc /
                     timezonec / iana-comp / x-comp)


If this was instead:

        icalbody   = *calprops 1*component

        calprops   =
                   ;
                   ; The following are REQUIRED,
                   ; but MUST NOT occur more than once.
                   ;
                   prodid / version /
                   ;
                   ; The following are OPTIONAL,
                   ; but MUST NOT occur more than once.
                   ;
                   calscale / method /
                   ;
                   ; The following are OPTIONAL,
                   ; and MAY occur more than once.
                   ;


                   x-prop / iana-prop
                   ;

        component  = eventc / todoc / journalc / freebusyc /
                     timezonec / iana-comp / x-comp


Then, something like:

calprops =/ uid / name

component =/ VPOLL

Would do what we want.

-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


--------------F542F175A9878E3050F202F4
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 1/29/21 11:54 AM, Ken Murchison
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:95d74648-c855-1e7f-f0f1-f4384c45e52c@fastmail.com">
      <br>
      On 1/29/21 11:13 AM, Cyrus Daboo wrote:
      <br>
      <blockquote type="cite">Hi Ken,
        <br>
        <br>
        --On Fri, 29 Jan 2021 11:00:40 -0500 Ken Murchison
        <a class="moz-txt-link-rfc2396E" href="mailto:murch@fastmail.com">&lt;murch@fastmail.com&gt;</a> wrote:
        <br>
        <br>
        <br>
        <blockquote type="cite">I started making these changes and then
          ran into what I think is the reason
          <br>
          for the "ugly" ABNF.  With the above definition of alarmprop,
          how do we add
          <br>
          the new properties defined in the later sections?  We have the
          incremental
          <br>
          alternatives syntax in ABNF, but no incremental concatenation
          syntax.  So,
          <br>
          <br>
          alarmprop =/ [uid]
          <br>
          <br>
          Is incorrect.  I'd like to be able to do:
          <br>
          <br>
          alarmprop =+ [uid]
          <br>
          <br>
          Does the following make sense and is it allowed?
          <br>
          <br>
          alarmprop = alarmprop [uid]
          <br>
        </blockquote>
        <br>
        I recall thinking about how to improve the ABNF in the past and
        not coming up with a feasible solution. My preference is to
        leave this alone as anyone who is familiar with 5545 knows how
        to cope with the current "awkward" syntax. Plus changing it here
        would mean we should do the same for all pending calext drafts.
        <br>
        <br>
        Whilst I think Barry's proposed changes are a step in the right
        direction, I do not believe they really manage the stated goal
        of allowing the ABNF to be machine parsed because there are
        still "normative comments" present to deal with the fact that
        ABNF itself does not have an "unordered list of elements"
        construct. Plus ABNF does not have anything to say about the
        concept of "normative comments".
        <br>
        <br>
        If we want to solve this properly then we should do something
        similar to HTTP (<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/rfc7230#section-7">https://tools.ietf.org/html/rfc7230#section-7</a>),
        and create our own ABNF rule for unordered list. That way ABNF
        parsers can be extended to understand the new rule (and not
        comments) and deal with it. Of course such a change should
        really be done as an update to 5545 and not this spec.
        <br>
      </blockquote>
      <br>
      <br>
      So, I went and took a look at what we have done in the past to
      extend the list of properties for a given component.  E.g.,
      <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/rfc7986#section-4">https://tools.ietf.org/html/rfc7986#section-4</a>
      <a class="moz-txt-link-rfc2396E" href="https://tools.ietf.org/html/rfc7986#section-4">&lt;https://tools.ietf.org/html/rfc7986#section-4&gt;</a>
      <br>
      <br>
      Is what is done there to extend calprops, eventprop, etc
      technically correct?  Doesn't the use of the incremental
      alternative syntax mean that calprops can be the existing calprops
      OR the newly defined properties?  Or have I completely lost my
      ABNF bearings?
      <br>
    </blockquote>
    <p><br>
    </p>
    <p>The problem as I see it is in RFC 5545.  Its defines:<br>
    </p>
    <pre class="newpage">       icalbody   = calprops component

       calprops   = *(
                  ;
                  ; The following are REQUIRED,
                  ; but MUST NOT occur more than once.
                  ;
                  prodid / version /
                  ;
                  ; The following are OPTIONAL,
                  ; but MUST NOT occur more than once.
                  ;
                  calscale / method /
                  ;
                  ; The following are OPTIONAL,
                  ; and MAY occur more than once.
                  ;

                  x-prop / iana-prop
                  ;
                  )

       component  = 1*(eventc / todoc / journalc / freebusyc /
                    timezonec / iana-comp / x-comp)</pre>
    <p><br>
    </p>
    <p>If this was instead:</p>
    <pre class="newpage">       icalbody   = *calprops 1*component

       calprops   =
                  ;
                  ; The following are REQUIRED,
                  ; but MUST NOT occur more than once.
                  ;
                  prodid / version /
                  ;
                  ; The following are OPTIONAL,
                  ; but MUST NOT occur more than once.
                  ;
                  calscale / method /
                  ;
                  ; The following are OPTIONAL,
                  ; and MAY occur more than once.
                  ;


                  x-prop / iana-prop
                  ;

       component  = eventc / todoc / journalc / freebusyc /
                    timezonec / iana-comp / x-comp


</pre>
    <p>Then, something like:</p>
    <p><font face="monospace">calprops =/ uid / name</font></p>
    <p><font face="monospace">component =/ VPOLL</font></p>
    <p>Would do what we want.<br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC</pre>
  </body>
</html>

--------------F542F175A9878E3050F202F4--


From nobody Fri Jan 29 09:18:54 2021
Return-Path: <cyrus@daboo.name>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 710613A1191; Fri, 29 Jan 2021 09:18:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sXK6pkw3C5ZQ; Fri, 29 Jan 2021 09:18:52 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id E7E503A1196; Fri, 29 Jan 2021 09:18:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 4ABE13040A231A; Fri, 29 Jan 2021 12:18:51 -0500 (EST)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rkRL2DoKGH9V; Fri, 29 Jan 2021 12:18:50 -0500 (EST)
Received: from cyrus.local (unknown [173.13.55.49]) by daboo.name (Postfix) with ESMTPSA id D609D3040A2308; Fri, 29 Jan 2021 12:18:50 -0500 (EST)
Date: Fri, 29 Jan 2021 12:18:50 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Ken Murchison <murch@fastmail.com>, Barry Leiba <barryleiba@computer.org>
cc: draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
Message-ID: <634d1ffe-8dc8-4a7c-bd9b-11068869d868@cyrus.local>
In-Reply-To: <95d74648-c855-1e7f-f0f1-f4384c45e52c@fastmail.com>
References: <95d74648-c855-1e7f-f0f1-f4384c45e52c@fastmail.com>
X-Mailer: Mulberry/5.0.0a1 (macOS/10.16)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; size=1538
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/sgc4_v3ziiI08xtm0RF24qkucB0>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 17:18:54 -0000

Hi Ken,

--On Fri, 29 Jan 2021 11:54:18 -0500 Ken Murchison <murch@fastmail.com>=20
wrote:


> So, I went and took a look at what we have done in the past to extend the
> list of properties for a given component.=C2=A0 E.g.,
> https://tools.ietf.org/html/rfc7986#section-4
> <https://tools.ietf.org/html/rfc7986#section-4>
>
> Is what is done there to extend calprops, eventprop, etc technically
> correct?=C2=A0 Doesn't the use of the incremental alternative syntax mean=
 that
> calprops can be the existing calprops OR the newly defined properties?=C2=
=A0 Or
> have I completely lost my ABNF bearings?

I don't see in issue there: use of the "=3D/" ABNF syntax to extend existin=
g=20
definitions is fine. All 7986 is doing is adding new properties into=20
existing components.

The specific issue for valarm is that the original 5545 definition of=20
"alarmc" was not granular enough to allow use of "=3D/" for extending the=20
definitions. Hence the need for the "alarmcext" version of the syntax in th=
e=20
new extension which splits things up so there is "alarmprop" for properties=
=20
common to all alarm actions, and "actionprops" which specifies the=20
action-speific ones and can be extended with new actions. Ideally this new =

syntax would replace the existing one in any update to 5545.

This also emphasises my earlier point about keeping "x-prop", because the=20
new spec is simply providing an alternative way of defining the existing=20
5545 syntax, without altering it in any way. Since 5545 has "x-prop", this =

alternative syntax should keep it.

--=20
Cyrus Daboo


From nobody Fri Jan 29 09:29:37 2021
Return-Path: <cyrus@daboo.name>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 256463A11AD; Fri, 29 Jan 2021 09:29:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l3fs5KJr1cu1; Fri, 29 Jan 2021 09:29:34 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 631BE3A11A9; Fri, 29 Jan 2021 09:29:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id AA88B3040A2580; Fri, 29 Jan 2021 12:29:33 -0500 (EST)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oor8_3Rv1yWg; Fri, 29 Jan 2021 12:29:33 -0500 (EST)
Received: from cyrus.local (unknown [173.13.55.49]) by daboo.name (Postfix) with ESMTPSA id 589BE3040A256E; Fri, 29 Jan 2021 12:29:33 -0500 (EST)
Date: Fri, 29 Jan 2021 12:29:32 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Ken Murchison <murch@fastmail.com>, Barry Leiba <barryleiba@computer.org>
cc: draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
Message-ID: <3ea8c984-1245-44d0-8b19-35c6d9b271d5@cyrus.local>
In-Reply-To: <5ef5dc43-72e1-6a90-0bce-79f854629d73@fastmail.com>
References: <5ef5dc43-72e1-6a90-0bce-79f854629d73@fastmail.com>
X-Mailer: Mulberry/5.0.0a1 (macOS/10.16)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; size=772
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/-Ul6MlOaAHb99Dit_GrTD1LSha4>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 17:29:36 -0000

Hi Ken,

--On Fri, 29 Jan 2021 12:15:35 -0500 Ken Murchison <murch@fastmail.com>=20
wrote:

> The problem as I see it is in RFC 5545.=C2=A0 Its defines:
>
>       icalbody   =3D calprops component

> The problem as I see it is in RFC 5545.=C2=A0 Its defines:
>
>        icalbody   =3D calprops component

> Then, something like:
>
> calprops =3D/ uid / name
>
> component =3D/ VPOLL
>
> Would do what we want.

I don't think there is anything wrong with the existing syntax. I think thi=
s=20
is correct:

These two:

  a =3D *(x / y)

  a /=3D *(z)

are equivalent to:

  a =3D *(x /y) / *(z)

which is equivalent to:

  a=3D *(x / y / z)

Admittedly, your alternative syntax is easier to understand in that you=20
don't have to think too hard about how all the ABNF operators combine.
=20
--=20
Cyrus Daboo


From nobody Fri Jan 29 09:34:35 2021
Return-Path: <murch@fastmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B32573A11B5; Fri, 29 Jan 2021 09:34:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=UPOUYSqH; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=fi9/85Jc
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qgTjcd23aGeV; Fri, 29 Jan 2021 09:34:31 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B155F3A11B2; Fri, 29 Jan 2021 09:34:31 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 237D05C025B; Fri, 29 Jan 2021 12:34:30 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 29 Jan 2021 12:34:30 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=T W3x+jxG0qMRqvMLW9xPjHOEyZW/cmSpSOu8qr0jsJY=; b=UPOUYSqHFWnr5izmm 1ziXBpEzLjPXZaM5fXQSMgRu5z55kteiqAsGUJUl5yBZEJnt8PtZYqyrksmRKc40 rxhxonbWUYD3j/LHRnrI23NXliR9YbnlPMVubeIeoMgogA3Z1mkVpnM4qBKWwDx0 otbxqK4miWFhWO6D+0h54KE6mxVepCD80O0aWC7lxRi7sEtsNN6J5FpnK+nLllxh zLSpaWTcXulOSx+eknB5Me6djYqeEaScyQ9/h4yFC0Ezg0DOU0olKAcf7ffro9DA wWAJ3jMvqGsPQjFrVgEhxKQ2q5tOksBOpMq3fn0IJIj9zBAbXcPj97GpBjFZGQfZ 0uhUQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=TW3x+jxG0qMRqvMLW9xPjHOEyZW/cmSpSOu8qr0js JY=; b=fi9/85Jcis2q/LWGB5jHlxSqIiktI3H9eBFuasyg8QVC6h7rizrMae/tF XBjYoWKyMtJyAOqyWHMVjo1l11+SzXz7op3Bnutzb/cIU20WQAeBsa+FaPCbUERO m1vBj+0k+cQDLmqk0zBY94XbM1ST0OCKYfNunilSZ5ecgsdonBmzR+ogVcj4UZar bIxRGrqXtrfYyoMVidLLyDKhTn9NsOmZHghJJv4rq7CzhGaE7I0NsM08AVNwbdyC bVwLlR7EwzmdsbYBlFdWwivyX+8fqJqYp14HEoW7R9htGzH0Vplu2N0D03jxm3+p DQHpJ6gNhavQYLhgdwxUT4gkikYoQ==
X-ME-Sender: <xms:JUcUYMRvZROyiuxgscTTn3uiAk7cp7qID69EXCqhe3F3ZT-txzhAJA> <xme:JUcUYJzKQK2zDmDQ_Y_hzXlHgAW6PpR3ZiKBYXxaQ-YxGADV6Bqq8cehT7759SxL3 wImOiKCdMqF9Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedvgddutdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomhepmfgvnhcu ofhurhgthhhishhonhcuoehmuhhrtghhsehfrghsthhmrghilhdrtghomheqnecuggftrf grthhtvghrnhepvdeutedugeeiffeitedvhfeiudetvdegjeekkedutedvvddvudetjeev gffhvdeknecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepjeegrdejjedrkeehrd dvhedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep mhhurhgthhesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:JUcUYJ3EzgFnUeqYnVs2kng1ncuTn6fp62-5dcFbJukY_eVveYIrNw> <xmx:JUcUYAAxTjVmeQRb6WhP9ABTUSctbXM2g9PGDCHF942DcWPIAfqJFQ> <xmx:JUcUYFihlFrmKS_HYR8S999otx9g7inPTZPZveuB9lviw1h_fVx8CA> <xmx:JkcUYFZc2p9KEtkCMMjvEDRHmethJIurtOdJAV_29BkqFPnjBCiMJQ>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 1657924005D; Fri, 29 Jan 2021 12:34:29 -0500 (EST)
To: Cyrus Daboo <cyrus@daboo.name>, Barry Leiba <barryleiba@computer.org>
Cc: draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
References: <5ef5dc43-72e1-6a90-0bce-79f854629d73@fastmail.com> <3ea8c984-1245-44d0-8b19-35c6d9b271d5@cyrus.local>
From: Ken Murchison <murch@fastmail.com>
Message-ID: <71bae7d6-8750-62c4-d331-dd05c4ba62b1@fastmail.com>
Date: Fri, 29 Jan 2021 12:34:28 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <3ea8c984-1245-44d0-8b19-35c6d9b271d5@cyrus.local>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/LJGWEECtrY50Ev72Akv-uLeh7p4>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 17:34:34 -0000

On 1/29/21 12:29 PM, Cyrus Daboo wrote:
> Hi Ken,
>
> --On Fri, 29 Jan 2021 12:15:35 -0500 Ken Murchison 
> <murch@fastmail.com> wrote:
>
>> The problem as I see it is in RFC 5545. Its defines:
>>
>>       icalbody   = calprops component
>
>> The problem as I see it is in RFC 5545. Its defines:
>>
>>        icalbody   = calprops component
>
>> Then, something like:
>>
>> calprops =/ uid / name
>>
>> component =/ VPOLL
>>
>> Would do what we want.
>
> I don't think there is anything wrong with the existing syntax. I 
> think this is correct:
>
> These two:
>
>  a = *(x / y)
>
>  a /= *(z)
>
> are equivalent to:
>
>  a = *(x /y) / *(z)


I read the above as zero or more 'x' and/or 'y'  OR zero or more 'z'.  I 
don't see how https://tools.ietf.org/html/rfc5234#section-3.2 
<https://tools.ietf.org/html/rfc5234#section-3.2> would allow having 'x' 
and 'z' together.


>
> which is equivalent to:
>
>  a= *(x / y / z)
>
> Admittedly, your alternative syntax is easier to understand in that 
> you don't have to think too hard about how all the ABNF operators 
> combine.
>
-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


From nobody Fri Jan 29 10:01:44 2021
Return-Path: <murch@fastmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA5383A11D7; Fri, 29 Jan 2021 10:01:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=Kvju6Iqx; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=HTiPMQCz
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8U_gxycqRI9B; Fri, 29 Jan 2021 10:01:41 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52B2B3A0CB7; Fri, 29 Jan 2021 10:01:41 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 88E9A5C0209; Fri, 29 Jan 2021 13:01:40 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 29 Jan 2021 13:01:40 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:from:to:cc:references:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=G UiedXGhX2qg8XylR8zhlsNzGMWwn6c2wxUYnNHOmXg=; b=Kvju6IqxwPzty5Fpb 79o5es+ZyCLfkBfRtkFYliISz1MzU3YkEPuUuV/KlaLRu1pq2k7PwIksGjqoylt+ rxRjsyGULNdBAgyK7e6481l6s/8O1uvNeOl0TZ2SF5Zb8LFboQpVV8kokOtfdXIB xN4+EgHXNimCtrCrgJcWZPERAPZVHfN6ONgX2k35Sb2tnSdz9TfrH6ny/Ldcqzn2 8wsM9wahIYTqR43ftyx8Sn0NsoEsH6tTdnUY1timNkJZwg5WV/7/VeyNCVcyZd+I Lx90ebvbAYeurXRusCey0UXEAQVAx7Fn3GqqX3M4TLmlHTitTMPfyxFpLlYVh0n/ cn42w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=GUiedXGhX2qg8XylR8zhlsNzGMWwn6c2wxUYnNHOm Xg=; b=HTiPMQCz8FYBfdkHRsLYKwt2tBdkpKm/PvW6nCZgHozdVrlGNTWvnlJxb ESZIyD/HSWVQsy1YXGgNJMtow7e/e5U+0/mYgwwwuutoLzzPkmmMYDDHObS/VfSx lhWlqIQmljqXMloV6fVl/DN9iDFwjuecMJCh/+rDCSvINLwScK9pbxjKLVlDc2VT GWuMZEJ1efKp5Kk0mKMo5N2oKg03NuWtMCd3aY2rx9lTviqvG2J/dDITZMzinKvd JwOFGpAs0Owa07tKH7P4s1LZZt2i9iGqBTeezYSNjXfeDlJDGvrxeUNHjPqU1rrQ NPT8SnPWlyrPvx3GlrCSaQ6q14Mxg==
X-ME-Sender: <xms:hE0UYPBdTw5CyYsYNYBUpYQy7eNB5PDqmUzZIUF4f7o6JwUzRensgw> <xme:hE0UYFi7ZmeIOM4O0BXiaigsdYJGtt5I7MaLqw4VM03HTOVN27_p6YIgxSmKMd7Qb E3KY0gmf3OIiQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedvgddutdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffhvfhfkffffgggjggtgfesthekredttdefjeenucfhrhhomhepmfgvnhcu ofhurhgthhhishhonhcuoehmuhhrtghhsehfrghsthhmrghilhdrtghomheqnecuggftrf grthhtvghrnhepjefgueefgedufeeitedvfeejvefhjeehtdevtdefuefffeeigefgudfg vdekkeffnecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepjeegrdejjedrkeehrd dvhedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep mhhurhgthhesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:hE0UYKksj08A5QDR3BIgCqm3zIIeQYbUPtZffva5maJEaJdVxTzfaQ> <xmx:hE0UYBxGxYD2EuuYOv9xDOAjtV9wD2LNfFudgWNBg_OEf-sBDnjjvA> <xmx:hE0UYETGDzcq5B3nVOFpQMon12qosGLFPCtRyyzgozSrDx1DmYJwTw> <xmx:hE0UYPJ4XMGpM5DxkyDfcz0K0XHA-Wq5IIyry1jEOdRtdSy8QeUDnA>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id E82A424005E; Fri, 29 Jan 2021 13:01:39 -0500 (EST)
From: Ken Murchison <murch@fastmail.com>
To: Cyrus Daboo <cyrus@daboo.name>, Barry Leiba <barryleiba@computer.org>
Cc: draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
References: <5ef5dc43-72e1-6a90-0bce-79f854629d73@fastmail.com> <3ea8c984-1245-44d0-8b19-35c6d9b271d5@cyrus.local> <71bae7d6-8750-62c4-d331-dd05c4ba62b1@fastmail.com>
Message-ID: <6b55aa41-0153-3335-d053-f8bf084a2938@fastmail.com>
Date: Fri, 29 Jan 2021 13:01:39 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <71bae7d6-8750-62c4-d331-dd05c4ba62b1@fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/Rx2EorcSYHZv-etvzVl6COUjK4E>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 18:01:43 -0000

On 1/29/21 12:34 PM, Ken Murchison wrote:
>
> On 1/29/21 12:29 PM, Cyrus Daboo wrote:
>> Hi Ken,
>>
>> --On Fri, 29 Jan 2021 12:15:35 -0500 Ken Murchison 
>> <murch@fastmail.com> wrote:
>>
>>> The problem as I see it is in RFC 5545. Its defines:
>>>
>>>       icalbody   = calprops component
>>
>>> The problem as I see it is in RFC 5545. Its defines:
>>>
>>>        icalbody   = calprops component
>>
>>> Then, something like:
>>>
>>> calprops =/ uid / name
>>>
>>> component =/ VPOLL
>>>
>>> Would do what we want.
>>
>> I don't think there is anything wrong with the existing syntax. I 
>> think this is correct:
>>
>> These two:
>>
>>  a = *(x / y)
>>
>>  a /= *(z)
>>
>> are equivalent to:
>>
>>  a = *(x /y) / *(z)
>
>
> I read the above as zero or more 'x' and/or 'y'  OR zero or more 'z'.  
> I don't see how https://tools.ietf.org/html/rfc5234#section-3.2 
> <https://tools.ietf.org/html/rfc5234#section-3.2> would allow having 
> 'x' and 'z' together.


To continue my thought. Given:

a = *(x /y) / *(z)

*a would equate to: *(x / y / z)

-- 

Kenneth Murchison
Senior Software Developer
Fastmail US LLC


From nobody Fri Jan 29 10:02:35 2021
Return-Path: <barryleiba@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2B263A11D8; Fri, 29 Jan 2021 10:02:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8kJ4pgxQJsaJ; Fri, 29 Jan 2021 10:02:32 -0800 (PST)
Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 546DF3A11D7; Fri, 29 Jan 2021 10:02:32 -0800 (PST)
Received: by mail-lj1-f180.google.com with SMTP id m22so4074290ljj.4; Fri, 29 Jan 2021 10:02:32 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gHB1aBDF/DG2tZw3pnV5sB1ht4UNYOZcSBCSK3SomfY=; b=mJM/whpWsu024IwlGKcaQy5JYLb9YSpmEyq9qWrLrhyLhfFfSoJwDqqiBTP+yMnAyj q05gUeWLUsXacCsEBrB0BcXQ6dRg4gqeLsWMzyJHllDIpRrCnGYwWwsnAbpyJFj73HVj WbOCUhzmUrrYSlBVBekdKB4oEdHbg2nImapQxtseeh9NzjS/F6JA5RV5fx4exzdD1gSu 8/WHgvRvQItV2+jp1ocdAxVFUGE0kfWE2VqNDZG3olmVHeyKqHvPbute6Sl598Ng7IGH rUkHsPYnJ24J1HKcnfmy6npFwOSrpb5hd0FYIvBH5zE0f6y7Jn8ehOR3pZqXNMiGGD+W SyZA==
X-Gm-Message-State: AOAM531Enm3B0tufpKwo758aaOtKYwOiEZmYFIH6CQaNgOYEypE3WfQH t4aNyGChm9Jjdg03Ynn3+pTblPxR90AM5uno54k=
X-Google-Smtp-Source: ABdhPJzcDz3BXiyG6cNgJB4+lNRR2/Bs/MUWNbXa9J7j32DK5HXgfS9CNH2oCO5swVVAuQ3LnitKuJLizNQiNM6i3IU=
X-Received: by 2002:a2e:7d04:: with SMTP id y4mr3028561ljc.65.1611943348957; Fri, 29 Jan 2021 10:02:28 -0800 (PST)
MIME-Version: 1.0
References: <5ef5dc43-72e1-6a90-0bce-79f854629d73@fastmail.com> <3ea8c984-1245-44d0-8b19-35c6d9b271d5@cyrus.local> <71bae7d6-8750-62c4-d331-dd05c4ba62b1@fastmail.com>
In-Reply-To: <71bae7d6-8750-62c4-d331-dd05c4ba62b1@fastmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 29 Jan 2021 13:02:17 -0500
Message-ID: <CALaySJ+8hshp87wWiBh6+6cg1vbAG_DnPSUSKM++6_C49vmU1g@mail.gmail.com>
To: Ken Murchison <murch@fastmail.com>
Cc: Cyrus Daboo <cyrus@daboo.name>, draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/19dVO_q0KX0PGFtgKQ4QcTeYYEs>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 18:02:34 -0000

Ken, I think your interpretation is correct.

One way to handle the various combinations of required "things",
optional-but-once things, and optional-multiple things is something
like this:

   abc = req opt-once *("," opt-mult)

   req = r1 "," r2 "," r3

   opt-once = ["," o1] ["," o2] ["," o3]

   opt-multi = m1 / m2 / m3 / r3

In this case, r3 is required once and can appear multiple times, so
it's in both places.

The problem with that mechanism is that it's hard to extend anything
except opt-multi.  You can do

   opt-multi =/ m4

...but you can't do anything similar with req or opt-once.  And also,
req and opt-once are ordered, which is sad.

I'm chatting with Dave Crocker and some others about whether it makes
sense to extend ABNF to support unordered lists.

Anyway, the more we talk about this, the more convinced I am that
Cyrus is right: we should leave the ABNF alone here, and deal with
properly updating it in an update of the base doc, if we ever get to
that.

Barry

On Fri, Jan 29, 2021 at 12:34 PM Ken Murchison <murch@fastmail.com> wrote:
>
>
> On 1/29/21 12:29 PM, Cyrus Daboo wrote:
> > Hi Ken,
> >
> > --On Fri, 29 Jan 2021 12:15:35 -0500 Ken Murchison
> > <murch@fastmail.com> wrote:
> >
> >> The problem as I see it is in RFC 5545. Its defines:
> >>
> >>       icalbody   = calprops component
> >
> >> The problem as I see it is in RFC 5545. Its defines:
> >>
> >>        icalbody   = calprops component
> >
> >> Then, something like:
> >>
> >> calprops =/ uid / name
> >>
> >> component =/ VPOLL
> >>
> >> Would do what we want.
> >
> > I don't think there is anything wrong with the existing syntax. I
> > think this is correct:
> >
> > These two:
> >
> >  a = *(x / y)
> >
> >  a /= *(z)
> >
> > are equivalent to:
> >
> >  a = *(x /y) / *(z)
>
>
> I read the above as zero or more 'x' and/or 'y'  OR zero or more 'z'.  I
> don't see how https://tools.ietf.org/html/rfc5234#section-3.2
> <https://tools.ietf.org/html/rfc5234#section-3.2> would allow having 'x'
> and 'z' together.
>
>
> >
> > which is equivalent to:
> >
> >  a= *(x / y / z)
> >
> > Admittedly, your alternative syntax is easier to understand in that
> > you don't have to think too hard about how all the ABNF operators
> > combine.
> >
> --
> Kenneth Murchison
> Senior Software Developer
> Fastmail US LLC
>


From nobody Fri Jan 29 10:10:16 2021
Return-Path: <murch@fastmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EBBE3A11E5; Fri, 29 Jan 2021 10:10:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=gACEXy12; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=gyeFP4va
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MLndrsHuxURh; Fri, 29 Jan 2021 10:10:12 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8AC83A11E4; Fri, 29 Jan 2021 10:10:12 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 4B4205C0334; Fri, 29 Jan 2021 13:10:09 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 29 Jan 2021 13:10:09 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=H nKYrDqi1SjUR18uP36vHod56SLdG2BCRPqGQTEBP6Y=; b=gACEXy12VwZSfK2Jk /0WXrqUqVCOZEQax0szNGwHX4OcIuEuM7PO9YQh71KoUqmp9wV8pgQv1mBxLrKuZ dY7wtYrhjXEap0T/Or/8GZe/oux+6PG4gIaT/NUhkcmUE8s7o/zqqhs9SS8I6/5q 3h8lDDH2IkwIVmMDBMM3QJdGNJA7Yf71bLIG3c6lo3T517sI1IzZisB3i7zK2G5N xJkHXMILQAAlttFfrRaTUPfVWkl/bfwPJFB2LNOrmOKB2tlfRkIaQmm0DB1HdzJf E2r8tOyuzzeXCIn5J8aV8iPoUVM50tnwgKyHF6/+rDLZpebGmPxQfHJiXQYBXHJg XaRvg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=HnKYrDqi1SjUR18uP36vHod56SLdG2BCRPqGQTEBP 6Y=; b=gyeFP4vap/TyDv+f1lcxbmhT6qmXAcT6WW3VbGpNEh0IDORv6W4+YkPTq nQZn3Qlz4eZNIdmlZeVFJ9spJT8hKia9ai+r6B1ngsdu4jrJf/cdYsPgQ0qHjr6Q d1VBS3oDtEa0ggTZzmVlcmuBojX1CSN5hcbtusFz+JPbhAM1tnh2YNnar43dIeqe d7YFtBpBOIF4RHYchExYnnjoSc9lb4WwYU4EUnRy0YGmc8/+mBMQdrG8X3hDs3U8 nj0ywzZruE6ZJIg8kn6UH+03pCkPpYpzq+MLGtHkZ2GdX4cQWQu4RN2kAySSsWht ktww9DmiYKLQ/EMtE4xF8mpLoulpQ==
X-ME-Sender: <xms:f08UYK1tk5rQYft0nJf4pUKOEUDpM6nLKVDZkXrhfQ_mn0ahm43yKQ> <xme:f08UYIxZcdrXdYPkPNy9HJszhngqjIP1-Z7d9CrMc9BMTNyeT6vZel-g1QHZuWHm- V-jkz0yed7maA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedvgddutdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthejredttdefjeenucfhrhhomhepmfgvnhcu ofhurhgthhhishhonhcuoehmuhhrtghhsehfrghsthhmrghilhdrtghomheqnecuggftrf grthhtvghrnhepiedulefhjefhueehlefgueetvefhtdffheetjeffgfduffetvedutedv ueduudetnecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepjeegrdejjedrkeehrd dvhedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep mhhurhgthhesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:f08UYPXpO_6fPS9EYwmgWsG2TIKmCaI7PrCNKbMOMsesQusFn_JRww> <xmx:f08UYE-TrpN0PeNClgMOscK1ic_qC7MlmMIF22xIweIjXdD08x2zmQ> <xmx:f08UYCsqhOE8gfXY9Padn1g3nofBfHzV1i19fTa43m2Vcepi-1M66Q> <xmx:gU8UYH7gZYWQYHAvATW94VYswQi449i4T7e7tlVm0zry4RStgR3atQ>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id BED34240068; Fri, 29 Jan 2021 13:10:07 -0500 (EST)
To: Barry Leiba <barryleiba@computer.org>
Cc: Cyrus Daboo <cyrus@daboo.name>, draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
References: <5ef5dc43-72e1-6a90-0bce-79f854629d73@fastmail.com> <3ea8c984-1245-44d0-8b19-35c6d9b271d5@cyrus.local> <71bae7d6-8750-62c4-d331-dd05c4ba62b1@fastmail.com> <CALaySJ+8hshp87wWiBh6+6cg1vbAG_DnPSUSKM++6_C49vmU1g@mail.gmail.com>
From: Ken Murchison <murch@fastmail.com>
Message-ID: <6b11cc6f-6ea5-15d4-7025-ba5af6190c4d@fastmail.com>
Date: Fri, 29 Jan 2021 13:10:07 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CALaySJ+8hshp87wWiBh6+6cg1vbAG_DnPSUSKM++6_C49vmU1g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/WGHRtDhKich3YV6B0tXOVXvRcGY>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 18:10:14 -0000

On 1/29/21 1:02 PM, Barry Leiba wrote:
> Ken, I think your interpretation is correct.
>
> One way to handle the various combinations of required "things",
> optional-but-once things, and optional-multiple things is something
> like this:
>
>     abc = req opt-once *("," opt-mult)
>
>     req = r1 "," r2 "," r3
>
>     opt-once = ["," o1] ["," o2] ["," o3]
>
>     opt-multi = m1 / m2 / m3 / r3
>
> In this case, r3 is required once and can appear multiple times, so
> it's in both places.
>
> The problem with that mechanism is that it's hard to extend anything
> except opt-multi.  You can do
>
>     opt-multi =/ m4
>
> ...but you can't do anything similar with req or opt-once.  And also,
> req and opt-once are ordered, which is sad.
>
> I'm chatting with Dave Crocker and some others about whether it makes
> sense to extend ABNF to support unordered lists.
>
> Anyway, the more we talk about this, the more convinced I am that
> Cyrus is right: we should leave the ABNF alone here, and deal with
> properly updating it in an update of the base doc, if we ever get to
> that.


Agreed that we shouldn't try to reinvent the wheel here, but still I 
think our current use of alarmprop =/ foo in this draft follows previous 
use, but doesn't actually do what we want.

I also think this is an issue in 
https://tools.ietf.org/html/draft-ietf-calext-eventpub-extensions-18#section-4 
<https://tools.ietf.org/html/draft-ietf-calext-eventpub-extensions-18#section-4>


-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


From nobody Fri Jan 29 11:00:49 2021
Return-Path: <cyrus@daboo.name>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A4723A1232; Fri, 29 Jan 2021 11:00:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FAgCilWghPyD; Fri, 29 Jan 2021 11:00:46 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 01B043A1231; Fri, 29 Jan 2021 11:00:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 1BB353040A3965; Fri, 29 Jan 2021 14:00:41 -0500 (EST)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eYInHL9vP6aE; Fri, 29 Jan 2021 14:00:38 -0500 (EST)
Received: from 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa (unknown [173.13.55.49]) by daboo.name (Postfix) with ESMTPSA id 780CB3040A3953; Fri, 29 Jan 2021 14:00:38 -0500 (EST)
Date: Fri, 29 Jan 2021 14:00:37 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Ken Murchison <murch@fastmail.com>, Barry Leiba <barryleiba@computer.org>
cc: draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
Message-ID: <a5ba5dea-7f86-4231-aa0f-31f82d82a6d9@cyrus.local>
In-Reply-To: <6b55aa41-0153-3335-d053-f8bf084a2938@fastmail.com>
References: <6b55aa41-0153-3335-d053-f8bf084a2938@fastmail.com>
X-Mailer: Mulberry/5.0.0a1 (macOS/10.16)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; size=499
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/ZYQRGM1HwOm4n1qMKWqXXbPU7vo>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 19:00:48 -0000

Hi Ken,

--On Fri, 29 Jan 2021 13:01:39 -0500 Ken Murchison <murch@fastmail.com>=20
wrote:


>> I read the above as zero or more 'x' and/or 'y'=C2=A0 OR zero or more 'z=
'.=C2=A0  I
>> don't see how https://tools.ietf.org/html/rfc5234#section-3.2
>> <https://tools.ietf.org/html/rfc5234#section-3.2> would allow having  'x'
>> and 'z' together.
>
>
> To continue my thought. Given:
>
> a =3D *(x /y) / *(z)
>
> *a would equate to: *(x / y / z)
>

Yeah, OK. I guess I got it wrong in 7986 then :-(

--=20
Cyrus Daboo


From nobody Fri Jan 29 11:11:30 2021
Return-Path: <murch@fastmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 328FB3A1239; Fri, 29 Jan 2021 11:11:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level: 
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_HTML_ATTACH=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.com header.b=L1wAfV+W; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=axQPhS3m
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kSEyMaRNvW2N; Fri, 29 Jan 2021 11:11:25 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AE873A112A; Fri, 29 Jan 2021 11:11:25 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 12F965C00E2; Fri, 29 Jan 2021 14:11:24 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 29 Jan 2021 14:11:24 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type; s=fm2; bh=R+4CRu7p2+nMrEvtFmX0MPvED5S HWPMP8+EIQJrB9+c=; b=L1wAfV+WIKuY9Iamh1AEC0aQWsRwSPt2xKYpzuz2hhA 2KKRwDDg8MngpTgY6D37s9fSSjmCmkaJ7cNPh9W73AIn9lreDWT7kfK+78iboX+3 L1BaPLRN5jz9+7CUGvUeZCvmcJ1UZPkOiThAhWj9uUUG76YAgjvxgctWbt+orSut GNtakfuIm/RFUnhdntYojF0cSQdFiOY+U780B8BOxtUkLvTcXYR70zaaDoSAHRX7 Mv8PxEUr7+zYqy5OOp77DGxSgNEEyv0axVRS020UxuIlH/HaGYBayqPFDlCoGKlO c7sesCgcNoPOcE0K9JXZ3X77G0ewI5VE7D6osZ9dY1Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=R+4CRu 7p2+nMrEvtFmX0MPvED5SHWPMP8+EIQJrB9+c=; b=axQPhS3mm0FgKgWJ3jeSj2 MdjhHYcYviEHK0GPm5UtcBdTGa1pWF8JDmtBLbeW1k3W0F/KcOEjIh9T9bjeWAEF F1qJnpvcJImJp+5470wmBiJJCd/ER+95XUvDilWlPW7Ry0fbhWewqJetPB67x9H7 2Ine48LWXwmTehsa/u8YBHdv7UA4yQ6Tidgs+w33Gt3eXYDHITbTBb22MEa4yCFi jN5MqE27zsuaGOswcpfHI0fkexqufGhY8qke1RgQiwQw7lxeQ/O5Bu6srqHxXvz1 9lahD5ROuUBIHHFdAHxBoTN0OIgHUZEQgFnXssk6Gn2rfUcFqV6pih/dpkHE07Aw ==
X-ME-Sender: <xms:210UYN5wDnf57khlPFYNVcOgUqwIxigMhNkKc_sIxfLoEtrTxAFfow> <xme:210UYK6eK4MhRwxk134lEiM7kUAyIjkcEHs76LnmEn-SUbNBqCf0PY92tc8KA7mSA 5Ghkzzrwk8uaQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedvgdduvddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtsehmtderredtfeejnecuhfhrohhmpefmvghnucfo uhhrtghhihhsohhnuceomhhurhgthhesfhgrshhtmhgrihhlrdgtohhmqeenucggtffrrg htthgvrhhnpeffjedtueetfeeuudefleehheffteduteeftefgvdegteelieevjeffudev vdeugeenucffohhmrghinhepihgvthhfrdhorhhgnecukfhppeejgedrjeejrdekhedrvd ehtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehm uhhrtghhsehfrghsthhmrghilhdrtghomh
X-ME-Proxy: <xmx:210UYEc86y3ld1sWdofrztGlna0zqO5pOccH7r4ywzFsdLi2qOpRtQ> <xmx:210UYGLgp02dxiBr0KZnnolsstcs2KEatmUZTpIohzQ3Vi8k3sx2OA> <xmx:210UYBJarvaNnfnhQvZHTwsDgx2Et3d1vGQPc3zBNtNph5p-37-XCg> <xmx:3F0UYPjVga7NAAE30BzBNj2qqkbKChLjqsqUNhDdSv1WXM3RY8OzRw>
Received: from [192.168.1.22] (cpe-74-77-85-250.buffalo.res.rr.com [74.77.85.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 2741E240057; Fri, 29 Jan 2021 14:11:23 -0500 (EST)
To: Cyrus Daboo <cyrus@daboo.name>, Barry Leiba <barryleiba@computer.org>
Cc: draft-ietf-calext-valarm-extensions.all@ietf.org, calsify@ietf.org
References: <6b55aa41-0153-3335-d053-f8bf084a2938@fastmail.com> <a5ba5dea-7f86-4231-aa0f-31f82d82a6d9@cyrus.local>
From: Ken Murchison <murch@fastmail.com>
Message-ID: <aef47d99-431e-e683-e012-974c321f9569@fastmail.com>
Date: Fri, 29 Jan 2021 14:11:22 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <a5ba5dea-7f86-4231-aa0f-31f82d82a6d9@cyrus.local>
Content-Type: multipart/mixed; boundary="------------C1B5D40F3F0ABD477ED893F0"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/fuS1YKgPsWs_7Q_BnWZ2i1cXVnA>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 19:11:29 -0000

This is a multi-part message in MIME format.
--------------C1B5D40F3F0ABD477ED893F0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit


On 1/29/21 2:00 PM, Cyrus Daboo wrote:
> Hi Ken,
>
> --On Fri, 29 Jan 2021 13:01:39 -0500 Ken Murchison 
> <murch@fastmail.com> wrote:
>
>
>>> I read the above as zero or more 'x' and/or 'y'  OR zero or more 
>>> 'z'.   I
>>> don't see how https://tools.ietf.org/html/rfc5234#section-3.2
>>> <https://tools.ietf.org/html/rfc5234#section-3.2> would allow 
>>> having  'x'
>>> and 'z' together.
>>
>>
>> To continue my thought. Given:
>>
>> a = *(x /y) / *(z)
>>
>> *a would equate to: *(x / y / z)
>>
>
> Yeah, OK. I guess I got it wrong in 7986 then :-(


We all got it wrong, since it passed review without being caught.

Anyhow, attached are my proposed changes per Barry's review and our ABNF 
discussion.

-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC


--------------C1B5D40F3F0ABD477ED893F0
Content-Type: text/html; charset=UTF-8;
 name="Diff draft-ietf-calext-valarm-extensions-03.txt -
 draft-ietf-calext-valarm-extensions.txt.html"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename*0="Diff draft-ietf-calext-valarm-extensions-03.txt - draft-ietf";
 filename*1="-calext-valarm-extensions.txt.html"

PCFET0NUWVBFIGh0bWwgUFVCTElDICItLy9XM0MvL0RURCBYSFRNTCAxLjAgVHJhbnNpdGlv
bmFsLy9FTiIgImh0dHA6Ly93d3cudzMub3JnL1RSL3hodG1sMS9EVEQveGh0bWwxLXRyYW5z
aXRpb25hbC5kdGQiPgo8IS0tIEdlbmVyYXRlZCBieSByZmNkaWZmIDEuNDg6IHJmY2RpZmYg
IC0tPgo8IS0tIDwhRE9DVFlQRSBodG1sIFBVQkxJQyAiLS8vVzNDLy9EVEQgSFRNTCA0LjAx
IFRyYW5zaXRpb25hbCIgPiAtLT4KPCEtLSBTeXN0ZW06IExpbnV4IHppbmZhbmRlbCAzLjIu
MC02LWFtZDY0ICMxIFNNUCBEZWJpYW4gMy4yLjEwMi0xIHg4Nl82NCBHTlUvTGludXggLS0+
CjwhLS0gVXNpbmcgYXdrOiAvdXNyL2Jpbi9nYXdrOiBHTlUgQXdrIDQuMC4xIC0tPgo8IS0t
IFVzaW5nIGRpZmY6IC91c3IvYmluL2RpZmY6IGRpZmYgKEdOVSBkaWZmdXRpbHMpIDMuMiAt
LT4KPCEtLSBVc2luZyB3ZGlmZjogL3Vzci9iaW4vd2RpZmY6IHdkaWZmIChHTlUgd2RpZmYp
IDEuMS4yIC0tPgo8aHRtbCB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94aHRtbCI+
PGhlYWQ+IAogIDxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0idGV4
dC9odG1sOyBjaGFyc2V0PVVURi04Ij4gCiAgPG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1T
dHlsZS1UeXBlIiBjb250ZW50PSJ0ZXh0L2NzcyI+IAogIDx0aXRsZT5EaWZmOiBkcmFmdC1p
ZXRmLWNhbGV4dC12YWxhcm0tZXh0ZW5zaW9ucy0wMy50eHQgLSBkcmFmdC1pZXRmLWNhbGV4
dC12YWxhcm0tZXh0ZW5zaW9ucy50eHQ8L3RpdGxlPiAKICA8c3R5bGUgdHlwZT0idGV4dC9j
c3MiPiAKICAgIGJvZHkgICAgeyBtYXJnaW46IDAuNGV4OyBtYXJnaW4tcmlnaHQ6IGF1dG87
IH0gCiAgICB0ciAgICAgIHsgfSAKICAgIHRkICAgICAgeyB3aGl0ZS1zcGFjZTogcHJlOyBm
b250LWZhbWlseTogbW9ub3NwYWNlOyB2ZXJ0aWNhbC1hbGlnbjogdG9wOyBmb250LXNpemU6
IDAuODZlbTt9IAogICAgdGggICAgICB7IGZvbnQtc2l6ZTogMC44NmVtOyB9IAogICAgLnNt
YWxsICB7IGZvbnQtc2l6ZTogMC42ZW07IGZvbnQtc3R5bGU6IGl0YWxpYzsgZm9udC1mYW1p
bHk6IFZlcmRhbmEsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsgfSAKICAgIC5sZWZ0ICAgeyBi
YWNrZ3JvdW5kLWNvbG9yOiAjRUVFOyB9IAogICAgLnJpZ2h0ICB7IGJhY2tncm91bmQtY29s
b3I6ICNGRkY7IH0gCiAgICAuZGlmZiAgIHsgYmFja2dyb3VuZC1jb2xvcjogI0NDRjsgfSAK
ICAgIC5sYmxvY2sgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjQkZCOyB9IAogICAgLnJibG9jayB7
IGJhY2tncm91bmQtY29sb3I6ICNGRjg7IH0gCiAgICAuaW5zZXJ0IHsgYmFja2dyb3VuZC1j
b2xvcjogIzhGRjsgfSAKICAgIC5kZWxldGUgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjQUNGOyB9
IAogICAgLnZvaWQgICB7IGJhY2tncm91bmQtY29sb3I6ICNGRkI7IH0gCiAgICAuY29udCAg
IHsgYmFja2dyb3VuZC1jb2xvcjogI0VFRTsgfSAKICAgIC5saW5lYnIgeyBiYWNrZ3JvdW5k
LWNvbG9yOiAjQUFBOyB9IAogICAgLmxpbmVubyB7IGNvbG9yOiByZWQ7IGJhY2tncm91bmQt
Y29sb3I6ICNGRkY7IGZvbnQtc2l6ZTogMC43ZW07IHRleHQtYWxpZ246IHJpZ2h0OyBwYWRk
aW5nOiAwIDJweDsgfSAKICAgIC5lbGlwc2lzeyBiYWNrZ3JvdW5kLWNvbG9yOiAjQUFBOyB9
IAogICAgLmxlZnQgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjREREOyB9IAogICAgLnJp
Z2h0IC5jb250IHsgYmFja2dyb3VuZC1jb2xvcjogI0VFRTsgfSAKICAgIC5sYmxvY2sgLmNv
bnQgeyBiYWNrZ3JvdW5kLWNvbG9yOiAjOUQ5OyB9IAogICAgLnJibG9jayAuY29udCB7IGJh
Y2tncm91bmQtY29sb3I6ICNERDY7IH0gCiAgICAuaW5zZXJ0IC5jb250IHsgYmFja2dyb3Vu
ZC1jb2xvcjogIzBERDsgfSAKICAgIC5kZWxldGUgLmNvbnQgeyBiYWNrZ3JvdW5kLWNvbG9y
OiAjOEFEOyB9IAogICAgLnN0YXRzLCAuc3RhdHMgdGQsIC5zdGF0cyB0aCB7IGJhY2tncm91
bmQtY29sb3I6ICNFRUU7IHBhZGRpbmc6IDJweCAwOyB9IAogICAgc3Bhbi5oaWRlIHsgZGlz
cGxheTogbm9uZTsgY29sb3I6ICNhYWE7fSAgICBhOmhvdmVyIHNwYW4geyBkaXNwbGF5OiBp
bmxpbmU7IH0gICAgdHIuY2hhbmdlIHsgYmFja2dyb3VuZC1jb2xvcjogZ3JheTsgfSAKICAg
IHRyLmNoYW5nZSBhIHsgdGV4dC1kZWNvcmF0aW9uOiBub25lOyBjb2xvcjogYmxhY2sgfSAK
ICA8L3N0eWxlPiAKICAgICA8c2NyaXB0Pgp2YXIgY2h1bmtfaW5kZXggPSAwOwp2YXIgb2xk
X2NodW5rID0gbnVsbDsKCmZ1bmN0aW9uIGZvcm1hdF9jaHVuayhpbmRleCkgewogICAgdmFy
IHByZWZpeCA9ICJkaWZmIjsKICAgIHZhciBzdHIgPSBpbmRleC50b1N0cmluZygpOwogICAg
Zm9yICh4PTA7IHg8KDQtc3RyLmxlbmd0aCk7ICsreCkgewogICAgICAgIHByZWZpeCs9JzAn
OwogICAgfQogICAgcmV0dXJuIHByZWZpeCArIHN0cjsKfQoKZnVuY3Rpb24gZmluZF9jaHVu
ayhuKXsKICAgIHJldHVybiBkb2N1bWVudC5xdWVyeVNlbGVjdG9yKCd0cltpZCQ9IicgKyBu
ICsgJyJdJyk7Cn0KCmZ1bmN0aW9uIGNoYW5nZV9jaHVuayhvZmZzZXQpIHsKICAgIHZhciBp
bmRleCA9IGNodW5rX2luZGV4ICsgb2Zmc2V0OwogICAgdmFyIG5ld19zdHI7CiAgICB2YXIg
bmV3X2NodW5rOwoKICAgIG5ld19zdHIgPSBmb3JtYXRfY2h1bmsoaW5kZXgpOwogICAgbmV3
X2NodW5rID0gZmluZF9jaHVuayhuZXdfc3RyKTsKICAgIGlmICghbmV3X2NodW5rKSB7CiAg
ICAgICAgcmV0dXJuOwogICAgfQogICAgaWYgKG9sZF9jaHVuaykgewogICAgICAgIG9sZF9j
aHVuay5zdHlsZS5vdXRsaW5lID0gIiI7CiAgICB9CiAgICBvbGRfY2h1bmsgPSBuZXdfY2h1
bms7CiAgICBvbGRfY2h1bmsuc3R5bGUub3V0bGluZSA9ICIxcHggc29saWQgcmVkIjsKICAg
IHdpbmRvdy5sb2NhdGlvbi5oYXNoID0gIiMiICsgbmV3X3N0cjsKICAgIHdpbmRvdy5zY3Jv
bGxCeSgwLC0xMDApOwogICAgY2h1bmtfaW5kZXggPSBpbmRleDsKfQoKZG9jdW1lbnQub25r
ZXlkb3duID0gZnVuY3Rpb24oZSkgewogICAgc3dpdGNoIChlLmtleUNvZGUpIHsKICAgIGNh
c2UgNzg6CiAgICAgICAgY2hhbmdlX2NodW5rKDEpOwogICAgICAgIGJyZWFrOwogICAgY2Fz
ZSA4MDoKICAgICAgICBjaGFuZ2VfY2h1bmsoLTEpOwogICAgICAgIGJyZWFrOwogICAgfQp9
OwogICA8L3NjcmlwdD4gCjwvaGVhZD4gCjxib2R5PiAKICA8dGFibGUgY2VsbHNwYWNpbmc9
IjAiIGNlbGxwYWRkaW5nPSIwIiBib3JkZXI9IjAiPiAKICA8dGJvZHk+PHRyIGlkPSJwYXJ0
LTEiIGJnY29sb3I9Im9yYW5nZSI+PHRoPjwvdGg+PHRoPjxhIGhyZWY9Imh0dHBzOi8vdG9v
bHMuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWlldGYtY2FsZXh0LXZhbGFybS1leHRl
bnNpb25zLTAzLnR4dCIgc3R5bGU9ImNvbG9yOiMwMDg7IHRleHQtZGVjb3JhdGlvbjpub25l
OyI+Jmx0OzwvYT4mbmJzcDs8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtaWV0Zi1jYWxleHQtdmFsYXJtLWV4dGVuc2lvbnMtMDMudHh0IiBzdHlsZT0iY29s
b3I6IzAwOCI+ZHJhZnQtaWV0Zi1jYWxleHQtdmFsYXJtLWV4dGVuc2lvbnMtMDMudHh0PC9h
PiZuYnNwOzwvdGg+PHRoPiA8L3RoPjx0aD4mbmJzcDs8YSBocmVmPSJodHRwczovL3Rvb2xz
LmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1jYWxleHQtdmFsYXJtLWV4dGVuc2lvbnMudHh0
IiBzdHlsZT0iY29sb3I6IzAwOCI+ZHJhZnQtaWV0Zi1jYWxleHQtdmFsYXJtLWV4dGVuc2lv
bnMudHh0PC9hPiZuYnNwOzxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlm
Zj91cmwxPWRyYWZ0LWlldGYtY2FsZXh0LXZhbGFybS1leHRlbnNpb25zLnR4dCIgc3R5bGU9
ImNvbG9yOiMwMDg7IHRleHQtZGVjb3JhdGlvbjpub25lOyI+Jmd0OzwvYT48L3RoPjx0aD48
L3RoPjwvdHI+IAogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPk5ldHdvcmsgV29ya2luZyBHcm91cCAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBDLiBEYWJvbzwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPk5ldHdvcmsgV29ya2luZyBHcm91cCAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICBDLiBEYWJvbzwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+SW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIEFwcGxlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+SW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIEFwcGxlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij5VcGRhdGVzOiA1NTQ1IChpZiBhcHByb3ZlZCkgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgSy4gTXVyY2hpc29uLCBFZC48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij5VcGRhdGVzOiA1NTQ1IChpZiBhcHByb3ZlZCkgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgSy4gTXVyY2hpc29uLCBFZC48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPklu
dGVuZGVkIHN0YXR1czogU3RhbmRhcmRzIFRyYWNrICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICBGYXN0bWFpbDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPkludGVu
ZGVkIHN0YXR1czogU3RhbmRhcmRzIFRyYWNrICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICBGYXN0bWFpbDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyIGlkPSJkaWZmMDAwMSI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj5FeHBpcmVzOiA8c3BhbiBjbGFzcz0i
ZGVsZXRlIj5NYXkgMjksIDIwMjEgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
Tm92ZW1iZXIgMjUsIDIwMjA8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxv
Y2siPkV4cGlyZXM6IDxzcGFuIGNsYXNzPSJpbnNlcnQiPkF1Z3VzdCAyLCAyMDIxICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgSmFudWFyeSAyOSwgMjAyMTwvc3Bhbj48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAg
ICAgICBWQUxBUk0gRXh0ZW5zaW9ucyBmb3IgaUNhbGVuZGFyPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgICBWQUxBUk0gRXh0ZW5zaW9ucyBm
b3IgaUNhbGVuZGFyPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHIgaWQ9ImRpZmYwMDAyIj48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgICAgICAgICAgICAgICAgZHJhZnQt
aWV0Zi1jYWxleHQtdmFsYXJtLWV4dGVuc2lvbnMtMDxzcGFuIGNsYXNzPSJkZWxldGUiPjM8
L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgICAgICAgICAg
ICAgZHJhZnQtaWV0Zi1jYWxleHQtdmFsYXJtLWV4dGVuc2lvbnMtMDxzcGFuIGNsYXNzPSJp
bnNlcnQiPjQ8L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPkFic3RyYWN0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+QWJzdHJhY3Q8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVGhpcyBkb2N1
bWVudCBkZWZpbmVzIGEgc2V0IG9mIGV4dGVuc2lvbnMgdG8gdGhlIGlDYWxlbmRhciBWQUxB
Uk08L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBUaGlzIGRvY3VtZW50IGRl
ZmluZXMgYSBzZXQgb2YgZXh0ZW5zaW9ucyB0byB0aGUgaUNhbGVuZGFyIFZBTEFSTTwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgY29tcG9uZW50IHRvIGVuaGFuY2UgdXNl
IG9mIGFsYXJtcyBhbmQgaW1wcm92ZSBpbnRlcm9wZXJhYmlsaXR5PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgY29tcG9uZW50IHRvIGVuaGFuY2UgdXNlIG9mIGFsYXJt
cyBhbmQgaW1wcm92ZSBpbnRlcm9wZXJhYmlsaXR5PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICBiZXR3ZWVuIGNsaWVudHMgYW5kIHNlcnZlcnMuPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgYmV0d2VlbiBjbGllbnRzIGFuZCBzZXJ2ZXJzLjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBUaGlzIGRvY3VtZW50
IHVwZGF0ZXMgUkZDNTU0NS48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBU
aGlzIGRvY3VtZW50IHVwZGF0ZXMgUkZDNTU0NS48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+U3RhdHVzIG9mIFRoaXMgTWVtbzwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPlN0YXR1cyBvZiBUaGlzIE1lbW88L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJwYXJ0LTIiIGNsYXNz
PSJjaGFuZ2UiPjx0ZD48L3RkPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9z
bWFsbD48YSBocmVmPSIjcGFydC0yIj48ZW0+IHBhZ2UgMSwgbGluZSAzNTxzcGFuIGNsYXNz
PSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGg+IDwvdGg+PHRoPjxzbWFsbD5z
a2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9IiNwYXJ0LTIiPjxlbT4gcGFn
ZSAxLCBsaW5lIDM1PHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3Ro
Pjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPiAgIEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMg
b2YgdGhlIEludGVybmV0IEVuZ2luZWVyaW5nPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgSW50ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5nIGRvY3VtZW50cyBvZiB0aGUg
SW50ZXJuZXQgRW5naW5lZXJpbmc8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
IFRhc2sgRm9yY2UgKElFVEYpLiAgTm90ZSB0aGF0IG90aGVyIGdyb3VwcyBtYXkgYWxzbyBk
aXN0cmlidXRlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGFzayBGb3Jj
ZSAoSUVURikuICBOb3RlIHRoYXQgb3RoZXIgZ3JvdXBzIG1heSBhbHNvIGRpc3RyaWJ1dGU8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHdvcmtpbmcgZG9jdW1lbnRzIGFz
IEludGVybmV0LURyYWZ0cy4gIFRoZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgd29ya2luZyBkb2N1bWVudHMgYXMgSW50
ZXJuZXQtRHJhZnRzLiAgVGhlIGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC08L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIERyYWZ0cyBpcyBhdCBodHRwczovL2RhdGF0cmFj
a2VyLmlldGYub3JnL2RyYWZ0cy9jdXJyZW50Ly48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICBEcmFmdHMgaXMgYXQgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9k
cmFmdHMvY3VycmVudC8uPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIEludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBh
IG1heGltdW0gb2Ygc2l4IG1vbnRoczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgIEludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBhIG1h
eGltdW0gb2Ygc2l4IG1vbnRoczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
YW5kIG1heSBiZSB1cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRv
Y3VtZW50cyBhdCBhbnk8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBhbmQg
bWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1l
bnRzIGF0IGFueTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgdGltZS4gIEl0
IGlzIGluYXBwcm9wcmlhdGUgdG8gdXNlIEludGVybmV0LURyYWZ0cyBhcyByZWZlcmVuY2U8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICB0aW1lLiAgSXQgaXMgaW5hcHBy
b3ByaWF0ZSB0byB1c2UgSW50ZXJuZXQtRHJhZnRzIGFzIHJlZmVyZW5jZTwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbWF0ZXJpYWwgb3IgdG8gY2l0ZSB0aGVtIG90aGVy
IHRoYW4gYXMgIndvcmsgaW4gcHJvZ3Jlc3MuIjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgIG1hdGVyaWFsIG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3b3Jr
IGluIHByb2dyZXNzLiI8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAwMyI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBUaGlzIElu
dGVybmV0LURyYWZ0IHdpbGwgZXhwaXJlIG9uIDxzcGFuIGNsYXNzPSJkZWxldGUiPk1heSAy
OTwvc3Bhbj4sIDIwMjEuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIFRo
aXMgSW50ZXJuZXQtRHJhZnQgd2lsbCBleHBpcmUgb24gPHNwYW4gY2xhc3M9Imluc2VydCI+
QXVndXN0IDI8L3NwYW4+LCAyMDIxLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij5Db3B5cmlnaHQgTm90aWNlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+Q29weXJpZ2h0IE5vdGljZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDA0Ij48dGQ+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAg
IENvcHlyaWdodCAoYykgMjAyPHNwYW4gY2xhc3M9ImRlbGV0ZSI+MDwvc3Bhbj4gSUVURiBU
cnVzdCBhbmQgdGhlIHBlcnNvbnMgaWRlbnRpZmllZCBhcyB0aGU8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJibG9jayI+ICAgQ29weXJpZ2h0IChjKSAyMDI8c3BhbiBjbGFzcz0iaW5z
ZXJ0Ij4xPC9zcGFuPiBJRVRGIFRydXN0IGFuZCB0aGUgcGVyc29ucyBpZGVudGlmaWVkIGFz
IHRoZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgZG9jdW1lbnQgYXV0aG9y
cy4gIEFsbCByaWdodHMgcmVzZXJ2ZWQuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgZG9jdW1lbnQgYXV0aG9ycy4gIEFsbCByaWdodHMgcmVzZXJ2ZWQuPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoaXMgZG9jdW1lbnQgaXMg
c3ViamVjdCB0byBCQ1AgNzggYW5kIHRoZSBJRVRGIFRydXN0J3MgTGVnYWw8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBUaGlzIGRvY3VtZW50IGlzIHN1YmplY3QgdG8g
QkNQIDc4IGFuZCB0aGUgSUVURiBUcnVzdCdzIExlZ2FsPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICBQcm92aXNpb25zIFJlbGF0aW5nIHRvIElFVEYgRG9jdW1lbnRzPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0
byBJRVRGIERvY3VtZW50czwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgKGh0
dHBzOi8vdHJ1c3RlZS5pZXRmLm9yZy9saWNlbnNlLWluZm8pIGluIGVmZmVjdCBvbiB0aGUg
ZGF0ZSBvZjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIChodHRwczovL3Ry
dXN0ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvKSBpbiBlZmZlY3Qgb24gdGhlIGRhdGUgb2Y8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHB1YmxpY2F0aW9uIG9mIHRoaXMg
ZG9jdW1lbnQuICBQbGVhc2UgcmV2aWV3IHRoZXNlIGRvY3VtZW50czwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgIHB1YmxpY2F0aW9uIG9mIHRoaXMgZG9jdW1lbnQuICBQ
bGVhc2UgcmV2aWV3IHRoZXNlIGRvY3VtZW50czwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgY2FyZWZ1bGx5LCBhcyB0aGV5IGRlc2NyaWJlIHlvdXIgcmlnaHRzIGFuZCBy
ZXN0cmljdGlvbnMgd2l0aCByZXNwZWN0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgY2FyZWZ1bGx5LCBhcyB0aGV5IGRlc2NyaWJlIHlvdXIgcmlnaHRzIGFuZCByZXN0
cmljdGlvbnMgd2l0aCByZXNwZWN0PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICB0byB0aGlzIGRvY3VtZW50LiAgQ29kZSBDb21wb25lbnRzIGV4dHJhY3RlZCBmcm9tIHRo
aXMgZG9jdW1lbnQgbXVzdDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHRv
IHRoaXMgZG9jdW1lbnQuICBDb2RlIENvbXBvbmVudHMgZXh0cmFjdGVkIGZyb20gdGhpcyBk
b2N1bWVudCBtdXN0PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBpbmNsdWRl
IFNpbXBsaWZpZWQgQlNEIExpY2Vuc2UgdGV4dCBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiA0
LmUgb2Y8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBpbmNsdWRlIFNpbXBs
aWZpZWQgQlNEIExpY2Vuc2UgdGV4dCBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiA0LmUgb2Y8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHRoZSBUcnVzdCBMZWdhbCBQcm92
aXNpb25zIGFuZCBhcmUgcHJvdmlkZWQgd2l0aG91dCB3YXJyYW50eSBhczwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHRoZSBUcnVzdCBMZWdhbCBQcm92aXNpb25zIGFu
ZCBhcmUgcHJvdmlkZWQgd2l0aG91dCB3YXJyYW50eSBhczwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBhcnQtMyIgY2xhc3M9
ImNoYW5nZSI+PHRkPjwvdGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3Nt
YWxsPjxhIGhyZWY9IiNwYXJ0LTMiPjxlbT4gcGFnZSAyLCBsaW5lIDI3PHNwYW4gY2xhc3M9
ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0aD4gPC90aD48dGg+PHNtYWxsPnNr
aXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iI3BhcnQtMyI+PGVtPiBwYWdl
IDIsIGxpbmUgMjc8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+
PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgICA3LjEuICBSZWxhdGlvbnNoaXAgVHlwZSBQcm9wZXJ0eSBQYXJh
bWV0ZXIgIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA5PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgICA3LjEuICBSZWxhdGlvbnNoaXAgVHlwZSBQcm9wZXJ0eSBQYXJhbWV0
ZXIgIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA5PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICA4LiAgQWxhcm0gUHJveGltaXR5IFRyaWdnZXIgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAgIDk8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICA4LiAgQWxhcm0gUHJveGltaXR5IFRyaWdnZXIgLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAgIDk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
ICAgOC4xLiAgUHJveGltaXR5IFByb3BlcnR5ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuICAxMDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAg
OC4xLiAgUHJveGltaXR5IFByb3BlcnR5ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuICAxMDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICA4LjIu
ICBFeGFtcGxlIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gIDExPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICA4LjIuICBF
eGFtcGxlIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gIDExPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICA5LiAgU2VjdXJpdHkg
Q29uc2lkZXJhdGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
MTE8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICA5LiAgU2VjdXJpdHkgQ29u
c2lkZXJhdGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTE8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIDEwLiBQcml2YWN5IENvbnNpZGVy
YXRpb25zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMTwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIDEwLiBQcml2YWN5IENvbnNpZGVyYXRp
b25zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMTwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgMTEuIElBTkEgQ29uc2lkZXJhdGlvbnMgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEyPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgMTEuIElBTkEgQ29uc2lkZXJhdGlvbnMgLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEyPC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDExLjEuICBQcm9wZXJ0eSBSZWdpc3RyYXRpb25zIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTI8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICAgIDExLjEuICBQcm9wZXJ0eSBSZWdpc3RyYXRpb25zIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTI8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgICAgMTEuMi4gIFJlbGF0aW9uc2hpcCBUeXBlcyBSZWdpc3RyeSAgLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgICAgMTEuMi4gIFJlbGF0aW9uc2hpcCBUeXBlcyBSZWdpc3RyeSAgLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+ICAgICAxMS4zLiAgUHJveGltaXR5IFZhbHVlIFJlZ2lzdHJ5IC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gIDEyPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgICAxMS4zLiAgUHJveGltaXR5IFZhbHVlIFJlZ2lzdHJ5IC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gIDEyPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHIgaWQ9ImRpZmYwMDA1Ij48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIDEyLiBBY2tub3dsZWRn
bWVudHMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAx
PHNwYW4gY2xhc3M9ImRlbGV0ZSI+Mjwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJibG9jayI+ICAgMTIuIEFja25vd2xlZGdtZW50cyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE8c3BhbiBjbGFzcz0iaW5zZXJ0Ij4zPC9zcGFu
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgMTMuIFJlZmVyZW5jZXMgIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEzPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgMTMuIFJlZmVyZW5jZXMgIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEzPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgIDEzLjEuICBOb3JtYXRpdmUgUmVmZXJl
bmNlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTM8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgIDEzLjEuICBOb3JtYXRpdmUgUmVmZXJlbmNl
cyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTM8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMDYiPjx0ZD48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxi
bG9jayI+ICAgICAxMy4yLiAgSW5mb3JtYXRpdmUgUmVmZXJlbmNlcyAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gIDxzcGFuIGNsYXNzPSJkZWxldGUiPjEzPC9zcGFuPjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgIDEzLjIuICBJbmZvcm1hdGl2
ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTQ8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAg
ICAxMy4zLiAgVVJJcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC48L3NwYW4+ICAxNDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2Nr
Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIEFwcGVuZGl4IEEuICBDaGFu
Z2UgSGlzdG9yeSAoVG8gYmUgcmVtb3ZlZCBieSBSRkMgRWRpdG9yIGJlZm9yZTwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIEFwcGVuZGl4IEEuICBDaGFuZ2UgSGlzdG9y
eSAoVG8gYmUgcmVtb3ZlZCBieSBSRkMgRWRpdG9yIGJlZm9yZTwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgIHB1YmxpY2F0aW9uKSAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE0PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgIHB1YmxpY2F0aW9uKSAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE0PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICBBdXRob3JzJyBBZGRyZXNzZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMTY8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBBdXRob3JzJyBBZGRyZXNzZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAgMTY8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+MS4gIEludHJvZHVjdGlvbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPjEuICBJbnRyb2R1Y3Rpb248L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgVGhlIGlDYWxlbmRhciBbUkZDNTU0NV0gc3BlY2lmaWNhdGlvbiBk
ZWZpbmVzIGEgc2V0IG9mIGNvbXBvbmVudHM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICBUaGUgaUNhbGVuZGFyIFtSRkM1NTQ1XSBzcGVjaWZpY2F0aW9uIGRlZmluZXMg
YSBzZXQgb2YgY29tcG9uZW50czwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
dXNlZCB0byBkZXNjcmliZSBjYWxlbmRhciBkYXRhLiAgT25lIG9mIHRob3NlIGlzIHRoZSAi
VkFMQVJNIjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHVzZWQgdG8gZGVz
Y3JpYmUgY2FsZW5kYXIgZGF0YS4gIE9uZSBvZiB0aG9zZSBpcyB0aGUgIlZBTEFSTSI8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGNvbXBvbmVudCB3aGljaCBhcHBlYXJz
IGFzIGEgc3ViLWNvbXBvbmVudCBvZiAiVkVWRU5UIiBhbmQgIlZUT0RPIjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGNvbXBvbmVudCB3aGljaCBhcHBlYXJzIGFzIGEg
c3ViLWNvbXBvbmVudCBvZiAiVkVWRU5UIiBhbmQgIlZUT0RPIjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgY29tcG9uZW50cy4gIFRoZSAiVkFMQVJNIiBjb21wb25lbnQg
aXMgdXNlZCB0byBzcGVjaWZ5IGEgcmVtaW5kZXIgZm9yPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgY29tcG9uZW50cy4gIFRoZSAiVkFMQVJNIiBjb21wb25lbnQgaXMg
dXNlZCB0byBzcGVjaWZ5IGEgcmVtaW5kZXIgZm9yPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0icGFydC00IiBjbGFzcz0iY2hh
bmdlIj48dGQ+PC90ZD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+
PGEgaHJlZj0iI3BhcnQtNCI+PGVtPiBwYWdlIDMsIGxpbmUgMjE8c3BhbiBjbGFzcz0iaGlk
ZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRoPiA8L3RoPjx0aD48c21hbGw+c2tpcHBp
bmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48YSBocmVmPSIjcGFydC00Ij48ZW0+IHBhZ2UgMywg
bGluZSAyMDxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGQ+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICBpQ2FsZW5kYXIuICBFYWNoIGV4dGVuc2lvbiBpcyBkZWZpbmVkIGluIGEg
c2VwYXJhdGUgc2VjdGlvbiBiZWxvdy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICBpQ2FsZW5kYXIuICBFYWNoIGV4dGVuc2lvbiBpcyBkZWZpbmVkIGluIGEgc2VwYXJh
dGUgc2VjdGlvbiBiZWxvdy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIEZv
ciB0aGUgbW9zdCBwYXJ0LCBlYWNoIGV4dGVuc2lvbiBjYW4gYmUgc3VwcG9ydGVkIGluZGVw
ZW5kZW50bHkgb2Y8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBGb3IgdGhl
IG1vc3QgcGFydCwgZWFjaCBleHRlbnNpb24gY2FuIGJlIHN1cHBvcnRlZCBpbmRlcGVuZGVu
dGx5IG9mPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICB0aGUgb3RoZXJzLCB0
aG91Z2ggaW4gc29tZSBjYXNlcyBvbmUgZXh0ZW5zaW9uIHdpbGwgcmVxdWlyZSBhbm90aGVy
LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHRoZSBvdGhlcnMsIHRob3Vn
aCBpbiBzb21lIGNhc2VzIG9uZSBleHRlbnNpb24gd2lsbCByZXF1aXJlIGFub3RoZXIuPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBJbiBhZGRpdGlvbiwgdGhpcyBzcGVj
aWZpY2F0aW9uIGRlc2NyaWJlcyBtZWNoYW5pc21zIGJ5IHdoaWNoIGNsaWVudHM8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBJbiBhZGRpdGlvbiwgdGhpcyBzcGVjaWZp
Y2F0aW9uIGRlc2NyaWJlcyBtZWNoYW5pc21zIGJ5IHdoaWNoIGNsaWVudHM8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGNhbiBpbnRlcm9wZXJhYmx5IGltcGxlbWVudCBj
b21tb24gZmVhdHVyZXMgc3VjaCBhcyAic25vb3ppbmciLjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgIGNhbiBpbnRlcm9wZXJhYmx5IGltcGxlbWVudCBjb21tb24gZmVh
dHVyZXMgc3VjaCBhcyAic25vb3ppbmciLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4yLiAgQ29udmVudGlvbnMgVXNlZCBpbiBUaGlzIERvY3VtZW50PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+Mi4gIENvbnZlbnRpb25zIFVzZWQgaW4g
VGhpcyBEb2N1bWVudDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICBUaGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1QgTk9UIiwgIlJFUVVJUkVEIiwgIlNI
QUxMIiwgIlNIQUxMIE5PVCIsPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
VGhlIGtleSB3b3JkcyAiTVVTVCIsICJNVVNUIE5PVCIsICJSRVFVSVJFRCIsICJTSEFMTCIs
ICJTSEFMTCBOT1QiLDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgIlNIT1VM
RCIsICJTSE9VTEQgTk9UIiwgIlJFQ09NTUVOREVEIiwgIk5PVCBSRUNPTU1FTkRFRCIsICJN
QVkiLCBhbmQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAiU0hPVUxEIiwg
IlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTk9UIFJFQ09NTUVOREVEIiwgIk1BWSIs
IGFuZDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJk
aWZmMDAwNyI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAiT1BUSU9OQUwiIGluIHRoaXMgZG9jdW1lbnQg
YXJlIHRvIGJlIGludGVycHJldGVkIGFzIGRlc2NyaWJlZCBpbiBCQ1A8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+ICAgIk9QVElPTkFMIiBpbiB0aGlzIGRvY3VtZW50IGFy
ZSB0byBiZSBpbnRlcnByZXRlZCBhcyBkZXNjcmliZWQgaW48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxibG9jayI+ICAgMTQgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+WzFdPC9zcGFuPiBb
UkZDMjExOV0gW1JGQzgxNzRdIHdoZW4sIGFuZCBvbmx5IHdoZW4sIHRoZXkgYXBwZWFyIGlu
IGFsbDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBCQ1AgMTQgW1JGQzIx
MTldIFtSRkM4MTc0XSB3aGVuLCBhbmQgb25seSB3aGVuLCB0aGV5IGFwcGVhciBpbiBhbGw8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGNhcGl0YWxzLCBhcyBzaG93biBo
ZXJlLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGNhcGl0YWxzLCBhcyBz
aG93biBoZXJlLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBXaGVuIFhNTCBlbGVtZW50IHR5cGVzIGluIHRoZSBuYW1lc3BhY2VzICJEQVY6IiBhbmQ8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBXaGVuIFhNTCBlbGVtZW50IHR5
cGVzIGluIHRoZSBuYW1lc3BhY2VzICJEQVY6IiBhbmQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgICJ1cm46aWV0ZjpwYXJhbXM6eG1sOm5zOmNhbGRhdiIgYXJlIHJlZmVy
ZW5jZWQgaW4gdGhpcyBkb2N1bWVudDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgICJ1cm46aWV0ZjpwYXJhbXM6eG1sOm5zOmNhbGRhdiIgYXJlIHJlZmVyZW5jZWQgaW4g
dGhpcyBkb2N1bWVudDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgb3V0c2lk
ZSBvZiB0aGUgY29udGV4dCBvZiBhbiBYTUwgZnJhZ21lbnQsIHRoZSBzdHJpbmcgIkRBVjoi
IGFuZDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG91dHNpZGUgb2YgdGhl
IGNvbnRleHQgb2YgYW4gWE1MIGZyYWdtZW50LCB0aGUgc3RyaW5nICJEQVY6IiBhbmQ8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICJDQUxEQVY6IiB3aWxsIGJlIHByZWZp
eGVkIHRvIHRoZSBlbGVtZW50IHR5cGUgbmFtZXMgcmVzcGVjdGl2ZWx5LjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICJDQUxEQVY6IiB3aWxsIGJlIHByZWZpeGVkIHRv
IHRoZSBlbGVtZW50IHR5cGUgbmFtZXMgcmVzcGVjdGl2ZWx5LjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4zLiAgRXh0ZW5zaWJsZSBzeW50YXggZm9yIFZB
TEFSTTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjMuICBFeHRlbnNpYmxlIHN5
bnRheCBmb3IgVkFMQVJNPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgIFNlY3Rpb24gMy42LjYgb2YgW1JGQzU1NDVdIGRlZmluZXMgdGhlIHN5bnRheCBm
b3IgIlZBTEFSTSIgY29tcG9uZW50czwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgIFNlY3Rpb24gMy42LjYgb2YgW1JGQzU1NDVdIGRlZmluZXMgdGhlIHN5bnRheCBmb3Ig
IlZBTEFSTSIgY29tcG9uZW50czwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBhcnQtNSIgY2xhc3M9ImNoYW5nZSI+PHRkPjwv
dGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9IiNw
YXJ0LTUiPjxlbT4gcGFnZSAzLCBsaW5lIDQ0PHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bh
bj48L2VtPjwvYT48L3RoPjx0aD4gPC90aD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5n
ZSBhdDwvc21hbGw+PGEgaHJlZj0iI3BhcnQtNSI+PGVtPiBwYWdlIDMsIGxpbmUgNDM8c3Bh
biBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRkPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
ZXh0ZW5kIHRoaXMgYnkgYWRkaW5nLCBlLmcuLCBhIG5ldyBwcm9wZXJ0eSBjb21tb24gdG8g
YWxsIHR5cGVzIG9mPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgZXh0ZW5k
IHRoaXMgYnkgYWRkaW5nLCBlLmcuLCBhIG5ldyBwcm9wZXJ0eSBjb21tb24gdG8gYWxsIHR5
cGVzIG9mPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBhbGFybS4gIFNpbmNl
IG1hbnkgb2YgdGhlIGV4dGVuc2lvbnMgZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50IG5lZWQg
dG88L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBhbGFybS4gIFNpbmNlIG1h
bnkgb2YgdGhlIGV4dGVuc2lvbnMgZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50IG5lZWQgdG88
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGV4dGVuZCB0aGUgYmFzZSBzeW50
YXgsIGFuIGFsdGVybmF0aXZlIGZvcm0gZm9yIHRoZSBiYXNlIHN5bnRheCBpczwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGV4dGVuZCB0aGUgYmFzZSBzeW50YXgsIGFu
IGFsdGVybmF0aXZlIGZvcm0gZm9yIHRoZSBiYXNlIHN5bnRheCBpczwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgZGVmaW5lZCBoZXJlLCB3aXRoIHRoZSBnb2FsIG9mIHNp
bXBsaWZ5aW5nIHNwZWNpZmljYXRpb24gb2YgdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgZGVmaW5lZCBoZXJlLCB3aXRoIHRoZSBnb2FsIG9mIHNpbXBsaWZ5aW5n
IHNwZWNpZmljYXRpb24gb2YgdGhlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBleHRlbnNpb25zLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGV4dGVu
c2lvbnMuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIEEg
IlZBTEFSTSIgY2FsZW5kYXIgY29tcG9uZW50IGlzIHJlLWRlZmluZWQgYnkgdGhlIGZvbGxv
d2luZzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIEEgIlZBTEFSTSIgY2Fs
ZW5kYXIgY29tcG9uZW50IGlzIHJlLWRlZmluZWQgYnkgdGhlIGZvbGxvd2luZzwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgbm90YXRpb246PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgbm90YXRpb246PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgIGFsYXJtY2V4dCAgPSAiQkVHSU4iICI6IiAiVkFMQVJNIiBD
UkxGPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgYWxhcm1jZXh0ICA9ICJC
RUdJTiIgIjoiICJWQUxBUk0iIENSTEY8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMDgiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICAgICAgICAg
ICAgIGFsYXJtcHJvcDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgICAg
ICAgICAgICAgPHNwYW4gY2xhc3M9Imluc2VydCI+Kjwvc3Bhbj5hbGFybXByb3A8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAiRU5EIiAiOiIgIlZB
TEFSTSIgQ1JMRjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAg
ICAgICAiRU5EIiAiOiIgIlZBTEFSTSIgQ1JMRjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDA5Ij48dGQ+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxv
Y2siPiAgIGFsYXJtcHJvcCAgPSA8c3BhbiBjbGFzcz0iZGVsZXRlIj4qPC9zcGFuPig8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgYWxhcm1wcm9wICA9ICg8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgIDsg
dGhlIGZvbGxvd2luZyBhcmUgUkVRVUlSRUQsPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgICAgICAgICAgICAgIDsgdGhlIGZvbGxvd2luZyBhcmUgUkVRVUlSRUQsPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgOyBidXQgTVVT
VCBOT1Qgb2NjdXIgbW9yZSB0aGFuIG9uY2U8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICAgICAgICAgICAgICAgOyBidXQgTVVTVCBOT1Qgb2NjdXIgbW9yZSB0aGFuIG9u
Y2U8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlm
ZjAwMTAiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxibG9jayI+PHNwYW4gY2xhc3M9ImRlbGV0ZSI+ICAgICAgICAgICAg
ICAgIGFjdGlvbiAvIHRyaWdnZXIgLzwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJibG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0ciBpZD0iZGlmZjAwMTEiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgICAgICAgICAg
ICBhY3Rpb24gLyB0cmlnZ2VyIC88L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICAgICAgICAgICAgICAgOyBvbmUgc2V0IG9mIGFjdGlvbiBwcm9wZXJ0aWVzIE1V
U1QgYmU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAg
OyBvbmUgc2V0IG9mIGFjdGlvbiBwcm9wZXJ0aWVzIE1VU1QgYmU8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICA7IHByZXNlbnQgYW5kIE1VU1QgbWF0
Y2ggdGhlIGFjdGlvbiBzcGVjaWZpZWQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICAgICAgICAgICAgICAgOyBwcmVzZW50IGFuZCBNVVNUIG1hdGNoIHRoZSBhY3Rpb24g
c3BlY2lmaWVkPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAg
ICAgOyBpbiB0aGUgQUNUSU9OIHByb3BlcnR5PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgICAgICAgICAgICAgIDsgaW4gdGhlIEFDVElPTiBwcm9wZXJ0eTwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgYWN0
aW9ucHJvcHMgLzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAg
ICAgICBhY3Rpb25wcm9wcyAvPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMTIiPjx0ZD48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICAg
ICAgICAgICAgIDsgdGhlIGZvbGxvd2luZyA8c3BhbiBjbGFzcz0iZGVsZXRlIj5pczwvc3Bh
bj4gT1BUSU9OQUwsPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgICAg
ICAgICAgICA7IHRoZSBmb2xsb3dpbmcgPHNwYW4gY2xhc3M9Imluc2VydCI+YXJlPC9zcGFu
PiBPUFRJT05BTCw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAg
ICAgICA7IGFuZCBNQVkgb2NjdXIgbW9yZSB0aGFuIG9uY2U8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgOyBhbmQgTUFZIG9jY3VyIG1vcmUgdGhh
biBvbmNlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAg
ICAgICAgICAgICB4LXByb3AgLyBpYW5hLXByb3A8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICAgICAgICAgICAgICAgeC1wcm9wIC8gaWFuYS1wcm9wPC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICApPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICk8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZm
MDAxMyI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBhY3Rpb25wcm9wcyA9IDxzcGFuIGNsYXNzPSJkZWxl
dGUiPmF1ZGlvcHJvcGV4dCAvIGRpc3Bwcm9wZXh0IC8gPC9zcGFuPmVtYWlscHJvcGV4dDwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBhY3Rpb25wcm9wcyA9IDxzcGFu
IGNsYXNzPSJpbnNlcnQiPiphdWRpb3Byb3BleHQgLyAqZGlzcHByb3BleHQgLyAqPC9zcGFu
PmVtYWlscHJvcGV4dDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDE0Ij48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIGF1ZGlvcHJv
cGV4dCAgPSA8c3BhbiBjbGFzcz0iZGVsZXRlIj4qPC9zcGFuPig8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJibG9jayI+ICAgYXVkaW9wcm9wZXh0ICA9ICg8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAgIDsgJ2R1cmF0
aW9uJyBhbmQgJ3JlcGVhdCcgYXJlIGJvdGggT1BUSU9OQUwsPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgIDsgJ2R1cmF0aW9uJyBhbmQgJ3Jl
cGVhdCcgYXJlIGJvdGggT1BUSU9OQUwsPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICAgICAgICAgICAgICAgICAgOyBhbmQgTVVTVCBOT1Qgb2NjdXIgbW9yZSB0aGFuIG9u
Y2UgZWFjaCw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAg
ICAgICAgOyBhbmQgTVVTVCBOT1Qgb2NjdXIgbW9yZSB0aGFuIG9uY2UgZWFjaCw8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICA7IGJ1dCBpZiBv
bmUgb2NjdXJzLCBzbyBNVVNUIHRoZSBvdGhlcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgICAgICAgICAgICAgICAgICA7IGJ1dCBpZiBvbmUgb2NjdXJzLCBzbyBNVVNU
IHRoZSBvdGhlcjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICAgICAgICAgICAgICAgICAgZHVyYXRpb24gLyByZXBlYXQgLzwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICBkdXJhdGlvbiAvIHJlcGVhdCAv
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAg
ICAgICAgICA7IHRoZSBmb2xsb3dpbmcgaXMgT1BUSU9OQUwsPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgIDsgdGhlIGZvbGxvd2luZyBpcyBP
UFRJT05BTCw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAg
ICAgICA7IGJ1dCBNVVNUIE5PVCBvY2N1ciBtb3JlIHRoYW4gb25jZTwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICA7IGJ1dCBNVVNUIE5PVCBv
Y2N1ciBtb3JlIHRoYW4gb25jZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgYXR0YWNoPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgIGF0dGFjaDwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgKTwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICApPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlm
ZjAwMTUiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgZGlzcHByb3BleHQgPSA8c3BhbiBjbGFzcz0iZGVs
ZXRlIj4qPC9zcGFuPig8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgZGlz
cHByb3BleHQgPSAoPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgICAgICAgICAgICAgICAgOyB0aGUgZm9sbG93aW5nIGFyZSBSRVFVSVJFRCw8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgIDsgdGhlIGZvbGxv
d2luZyBhcmUgUkVRVUlSRUQsPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAg
ICAgICAgICAgICAgIDsgYnV0IE1VU1QgTk9UIG9jY3VyIG1vcmUgdGhhbiBvbmNlPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICA7IGJ1dCBNVVNU
IE5PVCBvY2N1ciBtb3JlIHRoYW4gb25jZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgIGRlc2NyaXB0aW9uIC88L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgIGRlc2NyaXB0aW9uIC88
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAg
ICAgICA7ICdkdXJhdGlvbicgYW5kICdyZXBlYXQnIGFyZSBib3RoIE9QVElPTkFMLDwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgOyAnZHVyYXRp
b24nIGFuZCAncmVwZWF0JyBhcmUgYm90aCBPUFRJT05BTCw8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgOyBhbmQgTVVTVCBOT1Qgb2NjdXIgbW9y
ZSB0aGFuIG9uY2UgZWFjaCw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAg
ICAgICAgICAgICAgIDsgYW5kIE1VU1QgTk9UIG9jY3VyIG1vcmUgdGhhbiBvbmNlIGVhY2gs
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgIDsgYnV0
IGlmIG9uZSBvY2N1cnMsIHNvIE1VU1QgdGhlIG90aGVyPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICA7IGJ1dCBpZiBvbmUgb2NjdXJzLCBzbyBN
VVNUIHRoZSBvdGhlcjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICAgICAgICAgICAgICAgIGR1cmF0aW9uIC8gcmVwZWF0PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICBkdXJhdGlvbiAvIHJlcGVhdDwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAg
ICk8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgICk8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
IGlkPSJkaWZmMDAxNiI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICBlbWFpbHByb3BleHQgPSA8c3BhbiBj
bGFzcz0iZGVsZXRlIj4qKDwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9j
ayI+ICAgZW1haWxwcm9wZXh0ID0gPHNwYW4gY2xhc3M9Imluc2VydCI+KDwvc3Bhbj48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyYmxvY2siPiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICA8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgICAgICAgICAgICAgICAgIDsgdGhlIGZvbGxvd2luZyBhcmUgYWxsIFJFUVVJ
UkVELDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAg
IDsgdGhlIGZvbGxvd2luZyBhcmUgYWxsIFJFUVVJUkVELDwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAgOyBidXQgTVVTVCBOT1Qgb2NjdXIgbW9y
ZSB0aGFuIG9uY2U8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAg
ICAgICAgICA7IGJ1dCBNVVNUIE5PVCBvY2N1ciBtb3JlIHRoYW4gb25jZTwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICBkZXNj
cmlwdGlvbiAvIHN1bW1hcnkgLzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
ICAgICAgICAgICAgICAgIGRlc2NyaXB0aW9uIC8gc3VtbWFyeSAvPC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgIDsgdGhlIGZv
bGxvd2luZyBpcyBSRVFVSVJFRCw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICAgICAgICAgICAgICAgICA7IHRoZSBmb2xsb3dpbmcgaXMgUkVRVUlSRUQsPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICA7IGFuZCBNQVkgb2Nj
dXIgbW9yZSB0aGFuIG9uY2U8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAg
ICAgICAgICAgICAgICA7IGFuZCBNQVkgb2NjdXIgbW9yZSB0aGFuIG9uY2U8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAgYXR0
ZW5kZWUgLzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAg
ICAgIGF0dGVuZGVlIC88L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBhcnQtNiIgY2xhc3M9ImNoYW5nZSI+
PHRkPjwvdGQ+PHRoPjxzbWFsbD5za2lwcGluZyB0byBjaGFuZ2UgYXQ8L3NtYWxsPjxhIGhy
ZWY9IiNwYXJ0LTYiPjxlbT4gcGFnZSA1LCBsaW5lIDQxPHNwYW4gY2xhc3M9ImhpZGUiPiDC
tjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0aD4gPC90aD48dGg+PHNtYWxsPnNraXBwaW5nIHRv
IGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iI3BhcnQtNiI+PGVtPiBwYWdlIDUsIGxpbmUg
NDA8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRkPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+ICAgdGhlbiBiZSB1c2VkIHRvIHJlZmVyIHVuaXF1ZWx5IHRvIHRoZSAiVkFMQVJNIiBj
b21wb25lbnQuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgdGhlbiBiZSB1
c2VkIHRvIHJlZmVyIHVuaXF1ZWx5IHRvIHRoZSAiVkFMQVJNIiBjb21wb25lbnQuPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoZSAiVUlEIiBwcm9w
ZXJ0eSBkZWZpbmVkIGhlcmUgZm9sbG93cyB0aGUgZGVmaW5pdGlvbiBpbjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRoZSAiVUlEIiBwcm9wZXJ0eSBkZWZpbmVkIGhl
cmUgZm9sbG93cyB0aGUgZGVmaW5pdGlvbiBpbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgU2VjdGlvbiAzLjguNC43IG9mIFtSRkM1NTQ1XSB3aXRoIHRoZSBzZWN1cml0
eSBhbmQgcHJpdmFjeSB1cGRhdGVzIGluPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgU2VjdGlvbiAzLjguNC43IG9mIFtSRkM1NTQ1XSB3aXRoIHRoZSBzZWN1cml0eSBh
bmQgcHJpdmFjeSB1cGRhdGVzIGluPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBTZWN0aW9uIDUuMyBvZiBbUkZDNzk4Nl0uICBJbiBwYXJ0aWN1bGFyIGl0IE1VU1QgYmUg
YSBnbG9iYWxseSB1bmlxdWU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBT
ZWN0aW9uIDUuMyBvZiBbUkZDNzk4Nl0uICBJbiBwYXJ0aWN1bGFyIGl0IE1VU1QgYmUgYSBn
bG9iYWxseSB1bmlxdWU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGlkZW50
aWZpZXIgdGhhdCBkb2VzIG5vdCBjb250YWluIGFueSBzZWN1cml0eS0gb3IgcHJpdmFjeS1z
ZW5zaXRpdmU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBpZGVudGlmaWVy
IHRoYXQgZG9lcyBub3QgY29udGFpbiBhbnkgc2VjdXJpdHktIG9yIHByaXZhY3ktc2Vuc2l0
aXZlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBpbmZvcm1hdGlvbi48L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBpbmZvcm1hdGlvbi48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVGhlICJWQUxBUk0iIGNvbXBv
bmVudCBkZWZpbmVkIGluIFNlY3Rpb24gMyBpcyBleHRlbmRlZCBoZXJlIGFzOjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRoZSAiVkFMQVJNIiBjb21wb25lbnQgZGVm
aW5lZCBpbiBTZWN0aW9uIDMgaXMgZXh0ZW5kZWQgaGVyZSBhczo8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAxNyI+
PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGJsb2NrIj4gICBhbGFybXByb3AgIDxzcGFuIGNsYXNzPSJkZWxldGUiPi89ICo8
L3NwYW4+KDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBhbGFybXByb3Ag
IDxzcGFuIGNsYXNzPSJpbnNlcnQiPj0vIDwvc3Bhbj4oPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgOyB0aGUgZm9sbG93aW5n
IGlzIE9QVElPTkFMLDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAg
ICAgICAgICAgOyB0aGUgZm9sbG93aW5nIGlzIE9QVElPTkFMLDwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICA7IGJ1dCBNVVNUIE5PVCBvY2N1ciBt
b3JlIHRoYW4gb25jZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAg
ICAgICAgICAgOyBidXQgTVVTVCBOT1Qgb2NjdXIgbW9yZSB0aGFuIG9uY2U8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICB1aWQ8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgIHVpZDwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAg
ICAgICk8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAg
ICk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+NS4gIEFsYXJt
IFJlbGF0ZWQgVG88L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij41LiAgQWxhcm0g
UmVsYXRlZCBUbzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0icGFydC03IiBjbGFzcz0iY2hhbmdlIj48dGQ+
PC90ZD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0i
I3BhcnQtNyI+PGVtPiBwYWdlIDYsIGxpbmUgMjE8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9z
cGFuPjwvZW0+PC9hPjwvdGg+PHRoPiA8L3RoPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hh
bmdlIGF0PC9zbWFsbD48YSBocmVmPSIjcGFydC03Ij48ZW0+IHBhZ2UgNiwgbGluZSAyMTxz
cGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGQ+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgIFRoaXMgc3BlY2lmaWNhdGlvbiB1cGRhdGVzIHRoZSB1c2FnZSBvZiB0
aGUgIlJFTEFURUQtVE8iIHByb3BlcnR5PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgVGhpcyBzcGVjaWZpY2F0aW9uIHVwZGF0ZXMgdGhlIHVzYWdlIG9mIHRoZSAiUkVM
QVRFRC1UTyIgcHJvcGVydHk8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGRl
ZmluZWQgaW4gU2VjdGlvbiAzLjguNC41IG9mIFtSRkM1NTQ1XSB0byBlbmFibGUgaXRzIHVz
ZSB3aXRoPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgZGVmaW5lZCBpbiBT
ZWN0aW9uIDMuOC40LjUgb2YgW1JGQzU1NDVdIHRvIGVuYWJsZSBpdHMgdXNlIHdpdGg8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICJWQUxBUk0iIGNvbXBvbmVudHMuICBT
cGVjaWZpYyB0eXBlcyBvZiByZWxhdGlvbnNoaXBzIGJldHdlZW48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICAiVkFMQVJNIiBjb21wb25lbnRzLiAgU3BlY2lmaWMgdHlw
ZXMgb2YgcmVsYXRpb25zaGlwcyBiZXR3ZWVuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICAiVkFMQVJNIiBjb21wb25lbnRzIGNhbiBiZSBpZGVudGlmaWVkIGJ5IHJlZ2lz
dGVyaW5nIG5ldyB2YWx1ZXMgZm9yPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgIlZBTEFSTSIgY29tcG9uZW50cyBjYW4gYmUgaWRlbnRpZmllZCBieSByZWdpc3Rlcmlu
ZyBuZXcgdmFsdWVzIGZvcjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgdGhl
ICJSRUxUWVBFIiBwcm9wZXJ0eSBwYXJhbWV0ZXIgZGVmaW5lZCBpbiBTZWN0aW9uIDMuMi4x
NSBvZjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHRoZSAiUkVMVFlQRSIg
cHJvcGVydHkgcGFyYW1ldGVyIGRlZmluZWQgaW4gU2VjdGlvbiAzLjIuMTUgb2Y8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFtSRkM1NTQ1XS48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICBbUkZDNTU0NV0uPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoZSAiVkFMQVJNIiBjb21wb25lbnQgZGVmaW5lZCBp
biBTZWN0aW9uIDMgaXMgZXh0ZW5kZWQgaGVyZSBhczo8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBUaGUgIlZBTEFSTSIgY29tcG9uZW50IGRlZmluZWQgaW4gU2VjdGlv
biAzIGlzIGV4dGVuZGVkIGhlcmUgYXM6PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMTgiPjx0ZD48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+
ICAgYWxhcm1wcm9wICA8c3BhbiBjbGFzcz0iZGVsZXRlIj4vPSAqPC9zcGFuPig8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgYWxhcm1wcm9wICA8c3BhbiBjbGFzcz0i
aW5zZXJ0Ij49LyA8L3NwYW4+KDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICAgICAgICAgICAgIDsgdGhlIGZvbGxvd2luZyBpcyBPUFRJT05BTCw8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgIDsgdGhl
IGZvbGxvd2luZyBpcyBPUFRJT05BTCw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMTkiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICAgICAgICAg
ICAgICA7IDxzcGFuIGNsYXNzPSJkZWxldGUiPmJ1dDwvc3Bhbj4gTUFZIG9jY3VyIG1vcmUg
dGhhbiBvbmNlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgICAgICAg
ICAgICAgOyA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5hbmQ8L3NwYW4+IE1BWSBvY2N1ciBtb3Jl
IHRoYW4gb25jZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICAgICAgICAgICAgICAgIHJlbGF0ZWQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICAgICAgICAgICAgICAgIHJlbGF0ZWQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICApPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICApPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPjYuICBBbGFybSBBY2tub3dsZWRnZW1lbnQ8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij42LiAgQWxhcm0gQWNrbm93bGVkZ2VtZW50PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoZXJlIGlzIGN1cnJl
bnRseSBubyB3YXkgZm9yIGEgIlZBTEFSTSIgY29tcG9uZW50IHRvIGluZGljYXRlPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhlcmUgaXMgY3VycmVudGx5IG5vIHdh
eSBmb3IgYSAiVkFMQVJNIiBjb21wb25lbnQgdG8gaW5kaWNhdGU8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgIHdoZXRoZXIgaXQgaGFzIGJlZW4gdHJpZ2dlcmVkIGFuZCBh
Y2tub3dsZWRnZWQuICBXaXRoIHRoZSBhZHZlbnQgb2YgYTwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPiAgIHdoZXRoZXIgaXQgaGFzIGJlZW4gdHJpZ2dlcmVkIGFuZCBhY2tu
b3dsZWRnZWQuICBXaXRoIHRoZSBhZHZlbnQgb2YgYTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+ICAgc3RhbmRhcmQgY2xpZW50L3NlcnZlciBwcm90b2NvbCBmb3IgY2FsZW5k
YXJpbmcgYW5kIHNjaGVkdWxpbmcgZGF0YTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgIHN0YW5kYXJkIGNsaWVudC9zZXJ2ZXIgcHJvdG9jb2wgZm9yIGNhbGVuZGFyaW5n
IGFuZCBzY2hlZHVsaW5nIGRhdGE8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJwYXJ0LTgiIGNsYXNzPSJjaGFuZ2UiPjx0ZD48
L3RkPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48YSBocmVmPSIj
cGFydC04Ij48ZW0+IHBhZ2UgNywgbGluZSA1PHNwYW4gY2xhc3M9ImhpZGUiPiDCtjwvc3Bh
bj48L2VtPjwvYT48L3RoPjx0aD4gPC90aD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5n
ZSBhdDwvc21hbGw+PGEgaHJlZj0iI3BhcnQtOCI+PGVtPiBwYWdlIDcsIGxpbmUgNTxzcGFu
IGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90aD48dGQ+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICB0
b28uPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgdG9vLjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBBbHNvLCB3aXRoIHJlY3Vycmlu
ZyBldmVudHMgdGhhdCBoYXZlIGFsYXJtcywgaXQgaXMgaW1wb3J0YW50IHRvIGtub3c8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBBbHNvLCB3aXRoIHJlY3VycmluZyBl
dmVudHMgdGhhdCBoYXZlIGFsYXJtcywgaXQgaXMgaW1wb3J0YW50IHRvIGtub3c8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIHdoZW4gdGhlIGxhc3QgYWxhcm0gaW4gdGhl
IHJlY3VycmluZyBzZXQgd2FzIGFja25vd2xlZGdlZCwgc28gdGhhdDwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgIHdoZW4gdGhlIGxhc3QgYWxhcm0gaW4gdGhlIHJlY3Vy
cmluZyBzZXQgd2FzIGFja25vd2xlZGdlZCwgc28gdGhhdDwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgdGhlIGNsaWVudCBjYW4gZGV0ZXJtaW5lIHdoZXRoZXIgcGFzdCBh
bGFybXMgaGF2ZSBiZWVuIG1pc3NlZC48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICB0aGUgY2xpZW50IGNhbiBkZXRlcm1pbmUgd2hldGhlciBwYXN0IGFsYXJtcyBoYXZl
IGJlZW4gbWlzc2VkLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICBUbyBhZGRyZXNzIHRoZXNlIG5lZWRzLCB0aGlzIHNwZWNpZmljYXRpb24gYWRkcyBh
biAiQUNLTk9XTEVER0VEIjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRv
IGFkZHJlc3MgdGhlc2UgbmVlZHMsIHRoaXMgc3BlY2lmaWNhdGlvbiBhZGRzIGFuICJBQ0tO
T1dMRURHRUQiPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBwcm9wZXJ0eSB0
byAiVkFMQVJNIiBjb21wb25lbnRzIHRvIGluZGljYXRlIHdoZW4gdGhlIGFsYXJtIHdhcyBs
YXN0PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgcHJvcGVydHkgdG8gIlZB
TEFSTSIgY29tcG9uZW50cyB0byBpbmRpY2F0ZSB3aGVuIHRoZSBhbGFybSB3YXMgbGFzdDwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgc2VudCBvciBhY2tub3dsZWRnZWQu
ICBUaGlzIGlzIGRlZmluZWQgYnkgdGhlIHN5bnRheCBiZWxvdy48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICBzZW50IG9yIGFja25vd2xlZGdlZC4gIFRoaXMgaXMgZGVm
aW5lZCBieSB0aGUgc3ludGF4IGJlbG93LjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDIwIj48dGQ+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2si
PiAgIGFsYXJtcHJvcCAgICAgICA8c3BhbiBjbGFzcz0iZGVsZXRlIj4vPSAqPC9zcGFuPig8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgYWxhcm1wcm9wICAgICAgIDxz
cGFuIGNsYXNzPSJpbnNlcnQiPj0vIDwvc3Bhbj4oPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgICA7IHRoZSBmb2xsb3dp
bmcgaXMgT1BUSU9OQUwsPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAg
ICAgICAgICAgICAgICAgIDsgdGhlIGZvbGxvd2luZyBpcyBPUFRJT05BTCw8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgICA7IGJ1dCBNVVNU
IE5PVCBvY2N1ciBtb3JlIHRoYW4gb25jZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgICAgICAgICAgICAgICAgICAgICA7IGJ1dCBNVVNUIE5PVCBvY2N1ciBtb3JlIHRo
YW4gb25jZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAg
ICAgICAgICAgICAgICAgICAgYWNrbm93bGVkZ2VkPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgICAgICAgICAgICAgICAgICAgIGFja25vd2xlZGdlZDwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgICAg
KTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICAg
ICApPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjYuMS4gIEFj
a25vd2xlZGdlZCBQcm9wZXJ0eTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjYu
MS4gIEFja25vd2xlZGdlZCBQcm9wZXJ0eTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0icGFydC05IiBjbGFz
cz0iY2hhbmdlIj48dGQ+PC90ZD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwv
c21hbGw+PGEgaHJlZj0iI3BhcnQtOSI+PGVtPiBwYWdlIDcsIGxpbmUgMzk8c3BhbiBjbGFz
cz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRoPiA8L3RoPjx0aD48c21hbGw+
c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48YSBocmVmPSIjcGFydC05Ij48ZW0+IHBh
Z2UgNywgbGluZSAzOTxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90
aD48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICBEZXNjcmlwdGlvbjogIFRoaXMgcHJvcGVydHkgaXMgdXNlZCB0
byBzcGVjaWZ5IHdoZW4gYW4gYWxhcm0gd2FzIGxhc3Q8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBEZXNjcmlwdGlvbjogIFRoaXMgcHJvcGVydHkgaXMgdXNlZCB0byBz
cGVjaWZ5IHdoZW4gYW4gYWxhcm0gd2FzIGxhc3Q8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgICAgIHNlbnQgb3IgYWNrbm93bGVkZ2VkLiAgVGhpcyBhbGxvd3MgY2xpZW50
cyB0byBkZXRlcm1pbmUgd2hlbiBhPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgICAgc2VudCBvciBhY2tub3dsZWRnZWQuICBUaGlzIGFsbG93cyBjbGllbnRzIHRvIGRl
dGVybWluZSB3aGVuIGE8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIHBl
bmRpbmcgYWxhcm0gaGFzIGJlZW4gYWNrbm93bGVkZ2VkIGJ5IGEgY2FsZW5kYXIgdXNlciBz
byB0aGF0IGFueTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIHBlbmRp
bmcgYWxhcm0gaGFzIGJlZW4gYWNrbm93bGVkZ2VkIGJ5IGEgY2FsZW5kYXIgdXNlciBzbyB0
aGF0IGFueTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgYWxlcnRzIGNh
biBiZSBkaXNtaXNzZWQgYWNyb3NzIG11bHRpcGxlIGRldmljZXMuICBJdCBhbHNvIGFsbG93
czwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIGFsZXJ0cyBjYW4gYmUg
ZGlzbWlzc2VkIGFjcm9zcyBtdWx0aXBsZSBkZXZpY2VzLiAgSXQgYWxzbyBhbGxvd3M8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIGNsaWVudHMgdG8gdHJhY2sgcmVw
ZWF0aW5nIGFsYXJtcyBvciBhbGFybXMgb24gcmVjdXJyaW5nIGV2ZW50cyBvcjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIGNsaWVudHMgdG8gdHJhY2sgcmVwZWF0
aW5nIGFsYXJtcyBvciBhbGFybXMgb24gcmVjdXJyaW5nIGV2ZW50cyBvcjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgdG8tZG9zIHRvIGVuc3VyZSB0aGF0IHRoZSBy
aWdodCBudW1iZXIgb2YgbWlzc2VkIGFsYXJtcyBjYW4gYmU8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICAgICB0by1kb3MgdG8gZW5zdXJlIHRoYXQgdGhlIHJpZ2h0IG51
bWJlciBvZiBtaXNzZWQgYWxhcm1zIGNhbiBiZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgICAgdHJhY2tlZC48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICAgICB0cmFja2VkLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICAgICBDbGllbnRzIFNIT1VMRCBzZXQgdGhpcyBwcm9wZXJ0eSB0byB0aGUgY3VycmVu
dCBkYXRlLXRpbWUgdmFsdWUgaW48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICAgICBDbGllbnRzIFNIT1VMRCBzZXQgdGhpcyBwcm9wZXJ0eSB0byB0aGUgY3VycmVudCBk
YXRlLXRpbWUgdmFsdWUgaW48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAg
IFVUQyB3aGVuIGEgY2FsZW5kYXIgdXNlciBhY2tub3dsZWRnZXMgYSBwZW5kaW5nIGFsYXJt
LiAgQ2VydGFpbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIFVUQyB3
aGVuIGEgY2FsZW5kYXIgdXNlciBhY2tub3dsZWRnZXMgYSBwZW5kaW5nIGFsYXJtLiAgQ2Vy
dGFpbjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJk
aWZmMDAyMSI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgICBraW5kcyBvZiA8c3BhbiBjbGFzcz0iZGVs
ZXRlIj5hbGFybSBtYXk8L3NwYW4+IG5vdCBwcm92aWRlIGZlZWRiYWNrIGFzIHRvIHdoZW4g
dGhlIGNhbGVuZGFyPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgICAgIGtp
bmRzIG9mIDxzcGFuIGNsYXNzPSJpbnNlcnQiPmFsYXJtcywgc3VjaCBhcyBlbWFpbC1iYXNl
ZCBhbGVydHMsIG1pZ2h0PC9zcGFuPiBub3QgcHJvdmlkZTwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGJsb2NrIj4gICAgICB1c2VyIHNlZXMgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+dGhl
bSwgZm9yIGV4YW1wbGUgZW1haWwgYmFzZWQgYWxlcnRzLjwvc3Bhbj4gIEZvciB0aG9zZSBr
aW5kczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgICBmZWVkYmFjayBh
cyB0byB3aGVuIHRoZSBjYWxlbmRhciB1c2VyIHNlZXMgPHNwYW4gY2xhc3M9Imluc2VydCI+
dGhlbS48L3NwYW4+ICBGb3IgdGhvc2Uga2luZHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgICAgIG9mIGFsYXJtcywgdGhlIGNsaWVudCBTSE9VTEQgc2V0IHRoaXMgcHJv
cGVydHkgd2hlbiB0aGUgYWxhcm0gaXM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICAgICBvZiBhbGFybXMsIHRoZSBjbGllbnQgU0hPVUxEIHNldCB0aGlzIHByb3BlcnR5
IHdoZW4gdGhlIGFsYXJtIGlzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAg
ICB0cmlnZ2VyZWQgYW5kIHRoZSBhY3Rpb24gc3VjY2Vzc2Z1bGx5IGNhcnJpZWQgb3V0Ljwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIHRyaWdnZXJlZCBhbmQgdGhl
IGFjdGlvbiBzdWNjZXNzZnVsbHkgY2FycmllZCBvdXQuPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIFdoZW4gYW4gYWxhcm0gaXMgdHJpZ2dlcmVk
IG9uIGEgY2xpZW50LCBjbGllbnRzIGNhbiBjaGVjayB0byBzZWU8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICAgICBXaGVuIGFuIGFsYXJtIGlzIHRyaWdnZXJlZCBvbiBh
IGNsaWVudCwgY2xpZW50cyBjYW4gY2hlY2sgdG8gc2VlPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICAgICBpZiBhbiAiQUNLTk9XTEVER0VEIiBwcm9wZXJ0eSBpcyBwcmVz
ZW50LiAgSWYgaXQgaXMsIGFuZCB0aGUgdmFsdWU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICAgICBpZiBhbiAiQUNLTk9XTEVER0VEIiBwcm9wZXJ0eSBpcyBwcmVzZW50
LiAgSWYgaXQgaXMsIGFuZCB0aGUgdmFsdWU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgICAgIG9mIHRoYXQgcHJvcGVydHkgaXMgZ3JlYXRlciB0aGFuIG9yIGVxdWFsIHRv
IHRoZSBjb21wdXRlZCB0cmlnZ2VyPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgICAgb2YgdGhhdCBwcm9wZXJ0eSBpcyBncmVhdGVyIHRoYW4gb3IgZXF1YWwgdG8gdGhl
IGNvbXB1dGVkIHRyaWdnZXI8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAg
IHRpbWUgZm9yIHRoZSBhbGFybSwgdGhlbiB0aGUgY2xpZW50IFNIT1VMRCBOT1QgdHJpZ2dl
ciB0aGUgYWxhcm0uPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgdGlt
ZSBmb3IgdGhlIGFsYXJtLCB0aGVuIHRoZSBjbGllbnQgU0hPVUxEIE5PVCB0cmlnZ2VyIHRo
ZSBhbGFybS48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIFNpbWlsYXJs
eSwgaWYgYW4gYWxhcm0gaGFzIGJlZW4gdHJpZ2dlcmVkIGFuZCBhbiAiYWxlcnQiIHByZXNl
bnRlZDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIFNpbWlsYXJseSwg
aWYgYW4gYWxhcm0gaGFzIGJlZW4gdHJpZ2dlcmVkIGFuZCBhbiAiYWxlcnQiIHByZXNlbnRl
ZDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgdG8gYSBjYWxlbmRhciB1
c2VyLCBjbGllbnRzIGNhbiBtb25pdG9yIHRoZSBpQ2FsZW5kYXIgZGF0YSB0bzwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIHRvIGEgY2FsZW5kYXIgdXNlciwgY2xp
ZW50cyBjYW4gbW9uaXRvciB0aGUgaUNhbGVuZGFyIGRhdGEgdG88L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxlZnQiPiAgICAgIGRldGVybWluZSB3aGV0aGVyIGFuICJBQ0tOT1dMRURH
RUQiIHByb3BlcnR5IGlzIGFkZGVkIG9yIGNoYW5nZWQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICAgICBkZXRlcm1pbmUgd2hldGhlciBhbiAiQUNLTk9XTEVER0VEIiBw
cm9wZXJ0eSBpcyBhZGRlZCBvciBjaGFuZ2VkPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICAgICBpbiB0aGUgYWxhcm0gY29tcG9uZW50LiAgSWYgdGhlIHZhbHVlIG9mIGFu
eSAiQUNLTk9XTEVER0VEIjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAg
IGluIHRoZSBhbGFybSBjb21wb25lbnQuICBJZiB0aGUgdmFsdWUgb2YgYW55ICJBQ0tOT1dM
RURHRUQiPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBwcm9wZXJ0eSBp
biB0aGUgYWxhcm0gY2hhbmdlcyBhbmQgaXMgZ3JlYXRlciB0aGFuIG9yIGVxdWFsIHRvIHRo
ZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIHByb3BlcnR5IGluIHRo
ZSBhbGFybSBjaGFuZ2VzIGFuZCBpcyBncmVhdGVyIHRoYW4gb3IgZXF1YWwgdG8gdGhlPC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICB0cmlnZ2VyIHRpbWUgb2YgdGhl
IGFsYXJtLCB0aGVuIGNsaWVudHMgU0hPVUxEIGRpc21pc3Mgb3IgY2FuY2VsPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgdHJpZ2dlciB0aW1lIG9mIHRoZSBhbGFy
bSwgdGhlbiBjbGllbnRzIFNIT1VMRCBkaXNtaXNzIG9yIGNhbmNlbDwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgYW55ICJhbGVydCIgcHJlc2VudGVkIHRvIHRoZSBj
YWxlbmRhciB1c2VyLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIGFu
eSAiYWxlcnQiIHByZXNlbnRlZCB0byB0aGUgY2FsZW5kYXIgdXNlci48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgRm9ybWF0IERlZmluaXRpb246ICBU
aGlzIHByb3BlcnR5IGlzIGRlZmluZWQgYnkgdGhlIGZvbGxvd2luZzwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgIEZvcm1hdCBEZWZpbml0aW9uOiAgVGhpcyBwcm9wZXJ0
eSBpcyBkZWZpbmVkIGJ5IHRoZSBmb2xsb3dpbmc8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgICAgIG5vdGF0aW9uOjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgICAgIG5vdGF0aW9uOjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDIyIj48dGQ+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIGFja25v
d2xlZGdlZCA9ICJBQ0tOT1dMRURHRUQiIGFja25vd2xlZGdlZHBhcmFtICI6IiBkYXRldGlt
ZSBDUkxGPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIGFja25vd2xlZGdl
ZCA9ICJBQ0tOT1dMRURHRUQiIDxzcGFuIGNsYXNzPSJpbnNlcnQiPio8L3NwYW4+YWNrbm93
bGVkZ2VkcGFyYW0gIjoiIGRhdGV0aW1lIENSTEY8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAyMyI+PHRkPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJs
b2NrIj4gICBhY2tub3dsZWRnZWRwYXJhbSAgPSA8c3BhbiBjbGFzcz0iZGVsZXRlIj4qPC9z
cGFuPig8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgYWNrbm93bGVkZ2Vk
cGFyYW0gID0gKDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICAgICAgICAgICAgICAgICAgICAgICA7IHRoZSBmb2xsb3dpbmcgaXMgT1BUSU9OQUwsPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAgICAgICAgICAg
OyB0aGUgZm9sbG93aW5nIGlzIE9QVElPTkFMLDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgICAgICAgICAgICAgICAgICAgICAgOyBhbmQgTUFZIG9jY3VyIG1vcmUgdGhh
biBvbmNlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAg
ICAgICAgICAgOyBhbmQgTUFZIG9jY3VyIG1vcmUgdGhhbiBvbmNlPC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAgICAgICgi
OyIgb3RoZXItcGFyYW0pPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAg
ICAgICAgICAgICAgICAgICAgKCI7IiBvdGhlci1wYXJhbSk8L3RkPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQg
Y2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAgICAgICAgKTwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICAgICAgICk8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgRXhhbXBsZTog
IFRoZSBmb2xsb3dpbmcgaXMgYW4gZXhhbXBsZSBvZiB0aGlzIHByb3BlcnR5OjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIEV4YW1wbGU6ICBUaGUgZm9sbG93aW5nIGlz
IGFuIGV4YW1wbGUgb2YgdGhpcyBwcm9wZXJ0eTo8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90
ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBhcnQtMTAi
IGNsYXNzPSJjaGFuZ2UiPjx0ZD48L3RkPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdl
IGF0PC9zbWFsbD48YSBocmVmPSIjcGFydC0xMCI+PGVtPiBwYWdlIDgsIGxpbmUgMzg8c3Bh
biBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRoPiA8L3RoPjx0aD48
c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFsbD48YSBocmVmPSIjcGFydC0xMCI+
PGVtPiBwYWdlIDgsIGxpbmUgMzg8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+
PC9hPjwvdGg+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgYSBzdGFuZGFyZCBhcHByb2FjaCB0byBhY2NvbXBs
aXNoIHRoYXQuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgYSBzdGFuZGFy
ZCBhcHByb2FjaCB0byBhY2NvbXBsaXNoIHRoYXQuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRvICJzbm9vemUiIGFuIGFsYXJtLCBjbGllbnRzIGNy
ZWF0ZSBhIG5ldyAiVkFMQVJNIiBjb21wb25lbnQgd2l0aGluPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgVG8gInNub296ZSIgYW4gYWxhcm0sIGNsaWVudHMgY3JlYXRl
IGEgbmV3ICJWQUxBUk0iIGNvbXBvbmVudCB3aXRoaW48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgIHRoZSBwYXJlbnQgY29tcG9uZW50IG9mIHRoZSAiVkFMQVJNIiB0aGF0
IHdhcyB0cmlnZ2VyZWQgYW5kIGlzIGJlaW5nPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgdGhlIHBhcmVudCBjb21wb25lbnQgb2YgdGhlICJWQUxBUk0iIHRoYXQgd2Fz
IHRyaWdnZXJlZCBhbmQgaXMgYmVpbmc8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgICJzbm9vemVkIiAoaS5lLiwgYXMgYSAic2libGluZyIgY29tcG9uZW50IG9mIHRoZSAi
VkFMQVJNIiBiZWluZzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICJzbm9v
emVkIiAoaS5lLiwgYXMgYSAic2libGluZyIgY29tcG9uZW50IG9mIHRoZSAiVkFMQVJNIiBi
ZWluZzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgc25vb3plZCkuICBUaGUg
bmV3ICJWQUxBUk0iIE1VU1QgYmUgc2V0IHRvIHRyaWdnZXIgYXQgdGhlIHVzZXInczwvdGQ+
PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIHNub296ZWQpLiAgVGhlIG5ldyAiVkFM
QVJNIiBNVVNUIGJlIHNldCB0byB0cmlnZ2VyIGF0IHRoZSB1c2VyJ3M8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGNob3NlbiAic25vb3plIiBpbnRlcnZhbCBhZnRlciB0
aGUgb3JpZ2luYWwgYWxhcm0gdHJpZ2dlcmVkLiAgQ2xpZW50czwvdGQ+PHRkPiA8L3RkPjx0
ZCBjbGFzcz0icmlnaHQiPiAgIGNob3NlbiAic25vb3plIiBpbnRlcnZhbCBhZnRlciB0aGUg
b3JpZ2luYWwgYWxhcm0gdHJpZ2dlcmVkLiAgQ2xpZW50czwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+ICAgU0hPVUxEIHVzZSBhbiBhYnNvbHV0ZSAiVFJJR0dFUiIgcHJvcGVy
dHkgd2l0aCBhICJEQVRFLVRJTUUiIHZhbHVlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgU0hPVUxEIHVzZSBhbiBhYnNvbHV0ZSAiVFJJR0dFUiIgcHJvcGVydHkgd2l0
aCBhICJEQVRFLVRJTUUiIHZhbHVlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBzcGVjaWZpZWQgaW4gVVRDLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
IHNwZWNpZmllZCBpbiBVVEMuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMjQiPjx0ZD48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgQ2xp
ZW50cyA8c3BhbiBjbGFzcz0iZGVsZXRlIj5TSE9VTEQ8L3NwYW4+IGFkZCBhICJSRUxBVEVE
LVRPIiBwcm9wZXJ0eSB0byB0aGUgbmV3ICJWQUxBUk0iPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyYmxvY2siPiAgIENsaWVudHMgPHNwYW4gY2xhc3M9Imluc2VydCI+TVVTVDwvc3Bh
bj4gYWRkIGEgIlJFTEFURUQtVE8iIHByb3BlcnR5IHRvIHRoZSBuZXcgIlZBTEFSTSI8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGNvbXBvbmVudCB3aXRoIGEgdmFsdWUg
c2V0IHRvIHRoZSAiVUlEIiBwcm9wZXJ0eSB2YWx1ZSBvZiB0aGU8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICBjb21wb25lbnQgd2l0aCBhIHZhbHVlIHNldCB0byB0aGUg
IlVJRCIgcHJvcGVydHkgdmFsdWUgb2YgdGhlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICAiVkFMQVJNIiBjb21wb25lbnQgYmVpbmcgc25vb3plZC4gIElmIHRoZSAiVkFM
QVJNIiBjb21wb25lbnQgYmVpbmc8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICAiVkFMQVJNIiBjb21wb25lbnQgYmVpbmcgc25vb3plZC4gIElmIHRoZSAiVkFMQVJNIiBj
b21wb25lbnQgYmVpbmc8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0ciBpZD0iZGlmZjAwMjUiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgc25vb3plZCBkb2VzIG5vdCBh
bHJlYWR5IGhhdmUgYSAiVUlEIiBwcm9wZXJ0eSwgdGhlIGNsaWVudCA8c3BhbiBjbGFzcz0i
ZGVsZXRlIj5TSE9VTEQ8L3NwYW4+IGFkZDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJs
b2NrIj4gICBzbm9vemVkIGRvZXMgbm90IGFscmVhZHkgaGF2ZSBhICJVSUQiIHByb3BlcnR5
LCB0aGUgY2xpZW50IDxzcGFuIGNsYXNzPSJpbnNlcnQiPk1VU1Q8L3NwYW4+IGFkZDwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgb25lLiAgVGhlICJSRUxBVEVELVRPIiBw
cm9wZXJ0eSBhZGRlZCB0byB0aGUgbmV3ICJWQUxBUk0iIGNvbXBvbmVudDwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIG9uZS4gIFRoZSAiUkVMQVRFRC1UTyIgcHJvcGVy
dHkgYWRkZWQgdG8gdGhlIG5ldyAiVkFMQVJNIiBjb21wb25lbnQ8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMjYiPjx0ZD48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9j
ayI+ICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+U0hPVUxEPC9zcGFuPiBpbmNsdWRlIGEgIlJF
TFRZUEUiIHByb3BlcnR5IHBhcmFtZXRlciB3aXRoIGEgdmFsdWUgc2V0IHRvPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIDxzcGFuIGNsYXNzPSJpbnNlcnQiPk1VU1Q8
L3NwYW4+IGluY2x1ZGUgYSAiUkVMVFlQRSIgcHJvcGVydHkgcGFyYW1ldGVyIHdpdGggYSB2
YWx1ZSBzZXQgdG88L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICJTTk9PWkUi
LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICJTTk9PWkUiLjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9ImRp
ZmYwMDI3Ij48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIFdoZW4gdGhlICJzbm9vemUiIGFsYXJtIGlzIHRy
aWdnZXJlZCBhbmQgZGlzbWlzc2VkIHRoZSBjbGllbnQgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+
U0hPVUxEPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBXaGVu
IHRoZSAic25vb3plIiBhbGFybSBpcyB0cmlnZ2VyZWQgYW5kIGRpc21pc3NlZCB0aGUgY2xp
ZW50IDxzcGFuIGNsYXNzPSJpbnNlcnQiPk1VU1QgZG88L3NwYW4+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgIHJlbW92ZTwvc3Bh
bj4gdGhlIGNvcnJlc3BvbmRpbmcgIlZBTEFSTSIgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+Y29t
cG9uZW50LCBvciBzZXQ8L3NwYW4+IHRoZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJs
b2NrIj48c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICBvbmUgb2YgdGhlIGZvbGxvd2luZyB3aXRo
PC9zcGFuPiB0aGUgY29ycmVzcG9uZGluZyAiVkFMQVJNIiA8c3BhbiBjbGFzcz0iaW5zZXJ0
Ij5jb21wb25lbnQ6PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4g
ICAiQUNLTk9XTEVER0VEIiBwcm9wZXJ0eSAoc2VlIFNlY3Rpb24gPHNwYW4gY2xhc3M9ImRl
bGV0ZSI+Ni4xKS48L3NwYW4+ICBBbHRlcm5hdGl2ZWx5LCBpZiB0aGU8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+PC9zcGFuPjwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAic25vb3plIiBhbGFybSBpcyBpdHNl
bGYgInNub296ZWQiLCB0aGUgY2xpZW50IDxzcGFuIGNsYXNzPSJkZWxldGUiPlNIT1VMRDwv
c3Bhbj4gcmVtb3ZlIHRoZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48c3Bh
biBjbGFzcz0iaW5zZXJ0Ij4gICBvICBTZXQ8L3NwYW4+IHRoZSAiQUNLTk9XTEVER0VEIiBw
cm9wZXJ0eSAoc2VlIFNlY3Rpb24gPHNwYW4gY2xhc3M9Imluc2VydCI+Ni4xKTwvc3Bhbj48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgb3JpZ2luYWwgInNub296ZSIg
YWxhcm0gYW5kIGNyZWF0ZSBhIG5ldyBvbmUsIHdpdGggdGhlIGFwcHJvcHJpYXRlPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPjwvc3Bh
bj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgdHJpZ2dlciB0aW1lIGFu
ZCByZWxhdGlvbnNoaXAgc2V0LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj48
c3BhbiBjbGFzcz0iaW5zZXJ0Ij4gICBvICBSZW1vdmUgdGhlIGNvbXBvbmVudDwvc3Bhbj48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyYmxvY2siPiAgIEFsdGVybmF0aXZlbHksIGlmIHRoZSAic25vb3plIiBhbGFybSBp
cyBpdHNlbGYgInNub296ZWQiLCB0aGUgY2xpZW50PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICA8c3BhbiBj
bGFzcz0iaW5zZXJ0Ij5NVVNUPC9zcGFuPiByZW1vdmUgdGhlIG9yaWdpbmFsICJzbm9vemUi
IGFsYXJtIGFuZCBjcmVhdGUgYSBuZXcgb25lLCB3aXRoPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICB0aGUg
YXBwcm9wcmlhdGUgdHJpZ2dlciB0aW1lIGFuZCByZWxhdGlvbnNoaXAgc2V0LjwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJi
bG9jayI+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJs
b2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgPHNwYW4gY2xhc3M9
Imluc2VydCI+Tm90ZSB0aGF0IHJlZ2FyZGxlc3Mgb2YgdGhlIGZpbmFsIGRpc3Bvc2l0aW9u
IG9mIHRoZSAic25vb3plIiBhbGFybTwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNz
PSJpbnNlcnQiPiAgIHdoZW4gdHJpZ2dlcmVkLCB0aGUgb3JpZ2luYWwgIlZBTEFSTSIgY29t
cG9uZW50IGlzIGxlZnQgdW5jaGFuZ2VkLjwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+Ny4xLiAgUmVsYXRpb25zaGlwIFR5cGUgUHJvcGVydHkg
UGFyYW1ldGVyPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+Ny4xLiAgUmVsYXRp
b25zaGlwIFR5cGUgUHJvcGVydHkgUGFyYW1ldGVyPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoaXMgc3BlY2lmaWNhdGlvbiBhZGRzIHRoZSAiU05P
T1pFIiByZWxhdGlvbnNoaXAgdHlwZSBmb3IgdXNlIHdpdGg8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICBUaGlzIHNwZWNpZmljYXRpb24gYWRkcyB0aGUgIlNOT09aRSIg
cmVsYXRpb25zaGlwIHR5cGUgZm9yIHVzZSB3aXRoPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICB0aGUgIlJFTFRZUEUiIHByb3BlcnR5IGRlZmluZWQgaW4gU2VjdGlvbiAz
LjIuMTUgb2YgW1JGQzU1NDVdLiAgVGhpczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgIHRoZSAiUkVMVFlQRSIgcHJvcGVydHkgZGVmaW5lZCBpbiBTZWN0aW9uIDMuMi4x
NSBvZiBbUkZDNTU0NV0uICBUaGlzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHIgaWQ9ImRpZmYwMDI4Ij48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIGlzIHVzZWQgPHNw
YW4gY2xhc3M9ImRlbGV0ZSI+dG8gcmVsYXRlPC9zcGFuPiBhICJzbm9vemVkIiAiVkFMQVJN
IiBjb21wb25lbnQgdG8gdGhlIG9yaWdpbmFsPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPiAgIGlzIHVzZWQgPHNwYW4gY2xhc3M9Imluc2VydCI+d2hlbiByZWxhdGluZzwv
c3Bhbj4gYSAic25vb3plZCIgIlZBTEFSTSIgY29tcG9uZW50IHRvIHRoZSBvcmlnaW5hbDwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgYWxhcm0gdGhhdCB0aGUgInNub296
ZSIgd2FzIGdlbmVyYXRlZCBmb3IuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgYWxhcm0gdGhhdCB0aGUgInNub296ZSIgd2FzIGdlbmVyYXRlZCBmb3IuPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjguICBBbGFybSBQcm94aW1pdHkg
VHJpZ2dlcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjguICBBbGFybSBQcm94
aW1pdHkgVHJpZ2dlcjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0
Ij4gICBWQUxBUk1zIGFyZSBjdXJyZW50bHkgdHJpZ2dlcmVkIHdoZW4gYSBzcGVjaWZpYyBk
YXRlLXRpbWUgaXMgcmVhY2hlZC48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4g
ICBWQUxBUk1zIGFyZSBjdXJyZW50bHkgdHJpZ2dlcmVkIHdoZW4gYSBzcGVjaWZpYyBkYXRl
LXRpbWUgaXMgcmVhY2hlZC48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIEl0
IGlzIGFsc28gZGVzaXJhYmxlIHRvIGJlIGFibGUgdG8gdHJpZ2dlciBhbGFybXMgYmFzZWQg
b24gbG9jYXRpb24sPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgSXQgaXMg
YWxzbyBkZXNpcmFibGUgdG8gYmUgYWJsZSB0byB0cmlnZ2VyIGFsYXJtcyBiYXNlZCBvbiBs
b2NhdGlvbiw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGUuZy4gd2hlbiBh
cnJpdmluZyBhdCBvciBkZXBhcnRpbmcgZnJvbSBhIHBhcnRpY3VsYXIgbG9jYXRpb24uPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgZS5nLiB3aGVuIGFycml2aW5nIGF0
IG9yIGRlcGFydGluZyBmcm9tIGEgcGFydGljdWxhciBsb2NhdGlvbi48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVGhpcyBzcGVjaWZpY2F0aW9uIGFk
ZHMgdGhlIGZvbGxvd2luZyBwcm9wZXJ0aWVzIHRvICJWQUxBUk0iPC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgVGhpcyBzcGVjaWZpY2F0aW9uIGFkZHMgdGhlIGZvbGxv
d2luZyBwcm9wZXJ0aWVzIHRvICJWQUxBUk0iPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICBjb21wb25lbnRzIHRvIGluZGljYXRlIHdoZW4gYW4gYWxhcm0gY2FuIGJlIHRy
aWdnZXJlZCBiYXNlZCBvbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGNv
bXBvbmVudHMgdG8gaW5kaWNhdGUgd2hlbiBhbiBhbGFybSBjYW4gYmUgdHJpZ2dlcmVkIGJh
c2VkIG9uPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBsb2NhdGlvbi48L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBsb2NhdGlvbi48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgIlBST1hJTUlUWSIgLSBpbmRp
Y2F0ZXMgdGhhdCBhIGxvY2F0aW9uIGJhc2VkIHRyaWdnZXIgaXMgdG8gYmU8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAiUFJPWElNSVRZIiAtIGluZGljYXRlcyB0
aGF0IGEgbG9jYXRpb24gYmFzZWQgdHJpZ2dlciBpcyB0byBiZTwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgdXNlZCBhbmQgd2hpY2ggZGlyZWN0aW9uIG9mIG1vdGlv
biBpcyB1c2VkIGZvciB0aGUgdHJpZ2dlcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgICAgIHVzZWQgYW5kIHdoaWNoIGRpcmVjdGlvbiBvZiBtb3Rpb24gaXMgdXNlZCBm
b3IgdGhlIHRyaWdnZXI8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+ICAgICAgIlNUUlVDVFVSRUQtTE9DQVRJT04iIFtJLUQuaWV0Zi1jYWxleHQtZXZlbnRw
dWItZXh0ZW5zaW9uc10gLSB1c2VkPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgICAgIlNUUlVDVFVSRUQtTE9DQVRJT04iIFtJLUQuaWV0Zi1jYWxleHQtZXZlbnRwdWIt
ZXh0ZW5zaW9uc10gLSB1c2VkPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAg
ICB0byBpbmRpY2F0ZSB0aGUgYWN0dWFsIGxvY2F0aW9uIHRvIHRyaWdnZXIgb2ZmLCBzcGVj
aWZpZWQgdXNpbmcgYTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIHRv
IGluZGljYXRlIHRoZSBhY3R1YWwgbG9jYXRpb24gdG8gdHJpZ2dlciBvZmYsIHNwZWNpZmll
ZCB1c2luZyBhPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBnZW86IFVS
SSBbUkZDNTg3MF0gd2hpY2ggYWxsb3dzIGZvciB0d28gb3IgdGhyZWUgY29vcmRpbmF0ZSB2
YWx1ZXM8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICBnZW86IFVSSSBb
UkZDNTg3MF0gd2hpY2ggYWxsb3dzIGZvciB0d28gb3IgdGhyZWUgY29vcmRpbmF0ZSB2YWx1
ZXM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIHdpdGggYW4gb3B0aW9u
YWwgdW5jZXJ0YWludHk8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICB3
aXRoIGFuIG9wdGlvbmFsIHVuY2VydGFpbnR5PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMjkiPjx0ZD48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9j
ayI+ICAgYWxhcm1wcm9wICAgICAgIDxzcGFuIGNsYXNzPSJkZWxldGUiPi89ICo8L3NwYW4+
KDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBhbGFybXByb3AgICAgICAg
PHNwYW4gY2xhc3M9Imluc2VydCI+PS8gPC9zcGFuPig8L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAgICAgIDsgdGhlIGZvbGxv
d2luZyBpcyBPUFRJT05BTCw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAg
ICAgICAgICAgICAgICAgICAgOyB0aGUgZm9sbG93aW5nIGlzIE9QVElPTkFMLDwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICAgICAgICAgIDsgYnV0IE1V
U1QgTk9UIG9jY3VyIG1vcmUgdGhhbiBvbmNlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgICAgICAgICAgICAgICAgICAgIDsgYnV0IE1VU1QgTk9UIG9jY3VyIG1vcmUg
dGhhbiBvbmNlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAg
ICAgICAgICAgICAgICAgICAgICBwcm94aW1pdHkgLzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICAgICBwcm94aW1pdHkgLzwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgICAg
OyB0aGUgZm9sbG93aW5nIGlzIE9QVElPTkFMLDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPiAgICAgICAgICAgICAgICAgICAgICA7IHRoZSBmb2xsb3dpbmcgaXMgT1BUSU9O
QUwsPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAg
ICAgOyBhbmQgTUFZIG9jY3VyIG1vcmUgdGhhbiBvbmNlLCBidXQgb25seTwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgICAgICAgICA7IGFuZCBNQVkg
b2NjdXIgbW9yZSB0aGFuIG9uY2UsIGJ1dCBvbmx5PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAgICAgOyB3aGVuIGEgUFJPWElNSVRZIHByb3Bl
cnR5IGlzIGFsc28gcHJlc2VudDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
ICAgICAgICAgICAgICAgICAgICA7IHdoZW4gYSBQUk9YSU1JVFkgcHJvcGVydHkgaXMgYWxz
byBwcmVzZW50PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJwYXJ0LTExIiBjbGFzcz0iY2hhbmdlIj48dGQ+
PC90ZD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0i
I3BhcnQtMTEiPjxlbT4gcGFnZSAxMCwgbGluZSAyOTxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8
L3NwYW4+PC9lbT48L2E+PC90aD48dGg+IDwvdGg+PHRoPjxzbWFsbD5za2lwcGluZyB0byBj
aGFuZ2UgYXQ8L3NtYWxsPjxhIGhyZWY9IiNwYXJ0LTExIj48ZW0+IHBhZ2UgMTAsIGxpbmUg
Mzc8c3BhbiBjbGFzcz0iaGlkZSI+IMK2PC9zcGFuPjwvZW0+PC9hPjwvdGg+PHRkPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICBEZXNjcmlwdGlvbjogIFRoaXMgcHJvcGVydHkgaXMgdXNlZCB0
byBpbmRpY2F0ZSB0aGF0IGFuIGFsYXJtIGhhcyBhPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgRGVzY3JpcHRpb246ICBUaGlzIHByb3BlcnR5IGlzIHVzZWQgdG8gaW5k
aWNhdGUgdGhhdCBhbiBhbGFybSBoYXMgYTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+ICAgICAgbG9jYXRpb24tYmFzZWQgdHJpZ2dlci4gIEl0cyB2YWx1ZSBpZGVudGlmaWVz
IHRoZSBkaXJlY3Rpb24gb2Y8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAg
ICBsb2NhdGlvbi1iYXNlZCB0cmlnZ2VyLiAgSXRzIHZhbHVlIGlkZW50aWZpZXMgdGhlIGRp
cmVjdGlvbiBvZjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgbW90aW9u
IHVzZWQgdG8gdHJpZ2dlciB0aGUgYWxhcm0uICBPbmUgb3IgbW9yZSBsb2NhdGlvbiB2YWx1
ZXMgYXJlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgbW90aW9uIHVz
ZWQgdG8gdHJpZ2dlciB0aGUgYWxhcm0uICBPbmUgb3IgbW9yZSBsb2NhdGlvbiB2YWx1ZXMg
YXJlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBzZXQgdXNpbmcgIlNU
UlVDVFVSRUQtTE9DQVRJT04iIHByb3BlcnRpZXMuPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+ICAgICAgc2V0IHVzaW5nICJTVFJVQ1RVUkVELUxPQ0FUSU9OIiBwcm9wZXJ0
aWVzLjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAg
ICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICBX
aGVuIHRoZSBwcm9wZXJ0eSB2YWx1ZSBpcyBzZXQgdG8gIkFSUklWRSIsIHRoZSBhbGFybSBp
cyB0cmlnZ2VyZWQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICBXaGVu
IHRoZSBwcm9wZXJ0eSB2YWx1ZSBpcyBzZXQgdG8gIkFSUklWRSIsIHRoZSBhbGFybSBpcyB0
cmlnZ2VyZWQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgIHdoZW4gdGhl
IGNhbGVuZGFyIHVzZXIgYWdlbnQgYXJyaXZlcyBpbiB0aGUgdmljaW5pdHkgb2YgYW55IG9m
IHRoZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgIHdoZW4gdGhlIGNh
bGVuZGFyIHVzZXIgYWdlbnQgYXJyaXZlcyBpbiB0aGUgdmljaW5pdHkgb2YgYW55IG9mIHRo
ZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgc3BlY2lmaWVkIGxvY2F0
aW9ucy4gIFdoZW4gc2V0IHRvICJERVBBUlQiLCB0aGUgYWxhcm0gaXMgdHJpZ2dlcmVkPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgc3BlY2lmaWVkIGxvY2F0aW9u
cy4gIFdoZW4gc2V0IHRvICJERVBBUlQiLCB0aGUgYWxhcm0gaXMgdHJpZ2dlcmVkPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICB3aGVuIHRoZSBjYWxlbmRhciB1c2Vy
IGFnZW50IGRlcGFydHMgZnJvbSB0aGUgdmljaW5pdHkgb2YgYW55PC90ZD48dGQ+IDwvdGQ+
PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgd2hlbiB0aGUgY2FsZW5kYXIgdXNlciBhZ2VudCBk
ZXBhcnRzIGZyb20gdGhlIHZpY2luaXR5IG9mIGFueTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAzMCI+PHRkPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAg
ICBzcGVjaWZpZWQgbG9jYXRpb25zLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2Nr
Ij4gICAgICBzcGVjaWZpZWQgbG9jYXRpb25zLiAgPHNwYW4gY2xhc3M9Imluc2VydCI+Tm90
ZSB0aGF0IHRoZSBtZWFuaW5nIG9mICJ2aWNpbml0eSIgaW4gdGhpczwvc3Bhbj48L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgICAgIGNvbnRleHQgaXMgaW1wbGVtZW50
YXRpb24gZGVmaW5lZC48L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPiAgICAgIFdoZW4gdGhlIHByb3BlcnR5IHZhbHVlIGlzIHNldCB0byAiQ09O
TkVDVCIsIHRoZSBhbGFybSBpczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
ICAgIFdoZW4gdGhlIHByb3BlcnR5IHZhbHVlIGlzIHNldCB0byAiQ09OTkVDVCIsIHRoZSBh
bGFybSBpczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlk
PSJkaWZmMDAzMSI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgICB0cmlnZ2VyZWQgd2hlbiB0aGUgY2Fs
ZW5kYXIgdXNlciBhZ2VudCBjb25uZWN0cyB0byA8c3BhbiBjbGFzcz0iZGVsZXRlIj5hPC9z
cGFuPiBCbHVldG9vdGgoUik8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAg
ICAgdHJpZ2dlcmVkIHdoZW4gdGhlIGNhbGVuZGFyIHVzZXIgYWdlbnQgY29ubmVjdHMgdG8g
PHNwYW4gY2xhc3M9Imluc2VydCI+YW4gYXV0b21vYmlsZTwvc3Bhbj48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+W0JUY29y
ZV0tZW5hYmxlZCBhdXRvbW9iaWxlLjwvc3Bhbj4gIFdoZW4gc2V0IHRvICJESVNDT05ORUNU
IiwgdGhlIGFsYXJtPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNs
YXNzPSJpbnNlcnQiPiAgICAgIHRoYXQgaXMgZW5hYmxlZCBmb3I8L3NwYW4+IEJsdWV0b290
aChSKSA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5bQlRjb3JlXS48L3NwYW4+ICBXaGVuIHNldCB0
bzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgICBpcyB0cmlnZ2VyZWQg
d2hlbiB0aGUgY2FsZW5kYXIgdXNlciBhZ2VudCBkaXNjb25uZWN0cyBmcm9tIDxzcGFuIGNs
YXNzPSJkZWxldGUiPmE8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2si
PiAgICAgICJESVNDT05ORUNUIiwgdGhlIGFsYXJtIGlzIHRyaWdnZXJlZCB3aGVuIHRoZSBj
YWxlbmRhciB1c2VyIGFnZW50PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxz
cGFuIGNsYXNzPSJkZWxldGUiPiAgICAgIEJsdWV0b290aChSKS1lbmFibGVkIGF1dG9tb2Jp
bGUuPC9zcGFuPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAgICBkaXNj
b25uZWN0cyBmcm9tIDxzcGFuIGNsYXNzPSJpbnNlcnQiPmFuIGF1dG9tb2JpbGUgdGhhdCBp
cyBlbmFibGVkIGZvciBCbHVldG9vdGgoUikuPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBGb3JtYXQgRGVmaW5pdGlvbjogIFRoaXMgcHJv
cGVydHkgaXMgZGVmaW5lZCBieSB0aGUgZm9sbG93aW5nPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgRm9ybWF0IERlZmluaXRpb246ICBUaGlzIHByb3BlcnR5IGlzIGRl
ZmluZWQgYnkgdGhlIGZvbGxvd2luZzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgICAgbm90YXRpb246PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAg
bm90YXRpb246PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+
CiAgICAgIDx0ciBpZD0iZGlmZjAwMzIiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgcHJveGltaXR5ID0g
IlBST1hJTUlUWSIgcHJveGltaXR5cGFyYW0gIjoiIHByb3hpbWl0eXZhbHVlIENSTEY8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+ICAgcHJveGltaXR5ID0gIlBST1hJTUlU
WSIgPHNwYW4gY2xhc3M9Imluc2VydCI+Kjwvc3Bhbj5wcm94aW1pdHlwYXJhbSAiOiIgcHJv
eGltaXR5dmFsdWUgQ1JMRjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHIgaWQ9ImRpZmYwMDMzIj48dGQ+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPiAgIHByb3hp
bWl0eXBhcmFtICA9IDxzcGFuIGNsYXNzPSJkZWxldGUiPio8L3NwYW4+KDwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBwcm94aW1pdHlwYXJhbSAgPSAoPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgICAgICAg
IDsgdGhlIGZvbGxvd2luZyBpcyBPUFRJT05BTCw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgICA7IHRoZSBmb2xsb3dpbmcgaXMgT1BUSU9O
QUwsPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgICAgICAg
ICA7IGFuZCBNQVkgb2NjdXIgbW9yZSB0aGFuIG9uY2U8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgICA7IGFuZCBNQVkgb2NjdXIgbW9yZSB0
aGFuIG9uY2U8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
ICAgICAgICAgICAgICAgICAgKCI7IiBvdGhlci1wYXJhbSk8L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgICAoIjsiIG90aGVyLXBhcmFtKTwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAg
ICAgICAgICApPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAg
ICAgICAgICAgKTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICBwcm94aW1pdHl2YWx1ZSAgPSAiQVJSSVZFIiAvICJERVBBUlQiIC88L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBwcm94aW1pdHl2YWx1ZSAgPSAiQVJSSVZFIiAvICJE
RVBBUlQiIC88L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAg
ICAgICAgICJDT05ORUNUIiAvICJESVNDT05ORUNUIiAvIGlhbmEtdG9rZW4gLyB4LW5hbWU8
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICAgICAgICAi
Q09OTkVDVCIgLyAiRElTQ09OTkVDVCIgLyBpYW5hLXRva2VuIC8geC1uYW1lPC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlm
ZjAwMzQiPjx0ZD48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxibG9jayI+ICAgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+RXhhbXBsZTog
IFRoZSBmb2xsb3dpbmcgaXMgYW4gZXhhbXBsZSBvZiB0aGlzIHByb3BlcnR5Ojwvc3Bhbj48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJkZWxldGUiPjwvc3Bhbj48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2si
PjxzcGFuIGNsYXNzPSJkZWxldGUiPiAgIFBST1hJTUlUWTpBUlJJVkU8L3NwYW4+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGJsb2NrIj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+OC4yLiAgRXhhbXBsZTwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjguMi4gIEV4YW1wbGU8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVGhlIGZvbGxvd2luZyBleGFt
cGxlIHNob3dzIGEgIlZBTEFSTSIgY29tcG9uZW50IHdpdGggYSBwcm94aW1pdHk8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBUaGUgZm9sbG93aW5nIGV4YW1wbGUgc2hv
d3MgYSAiVkFMQVJNIiBjb21wb25lbnQgd2l0aCBhIHByb3hpbWl0eTwvdGQ+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
Pjx0ZCBjbGFzcz0ibGVmdCI+ICAgdHJpZ2dlciBzZXQgdG8gdHJpZ2dlciB3aGVuIHRoZSBk
ZXZpY2UgcnVubmluZyB0aGUgY2FsZW5kYXIgdXNlcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIHRyaWdnZXIgc2V0IHRvIHRyaWdnZXIgd2hlbiB0aGUgZGV2aWNlIHJ1
bm5pbmcgdGhlIGNhbGVuZGFyIHVzZXI8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgIGFnZW50IGxlYXZlcyB0aGUgdmljaW5pdHkgZGVmaW5lZCBieSB0aGUgc3RydWN0dXJl
ZCBsb2NhdGlvbjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIGFnZW50IGxl
YXZlcyB0aGUgdmljaW5pdHkgZGVmaW5lZCBieSB0aGUgc3RydWN0dXJlZCBsb2NhdGlvbjwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgcHJvcGVydHkuICBOb3RlIHVzZSBv
ZiB0aGUgInU9IiBwYXJhbWV0ZXIgd2l0aCB0aGUgImdlbyIgVVJJIHRvPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgcHJvcGVydHkuICBOb3RlIHVzZSBvZiB0aGUgInU9
IiBwYXJhbWV0ZXIgd2l0aCB0aGUgImdlbyIgVVJJIHRvPC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICBkZWZpbmUgdGhlIHByZWNpc2lvbiBvZiB0aGUgbG9jYXRpb24gZGV0
ZXJtaW5hdGlvbi48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBkZWZpbmUg
dGhlIHByZWNpc2lvbiBvZiB0aGUgbG9jYXRpb24gZGV0ZXJtaW5hdGlvbi48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgQkVHSU46VkFMQVJNPC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgQkVHSU46VkFMQVJNPC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBVSUQ6NzdEODBEMTQtOTA2Qi00MjU3LTk2M0YtODVC
MUU3MzREQkI2PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgVUlEOjc3RDgw
RDE0LTkwNkItNDI1Ny05NjNGLTg1QjFFNzM0REJCNjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9InBhcnQtMTIiIGNsYXNzPSJj
aGFuZ2UiPjx0ZD48L3RkPjx0aD48c21hbGw+c2tpcHBpbmcgdG8gY2hhbmdlIGF0PC9zbWFs
bD48YSBocmVmPSIjcGFydC0xMiI+PGVtPiBwYWdlIDEyLCBsaW5lIDEwPHNwYW4gY2xhc3M9
ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0aD4gPC90aD48dGg+PHNtYWxsPnNr
aXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iI3BhcnQtMTIiPjxlbT4gcGFn
ZSAxMiwgbGluZSAxOTxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90
aD48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICBvciBhcnJpdmVkIGF0IHRoZSBsb2NhdGlvbi4gIFRoZXJlZm9y
ZSwgQ2FsREFWIGNsaWVudHMgdGhhdCBpbXBsZW1lbnQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij4gICBvciBhcnJpdmVkIGF0IHRoZSBsb2NhdGlvbi4gIFRoZXJlZm9yZSwg
Q2FsREFWIGNsaWVudHMgdGhhdCBpbXBsZW1lbnQ8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgIHByb3hpbWl0eSBhbGFybXMgU0hPVUxEIGdpdmUgdXNlcnMgdGhlIG9wdGlv
biBvZiBzdG9yaW5nIGFuZC9vcjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
IHByb3hpbWl0eSBhbGFybXMgU0hPVUxEIGdpdmUgdXNlcnMgdGhlIG9wdGlvbiBvZiBzdG9y
aW5nIGFuZC9vcjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgYWNrbm93bGVk
Z2luZyB0aGUgYWxhcm1zIG9uIHRoZSBsb2NhbCBkZXZpY2Ugb25seSBhbmQgbm90IHN0b3Jp
bmcgdGhlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgYWNrbm93bGVkZ2lu
ZyB0aGUgYWxhcm1zIG9uIHRoZSBsb2NhbCBkZXZpY2Ugb25seSBhbmQgbm90IHN0b3Jpbmcg
dGhlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBhbGFybSBhbmQvb3IgYWNr
bm93bGVkZ21lbnQgb24gYSByZW1vdGUgc2VydmVyLjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFz
cz0icmlnaHQiPiAgIGFsYXJtIGFuZC9vciBhY2tub3dsZWRnbWVudCBvbiBhIHJlbW90ZSBz
ZXJ2ZXIuPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAg
ICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjExLiAg
SUFOQSBDb25zaWRlcmF0aW9uczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjEx
LiAgSUFOQSBDb25zaWRlcmF0aW9uczwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4xMS4xLiAgUHJvcGVydHkgUmVnaXN0cmF0aW9uczwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPjExLjEuICBQcm9wZXJ0eSBSZWdpc3RyYXRpb25zPC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIFRoaXMgZG9jdW1lbnQg
ZGVmaW5lcyB0aGUgZm9sbG93aW5nIG5ldyBpQ2FsZW5kYXIgcHJvcGVydGllcyB0byBiZTwv
dGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRoaXMgZG9jdW1lbnQgZGVmaW5l
cyB0aGUgZm9sbG93aW5nIG5ldyBpQ2FsZW5kYXIgcHJvcGVydGllcyB0byBiZTwvdGQ+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDAzNSI+PHRk
PjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFz
cz0ibGJsb2NrIj4gICBhZGRlZCB0byB0aGUgcmVnaXN0cnkgZGVmaW5lZCBpbiBTZWN0aW9u
IDguMi4zIG9mIDxzcGFuIGNsYXNzPSJkZWxldGUiPltSRkM1NTQ1XTo8L3NwYW4+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPiAgIGFkZGVkIHRvIHRoZSByZWdpc3RyeSBk
ZWZpbmVkIGluIFNlY3Rpb24gOC4yLjMgb2YgPHNwYW4gY2xhc3M9Imluc2VydCI+W1JGQzU1
NDVdIGFuZDwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgIGxv
Y2F0ZWQgaGVyZTogJmx0O2h0dHBzOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzL2ljYWxl
bmRhciNwcm9wZXJ0aWVzJmd0Ozwvc3Bhbj48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICstLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0r
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLSs8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLSstLS0tLS0tLS0tLS0t
LS0tLS0tLS0tKzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAg
IHwgUHJvcGVydHkgICAgIHwgU3RhdHVzICB8IFJlZmVyZW5jZSAgICAgICAgICAgIHw8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgfCBQcm9wZXJ0eSAg
ICAgfCBTdGF0dXMgIHwgUmVmZXJlbmNlICAgICAgICAgICAgfDwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICstLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0r
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLSs8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLSstLS0tLS0tLS0tLS0t
LS0tLS0tLS0tKzwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAg
IHwgQUNLTk9XTEVER0VEIHwgQ3VycmVudCB8IFJGQ1hYWFgsIFNlY3Rpb24gNi4xIHw8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgfCBBQ0tOT1dMRURH
RUQgfCBDdXJyZW50IHwgUkZDWFhYWCwgU2VjdGlvbiA2LjEgfDwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgIHwgUFJPWElNSVRZICAgIHwgQ3VycmVudCB8
IFJGQ1hYWFgsIFNlY3Rpb24gOC4xIHw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICAgICAgICAgICAgfCBQUk9YSU1JVFkgICAgfCBDdXJyZW50IHwgUkZDWFhYWCwgU2Vj
dGlvbiA4LjEgfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAg
ICstLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSs8L3Rk
Pjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgKy0tLS0tLS0tLS0t
LS0tKy0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tKzwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4xMS4yLiAgUmVsYXRpb25zaGlwIFR5cGVzIFJl
Z2lzdHJ5PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+MTEuMi4gIFJlbGF0aW9u
c2hpcCBUeXBlcyBSZWdpc3RyeTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsZWZ0Ij4gICBUaGlzIGRvY3VtZW50IGRlZmluZXMgdGhlIGZvbGxvd2luZyBuZXcgaUNh
bGVuZGFyIHJlbGF0aW9uc2hpcCB0eXBlPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgVGhpcyBkb2N1bWVudCBkZWZpbmVzIHRoZSBmb2xsb3dpbmcgbmV3IGlDYWxlbmRh
ciByZWxhdGlvbnNoaXAgdHlwZTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyIGlkPSJkaWZmMDAzNiI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICB0byBiZSBhZGRlZCB0
byB0aGUgcmVnaXN0cnkgZGVmaW5lZCBpbiBTZWN0aW9uIDguMy44IG9mIDxzcGFuIGNsYXNz
PSJkZWxldGUiPltSRkM1NTQ1XTo8L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
YmxvY2siPiAgIHRvIGJlIGFkZGVkIHRvIHRoZSByZWdpc3RyeSBkZWZpbmVkIGluIFNlY3Rp
b24gOC4zLjggb2YgPHNwYW4gY2xhc3M9Imluc2VydCI+W1JGQzU1NDVdIGFuZDwvc3Bhbj48
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyYmxvY2siPjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgIGxvY2F0ZWQgaGVyZTogJmx0
O2h0dHBzOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzLzwvc3Bhbj48L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxibG9jayI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2si
PjxzcGFuIGNsYXNzPSJpbnNlcnQiPiAgIGljYWxlbmRhciNyZWxhdGlvbnNoaXAtdHlwZXMm
Z3Q7PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3Ry
PgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4g
ICAgICAgICAgKy0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0rPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICst
LS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tKzwv
dGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgIHwgUmVsYXRpb25zaGlw
IFR5cGUgfCBTdGF0dXMgIHwgUmVmZXJlbmNlICAgICAgICAgICAgfDwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICB8IFJlbGF0aW9uc2hpcCBUeXBlIHwgU3Rh
dHVzICB8IFJlZmVyZW5jZSAgICAgICAgICAgIHw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0rLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLSs8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAg
ICAgICAgKy0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0rPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgfCBTTk9P
WkUgICAgICAgICAgICB8IEN1cnJlbnQgfCBSRkNYWFhYLCBTZWN0aW9uIDcuMSB8PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgIHwgU05PT1pFICAgICAgICAg
ICAgfCBDdXJyZW50IHwgUkZDWFhYWCwgU2VjdGlvbiA3LjEgfDwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICstLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0t
LSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tKzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmln
aHQiPiAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0rLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLSs8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+MTEuMy4gIFByb3hpbWl0eSBWYWx1ZSBSZWdpc3RyeTwvdGQ+PHRkPiA8L3RkPjx0ZCBj
bGFzcz0icmlnaHQiPjExLjMuICBQcm94aW1pdHkgVmFsdWUgUmVnaXN0cnk8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgVGhpcyBkb2N1bWVudCBjcmVh
dGVzIGEgbmV3IGlDYWxlbmRhciByZWdpc3RyeSBmb3IgdmFsdWVzIG9mIHRoZTwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFRoaXMgZG9jdW1lbnQgY3JlYXRlcyBhIG5l
dyBpQ2FsZW5kYXIgcmVnaXN0cnkgZm9yIHZhbHVlcyBvZiB0aGU8L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMzciPjx0ZD48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxibG9j
ayI+ICAgIlBST1hJTUlUWSIgPHNwYW4gY2xhc3M9ImRlbGV0ZSI+cHJvcGVydHk6PC9zcGFu
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICAiUFJPWElNSVRZIiA8c3Bh
biBjbGFzcz0iaW5zZXJ0Ij5wcm9wZXJ0eSBsb2NhdGVkIGhlcmU6ICZsdDtodHRwczovL3d3
dy5pYW5hLm9yZy9hc3NpZ25tZW50cy88L3NwYW4+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNz
PSJsYmxvY2siPiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICA8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9
InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgaWNhbGVuZGFyI3Byb3hpbWl0eS12
YWx1ZXMmZ3Q7PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAg
ICAgICAgICArLS0tLS0tLS0tLS0tKy0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0t
KzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgKy0tLS0t
LS0tLS0tLSstLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSs8L3RkPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgfCBWYWx1ZSAgICAgIHwgU3RhdHVz
ICB8IFJlZmVyZW5jZSAgICAgICAgICAgIHw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij4gICAgICAgICAgICAgIHwgVmFsdWUgICAgICB8IFN0YXR1cyAgfCBSZWZlcmVuY2Ug
ICAgICAgICAgICB8PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAg
ICAgICstLS0tLS0tLS0tLS0rLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rPC90
ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICArLS0tLS0tLS0t
LS0tKy0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tKzwvdGQ+PHRkIGNsYXNzPSJs
aW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0
ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICB8IEFSUklWRSAgICAgfCBDdXJyZW50IHwg
UkZDWFhYWCwgU2VjdGlvbiA4LjEgfDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgICAgICAgICAgICAgfCBBUlJJVkUgICAgIHwgQ3VycmVudCB8IFJGQ1hYWFgsIFNlY3Rp
b24gOC4xIHw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAg
fCBERVBBUlQgICAgIHwgQ3VycmVudCB8IFJGQ1hYWFgsIFNlY3Rpb24gOC4xIHw8L3RkPjx0
ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgIHwgREVQQVJUICAgICB8
IEN1cnJlbnQgfCBSRkNYWFhYLCBTZWN0aW9uIDguMSB8PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICAgICAgICAgICAgIHwgQ09OTkVDVCAgICB8IEN1cnJlbnQgfCBSRkNY
WFhYLCBTZWN0aW9uIDguMSB8PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAg
ICAgICAgICAgICB8IENPTk5FQ1QgICAgfCBDdXJyZW50IHwgUkZDWFhYWCwgU2VjdGlvbiA4
LjEgfDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAgICAgICAgICB8IERJ
U0NPTk5FQ1QgfCBDdXJyZW50IHwgUkZDWFhYWCwgU2VjdGlvbiA4LjEgfDwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAgICAgfCBESVNDT05ORUNUIHwgQ3Vy
cmVudCB8IFJGQ1hYWFgsIFNlY3Rpb24gOC4xIHw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxlZnQiPiAgICAgICAgICAgICAgKy0tLS0tLS0tLS0tLSstLS0tLS0tLS0rLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLSs8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAg
ICAgICAgICstLS0tLS0tLS0tLS0rLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0r
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjEyLiAgQWNrbm93
bGVkZ21lbnRzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+MTIuICBBY2tub3ds
ZWRnbWVudHM8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3Rk
Pjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
VGhpcyBzcGVjaWZpY2F0aW9uIGNhbWUgYWJvdXQgdmlhIGRpc2N1c3Npb25zIGF0IHRoZSBD
YWxlbmRhcmluZyBhbmQ8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBUaGlz
IHNwZWNpZmljYXRpb24gY2FtZSBhYm91dCB2aWEgZGlzY3Vzc2lvbnMgYXQgdGhlIENhbGVu
ZGFyaW5nIGFuZDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRy
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgU2NoZWR1bGlu
ZyBDb25zb3J0aXVtLiAgQWxzbywgdGhhbmtzIHRvIHRoZSBmb2xsb3dpbmcgZm9yIHByb3Zp
ZGluZzwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgIFNjaGVkdWxpbmcgQ29u
c29ydGl1bS4gIEFsc28sIHRoYW5rcyB0byB0aGUgZm9sbG93aW5nIGZvciBwcm92aWRpbmc8
L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIGZlZWRiYWNrOiBCZXJuYXJkIERl
c3J1aXNzZWF1eCwgTWlrZSBEb3VnbGFzcywgSmFjb2IgRmFya2FzLCBKZWZmcmV5PC90ZD48
dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgZmVlZGJhY2s6IEJlcm5hcmQgRGVzcnVp
c3NlYXV4LCBNaWtlIERvdWdsYXNzLCBKYWNvYiBGYXJrYXMsIEplZmZyZXk8L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0ciBpZD0iZGlmZjAwMzgiPjx0ZD48
L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9
ImxibG9jayI+ICAgSGFycmlzLCA8c3BhbiBjbGFzcz0iZGVsZXRlIj5hbmQgQ2lueSBKb3k8
L3NwYW4+LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJsb2NrIj4gICBIYXJyaXMsIDxz
cGFuIGNsYXNzPSJpbnNlcnQiPkNpbnkgSm95LCBCYXJyeSBMZWliYSwgYW5kIERhbmllbCBN
aWdhdWx0PC9zcGFuPi48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAg
IDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRk
PiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVm
dCI+MTMuICBSZWZlcmVuY2VzPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+MTMu
ICBSZWZlcmVuY2VzPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjEzLjEuICBOb3JtYXRpdmUgUmVmZXJlbmNlczwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmlnaHQiPjEzLjEuICBOb3JtYXRpdmUgUmVmZXJlbmNlczwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBbSS1ELmlldGYtY2FsZXh0LWV2ZW50cHViLWV4
dGVuc2lvbnNdPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgW0ktRC5pZXRm
LWNhbGV4dC1ldmVudHB1Yi1leHRlbnNpb25zXTwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgICAgICAgICAgICBEb3VnbGFzcywgTS4sICJFdmVudCBQdWJsaXNoaW5nIEV4
dGVuc2lvbnMgdG8gaUNhbGVuZGFyIiw8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICAgICAgICAgICAgIERvdWdsYXNzLCBNLiwgIkV2ZW50IFB1Ymxpc2hpbmcgRXh0ZW5z
aW9ucyB0byBpQ2FsZW5kYXIiLDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyIGlkPSJkaWZmMDAzOSI+PHRkPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj4gICAgICAgICAgICAgIDxz
cGFuIGNsYXNzPSJkZWxldGUiPmRyYWZ0LWlldGYtY2FsZXh0LWV2ZW50cHViLWV4dGVuc2lv
bnMtMTY8L3NwYW4+ICh3b3JrIGluPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2si
PiAgICAgICAgICAgICAgPHNwYW4gY2xhc3M9Imluc2VydCI+ZHJhZnQtaWV0Zi1jYWxleHQt
ZXZlbnRwdWItZXh0ZW5zaW9ucy0xODwvc3Bhbj4gKHdvcmsgaW48L3RkPjx0ZCBjbGFzcz0i
bGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48
dGQgY2xhc3M9ImxibG9jayI+ICAgICAgICAgICAgICBwcm9ncmVzcyksIDxzcGFuIGNsYXNz
PSJkZWxldGUiPk9jdG9iZXIgMjAyMC48L3NwYW4+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNz
PSJyYmxvY2siPiAgICAgICAgICAgICAgcHJvZ3Jlc3MpLCA8c3BhbiBjbGFzcz0iaW5zZXJ0
Ij5KYW51YXJ5IDIwMjEuPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNs
YXNzPSJsZWZ0Ij4gICBbUkZDMjExOV0gIEJyYWRuZXIsIFMuLCAiS2V5IHdvcmRzIGZvciB1
c2UgaW4gUkZDcyB0byBJbmRpY2F0ZTwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PiAgIFtSRkMyMTE5XSAgQnJhZG5lciwgUy4sICJLZXkgd29yZHMgZm9yIHVzZSBpbiBSRkNz
IHRvIEluZGljYXRlPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAg
ICAgIFJlcXVpcmVtZW50IExldmVscyIsIEJDUCAxNCwgUkZDIDIxMTksPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICBSZXF1aXJlbWVudCBMZXZlbHMi
LCBCQ1AgMTQsIFJGQyAyMTE5LDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAg
ICAgICAgICAgICBET0kgMTAuMTc0ODcvUkZDMjExOSwgTWFyY2ggMTk5Nyw8L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgIERPSSAxMC4xNzQ4Ny9SRkMy
MTE5LCBNYXJjaCAxOTk3LDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAg
ICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgICAg
ICAgICAgICAmbHQ7aHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvaW5mby9yZmMyMTE5Jmd0
Oy48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgICAgICAgICZsdDto
dHRwczovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzIxMTkmZ3Q7LjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICBbUkZDNDc5MV0gIERhYm9vLCBD
LiwgRGVzcnVpc3NlYXV4LCBCLiwgYW5kIEwuIER1c3NlYXVsdCw8L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICBbUkZDNDc5MV0gIERhYm9vLCBDLiwgRGVzcnVpc3NlYXV4
LCBCLiwgYW5kIEwuIER1c3NlYXVsdCw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgICAgICAgICAgICAgIkNhbGVuZGFyaW5nIEV4dGVuc2lvbnMgdG8gV2ViREFWIChDYWxE
QVYpIiwgUkZDIDQ3OTEsPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAg
ICAgICAgICAiQ2FsZW5kYXJpbmcgRXh0ZW5zaW9ucyB0byBXZWJEQVYgKENhbERBVikiLCBS
RkMgNDc5MSw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAg
RE9JIDEwLjE3NDg3L1JGQzQ3OTEsIE1hcmNoIDIwMDcsPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgICAgICAgICAgICBET0kgMTAuMTc0ODcvUkZDNDc5MSwgTWFyY2gg
MjAwNyw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQg
Y2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgJmx0
O2h0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjNDc5MSZndDsuPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAmbHQ7aHR0cHM6Ly93d3cu
cmZjLWVkaXRvci5vcmcvaW5mby9yZmM0NzkxJmd0Oy48L3RkPjx0ZCBjbGFzcz0ibGluZW5v
Ij48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xh
c3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJwYXJ0LTEzIiBjbGFzcz0i
Y2hhbmdlIj48dGQ+PC90ZD48dGg+PHNtYWxsPnNraXBwaW5nIHRvIGNoYW5nZSBhdDwvc21h
bGw+PGEgaHJlZj0iI3BhcnQtMTMiPjxlbT4gcGFnZSAxNCwgbGluZSA1PHNwYW4gY2xhc3M9
ImhpZGUiPiDCtjwvc3Bhbj48L2VtPjwvYT48L3RoPjx0aD4gPC90aD48dGg+PHNtYWxsPnNr
aXBwaW5nIHRvIGNoYW5nZSBhdDwvc21hbGw+PGEgaHJlZj0iI3BhcnQtMTMiPjxlbT4gcGFn
ZSAxNCwgbGluZSAyMTxzcGFuIGNsYXNzPSJoaWRlIj4gwrY8L3NwYW4+PC9lbT48L2E+PC90
aD48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRk
IGNsYXNzPSJsZWZ0Ij4gICBbQlRjb3JlXSAgIEJsdWV0b290aCBTcGVjaWFsIEludGVyZXN0
IEdyb3VwLCAiQmx1ZXRvb3RoIENvcmU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0
Ij4gICBbQlRjb3JlXSAgIEJsdWV0b290aCBTcGVjaWFsIEludGVyZXN0IEdyb3VwLCAiQmx1
ZXRvb3RoIENvcmU8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAg
ICAgU3BlY2lmaWNhdGlvbiBWZXJzaW9uIDUuMCIsIERlY2VtYmVyIDIwMTYsPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICBTcGVjaWZpY2F0aW9uIFZl
cnNpb24gNS4wIiwgRGVjZW1iZXIgMjAxNiw8L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3Rk
PjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9Imxl
ZnQiPiAgICAgICAgICAgICAgJmx0O2h0dHBzOi8vd3d3LmJsdWV0b290aC5jb20vc3BlY2lm
aWNhdGlvbnMvYmx1ZXRvb3RoLWNvcmUtPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdo
dCI+ICAgICAgICAgICAgICAmbHQ7aHR0cHM6Ly93d3cuYmx1ZXRvb3RoLmNvbS9zcGVjaWZp
Y2F0aW9ucy9ibHVldG9vdGgtY29yZS08L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgICAgICAgICAgICAgc3BlY2lmaWNhdGlvbiZndDsuPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyaWdodCI+ICAgICAgICAgICAgICBzcGVjaWZpY2F0aW9uJmd0Oy48L3RkPjx0ZCBj
bGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+
PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQi
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+ICAgW1JGQzU1NDZdICBEYWJvbywg
Qy4sIEVkLiwgImlDYWxlbmRhciBUcmFuc3BvcnQtSW5kZXBlbmRlbnQ8L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBbUkZDNTU0Nl0gIERhYm9vLCBDLiwgRWQuLCAiaUNh
bGVuZGFyIFRyYW5zcG9ydC1JbmRlcGVuZGVudDwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+ICAgICAgICAgICAgICBJbnRlcm9wZXJhYmlsaXR5IFByb3RvY29sIChpVElQKSIs
IFJGQyA1NTQ2LDwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAgICAgICAgICAg
ICAgSW50ZXJvcGVyYWJpbGl0eSBQcm90b2NvbCAoaVRJUCkiLCBSRkMgNTU0Niw8L3RkPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVu
byI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgRE9JIDEwLjE3NDg3L1JG
QzU1NDYsIERlY2VtYmVyIDIwMDksPC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+
ICAgICAgICAgICAgICBET0kgMTAuMTc0ODcvUkZDNTU0NiwgRGVjZW1iZXIgMjAwOSw8L3Rk
Pjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0cj48dGQgY2xhc3M9Imxp
bmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgICAgICAgICAgICAgJmx0O2h0dHBzOi8v
d3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjNTU0NiZndDsuPC90ZD48dGQ+IDwvdGQ+PHRk
IGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgICAmbHQ7aHR0cHM6Ly93d3cucmZjLWVkaXRv
ci5vcmcvaW5mby9yZmM1NTQ2Jmd0Oy48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyIGlkPSJkaWZmMDA0MCI+PHRkPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48
c3BhbiBjbGFzcz0iZGVsZXRlIj4xMy4zLiAgVVJJczwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJibG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgog
ICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxz
cGFuIGNsYXNzPSJkZWxldGUiPjwvc3Bhbj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJi
bG9jayI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRk
IGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjxzcGFuIGNsYXNzPSJk
ZWxldGUiPiAgIFsxXSBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvYmNwMTQ8L3NwYW4+
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBj
bGFzcz0ibGJsb2NrIj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgPC90ZD48dGQ+IDwvdGQ+PHRkIGNs
YXNzPSJyYmxvY2siPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAg
PHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+QXBwZW5kaXgg
QS4gIENoYW5nZSBIaXN0b3J5IChUbyBiZSByZW1vdmVkIGJ5IFJGQyBFZGl0b3IgYmVmb3Jl
PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+QXBwZW5kaXggQS4gIENoYW5nZSBI
aXN0b3J5IChUbyBiZSByZW1vdmVkIGJ5IFJGQyBFZGl0b3IgYmVmb3JlPC90ZD48dGQgY2xh
c3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgICAgICAgcHVibGljYXRpb24pPC90ZD48dGQ+
IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgICAgICAgICAgIHB1YmxpY2F0aW9uKTwvdGQ+
PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGlu
ZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHIgaWQ9
ImRpZmYwMDQxIj48dGQ+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8i
PjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmJs
b2NrIj4gICA8c3BhbiBjbGFzcz0iaW5zZXJ0Ij5DaGFuZ2VzIGluIGlldGYtMDM6PC9zcGFu
PjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFz
cz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQg
Y2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+PC9zcGFuPjwvdGQ+PHRkIGNs
YXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48
L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9j
ayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgMS4gIEZpeGVkIEFCTkYgdG8gYmUgcHJvcGVy
bHkgZXh0ZW5kZWQuPC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4K
ICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48
L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+
PC9zcGFuPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90cj4KICAgICAgPHRyPjx0
ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGJsb2NrIj48L3RkPjx0ZD4gPC90
ZD48dGQgY2xhc3M9InJibG9jayI+PHNwYW4gY2xhc3M9Imluc2VydCI+ICAgMi4gIEFkZHJl
c3NlZCBBRCByZXZpZXcgY29tbWVudHMgZnJvbSBCYXJyeSBMZWliYS48L3NwYW4+PC90ZD48
dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5l
bm8iPjwvdGQ+PHRkIGNsYXNzPSJsYmxvY2siPjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0i
cmJsb2NrIj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90
ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJs
ZWZ0Ij4gICBDaGFuZ2VzIGluIGlldGYtMDI6PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJy
aWdodCI+ICAgQ2hhbmdlcyBpbiBpZXRmLTAyOjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwv
dGQ+PC90cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0i
bGVmdCI+PC90ZD48dGQ+IDwvdGQ+PHRkIGNsYXNzPSJyaWdodCI+PC90ZD48dGQgY2xhc3M9
ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+
PHRkIGNsYXNzPSJsZWZ0Ij4gICAxLiAgQWRkcmVzc2VkIHNvbWUgV0dMQyBjb21tZW50cyBm
cm9tIERhbmllbCBNaWdhdWx0LjwvdGQ+PHRkPiA8L3RkPjx0ZCBjbGFzcz0icmlnaHQiPiAg
IDEuICBBZGRyZXNzZWQgc29tZSBXR0xDIGNvbW1lbnRzIGZyb20gRGFuaWVsIE1pZ2F1bHQu
PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8dHI+PHRkIGNsYXNz
PSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xh
c3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPiAgIENoYW5nZXMg
aW4gaWV0Zi0wMTo8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICBDaGFuZ2Vz
IGluIGlldGYtMDE6PC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4g
PC90ZD48dGQgY2xhc3M9InJpZ2h0Ij48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwv
dHI+CiAgICAgIDx0cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQi
PiAgIDEuICBSZWludHJvZHVjZWQgdGhlIFJFTEFURUQtVE8gcHJvcGVydHkgZm9yIFZBTEFS
TXMgYW5kIHRoZSBTTk9PWkU8L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJpZ2h0Ij4gICAx
LiAgUmVpbnRyb2R1Y2VkIHRoZSBSRUxBVEVELVRPIHByb3BlcnR5IGZvciBWQUxBUk1zIGFu
ZCB0aGUgU05PT1pFPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgogICAgICA8
dHI+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij4gICAgICAgdmFs
dWUgZm9yIHRoZSBSRUxUWVBFIHByb3BlcnR5IHBhcmFtZXRlci48L3RkPjx0ZD4gPC90ZD48
dGQgY2xhc3M9InJpZ2h0Ij4gICAgICAgdmFsdWUgZm9yIHRoZSBSRUxUWVBFIHByb3BlcnR5
IHBhcmFtZXRlci48L3RkPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjwvdHI+CiAgICAgIDx0
cj48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48dGQgY2xhc3M9ImxlZnQiPjwvdGQ+PHRkPiA8
L3RkPjx0ZCBjbGFzcz0icmlnaHQiPjwvdGQ+PHRkIGNsYXNzPSJsaW5lbm8iPjwvdGQ+PC90
cj4KICAgICAgPHRyPjx0ZCBjbGFzcz0ibGluZW5vIj48L3RkPjx0ZCBjbGFzcz0ibGVmdCI+
ICAgMi4gIEFkZCBQcml2YWN5IENvbnNpZGVyYXRpb25zIHNlY3Rpb24uPC90ZD48dGQ+IDwv
dGQ+PHRkIGNsYXNzPSJyaWdodCI+ICAgMi4gIEFkZCBQcml2YWN5IENvbnNpZGVyYXRpb25z
IHNlY3Rpb24uPC90ZD48dGQgY2xhc3M9ImxpbmVubyI+PC90ZD48L3RyPgoKICAgICA8dHI+
PHRkPjwvdGQ+PHRkIGNsYXNzPSJsZWZ0Ij48L3RkPjx0ZD4gPC90ZD48dGQgY2xhc3M9InJp
Z2h0Ij48L3RkPjx0ZD48L3RkPjwvdHI+CiAgICAgPHRyIGlkPSJlbmQiIGJnY29sb3I9Imdy
YXkiPjx0aCBjb2xzcGFuPSI1IiBhbGlnbj0iY2VudGVyIj4mbmJzcDtFbmQgb2YgY2hhbmdl
cy4gNDEgY2hhbmdlIGJsb2Nrcy4mbmJzcDs8L3RoPjwvdHI+CiAgICAgPHRyIGNsYXNzPSJz
dGF0cyI+PHRkPjwvdGQ+PHRoPjxpPjU4IGxpbmVzIGNoYW5nZWQgb3IgZGVsZXRlZDwvaT48
L3RoPjx0aD48aT4gPC9pPjwvdGg+PHRoPjxpPjY2IGxpbmVzIGNoYW5nZWQgb3IgYWRkZWQ8
L2k+PC90aD48dGQ+PC90ZD48L3RyPgogICAgIDx0cj48dGQgY29sc3Bhbj0iNSIgY2xhc3M9
InNtYWxsIiBhbGlnbj0iY2VudGVyIj48YnI+VGhpcyBodG1sIGRpZmYgd2FzIHByb2R1Y2Vk
IGJ5IHJmY2RpZmYgMS40OC4gVGhlIGxhdGVzdCB2ZXJzaW9uIGlzIGF2YWlsYWJsZSBmcm9t
IDxhIGhyZWY9Imh0dHA6Ly93d3cudG9vbHMuaWV0Zi5vcmcvdG9vbHMvcmZjZGlmZi8iPmh0
dHA6Ly90b29scy5pZXRmLm9yZy90b29scy9yZmNkaWZmLzwvYT4gPC90ZD48L3RyPgogICA8
L3Rib2R5PjwvdGFibGU+CiAgIAogICAKPC9ib2R5PjwvaHRtbD4=
--------------C1B5D40F3F0ABD477ED893F0--


From nobody Fri Jan 29 12:08:55 2021
Return-Path: <mikeadouglass@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE9293A128F for <calsify@ietfa.amsl.com>; Fri, 29 Jan 2021 12:08:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E0XmHJtJdPe6 for <calsify@ietfa.amsl.com>; Fri, 29 Jan 2021 12:08:52 -0800 (PST)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 224A73A1274 for <calsify@ietf.org>; Fri, 29 Jan 2021 12:08:52 -0800 (PST)
Received: by mail-qt1-x835.google.com with SMTP id z22so7624992qto.7 for <calsify@ietf.org>; Fri, 29 Jan 2021 12:08:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=TfUtn6kixcihQwzSX6UT0oyEPmfLn0PUZocRGIS8APo=; b=s0UAhnq1Nmr4T4mViBK8dzpZfYAxQVj78scIsUFGhDKPmeMs6/GnSYzbov9ahqYvNf jyalLjM3hF71J9S84NjgOV6p2zKfwgINN+Z3VPw+Cs9FJsH8bNUKINB0ylXzz6V26KV+ bE5I/TJ4Qf7hnLC76xIkx3+e7dk8gWRRiN9CSno/j/wxr1C8BhOXkF1xVFhel5+8fSIw ybp/fH6MYmIOxIl+cgSAE+70lyaaEZ4nIWjuU1rH2JBt3SDf4ADo7JMHqNzHXilTfEPU FyhjvMGRWvopvEE+YkfkUfXv4szYs6GdH+3I2kopC8qAw5XQxVud1Crj8ftfWbnf2sR1 qKuA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=TfUtn6kixcihQwzSX6UT0oyEPmfLn0PUZocRGIS8APo=; b=RLEPC70aOvLpOH2wZYg4KtqGTkxtWfK0bdqVw9zJFyWU5tlNxkXj+7DU7Jm6Xl2nTY Imd0anAwkIFUuKLNK3CMq+7ckOprpe0ATVmzTFvR9TnP5wGT9LVp7fgjO7oHyDhtTD2+ SfQP3VQNBQyPnw1xventIBUGN6NLYzHhNOMWaPl/LECuKhv8y0nAcV8E+Nexb7zrKW5/ 7zU3R26NmgeRi+1YA96eWaoM6xGIIUNEXpOaD9GFi7yjfn9G4F8MesUdQDlf7wAVCmwt KMJns/fi1G7IwsX3PNtdHL83oXKgmjrTuqbTeO0T/ZnJ50dvYquIr3qkY2mROYUSWz8C vAVQ==
X-Gm-Message-State: AOAM532nrQIt+3vgYPQA0OwddoJZltwH03uIJdBb9hx8nzkFzjC+58cf YkgvyygzV9YGUe9Y+4D9F2MXOq7G31k=
X-Google-Smtp-Source: ABdhPJx8/4PqnZbBxQS55hTn3hSEVFa+WAQbzptGqOK0MBLrBSvg7aZrmoTRJKZVD7SPutVva35DYw==
X-Received: by 2002:ac8:5a48:: with SMTP id o8mr5703293qta.196.1611950930915;  Fri, 29 Jan 2021 12:08:50 -0800 (PST)
Received: from [192.168.1.151] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id z30sm6436039qtd.21.2021.01.29.12.08.48 for <calsify@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 29 Jan 2021 12:08:48 -0800 (PST)
To: calsify@ietf.org
References: <6b55aa41-0153-3335-d053-f8bf084a2938@fastmail.com> <a5ba5dea-7f86-4231-aa0f-31f82d82a6d9@cyrus.local> <aef47d99-431e-e683-e012-974c321f9569@fastmail.com>
From: Michael Douglass <mikeadouglass@gmail.com>
Message-ID: <f6857eac-79cc-b3ae-5be5-448ff4ac0a2d@gmail.com>
Date: Fri, 29 Jan 2021 15:08:46 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <aef47d99-431e-e683-e012-974c321f9569@fastmail.com>
Content-Type: multipart/alternative; boundary="------------ECFFC93F35F756EDFC2C5F06"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/OA9J9q8kAGOKUESV-z8pO1dr5Pw>
Subject: Re: [calsify] AD review of draft-ietf-calext-valarm-extensions-03
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2021 20:08:54 -0000

This is a multi-part message in MIME format.
--------------ECFFC93F35F756EDFC2C5F06
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

One thought that comes to mind is that the abnf is pretty much unusable 
for anything other than descriptive purposes while it's spread across 
multiple documents.

If we want something that's truly usable by software - first it needs to 
cover all the cases - e.g. unordered lists - and we also should have an 
up to date complete abnf maintained as an external artifact - much as 
other bodies provide xml schemas.

It would be interesting to know if it's even possible to build a parser 
that reads abnf and then successfully parses any valid icalendar data

On 1/29/21 14:11, Ken Murchison wrote:
>
> On 1/29/21 2:00 PM, Cyrus Daboo wrote:
>> Hi Ken,
>>
>> --On Fri, 29 Jan 2021 13:01:39 -0500 Ken Murchison 
>> <murch@fastmail.com> wrote:
>>
>>
>>>> I read the above as zero or more 'x' and/or 'y'  OR zero or more 
>>>> 'z'.   I
>>>> don't see how https://tools.ietf.org/html/rfc5234#section-3.2
>>>> <https://tools.ietf.org/html/rfc5234#section-3.2> would allow 
>>>> having  'x'
>>>> and 'z' together.
>>>
>>>
>>> To continue my thought. Given:
>>>
>>> a = *(x /y) / *(z)
>>>
>>> *a would equate to: *(x / y / z)
>>>
>>
>> Yeah, OK. I guess I got it wrong in 7986 then :-(
>
>
> We all got it wrong, since it passed review without being caught.
>
> Anyhow, attached are my proposed changes per Barry's review and our 
> ABNF discussion.
>
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify

--------------ECFFC93F35F756EDFC2C5F06
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>One thought that comes to mind is that the abnf is pretty much
      unusable for anything other than descriptive purposes while it's
      spread across multiple documents.</p>
    <p>If we want something that's truly usable by software - first it
      needs to cover all the cases - e.g. unordered lists - and we also
      should have an up to date complete abnf maintained as an external
      artifact - much as other bodies provide xml schemas.</p>
    <p>It would be interesting to know if it's even possible to build a
      parser that reads abnf and then successfully parses any valid
      icalendar data <br>
    </p>
    <div class="moz-cite-prefix">On 1/29/21 14:11, Ken Murchison wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:aef47d99-431e-e683-e012-974c321f9569@fastmail.com">
      <br>
      On 1/29/21 2:00 PM, Cyrus Daboo wrote:
      <br>
      <blockquote type="cite">Hi Ken,
        <br>
        <br>
        --On Fri, 29 Jan 2021 13:01:39 -0500 Ken Murchison
        <a class="moz-txt-link-rfc2396E" href="mailto:murch@fastmail.com">&lt;murch@fastmail.com&gt;</a> wrote:
        <br>
        <br>
        <br>
        <blockquote type="cite">
          <blockquote type="cite">I read the above as zero or more 'x'
            and/or 'y'  OR zero or more 'z'.   I
            <br>
            don't see how
            <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/rfc5234#section-3.2">https://tools.ietf.org/html/rfc5234#section-3.2</a>
            <br>
            <a class="moz-txt-link-rfc2396E" href="https://tools.ietf.org/html/rfc5234#section-3.2">&lt;https://tools.ietf.org/html/rfc5234#section-3.2&gt;</a>
            would allow having  'x'
            <br>
            and 'z' together.
            <br>
          </blockquote>
          <br>
          <br>
          To continue my thought. Given:
          <br>
          <br>
          a = *(x /y) / *(z)
          <br>
          <br>
          *a would equate to: *(x / y / z)
          <br>
          <br>
        </blockquote>
        <br>
        Yeah, OK. I guess I got it wrong in 7986 then :-(
        <br>
      </blockquote>
      <br>
      <br>
      We all got it wrong, since it passed review without being caught.
      <br>
      <br>
      Anyhow, attached are my proposed changes per Barry's review and
      our ABNF discussion.
      <br>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
calsify mailing list
<a class="moz-txt-link-abbreviated" href="mailto:calsify@ietf.org">calsify@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/calsify">https://www.ietf.org/mailman/listinfo/calsify</a>
</pre>
    </blockquote>
  </body>
</html>

--------------ECFFC93F35F756EDFC2C5F06--

