RE: Comments on draft-ietf-v6ops-ent-scenarios-00

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

CP,

Thanks for the comments.

> Some quick comments:
>
> 1. The definition of scenario needs to be clarified. I was under the
>    assumption that a scenario would correspond to a stage in the
>    deployment of IPv6 in the enterprise network. For example,
>    the cases described in section 5 in
>   
> http://www.ietf.org/internet-drafts/draft-ietf-v6ops-unman-sce
narios-03.txt.

The Enterprise Scenarios are exponentially greater than uman scenarios.
Thus the potential stages of deployment within those is even greater.
What we could do is add a stages of deployment section to try to provide
a reference for users to be aware of to take those into consideration.
But Enterprises are quite different and will approach this in many
different ways.


2. The scenario description in section 3.1, and the examples in section
   3.3 do not seem to be in tune. The purpose of section 3.3 is to
   provide clarity on the base scenarios but, IMHO, it does not do that.
   For example, how does the example network A shed more light on
   Scenario 1, or 2, or 3?

Fair question.  We need to provide that in an appendix.  All three
examples 3.1 could apply to all specific examples in 3.3.  And we need
to cover this in the spec and then show examples in the spec.

For example:

Example Network A:

   A distributed network across a number of geographically separated
   campuses

Each scenario in 3.0 could be applied to Network A.

Then:
  - External network operation.
   - External connectivity required.
   - Multiple sites connected by leased lines.
   - Provider independent IPv4 addresses.
   - ISP does not offer IPv6 service.
   - Private Leased Lines no Service Provider Used

Each apply for this example from each scenario.

   Applications run by the enterprise:
   - Internal Web/Mail.
   - File servers.
   - Java applications.
   - Collaborative development tools.
   - Enterprise Resource Applications.
   - Multimedia Applications.
   - Financial Enterprise Applications.
   - Data Warehousing Applications.

These could be required in all 3.0 scenarios.

   Internal network operation:
   - In house operation of the network.
   - DHCP (v4) is used for all desktops, servers use static address
     configuration.
   - The DHCP server to update naming records for dynamic desktops uses
     dynamic DNS.
   - A web based tool is used to enter name to address mappings for
     statically addressed servers.
   - Network management is done using SNMP.
   - All routers and switches are upgradeable to IPv6.
   - Existing firewalls can be upgraded to support IPv6 rules.
   - Load balancers do not support IPv6, upgrade path unclear.
   - Peer-2-Peer Application and Security supported.

This could be the case for each scenario too.

The idea is 3.0 scenarios state generic base solutions that cover a wide
range of Enterprise approaches to IPv6 deployment.

Then 3.3 "specific examples" give types of networks that could use any
of the base scenarios.

/jim



CP


On Mon, 20 Oct 2003 09:48:57 +0300 (EEST), "Pekka Savola"
<pekkas@netcore.fi> said:
> On Sat, 18 Oct 2003, Tim Chown wrote:
> > Here are some (long) comments on draft 00.  I am sorry they are
> > later than ideal but I hope they are still useful prior to
> > Minneapolis.
> >
> > The document is absolutely on the right track, in my view.  The
> > detail of comments is mainly for clarification :)
> [...]
>
> Thanks Tim.  These kind of comments are exactly what we need to move
> the scenarios documents forward.  Hopefully other folks also have a
> chance to read and comment on the document.
>
> Pekka writing as WG co-chair
>
>