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

"Mirja Kuehlewind" <ietf@kuehlewind.net> Mon, 13 June 2016 13:28 UTC

Return-Path: <ietf@kuehlewind.net>
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 BBB5B12B017; Mon, 13 Jun 2016 06:28:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kuehlewind <ietf@kuehlewind.net>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.21.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160613132809.12486.44511.idtracker@ietfa.amsl.com>
Date: Mon, 13 Jun 2016 06:28:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/0rkugUs7JgU7npfIjZ7gi5gMerg>
Cc: idr@ietf.org, shares@ndzh.com, idr-chairs@ietf.org, draft-ietf-idr-ix-bgp-route-server@ietf.org
Subject: [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
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: Mon, 13 Jun 2016 13:28:10 -0000

Mirja Kühlewind 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:
----------------------------------------------------------------------

Quick question: Why is the following statement a SHOULD and not a MUST:
"the route server SHOULD NOT prepend its own AS number to the AS_PATH
   segment nor modify the AS_PATH segment in any other way. "
Is this because the clients might eitherwise not accept the message? 
Maybe add one sentence to explain the SHOULD!