Re: [sidr] Alexey Melnikov's No Objection on draft-ietf-sidr-bgpsec-algs-16: (with COMMENT)

Sean Turner <sean@sn3rd.com> Sat, 10 December 2016 14:42 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 688DF12951E for <sidr@ietfa.amsl.com>; Sat, 10 Dec 2016 06:42:55 -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=unavailable 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 gguIGzg-rAiS for <sidr@ietfa.amsl.com>; Sat, 10 Dec 2016 06:42:53 -0800 (PST)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (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 84EE812951F for <sidr@ietf.org>; Sat, 10 Dec 2016 06:42:53 -0800 (PST)
Received: by mail-qk0-x234.google.com with SMTP id n204so44801427qke.2 for <sidr@ietf.org>; Sat, 10 Dec 2016 06:42:53 -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=7XVaJ+pjRDf0+k+tE9fthXgs/TOnaxlWb2SiVBhBXN8=; b=g5W6jUUyDj+qR7MrJqCuYncGInQ1l9I9lF2PV5lC/wpdAbwHd5H/JKkUe90+ZirOVc aZPI0nt34+LRDzyi3ZORoZVTakyIQpjfdnNkPvfPsK9+WvXKfkvliV9WXcsgjcmYadGt C3r/G4zsprQjVR55u7fXOCY0Mm7mV2MRhR3lY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7XVaJ+pjRDf0+k+tE9fthXgs/TOnaxlWb2SiVBhBXN8=; b=Eol2oLmAqKlLf2tuXDM5xbDOStgHvTwkaMKKNH5i8Sr/502sPiGZtSyJFcACJvUslp EIlr+/3dH9V0xBsu9suxBJSgNpf2lq4lO7kmPokGSr0RcZckr31n5ZwE9hiZb3aT5NgA B2Etedx35VQv1ycpp/sCcvGyoXJNEyBzphw/3z1UBdUi6zaeKHQeJctoiUSMAiBeXkiQ D2m3UyUuB2S3Z0el1sfrED4rUYkKl259M4+83YY3V+D9CKTeSr6CxpgaPlquOGWJP1z4 Ilz5qleUH4IXIDMPe/EofFsMoqRdn8a2p/vHaQMnLrcYqSqcmL/UI7ELFqme4lOH0n+Q tsnQ==
X-Gm-Message-State: AKaTC0266E4Wb5coI4MLNDv74SoBtjGaCdkRKyl1SHFaKm+Xey1yRkS0zoYekgCbESmAEw==
X-Received: by 10.55.16.10 with SMTP id a10mr71876909qkh.66.1481380972601; Sat, 10 Dec 2016 06:42:52 -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 f2sm19472027qtg.22.2016.12.10.06.42.51 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 10 Dec 2016 06:42:52 -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: <BFD3CF9B-0D6E-469A-8B16-5F9986498D94@fastmail.fm>
Date: Sat, 10 Dec 2016 09:42:50 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D923C44-DD00-4C6B-90A0-ABB4AB2ADD4E@sn3rd.com>
References: <148137065859.3698.8955088480248952167.idtracker@ietfa.amsl.com> <0A3548C0-D59D-4232-A6DF-6371395FFFAA@sn3rd.com> <BFD3CF9B-0D6E-469A-8B16-5F9986498D94@fastmail.fm>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/t3yPKnMlsAyIKsF2rpQGst30_PI>
Cc: draft-ietf-sidr-bgpsec-algs@ietf.org, Sandra Murphy <sandy@tislabs.com>, sidr-chairs@ietf.org, The IESG <iesg@ietf.org>, sidr@ietf.org
Subject: Re: [sidr] Alexey Melnikov's No Objection on draft-ietf-sidr-bgpsec-algs-16: (with 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: Sat, 10 Dec 2016 14:42:55 -0000

> On Dec 10, 2016, at 08:56, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:
> 
> 
>> On 10 Dec 2016, at 12:40, Sean Turner <sean@sn3rd.com> wrote:
>> 
>>> On Dec 10, 2016, at 06:50, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:
>>> 
>>> Maybe I missed it, but I don't think the document is clear on why new
>>> algorithms are needed. Is this specified in one of referenced documents?
>> 
>> I think you’re asking why different algorithms are needed to those specified for the rest of the RPKI?  If that’s the case, it’s key/sig size to keep the protocol smaller than if we used RSA/RSA-PSS and that’s covered in RFC 5480.  
> 
> Thank you, Sean. Maybe the document should have a sentence on this.

Ack - maybe in the last para of s1 we put something like this:

BGPsec uses a different algorithm as compared to the rest of the RPKI to minimize the size of the protocol exchanged between routers [RFC5480].

I’m not wed to this wording though so wordsmithing from the WG is welcome.

spt