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

Sean Turner <sean@sn3rd.com> Thu, 05 January 2017 00:34 UTC

Return-Path: <sean@sn3rd.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 752E8129477 for <sidr@ietfa.amsl.com>; Wed, 4 Jan 2017 16:34:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 HykRFuxPeMXT for <sidr@ietfa.amsl.com>; Wed, 4 Jan 2017 16:34:53 -0800 (PST)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF62D12947A for <sidr@ietf.org>; Wed, 4 Jan 2017 16:34:52 -0800 (PST)
Received: by mail-qk0-x22a.google.com with SMTP id n21so418184563qka.3 for <sidr@ietf.org>; Wed, 04 Jan 2017 16:34:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jRR1SPIRzQv5JnwlDQ7Io3PaXOPfcMgEalTl33r9a50=; b=C3jnXsZXGHOf9TTP8nELQq21d7AyBAVTeIbRehDsRkPEtEs0dvT9MO1mYQyyYOJFPs ewdqUIUUrIzdib1d9aBDXGrbxsPl2p8hbfQ57QkIo7PLJgF6la5K2AXDmd+E8u8m4LtR 4cFbDPvdYsGCMogppUrDzs1jOS5alVzWVa6hg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jRR1SPIRzQv5JnwlDQ7Io3PaXOPfcMgEalTl33r9a50=; b=YR4W4fYxhzhoRRR0pP/s0EkBQqP681rSF4HGSeBghm47uA9PXslMqjoRdGJY+el/81 JWeR9e377WQBpMIknh68NT5Dsyhe9SCQM0aovTBfXoOOECVOzf276Fi8rKY2S72du4/c Jm9ZvvYeywG2cY4GK0O1O1tVAgwySzr/IQ0edOMMjSPJdiPfTXnxdEFlzBiS1rLDJJYI eoedhXLLj6TfrdwVAJF4RUeXpLVLf5vFSoLSl80v+u2pegb1rpneqJKu96iiUq5fmYQc L5xbwwQwzmzyBQtHVOHblJFxqJmWg+ihMk6U9WzkWVYh4Q0zv4H4LwfWUobMz32c712h /aSw==
X-Gm-Message-State: AIkVDXL0+x7X0ThD8G3xDQrWKCVvHxSUqz1a4KiDLMT642/TfDmCkENnn0ZfnCKrKsABdA==
X-Received: by 10.55.92.195 with SMTP id q186mr37524979qkb.83.1483576491912; Wed, 04 Jan 2017 16:34:51 -0800 (PST)
Received: from [172.16.0.92] (pool-173-73-120-80.washdc.east.verizon.net. [173.73.120.80]) by smtp.gmail.com with ESMTPSA id i41sm47199030qtc.18.2017.01.04.16.34.49 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 04 Jan 2017 16:34:50 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <148353788046.13042.160471261406266.idtracker@ietfa.amsl.com>
Date: Wed, 04 Jan 2017 19:34:48 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F5E3802E-8FEB-4448-884F-CB6178A1FB6E@sn3rd.com>
References: <148353788046.13042.160471261406266.idtracker@ietfa.amsl.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/hJbo2L2fQCaIfaiqa4Ey-W8ECwY>
Cc: 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:34:54 -0000

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> 
> - section 2: I think this is a bit badly written: "The use
> of BGPsec Router Certificates in no way affects RPKI RPs
> that process Manifests and ROAs because the public key
> found in the BGPsec Router Certificate is used only to
> verify the signature on the BGPsec certificate request
> (only CAs process these) and the signature on a BGPsec
> Update Message [ID.sidr-bgpsec-protocol] (only BGPsec
> routers process these)." Do you mean that there's no way
> that an entity can confuse a Manifest, ROA, CSR or BGPsec
> update so there's no issue with which public keys are used
> to verify the signatures on those data structures?

Gahhhh … so that’s a little tortured; it’s a continuation of the whole “these certs don’t really affect the rest of the RPKI".  How about:

BGPsec Router Certificates are used only to verify the signature on the BGPsec certificate request (only CAs process these) and the signature on a BGPsec Update Message [ID.sidr-bgpsec-protocol] (only BGPsec routers process these); BGPsec Router Certificates are not used to process Manifests and ROAs or verify signatures on Certificates or CRLs.

> - section 3: As noted in my comments on the BGPsec
> protocol, it'd be better to call out the SKI here if you
> don't add the direct ref to 6487 to the BGPsec protocol
> draft.

Wait, I thought I wasn’t supposed to duplicate any of the crazy stuff from 6487 :)

spt