[162109] in North American Network Operators' Group

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

Re: RFC 1149

daemon@ATHENA.MIT.EDU (Steven Bellovin)
Tue Apr 2 18:45:13 2013

From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <55A3CE6F-6688-47A4-94B9-E0B7A2DF9B77@delong.com>
Date: Tue, 2 Apr 2013 18:44:57 -0400
To: Owen DeLong <owen@delong.com>
Cc: 'NANOG' <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

DLT?  I first heard it as a station wagon full of (9-track, 1600 bpi,
that having been the state of the art) mag tapes on the Taconic Parkway,
circa 1970.  I suspect, though, that Herman Hollerith expressed the idea 
about a stage coach full of punchcards, back in the 1880s.


On Apr 2, 2013, at 3:41 PM, Owen DeLong <owen@delong.com> wrote:

> "Never underestimate the bandwidth of a 747 full of DLT cartridges."
> 
> Owen
> 
> On Apr 2, 2013, at 11:31 , "Scott Berkman" <scott@sberkman.net> wrote:
> 
>> Hey careful, Pigeons have won this fight before:
>> 
>> http://news.bbc.co.uk/2/hi/8248056.stm
>> 
>> -----Original Message-----
>> From: George Herbert [mailto:george.herbert@gmail.com] 
>> Sent: Monday, April 01, 2013 10:37 PM
>> To: Jeff Kell
>> Cc: NANOG
>> Subject: Re: RFC 1149
>> 
>> Packets, shmackets.  I'm just upset that my BGP over Semaphore Towers
>> routing protocol extension hasn't been experimentally validated yet.
>> 
>> Whoever you are who keeps flying pigeons between my test towers, you can't
>> deliver packets without proper routing updates!  Knock it off long enough
>> for me to converge the #@$#$@ routing table...
>> 
>> 
>> 
>> On Mon, Apr 1, 2013 at 7:19 PM, Jeff Kell <jeff-kell@utc.edu> wrote:
>> 
>>> On 4/1/2013 10:15 PM, Eric Adler wrote:
>>>> Make sure you don't miss the QoS implementation of RFC 2549 (and 
>>>> make
>>> sure
>>>> that you're ready to implement RFC 6214).  You'll be highly 
>>>> satisfied
>>> with
>>>> the results (presuming you and your packets end up in one of the 
>>>> higher quality classes).
>>>> I'd also suggest a RFC 2322 compliant DHCP server for devices inside 
>>>> the hurricane zone, but modified by implementing zip ties such that 
>>>> the C47s aren't released under heavy (wind or water) loads.
>>> 
>>> Actually, given recent events, I'd emphasize and advocate RFC3514
>>> (http://www.ietf.org/rfc/rfc3514.txt) which I think is LONG overdue 
>>> for adoption.  The implementation would forego most of the currently 
>>> debated topics as related to network abuse or misuse :)
>>> 
>>> Jeff
>>> 
>>> 
>>> 
>> 
>> 
>> --
>> -george william herbert
>> george.herbert@gmail.com
>> 
> 
> 
> 


		--Steve Bellovin, https://www.cs.columbia.edu/~smb







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