CURRENT_MEETING_REPORT_ Reported by Sue Hares/Merit and Bill Manning/SESQUINET Minutes of the OSI IDRP for IP over IP Working Group (IPIDRP) Agenda o Discussion of the Working Group Charter. o Review of IDRP for IP Document. o ISIS-IDRP Interactions Paper. o Next Steps. Susan Hares (Chair) led the discussions and gave the presentations. Working Group Charter A great deal of discussion occurred about the Working Group Charter. The focus was what documents should be developed. The documents to be developed are: o IDRP for IP: Merit will implement a version by Nov'92. o MIB: Sue will derive from BGPv3. Not further discussed here. o Useage Document. A great deal of discussion was given to what should go in the Usage document. In the usage document should go: - History of the protocol. - Typical scenarios for Useage IDRP in Internet. - Sample Policy description language. - How IDRP interacts with CIDR and C#. A great deal of discussion was engaged in about whether interactions to other protocols belong in a usage document. It was decided the interactions should go in separate documents. Interactions that will need to be discussed are: IDRP <-> ISIS, IDRP <->EGP, IDRP <-> BGP2/BGP3/BGP4. These documents will be new documents added to the Working Group Charter. The family tree document will tie these documents together. Review of IDRP for IP Document IDRP for IP can not assume correct routing if the addresses used are NOT globally unique. Mentioned because some proposal to fix the IP addressing problems do not guarantee this. This basic assumption will be placed in a section in the beginning of the document. 1 A great deal of discussion centered around a QOS flag for RE, and asynchronous routes. Many people thought asynchronous routes provide problems for users, but some people challenged this discussion. ISIS-IDRP Paper Overview One goal of the ISIS-IDRP interactions is to allow a BIS to learn things from the IGP IS-IS. A tutorial was given about this. The paper can be obtained from merit.edu in /pub/iso/isisidrp.ps. This paper was presented to the SC6 committee during their July meeting which ran the same time as IETF. BIS can learn network layer reachability information from IS-IS in three methods: o No Summarization: - Skipped over the MIB ways - Mash into the NRLI - use mask o Automatic: - Local RDI template o Pre-configured Given some IS-IS changes, BIS can discover each other via IS-IS. IDRP information can either be tunneled through a domain or injected into the IGP for transmittal across the domain. A discussion occurred on how you choose when to tunnel vs. inject into the IGP. Tunneling can be based on overload bit in IS-IS. Dennis Ferguson (CA*NET) suggested we should ask for this type of feature in IP. We need a general specification on tunneling, otherwise there will be problems. Tunneling brings up the issue of encapsulating CLNP in IP or IP in IP. Vint Cerf suggested that we look at earlier work in multiple encapsulations. Vint suggested Paul Tsuchiya's paper on encapsulation loops. Action Items o Discussion of ASYNC routes on this list. o New Charter published by Chair. o Document delivered in August. o EGP-IDRP interactions document helpers: Scott Brim, Sue Hares o BGP-IDRP interactions document helpers: Scott Brim, Sue Hares o OSPF-IDRP interactions document helpers: Suggested to catch Kannan who wrote BGP-OSPF document. 2 Attendees Nagaraj Arunkumar nak@3com.com Tony Ballardie a.ballardie@cs.ucl.ac.uk William Barns barns@gateway.mitre.org Tony Bates tony@ean-relay.ac.uk David Bolen db3l@nis.ans.net Scott Brim swb@cornell.edu Ross Callon callon@bigfut.enet.dec.com Vinton Cerf vcerf@nri.reston.va.us John Chang jrc@uswest.com Richard Colella colella@osi.ncsl.nist.gov Michael Conn 004387451@mcimail.com Michael Craren mjc@proteon.com Richard desJardins desjardi@boa.gsfc.nasa.gov Pierre Dupont dupont@mdd.comm.mot.com Steven Fancher sfancher@ursa-major.spdcc.com Dennis Ferguson dennis@mrbill.canet.ca Vince Fuller vaf@stanford.edu Susan Hares skh@merit.edu Dimitry Haskin dhaskin@bbn.com Matthew Jonson jonson@server.af.mil James Keller j.keller@sprint.com Paulina Knibbe knibbe@cisco.com Mark Knopper mak@merit.edu Mark Knutsen knutsen@almaden.ibm.com Walter Lazear lazear@gateway.mitre.org Whay Lee whay@merlin.dev.cdx.mot.com Tony Li tli@cisco.com Kent Malave kent@chang.austin.ibm.com Bill Manning bmanning@rice.edu Douglas Miller dmm@telebit.com Dennis Morris morrisd@imo-uvax.disa.mil Kraig Owen tko@merit.edu James Pearl jim@microcom.com Roy Perry rperry@uswat.uswest.com David Piscitello dave@sabre.bellcore.com Bala Rajagopalan braja@qsun.att.com Yakov Rekhter yakov@watson.ibm.com April Richstein abm@tycho.ncsc.mil Erik Sherk sherk@sura.net Rajesh Srivastava rajesh@flash.tandem.com Sally Tarquinio sallyt@gateway.mitre.org Fumio Teraoka tera@csl.sony.co.jp Marten Terpstra terpstra@ripe.net Kannan Varadhan kannan@oar.net Cathy Wittbrodt cjw@nersc.gov 3