Notes from 3/5/96 working group meeting
skh@merit.edu Wed, 06 March 1996 15:56 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10994; 6 Mar 96 10:56 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa10990; 6 Mar 96 10:56 EST
Received: from p-o.ans.net by CNRI.Reston.VA.US id aa07639; 6 Mar 96 10:56 EST
Received: by p-o.ans.net id AA19863 (5.65c/IDA-1.4.4 for bgp-outgoing); Wed, 6 Mar 1996 15:32:38 GMT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: skh@merit.edu
Date: Wed, 06 Mar 1996 10:32:29 -0500
Message-Id: <199603061532.KAA02016@idrp.merit.edu>
To: bgp@ans.net
Subject: Notes from 3/5/96 working group meeting
Cc: skh@merit.edu
X-Orig-Sender: bgp-owner@ans.net
Precedence: bulk
Reply-To: bgp@ans.net
BGP Working Group Date: 3/5/96 time 3:30pm -5:30pm PST (note taker: Susan Hares) 1) BGP-4 MIB (draft-ietf-bgp-mibv4-06.txt) Jeff Johnson (Cisco), the latest editor, of the BGP-4 MIB document will make the few minor editorial changes given by the list. The working group needs to forward two reports of those using the BGP-4 MIB. Cisco and GateD have BGP-4 mibs. Someone from Cisco, and Sue Hares from Merit will forward experience reports to Yakov to send to the IESG. At this point the BGP-4 MIB will be forwarded to Draft Standard. MIB entries for newer attributes (Destination Preference Attribute, BGP communities, and Conferations) will go in a separate document. 2) IDRP for IPv[46] (draft-ietf-idr-idrp-v4v6-02.txt) Yakov will produce a complete IDRP specification based on the the difference document and the IDRP specification. Anyone wishing to comment on features in BGP-4 or the features in the existing document should send mail to the mailing list or Yakov Rekhter. 3) Confederation (Ramesh Govindan) (draft-ietf-idr-idr-config-00.txt) One problem with IDRP confederations is that every BGP speaker must know what confederations it belongs to. This amount of configuration guarantees that the correct processing of confederations even if individual nodes are mis-configured. If instead you, configure - only the border routers AND - if there is ambiquity, assume nesting You may be able to limit configuration amounts. This proposal had some discussion from the floor and will continued to be discussed on the mailing list. 4) Destination Preference Attribute (DPA) (draft-ietf-idr-bgp-dpa-05.txt draft-ietf-idr-dpa-application-02.txt draft-ietf-idr-symm-multi-prov-02.txt) The processing of the the DPA value is currently included in the route policy calculation as: Multi-Exit-Discriminator (MED) - 1st Destination Preference Attribute (DPA) - 2nd Cisco and RsD implement the preference in that way. Discussions will continue offline and a new internet draft will capture joint agreement of current authors and implementors. Watch your mailing list for an announcement of this document. 5) BGP communities -draft-chandra-bgp-communities-00.txt The BGP community specification has been release for over a year. It has been implemented by Bay networks and Cisco. It is suggested that Yakov make the last call, and move it to proposed standard. Tony Bates and Enke Chen has released a draft on the usage of communities. Enke Chen made a presentation of this feature at the NANOG meeting in February 1996. [draft-bgp-communities-00.txt) (The editor needs the draft name of the document.) 6) BGP Confederations draft-trainia-bgp-confed-00.txt It was moved that is be moved to experimental. In deployment Cisco discovered some problems with this approach. 7) Route Reflection draft-bates-route-reflect-00.txt Cisco has implemented the route reflection a year ago. MCI has used this in it's network for a year. (Has Bay implemented this?) The working group recommends that this move forward to experimental. A work item for the group is to decide which solution to the IBGP mesh problem will be selected by the group: the Route Reflection or the Route Server (Dimitry Haskins) or a cobmination of both. Fun quotes: "You forced this @#* MIB down my throat." "Standards don't matter if the code is running in all the routers"
- Re: Notes from 3/5/96 working group meeting Howard C. Berkowitz
- Notes from 3/5/96 working group meeting skh
- Re: Notes from 3/5/96 working group meeting Tony Bates
- Re: Notes from 3/5/96 working group meeting Erik Sherk
- Re: Notes from 3/5/96 working group meeting Paul Traina
- Re: Notes from 3/5/96 working group meeting Paul Traina
- Checking MCI -> DANTE routing Michael Behringer