30
Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Embed Size (px)

Citation preview

Page 1: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Peering BOF – Peering Personal

NANOG 25 Richmond Hill, CA

June 10, 2002

Page 2: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Redneck Horseshoes

Page 3: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

What is this?

Moo Shoe Pork

Page 4: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Smaller ISP getting Peering with Large ISP: The Cajoling Tactic

Page 5: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Teaser for “The Art of Peering” Research

• When e-mail to peering@<ispdomain>.net generates no response, what do Peering Coordinators do?

• Document the “Tricks of the Trade”• Enumerate Tactics to Obtain Peering when

otherwise might not be able to.“A must-read for Peering Coordinators” -- Eric Anderson (Concert)

Page 6: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

P?

Graphical Representation of Methods

BA

ISP Initiator ISP Target

A B

ISP A Customers

ISP BCustomers

Larger Circle=More Customer Prefixes Thicker Lines=More Traffic

P?=Peering Request w/Peering Coordinator

Peering Negotiation

T?=Transit RequestTo Sales Person

Transit Negotiations

APC BPC

P?

APC BS

T?

APC BPC

APC BS

T?

$

$

To Portray Peering Plays Pictorially…

Page 7: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Transit and Peering Sessions

A BT

A BP

T=Established Transit Session(Selling Access to entire Internet)Size indicates effective size of transportSupporting the session

P=Established Peering Session(Reciprocal Access to each others customers) Size indicates effective size of transportSupporting the session

A BP

A BT

$

$

Graphical Display of Routing Announcements

Represents “the rest of the Internet”

Page 8: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Traffic over Transit and Peering Sessions

A BT

A BP

Traffic showed as directed lines

Thickness of line indicates amount of Traffic in relevant direction

A BP

A BT $

$

Other VariationsP->T = Transition of RelationshipP | T = Either Peering or Transit apply = Traffic destined anywhere = Fictitious Traffic = Packet Loss ridden Traffic = Traffic destined to green network = Traffic destined to brown network

Page 9: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Other Graphical Symbols

PeeringPoint

Exchange Point, Telco Hotel

Tiedwith

Indicates two or moreElements tied withrelationship

Indicates a ordering,A sequence to be followedIn the Peering Play

or

Page 10: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

A B

L

G

P

T

T

T $

$

$

A forces trafficOver B’s transit

9)    In the Traffic Manipulation tactic, ISPs or content players force traffic along the network path that makes

peering appear most cost effective.

APC BPC

L

G

P

T

T

T $

$

$

P?

1 MONTH LATERContact PC-We should Peer!

B hears A’s route‘for free’ through Peer L

CH ISPi.e.Yahoo!

A B

L

G

P

T

T

T $

$

$

Page 11: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

18) The False Peering Outage tactic involves deceiving an ill-equipped NOC into believing a non-existing peering

session is down.

ANOC

BNOCPeeringPoint

X

ANOC: Hey – Emergency! ANOC: Our Peering Session with you Went Down!BNOC: Strange. <looks on router> I don’t see it configured.ANOC: It was. Don’t make me escalate to <famous person>BNOC: Ah – I bet is was that last config run that trashed it.BNOC: Give me a few minutes to fix it on both ends.

Page 12: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

19) The Leverage Broader Business Arrangement takes advantage of other aspects of the relationship between two

companies to obtain peering in exchange for something else.

APC BS

P?

A BP

A B

Other

APC BS

P?PeeringTied with“Other”+Fiber deal+Dial-in deal+Racks+Transport+Strategic deal:

Tiedwith

Page 13: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Motivations for Peering

• Notable: Cable Cos (formerly behind Excite@Home)

• Kazaa

• The most difficult part of Peering…

• Open Peering Dominates

Page 14: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Icons Peering

• To indicate willingness to peer

Goal:

Match up Peering Policies

Maximize # of Peering Session

• First run at GPF III in Dallas, TX• Second run at NANOG 23 in Oakland, CA• Stepwise Evolution…

Page 15: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Peering Policy Icons

Large Traffic to Exchange

Content Heavy

Open Peering

Peering w/Content OK

Access Heavy

Contract Required for Peering

Page 16: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Large Traffic Flows“We have huge volumes of traffic (lots of users and/or lots of content)(Huge: > 1 Gbps total outbound traffic to peers and transit providers)”

Example:

Page 17: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Content Peering OK“Peering with Content Players or Content Heavy ISPs is OK by us”

Example:

GlobalNaps

Page 18: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

EyeballsExample:

                                                                                                                                                                              

“We are Access-Heavy”

Page 19: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Open Peering Policy

Example:Open Peering

“We will peer with anyoneIn any single location.”

Page 20: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Some Peering PreReqs

If not completely open, assume some pre reqs:

Common Prereqs:Multiple Geographical Locations RequiredTraffic Volume Minimums RequiredBribe needed

Page 21: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Content Heavy“We are Content Heavy”

Page 22: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Contract Required“We require written contracts for peering”

Page 23: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Just Getting Started with Peering

ISP A

Page 24: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

2-3 minutes per Peering Coordinator

• Say a few words about

1) Your Network (incl. AS#)1) Your Network (incl. AS#)

2) Your Ideal Peer? Why Peer with you?2) Your Ideal Peer? Why Peer with you?

3) Which IXes are you in?3) Which IXes are you in?

Which IXes are you Which IXes are you considering?considering?

Page 25: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Run Peering Personals

• Done Manually

• Now evolved to Peering Personal Program

• Simple Rules:

• Eyeballs love Content

• Content loves eyeballs

• Some eyeballs will peer with content

• Some content will peer with content

Page 26: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Peering Personals pg. 1

Large Traffic to ExchangeContent Heavy Open Peering

Peering w/Content OKAccess Heavy Contract Req.

Daniel McGillicuddy

Nemo Semret

Mike Salafia/Tricia Tsai

Blake Williams

GlobalNaps Karthik Arumugham

Page 27: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Peering Personals pg. 2

Large Traffic to ExchangeContent Heavy Open Peering

Peering w/Content OKAccess Heavy Contract Req.

Scott Sneddon

Alex Ponnath

Paul Nguyen

Ren Nowlin

Jeffrey Papen

Page 28: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Peering Personals pg. 3

Large Traffic to ExchangeContent Heavy Open Peering

Peering w/Content OKAccess Heavy Contract Req.

Doug Toye

          

                                  

Troy Davis

Gary James

Joe Provo

Tatsuo Sato

Page 29: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Peering Personals pg. 4

Large Traffic to ExchangeContent Heavy Open Peering

Peering w/Content OKAccess Heavy Contract Req.

Mitchell Rose

Jeb Linton

Phillip Chan

Ian Neale

Dwight Ringdahl

Page 30: Peering BOF – Peering Personal NANOG 25 Richmond Hill, CA June 10, 2002

Peering Personals pg. 5

Large Traffic to ExchangeContent Heavy Open Peering

Peering w/Content OKAccess Heavy Contract Req.

Glen Larwill