Re: [Dots] IPR confirmation for draft-ietf-dots-rfc8782-bis-02

supjps-ietf@jpshallow.com Thu, 26 November 2020 11:12 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 059113A11A1 for <dots@ietfa.amsl.com>; Thu, 26 Nov 2020 03:12:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 WfD1B5L-shu5 for <dots@ietfa.amsl.com>; Thu, 26 Nov 2020 03:12:43 -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 CA9933A11E9 for <dots@ietf.org>; Thu, 26 Nov 2020 03:12:41 -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 1kiFCZ-00035u-1R; Thu, 26 Nov 2020 11:12:39 +0000
From: <supjps-ietf@jpshallow.com>
To: <mohamed.boucadair@orange.com>, "'Valery Smyslov'" <valery@smyslov.net>, <draft-ietf-dots-rfc8782-bis@ietf.org>
Cc: <dots-chairs@ietf.org>, <dots@ietf.org>
References: <0eeb01d6c3c6$ab431710$01c94530$@smyslov.net> <11455_1606384251_5FBF7A7B_11455_247_1_787AE7BB302AE849A7480A190F8B933031584357@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <11455_1606384251_5FBF7A7B_11455_247_1_787AE7BB302AE849A7480A190F8B933031584357@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Date: Thu, 26 Nov 2020 11:12:44 -0000
Message-ID: <000301d6c3e5$104961a0$30dc24e0$@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: AQKVYpiwwecbJMbSk9xhSDFHWW5t+AJVlHBUqEpUWWA=
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/wP5kheyWwgXbEfISsjFWWV3DBGw>
Subject: Re: [Dots] IPR confirmation for draft-ietf-dots-rfc8782-bis-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, 26 Nov 2020 11:12:46 -0000

Hi Valery and all,

I likewise confirm that I do not have any IPR or am aware of any related to
this draft.

In terms of the propriety implementation that I work on, as all the CBOR
mappings were the same so there was no need to change any code specifically
relating to  this draft (other than updating some code comments).  The YANG
model (the primary change to rfc8782) is used as a reference guidance and
the new augmenting helps clarify what should be happening.

Kaname and I did an interop (propriety versus open source implementations)
recently and no issues were found with this draft.

Regards

Jon 


> -----Original Message-----
> From: Dots [mailto:dots-bounces@ietf.org] On Behalf Of
mohamed.boucadair@orange.com
> Sent: 26 November 2020 09:51
> To: Valery Smyslov; draft-ietf-dots-rfc8782-bis@ietf.org
> Cc: dots-chairs@ietf.org; dots@ietf.org
> Subject: Re: [Dots] IPR confirmation for draft-ietf-dots-rfc8782-bis-02
> 
> Hi Valery, all,
> 
> I don't have any IPR nor I'm aware of any related to this draft.
> 
> There are at least two implementations. Jon and Kaname can provide more
> information including latest interops.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : Valery Smyslov [mailto:valery@smyslov.net]
> > Envoyé : jeudi 26 novembre 2020 08:35
> > À : draft-ietf-dots-rfc8782-bis@ietf.org
> > Cc : dots@ietf.org; dots-chairs@ietf.org
> > Objet : IPR confirmation for draft-ietf-dots-rfc8782-bis-02
> >
> > Hi authors,
> >
> > while preparing shepherd write-up for draft-ietf-dots-rfc8782-bis-
> > 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. I know that at the time of draft adoption you provided
> > this confirmation. Can you, please, re-confirm it for the latest
> > version of the draft.
> >
> > And I'd also like to ask you about implementation status of the
> > draft.
> > I guess that there is at least one implementation of the draft.
> > Am I right? Are there other implementations 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.
> 
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots