TODO list for Edge Aware Inter-domain Routing (EIR)

1. Use-case evaluation

1.1. Edge peering

Description: Two example scenarios can be considered:

a) Two small enterprise networks N1 and N2 which operate in geographically close locations (e.g. on different floors of a building) and have different Internet service providers ISP1 and ISP2, setting up a peering link as a backup. This would enable one to use the other in case one of the upstream providers fail.

b) Time Square / Concert / Stadium events, wherein, an upstream provider may not have the capacity to carry large volumes of traffic, but would benefit by peering and carrying traffic along the edge.

Solution: Needs more thought into formalizing the evaluation scenario

Status: Not evaluated

1.2. Cross-domain multi-homing

Description: Basic example of an end-host connected simultaneously through 2 or more interfaces, trying to download content, where each connection maintained by a different ISP.

Implementation: Multihoming would require an algorithm by which the appropriate branching out point needs to be decided. A simple approach would be to use the longest common path, which would not require any modification of the existing routing logic.

However, if multiple interfaces are used simultaneously, a scheduling algorithm needs to be formulated to be run on the splitting router.

Status: Not evaluated (best interface use can be simulated without any change)

1.3. Cross-domain multicast

Description: ...

Proposed solution: ...

Status: Not evaluated

1.4. Service anycast

Description: ...

Proposed solution: ...

Status: Not evaluated

2. EIR + GNRS

2.1. Basic Integration

Description: ...

Proposed solution: ...

Status: Not implemented

2.2. Balance b/w late-binding and telescopic flooding

Description: ...

Proposed solution: ...

Status:

2.3. GENI deployment

Description: ...

Proposed solution: ...

Status:

3. Revisit GSTAR features for EIR

Description: ...

Proposed solution: ...

Status: ...