Document Action: A BGP/IDRP Route Server alternative to a full mesh routing to Experimental
IESG Secretary <iesg-secretary@CNRI.Reston.VA.US> Fri, 15 September 1995 20:57 UTC
Received: from [132.151.1.1] by IETF.CNRI.Reston.VA.US id aa21923;
15 Sep 95 16:57 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa06755;
15 Sep 95 16:57 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa21852;
15 Sep 95 16:57 EDT
Received: from [132.151.1.1] by IETF.CNRI.Reston.VA.US id aa21522;
15 Sep 95 16:46 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa03431;
15 Sep 95 16:46 EDT
Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa21509;
15 Sep 95 16:45 EDT
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: bgp@ans.net
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: IESG Secretary <iesg-secretary@CNRI.Reston.VA.US>
Subject: Document Action: A BGP/IDRP Route Server alternative to a full
mesh routing to Experimental
Date: Fri, 15 Sep 95 16:45:53 -0400
X-Orig-Sender: scoya@CNRI.Reston.VA.US
Message-ID: <9509151645.aa21509@IETF.CNRI.Reston.VA.US>
The IESG has reviewed the Internet-Draft "A BGP/IDRP Route Server alternative to a full mesh routing" <draft-haskin-bgp-idrp-mesh-routing-01.txt> and recommends that it be published by the RFC Editor as an Experimental RFC. This document is the product of the Inter-Domain Routing Working Group. The IESG contact person is Joel Halpern.
- Document Action: A BGP/IDRP Route Server alternat… IESG Secretary
- Document Action: A BGP/IDRP Route Server alternat… IESG Secretary