[157391] in North American Network Operators' Group
RE: 169.254.0.0/16
daemon@ATHENA.MIT.EDU (Darren O'Connor)
Thu Oct 18 11:22:41 2012
From: Darren O'Connor <darrenoc@outlook.com>
To: "Majdi S. Abbas" <msa@latt.net>
Date: Thu, 18 Oct 2012 16:22:22 +0100
In-Reply-To: <20121018151856.GD3768@puck.nether.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I would agree. I don't see it as a problem using it=2C but I was mainly won=
dering about what other people thought of using it.
And yes=2C it's nice to use as people are using RFC1918 addresses in their =
networks and you can be sure that 169.254.0.0/16 isn't used. At least until=
people do start using it and then you have the same overlapping problem ag=
ain
> Date: Thu=2C 18 Oct 2012 11:18:56 -0400
> From: msa@latt.net
> To: darrenoc@outlook.com
> CC: nanog@nanog.org
> Subject: Re: 169.254.0.0/16
>=20
> On Wed=2C Oct 17=2C 2012 at 06:59:09PM +0100=2C Darren O'Connor wrote:
> > I've just set up a vpn tunnel to Amazon's AWS and as part of the config=
=20
> > they required me to configure to /30 tunnels using addressing from the=
=20
> > 169.254.0.0/16 space.
>=20
> Yeah=2C they do that for Direct Connect.
>=20
> > RFC3927 basically says that this address should only be used as a temp=
=20
> > measure until the interface has a proper private or public address.
>=20
> So? :)
>=20
> > So what's the consensus then? Is their a problem using this space as=20
> > link-local address for routers here and there (I mean we have 65K=20
> > addresses wasted in this block) or is it a strict no-no? And if no=2C w=
hy=20
> > is Amazon using it?
>=20
> RFCs are just paper. As for why they use it.. the common private
> use reserved blocks (10/8=2C 172.16/12=2C 192.168/16) are all in use=20
> internally in their customers networks. This is probably the easiest
> way to avoid addressing conflicts.
>=20
> Since these networks are all isolated=2C I don't see a great deal
> of harm in it (probably less than overlapping more commonly used private
> blocks.)
>=20
> --msa
=
