Re: [dhcwg] Adopt draft-troan-dhc-dhcpv6-stateful-issues-00 as WG item
Tomek Mrugalski <tomasz.mrugalski@gmail.com> Sun, 08 April 2012 16:19 UTC
Return-Path: <tomasz.mrugalski@gmail.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 5F65721F8527 for <dhcwg@ietfa.amsl.com>; Sun, 8 Apr 2012 09:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rBpsctHW6RSD for <dhcwg@ietfa.amsl.com>; Sun, 8 Apr 2012 09:19:04 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id D7BA021F8523 for <dhcwg@ietf.org>; Sun, 8 Apr 2012 09:19:03 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so2376258wgb.13 for <dhcwg@ietf.org>; Sun, 08 Apr 2012 09:19:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=1wxF9s7Dr5U4N2cvR1fcu7Gtaqn7HF9wpZUx2bXjyUk=; b=B5+io2S/gVuobkWskhdBOHB62RlmM6BO1UKm5n/1dXQoVSg8Tco46E1fZgu9GN8RNc hQ7VIM+v/Y2Mv0ZPt1fIz3Tx4gBRebp1rCaw9dHOCa+N3jDKBq4RkdZGHjnRIoHRFn7e SIJnzUQRbDLCkbwvZgq230lQiKCQ0QQJYiQFPOt+fEattxwubgupvypuaQ9TdbG967p2 MTrAjfoo3WyXmZ/rWgNW65BKJQpItOjPiiTXfZnhrc9OQKt94RGvF/8WIE3Mu6KNEckg BTDdl1SpiRou8BoYTcdBGnGawPp6WB+sy/658W2l/iyPF1Hg17WkJPU8+k6P08n7ukTk pSZA==
Received: by 10.180.105.194 with SMTP id go2mr9869772wib.22.1333901942993; Sun, 08 Apr 2012 09:19:02 -0700 (PDT)
Received: from tomek.local (095160002041.lomza.vectranet.pl. [95.160.2.41]) by mx.google.com with ESMTPS id h8sm37967797wix.4.2012.04.08.09.19.01 (version=SSLv3 cipher=OTHER); Sun, 08 Apr 2012 09:19:02 -0700 (PDT)
Message-ID: <4F81BA73.4000400@gmail.com>
Date: Sun, 08 Apr 2012 18:18:59 +0200
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: dhcwg@ietf.org, Ole Troan <ot@cisco.com>
References: <D9B5773329187548A0189ED6503667890B9F42CB@XMB-RCD-101.cisco.com>
In-Reply-To: <D9B5773329187548A0189ED6503667890B9F42CB@XMB-RCD-101.cisco.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: [dhcwg] Adopt draft-troan-dhc-dhcpv6-stateful-issues-00 as WG item
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Apr 2012 16:19:05 -0000
On 12-04-05 19:25, Bernie Volz (volz) wrote: > I kindly request that we adopt this document as a DHC WG work item. I do support this work and its adoption. I also have couple of comments: 0. Would it be reasonable to name this work 3315bis? 1. I assume this work will also cover all combinations of IA_NA/IA_PD/IA_TA. But what about IA_PA, specified in draft-ietf-dhc-host-gen-id? This work was adopted by DHC, so authors should take a closer look at it. (I'm sorry I can't offer any better comments here. I haven't read host-gen-id yet). 2. stateful-issues draft is a very useful work. Once adopted it should also look at CGA issues - my understanding is that it basically degrades DHCP into registration service, compared to normal assignment service. I haven't read CGA drafts recently, so again this is only a pointer to something that should be looked at. It is possible that there's nothing to do in that matter. 3. Abstract could be reworded: "the ne options for Prefix Delegation options for DHCPv6 into DHCPv6" part is repetitive. The same is true for first paragraph of Introduction section. 4. Text refer to different IA options as IA_. I think it would look better without the underscore. If that is not clear, perhaps it could be clarified that "IA option" means any of IA_NA, IA_TA or IA_PD. 5. Section 3.1 states that client MUST ignore IAs with status code NoAddrAvail. That doesn't help much. What about other status codes? IA_PD may be returned with NoPrefixAvail. Much better would be to say that client MUST ignore IAs with status code other than Success. We should also add that client SHOULD rate advertise without assigned IAs lower than other advertises, but exact advertise rating algorithm is up to client imlementors. For example, I would implement a client that accepts advertise with preference=5 and all IAs assigned rather than one with preference=10, but without IA_NA or IA_PD assigned. 6. Section 3.2 says that 3 non-success status codes (NoAddrsAvail, NoPrefixAvail and NotOnLink) should appear within IA options. It would be better to not explicitely limit to those 3 status code, but say all non-success status codes to maintain forward compatibility. Something like "e.g. NoAddrsAvail, NoPrefixAvail, NotOnLink and other non-success status codes" will do. BTW you missed UnspecFail code that is already defined and could be used, so the text as it is does not cover all situations from day 1. 7. It should be clarified that status codes are specified per instance of an option, not per option type. Think about client that sends 3 IA_NA options. It can receive 2 addresses and NoAddrAvail in the third instance. That could be either due to pool depletion (unlikely) or server policy that allow server to assign no more than 2 addresses per client (likely). 8. Proposed replacement errata in section 3.2 should clarify that such proposed action should be taken on each IA being answered. 9. Section 3.3 could mention relation between T1/T2 and information refresh option (RFC4242). The reasonable clarification would be that client MAY request other options in ORO when sending RENEW or REBIND. 10. Allowing PD to be confirmed with CONFIRM could be tricky. In many deployment scenarios routing is configured separately for each delegated prefix and server can't really say "yeah, I've never assigned you that one, but it should be valid on your link.". I don't object allowing IA_PD in CONFRIM, but it should be accompanied with a clause that server MUST include IA_PD response only if it is certain that delegated prefix is really valid. This will complicate things. What is client sends CONFIRM with IA_NA and IA_PD and server can confirm that address is on-link, but is not sure about prefix? There's no such status as IdontKnow. Different IA combinations should be given more thought. 11. Section 3.5. A what??? Are you suggesting that client can send RENEW *after* it sent RELEASE? If that is the case, I strongly object. Once client released a lease, it has no further claims to released address/prefix. It MUST NOT send RENEW. Proper way it to send REQUEST, not RENEW. Also. Section 3.5 title mentions DECLINE, but there is nothing about DECLINE in the text. Authors probably forgot adding a sentence that DECLINE may be sent at any time when client owns a lease. 12. A question about proposed operation in section 3.6. What if there are two servers. Imagines a case with 2 servers: one that provides addresses and second one that provides prefixes. Client requests IA_NA and IA_PD. What should client do? 13. In 3rd paragraph in section 3.6 it would be better to say non-success status codes rather than NoAddrsAvail (or at least NoAddrsAvail/NoPrefixAvail/NotOnLink/UnspecFail). 14. Section 3.7 is the most unfortunate. I understand the reasons that led authors to that decision, so I sadly accept it. Despite my comments, I strongly support this work and it adoption. It is great that we will get this thing clarified. Greetings to all woods dwellers, Tomek
- [dhcwg] Call for Adoption, draft-troan-dhc-dhcpv6… Ted Lemon
- [dhcwg] Adopt draft-troan-dhc-dhcpv6-stateful-iss… Bernie Volz (volz)
- Re: [dhcwg] Call for Adoption, draft-troan-dhc-dh… Kim Kinnear
- Re: [dhcwg] Call for Adoption, draft-troan-dhc-dh… Daryl Tanner
- Re: [dhcwg] Call for Adoption, draft-troan-dhc-dh… Dedecker Hans
- Re: [dhcwg] Call for Adoption, draft-troan-dhc-dh… Timothy Winters
- Re: [dhcwg] Call for Adoption, draft-troan-dhc-dh… Tina TSOU
- Re: [dhcwg] Call for Adoption, draft-troan-dhc-dh… Chris Donley
- Re: [dhcwg] Call for Adoption, draft-troan-dhc-dh… Gaurav Halwasia (ghalwasi)
- Re: [dhcwg] Call for Adoption, draft-troan-dhc-dh… Hans Liu
- Re: [dhcwg] Adopt draft-troan-dhc-dhcpv6-stateful… Tomek Mrugalski
- Re: [dhcwg] Adopt draft-troan-dhc-dhcpv6-stateful… Bernie Volz (volz)
- Re: [dhcwg] Adopt draft-troan-dhc-dhcpv6-stateful… Tomek Mrugalski
- Re: [dhcwg] Adopt draft-troan-dhc-dhcpv6-stateful… Bernie Volz (volz)
- Re: [dhcwg] Adopt draft-troan-dhc-dhcpv6-stateful… Bernie Volz (volz)
- Re: [dhcwg] Call for Adoption, draft-troan-dhc-dh… STARK, BARBARA H
- Re: [dhcwg] Adopt draft-troan-dhc-dhcpv6-stateful… Bud Millwood
- [dhcwg] Fwd: Call for Adoption, draft-troan-dhc-d… Ted Lemon
- Re: [dhcwg] Fwd: Call for Adoption, draft-troan-d… Weil, Jason
- Re: [dhcwg] Fwd: Call for Adoption, draft-troan-d… Tomek Mrugalski
- Re: [dhcwg] Fwd: Call for Adoption, draft-troan-d… Ted Lemon
- Re: [dhcwg] Fwd: Call for Adoption, draft-troan-d… Leaf yeh
- Re: [dhcwg] Call for Adoption, draft-troan-dhc-dh… Ted Lemon