Re: [sidr] I-D Action: draft-ietf-sidr-rpki-rtr-17.txt

"t.petch" <ietfc@btconnect.com> Fri, 07 October 2011 14:21 UTC

Return-Path: <ietfc@btconnect.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 934B921F8BAB for <sidr@ietfa.amsl.com>; Fri, 7 Oct 2011 07:21:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.73
X-Spam-Level:
X-Spam-Status: No, score=-1.73 tagged_above=-999 required=5 tests=[AWL=-0.423, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UdEVQM+pLnWy for <sidr@ietfa.amsl.com>; Fri, 7 Oct 2011 07:21:17 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr13.btconnect.com [213.123.20.131]) by ietfa.amsl.com (Postfix) with ESMTP id B077921F8BA4 for <sidr@ietf.org>; Fri, 7 Oct 2011 07:21:16 -0700 (PDT)
Received: from host86-163-147-122.range86-163.btcentralplus.com (HELO pc6) ([86.163.147.122]) by c2bthomr13.btconnect.com with SMTP id EQY98770; Fri, 07 Oct 2011 15:21:57 +0100 (BST)
Message-ID: <003f01cc84f3$72b22a60$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
Cc: <sidr@ietf.org>
References: <20111001163959.11213.35009.idtracker@ietfa.amsl.com>
Date: Fri, 7 Oct 2011 15:17:06 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4E8F0B05.014B, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.10.7.133314:17:7.586, ip=86.163.147.122, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, MISSING_HEADERS, __ANY_URI, __CP_URI_IN_BODY, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_1600_1699, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, __PHISH_SPEAR_STRUCTURE_1, RDNS_SUSP, BODY_SIZE_2000_LESS, __PHISH_SPEAR_STRUCTURE_2, BODY_SIZE_7000_LESS, TO_MALFORMED
X-Junkmail-Status: score=10/50, host=c2bthomr13.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0205.4E8F0B9D.0004, ss=1, fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Subject: Re: [sidr] I-D Action: draft-ietf-sidr-rpki-rtr-17.txt
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 07 Oct 2011 14:21:17 -0000

When this says, in s.7.2, that the CN field should be used to denote the
router's identity, is there any underlying idea what form that should take?
serial number, sysName, iPAddress or is it open to anything?

Tom Petch


----- Original Message -----
From: <internet-drafts@ietf.org>
To: <i-d-announce@ietf.org>
Cc: <sidr@ietf.org>
Sent: Saturday, October 01, 2011 6:39 PM
Subject: [sidr] I-D Action: draft-ietf-sidr-rpki-rtr-17.txt


> A New Internet-Draft is available from the on-line Internet-Drafts
directories. This draft is a work item of the Secure Inter-Domain Routing
Working Group of the IETF.
>
> Title           : The RPKI/Router Protocol
> Author(s)       : Randy Bush
>                           Rob Austein
> Filename        : draft-ietf-sidr-rpki-rtr-17.txt
> Pages           : 25
> Date            : 2011-10-01
>
>    In order to formally validate the origin ASs of BGP announcements,
>    routers need a simple but reliable mechanism to receive RPKI
>    [I-D.ietf-sidr-arch] prefix origin data from a trusted cache.  This
>    document describes a protocol to deliver validated prefix origin data
>    to routers.
>
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sidr-rpki-rtr-17.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-sidr-rpki-rtr-17.txt
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr