IETF 87 DHC WG Berlin, Germany Thursday, 1 August, 2013

Slides:



Advertisements
Similar presentations
Dynamic Allocation of Shared IPv4 Addresses draft-csf-dhc-dynamic-shared-v4allocation-00 Q. Sun, Y. Cui, I. Farrer, Y. Lee, Q. Sun, M. Boucadair IETF 89,
Advertisements

Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made.
1 Improved DNS Server Selection for Multi-Homed Nodes draft-savolainen-mif-dns-server-selection-04 Teemu Savolainen (Nokia) Jun-ya Kato (NTT) MIF WG meeting.
RFC 2131 DHCP. Dynamic Host Configuration Protocol.
SIP working group status Keith Drage, Dean Willis.
DHCP: Dual-Stack Issues draft-ietf-dhc-dual-stack-01 Tim Chown dhc WG, IETF 60, San Diego, August 2, 2004.
1 CMPT 471 Networking II DHCP Failover and multiple servers © Janice Regan,
The Future of DHCP Dr. Ralph Droms Bucknell University.
Dynamic Host Configuration Protocol Engr. Mehran Mamonai.
DIME WG IETF 82 Dime WG Agenda & Status THURSDAY, November 17, 2011 Jouni Korhonen & Lionel Morand.
Prefix Delegation Protocol Selection T.J. Kniveton MEXT Working Group IETF 70 - December ’07 - Vancouver.
1 Behcet Sarikaya Frank Xia Ted Lemon July 2011 DHCPv6 Prefix Delegation as IPv6 Migration Tool in Mobile Networks IETF 81
July 27, 2009IETF NEA Meeting1 NEA Working Group IETF 75 Co-chairs: Steve Hanna
IAB Report Technical Plenary IETF 81 July 25, 2011.
IETF #82 DRINKS WG Meeting Taipei, Taiwan Fri, Nov 18 th
EAI WG meeting IETF-65, March 20, Agenda 17:40 Welcome, blue sheet, scribe, agenda bashing 17:50 Review of WG charter (approved) 17:55 Problem/framing:
DHC WG IETF 55, 11/18/ /18/2002IETF 552 Agenda Administrivia, agenda bashingRalph Droms Use of IPsec for Securing DHCPv4 Messages Exchanged Between.
6bone address registry proposal Bob Fink ESnet 17 July 2002 Yokohama.
Exposing Source IP Address Type Requirements with DHCPv6 D. Moses, A. Yegin draft-moses-dmm-dhcp-ondemand-mobility-00.
ECRIT Virtual Interim Meeting 3rd June 2009, 1PM EDT (New York) Marc Linsner Hannes Tschofenig.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IETF Liaison Report Date Submitted: July 20, 2006 Presented at IEEE.
L3VPN WG IETF 78 30/07/ :00-11:30 Chairs: Marshall Eubanks Danny McPherson Ben Niven-Jenkins.
IETF-90 (Toronto) DHC WG Meeting Wednesday, July 23, GMT IETF-90 DHC WG1 Last Updated: 07/21/ :10 EDT.
File: /ram/wgchairs.sxi Date: 7 January, 2016 Slide 1 Process and Tools (PROTO) Team General Area Meeting IETF59, Seoul, Korea -- March 2004
1 MPLS Architectural Considerations for a Transport Profile ITU-T - IETF Joint Working Team Dave Ward, Malcolm Betts, ed. April 16, 2008.
July 2007 CAPWAP Protocol Specification Editors' Report July 2007
DHCP options for PAA Status report of draft-ietf-dhc-paa-option-01.txt Lionel Morand IETF-65, Dallas.
IETF-89 (London) DHC WG Meeting Monday, March 3, GMT IETF-89 DHC WG1 Last Updated: 02/27/ EST.
MODERN BoF Managing, Ordering, Distributing, Exposing, and Registering telephone Numbers IETF 92.
DHCPv4 option for PANA Authentication Agents draft-suraj-dhcpv4-paa-option-00.txt DHC/PANA WG IETF-63 France, Paris.
Dhc WG 3/2/2004, IETF 59, Seoul. 3/2/2004dhc WG - IETF 59, Seoul2 Agenda Administrivia, Agenda bashing Ralph Droms 05 minutes DHCP Option for Proxy Server.
Pseudowire And LDP-enabled Services (PALS) WG Status IETF-92 Dallas Co-Chairs: Stewart Bryant and Andy Malis
SIPPING Working Group IETF 67 Mary Barnes Gonzalo Camarillo.
ITU Liaison on T-MPLS Stewart Bryant
GGF-Process WG Administrative Information Process Working Group:ggf-proc-wg Chairs:"Tony Genovese" "Cees de Laat" Secretary/Webmaster:"Stacey Bruno"
SNMP (Simple Network Management Protocol) Overview
CLUE WG Interim Meeting San Jose, CA Sept , 2012
Emergency Context Resolution with Internet Technologies (ECRIT) Chairs: Marc Linsner & Roger Marshall Standing In for the Chairs: Brian Rosen IETF 94.
Discussion on DHCPv6 Routing Configuration
CLUE WG Interim Meeting San Jose, CA Sept , 2012
Objective: ARP.
Lightweight 4over6 deployment with DHCPv4 over DHCPv6
Lionel Morand DHCP options for PAA Lionel Morand
Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made.
IETF 86 Orlando MBONED.
TRILL Working Group TRansparent Interconnection of Lots of Links
SNMP (Simple Network Management Protocol) Overview
IP Telephony (iptel) IETF 56
Net 431 D: ADVANCED COMPUTER NETWORKS
Alignment of Part 4B with ISAE 3000
Proposal for IEEE 802.1CQ-LAAP
Working Group Re-charter Draft Charter Reference Materials
Proposal for IEEE 802.1CQ-LAAP
Wednesday, 9:30-12:00 Morning session I, Van Horne
Tuesday , 9:30-12:00 Morning session I, Buckingham
IEEE 802 JTC1 Standing Committee Proposal for SC6 contribution process
Proposal for IEEE 802.1CQ-LAAP
Allocating IP Addressing by Using Dynamic Host Configuration Protocol
MODULE B - PROCESS SUBMODULES B1. Organizational Structure
Overview Multimedia: The Role of DHCP in the Network Infrastructure
IEEE IMT-Advanced Review Process
IEEE IMT-Advanced Review Process
Technical Issues with draft-ietf-mpls-bfd-directed
IEEE IMT-Advanced Review Process
TG1 Draft Topics Date: Authors: September 2012 Month Year
Multiple Interfaces (MIF) WG
Alignment of Part 4B with ISAE 3000
IETF 103 Bangkok, Thailand - November 2018
IETF-104 (Prague) DHC WG Next steps
MIF DHCPv6 Route Option Update
Presentation transcript:

