Last Call: A BGP/IDRP Route Server alternative to a full mesh routing to Experimental
The IESG <iesg-secretary@CNRI.Reston.VA.US> Sun, 20 August 1995 16:15 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10133;
20 Aug 95 12:15 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa10129;
20 Aug 95 12:15 EDT
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa09727;
20 Aug 95 12:15 EDT
Received: by interlock.ans.net id AA37896
(InterLock SMTP Gateway 3.0 for iwg-out@ans.net);
Sun, 20 Aug 1995 12:07:05 -0400
Message-Id: <199508201607.AA37896@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2);
Sun, 20 Aug 1995 12:07:05 -0400
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1);
Sun, 20 Aug 1995 12:07:05 -0400
To: IETF-Announce: ;
Cc: bgp@ans.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: The IESG <iesg-secretary@CNRI.Reston.VA.US>
Subject: Last Call: A BGP/IDRP Route Server alternative to a full mesh
routing to Experimental
Reply-To: IESG <iesg@IETF.CNRI.Reston.VA.US>
Date: Sun, 20 Aug 95 12:04:25 -0400
X-Orig-Sender: scoya@CNRI.Reston.VA.US
The IESG has received a request from the Inter-Domain Routing Working Group to consider "A BGP/IDRP Route Server alternative to a full mesh routing" <draft-haskin-bgp-idrp-mesh-routing-01.txt> as an Experimental Protocol. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@cnri.reston.va.us or ietf@cnri.reston.va.us mailing lists by September 1, 1995.