Re: [Cbor] Review draft-ietf-cbor-date-tag-01

Jim Schaad <ietf@augustcellars.com> Wed, 01 July 2020 14:28 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E9093A0C5C; Wed, 1 Jul 2020 07:28:12 -0700 (PDT)
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, HTML_MESSAGE=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 44M-ImK1YlpZ; Wed, 1 Jul 2020 07:28:10 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACD413A0C41; Wed, 1 Jul 2020 07:28:09 -0700 (PDT)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 1 Jul 2020 07:28:01 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Mike Jones' <Michael.Jones@microsoft.com>, draft-ietf-cbor-date-tag@ietf.org
CC: cbor@ietf.org
References: <DM6PR00MB06840B56C025B61B4543733BF5810@DM6PR00MB0684.namprd00.prod.outlook.com> <CH2PR00MB0679055CB2A46FDC7CFDF8E4F56C0@CH2PR00MB0679.namprd00.prod.outlook.com>, <03c801d64f44$d265ddb0$77319910$@augustcellars.com> <CH2PR00MB0679708DDDC6E04BC0D8A3E6F56C0@CH2PR00MB0679.namprd00.prod.outlook.com>
In-Reply-To: <CH2PR00MB0679708DDDC6E04BC0D8A3E6F56C0@CH2PR00MB0679.namprd00.prod.outlook.com>
Date: Wed, 01 Jul 2020 07:27:59 -0700
Message-ID: <03ff01d64fb3$d415d830$7c418890$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0400_01D64F79.27B7EA90"
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
thread-index: AQG9hUW0rmWg4KI81Ec+8sUnWhASEwN/3HsqAh4zqBwBSm0FeqjtGBng
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/gSqDLfzyaC2zGhWABw32IGJxj9w>
Subject: Re: [Cbor] Review draft-ietf-cbor-date-tag-01
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jul 2020 14:28:13 -0000

That text does not represent what I was looking for.  I was thinking of
something more along the lines of 

 

When using this data type for decision making, for examples access control,
it needs to be noted that since this does not represent a specific point in
time the results of the evaluation can differ depending upon where the
decision is made.  This can represent more than  24-hour period in total as
a different 24-hours are used in the timezone -12:00 and +12:00.

 

That text probably needs to get cleaned up and expanded but it gives the
gist of what I am looking for.  You can also look at the latest email on the
CBOR mailing list.

 

Jim

 

 

From: Mike Jones <Michael.Jones@microsoft.com> 
Sent: Tuesday, June 30, 2020 6:43 PM
To: Jim Schaad <ietf@augustcellars.com>; draft-ietf-cbor-date-tag@ietf.org
Cc: cbor@ietf.org
Subject: RE: Review draft-ietf-cbor-date-tag-01

 

I created text.

 

-- Mike

 

  _____  

From: Jim Schaad <ietf@augustcellars.com <mailto:ietf@augustcellars.com> >
Sent: Tuesday, June 30, 2020 6:13:22 PM
To: Mike Jones <Michael.Jones@microsoft.com
<mailto:Michael.Jones@microsoft.com> >; draft-ietf-cbor-date-tag@ietf.org
<mailto:draft-ietf-cbor-date-tag@ietf.org>
<draft-ietf-cbor-date-tag@ietf.org
<mailto:draft-ietf-cbor-date-tag@ietf.org> >
Cc: cbor@ietf.org <mailto:cbor@ietf.org>  <cbor@ietf.org
<mailto:cbor@ietf.org> >
Subject: [EXTERNAL] RE: Review draft-ietf-cbor-date-tag-01 

 



> -----Original Message-----
> From: Mike Jones <Michael.Jones@microsoft.com
<mailto:Michael.Jones@microsoft.com> >
> Sent: Tuesday, June 30, 2020 5:41 PM
> To: Jim Schaad <ietf@augustcellars.com <mailto:ietf@augustcellars.com> >;
draft-ietf-cbor-date-tag@ietf.org <mailto:draft-ietf-cbor-date-tag@ietf.org>

> Cc: cbor@ietf.org <mailto:cbor@ietf.org> 
> Subject: RE: Review draft-ietf-cbor-date-tag-01
> 
> Hi Jim,
> 
> I've applied these changes in
https://tools.ietf.org/html/draft-ietf-cbor-date-
> tag-02.
> 
>                                Thanks again,
>                                -- Mike
> 
> -----Original Message-----
> From: Mike Jones
> Sent: Friday, June 12, 2020 11:52 AM
> To: Jim Schaad <ietf@augustcellars.com <mailto:ietf@augustcellars.com> >;
draft-ietf-cbor-date-tag@ietf.org <mailto:draft-ietf-cbor-date-tag@ietf.org>

> Cc: cbor@ietf.org <mailto:cbor@ietf.org> 
> Subject: RE: Review draft-ietf-cbor-date-tag-01
> 
> Thanks for your review, Jim.  My replies are inline below...
> 
> Is it time to start WGLC so others also get their reviews in?  I'll note
that the
> IANA registrations have already occurred at
> https://www.iana.org/assignments/cbor-tags/cbor-tags.xhtml.
> 
> -----Original Message-----
> From: Jim Schaad <ietf@augustcellars.com <mailto:ietf@augustcellars.com> >
> Sent: Thursday, June 11, 2020 11:48 AM
> To: draft-ietf-cbor-date-tag@ietf.org
<mailto:draft-ietf-cbor-date-tag@ietf.org> 
> Cc: cbor@ietf.org <mailto:cbor@ietf.org> 
> Subject: Review draft-ietf-cbor-date-tag-01
> 
> * Is there any chance that you can upgrade to using the v3 of xml2rfc
schema?
> If not then there is not an issue as the RFC Editor will do it.
> 
> I haven't really learned all the ins and outs of the new syntax yet, so
I'd have
> more confidence with the RFC Editor doing it correctly than me.
> 
> * Introduction:  I prefer the abstract form of /date but not a time/date
without
> a time/
> 
> I agree and will make this change in the next published draft.
> 
> * While this is something that is clear to me, I got a recent comment when
I
> suggested that this be used elsewhere of, "But how does this work with
time
> zones?".  Based on that I think that there needs to be some text about why
time
> zones are not of interest here.
> 
> Agreed and will do.
> 
> * Section 3- I think that the second paragraph would be wise to
distinguish
> between a point in time and a date when looking at access control
decisions.
> 
> I understand your point in general.  Is there particular text that you'd
suggest
> that I incorporate?

No I don't have any text in mind. 

Jim

> 
> Jim
> 
>                                Thanks again,
>                                -- Mike
>