1 / 16

dhc WG

dhc WG. 3/2/2004, IETF 59, Seoul. Agenda. Administrivia, Agenda bashing Ralph Droms 05 minutes DHCP Option for Proxy Server Configuration Vijay AK 03 minutes <draft-ietf-dhc-proxyserver-opt-00> Technical discussion; ready for WG last call?

treva
Download Presentation

dhc WG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. dhc WG 3/2/2004, IETF 59, Seoul

  2. Agenda Administrivia, Agenda bashing Ralph Droms 05 minutes DHCP Option for Proxy Server Configuration Vijay AK 03 minutes <draft-ietf-dhc-proxyserver-opt-00> Technical discussion; ready for WG last call? The Extended Remote Boot Option for DHCPv4 Vijay AK 03 minutes <draft-ietf-dhc-opt-extrboot-00> Technical discussion; ready for WG last call? Vendor-Identifying Vendor Options for DHCPv4 Ralph Droms 03 minutes <draft-ietf-dhc-vendor-01> Technical discussion; ready for WG last call? Requirements for Proposed Changes to DHCPv4 <TBD> 03 minutes <draft-ietf-dhc-changes-00> Technical discussion; ready for WG last call? Node-Specific Client Identifiers for DHCPv4 Ted Lemon 03 minutes <draft-ietf-dhc-3315id-for-v4-01> Technical discussion; ready for WG last call? Rapid Commit Option for DHCPv4 Ralph Droms 03 minutes <draft-ietf-dhc-rapid-commit-opt-00> Technical discussion; ready for WG last call? DHCPv6 Support for Remote Boot Vijay AK 03 minutes <draft-ietf-dhc-dhcpv6-opt-rboot-00> Technical discussion; ready for WG last call? Configured Tunnel End Point Option for DHCPv6 S D Park 03 minutes <draft-ietf-dhc-dhcpv6-ctep-opt-01> Technical discussion; ready for WG last call? Reclassifying DHCPv4 Options Ralph Droms 03 minutes <draft-ietf-dhc-reclassify-options-00> Technical discussion; ready for WG last call? dhc WG - IETF 59, Seoul

  3. Agenda (2) DHCPv4 Support for Conf. IPv6-in-IPv4 Tunnels S D Park 05 minutes <draft-daniel-dhc-ipv6in4-tunnels-00> Accept as WG work item? Micro-block IP Addr. Alloc. With DHCP Proxy Server Naiming Shen 05 minutes <draft-shen-dhc-block-alloc-01> Accept as WG work item? Vendor-Specific Suboption for the DHCP RAIO Ralph Droms 05 minutes <draft-stapp-dhc-vendor-suboption-00> Accept as WG work item? Renumbering Requirements for Stateless DHCPv6 Stig Venaas 10 minutes <draft-chown-dhc-stateless-dhcpv6-renumbering-00> Accept as WG work item? Lifetime Option for DHCPv6 Stig Venaas 10 minutes <draft-venaas-dhc-lifetime-01> Accept as WG work item? Multicast Reconf. Protocol for Stateless DHCPv6 Vijay AK 10 minutes <draft-vijay-dhc-dhcpv6-mcast-reconf-00> Accept as WG work item? dhc WG - IETF 59, Seoul

  4. Agenda (3) Introduction to dual-stack (DHCPv4/DHCPv6) issues Ralph Droms 05 minutes IPv4 and IPv6 Dual-Stack Issues for DHCPv6 Stig Venaas 20 minutes <draft-chown-dhc-dual-stack-00> Accept as WG work item? DHCPv6 IPv4 Information Options <TBD> 10 minutes <draft-cadar-dhc-dhcpv6-v4options-00> Accept as WG work item? Update of dhc WG charter Ralph Droms 15 minutes Update on IPR issue with two drafts Ralph Droms 15 minutes dhc WG - IETF 59, Seoul

  5. Vendor-Specific Suboption for the DHCP RAIO • draft-stapp-dhc-vendor-suboption-00 • Provides same function as vendor-specific options in client-server messages • Encoded like vendor-identifying options dhc WG - IETF 59, Seoul

  6. Dual-stack issues • Pose issues briefly • How do dual-stack hosts configure IPv4 and IPv6 parameters? • Client: • One or two clients • Merging configuration from multiple sources • Server: • One or two servers • Management coordination and complexity • Internet Draft describes issues • WG will consider issues and alternatives and come to consensus on solution dhc WG - IETF 59, Seoul

  7. Charter • WG needs to review charter for progress, consider update to charter for new work (renumbering for stateless DHCPv6, dual stack issues)?, update milestones • Will look at major pieces of charter independently dhc WG - IETF 59, Seoul

  8. Charter – part 1 • The dhc working group (DHC WG) has developed DHCP for automated allocation, configuration and management of IP addresses and TCP/IP protocol stack parameters. DHCP is currently a "Draft Standard". The base protocol is documented in RFC2131 and RFC2132 (DHCP for IPv4) and RFCxxxx (DHCP for IPv6). Additional options are documented in subsequent RFCs. dhc WG - IETF 59, Seoul

  9. Charter – part 2 • The DHC WG is responsible for reviewing (and sometimes developing) DHCP options or other extensions (for both IPv4 and IPv6). The DHC WG is expected to review all proposed extensions to DHCP to ensure that they are consistent with the DHCP specification and other option formats, that they do not duplicate existing mechanisms, etc. The DHC WG will not (generally) be responsible for evaluating the semantic content of proposed options. The DHC WG will not adopt new proposals for extensions to DHCP as working group documents without first coordinating with other relevant working groups and determining who has the responsibility for reviewing the semantic content of an option. dhc WG - IETF 59, Seoul

  10. Charter – DHCP Security The DHC WG will address security in DHCP • Develop and document security requirements for DHCP. RFC 3118 defines current security mechanisms for DHCPv4. Unfortunately, RFC 3118 has neither been implemented nor deployed to date. Specific issues to be considered include: • Improved key management and scalability • Security for messages passed between relay agents and servers • Threats of DoS attacks through FORCERENEW • The increased usage of DHC on unsecured (e.g., wireless) and public LANs • The need for clients to be able to authenticate servers, without simultaneously requiring client authentication by the server. • Develop and document a roadmap of any new documents or protocols needed to meet the security requirements for DHCP dhc WG - IETF 59, Seoul

  11. Review RFC 2131, RFC 2132 • Write an analysis of the DHCP specification, including RFC2131, RFC2132 and other RFCs defining additional options, which identifies ambiguities, contradictory specifications and other obstacles to development of interoperable implementations. Recommend a process for resolving identified problems and incorporating the resolutions into the DHCP specification. dhc WG - IETF 59, Seoul

  12. Work in progress options • (long list of Internet Drafts) dhc WG - IETF 59, Seoul

  13. New charter items? • Stateless DHCpv6 renumbering • Dual stack issues dhc WG - IETF 59, Seoul

  14. Milestones Feb 03 Submit DHCP Options for Internet Storage Name Service to IESG (draft-ietf-dhc-isnsoption-03.txt) Feb 03 Submit DNS Configuration options for DHCPv6 to IESG (draft-ietf-dhc-dhcpv6-opt-dnsconfig-01.txt) Feb 03 Submit NIS Configuration Options for DHCPv6 to IESG (draft-ietf-dhc-dhcpv6-opt-nisconfig-01.txt) Feb 03 Submit Time Configuration Options for DHCPv6 to IESG (draft-ietf-dhc-dhcpv6-opt-timeconfig-01.txt) Mar 03 Submit IPv6 Prefix Options for DHCPv6 to IESG (draft-troan-dhcpv6-opt-prefix-delegation-02.txt) Mar 03 Submit Load Balancing for DHCPv6 to IESG (draft-ietf-dhc-dhcpv6-loadb-02.txt) dhc WG - IETF 59, Seoul

  15. New Milestones? dhc WG - IETF 59, Seoul

  16. IPR Issues • New RFCs with text about IPR: • RFC 3667: IETF Rights in Contributions • RFC 3668: IPR in IETF Technology • RFC 3669: Guidelines for WGs on IPR Issues • WG members should review these documents; impacts outside current IPR issues • Discussion? dhc WG - IETF 59, Seoul

More Related