Re: [v6ops] Éric Vyncke's Discuss on draft-ietf-v6ops-cpe-slaac-renum-05: (with DISCUSS and COMMENT)

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Wed, 10 February 2021 07:38 UTC

Return-Path: <evyncke@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57AD13A0D78; Tue, 9 Feb 2021 23:38:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.92
X-Spam-Level:
X-Spam-Status: No, score=-11.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=er666IBF; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=p7TfurPp
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 TC9M8kZlQi-j; Tue, 9 Feb 2021 23:38:41 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C8063A0D75; Tue, 9 Feb 2021 23:38:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10166; q=dns/txt; s=iport; t=1612942721; x=1614152321; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=yTgoPZUoH3pbZVv63Xx8QG5I0kzcH7KhF5BZkRgvfnc=; b=er666IBF+syw6vlb+RL4LWQfgi0ATdbL1xongDhissrq1d1xkWu4E8t0 gdidyqINK/nrgp71jzZOFFoI+DDCAxWaA9C3esCLBHSrKjhsK5vAJlO5v MVlbQ9iAXJjSRyXba5NXlLzMvDa4JFpJhpLB+pfYkMWedSdsaaFZ1FEsv w=;
X-IPAS-Result: A0DpAQDqiyNgmIwNJK1iHAEBAQEBAQcBARIBAQQEAQFAgU+BU1F9WjYxhEGDSAOOEgOZHIFCgREDVAsBAQENAQEnBgIEAQGESwIXgWsCJTgTAgMBAQEDAgMBAQEBBQEBAQIBBgQUAQEBAQEBAQGGNg2GQwEBAQMBIxEMAQE3AQsEAgEIDgMDAQIDAhEVAgICMBUFAwgCBAENBYJwAYJVAw4gAQ6kAgKKJXaBMoMEAQEGgTcCAQ1BgwoYghIDBoEOKoJ2gmxQR4IxHYNyJhuBQT+BESccglY+gl0CAgEBgRReKIJXNIIrgWkuLQY+JgEDGCsQFERAGFECBQoCHRqQMAg8gjxAinmJDZFGCoJ6iTaSUQMfliyMeYR7ijqEf4srkXOEWAICAgIEBQIOAQEGgWwhgVlwFTsqAYI+UBcCDY4fDA4JFIM6hRSFRXMCNQIGAQkBAQMJAXuIUweCPQEB
IronPort-PHdr: 9a23:d5CrsBMe9ryrmmjqSOsl6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEvK8z3kTIA4PW9+1DkenN9avnXD9I7ZWAtSUEd5pBH18AhN4NlgMtSMiCFQXgLfHsYiB7eaYKVFJs83yhd0QAHsH4ag7JoyO04CINHQ/8Lkx+IeGmUoLXht68gua1/ZCbag5UhT27NLV1Khj+rQjYusQMx4V4LaNkwRrSqXwOcONTlm4=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.81,167,1610409600"; d="scan'208";a="643951937"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 Feb 2021 07:38:40 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id 11A7cdHI018926 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 10 Feb 2021 07:38:40 GMT
Received: from xfe-rcd-005.cisco.com (173.37.227.253) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 10 Feb 2021 01:38:39 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xfe-rcd-005.cisco.com (173.37.227.253) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.2.792.3; Wed, 10 Feb 2021 01:38:39 -0600
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 10 Feb 2021 02:38:39 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=aBCmpekc37hjAts273ZxNOzhcStLpaAG4g3/1YZ0cKYiedwA2/He34lnJGbAQ1asejsnOIV8QO2b0lVLjT4ECcWqlliKlNeUkgDFuiC9CH6vr9fd4f4H9mTwUv3ZprEBL6I7lCrDXzOm2bTD8veWDRFM/worZ/65XOIBeHV1nC+Pwky4Sf7gxt3qq0/9baxigg/m15BiXozRcHjF1pJ7kTidYgIza31kPwc+RAlTrKGMfNSRRGr/6BK7CMt497emL2tcFrGr8wJZIVAN7XddIqAwN68cTtcI2wZsi2C+rxJpZD0C7sbpypzW0J7h6hHSRanLsztBbINHYFf57t40SQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yTgoPZUoH3pbZVv63Xx8QG5I0kzcH7KhF5BZkRgvfnc=; b=fjnoeVvW0NBGyAjl2SXP5Wgq/0XPZwxpgTz04gTIMQoVKQQg/3+d6L9i8mG741Jjr7lgR5TygpvaEJNn0uMgUHEmX7d4HTajkgYxTeyj6EQQgiiwdwtg7eivZCkCEkjf1TP88x49tjgwe1Al6bdKLYPGPL298KpCoz/1lkgwdQyCiQ9LSLwdy7zeNv+E5xIQ+b9cmjb1neeA0Yc6fMp0wD50bo+78RxRt8Os2z8RKXFLc37UpLMb3jL/xSh7ETidKLpSDj5dFxm/3bKaPVSYzO3zuNR1zspYSF0+gE9a+gC7s8WccfxUo/Bfme3pOQvIpZEkYHoFu9IAvScNMPhlww==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yTgoPZUoH3pbZVv63Xx8QG5I0kzcH7KhF5BZkRgvfnc=; b=p7TfurPpnqeBNcr779d1KolN2RaHfAvA/CDLekBJ7hvgILflvHQjVBt2UNmpZGypW8UnUdhg90JfqLDQP70pkqt79XQW+Q+dSj9WpVrxgdwcyZrtr4ZPuFtkm1ouuiraCUxKIHbipQy5+Ljdxl4oDWahBaoKxIBhRQKmBLYzjHc=
Received: from PH0PR11MB4966.namprd11.prod.outlook.com (2603:10b6:510:42::21) by PH0PR11MB4984.namprd11.prod.outlook.com (2603:10b6:510:34::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3825.24; Wed, 10 Feb 2021 07:38:38 +0000
Received: from PH0PR11MB4966.namprd11.prod.outlook.com ([fe80::7d4c:6b05:89aa:85b]) by PH0PR11MB4966.namprd11.prod.outlook.com ([fe80::7d4c:6b05:89aa:85b%3]) with mapi id 15.20.3825.030; Wed, 10 Feb 2021 07:38:38 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Fernando Gont <fgont@si6networks.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-v6ops-cpe-slaac-renum@ietf.org" <draft-ietf-v6ops-cpe-slaac-renum@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, Owen DeLong <owen@delong.com>, "suresh@kaloom.com" <suresh@kaloom.com>, "jiangsheng@huawei.com" <jiangsheng@huawei.com>
Thread-Topic: Éric Vyncke's Discuss on draft-ietf-v6ops-cpe-slaac-renum-05: (with DISCUSS and COMMENT)
Thread-Index: AQHWqGTpkc+IdJBL80CER0xOy9YU2Ko8xKmAgBT6zIA=
Date: Wed, 10 Feb 2021 07:38:38 +0000
Message-ID: <D4777F08-B56A-4A40-8D1A-427172A29FEB@cisco.com>
References: <160336543195.21161.17851078775777074492@ietfa.amsl.com> <bae28190-9537-fed0-be43-9d1e1344c9b9@si6networks.com>
In-Reply-To: <bae28190-9537-fed0-be43-9d1e1344c9b9@si6networks.com>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.45.21011103
authentication-results: si6networks.com; dkim=none (message not signed) header.d=none;si6networks.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2001:420:c0c1:36:edec:8431:3962:529]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d059c79b-9ff1-4501-cfe3-08d8cd96e154
x-ms-traffictypediagnostic: PH0PR11MB4984:
x-microsoft-antispam-prvs: <PH0PR11MB4984CE175AAB6B8F169167F0A98D9@PH0PR11MB4984.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: SNHjjQpKtW9EBzD/IZ8AA4hwRcMBkJWBH68cO9KfNSFEQDnJTwKhllltQ/SvfAuHqGnJtjcPk8Mzt/52zRkG17iUwo6ZW50LdXXXJ2jAUnlxsvqN/I9JzCzF8qVvgdGuW8n/+8L08nbdMpA+/jiz3Hd2i8bXcTDy1Wx1R11SnlTE5iwgl4B3wCi+dP3S63GP+rSSdeSs8ZYmam7gibMozJobdKdNL/o+AZ64wha7EmKieBJjCtS5izTuwRhLZhdbgkY0Q6wNeE92GDFllAwYyPeXgHC2Qu6Sk6BGtwHSvFxiY+300U0GpDAp90PYf3E6zbTiknkyHoz/NLd2mGQ7ZJ956zmluGGipaFLxfpSquJ7AaNHoFHh7gkC1xTmgVvfJXFt/IKBfJ8XpSaFcbwtQcA70jKlKFR2fklrOaAnpmIab+icveb9aF0sfVmEpbub/f4SF9uFSLKLEaB3Rht1XtSHQKFQDOqEZv2DyT6pWvUfMJtEr3qhtsmlKYAQIAU9eA6CyihEvvK1TWujhwZt9wv+nygYaVwt0ISbjlxPKL2c+LF8cmCcDPcj7KIM6Wclm10D3qe3Q1X0PlNi9tERGL3nF8v1gxQ80UOQOeKPoN6FQbVzMEgWAjnwEZaLzGvmsTXHOzESVwW91zMojR0fKg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:PH0PR11MB4966.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(396003)(376002)(346002)(366004)(136003)(39860400002)(6506007)(91956017)(53546011)(36756003)(4326008)(54906003)(316002)(110136005)(86362001)(71200400001)(66476007)(66446008)(2616005)(33656002)(478600001)(66556008)(186003)(6486002)(2906002)(966005)(66574015)(224303003)(83380400001)(5660300002)(8936002)(6512007)(4001150100001)(76116006)(64756008)(66946007)(45980500001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: +9yWwwdTxQxzjoKTS5h7hGHwtbyb5j6ZgIRbqoknTz6zc8o29KzcVkvLR12kza2rrTM+uvCjMAuopkwaRMFtmrtXt7lHykHzujadl3mRKfodOtVd7DXqdmk7loKPYuFOs2DfWHf8QuPGj2Rksy+GJaCPdyK9CObWefORgPYz0IGJIVgTFDh4+dgDi5U4xwzR7A0JoJJABSZluDNWG0Bzh7EDEq+GhAU+YQ33riD9OJSLbY4IrkmiBIIIIjjw+sfHHPGjV04sMndsJLsxvM4ZjNE9g9EcOUSnFFPTC4pojUViV6Ix/UcqVm7S5U9bFZvhj0N98dYaycxLFhw1wejNRLasRRPxoJX8MEY9gHwCdZG01JWvD0O2XdjxmlsyFcpA/4gHJpgWquc52l6r19kxqou0IMKjjGX4t5j9qbX6kUzfme6rbeC7KnCEjSVsWY180RHL5fTKoCestSftEaVbE9C+U29hnYLcVNaoeRifDPdZw4hNS6vlrqXQ3fi+yFyVai+NTxTwJ/t1TToa87JsTbGExboPIx/SValvID0nk4Y7JsrITR63g2nZrDFm+A+9JmM+NxG9hl51gJzXom1zAVHDRdhMTkfLxCCacqo108DlA63NxlDsaxXUOA2k292tBuVbj1boxwkdgotTP+2Ol4UDtpaPByqiz6AmDZNhoTddiRFbEJ/mER7dbcho5ciS1QdKFQFXLXiPED8HW7/FCqDOmem0VEGoNmgGNu4mRh7q7fEwMMG4Al7zDjZFFYSXG8Scdx11d0uSr6B3iacXfi54uIBTbnlsbCC4chvu3ysVQUra+PydcxBb4HQq+Z8h7loELKFJmkXxGBV/wwDJ8hwSmblL+O6W/pqgXK8OWUMjZhcI59dzM03koMJNt5AYp3iq6Txp3IFHUAAyC55c6IO/9Idc54BTZWdNSeg8nAYWKAqXTT+J3hF54Mnx5Yj7ZqVGVn1QL2YsRzVJ9OtarPi0QtSzs35UivOvWymrCqud2gJpcyVhOK4JHIBimUghUXqlh/cqI7RtKOXdCgt1iWPPu7Q1huJIgDTDwBM4t0rHUf5fPJawGpiitTNKkI1jK21tAQgAuXsdhKb7uLzNpoj+wA+53/DpuI+DZXnj3taTNsDCm/sjJm0MNeOPuDY65pIApkzMZi5++p3ao3MumfREP1Muc9bz3juiL2oSmNKL+JoCe5UwqeL06/scKpILxYDG4PmGejLJIzvoQLV8R/jYZxAb829p+BWt09aAZNSrhfEPgVgx8u+42+rjCyFe5p9tvdUg+PBWMicSIN+ZFrsCSvZYy+xE8o3/XdyQ4tdABMyvnQBjotnGmewwu33gCF7D3rKI2zOfCLTm+SFUdH5rvmVooi/Xf7SB/F1/yeD9/TWiwphCYHIenOAq5MIN
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <ADC4F668E5148945A01AC7EA459452BA@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: PH0PR11MB4966.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d059c79b-9ff1-4501-cfe3-08d8cd96e154
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Feb 2021 07:38:38.0462 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 1HnWneR04WCcwqtou2jPYGpbDd3XGx3VBUxt8aelaHVdb1Pbn30xExqudZXIRGjGzAo0W7XdxQdbQI4qTWtO4w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH0PR11MB4984
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: alln-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/EgciGYBoKcupMbTtZDYMvHVPsgI>
Subject: Re: [v6ops] Éric Vyncke's Discuss on draft-ietf-v6ops-cpe-slaac-renum-05: (with DISCUSS and COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2021 07:38:46 -0000

Hello Fernando,

Sorry for belated reply. See in-line for EV>

I used the published -06 (dated 11th December 2020 so after the IESG evaluation) as the basis for the discussion.  The -06 is now BCP, contains the right BCP 14 boilerplate, and a Last Call has completed, so, I will clear my DISCUSS later today (but still supporting Erik Kline's DISCUSS).

Also, I wonder whether a -07 is in preparation to better fit your comments below ?
-  Suresh Krishnan's IoT directorate review:
	https://datatracker.ietf.org/doc/review-ietf-v6ops-cpe-slaac-renum-05-iotdir-telechat-krishnan-2020-10-21/ 
- Sheng Jiang's Internet directorate review: 
	https://datatracker.ietf.org/doc/review-ietf-v6ops-cpe-slaac-renum-05-intdir-telechat-jiang-2020-10-19/ 

Finally, did the authors replied to the IoT and INT directorates reviews ?

Regards

-éric


-----Original Message-----
From: Fernando Gont <fgont@si6networks.com>
Date: Thursday, 28 January 2021 at 01:17
To: Eric Vyncke <evyncke@cisco.com>, The IESG <iesg@ietf.org>
Cc: "draft-ietf-v6ops-cpe-slaac-renum@ietf.org" <draft-ietf-v6ops-cpe-slaac-renum@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, Owen DeLong <owen@delong.com>, Suresh Krishnan <suresh@kaloom.com>, "jiangsheng@huawei.com" <jiangsheng@huawei.com>
Subject: Re: Éric Vyncke's Discuss on draft-ietf-v6ops-cpe-slaac-renum-05: (with DISCUSS and COMMENT)

    Hi, Eric,

    It seems that I somehow failed to respond to your message in time. My 
    apologies for that. IN-line....

    On 22/10/20 08:17, Éric Vyncke via Datatracker wrote:
    [...]
    > -- Abstract --
    > I wonder why the word "IPv6" is never mentioned in the abstract while the whole
    > document is about IPv6. OTOH, perhaps the default IP version in 2020 is indeed
    > IPv6 ;-)

    I've know included it :-)

EV> Looking at the -06 version, but, I guess that -07 will contain it

    > -- Section 3 --
    > Should the L-13 of RFC 7084 be also updated ? Briefly discussed in section 3.3

    Good grief. My take is that requirement L-13 is replaced with what's 
    requirement L-17 in our document.

    So, maybe in Section 3 we should say:

    "Requirement L-13 from RFC7084 is replaced with:

        o  L-13: CE routers MUST signal stale configuration information as
           specified in Section 3.3.

    And the renumber (! :-) ) our list, so the current L-18 becomes L-17?

EV> this sounds good to me (including the renumbering ;-) )

    > I wonder what is the actual structure of this section? There are 4 L-XX
    > requirements followed by 3 subsections and mapping between L-15 with section
    > 3.1 and the same for L-16, L-17 but not for L-18 ?

    That's correct. Sections 3.1-3.3 essentially spell out the details for 
    reqs L-15-17.

    There's no much more to add, but, for the sake of consistency we could 
    add a short Section 3.4 with something like:

    ---- cut here ----
    3.4. Automatic DHCPv6 RELEASEs

    Some CE Routers are known to automatically CE send DHCPv6-PD RELEASE 
    messages upon reboot events. However, this may inadvertently trigger a 
    flash-renumbering scenario, along with the associated problems discussed 
    in [draft-ietf-v6ops-slaac-renum], that this document tries to mitigate.

    As a result, L-18 specifies that CE routers SHOULD NOT automatically 
    send DHCPv6-PD RELEASE messages upon reboot events.
    ---- cut here ----

    ?

EV>  beside the spurious 'CE' in the proposed text, I support this change as it improves the readability


    > As noted in section 3.1, L-13 is actually Section 6.3 of [RFC8415] that is
    > standard track

    How about changing:
           *  The recommendations in this section expand from requirement
              L-13 in Section 4.3 of [RFC7084].

    to

           *  The recommendations in this section expand from requirement
              L-13 in Section 4.3 of [RFC7084] and Section 6.3 of [RFC8415].

    ?

EV> actually no more required IMHO with the above change about L-13

    > 
    > -- Section 3.2 --
    > There is a reference to section 2.1 of this document but the authors probably
    > meant section 3.1 of this document or Section 6.3 of [RFC8415].

    Yep. Good grief! Fixed.

EV> ;-)


    > Should the list of ND options include by default all options ? or at least
    > indicate that this is not an exhaustive list to allow for future ND options ?

    The thing is that not all options have lifetimes. (TBH, I just looked at 
    https://www.iana.org/assignments/icmpv6-parameters/icmpv6-parameters.xhtml#icmpv6-parameters-5 
    , and probably many of them wouldn't even apply).

EV> agreed but what about future options ?

    So I'd leave "as is", or add a parenthetical note right after the second 
    paragraph of Section 3.2 that says:

         NOTE:
         We note that the above text refers to the Neighbor Discovery Options
         that may typically be employed by CE Routers. A CE Router may need
         to apply the same policy for setting the lifetime of other Neighbor
         Discovery options it may employ, if and where applicable.

    ?

EV> this sounds good to me as it does not close the way for future options


    > -- Section 3.3 --
    > I agree with "IPv6 network renumbering is expected to take place in a planned
    > manner," but this sentence seems to contradict the premisses of
    > draft-ietf-v6ops-slaac-renum. Unsure how to reconciliate the two I-D (sharing
    > some authors ;-) ).

    At least in my mental model, the two documents are reconciliated as follows:

    "IPv6 network renumbering is expected to take place in a planned manner. 
    Now, welcome to the real world" :-)


EV> you can leave it like it is anyway, it is a NON blocking comment ;-)

    > " since we acknowledge " suggest to slightly rewrite this sentence to make it
    > less personal.

    Done.

EV> good

    > Suggestion to mention whether RA are sent only on received RS, multicasted
    > immediately (the document mention periodically), or unicasted when possible
    > (some CPE keeps the mapping of all its unicast client notably on the Wi-Fi
    > side).

    That's a good point. I wonder how to do it without getting into too much 
    detail that might e.g. override good possible behavior such as the one 
    you describe.

    I wonder if we should add to this sentence:
    "The aforementioned advertisement SHOULD be performed for at least the 
    "Valid Lifetime" previously employed for such prefix."

    Something like:
    "The CE Router MUST advertise this information with unsolicited Router 
    Advertisements as described in Section 6.2.4 of [RFC4861]. A CE Router 
    MAY advertise this information via unicast Router Advertisement, when 
    possible and applicable"

    My rationale is that the unsolicted RAs are the catch-all case. Whereas 
    the unicasted RAs are desirable.

    Thoughts?

EV> it works for me as it take into account unicast RA (used in some places as multicast RA are not reliable)

    Thanks!

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