netdev - Re: [RFC v2 PATCH 0/5] seg6: Segment routing fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <000fe40c-18d9-9fc0-b894-f7bcecdfcb47@solarflare.com>
Date:   Mon, 10 Jun 2019 13:54:48 +0100
From:   Edward Cree <ecree@...arflare.com>
To:     Tom Herbert <tom@...bertland.com>, <davem@...emloft.net>,
        <netdev@...r.kernel.org>, <dlebrun@...gle.com>
CC:     Tom Herbert <tom@...ntonium.net>
Subject: Re: [RFC v2 PATCH 0/5] seg6: Segment routing fixes

On 07/06/2019 19:55, Tom Herbert wrote:
> This patch set includes fixes to bring the segment routing
> implementation into conformance with the latest version of the
> draft (draft-ietf-6man-segment-routing-header-19).
AIUI the concept of "conformance" doesn't really belong in the context
 of an Internet-Draft.  See e.g. RFC2026 §2.2, and the I-D preface
    'It is inappropriate to use Internet-Drafts as reference
     material or to cite them other than as "work in progress."'

-Ed