Re: [Ace] Shepard comments draft-ietf-ace-coap-est-08

Jim Schaad <ietf@augustcellars.com> Mon, 18 February 2019 18:15 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 663EF130F6A; Mon, 18 Feb 2019 10:15:03 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 20guC-2Wuay4; Mon, 18 Feb 2019 10:15:00 -0800 (PST)
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 80000130F7B; Mon, 18 Feb 2019 10:15:00 -0800 (PST)
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; Mon, 18 Feb 2019 10:14:54 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: "'Panos Kampanakis (pkampana)'" <pkampana@cisco.com>, <draft-ietf-ace-coap-est@ietf.org>
CC: <ace@ietf.org>
References: <00fb01d4c631$94657040$bd3050c0$@augustcellars.com> <1d372f1e5d94421290646659b9c5899c@XCH-ALN-010.cisco.com>
In-Reply-To: <1d372f1e5d94421290646659b9c5899c@XCH-ALN-010.cisco.com>
Date: Mon, 18 Feb 2019 10:14:54 -0800
Message-ID: <01a501d4c7b5$daa63280$8ff29780$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHf+4kJ0/lemmBNxB2Fx5M5nQJRDgDdihWHpciIGvA=
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/LeOQ1JSamAuM9tJlwXV7Mm1fFuc>
Subject: Re: [Ace] Shepard comments draft-ietf-ace-coap-est-08
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Feb 2019 18:15:08 -0000


> -----Original Message-----
> From: Panos Kampanakis (pkampana) <pkampana@cisco.com>
> Sent: Monday, February 18, 2019 9:54 AM
> To: Jim Schaad <ietf@augustcellars.com>; draft-ietf-ace-coap-est@ietf.org
> Cc: ace@ietf.org
> Subject: RE: [Ace] Shepard comments draft-ietf-ace-coap-est-08
> 
> Hi Jim,
> 
> About
> 
> > 4.  The query in section 5.1 to a resource directory is not correct.  It
would
> not go to /.well-known/core but to /rd-lookup (or what ever name is used
by
> the RD).   If this is not intended to be an RD query, then the sentence
about it
> above can be omitted.
> 
> > 5.  Please remove the "anchor" target attribute from the response from
> the RD.  I believe that this is no longer required and it is just adding
noise
> without adding value.  If this is intended to be from well-known then it
is
> sufficient to have the anchor but not to  have the authority section in
the
> href.   </est>;rt="ace.est";anchor="coaps://2001:db8::123]:61617"
> 
> The text will now read
> ~~~~~~~~~~~
> Discoverable port numbers can be returned in the payload An example
> response payload for non-default CoAPS server port 61617 follows below.
> Linefeeds were included only for readability.
> 
>   REQ: GET /.well-known/core?rt=ace.est*
> 
>   RES: 2.05 Content
> <coap://[2001:db8:3::123]:61617/est>;rt="ace.est",
> <coap://[2001:db8:3::123]:61617/est/crts>;rt="ace.est.crts"; ct="281
> TBD287",
> <coap://[2001:db8:3::123]:61617/est/sen>;rt="ace.est.sen";ct="281 TBD287",
> <coap://[2001:db8:3::123]:61617/est/sren>;rt="ace.est.sren";ct="281
> TBD287",
<coap://[2001:db8:3::123]:61617/est/att>;rt="ace.est.att";ct="285",
> <coap://[2001:db8:3::123]:61617/est/skg>;rt="ace.est.skg";ct="62 280 284
> 281 TBD287"
> ~~~~~~~~~~~
> 
> What do you think? Does it address your two comments 4 and 5?

Yes that would be just fine.  The only possible comment is that you should
be using 'coaps' not 'coap' to say that this is a DTLS schema.

Jim

> 
> Rgs,
> Panos
> 
> -----Original Message-----
> From: Ace <ace-bounces@ietf.org> On Behalf Of Jim Schaad
> Sent: Saturday, February 16, 2019 2:56 PM
> To: draft-ietf-ace-coap-est@ietf.org
> Cc: ace@ietf.org
> Subject: [Ace] Shepard comments draft-ietf-ace-coap-est-08
> 
> 1.  In section 10.1 the last sentence of the first paragraph and the first
> sentence of the last paragraph duplicate each other.  This should be
cleaned
> up.
> 
> 2.  Correct the grammar in the first sentence of section 10.2 -
s/registers a
> new/registers new/
> 
> 3.  The correct example DNS name is est-coaps.example.org not
> est-coaps.example.ietf.org.   Please correct this.  (See RFC 2606)
> 
> 4.  The query in section 5.1 to a resource directory is not correct.  It
would not
> go to /.well-known/core but to /rd-lookup (or what ever name is
> used by the RD).   If this is not intended to be an RD query, then the
> sentence about it above can be omitted.
> 
> 5.  Please remove the "anchor" target attribute from the response from the
> RD.  I believe that this is no longer required and it is just adding noise
without
> adding value.  If this is intended to be from well-known then it is
sufficient to
> have the anchor but not to  have the authority section in the href.
> 
> </est>;rt="ace.est";anchor="coaps://2001:db8::123]:61617"
> 
> 6.  You have registered 282 and 283 as content types, however you also do
> not define anything that uses these types.  Either some text about the
> content types needs to exist or potentially the registrations should be
> abandoned.
> 
> 7.  There is an outstanding review from Klaus that needs to be addressed.
> 
> 8.  There is still an open issue dealing with content types.  I have
requested
> that this be added to the agenda for the next CoRE interim meeting.
> 
> Jim
> 
> 
> 
> _______________________________________________
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace