mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: paolo.lungaroni@cnit.it
Cc: kuba@kernel.org, kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	andrea.mayer@uniroma2.it, ahmed.abdelsalam@gssi.it
Subject: Re: [net] seg6: fix SRv6 L2 tunnels to use IANA-assigned protocol number
Date: Wed, 11 Mar 2020 23:50:31 -0700 (PDT)	[thread overview]
Message-ID: <20200311.235031.754217366237670514.davem@davemloft.net> (raw)
In-Reply-To: <20200311165406.22044-1-paolo.lungaroni@cnit.it>

From: Paolo Lungaroni <paolo.lungaroni@cnit.it>
Date: Wed, 11 Mar 2020 17:54:06 +0100

> The Internet Assigned Numbers Authority (IANA) has recently assigned
> a protocol number value of 143 for Ethernet [1].
> 
> Before this assignment, encapsulation mechanisms such as Segment Routing
> used the IPv6-NoNxt protocol number (59) to indicate that the encapsulated
> payload is an Ethernet frame.
> 
> In this patch, we add the definition of the Ethernet protocol number to the
> kernel headers and update the SRv6 L2 tunnels to use it.
> 
> [1] https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml
> 
> Signed-off-by: Paolo Lungaroni <paolo.lungaroni@cnit.it>
> Reviewed-by: Andrea Mayer <andrea.mayer@uniroma2.it>
> Acked-by: Ahmed Abdelsalam <ahmed.abdelsalam@gssi.it>

Applied.

But this is that classic case where we add a protocol element to the
tree before the official number is assigned.

Then the number is assigned and if we change it then everything using
the original number is no longer interoperable.

  reply	other threads:[~2020-03-12  6:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 16:54 Paolo Lungaroni
2020-03-12  6:50 ` David Miller [this message]
2020-03-12 10:00   ` Ahmed Abdelsalam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200311.235031.754217366237670514.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ahmed.abdelsalam@gssi.it \
    --cc=andrea.mayer@uniroma2.it \
    --cc=kuba@kernel.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paolo.lungaroni@cnit.it \
    --cc=yoshfuji@linux-ipv6.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®