IETF Logo Mail Archive

Re: [Idr] Mirja Kühlewind's No Objection on draft-ietf-idr-ix-bgp-route-server-11: (with COMMENT)

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Fri, 17 June 2016 10:45 UTC

Return-Path: <ietf@kuehlewind.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 E749012D11D for <idr@ietfa.amsl.com>; Fri, 17 Jun 2016 03:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.328
X-Spam-Level:
X-Spam-Status: No, score=-3.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, 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 Go_WYL7tqGOg for <idr@ietfa.amsl.com>; Fri, 17 Jun 2016 03:45:26 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA7CE12D11A for <idr@ietf.org>; Fri, 17 Jun 2016 03:45:25 -0700 (PDT)
Received: (qmail 1134 invoked from network); 17 Jun 2016 12:45:23 +0200
Received: from p5dec287c.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (93.236.40.124) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 17 Jun 2016 12:45:23 +0200
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <m2ziqnk8b1.wl%randy@psg.com>
Date: Fri, 17 Jun 2016 12:45:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CE1FDB6A-53EE-4649-B880-23EA1D7F75D4@kuehlewind.net>
References: <20160613132809.12486.44511.idtracker@ietfa.amsl.com> <575EB839.3050303@foobar.org> <0DE7AB8E-4CFD-44C5-898F-47F48B542599@kuehlewind.net> <575F2704.3050509@foobar.org> <m237ogo5w1.wl%randy@psg.com> <CAL9jLaaCa9aUOw0HUfyrt05GTYL+yGZum1M=3_4r_E0nx4PqJg@mail.gmail.com> <A65A6088-433D-4200-B098-B2FFEB0A45CD@psg.com> <CAL9jLabgF=h9wSg4GoDoJiT76HcKK2DhpJv=ZxLws7LSs8RN3g@mail.gmail.com> <575FD94E.8030606@foobar.org> <m2inxckqr8.wl%randy@psg.com> <575FF3B9.3080501@foobar.org> <m2ziqnk8b1.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/0SdMl9fx-vEviBA4sIwJyjhuZSU>
Cc: idr wg <idr@ietf.org>
Subject: Re: [Idr] Mirja Kühlewind'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
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: Fri, 17 Jun 2016 10:45:28 -0000

Hi all,

sorry for my late reply. Yes, that was not capturing my point. Please provide some reasoning with the SHOULD is not a MUST. What are the cases where you should not follow the SHOULD.

Mirja


> Am 14.06.2016 um 19:08 schrieb Randy Bush <randy@psg.com>:
> 
>> Does the proposed wording work for you?
>> 
>>> While it is technically possible to operate a route server which
>>> prepends its own AS to the AS_PATH, it is not recommended to do so
>>> because creating an undesirably longer AS_PATH may adversely affect
>>> the resulting network topology between the route server clients.
> 
> i suspect that the AD is competent to speak for herself.  but imiho this
> misses her point, why is the SHOULD not a MUST?  this says why it might
> be a MUST.  why allow the loophole?  i admit my example was baroque.
> 
> randy

v2.23.0 | Report a Bug | By Email