1 / 3

Accountable Internet Protocol

Accountable Internet Protocol. David Andersen (CMU) Hari Balakrishnan (MIT) Nick Feamster (Georgia Tech) Scott Shenker (Berkeley). http://www.aip-arch.net /. Many Security Problems/Point Solutions. For each problem, point solutions

odette-albert
Download Presentation

Accountable Internet Protocol

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Accountable Internet Protocol David Andersen (CMU)Hari Balakrishnan (MIT) Nick Feamster (Georgia Tech) Scott Shenker (Berkeley) http://www.aip-arch.net/

  2. Many Security Problems/Point Solutions • For each problem, point solutions • Fundamental problem: accountability is not intrinsic to current Internet architecture

  3. AD1 AD2 Accountable Internet Protocol • Key idea: New addressing for networks and hosts • Other protocols can use this property as foundation: (Anti-spoofing, secure routing, DDoS shut-off, etc.) • AD and EID are self-certifying flat names • AD = hash( public_key_of_AD ) • Self-certification binds name to named entity Address Structure Application: Anti-Spoofing 1. Send P Address = AD1:EID 2. Sent P? {nonce} A If multihomed, has multiple addressesAD1:EID,AD2:EID,AD3:EID 3. Yes! { hash(P), nonce } K-1 A Signed with private key corresponding to EID A

More Related