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

"Bernie Volz (volz)" <volz@cisco.com> Wed, 30 October 2019 13:46 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 615AE1200FD for <v6ops@ietfa.amsl.com>; Wed, 30 Oct 2019 06:46:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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=WGRgR/Y+; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=FpEqViQR
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 DXcdMVxtbi1U for <v6ops@ietfa.amsl.com>; Wed, 30 Oct 2019 06:46:16 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC45D1200DE for <v6ops@ietf.org>; Wed, 30 Oct 2019 06:46:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26719; q=dns/txt; s=iport; t=1572443175; x=1573652775; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=KeTWxn47vDAHAfTOKA8C4WbAsOOcWaJlt+a8gc6pcn4=; b=WGRgR/Y+qgz6hOwx4O8Lb9DsJp0D+VkaP9B2moa30O50cs/6UQN+6qFQ 3LW07L5JwzNmDeD/Mr/dOwi4VGrzaPaRxCIylb0eTuhnhGoKMUfRs+7no aXLv5NffVZjKvH7D5IqqnwtkL9TGPOfIqFRzbBjn62jg3V7eTCql9EGoM g=;
IronPort-PHdr: =?us-ascii?q?9a23=3ARbZ5sB8ADnMkmv9uRHGN82YQeigqvan1NQcJ65?= =?us-ascii?q?0hzqhDabmn44+/YR7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfJq3UeaNpJXh?= =?us-ascii?q?4Bh98Rmlk+B8qXIUb6N/XtKSc9GZcKWQ=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AGAAC9k7ld/4sNJK1kDgsBAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBAREBAQEBAQEBAQEBAYFpBAEBAQEBCwGBGy9QBWxYIAQLKgq?= =?us-ascii?q?EHoNGA4RahhaCXpdrgS4UgRADVAkBAQEMAQEYAQoKAgEBgUyCdAIXg08kNAk?= =?us-ascii?q?OAgMJAQEEAQEBAgEFBG2FNwyFUQEBAQEDAQEQEQoTAQEsCwEPAgEIEQMBAig?= =?us-ascii?q?DAgICJQsUCQgCBAENBSKDAAGBeU0DLgEOqCcCgTiIYHWBMoJ+AQEFgTQBg2M?= =?us-ascii?q?YghcJgTYBiB2CVYEeGIF/JmooH4JMPoJiAQGBJSQCAiQHCQYGCgiCUjKCLIx?= =?us-ascii?q?yCAEQgnKFPII5lgAKgiSIXYoZgjsbgjyXIoRXhhODVplOAgQCBAUCDgEBBYF?= =?us-ascii?q?SOYFYcBU7KgGCQQlHEBSDBoNzhRSFBDt0gSiLBoEwAS9TCwEB?=
X-IronPort-AV: E=Sophos;i="5.68,247,1569283200"; d="scan'208,217";a="361596457"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 30 Oct 2019 13:46:14 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id x9UDkEb2009048 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 30 Oct 2019 13:46:14 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 30 Oct 2019 08:46:14 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 30 Oct 2019 08:46:11 -0500
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 30 Oct 2019 08:46:11 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fwpwneqTUebNeKRUzYCAoaSk5K5cUxya6rux4zNEMhSoOOgpEbP6snQHb4qJ+aKaU2Nb5H/onyezivP5yA6HIL64/4s4wO8HdgRtTvz/IHFJ7DQUpCJK4pcOS5zW8tEkV/dpUzhdqGOPS6W+UsT2NoZdPYPpxNe96ywK9GL7Y8SF7u4ywb0C2tRnnnHFjFwbmh0RIFxk4gX2fQK6syWeBt5paAyNi8YjnNvuijPg89iBGqXWUcftcTZQnBPVT5JBgvd939z/TCagNHacl+aDRn/meXudGUWV9cQK8S2jhlS7E4zIAac0upZhiBQgdhuIO27QSWlwyF0z40lvGrKwWg==
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=KeTWxn47vDAHAfTOKA8C4WbAsOOcWaJlt+a8gc6pcn4=; b=Ko7XDIa6s9jebDGGjXy2amK7N915HU7+ZMOV87LqLtbp/rFx9eQQe/8pEXxBp1hoTPM1VFDxTWPcWXH7UuhT0M5NaInInp5he3piyFpgrtc4EA0wLr67xClfI1bcwFP0zEL/NQaFIQV4IOO/jDNuZkr4WLxlIHMXRURP2LIH/hQVs9wCGkda8apIlm4dMoqA7Qfk0aeh1PcIPyzzVlaNrOqzN8upEH/lbXOEwW2dto9MgHKo5GAnmHSeJLeJRHr9o7ftNiBoJwD5n7dUx4N5dUuohT/HTBzG85iWU/wlyDywxbgZWX2dF6ZX9NFcuvUrYKw4lA+bpWu7sK4aet5Qzw==
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=KeTWxn47vDAHAfTOKA8C4WbAsOOcWaJlt+a8gc6pcn4=; b=FpEqViQRErWyNsgrL5+tL1V8nITY8wkmftpxLfaC960RI15u0FoBCIAzGj5XXnRg6ersNzSXsJETRkb0WbgxEEldj30B7NrUiDy1XRtwgZ18AjfuJ58NnTbfIpCBDxiPfEaBNimngJuExUjRqEwrdE5JeagJVLaZr+rOZXgSeOI=
Received: from MWHPR1101MB2288.namprd11.prod.outlook.com (10.174.97.139) by MWHPR1101MB2191.namprd11.prod.outlook.com (10.174.101.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.22; Wed, 30 Oct 2019 13:46:10 +0000
Received: from MWHPR1101MB2288.namprd11.prod.outlook.com ([fe80::808:4d44:a5d1:c7f6]) by MWHPR1101MB2288.namprd11.prod.outlook.com ([fe80::808:4d44:a5d1:c7f6%11]) with mapi id 15.20.2387.028; Wed, 30 Oct 2019 13:46:10 +0000
From: "Bernie Volz (volz)" <volz@cisco.com>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, Ted Lemon <mellon@fugue.com>, Timothy Winters <twinters@iol.unh.edu>
CC: IPv6 Operations <v6ops@ietf.org>
Thread-Topic: [v6ops] SLAAC renum: Problem Statement & Operational workarounds
Thread-Index: AQHVibwc6PRwlsH+ZUmOeFzp+XKiI6dt8FJugAA0sICAAERiAIAAM1UOgAAj7oCAAC8lwYACBjMAgADxGbaAASHcfIAAAh0AgAAETICAAAb1gIAAEaAAgAAA6YCAAAIjAIAABSGA///EFwCAAEVzAP//wJQA
Date: Wed, 30 Oct 2019 13:46:09 +0000
Message-ID: <5329B4F4-A06E-4CE4-AE6F-6F96CEFE24ED@cisco.com>
References: <CAOSSMjVhK_V4HpMzprOyo9pj=ysFef+uZUs=twd_zfPaBdPu3Q@mail.gmail.com> <0F0B6068-CA62-449B-B56E-78E9EF8D998E@fugue.com> <CAOSSMjVLP4dx0Z1OKgXBgmuUCmR_C35J87fgkX7V=e7E3iQY3w@mail.gmail.com> <96344740-2F4B-4BCE-A881-EB1A5933AFA2@fugue.com> <F7F614D9-EC79-474C-B81C-CEF0B9EF6908@cisco.com> <724EA0E3-9CD6-4721-90F6-B47ADC31E439@consulintel.es>
In-Reply-To: <724EA0E3-9CD6-4721-90F6-B47ADC31E439@consulintel.es>
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: 2bcf561d-7b26-4edc-5c7d-08d75d3f858b
x-ms-traffictypediagnostic: MWHPR1101MB2191:
x-microsoft-antispam-prvs: <MWHPR1101MB21913880FAAC043F850BEA32CF600@MWHPR1101MB2191.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 02065A9E77
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(366004)(39860400002)(376002)(136003)(346002)(189003)(199004)(66556008)(91956017)(76116006)(76176011)(229853002)(4326008)(66066001)(14454004)(5660300002)(25786009)(316002)(54896002)(66946007)(58126008)(6306002)(6512007)(36756003)(6486002)(966005)(478600001)(7736002)(6436002)(6246003)(236005)(2171002)(99286004)(66476007)(8676002)(64756008)(446003)(186003)(11346002)(81166006)(81156014)(33656002)(256004)(14444005)(5024004)(86362001)(2616005)(486006)(2906002)(476003)(71190400001)(71200400001)(8936002)(6506007)(53546011)(66574012)(3846002)(6116002)(102836004)(26005)(66446008)(110136005); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR1101MB2191; H:MWHPR1101MB2288.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: e1g9+9Sf1fQcbyGs9WRmBdnHnCpOnl7UaBSQM328iVBDUohOPe3oiP1dgylUxesGhjb7Xxxn6d/x165E43+8jQszY5ktds9lZlwKchRpufgvIi/ZzHq9NfED/jrS0SEoGJiGM3usZ8GlWeC9f0CzpiAVDXNM5kZoa73WGW/XY4+Kv1VS7jRDX+crkUJtBprKmdZmZGyj7kdlj8b9s8x9l9mhh1z6HL2CzCc2TWiDI8YbJfY/fIwvkP9LRf/U3ZCWeE34dp0F5xjcSv0cUwxW2hSus3EfXadoVh7xKRqeyleFh1FzKDFAcMll7fLHCDQxr7f1jqNro+Y8CaeTnXOa6tIT97JfjJ5Fk2cRpn5HI0ZmU/l/2IUfafPGJWz7QYWjg5ye8tZnTRotfHtjSTL/2aCTE3gPfsTjmwQYbxgFPnokahhSE+IcJYttk4RFJQsN
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_5329B4F4A06E4CE4AE6F6F96CEFE24EDciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2bcf561d-7b26-4edc-5c7d-08d75d3f858b
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Oct 2019 13:46:09.6222 (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: qsUAFy/wuDssEXfQRm3VRcn3BgDbKQ21++LrEtC0Ahpj/ujFVBK5/BAK+MjwWPRr
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR1101MB2191
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.11, xch-rcd-001.cisco.com
X-Outbound-Node: alln-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/lsyslmfFakNGbYipxk-DHOhCo-k>
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: Wed, 30 Oct 2019 13:46:19 -0000

I don’t really think so as this is a relay agent option – not a CPE option. For the SP, the CPE is a DHCP client.

If you are trying to simply say that a relayed packet may be the trigger, one could certainly consider doing that in all those cases but it is not clear if that could cause some problems (if theory it should not … but you never know). Certainly, one could consider a DHCP server configuration knob that says “do this” (for some part or all of the configuration).


  *   Bernie

From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Date: Wednesday, October 30, 2019 at 9:33 AM
To: Bernie Volz <volz@cisco.com>om>, Ted Lemon <mellon@fugue.com>om>, Timothy Winters <twinters@iol.unh.edu>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds

Hi Bernie,

I think RFC4649, option 37, provides that option.

Regards,
Jordi
@jordipalet



El 30/10/19 14:25, "v6ops en nombre de Bernie Volz (volz)" <v6ops-bounces@ietf.org<mailto:v6ops-bounces@ietf.org> en nombre de volz@cisco.com<mailto:volz@cisco.com>> escribió:

While I haven’t followed this discussion in detail, I do wonder if the SP DHCP server could provide some assistance to CPEs that don’t have storage …

When a CPE boots and does a Solicit / Request, it could include a new option that tells the DHCP server that it has no storage and therefore no knowledge of any “past” leases. The DHCP server in this case could include any “old” leases it still has a record of (i.e., that have not expired but are no longer “valid” in terms of the configuration because of renumbering or other conditions) with 0 lifetimes. That would allow a rebooting CPE to learn old delegated prefixes that it might have advertised to its clients and initiate deprecation of these prefixes (and any addresses generated from them).

This would improve the situation when the CPE has no storage and reboots (whether customer or SP initiated).

Note: There could be conditions in which this would fail (such as if SP removed all configuration related to the older prefixes from the DHCP server), but in many cases it would allow for clean renumbering. Of course, it requires updating the DHCP software (on the SP servers and in the CPEs), but it probably easier to accomplish than requiring use of storage on the CPE device.

Be a relative easy draft to write up (at least in theory).


-          Bernie

From: v6ops <v6ops-bounces@ietf.org> on behalf of Ted Lemon <mellon@fugue.com>
Date: Wednesday, October 30, 2019 at 9:00 AM
To: Timothy Winters <twinters@iol.unh.edu>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds

On Oct 30, 2019, at 8:40 AM, Timothy Winters <twinters@iol.unh.edu<mailto:twinters@iol.unh.edu>> wrote:
We check both, the handling of the IA_PD and the error message.

And to be clear, you mean that if the CPE asks for a prefix delegation and doesn’t get the prefix it previously had, it deprecates it as described in L-14?  When this deprecation happens, what ways are being tested for it to happen?

E.g., is it the case that the client sends an IA PD containing an IA Prefix option, is the server returning the IA Prefix option containing the same prefix, with a status code encapsulated in it?   What status code?   Or is it returning an IA Prefix option with a different prefix?   Or is it doing both?

_______________________________________________ v6ops mailing list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops

**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.