> On Nov 5, 2015, at 2:44 PM, Jared Mauch wrote:
>
>
>> On Nov 2, 2015, at 2:04 AM, Jeffrey Haas wrote:
>>
>> I suggest it be considered for BCP status. Why BCP? Because operators
>> already have to go do this for the safety of their network and are doing so
>> via configuration template.
> On Nov 2, 2015, at 4:37 AM, Gert Doering wrote:
> 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
> On Nov 2, 2015, at 2:04 AM, Jeffrey Haas wrote:
>
> I suggest it be considered for BCP status. Why BCP? Because operators
> already have to go do this for the safety of their network and are doing so
> via configuration template.
How do we get the implementors to adhere to this BCP?
- Ja
On 05/11/15 10:20, Jon Mitchell wrote:
> Nit for author - any reason why such short abbreviation for ADDPATH (AP)
> in section 4/5 subtypes while unicast/multicast spelled out - would it
> be more readable as ADDPATH?
I was using the 'AS4' abbreviation that is already in place as a suggestion.
S
> On Nov 2, 2015, at 3:57 PM, 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 pol
> On Nov 2, 2015, at 6:37 PM, Gert Doering wrote:
>
> 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, ple
On 02/11/15 17:48 +1100, Christopher Morrow wrote:
> 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
>
