[Idr] Joel Jaeggli's No Objection on draft-ietf-idr-ix-bgp-route-server-11: (with COMMENT)
"Joel Jaeggli" <joelja@bogus.com> Tue, 14 June 2016 15:37 UTC
Return-Path: <joelja@bogus.com>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 24D3612D7C8; Tue, 14 Jun 2016 08:37:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Jaeggli <joelja@bogus.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.22.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160614153754.19291.870.idtracker@ietfa.amsl.com>
Date: Tue, 14 Jun 2016 08:37:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/jx7AFvtegW98n9qO-T86YeyE604>
Cc: idr@ietf.org, shares@ndzh.com, idr-chairs@ietf.org, draft-ietf-idr-ix-bgp-route-server@ietf.org
Subject: [Idr] Joel Jaeggli's No Objection on draft-ietf-idr-ix-bgp-route-server-11: (with COMMENT)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 14 Jun 2016 15:37:54 -0000
Joel Jaeggli has entered the following ballot position for draft-ietf-idr-ix-bgp-route-server-11: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-idr-ix-bgp-route-server/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I'm at a bit of a loss to understand why path hiding would be a considered an undesirable property of an MLPE routeserver. IMHO as an operator that peers on MLPE exchanges as well as bilaterally on exchange fabrics and via PNIs. blinding a client of the MLPE which I may have a session already with at the exchange or via PNI is basically mandatory. Likewise without per-asn export policy at exchanges my ability to advertise anycast prefixes via the MLPE is basically noexistant If an IXP operator deploys a route server without implementing a per-client routing policy control system, then path hiding does not occur as all paths are considered equally valid from the point of view of the route server. Does not seem like a particularly desirable outcome. While I'm fine with 2.3 not being normative, it does seem desirable that an MLPE service offer the client control, it greatly increases the sorts of clients that can safely use the service.
- Re: [Idr] Joel Jaeggli's No Objection on draft-ie… Nick Hilliard
- Re: [Idr] Joel Jaeggli's No Objection on draft-ie… Alvaro Retana (aretana)
- Re: [Idr] Joel Jaeggli's No Objection on draft-ie… joel jaeggli
- Re: [Idr] Joel Jaeggli's No Objection on draft-ie… Nick Hilliard
- Re: [Idr] Joel Jaeggli's No Objection on draft-ie… joel jaeggli
- Re: [Idr] Joel Jaeggli's No Objection on draft-ie… Nick Hilliard
- [Idr] Joel Jaeggli's No Objection on draft-ietf-i… Joel Jaeggli