IETF 87 DHC WG Berlin, Germany Thursday, 1 August, 2013 DHC Recharter IETF 87 DHC WG Berlin, Germany Thursday, 1 August, 2013 11/2/2019 DHC WG – Re-charter & Directorate – Rev 1

DHC WG – Re-charter & Directorate – Rev 1 Current charter is from July 2003! DHC Co-chairs worked with Ted to redraft Proposed text sent to mailing list June 25th Kim Kinnear raised issue; resolved Discuss here and then submit to IESG for approval Milestones updated more recently (2009), but still very much out of date New version in development (author input solicited) Will be shared on mailing list in August 11/2/2019 DHC WG – Re-charter & Directorate – Rev 1

Proposed New Charter (1/3) The Dynamic Host Configuration working group (DHC WG) has developed DHCP for automated allocation, configuration and management of IP addresses and TCP/IP protocol stack parameters. DHCPv4 is currently a Draft Standard and is documented in RFC 2131 and RFC 2132. DHCPv6 is currently a Proposed Standard and is documented in RFC 3315. Subsequent RFCs document additional options and other enhancements to the specifications. The DHC WG is responsible for defining DHCP protocol extensions. Definitions of new DHCP options that are delivered using standard mechanisms with documented semantics are not considered a protocol extension and thus are outside of scope for the DHC WG. Such options should be defined within their respective WGs and reviewed by the DHCP Directorate. However, if such options require protocol extensions or new semantics, the protocol extension work must be done in the DHC WG. 11/2/2019 DHC WG – Re-charter & Directorate – Rev 1

Proposed New Charter (2/3) The DHC WG has the following main objectives: 1. Develop extensions to the DHCPv6 infrastructure as required to meet new applications and deployments of DHCP. The topics currently in development are: DHCPv6 Failover, High Availability and Load Balancing DNS Update strategies for delegated prefixes (draft-ietf-dhc-dns-pd) Extend DHCPv6 to work with multiple provisioning domains DHCP provisioning of IPv4 clients over IPv6 networks SOLMAXRT counter update Container option Access Network Identifier (draft-ietf-dhc-access-network-identifier) New NTP option to replace OPTION_NTP_SERVER (RFC 5908) Prefix coloring (draft-bhandari-dhc-class-based-prefix) Additional topics may only be added with approval from the responsible Area Director or by re-chartering. 11/2/2019 DHC WG – Re-charter & Directorate – Rev 1

Proposed New Charter (3/3) 2. Specify guidelines for creating new DHCPv6 options. 3. Develop documents that help explain operational considerations for the wider community. 4. Advance DHCPv6 (RFC 3315) along the IETF Standards Track. This will include writing analyses, corrections, and clarifications of the DHCPv6 specifications, including RFC 3315, RFC 3633, RFC 3736 and other RFCs defining additional options, which identifies and resolves ambiguities, contradictory specifications and other obstacles to development of interoperable implementations. 11/2/2019 DHC WG – Re-charter & Directorate – Rev 1

IETF 87 DHC WG Berlin, Germany Thursday, 1 August, 2013 DHCP Directorate IETF 87 DHC WG Berlin, Germany Thursday, 1 August, 2013 11/2/2019 DHC WG – Re-charter & Directorate – Rev 1

