Re: WGLC for BFD Multipoint documents (last round)

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Fri, 09 February 2018 03:49 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 4DB2C127137 for <rtg-bfd@ietfa.amsl.com>; Thu, 8 Feb 2018 19:49:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level:
X-Spam-Status: No, score=-14.53 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, 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 U3bI-p3JaAiz for <rtg-bfd@ietfa.amsl.com>; Thu, 8 Feb 2018 19:49:14 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 398B11242EA for <rtg-bfd@ietf.org>; Thu, 8 Feb 2018 19:49:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=55160; q=dns/txt; s=iport; t=1518148154; x=1519357754; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=EKsVmUTLxM4mc1mEorUM1OwrrUJs5X39m1eM7UPOobc=; b=WLoeJodcSNl3hz01UJUjakr27+zwIIRpQxf6AG6ijOAxGbzO44BkxARs sK2+Im+TAPDgzhSDLdXdie8k92+LCRaDwu93pBWBmhj4o3qqRoiCFueIv vFsbXfKc+RzhJokrevV1NOeRuFWZsPGSFRNxkxR2HFqt9fycSE+WtNYJR w=;
X-Files: image001.gif, image002.gif, image003.gif, image004.gif : 6016, 2065, 6018, 2067
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ARAQCbGH1a/4MNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJZeGZwKAqDW4okjiWBHT4nl1WCGAcBAhuFIAIaghVUGAECAQE?= =?us-ascii?q?BAQEBAmsdC4UjAQEBBAUeAggBGxsHDhACAQYCEQMBAgYBAQEYBwMCAgIFEAYJD?= =?us-ascii?q?BQJCAIEDgQBDoonkWGddIInhQGDe4IKAQEBAQEBAQEBAQEBAQEBAQEBAQEBDg+?= =?us-ascii?q?EfIIVgVeBaCkMgnmDLwSBTwEBLAkJFgiCWTGCFCAFi3KHMYcBhXkBgmiBJQkCh?= =?us-ascii?q?xYBjmMOghCKQIdgl18CERkBgTsBHzmBUHAVZwGCGwmCTByCBQF4ijKBJYEXAQE?= =?us-ascii?q?B?=
X-IronPort-AV: E=Sophos;i="5.46,481,1511827200"; d="gif'147?scan'147,208,217,147";a="353680021"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Feb 2018 03:49:12 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id w193nC3t006565 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 9 Feb 2018 03:49:12 GMT
Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 8 Feb 2018 21:49:11 -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; Thu, 8 Feb 2018 21:49:12 -0600
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: "gregory.mirsky@ztetx.com" <gregory.mirsky@ztetx.com>
CC: "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: AQHTniFJQKkp4UZhy0e3Kn8Lrj3T1qOZ5zYAgAB4eACAASa2gA==
Date: Fri, 9 Feb 2018 03:49:12 +0000
Message-ID: <E246D09F-1600-49CF-A53D-88E5CECD5B1A@cisco.com>
References: <201802081314229933172@zte.com.cn>
In-Reply-To: <201802081314229933172@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.245.111]
Content-Type: multipart/related; boundary="_007_E246D09F160049CFA53D88E5CECD5B1Aciscocom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/HrOx7lfn0N6PJ13b_aEW2mWHd6E>
X-Mailman-Approved-At: Thu, 08 Feb 2018 19:49:46 -0800
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: Fri, 09 Feb 2018 03:49:17 -0000

Greg, I agree “MUST use” doesn’t read well. s/use/expect/ is good with me.

Regards,
Reshad.

From: "gregory.mirsky@ztetx.com"; <gregory.mirsky@ztetx.com>;
Date: Thursday, February 8, 2018 at 12:14 AM
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com>;
Cc: "rtg-bfd@ietf.org"; <rtg-bfd@ietf.org>;
Subject: Re: WGLC for BFD Multipoint documents (last round)


Hi Reshad,

thank you for your consideration. I've came across what looks as simple editorial change. Appreciate your comment.

In the second paragraph of section 4.8 Packet consumption on tails the following

  For multipoint LSPs, when IP/UDP encapsulation of BFD control packets

  is used, MultipointTail MUST use destination UDP port "3784" ...

reads akwardly because, I think, of 'MUST use'. I propose simple s/use/look for/ or s/use/expect/. What do you think? Is the text god as-is or minor editing may help?



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/>

Original Mail
Sender: ReshadRahman(rrahman) <rrahman@cisco.com>;
To: gregory mirsky10211915;rtg-bfd@ietf.org <rtg-bfd@ietf.org>;
Date: 2018/02/08 11:03
Subject: Re: WGLC for BFD Multipoint documents (last round)
<Sorry for the delay>
Hi Greg,

I would go with normative SHOULD. What you proposed below is fine.

Regards,
Reshad.


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


Hi Reshad,

you've said:

Hi Greg,



While OOB mechanism would improve security, my personal opinion is that we should try to improve security without requiring an OOB mechanism. I think we can add text to the security considerations to address the concerns below, e.g. A tail SHOULD prevent the number of MultipointTail sessions from exceeding the number of expected streams.  The concern expressed in b) cannot be fixed by what I proposed because of multiple streams.  So just preventing the number of MultipointTail sessions from exceeding the number of expected streams should be good enough.



Regards,

Reshad.



If we make it normative SHOULD, i.e. s/should/SHOULD/ in the third recommendation to the implementers:

     The implementation SHOULD have a reasonable upper bound on the

      number of MultipointTail sessions that can be created, with the

      upper bound potentially being computed based on the number of

      multicast streams that the system is expecting.



Or keep the lower case as it is consistent with the rest of the section, e.g. 'a MultipointTail session should not be created'?



Kind 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/>