From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2F238ED2 for ; Fri, 15 Sep 2023 03:08:19 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 45AB6C433C8; Fri, 15 Sep 2023 03:08:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1694747299; bh=7FrTAJzDfQNtCoU7xoLCY3JDAAiuz6chuqMQHUAg074=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=gKu9pswdkmp7iVYNR2YoS1HTjjkROIlZL6oQ0F6PnEPdjxfi5y/ms0xHxjHDOLhma rQICRSMN0yJlYbutX17NwAbTz2abApq/0RlkSBWtU6qwv6J4s4z0xbNmaphXJ/UNxy tlhZPybZyGmOv283sM3x1B+57noDfwnAFnG1laW+aTUncVPzlWJja42RXTaENeDm5R cRVQNIMLah8tJxY5Yt5j8TzZycCAfuJN/RezClRhh2k5gH8fNe3qvQxhCQ5k6akVue fxeLn3eU6Jf1nMSefqLu+8/7M45zMU35ac3CumdmTzzH91++zDF7XYsfV1HHXPfZZv iS/YTSRpgMu2g== Message-ID: Date: Thu, 14 Sep 2023 21:08:18 -0600 Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.15.0 Subject: Re: [PATCH net-next] ipv6: do not merge differe type and protocol routes Content-Language: en-US To: Hangbin Liu , Nicolas Dichtel Cc: netdev@vger.kernel.org, "David S . Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Ido Schimmel , Thomas Haller References: <20230830061550.2319741-1-liuhangbin@gmail.com> <01baf374-97c0-2a6f-db85-078488795bf9@kernel.org> <62bcd732-31ed-e358-e8dd-1df237d735ef@6wind.com> <2546e031-f189-e1b1-bc50-bc7776045719@kernel.org> From: David Ahern In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 9/14/23 8:23 PM, Hangbin Liu wrote: > On Fri, Sep 01, 2023 at 11:36:51AM +0200, Nicolas Dichtel wrote: >>> I do agree now that protocol is informative (passthrough from the kernel >>> perspective) so not really part of the route. That should be dropped > > I'm not sure. Is there any user space route daemon will use this info? e.g. some > BGP route daemon? It is passthrough information for userspace to track who installed the route. It is not part of the route itself, but metadata passed in and returned.