WG Review: Recharter of Dynamic Host Configuration WG (dhc)

[IESG Secretary <iesg-secretary at ietf.org>]

A modified charter has been submitted for the Dynamic Host Configuration
(dhc) working group in the Internet Area of the IETF. The IESG has not
made any determination as yet.  The modified charter is provided below 
for informational purposes only.  Please send your comments to the IESG 
mailing list (iesg at ietf.org) by October 16.

Dynamic Host Configuration (dhc)
================================

Current Status: Active Working Group

Chair(s):
Ralph Droms <rdroms at cisco.com> 
Stig Venaas <venaas at uninett.no> 

Internet Area Director(s):
Jari Arkko <jari.arkko at piuha.net> 
Mark Townsley <townsley at cisco.com> 

Internet Area Advisor:
Jari Arkko <jari.arkko at piuha.net> 

Mailing Lists:
General Discussion: dhcwg at ietf.org
To Subscribe: http://www1.ietf.org/mailman/listinfo/dhcwg
Archive: http://www.ietf.org/mail-archive/web/dhcwg/index.html

The dhc 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 reviewing 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. Generally speaking, the DHC WG
will not be responsible for evaluating the semantic content of
proposed options. Similarly, the ownership of specifications typically
belongs the relevant working group that needs more functionality from
DHCP, not the DHC WG. The DHC WG coordinates reviews of the proposed
options together with those working groups. It is required that those
working groups have consensus to take on the work and that the work is
within their charter. Exceptionally, with AD agreement, this same
process can also be used for Individual Submissions originating
outside WGs.

However, the DHC WG can in some cases develop its own options that
relate to either maintenance of existing specifications or
improvements in the operation of the DHCP infrastructure itself.

The DHC WG has the following main objectives:

* Develop extensions to the DHCP infrastructure as required to meet
new applications and deployments of DHCP. The topics currently
in development are:

- Subnet allocation mechanisms
- Virtual subnet identification option
- Option for passing DNS domain information in DHCPv6
- DHCP relay agent assignment notification in DHCPv6
- Option for DHCPv6 server reply sequence numbers
- Rebinding capability for DHCPv6 Reconfigure messages
| - Behavior of layer 2 relay agents

The adoption of new items requires explicit agreement from
the AD or rechartering.

* Write analyses of the DHCPv4 and DHCPv6 specifications,
including RFC 2131, RFC 2132, RFC 3315 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.

Secondly, advance DHCPv4 (RFC 2131 and RFC 2132) and DHCPv6 (RFC
3315) in IETF Standards Track.

Thirdly, specify guidelines for creating new DHCP options, and
report on the status of DHCPv4 option reclassification.

* Assess the requirements for a dual-stack host to use DHCP to obtain
configuration settings for both IPv4 and IPv6. Hosts that include
implementations of both IPv4 and IPv6 ("dual-stack hosts") may use
DHCP to obtain configuration settings (including assigned addresses)
for both IPv4 and IPv6. The DHCPv4 and DHCPv6 specifications (RFC
2131, RFC 2132, RFC 3315 and subsequent RFCs) do not explicitly
explain how a dual-stack host uses DHCP to obtain configuration
settings for both IP stacks. The DHC WG will evaluate solutions for
configuration of dual-stack hosts through DHCP and select a solution
that will be developed and published by the WG.

* Hold a discussion whether on-link prefix information and default
router information is needed in DHCP in addition to router
advertisements. Actual solutions are out of scope for the WG,
however.

Milestones:

