IETF Logo Mail Archive

Re: [v6ops] [dhcwg] some feedback on http://tools.ietf.org/html/draft-ietf-dhc-addr-registration-01

Ted Lemon <Ted.Lemon@nominum.com> Mon, 19 November 2012 03:14 UTC

Return-Path: <Ted.Lemon@nominum.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 2AE4E21F85D9; Sun, 18 Nov 2012 19:14:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.582
X-Spam-Level:
X-Spam-Status: No, score=-106.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ahS2PTJlyHAk; Sun, 18 Nov 2012 19:14:14 -0800 (PST)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id E3B4721F85D6; Sun, 18 Nov 2012 19:14:12 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKUKmkBCCvqyWxevgBXRUDaRrapNoeoAD/@postini.com; Sun, 18 Nov 2012 19:14:13 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 247941B80A9; Sun, 18 Nov 2012 19:14:12 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 186FD190043; Sun, 18 Nov 2012 19:14:12 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Sun, 18 Nov 2012 19:14:12 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Sheng Jiang <jiangsheng@huawei.com>
Thread-Topic: [dhcwg] [v6ops] some feedback on http://tools.ietf.org/html/draft-ietf-dhc-addr-registration-01
Thread-Index: AQHNxgKaF9DIw6/Nnk+UmCfAcna/WpfxAfqA
Date: Mon, 19 Nov 2012 03:14:10 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63074740B8A9@mbx-01.win.nominum.com>
References: <50A33EFA.7070008@bogus.com> <5D36713D8A4E7348A7E10DF7437A4B9239F8E40C@szxeml545-mbx.china.huawei.com> <50A59C1F.2040407@bogus.com> <5D36713D8A4E7348A7E10DF7437A4B9239F8E520@szxeml545-mbx.china.huawei.com> <50A5BB8E.6010308@bogus.com> <5D36713D8A4E7348A7E10DF7437A4B9239F8E5CB@szxeml545-mbx.china.huawei.com> <1353047488.86944.YahooMailNeo@web32501.mail.mud.yahoo.com> <8D23D4052ABE7A4490E77B1A012B630747408741@mbx-01.win.nominum.com> <5D36713D8A4E7348A7E10DF7437A4B9239F8ED16@szxeml545-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B9239F8ED16@szxeml545-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CAC1E23FA2725A4592D7F0D09722FE0B@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, IPv6 Ops WG <v6ops@ietf.org>, "draft-ietf-dhc-addr-registration@tools.ietf.org" <draft-ietf-dhc-addr-registration@tools.ietf.org>
Subject: Re: [v6ops] [dhcwg] some feedback on http://tools.ietf.org/html/draft-ietf-dhc-addr-registration-01
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 19 Nov 2012 03:14:15 -0000

On Nov 18, 2012, at 10:03 PM, Sheng Jiang <jiangsheng@huawei.com>
 wrote:
> Thanks for your email. Yes, my original use case falls into the first category. However, since we are trying to define a generic addr registration mechanism, we could include more applicable use cases. I guess what we should do now is to add a "Applicability" section into the draft. Are you interested and have time to contribute some text?

I can try.   I have a lot of things on my list.   :}

> For me, router-based addr registration may need another dedicated draft. Although current IA can work out, a new DHCP option that support bulk addr registration may be more efficient than one addr per time. What's your opinion?

I think that bulk registration won't work because hosts aren't discovered all at the same time; either the router waits until it's accumulated enough to fill a packet, or it sends an update each time it discovers a new one.

v2.23.0 | Report a Bug | By Email