Re: [Detnet] Regarding IPR on draft-sdt-detnet-security-01

Henrik Austad <henrik@austad.us> Sat, 26 August 2017 06:48 UTC

Return-Path: <henrik@austad.us>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9FEF132C82 for <detnet@ietfa.amsl.com>; Fri, 25 Aug 2017 23:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=austad-us.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nHF0Wvul24CT for <detnet@ietfa.amsl.com>; Fri, 25 Aug 2017 23:48:45 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 316AB132C7F for <detnet@ietf.org>; Fri, 25 Aug 2017 23:48:44 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id z12so2966467lfd.3 for <detnet@ietf.org>; Fri, 25 Aug 2017 23:48:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=austad-us.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=d6BQeykGy0fjtTkxHXrwPHJvbvKJCMHseAG9rmzbQyM=; b=C55abyOK3pKfGo6jeL1aCHnR+F9fjmAwskIEVw9LYaYIW9vcKFbbG5bt6rbz3sF9QP oOuyIf/1Rr/ni+RoXPO2ti3668mYK2Nf3XQTTCukUsmG7FeKY/C9tWeJosFE+r6KkqEB /JlepBsV4nnBVqJ/fxaQd0TI4Em/rwj3lDDvMGzZW4KVeAvwQfG240kG5xxgBJOKY5Ua pM4Zj5tFL6NbsUpCgLpVaAnU1DdsEbDS/IBfcUPt3Fj6IzYOh6xhFaAA74BgYBPU7yKO reJY0vSJM0zcE+1CFk6oai5XfFS4M4r6z3KozjnTb30wny0OCahlgggNqRLRdhhyfmyO OHKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=d6BQeykGy0fjtTkxHXrwPHJvbvKJCMHseAG9rmzbQyM=; b=bi/DJ/nAdE3N21Qrn00QCzmniCzKDnaz3C2A5DpitrRVJFVBb65NCf3Xh1eCOuExw+ DGlHdtwonZARQk/tUvU//k0NJH7I/CKQo6b8z9hCiMjNoxDMGS9VDsJ3MgWQrM3c1SBl oBcVzH88lOXqzqPLffOqtV4UFAXsdn0wpn8nkAVhIm6NnUQCjWKKMtTla44yu2eTzaKM Lr74y8cegAEtnqX0PQbWFuHU7avoGUqyRd/QvcLTWTUIvGEkhn04nGcCZC6ATIilmlP8 8KgavF/Yy4B+VTdiqawPL4O1uLaqxJ5zXhEF+qLROYv0GRDHQHwmxdWd2f6kPl0VYWuI vosg==
X-Gm-Message-State: AHYfb5j8GuZhoQRSyvpdRg76NiT5Vw9GmScC9VPOuomfzdvR5SeSzP5E AQ3lf8NUB/IWia+51FQ7Bg/oSV4Y8hRd
X-Received: by 10.46.81.1 with SMTP id f1mr328828ljb.142.1503730122957; Fri, 25 Aug 2017 23:48:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.86.156 with HTTP; Fri, 25 Aug 2017 23:48:42 -0700 (PDT)
X-Originating-IP: [51.175.50.162]
In-Reply-To: <6ffef23c-06f0-c7ee-b118-be2561a535ce@labn.net>
References: <6ffef23c-06f0-c7ee-b118-be2561a535ce@labn.net>
From: Henrik Austad <henrik@austad.us>
Date: Sat, 26 Aug 2017 08:48:42 +0200
Message-ID: <CAM6o_m2Qv=wKN_6PrG7OPG67W=KAnM+L8Vx+55aq1wCV9dd89w@mail.gmail.com>
To: Lou Berger <lberger@labn.net>
Cc: ajhacker@mistiqtech.com, Norman Finn <norman.finn@mail01.huawei.com>, sdas@appcomsci.com, ethan.grossman@dolby.com, "Stanton, Kevin B (kevin.b.stanton@intel.com)" <kevin.b.stanton@intel.com>, DetNet WG <detnet@ietf.org>, "Tal Mizrahi (talmi@marvell.com)" <talmi@marvell.com>, John Dowdell <john.dowdell.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="f403045ff0d8d150600557a2732d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/1iec1pDJ0WwxB4B5req2zn-Fccc>
Subject: Re: [Detnet] Regarding IPR on draft-sdt-detnet-security-01
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Aug 2017 06:48:48 -0000

No, I'm not aware of any IPR that applies to this draft

-Henrik

25. aug. 2017 10.27 p.m. skrev "Lou Berger" <lberger@labn.net>:


Authors, Contributors, WG,

As part of the preparation for WG Adoption Call:

Are you aware of any IPR that applies to drafts identified above?

Please state either:

"No, I'm not aware of any IPR that applies to this draft"
or
"Yes, I'm aware of IPR that applies to this draft"

If so, has this IPR been disclosed in compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate.

If you are listed as a document author or contributor please answer the
above by responding to this email regardless of whether or not you are
aware of any relevant IPR. This document will not advance to the next
stage until a response has been received from each author and listed
contributor. NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S
TO LINES.

If you are on the WG email list or attend WG meetings but are not listed
as an author or contributor, we remind you of your obligations under
the IETF IPR rules which encourages you to notify the IETF if you are
aware of IPR of others on an IETF contribution, or to refrain from
participating in any contribution or discussion related to your
undisclosed IPR. For more information, please see the RFCs listed above
and
http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.

Thank you,
DetNet WG Chairs

PS Please include all listed in the headers of this message in your
response.