[171581] in North American Network Operators' Group

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

Re: US patent 5473599

daemon@ATHENA.MIT.EDU (David Conrad)
Tue May 6 15:38:11 2014

X-Original-To: nanog@nanog.org
From: David Conrad <drc@virtualized.org>
In-Reply-To: <CAPKkNb4yCvquRO20B0FeB-x6zWn8AkK+tPBahAPrjz0pLWb8gQ@mail.gmail.com>
Date: Tue, 6 May 2014 12:31:38 -0700
To: "Constantine A. Murenin" <mureninc@gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org


--Apple-Mail=_ABC6D5E8-C345-45E7-B597-ED47654B5FC3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Constantine,

On May 6, 2014, at 11:54 AM, Constantine A. Murenin <mureninc@gmail.com> =
wrote:
>>>>> As a final note of course, when we petitioned IANA, the IETF body =
regulating "official" internet protocol numbers, to give us numbers for =
CARP and pfsync our request was denied. Apparently we had failed to go =
through an official standards organization.

Yes. The 8-bit IP protocol field is assigned by IANA according to "IESG =
Approval or Standards Action".=20

>>>>>  Consequently we were forced to choose a protocol number which =
would not conflict with anything else of value, and decided to place =
CARP at IP protocol 112.

Protocol 112 was assigned by IANA for VRRP in 1998.

When did OpenBSD choose to squat on 112?=20

>>>>> We also placed pfsync at an open and unused number. We informed =
IANA of these decisions, but they declined to reply.

I would imagine the reply was "IANA does not have discretion to assign =
those values, they are assigned by IESG or via a standards action." =
Indeed, IP protocol 240 is not yet allocated. Presumably the OpenBSD =
community expects everyone else to acknowledge the squatting on 240.

> Frankly, I don't really see what the huge loss is. =20

Not surprising.=20

> Perhaps people
> should realise that OpenBSD has recently removed The Heartbeat
> Extension from TLS in libssl, and boycott the upcoming LibreSSL, since
> its likelihood of having another heartbleed has been so reduced, yet
> the API is still compatible with OpenSSL.  ???


Sorry, the relationship between OpenBSD developers intentionally and =
childishly squatting on a protocol number and OpenBSD developers hacking =
apart OpenSSL is what exactly?

Regards,
-drc


--Apple-Mail=_ABC6D5E8-C345-45E7-B597-ED47654B5FC3
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJTaTiaAAoJENV6ebf0/4rXBX4H/2RRmGoBAPimTtb1OZsSixDQ
GcWkO6gx6NFKw2jZT+nNSEQtTd/CFYWVsnPwuFgnwfVbHb+iVP4jL/O7e8zA2ljm
Akid2FK/8uEBPUj4Vu8qfeQfRNfElm1lQd41OpwWiUVTAhlrJAKfHAHKBkJ8Az2Q
/qITvgnk6zHHzBunJeiHDqMM04EpmPXkXN4QblSzEGyKWUMkdb0djdoGNOgkO1PA
/MdGboOXKUxxvui0Ajp3iABWZl5g3LuJ2oV8frpWS4IrgGpYGy32g4cEcH06z/GU
bWcqRGPRmvBWnbC/oM9vOf27xN9MZNtQ4Jjct2uXRk68vEsHjYUmtQxT6BXLEoc=
=+bP9
-----END PGP SIGNATURE-----

--Apple-Mail=_ABC6D5E8-C345-45E7-B597-ED47654B5FC3--

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