Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

[Theodore Baschak]

> On Mar 20, 2017, at 12:29 PM, Tore Anderson  wrote:
> 
> * Ben Maddison
> 
>> Fully support this. It adds a much needed sanity check to the
>> behavior of BGP in the wild.
> 
> Concur.
> 
> Tore

Many new/inexperienced operators who go from 1 to 2 upsteams will continue to  
cause leaks and experience problems until this is default.

Fully support this default behavior.

Theodore Baschak - AS395089 - Hextet Systems
https://bgp.guru/ - https://hextet.net/
http://mbix.ca/ - http://mbnog.ca/

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

Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

[Tore Anderson]

* Ben Maddison

> Fully support this. It adds a much needed sanity check to the
> behavior of BGP in the wild.

Concur.

Tore

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

Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

[Susan Hares]

+1 to change - good catch by Ignas. 

Sue 

-Original Message-
From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of Job Snijders
Sent: Monday, March 20, 2017 10:43 AM
To: Ignas Bagdonas
Cc: grow-cha...@ietf.org; grow@ietf.org grow@ietf.org;
grow-...@tools.ietf.org
Subject: Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar
19)

On Mon, Mar 20, 2017 at 02:06:13PM +, Ignas Bagdonas wrote:
> Fully support. Speaking as an operator, this is the right thing to do, 
> and it has been deployed as a standard practice either natively if 
> implementations do support this now or as an initial policy 
> preconfiguration if it is not yet supported.
> 
> A small nit on the clarity of the applicability to al address families 
> - the way how it is worded now seems to assume global and VPN address 
> families only. What about explicitly requiring all address families 
> active on the session to be affected by this?
> 
> OLD:
>This specification intends to improve this situation by requiring the
>explicit configuration of a BGP import and export policy for any
>External BGP (EBGP) session such as customers, peers, or
>confederation boundaries in a base router or VPN instances.
> 
> NEW:
>This specification intends to improve this situation by requiring the
>explicit configuration of a BGP import and export policy for any
>External BGP (EBGP) session such as customers, peers, or
>confederation boundaries for all enabled address families.

I'd like to incorporate your suggestion, I agree it adds clarity.

Kind regards,

Job

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

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

Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

[Job Snijders]

On Mon, Mar 20, 2017 at 02:06:13PM +, Ignas Bagdonas wrote:
> Fully support. Speaking as an operator, this is the right thing to do, and
> it has been deployed as a standard practice either natively if
> implementations do support this now or as an initial policy preconfiguration
> if it is not yet supported.
> 
> A small nit on the clarity of the applicability to al address families - the
> way how it is worded now seems to assume global and VPN address families
> only. What about explicitly requiring all address families active on the
> session to be affected by this?
> 
> OLD:
>This specification intends to improve this situation by requiring the
>explicit configuration of a BGP import and export policy for any
>External BGP (EBGP) session such as customers, peers, or
>confederation boundaries in a base router or VPN instances.
> 
> NEW:
>This specification intends to improve this situation by requiring the
>explicit configuration of a BGP import and export policy for any
>External BGP (EBGP) session such as customers, peers, or
>confederation boundaries for all enabled address families.

I'd like to incorporate your suggestion, I agree it adds clarity.

Kind regards,

Job

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

Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

[Ignas Bagdonas]

Fully support. Speaking as an operator, this is the right thing to do, 
and it has been deployed as a standard practice either natively if 
implementations do support this now or as an initial policy 
preconfiguration if it is not yet supported.


A small nit on the clarity of the applicability to al address families - 
the way how it is worded now seems to assume global and VPN address 
families only. What about explicitly requiring all address families 
active on the session to be affected by this?


OLD:
   This specification intends to improve this situation by requiring the
   explicit configuration of a BGP import and export policy for any
   External BGP (EBGP) session such as customers, peers, or
   confederation boundaries in a base router or VPN instances.

NEW:
   This specification intends to improve this situation by requiring the
   explicit configuration of a BGP import and export policy for any
   External BGP (EBGP) session such as customers, peers, or
   confederation boundaries for all enabled address families.

Ignas


On 20/03/2017 01:47, Christopher Morrow wrote:

Howdy folks!
There were 3 people, 4 if you include me, that had something to say 
here...


it'd be nice if a few more folk had read through and agreed/disagreed :)

I'll delay decision making until Tues (3/21/2017)... read and respond 
pls :)

-chris

On Sun, Mar 5, 2017 at 4:30 PM, Christopher Morrow 
> 
wrote:


Howdy WG folks,
This request starts the WGLC for:
  >

with abstract:
  "This document defines the default behavior of a BGP speaker when
   there is no import or export policy associated with an External BGP
   session."

please have a read-through, decide if this needs more work and
then speak up on list.
thanks!
-chris
co-chair-personage.




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


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

Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

[Smith, Donald]

Support, the basic concept that if I am not configured to speak to you, I don't 
listen, nor announce to you, is sound and should be the default behavior.







if (initial_ttl!=255) then (rfc5082_compliant==0)
donald.sm...@centurylink.com<mailto:donald.sm...@centurylink.com>

From: GROW [grow-boun...@ietf.org] on behalf of Susan Hares [sha...@ndzh.com]
Sent: Monday, March 20, 2017 5:36 AM
To: 'Christopher Morrow'; grow@ietf.org; grow-...@tools.ietf.org; 
grow-cha...@ietf.org
Subject: Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

Grow folks:

Section 2 aligns with the intent of RFC4271.   I feel this concise draft 
address appropriate security considerations. I believe this drafts is ready 
from a technical viewpoint for publication.
I am not an operator of a network, so I cannot comment on operator issues.

Sue

