IETF Logo Mail Archive

Re: [v6ops] [Idr] BGP Identifier

joel jaeggli <joelja@bogus.com> Mon, 17 February 2014 20:28 UTC

Return-Path: <joelja@bogus.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 894031A04E5; Mon, 17 Feb 2014 12:28:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 rVmZ69kfcpH2; Mon, 17 Feb 2014 12:28:34 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id C3E721A04D2; Mon, 17 Feb 2014 12:28:34 -0800 (PST)
Received: from mb-aye.local (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s1HKSTlG052575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 17 Feb 2014 20:28:30 GMT (envelope-from joelja@bogus.com)
Message-ID: <530270E8.5090603@bogus.com>
Date: Mon, 17 Feb 2014 12:28:24 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: David Farmer <farmer@umn.edu>, Shane Amante <shane@castlepoint.net>
References: <12AA6714-4BBE-4ACE-8191-AA107D04FBF4@cisco.com> <m2wqgyjifd.wl%randy@psg.com> <B4D8E670-3823-468F-AA41-FE14754F168C@steffann.nl> <11C9319C-A886-4B9E-9E8D-6947A73DB08E@castlepoint.net> <5423C5E9-C6A4-4285-9349-F6928BA5D689@umn.edu>
In-Reply-To: <5423C5E9-C6A4-4285-9349-F6928BA5D689@umn.edu>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="p6sDx158VsAp83MjGOIW8Tnpfjwd1SI67"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Mon, 17 Feb 2014 20:28:30 +0000 (UTC)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/LE3PXi4ZYg9xCMsUP3WL3hoFVQU
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: Mon, 17 Feb 2014 20:28:36 -0000

On 2/15/14, 11:25 AM, David Farmer wrote:

> As an example: let's say your ROUTER_ID is 192.0.2.5 or 0xC0000205.
> Then you can use an IPv6 loopback address of 2001:db8:1::c000:205, or
> you could even used mixed notation 2001:db8:1::192.0.2.5.

You could, but you shouldn't whether it's merely shorthand or not
because ipv6 mapped ipv4 addresses and accompanying notation are are
sort of ugly representation that will be throwing junior network
operators under the bus for years to come.

http://tools.ietf.org/html/draft-itojun-v6ops-v4mapped-harmful-00

v2.23.0 | Report a Bug | By Email