IETF Logo Mail Archive

Re: [sidr] Alexey Melnikov's Yes on draft-ietf-sidr-bgpsec-protocol-21: (with COMMENT)

Alexey Melnikov <aamelnikov@fastmail.fm> Wed, 11 January 2017 22:25 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 B4C011295B2; Wed, 11 Jan 2017 14:25:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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=fastmail.fm header.b=h5Qk4nKl; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=Xc6amLoQ
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 jYMIo2GUK7Nz; Wed, 11 Jan 2017 14:25:29 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0217D1295A5; Wed, 11 Jan 2017 14:25:29 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 47EED20B44; Wed, 11 Jan 2017 17:25:28 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Wed, 11 Jan 2017 17:25:28 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=SUVhYeb1192TPOC g3gy/am0iesY=; b=h5Qk4nKlQZGVwGxUo0WBqoYxFBoNlSRdL28Tw0gEfi62zme qqWipcxdyuY5eBMHxqwgCGw+zgcBFdBqafLFl03su+kRl0jV/pslYQ/7wMeDm+C5 4YOpPX/Uoo0vg5OxdxCYDjcbrQCXA3BlsBsLOXJgkQtoAvrbMaOxmwtgdBUc=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=SUVhYeb1192TPOCg3gy/am0iesY=; b=Xc6amLoQb7N0/XpaNXyj GCoyKbmsOGbx3lriWEF82V/4bFZ+NV4EwbowEX7YT+z1UDz9YflCEr/AowhN39YW pBNvxnPJBFXeO8+CM1i8xmKDdWwKNVAsCCw8o+0sBN0bsCatKZ7z9iP5h0FrKCom RnmAsm4wOk0QxGhiGeeBtHo=
X-ME-Sender: <xms:2LB2WEcVEVzOgnBxdEKP1uykUFr6MI9kDgnRPt1z4D95RhdSNr90wQ>
X-Sasl-enc: +KZbR0DaEtGKIvxAwXIGidyeRlx1r+IAbQV8n8Y2TXtb 1484173527
Received: from [10.238.179.8] (unknown [185.69.145.100]) by mail.messagingengine.com (Postfix) with ESMTPA id DD4F82471E; Wed, 11 Jan 2017 17:25:27 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPhone Mail (13G35)
In-Reply-To: <DM2PR09MB04465394949EA3F934F2D5DD84660@DM2PR09MB0446.namprd09.prod.outlook.com>
Date: Wed, 11 Jan 2017 22:34:48 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <A6D95FEC-CDDE-49FA-BAC7-429821A3CDE0@fastmail.fm>
References: <148352385243.12916.15407627777806532255.idtracker@ietfa.amsl.com> <m2vatvkug0.wl-randy@psg.com> <64ABB874-A355-4F91-93D6-6671CB6A354C@sn3rd.com> <E87B771635882B4BA20096B589152EF6440DC8C3@eusaamb107.ericsson.se> <309117C0-FA5E-412A-B19B-F2C86B2DA02B@fastmail.fm> <DM2PR09MB04465394949EA3F934F2D5DD84660@DM2PR09MB0446.namprd09.prod.outlook.com>
To: "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/yauWsAmLEPtRVxPrO1qGVJnWikc>
Cc: "draft-ietf-sidr-bgpsec-protocol@ietf.org" <draft-ietf-sidr-bgpsec-protocol@ietf.org>, "m.waehlisch@fu-berlin.de" <m.waehlisch@fu-berlin.de>, Suresh Krishnan <suresh.krishnan@ericsson.com>, sidr chairs <sidr-chairs@ietf.org>, The IESG <iesg@ietf.org>, sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] Alexey Melnikov's Yes on draft-ietf-sidr-bgpsec-protocol-21: (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: Wed, 11 Jan 2017 22:25:31 -0000

Hi Sriram,

> On 11 Jan 2017, at 20:17, Sriram, Kotikalapudi (Fed) <kotikalapudi.sriram@nist.gov> wrote:
> 
> Hi Alexey,
> 
> My comment in line below.
> 
>> From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm] 
>> Sent: Thursday, January 05, 2017 4:57 AM)
>> 
>>>> On 5 Jan 2017, at 03:19, Suresh Krishnan <suresh.krishnan@ericsson.com> wrote:
>>>> 
>>>> On 01/04/2017 09:38 AM, Sean Turner wrote:
>>>> 
>>>>>> On Jan 4, 2017, at 05:09, Randy Bush <randy@psg.com> wrote:
>>>>>> 
>>>>>> +1 to the comment from Suresh about order. I though that something 
>>>>>> +like
>>>>>> what he proposed will minimize memcopies and possibly use of memory 
>>>>>> why hashing. So I am also curious to know answer to his question.
>>>>> 
>>>>> a vendor engineer actually implementing requested the change to the 
>>>>> current syntax for ease of generating/parsing.
>>>>> 
>>>>> randy
>>>> 
>>>> I believe this is that thread that resulted in the final organization:
>>>> 
>>>> https://mailarchive.ietf.org/arch/msg/sidr/8B_e4CNxQCUKeZ_AUzsdnn2f5M
>>>> U
>>> 
>>> Thanks for the pointer Sean. Very interesting.
>> 
>> Indeed! I wish a few words about design could be added to the draft.
> 
> The design explanation would be a bit long as you can see from 
> Oliver's (implementer's) post.
> There is a BGPsec design discussion document (to be published
> as an independent submission RFC):
> 
> https://tools.ietf.org/html/draft-sriram-bgpsec-design-choices-11  
> 
> I think that would be better place to include this design rationale as well.

Works for me.

v2.23.0 | Report a Bug | By Email