All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ahmed Abdelsalam <ahabdels@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	andrea.mayer@uniroma2.it
Subject: Re: [PATCH] seg6: using DSCP of inner IPv4 packets
Date: Sat, 15 Aug 2020 11:47:04 +0200	[thread overview]
Message-ID: <56fb26ec-f35f-a7e9-53af-2ede1104bd28@gmail.com> (raw)
In-Reply-To: <20200807.174342.2147963305722259387.davem@davemloft.net>

Hi David,

Sorry for the late reply. I'm on PTO with limited email access.

I will revise the patch in the next weeks and make outer IPv6 header 
inherit Hop limit from Inner packet for the IPv6 case.

Ahmed


On 08/08/2020 02:43, David Miller wrote:
> From: Ahmed Abdelsalam <ahabdels@gmail.com>
> Date: Thu, 6 Aug 2020 08:43:06 +0200
> 
>> SRv6 as defined in [1][2] does not mandate that the hop_limit of the
>> outer IPv6 header has to be copied from the inner packet.
> 
> This is not an issue of seg6 RFCs, but rather generic ip6 in ip6
> tunnel encapsulation.
> 
> Therefore, what the existing ip6 tunnel encap does is our guide,
> and it inherits from the inner header.
> 
> And that's what the original seg6 code almost certainly used to
> guide the decision making in this area.
> 

      reply	other threads:[~2020-08-15 22:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04  7:40 [PATCH] seg6: using DSCP of inner IPv4 packets Ahmed Abdelsalam
2020-08-04 20:08 ` David Miller
2020-08-06  0:40 ` David Miller
2020-08-06  6:43   ` Ahmed Abdelsalam
2020-08-08  0:43     ` David Miller
2020-08-15  9:47       ` Ahmed Abdelsalam [this message]

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=56fb26ec-f35f-a7e9-53af-2ede1104bd28@gmail.com \
    --to=ahabdels@gmail.com \
    --cc=andrea.mayer@uniroma2.it \
    --cc=davem@davemloft.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.