From vishwas.ietf@gmail.com Wed Mar 18 13:09:57 2009 Return-Path: X-Original-To: rtg-bfd@core3.amsl.com Delivered-To: rtg-bfd@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6622228C0F5 for ; Wed, 18 Mar 2009 13:09:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vjyKWxP4QYLt for ; Wed, 18 Mar 2009 13:09:56 -0700 (PDT) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.170]) by core3.amsl.com (Postfix) with ESMTP id CCB893A69B3 for ; Wed, 18 Mar 2009 13:09:56 -0700 (PDT) Received: by wf-out-1314.google.com with SMTP id 24so228322wfg.31 for ; Wed, 18 Mar 2009 13:10:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=t6NP8n9feasP13m9eon3T7bapHsodfsWeLHKA+DjIHI=; b=L5OLoQx4NKGMA9bZKqf+J+L3L0OBp2oX8fqRN1EEMzRBhPSbd+8iUOjWw+1ykItpbX gL825fZKR3mhXGs7VPVFGb62Ke/sScDtT4jfu1TYkRRQ8rzM5L1IBPZUMcyc8ocqXNkC nX+jK9W9lTrx5RRTH3Ue147uutc3NVtw7BllM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=V+/IawRcYgj35Ay/qiQY2BT6QYzF8doTVsD2KLqj4gXnXiX4yve4EWi1hCL/9hUL5o zhghCwEQdxRDBI0bSIBdvhJGdaX4e23qXeXvprFmgPaJbEC5YgjBuCNwQyyMjHTrUDLr Qxa9QsQs/jzxN4wDZ42ifGk25tb6HRVCtd5wc= MIME-Version: 1.0 Received: by 10.142.217.17 with SMTP id p17mr684533wfg.40.1237407041516; Wed, 18 Mar 2009 13:10:41 -0700 (PDT) In-Reply-To: <77ead0ec0903181308g4e7c0eb5g86f140c1e0c7929c@mail.gmail.com> References: <77ead0ec0903181308g4e7c0eb5g86f140c1e0c7929c@mail.gmail.com> Date: Wed, 18 Mar 2009 13:10:41 -0700 Message-ID: <77ead0ec0903181310q11b7d5bcg9a5827721a40986e@mail.gmail.com> Subject: BFD at the IETF From: Vishwas Manral To: rtg-bfd@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: rtg-bfd@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "RTG Area: Bidirectional Forwarding Detection DT" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Mar 2009 20:09:57 -0000 Hi, Do we have a BFD meeting at the upcoming IETF? If not will the chairs be there so that we can discuss some new items of work. Thanks, Vishwas From tnadeau@lucidvision.com Wed Mar 18 13:10:42 2009 Return-Path: X-Original-To: rtg-bfd@core3.amsl.com Delivered-To: rtg-bfd@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B74A28C0F5 for ; Wed, 18 Mar 2009 13:10:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.125 X-Spam-Level: X-Spam-Status: No, score=-2.125 tagged_above=-999 required=5 tests=[AWL=0.474, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z0F67LCrvjU1 for ; Wed, 18 Mar 2009 13:10:41 -0700 (PDT) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by core3.amsl.com (Postfix) with ESMTP id 9961A3A69BB for ; Wed, 18 Mar 2009 13:10:41 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lucidvision.com (Postfix) with ESMTP id 5FBEC3BB7937; Wed, 18 Mar 2009 16:11:26 -0400 (EDT) X-Virus-Scanned: amavisd-new at lucidvision.local Received: from lucidvision.com ([127.0.0.1]) by localhost (static-72-71-250-34.cncdnh.fios.verizon.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FhcEJAgeDCVP; Wed, 18 Mar 2009 16:11:25 -0400 (EDT) Received: from [192.168.1.120] (static-72-71-250-36.cncdnh.fios.myfairpoint.net [72.71.250.36]) by lucidvision.com (Postfix) with ESMTP id 7C3A93BB7928; Wed, 18 Mar 2009 16:11:25 -0400 (EDT) Message-Id: From: Thomas Nadeau To: Vishwas Manral In-Reply-To: <77ead0ec0903181310q11b7d5bcg9a5827721a40986e@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: BFD at the IETF Date: Wed, 18 Mar 2009 16:11:25 -0400 References: <77ead0ec0903181308g4e7c0eb5g86f140c1e0c7929c@mail.gmail.com> <77ead0ec0903181310q11b7d5bcg9a5827721a40986e@mail.gmail.com> X-Mailer: Apple Mail (2.930.3) Cc: rtg-bfd@ietf.org X-BeenThere: rtg-bfd@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "RTG Area: Bidirectional Forwarding Detection DT" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Mar 2009 20:10:42 -0000 Can you specify that the proposed new items are here on the list? --Tom > Hi, > > Do we have a BFD meeting at the upcoming IETF? If not will the chairs > be there so that we can discuss some new items of work. > > Thanks, > Vishwas > From vishwas.ietf@gmail.com Wed Mar 18 13:58:37 2009 Return-Path: X-Original-To: rtg-bfd@core3.amsl.com Delivered-To: rtg-bfd@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA0E93A6956 for ; Wed, 18 Mar 2009 13:58:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.579 X-Spam-Level: ** X-Spam-Status: No, score=2.579 tagged_above=-999 required=5 tests=[AWL=-5.178, BAYES_00=-2.599, FB_NOT_SEXUAL=10.357] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HCenQ4bO24vt for ; Wed, 18 Mar 2009 13:58:37 -0700 (PDT) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240]) by core3.amsl.com (Postfix) with ESMTP id 906AC3A63EB for ; Wed, 18 Mar 2009 13:58:33 -0700 (PDT) Received: by an-out-0708.google.com with SMTP id d11so227483and.4 for ; Wed, 18 Mar 2009 13:59:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=G1nnIxF/WAhhGF3FHd6ZhkPc02H8naZczR52IEHNL30=; b=Jqcs4kHY51k5QAhW3MOCqLnejdMSY8eS/GDgIQvpRS3KVyQQCKtXHW0suLRyLc9Kb0 TH/HQ4QAC21oI6Pvfpy/g3eHmzUS3HfKKaYgrAei1bq0mrVm5PWx3qCJXIl5DIjslatv ARLDZKQ+EendYk5uNg9zZr+0tTAJwzfKNNLXY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Xnj8ojEfny9JRJ03WekdY9YKxzu7nj6NPA3MofzOrCcaA/krZISypfQhgnG8hdUrBB e1eOJGhQLmdYnI4BBtauMS24JBNWxIh+kDz6EpFtyWZvX+PQguX8p+RDkwHB1E/ez7Bi QekhCTin8jhB/UpFXO30EBg1FqiedCO2I7/hU= MIME-Version: 1.0 Received: by 10.142.89.13 with SMTP id m13mr682420wfb.185.1237409957308; Wed, 18 Mar 2009 13:59:17 -0700 (PDT) In-Reply-To: References: <77ead0ec0903181308g4e7c0eb5g86f140c1e0c7929c@mail.gmail.com> <77ead0ec0903181310q11b7d5bcg9a5827721a40986e@mail.gmail.com> Date: Wed, 18 Mar 2009 13:59:17 -0700 Message-ID: <77ead0ec0903181359x68a1c448w4fae2b4441c52901@mail.gmail.com> Subject: Re: BFD at the IETF From: Vishwas Manral To: Thomas Nadeau Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: rtg-bfd@ietf.org X-BeenThere: rtg-bfd@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "RTG Area: Bidirectional Forwarding Detection DT" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Mar 2009 20:58:37 -0000 Hi Tom, It is based on an earlier mail I had sent about a couple of months back - about BFD for some L2 technologies. After I discussed the work we got the Multicast work revived, so we have lesser pieces of the puzzle to solve. We seemed to have got some customers requesting the same from us after we discussed that on the list. Should we discuss the MPLS MIB issues we had talked about earlier this IETF (changing the Texual conventions for the same)? Thanks, Vishwas On Wed, Mar 18, 2009 at 1:11 PM, Thomas Nadeau wr= ote: > > =A0 =A0 =A0 =A0Can you specify that the proposed new items are here on th= e list? > > =A0 =A0 =A0 =A0--Tom > >> Hi, >> >> Do we have a BFD meeting at the upcoming IETF? If not will the chairs >> be there so that we can discuss some new items of work. >> >> Thanks, >> Vishwas >> > > From tnadeau@lucidvision.com Wed Mar 18 15:05:33 2009 Return-Path: X-Original-To: rtg-bfd@core3.amsl.com Delivered-To: rtg-bfd@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 15C5E3A6997 for ; Wed, 18 Mar 2009 15:05:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.986 X-Spam-Level: ** X-Spam-Status: No, score=2.986 tagged_above=-999 required=5 tests=[AWL=-4.772, BAYES_00=-2.599, FB_NOT_SEXUAL=10.357] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HL6WvBqKuob4 for ; Wed, 18 Mar 2009 15:05:32 -0700 (PDT) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by core3.amsl.com (Postfix) with ESMTP id 3D2F13A688D for ; Wed, 18 Mar 2009 15:05:32 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lucidvision.com (Postfix) with ESMTP id 7F0423BB7FDA; Wed, 18 Mar 2009 18:06:17 -0400 (EDT) X-Virus-Scanned: amavisd-new at lucidvision.local Received: from lucidvision.com ([127.0.0.1]) by localhost (static-72-71-250-34.cncdnh.fios.verizon.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c8HWgzZ5Rxee; Wed, 18 Mar 2009 18:06:16 -0400 (EDT) Received: from [192.168.1.120] (static-72-71-250-36.cncdnh.fios.myfairpoint.net [72.71.250.36]) by lucidvision.com (Postfix) with ESMTP id 7918C3BB7FCB; Wed, 18 Mar 2009 18:06:16 -0400 (EDT) Message-Id: <6B03B88E-0510-4C2B-A11B-92B12EF59141@lucidvision.com> From: Thomas Nadeau To: Vishwas Manral In-Reply-To: <77ead0ec0903181359x68a1c448w4fae2b4441c52901@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: BFD at the IETF Date: Wed, 18 Mar 2009 18:06:15 -0400 References: <77ead0ec0903181308g4e7c0eb5g86f140c1e0c7929c@mail.gmail.com> <77ead0ec0903181310q11b7d5bcg9a5827721a40986e@mail.gmail.com> <77ead0ec0903181359x68a1c448w4fae2b4441c52901@mail.gmail.com> X-Mailer: Apple Mail (2.930.3) Cc: rtg-bfd@ietf.org X-BeenThere: rtg-bfd@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "RTG Area: Bidirectional Forwarding Detection DT" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Mar 2009 22:05:33 -0000 On Mar 18, 2009, at 4:59 PM, Vishwas Manral wrote: > Hi Tom, > > It is based on an earlier mail I had sent about a couple of months > back - about BFD for some L2 technologies. After I discussed the work > we got the Multicast work revived, so we have lesser pieces of the > puzzle to solve. We seemed to have got some customers requesting the > same from us after we discussed that on the list. I am not going to speak for the chairs, but I personally don't think we need to hold a WG meeting just for that topic. :P > Should we discuss the MPLS MIB issues we had talked about earlier this > IETF (changing the Texual conventions for the same)? That is probably best on the MPLS WG list if you ask me. --Tom > > Thanks, > Vishwas > > On Wed, Mar 18, 2009 at 1:11 PM, Thomas Nadeau > wrote: >> >> Can you specify that the proposed new items are here on the >> list? >> >> --Tom >> >>> Hi, >>> >>> Do we have a BFD meeting at the upcoming IETF? If not will the >>> chairs >>> be there so that we can discuss some new items of work. >>> >>> Thanks, >>> Vishwas >>> >> >> > From dward@cisco.com Thu Mar 19 09:20:18 2009 Return-Path: X-Original-To: rtg-bfd@core3.amsl.com Delivered-To: rtg-bfd@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 72BF93A68D8 for ; Thu, 19 Mar 2009 09:20:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.255 X-Spam-Level: X-Spam-Status: No, score=-1.255 tagged_above=-999 required=5 tests=[AWL=-5.013, BAYES_00=-2.599, FB_NOT_SEXUAL=10.357, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GT08lecNLeRK for ; Thu, 19 Mar 2009 09:20:13 -0700 (PDT) Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 189113A6B64 for ; Thu, 19 Mar 2009 09:20:13 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.38,389,1233532800"; d="scan'208";a="158338595" Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by sj-iport-1.cisco.com with ESMTP; 19 Mar 2009 16:20:57 +0000 Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n2JGKwl2020830; Thu, 19 Mar 2009 12:20:58 -0400 Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n2JGKw1I024049; Thu, 19 Mar 2009 16:20:58 GMT Received: from xmb-rtp-202.amer.cisco.com ([64.102.31.52]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Mar 2009 12:20:58 -0400 Received: from [127.0.0.1] ([171.68.225.134]) by xmb-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Mar 2009 12:20:57 -0400 Message-Id: From: David Ward To: Vishwas Manral In-Reply-To: <77ead0ec0903181359x68a1c448w4fae2b4441c52901@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: BFD at the IETF Date: Thu, 19 Mar 2009 11:20:56 -0500 References: <77ead0ec0903181308g4e7c0eb5g86f140c1e0c7929c@mail.gmail.com> <77ead0ec0903181310q11b7d5bcg9a5827721a40986e@mail.gmail.com> <77ead0ec0903181359x68a1c448w4fae2b4441c52901@mail.gmail.com> X-Mailer: Apple Mail (2.930.3) X-OriginalArrivalTime: 19 Mar 2009 16:20:57.0846 (UTC) FILETIME=[AF789160:01C9A8AE] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1273; t=1237479658; x=1238343658; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dward@cisco.com; z=From:=20David=20Ward=20 |Subject:=20Re=3A=20BFD=20at=20the=20IETF |Sender:=20 |To:=20Vishwas=20Manral=20; bh=Z09DR/yYvfeLn+Cjj7HgKAKZxNKa2wCxW5gL6YYfE38=; b=kygJ17n2RKqOj2wJe7fLgs8KAaD/BTJUySnw8MKnvKlJMIlnS25UrFQ4hS RXhXBVJ1sQQPphSxGm3TTGAQF4uxfIGrTmkIXLdGOt2UG03zcD4MPYJSUrKC FG4ulDjVis; Authentication-Results: rtp-dkim-2; header.From=dward@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); Cc: rtg-bfd@ietf.org, David Ward X-BeenThere: rtg-bfd@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "RTG Area: Bidirectional Forwarding Detection DT" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Mar 2009 16:20:18 -0000 We aren't having a meeting in San Fran. Note that the p2mp will be revived once we have all the discusses cleared (we are very close). As for BFD over L2, as mentioned we agreed with the IEEE we would not take on that work. The MIB is best discussed on list and with the authors. -DWard On Mar 18, 2009, at 3:59 PM, Vishwas Manral wrote: > Hi Tom, > > It is based on an earlier mail I had sent about a couple of months > back - about BFD for some L2 technologies. After I discussed the work > we got the Multicast work revived, so we have lesser pieces of the > puzzle to solve. We seemed to have got some customers requesting the > same from us after we discussed that on the list. > > Should we discuss the MPLS MIB issues we had talked about earlier this > IETF (changing the Texual conventions for the same)? > > Thanks, > Vishwas > > On Wed, Mar 18, 2009 at 1:11 PM, Thomas Nadeau > wrote: >> >> Can you specify that the proposed new items are here on the >> list? >> >> --Tom >> >>> Hi, >>> >>> Do we have a BFD meeting at the upcoming IETF? If not will the >>> chairs >>> be there so that we can discuss some new items of work. >>> >>> Thanks, >>> Vishwas >>> >> >> From wwwrun@core3.amsl.com Fri Mar 20 09:46:02 2009 Return-Path: X-Original-To: rtg-bfd@ietf.org Delivered-To: rtg-bfd@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id CC24D3A6C62; Fri, 20 Mar 2009 09:46:02 -0700 (PDT) X-idtracker: yes From: The IESG To: IETF-Announce Subject: Protocol Action: 'Generic Application of BFD' to Proposed Standard Message-Id: <20090320164602.CC24D3A6C62@core3.amsl.com> Date: Fri, 20 Mar 2009 09:46:02 -0700 (PDT) Cc: bfd mailing list , Internet Architecture Board , bfd chair , RFC Editor X-BeenThere: rtg-bfd@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "RTG Area: Bidirectional Forwarding Detection DT" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2009 16:46:02 -0000 The IESG has approved the following document: - 'Generic Application of BFD ' as a Proposed Standard This document is the product of the Bidirectional Forwarding Detection Working Group. The IESG contact persons are Ross Callon and David Ward. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-bfd-generic-05.txt Technical Summary As the utility of BFD has become understood, there have been calls to specify BFD interactions with a growing list of network functions. Rather than producing a long series of short documents on the application of BFD, it seemed worthwhile to describe the interactions between BFD and other network functions ("BFD clients") in a broad way. This document describes the generic application of the Bidirectional Forwarding Detection (BFD) protocol. Working Group Summary Working group progress has been reported as quite smooth. Document Quality The protocol is widely implemented and deployed and has become part of default deployments on the internet. The drafts reflect the lessons learned from the deployed and operation. Multiple vendors have implemented and deployed BFD in operational networks. There are a few minor nits to be corrected based on Gen-Art and Last Call comments. The authors would like to correct these along with any IESG comments received. Personnel Dave Ward is the document shepherd. Ross Callon is the responsible Area Director. From wwwrun@core3.amsl.com Fri Mar 20 09:47:17 2009 Return-Path: X-Original-To: rtg-bfd@ietf.org Delivered-To: rtg-bfd@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id AD2CC3A6C7D; Fri, 20 Mar 2009 09:47:17 -0700 (PDT) X-idtracker: yes From: The IESG To: IETF-Announce Subject: Protocol Action: 'BFD for Multihop Paths' to Proposed Standard Message-Id: <20090320164717.AD2CC3A6C7D@core3.amsl.com> Date: Fri, 20 Mar 2009 09:47:17 -0700 (PDT) Cc: bfd mailing list , Internet Architecture Board , bfd chair , RFC Editor X-BeenThere: rtg-bfd@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "RTG Area: Bidirectional Forwarding Detection DT" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2009 16:47:17 -0000 The IESG has approved the following document: - 'BFD for Multihop Paths ' as a Proposed Standard This document is the product of the Bidirectional Forwarding Detection Working Group. The IESG contact persons are Ross Callon and David Ward. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-bfd-multihop-07.txt Technical Summary BFD can be useful on arbitrary paths between systems, which may span multiple network hops and follow unpredictable paths. Furthermore, a pair of systems may have multiple paths between them that may overlap. This document describes the use of the Bidirectional Forwarding Detection protocol (BFD) over multihop paths, including unidirectional links. Working Group Summary Working group progress has been reported as being quite smooth. Document Quality BFD as a whole is widely implemented and deployed and has become part of default deployments on the internet. The drafts reflect the lessons learned from the deployed and operation. Multiple vendors have implemented and deployed BFD in operational networks. However, I am not sure about use of BFD over multihop paths (it makes sense to deploy BFD over single links and MPLS LSPs first). There are a few minor nits to be corrected based on Gen-Art and Last Call comments. The authors would like to correct these along with any IESG comments received. Personnel Dave Ward is the document shepherd. Ross Callon is the responsible Area Director. From vishwas.ietf@gmail.com Fri Mar 27 11:54:38 2009 Return-Path: X-Original-To: rtg-bfd@core3.amsl.com Delivered-To: rtg-bfd@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A084C3A6C6F for ; Fri, 27 Mar 2009 11:54:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.873 X-Spam-Level: X-Spam-Status: No, score=-0.873 tagged_above=-999 required=5 tests=[AWL=1.726, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0dIxGfTM54av for ; Fri, 27 Mar 2009 11:54:37 -0700 (PDT) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174]) by core3.amsl.com (Postfix) with ESMTP id CE3543A6A6E for ; Fri, 27 Mar 2009 11:54:37 -0700 (PDT) Received: by wf-out-1314.google.com with SMTP id 24so1467008wfg.31 for ; Fri, 27 Mar 2009 11:55:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=+ZWn2gmoiXZbNRZq2DssNMD9TJwg2UT3Mz8BjT7fNEA=; b=xccpVqfs/p9hmQMHa/TNWFTkCqxfSbO21+CskGNqegZBjdx8Vrd8ayVkfJ0ByhmlTD a6pN/bZMQaYNmyPr1/j0CVBgG4cmxZFsu37Wn7/lkwydN8Pkyq5n69o88F74xdrD3cgp 5d5Ke8SMD9SNiKf1MpAY9kR0brM1U7fJ7IHH0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=VdnZuMYFgEKBlHxIrT0AZ74Z2nHFYSGWAdJQW2mrKxpbKWHzMX5y4a7grOFV1BICOq Vp1BEL0k1/lQQRUUNHZny8hcnuXlfRg6Lmf0Pe6vj3n54JZK7Sk4n2gCmL5TGMW9GvnG psZUSBmHdq7ghAwH9DoEYOy9aJD20D46p7dhg= MIME-Version: 1.0 Received: by 10.143.167.15 with SMTP id u15mr1013674wfo.147.1238180132666; Fri, 27 Mar 2009 11:55:32 -0700 (PDT) Date: Fri, 27 Mar 2009 11:55:32 -0700 Message-ID: <77ead0ec0903271155n6b253f6uf7700ca7a4a88699@mail.gmail.com> Subject: BFD MIB From: Vishwas Manral To: rtg-bfd@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: rtg-bfd@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "RTG Area: Bidirectional Forwarding Detection DT" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2009 18:54:38 -0000 Hi, Why dont we have a TC for the Detect Multiplier which has a value between 1- 255 instead of Unsigned32. bfdSessDetectMult OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "This object specifies the Detect time multiplier." ::= { bfdSessEntry 25 } Thanks, Vishwas From jhaas@slice.pfrc.org Fri Mar 27 12:20:12 2009 Return-Path: X-Original-To: rtg-bfd@core3.amsl.com Delivered-To: rtg-bfd@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AB773A6C89 for ; Fri, 27 Mar 2009 12:20:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.042 X-Spam-Level: X-Spam-Status: No, score=-2.042 tagged_above=-999 required=5 tests=[AWL=0.223, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iRe3igGl+iwP for ; Fri, 27 Mar 2009 12:20:12 -0700 (PDT) Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by core3.amsl.com (Postfix) with ESMTP id EFB833A6A4D for ; Fri, 27 Mar 2009 12:20:11 -0700 (PDT) Received: by slice.pfrc.org (Postfix, from userid 1001) id 66A97244200; Fri, 27 Mar 2009 19:21:06 +0000 (UTC) Date: Fri, 27 Mar 2009 15:21:06 -0400 From: Jeffrey Haas To: Vishwas Manral Subject: Re: BFD MIB Message-ID: <20090327192105.GA12240@slice> References: <77ead0ec0903271155n6b253f6uf7700ca7a4a88699@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <77ead0ec0903271155n6b253f6uf7700ca7a4a88699@mail.gmail.com> User-Agent: Mutt/1.5.15+20070412 (2007-04-11) Cc: rtg-bfd@ietf.org X-BeenThere: rtg-bfd@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "RTG Area: Bidirectional Forwarding Detection DT" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2009 19:20:12 -0000 Vishwas, On Fri, Mar 27, 2009 at 11:55:32AM -0700, Vishwas Manral wrote: > Why dont we have a TC for the Detect Multiplier which has a value > between 1- 255 instead of Unsigned32. That seems like an excellent idea. It would apply to both bfdSessDetectMult and bfdSessNegotiatedDetectMult. -- Jeff