From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of Christopher Morrow
Sent: Sunday, March 19, 2017 9:48 PM
To: grow@ietf.org grow@ietf.org; grow-...@tools.ietf.org; grow-cha...@ietf.org
Subject: Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

Howdy folks!
There were 3 people, 4 if you include me, that had something to say here...

it'd be nice if a few more folk had read through and agreed/disagreed :)

I'll delay decision making until Tues (3/21/2017)... read and respond pls :)
-chris

On Sun, Mar 5, 2017 at 4:30 PM, Christopher Morrow 
<christopher.mor...@gmail.com<mailto:christopher.mor...@gmail.com>> wrote:
Howdy WG folks,
This request starts the WGLC for:
  <https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-reject/>

with abstract:
  "This document defines the default behavior of a BGP speaker when
   there is no import or export policy associated with an External BGP
   session."

please have a read-through, decide if this needs more work and then speak up on 
list.
thanks!
-chris
co-chair-personage.

This communication is the property of CenturyLink and may contain confidential 
or privileged information. Unauthorized use of this communication is strictly 
prohibited and may be unlawful. If you have received this communication in 
error, please immediately notify the sender by reply e-mail and destroy all 
copies of the communication and any attachments.
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow

Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

[Susan Hares]

Grow folks: 

 

Section 2 aligns with the intent of RFC4271.   I feel this concise draft 
address appropriate security considerations. I believe this drafts is ready 
from a technical viewpoint for publication.  

I am not an operator of a network, so I cannot comment on operator issues. 

 

Sue 

 

From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of Christopher Morrow
Sent: Sunday, March 19, 2017 9:48 PM
To: grow@ietf.org grow@ietf.org; grow-...@tools.ietf.org; grow-cha...@ietf.org
Subject: Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

 

Howdy folks!

There were 3 people, 4 if you include me, that had something to say here... 

 

it'd be nice if a few more folk had read through and agreed/disagreed :)

 

I'll delay decision making until Tues (3/21/2017)... read and respond pls :)

-chris

 

On Sun, Mar 5, 2017 at 4:30 PM, Christopher Morrow 
<christopher.mor...@gmail.com> wrote:

Howdy WG folks,

This request starts the WGLC for:
  <https://datatracker.ietf.org/doc/draft-ietf-grow-bgp-reject/>

 

with abstract:
  "This document defines the default behavior of a BGP speaker when

   there is no import or export policy associated with an External BGP

   session."

 

please have a read-through, decide if this needs more work and then speak up on 
list.

thanks!

-chris

co-chair-personage.

 

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

Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

[Dickinson, Ian]

Concur. This is a sane default that would have avoid many leaks over the years, 
so I support this.

Ian

-Original Message-
From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of Nick Hilliard
Sent: 20 March 2017 11:24
To: Christopher Morrow <christopher.mor...@gmail.com>
Cc: grow-cha...@ietf.org; grow@ietf.org grow@ietf.org <grow@ietf.org>; 
grow-...@tools.ietf.org
Subject: Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

Christopher Morrow wrote:
> Howdy folks!
> There were 3 people, 4 if you include me, that had something to say here... 
> 
> it'd be nice if a few more folk had read through and agreed/disagreed :)

violent support for this.

This is something that should have been in bgp on day one, and its
omission has caused and continues to cause a tremendous amount of damage
on the internet.

Nick

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

Information in this email including any attachments may be privileged, 
confidential and is intended exclusively for the addressee. The views expressed 
may not be official policy, but the personal views of the originator. If you 
have received it in error, please notify the sender by return e-mail and delete 
it from your system. You should not reproduce, distribute, store, retransmit, 
use or disclose its contents to anyone. Please note we reserve the right to 
monitor all e-mail communication through our internal and external networks. 
SKY and the SKY marks are trademarks of Sky plc and Sky International AG and 
are used under licence.
Sky UK Limited (Registration No. 2906991), Sky-In-Home Service Limited 
(Registration No. 2067075) and Sky Subscribers Services Limited (Registration 
No. 2340150) are direct or indirect subsidiaries of Sky plc (Registration No. 
2247735). All of the companies mentioned in this paragraph are incorporated in 
England and Wales and share the same registered office at Grant Way, Isleworth, 
Middlesex TW7 5QD.

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

Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

[Nick Hilliard]

Christopher Morrow wrote:
> Howdy folks!
> There were 3 people, 4 if you include me, that had something to say here... 
> 
> it'd be nice if a few more folk had read through and agreed/disagreed :)

violent support for this.

This is something that should have been in bgp on day one, and its
omission has caused and continues to cause a tremendous amount of damage
on the internet.

Nick

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

Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

[Jared Mauch]

On Sun, Mar 19, 2017 at 09:47:30PM -0400, Christopher Morrow wrote:
> Howdy folks!
> There were 3 people, 4 if you include me, that had something to say here...
> 
> it'd be nice if a few more folk had read through and agreed/disagreed :)
> 
> I'll delay decision making until Tues (3/21/2017)... read and respond pls :)

I have read this and support it :-)

- Jared

-- 
Jared Mauch  | pgp key available via finger from ja...@puck.nether.net
clue++;  | http://puck.nether.net/~jared/  My statements are only mine.

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

Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

[Gert Doering]

Hi,

On Sun, Mar 05, 2017 at 04:30:00PM -0500, Christopher Morrow wrote:
> Howdy WG folks,
> This request starts the WGLC for:
>   
> 
> with abstract:
>   "This document defines the default behavior of a BGP speaker when
>there is no import or export policy associated with an External BGP
>session."
> 
> please have a read-through, decide if this needs more work and then speak
> up on list.

Still supporting it.  Go for it.

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

SpaceNet AGVorstand: 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

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