IETF Logo Mail Archive

Re: [dhcwg] *DRAFT* dhc WG agenda

Jari Arkko <jari.arkko@piuha.net> Fri, 25 July 2008 17:02 UTC

Return-Path: <dhcwg-bounces@ietf.org>
X-Original-To: dhcwg-archive@megatron.ietf.org
Delivered-To: ietfarch-dhcwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D839528C104; Fri, 25 Jul 2008 10:02:01 -0700 (PDT)
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F54228C104 for <dhcwg@core3.amsl.com>; Fri, 25 Jul 2008 10:02:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level:
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XTZOvQ7W+tCi for <dhcwg@core3.amsl.com>; Fri, 25 Jul 2008 10:01:59 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 52F1F3A6838 for <dhcwg@ietf.org>; Fri, 25 Jul 2008 10:01:59 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id C84C519870F; Fri, 25 Jul 2008 20:02:00 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 0A4CA1986E3; Fri, 25 Jul 2008 20:01:37 +0300 (EEST)
Message-ID: <4889C6F4.9070902@piuha.net>
Date: Fri, 25 Jul 2008 15:28:36 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.14 (X11/20080505)
MIME-Version: 1.0
To: Ralph Droms <rdroms@cisco.com>
References: <DC113ED5-44B8-4F3E-87EE-EA3855C0B558@cisco.com>
In-Reply-To: <DC113ED5-44B8-4F3E-87EE-EA3855C0B558@cisco.com>
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: DHC WG <dhcwg@ietf.org>, Dhc Chairs <dhc-chairs@tools.ietf.org>
Subject: Re: [dhcwg] *DRAFT* dhc WG agenda
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

>
> Secure DHCPv6 using CGA                         S. Jiang         10 
> minutes
>   <draft-jiang-dhc-Secure-DHCPv6-00>
>   Initial WG review; accept as WG work item?

Note that we have another WG, CSI, whose charter has a work item on 
securing DHCP with CGA. Or to be more exact, producing first a design 
analysis before actually picking a solution.

As a result, I don't think we want to adopt this document in the DHC WG.

But don't take this as a suggestion to avoid the discussion! The 
discussion on the list has been useful, and we should also talk about it 
in the meeting. Has a slot been requested from CSI?

Jari


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg

v2.37.1 | Report a Bug | By Email | System Status