Re: [sidr] about a router AS-related certificate
Stephen Kent <kent@bbn.com> Mon, 17 October 2011 14:53 UTC
Return-Path: <kent@bbn.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 7B5FB21F8C1D for <sidr@ietfa.amsl.com>; Mon, 17 Oct 2011 07:53:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.338
X-Spam-Level:
X-Spam-Status: No, score=-106.338 tagged_above=-999 required=5 tests=[AWL=0.261, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 rrfPuPamhemx for <sidr@ietfa.amsl.com>; Mon, 17 Oct 2011 07:53:54 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 7809221F8C19 for <sidr@ietf.org>; Mon, 17 Oct 2011 07:53:51 -0700 (PDT)
Received: from dhcp89-089-093.bbn.com ([128.89.89.93]:49167) by smtp.bbn.com with esmtp (Exim 4.74 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1RFoZa-000D8D-L8; Mon, 17 Oct 2011 10:53:50 -0400
Mime-Version: 1.0
Message-Id: <p06240806cac1efb44b4c@[128.89.89.93]>
In-Reply-To: <Pine.WNT.4.64.1110131917350.4820@SMURPHY-LT.columbia.ads.sparta.com>
References: <Pine.WNT.4.64.1110131917350.4820@SMURPHY-LT.columbia.ads.sparta.com>
Date: Mon, 17 Oct 2011 10:47:03 -0400
To: Sandra Murphy <Sandra.Murphy@sparta.com>
From: Stephen Kent <kent@bbn.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: sidr@ietf.org
Subject: Re: [sidr] about a router AS-related certificate
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: Mon, 17 Oct 2011 14:54:07 -0000
At 10:50 AM -0400 10/14/11, Sandra Murphy wrote: >The wg has just demonstrated a lack of support for adoption of a >suggested cert profile for routers in >draft-turner-sidr-bgpsec-pki-profiles. > >Unfortunately, a router certificate is already mentioned in existing >wg drafts. Sandy, Since the WG is proceeding with the BGPSEC protocol and architecture, there is a need for a cert profile for routers. It also makes sense to have these certs be tied to the RPLI, since theses certs are linked to the AS# of the net with which the router is associated. So, I believe that WG members (including me?) were not paying attention for this call for adoption. Can we have a do over :-)? Steve
- [sidr] about a router AS-related certificate Sandra Murphy
- Re: [sidr] about a router AS-related certificate … Sandra Murphy
- Re: [sidr] about a router AS-related certificate Stephen Kent
- Re: [sidr] about a router AS-related certificate Warren Kumari