James Knott
Sebastian Freundt wrote:
Are you IANA? So tell me, how would you split your /56 amongst 6000 users so that each and every one of them gets a /64?
I have never said that every user (just me, my dog & cat :-) on my local network gets a /64 subnet. I said I get a /56 subnet that can be split into 256 /64 subnets, each of which could have up to 2^64 hosts. I wish you would stop trying to put words in my mouth.
monitor each individual computer behind the NAT router, only the aggregate traffic from the router. Same thing with IPv6, just monitor all the traffic coming from the customer's router. I have a cable You obviously haven't had the joy of working in a network where
Compare that to what happens now with IPv4 and NAT. The ISP cannot the use of _every_ IP address (even temporary ones and 192.168. private ones) require prior written permission. Technically there is no problem (just effort) to keep track of users, noone is doubting that. Red-tape is the problem, and you're not exactly helping with claims like `just monitor all traffic'
You were referring to an ISP having to monitor subscriber traffic. That has nothing to do with getting permission to use an RFC1918 address on the local network. Does your ISP see that 192.168.x.y address? Not if you're behind your NAT router. Is the ISP providing that subnet?
Nope, and nope. They do see traffic I happen to route to the routers address (::1 in my /64 here) from addresses other than my assigned one (::2 in my /64 here). And even though technically it's possible to route that traffic, they don't, because I don't give them enough money. So what's the problem again?
You seem to forget that this has to be configured, a BGP route to your AS (or a part of it) has to be established, paperwork has to be done if that part of the AS is to be routed differently, etc.
Why do you keep dragging BGP in, when it has nothing to do with the discussion? Use of a subnet does not require BGP. BGP is only used for automous networks, with multiple routes. That does not descripe the typical subscriber, business or home, user.
Well because if you insist on configuring *your* network it requires you to set up BGP and talk to other carriers, how would they know about *your* network otherwise? From your statement below I get the impression you confuse tunnel'd 6-in-4 traffic (where there IS a BGP entry to `your' (read your tunnelbroker's) network actually you just didn't bother thinking about it) with a native setup where you get your /64, an *assigned* static address within that /64 (mostly ::2), a router address (there's experiments to propagate that through ppp, but for now it's mostly in your /64 the ::1) and that's all you have. Did you overlook the fact that you have NO control over the remote side's router? Or are you talking about something completely different, see below.
Also, you haven't surveyed your local ISPs about native v6 connectivity lately, have you? A customer with more than one computer is happily encouraged to buy the fully routed /64 package. Or a /48. Or buy transit to your own AS. Not the cheapest options these days:( but competition will mitigate that I hope.
With IPv4, addresses are scare. With IPv6, they are extremely plentiful, so there's no need to ration or charge for them. I get my /56 subnet from a tunnel broker for absolutely no cost. Others hand out /48 subnets, again at no cost.
What do you mean by tunnel then? I thought tunnelbrokers are part of the transition plan and give you a v4 address that you can send 6-in-4 traffic to. Well native connectivity costs money here, what can I do about it? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org