[182041] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Dual stack IPv6 for IPv4 depletion

daemon@ATHENA.MIT.EDU (Owen DeLong)
Thu Jul 9 17:19:26 2015

X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <9578293AE169674F9A048B2BC9A081B401C7097A32@MUNPRDMBXA1.medline.com>
Date: Thu, 9 Jul 2015 14:19:20 -0700
To: "Naslund, Steve" <SNaslund@medline.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

Sigh=E2=80=A6

Home gateways are an application in this context. How the firmware gets =
written in those things will be affected.

Further, applications do care about things like =E2=80=9CCan I assume =
that every home is reachable in its entirety via a packet to =
ff02::<group>?=E2=80=9D which is, for example, already baked into many =
products as the current mDNS default scope.

SSDPv6 also seems to default to ff02:: scoping.

Whether or not applications come into existence that can take advantage =
of diverse topology in the home will depend entirely on whether or not =
we make diverse topology possible going forward.

/56 will enable some development in this area, but it will hinder =
several potential areas of exploration.

/48 is a reasonable end-site boundary. It allows enough flexibility for =
dynamic topologies while still leaving enough prefix space to have lots =
of extra room for sparse allocations and everything else.

So, instead of focusing on the narrowest possible definition of =
=E2=80=9Capplication=E2=80=9D by todays terms, try opening your mind =
just a little bit and recognize that anything that requires software and =
interacts with the network in any way is a better definition of =
application in this context.

Owen

> On Jul 9, 2015, at 13:56 , Naslund, Steve <SNaslund@medline.com> =
wrote:
>=20
> Huh, since when does ANY application care about what size address =
allocation you have?  A V6 address is a 128 bit address period.  Any =
IPv6 aware application will handle addresses as a 128 bit variable.
>=20
> Does any application running on IPv4 care if you have a /28 or a /29?  =
In fact the application should not even be aware of what the net mask is =
because that is an OS function to handle the IP stack.  This argument =
makes no sense at all since every application will be able to handle any =
allocation size since it is not even aware what that is.  Any IPv6 =
compatible OS will not care either because they would be able to handle =
any number of masked bits.  No app developer has ever been tied into the =
size of a subnet since CIDR was invented.
>=20
> Steven Naslund
> Chicago IL
>=20
>=20
>> Subject: Re: Dual stack IPv6 for IPv4 depletion
>>=20
>> And I=E2=80=99m saying you=E2=80=99re ignoring an important part of =
reality.
>>=20
>> Whatever ISPs default to deploying now will become the standard to =
which application developers develop.
>>=20
>> Changing the ISP later is easy.
>>=20
>> Changing the applications is hard.
>>=20
>> Let=E2=80=99s not bake unnecessary limitations into applications by =
assuming that tomorrow=E2=80=99s networks in homes will necessarily be =
as simple as today=E2=80=99s.
>>=20
>> Owen
>=20


home help back first fref pref prev next nref lref last post