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

Randy Bush <randy@psg.com> Wed, 04 January 2017 10:09 UTC

Return-Path: <randy@psg.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 2FAEC128DF6; Wed, 4 Jan 2017 02:09:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.001
X-Spam-Level:
X-Spam-Status: No, score=-10.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-3.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 TMCdkl9iudOd; Wed, 4 Jan 2017 02:09:42 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 3E9CB12711D; Wed, 4 Jan 2017 02:09:42 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cOiVm-0008HN-AN; Wed, 04 Jan 2017 10:09:38 +0000
Date: Wed, 04 Jan 2017 19:09:35 +0900
Message-ID: <m2vatvkug0.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
In-Reply-To: <148352385243.12916.15407627777806532255.idtracker@ietfa.amsl.com>
References: <148352385243.12916.15407627777806532255.idtracker@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/AjEyj7lpK7zQezwAuBhgeQue-1o>
Cc: sidr-chairs@ietf.org, draft-ietf-sidr-bgpsec-protocol@ietf.org, The IESG <iesg@ietf.org>, m.waehlisch@fu-berlin.de, 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, 04 Jan 2017 10:09:43 -0000

> +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