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:14 UTC
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa10079;
20 Aug 95 12:14 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa09697;
20 Aug 95 12:14 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10006;
20 Aug 95 12:14 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09789;
20 Aug 95 12:04 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa09543;
20 Aug 95 12:04 EDT
Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa09784;
20 Aug 95 12:04 EDT
To: IETF-Announce: ;
cc: bgp@ans.net
Sender: ietf-announce-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
Message-ID: <9508201204.aa09784@IETF.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.