
From nobody Tue Dec 12 19:10:50 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB4991272E1; Tue, 12 Dec 2017 19:10:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=h3ZX+y3T; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=m+K2fkK5
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 9JB6nnJEJ3d4; Tue, 12 Dec 2017 19:10:42 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0812F127275; Tue, 12 Dec 2017 19:10:39 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 259DE20985; Tue, 12 Dec 2017 22:10:38 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Tue, 12 Dec 2017 22:10:38 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=0+QPf7okf+fvaGpvzuOwReaBHwH8c mfK+c1b5Hm2zEE=; b=h3ZX+y3T/2URI/1PHbGTi5Wb3nyd6q0j2Ko1j/VwIfQcy GmuAl4e/j5EMYYZaES/7C1+d6SiI0JMQrSm7Z/zbFuizOoq5/iCMKoHRM3OvgEmm SnKb4AZn6QGFDwcdrT63vpaLlyqohqY1I8mdnJS6nDrmBZaaoHNiK9jERLukqU3s K9OqYhqSX77JK3Wn/hHE5n6HbGLhFZfZ+V8T9pjuneJgjqvz0eD9Vcs8BqJGRDtm 7WMG2iZFWC3MN/59WhinD0HrwTwzbz3zNPRWtXObQrDfzXhe1zi9juufIQv/GwRi 8YqlXR4pW9xsEocuspVIbF1hd7o+AnqBmG6F807XQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=0+QPf7 okf+fvaGpvzuOwReaBHwH8cmfK+c1b5Hm2zEE=; b=m+K2fkK5oQoBzu9wuxBd4s 2R3Zl6H0ggXNsyHNOusXzbJ8CFYIVMPhaJ0mvWZCTm3XNtnVKa4NDeZAPhAbfYrk aQ9QIUiK9t2FWr4NDCMASkwhSuh1Odokav0cJ+yFNKfhrND2V05gpRuFkf0L0jqU zJaXpZSNl3WzpbpN1cQtFkJqLk1GyijBvuLrRvHBG4EVRNnG/vP0pauotrcKjnSB KC3XXYhOHC4U3YPfFp568vATjLl7m6xv/9B4Mv7Eoi01r/MR7vr4p6xmcNKTlDaK 1TTcSknEh1nSAWioL58PQPUXBg9nzsCDjqihHJq2l77Hp0+ATFi/4rihcg2hBS4Q ==
X-ME-Sender: <xms:LpowWs1sLtveIFVbBx_UekO8PuySMt0v09CiU-Nx1MabXXyEUatwOA>
Received: from alcoop-m-mx19.fios-router.home (pool-108-48-166-97.washdc.fios.verizon.net [108.48.166.97]) by mail.messagingengine.com (Postfix) with ESMTPA id CCE8524009; Tue, 12 Dec 2017 22:10:37 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <150759929173.18515.8831141207586025582@ietfa.amsl.com>
Date: Tue, 12 Dec 2017 22:10:37 -0500
Cc: gen-art <gen-art@ietf.org>, grow@ietf.org, draft-ietf-grow-bgp-gshut.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA9ADE0F-84D9-470F-9A0A-509D51D4EB74@cooperw.in>
References: <150759929173.18515.8831141207586025582@ietfa.amsl.com>
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/CVnWIOqoRoDOqRzvAiL0LKQDZio>
Subject: Re: [GROW] [Gen-art] Genart last call review of draft-ietf-grow-bgp-gshut-11
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Dec 2017 03:10:44 -0000

Matt, thanks for your review. Authors/WG, thanks for addressing Matt=E2=80=
=99s issues. I have entered a No Objection ballot.

Best,
Alissa

> On Oct 9, 2017, at 9:34 PM, Matthew Miller =
<linuxwolf+ietf@outer-planes.net> wrote:
>=20
> Reviewer: Matthew Miller
> Review result: Ready with Issues
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-grow-bgp-gshut-11
> Reviewer: Matthew A. Miller
> Review Date: 2017-10-09
> IETF LC End Date: 2017-10-11
> IESG Telechat date: N/A
>=20
> Summary:
>=20
> This document is ready to be published as an Informational document, =
but
> there is one issue that I think clarification would help.
>=20
> Major issues:
>=20
> NONE
>=20
> Minor issues:
>=20
> In Section 4. "EBGP graceful shutdown procedure", it states that 0 can
> used in all cases except where the AS already has a special meaning =
for
> 0. It seems to me more ought to be said, but I admit I'm not =
well-versed
> on (I) BGP and might be seeing dragons where only windmills are =
present.
>=20
>=20
> Nits/editorial comments:
>=20
> * I suggest using RFC 8174 and its terminology boiler plate to help
>  disambiguate "may" versus "MAY".
>=20
> * A number of acronyms are used throughout without being spelled out =
(e.g.,
>  RR, IBGP, FIB, EBGP, AS), but some (e.g., ASBR) are spelled out.  I =
would
>  find it helpful to be consistent here, preferably by spelling them =
out on
>  first use.
>=20
> * In Section 1. "Introduction", second paragraph, the word "operation"
>  seems to be missing from the first sentence:
>=20
>  """
>  This document discusses operational procedures to be applied in order
>  to reduce or eliminate loss of packets during a maintenance.
>  """
>=20
> * Throughout the Appendices, there are some inconsistent uses of some =
terms,
>  especially when compared to the rest of the document:
>=20
>  - "Local-Pref" versus "LOCAL_PREF"
>  - "nexhop" versus "NEXT_HOP"
>=20
> * In Appendix A. "Alternative techniques with limited applicability", =
the
>  phrase "describe them" ought to be "describes them".
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Dec 13 19:28:00 2017
Return-Path: <aretana.ietf@gmail.com>
X-Original-To: grow@ietf.org
Delivered-To: grow@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 108E512426E; Wed, 13 Dec 2017 19:27:59 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alvaro Retana <aretana.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-grow-bgp-gshut@ietf.org, Christopher Morrow <christopher.morrow@gmail.com>, grow-chairs@ietf.org, grow@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.67.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151322207906.6214.4249731531575998998.idtracker@ietfa.amsl.com>
Date: Wed, 13 Dec 2017 19:27:59 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/xda_RAsLFImKumS3iOhclvZ06dE>
Subject: [GROW] Alvaro Retana's Discuss on draft-ietf-grow-bgp-gshut-12: (with DISCUSS and COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 03:27:59 -0000

Alvaro Retana has entered the following ballot position for
draft-ietf-grow-bgp-gshut-12: Discuss

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-grow-bgp-gshut/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Why is this document not in the Standards Track?  I ask because I think that
the definition of a well-known community (one which has "global significance
and their operations shall be implemented in any community-attribute-aware BGP
speaker" [rfc1997], in other words, everywhere!) should result in a Standards
Track specification, and not in an Informational document.  I couldn't find any
specific justification for the status in the writeups (Shepherd or Ballot), nor
a related discussion in the archive.

To resolve this DISCUSS, I would prefer to see a change in the status, but will
yield to WG consensus (so a pointer to that discussion would be enough).


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Nit:  It would be very nice if the appendices were referenced in the text.



From nobody Wed Dec 13 20:28:26 2017
Return-Path: <ben@nostrum.com>
X-Original-To: grow@ietf.org
Delivered-To: grow@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A0E72126E01; Wed, 13 Dec 2017 20:28:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ben Campbell <ben@nostrum.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-grow-bgp-gshut@ietf.org, Christopher Morrow <christopher.morrow@gmail.com>, grow-chairs@ietf.org, christopher.morrow@gmail.com, grow@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.67.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151322570465.6210.17202569330170241275.idtracker@ietfa.amsl.com>
Date: Wed, 13 Dec 2017 20:28:24 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/vubuOncuh1AHGJCE33-gH1LhEkg>
Subject: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 04:28:25 -0000

Ben Campbell has entered the following ballot position for
draft-ietf-grow-bgp-gshut-12: Yes

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-grow-bgp-gshut/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I'm balloting "yes" because I think it's important to publish this. But, like
Alvaro,  I wonder why this is not standards track, BCP, or just about anything
but informational. So I support his DISCUSS, including his the comments on how
to resolve it.

-1, last paragraph: This references RFC 8174, but does not use the actual 8174
boilerplate. Is there a reason not to do so?



From nobody Thu Dec 14 05:05:58 2017
Return-Path: <ietf@kuehlewind.net>
X-Original-To: grow@ietf.org
Delivered-To: grow@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 46207124205; Thu, 14 Dec 2017 05:05:57 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-grow-bgp-gshut@ietf.org, Christopher Morrow <christopher.morrow@gmail.com>, grow-chairs@ietf.org, christopher.morrow@gmail.com, grow@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.67.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151325675727.6083.15666522007655187267.idtracker@ietfa.amsl.com>
Date: Thu, 14 Dec 2017 05:05:57 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/LIHUuqQBHnLhJ9F0phKbfl0Mhjo>
Subject: [GROW] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-grow-bgp-gshut-12=3A_=28with_COMMENT=29?=
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 13:05:57 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-grow-bgp-gshut-12: 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-grow-bgp-gshut/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I also believe this should be standards track. Or is there any good reason why
it should not be standards track similar as other docs that define well known
communities?



From nobody Thu Dec 14 06:42:36 2017
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43AB5126C89; Thu, 14 Dec 2017 06:42:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level: 
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 udRANtrk6eGZ; Thu, 14 Dec 2017 06:42:33 -0800 (PST)
Received: from orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E536126B6E; Thu, 14 Dec 2017 06:42:30 -0800 (PST)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id 892B660748; Thu, 14 Dec 2017 15:42:28 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.27]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 5312B180083; Thu, 14 Dec 2017 15:42:28 +0100 (CET)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM7C.corporate.adroot.infra.ftgroup ([fe80::8007:17b:c3b4:d68b%19]) with mapi id 14.03.0361.001; Thu, 14 Dec 2017 15:42:27 +0100
From: <bruno.decraene@orange.com>
To: Ben Campbell <ben@nostrum.com>
CC: "draft-ietf-grow-bgp-gshut@ietf.org" <draft-ietf-grow-bgp-gshut@ietf.org>,  Christopher Morrow <christopher.morrow@gmail.com>, "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "christopher.morrow@gmail.com" <christopher.morrow@gmail.com>, "grow@ietf.org" <grow@ietf.org>, The IESG <iesg@ietf.org>
Thread-Topic: Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
Thread-Index: AQHTdJP90cSHHsziR0WKcqR14+JgtqNC5Xiw
Date: Thu, 14 Dec 2017 14:42:27 +0000
Message-ID: <15461_1513262548_5A328DD4_15461_64_1_53C29892C857584299CBF5D05346208A47920D36@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <151322570465.6210.17202569330170241275.idtracker@ietfa.amsl.com>
In-Reply-To: <151322570465.6210.17202569330170241275.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/Tku7Ob6EqNUhYSWurPiNfXHub3E>
Subject: Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 14:42:35 -0000

QmVuLA0KDQpUaGFua3MgZm9yIHlvdXIgcmV2aWV3IGFuZCBjb21tZW50cy4NCk1vcmUgaW5saW5l
LiBbQnJ1bm9dDQoNCj4gRnJvbTogQmVuIENhbXBiZWxsIFttYWlsdG86YmVuQG5vc3RydW0uY29t
XQ0KPiANCiA+IEJlbiBDYW1wYmVsbCBoYXMgZW50ZXJlZCB0aGUgZm9sbG93aW5nIGJhbGxvdCBw
b3NpdGlvbiBmb3INCiA+IGRyYWZ0LWlldGYtZ3Jvdy1iZ3AtZ3NodXQtMTI6IFllcw0KID4gDQog
PiBXaGVuIHJlc3BvbmRpbmcsIHBsZWFzZSBrZWVwIHRoZSBzdWJqZWN0IGxpbmUgaW50YWN0IGFu
ZCByZXBseSB0byBhbGwNCiA+IGVtYWlsIGFkZHJlc3NlcyBpbmNsdWRlZCBpbiB0aGUgVG8gYW5k
IENDIGxpbmVzLiAoRmVlbCBmcmVlIHRvIGN1dCB0aGlzDQogPiBpbnRyb2R1Y3RvcnkgcGFyYWdy
YXBoLCBob3dldmVyLikNCiA+IA0KID4gDQogPiBQbGVhc2UgcmVmZXIgdG8gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvaWVzZy9zdGF0ZW1lbnQvZGlzY3Vzcy1jcml0ZXJpYS5odG1sDQogPiBmb3IgbW9y
ZSBpbmZvcm1hdGlvbiBhYm91dCBJRVNHIERJU0NVU1MgYW5kIENPTU1FTlQgcG9zaXRpb25zLg0K
ID4gDQogPiANCiA+IFRoZSBkb2N1bWVudCwgYWxvbmcgd2l0aCBvdGhlciBiYWxsb3QgcG9zaXRp
b25zLCBjYW4gYmUgZm91bmQgaGVyZToNCiA+IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcv
ZG9jL2RyYWZ0LWlldGYtZ3Jvdy1iZ3AtZ3NodXQvDQogPiANCiA+IA0KID4gDQogPiAtLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tDQogPiBDT01NRU5UOg0KID4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KID4gDQogPiBJJ20gYmFsbG90
aW5nICJ5ZXMiIGJlY2F1c2UgSSB0aGluayBpdCdzIGltcG9ydGFudCB0byBwdWJsaXNoIHRoaXMu
IEJ1dCwgbGlrZQ0KID4gQWx2YXJvLCAgSSB3b25kZXIgd2h5IHRoaXMgaXMgbm90IHN0YW5kYXJk
cyB0cmFjaywgQkNQLCBvciBqdXN0IGFib3V0IGFueXRoaW5nDQogPiBidXQgaW5mb3JtYXRpb25h
bC4gU28gSSBzdXBwb3J0IGhpcyBESVNDVVNTLCBpbmNsdWRpbmcgaGlzIHRoZSBjb21tZW50cyBv
biBob3cNCiA+IHRvIHJlc29sdmUgaXQuDQogDQpbQnJ1bm9dIFdlbGwgbm90ZWQ6IHdlIG5vdyBo
YXZlIDMgQUQgYXNraW5nIGZvciBTVEQgdHJhY2suDQpJZiB5b3UgZG9uJ3QgbWluZCwgdG8gYXZv
aWQgZHVwbGljYXRpb24sIEknbGwgZm9sbG93IHVwIG9uIEFsdmFybydzIGVtYWlsLiAoaW4gc2hv
cnQsIFNURCB0cmFjayBpcyBvayBmb3IgbWUpDQogDQogPiAtMSwgbGFzdCBwYXJhZ3JhcGg6IFRo
aXMgcmVmZXJlbmNlcyBSRkMgODE3NCwgYnV0IGRvZXMgbm90IHVzZSB0aGUgYWN0dWFsIDgxNzQN
CiA+IGJvaWxlcnBsYXRlLiBJcyB0aGVyZSBhIHJlYXNvbiBub3QgdG8gZG8gc28/DQogDQpbQnJ1
bm9dIE15IG1pc3Rha2U6IEkgaGFkIGEgY29tbWVudCB0byByZWZlcmVuY2UgUkZDIDgxNzQgcmF0
aGVyIHRoYW4gUkZDIDIxMTkuIEkgd2FzIG5vdCBhd2FyZSB0aGF0IHRoaXMgYWxzbyBpbXBsaWVk
IGNoYW5naW5nIHRoZSB0ZXh0Lg0KTXkgdW5kZXJzdGFuZGluZyBpcyB0aGUgZm9sbG93aW5nOg0K
T0xEOg0KCSA8dD5UaGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1QgTk9UIiwgIlJFUVVJUkVEIiwg
IlNIQUxMIiwNCgkgIlNIQUxMIE5PVCIsICJTSE9VTEQiLCAiU0hPVUxEIE5PVCIsICJSRUNPTU1F
TkRFRCIsICJNQVkiLA0KCSBhbmQgIk9QVElPTkFMIiBpbiB0aGlzIGRvY3VtZW50IGFyZSB0byBi
ZSBpbnRlcnByZXRlZCBhcw0KCSBkZXNjcmliZWQgaW4gUkZDIDgxNzQgPHhyZWYgdGFyZ2V0PSJS
RkM4MTc0Ii8+LjwvdD4NCg0KDQpORVcNCgk8dD5UaGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1Qg
Tk9UIiwgIlJFUVVJUkVEIiwgIlNIQUxMIiwgIlNIQUxMDQogICAgICBOT1QiLCAiU0hPVUxEIiwg
IlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTk9UIFJFQ09NTUVOREVEIiwNCiAgICAgICJN
QVkiLCBhbmQgIk9QVElPTkFMIiBpbiB0aGlzIGRvY3VtZW50IGFyZSB0byBiZSBpbnRlcnByZXRl
ZCBhcw0KICAgICAgZGVzY3JpYmVkIGluIFtCQ1AxNF0gPHhyZWYgdGFyZ2V0PSJSRkMyMTE5Ii8+
IDx4cmVmIHRhcmdldD0iUkZDODE3NCIvPiB3aGVuLCBhbmQgb25seSB3aGVuLCB0aGV5DQogICAg
ICBhcHBlYXIgaW4gYWxsIGNhcGl0YWxzLCBhcyBzaG93biBoZXJlLjwvdD4NCiANCg0KDQpUaGF0
IGJlaW5nIHNhaWQsIHRoZSBpcm9ueSBpcyB0aGF0IFJGQyA4MTc0IGRvZXMgbm90IHVzZSBhbiB1
cHBlciBjYXNlICJzaG91bGQiOg0KIkF1dGhvcnMgd2hvIGZvbGxvdyB0aGVzZSBndWlkZWxpbmVz
IHNob3VsZCBpbmNvcnBvcmF0ZSB0aGlzIHBocmFzZSBuZWFyIHRoZSBiZWdpbm5pbmcgb2YgdGhl
aXIgZG9jdW1lbnQ6Ig0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzgxNzQjc2VjdGlv
bi0yDQoNCi0tQnJ1bm8NCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fCgpDZSBtZXNzYWdlIGV0IHNlcyBwaWVjZXMgam9pbnRl
cyBwZXV2ZW50IGNvbnRlbmlyIGRlcyBpbmZvcm1hdGlvbnMgY29uZmlkZW50aWVsbGVzIG91IHBy
aXZpbGVnaWVlcyBldCBuZSBkb2l2ZW50IGRvbmMKcGFzIGV0cmUgZGlmZnVzZXMsIGV4cGxvaXRl
cyBvdSBjb3BpZXMgc2FucyBhdXRvcmlzYXRpb24uIFNpIHZvdXMgYXZleiByZWN1IGNlIG1lc3Nh
Z2UgcGFyIGVycmV1ciwgdmV1aWxsZXogbGUgc2lnbmFsZXIKYSBsJ2V4cGVkaXRldXIgZXQgbGUg
ZGV0cnVpcmUgYWluc2kgcXVlIGxlcyBwaWVjZXMgam9pbnRlcy4gTGVzIG1lc3NhZ2VzIGVsZWN0
cm9uaXF1ZXMgZXRhbnQgc3VzY2VwdGlibGVzIGQnYWx0ZXJhdGlvbiwKT3JhbmdlIGRlY2xpbmUg
dG91dGUgcmVzcG9uc2FiaWxpdGUgc2kgY2UgbWVzc2FnZSBhIGV0ZSBhbHRlcmUsIGRlZm9ybWUg
b3UgZmFsc2lmaWUuIE1lcmNpLgoKVGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVudHMgbWF5
IGNvbnRhaW4gY29uZmlkZW50aWFsIG9yIHByaXZpbGVnZWQgaW5mb3JtYXRpb24gdGhhdCBtYXkg
YmUgcHJvdGVjdGVkIGJ5IGxhdzsKdGhleSBzaG91bGQgbm90IGJlIGRpc3RyaWJ1dGVkLCB1c2Vk
IG9yIGNvcGllZCB3aXRob3V0IGF1dGhvcmlzYXRpb24uCklmIHlvdSBoYXZlIHJlY2VpdmVkIHRo
aXMgZW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBhbmQgZGVsZXRlIHRo
aXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzLgpBcyBlbWFpbHMgbWF5IGJlIGFsdGVyZWQs
IE9yYW5nZSBpcyBub3QgbGlhYmxlIGZvciBtZXNzYWdlcyB0aGF0IGhhdmUgYmVlbiBtb2RpZmll
ZCwgY2hhbmdlZCBvciBmYWxzaWZpZWQuClRoYW5rIHlvdS4KCg==


From nobody Thu Dec 14 06:55:39 2017
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 845751270A7; Thu, 14 Dec 2017 06:55:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.618
X-Spam-Level: 
X-Spam-Status: No, score=-1.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 4RfLHIkdgNNW; Thu, 14 Dec 2017 06:55:37 -0800 (PST)
Received: from orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4B8D126D3F; Thu, 14 Dec 2017 06:55:36 -0800 (PST)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) by opfedar26.francetelecom.fr (ESMTP service) with ESMTP id 812BA1C0845; Thu, 14 Dec 2017 15:55:35 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.18]) by opfedar00.francetelecom.fr (ESMTP service) with ESMTP id 4037E180063; Thu, 14 Dec 2017 15:55:35 +0100 (CET)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM34.corporate.adroot.infra.ftgroup ([fe80::cba:56d0:a732:ef5a%19]) with mapi id 14.03.0361.001; Thu, 14 Dec 2017 15:55:34 +0100
From: <bruno.decraene@orange.com>
To: Alvaro Retana <aretana.ietf@gmail.com>, Warren Kumari <warren@kumari.net>,  Ben Campbell <ben@nostrum.com>
CC: "draft-ietf-grow-bgp-gshut@ietf.org" <draft-ietf-grow-bgp-gshut@ietf.org>,  Christopher Morrow <christopher.morrow@gmail.com>, "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "grow@ietf.org" <grow@ietf.org>, The IESG <iesg@ietf.org>
Thread-Topic: Alvaro Retana's Discuss on draft-ietf-grow-bgp-gshut-12: (with DISCUSS and COMMENT)
Thread-Index: AQHTdIuLjHLjmVZRaUOvZEvyU78JsqNC6pTA
Date: Thu, 14 Dec 2017 14:55:34 +0000
Message-ID: <4697_1513263335_5A3290E7_4697_326_1_53C29892C857584299CBF5D05346208A47920DE6@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <151322207906.6214.4249731531575998998.idtracker@ietfa.amsl.com>
In-Reply-To: <151322207906.6214.4249731531575998998.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/PiGlw49LsbC7Jvw0aQxk0Gfr0UU>
Subject: Re: [GROW] Alvaro Retana's Discuss on draft-ietf-grow-bgp-gshut-12: (with DISCUSS and COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 14:55:38 -0000

WytCZW4gQ2FtcGJlbGwgK1dhcnJlbiBLdW1hcmldICAoRXhwbGljaXRseSBhZGRpbmcgQmVuIGFu
ZCBXYXJyZW4gd2hvIGV4cHJlc3NlZCB0aGUgc2FtZSBjb21tZW50KQ0KDQpIaSBBbHZhcm8sDQoN
ClRoYW5rcyBmb3IgeW91ciByZXZpZXcgYW5kIGNvbW1lbnRzLg0KTW9yZSBpbmxpbmUgW0JydW5v
XQ0KDQo+IEZyb206IEFsdmFybyBSZXRhbmEgW21haWx0bzphcmV0YW5hLmlldGZAZ21haWwuY29t
XQ0KID4gU2VudDogVGh1cnNkYXksIERlY2VtYmVyIDE0LCAyMDE3IDQ6MjggQU0NCj4gDQogPiBB
bHZhcm8gUmV0YW5hIGhhcyBlbnRlcmVkIHRoZSBmb2xsb3dpbmcgYmFsbG90IHBvc2l0aW9uIGZv
cg0KID4gZHJhZnQtaWV0Zi1ncm93LWJncC1nc2h1dC0xMjogRGlzY3Vzcw0KID4gDQogPiBXaGVu
IHJlc3BvbmRpbmcsIHBsZWFzZSBrZWVwIHRoZSBzdWJqZWN0IGxpbmUgaW50YWN0IGFuZCByZXBs
eSB0byBhbGwNCiA+IGVtYWlsIGFkZHJlc3NlcyBpbmNsdWRlZCBpbiB0aGUgVG8gYW5kIENDIGxp
bmVzLiAoRmVlbCBmcmVlIHRvIGN1dCB0aGlzDQogPiBpbnRyb2R1Y3RvcnkgcGFyYWdyYXBoLCBo
b3dldmVyLikNCiA+IA0KID4gDQogPiBQbGVhc2UgcmVmZXIgdG8gaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvaWVzZy9zdGF0ZW1lbnQvZGlzY3Vzcy1jcml0ZXJpYS5odG1sDQogPiBmb3IgbW9yZSBpbmZv
cm1hdGlvbiBhYm91dCBJRVNHIERJU0NVU1MgYW5kIENPTU1FTlQgcG9zaXRpb25zLg0KID4gDQog
PiANCiA+IFRoZSBkb2N1bWVudCwgYWxvbmcgd2l0aCBvdGhlciBiYWxsb3QgcG9zaXRpb25zLCBj
YW4gYmUgZm91bmQgaGVyZToNCiA+IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2Ry
YWZ0LWlldGYtZ3Jvdy1iZ3AtZ3NodXQvDQogPiANCiA+IA0KID4gDQogPiAtLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
DQogPiBESVNDVVNTOg0KID4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KID4gDQogPiBXaHkgaXMgdGhpcyBkb2N1
bWVudCBub3QgaW4gdGhlIFN0YW5kYXJkcyBUcmFjaz8gIEkgYXNrIGJlY2F1c2UgSSB0aGluayB0
aGF0DQogPiB0aGUgZGVmaW5pdGlvbiBvZiBhIHdlbGwta25vd24gY29tbXVuaXR5IChvbmUgd2hp
Y2ggaGFzICJnbG9iYWwgc2lnbmlmaWNhbmNlDQogPiBhbmQgdGhlaXIgb3BlcmF0aW9ucyBzaGFs
bCBiZSBpbXBsZW1lbnRlZCBpbiBhbnkgY29tbXVuaXR5LWF0dHJpYnV0ZS1hd2FyZSBCR1ANCiA+
IHNwZWFrZXIiIFtyZmMxOTk3XSwgaW4gb3RoZXIgd29yZHMsIGV2ZXJ5d2hlcmUhKSBzaG91bGQg
cmVzdWx0IGluIGEgU3RhbmRhcmRzDQogPiBUcmFjayBzcGVjaWZpY2F0aW9uLCBhbmQgbm90IGlu
IGFuIEluZm9ybWF0aW9uYWwgZG9jdW1lbnQuICBJIGNvdWxkbid0IGZpbmQgYW55DQogPiBzcGVj
aWZpYyBqdXN0aWZpY2F0aW9uIGZvciB0aGUgc3RhdHVzIGluIHRoZSB3cml0ZXVwcyAoU2hlcGhl
cmQgb3IgQmFsbG90KSwgbm9yDQogPiBhIHJlbGF0ZWQgZGlzY3Vzc2lvbiBpbiB0aGUgYXJjaGl2
ZS4NCg0KW0JydW5vXQ0KU2hvcnQgdmVyc2lvbjogdGhlcmUgaXMgbm8gc3BlY2lmaWMgcmVhc29u
IG5vdCB0byB1c2UgU3RhbmRhcmRzIFRyYWNrLiBBdXRob3JzIGFyZSBmaW5lIHRvIGNoYW5nZSB0
byBTdGFuZGFyZHMgVHJhY2ssIGVzcGVjaWFsbHkgYWZ0ZXIgMyBBRCByZXZpZXdzIGFza2luZyBm
b3IgaXQuIEZvbGxvd2luZyBhIGRpc2N1c3Npb24gd2l0aCBXYXJyZW4sIEknbGwgd2FpdCBmb3Ig
dGhlIElFU0cgdGVsZWNoYXQgYmVmb3JlIHVwbG9hZGluZyB0aGUgbmV3IHZlcnNpb24uDQoNCkxv
bmcgdmVyc2lvbjoNCkkgdGhpbmsgdGhpcyBoYWQgYmVlbiBkaXNjdXNzZWQgb24gdGhlIG1haWxp
bmcgbGlzdCwgYnV0IEkgY2FuJ3QgZmluZCB0aGUgdGhyZWFkLiBBRkFJUiAob3IgZHJlYW10KSBv
bmUgV0cgcGFydGljaXBhbnQgc2FpZCB0aGF0IEluZm9ybWF0aW9uYWwgd2FzIGVub3VnaCBhbmQg
bm9ib2R5IGFza2VkIGZvciBTdGFuZGFyZCBUcmFja3MuDQpOb3RlIHRoYXQgZnJvbSBhIHRlY2hu
aWNhbCBzdGFuZHBvaW50LCB0aGlzIGNvbW11bml0eSBtYXkgYmUgZGVwbG95ZWQgaW5jcmVtZW50
YWxseSwgb24gYSBwZXIgQVNCUiBvciBldmVuIEVCR1Agc2Vzc2lvbiBiYXNpcy4gU3RyaWN0bHkg
c3BlYWtpbmcsIHRoZXJlIGlzIG5vIHJlcXVpcmVtZW50IHRoYXQgYWxsIGltcGxlbWVudGF0aW9u
cyAoaW4gdGhlIEFTIGFuZCBuZWlnaGJvcmluZyBBU2VzKSByZWNvZ25pemUgdGhpcyBjb21tdW5p
dHkuDQpIb3dldmVyLCB3ZSBkbyB3YW50IHRvIGFzc29jaWF0ZSBhIHdlbGwtZGVmaW5lZCBiZWhh
dmlvciB0byB0aGlzIElBTkEgcmVzZXJ2ZWQgY29tbXVuaXR5LCBzbyBTdGFuZGFyZCBUcmFja3Mg
aXMgZmluZSB3aXRoIG1lLg0KDQpCZXN0IHJlZ2FyZHMsDQotLUJydW5vDQoNCg0KIA0KID4gVG8g
cmVzb2x2ZSB0aGlzIERJU0NVU1MsIEkgd291bGQgcHJlZmVyIHRvIHNlZSBhIGNoYW5nZSBpbiB0
aGUgc3RhdHVzLCBidXQgd2lsbA0KID4geWllbGQgdG8gV0cgY29uc2Vuc3VzIChzbyBhIHBvaW50
ZXIgdG8gdGhhdCBkaXNjdXNzaW9uIHdvdWxkIGJlIGVub3VnaCkuDQogPiANCiA+IA0KID4gLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KID4gQ09NTUVOVDoNCiA+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCiA+IA0KID4gTml0OiAg
SXQgd291bGQgYmUgdmVyeSBuaWNlIGlmIHRoZSBhcHBlbmRpY2VzIHdlcmUgcmVmZXJlbmNlZCBp
biB0aGUgdGV4dC4NCiA+IA0KDQoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXwoKQ2UgbWVzc2FnZSBldCBzZXMgcGllY2VzIGpv
aW50ZXMgcGV1dmVudCBjb250ZW5pciBkZXMgaW5mb3JtYXRpb25zIGNvbmZpZGVudGllbGxlcyBv
dSBwcml2aWxlZ2llZXMgZXQgbmUgZG9pdmVudCBkb25jCnBhcyBldHJlIGRpZmZ1c2VzLCBleHBs
b2l0ZXMgb3UgY29waWVzIHNhbnMgYXV0b3Jpc2F0aW9uLiBTaSB2b3VzIGF2ZXogcmVjdSBjZSBt
ZXNzYWdlIHBhciBlcnJldXIsIHZldWlsbGV6IGxlIHNpZ25hbGVyCmEgbCdleHBlZGl0ZXVyIGV0
IGxlIGRldHJ1aXJlIGFpbnNpIHF1ZSBsZXMgcGllY2VzIGpvaW50ZXMuIExlcyBtZXNzYWdlcyBl
bGVjdHJvbmlxdWVzIGV0YW50IHN1c2NlcHRpYmxlcyBkJ2FsdGVyYXRpb24sCk9yYW5nZSBkZWNs
aW5lIHRvdXRlIHJlc3BvbnNhYmlsaXRlIHNpIGNlIG1lc3NhZ2UgYSBldGUgYWx0ZXJlLCBkZWZv
cm1lIG91IGZhbHNpZmllLiBNZXJjaS4KClRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRz
IG1heSBjb250YWluIGNvbmZpZGVudGlhbCBvciBwcml2aWxlZ2VkIGluZm9ybWF0aW9uIHRoYXQg
bWF5IGJlIHByb3RlY3RlZCBieSBsYXc7CnRoZXkgc2hvdWxkIG5vdCBiZSBkaXN0cmlidXRlZCwg
dXNlZCBvciBjb3BpZWQgd2l0aG91dCBhdXRob3Jpc2F0aW9uLgpJZiB5b3UgaGF2ZSByZWNlaXZl
ZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgYW5kIGRlbGV0
ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cy4KQXMgZW1haWxzIG1heSBiZSBhbHRl
cmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhhdCBoYXZlIGJlZW4gbW9k
aWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVkLgpUaGFuayB5b3UuCgo=


