Re: [Idr] I-D Action: draft-ietf-idr-large-community-01.txt

Job Snijders <job@ntt.net> Sat, 15 October 2016 12:46 UTC

Return-Path: <job@ntt.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA2F312963B for <idr@ietfa.amsl.com>; Sat, 15 Oct 2016 05:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.931
X-Spam-Level:
X-Spam-Status: No, score=-4.931 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, SPF_SOFTFAIL=0.665] 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 rGO5N1dyOStC for <idr@ietfa.amsl.com>; Sat, 15 Oct 2016 05:46:07 -0700 (PDT)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F3B81295EB for <idr@ietf.org>; Sat, 15 Oct 2016 05:46:07 -0700 (PDT)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <job@ntt.net>) id 1bvOLi-000DW9-LU (job@us.ntt.net); Sat, 15 Oct 2016 12:46:03 +0000
Date: Sat, 15 Oct 2016 14:45:56 +0200
From: Job Snijders <job@ntt.net>
To: "t.petch" <ietfc@btconnect.com>
Message-ID: <20161015124556.GW57491@Vurt.local>
References: <57F92043.20301@foobar.org> <A9BBA442-361F-444F-9AFC-33FAAF5F6061@gmail.com> <00ff01d22214$a9832440$4001a8c0@gateway.2wire.net> <57FAD3EA.6070800@foobar.org> <020b01d223a1$f0e34a20$4001a8c0@gateway.2wire.net> <20161011095417.GL19434@gir.theapt.org> <1476317462333.82977@dacor.de> <00fb01d2252f$700c2360$4001a8c0@gateway.2wire.net> <370dd06bff7c425db78dc82c5bce8907@XCH-ALN-014.cisco.com> <015001d226da$32df80c0$4001a8c0@gateway.2wire.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <015001d226da$32df80c0$4001a8c0@gateway.2wire.net>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.0 (2016-08-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/m5gh4hUGo69kBvYVxTH-H6gC6Cs>
Cc: idr <idr@ietf.org>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-large-community-01.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Oct 2016 12:46:08 -0000

Hi,

On Sat, Oct 15, 2016 at 12:49:28PM +0100, t.petch wrote:
> I think that Brian well expressed the issue in a post 15 minutes
> before yours.

No. That posting is proposing new radical ideas about propagation
behaviourisms that are not part of this specification.  A specific
design requirement for -large-, stated by member of the working group is
the simple transitive nature of the attribute. Given the very different
nature of what you and Brian propose, I suspect it might warrant its own
draft.

> My concern starts with the protocol rather than the implementation,
> seeing getting the protocol right as the first step, even if it does
> not seem possible at present for a router to enforce the protocol
> rigidly. I see BGP as a whole as somewhat weak on security, on
> authentication and data integrity, and these things only getting fixed
> after a disaster or two.  So I am content to specify a protocol which
> implementations may or may not catch up with at a later date.

I am not content with a protocol for which there are zero
implementations. Without implementations, there is no standardisation in
IDR.

Based on my experience with RFC 1997 - I feel that you may be
misrepresenting the risk surface. 

Kind regards,

Job