[Ace] FW: The ACE WG has placed draft-boucadair-dots-server-discovery in state "Call For Adoption By WG Issued"

2018-11-30 Thread Roman Danyliw
This document state change is an error on my part.  I selected the wrong WG in 
the datatracker interface.  ACE is NOT considering this draft for adoption!

Regards,
Roman

-Original Message-
From: IETF Secretariat [mailto:ietf-secretariat-re...@ietf.org] 
Sent: Friday, November 30, 2018 5:25 PM
To: ace-cha...@ietf.org; draft-boucadair-dots-server-discov...@ietf.org; 
ace@ietf.org
Subject: The ACE WG has placed draft-boucadair-dots-server-discovery in state 
"Call For Adoption By WG Issued"


The ACE WG has placed draft-boucadair-dots-server-discovery in state Call For 
Adoption By WG Issued (entered by Roman Danyliw)

The document is available at
https://datatracker.ietf.org/doc/draft-boucadair-dots-server-discovery/

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace


[Ace] The ACE WG has placed draft-boucadair-dots-server-discovery in state "Call For Adoption By WG Issued"

2018-11-30 Thread IETF Secretariat


The ACE WG has placed draft-boucadair-dots-server-discovery in state
Call For Adoption By WG Issued (entered by Roman Danyliw)

The document is available at
https://datatracker.ietf.org/doc/draft-boucadair-dots-server-discovery/

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace


[Ace] The ACE WG has placed draft-tiloca-ace-oscoap-joining in state "Call For Adoption By WG Issued"

2018-11-30 Thread IETF Secretariat


The ACE WG has placed draft-tiloca-ace-oscoap-joining in state
Call For Adoption By WG Issued (entered by Roman Danyliw)

The document is available at
https://datatracker.ietf.org/doc/draft-tiloca-ace-oscoap-joining/

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace


[Ace] The ACE WG has placed draft-palombini-ace-key-groupcomm in state "Call For Adoption By WG Issued"

2018-11-30 Thread IETF Secretariat


The ACE WG has placed draft-palombini-ace-key-groupcomm in state
Call For Adoption By WG Issued (entered by Roman Danyliw)

The document is available at
https://datatracker.ietf.org/doc/draft-palombini-ace-key-groupcomm/

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace


[Ace] Call for adoption of draft-tiloca-ace-oscoap-joining

2018-11-30 Thread Roman Danyliw
Hello!

This is the start of a two week call for input on the WG adoption of the 
document:

draft-tiloca-ace-oscoap-joining
https://tools.ietf.org/html/draft-tiloca-ace-oscoap-joining-05

The document has been presented and discussed at the last few meetings; and 
revisions have been made based on WG feedback.  At the IETF 103 meeting, there 
was support for adoption; and volunteers to review and implement the draft. 

Please provide feedback to the list/chairs if you believe that this document 
should be adopted as a WG document.The adoption call will end on December 
14 2018.

Regards,
Roman and Jim

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace


[Ace] Call for adoption of draft-palombini-ace-key-groupcomm

2018-11-30 Thread Roman Danyliw
Hello!

This is the start of a two week call for input on the WG adoption of the 
document:

draft-palombini-ace-key-groupcomm
https://tools.ietf.org/html/draft-palombini-ace-key-groupcomm-02

The document has been presented and discussed at the last few meetings; and 
revisions have been made based on WG feedback.  At the IETF 103 meeting, there 
was support for adoption; and volunteers to review and implement the draft. 

Please provide feedback to the list/chairs if you believe that this document 
should be adopted as a WG document.The adoption call will end on December 
14 2018.

Regards,
Roman and Jim

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace


Re: [Ace] Idnits on draft-ietf-ace-cwt-proof-of-possession-05

2018-11-30 Thread Carsten Bormann
On Nov 30, 2018, at 17:50, Roman Danyliw  wrote:
> 
> /protected header / h’A1010A' /{ \alg\ 1:10 \AES-CCM-16-64-128\}/,

You may want to switch to the << … >> form:

> /protected header / << { /alg/ 1: 10 /AES-CCM-16-64-128/ } >>,

Grüße, Carsten

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace


Re: [Ace] Syntax check of examples in draft-ietf-ace-cwt-proof-of-possession-05

2018-11-30 Thread Mike Jones
Thanks - we'll address that as well.

-- Mike

-Original Message-
From: Ace  On Behalf Of Roman Danyliw
Sent: Friday, November 30, 2018 11:10 AM
To: ace@ietf.org
Subject: [Ace] Syntax check of examples in 
draft-ietf-ace-cwt-proof-of-possession-05

