Re: [Ace] Genart telechat review of draft-ietf-ace-cbor-web-token-12

Hi Mike, The edits that you propose in #1 and #2 are good IMO and they would improve the clarity of the document. Concerning #3 - all the 'running code' examples that you provided are all for one type of policy only - Specification Required. The case here seems a little more complex, as the

[Ace] Agenda Items for London

Please let the chairs know if you want a slot on the agenda for London. Please give us an idea of what you think you need to cover, how long you think it will take and who is doing the presentations. For people doing the presentations, I would like to get slides during the week of March 12th so

[Ace] Adoption of draft-vanderstok-ace-est

Looking at the mailing list, it appears that the working group thinks that the document should be adopted. Peter, please republish the document as an ACE working group document and I will then approve it. Jim ___ Ace mailing list Ace@ietf.org

[Ace] ace - Requested session has been scheduled for IETF 101

Dear Benjamin Kaduk, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. ace Session 1 (2:00:00) Monday, Morning Session I 0930-1200 Room Name: Balmoral size: 250

Re: [Ace] Genart telechat review of draft-ietf-ace-cbor-web-token-12

From: Dan Romascanu [mailto:droma...@gmail.com] Sent: Tuesday, February 27, 2018 2:23 PM To: Jim Schaad Cc: Benjamin Kaduk ; gen-art ; draft-ietf-ace-cbor-web-token@ietf.org; ietf ; ace@ietf.org Subject: Re: [Ace]

Re: [Ace] Genart telechat review of draft-ietf-ace-cbor-web-token-12

Replies inline… From: Ace On Behalf Of Dan Romascanu Sent: Tuesday, February 27, 2018 2:23 PM To: Jim Schaad Cc: gen-art ; ace@ietf.org; ietf ; Benjamin Kaduk ;

Re: [Ace] Genart telechat review of draft-ietf-ace-cbor-web-token-12

I agree with Jim. This information is in the registration template at https://tools.ietf.org/html/draft-ietf-ace-cbor-web-token-12#section-9.1.1, as follows: Claim Key: CBOR map key for the claim. Integer values between -256 and 255 and strings of length 1 are designated as

Re: [Ace] Genart telechat review of draft-ietf-ace-cbor-web-token-12

Integer values between -256 and 255 and strings of length 1 are designated as Standards Track Required. Integer values from -65536 to 65535 and strings of length 2 are designated as Specification Required. Integer values of greater than 65535 and strings of length greater than 2 are

Re: [Ace] Genart telechat review of draft-ietf-ace-cbor-web-token-12

On Tue, Feb 27, 2018 at 11:59:50AM +0200, Dan Romascanu wrote: > Hi, > > See also my other notes. > > I believe that what the document tries to say is: > > Register R is divided into four different ranges R1, R2, R3, R4 (defining > the value limits may be useful) > > Values in range R1 are

Re: [Ace] Genart telechat review of draft-ietf-ace-cbor-web-token-12

Hi, See also my other notes. I believe that what the document tries to say is: Register R is divided into four different ranges R1, R2, R3, R4 (defining the value limits may be useful) Values in range R1 are allocated according to policy P1 in the case that ... Values in range R2 are allocated