Corrected Announcement: RFC 7868 on Cisco's Enhanced Interior Gateway Routing Protocol (EIGRP)
rfc-editor@rfc-editor.org Thu, 26 May 2016 15:21 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E7BF12D6FA for <ietf-announce@ietfa.amsl.com>; Thu, 26 May 2016 08:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level:
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id od8sxMLHGV1M for <ietf-announce@ietfa.amsl.com>; Thu, 26 May 2016 08:21:13 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D662312D180 for <ietf-announce@ietf.org>; Thu, 26 May 2016 08:21:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 11C94180004; Thu, 26 May 2016 08:20:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: Corrected Announcement: RFC 7868 on Cisco's Enhanced Interior Gateway Routing Protocol (EIGRP)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160526152036.11C94180004@rfc-editor.org>
Date: Thu, 26 May 2016 08:20:36 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/s0UPTAPUwBUk7jHX5GHeI03G-5Q>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2016 15:21:15 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7868
Title: Cisco's Enhanced Interior Gateway Routing
Protocol (EIGRP)
Author: D. Savage, J. Ng,
S. Moore, D. Slice,
P. Paluch, R. White
Status: Informational
Stream: Independent
Date: May 2016
Mailbox: dsavage@cisco.com,
jamng@cisco.com,
smoore@cisco.com,
dslice@cumulusnetworks.com,
peter.paluch@fri.uniza.sk,
russ@riw.us
Pages: 80
Characters: 179677
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-savage-eigrp-05.txt
URL: https://www.rfc-editor.org/info/rfc7868
DOI: http://dx.doi.org/10.17487/RFC7868
This document describes the protocol design and architecture for
Enhanced Interior Gateway Routing Protocol (EIGRP). EIGRP is a
routing protocol based on Distance Vector technology. The specific
algorithm used is called "DUAL", a Diffusing Update Algorithm as
referenced in "Loop-Free Routing Using Diffusing Computations"
(Garcia-Luna-Aceves 1993). The algorithm and procedures were
researched, developed, and simulated by SRI International.
INFORMATIONAL: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC