IETF Logo Mail Archive

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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 10 May 2019 08:18 UTC

Return-Path: <alexandre.petrescu@gmail.com>
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 9103E120125 for <ipv6@ietfa.amsl.com>; Fri, 10 May 2019 01:18:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] 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 Hh-eQygewAFS for <ipv6@ietfa.amsl.com>; Fri, 10 May 2019 01:18:49 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 DEDFB120113 for <ipv6@ietf.org>; Fri, 10 May 2019 01:18:48 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x4A8IbmM025644; Fri, 10 May 2019 10:18:37 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 42BDF2041A5; Fri, 10 May 2019 10:18:37 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 3A34E2041A4; Fri, 10 May 2019 10:18:37 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x4A8Ib4f017914; Fri, 10 May 2019 10:18:37 +0200
Subject: Re: New Version Notification for draft-petrescu-6man-ll-prefix-len-17.txt
To: Nick Hilliard <nick@foobar.org>
Cc: Gyan Mishra <hayabusagsm@gmail.com>, IPv6 <ipv6@ietf.org>
References: <155721765664.29439.5319050830659075854.idtracker@ietfa.amsl.com> <a8b10b95-d06a-827b-b3b9-72e7dca0ec69@gmail.com> <CABNhwV0Gexct===O6iyuLi3Xi=3AA-HDjkwiC5_h=_DjaJ0XDg@mail.gmail.com> <f5c51387-c7da-fcc9-a9b4-dbbce4483b28@gmail.com> <8751E773-74FA-4468-BE0A-5CE7474B270A@gmail.com> <880be598-be49-a28c-57eb-f5e27a92a8f0@gmail.com> <5a96f657-9db3-6ecc-7bc7-b2e744361af3@foobar.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <3353e235-8f20-eb1f-847b-16fda4db0a5e@gmail.com>
Date: Fri, 10 May 2019 10:18:37 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <5a96f657-9db3-6ecc-7bc7-b2e744361af3@foobar.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/dkoRvbfsk_5l3TzRnTPtDEukXtY>
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:18:51 -0000


Le 09/05/2019 à 19:03, Nick Hilliard a écrit :
> Alexandre Petrescu wrote on 09/05/2019 17:54:
>> 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?

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

Alex

v2.23.0 | Report a Bug | By Email