Re: [radext] AD review of draft-ietf-radext-dynamic-discovery

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Mon, 02 March 2015 16:18 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 407BA1A1B37 for <radext@ietfa.amsl.com>; Mon, 2 Mar 2015 08:18:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 spR_PtWwaGWX for <radext@ietfa.amsl.com>; Mon, 2 Mar 2015 08:17:55 -0800 (PST)
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) (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 0CE2F1A1A8D for <radext@ietf.org>; Mon, 2 Mar 2015 08:17:55 -0800 (PST)
Received: by lbiz11 with SMTP id z11so5139488lbi.3 for <radext@ietf.org>; Mon, 02 Mar 2015 08:17:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=+4lfJpQJ3Zi5RANCmMhkvJTkHol0yFkJE3AmF4DZRiQ=; b=AWPPrmK7QQPqCb/oiPQBV92k0aN2+DE2jje7X0XHOODqagq07Qgm0n7ioQAAdus3t/ 7TGMkBdFe0w34vzMgUJ9NaKJSGUV4dKtZ5ppW780QF5rVRwTrvY9VMBMr17zClQsUA6F P/iM8Jskk5KsgeSjHa2WEu7TmopvQ//6J87d+O7P/MZV6XDV0h9RTiZnn0UPlb0YT2bb YtFBO/FHBOlu+VmzmG+8PISmZJj4TbDCxMc/2/VESv9NZJ2gxzsxy4xRgI42drATn2ct FsTYpyVo/U3Jf6XNTpew3/7EQb7/3H57L4KV6jihh2ExpfqryWrOmQX6+aTAE5TfuRrM EAXQ==
MIME-Version: 1.0
X-Received: by 10.112.181.41 with SMTP id dt9mr25649996lbc.56.1425313073534; Mon, 02 Mar 2015 08:17:53 -0800 (PST)
Received: by 10.112.167.101 with HTTP; Mon, 2 Mar 2015 08:17:53 -0800 (PST)
In-Reply-To: <CAHbuEH7bH+g11etTb_P+ZJMQh=N+=zkpvg0EOm3bjmy9s0iyjw@mail.gmail.com>
References: <CAHbuEH7bH+g11etTb_P+ZJMQh=N+=zkpvg0EOm3bjmy9s0iyjw@mail.gmail.com>
Date: Mon, 02 Mar 2015 11:17:53 -0500
Message-ID: <CAHbuEH5oaBchqac0g00sF7mKuui3W95KM4PZdX=bdabTkdLNAg@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: radext@ietf.org
Content-Type: multipart/alternative; boundary="001a11c369867191aa0510508f49"
Archived-At: <http://mailarchive.ietf.org/arch/msg/radext/z9iauY0oetSA-JDaFgQtE0FRvfo>
Subject: Re: [radext] AD review of draft-ietf-radext-dynamic-discovery
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Mar 2015 16:18:01 -0000

Hi,

I haven't seen any follow up yet and would like to progress this to IETF
last call soon if possible.  My comments are mainly nits or requests to
further clarify text, so hopefully these will be easy to resolve before we
get broader reviews on the drafts where these questions are likely to arise.

Thank you,
Kathleen

On Wed, Feb 25, 2015 at 7:11 PM, Kathleen Moriarty <
kathleen.moriarty.ietf@gmail.com> wrote:

> Hello,
>
> I reviewed draft-ietf-radext-dynamic-discovery and found it to be very
> well written, and covering security and privacy considerations nicely as
> well.  Thank you for that.
>
> I just have a few nits and a question to see if some text can be further
> clarified before progressing this to last call.  I'd like to start IETF
> last call very soon if the WG is ok with that.
>
> Nits & comments:
>
> Please expand out names of DNS labels on first use (NAPTR, SRV, RR,
> etc.).  They are obvious to most of us, but are not in the list of acronyms
> that don't have to be spelled out,
> https://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt
> (If there is a *, RFC editor is okay with not expanding)
>
> Section 3.4.3
> In the algorithm, I am confused by step 12 that simply says "Proceed with
> step 18."  Are there conditions that would have you decide to skip steps
> 13-17 or is this meant to be interpreted as proceed with step 18, then go
> back to step 13?  The example later shows that you skip 13-17, but why this
> happens isn't clear to me.  Did I miss an explanation?
>
> Section 3.4.4
> First paragraph: The second sentence is super long and the last one is
> also a bit too long, can something be done to make these sentences easier
> to read?
>
> Section 3.4.5
> Second to last sentence, just a nit:
> s/control/controls/
>
> The algorithm therefore control execution time with
>    TIMER.
>
>
> Section 3.4.6
> There are some formatting issues at the start of this section, you are
> probably aware of already.
>
> Thank you.
> --
>
> Best regards,
> Kathleen
>



-- 

Best regards,
Kathleen