IETF Logo Mail Archive

Re: [Gen-art] Genart last call review of draft-ietf-6man-rfc4941bis-10

Fernando Gont <fgont@si6networks.com> Sat, 12 September 2020 08:14 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D82C3A0EFA; Sat, 12 Sep 2020 01:14:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.845
X-Spam-Level:
X-Spam-Status: No, score=-2.845 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.948, SPF_HELO_NONE=0.001, SPF_NONE=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 VVf7EH0-4hXn; Sat, 12 Sep 2020 01:14:47 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 046213A0921; Sat, 12 Sep 2020 01:14:24 -0700 (PDT)
Received: from [IPv6:2800:810:464:1088:5583:d414:95e6:ba0f] (unknown [IPv6:2800:810:464:1088:5583:d414:95e6:ba0f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 674BE2807DC; Sat, 12 Sep 2020 08:14:20 +0000 (UTC)
To: Russ Housley <housley@vigilsec.com>, gen-art@ietf.org
Cc: draft-ietf-6man-rfc4941bis.all@ietf.org, last-call@ietf.org, ipv6@ietf.org
References: <159985539023.6692.3362899198639789498@ietfa.amsl.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <a4dab342-219a-0f54-9972-623146d3a5d3@si6networks.com>
Date: Sat, 12 Sep 2020 03:00:13 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <159985539023.6692.3362899198639789498@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/6VObAhPKhYj3WSB_cW8MjcPD6YQ>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-6man-rfc4941bis-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Sep 2020 08:14:50 -0000

Hello, Russ,

Thanks a lot for your comments! In-line....

On 11/9/20 17:16, Russ Housley via Datatracker wrote:
> Reviewer: Russ Housley
> Review result: Almost Ready
[....]
> Major Concerns:
> 
> In Section 2.2, the discussion of DNS names comes out of the blue.  In
> RFC 4941, there was context for this discussion that has been dropped
> from this document.  Some context is needed.

I reared the text, but I don't find it as "coming out of the blue". I 
guess one could add something to Section 2.1 to include DNS names... 
but, at the end of the day, the name is just another identifier.

Or put another way, I'm not sure what's the "context" I would add if 
asked to.

Thoughts?



> Minor Concerns:
> 
> The Abstract says: "This document describes an extension that ...".
> It should state what protocol is being extended.  I believe this is an
> extension for SLAAC.

Will tweak to "..describes an extension to Stateless Address 
Autoconfiguration in IPv6"



> Nits:
> 
> Section 1, first paragraph says: "... in [RFC7721],[RFC7217], and
> RFC7707."  All three should be references.

Fixed.



> Section 1.1, last paragraph says: '... and not to "globally reachable"
> as defined in [RFC8190].'  I think you want to say that this term does
> not imply "globally reachable" as defined in [RFC8190].  That is, it
> might be globally reachable, but it might not.

I could tweak to "..not imply 'global reachability' as defined in..".. 
but then RFC8190 only defines "globally reachable".

May be better to tweak the original text to:
'..and not to "globally reachable" addresses, as defined...'

?


> IDnits reports:
> 
> ** The document seems to lack an IANA Considerations section.  (See Section
>     2.2 of https://www.ietf.org/id-info/checklist for how to handle the case
>     when there are no actions for IANA.)
> 
> == The 'Obsoletes: ' line in the draft header should list only the
>     _numbers_ of the RFCs which will be obsoleted by this document (if
>     approved); it should not include the word 'RFC' in the list.

Fixed.

Thanks a lot!

Regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

v2.23.0 | Report a Bug | By Email