[Idr] Last Call: 'A Border Gateway Protocol 4 (BGP-4)' to Draft Standard
The IESG <iesg-secretary@ietf.org> Mon, 22 March 2004 10:00 UTC
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13564 for <idr-archive@ietf.org>; Mon, 22 Mar 2004 05:00:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B5MEB-0000bW-00 for idr-archive@ietf.org; Mon, 22 Mar 2004 05:00:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B5MDD-0000Tj-00 for idr-archive@ietf.org; Mon, 22 Mar 2004 04:59:16 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B5MC5-0000Hj-00; Mon, 22 Mar 2004 04:58:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B5MBS-0002CM-8C; Mon, 22 Mar 2004 04:57:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B3M8J-0004kH-8o for idr@optimus.ietf.org; Tue, 16 Mar 2004 16:29:55 -0500
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26447 for <idr@odin.ietf.org>; Tue, 16 Mar 2004 16:29:52 -0500 (EST)
Received: from nobody by optimus.ietf.org with local (Exim 4.20) id 1B3M7o-0004hU-Uk; Tue, 16 Mar 2004 16:29:24 -0500
X-test-idtracker: no
To: IETF-Announce:;
Cc: idr@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Reply-to: iesg@ietf.org
Message-Id: <E1B3M7o-0004hU-Uk@optimus.ietf.org>
Subject: [Idr] Last Call: 'A Border Gateway Protocol 4 (BGP-4)' to Draft Standard
Sender: idr-admin@ietf.org
Errors-To: idr-admin@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/mail-archive/working-groups/idr/>
Date: Tue, 16 Mar 2004 16:29:24 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=1.4 required=5.0 tests=AWL, TO_HAS_SPACES autolearn=no version=2.60
The IESG has received a request from the Inter-Domain Routing WG to consider the following set of documents updating the Border Gateway Protocol 4 specification. BGP4 protocol-related documents: - 'A Border Gateway Protocol 4 (BGP-4) ' <draft-ietf-idr-bgp4-23.txt> as a Draft Standard - 'BGP Security Vulnerabilities Analysis ' <draft-ietf-idr-bgp-vuln-00.txt> as an Informational RFC - 'BGP-4 Protocol Analysis ' <draft-ietf-idr-bgp-analysis-04.txt> as an Informational RFC - 'Experience with the BGP-4 Protocol ' <draft-ietf-idr-bgp4-experience-protocol-03.txt> as an Informational RFC BGP4 MIB-related documents: - 'Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4) ' <draft-ietf-idr-bgp4-mib-13.txt> as a Proposed Standard Implementation reports: - 'BGP 4 Implementation Report ' <draft-ietf-idr-bgp-implementation-00.txt> as an Informational RFC - 'BGP MIB V1 implementation survey ' <draft-ietf-idr-bgp-mibagent-survey-00.txt> as an Informational RFC The documents above satisfy the standardization criteria for Routing Protocols described in RFC 1264. Since draft-ietf-idr-bgp4-23.txt specifies the TCP MD5 Signature Option (RFC 2385), which is a Proposed Standard, as the mandatory to implement authentication mechanism, the IESG is planning to apply the variance procedure per RFC 2026 to allow the BGP4 protocol specification at the Draft Standard level to have a normative reference to RFC 2385. The variance prodedure request is documented in the following document: - 'Standards Maturity Variance Regarding the TCP MD5 Signature Option (RFC 2385) and the BGP-4 Specification ' <draft-iesg-tcpmd5app-00.txt> as an Informational RFC 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@ietf.org or ietf@ietf.org mailing lists by 2004-04-13. The files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp4-23.txt http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp-vuln-00.txt http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp-analysis-04.txt http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp4-experience-protocol- 03.txt http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp4-mib-13.txt http://www.ietf.org/internet-drafts/draft-iesg-tcpmd5app-00.txt Implementation Reports can be accessed at http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp-implementation-00.txt http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp-mibagent-survey-00.tx _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr