Re: [GROW] Working Group Adoption Call: draft-mauch-bgp-reject

2015-11-02 Thread Thomas King
Hi all,

I support the adaption of this draft.

Best regards,
Thomas

> On 2 Nov 2015, at 15:57, Christopher Morrow  
> wrote:
> 
> Howdy Grow folk (again),
> Please consider this as the start of a 3wk working group adoption call
> for the subject draft who's abstract is:
> 
>  "This document defines the default behaviour of a BGP speaker when no
>   explicit policy is associated with a BGP peering session."
> 
> Please read/comment/advise before 11/23/2015 - Nov 23, 2015.
> 
> Thanks!
> -chris
> grow-co-chair
> 
> ___
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


-- 
Dr. Thomas King
Manager Research & Development

DE-CIX Management GmbH | Lindleystraße 12 | 60314 Frankfurt am Main | Germany | 
www.de-cix.net |
Phone +49 69 1730902 87 | Mobile +49 175 1161428 | Fax +49 69 4056 2716 | 
thomas.k...@de-cix.net |
Geschaeftsfuehrer Harald A. Summa | Registergericht AG Koeln HRB 51135





smime.p7s
Description: S/MIME cryptographic signature
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow


Re: [GROW] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths

2015-11-02 Thread Thomas King
Hi all,

I support this draft as Add-Path is important as well as MRT is.

Best regards,
Thomas

> On 2 Nov 2015, at 15:48, Christopher Morrow  
> wrote:
> 
> Howdy WG folks,
> 
> Please consider this the start of a 3 week Adoption call for the noted
> draft who's abstract is:
>   "This document updates the Multi-threaded Routing Toolkit (MRT) export
>   format for Border Gateway Protocol (BGP) routing information by
>   extending it to support the Advertisement of Multiple Paths in BGP
>   extensions."
> 
> Please read/comment/advise by:
>  11/23/2015 - Nov 23 2015
> 
> thanks!
> -chris
> grow-co-chair
> 
> ___
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


smime.p7s
Description: S/MIME cryptographic signature
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow


Re: [GROW] Working Group Adoption Call: draft-mauch-bgp-reject

2015-11-02 Thread Sriram, Kotikalapudi
I support and will help with review.

Sriram


From: GROW  on behalf of Christopher Morrow 

Sent: Monday, November 2, 2015 1:57 AM
To: grow-cha...@ietf.org; grow-...@tools.ietf.org; grow@ietf.org grow@ietf.org
Subject: [GROW] Working Group Adoption Call: draft-mauch-bgp-reject

Howdy Grow folk (again),
Please consider this as the start of a 3wk working group adoption call
for the subject draft who's abstract is:

  "This document defines the default behaviour of a BGP speaker when no
   explicit policy is associated with a BGP peering session."

Please read/comment/advise before 11/23/2015 - Nov 23, 2015.

Thanks!
-chris
grow-co-chair

___
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] Working Group Adoption Call: draft-mauch-bgp-reject

2015-11-02 Thread Russ White
 
> Please read/comment/advise before 11/23/2015 - Nov 23, 2015.

Support -- very much worth progressing.

:-)

Russ

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


Re: [GROW] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths

2015-11-02 Thread joel jaeggli
On 11/3/15 7:12 AM, Susan Hares wrote:
> Multiple paths are a fact of life in many BGP deployments.  Please accept
> and publish soon. 

+1

> Sue Hares
> 
> -Original Message-
> From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of heasley
> Sent: Monday, November 02, 2015 11:25 AM
> To: Jeffrey Haas
> Cc: grow-cha...@ietf.org; grow@ietf.org grow@ietf.org;
> grow-...@tools.ietf.org
> Subject: Re: [GROW] Working Group Adoption Call:
> draft-petrie-grow-mrt-add-paths
> 
> Mon, Nov 02, 2015 at 05:27:15PM +0900, Jeffrey Haas:
>>> Please consider this the start of a 3 week Adoption call for the 
>>> noted draft who's abstract is:
>>>   "This document updates the Multi-threaded Routing Toolkit (MRT) export
>>>   format for Border Gateway Protocol (BGP) routing information by
>>>   extending it to support the Advertisement of Multiple Paths in BGP
>>>   extensions."
>>
>> IMO, this one is a no-brainer.  I encourage adoption, swift editing and
> then ship as an RFC.
> 
> Agree with Jeff.
> 
> ___
> 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
> 




signature.asc
Description: OpenPGP digital signature
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow


Re: [GROW] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths

2015-11-02 Thread Susan Hares
Multiple paths are a fact of life in many BGP deployments.  Please accept
and publish soon. 

Sue Hares

-Original Message-
From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of heasley
Sent: Monday, November 02, 2015 11:25 AM
To: Jeffrey Haas
Cc: grow-cha...@ietf.org; grow@ietf.org grow@ietf.org;
grow-...@tools.ietf.org
Subject: Re: [GROW] Working Group Adoption Call:
draft-petrie-grow-mrt-add-paths

Mon, Nov 02, 2015 at 05:27:15PM +0900, Jeffrey Haas:
> > Please consider this the start of a 3 week Adoption call for the 
> > noted draft who's abstract is:
> >   "This document updates the Multi-threaded Routing Toolkit (MRT) export
> >   format for Border Gateway Protocol (BGP) routing information by
> >   extending it to support the Advertisement of Multiple Paths in BGP
> >   extensions."
> 
> IMO, this one is a no-brainer.  I encourage adoption, swift editing and
then ship as an RFC.

Agree with Jeff.

___
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] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths

2015-11-02 Thread heasley
Mon, Nov 02, 2015 at 05:27:15PM +0900, Jeffrey Haas:
> > Please consider this the start of a 3 week Adoption call for the noted
> > draft who's abstract is:
> >   "This document updates the Multi-threaded Routing Toolkit (MRT) export
> >   format for Border Gateway Protocol (BGP) routing information by
> >   extending it to support the Advertisement of Multiple Paths in BGP
> >   extensions."
> 
> IMO, this one is a no-brainer.  I encourage adoption, swift editing and then 
> ship as an RFC.

Agree with Jeff.

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


Re: [GROW] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths

2015-11-02 Thread Thomas Mangin
I support the adoption of this draft.

Thomas

http://exa.net.uk/about/contact-us
On 2 Nov 2015, at 6:48, Christopher Morrow wrote:

> Howdy WG folks,
>
> Please consider this the start of a 3 week Adoption call for the noted
> draft who's abstract is:
>  "This document updates the Multi-threaded Routing Toolkit (MRT) export
>  format for Border Gateway Protocol (BGP) routing information by
>  extending it to support the Advertisement of Multiple Paths in BGP
>  extensions."
>
> Please read/comment/advise by:
> 11/23/2015 - Nov 23 2015
>
> thanks!
> -chris
> grow-co-chair
>
> ___
> 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] draft-mauch-bgp-reject

2015-11-02 Thread Nick Hilliard
On 02/11/2015 04:18, Jared Mauch wrote:
> I plan on covering this briefly in the GROW meeting today and uploaded
> the revised text that has been sitting in my output queue since August.
> 
> This is basically codifying the fact that you MUST NOT default to "bgp
> unsafe-ebgp-policy” for any BGP speaking device.

definitely support.

Long overdue.  Also, sad that we need to actually document something as
basic as this.

Nick

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


Re: [GROW] draft-mauch-bgp-reject

2015-11-02 Thread Gert Doering
Hi,

On Sun, Nov 01, 2015 at 11:18:55PM -0500, Jared Mauch wrote:
> I plan on covering this briefly in the GROW meeting today and uploaded the 
> revised text that has been sitting in my output queue since August.
> 
> This is basically codifying the fact that you MUST NOT default to "bgp 
> unsafe-ebgp-policy??? for any BGP speaking device.

There is one item I don't understand here:

   o  Software MUST provide protection from internal failures preventing
  the advertisement and acceptance of routes

what does that mean (in other words "more verbose explanation, please")?

(All the rest is obviously the right way forward, so "support!" and "BCP!")

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


Re: [GROW] Working Group Adoption Call: draft-mauch-bgp-reject

2015-11-02 Thread Jeff Tantsura
Yes, support

Cheers,
Jeff






>
>On Mon, Nov 02, 2015 at 05:57:54PM +1100, Christopher Morrow wrote:
>> Howdy Grow folk (again),
>> Please consider this as the start of a 3wk working group adoption call
>> for the subject draft who's abstract is:
>> 
>>   "This document defines the default behaviour of a BGP speaker when no
>>explicit policy is associated with a BGP peering session."
>> 
>> Please read/comment/advise before 11/23/2015 - Nov 23, 2015.
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow


Re: [GROW] Working Group Adoption Call: draft-mauch-bgp-reject

2015-11-02 Thread Gert Doering
Hi,

On Mon, Nov 02, 2015 at 05:57:54PM +1100, Christopher Morrow wrote:
> Howdy Grow folk (again),
> Please consider this as the start of a 3wk working group adoption call
> for the subject draft who's abstract is:
> 
>   "This document defines the default behaviour of a BGP speaker when no
>explicit policy is associated with a BGP peering session."
> 
> Please read/comment/advise before 11/23/2015 - Nov 23, 2015.

Yes, please.  Support.

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


Re: [GROW] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths

2015-11-02 Thread Jeffrey Haas

> On Nov 2, 2015, at 3:48 PM, Christopher Morrow  
> wrote:
> 
> Howdy WG folks,
> 
> Please consider this the start of a 3 week Adoption call for the noted
> draft who's abstract is:
>   "This document updates the Multi-threaded Routing Toolkit (MRT) export
>   format for Border Gateway Protocol (BGP) routing information by
>   extending it to support the Advertisement of Multiple Paths in BGP
>   extensions."

IMO, this one is a no-brainer.  I encourage adoption, swift editing and then 
ship as an RFC.

-- Jeff

> 
> Please read/comment/advise by:
>  11/23/2015 - Nov 23 2015
> 
> thanks!
> -chris
> grow-co-chair
> 
> ___
> 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] Working Group Adoption Call: draft-mauch-bgp-reject

2015-11-02 Thread Susan Hares
Support.  Warren – I agree with your comment.

 

Sue 

 

From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of Warren Kumari
Sent: Monday, November 02, 2015 2:19 AM
To: Christopher Morrow
Cc: grow-cha...@ietf.org; grow@ietf.org grow@ietf.org; grow-...@tools.ietf.org
Subject: Re: [GROW] Working Group Adoption Call: draft-mauch-bgp-reject

 



On Monday, November 2, 2015, Christopher Morrow  
wrote:

Howdy Grow folk (again),
Please consider this as the start of a 3wk working group adoption call
for the subject draft who's abstract is:

  "This document defines the default behaviour of a BGP speaker when no
   explicit policy is associated with a BGP peering session."

Please read/comment/advise before 11/23/2015 - Nov 23, 2015.

 

 

Yah.

 

This shouldn't be needed... but is. 

Support adoption, willing to edit / contribute / review / whatever is needed.

 

W

 

 

Thanks!
-chris
grow-co-chair

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



-- 
I don't think the execution is relevant when it was obviously a bad idea in the 
first place.
This is like putting rabid weasels in your pants, and later expressing regret 
at having chosen those particular rabid weasels and that pair of pants.
   ---maf

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


Re: [GROW] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths

2015-11-02 Thread Job Snijders
I support adoption of this draft. 

Job

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