IETF Logo Mail Archive

Re: [v6ops] [Idr] BGP Identifier

Robert Raszuk <robert@raszuk.net> Fri, 14 February 2014 09:05 UTC

Return-Path: <rraszuk@gmail.com>
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 8B0841A01EA; Fri, 14 Feb 2014 01:05:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.677
X-Spam-Level:
X-Spam-Status: No, score=-0.677 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_51=0.6, SPF_PASS=-0.001] autolearn=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 gMpiw22HdVKX; Fri, 14 Feb 2014 01:05:51 -0800 (PST)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) by ietfa.amsl.com (Postfix) with ESMTP id B81AD1A011E; Fri, 14 Feb 2014 01:05:50 -0800 (PST)
Received: by mail-lb0-f176.google.com with SMTP id w7so8984619lbi.21 for <multiple recipients>; Fri, 14 Feb 2014 01:05:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=hXWYXiHxf5Rj3TRsYdaJkYsQPpWJIth5C23uVS+aR4U=; b=OxiGYeknqEnKEFBShxgNFllSUoJ3ilWua1YwfAq8zq0dpkcKjzh12s6zTOctZV37wL lnXo9wDEP4yOtE3WFRKr7AObXHOmK8/uqj1rkBojCrO9DplsUZnBn8uY6X4+vTrLlt3X Rc5sBLbO4r7SKmcT+1kQ33PcXj9Eu9WEshnk4SXPt7e9QuA2IwMOV2OG7W+yDCnO/Gcy Kp7SPjEGttcJEpH6YszHU40WLsfKa5nV5SfwHk1l7+a+i8ejDqUZrwUkOWMjFEJnQSOb 7YWCEDbjMJn98NJmuV1EmvSCvWdNU0jY9ZDZufZ3tbifzJmBW6qz/AiHCyFiLtY8coeb 6vTQ==
MIME-Version: 1.0
X-Received: by 10.112.172.8 with SMTP id ay8mr1333531lbc.41.1392368748481; Fri, 14 Feb 2014 01:05:48 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.112.51.105 with HTTP; Fri, 14 Feb 2014 01:05:48 -0800 (PST)
In-Reply-To: <m2wqgyjifd.wl%randy@psg.com>
References: <12AA6714-4BBE-4ACE-8191-AA107D04FBF4@cisco.com> <m2wqgyjifd.wl%randy@psg.com>
Date: Fri, 14 Feb 2014 10:05:48 +0100
X-Google-Sender-Auth: 11kLKKNItesOtjQrTGQJuEnGBlo
Message-ID: <CA+b+ERk=DEge0cAxTsFh9Vnd3YC3eg_Pj+JETZzxDfsZAgPYUA@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary="001a11c2b3f0a651e304f25a1c03"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/Crr56b7kPM4Zdlq_4rdjUQpoQvI
Cc: idr wg <idr@ietf.org>, V6 Ops List <v6ops@ietf.org>
Subject: Re: [v6ops] [Idr] 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 09:05:53 -0000

I agree with Randy'a point here.

BGP rtr_id does not need to be a routable address - it just needs to be
unique 32 bits within the domain scope.

We have had this discussion already during RFC6286 and concluded that 4
octet is sufficient for any type of BGP mesh.

If anything I would propose to go opposite and to ask your implementation
to allow UTF-8 encoded BGP rtr_id format.

Rgs,
R.


On Fri, Feb 14, 2014 at 7:51 AM, Randy Bush <randy@psg.com> wrote:

> > 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.
>
> randy
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>

v2.23.0 | Report a Bug | By Email