IETF Logo Mail Archive

Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-dns-capture-format

S Mooensamy <sm+ietf@elandsys.com> Sat, 07 July 2018 10:19 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2FE4130DEE for <dnsop@ietfa.amsl.com>; Sat, 7 Jul 2018 03:19:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=zw/kSydg; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=ykCisYEc
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 B0cuDz0PA3C0 for <dnsop@ietfa.amsl.com>; Sat, 7 Jul 2018 03:19:20 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id CF379130E03 for <dnsop@ietf.org>; Sat, 7 Jul 2018 03:19:20 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.20.123]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id w67AJ6E2000189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 7 Jul 2018 03:19:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1530958757; x=1531045157; bh=VTkolqmu3T6PBNSHmEvGTJzjpL4Oog6Mecgjqeb2zOw=; h=Date:To:From:Subject:In-Reply-To:References; b=zw/kSydgG/c1UnkJ0Es1pZrZGInpjMjZ5XKLbiJj8Hcfyu6lFD2hmrcn8PW6NsHAj PqC3V2Xp10D4bx2mWDIGnvuT87VJkIkDpGXQwTZV2xxQGdgN8/tpQujuVvDv+E0TAW l99TASL48h4p7Wwle8t/PuFVAKXNe3qrz9s2t/VE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1530958757; x=1531045157; i=@elandsys.com; bh=VTkolqmu3T6PBNSHmEvGTJzjpL4Oog6Mecgjqeb2zOw=; h=Date:To:From:Subject:In-Reply-To:References; b=ykCisYEc6CZDowo5lN+zeLq4bTzLUm7jc/IVldDr7tkeif5KPor6EAftYo4t2Iivq mvWprymtXVlxtWIVaiH2VfN5i8Y/n4ID3FfGmbvk0Sz/fVAcD8xnzUQ8q42VIn+uA0 gtkQp1xWXrvIS9WDl3eQMnc+7UE3LDJSs2/iAOA8=
Message-Id: <6.2.5.6.2.20180707024510.0b62f740@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 07 Jul 2018 03:18:06 -0700
To: Tim Wicinski <tjw.ietf@gmail.com>, dnsop@ietf.org
From: S Mooensamy <sm+ietf@elandsys.com>
In-Reply-To: <CADyWQ+ELFcHvOuaKBAz2=oOs_ps2rEUS5qcjHBWe4vun4-3BTA@mail.g mail.com>
References: <b96bf132-ac52-e687-a8b4-19dcb9d35249@gmail.com> <6.2.5.6.2.20180707001051.0d40cbb8@elandnews.com> <CADyWQ+ELFcHvOuaKBAz2=oOs_ps2rEUS5qcjHBWe4vun4-3BTA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/rDuitBtg17aaT0EzkbTtISeDOP0>
Subject: Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-dns-capture-format
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jul 2018 10:19:22 -0000

Hi Tim,
At 02:31 AM 07-07-2018, Tim Wicinski wrote:
>There were initial concerns that the IPR was unclear, and never 
>fully settled.
>All the guidance I received was that the issue would be addressed
>
>https://datatracker.ietf.org/ipr/2909/
>
>Yes, it is old, but it was the only reference I could dig up.

Thank you for the URL.  The Tracker does not list the IPR disclosure 
for the WG draft.  I suggest looking at Section 3.3 of RFC 6702 [1].

Regards,
S. Moonesamy

1. It is Informational

v2.23.0 | Report a Bug | By Email