From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934008AbeAJPbg (ORCPT + 1 other); Wed, 10 Jan 2018 10:31:36 -0500 Received: from mail.us.es ([193.147.175.20]:59246 "EHLO mail.us.es" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752580AbeAJPbc (ORCPT ); Wed, 10 Jan 2018 10:31:32 -0500 Date: Wed, 10 Jan 2018 16:31:27 +0100 X-SMTPAUTHUS: auth mail.us.es From: Pablo Neira Ayuso To: Ahmed Abdelsalam Cc: davem@davemloft.net, linux-kernel@vger.kernel.org, netfilter-devel@vger.kernel.org, coreteam@netfilter.org Subject: Re: [net-next v2] netfilter: add segment routing header 'srh' match Message-ID: <20180110153127.4cc22m25p7vhavkj@salvia> References: <1515349322-23097-1-git-send-email-amsalam20@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1515349322-23097-1-git-send-email-amsalam20@gmail.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Sun, Jan 07, 2018 at 07:22:02PM +0100, Ahmed Abdelsalam wrote: > It allows matching packets based on Segment Routing Header > (SRH) information. > The implementation considers revision 7 of the SRH draft. > https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-07 > > Currently supported match options include: > (1) Next Header > (2) Hdr Ext Len > (3) Segments Left > (4) Last Entry > (5) Tag value of SRH Now applied to nf-next, thanks for your patience.