Re: [dhcwg] *DRAFT* Agenda for dhc WG meeting in San Diego

JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Fri, 09 July 2004 14:42 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03132; Fri, 9 Jul 2004 10:42:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Biw70-0003OG-9O; Fri, 09 Jul 2004 10:12:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BivfA-0003YF-HZ for dhcwg@megatron.ietf.org; Fri, 09 Jul 2004 09:43:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27199 for <dhcwg@ietf.org>; Fri, 9 Jul 2004 09:43:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bivf4-0001R8-Mo for dhcwg@ietf.org; Fri, 09 Jul 2004 09:43:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bive9-000198-00 for dhcwg@ietf.org; Fri, 09 Jul 2004 09:42:38 -0400
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx with esmtp (Exim 4.12) id 1Bivdd-0000qc-00 for dhcwg@ietf.org; Fri, 09 Jul 2004 09:42:06 -0400
Received: from ocean.jinmei.org (unknown [2001:200:0:8002:adbf:fe5a:f394:422f]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 753AE15272; Fri, 9 Jul 2004 22:42:03 +0900 (JST)
Date: Fri, 09 Jul 2004 22:42:01 +0900
Message-ID: <y7vvfgx1emu.wl@ocean.jinmei.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
To: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] *DRAFT* Agenda for dhc WG meeting in San Diego
In-Reply-To: <4.3.2.7.2.20040708155658.0290b6f8@flask.cisco.com> <y7vhdskgmuc.wl@ocean.jinmei.org>
References: <4.3.2.7.2.20040708155658.0290b6f8@flask.cisco.com>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: multipart/mixed; boundary="Multipart_Fri_Jul__9_22:42:01_2004-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

>>>>> On Thu, 08 Jul 2004 15:59:03 -0400, 
>>>>> Ralph Droms <rdroms@cisco.com> said:

> Below is the draft scheduled time and agenda for the dhc WG meeting in San
> Diego.  NOTE THAT THE MEETING DAY HAS CHANGED TO WEDNESDAY!!  Let me know if
> you have additional items for the agenda.

As I asked the other day, I'm wondering if we can discuss DHCPv6
authentication issues in San Diego (attached below).

I'm almost done on writing a short internet-draft discussing the
issues.  Regardless of whether the request is accepted, I'll submit it
before the initial cut-off date on July 12th.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

--- Begin Message ---
>>>>> On Mon, 21 Jun 2004 18:48:44 -0400, 
>>>>> Ralph Droms <rdroms@cisco.com> said:

> Below is the draft scheduled time and agenda for the dhc WG meeting in San 
> Diego.  Let me know if you have additional items for the agenda.

Does it make sense to discuss (possible) clarifications on the
authentication mechanism of DHCPv6 (RFC3315)?  I raised some questions
the other day (*), and, according to the succeeding messages, there
seem to be some issues that need further discussion.  But I'm not sure
if my questions are valid in the first place since I've not seen any
responses from the RFC3315 authors.

If this is worth a discussion, I'll try to find time to make a very
short draft summarizing the issues, and will ask for a short slot in
the meeting.

(*) http://www1.ietf.org/mail-archive/web/dhcwg/current/msg03645.html

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg
--- End Message ---
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg