Rate of growth on IPv6 not fast enough?

> > * Nick Hilliard:
> >
> > >> The eyeball ISPs will find it trivial to NAT should they ever need to do
> > >> so [...]
> >
> > > Having made this bold claim, have you ever actually tried to run a natted
> > > eyeball network? The last two natted eyeball networks I worked with could
> > > never figure out which aspect of NAT hurt more: the technical side or the
> > > business side.
> >
> > I'm pretty sure the acceptance of NAT varies regionally. I think
> > there's a large ISP in Italy which has been doing NAT since the 90s.
> > So it's not just the mobile domain.
> >
> > It can be tricky to introduce a new NATted product and compete with
> > established players which do not NAT, though.
>
> It's another opportunity to monetize things. Give people the option of
> a "real" IP address for $5 extra a month in case they actually need it
> for gaming, etc., and default Grandma's average everyday connection to
> NAT.

That'd be easy if you were just starting up an ISP. What do you do with
your existing customer base? If their current service includes a
dynamic public IPv4 address, you can't gracefully take it away, without
likey violating services T&Cs, government telco regulations etc. So
you'll have to go through a formal process of getting agreement with
customers to take them away.

I haven't seen any such documents or regulations.

Or do you have a flag fall day when after that new customers get NATted,
but old customers don't? Do you offer a LSN vs non-LSN product at
different price points? The price difference must be large enough for people to care about, or better
described, bother with it, yet the problem might be that that discount
might need to be so large that it doesn't actually cover the costs of
providing a service to that customer.

Maybe the price difference for existing customers is $0. You put them
on NAT, and if they squawk, put them back. Since you don't need to
do your whole customer base at once, you can even learn along the way.

Thinking about what sort of discount I'd find attractive enough on
roughly what I spend for ADSL Internet access, and putting myself in a
customers position, I'd figure it'd be at least 10%. You'd have to
state up front why you're offering a cheaper product, and for people to
make an informed judgement value, they'll need to understand the
problem i.e. the Internet running out of IPv4 addresses and what the
consequences of NAT are. Their eyes will probably glaze over at this
point, because all they want is "Internet" and don't care how it works,
and are probably not going to want to accept restrictions now that
might bite them in the future. At a certain point, the risks of going
with a cheaper limited service, when you don't understand or fully
understand it's restrictions, becomes higher than the price of the full
service. IOW, if it's too hard to understand why the LSN service is
cheaper, people will just pay the extra 10% - it's less riskier that
way. That extra 10% is insurance.

Many/most people are _already_ behind a NAT gateway.

The guy who wrote "The Internet for Dummies" went for a good while
behind a carrier NAT without realizing he was. And he's no dummy.

Practical experience by network operators who have deployed NAT
suggests that it's not ideal, but it's not horrible or impossible.

A vast number of people just want to do their stuff and don't really
care too much as long as things don't break. So what you need to do
is consider what it is most people do, and how much of that would
break. For an average household that's browsing the web and checking
mail, NAT == not noticeable. And there will be other things, too,
that work just fine.

... JG

> That'd be easy if you were just starting up an ISP. What do you do with
> your existing customer base? If their current service includes a
> dynamic public IPv4 address, you can't gracefully take it away, without
> likey violating services T&Cs, government telco regulations etc. So
> you'll have to go through a formal process of getting agreement with
> customers to take them away.

I haven't seen any such documents or regulations.

People purchaced the service on the understanding that they would
get a Internet address. A address behind a NAT is not a Internet
address, it's a *shared* Internet address which is a very different
thing.

Many/most people are _already_ behind a NAT gateway.

They are behind NAT44 which they deployed themselves and control
the configuration of themselves. They can direct incoming traffic
as they see fit. They are NOT restricted to UDP and TCP.

NAT444 is a different kettle of fish. There are lots of things
that you do with a NAT44 that you can't do with a NAT444.

If all you do is browse the web and read email then you won't see
the much of a difference. If you do anything more complicated than
making outgoing queries you will see the difference.

Mark

Mark Andrews wrote:

That'd be easy if you were just starting up an ISP. What do you do with
your existing customer base? If their current service includes a
dynamic public IPv4 address, you can't gracefully take it away, without
likey violating services T&Cs, government telco regulations etc. So
you'll have to go through a formal process of getting agreement with
customers to take them away.

I haven't seen any such documents or regulations.

People purchaced the service on the understanding that they would
get a Internet address. A address behind a NAT is not a Internet
address, it's a *shared* Internet address which is a very different
thing.

Given that many ISPs put their sign-up documents, including contracts,
on-line, you can no doubt supply a link to such a document that has
legal terms that would preclude NATed service, yes?

My recollection is only that I would be provided with "Internet service"
  or "access to the Internet" . No mention of RFC1918 space or other
distinguishing information was given.

Note in the below blurb no mention of publicly routable addresses...

Comcast's contract states:

"Comcast will provide you with dynamic Internet protocol ("IP")
address(es) as a component of HSI, and these IP address(es) can and do
change over time. You will not alter, modify, or tamper with dynamic IP
address(es) assigned to you or any other customer. You agree not to use
a dynamic domain name server or DNS to associate a host name with the
dynamic IP address(es) for any commercial purpose. You also agree not to
use any software that provides for static IP address(es) on or in
conjunction with any computer(s) or network device connected to HSI. If
applicable, Comcast will release and/or recover the dynamic IP
address(es) when the Service or this Agreement is disconnected,
discontinued, or terminated."

--Patrick

Mark Andrews wrote:
>>> That'd be easy if you were just starting up an ISP. What do you do with
>>> your existing customer base? If their current service includes a
>>> dynamic public IPv4 address, you can't gracefully take it away, without
>>> likey violating services T&Cs, government telco regulations etc. So
>>> you'll have to go through a formal process of getting agreement with
>>> customers to take them away.
>> I haven't seen any such documents or regulations.
>
> People purchaced the service on the understanding that they would
> get a Internet address. A address behind a NAT is not a Internet
> address, it's a *shared* Internet address which is a very different
> thing.

Given that many ISPs put their sign-up documents, including contracts,
on-line, you can no doubt supply a link to such a document that has
legal terms that would preclude NATed service, yes?

My recollection is only that I would be provided with "Internet service"
or "access to the Internet" . No mention of RFC1918 space or other
distinguishing information was given.

Note in the below blurb no mention of publicly routable addresses...

It doesn't have to as the normal definition of a Internet address
is a publically routable internet address. A address behind a NAT
is not a Internet address (Big I Internet).

If you supply something less than a full blown Internet access you
need to point out the restriction otherwise I would expect you to
be subject to "Bait and Switch" and other consumer protection laws.

Mark

Mark Andrews wrote:

Mark Andrews wrote:

I haven't seen any such documents or regulations.

People purchaced the service on the understanding that they would
get a Internet address. A address behind a NAT is not a Internet
address, it's a *shared* Internet address which is a very different
thing.

Given that many ISPs put their sign-up documents, including contracts,
on-line, you can no doubt supply a link to such a document that has
legal terms that would preclude NATed service, yes?

My recollection is only that I would be provided with "Internet service"
or "access to the Internet" . No mention of RFC1918 space or other
distinguishing information was given.

Note in the below blurb no mention of publicly routable addresses...

It doesn't have to as the normal definition of a Internet address
is a publically routable internet address. A address behind a NAT
is not a Internet address (Big I Internet).

(hope the attribution is not screwed up)

*ANY* valid Internet Protocol address is an "IP address" as mentioned in
the contract I quoted. Including 192.168.99.2 .

If you supply something less than a full blown Internet access you
need to point out the restriction otherwise I would expect you to
be subject to "Bait and Switch" and other consumer protection laws.

You are charmingly naive about how "the law" actually works in the USA -
that is IMHO.

In any case, I left the large amount of quotes in to show that I (and
possibly Joe) are asking you for specific examples to support your
argument - and all you are offering is more of your personal opinion,
which is not an objective source of support for your position.

If I want that, I can go to any of *.livejournal.com, *.blogger.com , etc.

--Patrick

Mark Andrews wrote:
>> Mark Andrews wrote:
:
>>>> I haven't seen any such documents or regulations.
>>> People purchaced the service on the understanding that they would
>>> get a Internet address. A address behind a NAT is not a Internet
>>> address, it's a *shared* Internet address which is a very different
>>> thing.
>> Given that many ISPs put their sign-up documents, including contracts,
>> on-line, you can no doubt supply a link to such a document that has
>> legal terms that would preclude NATed service, yes?
>>
>> My recollection is only that I would be provided with "Internet service"
>> or "access to the Internet" . No mention of RFC1918 space or other
>> distinguishing information was given.
>>
>> Note in the below blurb no mention of publicly routable addresses...
>
> It doesn't have to as the normal definition of a Internet address
> is a publically routable internet address. A address behind a NAT
> is not a Internet address (Big I Internet).
>

(hope the attribution is not screwed up)

*ANY* valid Internet Protocol address is an "IP address" as mentioned in
the contract I quoted. Including 192.168.99.2 .

> If you supply something less than a full blown Internet access you
> need to point out the restriction otherwise I would expect you to
> be subject to "Bait and Switch" and other consumer protection laws.

You are charmingly naive about how "the law" actually works in the USA -
that is IMHO.

