Re: musings

Fred Baker <> Thu, 16 May 1996 22:38 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa27050; 16 May 96 18:38 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa27046; 16 May 96 18:38 EDT
Received: from by CNRI.Reston.VA.US id aa05468; 16 May 96 18:38 EDT
Received: by (5.65c/5.61+local-23) id <AA10721>; Thu, 16 May 1996 15:21:00 -0700
Received: from by (5.65c/5.61+local-23) id <AA10715>; Thu, 16 May 1996 15:20:59 -0700
Received: from by (5.65c/5.61+local-23) id <AA20651>; Thu, 16 May 1996 15:20:58 -0700
Received: from [] ( []) by (8.6.8+c/8.6.5) with SMTP id PAA23060; Thu, 16 May 1996 15:20:51 -0700
Message-Id: <v02140b0dadc15635c9ee@[]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 16 May 1996 15:20:53 -0700
To: Robert Elz <>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Fred Baker <>
Subject: Re: musings
Precedence: bulk

At 7:36 AM 5/17/96, Robert Elz wrote:
>If one did feel the need to find an implementation of rreq, I'm
>not sure I'd be looking inside routers anyway - in there I'd
>find implementations of BCP, PPP, OSPF, IP TCP, ...   For rreq
>I think I'd look in the tender or RFP docs, see whether rreq has
>been specified, and used - that's probably what is an implementation
>of 1812, if anything is.

Oh, it's used. They ask "do you conform?". We say "no." They send money.

Since it was pointed out to me that we can't use path mtu with
PIM/DVMRP/etc because 1812 says "don't do path mtu on multicast packets," I
think that if we're going to go to BCP we should change that first.

Meddle not in the affairs of dragons, for you are crunchy and taste
good with ketchup.