Done WG last call for "Subnet Allocation Option"
<draft-ietf-dhc-subnet-alloc-04>
Done WG last call on "Virtual Subnet Selection Option",
<draft-ietf-dhc-vpn-option>
Oct 07 Submit "Subnet Allocation Option"
<draft-ietf-dhc-subnet-alloc-04> to IESG
for Proposed Standard
Nov 07 WG last call on "Guidelines for Creating New DHCP Options"
<draft-ietf-dhc-option-guidelines>
Nov 07 Submit "Virtual Subnet Selection Option",
<draft-From ietf-announce-bounces at ietf.org Tue Oct 09 15:44:21 2007
Return-path: <ietf-announce-bounces at ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IfKYT-0005oZ-Vg; Tue, 09 Oct 2007 15:15:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IfKYR-0005m3-1D; Tue, 09 Oct 2007 15:15:43 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IfKYQ-0003Yv-Il; Tue, 09 Oct 2007 15:15:42 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 448B7175AB;
	Tue,  9 Oct 2007 19:15:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IfKXl-00012n-Q6; Tue, 09 Oct 2007 15:15:01 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: ietf-announce at ietf.org
From: IESG Secretary <iesg-secretary at ietf.org>
Message-Id: <E1IfKXl-00012n-Q6 at stiedprstage1.ietf.org>
Date: Tue, 09 Oct 2007 15:15:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: Spencer Shepler <spencer.shepler at sun.com>,
	Brian Pawlowski <beepy at netapp.com>, nfsv4 at ietf.org
Subject: WG Review: Recharter of Network File System Version 4 WG (nfsv4) 
X-BeenThere: ietf-announce at ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg at ietf.org
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>,
	<mailto:ietf-announce-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce at ietf.org>
List-Help: <mailto:ietf-announce-request at ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>,
	<mailto:ietf-announce-request at ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces at ietf.org

A modified charter has been submitted for the Network File System
Version 4 (nfsv4) working group in the Transport Area of the IETF.  
The IESG has not made any determination as yet. The modified charter is
provided below for informational purposes only. Please send your 
comments to the IESG mailing list (iesg at ietf.org) by October 16.

+++

Network File System Version 4 (nfsv4)
======================================

Current Status: Active Working Group

Chair(s):
Brian Pawlowski <beepy at netapp.com> 
Spencer Shepler <spencer.shepler at sun.com> 

Transport Area Director(s):
Magnus Westerlund <magnus.westerlund at ericsson.com> 
Lars Eggert <lars.eggert at nokia.com> 

Transport Area Advisor:
Lars Eggert <lars.eggert at nokia.com> 

Mailing Lists:
General Discussion: nfsv4 at ietf.org
To Subscribe: https://www1.ietf.org/mailman/listinfo/nfsv4
Archive: http://www.ietf.org/mail-archive/web/nfsv4/index.html

Description of Working Group:


NFS Version 4 is the IETF standard for file sharing. To maintain
the utility and currency of NFS Version 4, the working group is
chartered to maintain the existing NFSv4 and related specifications,
such as RPC and XDR and progress these specifications along the
standards track. The group is also chartered to design an NFSv4.1
minor-version extension that adds a carefully-selected set of
features

The current charter items are:

(1) NFS Version 4 Maintenance

Under this charter item, the WG correct errors and ambiguities in
the protocol currently specified in RFC 3530 and advances it along
the standards track. Extensions of any other kind are out of scope
under this charter item.

(2) NFS Version 4 Minor Version

NFS Version 4 contains within it the capability for minor versioning.
Under this charter item, the WG develops a minor-version extension
to NFSv4 that includes the following feature additions:

- improve correctness around non-idempotent operations

- enable delegation reclaims

- support clustered file server deployments as defined by
Parallel NFS (pNFS)

(3) RPC and XDR protocol maintenance

The NFSv4 protocol depends on two related specifications: ONC RPC
and XDR. Similar to charter item (1), the WG corrects errors and
ambiguitietf-dhc-vpn-option> and <draft-ietf-dhc-agent-vpn-id>
to IESG for Proposed Standard
Dec 07 WG last call for "Domain Suffix Option for DHCPv6"
<draft-ietf-dhc-dhcpv6-opt-dnsdomain>
Jan 08 Submit "Domain Suffix Option for DHCPv6"
<draft-ietf-dhc-dhcpv6-opt-dnsdomain> to IESG
for Proposed Standard
Jan 08 Submit "Guidelines for Creating New DHCP Options"
<draft-ietf-dhc-option-guidelines> to IESG for Best Current
Practice
Jan 08 Develop plan for advancing DHCPv4 and DHCPv6; plan to include
completion of DHCPv4 specification review report,
"Implementation Issues with RFC 2131"
<draft-ietf-dhc-implementation-02> for Informational
Feb 08 WG last call for "Status of Reclassifying DHCPv4 Options"
<draft-ietf-dhc-status-3942-00>
Feb 08 WG last call for "Dual-stack clients and merging of data from
DHCPv4 and DHCPv6" <draft-ietf-dhc-dual-stack-merge-01.txt>;
waiting for more experience with IPv6 deployment
Feb 08 WG last call for "Rebind Capability in DHCPv6 Reconfigure
Messages" <draft-ietf-dhc-dhcpv6-reconfigure-rebind-00>
Mar 08 Submit "Status of Reclassifying DHCPv4 Options"
<draft-ietf-dhc-status-3942-00> to IESG for Informational
Apr 08 2nd WG last call for "DHCP Relay Agent Assignment Notification
Option" <draft-ietf-dhc-dhcpv6-agentopt-delegate-01> and
"DHCPv6 Server Reply Sequence Number Option"
<draft-ietf-dhc-dhcpv6-srsn-option-00>
May 08 Submit "Rebind Capability in DHCPv6 Reconfigure Messages"
<draft-ietf-dhc-dhcpv6-reconfigure-rebind-00> to IESG for
Proposed Standard
Jun 08 WG last call on "Layer 2 Relay Agent Behaviour"
<draft-ietf-dhc-layer2-relay-agent-00>
Jul 08 Submit "Layer 2 Relay Agent Behaviour" to IESG
<draft-ietf-dhc-layer2-relay-agent-00> for Informational
Jul 08 Submit "DHCP Relay Agent Assignment Notification Option"
<draft-ietf-dhc-dhcpv6-agentopt-delegate-01> and "DHCPv6 Server
Reply Sequence Number Option"
<draft-ietf-dhc-dhcpv6-srsn-option-00> to IESG for
Proposed Standard
Jul 08 Recharter, if needed

_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce





ies in the ONC RPC and XDR protocols currently specified
by RFCs 1831, 1833 and 2203. In conjunction with the advancement
of the NFSv4 specification along the standards track, the WG will
also advance the ONC RPC and XDR dependencies. The WG will also
update the ONC RPC specification for compatibility with IPv6.
Additionally, it will create an IANA registry for RPC program numbers
and seed it with a registry Sun has been maintaining.

Goals and Milestones [replaces all current not "DONE" milestones]:

DONE Request publication of "NFS RDMA Problem Statement"
(draft-ietf-nfsv4-nfs-rdma-problem-statement) as Informational

DONE Request publication of "DMA Transport for ONC RPC"
(draft-ietf-nfsv4-rpcrdma) as Proposed Standard

DONE Request publication of "NFS Direct Data Placement"
(draft-ietf-nfsv4-nfsdirect) as Proposed Standard

Dec 2007 Request publication of "RPC: Remote Procedure Call Protocol
Specification Version 2" (draft-ietf-nfsv4-rfc1831bis) as
Proposed Standard

Mar 2008 Request publication of "NFSv4 Minor Version 1"
(draft-ietf-nfsv4-minorversion1) as Proposed Standard

Mar 2008 Request publication of "Object-based pNFS Operations"
(draft-ietf-nfsv4-pnfs-obj) as Proposed Standard

Mar 2008 Request publication of "pNFS Block/Volume Layout"
(draft-ietf-nfsv4-pnfs-block) as Proposed Standard

_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce