Subject: [homegate] How many documents?

From: Paul Hoffman <[email-masked]>
Date: Sun, 4 Jul 2010 13:16:14 -0700

The current charter says:

>The basic hypothesis of this working group is that a well organized collection of requirements for support of various features would make it more likely that future home gateway devices behave better in these situations. This collection of requirements would form a single document to document the baseline requirements derived from "core" RFCs which must be supported. A secondary objective is to list desired-but-optional, or "advanced", requirements from the same RFCs as well as other, non-core RFCs.

But the Proposed Deliverables reads:

>1. Requirements document for basic, mandatory functionality for IPv4-only home gateways (BCP)
>2. Requirements document for basic, mandatory functionality for dual-stack (IPv4 and IPv6) home gateways (BCP)
>3. Requirements document for additional, optional functionality in home gateways (BCP)

3>>1

I propose that the WG's deliverable (singular) is the one described in the text, and that there be a single proposed deliverable: "Requirements document for basic, mandatory functionality for home gateways (BCP)". That is, in 2011 when this document is finished, we do not support the notion of an "IPv4-only home gateway". The RFC we produce will say explicitly that correct IPv6 functionality is the best current practice.

Also, we should not spend WG time wading into the morass of "additional, optional functionality in home gateways". *Every* standards-track RFC is functionality that a home gateway should not impede; list them all is of little value.

--Paul Hoffman, Director
--VPN Consortium