Re: [Dots] IPR confirmation for draft-ietf-dots-robust-blocks-02

supjps-ietf@jpshallow.com Thu, 10 February 2022 10:41 UTC

Return-Path: <jon.shallow@jpshallow.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B04493A0D3A for <dots@ietfa.amsl.com>; Thu, 10 Feb 2022 02:41:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 jp8AEgYvEpkl for <dots@ietfa.amsl.com>; Thu, 10 Feb 2022 02:40:56 -0800 (PST)
Received: from mail.jpshallow.com (mail.jpshallow.com [217.40.240.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 280F13A0CB3 for <dots@ietf.org>; Thu, 10 Feb 2022 02:40:55 -0800 (PST)
Received: from mail2.jpshallow.com ([192.168.0.3] helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.92.3) (envelope-from <jon.shallow@jpshallow.com>) id 1nI6sd-0004Rh-PA; Thu, 10 Feb 2022 10:40:51 +0000
From: supjps-ietf@jpshallow.com
To: 'Valery Smyslov' <valery@smyslov.net>, draft-ietf-dots-robust-blocks@ietf.org, dots@ietf.org
Cc: dots-chairs@ietf.org
References: <18e601d81e4e$30dde340$9299a9c0$@smyslov.net> <9271_1644481412_6204CB84_9271_137_1_787AE7BB302AE849A7480A190F8B93303548F623@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <9271_1644481412_6204CB84_9271_137_1_787AE7BB302AE849A7480A190F8B93303548F623@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Date: Thu, 10 Feb 2022 10:40:51 -0000
Message-ID: <053401d81e6a$ac513740$04f3a5c0$@jpshallow.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKQ/EmWxD4QtN1GoaZErccuWK5P/AK/Pc7xqwThl2A=
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/_XJZCv8O8dbHaSg9s9ZGBMa8_No>
Subject: Re: [Dots] IPR confirmation for draft-ietf-dots-robust-blocks-02
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Feb 2022 10:41:06 -0000

Hi all,

I likewise confirm that I do not have any IPR, nor am I aware of any related
to this I-D.

I confirm that I do have an implementation that negotiates these parameters,
as well as using the rest of the draft-ietf-core-new-block that these
parameters are associated with.

Regards

Jon

> -----Original Message-----
> From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com]
> Sent: 10 February 2022 08:24
> To: Valery Smyslov; draft-ietf-dots-robust-blocks@ietf.org; dots@ietf.org
> Cc: dots-chairs@ietf.org
> Subject: RE: IPR confirmation for draft-ietf-dots-robust-blocks-02
> 
> Hi Valery, all,
> 
> I don't have any IPR nor I'm aware of any related to this I-D.
> 
> Jon has an implementation.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : Valery Smyslov <valery@smyslov.net>
> > Envoyé : jeudi 10 février 2022 08:17
> > À : draft-ietf-dots-robust-blocks@ietf.org; dots@ietf.org
> > Cc : dots-chairs@ietf.org
> > Objet : IPR confirmation for draft-ietf-dots-robust-blocks-02
> >
> > Hi authors,
> >
> > while preparing shepherd write-up for draft-ietf-dots-robust-blocks-02,
> > in accordance with BCP78 and BCP79 I have to ask all authors and
> > contributors whether they are aware of any IPR regarding this document.
> > Can you please confirm that you are not aware of any IPR or disclose any
> > IPR you are aware of that are concerned with this draft.
> >
> > I'd also like to ask authors about implementation status of the draft.
> > Are there any implementations that follow recommendations from the draft
> > you are aware of?
> >
> > Regards,
> > Valery.
> 
> 
> ___________________________________________________________________
> ______________________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
recu ce
> message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou
> falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and
delete this
> message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.