[115390] in North American Network Operators' Group
Re: question about Mark Koster's ARIN presentation
daemon@ATHENA.MIT.EDU (Michael Hallgren)
Thu Jun 18 15:37:40 2009
From: Michael Hallgren <m.hallgren@free.fr>
To: nanog@nanog.org
In-Reply-To: <20090618160520.93FEE3F476@pecan.tislabs.com>
Date: Thu, 18 Jun 2009 21:35:53 +0200
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--=-Qj+EKwDNPdfynhyRHx87
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Le jeudi 18 juin 2009 =C3=A0 12:05 -0400, Sandy Murphy a =C3=A9crit :
> This message is sent to the whole nanog list, rather than the
> nanog-attendees list,
How come there is a nanog-attendees list disjunct from the nanog list.
Wouldn't it be natural to broadcast any kind of content to the
entire community?
Cheers,
mh
> as I'm not sure who would be watching that
> list when the conference is over.
>=20
> I stood up to ask a question at the end of Mark Koster's presentation=20
> yesterday, but before I got to the end of the table, he was being applaud=
ed
> and leaving the stage. I must be too short.
>=20
> The presentation said that ARIN would be doing a lot of work to
> improve the IRR. The last I asked, the ARIN IRR did not support the
> RPSS (Routing Policy System Security - RFC2725). RIPE supports this,
> I know. Will the ARIN improvements include support for RPSS?
Interesting, yes.
>=20
> The presentation talked about the RPKI pilot, and Mark said that
> ARIN would be using the RIPE code. I believe RIPE has or had a couple
> different attempts at this, so I'm not sure what features the code
> you use will have. Will you have the ability to hand certs to ISPs
> so that they can do their own cert generation for the allocations
> they hand to their own customers? I.e., is ARIN going to run a
> service just for its members, or will it enable its members to
> participate in the RPKI themselves?
>=20
As well.
> --Sandy
>=20
mh
--=20
michael hallgren, mh2198-ripe
--=-Qj+EKwDNPdfynhyRHx87
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Ceci est une partie de message
=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEABECAAYFAko6lxQACgkQZNZ/rrgsqaeH0gCfQX2WMug54j185jxx2v4OcR2t
LUcAn01mgYxMGFwDH7Idlnm3AkaMsfRu
=XU4y
-----END PGP SIGNATURE-----
--=-Qj+EKwDNPdfynhyRHx87--
