IETF Logo Mail Archive

Re: [v6ops] BGP Identifier

Jared Mauch <jared@puck.nether.net> Fri, 14 February 2014 21:14 UTC

Return-Path: <jared@puck.nether.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 0F2551A03DF; Fri, 14 Feb 2014 13:14:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 N8Jzirr7K6TP; Fri, 14 Feb 2014 13:14:38 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 30F451A043A; Fri, 14 Feb 2014 13:14:34 -0800 (PST)
Received: from [IPv6:2601:4:2180:300:7ed1:c3ff:feec:5ab7] ([IPv6:2601:4:2180:300:7ed1:c3ff:feec:5ab7]) (authenticated bits=0) by puck.nether.net (8.14.7/8.14.5) with ESMTP id s1ELETrT000455 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 14 Feb 2014 16:14:29 -0500
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Content-Type: text/plain; charset="us-ascii"
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <B4D8E670-3823-468F-AA41-FE14754F168C@steffann.nl>
Date: Fri, 14 Feb 2014 16:14:28 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F967D44B-1D28-4A51-B1B8-BFB9DFA27331@puck.nether.net>
References: <12AA6714-4BBE-4ACE-8191-AA107D04FBF4@cisco.com> <m2wqgyjifd.wl%randy@psg.com> <B4D8E670-3823-468F-AA41-FE14754F168C@steffann.nl>
To: Sander Steffann <sander@steffann.nl>
X-Mailer: Apple Mail (2.1827)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.7 (puck.nether.net [IPv6:2001:418:3f4::5]); Fri, 14 Feb 2014 16:14:30 -0500 (EST)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/BZMoSE9Dhjy0TN-1Sjat3LwbDc4
Cc: idr wg <idr@ietf.org>, V6 Ops List <v6ops@ietf.org>
Subject: Re: [v6ops] BGP Identifier
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: Fri, 14 Feb 2014 21:14:40 -0000

On Feb 14, 2014, at 3:13 PM, Sander Steffann <sander@steffann.nl> wrote:

> Hi,
> 
>>> http://tools.ietf.org/html/draft-fan-idr-ipv6-bgp-id
>>> "IPv6 BGP Identifier Capability for BGP-4", Peng Fan, Zhenqiang Li,
>>> 2014-02-12
>> 
>> please no.  if you can not assign a unique four octet integer to each
>> router in your network, then you have much bigger problems.  and adding
>> a capability and more complexity to try to patch over your inability to
>> configure your routers will just compound your problems.
> 
> I agree. It's a shame that the router-id looks like an IPv4 address and IPv4 addresses are used to auto-configure it when the operator doesn't explicitly set it. There are too many people that think that a router-id is more than a 32-bit number and must be an IPv4 address, but creating more complexity to avoid educating router operators isn't the answer...

+1

Perhaps this is another thing like ASDOT vs ASPLAIN where we can shift the configuration on devices to accept a decimal number?

- Jared

v2.23.0 | Report a Bug | By Email