Re: [dhcwg] RFC3315 DECLINE definition

"Mudric, Dusan (Dusan)" <dmudric@avaya.com> Fri, 10 February 2017 17:10 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 5586C129A47 for <dhcwg@ietfa.amsl.com>; Fri, 10 Feb 2017 09:10:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 mXA5BXwRUZTs for <dhcwg@ietfa.amsl.com>; Fri, 10 Feb 2017 09:10:38 -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 8724B129A42 for <dhcwg@ietf.org>; Fri, 10 Feb 2017 09:10:38 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2EYAQBg851Y/yYyC4deGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm8hQmGBCQeDUooIkguTJ4IPgg2GIgIagl8/GAECAQEBAQEBAQN?= =?us-ascii?q?fKIRpAQEBAQIBEhEKRwUFBwQCAQgNAQMEAQEBCh0DAgICMBQJCAIEDgUIGolOC?= =?us-ascii?q?AGlPopigiUmAosiAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYZNhG6BPIMCGBWCby6?= =?us-ascii?q?CMQWJBW+HFYRLhh4BlA6FF4NEhi+TFR85fk8VhHuCA3WHZCuBAwGBCwEBAQ?=
X-IPAS-Result: =?us-ascii?q?A2EYAQBg851Y/yYyC4deGQEBAQEBAQEBAQEBBwEBAQEBgm8?= =?us-ascii?q?hQmGBCQeDUooIkguTJ4IPgg2GIgIagl8/GAECAQEBAQEBAQNfKIRpAQEBAQIBE?= =?us-ascii?q?hEKRwUFBwQCAQgNAQMEAQEBCh0DAgICMBQJCAIEDgUIGolOCAGlPopigiUmAos?= =?us-ascii?q?iAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYZNhG6BPIMCGBWCby6CMQWJBW+HFYRLh?= =?us-ascii?q?h4BlA6FF4NEhi+TFR85fk8VhHuCA3WHZCuBAwGBCwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.35,142,1484024400"; d="scan'208,217";a="227582928"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 10 Feb 2017 12:10:36 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-US1EXHC01.global.avaya.com) ([135.11.85.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Feb 2017 12:10:36 -0500
Received: from AZ-US1EXMB03.global.avaya.com ([fe80::a5d3:ad50:5be9:1922]) by AZ-US1EXHC01.global.avaya.com ([135.11.85.12]) with mapi id 14.03.0319.002; Fri, 10 Feb 2017 12:10:35 -0500
From: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
To: Andre Kostur <akostur@incognito.com>
Thread-Topic: [dhcwg] RFC3315 DECLINE definition
Thread-Index: AdKCVGJ7VzCckicuS8ujStD5DUW3kQAAXlQAAADH2iAAAEJQgAAATJqQAAClqeAAH3aUcAAClxKAAAGY9gD///saAIAADr9wgAA6TwCAAFLTEP//ubmAgABS6jD//68/gIAAUzJQ//+28gAACnV4EAAKQI6AAB7vbSAAMyFpAABwmj1wAK+Iqs8BXkNKMA==
Date: Fri, 10 Feb 2017 17:10:35 +0000
Message-ID: <9142206A0C5BF24CB22755C8EC422E457AA1906F@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>
In-Reply-To: <CAL10_BqFTSbhe6krvTUz1VnLw0pQGodPRrt8c39sNcMhRUqvQw@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: multipart/alternative; boundary="_000_9142206A0C5BF24CB22755C8EC422E457AA1906FAZUS1EXMB03glob_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/W1rwnbCxqOLt8zqrdu1Oc7ZIdN4>
Cc: dhcwg <dhcwg@ietf.org>
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: Fri, 10 Feb 2017 17:10:40 -0000

Hi Andre,

Please see inlined

Thanks,
Dusan.

-----Original Message-----
From: Andre Kostur [mailto:akostur@incognito.com]
Sent: Friday, February 10, 2017 11:25 AM
To: Mudric, Dusan (Dusan)
Cc: Simon Hobson; dhcwg
Subject: Re: [dhcwg] RFC3315 DECLINE definition

On Fri, Feb 10, 2017 at 6:35 AM, Mudric, Dusan (Dusan) <dmudric@avaya.com<mailto:dmudric@avaya.com>> wrote:
> - If the key feature of the stateful DHCPv6 is the address assignment,
> why there is no any address validation?

You need to be clear on what you mean by "address validation".  (Oh, and DHCPv6 is responsible for both address and prefix assignment)

[Dusan] - Syntax checks
              - Semantic checks
              - Prefix checks

> - Why is the human intervention a part of the protocol? Why the
> protocol requires an administrator not to make mistakes?

Everything is susceptible to human error.  You need to have more specific use-cases to get anywhere near this question.  Also, the protocol does not mandate configuration management.  Perhaps your DHCP server has the capability of comparing its configuration with that on a router to look for certain potential configuration mismatches.  But that's a quality of implementation issue, not a protocol issue.

[Dusan] If the server communicates with a router to compare the configuration, it is a protocol

> - Why the client must assign every address offered by the server? Why
> should the client save the advertised leases for every IAADDR in IA’s,
> if the status code is STATUS_Success?

It doesn't have to.  The client can pick and choose, preferably at the ADVERTISE/REQUEST stage.  The server ADVERTISEs a dozen addresses, the
client decides that it wants only 1 of them and REQUESTs it.   Or a
less well-behaved client could REQUEST them all, but only actually configure one of them on an interface.

[Dusan] Which section in RFC3315 defines how DHCPv6 client selects the leases? Which section defines what the client does with non-selected leases?

> - Why the client must use the address that does not match any of the
> router prefixes?

The router may not be advertising any prefixes, so the client doesn't know any different.  (Nor should it)

[Dusan] What if the router advertised a prefix and the client received an address that does not start with the prefix?

> - Why the client is not interworking with ND protocol?

Be more specific.  ND covers a lot of ground.

[Dusan] DHCPv6 client does not know about router prefixes and does not know which router is reachable. Which section in RFC3315 defines what the client should do with the address:
- if ND receives prefix P1?
- if the router that advertised P1 is not reachable?

> - Why the client does not return the address it does not use?

Talk to your client vendor.  The client can return addresses by protocol.  Either by not REQUESTing it in the first place (though this isn't returning an address, it's just not claiming it), or by RELEASEing it.

[Dusan] Which section in RFC3315 defines what the client should RELEASE after ADVERTISE and REPLY? Why should RELEASE be used for the address that is not even assigned?

> - Why is DECLINE message associated with only one error code (DAD failed)?

No use-case has been presented that the DHC working group has agreed upon that a DECLINE for other reasons is the appropriate response.

[Dusan] That is why I am presenting these use cases.

--
Andre Kostur