[Sidrops] draft-madi-sidrops-rp adoption
Di Ma <madi@zdns.cn> Tue, 18 July 2017 08:21 UTC
Return-Path: <madi@zdns.cn>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 486381317AD for <sidrops@ietfa.amsl.com>; Tue, 18 Jul 2017 01:21:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=zdns.cn
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 MJBtv1zZnqb6 for <sidrops@ietfa.amsl.com>; Tue, 18 Jul 2017 01:21:20 -0700 (PDT)
Received: from mail.zdns.cn (mail.zdns.cn [202.173.10.13]) (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 313CF131A50 for <sidrops@ietf.org>; Tue, 18 Jul 2017 01:21:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zdns.cn; s=dkim; x=1500970878; i=madi@zdns.cn; h=From:Content-Type: Content-Transfer-Encoding:Mime-Version:Subject:Message-Id:Date: Cc:To; bh=rMAnhQf8hEfN2mcwW3YtDssEe/PJIErL9h/twcWvkgY=; b=ma2Tlt TAxdKrRskFys0KBkCEBwp2/3YhE2coaLxL/fnhVC1ZbwZJOMrPW0QpZk0g3FoRNF LvivQH1CVe2Io6gie010qDKri2xFEpxJYySwPFcXGbVr7k+3z9QWnvaFRR8gOXaj BBmZpZrqITrxaUUHcw6Rdw8zHE5KTye9k6OiY=
X-TM-DID: 0e6c0e80312adf8b6989fbe7fc72405b
From: Di Ma <madi@zdns.cn>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <BC0A2FAD-0982-43F2-8734-64D734686BDB@zdns.cn>
Date: Tue, 18 Jul 2017 10:21:10 +0200
Cc: Chris Morrow <morrowc@ops-netman.net>, Keyur Patel <keyur@arrcus.com>
To: sidrops@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/mhDe38dVR12e8Xsc_5qmfzm6sfU>
Subject: [Sidrops] draft-madi-sidrops-rp adoption
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 08:21:22 -0000
Hi all, As I mentioned in SIDROPS meeting yesterday, we authors think the informational draft Requirements for RPKI Relying Parties (draft-madi-sidrops-rp-00) is in alignment with the charter of this WG in terms of RP. This document provides a single reference point for requirements for RP software for use in the RPKI and it outlines the RP functions, summarizes them and then gives reference to those precise sections or paragraphs. Chairs, please consider this a formal request to put out an adoption call. Thanks. Di