Just joined....

Margaret Wasserman wrote:
For homes? Or larger enterprises?

My original 6AI BOF request suggested multiple work items, two of which were:

(1) An information (or BCP?) document on how to build a home gateway for IPv6 that includes a firewall (for simple security) and prefix delegation, etc. for easy configuration, but no NAT functionality.

(2) NAT66 to provide address independence for enterprises.

Do we think that home users (regular home users, not us) actually need address independence, or they would be happy to get their addresses from their ISP via PD and to be renumbered when/if needed?

DMZ configuration is not uncommon for home users with separate rfc1918
networks. There are a number of drivers toward something larger than
/64. But even though I have a /48 in my home, something smaller than
/56, and more likely /62 will work for homes and small business offices
(think medical and HIPPA compliance).


If we view NAT66 as applicable to home networks, I agree that we will need to handle prefixes longer than /48. However, I expect that most enterprises will get /48 or larger.

Margaret


On Mar 28, 2009, at 11:29 PM, Mark Townsley wrote:


My ISP currently hands out a /60 via 6rd (space gets a little tight with the embedded IPv4 address). The BBF is settling on /56 as its recommended prefix size for residential customers. I've seen /64's out there as well (and stomped on them as quickly as possible, but can only do so much).

I have to agree that we must expect that variable prefix sizes to sites will be a reality.

- Mark

[email protected] wrote:
>From my perspective the NAT solution that might be specified within 6AI should be able to deal also with prefixes shorter, equal or _longer_ than a /48 since there might be ISPs giving out such longer prefixes to their customers. (A reason for that are the changed RIR policies that allow the ISPs freely to decide if they want to give a /48, a /56 or even a /61 to its customers.)

Removing the /48 assumption will have major impact e.g. on Margarets draft.

br olaf
_______________________________________________
nat66 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nat66



_______________________________________________
nat66 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nat66



_______________________________________________
nat66 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nat66

Reply via email to