Re: [DNSOP] Working Group Last Call on draft-ietf-dnsop-5966bis

Stephane Bortzmeyer <bortzmeyer@nic.fr> Mon, 12 October 2015 15:15 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8228B1A6FAE for <dnsop@ietfa.amsl.com>; Mon, 12 Oct 2015 08:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.56
X-Spam-Level:
X-Spam-Status: No, score=-1.56 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, T_RP_MATCHES_RCVD=-0.01] autolearn=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 ehHcCZ3gpsKZ for <dnsop@ietfa.amsl.com>; Mon, 12 Oct 2015 08:15:09 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (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 AFD261A6F99 for <dnsop@ietf.org>; Mon, 12 Oct 2015 08:15:00 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id AEB202801F8; Mon, 12 Oct 2015 17:14:58 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id A0539280125; Mon, 12 Oct 2015 17:14:58 +0200 (CEST)
Received: from bortzmeyer.nic.fr (unknown [IPv6:2001:67c:1348:7::86:133]) by relay2.nic.fr (Postfix) with ESMTP id 9286CB3800C; Mon, 12 Oct 2015 17:14:28 +0200 (CEST)
Date: Mon, 12 Oct 2015 17:14:28 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: "Visweswaran, Gowri" <gvisweswaran@verisign.com>
Message-ID: <20151012151428.GA4198@nic.fr>
References: <561813AA.30409@gmail.com> <D2412A9B.B6FF%gvisweswaran@verisign.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <D2412A9B.B6FF%gvisweswaran@verisign.com>
X-Operating-System: Debian GNU/Linux 8.2
X-Kernel: Linux 3.16.0-4-686-pae i686
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/zfEgJ_Hl4csznDWt8tfKzd4eBnQ>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Working Group Last Call on draft-ietf-dnsop-5966bis
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 12 Oct 2015 15:15:13 -0000

On Mon, Oct 12, 2015 at 01:23:27PM +0000,
 Visweswaran, Gowri <gvisweswaran@verisign.com> wrote 
 a message of 51 lines which said:

> is there any supporting documentation that outlines recommendations
> on how a recursive server can identify expected clients?

Don't think it is written down somewhere. The most common method is
restricting access to some IP prefixes. Some people probably use TSIG
instead (or SIG(0)?). OpenNIC apparently uses DNScrypt.