IETF Logo Mail Archive

Re: New Version Notification for draft-petrescu-6man-ll-prefix-len-17.txt

sthaug@nethelp.no Fri, 10 May 2019 08:31 UTC

Return-Path: <sthaug@nethelp.no>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2237612017A for <ipv6@ietfa.amsl.com>; Fri, 10 May 2019 01:31:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 VQN4_Jayq6wz for <ipv6@ietfa.amsl.com>; Fri, 10 May 2019 01:30:58 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by ietfa.amsl.com (Postfix) with ESMTP id ED3AF120177 for <ipv6@ietf.org>; Fri, 10 May 2019 01:30:57 -0700 (PDT)
Received: from localhost (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by bizet.nethelp.no (Postfix) with ESMTP id 8CD1BE6047; Fri, 10 May 2019 10:30:55 +0200 (CEST)
Date: Fri, 10 May 2019 10:30:55 +0200
Message-Id: <20190510.103055.305870287.sthaug@nethelp.no>
To: alexandre.petrescu@gmail.com
Cc: nick@foobar.org, ipv6@ietf.org
Subject: Re: New Version Notification for draft-petrescu-6man-ll-prefix-len-17.txt
From: sthaug@nethelp.no
In-Reply-To: <3353e235-8f20-eb1f-847b-16fda4db0a5e@gmail.com>
References: <880be598-be49-a28c-57eb-f5e27a92a8f0@gmail.com> <5a96f657-9db3-6ecc-7bc7-b2e744361af3@foobar.org> <3353e235-8f20-eb1f-847b-16fda4db0a5e@gmail.com>
X-Mailer: Mew version 6.7 on Emacs 26 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/SLx-_raUdTeR8Q1ZcS7zmK1WOOM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2019 08:31:00 -0000

>>> Why OSPF(v3) for IPv6 does not use an IPv6 address in the neighbor ID,
>>> and why does it use an IPv4 address instead?
>> both OSPFv2 and OSPFv3 use a 32-bit instance ID, which is
>> traditionally represented as an ipv4 address.  It's not actually an
>> ipv4 address.
> 
> The 32bit instance ID responds to ping?

No.

> The 32bit instance ID is present in routing tables as next-hop?

No.

Think of it as a 32-bit *number*, not as an IPv4 address (because it
*is not* an IPv4 address).

Steinar Haug, AS2116

v2.23.0 | Report a Bug | By Email