Date: Fri, 2 Jun 2017 11:43:55 -0400 From: Jon Radel <jon@radel.com> To: byrnejb@harte-lyne.ca, freebsd-questions@harte-lyne.ca Subject: Re: IPv4 to IPv6 Message-ID: <691d853e-e2f7-b5f3-d281-73511845bd6a@radel.com> In-Reply-To: <74b7b58aa45cc01585338ef2270ccc57.squirrel@webmail.harte-lyne.ca>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
On 6/2/17 10:26, James B. Byrne via freebsd-questions wrote:
> We are beginning the process of transitioning to IPv6. I have read a
> great deal respecting the difficulty of moving from IPv4 to IPv6 and
> maintaining general Internet connectivity. If any reading this have
> gone through the process upon which we are embarking then I would be
> grateful if you share your experience. Particularly any 'gotchas' that
> cropped up.
>
> We will be using FreeBSD-11 as the platform for our Internet
> connectivity. The main services we provide publicly are SMTP and DNS.
> We will maintain IPv4 addresses for these together with IPv6.
>
>
Do you really plan to remove IPv4 from everything other than your SMTP
and DNS servers? If so, how will your users [assuming you have such]
reach resources on the IPv4 Internet? Or have I misunderstood?
An orderly migration to being dual-stacked on everything would probably
be a lot less painful than what I think you're planning. While there
are possible mechanisms for an IPv6-only client to reach resources on
the IPv4 Internet, I'm unclear on the benefits of bothering with such an
architecture.
--
--Jon Radel
jon@radel.com
[-- Attachment #2 --]
0 *H
010
`He 0 *H
00 #SanzTgk!0
*H
0o10 USE10U
AddTrust AB1&0$UAddTrust External TTP Network1"0 UAddTrust External CA Root0
141222000000Z
200530104838Z010 UGB10UGreater Manchester10USalford10U
COMODO CA Limited1A0?U8COMODO SHA-256 Client Authentication and Secure Email CA0"0
*H
0
zSNpRV&IQZI`zQBy"aNv#
J n=ٺ.CRC|2PȦOZϓ%{0dV*$3DiFK3@@:*S= a<UNv%!)|qvO_T{5R"=,0-1YR73i-C֥wgQ'뼥8v8ߌIs:2:=F:WtaP@?⟢! 00U#0z4&&T$T0UakᢠOg£ 0U0U0 0U%0++0U
00U 0DU=0;09753http://crl.usertrust.com/AddTrustExternalCARoot.crl05+)0'0%+0http://ocsp.usertrust.com0
*H
*nU:Uka+ #fjow^a } [jr
AX&MX"cR6}Xޫ;cs{B#ʶM>K-ػBKiۦ74{:ǟO4ne6d)5ֱqC>2Svʆ4,Jؙ
␒ZBj#!eջ~ꌅ b:,Yř38zyJ&|00sT<}k
`i
0
*H
010 UGB10UGreater Manchester10USalford10U
COMODO CA Limited1A0?U8COMODO SHA-256 Client Authentication and Secure Email CA0
150330000000Z
180329235959Z010 UUS10U2215010 UVA10USpringfield10U 6917 Ridgeway Dr.10U
Jon T. Radel1200U)Issued through Jon T. Radel E-PKI Manager10UCorporate Secure Email10U Jon Radel10 *H
jon@radel.com0"0
*H
0
aЩ@@g3eGރ͛; d#>q7&Hf
:3vL"jV#Xݷ>U-H[$SUڻ{Ϝ,z¶IchO=rcyrn v.Vh7k;%ueYuӬnz6!| !Aȡ+,u+
CAպF-un#vjUJWnk%j]
2JPkl 00U#0akᢠOg£ 0UE|GDp/ʚB0U0U0 0U%0++0FU ?0=0;+10+0)+https://secure.comodo.net/CPS0]UV0T0RPNLhttp://crl.comodoca.com/COMODOSHA256ClientAuthenticationandSecureEmailCA.crl0+00X+0Lhttp://crt.comodoca.com/COMODOSHA256ClientAuthenticationandSecureEmailCA.crt0$+0http://ocsp.comodoca.com0U0
jon@radel.com0
*H
KS `?H_D`8G߿VbĘ<tB-Ӈї|{'Ũݹg0Gp$%F(;*MO*gt$@ t6,?0|#ăz,&! {j2i[%b7ߪP+9G㲍["y<?8rZ'[UR6%L̤
w"=:L~Ƨ^jf36 OP1.}(e1A0=0010 UGB10UGreater Manchester10USalford10U
COMODO CA Limited1A0?U8COMODO SHA-256 Client Authentication and Secure Email CAsT<}k
`i
0
`He a0 *H
1 *H
0 *H
1
170602154355Z0/ *H
1" 8ͅ@8$sF!AQ0l *H
1_0]0 `He*0 `He0
*H
0*H
0
*H
@0+0
*H
(0 +710010 UGB10UGreater Manchester10USalford10U
COMODO CA Limited1A0?U8COMODO SHA-256 Client Authentication and Secure Email CAsT<}k
`i
0*H
1010 UGB10UGreater Manchester10USalford10U
COMODO CA Limited1A0?U8COMODO SHA-256 Client Authentication and Secure Email CAsT<}k
`i
0
*H
?ɜѵ=9>xm_eaHE0 meXM{5X8e[<
C5w-}
_Vn`襥ϭǑxV` ?: .fX%arsGu@E MG
-ҩE` tdme/0j-ϫp}Ďs>|ƨ:ghߑWWZiɃR+
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?691d853e-e2f7-b5f3-d281-73511845bd6a>
