Re: [dhcwg] Moving SeDHCPv6 forward
Ted Lemon <Ted.Lemon@nominum.com> Sat, 21 March 2015 20:45 UTC
Return-Path: <Ted.Lemon@nominum.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 4F7501A90C5 for <dhcwg@ietfa.amsl.com>; Sat, 21 Mar 2015 13:45:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.61
X-Spam-Level:
X-Spam-Status: No, score=-1.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] autolearn=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 aEQOYKUI7swu for <dhcwg@ietfa.amsl.com>; Sat, 21 Mar 2015 13:45:20 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 AE94B1A8AB6 for <dhcwg@ietf.org>; Sat, 21 Mar 2015 13:45:20 -0700 (PDT)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 5FCF2DA00B1; Sat, 21 Mar 2015 20:45:20 +0000 (UTC)
Received: from [192.168.5.108] (107.19.189.88) by CAS-03.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.224.2; Sat, 21 Mar 2015 13:45:06 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <CAJE_bqeZE-8nNrs-htvUEqG_KHjLu3CFE31Ve9-CvfHNtx4qhg@mail.gmail.com>
Date: Sat, 21 Mar 2015 16:43:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <CA7DA240-8AC1-46E0-BEAB-DB3F03EBA20B@nominum.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923B05E058@nkgeml512-mbx.china.huawei.com> <CAJE_bqeZE-8nNrs-htvUEqG_KHjLu3CFE31Ve9-CvfHNtx4qhg@mail.gmail.com>
To: 神明達哉 <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [107.19.189.88]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/o06OQNrk-LImOvomoKtQodOVTdk>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Moving SeDHCPv6 forward
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: Sat, 21 Mar 2015 20:45:21 -0000
I would be really happy to see some more detail about the use cases that we've talked about and understand. The reason I pushed back earlier is that the use cases that were described in the draft that was submitted for publication were theoretical and didn't make sense to me. So I certainly don't object to some concrete use cases that we can describe clearly and that would actually be useful, and I think the cases you're talking about in your point A qualify. I think your point B is worth pursuing if it can be done, but should be considered optional. We should not document anything that we don't clearly understand how to use. But I agree that in principle this is worth doing, and would be happy to help try to do it. To your point C, I think this is not a bad idea, but it may be better to talk about general processing rules separately from processing rules for specific use cases that we've identified. I agree with point D, obviously. :)
- [dhcwg] Moving SeDHCPv6 forward Sheng Jiang
- Re: [dhcwg] Moving SeDHCPv6 forward 神明達哉
- Re: [dhcwg] Moving SeDHCPv6 forward Templin, Fred L
- Re: [dhcwg] Moving SeDHCPv6 forward 神明達哉
- Re: [dhcwg] Moving SeDHCPv6 forward Templin, Fred L
- Re: [dhcwg] Moving SeDHCPv6 forward 神明達哉
- Re: [dhcwg] Moving SeDHCPv6 forward Templin, Fred L
- Re: [dhcwg] Moving SeDHCPv6 forward Ted Lemon
- Re: [dhcwg] Moving SeDHCPv6 forward Templin, Fred L
- Re: [dhcwg] Moving SeDHCPv6 forward Ted Lemon
- Re: [dhcwg] Moving SeDHCPv6 forward Templin, Fred L
- Re: [dhcwg] Moving SeDHCPv6 forward Ted Lemon
- Re: [dhcwg] Moving SeDHCPv6 forward Robert Elz
- Re: [dhcwg] Moving SeDHCPv6 forward 神明達哉
- Re: [dhcwg] Moving SeDHCPv6 forward Ted Lemon
- Re: [dhcwg] Moving SeDHCPv6 forward 神明達哉
- Re: [dhcwg] Moving SeDHCPv6 forward Robert Elz
- Re: [dhcwg] Moving SeDHCPv6 forward Niall O'Reilly
- Re: [dhcwg] Moving SeDHCPv6 forward Robert Elz
- Re: [dhcwg] Moving SeDHCPv6 forward Ted Lemon
- Re: [dhcwg] Moving SeDHCPv6 forward 神明達哉
- Re: [dhcwg] Moving SeDHCPv6 forward Ted Lemon
- Re: [dhcwg] Moving SeDHCPv6 forward 神明達哉
- Re: [dhcwg] Moving SeDHCPv6 forward Templin, Fred L
- Re: [dhcwg] Moving SeDHCPv6 forward 神明達哉
- Re: [dhcwg] Moving SeDHCPv6 forward Ted Lemon
- Re: [dhcwg] Moving SeDHCPv6 forward 神明達哉