Architecting for innovation
This presentation is the property of its rightful owner.
Sponsored Links
1 / 18

Architecting for Innovation PowerPoint PPT Presentation


  • 80 Views
  • Uploaded on
  • Presentation posted in: General

Architecting for Innovation. ACM SIGCOMM Computer Communication Review 2011 July Presenter :許耀中 101062539. Outline. Introduction Motivating the Framework Pathlets NetAPI Dealing with DoS Evaluation Conclusion. Introduction. The biggest problem with the current Internet architecture

Download Presentation

Architecting for Innovation

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Architecting for innovation

Architecting for Innovation

ACM SIGCOMM Computer Communication Review 2011 July

Presenter :許耀中

101062539


Outline

Outline

  • Introduction

  • Motivating the Framework

  • Pathlets

  • NetAPI

  • Dealing with DoS

  • Evaluation

  • Conclusion


Introduction

Introduction

  • The biggest problem with the current Internet architecture

    • Inability to accommodate innovation

  • The original Internet architecture falls short

    • Mobility

    • Data-oriented functionality

  • Clean slate redesigns

    • Current needs

    • Future requirements


Introduction1

Introduction

  • Goal

  • To design an Internet that supports architectural evolution and diversity


Motivating the framework

Motivating the Framework

  • Many desirable design changes:

    • Require widespread agreement

    • Radiate throughout the architecture

    • Physical infrastructure

  • Lack of architectural modularity

  • Core fixed design

    • Not be a comprehensive architecture, but only a minimal architectural framework.

    • Augmented with additional architectural components

    • Microkernel & User-space modules


Motivating the framework1

Motivating the Framework

  • Architectural modularity requires interfaces be both

    • Extensible

      • New functionality

      • Obsolete

    • Abstract

      • Avoiding implementation details


Motivating the framework2

Motivating the Framework

  • Framework for Internet Innovation (FII) only defines three core primitives:

    • Interdomain routing

      • Require global agreement among the domains

    • Network API

      • Every application need to be modified

    • Against denial-of-service attacks

      • Availability, identity,authenticity

      • Standard cryptographic techniques


Motivating the framework3

Motivating the Framework

  • Additional Primitives

    • Meta-negotiation

    • Bootstrap interface

      • The domain identifier

      • Intradomainaddress (IDA)

    • Interface query

  • Assumptions:

    • Domain structure


Motivating the framework4

Motivating the Framework


Pathlets

Pathlets

  • Each domain advertises a set of path segments (pathlets) over which they are willing to carry traffic.

  • Pathlets are specified in terms of the “virtual nodes” they traverse.

  • Route computation agent (RCA)

    • Provides the host an appropriate end-to-end path to a given destination


Pathlets1

Pathlets

  • Abstraction

    • Independent of domain internals

  • Extensibility

    • These pathlet descriptions can be augmented with extensible metadata

      • QoS , Bandwidth

    • The granularity of pathletsis not specified

      • AS , a physical router

      • physical link, Path across several AS


Netapi

NetAPI

  • NetAPI

    • Sockets, PubSub, RPC

  • NetAPI refer to entities in the world with names.

    • Name resolution of a host would typically return a full address


Dealing with dos

Dealing with DoS

  • Shut up message (SUM)

  • Interface uses two fields in a packet header

    • Who to contact (trusted third party, TTP) to shut up the source of that packet

    • An accountability field that allows the TTP to identify the source of the packet


Example

Example


Evaluation

Evaluation


Evaluation1

Evaluation


Evaluation2

Evaluation


Conclusion

Conclusion

  • We described a microkernel-like approach to Internet architecture, where fixing a minimal design allows the rest of the architecture to evolve much more easily.


  • Login