From mailman-bounces@ietf.org Fri Oct 1 07:43:12 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20375 for ; Fri, 1 Oct 2004 07:43:12 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDLx8-00057u-OG for rtg-bfd-archive@ietf.org; Fri, 01 Oct 2004 07:51:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDJrR-0002Yn-PJ for rtg-bfd-archive@ietf.org; Fri, 01 Oct 2004 05:37:57 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: rtg-bfd-archive@ietf.org X-No-Archive: yes Message-ID: Date: Fri, 01 Oct 2004 05:16:00 -0400 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list X-List-Administrivia: yes Sender: mailman-bounces@ietf.org Errors-To: mailman-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: 7bit This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. ********************************************************************** NOTE WELL: Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: o the IETF plenary session, o any IETF working group or portion thereof, o the IESG, or any member thereof on behalf of the IESG, o the IAB or any member thereof on behalf of the IAB, o any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, o the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3667 and RFC 3668. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3667 for details. ******************************************************************************* If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! Passwords for rtg-bfd-archive@ietf.org: List Password // URL ---- -------- rtg-bfd@ietf.org maicos https://www1.ietf.org/mailman/options/rtg-bfd/rtg-bfd-archive%40ietf.org From mailman-bounces@ietf.org Fri Oct 1 10:36:50 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05530 for ; Fri, 1 Oct 2004 10:36:50 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDOfB-00006b-J2 for rtg-bfd-web-archive@ietf.org; Fri, 01 Oct 2004 10:45:37 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDKGj-0001k5-3w for rtg-bfd-web-archive@ietf.org; Fri, 01 Oct 2004 06:04:05 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: rtg-bfd-web-archive@ietf.org X-No-Archive: yes Message-ID: Date: Fri, 01 Oct 2004 05:24:36 -0400 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list X-List-Administrivia: yes Sender: mailman-bounces@ietf.org Errors-To: mailman-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: 7bit This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. ********************************************************************** NOTE WELL: Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: o the IETF plenary session, o any IETF working group or portion thereof, o the IESG, or any member thereof on behalf of the IESG, o the IAB or any member thereof on behalf of the IAB, o any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, o the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3667 and RFC 3668. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3667 for details. ******************************************************************************* If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! Passwords for rtg-bfd-web-archive@ietf.org: List Password // URL ---- -------- rtg-bfd@ietf.org poxauc https://www1.ietf.org/mailman/options/rtg-bfd/rtg-bfd-web-archive%40ietf.org From rtg-bfd-bounces@ietf.org Mon Oct 18 18:40:54 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01734; Mon, 18 Oct 2004 18:40:53 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJgNW-0003Ux-In; Mon, 18 Oct 2004 18:53:25 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJflw-000475-N8; Mon, 18 Oct 2004 18:14:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJfRG-0003Yx-20 for rtg-bfd@megatron.ietf.org; Mon, 18 Oct 2004 17:53:10 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27443 for ; Mon, 18 Oct 2004 17:53:02 -0400 (EDT) Received: from dns.nexthop.com ([65.247.36.216] helo=aa-mx1.nexthop.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJfdE-0002YW-94 for rtg-bfd@ietf.org; Mon, 18 Oct 2004 18:05:34 -0400 Received: from localhost (localhost [127.0.0.1]) by aa-mx1.nexthop.com (Postfix) with ESMTP id 2094B2D49ED; Mon, 18 Oct 2004 17:52:30 -0400 (EDT) Received: from aa-mx1.nexthop.com ([127.0.0.1]) by localhost (aa-mx1.nexthop.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20205-01-95; Mon, 18 Oct 2004 17:52:26 -0400 (EDT) Received: from jhaas.nexthop.com (jhaas.nexthop.com [65.247.36.31]) by aa-mx1.nexthop.com (Postfix) with ESMTP id 1CC052D4A10; Mon, 18 Oct 2004 17:47:04 -0400 (EDT) Received: (from jhaas@localhost) by jhaas.nexthop.com (8.11.6/8.11.6) id i9ILl3Z07560; Mon, 18 Oct 2004 17:47:03 -0400 (EDT) Date: Mon, 18 Oct 2004 17:47:03 -0400 From: Jeffrey Haas To: rtg-bfd@ietf.org, David Ward Message-ID: <20041018214703.GR26825@nexthop.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new at nexthop.com X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Cc: Alex Zinin Subject: IETF 61; BFD current status X-BeenThere: rtg-bfd@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "RTG Area: Bidirectional Forwarding Detection DT" List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rtg-bfd-bounces@ietf.org Errors-To: rtg-bfd-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Working Group, We are currently not planning on meeting at the upcoming IETF 61. If anyone believes we have reason to meet, please let us know but at this point we believe the current working group items are stalled. o The BFD base specification authors are waiting on input from the IESG and the security folks on the BFD security issues. This item currently blocks all further progress on the work items. o The WG drafts will need to be updated to current IETF boiler plate. Authors, please do have this part done so that once we unblock we can get things moving quickly. :-) o The MIB is waiting on the security issues to become unblocked. o Mutual review on BFD for MPLS needs to be accomplished with the MPLS WG. This draft requires the allocation of a TLV for MPLS Ping. o IPR disclosures are still pending, presumably on the authors' respective legal departments. These MUST be dealt with before the documents are allowed to progress. Group review of the existing drafts for any issues, particular with the proposed MIB objects, is highly encouraged. Tell your friends. -- Jeff Haas NextHop Technologies From rtg-bfd-bounces@ietf.org Wed Oct 27 02:54:47 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10310; Wed, 27 Oct 2004 02:54:47 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMhvd-0006n4-76; Wed, 27 Oct 2004 03:09:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMhfq-00076B-Nb; Wed, 27 Oct 2004 02:52:46 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMhf0-0006pw-Na for rtg-bfd@megatron.ietf.org; Wed, 27 Oct 2004 02:51:54 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10179 for ; Wed, 27 Oct 2004 02:51:49 -0400 (EDT) Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMhsl-0006kA-Vl for rtg-bfd@ietf.org; Wed, 27 Oct 2004 03:06:08 -0400 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-2.cisco.com with ESMTP; 27 Oct 2004 00:00:21 -0700 Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9R6onYJ002443; Tue, 26 Oct 2004 23:50:49 -0700 (PDT) Received: from ginsberg-w2k.cisco.com (sjc-vpn5-416.cisco.com [10.21.89.160]) by mira-sjc5-a.cisco.com (MOS 3.4.5-GR) with ESMTP id AVC75826; Tue, 26 Oct 2004 23:48:09 -0700 (PDT) Message-Id: <4.3.2.7.2.20041026234233.01e24308@mira-sjc5-3.cisco.com> X-Sender: ginsberg@mira-sjc5-3.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 26 Oct 2004 23:51:16 -0700 To: David Ward , Dave Katz From: Les Ginsberg Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Cc: rtg-bfd@ietf.org Subject: Graceful Restart and BFD X-BeenThere: rtg-bfd@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "RTG Area: Bidirectional Forwarding Detection DT" List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: rtg-bfd-bounces@ietf.org Errors-To: rtg-bfd-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Dave(s) - Section 7.4 of draft-ietf-bfd-v4v6-1hop-00.txt discusses "Interactions with OSPF and IS-IS with Graceful Restart". The last paragraph of this section says: "If BFD shares its fate with the control plane on either system (either the local system shares fate with the control plane, or the remote system is transmitting BFD packets with the C bit set to zero), it is not useful during graceful restart, as the BFD session is likely to fail regardless of the state of the forwarding plane. In this situation, if a BFD session fails while graceful restart is taking place (or if the BFD session failure triggers a graceful restart event), the graceful restart SHOULD be allowed to complete and the topology change should not be made visible to the network as outlined in section 7.3." This text recommends a behavior which is unsupportable in many cases. In order for this recommendation to be supported, the router which is about to restart MUST provide an indication to its neighbors that a planned graceful restart(GR) is about to happen ("I'll be back"). As "I'll be back" is NOT part of the IS-IS GR extensions, this CANNOT be supported by IS-IS. In addition, it cannot be supported by either protocol in cases of unplanned restart. There are strategies an implementation could employ to deal with the control plane dependency issue, none of which conform to your recommendation ("if a BFD session fails while graceful restart is taking place..."). For example: 1)BFD could be administratively disabled prior to the start of GR.This works only for planned restarts, not unplanned restarts. 2)BFD failures could be ignored at all times when the remote end indicates control plane dependency ( C bit = 0). This effectively disables BFD in that direction. Exactly what you want to say about this is up to you - but the current text should definitely be revised. Les