IDR WG meeting in Stockholm
yakov@watson.ibm.com Thu, 25 May 1995 13:20 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa02248;
25 May 95 9:20 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa02244;
25 May 95 9:20 EDT
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa06097;
25 May 95 9:20 EDT
Received: by interlock.ans.net id AA59524
(InterLock SMTP Gateway 3.0 for iwg-out@ans.net);
Thu, 25 May 1995 09:10:31 -0400
Message-Id: <199505251310.AA59524@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2);
Thu, 25 May 1995 09:10:31 -0400
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1);
Thu, 25 May 1995 09:10:31 -0400
Date: Thu, 25 May 95 09:03:29 EDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: yakov@watson.ibm.com
To: bgp@ans.net
Subject: IDR WG meeting in Stockholm
Folks, As the next IETF is less than 2 months ahead, I'd like to solicit from you topics you'd like to discuss at the next IDR WG meeting. Please send your suggestions. Among the things I'd like us to do at the meeting is to advance BGP-4 to a Full Standard. As far as I know there are two things that we need to fix in the current BGP-4 spec: - handling of unrecognized Optional Parameters in the OPEN message - need to add some text on suppressing routing information looping We (Tony and myself) expect to have a revised version of the protocol spec really soon. If there are other outstanding items wrt to BGP-4 please let us know as soon as possible. Yakov. P.S. We got for our meeting two slots. If you think we need more, please send me a note.