From nobody Thu Dec 14 08:48:37 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: grow@ietf.org
Delivered-To: grow@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C04F128B8E; Thu, 14 Dec 2017 08:48:35 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: grow@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.67.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151327011539.28731.10748025497851535620@ietfa.amsl.com>
Date: Thu, 14 Dec 2017 08:48:35 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/YXQNuluX5s69dyFwzoOLWMzepm0>
Subject: [GROW] I-D Action: draft-ietf-grow-bgp-gshut-13.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 16:48:35 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Global Routing Operations WG of the IETF.

        Title           : Graceful BGP session shutdown
        Authors         : Pierre Francois
                          Bruno Decraene
                          Cristel Pelsser
                          Keyur Patel
                          Clarence Filsfils
	Filename        : draft-ietf-grow-bgp-gshut-13.txt
	Pages           : 11
	Date            : 2017-12-14

Abstract:
   This draft standardizes a new well-known BGP community
   GRACEFUL_SHUTDOWN to signal the graceful shutdown of paths.  This
   draft also describes operational procedures which use this community
   to reduce the amount of traffic lost when BGP peering sessions are
   about to be shut down deliberately, e.g. for planned maintenance.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-gshut/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-13
https://datatracker.ietf.org/doc/html/draft-ietf-grow-bgp-gshut-13

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-grow-bgp-gshut-13


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Dec 14 08:51:11 2017
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D00EF1273B1; Thu, 14 Dec 2017 08:51:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.618
X-Spam-Level: 
X-Spam-Status: No, score=-1.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 psrVSgU37H-U; Thu, 14 Dec 2017 08:51:03 -0800 (PST)
Received: from orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BC9D124234; Thu, 14 Dec 2017 08:51:03 -0800 (PST)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id 2D08A100658; Thu, 14 Dec 2017 17:51:02 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.41]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id DB3F480070; Thu, 14 Dec 2017 17:51:01 +0100 (CET)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM31.corporate.adroot.infra.ftgroup ([fe80::2cc9:4bac:7b7d:229d%19]) with mapi id 14.03.0361.001; Thu, 14 Dec 2017 17:51:01 +0100
From: <bruno.decraene@orange.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
CC: "draft-ietf-grow-bgp-gshut@ietf.org" <draft-ietf-grow-bgp-gshut@ietf.org>,  Christopher Morrow <christopher.morrow@gmail.com>, "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "grow@ietf.org" <grow@ietf.org>, The IESG <iesg@ietf.org>
Thread-Topic: Alvaro Retana's Discuss on draft-ietf-grow-bgp-gshut-12: (with DISCUSS and COMMENT)
Thread-Index: AQHTdIuLjHLjmVZRaUOvZEvyU78JsqNC6pTAgAAGNKA=
Date: Thu, 14 Dec 2017 16:51:01 +0000
Message-ID: <10782_1513270261_5A32ABF5_10782_364_1_53C29892C857584299CBF5D05346208A47921213@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <151322207906.6214.4249731531575998998.idtracker@ietfa.amsl.com> <4697_1513263335_5A3290E7_4697_326_1_53C29892C857584299CBF5D05346208A47920DE6@OPEXCLILM21.corporate.adroot.infra.ftgroup>
In-Reply-To: <4697_1513263335_5A3290E7_4697_326_1_53C29892C857584299CBF5D05346208A47920DE6@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/d_o2Sdv6qfjsYdh2f2PtzMte508>
Subject: Re: [GROW] Alvaro Retana's Discuss on draft-ietf-grow-bgp-gshut-12: (with DISCUSS and COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 16:51:05 -0000

IEhpIEFsdmFybywNCiANCiBUaGFua3MgZm9yIHlvdXIgcmV2aWV3IGFuZCBjb21tZW50cy4NCiBN
b3JlIGlubGluZSBbQnJ1bm8yXQ0KDQogPiBGcm9tOiBicnVuby5kZWNyYWVuZUBvcmFuZ2UuY29t
IFttYWlsdG86YnJ1bm8uZGVjcmFlbmVAb3JhbmdlLmNvbV0NCiA+IFNlbnQ6IFRodXJzZGF5LCBE
ZWNlbWJlciAxNCwgMjAxNyAzOjU2IFBNDQo+IA0KID4gWytCZW4gQ2FtcGJlbGwgK1dhcnJlbiBL
dW1hcmldICAoRXhwbGljaXRseSBhZGRpbmcgQmVuIGFuZCBXYXJyZW4gd2hvIGV4cHJlc3NlZCB0
aGUgc2FtZQ0KID4gY29tbWVudCkNCiA+IA0KID4gSGkgQWx2YXJvLA0KID4gDQogPiBUaGFua3Mg
Zm9yIHlvdXIgcmV2aWV3IGFuZCBjb21tZW50cy4NCiA+IE1vcmUgaW5saW5lIFtCcnVub10NCiA+
IA0KID4gPiBGcm9tOiBBbHZhcm8gUmV0YW5hIFttYWlsdG86YXJldGFuYS5pZXRmQGdtYWlsLmNv
bV0NCiA+ICA+IFNlbnQ6IFRodXJzZGF5LCBEZWNlbWJlciAxNCwgMjAxNyA0OjI4IEFNDQogPiA+
DQogPiAgPiBBbHZhcm8gUmV0YW5hIGhhcyBlbnRlcmVkIHRoZSBmb2xsb3dpbmcgYmFsbG90IHBv
c2l0aW9uIGZvcg0KID4gID4gZHJhZnQtaWV0Zi1ncm93LWJncC1nc2h1dC0xMjogRGlzY3Vzcw0K
ID4gID4NCiA+ICA+IFdoZW4gcmVzcG9uZGluZywgcGxlYXNlIGtlZXAgdGhlIHN1YmplY3QgbGlu
ZSBpbnRhY3QgYW5kIHJlcGx5IHRvIGFsbA0KID4gID4gZW1haWwgYWRkcmVzc2VzIGluY2x1ZGVk
IGluIHRoZSBUbyBhbmQgQ0MgbGluZXMuIChGZWVsIGZyZWUgdG8gY3V0IHRoaXMNCiA+ICA+IGlu
dHJvZHVjdG9yeSBwYXJhZ3JhcGgsIGhvd2V2ZXIuKQ0KID4gID4NCiA+ICA+DQogPiAgPiBQbGVh
c2UgcmVmZXIgdG8gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvaWVzZy9zdGF0ZW1lbnQvZGlzY3Vzcy1j
cml0ZXJpYS5odG1sDQogPiAgPiBmb3IgbW9yZSBpbmZvcm1hdGlvbiBhYm91dCBJRVNHIERJU0NV
U1MgYW5kIENPTU1FTlQgcG9zaXRpb25zLg0KID4gID4NCiA+ICA+DQogPiAgPiBUaGUgZG9jdW1l
bnQsIGFsb25nIHdpdGggb3RoZXIgYmFsbG90IHBvc2l0aW9ucywgY2FuIGJlIGZvdW5kIGhlcmU6
DQogPiAgPiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLWdyb3ct
YmdwLWdzaHV0Lw0KID4gID4NCiA+ICA+DQoNClsuLi5dDQoNCiA+ICA+DQogPiAgPiAtLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tDQogPiAgPiBDT01NRU5UOg0KID4gID4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KID4gID4NCiA+ICA+
IE5pdDogIEl0IHdvdWxkIGJlIHZlcnkgbmljZSBpZiB0aGUgYXBwZW5kaWNlcyB3ZXJlIHJlZmVy
ZW5jZWQgaW4gdGhlIHRleHQuDQogDQpbQnJ1bm8yXSBHb29kIGlkZWEuIFRoYW5rcy4NCkRvbmUg
aW4gLTEzIHRoYXQgSSBoYXZlIGp1c3QgdXBsb2FkZWQuIGh0dHBzOi8vd3d3LmlldGYub3JnL3Jm
Y2RpZmY/dXJsMj1kcmFmdC1pZXRmLWdyb3ctYmdwLWdzaHV0LTEzDQoNClJlZ2FyZHMsDQotLUJy
dW5vDQoNCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fCgpDZSBtZXNzYWdlIGV0IHNlcyBwaWVjZXMgam9pbnRlcyBwZXV2ZW50
IGNvbnRlbmlyIGRlcyBpbmZvcm1hdGlvbnMgY29uZmlkZW50aWVsbGVzIG91IHByaXZpbGVnaWVl
cyBldCBuZSBkb2l2ZW50IGRvbmMKcGFzIGV0cmUgZGlmZnVzZXMsIGV4cGxvaXRlcyBvdSBjb3Bp
ZXMgc2FucyBhdXRvcmlzYXRpb24uIFNpIHZvdXMgYXZleiByZWN1IGNlIG1lc3NhZ2UgcGFyIGVy
cmV1ciwgdmV1aWxsZXogbGUgc2lnbmFsZXIKYSBsJ2V4cGVkaXRldXIgZXQgbGUgZGV0cnVpcmUg
YWluc2kgcXVlIGxlcyBwaWVjZXMgam9pbnRlcy4gTGVzIG1lc3NhZ2VzIGVsZWN0cm9uaXF1ZXMg
ZXRhbnQgc3VzY2VwdGlibGVzIGQnYWx0ZXJhdGlvbiwKT3JhbmdlIGRlY2xpbmUgdG91dGUgcmVz
cG9uc2FiaWxpdGUgc2kgY2UgbWVzc2FnZSBhIGV0ZSBhbHRlcmUsIGRlZm9ybWUgb3UgZmFsc2lm
aWUuIE1lcmNpLgoKVGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVudHMgbWF5IGNvbnRhaW4g
Y29uZmlkZW50aWFsIG9yIHByaXZpbGVnZWQgaW5mb3JtYXRpb24gdGhhdCBtYXkgYmUgcHJvdGVj
dGVkIGJ5IGxhdzsKdGhleSBzaG91bGQgbm90IGJlIGRpc3RyaWJ1dGVkLCB1c2VkIG9yIGNvcGll
ZCB3aXRob3V0IGF1dGhvcmlzYXRpb24uCklmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgZW1haWwg
aW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBhbmQgZGVsZXRlIHRoaXMgbWVzc2Fn
ZSBhbmQgaXRzIGF0dGFjaG1lbnRzLgpBcyBlbWFpbHMgbWF5IGJlIGFsdGVyZWQsIE9yYW5nZSBp
cyBub3QgbGlhYmxlIGZvciBtZXNzYWdlcyB0aGF0IGhhdmUgYmVlbiBtb2RpZmllZCwgY2hhbmdl
ZCBvciBmYWxzaWZpZWQuClRoYW5rIHlvdS4KCg==


From nobody Thu Dec 14 08:55:23 2017
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FC76124234 for <grow@ietfa.amsl.com>; Thu, 14 Dec 2017 08:55:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level: 
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 hvuqOR9iUMFf for <grow@ietfa.amsl.com>; Thu, 14 Dec 2017 08:55:20 -0800 (PST)
Received: from orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EE84129438 for <grow@ietf.org>; Thu, 14 Dec 2017 08:55:18 -0800 (PST)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 57E12C062F for <grow@ietf.org>; Thu, 14 Dec 2017 17:55:16 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.33]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id 3CC861A007E for <grow@ietf.org>; Thu, 14 Dec 2017 17:55:16 +0100 (CET)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM42.corporate.adroot.infra.ftgroup ([fe80::d5fd:9c7d:2ee3:39d9%19]) with mapi id 14.03.0361.001; Thu, 14 Dec 2017 17:55:16 +0100
From: <bruno.decraene@orange.com>
To: "grow@ietf.org" <grow@ietf.org>
Thread-Topic: [GROW] I-D Action: draft-ietf-grow-bgp-gshut-13.txt
Thread-Index: AQHTdPtlYJY6/kREV0Wzi/jbAnQ4JKNDDfLQ
Date: Thu, 14 Dec 2017 16:55:15 +0000
Message-ID: <17878_1513270516_5A32ACF4_17878_210_1_53C29892C857584299CBF5D05346208A47921255@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <151327011539.28731.10748025497851535620@ietfa.amsl.com>
In-Reply-To: <151327011539.28731.10748025497851535620@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/Y0CXworGU7Xpr9kdcCoNRIJGGVI>
Subject: Re: [GROW] I-D Action: draft-ietf-grow-bgp-gshut-13.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 16:55:22 -0000

Hi all,

-13 addresses the comments received so far during IESG review.

> A diff: https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-grow-bgp-gshut-13

Main comment is to change the category to Standard Tracks.
As a side effect, document needs another IETF LC (Std Track is 4 weeks, Inf=
ormational was only 2 weeks).

Best regards,
--Bruno

 > -----Original Message-----
 > From: GROW [mailto:grow-bounces@ietf.org] On Behalf Of internet-drafts@i=
etf.org
 > Sent: Thursday, December 14, 2017 5:49 PM
 > To: i-d-announce@ietf.org
 > Cc: grow@ietf.org
 > Subject: [GROW] I-D Action: draft-ietf-grow-bgp-gshut-13.txt
 >=20
 >=20
 > A New Internet-Draft is available from the on-line Internet-Drafts direc=
tories.
 > This draft is a work item of the Global Routing Operations WG of the IET=
F.
 >=20
 >         Title           : Graceful BGP session shutdown
 >         Authors         : Pierre Francois
 >                           Bruno Decraene
 >                           Cristel Pelsser
 >                           Keyur Patel
 >                           Clarence Filsfils
 > 	Filename        : draft-ietf-grow-bgp-gshut-13.txt
 > 	Pages           : 11
 > 	Date            : 2017-12-14
 >=20
 > Abstract:
 >    This draft standardizes a new well-known BGP community
 >    GRACEFUL_SHUTDOWN to signal the graceful shutdown of paths.  This
 >    draft also describes operational procedures which use this community
 >    to reduce the amount of traffic lost when BGP peering sessions are
 >    about to be shut down deliberately, e.g. for planned maintenance.
 >=20
 >=20
 > The IETF datatracker status page for this draft is:
 > https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-gshut/
 >=20
 > There are also htmlized versions available at:
 > https://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-13
 > https://datatracker.ietf.org/doc/html/draft-ietf-grow-bgp-gshut-13
 >=20
 > A diff from the previous version is available at:
 > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-grow-bgp-gshut-13
 >=20
 >=20
 > Please note that it may take a couple of minutes from the time of submis=
sion
 > until the htmlized version and diff are available at tools.ietf.org.
 >=20
 > Internet-Drafts are also available by anonymous FTP at:
 > ftp://ftp.ietf.org/internet-drafts/
 >=20
 > _______________________________________________
 > GROW mailing list
 > GROW@ietf.org
 > https://www.ietf.org/mailman/listinfo/grow

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Thu Dec 14 09:02:37 2017
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96D80129431; Thu, 14 Dec 2017 09:02:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level: 
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 tZZKaezp23Rn; Thu, 14 Dec 2017 09:02:30 -0800 (PST)
Received: from orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA64D126C0F; Thu, 14 Dec 2017 09:02:29 -0800 (PST)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 88D5EC0849; Thu, 14 Dec 2017 18:02:28 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.59]) by opfednr00.francetelecom.fr (ESMTP service) with ESMTP id 672311A0064; Thu, 14 Dec 2017 18:02:28 +0100 (CET)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c%19]) with mapi id 14.03.0361.001; Thu, 14 Dec 2017 18:02:27 +0100
From: <bruno.decraene@orange.com>
To: =?utf-8?B?TWlyamEgS8O8aGxld2luZA==?= <ietf@kuehlewind.net>
CC: "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "draft-ietf-grow-bgp-gshut@ietf.org" <draft-ietf-grow-bgp-gshut@ietf.org>, "grow@ietf.org" <grow@ietf.org>, The IESG <iesg@ietf.org>
Thread-Topic: =?utf-8?B?W0dST1ddIE1pcmphIEvDvGhsZXdpbmQncyBObyBPYmplY3Rpb24gb24gZHJh?= =?utf-8?Q?ft-ietf-grow-bgp-gshut-12:_(with_COMMENT)?=
Thread-Index: AQHTdNxMKEoyVOKqd0+vWrk8tfUt0KNDDvAQ
Date: Thu, 14 Dec 2017 17:02:27 +0000
Message-ID: <28140_1513270948_5A32AEA4_28140_146_1_53C29892C857584299CBF5D05346208A479212AF@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <151325675727.6083.15666522007655187267.idtracker@ietfa.amsl.com>
In-Reply-To: <151325675727.6083.15666522007655187267.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/-GattHO27dl3rUqeBoImGCTOwKg>
Subject: Re: [GROW]  =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-?= =?utf-8?q?ietf-grow-bgp-gshut-12=3A_=28with_COMMENT=29?=
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 17:02:36 -0000

TWlyamEsDQoNClRoYW5rcyBmb3IgeW91ciByZXZpZXcgYW5kIGNvbW1lbnRzLg0KUGxlYXNlIHNl
ZSBpbmxpbmUgW0JydW5vXQ0KDQo+IEZyb206IEdST1cgW21haWx0bzpncm93LWJvdW5jZXNAaWV0
Zi5vcmddIE9uIEJlaGFsZiBPZiBNaXJqYSBLw7xobGV3aW5kDQogPiBTZW50OiBUaHVyc2RheSwg
RGVjZW1iZXIgMTQsIDIwMTcgMjowNiBQTQ0KPiANCiA+IE1pcmphIEvDvGhsZXdpbmQgaGFzIGVu
dGVyZWQgdGhlIGZvbGxvd2luZyBiYWxsb3QgcG9zaXRpb24gZm9yDQogPiBkcmFmdC1pZXRmLWdy
b3ctYmdwLWdzaHV0LTEyOiBObyBPYmplY3Rpb24NCiA+IA0KID4gV2hlbiByZXNwb25kaW5nLCBw
bGVhc2Uga2VlcCB0aGUgc3ViamVjdCBsaW5lIGludGFjdCBhbmQgcmVwbHkgdG8gYWxsDQogPiBl
bWFpbCBhZGRyZXNzZXMgaW5jbHVkZWQgaW4gdGhlIFRvIGFuZCBDQyBsaW5lcy4gKEZlZWwgZnJl
ZSB0byBjdXQgdGhpcw0KID4gaW50cm9kdWN0b3J5IHBhcmFncmFwaCwgaG93ZXZlci4pDQogPiAN
CiA+IA0KID4gUGxlYXNlIHJlZmVyIHRvIGh0dHBzOi8vd3d3LmlldGYub3JnL2llc2cvc3RhdGVt
ZW50L2Rpc2N1c3MtY3JpdGVyaWEuaHRtbA0KID4gZm9yIG1vcmUgaW5mb3JtYXRpb24gYWJvdXQg
SUVTRyBESVNDVVNTIGFuZCBDT01NRU5UIHBvc2l0aW9ucy4NCiA+IA0KID4gDQogPiBUaGUgZG9j
dW1lbnQsIGFsb25nIHdpdGggb3RoZXIgYmFsbG90IHBvc2l0aW9ucywgY2FuIGJlIGZvdW5kIGhl
cmU6DQogPiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLWdyb3ct
YmdwLWdzaHV0Lw0KID4gDQogPiANCiA+IA0KID4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KID4gQ09NTUVOVDoN
CiA+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0NCiA+IA0KID4gSSBhbHNvIGJlbGlldmUgdGhpcyBzaG91bGQgYmUg
c3RhbmRhcmRzIHRyYWNrLiBPciBpcyB0aGVyZSBhbnkgZ29vZCByZWFzb24gd2h5DQogPiBpdCBz
aG91bGQgbm90IGJlIHN0YW5kYXJkcyB0cmFjayBzaW1pbGFyIGFzIG90aGVyIGRvY3MgdGhhdCBk
ZWZpbmUgd2VsbCBrbm93bg0KID4gY29tbXVuaXRpZXM/DQogDQpbQnJ1bm9dIE9LLiBUaGlzIGhh
cyBiZWVuIHF1aXRlIGEgZ2VuZXJhbCBjb21tZW50IHNvIGZhci4NCkRvY3VtZW50IGhhcyBqdXN0
IGJlZW4gdXBkYXRlZCAoLTEzKSBhbmQgY2hhbmdlZCB0byBzdGFuZGFyZCB0cmFjay4gV2FycmVu
IGFsc28gY2hhbmdlZCB0aGUgZGF0YXRyYWNrZXIgZGF0YS4NCg0KPiAyMDE3LTEyLTE0IAkxMyAJ
QnJ1bm8gRGVjcmFlbmUgCU5ldyB2ZXJzaW9uIGF2YWlsYWJsZTogZHJhZnQtaWV0Zi1ncm93LWJn
cC1nc2h1dC0xMy50eHQNCj4gMjAxNy0xMi0xNCAJMTIgCVdhcnJlbiBLdW1hcmkgCUludGVuZGVk
IFN0YXR1cyBjaGFuZ2VkIHRvIFByb3Bvc2VkIFN0YW5kYXJkIGZyb20gSW5mb3JtYXRpb25hbA0K
DQpGWUkgZGlmZjogaHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWlldGYt
Z3Jvdy1iZ3AtZ3NodXQtMTMNCg0KVGhhbmtzLA0KQmVzdCByZWdhcmRzLA0KLS1CcnVubw0KDQog
PiANCiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQog
PiBHUk9XIG1haWxpbmcgbGlzdA0KID4gR1JPV0BpZXRmLm9yZw0KID4gaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9ncm93DQoKX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwoKQ2UgbWVzc2FnZSBldCBzZXMg
cGllY2VzIGpvaW50ZXMgcGV1dmVudCBjb250ZW5pciBkZXMgaW5mb3JtYXRpb25zIGNvbmZpZGVu
dGllbGxlcyBvdSBwcml2aWxlZ2llZXMgZXQgbmUgZG9pdmVudCBkb25jCnBhcyBldHJlIGRpZmZ1
c2VzLCBleHBsb2l0ZXMgb3UgY29waWVzIHNhbnMgYXV0b3Jpc2F0aW9uLiBTaSB2b3VzIGF2ZXog
cmVjdSBjZSBtZXNzYWdlIHBhciBlcnJldXIsIHZldWlsbGV6IGxlIHNpZ25hbGVyCmEgbCdleHBl
ZGl0ZXVyIGV0IGxlIGRldHJ1aXJlIGFpbnNpIHF1ZSBsZXMgcGllY2VzIGpvaW50ZXMuIExlcyBt
ZXNzYWdlcyBlbGVjdHJvbmlxdWVzIGV0YW50IHN1c2NlcHRpYmxlcyBkJ2FsdGVyYXRpb24sCk9y
YW5nZSBkZWNsaW5lIHRvdXRlIHJlc3BvbnNhYmlsaXRlIHNpIGNlIG1lc3NhZ2UgYSBldGUgYWx0
ZXJlLCBkZWZvcm1lIG91IGZhbHNpZmllLiBNZXJjaS4KClRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0
dGFjaG1lbnRzIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBvciBwcml2aWxlZ2VkIGluZm9ybWF0
aW9uIHRoYXQgbWF5IGJlIHByb3RlY3RlZCBieSBsYXc7CnRoZXkgc2hvdWxkIG5vdCBiZSBkaXN0
cmlidXRlZCwgdXNlZCBvciBjb3BpZWQgd2l0aG91dCBhdXRob3Jpc2F0aW9uLgpJZiB5b3UgaGF2
ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIg
YW5kIGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cy4KQXMgZW1haWxzIG1h
eSBiZSBhbHRlcmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhhdCBoYXZl
IGJlZW4gbW9kaWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVkLgpUaGFuayB5b3UuCgo=


