2.4.5 Global Routing Operations (grow)

NOTE: This charter is a snapshot of the 61st IETF Meeting in Washington, DC USA. It may now be out-of-date.

Last Modified: 2004-09-07


Geoff Huston <gih@telstra.net>
David Meyer <dmm@1-4-5.net>

Operations and Management Area Director(s):

Bert Wijnen <bwijnen@lucent.com>
David Kessens <david.kessens@nokia.com>

Operations and Management Area Advisor:

David Kessens <david.kessens@nokia.com>

Technical Advisor(s):

Bill Fenner <fenner@research.att.com>
Vijay Gill <vijay@umbc.edu>

Mailing Lists:

General Discussion: grow@lists.uoregon.edu
To Subscribe: majordomo@lists.uoregon.edu
Archive: http://darkwing.uoregon.edu/~llynch/grow/

Description of Working Group:

The Border Gateway Protocol (BGP) is fundamental to the operation
of the Internet. In recent years, occurrences of BGP related
operational issues have increased, and while overall
understanding of the default-free routing system has improved,
there is still a long and growing list of concerns. Among these
are routing table growth rates, interaction of interior and
exterior routing protocols, dynamic properties of the routing
system, and the effects of routing policy on both the size and
dynamic nature of the routing table. In addition, new and
innovative uses of BGP, such as the use of BGP as a signaling
protocol for some types of Virtual Private Networks, have created
new and unexpected operational issues.

The purpose of the GROW is to consider the operational problems
associated with the IPv4 and IPv6 global routing systems,
including but not limited to routing table growth, the effects of
the interactions between interior and exterior routing protocols,
and the effect of address allocation policies and practices on
the global routing system. Finally, where appropriate, the GROW
documents the operational aspects of measurement, policy,
security, and VPN infrastructures.

GROW will also advise various working groups, including the IDR
and RPSEC working groups, with respect to whether it is
addressing the relevant operational needs, and where appropriate,
suggest course corrections. Finally, operational requirements
developed in GROW can also be used by any new working group
charged with standardizing a next generation inter-domain routing


(i). Evaluate and develop various methodologies of controlling
                policy information in order to reduce the effect of
                prefix sub-aggregates beyond the necessary diameter, so
                as to reduce the Network Layer Reachability Information
                (or NLRI; see e.g.,draft-ietf-idr-bgp4-23.txt) load on
                network infrastructure.

(ii). Document and suggest operational solutions to problematic
                aspects of the currently deployed routing
                system. Examples include instability caused by
                oscillation of MULTI_EXIT_DISC (or MED; see RFC 3345)

(iii). Analyze aspects of supporting new applications, including
                extending existing routing protocols and creating new
                ones. This includes risk, interference and application

(iv). Determine the effect of IGP extensions on the stability of
                the Internet routing system.

(v). Document the operational aspects of securing the Internet
                routing system, and provide recommendations to

Some Relevant References:

Goals and Milestones:

Done  Publish Risk, Interference and Fit (RIFT) document as WG I-D
Done  Publish Embedding Globally ...Considered Harmful as WG I-D
Done  Publish MED Considerations Draft as WG I-D
Done  Publish Collection Communities as WG I-D
Done  Submit Collection Communities to IESG for BCP
Sep 04  Submit MED Considerations to IESG for Info
Sep 04  Submit Embedding Globally ...Considered Harmful to IESG for Info
Dec 04  Submit the RIFT document to IESG for Info


  • draft-ietf-grow-collection-communities-06.txt
  • draft-ietf-grow-bgp-med-considerations-02.txt
  • draft-ietf-grow-embed-addr-04.txt
  • draft-ietf-grow-bgp-wedgies-00.txt

    No Request For Comments

    Current Meeting Report

    minutes for IETF-61

    1. WG Last Call for draft-ietf-grow-bgp-wedgies-00.txt
    2. Consult with the AD for advise whether to continue with the RIFT document or not and advise the working group
    3. Consult with AD on the possible need to re-charter to fold in MRT format as a standardization activity
    4. WG mailer call to adopt anycast draft as a WG document

    Draft Status

    - med-consideration
    Ready for WG Last Call?
    a few folk have read the draft. Request for review comment by the wg.

    - bgp collection communities
    In AD followup - AD is ready to go

    - embedded addresses
    In AD followup - AD is ready to go

    - BGP Wedgies
    ready for WG Last Call

    - RIFT
    (note that the RIFT draft has expired)

    proposed to cease this WG activity and not to undertake any further activity on this document

    This positionm was supported by Yakov, who felt that the document was unhelpful.

    Another view was that this document represented a narrative of a discussion that is worth placing in the RFC document series

    A call was made for specific objections to the document to be posted to the mailing list.


    MRT format standardization
    Working group interest in adopting this as a WG document and publishing this.

    There is a charter issue, as this is not explicitly within the GROW charter. Chairs to consult with the AD on this topic.

    There was support in the room to take this on as a working group document. This is to be confirmed on the mailer.

    The authors want another revision of the document to address comments made on the initial draft.

    Highly Active Prefixes
    no working group actions

    BGP Status Report
    no working group actions


    Standardizing the MRT format
    Operation of Anycast Services
    Preliminary Measurement Results on Highly Active Prefixes in BGP Routing
    Routing Table Status Report