Scribd Logo
Upload

Welcome to Scribd!

  • Engineer a global peering network

    Uploaded by

    JennieAWalsh
    13 views11 pages
    This document discusses considerations for engineering a global peering network in 3 or fewer sentences. It recommends evaluating goals such as reducing latency or accessing new networks. Key factors to consider include traffic engineering, using a global or regional ASN, automation tools, operational impacts of keeping track of changing peers, and communication with other networks who have experience with global peering. The document advises carefully evaluating all impacts and talking to experienced resources before making decisions to better serve customers and the global internet.

    Original Description:

    hg,h

    Original Title

    e Hughes Peeringbofnanog51

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document discusses considerations for engineering a global peering network in 3 or fewer sentences. It recommends evaluating goals such as reducing latency or accessing new networks. Key factors to consider include traffic engineering, using a global or regional ASN, automation tools, operational impacts of keeping track of changing peers, and communication with other networks who have experience with global peering. The document advises carefully evaluating all impacts and talking to experienced resources before making decisions to better serve customers and the global internet.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    13 views11 pages

    Engineer a global peering network

    Uploaded by

    JennieAWalsh
    This document discusses considerations for engineering a global peering network in 3 or fewer sentences. It recommends evaluating goals such as reducing latency or accessing new networks. Key factors to consider include traffic engineering, using a global or regional ASN, automation tools, operational impacts of keeping track of changing peers, and communication with other networks who have experience with global peering. The document advises carefully evaluating all impacts and talking to experienced resources before making decisions to better serve customers and the global internet.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 11

    How to engineer a global peering network

    Peering Track Feb 1, 2011

    Tuesday, February 1, 2011

    Take aways..

    These are not denitive answers Take notes on things to consider and discuss with (potential) peers or networks who have done this.

    Tuesday, February 1, 2011

    Making the decision


    Transport vs. Transit How are you going to get there? Can you get there? Transport availability? Cost? (Does this still make sense?) Leverage transport for qualication?
    Tuesday, February 1, 2011

    Peering Growth Decision..

    Youve made the decision to expand Sounds simple but..

    Tuesday, February 1, 2011

    Goals
    What are you looking to achieve? Larger / different types of peers? Reduction of latency? New services unique to region(s)? Blended cost reduction? Direct access to specic networks?
    Tuesday, February 1, 2011

    Considerations
    Impacts on Trafc Engineering Tools Communication Quality Support staff (internal resources) Contracts? Legal? Transit v Peer.
    Tuesday, February 1, 2011

    Trafc Engineering
    Hot Potato becomes very important! Analytics... Paths for src/dst optimization Single ASN vs. Regional ASN? Impact of each peer modication Peers at single locations Impacts of being DE-peered region(s)
    Tuesday, February 1, 2011

    Global ASN vs. Regional ASN?


    ASN recognition? Evaluate your (potential) peer requirements Consistent announcement requirements Trafc path selection Additional tools / monitoring / ops
    Tuesday, February 1, 2011

    Tools
    Automation becomes very important Database almost a must Monitoring from regional perspective Tracking peer communications Tracking changes in qualications Impacts of failure scenarios
    Tuesday, February 1, 2011

    Operational Impacts
    Keeping track of peers (changes) M&A (AS consolidation) Regional peers who become multiregional (Now impact you too) Language / Maintenance / Communication NOC to NOC issues New Exchanges Evaluation
    Tuesday, February 1, 2011

    Summary

    Evaluate total impact carefully Talk to resources who have experience Make sound decisions to better the Global Internet and your customers

    Tuesday, February 1, 2011

    You might also like