I-D Action: draft-sriram-replay-protection-design-discussion-06.txt

internet-drafts@ietf.org Mon, 18 April 2016 16:25 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-sriram-replay-protection-design-discussion-06.txt
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160418162518.9271.75793.idtracker@ietfa.amsl.com>
Date: Mon, 18 Apr 2016 09:25:18 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/i-d-announce/d0JrqTVFjGV8YS6uI3XVRnKu7ic>
Reply-To: internet-drafts@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : Design Discussion and Comparison of Protection Mechanisms for Replay Attack and Withdrawal Suppression in BGPsec
        Authors         : Kotikalapudi Sriram
                          Doug Montgomery
	Filename        : draft-sriram-replay-protection-design-discussion-06.txt
	Pages           : 17
	Date            : 2016-04-18

Abstract:
   In the context of BGPsec, a withdrawal suppression occurs when an
   adversary AS suppresses a prefix withdrawal with the intension of
   continuing to attract traffic for that prefix based on a previous
   (signed and valid) BGPsec announcement that was earlier propagated.
   Subsequently if the adversary AS had a BGPsec session reset with a
   neighboring BGPsec speaker and when the session is restored, the AS
   replays said previous BGPsec announcement (even though it was
   withdrawn), then such a replay action is called a replay attack.  The
   BGPsec protocol should incorporate a method for protection from
   Replay Attack and Withdrawal Suppression (RAWS), at least to control
   the window of exposure.  This informational document provides design
   discussion and comparison of multiple alternative RAWS protection
   mechanisms weighing their pros and cons.  This is meant to be a
   companion document to the standards track I-D.-ietf-sidr-bgpsec-
   rollover that will specify a method to be used with BGPsec for RAWS
   protection.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-sriram-replay-protection-design-discussion/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-sriram-replay-protection-design-discussion-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-sriram-replay-protection-design-discussion-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

I-D Action: draft-sriram-replay-protection-design… internet-drafts