Re: [dhcwg] DHCPv6 RENEW with a new address
"Bernie Volz (volz)" <volz@cisco.com> Tue, 13 December 2016 18:19 UTC
Return-Path: <volz@cisco.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 511C51296E5 for <dhcwg@ietfa.amsl.com>; Tue, 13 Dec 2016 10:19:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.418
X-Spam-Level:
X-Spam-Status: No, score=-17.418 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, SPF_PASS=-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
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 BARtCAzeYOM1 for <dhcwg@ietfa.amsl.com>; Tue, 13 Dec 2016 10:19:34 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D837F1293E9 for <dhcwg@ietf.org>; Tue, 13 Dec 2016 10:19:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9582; q=dns/txt; s=iport; t=1481653173; x=1482862773; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=quo2tc0EOhjO4qKA62DcJDZxAJ5qRwRp9KXgjVs8A8M=; b=CttLYJdPtlpY4KmUWZVaT6sb0PL0AeUv5ZxeMdoSmNlXLLawJGBdYJGN yzfsQPtWYMPo2NNDTtAaPdFALw0Brcy64p/C2k0yXqg0QXBsQvmnt/Wqi BNhYmF/mCkumzdCS3SrS+tjprXL56HJP5HpWRk6zz1UZyPx/zbK8hW685 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AVAQD8OlBY/51dJa1dGQEBAQEBAQEBAQEBBwEBAQEBgywLAQEBAQEfWoEGB41DlxqVBoIJHgeFfAIagWA/FAECAQEBAQEBAWIohGgBAQEDAQEiERogFwQCAQgRAwEBAQMCCBsDAgICJgkBFAEICAEBBAESGQQEiEIIqwWCKIsSAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYELhzCCXoQaEQEGFheCbS2CMAWIXAeHYIooAYZPhXGEaoF0UYQwiVOOEoQOAR83Yz4nDgEBgzwcgV1yAQEBhjyBIYENAQEB
X-IronPort-AV: E=Sophos;i="5.33,342,1477958400"; d="scan'208";a="182821725"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Dec 2016 18:19:32 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id uBDIJWxe031179 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 13 Dec 2016 18:19:32 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 13 Dec 2016 12:19:32 -0600
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1210.000; Tue, 13 Dec 2016 12:19:32 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] DHCPv6 RENEW with a new address
Thread-Index: AdJSI3ONGjQw6UQqR0O7cU9FkICPzwAEkbcQAM0HyFAAAv62gA==
Date: Tue, 13 Dec 2016 18:19:32 +0000
Message-ID: <30B50E12-5A27-4CFE-ACB1-230E0DC80472@cisco.com>
References: <9142206A0C5BF24CB22755C8EC422E457A9F5B8C@AZ-US1EXMB03.global.avaya.com> <f41e7c53fae84dc7bf6af92ed6d3b41d@XCH-ALN-003.cisco.com> <9142206A0C5BF24CB22755C8EC422E457A9F872C@AZ-US1EXMB03.global.avaya.com>
In-Reply-To: <9142206A0C5BF24CB22755C8EC422E457A9F872C@AZ-US1EXMB03.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1c.0.161115
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.131.32.248]
Content-Type: text/plain; charset="utf-8"
Content-ID: <2B41897677FE974394A748C13606C506@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/otVgylPShn8n5j9MFNmuetMkoFU>
Subject: Re: [dhcwg] DHCPv6 RENEW with a new address
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: Tue, 13 Dec 2016 18:19:36 -0000
You’ll have to ask this question on the support forum for whatever server implementation you are using. This is not the forum for implementation specific support questions. - Bernie On 12/13/16, 12:54 PM, "Mudric, Dusan (Dusan)" <dmudric@avaya.com> wrote: Hi Bernie, I tried adding another subnet, fc00::/64, to the dhcpd6.conf but the client did not get one more address in REPLY for RENEW. It got 2000::410 again. What exactly should I do to get a new address during RENEW-REPLY? subnet6 fc00::/64 { host SIP_phone_9611_at_Dusan_desk { hardware ethernet 6c:a8:49:87:4f:2a; fixed-address6 fc00::208; fixed-prefix6 fc00::/64; } range6 fc00::610 fc00::612; } subnet6 2000::/64 { range6 2000::410 2000::450; } Regards, Dusan. -----Original Message----- From: Bernie Volz (volz) [mailto:volz@cisco.com] Sent: Friday, December 09, 2016 11:07 AM To: Mudric, Dusan (Dusan); dhcwg@ietf.org Subject: RE: [dhcwg] DHCPv6 RENEW with a new address The most likely cases are if there has been a reconfiguration on the server or a network renumbering event has occurred (which might add a new prefix before an old one is removed). An easy way to test this is to change the configuration on the server so that the old prefix from which the client got leases is no longer valid when the Renew occurs. Or, add a second prefix to the configuration (so that the client is supposed to get an address from each prefix). - Bernie -----Original Message----- From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Mudric, Dusan (Dusan) Sent: Friday, December 09, 2016 8:56 AM To: dhcwg@ietf.org Subject: Re: [dhcwg] DHCPv6 RENEW with a new address Hi, I posted this question in dhcp-users group. Since there was no answer, I am resending the same question to DHCWG. > > Hi, >> > > What would be a real life use case (even better, use cases) for > > getting a new address during the IPv6 address renewal? >> > >> Thanks, > > Dusan. 18.1.3. Creation and Transmission of Renew Messages "The server may also add new addresses to the IA. " "The server may remove addresses from the IA by setting the preferred and valid lifetimes of those addresses to zero." When will server do this? How can I test it? Regards, Dusan. -----Original Message----- From: dhcp-users [mailto:dhcp-users-bounces@lists.isc.org] On Behalf Of dhcp-users-request@lists.isc.org Sent: Thursday, November 24, 2016 7:00 AM To: dhcp-users@lists.isc.org Subject: dhcp-users Digest, Vol 97, Issue 16 Send dhcp-users mailing list submissions to dhcp-users@lists.isc.org To subscribe or unsubscribe via the World Wide Web, visit https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.isc.org_mailman_listinfo_dhcp-2Dusers&d=DQICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=UT3Bk9cbLeaJxhf3iCrhIoUWB8YLZU23029sMQGQ2kY&m=bJvWui61rhgrP19VTIFe8ZmEgn8gb0lK0b29th12ekc&s=Bvgv76PzHyLYpsyoPoihwhizQ7bhyZt9SXyXYOyteTA&e= or, via email, send a message with subject or body 'help' to dhcp-users-request@lists.isc.org You can reach the person managing the list at dhcp-users-owner@lists.isc.org When replying, please edit your Subject line so it is more specific than "Re: Contents of dhcp-users digest..." Today's Topics: 1. Re: DHCPv6 RENEW with a new address (Mudric, Dusan (Dusan)) ---------------------------------------------------------------------- Message: 1 Date: Wed, 23 Nov 2016 14:39:47 +0000 From: "Mudric, Dusan (Dusan)" <dmudric@avaya.com> To: "dhcp-users@lists.isc.org" <dhcp-users@lists.isc.org> Subject: Re: DHCPv6 RENEW with a new address Message-ID: <9142206A0C5BF24CB22755C8EC422E457A9E6922@AZ-US1EXMB03.global.avaya.com> Content-Type: text/plain; charset="us-ascii" On RENEW, it is allowed to remove the old IPv6 address and add a new one: https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc3315-23section-2D18.1.3&d=DQICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=UT3Bk9cbLeaJxhf3iCrhIoUWB8YLZU23029sMQGQ2kY&m=bJvWui61rhgrP19VTIFe8ZmEgn8gb0lK0b29th12ekc&s=9wJndZlFqkiC7Dx4A4Cykpsgx1MtPKxUcrnOk7ssG7I&e= 18.1.3. Creation and Transmission of Renew Messages "The server may also add new addresses to the IA. " "The server may remove addresses from the IA by setting the preferred and valid lifetimes of those addresses to zero." When will server do this? After an outage? Regards, Dusan. > Date: Tue, 22 Nov 2016 10:00:03 -0500 (EST) > From: perl-list <perl-list@network1.net> > To: Users of ISC DHCP <dhcp-users@lists.isc.org> > Subject: Re: DHCPv6 RENEW with a new address > Message-ID: > <1482875728.114430.1479826803268.JavaMail.zimbra@network1.net> > Content-Type: text/plain; charset="utf-8" > > I don't think that it would ever happen quite that way. If the renewal failed, at the end of the lease, the client > device should send a solicit message which could result in a new address (or the same address the client had > before). I don't think the client can get a new (different?) address during renewal? > > Anyone else? > > > From: "Mudric, Dusan (Dusan)" <dmudric@avaya.com> > > To: dhcp-users@lists.isc.org > > Sent: Tuesday, November 22, 2016 9:07:05 AM > > Subject: DHCPv6 RENEW with a new address > > > > Hi, >> > > What would be a real life use case (even better, use cases) for > > getting a new address during the IPv6 address renewal? >> > >> Thanks, > > Dusan. ------------------------------ Subject: Digest Footer _______________________________________________ dhcp-users mailing list dhcp-users@lists.isc.org https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.isc.org_mailman_listinfo_dhcp-2Dusers&d=DQICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=UT3Bk9cbLeaJxhf3iCrhIoUWB8YLZU23029sMQGQ2kY&m=bJvWui61rhgrP19VTIFe8ZmEgn8gb0lK0b29th12ekc&s=Bvgv76PzHyLYpsyoPoihwhizQ7bhyZt9SXyXYOyteTA&e= ------------------------------ End of dhcp-users Digest, Vol 97, Issue 16 ****************************************** _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_dhcwg&d=DQIFAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=UT3Bk9cbLeaJxhf3iCrhIoUWB8YLZU23029sMQGQ2kY&m=TqN0vVxtwdsttFd4jQTChaTm3FoRHrQcEUtVlu4_VqE&s=hYRqEl3WEt-frCty44b5MZwchujLFaf3pdjLFTh4wko&e=
- Re: [dhcwg] DHCPv6 RENEW with a new address Mudric, Dusan (Dusan)
- Re: [dhcwg] DHCPv6 RENEW with a new address Bernie Volz (volz)
- Re: [dhcwg] DHCPv6 RENEW with a new address Mudric, Dusan (Dusan)
- Re: [dhcwg] DHCPv6 RENEW with a new address Mudric, Dusan (Dusan)
- Re: [dhcwg] DHCPv6 RENEW with a new address Bernie Volz (volz)