CURRENT_MEETING_REPORT_ Reported by Paul Traina/cisco Systems Minutes of the Inter-Domain Routing Working Group (IDR) The IDR Working Group is the result of a merge between the Border Gateway Protocol Working Group (BGP) and the OSI IDRP for IP Over IP Working Group (IPIDRP). These minutes are from the joint session of BGP and IPIDRP that was held at the IETF in Toronto. Agenda o Agenda bashing o New group charter review o BGP-4 status update o BGP/OSPF interaction document o AS space growth o IDRP implementation report o Inter-domain routing for IPng o Deprecation of EGP New Group Charter Review The BGP and IDRP groups have been meeting in joint session for a long time. There was consensus that the two working groups should be merged into a single group which will handle the inter-domain routing area. Yakov and Sue were suggested as co-chairs for the new group and the name suggested by the attendees is ``Inter-Domain Routing Working Group'' or IDR Working Group. BGP-4 Document Status Update All current BGP-4 documents have been moved to Proposed Standard status. In point of fact, all requirements have been met to move BGP-4 to Draft Standard except that the six month timer in Proposed Standard status has not expired yet. Paul Traina will produce final documents (protocol analysis and operational experience) needed for advancing BGP-4 to Draft Standard. The documents could be based on similar documents produced for BGP-3 (RFC 1265 and RFC 1266). Once BGP-4 reaches Draft Standard, it is expected that BGP-3 will become obsolete. BGP/OSPF Interaction Document Before this IETF, Kannan Varadhan updated the BGP-4/OSPF interaction document. No protocol or technical changes were made. Comments were made by several attendees that the new tables that were added made things more obscure. Suggestions are to be sent to Kannan over the next month. At the close of the comment period, the document will be revised (hopefully for the last time) and this revision will be moved to Proposed Standard. There are currently four reported implementations of BGP-4/OSPF interaction as described by this document: cisco, gated, Proteon, and Wellfleet. AS Space Growth There are currently 4000 AS entries allocated by the IANA out of a possible space of 65,535. Of these allocated entries, 400 of them currently appear in AS path tables as analyzed by Tony Bates. There is some concern that the AS space will be used up in the same fashion as the IPv4 address space. Things to be done: o Monitor AS usage and allocation growth o Instruct the IANA, NSPs and NICs to treat ASs as a finite resource and grant them according to a set of guidelines o Encourage vendors who suggest that all sites apply for an AS number to change their documentation o Further consideration of this issue to be referred to the CIDRD and ALE Working Groups John Hawkinson will coordinate with Tony Bates to write guidelines as to when AS numbers should be issued. IDRP Implementation Report David Jacobson presented a status report on a prototype IDRP implementation that was funded by the National Science Foundation and will be made publicly available shortly. IPng Transition The group reached clear consensus that BGP-4 will not be extended or modified for IPng, rather IDRP will be used as a basis for the IPng IDRP. IDRP will be used with the following changes: o IDRP's MULTI_EXIT_DISCRIMINATOR and LOCAL_PREF fields will be changed from one octet to four octets in length to match BGP-4. o A form of BGP-4's optional AGGREGATOR attribute will be added to IDRP. o IDRP will be changed to not prepend the local RD to the RD path until an advertisement is sent outside the current RD (a la BGP). If reason(s) can be found for this change between BGP and IDRP, this will need to be reviewed. Tony Li, Yakov Rekhter and Paul Traina will write the IDRP for IPng document. Dennis Ferguson will write a document describing constraints upon IDRP to ease the transition from BGP to IDRP/IP and eventually IDRP/IPng. Fred Baker, Dennis Ferguson and Paul Traina will produce a document that will be presented by the working group to the people working on IPng's IGPs listing desired features in an IGP that will improve IGP/IDRP cooperation (examples might include carrying RD path information, extending tag fields, etc.). Vadim Antonov has volunteered to write an Internet-Draft on security and authentication uses and requirements for an IDRP. A volunteer is needed to write an IDRP $ IGP interaction document covering both IPv4 and IPng. EGP Consensus among the group was to move EGP in all forms to Historic status. This will be conveyed to the IESG for appropriate actions.