CURRENT_MEETING_REPORT_ Reported by Martha Steenstrup/BBN IDPR Minutes The Inter-Domain Policy Routing Working Group met for two sessions in Atlanta. As usual, we conducted a tutorial for the first half of the first session. We spent the rest of the time discussing two new IDPR documents recently released as Internet Drafts. The documents are a configuration guide and a MIB. As the documents became available shortly before the IETF meeting, we did not expect that people would have had time to read them. Instead, we gave an overview of the content of each document, and we raised the issues that are not yet closed. The main open configuration issue is the following. We advocate using the existing domain name servers to resolve addresses to administrative domain identifiers. This feature is not yet available in the DNS but would not be difficult to add. The open questions are: o Is the DNS in fact the correct place for this functionality? o Should the address input be at the level of network, subnet, or host? o How do we handle the traversal of the DNS hierarchy? There are two open MIB issues. 1. What information to put in the MIB. IDPR has more configuration parameters than most routing protocols and more potential quantities to measure, because of policy support. The MIB contains a first cut at what information we expect that people will want to measure. However, some of the information is of general use, while other pieces of information are of most use to experts who know the details of the protocols. We want to make sure that we provide enough information in the MIB to allow problem detection, but we don't want to overload the MIB with information only useful for detailed fault detection and correction. 2. How to represent policy information. IDPR allows a domain administrator to configure transit policies that apply to traffic traversing its domain and source policies that apply to traffic generated by hosts in its domain bound for hosts in other domains. The current draft of the MIB does not contain policy information, because we had not at that time decided on how best to represent this information. At the Working Group meeting, we tentatively decided on an approach, and the next version of the MIB will contain this information. 1 We are seeking constructive criticism on both the MIB and configuration guide documents. Please send all comments to idpr-wg@bbn.com. Attendees Nagaraj Arunkumar nak@3com.com James Beers Helen Bowns hbowns@bbn.com John Chang jrc@uswest.com George Clapp meritec!clapp@uunet.uu.net Richard Cogger Dimitry Haskin dhaskin@bbn.com Tony Li tli@cisco.com Keith McCloghrie kzm@hls.com Paul Mockapetris pvm@darpa.mil Andy Nicholson droid@cray.com Chandy Nilakantan csn@3com.com Yakov Rekhter yakov@ibm.com Mark Sleeper mws@sparta.com Martha Steenstrup msteenst@bbn.com Robert Woodburn woody@cseic.saic.com L. Michele Wright uncng!michele@uunet.uu.net Osmund de Souza desouza@osdpc.ho.att.com 2