From nobody Mon Sep 29 07:21:35 2014 Return-Path: X-Original-To: int-dir@ietfa.amsl.com Delivered-To: int-dir@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 580871A7009 for ; Mon, 29 Sep 2014 00:35:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham 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 uTbqpwi3_0Ho for ; Mon, 29 Sep 2014 00:35:11 -0700 (PDT) Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 831011A700D for ; Mon, 29 Sep 2014 00:35:11 -0700 (PDT) Received: by mail-la0-f45.google.com with SMTP id q1so5739448lam.4 for ; Mon, 29 Sep 2014 00:35:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=VtmGwLiEJdiltUU1BG14eJHh1Qpuw7lNaX2LlLKZpoc=; b=OoRFW9vNd4OC/RjG6Ndt1DFeBcpSR0xRrAZ86qgE+SCAl4ST/1768e7fcGPtyHAzZd GvlTkancxnNBBog/HfT3aQncIRo9+ORJGO22sglJdnSyQYH634tycO+wt3J0ZRKS613U jYbYuEFsCz4Hw9NoRxIs2bSooCG3DAiUydck87X/pFNj5NhzuhBi4LdwJAuGBiKaujIf fRvPt1SEXI1D7EPPOZ99BLI1i8FL3wBihg0kkTF1hkxs6q7IvZRLIuwUuGQTJZPSJTm2 0gF/sP/1Kypct+EpXJhCNaLeGHtsa8tLYsqR45KFe+8mX0D2UPg0CnQPquid6vgEq4EG enoQ== X-Received: by 10.112.138.8 with SMTP id qm8mr35471684lbb.37.1411976109503; Mon, 29 Sep 2014 00:35:09 -0700 (PDT) Received: from martins-mbp-4.fritz.box (port-92-202-110-123.dynamic.qsc.de. [92.202.110.123]) by mx.google.com with ESMTPSA id ro7sm4173831lbb.14.2014.09.29.00.35.08 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Sep 2014 00:35:08 -0700 (PDT) Message-ID: <54290BAB.9000604@gmail.com> Date: Mon, 29 Sep 2014 09:35:07 +0200 From: Martin Stiemerling User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: int-dir@ietf.org Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/int-dir/5ViclXBn-9LwaMNKwCgsi2tMu-8 X-Mailman-Approved-At: Mon, 29 Sep 2014 07:21:32 -0700 Subject: [Int-dir] Looking for an expert reviewer for the S-NAPTR registry @ IANA X-BeenThere: int-dir@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: mls.ietf@gmail.com List-Id: "This list is for discussion between the members of the Internet Area directorate." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 07:35:13 -0000 Hi, IANA is maintaining a registry for the Straightforward-NAPTR (S-NAPTR) paramters [1]. No expert reviewer has been assigned to this registry by now and IANA is looking for such an expert reviewer. The role of an expert reviewer is defined in RFC 5226 in Section 3. "Designated Experts". Please contact me directly, in case you know somebody who could be willing to serve as expert for the S-NAPTR registries. There are typically not many request to be reviewed for this registry. Thank you, Martin Stiemerling [1] http://www.iana.org/assignments/s-naptr-parameters/s-naptr-parameters.xhtml