netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Anton Makarov <antonmakarov11235@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, david.lebrun@uclouvain.be
Subject: Re: [net-next 1/1] seg6: add support for SRv6 Headend Reduced Encapsulation
Date: Tue, 7 Jun 2022 17:21:29 -0700	[thread overview]
Message-ID: <20220607172129.73d7b307@kernel.org> (raw)
In-Reply-To: <4f26bfaf-3c91-fe19-ede1-d47d852c17f6@gmail.com>

On Mon, 6 Jun 2022 21:41:59 +0300 Anton Makarov wrote:
> This patch extends SRv6 Headend behaviors with reduced SRH encapsulation
> accordingly to RFC 8986. Additional SRv6 Headend behaviors H.Encaps.Red and
> H.Encaps.L2.Red optimize overhead of network traffic for SRv6 L2 and L3 
> VPNs.
> 
> Signed-off-by: Anton Makarov <anton.makarov11235@gmail.com>

Thurnderbird line-wrapped the patch contents. Could you try reposting
with git send-email?

      reply	other threads:[~2022-06-08  2:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 18:41 [net-next 1/1] seg6: add support for SRv6 Headend Reduced Encapsulation Anton Makarov
2022-06-08  0:21 ` Jakub Kicinski [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=20220607172129.73d7b307@kernel.org \
    --to=kuba@kernel.org \
    --cc=antonmakarov11235@gmail.com \
    --cc=davem@davemloft.net \
    --cc=david.lebrun@uclouvain.be \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).