Proposal : Common issues across Scenarios Design Team should be new work item

["Bound, Jim" <jim.bound@hp.com>]

Folks,

We got some input to address this in DNS or that in DNS or address this
for Mail or that for Mail for Enterprise work.  These I am thinking
common problems for all scenarios. How dynamic DNS updates work in
secure manner over an IPv4 Tunnel, as example, is the same
issue/resolution for Enterprise, 3GPP, ISP, and Unmanaged.

Do we need to select out common scenario issues for any network and make
that its own scenario document.

This would also avoid having to identify these issues in the above spec
work because the common scenarios spec would be first read or second
read to define how one deploys or transtions to IPv6.

Why do this:

1.  This would speed up efforts to deliver the four scenarios documents.

2.  It would support a focus for the common scenario issues.

3.  ISP, 3GPP, and Umanaged have not put this in their specs for the
most part thus it is no work for them.

4.  Enterprise work does not become the designated v6ops dumping ground
for common problems for application issues that are relevant to all
scenarios.  And this will slow down the process to complete the
Enterprise.  ISP scenarios face similar problem potentially.

5.  Users of any scenario focus we need to create can learn the base
common application or infrastructure scenarios common to any network
definition scenario.

Proposal: Begin a new design team and effort to work on the common IPv6
operational issues across any scenario that must be addressed (e.g. DNS,
Porting, Mail).  There are also probably common security issues for all
scenarios in addition to the specific ones for each scenario work effort
in v6ops.

Comments?

thanks
/jim