Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds

"Bernie Volz (volz)" <volz@cisco.com> Fri, 01 November 2019 16:16 UTC

Return-Path: <volz@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 AC5FA1209E0 for <v6ops@ietfa.amsl.com>; Fri, 1 Nov 2019 09:16:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, 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=fko/3yOG; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=DoX7O5or
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 i244uCdWwsuN for <v6ops@ietfa.amsl.com>; Fri, 1 Nov 2019 09:16:23 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 379A41209B3 for <v6ops@ietf.org>; Fri, 1 Nov 2019 09:16:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5482; q=dns/txt; s=iport; t=1572624971; x=1573834571; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Xdy9biID5XlkNN7g0SOLqD6U6sJ8FjLc9VZlEk3Z838=; b=fko/3yOGMop/4mn8HIH6H5IgPd7sLo3qo9imI3RXlB8sMbLgWFAAET2P 9x8GUBpurRwy7uirhHgmIQTLGpxA7SejP07Ie5SwY9aNzLleqfjOKeKeM wbP6lEkG8nfaozeEOD8gHyoJlH+sStba+7Rsmm7wnD8v0SOBpjVZJ17a+ w=;
IronPort-PHdr: =?us-ascii?q?9a23=3AXSJaKxPUIPXq2S8F0OUl6mtXPHoupqn0MwgJ65?= =?us-ascii?q?Eul7NJdOG58o//OFDEuKg/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDOIdJSw?= =?us-ascii?q?dDjMwXmwI6B8vQF0r/PtbhbjcxG4JJU1o2t3w=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AJAACYWbxd/5JdJa1lGgEBAQEBAQE?= =?us-ascii?q?BAQMBAQEBEQEBAQICAQEBAYFpBQEBAQELAYFKJCwFbFggBAsqCoQeg0YDhFq?= =?us-ascii?q?GGoJef5Z9gS6BJANUCQEBAQwBARgLCgIBAYRAAheDZCQ0CQ4CAwsBAQQBAQE?= =?us-ascii?q?CAQUEbYU3DIVRAQEBAQIBAQEQEREMAQEsCwEECwIBCBgCAiMDAgICJQsUARA?= =?us-ascii?q?CBAENBSKDAAGCRgMOIAEOpz8CgTiIYHWBMoJ+AQEFgTQBg18YghcDBoEOKAG?= =?us-ascii?q?MEBiBf4ERJx+CFzU+gmIBAYFFBgIUFxWCZDKCLI0LCYJph3eWAgqCJIwviQY?= =?us-ascii?q?bmWWEV4YTg1aZVAIEAgQFAg4BAQWBUjmBWHAVOyoBgkFQERSDBgwXg1CFFIU?= =?us-ascii?q?/dIEoiwaBMAEvXgEB?=
X-IronPort-AV: E=Sophos;i="5.68,256,1569283200"; d="scan'208";a="363273850"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 01 Nov 2019 16:16:10 +0000
Received: from XCH-RCD-006.cisco.com (xch-rcd-006.cisco.com [173.37.102.16]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id xA1GGArp013258 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 1 Nov 2019 16:16:10 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-006.cisco.com (173.37.102.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 1 Nov 2019 11:16:09 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 1 Nov 2019 11:16:08 -0500
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 1 Nov 2019 11:16:08 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Df1/JomIZ3Ap0DLiJjqXJc5KKccKdvDsbtJo7k2hw7Lr1xuF3kJEZ0/VPsU7s4+YVSRnkvRRkoZ3dE5QZ94d1ac7SNvb24e30RC3bWrdwCl1doJlRgiHqMZF2LMZE5tAtZisn3m2R008QC5+78Z39eB4LEY2DCDCGmW9PGsWAnM1s+sP3eH4F6eqSGDRhw6KEu1BYfIflfnQnVjpqaeeV7MOtSa8UGSCIHLa9F5sih+NGdGeGY++Kx7pogve3TAokRRD3uFizjFyFlmDQZGvOytQ1xnGL2/f1ISuFNjreBsD1qDx3soSMBS93tGGwUy02jm2mAPCKtJYzm5iqnbqRw==
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=Xdy9biID5XlkNN7g0SOLqD6U6sJ8FjLc9VZlEk3Z838=; b=DAzghC+khKjo9zBRwo+ZwSNV00JVz1FzKzSnLmt0jqO/HmlLaIJLibCXbShS3i/3bREAUC3C4tMxhrPe8JGDtJqGA3cum0iB51THzpCiV4ZRaNtrHPtu95zK2dXdHABZ0iaNUOcPy68a/jO28zzSgBhKO/pdNoLIJ3FOqAYschAobwluIcIgn9O5udqqW7OPRVYHrR0gnxEZvonOopuhaSBExU3ADrZEeu1agvyieB/bnt76cvY3evlTwkTEINE/79u8v2IxArEZUae59Da2e4pVCDNmmvwZ6E0Ef4hnR27Nqy54/gHT0c1/inD6xnFERW9zbeOeVHukFHC5/35KVA==
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=Xdy9biID5XlkNN7g0SOLqD6U6sJ8FjLc9VZlEk3Z838=; b=DoX7O5orgCEfYuegLE8jAG1nYzsAwgWSSM65xxnok/ETq7tzrIeNI4QDi44oAEYlRsFwKX2PoxWBcdtnlYYqZjsrSNYOCGBhI/Fc57vPrQaSQgTiSbMpqo55KGgXipjz8tauCuuaAN1zXcM7VgB5PN0Ltfe4pdlcSuqrvldHcXI=
Received: from CY4PR1101MB2279.namprd11.prod.outlook.com (10.172.75.137) by CY4PR1101MB2181.namprd11.prod.outlook.com (10.174.52.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.17; Fri, 1 Nov 2019 16:16:07 +0000
Received: from CY4PR1101MB2279.namprd11.prod.outlook.com ([fe80::81f5:2724:385e:dbab]) by CY4PR1101MB2279.namprd11.prod.outlook.com ([fe80::81f5:2724:385e:dbab%10]) with mapi id 15.20.2387.030; Fri, 1 Nov 2019 16:16:07 +0000
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Owen DeLong <owen@delong.com>, Fernando Gont <fgont@si6networks.com>
CC: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] SLAAC renum: Problem Statement & Operational workarounds
Thread-Index: AQHVibwc6PRwlsH+ZUmOeFzp+XKiI6dt8FJugAA0sICAAERiAIAACLmAgAATKlOAAANjAIAGpb+AgAAD94CAAHz9AIAA0laA///HGgA=
Date: Fri, 1 Nov 2019 16:16:07 +0000
Message-ID: <B1BF35FC-852E-43C7-847D-7C62C7418E6E@cisco.com>
References: <CAO42Z2yQ_6PT3nQrXGD-mKO1bjsW6V3jZ_2kNGC2x586EMiNZg@mail.gmail.com> <B53CE471-C6E8-4DC1-8A72-C6E23154544F@fugue.com> <e67f597d-93a7-3882-3a12-69519178893d@foobar.org> <m1iOinq-0000J3C@stereo.hq.phicoh.net> <DC2F31E2-8CA4-483A-B1A1-6730A904BA32@fugue.com> <c06adfb0-1bab-d177-96e4-d1263e618000@si6networks.com> <E9C816FC-57A7-49A9-A4E3-90A3E2F38D5D@delong.com> <8f46bb68-1713-8c68-96b1-c46cf2003325@si6networks.com> <071E7287-74DD-44B9-9917-5231652F9E3D@delong.com>
In-Reply-To: <071E7287-74DD-44B9-9917-5231652F9E3D@delong.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1e.0.191013
authentication-results: spf=none (sender IP is ) smtp.mailfrom=volz@cisco.com;
x-originating-ip: [173.38.117.77]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3aefa0e9-7c45-4c7b-6a25-08d75ee6cd78
x-ms-traffictypediagnostic: CY4PR1101MB2181:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <CY4PR1101MB218133AA514049EA2552F177CF620@CY4PR1101MB2181.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 020877E0CB
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(136003)(39860400002)(396003)(376002)(346002)(189003)(199004)(53546011)(2906002)(476003)(36756003)(86362001)(14444005)(256004)(316002)(110136005)(99286004)(6246003)(91956017)(5024004)(486006)(11346002)(76116006)(2616005)(6306002)(6512007)(4326008)(66946007)(186003)(58126008)(66574012)(6116002)(446003)(229853002)(14454004)(26005)(66556008)(6436002)(8936002)(102836004)(8676002)(81156014)(64756008)(76176011)(966005)(6506007)(66446008)(71190400001)(25786009)(5660300002)(33656002)(66066001)(3846002)(6486002)(7736002)(478600001)(71200400001)(66476007)(305945005)(81166006); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR1101MB2181; H:CY4PR1101MB2279.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: o7ERC7OdYJH3t/VVPqZDIHS7gvlj4OPNEwopx/x3eHGsbY5E67Y/8lJomabSZ+ZMYztqv0O0NHQ4XtqH33X+8TPHgWqhBw3c9iGXW+msSTtHmDo3RxaTwzTpAfWx38vhp4ggoyxDFg7hJAfqLC6yDzsG6/6ehEutGUCqcbMBi9umIVLFA/U/ftGPVo/MCD2ZshS/8TbPWnfln2IictOj9x5ZR0CwKmGKXqDuIQzKYT7Y1L5SfljINC1TPmAYhU/1/c2pnmLAGEMfk6TYcPZ7LG973OV+kiPJdedv8q2K2MAqBbBww8XMYRtnDWa7FmfAArCeV07UgmwOQ2gQWF+kPEDGA6Yd0WVXoncPnIlfCvubgG+20GAGFtyXiK+znvhQ+1eH868woBfmCqWGq3CvmxQi/6td/D88PhVHmptcIniLWMsNl0qzvI265SokLqutI+htVCkRWwsYE8bYUtVhmjFDO6KeV+R1TKqFhkHe9bQ=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <0FE9AF9B2A711A47885130020FA6449D@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3aefa0e9-7c45-4c7b-6a25-08d75ee6cd78
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Nov 2019 16:16:07.7435 (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: RX3k6Z5hrjpCSY1DfDZDuCS2urLwj56sjllW0lUQ2BLslj9i8oNonLIYf140Vmm4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR1101MB2181
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.16, xch-rcd-006.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/uJQh20UyFZz8vgUnlXsWe0AqZH8>
Subject: Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds
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: Fri, 01 Nov 2019 16:16:29 -0000

>    Where is the mention of storing the expiration times?

Also, based on RFC8415 this means that the client should use a DHCPv6 Rebind when it powers back on as now it has the information to ask whether it is still valid (assuming it hasn't expired)?

See Section 18.2.18 of RFC8415:

   Whenever a client may have moved to a new link, the
   prefixes/addresses assigned to the interfaces on that link may no
   longer be appropriate for the link to which the client is attached.
   Examples of times when a client may have moved to a new link include
   the following:

   -  The client reboots (and has stable storage and persistent DHCP
      state).

   -  The client is reconnected to a link on which it has obtained
      leases.

   -  The client returns from sleep mode.

   -  The client changes access points (e.g., if using Wi-Fi
      technology).
...

   If the client has any valid delegated prefixes obtained from the DHCP
   server, the client MUST initiate a Rebind/Reply message exchange as
...


- Bernie

On 11/1/19, 11:41 AM, "v6ops on behalf of Owen DeLong" <v6ops-bounces@ietf.org on behalf of owen@delong.com> wrote:

    
    
    > On Oct 31, 2019, at 8:06 PM, Fernando Gont <fgont@si6networks.com> wrote:
    > 
    > On 31/10/19 16:39, Owen DeLong wrote:
    >> 
    >> 
    >>> On Oct 31, 2019, at 12:25 PM, Fernando Gont <fgont@si6networks.com> wrote:
    >>> 
    >>> On 27/10/19 10:54, Ted Lemon wrote:
    >>>> On Oct 27, 2019, at 9:41 AM, Philip Homburg <pch-v6ops-9@u-1.phicoh.com
    >>>> <mailto:pch-v6ops-9@u-1.phicoh.com>> wrote:
    >>>>> The little bit missing is that the CPE should write prefixes
    >>>>> advertised using
    >>>>> SLAAC to persistent storage which allows the CPE to invalidate stale
    >>>>> prefixes
    >>>>> after a reboot.
    >>>> 
    >>>> Actually I do not believe this is correct behavior.   Let us assume
    >>>> prefix delegation.   If we have prefix delegation, then when the CPE
    >>>> comes back from a power cycle, it should reconfirm the prefix it had
    >>>> previously; the assumption is that that prefix is still valid.  This can
    >>>> be handled in infrastructure—the ISP edge router should know whether the
    >>>> prefix is still valid, because if it is it should be advertising a route
    >>>> for it.   If it is not still valid, then the CPE router should attempt
    >>>> to renew it, which would go to the DHCP server (possibly both messages
    >>>> would).
    >>> 
    >>> That assues the CPE has stored the previously-leased prefix on stable
    >>> storage -- which does not need to be the case. Hence the related text in
    >>> our I-D.
    >> 
    >> IMHO, the CPE requirements should be increased and the CPE should be required
    >> to store the prefix and it’s expected valid and preferred expiration times in persistent
    >> storage. I would like to see the text in the I-D updated accordingly.
    > 
    > It's already there (draft-gont-v6ops-slaac-renum-00):
    > 
    > 3.2.1.  Signaling Stale Configuration Information
    > 
    >   In order to phase-out stale configuration information:
    > 
    >   o  A CPE router sending RAs that advertise dynamically-learned
    >      prefixes (e.g. via DHCPv6-PD) on an interface MUST record, on
    >      stable storage, the list of prefixes being advertised on each
    >      network segment.
    
    Where is the mention of storing the expiration times?
    
    Did I miss it, or did you miss that part of my comment?
    
    Owen
    
    > 
    > 
    > Thanks!
    > 
    > Cheers,
    > -- 
    > Fernando Gont
    > SI6 Networks
    > e-mail: fgont@si6networks.com
    > PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
    > 
    > 
    > 
    
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops