RE: Some Enterprise Scenarios comments

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

Pekka,

Thanks for the carful review.


>Substantial:
>------------
>
>==> The approach in section 6 in M1-M6 seems, at places, a bit 
>solution-specific.  In many cases it says "enterprise policy 
>is FOO".  My point is that the document here is trying to 
>grasp IPV4 enterprise systems as they are, describe them, and 
>perhaps give some view on how to proceed with a solutions 
>document.  The point of subsequent work of v6ops is to 
>give reasoning why a certain type of enterprise policy is 
>adopted -- not 
>(yet!) the other way around.  The approach seems a bit 
>solutions-centric, 
>in particular with M2 and M3.

So what your saying is to state the Enterprise need for IPv6?  Each
enterprise will adopt different reasons for IPv6.  I don't think that is
the job of this spec.  The job of this spec is to identify scenarios how
the enterprise will approach the problem.  The M variable defines how
that can be accomplished and the Enterprises are looking at the M
variables before they move to IPv6, and this is only part of the
specifications equation.  Listing them is important for the context of
how the enterprise arrives at their choice, is our thinking model.

M2 and M3 are no different than the other M values.  These are simply
choices in strategy and if anything we are missing some values.  

>
>Semi-editorial:
>---------------
>
>Abstract
>
>   IPv6 will be deployed in Enterprise networks. This scenario has
>   requirements for the adoption of IPv6.  
>
>==> This should be reworded; "this scenario" is ambiguous and 
>sounds bad, and the scope of the work here is not to set 
>requirements for IPv6 
>adoption (rather, to describe the current IPv4 enterprise networks).

This wording has changed 4 times on the team.  

But this is a good point.

We on the team have never believed the mission here is to describe IPv4
enterprise networks.  So we may not agree on a very basic premise.  The
job is to describe how IPv4 Enterprises will approach moving to IPv6.

>
>                                        This document will focus upon
>   and define: a set of technology scenarios that shall exist for the
>   enterprise network, the set of transition variables, transition
>   methods, and tools required by different scenarios. [...]
>
>==> "transition methods" and especially "and tools required by 
>different 
>scenarios" seem too vague.  My first impression was that the document 
>would be specifying which transition mechanisms (like 6to4, etc.etc.) 
>would be required.  Luckily, this was not the case, but may 
>require some 
>more verbose text.

I for one agree. 

Not going to respond to other comments till I feel we agree on the scope
of the work.  I am sure you can understand that because it affects all
other responses.

Regards,
/jim