On Tue, Jun 20, 2017 at 02:48:51PM -0500, Greg Mirsky wrote:
> Hi Jeff,
> thank you for the great summary of the discussion, helps me to catch the
> wave.
> I'm skeptical that there's realistic scenario where two BFD systems will be
> requested to run multiple BFD single-hop session between them
Hi Jeff,
thank you for the great summary of the discussion, helps me to catch the
wave.
I'm skeptical that there's realistic scenario where two BFD systems will be
requested to run multiple BFD single-hop session between them over the same
interfaces (logical or physical). I believe that we should
Greg,
On Tue, Jun 20, 2017 at 12:55:58PM -0500, Greg Mirsky wrote:
> Hi Jeff,
> I'd like to hear from others who are familiar with implementations of BFD
> that supports per protocol single-hop BFD multi-sessions between the same
> pair of BFD systems. RFC 5881 does allow per protocol single-hop
On 6/20/17, 1:50 PM, "Mahesh Jethanandani" wrote:
>
>> On Jun 20, 2017, at 8:40 AM, Acee Lindem (acee) wrote:
>>
>> Hi Jeff,
>>
>> On 6/20/17, 10:58 AM, "Jeffrey Haas" wrote:
>>
>>> Les,
>>>
>>> On Tue, Jun 20, 2017 at 02:25:12PM
Hi Jeff,
I'd like to hear from others who are familiar with implementations of BFD
that supports per protocol single-hop BFD multi-sessions between the same
pair of BFD systems. RFC 5881 does allow per protocol single-hop sessions
on the same interface, logical or physical, between the same pair
> On Jun 20, 2017, at 8:40 AM, Acee Lindem (acee) wrote:
>
> Hi Jeff,
>
> On 6/20/17, 10:58 AM, "Jeffrey Haas" wrote:
>
>> Les,
>>
>> On Tue, Jun 20, 2017 at 02:25:12PM +, Les Ginsberg (ginsberg) wrote:
Different protocols have different
Hi Jeff,
On 6/20/17, 10:58 AM, "Jeffrey Haas" wrote:
>Les,
>
>On Tue, Jun 20, 2017 at 02:25:12PM +, Les Ginsberg (ginsberg) wrote:
>> > Different protocols have different survivability requirements. An
>>IGP may
>> > very well want sub-second timers, potentially for repair
On Mon, Jun 19, 2017 at 9:19 PM, Xuxiaohu wrote:
> Hi Alia,
>
>
>
> Thanks a lot for your AD review. Please see our response inline.
>
>
>
> *发件人**:* Alia Atlas [mailto:akat...@gmail.com ]
> *发送时间**:* 2017年6月15日 6:56
> *收件人**:* OSPF List;
Les,
On Tue, Jun 20, 2017 at 02:25:12PM +, Les Ginsberg (ginsberg) wrote:
> > Different protocols have different survivability requirements. An IGP may
> > very well want sub-second timers, potentially for repair behaviors. BGP may
> > want fast failover, but may be fine with second level
Jeff -
Inline.
> -Original Message-
> From: Rtg-bfd [mailto:rtg-bfd-boun...@ietf.org] On Behalf Of Jeffrey Haas
> Sent: Tuesday, June 20, 2017 7:17 AM
> To: Mahesh Jethanandani
> Cc: Jeffrey Haas; Reshad Rahman (rrahman); OSPF WG List; draft-ietf-ospf-
> y...@ietf.org; rtg-...@ietf.org;
Jeff,
On 6/20/17, 10:20 AM, "Jeffrey Haas" wrote:
>Acee,
>
>On Mon, Jun 19, 2017 at 10:10:43PM +, Acee Lindem (acee) wrote:
>> I don’t really feel there is a strong requirement to support different
>> timers values per protocol even though several implementations allow
>>
Hi Jeff, Mahesh,
See a couple inlines.
On 6/20/17, 10:16 AM, "Jeffrey Haas" wrote:
>Mahesh,
>
>On Mon, Jun 19, 2017 at 03:11:25PM -0700, Mahesh Jethanandani wrote:
>> > On Jun 19, 2017, at 11:57 AM, Jeffrey Haas wrote:
>> > Where we run into some issues are
Acee,
On Mon, Jun 19, 2017 at 10:10:43PM +, Acee Lindem (acee) wrote:
> I don’t really feel there is a strong requirement to support different
> timers values per protocol even though several implementations allow
> different protocol specific values to be configured (with varying
>
Mahesh,
On Mon, Jun 19, 2017 at 03:11:25PM -0700, Mahesh Jethanandani wrote:
> > On Jun 19, 2017, at 11:57 AM, Jeffrey Haas wrote:
> > Where we run into some issues are the cases highlighted: when the sessions
> > don't share common properties, how should the protocol pick what
14 matches
Mail list logo