Re: [internet-drafts@ietf.org: I-D Action: draft-haas-bfd-large-packets-00.txt]
PFFC JHAAS <jhaas@pfrc.org> Tue, 20 March 2018 11:30 UTC
Return-Path: <jhaas@pfrc.org>
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 70E5412D86D for <rtg-bfd@ietfa.amsl.com>; Tue, 20 Mar 2018 04:30:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 R7jvdZhA3eKI for <rtg-bfd@ietfa.amsl.com>; Tue, 20 Mar 2018 04:30:23 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 404F112D872 for <rtg-bfd@ietf.org>; Tue, 20 Mar 2018 04:30:23 -0700 (PDT)
Received: from [31.133.156.196] (dhcp-9cc4.meeting.ietf.org [31.133.156.196]) by slice.pfrc.org (Postfix) with ESMTPSA id 358FC1E3F9; Tue, 20 Mar 2018 07:30:31 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-8AC82B8F-1A03-42C2-9B0A-615024387237"
Mime-Version: 1.0 (1.0)
Subject: Re: [internet-drafts@ietf.org: I-D Action: draft-haas-bfd-large-packets-00.txt]
From: PFFC JHAAS <jhaas@pfrc.org>
X-Mailer: iPhone Mail (15D100)
In-Reply-To: <CA+RyBmXU_in--u+JAmm47PUBxZvRJjjLAg3gevVfMUz6vqKmhA@mail.gmail.com>
Date: Tue, 20 Mar 2018 11:30:20 +0000
Cc: rtg-bfd@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <59DF10ED-13C4-4D8A-AB35-29C43C72369C@pfrc.org>
References: <20180319161948.GA11643@pfrc.org> <CA+RyBmXU_in--u+JAmm47PUBxZvRJjjLAg3gevVfMUz6vqKmhA@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/1S9qoAP_7mNT40QtGtf38rH1OKQ>
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: Tue, 20 Mar 2018 11:30:25 -0000
Thanks for your comments, Greg. Non tcp applications like financial stuff are an excellent example. Jeff > On Mar 20, 2018, at 10:40, Greg Mirsky <gregimirsky@gmail.com> wrote: > > Hi Jeff, > thank you for bringing up for discussion this interesting proposal. A question and a comment ahead of the meeting to save us time: > which applications will benefit from monitoring path MTU (PMTU) rather from using PMTU discovery and updating the value; > note that "The Don't Fragment bit (Section 2.3 of [RFC0791]) of the IP payload, when using IP encapsulations, MUST be set." is only applicable to IPv4 environment as IPv6 does not allow IP fragmentation. > Regards, > Greg > >> On Mon, Mar 19, 2018 at 4:19 PM, Jeffrey Haas <jhaas@pfrc.org> wrote: >> Working Group, >> >> A trivial draft I'm hoping to present in the upcoming BFD session if there's >> time. >> >> >> ----- Forwarded message from internet-drafts@ietf.org ----- >> >> A New Internet-Draft is available from the on-line Internet-Drafts directories. >> >> >> Title : BFD Encapsulated in Large Packets >> Authors : Jeffrey Haas >> Albert Fu >> Filename : draft-haas-bfd-large-packets-00.txt >> Pages : 5 >> Date : 2018-03-19 >> >> Abstract: >> The Bidirectional Forwarding Detection (BFD) protocol is commonly >> used to verify connectivity between two systems. BFD packets are >> typically very small. It is desirable in some circumstances to know >> that not only is the path between two systems reachable, but also >> that it is capable of carrying a payload of a particular size. This >> document discusses thoughts on how to implement such a mechanism >> using BFD in Asynchronous mode. >> >> >> >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-haas-bfd-large-packets/ >> >> There are also htmlized versions available at: >> https://tools.ietf.org/html/draft-haas-bfd-large-packets-00 >> https://datatracker.ietf.org/doc/html/draft-haas-bfd-large-packets-00 >> >> >> Please note that it may take a couple of minutes from the time of submission >> until the htmlized version and diff are available at tools.ietf.org. >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> ----- End forwarded message ----- >> >
- [internet-drafts@ietf.org: I-D Action: draft-haas… Jeffrey Haas
- Re: [internet-drafts@ietf.org: I-D Action: draft-… Greg Mirsky
- Re: [internet-drafts@ietf.org: I-D Action: draft-… PFFC JHAAS
- Re: [internet-drafts@ietf.org: I-D Action: draft-… Jeffrey Haas