Re: [dhcwg] Tentative agenda for dhc WG meeting at IETF 61
Daniel Park <soohong.park@samsung.com> Mon, 08 November 2004 00:55 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 TAA17381; Sun, 7 Nov 2004 19:55:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQxjx-0005ND-ON; Sun, 07 Nov 2004 19:50:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQxcQ-0004aG-Fh for dhcwg@megatron.ietf.org; Sun, 07 Nov 2004 19:42:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15931 for <dhcwg@ietf.org>; Sun, 7 Nov 2004 19:42:46 -0500 (EST)
Received: from mailout3.samsung.com ([203.254.224.33]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQxcr-0000tv-0j for dhcwg@ietf.org; Sun, 07 Nov 2004 19:43:17 -0500
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0I6U0086M4LM0U@mailout3.samsung.com> for dhcwg@ietf.org; Mon, 08 Nov 2004 09:41:46 +0900 (KST)
Received: from ep_ms3_bk (mailout3.samsung.com [203.254.224.33]) by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0I6U00CD73J4IO@mailout3.samsung.com> for dhcwg@ietf.org; Mon, 08 Nov 2004 09:18:40 +0900 (KST)
Received: from localhost (ms3.samsung.com [203.254.225.112]) by ms3.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with SMTP id <0I6U00HSF3J435@ms3.samsung.com> for dhcwg@ietf.org; Mon, 08 Nov 2004 09:18:40 +0900 (KST)
Date: Mon, 08 Nov 2004 00:18:35 +0000
From: Daniel Park <soohong.park@samsung.com>
Subject: Re: [dhcwg] Tentative agenda for dhc WG meeting at IETF 61
X-Sender: Samsung Electronics?Mobile Platform Lab?Engineer
To: Ralph Droms <rdroms@cisco.com>, soohong.park@samsung.com
Message-id: <2983078.1099873111651.JavaMail.weblogic@ep_app32>
MIME-version: 1.0
Content-type: text/plain; charset="windows-1252"
Content-transfer-encoding: 7bit
X-Priority: 3
Msgkey: 20041108001831649@soohong.park
X-MTR: 20041108001831649@soohong.park
X-EPLocale: en_US.windows-1252
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-Spam-Score: 0.8 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Content-Transfer-Encoding: 7bit
Cc: "dhcwg@ietf.org " <dhcwg@ietf.org>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: soohong.park@samsung.com
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
Content-Transfer-Encoding: 7bit
Just for clarifying on below discussion prior to presenting it. Multicast Reconfig. Protocol for Stateless DHCPv6 Daniel Park 10 minutes <draft-vijay-dhc-dhcpv6-mcast-reconf> Technical discussion This protocol is for providing reconfiguration in the stateless DHCPv6 domain when any configuration information is changed and initial version was presented at Seoul meeting. This protocol uses a RA message to trigger a client to initiate Renew/Reply or Information-Request/Reply by which it can obtain the updated configuration information. Regarding this protocol, I think we should make sure one related draft which aims M and O flag of RA to be clarified and it was officially accepted as IPv6 WG work item. This draft defines three DHCP policies for each flag. For more detail understanding, please read below draft. http://www.watersprings.org/pub/id/draft-daniel-ipv6-ra-mo-flags-01.txt What I am trying to say is that this reconf protocol is only applied to both O-Policy 1 and 2 not 3 since O-Policy 3 does not invoke any configuration scheme regardless of flag change. Moreover, initial version proposed a new ICMPv6 option to inform the information change to the client, however it is just applied for O-Policy 2. If O-Policy 1 is enabled, the client can invoke the reconfiguration scheme regardless of change of flag or any new option. Now, I think it should be discussed during this meeting if this protocol is of interest... Please take a look at the M&O flag document and let me know your comments and thoughts... Thanks Daniel (Soohong Daniel Park) Mobile Platform Laboratory. SAMSUNG Electronics ------- Original Message ------- Sender : Ralph Droms<rdroms@cisco.com> Date : Nov 07, 2004 09:25 Title : [dhcwg] Tentative agenda for dhc WG meeting at IETF 61 Here is yet another latest draft agenda for the dhc WG meeting at IETF 61. - Ralph DHC WG agenda - IETF 61 0900 Tue 2004-11-09 (tentative) (Last revised 2004-11-06 07:20 PM ET) ------------------------------------- Administrivia Ralph Droms 10 minutes Agenda bashing; blue sheets; scribe; Jabber scribe Request for milestones for dhc WG drafts DNS zone suffix option for DHCPv6 Renxiang Yan 10 minutes <draft-yan-dhc-dhcpv6-opt-dnszone> Accept as dhc WG work item? Reclassifying DHCPv4 Options Bernie Volz 10 minutes <draft-ietf-dhc-reclassify-options> How to implement the process after RFC is published? Vendor-Specific Information Suboption Mark Stapp 10 minutes <draft-stapp-dhc-vendor-suboption> Ready for WG last call? DHCP Authentication via EAP Mark Stapp 10 minutes Technical discussion Lifetime Option for DHCPv6 Stig Venaas 10 minutes <draft-ietf-dhc-lifetime> Ready for WG last call? Multicast Reconfig. Protocol for Stateless DHCPv6 Daniel Park 10 minutes <draft-vijay-dhc-dhcpv6-mcast-reconf> Technical discussion Anycast Address Assignment using DHCPv6 Syam Madanapalli 10 minutes <draft-madanapalli-dhcpv6-anycast> Accept as dhc WG work item? Source Address Selection Policy option for DHCPv6 T. Fujisaki 10 minutes <draft-hirotaka-dhc-source-address-selection-opt> Accept as dhc WG work item? DHCPv6 Relay Agent Information Option Wing Cheong Lau 10 minutes <draft-droms-dhc-v6-relayopt> Accept as dhc WG work item? DHCP Relay Agent Opt for MIPv6 bootstrapping Kuntal Chowdhury 10 minutes <draft-chowdhury-dhc-mip6-agentop> Accept as dhc WG work item? Clarifications on DHCPv6 Authentication T. Jinmei 10 minutes <draft-ietf-dhc-dhcpv6-clarify-auth> Technical discussion DHCP-DNS interaction Bernie Volz 30 minutes <draft-ietf-dhc-dhcpv6-fqdn> <draft-ietf-dhc-fqdn-option> <draft-ietf-dhc-ddns-resolution> Technical discussion ----------- 150 minutes _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Tentative agenda for dhc WG meeting at IE… Ralph Droms
- [dhcwg] Tentative agenda for dhc WG meeting at IE… Ralph Droms
- [dhcwg] Tentative agenda for dhc WG meeting at IE… Ralph Droms
- [dhcwg] Tentative agenda for dhc WG meeting at IE… Ralph Droms
- Re: [dhcwg] Tentative agenda for dhc WG meeting a… Syam Madanapalli
- [dhcwg] Tentative agenda for dhc WG meeting at IE… Ralph Droms
- [dhcwg] Tentative agenda for dhc WG meeting at IE… Ralph Droms
- Re: [dhcwg] Tentative agenda for dhc WG meeting a… JINMEI Tatuya / 神明達哉
- [dhcwg] Tentative agenda for dhc WG meeting at IE… Ralph Droms
- [dhcwg] Tentative agenda for dhc WG meeting at IE… Ralph Droms
- Re: [dhcwg] Tentative agenda for dhc WG meeting a… Daniel Park