DHC WG – Re-charter & Directorate – Rev 1 Background Concept introduced by Ted Lemon at Orlando IETF to: help streamline the DHC WG workload, and provide assistance to and expedite other working groups developing “good” DHCP options. Since Orlando, Ted and the DHC WG co-chairs developed the a proposal for an DHCP Directorate (shared on mailing list on June 25). The Directorate concept is detailed in RFC 2418:   In many areas, the Area Directors have formed an advisory group or directorate.  These comprise experienced members of the IETF and the technical community represented by the area.  The specific name and the details of the role for each group differ from area to area, but the primary intent is that these groups assist the Area Director(s), e.g., with the review of specifications produced in the area. 11/2/2019 DHC WG – Re-charter & Directorate – Rev 1

DHC WG – Re-charter & Directorate – Rev 1 DHCP Directorate (1/5) The DHCP Directorate is an advisory group of DHCP experts selected by the Internet Area Directors. What Does the Directorate Do? The main purpose of the DHCP Directorate is to review all documents submitted to the IESG for publication that define new DHCP (DHCPv6 or DHCPv4) options, DHCP messages, or DHCP client, relay agent or server processing. Generally speaking, documents advanced by the DHC WG will have already received review from members of the DHCP Directorate and thus may not require such review. While the DHC WG is active, the DHCP Directorate is responsible for reviewing DHCP options or other extensions (for both IPv4 and IPv6). The Directorate 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. Generally speaking, the Directorate will not be responsible for evaluating the semantic content of proposed options. 11/2/2019 DHC WG – Re-charter & Directorate – Rev 1

DHC WG – Re-charter & Directorate – Rev 1 DHCP Directorate (2/5) The tasks performed by the Directorate are: 1. Review all documents submitted to the IESG for publication that have DHCP options, messages, or processing requirements. A review is triggered: By request for early review (by any AD or by any WG chair) By a document moving to 'publication requested' state By entry on the IESG agenda (for other documents) 2. Assist ADs with judgment issues when requested - The ADs may send email to the directorate list when they have issues that they want help with. Examples for judgment issues are: New option formats. New client, relay, server agent processing. 3. Try to follow IETF documents related to DHCP as early as possible and provide guidance to authors as early as possible. 11/2/2019 DHC WG – Re-charter & Directorate – Rev 1

DHC WG – Re-charter & Directorate – Rev 1 DHCP Directorate (3/5) How is Document Review Organized? 1. The DHCP Directorate Coordinator assigns each document that is triggered for review to at least two (2) reviewers and issues a Review Request. Authors and contributors to a document must not be assigned. The Review Request will include the document and review deadline. 2. The assigned reviewers must acknowledge and agree to review the document within 72 hours and respond with a "can review by deadline" or "can't review". No reply is interpreted as "can't review". 3. If the Coordinator does not receive "can review by deadline" within 72 hours, the Coordinator selects at least one or two additional reviewers. This process is repeated until at least two reviewers are found. 4. The reviewers provide comments as appropriate (IETF Last Call, Area Director, document authors). 5. The Coordinator may decide to call upon additional reviewers if expected review is overdue or the topic under review is a complex one. 11/2/2019 DHC WG – Re-charter & Directorate – Rev 1

DHC WG – Re-charter & Directorate – Rev 1 DHCP Directorate (4/5) How is the Directorate Formed? 1. Directorate members are assigned to the Directorate by the Internet Area Directors. 2. There is an expectation that Directorate membership will not be limited to 'old-time DHCP gods from years past'. It is assumed that the Directorate will include younger and newer participants who are interested in 'learning while doing work'. 3. Each assignment is for a three year term, unless the member or Internet Area Director requests a shorter term. 4. The terms are staggered so that approximately 1/3 of the directorate members have their term end each year. 5. When the Directorate is first established members of the Directorate will be assigned either one year, two years, or three years in their first term. 6. When a member's term expires, the Internet ADs may replace the person whose term expires, may reappoint the same person, or may reduce the size of the Directorate. There is no expectation that the same person will either want to be returned, or will be returned. 7. The three year term serves as the limit of the commitment of a Directorate member, but also serves as a way to return Directorate members to the community. 11/2/2019 DHC WG – Re-charter & Directorate – Rev 1

DHC WG – Re-charter & Directorate – Rev 1 DHCP Directorate (5/5) How is the Directorate Formed? (Continued) 8. In deciding whether to reappoint a member whose term has expired, the Internet ADs may consider the quantity of work that they have done, the ADs' impression of the quality of the work, and the comments from the authors and other Directorate members regarding the reviews. 9. If a member resigns before the member's term expires, the Internet Area Directors may appoint a replacement. 10. The Internet Area Directors may remove a member before the member's term expires, and may appoint a replacement. 11. Internet ADs can assign additional members to the Directorate whenever they want to, subject to willingness of people to serve. 12. Both ADs need to agree in order to assign a member to the Directorate. 13. Both ADs select one of the Directorate members as the DHCP Directorate Coordinator on a yearly basis. 11/2/2019 DHC WG – Re-charter & Directorate – Rev 1