Here are the minutes of the last meeting. Comment/corrections welcome, -- Jean-Michel RIPE Routing-WG Draft Minutes Lisbon, Tuesday September 13th 1994 Minutes: Jean-Michel Jouanigot, Gilles Farrache (scribe) 0. Previous minutes, agenda. The previous minutes and the agenda were approved. Gilles Farrache volunteered once again (?) as a scribe. 1. Ripe-81++ and companion documents Reading: URL ftp://ftp.ripe.net/ripe/drafts/ripe-81++.{txt,ps} 1.1 Summary of changes since last version of the draft Reading: URL ftp://ftp.ripe.net/ripe/drafts/ripe-81++.changes.{txt,ps} Tony Bates presented the modifications added into the Ripe-81 draft document since the Working group meeting in Amsterdam: - Network lists have been added - More information on the default route generation - "sugar" added - as-reject is renamed as-exclude - line wrapping feature - 'Component' attribute is replaced by 'withdrawn' and 'hole' - A new router object has been created: inet-rtr - The evaluation of the various operators (OR, AND,...) has been clarified - An 'as-name' attribute has been added to the aut-num object (optional, for transition reasons, but will become mandatory) The Working group unanimously agreed these modifications. 1.2 Outstanding issues: interas-in/out and as-in/out The interas-in/out attribute in the aut-num object is needed to represent local policies between two ASes peering at several points. The possibility to merge the as-in/out and interas-in/out attributes was rejected because of clarity and the fact that only the global policy (expressed in as-in/out) is relevant to other ASes. To identify a peering, the local and remote ID routers are needed (ID means here the interface addresses, not the BGP router ID). A syntax was agreed for the interas-in/out attribute: interas-in: [from] ASxxx <local id> <neighbor id> <pref> <policy> It was agreed that both <local id> and <neighbor id> are mandatory. It was also noted that as-in/out attributes can be filled automatically if only the interas-in/out attributes are present. This is an implementation issue when registering and object, but the output of a database query MUST contain the corresponding as-in/out attribute when an interas-in/out attribute is present. It was agreed that these decisions should be integrated into the current draft (or clarified when already present); this draft will be presented as the final document to RIPE, sent to the list, and hopefully agreed. Deadline for comments was fixed to Friday September 30th 1994. The final Ripe-81++ document will be renamed Ripe-181. It also was proposed to publish this document more widely (i.e. FYI) so that other routing registries may join the effort. Final decision will be taken when the final document is approved. 2. Router object Reading: URL ftp://ftp.ripe.net/ripe/drafts/inet-rtr.ps The previous 'inetnum:' object used to have an 'ias-int' attribute to help the tools (i.e. prtraceroute) to determine which AS a router interface belongs to. In the new database model, a new object describing the internet routers has been created to register this information as well as peering relationships. It was proposed and agreed to also register the network mask for an interface using the syntax: ifaddr: <address> mask <mask> It was also agreed that the list of routing protocols allowed in the peering information should be flexible, and that IGP was too generic. Using the name (and sometimes version) of the protocol helps in determining if the routing protocol is CIDR capable or not. The Working Group unanimously agreed that this object should not be used for the configuration of routers. It was agree to propose these extensions to the Database Working group ask them to approve the changes urgently. 3. AOB The chairman thanked the working group members for their active participation, Merit for their very valuable input and the PRIDE project for its essential contribution to this work. A new charter for the group is to be proposed. Comments/suggestions should be sent to the list. [eof]