RFC 3706 on A Traffic-Based Method of Detecting Dead Internet

rfc-editor@rfc-editor.org Thu, 19 February 2004 19:16 UTC

Message-Id: <200402191855.i1JItuk27595@gamma.isi.edu>
To: IETF-Announce: ;
Subject: RFC 3706 on A Traffic-Based Method of Detecting Dead Internet
Cc: rfc-editor@rfc-editor.org, ipsec@lists.tislabs.com
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Thu, 19 Feb 2004 10:55:56 -0800
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

A new Request for Comments is now available in online RFC libraries.


        RFC 3706

        Title:      A Traffic-Based Method of Detecting Dead Internet
                    Key Exchange (IKE) Peers
        Author(s):  G. Huang, S. Beaulieu, D. Rochefort
        Status:     Informational
        Date:       February 2004
        Mailbox:    ghuang@cisco.com, stephane@cisco.com,
                    danyr@cisco.com
        Pages:      13
        Characters: 30196
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ipsec-dpd-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3706.txt


This document describes the method detecting a dead Internet Key
Exchange (IKE) peer that is presently in use by a number of vendors.
The method, called Dead Peer Detection (DPD) uses IPSec traffic
patterns to minimize the number of IKE messages that are needed to
confirm liveness.  DPD, like other keepalive mechanisms, is needed to
determine when to perform IKE peer failover, and to reclaim lost
resources.

This document is a product of the IP Security Protocol Working Group
of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc3706.txt"><ftp://ftp.isi.edu/in-notes/rfc3706.txt>

RFC 3706 on A Traffic-Based Method of Detecting D… rfc-editor