Re: [dhcwg] WGLC for draft-ietf-dhc-addr-registration-04 - respond by April 13, 2014

"Darpan Malhotra (damalhot)" <damalhot@cisco.com> Sun, 30 March 2014 08:41 UTC

Return-Path: <damalhot@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15D251A07A1 for <dhcwg@ietfa.amsl.com>; Sun, 30 Mar 2014 01:41:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.51
X-Spam-Level:
X-Spam-Status: No, score=-9.51 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 nVosGWjXFa7z for <dhcwg@ietfa.amsl.com>; Sun, 30 Mar 2014 01:41:36 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id CC1811A07A0 for <dhcwg@ietf.org>; Sun, 30 Mar 2014 01:41:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16435; q=dns/txt; s=iport; t=1396168893; x=1397378493; h=from:to:subject:date:message-id:mime-version; bh=RgKTkLnrBgXR29Bs+Vs1ui0bCrtKCydcpk6kCVujBMQ=; b=NwroEBXjjiRfUGN7j3Dc9Z9/dfXr7X8kiSXULL6MBtD+1igDxZNejlGn 24gl+Je3ia3Ma4Qtjo/xCeRpfrlo6+u149m7AvqHtqp3enOmoaIY9wjZr sPI4zLbdMpZUgHUQLlJ7IxI4rLfxFBSQEe6D8RwchYD6YHq7ThnGt6OcI I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al4FAFvYN1OtJV2c/2dsb2JhbABZgkJEO1e6HYh0gRAWdIIlAQEBAwEtXgEIEQMBAQEoORQJCgQBEgmHaAgN0SIXji4BAQY4FweEMgSYToEzkQKBcYE/gWoIFyI
X-IronPort-AV: E=Sophos; i="4.97,759,1389744000"; d="scan'208,217"; a="31490608"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-4.cisco.com with ESMTP; 30 Mar 2014 08:41:32 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s2U8fWCe016694 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Sun, 30 Mar 2014 08:41:32 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.56]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0123.003; Sun, 30 Mar 2014 03:41:32 -0500
From: "Darpan Malhotra (damalhot)" <damalhot@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-addr-registration-04 - respond by April 13, 2014
Thread-Index: AQHPS/PZRPBq6LSmDkC6ZBKgVsxdEw==
Date: Sun, 30 Mar 2014 08:41:31 +0000
Message-ID: <CF5DC163.EBA9%damalhot@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [10.142.40.50]
Content-Type: multipart/alternative; boundary="_000_CF5DC163EBA9damalhotciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/LrIagHbipGMUB0l1VcRvbL-Ay7o
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-addr-registration-04 - respond by April 13, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sun, 30 Mar 2014 08:41:43 -0000

I have few questions/doubts :


  1.  If there are two (or more) DHCPv6 servers , which server takes up the task of configuring DNS server ?

[Does the answer come from draft-ietf-dhc-dhcpv6-load-balancing-01 ? ]

2. Section 5.2  says :

If the address registration server does not receive such a refresh after the valid-lifetime has passed, it SHOULD  remove the IPv6-address-to-FQDN bindings in DNS.

DHCPv6 server is not managing this IAADDR (after all, it is generated by client). How will DHCPv6 server know that valid-lifetime of the address gas expired?  Does this mean that DHCPv6 server keeps recording all the successful ADDR-REGISTRATION-REQUEST transactions ( DUID (client-id) + IA_type + IAID + IAADDR + FQDN + valid-lifetime ) in its stable storage ?



Minor typos observed :

1. Section 1 : Introduction
A new ADDR-REGISTRATION-REQUEST DHCPv6 message type is defined to
initiate the address registration request, and two new Status codes
is defined to indicate registration errors on the server side.

>> two new Status codes are defined to indicate registration errors on the server side.


2. Section 7: IANA Considerations

This document defines a new DHCPv6 message, the ADDR-REGISTRATION-
   REQUEST message (TBA1) described in Section 5<http://tools.ietf.org/html/draft-ietf-dhc-addr-registration-04#section-5>,

This document defines two new DHCPv6 Status code, the
   RegistrationNotSupported (TBA2) and RegistrationDenied (TBA3)
   described in Section 6<http://tools.ietf.org/html/draft-ietf-dhc-addr-registration-04#section-6>,


>> ADDR-REGISTRATION-REQUEST is defined in Section 4 and two new Status Codes are defined in Section 5.

Regards,
Darpan

From: "Bernie Volz (volz)" <volz@cisco.com<mailto:volz@cisco.com>>
Date: Saturday, 29 March 2014 7:35 PM
To: "dhcwg@ietf.org<mailto:dhcwg@ietf.org>" <dhcwg@ietf.org<mailto:dhcwg@ietf.org>>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-addr-registration-04 - respond by April 13, 2014


(WG co-chair hat off)



I do not feel the document is ready “as is”. Please see my comments at http://www.ietf.org/mail-archive/web/dhcwg/current/msg15362.html.



-          Bernie

From: Bernie Volz (volz)
Sent: Saturday, March 29, 2014 10:04 AM
To: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: WGLC for draft-ietf-dhc-addr-registration-04 - respond by April 13, 2014


Folks, the authors of draft-ietf-dhc-addr-registration (http://tools.ietf.org/html/draft-ietf-dhc-addr-registration-04)

feel it's ready for work group last call. Please review this draft and indicate whether or not you feel it is ready to be published.



At the time of this writing, there is no IPR reported against this draft.



Tomek and I will evaluate consensus after April 13, 2014.



Thanks,

Bernie & Tomek