Re: [v6ops] EIGRP and the Design Choices draft

Gert Doering <gert@space.net> Wed, 13 May 2015 14:57 UTC

Return-Path: <gert@Space.Net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD95D1B2D29 for <v6ops@ietfa.amsl.com>; Wed, 13 May 2015 07:57:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 jXt5CVDL3wz3 for <v6ops@ietfa.amsl.com>; Wed, 13 May 2015 07:57:34 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB5381B2D20 for <v6ops@ietf.org>; Wed, 13 May 2015 07:57:33 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 8447E6097A for <v6ops@ietf.org>; Wed, 13 May 2015 16:57:29 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 34338608CF for <v6ops@ietf.org>; Wed, 13 May 2015 16:57:29 +0200 (CEST)
Received: (qmail 22790 invoked by uid 1007); 13 May 2015 16:57:29 +0200
Date: Wed, 13 May 2015 16:57:29 +0200
From: Gert Doering <gert@space.net>
To: "Fred Baker (fred)" <fred@cisco.com>
Message-ID: <20150513145729.GC54385@Space.Net>
References: <555112D8.3000008@gmail.com> <1592568679.113935.1431386263763.JavaMail.yahoo@mail.yahoo.com> <41D8A9FE-0324-4DDF-8868-5187F122F9A7@nominum.com> <CE02D71F-93AA-4441-85AE-CD0DF1DDD095@cisco.com> <16AE7703-1288-40F6-9CD9-29196986B8C6@nominum.com> <C2A44BA9-2D74-4E3B-8093-E5B352BF153C@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="2fLGufcSJaIWCyz8"
Content-Disposition: inline
In-Reply-To: <C2A44BA9-2D74-4E3B-8093-E5B352BF153C@cisco.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/JhTNyRt6ftV-Jep8F7BNDXRqKqg>
Cc: v6ops list <v6ops@ietf.org>, Philip Matthews <philip_matthews@magma.ca>
Subject: Re: [v6ops] EIGRP and the Design Choices draft
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2015 14:57:41 -0000

Hi,

On Tue, May 12, 2015 at 09:05:39PM +0000, Fred Baker (fred) wrote:
> If we're documenting deployment experience with common routing protocols, it's one of them. Is this about the purity of the RFC series, or the relevance to operational networks? If it is about routing in operational networks, why would we exclude discussion of protocols in current use in operational networks?
> 
> As to Brian's suggestion of putting EIGRP into an appendix, I'm not the author, but if I were, I would wonder how he wanted me to do that. The request is to add one or more rows (the current draft mentions "RIP [RFC2080] or non-standardized protocols") to

This approach works for me - have it in the table, and maybe add a footnote
that explains that EIGRP is not an IETF standard but a vendor protocol.

"Operational useful content" in an operational RFC trumps "purity" for me.

(I'm actually one of the people that use EIGRP for IPv4 and have also
used it for IPv6, and prefer it to OSPF or ISIS any day)

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279