-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Mark" == Mark Baker <mark@xxxxxxxxxx> writes:
>> As there are no huge technical or address allocational reasons why
>> ISP's could not give at least /64, those ISP's that do get more
>> popular and ones dealing /128's do not, and disappear from IPv6
>> market.
Mark> There are, however, technical reasons why ISPs might want to use
Mark> dynamic IPs (if they have lots of dial-up hardware in different
Mark> locations, routing issues make static IP difficult), so although
Mark> their customers would get a /64, it might be a different one every
Mark> time they dial up.
Mark> In that situation, since I wouldn't want addresses on my local
Mark> network to keep changing, I would want to use NAT to translate the
Mark> address block assigned by the ISP onto some site local address
Mark> space.
You might use 1:1 NAT (not NAPT), but that would be a mistake.
1) you use site local addresses to talk between hosts locally.
2) you use router advertisements to get a public address for your network.
3) you use TSIG signed updates to a DNS server to get your addresses
into a DNS server. (possibly, just updating a single A6 record)
This is all possible *NOW*.
No need for NAT.
] ON HUMILITY: to err is human. To moo, bovine. | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr@xxxxxxxxxxxxxxxxxxxxxx http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another NetBSD/notebook using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
Comment: Processed by Mailcrypt 3.5.6, an Emacs/PGP interface
iQCVAwUBO2sQWYqHRg3pndX9AQEifQP9H8NzYUBi6Sgif+7Ut8UP7A3B6tSZBZ5G
JuZjdZXZx6c4+lHSCFLqHaHu3Zl5cEBq8ckEfNMO8C76KUVo5JTEk3C45kQ/SyPp
JITSVAHPMuDZZ87ubbWYLKHOlt02BbiCi6dqDQcmOqmjKj1OkBZ15VDLpQcg+hQ5
tiaXaOUiQAg=
=5l5w
-----END PGP SIGNATURE-----
|