BGP Deployment BOF minutes. 

BGP Deployment & Application

Charter

Chair:
        Jessica Yu, Merit, jyy@merit.edu

Mailing Lists:

        General Discussion: iwg@rice.edu 
        To Subscribe:   iwg-request@rice.edu

Description of Working Group:

        The major purpose of this group is to coordinate BGP deployment
        and application in the current Internet.

        It intends to create a forum for BGP users to share BGP deployment
        experiences and also provide a channel for users to communicate
        with router vendors who implemented or implementing BGP.
        It also intends to discuss BGP policy application and coordiante
        policy implementation in the current internet routing enviroment
        which includes define the usage of policy, define a mechanism
        to share policy information, etc. 

Goals and Milestones:

        Helping deploy BGP as widely as possible

        Define BGP policy usage and application

        Define mechanism to share policy information between Routing doamins

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

The minutes of the first meeting.

        BGP Deployment & Application BOF

    Chair
        - Jessica Yu, jyy@merit.edu

    Agenda
        - Coordinate BGP deployment
        - Coordinate BGP policy implementations
    
    1) Implementation testing for interoperability and verification
       before production deployment is desirable.
    2) RFC 1267 & 1268 refers to the latest BGP protocol and usage.
    3) Tony Li from cisco volunteered to coordinate joint testing.
       He is reachable at cs@cisco.com. Jessica Yu volunteered Merit as the 
       place where the testing could occur.
    4) Who's using BGP?
        - PSC - gated on T1 NSS and T3 ENSS.
        - SDSC - gated on T1 NSS.
        - CA*Net - gated with Dennis Furgusson's extensions.
        - Cornell/ICM - cisco.
        - Merit - cisco 8.2(6) on T1 and T3 NSS.
        - VPI - cisco on T3
        - IBM Information Network - cisco on T3
        - ANS connection to T3 backbone   
     5) who's testing it
        - Sesquinet
        - Argonne
        - ConcertNet
        - ESNet
        - Nearnet
        - EASINet
     6) Who has implemented it?
        - cisco BGP2 in software release 8.3.
        - NSFNET which supports BGP1 and BGP2.
        - gated which supports BGP1 only.
        - implementation from Canada.
        - BBN in the T20 router - BGP3.
     7) BGP status in gated - by Scott Brim.
        - BGP2 & BGP3.
        - Flexible definition of neighbors.
        - Internal, External, and Test neighbor definition. Test
          dumps everything to peer but believes nothing.
        - IBGP works. Can run with OSPF and synchronizes correctly.
          Currently there is no flexibility to adapt to other IGPs.
        - Shared subnet between external neighbors is enforced.
        - If between two ASs, can have different AS numbers, and ASpaths
          will be correct.
        - Improved performance.
        - RFC 1164 specifies a policy language that has been implemented
          in gated. 
    8) BGP MIB
        - Will be updated to reflect the latest protocol version 1Q92
    9) cisco implementation status - by Tony Li.
        - BGP2 available in 8.3(1) and 8.2(7) soon. 
        - 9.0 available 1Q92 which has BGP2 & BGP3.
            - AS-path access lists are supported. Uses regular expressions.
        - BGP to do list - for future,no commitments.
            - multiple BGP processes.
            - use AS number filter for redistribution into OSPF.
            - performance enhancements.
            - convergence time improvements to IP forwarding table for
              BGP routes.
    10) NSFNET's implementation status - by Yakov Rekhter.
        - current version is BGP2. Plans to use gated's implementation.
        - plans to carry BGP information in IS-IS as an alternative to
          internal BGP.
    11) What sites tried BGP but backed it out and reasons why.
        - NEARnet
            - redistribution problems.
        - ESNet
            - access list problems.
        - MILnet at FIX-E
            - ran into meomory shortage problem due to usage of CSC2
              board.  In the process of upgrading it to CSC3 board.
        - BARRNet
            - multiple vendors interoperating with half running BGP had
              consistency problems.
        - Sesquinet
            - redistribution problems
              will try new software from cisco.
    12) Mailing list is iwg@rice.edu.

    This minutes is taken by Dino Farinacci.