From nobody Thu Dec 14 09:08:19 2017
Return-Path: <job@instituut.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15417129449 for <grow@ietfa.amsl.com>; Thu, 14 Dec 2017 09:08:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.417
X-Spam-Level: 
X-Spam-Status: No, score=-1.417 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 FUzzgC7UMdAk for <grow@ietfa.amsl.com>; Thu, 14 Dec 2017 09:08:10 -0800 (PST)
Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) (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 7317C129443 for <grow@ietf.org>; Thu, 14 Dec 2017 09:08:10 -0800 (PST)
Received: by mail-wm0-f46.google.com with SMTP id n138so12680132wmg.2 for <grow@ietf.org>; Thu, 14 Dec 2017 09:08:10 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=p3QDjWSS9chyVE7Ek3+OHVALqFtnWGGb8qu14SCW8EM=; b=GQSDOASthuXvK39pUx74mbXDIc+2RGth8jLaOgPACKFqf20ycsqdYnAu4uvoGfejAQ etfNZu5zqf6c6lMwIdRe2NYgYwhAPcPxqqmVWgSWzw5x/evddTqLZXLANJGIpTgo429y Vx/5rx/DIQnJavAK/cWZDDvlLZaZ1KFBUhVBvCcH7DWzYtHOSrWmgjxxIIFvXQzMy4di uMJOFPEaIcA6w6GbPnGQO2vLSkR42DXkMaHKkNHhDen7EeMFzBhnTDBugs+9TpLVv8qC 10nGW8Cb2Pr7RrOFFVXBWIHUkBfTu3BClCKakEuOFElEDVSMViXq9x4x+zXTc1nuyMm3 I7CQ==
X-Gm-Message-State: AKGB3mIotgKcTQsJJb5CzoROkNSgW5Aox61ykverM3cVjtdalsuye0GE GISvV1qUCpKueXeJocyEC+Zcn3tvO9I=
X-Google-Smtp-Source: ACJfBovVII0J5ifgD1ZP55b9+TklawE+q5ZjBs6gJlWdU7q/1aqREct2hTSvB+9P3j39cUMt20DzDw==
X-Received: by 10.80.245.237 with SMTP id x42mr13298187edm.80.1513271288841; Thu, 14 Dec 2017 09:08:08 -0800 (PST)
Received: from vurt.meerval.net (vurt.meerval.net. [192.147.168.22]) by smtp.gmail.com with ESMTPSA id c25sm4007535edb.52.2017.12.14.09.08.07 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 14 Dec 2017 09:08:07 -0800 (PST)
Received: from localhost (vurt.meerval.net [local]) by vurt.meerval.net (OpenSMTPD) with ESMTPA id d82aa43e; Thu, 14 Dec 2017 17:08:07 +0000 (UTC)
Date: Thu, 14 Dec 2017 17:08:06 +0000
From: Job Snijders <job@ntt.net>
To: bruno.decraene@orange.com
Cc: "grow@ietf.org" <grow@ietf.org>
Message-ID: <20171214170806.GL95845@vurt.meerval.net>
References: <151327011539.28731.10748025497851535620@ietfa.amsl.com> <17878_1513270516_5A32ACF4_17878_210_1_53C29892C857584299CBF5D05346208A47921255@OPEXCLILM21.corporate.adroot.infra.ftgroup>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <17878_1513270516_5A32ACF4_17878_210_1_53C29892C857584299CBF5D05346208A47921255@OPEXCLILM21.corporate.adroot.infra.ftgroup>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.9.1 (2017-09-22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/_p1Lt6n7-hRni6jpmfunQT0fACw>
Subject: Re: [GROW] I-D Action: draft-ietf-grow-bgp-gshut-13.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 17:08:18 -0000

On Thu, Dec 14, 2017 at 04:55:15PM +0000, bruno.decraene@orange.com wrote:
> -13 addresses the comments received so far during IESG review.
> 
> > A diff:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-grow-bgp-gshut-13
> 
> Main comment is to change the category to Standard Tracks.  As a side
> effect, document needs another IETF LC (Std Track is 4 weeks,
> Informational was only 2 weeks).

Looks good Bruno!

Kind regards,

Job


From nobody Thu Dec 14 09:13:06 2017
Return-Path: <Donald.Smith@CenturyLink.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFA1E128961; Thu, 14 Dec 2017 09:13:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 BvaoSS0FPfq9; Thu, 14 Dec 2017 09:12:59 -0800 (PST)
Received: from lxdnp29m.centurylink.com (lxdnp29m.centurylink.com [155.70.32.52]) (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 095E9126C0F; Thu, 14 Dec 2017 09:12:59 -0800 (PST)
Received: from lxdnp04n.corp.intranet (lxdnp04n.corp.intranet [151.119.92.83]) by lxdnp29m.centurylink.com (8.14.8/8.14.8) with ESMTP id vBEHCwau051332 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 14 Dec 2017 10:12:58 -0700
Received: from lxdnp04n.corp.intranet (localhost [127.0.0.1]) by lxdnp04n.corp.intranet (8.14.8/8.14.8) with ESMTP id vBEHCrO7016260; Thu, 14 Dec 2017 10:12:53 -0700
Received: from lxdnp31k.corp.intranet (lxdnp23m.corp.intranet [151.119.92.134]) by lxdnp04n.corp.intranet (8.14.8/8.14.8) with ESMTP id vBEHCrF2016257 (version=TLSv1/SSLv3 cipher=AES256-SHA256 bits=256 verify=NO); Thu, 14 Dec 2017 10:12:53 -0700
Received: from lxdnp31k.corp.intranet (localhost [127.0.0.1]) by lxdnp31k.corp.intranet (8.14.8/8.14.8) with ESMTP id vBEHCqkH028714; Thu, 14 Dec 2017 10:12:52 -0700
Received: from vddcwhubex501.ctl.intranet (vddcwhubex501.ctl.intranet [151.119.128.28]) by lxdnp31k.corp.intranet (8.14.8/8.14.8) with ESMTP id vBEHCqHo028711 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 14 Dec 2017 10:12:52 -0700
Received: from PDDCWMBXEX503.ctl.intranet ([fe80::9033:ef22:df02:32a9]) by vddcwhubex501.ctl.intranet ([151.119.128.28]) with mapi id 14.03.0339.000; Thu, 14 Dec 2017 10:12:52 -0700
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, Ben Campbell <ben@nostrum.com>
CC: "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "draft-ietf-grow-bgp-gshut@ietf.org" <draft-ietf-grow-bgp-gshut@ietf.org>, "grow@ietf.org" <grow@ietf.org>, The IESG <iesg@ietf.org>
Thread-Topic: Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
Thread-Index: AQHTdOnn/WOAcmwiYU2OFCSyCkLtgqNDEXB/
Date: Thu, 14 Dec 2017 17:12:52 +0000
Message-ID: <68EFACB32CF4464298EA2779B058889D53D3936E@PDDCWMBXEX503.ctl.intranet>
References: <151322570465.6210.17202569330170241275.idtracker@ietfa.amsl.com>,  <15461_1513262548_5A328DD4_15461_64_1_53C29892C857584299CBF5D05346208A47920D36@OPEXCLILM21.corporate.adroot.infra.ftgroup>
In-Reply-To: <15461_1513262548_5A328DD4_15461_64_1_53C29892C857584299CBF5D05346208A47920D36@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [151.119.128.8]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/MLVxEUrChyigWVznIc9rjyInfPE>
Subject: Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 17:13:01 -0000

I don't see anything around MD5/TCPAO authentication.

>From https://tools.ietf.org/html/rfc6198

" Security considerations MUST be addressed by the proposed solutions.
   In particular, they SHOULD address the issues of bogus g-shut
   messages and how they would affect the network(s), as well as the
   impact of hiding a g-shut message so that g-shut is not performed."

I may have missed it somewhere?


if (initial_ttl!=3D255) then (rfc5082_compliant=3D=3D0)
Donald.Smith@centurylink.com

________________________________________
From: GROW [grow-bounces@ietf.org] on behalf of bruno.decraene@orange.com [=
bruno.decraene@orange.com]
Sent: Thursday, December 14, 2017 7:42 AM
To: Ben Campbell
Cc: grow-chairs@ietf.org; draft-ietf-grow-bgp-gshut@ietf.org; grow@ietf.org=
; The IESG
Subject: Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (wi=
th COMMENT)

Ben,

Thanks for your review and comments.
More inline. [Bruno]

> From: Ben Campbell [mailto:ben@nostrum.com]
>
 > Ben Campbell has entered the following ballot position for
 > draft-ietf-grow-bgp-gshut-12: Yes
 >
 > 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.htm=
l
 > 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-grow-bgp-gshut/
 >
 >
 >
 > ----------------------------------------------------------------------
 > COMMENT:
 > ----------------------------------------------------------------------
 >
 > I'm balloting "yes" because I think it's important to publish this. But,=
 like
 > Alvaro,  I wonder why this is not standards track, BCP, or just about an=
ything
 > but informational. So I support his DISCUSS, including his the comments =
on how
 > to resolve it.

[Bruno] Well noted: we now have 3 AD asking for STD track.
If you don't mind, to avoid duplication, I'll follow up on Alvaro's email. =
(in short, STD track is ok for me)

 > -1, last paragraph: This references RFC 8174, but does not use the actua=
l 8174
 > boilerplate. Is there a reason not to do so?

[Bruno] My mistake: I had a comment to reference RFC 8174 rather than RFC 2=
119. I was not aware that this also implied changing the text.
My understanding is the following:
OLD:
         <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
         "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
         and "OPTIONAL" in this document are to be interpreted as
         described in RFC 8174 <xref target=3D"RFC8174"/>.</t>


NEW
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
      "MAY", and "OPTIONAL" in this document are to be interpreted as
      described in [BCP14] <xref target=3D"RFC2119"/> <xref target=3D"RFC81=
74"/> when, and only when, they
      appear in all capitals, as shown here.</t>



That being said, the irony is that RFC 8174 does not use an upper case "sho=
uld":
"Authors who follow these guidelines should incorporate this phrase near th=
e beginning of their document:"
https://tools.ietf.org/html/rfc8174#section-2

--Bruno

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.

_______________________________________________
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow


This communication is the property of CenturyLink and may contain confident=
ial or privileged information. Unauthorized use of this communication is st=
rictly prohibited and may be unlawful. If you have received this communicat=
ion in error, please immediately notify the sender by reply e-mail and dest=
roy all copies of the communication and any attachments.



From nobody Thu Dec 14 09:21:04 2017
Return-Path: <job@instituut.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7CD9129443 for <grow@ietfa.amsl.com>; Thu, 14 Dec 2017 09:20:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.417
X-Spam-Level: 
X-Spam-Status: No, score=-1.417 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 oJa7fyHcT3Mt for <grow@ietfa.amsl.com>; Thu, 14 Dec 2017 09:20:53 -0800 (PST)
Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) (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 44F7E12943C for <grow@ietf.org>; Thu, 14 Dec 2017 09:20:53 -0800 (PST)
Received: by mail-wm0-f46.google.com with SMTP id 64so12833410wme.3 for <grow@ietf.org>; Thu, 14 Dec 2017 09:20:53 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=37TAVrW/noubYf2OqaTgqF1MXM69Dkf6ZQsT7FcBadg=; b=R082ljWzC5SuBvaPGYyJkLYLtHdT3S30X9o2i3lOq92eSO3w7SzOahoobNB887AR3M uRA86MK8fMJUcGqg3do6qKBu+t1qghLcH+PIjdtw44n9pNsyaJWwusbOU/XC3LPEyI39 BSt30EPk4bMDSmrYKu/oQFmfWG5XkKLKpq++fg1lROJjDgNnccEKvEzYIUcMYkNF44pA mf6XwBlaXLmCDR2LPUeOQmIBHRd0PfVA+OgFGikrqCMPRGmeRaeQsPZlxWG6DrwRV5H0 +F4u7Ic9EL+/RairCyV+utbTTl9hNDQneIlD90TJYKtidUBIM6d3AwvFP8yhMS7k317N 7HXQ==
X-Gm-Message-State: AKGB3mIymLgjVqAFHaZACg82hpKV5CwGXBl7I5/y73nPt4aiUM74ts42 yX6NPRNvRCBx9cv0kn5EX44ArQ==
X-Google-Smtp-Source: ACJfBot/VshkszdEF6001glcecLwl+NWIjwYvMmzK7xhtiwZEHgqnG/fRgYAzwIUf9LZtHEQAPJUyw==
X-Received: by 10.80.193.9 with SMTP id l9mr13283011edf.176.1513272051623; Thu, 14 Dec 2017 09:20:51 -0800 (PST)
Received: from vurt.meerval.net (vurt.meerval.net. [192.147.168.22]) by smtp.gmail.com with ESMTPSA id k18sm3897459eda.20.2017.12.14.09.20.42 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 14 Dec 2017 09:20:42 -0800 (PST)
Received: from localhost (vurt.meerval.net [local]) by vurt.meerval.net (OpenSMTPD) with ESMTPA id 8fc30f00; Thu, 14 Dec 2017 17:20:41 +0000 (UTC)
Date: Thu, 14 Dec 2017 17:20:41 +0000
From: Job Snijders <job@ntt.net>
To: "Smith, Donald" <Donald.Smith@CenturyLink.com>
Cc: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, Ben Campbell <ben@nostrum.com>, "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "draft-ietf-grow-bgp-gshut@ietf.org" <draft-ietf-grow-bgp-gshut@ietf.org>, "grow@ietf.org" <grow@ietf.org>, The IESG <iesg@ietf.org>
Message-ID: <20171214172041.GO95845@vurt.meerval.net>
References: <151322570465.6210.17202569330170241275.idtracker@ietfa.amsl.com> <15461_1513262548_5A328DD4_15461_64_1_53C29892C857584299CBF5D05346208A47920D36@OPEXCLILM21.corporate.adroot.infra.ftgroup> <68EFACB32CF4464298EA2779B058889D53D3936E@PDDCWMBXEX503.ctl.intranet>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <68EFACB32CF4464298EA2779B058889D53D3936E@PDDCWMBXEX503.ctl.intranet>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.9.1 (2017-09-22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/XsqBkQBZxYj7dyJzcMY1kBYmc7E>
Subject: Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 17:20:54 -0000

On Thu, Dec 14, 2017 at 05:12:52PM +0000, Smith, Donald wrote:
> I don't see anything around MD5/TCPAO authentication.
> 
> >From https://tools.ietf.org/html/rfc6198
> 
> " Security considerations MUST be addressed by the proposed solutions.
>   In particular, they SHOULD address the issues of bogus g-shut
>   messages and how they would affect the network(s), as well as the
>   impact of hiding a g-shut message so that g-shut is not performed."
> 
> I may have missed it somewhere?

I have trouble parsing this requirements text.

What makes a "bogus g-shut" a "bogus g-shut"?

How is 'hiding' (I interpret this as 'removing the gshut community) a
g-shut any different than the other BGP speaker not supporting g-shut?

How is any of this different than NO_EXPORT or NO_ADVERTISE?

Kind regards,

Job


From nobody Thu Dec 14 10:03:48 2017
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42B4112704A; Thu, 14 Dec 2017 10:03:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level: 
X-Spam-Status: No, score=-2.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 43Fyo5eT9Y00; Thu, 14 Dec 2017 10:03:44 -0800 (PST)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A410126DFF; Thu, 14 Dec 2017 10:03:44 -0800 (PST)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 584F9C0860; Thu, 14 Dec 2017 19:03:43 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.13]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 2628940060; Thu, 14 Dec 2017 19:03:43 +0100 (CET)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM6D.corporate.adroot.infra.ftgroup ([fe80::54f9:a6c3:c013:cbc7%19]) with mapi id 14.03.0361.001; Thu, 14 Dec 2017 19:03:42 +0100
From: <bruno.decraene@orange.com>
To: "Smith, Donald" <Donald.Smith@CenturyLink.com>
CC: "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "draft-ietf-grow-bgp-gshut@ietf.org" <draft-ietf-grow-bgp-gshut@ietf.org>, "grow@ietf.org" <grow@ietf.org>, The IESG <iesg@ietf.org>, Ben Campbell <ben@nostrum.com>
Thread-Topic: Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
Thread-Index: AQHTdJP90cSHHsziR0WKcqR14+JgtqNC5XiwgAAeKACAABWC4A==
Date: Thu, 14 Dec 2017 18:03:42 +0000
Message-ID: <5142_1513274623_5A32BCFF_5142_246_1_53C29892C857584299CBF5D05346208A4792151C@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <151322570465.6210.17202569330170241275.idtracker@ietfa.amsl.com>,  <15461_1513262548_5A328DD4_15461_64_1_53C29892C857584299CBF5D05346208A47920D36@OPEXCLILM21.corporate.adroot.infra.ftgroup> <68EFACB32CF4464298EA2779B058889D53D3936E@PDDCWMBXEX503.ctl.intranet>
In-Reply-To: <68EFACB32CF4464298EA2779B058889D53D3936E@PDDCWMBXEX503.ctl.intranet>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/jTbRCf33H5y4HYh8FfvTJy_S2dg>
Subject: Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 18:03:47 -0000

> From: Smith, Donald [mailto:Donald.Smith@CenturyLink.com]
 > Sent: Thursday, December 14, 2017 6:13 PM
>=20
 > I don't see anything around MD5/TCPAO authentication.

This is correct, but this is really not specific to this document and the c=
omment would apply to any information sent over BGP session, and probably t=
o most of IDR document extending the protocol with additional field or usag=
e.
If there is a need to discuss this all IETF document related to BGP, we can=
 indeed add some text. Would the following text be ok with you?

"This document does not change any underlying security issues associated wi=
th any other BGP Communities mechanism.  Unless a transport that
   provides integrity is used for the BGP session, the GRACEFUL_SHUTDOWN co=
mmunity may be added or removed by a man in the middle. However, the harm w=
ould be lower than adding or removing an NLRI, or adding a NO_EXPORT or NO_=
ADVERTISE community. Hence this does not constitute a new attack vector. Pr=
otection of the TCP session used by BGP is discussed in section 5.1 of RFC =
7454,  security section of [RFC4271] and [RFC4272]."

Regards,
--Bruno

 >=20
 > >From https://tools.ietf.org/html/rfc6198
 >=20
 > " Security considerations MUST be addressed by the proposed solutions.
 >    In particular, they SHOULD address the issues of bogus g-shut
 >    messages and how they would affect the network(s), as well as the
 >    impact of hiding a g-shut message so that g-shut is not performed."
 >=20
 > I may have missed it somewhere?
 >=20
 >=20
 > if (initial_ttl!=3D255) then (rfc5082_compliant=3D=3D0)
 > Donald.Smith@centurylink.com
 >=20
 > ________________________________________
 > From: GROW [grow-bounces@ietf.org] on behalf of bruno.decraene@orange.com
 > [bruno.decraene@orange.com]
 > Sent: Thursday, December 14, 2017 7:42 AM
 > To: Ben Campbell
 > Cc: grow-chairs@ietf.org; draft-ietf-grow-bgp-gshut@ietf.org; grow@ietf.=
org; The IESG
 > Subject: Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: =
(with COMMENT)
 >=20
 > Ben,
 >=20
 > Thanks for your review and comments.
 > More inline. [Bruno]
 >=20
 > > From: Ben Campbell [mailto:ben@nostrum.com]
 > >
 >  > Ben Campbell has entered the following ballot position for
 >  > draft-ietf-grow-bgp-gshut-12: Yes
 >  >
 >  > 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 th=
is
 >  > 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-grow-bgp-gshut/
 >  >
 >  >
 >  >
 >  > ----------------------------------------------------------------------
 >  > COMMENT:
 >  > ----------------------------------------------------------------------
 >  >
 >  > I'm balloting "yes" because I think it's important to publish this. B=
ut, like
 >  > Alvaro,  I wonder why this is not standards track, BCP, or just about=
 anything
 >  > but informational. So I support his DISCUSS, including his the commen=
ts on how
 >  > to resolve it.
 >=20
 > [Bruno] Well noted: we now have 3 AD asking for STD track.
 > If you don't mind, to avoid duplication, I'll follow up on Alvaro's emai=
l. (in short, STD track is ok for
 > me)
 >=20
 >  > -1, last paragraph: This references RFC 8174, but does not use the ac=
tual 8174
 >  > boilerplate. Is there a reason not to do so?
 >=20
 > [Bruno] My mistake: I had a comment to reference RFC 8174 rather than RF=
C 2119. I was not
 > aware that this also implied changing the text.
 > My understanding is the following:
 > OLD:
 >          <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
 >          "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
 >          and "OPTIONAL" in this document are to be interpreted as
 >          described in RFC 8174 <xref target=3D"RFC8174"/>.</t>
 >=20
 >=20
 > NEW
 >         <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
 >       NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
 >       "MAY", and "OPTIONAL" in this document are to be interpreted as
 >       described in [BCP14] <xref target=3D"RFC2119"/> <xref target=3D"RF=
C8174"/> when, and only
 > when, they
 >       appear in all capitals, as shown here.</t>
 >=20
 >=20
 >=20
 > That being said, the irony is that RFC 8174 does not use an upper case "=
should":
 > "Authors who follow these guidelines should incorporate this phrase near=
 the beginning of their
 > document:"
 > https://tools.ietf.org/html/rfc8174#section-2
 >=20
 > --Bruno
 >=20
 > ________________________________________________________________________=
_____
 > ____________________________________________
 >=20
 > Ce message et ses pieces jointes peuvent contenir des informations confi=
dentielles ou
 > privilegiees et ne doivent donc
 > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez r=
ecu ce message par
 > erreur, veuillez le signaler
 > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages=
 electroniques etant
 > susceptibles d'alteration,
 > Orange decline toute responsabilite si ce message a ete altere, deforme =
ou falsifie. Merci.
 >=20
 > This message and its attachments may contain confidential or privileged =
information that may be
 > protected by law;
 > they should not be distributed, used or copied without authorisation.
 > If you have received this email in error, please notify the sender and d=
elete this message and its
 > attachments.
 > As emails may be altered, Orange is not liable for messages that have be=
en modified, changed or
 > falsified.
 > Thank you.
 >=20
 > _______________________________________________
 > GROW mailing list
 > GROW@ietf.org
 > https://www.ietf.org/mailman/listinfo/grow
 >=20
 >=20
 > This communication is the property of CenturyLink and may contain confid=
ential or privileged
 > information. Unauthorized use of this communication is strictly prohibit=
ed and may be unlawful.
 > If you have received this communication in error, please immediately not=
ify the sender by reply e-
 > mail and destroy all copies of the communication and any attachments.
 >=20


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Thu Dec 14 11:38:31 2017
Return-Path: <job@instituut.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD8B7129464 for <grow@ietfa.amsl.com>; Thu, 14 Dec 2017 11:38:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level: 
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 NnucmcQdLlOg for <grow@ietfa.amsl.com>; Thu, 14 Dec 2017 11:38:25 -0800 (PST)
Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) (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 9BB15124D6C for <grow@ietf.org>; Thu, 14 Dec 2017 11:38:23 -0800 (PST)
Received: by mail-wm0-f49.google.com with SMTP id f9so13657087wmh.0 for <grow@ietf.org>; Thu, 14 Dec 2017 11:38:23 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=t700b2a8tIzt9atSxj6SrHBXiA3o+97vpaR2fmK5WCE=; b=QbbBRIAWTCHsmBzB14xHj4VkkQFcZEyjobX7ISFFA5or5TlcyBEozQ2/AfpUAz6oOx ea6w54lkcsxH36fBfFxsqI+tBnM2/kMjcYNkpicmZ2JsRFvQ3seBD6NI8qhkSxd30FFm Q7zQj4YU3UCwMnAc2k449H8fhl2dxSgGCy0c3R1No1dtN7hYE2aW+dvoIHML0nAQBGpa edyE5/MbhvBfS0Pff0vwc8JlLlmydQWFfaOsZZVpvux5YublwZDpfcKf9WIRRS2RCOnh KsC/merZVh1fV6yiypwNma3UWA3SqxDURam0AQX1abHAJO96DQ1GNx+FuPNImnB+m4Cp pKHA==
X-Gm-Message-State: AKGB3mL8qc4T9DpmK2nD1+l92nFRtM2uzIA577K89HHgs23SuVimaf9V 4CzUQqMFgCLXv5XRltCAi47yVPoPf1I=
X-Google-Smtp-Source: ACJfBou/5SnDHw/CB6VFxeD71ZNZuGQK3GzbcvWXjQpWRkAY82DqLrZ6JPfwyPNIWgf3Mi0NlLPW5Q==
X-Received: by 10.80.240.200 with SMTP id a8mr13801884edm.288.1513280301669; Thu, 14 Dec 2017 11:38:21 -0800 (PST)
Received: from vurt.meerval.net (vurt.meerval.net. [192.147.168.22]) by smtp.gmail.com with ESMTPSA id r8sm3712335edm.22.2017.12.14.11.38.19 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 14 Dec 2017 11:38:20 -0800 (PST)
Received: from localhost (vurt.meerval.net [local]) by vurt.meerval.net (OpenSMTPD) with ESMTPA id 2fc55896; Thu, 14 Dec 2017 19:38:19 +0000 (UTC)
Date: Thu, 14 Dec 2017 19:38:19 +0000
From: Job Snijders <job@ntt.net>
To: bruno.decraene@orange.com
Cc: "Smith, Donald" <Donald.Smith@CenturyLink.com>, "grow-chairs@ietf.org" <grow-chairs@ietf.org>, Ben Campbell <ben@nostrum.com>, "draft-ietf-grow-bgp-gshut@ietf.org" <draft-ietf-grow-bgp-gshut@ietf.org>, "grow@ietf.org" <grow@ietf.org>, The IESG <iesg@ietf.org>
Message-ID: <20171214193819.GS95845@vurt.meerval.net>
References: <151322570465.6210.17202569330170241275.idtracker@ietfa.amsl.com> <15461_1513262548_5A328DD4_15461_64_1_53C29892C857584299CBF5D05346208A47920D36@OPEXCLILM21.corporate.adroot.infra.ftgroup> <68EFACB32CF4464298EA2779B058889D53D3936E@PDDCWMBXEX503.ctl.intranet> <5142_1513274623_5A32BCFF_5142_246_1_53C29892C857584299CBF5D05346208A4792151C@OPEXCLILM21.corporate.adroot.infra.ftgroup>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5142_1513274623_5A32BCFF_5142_246_1_53C29892C857584299CBF5D05346208A4792151C@OPEXCLILM21.corporate.adroot.infra.ftgroup>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.9.1 (2017-09-22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/7UPzm7a6GYW-nsw2fDfC65sePQU>
Subject: Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 19:38:27 -0000

On Thu, Dec 14, 2017 at 06:03:42PM +0000, bruno.decraene@orange.com wrote:
> > From: Smith, Donald [mailto:Donald.Smith@CenturyLink.com]
>  > Sent: Thursday, December 14, 2017 6:13 PM
> > 
>  > I don't see anything around MD5/TCPAO authentication.
> 
> This is correct, but this is really not specific to this document and
> the comment would apply to any information sent over BGP session, and
> probably to most of IDR document extending the protocol with
> additional field or usage.  If there is a need to discuss this all
> IETF document related to BGP, we can indeed add some text. Would the
> following text be ok with you?
> 
> "This document does not change any underlying security issues
> associated with any other BGP Communities mechanism.  Unless a
> transport that provides integrity is used for the BGP session, the
> GRACEFUL_SHUTDOWN community may be added or removed by a man in the
> middle. However, the harm would be lower than adding or removing an
> NLRI, or adding a NO_EXPORT or NO_ADVERTISE community. Hence this does
> not constitute a new attack vector. Protection of the TCP session used
> by BGP is discussed in section 5.1 of RFC 7454,  security section of
> [RFC4271] and [RFC4272]."

I think the above is mostly good, but can be trimmed a little bit. The
following is on point and covers aspects relevant to GRACEFUL_SHUTDOWN.

    "This document does not change any underlying security issues
    associated with any other BGP Communities mechanism. Unless a
    transport that provides integrity is used for the BGP session, the
    GRACEFUL_SHUTDOWN community may be added or removed by a man in the
    middle."

Kind regards,

Job


From nobody Thu Dec 14 12:55:26 2017
Return-Path: <Donald.Smith@CenturyLink.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0839126D45; Thu, 14 Dec 2017 12:55:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=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 CepUg1KDkCMg; Thu, 14 Dec 2017 12:55:23 -0800 (PST)
Received: from lxomp52w.centurylink.com (lxomp52w.centurylink.com [155.70.50.76]) (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 006E21200C1; Thu, 14 Dec 2017 12:55:22 -0800 (PST)
Received: from lxomp90v.corp.intranet (lxomp90v.corp.intranet [151.117.203.59]) by lxomp52w.centurylink.com (8.14.8/8.14.8) with ESMTP id vBEKtLnd027616 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 14 Dec 2017 14:55:22 -0600
Received: from lxomp90v.corp.intranet (localhost [127.0.0.1]) by lxomp90v.corp.intranet (8.14.8/8.14.8) with ESMTP id vBEKtG3p047415; Thu, 14 Dec 2017 14:55:16 -0600
Received: from lxomp07u.corp.intranet (lxomp81v.corp.intranet [151.117.18.14]) by lxomp90v.corp.intranet (8.14.8/8.14.8) with ESMTP id vBEKtGqJ047412 (version=TLSv1/SSLv3 cipher=AES256-SHA256 bits=256 verify=NO); Thu, 14 Dec 2017 14:55:16 -0600
Received: from lxomp07u.corp.intranet (localhost [127.0.0.1]) by lxomp07u.corp.intranet (8.14.8/8.14.8) with ESMTP id vBEKtGjU008146; Thu, 14 Dec 2017 14:55:16 -0600
Received: from vddcwhubex501.ctl.intranet (vddcwhubex501.ctl.intranet [151.119.128.28]) by lxomp07u.corp.intranet (8.14.8/8.14.8) with ESMTP id vBEKtGZ4008143 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 14 Dec 2017 14:55:16 -0600
Received: from PDDCWMBXEX503.ctl.intranet ([fe80::9033:ef22:df02:32a9]) by vddcwhubex501.ctl.intranet ([151.119.128.28]) with mapi id 14.03.0339.000; Thu, 14 Dec 2017 13:55:15 -0700
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: Job Snijders <job@ntt.net>, "bruno.decraene@orange.com" <bruno.decraene@orange.com>
CC: "grow-chairs@ietf.org" <grow-chairs@ietf.org>, Ben Campbell <ben@nostrum.com>, "draft-ietf-grow-bgp-gshut@ietf.org" <draft-ietf-grow-bgp-gshut@ietf.org>, "grow@ietf.org" <grow@ietf.org>, "The IESG" <iesg@ietf.org>
Thread-Topic: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
Thread-Index: AQHTdOnn/WOAcmwiYU2OFCSyCkLtgqNDEXB/gACF1QCAABpvgP//nuVq
Date: Thu, 14 Dec 2017 20:55:15 +0000
Message-ID: <68EFACB32CF4464298EA2779B058889D53D3961F@PDDCWMBXEX503.ctl.intranet>
References: <151322570465.6210.17202569330170241275.idtracker@ietfa.amsl.com> <15461_1513262548_5A328DD4_15461_64_1_53C29892C857584299CBF5D05346208A47920D36@OPEXCLILM21.corporate.adroot.infra.ftgroup> <68EFACB32CF4464298EA2779B058889D53D3936E@PDDCWMBXEX503.ctl.intranet> <5142_1513274623_5A32BCFF_5142_246_1_53C29892C857584299CBF5D05346208A4792151C@OPEXCLILM21.corporate.adroot.infra.ftgroup>, <20171214193819.GS95845@vurt.meerval.net>
In-Reply-To: <20171214193819.GS95845@vurt.meerval.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [151.119.128.8]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/glA6JVWnnFYTS-1a9djLi2ZCttM>
Subject: Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 20:55:25 -0000

if (initial_ttl!=3D255) then (rfc5082_compliant=3D=3D0)
Donald.Smith@centurylink.com

>       ________________________________________
>       From: Job Snijders [job@ntt.net]
>       Sent: Thursday, December 14, 2017 12:38 PM
>       To: bruno.decraene@orange.com
>       Cc: Smith, Donald; grow-chairs@ietf.org; Ben Campbell; draft-ietf-g=
row-bgp-gshut@ietf.org; grow@ietf.org; The IESG
>       Subject: Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut=
-12: (with COMMENT)
>
>       On Thu, Dec 14, 2017 at 06:03:42PM +0000, bruno.decraene@orange.com=
 wrote:
>       > > From: Smith, Donald [mailto:Donald.Smith@CenturyLink.com]
>       >  > Sent: Thursday, December 14, 2017 6:13 PM
>       > >
>       >  > I don't see anything around MD5/TCPAO authentication.
>       >
>       > This is correct, but this is really not specific to this document=
 and
>       > the comment would apply to any information sent over BGP session,=
 and
>       > probably to most of IDR document extending the protocol with
>       > additional field or usage.  If there is a need to discuss this al=
l
>       > IETF document related to BGP, we can indeed add some text. Would =
the
>       > following text be ok with you?
>       >
>       > "This document does not change any underlying security issues
>       > associated with any other BGP Communities mechanism.  Unless a
>       > transport that provides integrity is used for the BGP session, th=
e
>       > GRACEFUL_SHUTDOWN community may be added or removed by a man in t=
he
>       > middle. However, the harm would be lower than adding or removing =
an
>       > NLRI, or adding a NO_EXPORT or NO_ADVERTISE community. Hence this=
 does
>       > not constitute a new attack vector. Protection of the TCP session=
 used
>       > by BGP is discussed in section 5.1 of RFC 7454,  security section=
 of
>       > [RFC4271] and [RFC4272]."
>
>       I think the above is mostly good, but can be trimmed a little bit. =
The
>       following is on point and covers aspects relevant to GRACEFUL_SHUTD=
OWN.
>
>           "This document does not change any underlying security issues
>           associated with any other BGP Communities mechanism. Unless a
>           transport that provides integrity is used for the BGP session, =
the
>           GRACEFUL_SHUTDOWN community may be added or removed by a man in=
 the
>           middle."
>
>       Kind regards,
>
>       Job

Since in theory you could do this blindly (tcp slipping in the window), I w=
ould remove the MITM and say by "unauthorized 3rd parties" or something lik=
e that.

Otherwise this is better than putting all the other security recommendation=
s from other rfcs [4271, 4272] so I support referencing them instead.


This communication is the property of CenturyLink and may contain confident=
ial or privileged information. Unauthorized use of this communication is st=
rictly prohibited and may be unlawful. If you have received this communicat=
ion in error, please immediately notify the sender by reply e-mail and dest=
roy all copies of the communication and any attachments.



From nobody Thu Dec 14 13:14:19 2017
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: grow@ietf.org
Delivered-To: grow@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 47DFE1200C1; Thu, 14 Dec 2017 13:14:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.67.1
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-ietf-grow-bgp-gshut@ietf.org, grow-chairs@ietf.org, grow@ietf.org, Christopher Morrow <christopher.morrow@gmail.com>, christopher.morrow@gmail.com, warren@kumari.net
Reply-To: ietf@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <151328605829.3527.11207434130326039764.idtracker@ietfa.amsl.com>
Date: Thu, 14 Dec 2017 13:14:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/TuuERHVl1T3UK3YYeN7qdgsTOMQ>
Subject: [GROW] Last Call: <draft-ietf-grow-bgp-gshut-13.txt> (Graceful BGP session shutdown) to Proposed Standard
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 21:14:18 -0000

The IESG has received a request from the Global Routing Operations WG (grow)
to consider the following document: - 'Graceful BGP session shutdown'
  <draft-ietf-grow-bgp-gshut-13.txt> as Proposed Standard

This is a second IETF Last Call. The document had an initial LC as an Informational 
document, but the IESG felt it was more appropriate to be Standards Track. As the 
Last Call time will run into the end of the year holiday period, we are requesting 
a 4-week Last Call.

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2018-01-11. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   This draft standardizes a new well-known BGP community
   GRACEFUL_SHUTDOWN to signal the graceful shutdown of paths.  This
   draft also describes operational procedures which use this community
   to reduce the amount of traffic lost when BGP peering sessions are
   about to be shut down deliberately, e.g. for planned maintenance.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-gshut/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-gshut/ballot/


No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc6198: Requirements for the Graceful Shutdown of BGP Sessions (Informational - IETF stream)




From nobody Thu Dec 14 14:15:36 2017
Return-Path: <Donald.Smith@CenturyLink.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A33E124D68; Thu, 14 Dec 2017 14:15:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 xQKxrqC4s8Kp; Thu, 14 Dec 2017 14:15:34 -0800 (PST)
Received: from lxdnp29m.centurylink.com (lxdnp29m.centurylink.com [155.70.32.52]) (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 E17DD1242EA; Thu, 14 Dec 2017 14:15:33 -0800 (PST)
Received: from lxdnp04n.corp.intranet (emailout.qintra.com [151.119.92.83]) by lxdnp29m.centurylink.com (8.14.8/8.14.8) with ESMTP id vBEMFXV1003027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 14 Dec 2017 15:15:33 -0700
Received: from lxdnp04n.corp.intranet (localhost [127.0.0.1]) by lxdnp04n.corp.intranet (8.14.8/8.14.8) with ESMTP id vBEMFSAM019525; Thu, 14 Dec 2017 15:15:28 -0700
Received: from lxdnp31k.corp.intranet (lxdnp23m.corp.intranet [151.119.92.134]) by lxdnp04n.corp.intranet (8.14.8/8.14.8) with ESMTP id vBEMFRv0019519 (version=TLSv1/SSLv3 cipher=AES256-SHA256 bits=256 verify=NO); Thu, 14 Dec 2017 15:15:27 -0700
Received: from lxdnp31k.corp.intranet (localhost [127.0.0.1]) by lxdnp31k.corp.intranet (8.14.8/8.14.8) with ESMTP id vBEMFR9n046034; Thu, 14 Dec 2017 15:15:27 -0700
Received: from vddcwhubex502.ctl.intranet (vddcwhubex502.ctl.intranet [151.119.128.29]) by lxdnp31k.corp.intranet (8.14.8/8.14.8) with ESMTP id vBEMFRiQ046031 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 14 Dec 2017 15:15:27 -0700
Received: from PDDCWMBXEX503.ctl.intranet ([fe80::9033:ef22:df02:32a9]) by vddcwhubex502.ctl.intranet ([151.119.128.29]) with mapi id 14.03.0339.000; Thu, 14 Dec 2017 15:15:27 -0700
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: Job Snijders <job@ntt.net>
CC: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, Ben Campbell <ben@nostrum.com>, "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "draft-ietf-grow-bgp-gshut@ietf.org" <draft-ietf-grow-bgp-gshut@ietf.org>, "grow@ietf.org" <grow@ietf.org>, The IESG <iesg@ietf.org>
Thread-Topic: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
Thread-Index: AQHTdOnn/WOAcmwiYU2OFCSyCkLtgqNDEXB/gAB50ID//9uB6g==
Date: Thu, 14 Dec 2017 22:15:26 +0000
Message-ID: <68EFACB32CF4464298EA2779B058889D53D3970F@PDDCWMBXEX503.ctl.intranet>
References: <151322570465.6210.17202569330170241275.idtracker@ietfa.amsl.com> <15461_1513262548_5A328DD4_15461_64_1_53C29892C857584299CBF5D05346208A47920D36@OPEXCLILM21.corporate.adroot.infra.ftgroup> <68EFACB32CF4464298EA2779B058889D53D3936E@PDDCWMBXEX503.ctl.intranet>, <20171214172041.GO95845@vurt.meerval.net>
In-Reply-To: <20171214172041.GO95845@vurt.meerval.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [151.119.128.8]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/ApwIFpg6zVtPsMqa1o3KR8xBCV8>
Subject: Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 22:15:36 -0000

I read bogus as spoofed or forged.


if (initial_ttl!=3D255) then (rfc5082_compliant=3D=3D0)
Donald.Smith@centurylink.com

________________________________________
From: Job Snijders [job@ntt.net]
Sent: Thursday, December 14, 2017 10:20 AM
To: Smith, Donald
Cc: bruno.decraene@orange.com; Ben Campbell; grow-chairs@ietf.org; draft-ie=
tf-grow-bgp-gshut@ietf.org; grow@ietf.org; The IESG
Subject: Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (wi=
th COMMENT)

On Thu, Dec 14, 2017 at 05:12:52PM +0000, Smith, Donald wrote:
> I don't see anything around MD5/TCPAO authentication.
>
> >From https://tools.ietf.org/html/rfc6198
>
> " Security considerations MUST be addressed by the proposed solutions.
>   In particular, they SHOULD address the issues of bogus g-shut
>   messages and how they would affect the network(s), as well as the
>   impact of hiding a g-shut message so that g-shut is not performed."
>
> I may have missed it somewhere?

I have trouble parsing this requirements text.

What makes a "bogus g-shut" a "bogus g-shut"?

How is 'hiding' (I interpret this as 'removing the gshut community) a
g-shut any different than the other BGP speaker not supporting g-shut?

How is any of this different than NO_EXPORT or NO_ADVERTISE?

Kind regards,

Job


This communication is the property of CenturyLink and may contain confident=
ial or privileged information. Unauthorized use of this communication is st=
rictly prohibited and may be unlawful. If you have received this communicat=
ion in error, please immediately notify the sender by reply e-mail and dest=
roy all copies of the communication and any attachments.



From nobody Thu Dec 14 15:04:45 2017
Return-Path: <ben@nostrum.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85CEE1270AE; Thu, 14 Dec 2017 15:04:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=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 hwgu1JRWW4PL; Thu, 14 Dec 2017 15:04:39 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 F3BCA127005; Thu, 14 Dec 2017 15:04:24 -0800 (PST)
Received: from [10.0.1.99] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id vBEN4M0K046753 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 14 Dec 2017 17:04:23 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.99]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <8AABAA84-04BD-4D41-95D1-2F591D2F6A57@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_EEBE48A2-0ED0-4B26-8B7D-C935ED95B1B9"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Thu, 14 Dec 2017 17:04:21 -0600
In-Reply-To: <15461_1513262548_5A328DD4_15461_64_1_53C29892C857584299CBF5D05346208A47920D36@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Cc: "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "draft-ietf-grow-bgp-gshut@ietf.org" <draft-ietf-grow-bgp-gshut@ietf.org>, "grow@ietf.org" <grow@ietf.org>, "christopher.morrow@gmail.com" <christopher.morrow@gmail.com>, The IESG <iesg@ietf.org>
To: bruno.decraene@orange.com
References: <151322570465.6210.17202569330170241275.idtracker@ietfa.amsl.com> <15461_1513262548_5A328DD4_15461_64_1_53C29892C857584299CBF5D05346208A47920D36@OPEXCLILM21.corporate.adroot.infra.ftgroup>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/TI-OXev1UB2ZxuoWI1uJIyW9ILk>
Subject: Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 23:04:42 -0000

--Apple-Mail=_EEBE48A2-0ED0-4B26-8B7D-C935ED95B1B9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



> On Dec 14, 2017, at 8:42 AM, bruno.decraene@orange.com wrote:
>=20
> Ben,
>=20
> Thanks for your review and comments.
> More inline. [Bruno]
>=20
>> From: Ben Campbell [mailto:ben@nostrum.com]
>>=20
>> Ben Campbell has entered the following ballot position for
>> draft-ietf-grow-bgp-gshut-12: Yes
>>=20
>> 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.)
>>=20
>>=20
>> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-gshut/
>>=20
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> COMMENT:
>> =
----------------------------------------------------------------------
>>=20
>> I'm balloting "yes" because I think it's important to publish this. =
But, like
>> Alvaro,  I wonder why this is not standards track, BCP, or just about =
anything
>> but informational. So I support his DISCUSS, including his the =
comments on how
>> to resolve it.
>=20
> [Bruno] Well noted: we now have 3 AD asking for STD track.
> If you don't mind, to avoid duplication, I'll follow up on Alvaro's =
email. (in short, STD track is ok for me)

Thanks, I will follow the discussion there.

>=20
>> -1, last paragraph: This references RFC 8174, but does not use the =
actual 8174
>> boilerplate. Is there a reason not to do so?
>=20
> [Bruno] My mistake: I had a comment to reference RFC 8174 rather than =
RFC 2119. I was not aware that this also implied changing the text.
> My understanding is the following:
> OLD:
> 	 <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
> 	 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
> 	 and "OPTIONAL" in this document are to be interpreted as
> 	 described in RFC 8174 <xref target=3D"RFC8174"/>.</t>
>=20
>=20
> NEW
> 	<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
>      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
>      "MAY", and "OPTIONAL" in this document are to be interpreted as
>      described in [BCP14] <xref target=3D"RFC2119"/> <xref =
target=3D"RFC8174"/> when, and only when, they
>      appear in all capitals, as shown here.</t>
>=20

Works for me.

>=20
>=20
> That being said, the irony is that RFC 8174 does not use an upper case =
"should":
> "Authors who follow these guidelines should incorporate this phrase =
near the beginning of their document:"
> https://tools.ietf.org/html/rfc8174#section-2
>=20

I think that was carefully chosen, since the 2119/8174 keywords are =
intended to be about interoperability among protocol implementations =
more than requirements for the standards process. OTOH, RFC 2119 has an =
all-caps MUST in the sentence that states that, making it a =
self-violating requirement:

"In particular, they MUST only be used where it is actually required for =
interoperation or to limit behavior which has potential for causing =
harm."

So, go figure :-)


Thanks!

Ben.


--Apple-Mail=_EEBE48A2-0ED0-4B26-8B7D-C935ED95B1B9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlozA3UACgkQgFZKbJXz
1A2E6g//SML9jswn8qe3Mj0RNjJYdhJ2D0YKoy73d3RSHeRRz33gBfXrN1zZ8gBS
k+xH4rG5pGQPHZr+jwIkHmDEKRttK5wundQgwQwGl6JTepdQKR+PgdE59seC2Pj9
dPb91G+YbMl2VlmmHXpbjlPzs+iffdnYdURdaTqCMkSmcfxNk7371aUxTtCm+TNk
XJ1otNMw6JFxHleHZg+7oHTqmhX5rbuLtJ7kQzz3FTaSRG4DWaFLzwiJWnWAHnNp
wfnIjxkNcUDbdkaL7Y6y9D2dMTV2ogbTSuj66pRnBu5YGIqVjNtXvy6WgEpkjudM
cl2gZIgPP2WHG36TKa2S/hyR7LnRiWYN4iWLltfxHlN1WEbrZB5SCRgGvmzryWVR
gX4Wnn96h+1vrYKiVSV0OVgBLr2JwBGOJE3+Hs8KyfvXbu8SG58qXDTNvmCF+uvh
0oUe18bWM05qq2iDVzx3ZiNw8Vm3Sg2Y8YAbaY0753/OnJkch7uy9zlh1PsgGGD+
L4pHfiVpf9wQ+FnSqMyd/hzffGwR3c19ngzsP/4XjCNh1rrhe/JhifeEC+T1c93c
NtTYjyxTwHa/ddQfHSqdE7EPkC+JlOm/HyehR6sJE2a3FqyhN62PFxaX+YdxObjq
YU6SYma5b0nDJ/LM3q8J/px3iQejy6Jde6Ht2/+igPg5am6x9O4=
=vsZA
-----END PGP SIGNATURE-----

--Apple-Mail=_EEBE48A2-0ED0-4B26-8B7D-C935ED95B1B9--


From nobody Fri Dec 15 01:29:34 2017
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F94F127B60; Fri, 15 Dec 2017 01:29:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 CSitWimxHe8U; Fri, 15 Dec 2017 01:29:26 -0800 (PST)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48091127599; Fri, 15 Dec 2017 01:29:26 -0800 (PST)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id D6CBE408EE; Fri, 15 Dec 2017 10:29:24 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.17]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 9F5CD1C0067; Fri, 15 Dec 2017 10:29:24 +0100 (CET)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM24.corporate.adroot.infra.ftgroup ([fe80::a1e6:3e6a:1f68:5f7e%18]) with mapi id 14.03.0361.001; Fri, 15 Dec 2017 10:29:24 +0100
From: <bruno.decraene@orange.com>
To: "Smith, Donald" <Donald.Smith@CenturyLink.com>, Job Snijders <job@ntt.net>
CC: "grow-chairs@ietf.org" <grow-chairs@ietf.org>, Ben Campbell <ben@nostrum.com>, "draft-ietf-grow-bgp-gshut@ietf.org" <draft-ietf-grow-bgp-gshut@ietf.org>, "grow@ietf.org" <grow@ietf.org>, "The IESG" <iesg@ietf.org>
Thread-Topic: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
Thread-Index: AQHTdJP90cSHHsziR0WKcqR14+JgtqNC5XiwgABXlIqAAAS3gIAA4J+A
Date: Fri, 15 Dec 2017 09:29:23 +0000
Message-ID: <25199_1513330164_5A3395F4_25199_77_1_53C29892C857584299CBF5D05346208A4792253E@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <151322570465.6210.17202569330170241275.idtracker@ietfa.amsl.com> <15461_1513262548_5A328DD4_15461_64_1_53C29892C857584299CBF5D05346208A47920D36@OPEXCLILM21.corporate.adroot.infra.ftgroup> <68EFACB32CF4464298EA2779B058889D53D3936E@PDDCWMBXEX503.ctl.intranet> <5142_1513274623_5A32BCFF_5142_246_1_53C29892C857584299CBF5D05346208A4792151C@OPEXCLILM21.corporate.adroot.infra.ftgroup>, <20171214193819.GS95845@vurt.meerval.net> <68EFACB32CF4464298EA2779B058889D53D3961F@PDDCWMBXEX503.ctl.intranet>
In-Reply-To: <68EFACB32CF4464298EA2779B058889D53D3961F@PDDCWMBXEX503.ctl.intranet>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/fw2_WVSsEy1KAUgszhxfc5rHrTU>
Subject: Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Dec 2017 09:29:29 -0000

> From: Smith, Donald [mailto:Donald.Smith@CenturyLink.com]
>=20
 >=20
 > if (initial_ttl!=3D255) then (rfc5082_compliant=3D=3D0)
 > Donald.Smith@centurylink.com
 >=20
 > >       ________________________________________
 > >       From: Job Snijders [job@ntt.net]
 > >       Sent: Thursday, December 14, 2017 12:38 PM
 > >       To: bruno.decraene@orange.com
 > >       Cc: Smith, Donald; grow-chairs@ietf.org; Ben Campbell; draft-iet=
f-grow-bgp-gshut@ietf.org;
 > grow@ietf.org; The IESG
 > >       Subject: Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gs=
hut-12: (with
 > COMMENT)
 > >
 > >       On Thu, Dec 14, 2017 at 06:03:42PM +0000, bruno.decraene@orange.=
com wrote:
 > >       > > From: Smith, Donald [mailto:Donald.Smith@CenturyLink.com]
 > >       >  > Sent: Thursday, December 14, 2017 6:13 PM
 > >       > >
 > >       >  > I don't see anything around MD5/TCPAO authentication.
 > >       >
 > >       > This is correct, but this is really not specific to this docum=
ent and
 > >       > the comment would apply to any information sent over BGP sessi=
on, and
 > >       > probably to most of IDR document extending the protocol with
 > >       > additional field or usage.  If there is a need to discuss this=
 all
 > >       > IETF document related to BGP, we can indeed add some text. Wou=
ld the
 > >       > following text be ok with you?
 > >       >
 > >       > "This document does not change any underlying security issues
 > >       > associated with any other BGP Communities mechanism.  Unless a
 > >       > transport that provides integrity is used for the BGP session,=
 the
 > >       > GRACEFUL_SHUTDOWN community may be added or removed by a man i=
n the
 > >       > middle. However, the harm would be lower than adding or removi=
ng an
 > >       > NLRI, or adding a NO_EXPORT or NO_ADVERTISE community. Hence t=
his does
 > >       > not constitute a new attack vector. Protection of the TCP sess=
ion used
 > >       > by BGP is discussed in section 5.1 of RFC 7454,  security sect=
ion of
 > >       > [RFC4271] and [RFC4272]."
 > >
 > >       I think the above is mostly good, but can be trimmed a little bi=
t. The
 > >       following is on point and covers aspects relevant to GRACEFUL_SH=
UTDOWN.
 > >
 > >           "This document does not change any underlying security issues
 > >           associated with any other BGP Communities mechanism. Unless a
 > >           transport that provides integrity is used for the BGP sessio=
n, the
 > >           GRACEFUL_SHUTDOWN community may be added or removed by a man=
 in the
 > >           middle."

OK.
Personally, I feel that the precision that this does not constitute a new a=
ttack vector was useful, but I can live without; at least while waiting for=
 the security review.=20

 > >       Kind regards,
 > >
 > >       Job
 >=20
 > Since in theory you could do this blindly (tcp slipping in the window), =
I would remove the MITM
 > and say by "unauthorized 3rd parties" or something like that.

Ok.
=20
 > Otherwise this is better than putting all the other security recommendat=
ions from other rfcs [4271,
 > 4272] so I support referencing them instead.
=20
Sorry, I'm not sure to follow. Are you fine with the text proposed by Job o=
r would you prefer adding references to the RFCs (i.e.  section 5.1 of RFC =
7454,  security section of [RFC4271] and [RFC4272].)

As draft -12 has just been IETF Last Called (again), in order to not create=
 a mess, I'll wait for the end of the last call before uploading a -13.

Thanks
--Bruno
=20
 >=20
 > This communication is the property of CenturyLink and may contain confid=
ential or privileged
 > information. Unauthorized use of this communication is strictly prohibit=
ed and may be unlawful.
 > If you have received this communication in error, please immediately not=
ify the sender by reply e-
 > mail and destroy all copies of the communication and any attachments.
 >=20


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Mon Dec 18 02:50:42 2017
Return-Path: <job@instituut.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAED5127517 for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 02:50:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level: 
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, UNPARSEABLE_RELAY=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 mvNncYaVyoAD for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 02:50:38 -0800 (PST)
Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) (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 A21B3126BFD for <grow@ietf.org>; Mon, 18 Dec 2017 02:50:38 -0800 (PST)
Received: by mail-wm0-f43.google.com with SMTP id f206so28376588wmf.5 for <grow@ietf.org>; Mon, 18 Dec 2017 02:50:38 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=nBx4n05nFU8ZN/cCthKRY0iAhQRBn8mkJXOMa4JtB+o=; b=QqO6KebMvGzCtujIHrg6FUG0yeENQZ88p2RTfjv0fDdMgJ9yH9nu3HgDGABnhT6ioy N5fwdCsEa7GgYBvgwGwm2nmCX2ViS829CxFP+rr34T2e+mGT2Q4nqFOPJQlYJ+jNUjpZ YWdHcZBjirmoLbb8rBKX0i+NhCtWjxLp6OWXgErXqnyVYS7sefhJzM/nBgdFuI5h0wQ0 /Gxw0fMKUvXlDhsYqsjnHDcRylhSmUcY7aqoXT86o0cdqXbSapDJxMBpCrJPJ3xoRH5L w+aQjCuE/zfehtAeqels20bH2qj1Z+vWXLAnX3VBjWuPBYZU3pY3GwIlO4kNm2mDs5wF gUYg==
X-Gm-Message-State: AKGB3mJ5dwjFLUFyedz2vXffBhLJXDQJ7Y3WFCNV+WapWxSdvYMVQg7Z pMuT5T8rKNbwWJqNSPFbk0jzlw==
X-Google-Smtp-Source: ACJfBotGM1IhriujexI8OqGMYMegbj5oyaaUvn4JzdlwTnEb2LSDpTcRFkf+HAJ6Fk9qzoH1tzFFVQ==
X-Received: by 10.80.145.154 with SMTP id g26mr29283105eda.140.1513594236867;  Mon, 18 Dec 2017 02:50:36 -0800 (PST)
Received: from vurt.meerval.net (vurt.meerval.net. [192.147.168.22]) by smtp.gmail.com with ESMTPSA id k19sm11184625ede.35.2017.12.18.02.50.35 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 18 Dec 2017 02:50:35 -0800 (PST)
Received: from localhost (vurt.meerval.net [local]) by vurt.meerval.net (OpenSMTPD) with ESMTPA id 37cb14bf; Mon, 18 Dec 2017 10:50:34 +0000 (UTC)
Date: Mon, 18 Dec 2017 10:50:34 +0000
From: Job Snijders <job@ntt.net>
To: grow@ietf.org
Message-ID: <20171218105034.GD43144@vurt.meerval.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/2FApL22TViXFdMvR1itCVHfUZwM>
Subject: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Dec 2017 10:50:41 -0000

Dear GROW,

After the gazillionth routing incident in which an IXP route server
amplified the problem, I think it is time we explore mechanisms to
improve accountability, auditability & make debugging easier.

It is common practise for route server operators to configure their
route server in such a way that the route server does not append its own
ASN to the AS_PATH attribute. Many IXPs view this practise as
justifiable because it gives them a competitive advantage over transit
providers.

RFC 7947 reasons "a route server does not participate in the process of
forwarding data between client routers", but meanwhile quite some IXPs
have more equipment and layer-2 hops as part of the forwarding path than
comparable IP networks for similar distances. [1] [2] [3] Does it even
matter that the route server device itself is not part of the
forwarding path? For all intents and purposes it is a BGP hop. The route
server is not under administrative control of the RS participants.

Whenever routing incidents occur, it takes considerable effort to
pinpoint which route server BGP speakers amplified the problem. Quite
some correlation & verification work is needed to reliably point out
which route server at what IXP contributed to the propagation of a
hijack or a route leak. If IXP route servers were visible in the
AS_PATH (just like normal IP networks), I think we'd see a lot more
responsible behavior and the implementations of route filters. 

Consider the following scenarios. When client A & client B at the same
IX have a bilateral session with each other, it doesn't matter whether
the route server injects its AS in the AS_PATH: the bilateral session
makes the route server control-plane path irrelevant. Since it is common
practise to assign a higher local preference to 'peering' routes
compared to 'transit' routes, in the case that client A & client B don't
have a bilateral session and only see each other via the route server,
padding the AS_PATH with the route servers ASN still won't have an
negative effect. It is only in corner cases that the AS_PATH becomes the
tie-breaker, and I find it hard to use those as justification to
sacrifice all of the route server's visibility.

Another benefit is that if route servers behave like normal BGP
speakers, client's dont need to disable safety checks such as "no bgp
enforce-first-as". Or that routing policy to match on prefixes coming
from the route server (on devices not connected to the IX) are simpler
if the ASN is vislble, and of course the same applies to analysis of MRT
dumps or use of BGP data in applications such as spam filtering. Or
think of hunting down announcements that became ghost routes, without
all ASNs visible in the AS_PATH as operator you'll be going through
severe pains to find the ghost route perpetrator.

Decades ago some argued that route servers should provide an experience
as close to bilateral peering as possible. But fast forward to 2017, we
see route servers with hundreds of thousands of paths, thousands of
sessions, in essence route servers became partial transit providers. I'd
argue that route server operators should assume their fiduciary duty and
stop hiding themselves. This will allow both operators & researchers to
more easily pinpoint issues, and help fix them.

In summary, I think RFC 7947 section 2.2.2.1 & 2.2.2.2 were misguided,
should be revisited, perhaps deleted. Thoughts?

Kind regards,

Job

[1]: https://ams-ix.net/technical/ams-ix-infrastructure
[2]: https://www.linx.net/tech-info-help/network-topology
[3]: https://www.nl-ix.net/network/projected-core-map-2017/


From nobody Mon Dec 18 03:41:22 2017
Return-Path: <hugge@nordu.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60E22124239 for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 03:41:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nordu.net
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 lCLyENzrrPGB for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 03:41:18 -0800 (PST)
Received: from e-mailfilter02.sunet.se (e-mailfilter02.sunet.se [IPv6:2001:6b0:8:2::202]) (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 F2525124B09 for <grow@ietf.org>; Mon, 18 Dec 2017 03:41:17 -0800 (PST)
Received: from smtp1.nordu.net (smtp1.nordu.net [109.105.111.32]) by e-mailfilter02.sunet.se (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id vBIBfDqt176554 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <grow@ietf.org>; Mon, 18 Dec 2017 12:41:14 +0100
Received: from kerio.nordu.net (kerio.nordu.net [109.105.113.41]) by smtp1.nordu.net (8.15.2/8.15.2) with ESMTPS id vBIBfAAZ028831 (version=TLSv1.1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO) for <grow@ietf.org>; Mon, 18 Dec 2017 11:41:13 GMT
X-Footer: bm9yZHUubmV0
Received: from hugges-macintosh.local ([109.105.104.135]) (authenticated user hugge@nordu.net) by kerio.nordu.net with ESMTPSA (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256 bits)) for grow@ietf.org; Mon, 18 Dec 2017 11:41:09 +0000
To: grow@ietf.org
References: <20171218105034.GD43144@vurt.meerval.net>
From: =?UTF-8?Q?Fredrik_Korsb=c3=a4ck?= <hugge@nordu.net>
Message-ID: <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net>
Date: Mon, 18 Dec 2017 12:41:07 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <20171218105034.GD43144@vurt.meerval.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Scanned-By: CanIt (www . roaringpenguin . com)
X-Scanned-By: MIMEDefang 2.78 on 109.105.111.32
X-Bayes-Prob: 0.0001 (Score 0, tokens from: outbound, outbound-nordu-net:default, nordu-net:default, base:default, @@RPTN)
X-p0f-Info: os=unknown unknown, link=Ethernet or modem
X-CanIt-Geo: ip=109.105.113.41; country=SE; latitude=59.3247; longitude=18.0560; http://maps.google.com/maps?q=59.3247,18.0560&z=6
X-CanItPRO-Stream: outbound-nordu-net:outbound (inherits from outbound-nordu-net:default, nordu-net:default, base:default)
X-Canit-Stats-ID: 0aULnFdPE - 7798802d12c1 - 20171218
X-CanIt-Archive-Cluster: PfMRe/vJWMiXwM2YIH5BVExnUnw
Received-SPF: neutral (e-mailfilter02.sunet.se: 109.105.113.41 is neither permitted nor denied by domain hugge@nordu.net) receiver=e-mailfilter02.sunet.se; client-ip=109.105.113.41; envelope-from=<hugge@nordu.net>; helo=smtp1.nordu.net; identity=mailfrom
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=nordu.net; h=subject:to :references:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; s=canit; bh=EK19/a/SCkS DWZhIsBjvu/wdQ9mBrpy3sMs2u4EOnYY=; b=bmIpZIfULX2UZd8SogolsD0pJqu 86gqkyrn4ct+IX3/QV8jhyypbLmkEjjk/j6b+dPpqVZgDNqV5T+7Cbv5LZTiJIRc 3FwstA0r7NPnQSxWAg01DpMjWdXuyyJmmIizmOEezgiOfdo0Z7uFRoe2CRa4aMj6 eb5HVQyai/0le98VKhqNB87aITZhUJBW2zO8sqEhY9E37NlHJXkJTn65ibxRlUEk DBsa2Cf8Ln6s8cWSqmQ9vyUNqOoZyjtCPPj6FSqboZ6StebiBE04+USyyrrqXHFM qvyZokXAX2uI4WGIKY+hntbLaj1DC8J3DP3tKmq026D1DcIKG/Zn4yCFDrQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/8w-CBlyLruC2ysW_iYMe9VbBpbk>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Dec 2017 11:41:21 -0000

On 2017-12-18 11:50, Job Snijders wrote:
> Dear GROW,
> 
> After the gazillionth routing incident in which an IXP route server
> amplified the problem, I think it is time we explore mechanisms to
> improve accountability, auditability & make debugging easier.
> 
> It is common practise for route server operators to configure their
> route server in such a way that the route server does not append its own
> ASN to the AS_PATH attribute. Many IXPs view this practise as
> justifiable because it gives them a competitive advantage over transit
> providers.
> 
> RFC 7947 reasons "a route server does not participate in the process of
> forwarding data between client routers", but meanwhile quite some IXPs
> have more equipment and layer-2 hops as part of the forwarding path than
> comparable IP networks for similar distances. [1] [2] [3] Does it even
> matter that the route server device itself is not part of the
> forwarding path? For all intents and purposes it is a BGP hop. The route
> server is not under administrative control of the RS participants.
> 
> Whenever routing incidents occur, it takes considerable effort to
> pinpoint which route server BGP speakers amplified the problem. Quite
> some correlation & verification work is needed to reliably point out
> which route server at what IXP contributed to the propagation of a
> hijack or a route leak. If IXP route servers were visible in the
> AS_PATH (just like normal IP networks), I think we'd see a lot more
> responsible behavior and the implementations of route filters.
> 
> Consider the following scenarios. When client A & client B at the same
> IX have a bilateral session with each other, it doesn't matter whether
> the route server injects its AS in the AS_PATH: the bilateral session
> makes the route server control-plane path irrelevant. Since it is common
> practise to assign a higher local preference to 'peering' routes
> compared to 'transit' routes, in the case that client A & client B don't
> have a bilateral session and only see each other via the route server,
> padding the AS_PATH with the route servers ASN still won't have an
> negative effect. It is only in corner cases that the AS_PATH becomes the
> tie-breaker, and I find it hard to use those as justification to
> sacrifice all of the route server's visibility.
> 
> Another benefit is that if route servers behave like normal BGP
> speakers, client's dont need to disable safety checks such as "no bgp
> enforce-first-as". Or that routing policy to match on prefixes coming
> from the route server (on devices not connected to the IX) are simpler
> if the ASN is vislble, and of course the same applies to analysis of MRT
> dumps or use of BGP data in applications such as spam filtering. Or
> think of hunting down announcements that became ghost routes, without
> all ASNs visible in the AS_PATH as operator you'll be going through
> severe pains to find the ghost route perpetrator.
> 
> Decades ago some argued that route servers should provide an experience
> as close to bilateral peering as possible. But fast forward to 2017, we
> see route servers with hundreds of thousands of paths, thousands of
> sessions, in essence route servers became partial transit providers. I'd
> argue that route server operators should assume their fiduciary duty and
> stop hiding themselves. This will allow both operators & researchers to
> more easily pinpoint issues, and help fix them.
> 
> In summary, I think RFC 7947 section 2.2.2.1 & 2.2.2.2 were misguided,
> should be revisited, perhaps deleted. Thoughts?
> 
> Kind regards,
> 
> Job
> 
> [1]: https://ams-ix.net/technical/ams-ix-infrastructure
> [2]: https://www.linx.net/tech-info-help/network-topology
> [3]: https://www.nl-ix.net/network/projected-core-map-2017/
> 

Hi.

This makes alot of sense actually. Now that we live in a world where a route-server and an IXP is not what it used to be 
we need to consider IXPs as any ISP out there. Heck, some of these IXPs runs bigger infrastructures then most of their 
customers do.

Injecting the RS asn into the path makes troubleshooting much easier and helps us understand the routingt-able alot 
better, and having a RS ASN show up when backtracking an incident on f.e BGP Play will shorten the lead-time to figuring 
out what actually happened significantly.

I do see a problem however that we kinda need to change this all at the same time to not get very wonky routing for 
those relying heavily on routeservers  - this i have no idea how to coordinate.

but should it be done? Yes it should




-- 
hugge


From nobody Mon Dec 18 05:04:11 2017
Return-Path: <nick@foobar.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CC71128C0A for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 05:04:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, 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 rIHXPT20hm-L for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 05:04:08 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A97A212895E for <grow@ietf.org>; Mon, 18 Dec 2017 05:04:07 -0800 (PST)
X-Envelope-To: grow@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id vBID44np029717 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Dec 2017 13:04:05 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
Message-ID: <5A37BCC3.8040008@foobar.org>
Date: Mon, 18 Dec 2017 13:04:03 +0000
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.22 (Macintosh/20171208)
MIME-Version: 1.0
To: Job Snijders <job@ntt.net>
CC: grow@ietf.org
References: <20171218105034.GD43144@vurt.meerval.net>
In-Reply-To: <20171218105034.GD43144@vurt.meerval.net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/tcLIVgbY9aGZG401zdpnZ-nzajg>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Dec 2017 13:04:10 -0000

Job Snijders wrote:
> After the gazillionth routing incident in which an IXP route server
> amplified the problem, I think it is time we explore mechanisms to
> improve accountability, auditability & make debugging easier.

you missed the term "misconfigured" or "malconfigured" when describing
the route server in question.

> It is common practise for route server operators to configure their
> route server in such a way that the route server does not append its own
> ASN to the AS_PATH attribute. Many IXPs view this practise as
> justifiable because it gives them a competitive advantage over transit
> providers.

It's also common practice for transit providers to use a single ASN
spanning the globe e.g. 174, 2914, 3356, etc. What you're describing
here is an aspect of the fact that that as-pathlen has not been a useful
determinant for the bgp decision engine for many years.

> RFC 7947 reasons "a route server does not participate in the process of
> forwarding data between client routers", but meanwhile quite some IXPs
> have more equipment and layer-2 hops as part of the forwarding path than
> comparable IP networks for similar distances.

tbh, most don't - the vast majority are localised to well-constrained
metro areas and keep local interconnection local.  It would be unhelpful
to this majority if observations were made about one type of IXP, and
and extrapolations were imposed on topologically dissimilar platforms.

> In summary, I think RFC 7947 section 2.2.2.1 & 2.2.2.2 were misguided,
> should be revisited, perhaps deleted. Thoughts?

Updating rfc4271 would be more productive - and getting IXPs to filter
ingress bgp feeds by default.

Nick


From nobody Mon Dec 18 05:13:13 2017
Return-Path: <job@instituut.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE87E129C56 for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 05:13:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.23
X-Spam-Level: 
X-Spam-Status: No, score=0.23 tagged_above=-999 required=5 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=no 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 SsrcWf0WNpyZ for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 05:13:11 -0800 (PST)
Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.50]) (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 C9B91129966 for <grow@ietf.org>; Mon, 18 Dec 2017 05:13:10 -0800 (PST)
Received: by mail-wm0-f50.google.com with SMTP id t8so29048815wmc.3 for <grow@ietf.org>; Mon, 18 Dec 2017 05:13:10 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=crsgWxxzuEXlk5LShY6jHw+szH8PJnZpuCq8m4GzRzU=; b=XqaJ5oQNethvtQc2x9Ye4gxkgviNjqMTBOvymdfllrLP4QyZuOaOEKuCRFSxyNDqU0 mQtkhpuNxx4PQq7WNuariQeLCseyeRt576BfDUpqaqMU4tjWI2ePDW9NtUfF6tq+hFB9 f/qFRjNogK/xK5eSvbB5Q7r3cZTlieetFJido3J/JBFndarpbffcz0OJq0HdfmePIvbX gb+KpkTPu5LQL47DuvbgsO0JGFX1YDedPd58cDLOH8cjbdyhbktCbme08vDJUUf3SKsS W22bz9m0KKW0AuQ0VVk+13EkReRLEiRIF3ViqKs+CyibLX9NvTi0SIgLgzKXBXLlu+kW jflw==
X-Gm-Message-State: AKGB3mK2r/los619D847+P9oxNozTscYlr0FxATOLndknvPMwuyLk3ZV 3t5PVwEtYnjiJtlB9sRZJaWSDA==
X-Google-Smtp-Source: ACJfBouE9sCFIg8ZlZpGC4ayiCHRvsT6ptRoI8Yde/yosN9OrkOCqkbbFWlKT7XlOibfoQgSdl0XfQ==
X-Received: by 10.80.158.196 with SMTP id a62mr29524280edf.307.1513602789052;  Mon, 18 Dec 2017 05:13:09 -0800 (PST)
Received: from localhost ([2001:67c:208c:10:e938:68b3:3dfe:7a6d]) by smtp.gmail.com with ESMTPSA id m23sm10732407edc.27.2017.12.18.05.13.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Dec 2017 05:13:07 -0800 (PST)
Date: Mon, 18 Dec 2017 14:13:06 +0100
From: Job Snijders <job@ntt.net>
To: Nick Hilliard <nick@foobar.org>
Cc: grow@ietf.org
Message-ID: <20171218131306.GB1009@hanna.meerval.net>
References: <20171218105034.GD43144@vurt.meerval.net> <5A37BCC3.8040008@foobar.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5A37BCC3.8040008@foobar.org>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.9.1 (2017-09-22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/uWAmJKsB77Z1KUtO3vf5YZogNps>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Dec 2017 13:13:12 -0000

Hi Nick,

On Mon, Dec 18, 2017 at 01:04:03PM +0000, Nick Hilliard wrote:
> Job Snijders wrote:
> > After the gazillionth routing incident in which an IXP route server
> > amplified the problem, I think it is time we explore mechanisms to
> > improve accountability, auditability & make debugging easier.
> 
> you missed the term "misconfigured" or "malconfigured" when describing
> the route server in question.

Which route server in question? They are close to invisible. :)

> > It is common practise for route server operators to configure their
> > route server in such a way that the route server does not append its
> > own ASN to the AS_PATH attribute. Many IXPs view this practise as
> > justifiable because it gives them a competitive advantage over
> > transit providers.
> 
> It's also common practice for transit providers to use a single ASN
> spanning the globe e.g. 174, 2914, 3356, etc. What you're describing
> here is an aspect of the fact that that as-pathlen has not been a
> useful determinant for the bgp decision engine for many years.

A common deployment strategy is that folks connect 2 transit providers
and an IXP, and uppref whatever is announced via the IXP. Since LP wins
over AS_PATH lenght, I maintain that for the common use case the
addition of the route server's ASN in the AS_PATH has no negative
effects and quite some positive effects.

> > RFC 7947 reasons "a route server does not participate in the process
> > of forwarding data between client routers", but meanwhile quite some
> > IXPs have more equipment and layer-2 hops as part of the forwarding
> > path than comparable IP networks for similar distances.
> 
> tbh, most don't - the vast majority are localised to well-constrained
> metro areas and keep local interconnection local.  It would be
> unhelpful to this majority if observations were made about one type of
> IXP, and and extrapolations were imposed on topologically dissimilar
> platforms.

I don't think smaller IXPs are any less susceptible to problems than
large IXPs. In both instances it is helpful if there is visibility on
what AS (and who is in administrative control of that BGP speaker) was
involved.

Even IXPs that indicate they apply ingress filters could suffer from
software bugs (ghost routes) or filtering issues. In those type of cases
having better visiblity is of tremendous value.

And of course, if the AS_PATH length tie-breaker _does_ make for
concerns, people can (and will) set up direct bilateral sessions with
each other.

> > In summary, I think RFC 7947 section 2.2.2.1 & 2.2.2.2 were
> > misguided, should be revisited, perhaps deleted. Thoughts?
> 
> Updating rfc4271 would be more productive

What kind of update would you suggest?

> - and getting IXPs to filter ingress bgp feeds by default.

It would be great if we can easily identify which IXPs are not
filtering.

Kind regards,

Job


From nobody Mon Dec 18 06:44:20 2017
Return-Path: <martijnschmidt@i3d.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0B5812D7E4 for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 06:44:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=i3d.net
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 JIZoxqHZ140t for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 06:44:15 -0800 (PST)
Received: from mail.i3d.net (mail.i3d.nl [213.163.77.240]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C5B7124B17 for <grow@ietf.org>; Mon, 18 Dec 2017 06:44:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=i3d.net; s=mail; h=from:subject:date:message-id:to:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=lxddjbDBL0XVzqhzwY15kYzVpPb4h2pnMuS4LrmwGkQ=; b=smHvXZil/2466z5VCSgRjCuqUC0nYRUD8ACkQXNb4J/enlpfDoKc4vpKx0oy0VYEzlJz26cx4lcCq pYI4H6KH4r0AQzEnQFhVXiEtF4vEpIhoX0SSIOIuaV0ecczUlgMQh1ywlekPRmg4dzaYAUGJxAZ8fF uxyPxnYBmWLdQXgjXV1kXTTyrUs7lEpDwOV8qAgy5+0djADSlETenJeYbr4p+MFdpkFnrBFDzeaO3b ObaTO0Ja4etaujbVFa0Z1Om1/rS9TUEhGH5enVKDYUt4+6r6KhYQmT+yw3DCRWGtz/GBxlMCBnxLoa 2Pe1zZsutANh1rf6c4wxg7M4zbI5g4g==
X-Footer: aTNkLm5s
Received: from localhost ([127.0.0.1]) by mail.i3d.net with ESMTPSA (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256 bits)); Mon, 18 Dec 2017 13:23:30 +0100
To: =?UTF-8?Q?Fredrik_Korsb=c3=a4ck?= <hugge@nordu.net>, grow@ietf.org, "i3D.net - Martijn Schmidt" <martijnschmidt@i3d.net>
References: <20171218105034.GD43144@vurt.meerval.net> <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net>
From: "i3D.net - Martijn Schmidt" <martijnschmidt@i3d.net>
Organization: i3D.net
Message-ID: <36e13c57-ac32-9fe9-ef31-e59ab1bc0c21@i3d.net>
Date: Mon, 18 Dec 2017 13:23:29 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/lxWci4vkRnPeeIWrE__TFIDmVVU>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Dec 2017 14:44:18 -0000

Dear Job, Fredrik,

I disagree. The last thing we need is for IXPs to randomly begin
applying new "inject one's own ASN into AS_PATH" behaviour to their
routeservers - anything which deviates from the de-facto standard will
result in a lot of time spent with IXPs working on migrating to the new
thing. Just look at all the effort it takes to get a no-brainer like
proper ingress route filtering pushed through..

I'm happy that everything has finally gotten to the point where
route-servers consistently apply the AS_PATH stripping behaviour - and I
consider it a reason _not_ to participate in the route-servers if their
ASN is still visible in the AS_PATH. For example, this proposed change
would wreak a lot of havoc on those networks with a wide geographical
footprint relying on consistent route announcements to ensure traffic
doesn't experience scenic routing. During the migration period, longhaul
traffic would be all over the place as a result of the differing AS_PATH
lengths that are seen at the various ingress points of an autonomous
system participating in route-servers.

What I _would_ support is a semi-standardized or well-known BGP
community to indicate whether a prefix was, at some point in its
lifecycle, propagated by a routeserver on an IXP. Better yet, a BGP
Large Community so that it's not stripped by other "community-filtering"
networks before it reaches a point where the route can be stored into a
database for later forensics.

Best regards,
Martijn Schmidt

On 18-12-17 12:41, Fredrik Korsbäck wrote:
> On 2017-12-18 11:50, Job Snijders wrote:
>> Dear GROW,
>>
>> After the gazillionth routing incident in which an IXP route server
>> amplified the problem, I think it is time we explore mechanisms to
>> improve accountability, auditability & make debugging easier.
>>
>> It is common practise for route server operators to configure their
>> route server in such a way that the route server does not append its own
>> ASN to the AS_PATH attribute. Many IXPs view this practise as
>> justifiable because it gives them a competitive advantage over transit
>> providers.
>>
>> RFC 7947 reasons "a route server does not participate in the process of
>> forwarding data between client routers", but meanwhile quite some IXPs
>> have more equipment and layer-2 hops as part of the forwarding path than
>> comparable IP networks for similar distances. [1] [2] [3] Does it even
>> matter that the route server device itself is not part of the
>> forwarding path? For all intents and purposes it is a BGP hop. The route
>> server is not under administrative control of the RS participants.
>>
>> Whenever routing incidents occur, it takes considerable effort to
>> pinpoint which route server BGP speakers amplified the problem. Quite
>> some correlation & verification work is needed to reliably point out
>> which route server at what IXP contributed to the propagation of a
>> hijack or a route leak. If IXP route servers were visible in the
>> AS_PATH (just like normal IP networks), I think we'd see a lot more
>> responsible behavior and the implementations of route filters.
>>
>> Consider the following scenarios. When client A & client B at the same
>> IX have a bilateral session with each other, it doesn't matter whether
>> the route server injects its AS in the AS_PATH: the bilateral session
>> makes the route server control-plane path irrelevant. Since it is common
>> practise to assign a higher local preference to 'peering' routes
>> compared to 'transit' routes, in the case that client A & client B don't
>> have a bilateral session and only see each other via the route server,
>> padding the AS_PATH with the route servers ASN still won't have an
>> negative effect. It is only in corner cases that the AS_PATH becomes the
>> tie-breaker, and I find it hard to use those as justification to
>> sacrifice all of the route server's visibility.
>>
>> Another benefit is that if route servers behave like normal BGP
>> speakers, client's dont need to disable safety checks such as "no bgp
>> enforce-first-as". Or that routing policy to match on prefixes coming
>> from the route server (on devices not connected to the IX) are simpler
>> if the ASN is vislble, and of course the same applies to analysis of MRT
>> dumps or use of BGP data in applications such as spam filtering. Or
>> think of hunting down announcements that became ghost routes, without
>> all ASNs visible in the AS_PATH as operator you'll be going through
>> severe pains to find the ghost route perpetrator.
>>
>> Decades ago some argued that route servers should provide an experience
>> as close to bilateral peering as possible. But fast forward to 2017, we
>> see route servers with hundreds of thousands of paths, thousands of
>> sessions, in essence route servers became partial transit providers. I'd
>> argue that route server operators should assume their fiduciary duty and
>> stop hiding themselves. This will allow both operators & researchers to
>> more easily pinpoint issues, and help fix them.
>>
>> In summary, I think RFC 7947 section 2.2.2.1 & 2.2.2.2 were misguided,
>> should be revisited, perhaps deleted. Thoughts?
>>
>> Kind regards,
>>
>> Job
>>
>> [1]: https://ams-ix.net/technical/ams-ix-infrastructure
>> [2]: https://www.linx.net/tech-info-help/network-topology
>> [3]: https://www.nl-ix.net/network/projected-core-map-2017/
>>
>
> Hi.
>
> This makes alot of sense actually. Now that we live in a world where a
> route-server and an IXP is not what it used to be we need to consider
> IXPs as any ISP out there. Heck, some of these IXPs runs bigger
> infrastructures then most of their customers do.
>
> Injecting the RS asn into the path makes troubleshooting much easier
> and helps us understand the routingt-able alot better, and having a RS
> ASN show up when backtracking an incident on f.e BGP Play will shorten
> the lead-time to figuring out what actually happened significantly.
>
> I do see a problem however that we kinda need to change this all at
> the same time to not get very wonky routing for those relying heavily
> on routeservers  - this i have no idea how to coordinate.
>
> but should it be done? Yes it should 


From nobody Mon Dec 18 07:07:04 2017
Return-Path: <nick@foobar.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4360E1270AC for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 07:07:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, 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 UAYRHgLF6m8c for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 07:07:00 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72BE91205D3 for <grow@ietf.org>; Mon, 18 Dec 2017 07:07:00 -0800 (PST)
X-Envelope-To: grow@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id vBIF6vi5045148 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Dec 2017 15:06:57 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
Message-ID: <5A37D990.2060505@foobar.org>
Date: Mon, 18 Dec 2017 15:06:56 +0000
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.22 (Macintosh/20171208)
MIME-Version: 1.0
To: Job Snijders <job@ntt.net>
CC: grow@ietf.org
References: <20171218105034.GD43144@vurt.meerval.net>
In-Reply-To: <20171218105034.GD43144@vurt.meerval.net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/7FYlWn0Wj9Gvxwkc3XjyRy7IahE>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Dec 2017 15:07:03 -0000

Job Snijders wrote:
> It is common practise for route server operators to configure their
> route server in such a way that the route server does not append its own
> ASN to the AS_PATH attribute. Many IXPs view this practise as
> justifiable because it gives them a competitive advantage over transit
> providers.

This is both incorrect and mildly pejorative. The justification for
stripping the RS-ASN is that multilateral peering is (mostly)
functionally equivalent to bilateral peering.  If the RS-ASN is injected
into the AS path, then they become substantially non-equivalent, and
bilateral peering sessions become preferred.

This is not ideal: it's extremely unusual for bilateral peering over an
ixp ever to have any filtering, so if you push IXPs to inject the route
server ASN, this will create pressure to implement more bilateral
peering and consequently more problems in the longer term, which are
effectively impossible to deal with.

I can see why you think that injecting the rsasn into the as-path is
alluring, but be careful what you wish for, because fiddling with this
will have consequences which extend far outside your assumed scope.

At least in most cases, it's pretty straightforward these days to
implement route servers with full, dynamically rebuilt filtering out of
the box.  The technical work has been done.  What's left is to get the
remaining IXPs which don't filter their inbound prefixes to deploy this.

Nick


From nobody Mon Dec 18 07:07:48 2017
Return-Path: <job@instituut.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 072A31205D3 for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 07:07:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.249
X-Spam-Level: 
X-Spam-Status: No, score=0.249 tagged_above=-999 required=5 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=no 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 1r_VYOhs5SFf for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 07:07:45 -0800 (PST)
Received: from mail-wr0-f172.google.com (mail-wr0-f172.google.com [209.85.128.172]) (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 B4DCB1201F8 for <grow@ietf.org>; Mon, 18 Dec 2017 07:07:44 -0800 (PST)
Received: by mail-wr0-f172.google.com with SMTP id u19so7980698wrc.3 for <grow@ietf.org>; Mon, 18 Dec 2017 07:07:44 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Zk1oZcd3mOx73iKxqbImbaQ8fpnIZ0zRwvr6tgKhH1A=; b=J+NZa6TMEgGX/l1w4NM2R/SBYjWMimOPnFQRrt6DXNpjgyj24PvZu+59xa6ZJfs9PM L6m1Pibw3dmWsaK4emgDDrzIll6NolXvhkqvuyKPOPl2DvscdgF4vsVDyzDzxs9QNdDA rnt/S+JbGzjeCh5yh/HYZmxYnYyF54gUiG0B7k/sSrPut8OfFH9JGjUSsMyQ4LUE1oZQ UPXADJkFEdALdfiJbLyMUdI2ADabTOPnBPw1uFGylUI5Yl3ApyPQFd0OXF/1SWPLVGJD 4f3KNtg73AvCUIsiQd/yfsQ2jZqx5VQDeEpiWaqoVXnpSFcXmPvrYa/t0LIjh8zWsbtx NV0A==
X-Gm-Message-State: AKGB3mI8WJctS//Z2qAz3TWVw7Pw7Py+OHeNGz1H09GZj5vrAhwsmWLA 0nzBiW2u30EYLFk+Ssjeo0EBFwsrJu8=
X-Google-Smtp-Source: ACJfBos8xKhDjrt62Ov4MOrhyABZ1IhNhp6BM51WxCEn2tnNHuq0c9R1noKpqsIrni7RAZg5OSXYWA==
X-Received: by 10.223.198.3 with SMTP id n3mr16974wrg.73.1513609662985; Mon, 18 Dec 2017 07:07:42 -0800 (PST)
Received: from localhost ([2001:67c:208c:10:e938:68b3:3dfe:7a6d]) by smtp.gmail.com with ESMTPSA id g45sm11832022eda.88.2017.12.18.07.07.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Dec 2017 07:07:42 -0800 (PST)
Date: Mon, 18 Dec 2017 16:07:41 +0100
From: Job Snijders <job@ntt.net>
To: "i3D.net - Martijn Schmidt" <martijnschmidt@i3d.net>
Cc: Fredrik =?iso-8859-1?Q?Korsb=E4ck?= <hugge@nordu.net>, grow@ietf.org
Message-ID: <20171218150741.GC1009@hanna.meerval.net>
References: <20171218105034.GD43144@vurt.meerval.net> <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net> <36e13c57-ac32-9fe9-ef31-e59ab1bc0c21@i3d.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <36e13c57-ac32-9fe9-ef31-e59ab1bc0c21@i3d.net>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.9.1 (2017-09-22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/JKCJMHrIk1axs9k5G2xPd9gZLV4>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Dec 2017 15:07:46 -0000

Dear Martijn,

On Mon, Dec 18, 2017 at 01:23:29PM +0100, i3D.net - Martijn Schmidt wrote:
> I disagree. The last thing we need is for IXPs to randomly begin
> applying new "inject one's own ASN into AS_PATH" behaviour to their
> routeservers 

Interesting use of the word 'randomly'! :)

> - anything which deviates from the de-facto standard will result in a
> lot of time spent with IXPs working on migrating to the new thing.
> Just look at all the effort it takes to get a no-brainer like proper
> ingress route filtering pushed through..

Right now some IXPs are using the IETF RFCs as a justification to not
hide their ASN in the AS_PATH - and unfortunately some of them gloss
over the recommendations to apply ingress filters. I don't see a need to
continue endorsing a practise that doesn't benefit the Internet as
whole: people cherry-pick from the RFCs, there isn't much we can do
about that. But we can at least ensure that the the set of documents
describes an operating mode that allows others to do troubleshooting,
and ensures there is a degree of visiblity.

I mentioned before, I suspect that the route server's lack of visiblity
is a direct contributor to the reluctance to apply filters on route
servers. We can often observe that improved transparency leads to
improved operations.

Participants of the routing eco system that don't hold the best interest
of all other participants at heart should at least be visible so that
their choices can be researched.

> I'm happy that everything has finally gotten to the point where
> route-servers consistently apply the AS_PATH stripping behaviour - and
> I consider it a reason _not_ to participate in the route-servers if
> their ASN is still visible in the AS_PATH. For example, this proposed
> change would wreak a lot of havoc on those networks with a wide
> geographical footprint relying on consistent route announcements to
> ensure traffic doesn't experience scenic routing. During the migration
> period, longhaul traffic would be all over the place as a result of
> the differing AS_PATH lengths that are seen at the various ingress
> points of an autonomous system participating in route-servers.

I think you are somewhat overestimating the consequences. The internet
is constantly in flux and peers come & go at internet exchanges and
route servers. Already today you'll be monitoring for performance and
deploying routing policy accordingly. If one IXP has a route server
which inserts their ASN in the AS_PATH, and another doesn't (AND this
affects your business), you can just as easily level the playing field
by prepending the RS ASN yourself.

At this point in time most route servers can be considered the
equivalent of a medimum to large sized regional operator. We don't ask
normal IP transit networks to strip their ASN either. A route server
adding its ASN to the AS_PATH is not the end of the world - quite the
opposite - it enables others to make better choices.

> What I _would_ support is a semi-standardized or well-known BGP
> community to indicate whether a prefix was, at some point in its
> lifecycle, propagated by a routeserver on an IXP. Better yet, a BGP
> Large Community so that it's not stripped by other
> "community-filtering" networks before it reaches a point where the
> route can be stored into a database for later forensics.

Communities propagate less reliably compared to AS_PATH.

Some brought up in offlist conversations that the value of a route
server is that a new participant of the internet exchange will glean
immediate value from connecting to the IXP. These benefits and this
concept does not change one jot if the route server presents itself as
like any normal BGP speaker. It would be very strange to operate under
the mode that route servers immediately become worthless if 1 ASN is
added to the AS_PATH.

Networks that operate on a global scale will have to make their own
considerations anyhow as to how they their traffic distribution. Some
have a backbone, some don't. Whenever the exchange of traffic becomes a
more complex question, parties are expected to set up direct bilateral
sessions anyhow. Route servers being a more visible part of the
ecosystem doesn't change that.

Kind regards,

Job


From nobody Mon Dec 18 07:33:00 2017
Return-Path: <nick@foobar.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30CDA127369 for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 07:32:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, 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 cfXcZkKg9MJq for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 07:32:57 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5147B12708C for <grow@ietf.org>; Mon, 18 Dec 2017 07:32:57 -0800 (PST)
X-Envelope-To: grow@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id vBIFWE51048886 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Dec 2017 15:32:15 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
Message-ID: <5A37DF7D.9040405@foobar.org>
Date: Mon, 18 Dec 2017 15:32:13 +0000
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.22 (Macintosh/20171208)
MIME-Version: 1.0
To: Job Snijders <job@ntt.net>
CC: "i3D.net - Martijn Schmidt" <martijnschmidt@i3d.net>, grow@ietf.org
References: <20171218105034.GD43144@vurt.meerval.net> <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net> <36e13c57-ac32-9fe9-ef31-e59ab1bc0c21@i3d.net> <20171218150741.GC1009@hanna.meerval.net>
In-Reply-To: <20171218150741.GC1009@hanna.meerval.net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/tHLixEnsUzDhHtjdUXHeGNMNDzg>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Dec 2017 15:32:59 -0000

Job Snijders wrote:
> Right now some IXPs are using the IETF RFCs as a justification to not
> hide their ASN in the AS_PATH - and unfortunately some of them gloss
> over the recommendations to apply ingress filters. 

the two RS RFCs are split: one is a specification of what BGP must do,
and the other is a recommendation on operational issues.  Glossing over
the fact that IXP operators have not been inserting the rsasn since the
mid 1990s and that the RFCs are dated 2016, the document that IXPs need
to use is the operations doc: rfc7948, which says that RSs should be
operated in compliance with all the bits of rfc7454 that talk about
filtering. Stopping routing leaks is the aim of the game here.

> I mentioned before, I suspect that the route server's lack of visiblity
> is a direct contributor to the reluctance to apply filters on route
> servers.

Job, seriously, if you have helpful or useful comments to make, then
please make them.

Nick


From nobody Mon Dec 18 07:37:01 2017
Return-Path: <job@instituut.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86ED61289B0 for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 07:37:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.249
X-Spam-Level: 
X-Spam-Status: No, score=0.249 tagged_above=-999 required=5 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=no 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 k38WUDuWLaD8 for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 07:36:59 -0800 (PST)
Received: from mail-wr0-f175.google.com (mail-wr0-f175.google.com [209.85.128.175]) (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 7953F127369 for <grow@ietf.org>; Mon, 18 Dec 2017 07:36:59 -0800 (PST)
Received: by mail-wr0-f175.google.com with SMTP id u19so8108131wrc.3 for <grow@ietf.org>; Mon, 18 Dec 2017 07:36:59 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=+80TpTinv84l/uLwXpbjwtEt8tcIb/AvkANiBKSEuvg=; b=P2gIjMpEf1Ssfg7RHPi9Qz0ITL7arQgv+6TaosERuNrYUBo/kO2yO9uGLMtPXQ7gso zEhko20L8bAomjR8s3ghduSHcJpu8MHcEokOBBXvogD+mAEIN97clH96ai3A/mfT21KT c92URbrDo6D1l5sgQ3kQi2bA9BlLwmVnaKsthEfP63DUP75dKEP7x1bE5tEmwDDQKRmm 7awupZJ3gRqkVhFr/rJ5OCCJVnnRd4+KXABigEY/dV/f6YUCScijU+bhl8sUdR5XqCmI Xs3yVjmi3ZQswuheRkLDR6deVCscTtZQuTZ3AZ49tvRjhb/VVjQaQB5QOCJbF6setMqW GFUA==
X-Gm-Message-State: AKGB3mIcGGOi4OILEq28OeeKeY+hojZpALcc8y6mtZxRamwGW5KmM8R5 zsOOWdm7Yuom0xSmS0vLAookGNAPAaw=
X-Google-Smtp-Source: ACJfBos8Fz+iu449IbBsxdqXtjYJ9+WZjd8KLeBQNnCL6CNseAfeOwYEPE6hSFPKPXDcneO+Dw2ZPg==
X-Received: by 10.223.184.244 with SMTP id c49mr178999wrg.18.1513611417610; Mon, 18 Dec 2017 07:36:57 -0800 (PST)
Received: from localhost ([2001:67c:208c:10:e938:68b3:3dfe:7a6d]) by smtp.gmail.com with ESMTPSA id j27sm13628716eda.59.2017.12.18.07.36.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Dec 2017 07:36:56 -0800 (PST)
Date: Mon, 18 Dec 2017 16:36:56 +0100
From: Job Snijders <job@ntt.net>
To: Nick Hilliard <nick@foobar.org>
Cc: grow@ietf.org
Message-ID: <20171218153656.GD1009@hanna.meerval.net>
References: <20171218105034.GD43144@vurt.meerval.net> <5A37D990.2060505@foobar.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5A37D990.2060505@foobar.org>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.9.1 (2017-09-22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/wdhNt9kFsxou6kjIEy_H-gJey2o>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Dec 2017 15:37:00 -0000

Hi Nick,

On Mon, Dec 18, 2017 at 03:06:56PM +0000, Nick Hilliard wrote:
> Job Snijders wrote:
> > It is common practise for route server operators to configure their
> > route server in such a way that the route server does not append its
> > own ASN to the AS_PATH attribute. Many IXPs view this practise as
> > justifiable because it gives them a competitive advantage over
> > transit providers.
> 
> This is both incorrect and mildly pejorative. The justification for
> stripping the RS-ASN is that multilateral peering is (mostly)
> functionally equivalent to bilateral peering.

Which part is incorrect? The desire for functional equivalence with
bilateral peering, stems from the desire to be able to compete with
transit while at the same time providing a convenience service to the IX
participants (reduced workload by aggregating many sessions onto a
select few sessions). I don't view this is not a bad thing, internet
exchanges have brought significant improvements around the world.

> If the RS-ASN is injected into the AS path, then they become
> substantially non-equivalent, and bilateral peering sessions become
> preferred. This is not ideal: it's extremely unusual for bilateral
> peering over an ixp ever to have any filtering, 

If bilateral sessions exist in addition to the multilateral sessions,
the point is moot anyhow. If the RS blocks an invalid announcement,
it'll pass via the bilateral session.

> so if you push IXPs to inject the route server ASN, this will create
> pressure to implement more bilateral peering and consequently more
> problems in the longer term, which are effectively impossible to deal
> with.

It does not follows that insertion of an ASN in the AS_PATH will create
pressure to set up bilateral sessions. People have always had a choice
whether to use multiateral or bilateral or both, the set of options
doesn't change.

> I can see why you think that injecting the rsasn into the as-path is
> alluring, but be careful what you wish for, because fiddling with this
> will have consequences which extend far outside your assumed scope.

Such as?

> At least in most cases, it's pretty straightforward these days to
> implement route servers with full, dynamically rebuilt filtering out
> of the box.  The technical work has been done.  What's left is to get
> the remaining IXPs which don't filter their inbound prefixes to deploy
> this.

It is quite laborious to track down which IXPs are not filtering, given
the lack of visiblity due to the AS hiding. Let's take an example from
RIPE RIS RRC03 updates.20171216.0300.gz:

	TIME: 12/16/17 03:00:06
	TYPE: BGP4MP/MESSAGE/Update
	FROM: 80.249.208.34 AS1103
	TO: 80.249.208.69 AS12654
	ORIGIN: INCOMPLETE
	ASPATH: 1103 7713 2914 286 34984
	NEXT_HOP: 80.249.208.34
	COMMUNITY: 0:65535 1103:101 1103:1000 1103:1011 2914:420 2914:1008 2914:2000 2914:3000 34307:50197 34307:60002 65504:286
	ANNOUNCE
	  212.252.176.0/20
	  213.153.247.0/24

AS 7713 inadvertently announced some of its peering & upstream routes to
other peering partners. Only through manual verification with AS 1103 we
could discover that there there is no bilateral session between 1103 and
7713, but a multilateral device is hiding between 1103 and 7713. This
could further be confirmed through PeeringDB where we see both ASNs
share a common IXP, and the IXP's RS ASN shows up in the BGP
communities: "34307:50197 34307:60002".

Life would be much simpler if we can simply read off our screen:

    AS_PATH: 1103 34307 7713 2914 286 34984

Kind regards,

Job


From nobody Mon Dec 18 07:54:24 2017
Return-Path: <job@instituut.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C597112708C for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 07:54:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.249
X-Spam-Level: 
X-Spam-Status: No, score=0.249 tagged_above=-999 required=5 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=no 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 VZvi8pI7MACc for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 07:54:21 -0800 (PST)
Received: from mail-wr0-f179.google.com (mail-wr0-f179.google.com [209.85.128.179]) (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 A20EC1200B9 for <grow@ietf.org>; Mon, 18 Dec 2017 07:54:21 -0800 (PST)
Received: by mail-wr0-f179.google.com with SMTP id s66so14552901wrc.9 for <grow@ietf.org>; Mon, 18 Dec 2017 07:54:21 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=ZyW7n17gwFybn77UUx6Pv/HbiOEoY7QvQBvK0oMsLFI=; b=D4Ge9uST0XGrh53z4FCEw+krsLryZ5wSPs57yoVvUFfsmwfIPgPA6Sb2gT/sCUO9IG 2K8/m/EJfc19Kbywb32adNpa4QNBvFdYJyVv9nc4CXddIXDlbqqihDUiTekfzjj/GcOV 90eXOXvlD4GjyBdNdqQyF4qJxt9kFH6yDQXdIiNpd31jolGCpViNPF9q6V1uubf5jkja Q3JBoHMrs6fZfCtyYY2APEGME1Cj5xiF1I6xnEnJig4PldCWO5kvZHBWcKBdrB41G4uN eenyibtvpD85pYVB5n3FLa54styKNGyNbxwQayPOKXtEVNXaMwbji/0loXpcZM4ViwzO 0e8g==
X-Gm-Message-State: AKGB3mJz+TKPAUXGQaCcWMjXzRyDlCUvR/3cMbdBfexbBi3QLUU/YO8d mjlMETUh+cC/NkaJh/gStRYALd2lF+Q=
X-Google-Smtp-Source: ACJfBoutXwd4iLt4M3HzxVRF8vv8/Tvkgf7RQ6rhjA1Cyd9B34l3rZejMCegHFDNwiihZiWXWmJ3tg==
X-Received: by 10.223.176.41 with SMTP id f38mr242556wra.80.1513612459851; Mon, 18 Dec 2017 07:54:19 -0800 (PST)
Received: from localhost ([2001:67c:208c:10:e938:68b3:3dfe:7a6d]) by smtp.gmail.com with ESMTPSA id c25sm11702551edb.52.2017.12.18.07.54.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Dec 2017 07:54:19 -0800 (PST)
Date: Mon, 18 Dec 2017 16:54:18 +0100
From: Job Snijders <job@ntt.net>
To: Nick Hilliard <nick@foobar.org>
Cc: grow@ietf.org
Message-ID: <20171218155418.GE1009@hanna.meerval.net>
References: <20171218105034.GD43144@vurt.meerval.net> <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net> <36e13c57-ac32-9fe9-ef31-e59ab1bc0c21@i3d.net> <20171218150741.GC1009@hanna.meerval.net> <5A37DF7D.9040405@foobar.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5A37DF7D.9040405@foobar.org>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.9.1 (2017-09-22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/oq1zx_yuKjFhUSj_NOEfma6Aa84>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Dec 2017 15:54:23 -0000

On Mon, Dec 18, 2017 at 03:32:13PM +0000, Nick Hilliard wrote:
> Job Snijders wrote:
> > I mentioned before, I suspect that the route server's lack of
> > visiblity is a direct contributor to the reluctance to apply filters
> > on route servers.
> 
> Job, seriously, if you have helpful or useful comments to make, then
> please make them.

You are free to disagree with my suspicions, but please ensure you
maintain a degree of decorum when doing so.

I've perceive advantages to transparency in many areas of business.
(well, in this context 'transparency' should be interpreted as 'explicit
visibility'). Oftentimes immediate improvement can be noticed when a
business operation is ranked against similar business, and reports are
published on performance indicators. This of course requires the
business to be visible in the first place.

The AS_PATH attribute serves multiple functions: its length is used as a
tie-breaker in best path selection, and the contents of the AS_PATH
itself serves as an (mutable) track record on what administrative
domains the announcement passed through.

You and Martijn appear to argue that the 'best path selection' component
should not be fiddled with, which leaves me wondering whether we have
any other methods to implement a track record ala 'this path
announcement passed through RS AS XYZ' other than communities. Or are
you of the opinion that the lack of visibility is not a problem to begin
with?

Respectfully,

Job


From nobody Mon Dec 18 09:38:29 2017
Return-Path: <nick@foobar.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 474D0127136 for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 09:38:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, 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 w-1oMjcG4mAd for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 09:38:26 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A01E126579 for <grow@ietf.org>; Mon, 18 Dec 2017 09:38:26 -0800 (PST)
X-Envelope-To: grow@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id vBIHcNcD064224 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Dec 2017 17:38:24 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
Message-ID: <5A37FD0E.5080306@foobar.org>
Date: Mon, 18 Dec 2017 17:38:22 +0000
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.22 (Macintosh/20171208)
MIME-Version: 1.0
To: Job Snijders <job@ntt.net>
CC: grow@ietf.org
References: <20171218105034.GD43144@vurt.meerval.net> <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net> <36e13c57-ac32-9fe9-ef31-e59ab1bc0c21@i3d.net> <20171218150741.GC1009@hanna.meerval.net> <5A37DF7D.9040405@foobar.org> <20171218155418.GE1009@hanna.meerval.net>
In-Reply-To: <20171218155418.GE1009@hanna.meerval.net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/SQegI6xopDAoGzYSxQbEl0MNOZc>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Dec 2017 17:38:28 -0000

Job Snijders wrote:
> You and Martijn appear to argue that the 'best path selection'
> component should not be fiddled with, which leaves me wondering
> whether we have any other methods to implement a track record ala
> 'this path announcement passed through RS AS XYZ' other than
> communities. Or are you of the opinion that the lack of visibility is
> not a problem to begin with?

communities are low-hanging fruit and non-intrusive, and probably not a
bad thing to do.

If you plan to spend time and energy dealing with the underlying
problem, i.e. routing leaks, then I'd suggest continuing to work on
getting IXPs to implement prefix filtering on their route servers.  It's
laborious and thankless but will actually fix the problem in the longer
term - and it needs to be done anyway.

Nick


From nobody Mon Dec 18 14:58:45 2017
Return-Path: <aa@highloadlab.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D63F12D960 for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 14:58:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=highloadlab-com.20150623.gappssmtp.com
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 PCjSVEKrd4fL for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 14:58:41 -0800 (PST)
Received: from mail-pl0-x242.google.com (mail-pl0-x242.google.com [IPv6:2607:f8b0:400e:c01::242]) (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 E95FE126C3D for <grow@ietf.org>; Mon, 18 Dec 2017 14:58:40 -0800 (PST)
Received: by mail-pl0-x242.google.com with SMTP id s3so5743678plp.4 for <grow@ietf.org>; Mon, 18 Dec 2017 14:58:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=highloadlab-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=IoCrE7DGfKWTSh/z0UgDspMaWFTKSJI0na0WHMcGlig=; b=uzkbp50gRMhPUVZCGyvViWNtNamQXnhG0lSOBec+7DcznKzC6/TYjkDdaMQaoPAgwF rzmBs1yE6s3C4iTmHQIYaKkFdyA0RROUbhRir2cCoJSHRrM7G0Javtm2ImNmrQ+tnp7p ki3lzQK9woiA8R5DHS9ZO8LBZl+Y0+2Yc5MXN0NrjSyzilT9qWRXTF57x8nGZ2EDV4ha 0WbvaQ7sDjMIZog5GBUop+dvupilsUbDInu7eDquiUbiftyWdLLYZGZug9/qGq0NwcNh fOITkIZ4YIzmaE9m+S3mpNWGvLdGzOAJb0pi3uAoCJtrk/xscDeIOxpTBiJ0VcI1aLA8 +UmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=IoCrE7DGfKWTSh/z0UgDspMaWFTKSJI0na0WHMcGlig=; b=rASfjfBSqAVNME0P0SkJXfvJju1NvbB3wR1guhhKeFWEUSb4w0ImqQ3R4DOybdu7Q5 3955bOFIammizqJn6RbYuzVYyBSDs1JwZGYLXhVxVhRzRejXYlUC2P9f+Lw3wRZ+mu2L EVjDkyLfSjcSYlxsEPhsgUCe4nuPB+5AOaqLKJlY2+V6t7JcRSIXtIZoMTcBBdewyb93 snceYN1XtlgjusbAC9obAHV3BRXCREBtlhZAolulcDDaaAHVVTtyS+1HFPAJNoa+KRdH p1X//xsICW4LN1cAMmM6u32f1/TkD15DFW4X5S5VCSyFwOPG3J/txCtzv6PObptS47aU W2ug==
X-Gm-Message-State: AKGB3mKXhLJWhV3y9D4tm+hsXjKMCaPSuHJ5QOgAbxnqyaIIVTcYaKnh 0zKWDY71yHdmHjWZUnYLih1WgKi4BZS2jJUdhJuL0N9E
X-Google-Smtp-Source: ACJfBoveNmiP4ILnjaYmr1v4FkbZyq3ZSZdUieDnWpU6O97T1GGLYTb7uP+iVI7jo5WuAvrSATA6H9PD4Xf1ohU0kDI=
X-Received: by 10.84.167.2 with SMTP id c2mr1189416plb.25.1513637920258; Mon, 18 Dec 2017 14:58:40 -0800 (PST)
MIME-Version: 1.0
Sender: aa@highloadlab.com
Received: by 10.100.128.81 with HTTP; Mon, 18 Dec 2017 14:58:39 -0800 (PST)
X-Originating-IP: [46.188.121.185]
In-Reply-To: <5A37FD0E.5080306@foobar.org>
References: <20171218105034.GD43144@vurt.meerval.net> <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net> <36e13c57-ac32-9fe9-ef31-e59ab1bc0c21@i3d.net> <20171218150741.GC1009@hanna.meerval.net> <5A37DF7D.9040405@foobar.org> <20171218155418.GE1009@hanna.meerval.net> <5A37FD0E.5080306@foobar.org>
From: Alexander Azimov <aa@qrator.net>
Date: Tue, 19 Dec 2017 01:58:39 +0300
X-Google-Sender-Auth: m1wcfkRhVUuAQIbQ-aP7kD_EFDU
Message-ID: <CAHgCvCPQPDmt7tqO0KVWZLgGbCkVKWucWr6h8d=yczVSuh1qAw@mail.gmail.com>
To: Nick Hilliard <nick@foobar.org>
Cc: Job Snijders <job@ntt.net>, grow@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c145bae8e528c0560a54a79"
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/BVVfep1dnMxLnrQcUod6zY2x-_c>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Dec 2017 22:58:44 -0000

--94eb2c145bae8e528c0560a54a79
Content-Type: text/plain; charset="UTF-8"

Hi all,

I'd like to share my support to Job's position, and the reason isn't only
'transparency' or filtering (while they are worth to fight for).

I see as the core of the problem, that one ISP MUST add its AS Number in
the AS_PATH and another ISP is permitted no to do it. Yes, one can tell me,
that IXP doesn't provide transit, it provides only local connectivity,
through L2 matrix, but does ISP becomes IXP if it provides local
connectivity? Imagine a situation when a customer has a choice: to purchase
partial transit (only customer cone) from ISP or to become a member of IX.
The price for both services could be quite comparable, but customer is
looking forward not only for lesser costs, but also for increase its
margin, and even if ISP will have all IX members as customers, it will be
less preferable because through IX the path will have -1 hop. Some ISPs are
already asking themselves a question, maybe they can also remove their AS
number, at least when announcing routes to customers?

And this pandora box has been already opened, I can name several ISPs that
provide transit and remove its ASN from AS_PATH attribute, some of them are
removing it even when announcing routes to upstreams. It's not right, it
violates BGP loop detection, but it has just same motivation as RS at IXP -
to make their routes more preferable, make 'virtual direct' connections.
Some of them even name themselves as IXPs.

In BGPSec it's getting even worse with pCount = 0. There is a statement in
section 7.2.:

> if a BGPsec speaker does not expect a peer AS to set its pCount=0 and
>    if an UPDATE message received from that peer violates this, then the
>    UPDATE message MUST be considered to be in error (see the list of
>    checks in Section 5.2).  See Section 8.4 for a discussion of security
>    considerations concerning pCount=0.

Well, I can assume that some transit providers will be checking this pCount
value, but I don't believe it will be checked from the customer side (it's
even impossible for all, except direct neighbor). It can end up with
everybody setting pCount=0 and AS_PATH attribute will lose much of its
current use cases.

2017-12-18 20:38 GMT+03:00 Nick Hilliard <nick@foobar.org>:

> Job Snijders wrote:
> > You and Martijn appear to argue that the 'best path selection'
> > component should not be fiddled with, which leaves me wondering
> > whether we have any other methods to implement a track record ala
> > 'this path announcement passed through RS AS XYZ' other than
> > communities. Or are you of the opinion that the lack of visibility is
> > not a problem to begin with?
>
> communities are low-hanging fruit and non-intrusive, and probably not a
> bad thing to do.
>
> If you plan to spend time and energy dealing with the underlying
> problem, i.e. routing leaks, then I'd suggest continuing to work on
> getting IXPs to implement prefix filtering on their route servers.  It's
> laborious and thankless but will actually fix the problem in the longer
> term - and it needs to be done anyway.
>
> Nick
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>



-- 
| Alexander Azimov  | HLL l QRATOR
| tel.: +7 499 241 81 92
| mob.: +7 915 360 08 86
| skype: mitradir
| mailto: aa@qrator.net
| visit: www.qrator.net

--94eb2c145bae8e528c0560a54a79
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>I&#39;d like to share my suppor=
t to Job&#39;s position, and the reason isn&#39;t only &#39;transparency&#3=
9; or filtering (while they are worth to=C2=A0fight for).</div><div><br></d=
iv><div><div>I see as the core of the problem, that one ISP MUST add its AS=
 Number in the AS_PATH and another ISP is permitted no to do it. Yes, one c=
an tell me, that IXP doesn&#39;t provide transit, it provides only local co=
nnectivity, through L2 matrix, but does ISP becomes IXP if it provides loca=
l connectivity? Imagine a situation when a customer has a choice: to purcha=
se partial transit (only customer cone) from ISP or to become a member of I=
X. The price for both services could be quite comparable, but customer is l=
ooking forward not only for lesser costs, but also for increase its margin,=
 and even if ISP will have all IX members as customers, it will be less pre=
ferable because through IX the path will have -1 hop. Some ISPs are already=
 asking themselves a=C2=A0question, maybe they can also remove their AS num=
ber, at least when announcing routes to customers?=C2=A0</div></div><div><b=
r></div><div>And this pandora=C2=A0box has been already opened, I can name =
several ISPs that provide transit and remove its ASN from AS_PATH attribute=
, some of them are removing=C2=A0it even when announcing routes to upstream=
s. It&#39;s not right, it violates BGP loop detection, but it has just same=
 motivation as RS at IXP - to make their=C2=A0routes more preferable, make =
&#39;virtual direct&#39; connections. Some of them even name=C2=A0themselve=
s as IXPs.=C2=A0</div><div><br></div><div>In BGPSec it&#39;s getting even w=
orse with pCount =3D 0. There is a statement in section 7.2.:</div><div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">if a BGPsec speaker does not=
 expect a peer AS to set its pCount=3D0 and<br>=C2=A0 =C2=A0if an UPDATE me=
ssage received from that peer violates this, then the<br>=C2=A0 =C2=A0UPDAT=
E message MUST be considered to be in error (see the list of<br>=C2=A0 =C2=
=A0checks in Section 5.2).=C2=A0 See Section 8.4 for a discussion of securi=
ty<br>=C2=A0 =C2=A0considerations concerning pCount=3D0.</blockquote><div>W=
ell, I can assume that some transit providers will be checking this pCount =
value, but I don&#39;t believe it will be checked from the customer side (i=
t&#39;s even impossible for all, except direct neighbor). It can end up wit=
h everybody setting pCount=3D0 and AS_PATH attribute will lose much of its =
current use cases.<br></div></div></div><div class=3D"gmail_extra"><br><div=
 class=3D"gmail_quote">2017-12-18 20:38 GMT+03:00 Nick Hilliard <span dir=
=3D"ltr">&lt;<a href=3D"mailto:nick@foobar.org" target=3D"_blank">nick@foob=
ar.org</a>&gt;</span>:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">J=
ob Snijders wrote:<br>
&gt; You and Martijn appear to argue that the &#39;best path selection&#39;=
<br>
&gt; component should not be fiddled with, which leaves me wondering<br>
&gt; whether we have any other methods to implement a track record ala<br>
&gt; &#39;this path announcement passed through RS AS XYZ&#39; other than<b=
r>
&gt; communities. Or are you of the opinion that the lack of visibility is<=
br>
&gt; not a problem to begin with?<br>
<br>
</span>communities are low-hanging fruit and non-intrusive, and probably no=
t a<br>
bad thing to do.<br>
<br>
If you plan to spend time and energy dealing with the underlying<br>
problem, i.e. routing leaks, then I&#39;d suggest continuing to work on<br>
getting IXPs to implement prefix filtering on their route servers.=C2=A0 It=
&#39;s<br>
laborious and thankless but will actually fix the problem in the longer<br>
term - and it needs to be done anyway.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Nick<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
______________________________<wbr>_________________<br>
GROW mailing list<br>
<a href=3D"mailto:GROW@ietf.org">GROW@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/grow" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/grow</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=
=3D"ltr"><div style=3D"font-family:Helvetica;font-size:12px;border-collapse=
:collapse"><font color=3D"#999999">| Alexander Azimov =C2=A0| HLL l QRATOR<=
/font></div><div style=3D"font-family:Helvetica;font-size:12px;border-colla=
pse:collapse"><font color=3D"#999999">| tel.: +7 499 241 81 92</font></div>=
<div style=3D"font-family:Helvetica;font-size:12px;border-collapse:collapse=
"><font color=3D"#999999">| mob.: +7 915 360 08 86</font></div><div style=
=3D"font-family:Helvetica;font-size:12px;border-collapse:collapse"><font co=
lor=3D"#999999">| skype: mitradir</font></div><div style=3D"font-family:Hel=
vetica;font-size:12px;border-collapse:collapse"><font color=3D"#999999">| m=
ailto:=C2=A0<a href=3D"mailto:aa@qrator.net" target=3D"_blank">aa@qrator.ne=
t</a></font></div><div style=3D"font-family:Helvetica;font-size:12px;border=
-collapse:collapse"><font color=3D"#999999">| visit:=C2=A0<a href=3D"http:/=
/www.qrator.net/" target=3D"_blank">www.qrator.net</a></font></div></div></=
div>
</div>

--94eb2c145bae8e528c0560a54a79--


From nobody Mon Dec 18 15:47:34 2017
Return-Path: <jared@puck.nether.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63EB112DA08 for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 15:47:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 i_jTOtLAZFo4 for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 15:47:31 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id DAFCC12DA06 for <grow@ietf.org>; Mon, 18 Dec 2017 15:47:31 -0800 (PST)
Received: from [10.0.0.137] (173-167-0-106-michigan.hfc.comcastbusiness.net [173.167.0.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id DED375408AD; Mon, 18 Dec 2017 18:47:29 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <5A37FD0E.5080306@foobar.org>
Date: Mon, 18 Dec 2017 18:47:28 -0500
Cc: Job Snijders <job@ntt.net>, grow@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <4BB72667-A6C5-4212-A7C9-0BDAA1BE620C@puck.nether.net>
References: <20171218105034.GD43144@vurt.meerval.net> <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net> <36e13c57-ac32-9fe9-ef31-e59ab1bc0c21@i3d.net> <20171218150741.GC1009@hanna.meerval.net> <5A37DF7D.9040405@foobar.org> <20171218155418.GE1009@hanna.meerval.net> <5A37FD0E.5080306@foobar.org>
To: Nick Hilliard <nick@foobar.org>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/eR_Uo5He6EZQqq7FL_5jnqFTci8>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Dec 2017 23:47:33 -0000

> On Dec 18, 2017, at 12:38 PM, Nick Hilliard <nick@foobar.org> wrote:
>=20
> Job Snijders wrote:
>> You and Martijn appear to argue that the 'best path selection'
>> component should not be fiddled with, which leaves me wondering
>> whether we have any other methods to implement a track record ala
>> 'this path announcement passed through RS AS XYZ' other than
>> communities. Or are you of the opinion that the lack of visibility is
>> not a problem to begin with?
>=20
> communities are low-hanging fruit and non-intrusive, and probably not =
a
> bad thing to do.
>=20
> If you plan to spend time and energy dealing with the underlying
> problem, i.e. routing leaks, then I'd suggest continuing to work on
> getting IXPs to implement prefix filtering on their route servers.  =
It's
> laborious and thankless but will actually fix the problem in the =
longer
> term - and it needs to be done anyway.

I know that Job has been pushing for the above, perhaps not in your view
but in the view of others here.

I do think that having a RS emit a community saying =E2=80=9CRS_ASN:xxx=E2=
=80=9D would be
of value.  As mentioned in other emails, finding these edges can be =
quite
complex when doing operations.

If we continue to see the active threats, market forces will dictate the
resulting implementations.

I=E2=80=99d like to see improvements in routing security, but the path =
forward is murky.

Aside from AS_PATH & Communities, are there other ideas?

- Jared


From nobody Mon Dec 18 19:06:32 2017
Return-Path: <heas@shrubbery.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 063BE126B6E for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 19:06:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 mE35GqwwMMJq for <grow@ietfa.amsl.com>; Mon, 18 Dec 2017 19:06:30 -0800 (PST)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC78B1200C5 for <grow@ietf.org>; Mon, 18 Dec 2017 19:06:29 -0800 (PST)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id ACE30436DA; Tue, 19 Dec 2017 03:06:29 +0000 (UTC)
Date: Tue, 19 Dec 2017 03:06:29 +0000
From: heasley <heas@shrubbery.net>
To: Job Snijders <job@ntt.net>
Cc: Nick Hilliard <nick@foobar.org>, grow@ietf.org
Message-ID: <20171219030629.GD48369@shrubbery.net>
References: <20171218105034.GD43144@vurt.meerval.net> <5A37D990.2060505@foobar.org> <20171218153656.GD1009@hanna.meerval.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20171218153656.GD1009@hanna.meerval.net>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.9.1 (2017-09-22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/bL8vOd1MwI1RrQACiHtjubrM5s0>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 03:06:31 -0000

Mon, Dec 18, 2017 at 04:36:56PM +0100, Job Snijders:
> pressure to set up bilateral sessions.

Is that negative?  Why not encourage ASes to have direct relationships
and stop maintaining route servers?  They should develop those relationships
and it might even be suggested that security and trouble shooting could
rely upon it.


From nobody Tue Dec 19 00:22:57 2017
Return-Path: <nick@foobar.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B29AD12DA41 for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 00:22:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 M8Sr9M5Ee9K3 for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 00:22:53 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F64A124205 for <grow@ietf.org>; Tue, 19 Dec 2017 00:22:52 -0800 (PST)
X-Envelope-To: grow@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id vBJ8MnS6084187 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Dec 2017 08:22:50 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
Message-ID: <5A38CC58.9080700@foobar.org>
Date: Tue, 19 Dec 2017 08:22:48 +0000
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.22 (Macintosh/20171208)
MIME-Version: 1.0
To: Jared Mauch <jared@puck.nether.net>
CC: Job Snijders <job@ntt.net>, grow@ietf.org
References: <20171218105034.GD43144@vurt.meerval.net> <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net> <36e13c57-ac32-9fe9-ef31-e59ab1bc0c21@i3d.net> <20171218150741.GC1009@hanna.meerval.net> <5A37DF7D.9040405@foobar.org> <20171218155418.GE1009@hanna.meerval.net> <5A37FD0E.5080306@foobar.org> <4BB72667-A6C5-4212-A7C9-0BDAA1BE620C@puck.nether.net>
In-Reply-To: <4BB72667-A6C5-4212-A7C9-0BDAA1BE620C@puck.nether.net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/H_e2H0yICYMjJb8bPCOBZwe2mV0>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 08:22:56 -0000

Jared Mauch wrote:
> I know that Job has been pushing for the above, perhaps not in your view
> but in the view of others here.

definitely.  It's been incredibly productive work, and his efforts have
produced major results in terms of pushing IXPs towards filtering.  This
needs to be continued.

Nick


From nobody Tue Dec 19 00:25:39 2017
Return-Path: <gert@space.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B073124BE8 for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 00:25:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] 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 Vhi0Ft6NHLXk for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 00:25:36 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40BF1124205 for <grow@ietf.org>; Tue, 19 Dec 2017 00:25:36 -0800 (PST)
X-Original-To: grow@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 6E95441B96 for <grow@ietf.org>; Tue, 19 Dec 2017 09:25:34 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 613D841B8D; Tue, 19 Dec 2017 09:25:34 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id 532126F268; Tue, 19 Dec 2017 09:25:34 +0100 (CET)
Date: Tue, 19 Dec 2017 09:25:34 +0100
From: Gert Doering <gert@space.net>
To: heasley <heas@shrubbery.net>
Cc: Job Snijders <job@ntt.net>, grow@ietf.org
Message-ID: <20171219082534.GA45648@Space.Net>
References: <20171218105034.GD43144@vurt.meerval.net> <5A37D990.2060505@foobar.org> <20171218153656.GD1009@hanna.meerval.net> <20171219030629.GD48369@shrubbery.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20171219030629.GD48369@shrubbery.net>
X-NCC-RegID: de.space
User-Agent: Mutt/1.8.2 (2017-04-18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/8K-RLe4UHKocMW6jNhv0QRcSYng>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 08:25:38 -0000

Hi,

On Tue, Dec 19, 2017 at 03:06:29AM +0000, heasley wrote:
> Mon, Dec 18, 2017 at 04:36:56PM +0100, Job Snijders:
> > pressure to set up bilateral sessions.
> 
> Is that negative?  Why not encourage ASes to have direct relationships
> and stop maintaining route servers?  They should develop those relationships
> and it might even be suggested that security and trouble shooting could
> rely upon it.

Economies of scale.  DECIX has over 600 active participants, and I have
little interest in talking to about 550 of them - but my routers would
appreciate having direct routes to the networks behind them.

So, route servers are a very (very!) welcome feature.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Tue Dec 19 00:40:52 2017
Return-Path: <nick@foobar.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBF2012D835 for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 00:40:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 o_YRUZG1hOjD for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 00:40:50 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F255124BE8 for <grow@ietf.org>; Tue, 19 Dec 2017 00:40:49 -0800 (PST)
X-Envelope-To: grow@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id vBJ8elWn086250 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Dec 2017 08:40:48 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
Message-ID: <5A38D08E.8020206@foobar.org>
Date: Tue, 19 Dec 2017 08:40:46 +0000
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.22 (Macintosh/20171208)
MIME-Version: 1.0
To: heasley <heas@shrubbery.net>
CC: grow@ietf.org
References: <20171218105034.GD43144@vurt.meerval.net> <5A37D990.2060505@foobar.org> <20171218153656.GD1009@hanna.meerval.net> <20171219030629.GD48369@shrubbery.net>
In-Reply-To: <20171219030629.GD48369@shrubbery.net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/4qUI9hseE4JCkWDuNWCU6pDRDNU>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 08:40:52 -0000

heasley wrote:
> Mon, Dec 18, 2017 at 04:36:56PM +0100, Job Snijders:
>> pressure to set up bilateral sessions.
> 
> Is that negative?  Why not encourage ASes to have direct relationships
> and stop maintaining route servers?  They should develop those relationships
> and it might even be suggested that security and trouble shooting could
> rely upon it.

in general, yes, this is negative.  If you have the resourcing to deploy
proper automation, including dynamic filtering and session management,
then bilateral is better.  If you don't, then properly managed route
servers will provide a better experience in practice.

Nick


From nobody Tue Dec 19 00:45:41 2017
Return-Path: <gert@space.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B40712D835 for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 00:45:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] 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 V8StE2vB9SVP for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 00:45:38 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22FA2124BE8 for <grow@ietf.org>; Tue, 19 Dec 2017 00:45:38 -0800 (PST)
X-Original-To: grow@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id B2E8541B8D for <grow@ietf.org>; Tue, 19 Dec 2017 09:45:36 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id A4F1840BA0; Tue, 19 Dec 2017 09:45:36 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id A1CBA6F333; Tue, 19 Dec 2017 09:45:36 +0100 (CET)
Date: Tue, 19 Dec 2017 09:45:36 +0100
From: Gert Doering <gert@space.net>
To: Nick Hilliard <nick@foobar.org>
Cc: heasley <heas@shrubbery.net>, grow@ietf.org
Message-ID: <20171219084536.GB45648@Space.Net>
References: <20171218105034.GD43144@vurt.meerval.net> <5A37D990.2060505@foobar.org> <20171218153656.GD1009@hanna.meerval.net> <20171219030629.GD48369@shrubbery.net> <5A38D08E.8020206@foobar.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5A38D08E.8020206@foobar.org>
X-NCC-RegID: de.space
User-Agent: Mutt/1.8.2 (2017-04-18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/kSHKY1GmdUM5-Kz646dbOskZ8sc>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 08:45:39 -0000

Hi,

On Tue, Dec 19, 2017 at 08:40:46AM +0000, Nick Hilliard wrote:
> If you have the resourcing to deploy
> proper automation, including dynamic filtering and session management,
> then bilateral is better.  

To emphasize some aspect of this for the non-operators on this list: the
technical bits of this are manageable.  Talking to 500 other ISPs that
are not responding to e-mail, do not have anyone in the same time zone,
generally lack understanding of BGP, etc. - this is what really costs,
and where a well-maintained route server really shines.

(And then, there's "poor BGP implementations that just do not scale
properly with 600+ peers on the same router"...  like, "most of them")

If there were only 10 other ISPs at the IXPs we connect to, we could
do without route servers :-)

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Tue Dec 19 00:53:15 2017
Return-Path: <job@instituut.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 994EC12D84D for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 00:53:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level: 
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=no 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 9T4hYXPLSE3L for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 00:53:12 -0800 (PST)
Received: from mail-wr0-f181.google.com (mail-wr0-f181.google.com [209.85.128.181]) (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 6E4CC1201F2 for <grow@ietf.org>; Tue, 19 Dec 2017 00:53:12 -0800 (PST)
Received: by mail-wr0-f181.google.com with SMTP id s66so17985064wrc.9 for <grow@ietf.org>; Tue, 19 Dec 2017 00:53:12 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=cbDgtcODAkpRDGipaVLQYrusD37V244W/s6tLa3bqoE=; b=APIqK5LkxQiWQmzR44LakGdrZkZ50Qxj/VNvvgV8r3PwWQAKWXuvd23let3r1qFoZv Mo8Oscr4ieiS+d+56+lGY0AD8/hK4hVAoY0nWaiswJBqIN7K3BhjpqC4EmDQu6hTpScY gan9s9lkedeXIgNIL/G2PTwplmHVBajcQj03TWVzFo1VhpP4NnfqyZ3F+d+LDgzTJjFA klfaY9rXm3PiVfgKaOj5mlK2sfuW5yoQPBOrh2HrOliZE9ZJim5JX8UhuCO7h9Bkz7hb LBBGGosICpo6JnsA+a60ECyK4rBGBnqJfGvLllKE6ddFECmjE79nA+WYe2LO/2GQvxhS IIBw==
X-Gm-Message-State: AKGB3mJFv68aY2CpJ5QGTdjQH0Dp2GuptDHR5BcmLkagsZqPgDRO5VEM toNzWr9PYs/y4XkpVppxMwurIi8WD7w=
X-Google-Smtp-Source: ACJfBosCtKrcDT2r1nUzYOVu5oxqMw8Vx1qVOw5XO1C7GBECSQG9fmGUDc73knKEwZxauYRbNO/HjQ==
X-Received: by 10.223.199.203 with SMTP id y11mr4177367wrg.37.1513673590573; Tue, 19 Dec 2017 00:53:10 -0800 (PST)
Received: from localhost ([2001:67c:208c:10:e938:68b3:3dfe:7a6d]) by smtp.gmail.com with ESMTPSA id r1sm11724522edb.71.2017.12.19.00.53.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Dec 2017 00:53:09 -0800 (PST)
Date: Tue, 19 Dec 2017 09:53:08 +0100
From: Job Snijders <job@ntt.net>
To: Gert Doering <gert@space.net>
Cc: grow@ietf.org
Message-ID: <20171219085308.GI1009@hanna.meerval.net>
References: <20171218105034.GD43144@vurt.meerval.net> <5A37D990.2060505@foobar.org> <20171218153656.GD1009@hanna.meerval.net> <20171219030629.GD48369@shrubbery.net> <5A38D08E.8020206@foobar.org> <20171219084536.GB45648@Space.Net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20171219084536.GB45648@Space.Net>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.9.1 (2017-09-22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/yqHRGvL15i9FYxts1WTNWYDthUs>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 08:53:14 -0000

On Tue, Dec 19, 2017 at 09:45:36AM +0100, Gert Doering wrote:
> On Tue, Dec 19, 2017 at 08:40:46AM +0000, Nick Hilliard wrote:
> > If you have the resourcing to deploy proper automation, including
> > dynamic filtering and session management, then bilateral is better.  
> 
> To emphasize some aspect of this for the non-operators on this list:
> the technical bits of this are manageable.  Talking to 500 other ISPs
> that are not responding to e-mail, do not have anyone in the same time
> zone, generally lack understanding of BGP, etc. - this is what really
> costs, and where a well-maintained route server really shines.
> 
> (And then, there's "poor BGP implementations that just do not scale
> properly with 600+ peers on the same router"...  like, "most of them")
> 
> If there were only 10 other ISPs at the IXPs we connect to, we could
> do without route servers :-)

Yes, route servers can be very useful, no question about it. I think
their value as a service would increase if they become visible
participants of the routing ecosystem.

Gert, do you think it would affect your operations if the route server
would insert its ASN into the AS_PATH?

Would you be willing to run a test? In your routing policy you can
append "6695" on inbound and prepend your own AS on outbound to simulate
what it would be like if that RS would insert itself.

Kind regards,

Job


From nobody Tue Dec 19 01:44:14 2017
Return-Path: <c@tix.at>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C5F412D84D for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 01:44:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=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 A-GcP-LwpCKt for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 01:44:10 -0800 (PST)
Received: from mail.hated.at (mail.hated.at [IPv6:2001:858:2:8::235]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE5DB127077 for <grow@ietf.org>; Tue, 19 Dec 2017 01:44:10 -0800 (PST)
Received: from [2a01:190:1702:0:1c9a:65a7:ae7e:3b62] by mail.hated.at with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <c@tix.at>) id 1eREA1-00049Y-8D; Tue, 19 Dec 2017 10:26:05 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
From: Christoph Loibl <c@tix.at>
In-Reply-To: <4BB72667-A6C5-4212-A7C9-0BDAA1BE620C@puck.nether.net>
Date: Tue, 19 Dec 2017 10:43:57 +0100
Cc: Nick Hilliard <nick@foobar.org>, grow@ietf.org, Job Snijders <job@ntt.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D3A28AD8-A9AE-4BAC-A5D6-1FB81DD67B51@tix.at>
References: <20171218105034.GD43144@vurt.meerval.net> <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net> <36e13c57-ac32-9fe9-ef31-e59ab1bc0c21@i3d.net> <20171218150741.GC1009@hanna.meerval.net> <5A37DF7D.9040405@foobar.org> <20171218155418.GE1009@hanna.meerval.net> <5A37FD0E.5080306@foobar.org> <4BB72667-A6C5-4212-A7C9-0BDAA1BE620C@puck.nether.net>
To: Jared Mauch <jared@puck.nether.net>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/AmVu1cus8GVJlz7c-D2kyDTfd0I>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 09:44:13 -0000

Hi,

Feedback on suggested path changes from another operator:

I imagine that in our case having *all* route-servers consistently add =
their ASN would not lead to too many path changes. The changes that we =
will see is that we will prefer direct peerings over route server =
prefixes because of AS-Path length (today it is another metric that is =
the tie breaker, since AS-path length is equal).=20

For our transit customers however, this may be a slightly different =
story because they suddenly see the direct peerings with a shorter =
as-path than routes propagated via route servers and may select =
different paths.

Suggestion:

I would prefer a solution that has no impact on the as-path:=20

> On 19.12.2017, at 00:47, Jared Mauch <jared@puck.nether.net> wrote:
>=20
> I do think that having a RS emit a community saying =E2=80=9CRS_ASN:xxx=E2=
=80=9D would be
> of value.  As mentioned in other emails, finding these edges can be =
quite
> complex when doing operations.

However, communities are very fragile when it comes to route =
propagation. Removing / modifying communities is happening everywhere =
(mostly at AS borders). I would not like to rely on BGP communities for =
this.
=20
We have a solution to a slightly similar problem in iBGP =
route-reflection. For that purpose we added an optional non-transitive =
attribute CLUSTER_LIST. I suggest a similar approach for IXP =
route-servers (ROUTESERVER_LIST optional,transitive =3D list of =
route-server ASNs that have propagated the prefix). That seems less =
fragile and the implementation changes are limited to the route-servers =
themselves.

Christoph


From nobody Tue Dec 19 01:50:35 2017
Return-Path: <gert@space.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AE2812D890 for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 01:50:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] 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 P8zhhkuXRKsB for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 01:50:32 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD30A12421A for <grow@ietf.org>; Tue, 19 Dec 2017 01:50:31 -0800 (PST)
X-Original-To: grow@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id DD4D044139 for <grow@ietf.org>; Tue, 19 Dec 2017 10:50:29 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id CE42544134; Tue, 19 Dec 2017 10:50:29 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id BFA266F6AD; Tue, 19 Dec 2017 10:50:29 +0100 (CET)
Date: Tue, 19 Dec 2017 10:50:29 +0100
From: Gert Doering <gert@space.net>
To: Job Snijders <job@ntt.net>
Cc: Gert Doering <gert@space.net>, grow@ietf.org
Message-ID: <20171219095029.GC45648@Space.Net>
References: <20171218105034.GD43144@vurt.meerval.net> <5A37D990.2060505@foobar.org> <20171218153656.GD1009@hanna.meerval.net> <20171219030629.GD48369@shrubbery.net> <5A38D08E.8020206@foobar.org> <20171219084536.GB45648@Space.Net> <20171219085308.GI1009@hanna.meerval.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="5VdWixFsa3mDfEV+"
Content-Disposition: inline
In-Reply-To: <20171219085308.GI1009@hanna.meerval.net>
X-NCC-RegID: de.space
User-Agent: Mutt/1.8.2 (2017-04-18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/NUJF9YfTONWfmc_HB83Uil8beOI>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 09:50:34 -0000

--5VdWixFsa3mDfEV+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Tue, Dec 19, 2017 at 09:53:08AM +0100, Job Snijders wrote:
> Yes, route servers can be very useful, no question about it. I think
> their value as a service would increase if they become visible
> participants of the routing ecosystem.

Not sure about that.  IXP participants know where the route is coming
=66rom, and why should it be of anyone else's concern whether I have a
direct peering with you, or use a RS for it?

> Gert, do you think it would affect your operations if the route server
> would insert its ASN into the AS_PATH?

Yes.  BGP works by comparing AS path lengths, you know :-) - and that
would cause significant work as direct peerings would automatically
have shorter AS paths than via-route-server peerings.

Thus, traffic shift, which needs to compensated - like, by adding=20
extra prepends to direct peerings - which would have consequences for
the AS path lenghts seen by our customers.

In other words: we asked for AS-Path transparent RSes 15 years ago, and=20
this is still what we want today.

Gert Doering
        -- NetMaster
--=20
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279

--5VdWixFsa3mDfEV+
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEruB5jRHVM+CjiYD131bAZeTOf8UFAlo44OIACgkQ31bAZeTO
f8U2xw//U1NkJCMWUTbBL8YHE9HSHnrb8z3PTB657lV7HS1sZllYiXH1EDmm7n1x
SrxY6areGeyhdc8OC41MSovePnMdA+XF0OD7Qzs9nq7CLqeXRE7N56XccvRYKRYE
A1ZCZp+fGrQVZhEYYHNGfasYb2NHNy5/r3IOen26LyL9KtHaD2p1Tg5YPTlE81iK
+c9pVDMT/J/hY5HKXAqUtTgLUbLKWyyG87GDuAVUSuCBHSm8pRQlvvWRF5NMil8/
zA4HaB6wHURAzXl0/yV/JXU1VxBhOLw6uBlntIOvud4qAB0iKL2i6jweKqKXXnXv
/Soefs1BMSeNsbu9s8/gcbChPN/xE+/linWrG9FYM3HsLEwkPg4+n9dxg3w8RiJT
rJWOa0kSamOTSOrfTKYKiZ8bIhPdarb5Oz2vmRm3KIpKvEGeG1s2zvgIc048TA0G
hqWjTwpRmOMKxcJaf9+dBBs8mJkGDgzFhAlITfY3EIA5xY8ly7h6FYqeJ3irq1d1
arv+cIkei6xFS73+yq2uChBvWXPL0EiWj5XO3/niDaENFz0jAEaTFADOxjAZOyj9
cm4B7RZj4iFn+0Sn29pAGSfIupRhTXquGHc+CkSkY77xBNiReXjFd6eCJVfGsWUi
v+aQc0yyYa7RnxDYhA6ZnXKgrCcnZnvhD/GHySzKXgcZ1dCXCeI=
=k7Sz
-----END PGP SIGNATURE-----

--5VdWixFsa3mDfEV+--


From nobody Tue Dec 19 02:04:43 2017
Return-Path: <wolfgang.tremmel@de-cix.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0A1912DA15 for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 02:04:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 jK1fU1qfgTjZ for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 02:04:39 -0800 (PST)
Received: from de-cix.net (relay4.de-cix.net [46.31.123.2]) (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 E1AA412D96B for <grow@ietf.org>; Tue, 19 Dec 2017 02:04:38 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.45,426,1508796000";  d="scan'208";a="1147578"
Received: from smtp.de-cix.net ([192.168.65.10]) by mailgw014.de-cix.net with ESMTP; 19 Dec 2017 11:04:38 +0100
Received: from MS-EXCHANGE.for-the-inter.net (MS-EXCHANGE.for-the-inter.net [192.168.49.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by smtp.de-cix.net (Postfix) with ESMTPS id 1D7CFB00B8 for <grow@ietf.org>; Tue, 19 Dec 2017 11:04:37 +0100 (CET)
Received: from MS-EXCHANGE.for-the-inter.net (192.168.49.2) by MS-EXCHANGE.for-the-inter.net (192.168.49.2) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 19 Dec 2017 11:04:36 +0100
Received: from MS-EXCHANGE.for-the-inter.net ([fe80::9449:4d85:69bf:3d4c]) by MS-EXCHANGE.for-the-inter.net ([fe80::9449:4d85:69bf:3d4c%12]) with mapi id 15.00.1347.000; Tue, 19 Dec 2017 11:04:36 +0100
From: Wolfgang Tremmel <wolfgang.tremmel@de-cix.net>
To: "grow@ietf.org" <grow@ietf.org>
Thread-Topic: [GROW] Route Server ASN stripping hiding considered harmful?
Thread-Index: AQHTd+4PVg44UhhoNkeC7aeywwI31aNJIxAAgAAIYgCAAMCogIAAXWYAgAABWgCAAAIbAIAAEAaAgAAD8IA=
Date: Tue, 19 Dec 2017 10:04:36 +0000
Message-ID: <1D586150-F777-4A81-8110-577F42006C20@de-cix.net>
References: <20171218105034.GD43144@vurt.meerval.net> <5A37D990.2060505@foobar.org> <20171218153656.GD1009@hanna.meerval.net> <20171219030629.GD48369@shrubbery.net> <5A38D08E.8020206@foobar.org> <20171219084536.GB45648@Space.Net> <20171219085308.GI1009@hanna.meerval.net> <20171219095029.GC45648@Space.Net>
In-Reply-To: <20171219095029.GC45648@Space.Net>
Reply-To: "grow@ietf.org" <grow@ietf.org>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3445.5.20)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.168.140.42]
Content-Type: text/plain; charset="utf-8"
Content-ID: <46E7597968D26744B632050DAEECE689@for-the-inter.net>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/Y6DkXZ0FhHxYP0C34U3daETtPaQ>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 10:04:42 -0000

SGksDQoNCmZpcnN0IGEgcmVtYXJrOiBBdCBERS1DSVggY3VzdG9tZXJzIGNhbiBjaG9vc2UgaWYg
dGhleSB3YW50IHRoZSBSUyBBUyBpbiB0aGUgcGF0aCBvZiB0aGUgcHJlZml4ZXMgdGhleSByZWNl
aXZlIGZyb20gdGhlIFJTIG9yIG5vdCAodGhleSBuZWVkIHRvIHNlbmQgYW4gZW1haWwgdG8gc3Vw
cG9ydCB0byBjaGFuZ2UgdGhlIGNvbmZpZykuDQoNCkFub3RoZXIgdGhvdWdodCAtIHBsZWFzZSBj
b3JyZWN0IG1lIGlmIEkgYW0gdGFsa2luZyBydWJiaXNoIGFzIEkgaGF2ZSBvbmx5IGdsYW5jZWQg
YXQgdGhlIFJGQ3MuLi4NCg0KSWYgdGhlIFJTIHdvdWxkIGluc2VydCBpdHNlbGYgYXMgYW4gYWdn
cmVnYXRvciB3aXRoIHRoZSBsZWZ0bW9zdCBBUyBpbiB0aGUgcGF0aDogDQpUaGUgcGF0aCB3b3Vs
ZCBub3QgYmVjb21lIGFueSBsb25nZXIgYXMgQVNfU0VUcyBjb3VudCBhcyBvbmUgaG9wIGFuZCB0
aGUgUlMgd291bGQgYmUgdmlzaWJsZS4uLiANCg0KY2hlZXJzDQpXb2xmZ2FuZw0KDQotLSANCldv
bGZnYW5nIFRyZW1tZWwsIEhlYWQgb2YgREUtQ0lYIEFjYWRlbXkgICAgICAgICAgICAgICAgICAg
ICANCg0KUGhvbmUgKzQ5IDY5IDE3MzA5MDIgMCB8IEZheCArNDkgNjkgNDA1NiAyNzE2IHwgYWNh
ZGVteUBkZS1jaXgubmV0DQpHZXNjaGFlZnRzZnVlaHJlciBIYXJhbGQgQS4gU3VtbWEgfCBSZWdp
c3RlcmdlcmljaHQgQUcgS8O2bG4gSFJCIDUxMTM1DQpERS1DSVggTWFuYWdlbWVudCBHbWJIIHwg
TGluZGxleXN0cmFzc2UgMTIgfCA2MDMxNCBGcmFua2Z1cnQgYW0gTWFpbiB8IEdlcm1hbnkgfCB3
d3cuZGUtY2l4Lm5ldA0KDQo=


From nobody Tue Dec 19 02:08:07 2017
Return-Path: <job@instituut.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 697CC12D961 for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 02:08:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.669
X-Spam-Level: 
X-Spam-Status: No, score=-1.669 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 CUO8qALT8E_6 for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 02:08:05 -0800 (PST)
Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) (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 4991212D87E for <grow@ietf.org>; Tue, 19 Dec 2017 02:08:05 -0800 (PST)
Received: by mail-wm0-f45.google.com with SMTP id g75so2468012wme.0 for <grow@ietf.org>; Tue, 19 Dec 2017 02:08:05 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=YbnFo12s7+VJ7cClvis0mBxvhCbTDJqlEB7295nGH3c=; b=nLUMZV14M79O3rd+jMcvCGibyOtmKTViZZX+XRfbhpj/kPCWmxCWTrTe1SK2yzpxdL QQJxfoy2+o7fu0y64vslMFawksvws7lM5EBM6pT+UzwpfgXcmY8N0q1Z363quEEBe1HY ncKUmgFogfFbImwfFLC5m4ufFV959MVv+2BQWehaocJq+fezR7NQSDNC6gP7AtvDNcwC tuiww5oefuDaNsKUXvWiXowErTJDeor4oIITb4suDKJh5lHb7htrDvkV8EF64r457cqy Z6TAcmk+NQbiLSxlqsa5ZNk6s8siNAFGgT04kO9qL/bf9/aBWWh0trpZ9N4xuQIMcosq jOlg==
X-Gm-Message-State: AKGB3mIUMMQH0i699mfcKICE4oqAlViKMZAwd2sT+RHO4Ks7Jn3mEyxZ aIhoG53WrRz8tzJx0Os7FoNT0g==
X-Google-Smtp-Source: ACJfBotVU8Zmd0Bv70RVU+Dh5heg28jFqN7+ab4KvimIP3aPhxs2Y+4wCAa70jYFa2b/Dm4EFAzFxg==
X-Received: by 10.28.141.209 with SMTP id p200mr2883450wmd.161.1513678078239;  Tue, 19 Dec 2017 02:07:58 -0800 (PST)
Received: from localhost ([2001:67c:208c:10:e938:68b3:3dfe:7a6d]) by smtp.gmail.com with ESMTPSA id s14sm11779389eds.78.2017.12.19.02.07.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Dec 2017 02:07:56 -0800 (PST)
Date: Tue, 19 Dec 2017 11:07:55 +0100
From: Job Snijders <job@ntt.net>
To: Gert Doering <gert@space.net>
Cc: grow@ietf.org
Message-ID: <20171219100755.GK1009@hanna.meerval.net>
References: <20171218105034.GD43144@vurt.meerval.net> <5A37D990.2060505@foobar.org> <20171218153656.GD1009@hanna.meerval.net> <20171219030629.GD48369@shrubbery.net> <5A38D08E.8020206@foobar.org> <20171219084536.GB45648@Space.Net> <20171219085308.GI1009@hanna.meerval.net> <20171219095029.GC45648@Space.Net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20171219095029.GC45648@Space.Net>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.9.1 (2017-09-22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/36ZV9ZV9dL3UGc5ENIhw-LXo7SY>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 10:08:06 -0000

On Tue, Dec 19, 2017 at 10:50:29AM +0100, Gert Doering wrote:
> On Tue, Dec 19, 2017 at 09:53:08AM +0100, Job Snijders wrote:
> > Yes, route servers can be very useful, no question about it. I think
> > their value as a service would increase if they become visible
> > participants of the routing ecosystem.
> 
> Not sure about that.  IXP participants know where the route is coming
> from, and why should it be of anyone else's concern whether I have a
> direct peering with you, or use a RS for it?

When route leaks or hijacks occur, I approach all ASNs in the AS_PATH to
figure out who originated it and which ASN(s) failed to apply filters. 

As I'm stating in this thread (ad nauseam), if the ASN of an involved
BGP operator is not visible, I can't approach them and help them improve
their operations.

When we look at a blogpost like https://radar.qrator.net/blog/born-to-hijack
it is easy to see that it is of paramount importance to ensure filters
are applied on _every_ boundary in the AS_PATH, also the ones that are
currently invisible.

> > Gert, do you think it would affect your operations if the route
> > server would insert its ASN into the AS_PATH?
> 
> Yes.  BGP works by comparing AS path lengths, you know :-) - and that
> would cause significant work as direct peerings would automatically
> have shorter AS paths than via-route-server peerings.
> 
> Thus, traffic shift, which needs to compensated - like, by adding
> extra prepends to direct peerings - which would have consequences for
> the AS path lenghts seen by our customers.
> 
> In other words: we asked for AS-Path transparent RSes 15 years ago,
> and this is still what we want today.

If I can summarize the above, you state "fiddling with the as_path
length would negatively affect my operations" - but do you agree with my
concern that a lack of visibility leads to a lack of accountability?

Kind regards,

Job


From nobody Tue Dec 19 04:37:09 2017
Return-Path: <nick@foobar.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79F8B126CD6 for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 04:37:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 ClHof7iW_N7p for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 04:37:04 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A06EB12778E for <grow@ietf.org>; Tue, 19 Dec 2017 04:37:03 -0800 (PST)
X-Envelope-To: grow@ietf.org
Received: from cupcake.local (089-101-195156.ntlworld.ie [89.101.195.156] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id vBJCawpb016709 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Dec 2017 12:36:59 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-195156.ntlworld.ie [89.101.195.156] (may be forged) claimed to be cupcake.local
Message-ID: <5A3907E9.3060101@foobar.org>
Date: Tue, 19 Dec 2017 12:36:57 +0000
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.22 (Macintosh/20171208)
MIME-Version: 1.0
To: Alexander Azimov <aa@qrator.net>
CC: Job Snijders <job@ntt.net>, grow@ietf.org
References: <20171218105034.GD43144@vurt.meerval.net> <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net> <36e13c57-ac32-9fe9-ef31-e59ab1bc0c21@i3d.net> <20171218150741.GC1009@hanna.meerval.net> <5A37DF7D.9040405@foobar.org> <20171218155418.GE1009@hanna.meerval.net> <5A37FD0E.5080306@foobar.org> <CAHgCvCPQPDmt7tqO0KVWZLgGbCkVKWucWr6h8d=yczVSuh1qAw@mail.gmail.com>
In-Reply-To: <CAHgCvCPQPDmt7tqO0KVWZLgGbCkVKWucWr6h8d=yczVSuh1qAw@mail.gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/bhAsrSm4hZpbJb17HbECiNeUm6o>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 12:37:07 -0000

Alexander,

I share your concerns, but we're not really discussing ISP filtering
politics, and there is a huge difference between an ISP providing a
partial peering transit service and an IXP.

The difference is that an ISP necessarily makes all the decisions about
what prefixes you receive as a customer, because you get a single bgp
feed from the ISP.  This means that the customer is 100% beholden to the
ISP about the selection of prefixes that is transmitted.

An IXP provides a platform and allows participants to make up their own
minds about what works best for them.  If party A wants to interconnect
with party B, then the IXP shouldn't interfere.  Same if party C doesn't
want to interconnect with party D.  It's their business and they can
make their own decisions.

The reason that IXPs are disinclined to insert the rsasn in a route
server feed is that a route server attempts to replicate what you would
see if you had bilateral peering sessions to all other RS clients.  If
the IXP operator inserts the rsasn, it's materially changing the bgp
feed and breaking the rough equivalence between bilateral and
multilateral peering.  This is generally considered to be a bad thing,
both by IXPs and by IXP participants.

Regarding loop detection, this isn't an issue at an IXP RS because the
RS does not participate in traffic forwarding.

If you have concerns about ISP behaviour, this isn't really something
that the IETF can deal with, except to say that stripping out the
next-hop ASN is stupid, dangerous and likely to end up causing routing
loops.  No doubt the people who did this are already aware of this, though.

Regarding Job's concerns, I agree that it would be more helpful if we
had some easy way of figuring out if there were a route server involved
in prefix propagation, but his proposed fix for this comes at a cost
which I think is too high for IXPs and IXP participants.  That, and the
fact that it doesn't solve the root problem relating to filter deployment.

Nick

Alexander Azimov wrote:
> Hi all,
> 
> I'd like to share my support to Job's position, and the reason isn't
> only 'transparency' or filtering (while they are worth to fight for).
> 
> I see as the core of the problem, that one ISP MUST add its AS Number in
> the AS_PATH and another ISP is permitted no to do it. Yes, one can tell
> me, that IXP doesn't provide transit, it provides only local
> connectivity, through L2 matrix, but does ISP becomes IXP if it provides
> local connectivity? Imagine a situation when a customer has a choice: to
> purchase partial transit (only customer cone) from ISP or to become a
> member of IX. The price for both services could be quite comparable, but
> customer is looking forward not only for lesser costs, but also for
> increase its margin, and even if ISP will have all IX members as
> customers, it will be less preferable because through IX the path will
> have -1 hop. Some ISPs are already asking themselves a question, maybe
> they can also remove their AS number, at least when announcing routes to
> customers? 
> 
> And this pandora box has been already opened, I can name several ISPs
> that provide transit and remove its ASN from AS_PATH attribute, some of
> them are removing it even when announcing routes to upstreams. It's not
> right, it violates BGP loop detection, but it has just same motivation
> as RS at IXP - to make their routes more preferable, make 'virtual
> direct' connections. Some of them even name themselves as IXPs. 
> 
> In BGPSec it's getting even worse with pCount = 0. There is a statement
> in section 7.2.:
> 
>     if a BGPsec speaker does not expect a peer AS to set its pCount=0 and
>        if an UPDATE message received from that peer violates this, then the
>        UPDATE message MUST be considered to be in error (see the list of
>        checks in Section 5.2).  See Section 8.4 for a discussion of security
>        considerations concerning pCount=0.
> 
> Well, I can assume that some transit providers will be checking this
> pCount value, but I don't believe it will be checked from the customer
> side (it's even impossible for all, except direct neighbor). It can end
> up with everybody setting pCount=0 and AS_PATH attribute will lose much
> of its current use cases.
> 
> 2017-12-18 20:38 GMT+03:00 Nick Hilliard <nick@foobar.org
> <mailto:nick@foobar.org>>:
> 
>     Job Snijders wrote:
>     > You and Martijn appear to argue that the 'best path selection'
>     > component should not be fiddled with, which leaves me wondering
>     > whether we have any other methods to implement a track record ala
>     > 'this path announcement passed through RS AS XYZ' other than
>     > communities. Or are you of the opinion that the lack of visibility is
>     > not a problem to begin with?
> 
>     communities are low-hanging fruit and non-intrusive, and probably not a
>     bad thing to do.
> 
>     If you plan to spend time and energy dealing with the underlying
>     problem, i.e. routing leaks, then I'd suggest continuing to work on
>     getting IXPs to implement prefix filtering on their route servers.  It's
>     laborious and thankless but will actually fix the problem in the longer
>     term - and it needs to be done anyway.
> 
>     Nick
> 
>     _______________________________________________
>     GROW mailing list
>     GROW@ietf.org <mailto:GROW@ietf.org>
>     https://www.ietf.org/mailman/listinfo/grow
>     <https://www.ietf.org/mailman/listinfo/grow>
> 
> 
> 
> 
> -- 
> | Alexander Azimov  | HLL l QRATOR
> | tel.: +7 499 241 81 92
> | mob.: +7 915 360 08 86
> | skype: mitradir
> | mailto: aa@qrator.net <mailto:aa@qrator.net>
> | visit: www.qrator.net <http://www.qrator.net/>


From nobody Tue Dec 19 04:54:17 2017
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57CAA126CD6 for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 04:54:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.629
X-Spam-Level: 
X-Spam-Status: No, score=-2.629 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 BRiiMQV63n_b for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 04:54:13 -0800 (PST)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BF3912DA6C for <grow@ietf.org>; Tue, 19 Dec 2017 04:54:13 -0800 (PST)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr21.francetelecom.fr (ESMTP service) with ESMTP id 14954C0C31; Tue, 19 Dec 2017 13:54:11 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.24]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id F084F4005D; Tue, 19 Dec 2017 13:54:10 +0100 (CET)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM7D.corporate.adroot.infra.ftgroup ([fe80::9044:c5ee:4dd2:4f16%19]) with mapi id 14.03.0361.001; Tue, 19 Dec 2017 13:54:10 +0100
From: <bruno.decraene@orange.com>
To: Job Snijders <job@ntt.net>
CC: "grow@ietf.org" <grow@ietf.org>
Thread-Topic: [GROW] Route Server ASN stripping hiding considered harmful?
Thread-Index: AQHTeBh9h2qHLl0MQU+5gRs1V0KKnqNKnaHw
Date: Tue, 19 Dec 2017 12:54:10 +0000
Message-ID: <23178_1513688051_5A390BF3_23178_44_1_53C29892C857584299CBF5D05346208A4792539A@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <20171218105034.GD43144@vurt.meerval.net> <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net> <36e13c57-ac32-9fe9-ef31-e59ab1bc0c21@i3d.net> <20171218150741.GC1009@hanna.meerval.net> <5A37DF7D.9040405@foobar.org> <20171218155418.GE1009@hanna.meerval.net>
In-Reply-To: <20171218155418.GE1009@hanna.meerval.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/uCAEY_S8JEetfYKnuUBkm4BlgUY>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 12:54:16 -0000

My 2 cents

> From: Job Snijders
>=20
[...]
 > The AS_PATH attribute serves multiple functions: its length is used as a
 > tie-breaker in best path selection, and the contents of the AS_PATH
 > itself serves as an (mutable) track record on what administrative
 > domains the announcement passed through.
=20
Good point.
I'm wondering if decoupling both would not be cleaner, and would avoid the =
incentive to "tweak" the AS Path.
One option would be to keep the AS Path for loop detection, administrative =
record, and policies.
Inter domain metric used for best path selection could be left for another =
field/data/extension. Yet given the incentive to tweak such data, we could =
even realize that since we can't trust it, we don't really need it. We coul=
d only let the end user (originator) express some high level policy (nomina=
l, backup1, backup2) using well known communities. (which indeed may also b=
e removed/changed by transit AS, but the end user could see it and negotiat=
e transparency though a contract).

Best regards,
--Bruno

>=20
 > You and Martijn appear to argue that the 'best path selection' component
 > should not be fiddled with, which leaves me wondering whether we have
 > any other methods to implement a track record ala 'this path
 > announcement passed through RS AS XYZ' other than communities. Or are
 > you of the opinion that the lack of visibility is not a problem to begin
 > with?
 >=20
 > Respectfully,
 >=20
 > Job
 >=20
 > _______________________________________________
 > GROW mailing list
 > GROW@ietf.org
 > https://www.ietf.org/mailman/listinfo/grow

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From nobody Tue Dec 19 05:28:59 2017
Return-Path: <md@Linux.IT>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2913812DA6C for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 05:28:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=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 AKhTA9ZJpoob for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 05:28:56 -0800 (PST)
Received: from attila.bofh.it (attila.bofh.it [IPv6:2001:4b78:2000::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CFF9129511 for <grow@ietf.org>; Tue, 19 Dec 2017 05:28:56 -0800 (PST)
Received: by attila.bofh.it (Postfix, from userid 10) id D62FE122820; Tue, 19 Dec 2017 14:28:53 +0100 (CET)
Received: by bongo.bofh.it (Postfix, from userid 1000) id 36EAA840322; Tue, 19 Dec 2017 14:28:42 +0100 (CET)
Date: Tue, 19 Dec 2017 14:28:42 +0100
To: grow@ietf.org
Message-ID: <20171219132842.GA27264@bongo.bofh.it>
References: <20171218105034.GD43144@vurt.meerval.net> <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net> <36e13c57-ac32-9fe9-ef31-e59ab1bc0c21@i3d.net> <20171218150741.GC1009@hanna.meerval.net> <5A37DF7D.9040405@foobar.org> <20171218155418.GE1009@hanna.meerval.net> <5A37FD0E.5080306@foobar.org> <CAHgCvCPQPDmt7tqO0KVWZLgGbCkVKWucWr6h8d=yczVSuh1qAw@mail.gmail.com> <5A3907E9.3060101@foobar.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="oyUTqETQ0mS9luUI"
Content-Disposition: inline
In-Reply-To: <5A3907E9.3060101@foobar.org>
User-Agent: Mutt/1.9.2 (2017-12-15)
From: md@Linux.IT (Marco d'Itri)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/K_NM1fJGNpj0-HFtlThFYo2mR3Q>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 13:28:58 -0000

--oyUTqETQ0mS9luUI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Dec 19, Nick Hilliard <nick@foobar.org> wrote:

> The reason that IXPs are disinclined to insert the rsasn in a route
> server feed is that a route server attempts to replicate what you would
> see if you had bilateral peering sessions to all other RS clients.  If
> the IXP operator inserts the rsasn, it's materially changing the bgp
> feed and breaking the rough equivalence between bilateral and
> multilateral peering.  This is generally considered to be a bad thing,
> both by IXPs and by IXP participants.
I agree. I understand that Job's goal is to be able to identify the RSes=20
in the path, and this can be done with much less operational troubles
with a well known community.

--=20
ciao,
Marco

--oyUTqETQ0mS9luUI
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQGzBAABCgAdFiEEGBsIcS5ipP0URKfyK/WlwSLE96QFAlo5FAoACgkQK/WlwSLE
96Q9+gv/co8l2Ts5AuEJnrTROvhvlMPyRW7qlZLTNJ6WIek/FpCO1Lectn8eS0gY
t9ukXusJxItyeuaOjt5R7Eu6Gd7uGZ3kk+6ahBJLBRXKCFVZbUceVp6m7pX/TqJh
zHTjNzvMYrlvtVKuDXBo8OYP1O8kgafbLYzCnNSMWDvqRhPfwv2Sg5mc0/O07db3
sFf7IPMiDNu7ltGkWK48PaO5Pby9GWeHsEsZHA7lvnvX6pn07I3J70OOaoT3Vrm/
16uLkSljFM6DLrGi/gEXIJ5guJoqMs0Ao9Wpjq7cvHewN/qFIYCVjj2Lm49R0gzX
37C+DEYr2mKwh5jhmmNV+od0FMakHsqlkuk08S8THUkdNaDowBnmvWhwtl7IYhld
HrfDEE89os1mNBjUzSdBzZM7rxjGBuY2+Ek5/0qUef0yeviHkonk6juSVgjFytzn
gG1HoLqF1HTn265IuNTifIbdv22g5mF9G0r/JN7+eWoTe/i0AtaZXX5QG0pGiSX6
a/zz8Vre
=hmlQ
-----END PGP SIGNATURE-----

--oyUTqETQ0mS9luUI--


From nobody Tue Dec 19 11:58:16 2017
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE27912D834 for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 11:58:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 s5XESjXEa4XQ for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 11:58:13 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id B0FB712D7FB for <grow@ietf.org>; Tue, 19 Dec 2017 11:58:13 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id B41E01E37C; Tue, 19 Dec 2017 15:02:17 -0500 (EST)
Date: Tue, 19 Dec 2017 15:02:17 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: Nick Hilliard <nick@foobar.org>
Cc: Job Snijders <job@ntt.net>, grow@ietf.org
Message-ID: <20171219200217.GT8708@pfrc.org>
References: <20171218105034.GD43144@vurt.meerval.net> <5A37BCC3.8040008@foobar.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5A37BCC3.8040008@foobar.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/BZ_hAjPJT4bVT7QwX_tyWjvKqJ8>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 19:58:15 -0000

On Mon, Dec 18, 2017 at 01:04:03PM +0000, Nick Hilliard wrote:
> It's also common practice for transit providers to use a single ASN
> spanning the globe e.g. 174, 2914, 3356, etc. What you're describing
> here is an aspect of the fact that that as-pathlen has not been a useful
> determinant for the bgp decision engine for many years.

While somewhat orthogonal to this discussion, path length (and thus
prepending) is about the only useful knob many BGP speakers have to try to
bias incoming traffic.  I suspect you mean something a bit different above.

> Updating rfc4271 would be more productive - and getting IXPs to filter
> ingress bgp feeds by default.

I hope to be retired before that level of "incremental update" is expected
to work in the Internet at large. :-)

-- Jeff

P.S. many providers provide knobs to ignore path length as a consideration.
No spec work is required.


From nobody Tue Dec 19 12:02:57 2017
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7A2812D7FB for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 12:02:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 DlWNkPI5Lu-z for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 12:02:55 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 0ABDA1270A0 for <grow@ietf.org>; Tue, 19 Dec 2017 12:02:55 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 2FD051E37C; Tue, 19 Dec 2017 15:06:59 -0500 (EST)
Date: Tue, 19 Dec 2017 15:06:59 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: "grow@ietf.org" <grow@ietf.org>
Message-ID: <20171219200658.GU8708@pfrc.org>
References: <20171218105034.GD43144@vurt.meerval.net> <5A37D990.2060505@foobar.org> <20171218153656.GD1009@hanna.meerval.net> <20171219030629.GD48369@shrubbery.net> <5A38D08E.8020206@foobar.org> <20171219084536.GB45648@Space.Net> <20171219085308.GI1009@hanna.meerval.net> <20171219095029.GC45648@Space.Net> <1D586150-F777-4A81-8110-577F42006C20@de-cix.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1D586150-F777-4A81-8110-577F42006C20@de-cix.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/F5f-Ehec9V8HPF0lqCOsahs5bi8>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 20:02:55 -0000

On Tue, Dec 19, 2017 at 10:04:36AM +0000, Wolfgang Tremmel wrote:
> Another thought - please correct me if I am talking rubbish as I have only glanced at the RFCs...
> 
> If the RS would insert itself as an aggregator with the leftmost AS in the path: 
> The path would not become any longer as AS_SETs count as one hop and the RS would be visible... 

This is a somewhat perverse hack... and work quite nicely. :-)

That said, sets offended enough people on this list and elsewhere (makes
bgpsec problematic) that it resulted in RFC 6472.

-- Jeff


From nobody Tue Dec 19 12:14:23 2017
Return-Path: <nick@foobar.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 382401270A0 for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 12:14:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 04XRopDi-2nU for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 12:14:17 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D99E126BF6 for <grow@ietf.org>; Tue, 19 Dec 2017 12:14:16 -0800 (PST)
X-Envelope-To: grow@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id vBJKEEaB076826 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Dec 2017 20:14:14 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
Message-ID: <5A397315.4020406@foobar.org>
Date: Tue, 19 Dec 2017 20:14:13 +0000
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.22 (Macintosh/20171208)
MIME-Version: 1.0
To: Jeffrey Haas <jhaas@pfrc.org>
CC: Job Snijders <job@ntt.net>, grow@ietf.org
References: <20171218105034.GD43144@vurt.meerval.net> <5A37BCC3.8040008@foobar.org> <20171219200217.GT8708@pfrc.org>
In-Reply-To: <20171219200217.GT8708@pfrc.org>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/ZMdLVQ6KrxYCayXddnhY4ljGp3c>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 20:14:22 -0000

Jeffrey Haas wrote:
> On Mon, Dec 18, 2017 at 01:04:03PM +0000, Nick Hilliard wrote:
>> It's also common practice for transit providers to use a single ASN
>> spanning the globe e.g. 174, 2914, 3356, etc. What you're describing
>> here is an aspect of the fact that that as-pathlen has not been a useful
>> determinant for the bgp decision engine for many years.
> 
> While somewhat orthogonal to this discussion, path length (and thus
> prepending) is about the only useful knob many BGP speakers have to try to
> bias incoming traffic.  I suspect you mean something a bit different above.

point taken, but I meant for outgoing: it's not useful when you have
upstream or peer global asns for outbound traffic.

>> Updating rfc4271 would be more productive - and getting IXPs to filter
>> ingress bgp feeds by default.
> 
> I hope to be retired before that level of "incremental update" is expected
> to work in the Internet at large. :-)

Probably hell would freeze over before consensus was reached on a
replacement decision engine.

> P.S. many providers provide knobs to ignore path length as a consideration.
> No spec work is required.

yeah, but you know dealing with ixp participants is hard.  IXPs are
firmly aimed at the mid- to low-end provider market, and often you're
dealing with people who just don't understand routing well or who don't
have time to twiddle knobs.  It's better policy to provide ixp
participants with simple guidelines and a well-managed 90% solution
rather than spend all day pushing them up the hill.

Nick


From nobody Tue Dec 19 12:17:15 2017
Return-Path: <gert@space.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D80212D837 for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 12:17:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] 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 i2Izo5mW1QUR for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 12:17:11 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9F611201F2 for <grow@ietf.org>; Tue, 19 Dec 2017 12:17:11 -0800 (PST)
X-Original-To: grow@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 3AFF4447D1 for <grow@ietf.org>; Tue, 19 Dec 2017 21:17:10 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 2911D4416C; Tue, 19 Dec 2017 21:17:10 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id 0FA3E35DD9; Tue, 19 Dec 2017 21:17:10 +0100 (CET)
Date: Tue, 19 Dec 2017 21:17:09 +0100
From: Gert Doering <gert@space.net>
To: Nick Hilliard <nick@foobar.org>
Cc: Jeffrey Haas <jhaas@pfrc.org>, grow@ietf.org, Job Snijders <job@ntt.net>
Message-ID: <20171219201709.GS45648@Space.Net>
References: <20171218105034.GD43144@vurt.meerval.net> <5A37BCC3.8040008@foobar.org> <20171219200217.GT8708@pfrc.org> <5A397315.4020406@foobar.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5A397315.4020406@foobar.org>
X-NCC-RegID: de.space
User-Agent: Mutt/1.8.2 (2017-04-18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/QToMutB5s9FaS935tHYWVoVrVYc>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 20:17:14 -0000

Hi,

On Tue, Dec 19, 2017 at 08:14:13PM +0000, Nick Hilliard wrote:
> yeah, but you know dealing with ixp participants is hard.  IXPs are
> firmly aimed at the mid- to low-end provider market, and often you're
> dealing with people who just don't understand routing well or who don't
> have time to twiddle knobs.  It's better policy to provide ixp
> participants with simple guidelines and a well-managed 90% solution
> rather than spend all day pushing them up the hill.

I like being pushed uphill :-) - but if I don't even have to *get* up
that hill, even better.  So, "what Nick says".

Gert Doering
        -- lazy ISP operator
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Tue Dec 19 13:51:19 2017
Return-Path: <ju1738@att.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85FE41200FC for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 13:51:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 TIbpDuO1y2yJ for <grow@ietfa.amsl.com>; Tue, 19 Dec 2017 13:51:15 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 AC11012D856 for <grow@ietf.org>; Tue, 19 Dec 2017 13:51:15 -0800 (PST)
Received: from pps.filterd (m0083689.ppops.net [127.0.0.1]) by m0083689.ppops.net-00191d01. (8.16.0.21/8.16.0.21) with SMTP id vBJLl75G047617; Tue, 19 Dec 2017 16:51:04 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0083689.ppops.net-00191d01. with ESMTP id 2ey8b9nkjc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 19 Dec 2017 16:51:04 -0500
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id vBJLp4L2005448; Tue, 19 Dec 2017 16:51:04 -0500
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id vBJLopxA004853 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 19 Dec 2017 16:50:58 -0500
Received: from zlp27127.vci.att.com (zlp27127.vci.att.com [135.66.87.31]) by mlpi409.sfdc.sbc.com (RSA Interceptor); Tue, 19 Dec 2017 21:50:37 GMT
Received: from zlp27127.vci.att.com (zlp27127.vci.att.com [127.0.0.1]) by zlp27127.vci.att.com (Service) with ESMTP id EB39540006FC; Tue, 19 Dec 2017 21:50:37 +0000 (GMT)
Received: from MISOUT7MSGHUBAG.ITServices.sbc.com (unknown [130.9.129.151]) by zlp27127.vci.att.com (Service) with ESMTPS id D848540006D5; Tue, 19 Dec 2017 21:50:37 +0000 (GMT)
Received: from MISOUT7MSGUSRCD.ITServices.sbc.com ([169.254.4.126]) by MISOUT7MSGHUBAG.ITServices.sbc.com ([130.9.129.151]) with mapi id 14.03.0361.001; Tue, 19 Dec 2017 16:50:37 -0500
From: "UTTARO, JAMES" <ju1738@att.com>
To: Jeffrey Haas <jhaas@pfrc.org>, Nick Hilliard <nick@foobar.org>
CC: "grow@ietf.org" <grow@ietf.org>, Job Snijders <job@ntt.net>
Thread-Topic: [GROW] Route Server ASN stripping hiding considered harmful?
Thread-Index: AQHTd+4RRPF5qSk7q0mD2NjSvDdySqNJZVCAgAIHL4D//8kewA==
Date: Tue, 19 Dec 2017 21:50:36 +0000
Message-ID: <B17A6910EEDD1F45980687268941550F366EE306@MISOUT7MSGUSRCD.ITServices.sbc.com>
References: <20171218105034.GD43144@vurt.meerval.net> <5A37BCC3.8040008@foobar.org> <20171219200217.GT8708@pfrc.org>
In-Reply-To: <20171219200217.GT8708@pfrc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.10.228.60]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-12-19_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1031 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1712190308
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/UkwLI2ilxXE99PydfhEnh6hWLLI>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2017 21:51:17 -0000

Interesting discussion, coming from the VPN space the selection of an AS as=
 a global or regional value has been a long discussion.. For better or wors=
e AS value per region forces a different paradigm than AS per global.. In t=
he VPN space we take great pains to not affect the AS or AS-Path at is mean=
ingful to customers. IMO AIGP is for more useful for selection for certain =
applications i.e 3107..

Jim Uttaro

-----Original Message-----
From: GROW [mailto:grow-bounces@ietf.org] On Behalf Of Jeffrey Haas
Sent: Tuesday, December 19, 2017 3:02 PM
To: Nick Hilliard <nick@foobar.org>
Cc: grow@ietf.org; Job Snijders <job@ntt.net>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?

On Mon, Dec 18, 2017 at 01:04:03PM +0000, Nick Hilliard wrote:
> It's also common practice for transit providers to use a single ASN
> spanning the globe e.g. 174, 2914, 3356, etc. What you're describing
> here is an aspect of the fact that that as-pathlen has not been a useful
> determinant for the bgp decision engine for many years.

While somewhat orthogonal to this discussion, path length (and thus
prepending) is about the only useful knob many BGP speakers have to try to
bias incoming traffic.  I suspect you mean something a bit different above.

> Updating rfc4271 would be more productive - and getting IXPs to filter
> ingress bgp feeds by default.

I hope to be retired before that level of "incremental update" is expected
to work in the Internet at large. :-)

-- Jeff

P.S. many providers provide knobs to ignore path length as a consideration.
No spec work is required.

_______________________________________________
GROW mailing list
GROW@ietf.org
https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mailman=
_listinfo_grow&d=3DDwICAg&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3D3qhKphE8RnwJQ6u8Mr=
AGeA&m=3Dpj_0O26biD9_MZUbccTTQ2LlWH2PMPXLuRPgQU0olFs&s=3D8K5jqMaS-4xLe7x_zF=
LoLUZOCAkHEMuARWekULTt39A&e=3D=20


From nobody Wed Dec 20 01:07:48 2017
Return-Path: <randy@psg.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF2012D967 for <grow@ietfa.amsl.com>; Wed, 20 Dec 2017 01:07:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level: 
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 v1xV1euFwz_n for <grow@ietfa.amsl.com>; Wed, 20 Dec 2017 01:07:37 -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 A75FC12D864 for <grow@ietf.org>; Wed, 20 Dec 2017 01:07:37 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1eRaLc-0005yv-7B; Wed, 20 Dec 2017 09:07:32 +0000
Date: Wed, 20 Dec 2017 10:07:31 +0100
Message-ID: <m2efnpojho.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Nick Hilliard <nick@foobar.org>
Cc: Job Snijders <job@ntt.net>, grow@ietf.org
In-Reply-To: <5A37DF7D.9040405@foobar.org>
References: <20171218105034.GD43144@vurt.meerval.net> <3f590dcc-da77-6349-6d36-cbd22c0b9693@nordu.net> <36e13c57-ac32-9fe9-ef31-e59ab1bc0c21@i3d.net> <20171218150741.GC1009@hanna.meerval.net> <5A37DF7D.9040405@foobar.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 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/grow/sMXC4gRdWrTcNDySSlOfxem41Vo>
Subject: Re: [GROW] Route Server ASN stripping hiding considered harmful?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Dec 2017 09:07:46 -0000

if the rs injects it as, then traffic will be biased against rs paths

randy