Hello!

As part of my shepherd review, I ran all of the examples in 
draft-ietf-ace-cwt-proof-of-possession-05 through a CBOR diagnostic-to-CBOR 
validator (thanks Carsten for cbor.me).  All of the examples were fine but the 
first one in Section 3.3:

--[current text]--
 {
  /kty/ 1 : /Symmetric/ 4,
  /alg/ 3 : /HMAC256/ 5,
  /k/ -1 : h'6684523ab17337f173500e5728c628547cb37df
 e68449c65f885d1b73b49eae1A0B0C0D0E0F10'
 }
--[end]--

The error was:

Expected one of [ \t\n\r], "/", [0-9a-fA-F] at line 5, column 56 (byte 184) 
after { /kty/ 1 : /Symmetric/ 4, /alg/ 3 : /HMAC256/ 5, /k/ -1 : 
h'6684523ab17337f173500e5728c628547cb37df e68449c65f885d1b73b49eae1A0B0C0D0E0F10

It appears that the string of hex encoded octets in /k/ is short one character.

Roman 

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace


Re: [Ace] Idnits on draft-ietf-ace-cwt-proof-of-possession-05

2018-11-30 Thread Mike Jones
Will do...

-Original Message-
From: Ace  On Behalf Of Roman Danyliw
Sent: Friday, November 30, 2018 8:50 AM
To: ace@ietf.org
Subject: [Ace] Idnits on draft-ietf-ace-cwt-proof-of-possession-05

Hi!

As part of the shepherd review, I ran idnits on 
draft-ietf-ace-cwt-proof-of-possession-05.  The following nits were found.  
Could these please be fixed in a revised draft.

--[ snip ]--  

  Checking nits according to https://www.ietf.org/id-info/checklist :
  

  ** There is 1 instance of too long lines in the document, the longest one
 being 1 character in excess of 72.

Checking references for intended status: Proposed Standard
  

  ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126)

  == Outdated reference: A later version (-17) exists of
 draft-ietf-ace-oauth-authz-16

  -- Obsolete informational reference (is this intentional?): RFC 7159
 (Obsoleted by RFC 8259)


 Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--).

--[ snip ]--

The line which exceeds 72 characters is in Section 3.4.  Specifically:

 /protected header / h'A1010A' /{ \alg\ 1:10 \AES-CCM-16-64-128\}/,

Regards,
Roman

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace


[Ace] Syntax check of examples in draft-ietf-ace-cwt-proof-of-possession-05

2018-11-30 Thread Roman Danyliw
Hello!

As part of my shepherd review, I ran all of the examples in 
draft-ietf-ace-cwt-proof-of-possession-05 through a CBOR diagnostic-to-CBOR 
validator (thanks Carsten for cbor.me).  All of the examples were fine but the 
first one in Section 3.3:

--[current text]--
 {
  /kty/ 1 : /Symmetric/ 4,
  /alg/ 3 : /HMAC256/ 5,
  /k/ -1 : h'6684523ab17337f173500e5728c628547cb37df
 e68449c65f885d1b73b49eae1A0B0C0D0E0F10'
 }
--[end]--

The error was:

