[102794] in North American Network Operators' Group

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

Re: YouTube IP Hijacking

daemon@ATHENA.MIT.EDU (Paul Ferguson)
Tue Feb 26 21:42:38 2008

From: "Paul Ferguson" <fergdawg@netzero.net>
Date: Wed, 27 Feb 2008 02:32:32 GMT
To: morrowc.lists@gmail.com
Cc: joelja@bogus.com, john@sackheads.org, patrick@ianai.net, nanog@merit.edu
Errors-To: owner-nanog@merit.edu


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- -- "Christopher Morrow" <morrowc.lists@gmail.com> wrote:

>>  Well... If you want to work on one, I'm willing help shepherd it
>> through =

>>  the process. We even have a working group setup for that purpose.
>
>proposal for work in GROW?

Actually, that sounds reasonable -- if GROW [1] outcomes are heeded
by the operations community.

Historically, it seems, the Internet operations community picks
and chooses the IETF RFCs/BCPs that each ISP implements on a
"one-off" basis.

Something (else) that I have long admired is the way the RIPE
community has built working groups around critical issues.

I'm still convinced that the NANOG community -- perhaps in
collaboration with RIPE and APNIC, et al -- should work to
craft ISP "best current practices" in these areas, since ISPs
don't seem to heed IETF documents, except when it serves their
own business & operational practices.

- - ferg

[1] http://www.ietf.org/html.charters/grow-charter.html

-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.6.3 (Build 3017)

wj8DBQFHxMu8q1pz9mNUZTMRAk/wAJ9Mm3sWL9t1cCfy8sAhTd6DfxMIGwCfTauG
9lha9MMTiR4kPoPEHtBjfRQ=3D
=3DatCM
-----END PGP SIGNATURE-----


--
"Fergie", a.k.a. Paul Ferguson
 Engineering Architecture for the Internet
 fergdawg(at)netzero.net
 ferg's tech blog: http://fergdawg.blogspot.com/


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