IETF Logo Mail Archive

Re: [sidr] Stephen Farrell's Discuss on draft-ietf-sidr-bgpsec-pki-profiles-19: (with DISCUSS and COMMENT)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 05 January 2017 00:19 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 C7A331294AB; Wed, 4 Jan 2017 16:19:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.401
X-Spam-Level:
X-Spam-Status: No, score=-7.401 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_MED=-2.3, RP_MATCHES_RCVD=-3.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 dkZ2ArKRt40v; Wed, 4 Jan 2017 16:19:49 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B61C129470; Wed, 4 Jan 2017 16:19:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id C2E28BE2F; Thu, 5 Jan 2017 00:19:47 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tSlwBWJlYhX4; Thu, 5 Jan 2017 00:19:46 +0000 (GMT)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D95DDBE2C; Thu, 5 Jan 2017 00:19:45 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1483575586; bh=jCVIcKLL0o0ezWcsl8Tmc3wTmN3IZPezKfHCWC8iXHc=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=HvV52YPl0u/VkOA2Zf0nHno7JVhyfN50DyXQTxuX1tp+rO+FffvqiDUXcKSV4Vu+X edjjOWbN3jcwPxoI7PHsiFH93pdGlmaLroUfCJgi3w1DxdPh8/D+gNRlpYJ2DwMm5D QN9e3DVuhzANP4VG6Otrjrvt7SUPfNmeqDaHFAEE=
To: Sean Turner <sean@sn3rd.com>
References: <148353788046.13042.160471261406266.idtracker@ietfa.amsl.com> <20170104200413.1DFD04581178@minas-ithil.hactrn.net> <99955d9c-4771-dd45-f019-313661631e87@cs.tcd.ie> <20170104221557.73CF84581C4F@minas-ithil.hactrn.net> <0811b400-fc2a-8675-7b74-4b549940de65@cs.tcd.ie> <E797A202-BF76-4D41-8679-D939E7CC44B1@sn3rd.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <c28c708f-4376-fd26-ad96-844072ff925a@cs.tcd.ie>
Date: Thu, 05 Jan 2017 00:19:45 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <E797A202-BF76-4D41-8679-D939E7CC44B1@sn3rd.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms020100070200000202070302"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/qJkpWykAOz2O5oWwQW-hr9rJae0>
Cc: Rob Austein <sra@hactrn.net>, Chris Morrow <morrowc@ops-netman.net>, sidr-chairs@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-sidr-bgpsec-pki-profiles@ietf.org, sidr@ietf.org
Subject: Re: [sidr] Stephen Farrell's Discuss on draft-ietf-sidr-bgpsec-pki-profiles-19: (with DISCUSS and COMMENT)
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: Thu, 05 Jan 2017 00:19:52 -0000

Hiya,

Yep, I guess the text below is good enough.

Thanks,
S.

On 04/01/17 23:56, Sean Turner wrote:
>    Common name encoding options that are supported are
>    printableString and UTF8String.  For BGPsec Router Certificates, it
>    is RECOMMENDED that the common name attribute contain the literal
>    string "ROUTER-" followed by the 32-bit AS Number [RFC3779] encoded
>    as eight hexadecimal digits and that the serial number attribute
>    contain the 32-bit BGP Identifier [RFC4271] (i.e., the router ID)
>    encoded as eight hexadecimal digits.  If there is more than one AS
>    number, the choice of which to include in the common name is at the
>    discretion of the Issuer. If the same certificate is issued to more
>    than one router (hence the private key is shared among these
>    routers), the choice of the router ID used in this name is at the
>    discretion of the Issuer.

v2.23.0 | Report a Bug | By Email