home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
ietf
/
idr
/
idr-minutes-95jul.txt
< prev
next >
Wrap
Text File
|
1995-10-18
|
4KB
|
117 lines
CURRENT_MEETING_REPORT_
Reported by Sue Hares/Merit
Minutes of the Inter-Domain Routing Working Group (IDR)
The IDR Working Group met on Tuesday, 18 July.
Agenda
o Agenda bashing
o BGP-4 to full Standard
o DPA proposal (Tony Bates, MCI)
o Route Server to Experimental
o Route Damping proposal
The meeting followed the above agenda and was done within one hour.
BGP-4 to Full Standard
The BGP-4 document has been out for a few weeks with its final changes.
Paul Traina should change the BGP-4 documents.
Destination Preference Attribute Proposal -- Tony Bates
The following documents are related to the DPA proposal:
o ``Destination Preference Attribute for BGP''
(draft-ietf-idr-bgp-dpa-01.txt) is intended to move along as a
Proposed Standard.
o ``Current Practice of Implementing Symmetric Routing and Load
Sharing in the Multi-Provider Internet''
(draft-ietf-idr-symm-multi-prov-01.txt) will become an
Informational RFC.
o ``Application of the BGP Destination Preference Attribute in
Implementing Symmetric Routing''
(draft-ietf-idr-dpa-application-01.txt) will become a Best Current
Practices RFC.
Tony Bates gave a presentation about DPA. The notes simply reviewed the
DPA document.
Two vendors indicated their plans to implement this feature. One of the
vendors is ISI, the creator of the Route Server.
One difficulty with the document is that the code for the attribute (10)
has been used by another implementor. The IANA should be handing out
the code points. Bill Manning will talk to Jon Postel (IANA) on getting
code points assigned, recorded and posted. At the bottom of these
notes, the current information on the code points have been included.
Once two implementations of DPA have been created, this specification
will move on to Proposed Standard.
Route Server Document to Experimental
The route server document will move on to Experimental. The route
server document has been implemented by Bay Networks.
However, a different Route Server has been implemented by cisco systems
to solve the same problem of the large IBGP mesh.
Ravi Chandra of cisco and Tony Bates promised to write up the cisco
implementation for the next IETF.
In the long run, only one solution to the IBGP problem will be forwarded
as a Standard. In the future, the group will review the experience of
users of these two implementations to decide which solution to select.
Route Damping Protocol
Curtis Villamizar wrote up a Route Damping protocol two years ago. The
Internet-Draft received little review during the last time. Comments
from the audience indicate that this was due to the intense focus on
getting ``the network'' to work during the last year or so. Now, the
route flapping is causing problems and the group wants to re-examine
this document.
Bill Manning volunteered Ramesh Govindan to talk to Curtis, and get the
Route Damping Document written up by the RA's. The RA route server has
implemented this function.
Notes on the Current Code Points
Bill Manning was told that the current definitive list was in the BGP-4
specification, however, he was not able to find an enumerated list. The
following is from the cisco headers and some clustering around.
1 origin
2 as path
3 next hop
4 multi exit disc.
5 local preference
6 atomic aggregate
7 aggregator
8 community cisco ID
9 originator cisco ID
10 cluster list cisco ID
11 destination preference MCI ID
?? bay route server proposal? BAY ID