Expected one of [ \t\n\r], "/", [0-9a-fA-F] at line 5, column 56 (byte 184) 
after { /kty/ 1 : /Symmetric/ 4, /alg/ 3 : /HMAC256/ 5, /k/ -1 : 
h'6684523ab17337f173500e5728c628547cb37df e68449c65f885d1b73b49eae1A0B0C0D0E0F10

It appears that the string of hex encoded octets in /k/ is short one character.

Roman 

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace


Re: [Ace] IPR Conformance check for draft-ietf-ace-cwt-proof-of-possession

2018-11-30 Thread Mike Jones
Likewise, I am not aware of any IPR that pertains to this specification.

-- Mike

From: Ace  on behalf of Göran Selander 

Sent: Friday, November 30, 2018 8:50:24 AM
To: Roman Danyliw; ace@ietf.org
Subject: Re: [Ace] IPR Conformance check for 
draft-ietf-ace-cwt-proof-of-possession


Correction!

I am NOT aware of any IPR related to this draft.


(Thanks Roman for spotting the unfortunate missing words !)

Göran

> 30 nov. 2018 kl. 16:42 skrev Göran Selander :
>
>
> I aware of any IPR related to this draft.
>
> BR
> Göran
>
> On 2018-11-27, 15:44, "Ace on behalf of Roman Danyliw"  on behalf of r...@cert.org> wrote:
>
>Hello draft-ietf-ace-cwt-proof-of-possession authors,
>(Hi Mike, Ludwig, Goeran, Samuel and Hannes,)
>
>As the shepherd for draft-ietf-ace-cwt-proof-of-possession, I'd like to 
> confirm with the authors that all IPR disclosures have occurred per RFC6702:
>
>--[ shepherd questions ]--
>
>(7) Has each author confirmed that any and all appropriate IPR disclosures 
> required for full conformance with the provisions of BCP 78 and BCP 79 have 
> already been filed. If not, explain why?
>
>--[end question]--
>
>Can you please respond to the list answering this question (e.g., "As a 
> co-author, I don't hold any IPR nor am I aware of any related to this draft").
>
>Thanks,
>Roman
>
>___
>Ace mailing list
>Ace@ietf.org
>https://www.ietf.org/mailman/listinfo/ace
>
>
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace


[Ace] Idnits on draft-ietf-ace-cwt-proof-of-possession-05

2018-11-30 Thread Roman Danyliw
Hi!

As part of the shepherd review, I ran idnits on 
draft-ietf-ace-cwt-proof-of-possession-05.  The following nits were found.  
Could these please be fixed in a revised draft.

--[ snip ]--  

  Checking nits according to https://www.ietf.org/id-info/checklist :
  

  ** There is 1 instance of too long lines in the document, the longest one
 being 1 character in excess of 72.

Checking references for intended status: Proposed Standard
  

  ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126)

  == Outdated reference: A later version (-17) exists of
 draft-ietf-ace-oauth-authz-16

  -- Obsolete informational reference (is this intentional?): RFC 7159
 (Obsoleted by RFC 8259)


 Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--).

--[ snip ]--

The line which exceeds 72 characters is in Section 3.4.  Specifically:

 /protected header / h'A1010A' /{ \alg\ 1:10 \AES-CCM-16-64-128\}/,

Regards,
Roman

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace


Re: [Ace] IPR Conformance check for draft-ietf-ace-cwt-proof-of-possession

2018-11-30 Thread Göran Selander

Correction!

I am NOT aware of any IPR related to this draft. 


(Thanks Roman for spotting the unfortunate missing words !)

Göran

> 30 nov. 2018 kl. 16:42 skrev Göran Selander :
> 
> 
> I aware of any IPR related to this draft.
> 
> BR
> Göran
> 
> On 2018-11-27, 15:44, "Ace on behalf of Roman Danyliw"  on behalf of r...@cert.org> wrote:
> 
>Hello draft-ietf-ace-cwt-proof-of-possession authors,
>(Hi Mike, Ludwig, Goeran, Samuel and Hannes,)
> 
>As the shepherd for draft-ietf-ace-cwt-proof-of-possession, I'd like to 
> confirm with the authors that all IPR disclosures have occurred per RFC6702:
> 
>--[ shepherd questions ]--
> 
>(7) Has each author confirmed that any and all appropriate IPR disclosures 
> required for full conformance with the provisions of BCP 78 and BCP 79 have 
> already been filed. If not, explain why?
> 
>--[end question]--
> 
>Can you please respond to the list answering this question (e.g., "As a 
> co-author, I don't hold any IPR nor am I aware of any related to this draft").
> 
>Thanks,
>Roman
> 
>___
>Ace mailing list
>Ace@ietf.org
>https://www.ietf.org/mailman/listinfo/ace
> 
> 
> ___
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace


smime.p7s
Description: S/MIME cryptographic signature
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace


Re: [Ace] IPR Conformance check for draft-ietf-ace-cwt-proof-of-possession

2018-11-30 Thread Göran Selander

I aware of any IPR related to this draft.

BR
Göran

On 2018-11-27, 15:44, "Ace on behalf of Roman Danyliw"  wrote:

Hello draft-ietf-ace-cwt-proof-of-possession authors,
(Hi Mike, Ludwig, Goeran, Samuel and Hannes,)

As the shepherd for draft-ietf-ace-cwt-proof-of-possession, I'd like to 
confirm with the authors that all IPR disclosures have occurred per RFC6702:

--[ shepherd questions ]--

(7) Has each author confirmed that any and all appropriate IPR disclosures 
required for full conformance with the provisions of BCP 78 and BCP 79 have 
already been filed. If not, explain why?

--[end question]--

Can you please respond to the list answering this question (e.g., "As a 
co-author, I don't hold any IPR nor am I aware of any related to this draft").

Thanks,
Roman

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace


___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace