• Meeting Home


• Agendas
• Attendees List
• Connectivity Info
• Dinner Venue
• EOF
• Feedback Trials
• General Info
• Hostmaster
  Consultation Centre
• Hotel Information
• Meeting Plan
• Meeting Venue
• Meet & Greet!
• Minutes
• RIPE NCC Service Desk
• Plenary Agenda
• Presentations
• Registration
• Sessions Archive
• Sponsorship
• Tutorials and Courses
• Webcasts

RIPE 47 Meeting

European Operators Forum

Preliminary Programme:

There will be no morning session on Monday, 26 January 2004.

About the EOF

Abstracts of Presentations and Tutorials

Monday:

Title: NSP Security BOF
Speaker: Danny McPherson

The purpose of this BOF is to encourage interaction and information sharing between service providers regarding network security related events. The agenda of this BOF is loosely structured and the environment is meant to encourage discussion among attendees.

Title: Fighting spam is interesting, but where?
Speaker: Patrik Falstrom

The last year it has become very interesting finding different mechanisms which are supposed to fight spam. Outside people not understanding the situation better than what is described in the evening newspaper ask "which one of these solutions will be the holy grail of spam fighting" when the truth is that we might need many different mechanisms.

One thing which have been missing in many discussions is where each one of these mechanisms are to be applied. "Where" in the form of "what paths in the possible SMTP flows is to be involved". I.e. a couple of years ago it was agreed to in the community that so called "open relays" are bad.

My personal view is that we need to use similar mechanisms to identify similar paths which might be good or bad, or have to be authenticated in various ways.

I will in this presentation go through what I think are the possible paths in a world where we use SMTP, and explain why I think some of them should be blocked (just like we today try to block open relays), and (might be important) why I think ISP's blocking port 25 are doing the wrong thing.

Description of what is to be discussed (PDF)

This is related to the work in the ASRG wg in the IRTF. Myself, as a member of the Internet Architecture Board, I am overlooking what ASRG (and other bodies) are doing which are related to SPAM and IETF work.

Title: AOL Backbone OSPF-ISIS Migration
Speaker: Vijay Gill
Abstract: This talk describes the AOL backbone network conversion from a multi-area OSPF IGP to IS-IS. Topics covered include reasoning for the migration, implementation, verification, and deployment of IS-IS in a live network with no visible impact to the service.

The emphasis will be on the actual experience gained while doing this.

- Draft Presentation

http://www.nanog.org/mtg-0310/gill.html

Title: RISwhois - mapping IP to ASN using RIS collected BGP data
Speaker: René Wilhelm (RIPE NCC)
Abstract: RISwhois is a new interface from the RIPE NCC to RIS data. It provides a comprehensive, looking-glass type of view of an entire set of BGP tables collected by the remote route collectors. Specifically, handed an IPv4 or IPv6 address, RISwhois will answer the question of which AS(es) are seen originating prefixes including that IP number. This presentation covers the concepts of RISwhois, the relation to other RIS query tools and provides examples of its use.

Relation to other known work and/or presentations if known:

• route-views @oregon.edu offer ip2asn mapping via DNS
  (host -a 1.0.0.193.asn.routeviews.org)

• Team Cymru have whois ip2asn using a format uncompatible with RPSL
  (whois -h whois.cymru.com 193.0.0.1)

• RISwhois' similarity to RPSL objects allows easy replacement of IRR servers in existing applications needing ip2asn mapping

Tuesday:

Integrated session: The actual times of the presentations may vary.

Title: IETF Network Configuration (NETCONF) Working Group
Speaker: Simon Leinen
Abstract: The IETF NETCONF (Network Configuration) Working Group has been formed in Spring 2003. Its task is to produce a protocol for the configuration of network devices. Network configuration had been identified as an area where operators - and those who develop tools for them - are suffering from the absence of useful standards. The new protocol will be based on the Extensibe Markup Language (XML), which is at least somewhat human-readable,supports complex hierarchical data structures that are common in device configurations, is extensible without dependence on a central instance, and enjoys wide industry acceptance, which leads to the availability of an abundance of support libraries.

In my talk, I'll outline the current state of the NETCONF protocol standardization effort, including a few example message exchanges. There are still many open design questions, and input from network operators is important to sort these out. A primary goal of this session is to get feedback from the EOF community - by bringing interested operators up to speed and encouraging them to participate in the NETCONF WG, but also (time permitting) by having an open discussion on operators' issues with, and requirements for, network configuration management.

Further reading and related presentations:

See the NETCONF WG Web site: http://www.ops.ietf.org/netconf/

NANOG28 in June 2003 had two slots on XML-based configuration management, see
http://www.nanog.org/mtg-0306/xml.html (panel)
http://www.nanog.org/mtg-0306/enns.html (tutorial)

At SWINOG 7 in October 2003, I gave an overview over the NETCONF WG's work and status:
http://www.swinog.ch/meetings/swinog7/netconf_swinog7.pdf

Title: NetML, a Network Markup Language
Speaker: Ivan Santarelli
Abstract: NetML is a language for describing computer networks. It is based on XML and its grammar is defined using XMLSchema, which allows for greater accuracy on data type definition and document structure. This allows the use of existing XML tools to perform analysis, transformations and many other operations directly on the network description. NetML comes with two tools written in Java that make use of the Xerces and Xalan libraries: one generates the configuration files for the routers belonging to the network (for Cisco, Juniper-text format, Juniper-xml format and Zebra routing daemon), the other produces a script for Netkit (a virtual network environment based on user-mode-linux) that starts the network in a virtual environment.

The presentation will give an overview of NetML. It will:

• Explain the levels that can be described and how
• Provide examples of network descriptions and the resulting generated router configurations and virtual networks
• Explain the role that a language like NetML can have when designing a network

It would also be an opportunity to better understand the needs of standardization in terms of network description and router configuration through feedback from the community.

For more information:

• NetML Home Page: http://giga.dia.uniroma3.it/~ivan/NetML
• Netkit Home Page: http://www.netkit.org/
• Computer Networks Research Group, Roma 3 University: http://www.dia.uniroma3.it/~compunet/

Title: The JUNOScript API
Speaker: Ian Jarrett
Abstract: This presentation provides an overview of the JUNOScript API from Juniper Networks (www.juniper.net). JUNOScript is an application programming interface supported on all Juniper Networks M and T-Series routers that allows client applications to exchange management information with routers as structured XML documents. The presentation begins with an introduction to XML, the JUNOS operating system and the access methods currently supported. It then explains how client applications can communicate with routers to exchange management information, including how this can be used to configure the routers themselves and the services that they provide. Examples are provided in the perl (www.perl.org) language and will show how to write clients that access Juniper router, and where possible these will be demonstrated.