Re: [dhcwg] RFC3315 DECLINE definition

"Mudric, Dusan (Dusan)" <dmudric@avaya.com> Mon, 13 February 2017 14:02 UTC

Return-Path: <dmudric@avaya.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEFCF1295A1 for <dhcwg@ietfa.amsl.com>; Mon, 13 Feb 2017 06:02:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 PCEYkwnWe5Dw for <dhcwg@ietfa.amsl.com>; Mon, 13 Feb 2017 06:02:51 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B80BA129535 for <dhcwg@ietf.org>; Mon, 13 Feb 2017 06:02:50 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2HlAgA0vKFY/xUHmMZeGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgxBCgXGDUq86gg+CDIYiAhqCTUAXAQIBAQEBAQEBA18ohGoCAQM?= =?us-ascii?q?SERFVAgEIDQ0CBiACAgIwFRACBAEaGolIAaNGimKCJSYCixsBAQEBAQUBAQEBA?= =?us-ascii?q?QEBASCBC4VChG6BPIMCGIMELoIxBZtyAZxphi+TFSABN4EAURWHAIhoK4EDAYE?= =?us-ascii?q?LAQEB?=
X-IPAS-Result: =?us-ascii?q?A2HlAgA0vKFY/xUHmMZeGQEBAQEBAQEBAQEBBwEBAQEBgxB?= =?us-ascii?q?CgXGDUq86gg+CDIYiAhqCTUAXAQIBAQEBAQEBA18ohGoCAQMSERFVAgEIDQ0CB?= =?us-ascii?q?iACAgIwFRACBAEaGolIAaNGimKCJSYCixsBAQEBAQUBAQEBAQEBASCBC4VChG6?= =?us-ascii?q?BPIMCGIMELoIxBZtyAZxphi+TFSABN4EAURWHAIhoK4EDAYELAQEB?=
X-IronPort-AV: E=Sophos;i="5.35,156,1484024400"; d="scan'208";a="227791568"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 13 Feb 2017 09:02:23 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-US1EXHC02.global.avaya.com) ([135.11.85.13]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Feb 2017 09:02:23 -0500
Received: from AZ-US1EXMB03.global.avaya.com ([fe80::a5d3:ad50:5be9:1922]) by AZ-US1EXHC02.global.avaya.com ([::1]) with mapi id 14.03.0319.002; Mon, 13 Feb 2017 09:02:23 -0500
From: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
To: dhcp-users <dhcp-users-bounces@lists.isc.org>, dhcwg <dhcwg@ietf.org>
Thread-Topic: [dhcwg] RFC3315 DECLINE definition
Thread-Index: AdKCVGJ7VzCckicuS8ujStD5DUW3kQAAXlQAAADH2iAAAEJQgAAATJqQAAClqeAAH3aUcAAClxKAAAGY9gD///saAIAADr9wgAA6TwCAAFLTEP//ubmAgABS6jD//68/gIAAUzJQ//+28gAACnV4EAAKQI6AAB7vbSAAMyFpAABwmj1wAKS8ff4BSSOxkAKHSe+ABJNGvAA=
Date: Mon, 13 Feb 2017 14:02:22 +0000
Message-ID: <9142206A0C5BF24CB22755C8EC422E457AA194E5@AZ-US1EXMB03.global.avaya.com>
References: <9142206A0C5BF24CB22755C8EC422E457AA186B9@AZ-US1EXMB03.global.avaya.com> <531b6fa753a441c19f1d47958f20b659@XCH-ALN-003.cisco.com> <9142206A0C5BF24CB22755C8EC422E457AA18717@AZ-US1EXMB03.global.avaya.com> <240e4b5573614422a42abec328872c0b@XCH-ALN-003.cisco.com> <9142206A0C5BF24CB22755C8EC422E457AA18746@AZ-US1EXMB03.global.avaya.com> <fd3365190bd445b1ad00a7d8043530dd@XCH-ALN-003.cisco.com> <9142206A0C5BF24CB22755C8EC422E457AA188B2@AZ-US1EXMB03.global.avaya.com> <6792EF5E-8C1F-4D3B-BC6D-8D2EA011BF31@cisco.com> <9142206A0C5BF24CB22755C8EC422E457AA1890A@AZ-US1EXMB03.global.avaya.com> <36880D80-601D-42BF-92F1-3E1B3A59A8FD@cisco.com> <9142206A0C5BF24CB22755C8EC422E457AA1892A@AZ-US1EXMB03.global.avaya.com> <15160861-4D37-4A5E-900A-8AD688218EEF@fugue.com> <9142206A0C5BF24CB22755C8EC422E457AA1898F@AZ-US1EXMB03.global.avaya.com> <C16D3614-AD9E-4AB3-915B-5288DB0EB239@fugue.com> <9142206A0C5BF24CB22755C8EC422E457AA189BD@AZ-US1EXMB03.global.avaya.com> <9142206A0C5BF24CB22755C8EC422E457AA189F9@AZ-US1EXMB03.global.avaya.com> <A3AFA8FF-FDEF-4058-814A-E687D5CC2969@fugue.com> <9142206A0C5BF24CB22755C8EC422E457AA18ABB@AZ-US1EXMB03.global.avaya.com> <A023117A-2B06-4660-88B9-9AB183F05B66@fugue.com> <9142206A0C5BF24CB22755C8EC422E457AA18B12@AZ-US1EXMB03.global.avaya.com> <B2511278-5D7A-40E0-AC4A-60784C101A80@fugue.com> <9142206A0C5BF24CB22755C8EC422E457AA18B5E@AZ-US1EXMB03.global.avaya.com> <36E8C88B-82EA-41FE-AB55-55F9CD110664@thehobsons.co.uk> <9142206A0C5BF24CB22755C8EC422E457AA18ED6@AZ-US1EXMB03.global.avaya.com> <CAL10_BqFTSbhe6krvTUz1VnLw0pQGodPRrt8c39sNcMhRUqvQw@mail.gmail.com> <9142206A0C5BF24CB22755C8EC422E457AA1906F@AZ-US1EXMB03.global.avaya.com> <CAL10_BorkqQXZUOFWarj_+275u1z9L9Xtkse=RQjGnOeFveNJg@mail.gmail.com> <9142206A0C5BF24CB22755C8EC422E457AA19187@AZ-US1EXMB03.global.avaya.com> <CAL10_Bpy+4Eb4wUwuy5YkKaOO+69o0Ombej7n_ApCg1Gw-r0QQ@mail.gmail.com> <9142206A0C5BF24CB22755C8EC422E457AA1924E@AZ-US1EXMB03.global.avaya.com> <CAL10_Bpb2eXAmnAnGpAeURMuqxBE=G+zYN+n1b1xk0qamtaU+Q@mail.gmail.com>
In-Reply-To: <CAL10_Bpb2eXAmnAnGpAeURMuqxBE=G+zYN+n1b1xk0qamtaU+Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.11.85.50]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/SDA5dHCGWTXQVAJJF1EbWJr1qfE>
Subject: Re: [dhcwg] RFC3315 DECLINE definition
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 14:02:52 -0000

Thanks to DHCWG group for their comments. I believe the proposals would benefit DHCv6 users.

For the record:

PROBLEM STATEMENTS:
- A network operator can set client IPv6 addresses on DHCPv6 server. An address can be invalid or make a client unreachable.
- A network operator can change an address prefix on a router. A client address can become unreachable
- A default router offering a prefix to a client can become unreachable. A client address can become unreachable on a local link 
- A client does not release unused addresses

PROPOSED FAILURE INDICATIONS
- A client validates the addresses and the address prefixes and notifies DHCPv6 server about the problems
- A client returns unused addresses
- DHCPv6 server:
  -- logs error messages (invalid & unreachable addresses with device IDs)
  -- does not assign the invalid addresses
  -- periodically checks for the reachability of unreachable addresses and, when they become reachable, assigns them again
- An operator
 -- checks if there are unreachable devices and the reason codes