[178236] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Interesting BFD discussion on reddit

daemon@ATHENA.MIT.EDU (Sudeep Khuraijam)
Fri Feb 20 17:17:38 2015

X-Original-To: nanog@nanog.org
From: Sudeep Khuraijam <skhuraijam@liveops.com>
To: "nanog@nanog.org" <nanog@nanog.org>
Date: Fri, 20 Feb 2015 14:17:25 -0800
In-Reply-To: <20150217074324.GB7567@pob.ytti.fi>

 DIR:OUT; SFP:1101; SCL:1; SRVR:BL2PR01MB420; H:webmail.liveops.com; FPR:;
 SPF:SoftFail; PTR:webmail.liveops.com; A:1; MX:1; LANG:en; 
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BL2PR01MB420;
X-Exchange-Antispam-Report-CFA: BCL:0;PCL:0;RULEID:;SRVR:BL2PR01MB420;
X-Forefront-PRVS: 0493852DA9
X-Exchange-Antispam-Report-CFA: BCL:0;PCL:0;RULEID:;SRVR:BL2PR01MB420;
X-OriginatorOrg: liveops.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 20 Feb 2015 22:17:27.4390 (UTC)
X-MS-Exchange-CrossTenant-Id: 66146db4-8cd6-4ad8-b4f9-ad07d42f53bf
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=66146db4-8cd6-4ad8-b4f9-ad07d42f53bf; Ip=[209.119.28.20]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL2PR01MB420
X-BeenThere: nanog@nanog.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: North American Network Operators Group <nanog.nanog.org>
List-Unsubscribe: <http://mailman.nanog.org/mailman/options/nanog>,
 <mailto:nanog-request@nanog.org?subject=unsubscribe>
List-Archive: <http://mailman.nanog.org/pipermail/nanog/>
List-Post: <mailto:nanog@nanog.org>
List-Help: <mailto:nanog-request@nanog.org?subject=help>
List-Subscribe: <http://mailman.nanog.org/mailman/listinfo/nanog>,
 <mailto:nanog-request@nanog.org?subject=subscribe>
Errors-To: nanog-bounces@nanog.org
Sender: "NANOG" <nanog-bounces@nanog.org>




>On (2015-02-17 06:11 +0530), Glen Kent wrote:
>
>> I think the hardware used was Broadcom. They have a few chipsets which
>>do
>> MD5 and (possibly) SHA in hardware for BFD -- which i have been told is
>> pretty much useless when you start scaling.

While I don=B9t fully understand the context of this particular test and th=
e
scaling limitation, there are merchant silicon, NPUs and even CPUs that do
support MD5 and SHA
at transport line rate requirements.  BFD requirements are just a fraction
of these capabilities.

The option to negotiate capabilities should be available independent of
scaling/cost/inefficiencies at present time.  It is a matter of
implementation/product design choice.

Sudeep Khuraijam


home help back first fref pref prev next nref lref last post