IETF Logo Mail Archive

Re: Route Tag

Fred Baker <fbaker@acc.com> Thu, 02 April 1992 20:17 UTC

Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa08445; 2 Apr 92 15:17 EST
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa23541; 2 Apr 92 15:20 EST
Received: from harvard.harvard.edu by NRI.Reston.VA.US id aa23536; 2 Apr 92 15:20 EST
Received: by harvard.harvard.edu (5.54/a0.25) (for IETF-archive@nri.reston.va.us) id AA01760; Thu, 2 Apr 92 15:15:18 EST
Received: from saffron.acc.com (2040c081) by Xylogics.COM (4.12/4.7_jlv1/7/90) id AA26582; Thu, 2 Apr 92 15:15:55 est
Received: by saffron.acc.com (4.1/SMI-4.1) id AA13992; Thu, 2 Apr 92 12:14:16 PST
Date: Thu, 02 Apr 1992 12:14:16 -0800
From: Fred Baker <fbaker@acc.com>
Message-Id: <9204022014.AA13992@saffron.acc.com>
To: gmalkin@xylogics.com
Subject: Re: Route Tag
Cc: ietf-rip@xylogics.com

I'd be willing to go with the authentication approach;
it makes the authentication field an instance instead of the route domain,
if that matters

Fred

v2.41.0 | Report a Bug | By Email | System Status