Yes, things vary around the world. You failed to state "In the
USA". There is plenty of case law in Australia about companies
attempting to arbitarially change terms and conditions to the
detriment of the consumer and being made to reverse the changes.

Changing from a public IP address to a private IP address is a big
change in the conditions of the contract. People do select ISP's
on the basis of whether they will get a public IP address or a
private IP address.

> > That'd be easy if you were just starting up an ISP. What do you do with
> > your existing customer base? If their current service includes a
> > dynamic public IPv4 address, you can't gracefully take it away, without
> > likey violating services T&Cs, government telco regulations etc. So
> > you'll have to go through a formal process of getting agreement with
> > customers to take them away.
>
> I haven't seen any such documents or regulations.

People purchaced the service on the understanding that they would
get a Internet address. A address behind a NAT is not a Internet
address, it's a *shared* Internet address which is a very different
thing.

  whats an "Internet" address? and are you sure thats part of
  the service offering?

Mark Andrews, ISC

--bill

> You are charmingly naive about how "the law" actually works in the USA -
> that is IMHO.

Yes, things vary around the world. You failed to state "In the
USA". There is plenty of case law in Australia about companies
attempting to arbitarially change terms and conditions to the
detriment of the consumer and being made to reverse the changes.

  this is the North American Network Operators Group.
  Not the Australian Network Operators Group.

Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia

--bill

>
> > You are charmingly naive about how "the law" actually works in the USA -
> > that is IMHO.
>
> Yes, things vary around the world. You failed to state "In the
> USA". There is plenty of case law in Australia about companies
> attempting to arbitarially change terms and conditions to the
> detriment of the consumer and being made to reverse the changes.

  this is the North American Network Operators Group.
  Not the Australian Network Operators Group.

And last I heard NA != USA. So have you decided to annex the rest of
NA and bring it under US law. :slight_smile:

>
> > You are charmingly naive about how "the law" actually works in the USA -
> > that is IMHO.
>
> Yes, things vary around the world. You failed to state "In the
> USA". There is plenty of case law in Australia about companies
> attempting to arbitarially change terms and conditions to the
> detriment of the consumer and being made to reverse the changes.

  this is the North American Network Operators Group.
  Not the Australian Network Operators Group.

So when did NA stop being the most litigious society on the planet?
I could see a class action suit over not getting proper big "I" Internet
access like you used to. You guys sue over hot coffee (of both
kinds)!

Well.. yeah. When it causes 3rd degree burns, you start thinking about suing.

http://www.lectlaw.com/files/cur78.htm

"McDonalds also argued that consumers know coffee is hot and that its
customers want it that way. The company admitted its customers were
unaware that they could suffer thirddegree burns from the coffee...."

Read that and tell me if you *still* think it's a totally frivolous lawsuit.

(Hot water is *dangerous* - in many cases even more so than an open flame.
If you stick your hand/arm in a flame, you can *usually* pull it out before
your shirt sleeve catches fire, and you only take damage the time your arm is
actually in the flame. You get a hot water spill on you, that sleeve
will hold the hot water against your skin, and the burn becomes a gift that
keeps on giving...)

nope - but we'll be glad to tell your PM that Australia is
  prepared to join the Union as the next five states and
  enjoy all the benefits of our enlighted government and laws.

  or would you prefer to be part of Canada?

--bill

Seems to me your objection is based on whether or not the customer
gets a public address vs a private address.

There's no need for NAT pools to be RFC1918. Pretty sure everyone
is going to get a public address of some form... it just won't
necessarily be globally unique to them.

As for jurisdictional issues: This particular Australian ISP amended
its T&C document to give us the discretion of providing LSN addresses
about two years ago. Will we need to? Perhaps not. But if we do, the
T&C's are already worked out. Looking ahead in time and forecasting
future risks is one of the things businesses are supposed to do, right?

Regards,

   - mark

> Changing from a public IP address to a private IP address is a big
> change in the conditions of the contract. People do select ISP's
> on the basis of whether they will get a public IP address or a
> private IP address.

Seems to me your objection is based on whether or not the customer
gets a public address vs a private address.

There's no need for NAT pools to be RFC1918. Pretty sure everyone
is going to get a public address of some form... it just won't
necessarily be globally unique to them.

RFC1918 addresses are not the only source of private addresses. If
you are giving out addresses behind a NAT then they are private address.

As for jurisdictional issues: This particular Australian ISP amended
its T&C document to give us the discretion of providing LSN addresses
about two years ago. Will we need to? Perhaps not. But if we do, the
T&C's are already worked out. Looking ahead in time and forecasting
future risks is one of the things businesses are supposed to do, right?

Which is a good thing to do. If you are offering a (potentially)
degraded service then the customer needs to be informed before they
agree to the service.

Mark