Actually, technically, Windows NT would meet the requirement in this proposal. 
It just couldn’t resolve DNS over IPv6.

Owen


> On Nov 6, 2019, at 11:40 , hostmas...@uneedus.com wrote:
> 
> Also, you can under this proposal still have that Windows 3.1 workstation, or 
> even a DOS workstation using packet drivers.
> 
> All it says is that 1) You have an IPv6 Assignment or Allocation from ARIN, 
> and 2) You have at least ONE workstation on it that is capable of 
> communicating using that IPv6 address space with ARIN.
> 
> It is NOT a requirement to place IPv6 everywhere in your network, although in 
> todays world that is getting to be more and more desirable.
> 
> And just FYI, there is a third party winsock that will allow you to use that 
> workstation on an IPv6 network, along with packet drivers for dos, that also 
> use IPv6.  Windows has had IPv6 support since W2K, almost 20 years ago.  This 
> requirement is NOT a hardship, just a friendly jolt in the correct direction 
> for the future.
> 
> Albert Erdmann
> Network Administrator
> Paradise On Line Inc.
> 
> 
> On Wed, 6 Nov 2019, scott wrote:
> 
>> 
>> 
>> On Wed, 6 Nov 2019, Michel Py wrote:
>> 
>>> I oppose this proposal. If I am ever in a position where ARIN is trying to 
>>> force me to request or use IPv6, I will sue ARIN for imposing an undue 
>>> burden.
>> 
>> What do you normally do when hardware or software hits EOL?
>> 
>>> I am serious. If ARIN generates more work for me, I will explore all 
>>> options to be compensated.
>> 
>> Look, you are free to run Windows 3.1 on your 10BASE2 network, if that makes 
>> less work for you, and less work is a variable you optimize for in your 
>> networks.  This is, however, 2019.  IPv6 has been around for a while. IPv4 
>> has been officially depleted for years now.  IPv4 being considered the 
>> "legacy Internet" is not that many years away.  Is it more work to get ahead 
>> of the curve, or play catch up?
>> 
>> 
>> 
>>> Michel.
>>> _______________________________________________
>>> ARIN-PPML
>>> You are receiving this message because you are subscribed to
>>> the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).
>>> Unsubscribe or manage your mailing list subscription at:
>>> https://lists.arin.net/mailman/listinfo/arin-ppml
>>> Please contact i...@arin.net if you experience any issues.
>> _______________________________________________
>> ARIN-PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).
>> Unsubscribe or manage your mailing list subscription at:
>> https://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact i...@arin.net if you experience any issues.
>> 
> _______________________________________________
> ARIN-PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact i...@arin.net if you experience any issues.

_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact i...@arin.net if you experience any issues.

Reply via email to