CURRENT_MEETING_REPORT_
Reported by Philip Almquist/Consultant
RREQ Minutes
Shortly before the St. Louis meeting, the second Internet Draft version
of the Router Requirements specification was released. Except for a few
open issues (described below), the technical content of the document is
fairly well set. Extensive editorial work remains to be done.
On the first day of the meeting, the Chair conducted a brief
``Introduction to Router Requirements'' session for first-time attendees
and anyone else who was interested. After that, the Working Group dove
into four half days of meetings.
Three of the four sessions were devoted to fine-tuning the draft.
Particular attention was paid to chapters 3 (Link Layer), 4 (Internet
Layer Protocols), 9 (Miscellaneous Application Layer Protocols), and 10
(Operations and Maintenance). We also discussed what still needed to be
done to complete the draft. Items identified included:
o Chapter 8 (Network Management) still needs to be written.
o Much of chapter 9 (Miscellaneous Application Protocols) still needs
to be written.
o Coverage of security-related topics needs to be extended.
o There should be additional discussion sections providing
implementation hints and explaining the rationale behind some of
the requirements.
o Several smaller sections need to be written or revised.
o As mentioned above, extensive editorial work is still required.
Volunteers were solicited to do the necessary work. The issue of
variable length subnet masks was also raised. Since the IETF Working
Group on this topic is still not underway, we tentatively decided that
Router Requirements would have to partially skirt this issue, though we
will say more than the current draft does.
The remaining session was devoted to discussion of three important and
interrelated issues: 1
1. Route choice -- how a router chooses which route to use to use for
a packet when the router has several routes (learned from different
routing domains) to the packet's destination.
2. Route leaking -- how a router which is in multiple routing domains
decides whether a route learned in one routing domain ought to be
advertised into other routing domains.
3. Route filtering -- how a router decides whether to disbelieve
certain routes from certain sources.
Each of these issues has two components:
1. Constraints -- what must (or must not) be done to avoid undesirable
phenomena such as routing loops and black holes?
2. Controls -- what sorts of configuration options does a network
manager need to be able to do to make routing work in moderately
complex parts of the Internet?
The Working Group was not able to reach any consensus on these issues,
but will continue to try to address them in the time before the IETF
meeting in Atlanta in July. However, several Working Group members also
participated in a productive Border Gateway Protocol (BGP) Working Group
session which addressed issues specific to route leaking between BGP and
OSPF.
Frank Solensky deserves considerable commendation for diligently noting
all of the changes to the draft which were agreed to during the course
of the meeting.
Attendees
Douglas Bagnall bagnall_d@apollo.hp.com
Atul Bansal bansal@netrix.nac.dec.com
Ballard Bare bare@hprnd.rose.hp.com
William Barns barns@gateway.mitre.org
Bob Beach bob@ultra.com
Arthur Berggreen art@acc.com
Helen Bowns hbowns@bbn.com
David Bridgham dab@asylum.sf.ca.us
Ronald Broersma ron@nosc.mil
Christopher Bucci bucci@pluto.dss.com
Jeffrey Burgan jeff@nsipo.nasa.gov
Ross Callon callon@bigfut.enet.dec.com
Graham Cobb cobb@marvin.enet.dec.com
2
Rob Coltun rcoltun@trantor.umd.edu
Don Coolidge coolidge@speaker.wpd.sgi.com
Nabil Damouny
Kurt Dobbins dobbins@ctron.com
Dino Farinacci dino@3com.com
Jeffrey Fitzgerald jjf@fibercom.com
Richard Fox rfox@synoptics.com
Vince Fuller vaf@Standford.EDU
Fred Gray fred@homer.msfc.nasa.gov
Martin Gray mg@spider.co.uk
Jeremy Greene greene@coral.com
Martin Gross gross@polaris.dca.mil
Patrick Heisinger heisinger@mdcguy.mdc.com
Jeffrey Honig jch@devvax.tn.cornell.edu
Kathleen Huber khuber@bbn.com
Harold Jones hjones@nac.enet.dec.com
Ajay Kachrani kachrani@regent.enet.dec.com
Frank Kastenholz kasten@asherah.clearpoint.com
Manu Kaycee kaycee@trlian.enet.dec.com
Stev Knowles stev@ftp.com
Alex Koifman akoifman@bbn.com
Anthony Lauck lauck@tl.enet.dec.com
Eliot Lear lear@net.bio.net
Tony Li tli@cisco.com
Mike Little little@ctt.bellcore.com
Joshua Littlefield josh@cayman.com
Then Liu
Gary Malkin gmalkin@ftp.com
Mike Marcinkevicz mdm@calstate.edu
Glenn McGregor ghm@merit.edu
Milo Medin medin@nsipo.nasa.gov
Carol Melowitz melowitz@mdcgwy.mdc.com
Jay Melvin infopath@well.sf.ca.us
Linda Melvin infopath@well.sf.ca.us
April Merrill
David Miller dtm@ulana.mitre.org
Greg Minshall minshall@wc.novell.com
John Moy jmoy@proteon.com
Gary Mussar mussar@bnr.ca
David O'Leary oleary@sura.net
Brad Parker brad@cayman.com
Stephanie Price price@cmc.com
Michael Reilly reilly@pa.dec.com
Kary Robertson kr@concord.com.kr
George Sanderson sanderson@mdc.com
Mark Schaefer schaefer@davidsys.com
Steven Sherry shsherry@eng.xyplex.com
Stephen Shew sdshew@bnr.ca
Frank Solensky solensky@clearpoint.com
Evan Solley solley@applelink.apple.com
Brad Solomon bsolomon@hobbes.msfc.nasa.gov
Michael St. Johns stjohns@umd5.umd.edu
Martha Steenstrup msteenst@bbn.com
Roxanne Streeter streeter@nsipo.nasa.gov
3
Glenn Trewitt trewitt@pa.dec.com
Walter Wimer walter.wimer@andrew.cmu.edu
Cathy Wittbrodt cjw@nersc.gov
John Wobus jmwobus@suvm.acs.syr.edu
Wing Fai Wong wfwong@malta.sbi.com
Chin Yuan cxyuan@pacbell.com
4