IETF Logo Mail Archive

RE: BFD WG adoption for draft-haas-bfd-large-packets

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Sun, 21 October 2018 00:14 UTC

Return-Path: <ginsberg@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 28FDB130E1B for <rtg-bfd@ietfa.amsl.com>; Sat, 20 Oct 2018 17:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.563
X-Spam-Level:
X-Spam-Status: No, score=-14.563 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.064, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 CyYfAl9moKN0 for <rtg-bfd@ietfa.amsl.com>; Sat, 20 Oct 2018 17:14:02 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 650F0130DFF for <rtg-bfd@ietf.org>; Sat, 20 Oct 2018 17:14:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12360; q=dns/txt; s=iport; t=1540080842; x=1541290442; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=aApXPnK3bF0qiVvu3J7HljA8Qx6f/wIScEuxAfa2RX4=; b=EqFIkTiklVYSxmqgdrEMpndnqWdhvHEsrFb18dyC7mVzS5i2UbF89DcL cZD3YjK0DL0V0pLqzi4ibxITHFaIdaqqVvfEnauTRIiUSJ6E2dytseSVP zR+T0AcLkCiuzbDM+fjRO+lzkRUhbUAYeDxt35lLPSBgxbtbutTMBCyYI Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AEAABDxMtb/5hdJa1jGgEBAQEBAgEBAQEHAgEBAQGBUQUBAQEBCwGBDXdmfygKg2uIGIwagg2RTYVIFIFmCwEBI4RJAheEcSE0DQ0BAwEBAgEBAm0cDIU6AQEBBCMKXAIBCBEEAQErAgICMB0IAgQBEgiDGoEdZA+lHoEuhD5AhRMFi1IXgUE/gRCBfoEVgxsCAwGBKgESAUWCXYJXAo41hhKKAQkChmCKCB+BUoRziWmMWIleAhEUgSYdOGRxcBU7gmyLGYU+b4kagR+BHwEB
X-IronPort-AV: E=Sophos;i="5.54,406,1534809600"; d="scan'208,217";a="188487831"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Oct 2018 00:14:01 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id w9L0E1jH016010 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <rtg-bfd@ietf.org>; Sun, 21 Oct 2018 00:14:01 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sat, 20 Oct 2018 19:14:00 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1395.000; Sat, 20 Oct 2018 19:14:00 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: RE: BFD WG adoption for draft-haas-bfd-large-packets
Thread-Topic: BFD WG adoption for draft-haas-bfd-large-packets
Thread-Index: AQHUZn7F2obCS5tWFUCJRL2ls+mZdKUo1C+g
Date: Sun, 21 Oct 2018 00:14:00 +0000
Message-ID: <7332e35048d34d44a65ea70df409699c@XCH-ALN-001.cisco.com>
References: <E052CA19-228D-4271-BF9E-7499255E7C53@cisco.com>
In-Reply-To: <E052CA19-228D-4271-BF9E-7499255E7C53@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.113.215]
Content-Type: multipart/alternative; boundary="_000_7332e35048d34d44a65ea70df409699cXCHALN001ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/14v_UGtto_Y3pNpt9eQeVxEjHSk>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 21 Oct 2018 00:14:04 -0000

I have some concerns.

It has been stated that there is a need for sub-second detection of this condition – but I really question that requirement.
What I would expect is that MTU changes only occur as a result of some maintenance operation (configuration change, link addition/bringup, insertion of a new box in the physical path etc.). The idea of using a mechanism which is specifically tailored for sub-second detection to monitor something that is only going to change occasionally seems inappropriate. It makes me think that other mechanisms (some form of OAM, enhancements to routing protocols to do what IS-IS already does ☺) could be more appropriate and would still meet the operational requirements.

I have listened to the Montreal recording – and I know there was discussion related to these issues (not sending padded packets all the time, use of BFD echo, etc.) – but I would be interested in more discussion of the need for sub-second detection.

Also, given that a path might be used with a variety of encapsulations, how do you see such a mechanism being used when multiple BFD clients share the same BFD session and their MTU constraints are different?

Thanx.

   Les


From: Rtg-bfd <rtg-bfd-bounces@ietf.org> On Behalf Of Reshad Rahman (rrahman)
Sent: Wednesday, October 17, 2018 6:06 PM
To: rtg-bfd@ietf.org
Subject: BFD WG adoption for draft-haas-bfd-large-packets

Hello BFD WG,

We have received an adoption request for “BFD encapsulated in large packets”.

https://datatracker.ietf.org/doc/draft-haas-bfd-large-packets/

The adoption call will end on Friday Nov 9th.

Please send email to the list indicating “yes/support”  or “no/do not support”. If you do not support adoption, please state your reasons.

Regards,
Reshad & Jeff.

v2.28.0 | Report a Bug | By Email | System Status