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

Christopher Morrow <morrowc.lists@gmail.com> Sun, 09 October 2011 14:01 UTC

Return-Path: <christopher.morrow@gmail.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 61F5F21F8A96 for <sidr@ietfa.amsl.com>; Sun, 9 Oct 2011 07:01:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.999
X-Spam-Level:
X-Spam-Status: No, score=-102.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 Y9+NOSqw7XsL for <sidr@ietfa.amsl.com>; Sun, 9 Oct 2011 07:01:08 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id D448C21F8A6C for <sidr@ietf.org>; Sun, 9 Oct 2011 07:01:08 -0700 (PDT)
Received: by iaby26 with SMTP id y26so7796866iab.31 for <sidr@ietf.org>; Sun, 09 Oct 2011 07:01:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=aYmxtKf9pCJmZr2CxXeC3dxdYA2qpyV3uRiLALDzjVE=; b=lyQ/f0ArEQe5M/S1A4J6c7uF2DLu9DOVygz9KGc/NgeOkLt0MGiPmqUXDDNM8MxgC2 J46mvwTowe/kHSFiWI+h3mgqBSdUEE8qXDnVpjEbcS5O2KN6CYOfvvV8uftJF/1a0dKp 2VBRQwJG37ScnSRYhDRVtZBf5luGhUkWn0h5Q=
MIME-Version: 1.0
Received: by 10.231.20.218 with SMTP id g26mr2792848ibb.88.1318168867433; Sun, 09 Oct 2011 07:01:07 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.231.59.206 with HTTP; Sun, 9 Oct 2011 07:01:07 -0700 (PDT)
In-Reply-To: <003f01cc84f3$72b22a60$4001a8c0@gateway.2wire.net>
References: <20111001163959.11213.35009.idtracker@ietfa.amsl.com> <003f01cc84f3$72b22a60$4001a8c0@gateway.2wire.net>
Date: Sun, 9 Oct 2011 10:01:07 -0400
X-Google-Sender-Auth: AtUfYiwr7sCUweU7n6_m3ICQMUI
Message-ID: <CAL9jLaZy4cmJ4T7wdyjh_9ARak=mygxKzz4kFnxzZx+drKwvBA@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: "t.petch" <ietfc@btconnect.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: sidr@ietf.org
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: Sun, 09 Oct 2011 14:01:09 -0000

On Fri, Oct 7, 2011 at 9:17 AM, t.petch <ietfc@btconnect.com> wrote:
> 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?
>

after a long discussion ... err, 'open to anything' seems like the right answer.
you only care about it from cache -> router or router -> cache, so you
can know sally's talking to bob, not jane.

-chris
<wg-regular-dude>

> 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
>
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
>