IETF Logo Mail Archive

Re: WGLC for BFD Multipoint documents (last round)

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Thu, 08 February 2018 03:21 UTC

Return-Path: <rrahman@cisco.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 492C312D811 for <rtg-bfd@ietfa.amsl.com>; Wed, 7 Feb 2018 19:21:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.529
X-Spam-Level:
X-Spam-Status: No, score=-14.529 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 kHvf6mxKc6DB for <rtg-bfd@ietfa.amsl.com>; Wed, 7 Feb 2018 19:21:31 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C15E12D7F6 for <rtg-bfd@ietf.org>; Wed, 7 Feb 2018 19:21:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=33608; q=dns/txt; s=iport; t=1518060091; x=1519269691; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=DogzgCsVqfepvWRxpNRQG0Lz9+cQ8Q2zn/FjT6XVIx4=; b=XNK6DkoBNxDHGF/Ymn1E/R1tdG1UEJb0lmmo/lvT1UZKf1TCDdLpto19 msV8FcPdwOd4+/etlSnVTrKX+YRzEZ1E2eBUwZMGuwPTieyU6Cpbi59Q6 TmNjbLh0EVMOkAnX9U2Ud3Vj22c3x304KUE3RO+/PTrc07x4sN/czARug 0=;
X-Files: image001.gif, image002.gif : 6017, 2066
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CjAACdwXta/4QNJK1UCRkBAQEBAQEBAQEBAQEHAQEBAQGCWXhmcCgKg1uKJI4mgR1liRaOPYIYBwECG4UgAhqCT1QYAQIBAQEBAQECayiFIwEBAQQFHgIIARsbBwcHEAIBBgIRAwECBgEBAR8DAgICBRAGBAUMFAkIAgQBDQQBDooPAxWTAZ10gieFAII6DYExggoBAQEBAQEBAQEBAQEBAQEBAQEBAQEOD4R1ghWBV4FoKQyCeYJrRASBRUoWCIJZMYIUIAWLcocxhwGFdwGCaHA1CQKHFgGJW4UHlD6OQokbAhEZAYE7AR85gVBwFWcBghsJgkwcggZ4jG+BFwEBAQ
X-IronPort-AV: E=Sophos;i="5.46,476,1511827200"; d="gif'147?scan'147,208,217,147";a="68001910"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Feb 2018 03:21:30 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id w183LU2A001898 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 8 Feb 2018 03:21:30 GMT
Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 7 Feb 2018 21:21:29 -0600
Received: from xch-rcd-005.cisco.com ([173.37.102.15]) by XCH-RCD-005.cisco.com ([173.37.102.15]) with mapi id 15.00.1320.000; Wed, 7 Feb 2018 21:21:29 -0600
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: "gregory.mirsky@ztetx.com" <gregory.mirsky@ztetx.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: Re: WGLC for BFD Multipoint documents (last round)
Thread-Topic: WGLC for BFD Multipoint documents (last round)
Thread-Index: AQHTnh8nQKkp4UZhy0e3Kn8Lrj3T1qOZ7FUA
Date: Thu, 08 Feb 2018 03:21:29 +0000
Message-ID: <B37EE335-5635-405B-9780-E5B5A4926122@cisco.com>
References: <201802050917570242948@zte.com.cn>
In-Reply-To: <201802050917570242948@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.9.0.180116
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.241.63]
Content-Type: multipart/related; boundary="_005_B37EE3355635405B9780E5B5A4926122ciscocom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/up8ZQL8iOzFOmuAMnrM61Ej8JMA>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Feb 2018 03:21:33 -0000

Hi Greg,

Regarding changing bfd.SilentTail on the fly, I think we should consider adding some text “… SHOULD not be modified after the MultipointTail session has been created.“. This is to prevent false failure detections as you mentioned.

Regards,
Reshad.

From: "gregory.mirsky@ztetx.com" <gregory.mirsky@ztetx.com>
Date: Sunday, February 4, 2018 at 8:18 PM
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Cc: "gregimirsky@gmail.com" <gregimirsky@gmail.com>
Subject: Re: WGLC for BFD Multipoint documents (last round)


Hi Reshad,

<have to switch my contact for a week>

You've said:

Hi Greg,



The question about whether we need a new variable wasn’t referring to MultipointClient state (I agree this is well explained). Since I mentioned “state variable” I realize the confusion…



The question was whether we need a new state variable (not for the MultipointClient state) to control the behavior explained in this paragraph, e.g the new state variable could be called bfd.TrackTails.



   If the head wishes to know the identity of the tails, it sends

   multipoint Polls as needed.  Previously known tails that don't

   respond to the Polls will be detected.



Regards,

Reshad.

I agree that an operator should have control over whether the head does tail discovery, tail monitoring. But I think that that may require whole suite of parameters and some might need coordidation for the MultipointHead with MultipointTail, e.g. when the given MultipointTail has bfd.SilentTail changed from 0 to 1 or vice versa. Would that trigger false negative on the head? I think that there's lots of open space ofr the innovation in the area of monitoring p2mp tails. I hope that someone will be interested to continue and produce more detailed specification than draft-ietf-bfd-multipoint-active-tail. For example, time interval between multicast Poll and relationship to unicast BFD control packets to tail(s).



Best regards,

Greg Mirsky



Sr. Standardization Expert
预研标准部/有线研究院/有线产品经营部 Standard Preresearch Dept./Wireline Product R&D Institute/Wireline Product Operation Division


[cid:9ae3e214c17d49ed935d87c674ba3ee2]

[cid:24242e5637af428891c4db731e7765ad]
E: gregory.mirsky@ztetx.com<mailto:gregory.mirsky@ztetx.com>
www.zte.com.cn<http://www.zte.com.cn/>

v2.23.0 | Report a Bug | By Email