[sidr] Fwd: New Version Notification for draft-madi-sidr-rp-00.txt

Declan Ma <madihello@icloud.com> Wed, 27 April 2016 01:47 UTC

Return-Path: <madihello@icloud.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8553F12D59B; Tue, 26 Apr 2016 18:47:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level:
X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=icloud.com
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 CCsZ7JubXhQW; Tue, 26 Apr 2016 18:46:58 -0700 (PDT)
Received: from pv33p07im-ztdg10141401.me.com (pv33p07im-ztdg10141401.me.com [17.142.253.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB39712B043; Tue, 26 Apr 2016 18:46:58 -0700 (PDT)
Received: from process-dkim-sign-daemon.pv33p07im-ztdg10141401.me.com by pv33p07im-ztdg10141401.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) id <0O6900800R4J0G00@pv33p07im-ztdg10141401.me.com>; Wed, 27 Apr 2016 01:46:58 +0000 (GMT)
Received: from [172.20.10.2] (unknown [61.148.243.162]) by pv33p07im-ztdg10141401.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0O6900BK5RM0BC20@pv33p07im-ztdg10141401.me.com>; Wed, 27 Apr 2016 01:46:57 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-27_01:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=7 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1604270019
Content-type: text/plain; charset="gb2312"
MIME-version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Declan Ma <madihello@icloud.com>
Date: Wed, 27 Apr 2016 09:46:47 +0800
Content-transfer-encoding: quoted-printable
Message-id: <E3DE4ED0-1BAE-48EE-849B-E0E0813CE411@icloud.com>
References: <20160412100344.32250.28492.idtracker@ietfa.amsl.com>
To: IETF SIDR <sidr@ietf.org>
X-Mailer: Apple Mail (2.3124)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=4d515a; t=1461721618; bh=z/sHhkVH/MU9nTqWr3oyqmSE05EYYXWZi1nN+CsJduU=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=T7BH3K6CQoyVsbzk4Yo7pTlvSz9glFYGSjqeaxdFyYptjWTwR5Uww3QftGExULC+d rBE5KmHG01p2hCwHSAQKxf3PsXpRIgFh/MKURQVR5Ih+WkxfgxkQqflh2f4svmKypw WohuaAQD1VqDqf6kgTWtK6CqzkJxzhchFNuIq171rwYD4PulWJjGaWwXYtb5O1InAa xQWPHFJm5cBmVabBojUaM2B1B0S8nwpMs+PNQ/SMa5+GMsF9d4K3XfCVVsvUMVDi9b SVxyzjf1JGVFQAM/4iJN509RLRtK6yosN/daA6fIG+02scD0Xn7OVD3GCmqStEKJp7 LSy5EULwSdncw==
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/xLZcHTJ-c3Le4-4PDp6RDLHLOgk>
Cc: sidr chairs <sidr-chairs@ietf.org>
Subject: [sidr] Fwd: New Version Notification for draft-madi-sidr-rp-00.txt
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2016 01:47:00 -0000

Hi, folks,

Steve Kent and I have generated this document to try to consolidate RP requirements in one document, with pointers to all the relevant RFCs. 

As I mentioned in IETF 95 meeting, there is no standards language (e.g., MUST, SHOULD, MAY, ...) in this doc, as it is just POINTING to the docs that have the real requirements. 

This doc outlines the RP functions, summarizes them and then gives reference to those precise sections or paragraphs, in order to make life easier for implementers to make sure he/she has addressed all of these requirements. 

Any comments and feedbacks are appreciated.


Di

ZDNS


> 下面是被转发的邮件:
> 
> 发件人: internet-drafts@ietf.org
> 主题: New Version Notification for draft-madi-sidr-rp-00.txt
> 日期: 2016年4月12日 GMT+8 18:03:44
> 收件人: "Dr. Stephen T. Kent" <kent@bbn.com>, "Di Ma" <madi@zdns.cn>, "Stephen Kent" <kent@bbn.com>
> 
> 
> A new version of I-D, draft-madi-sidr-rp-00.txt
> has been successfully submitted by Di Ma and posted to the
> IETF repository.
> 
> Name:		draft-madi-sidr-rp
> Revision:	00
> Title:		Requirements for Resource Public Key Infrastructure (RPKI) Relying Parties
> Document date:	2016-04-12
> Group:		Individual Submission
> Pages:		10
> URL:            https://www.ietf.org/internet-drafts/draft-madi-sidr-rp-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-madi-sidr-rp/
> Htmlized:       https://tools.ietf.org/html/draft-madi-sidr-rp-00
> 
> 
> Abstract:
>   This document provides a single reference point for requirements for
>   Relying Party (RP) software for use in the Resource Public Key
>   Infrastructure (RPKI).  It cites requirements that appear in several
>   RPKI RFCs, making it easier for implementers to become aware of these
>   requirements.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>