From bridge-mib-bounces@ietf.org Fri Jul 14 07:13:48 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1LcB-0007qB-Hk; Fri, 14 Jul 2006 07:13:47 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1Lc8-0007q3-O9 for bridge-mib@ietf.org; Fri, 14 Jul 2006 07:13:44 -0400 Received: from co300216-ier2.net.avaya.com ([198.152.13.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G1Lc7-0005o4-Dv for bridge-mib@ietf.org; Fri, 14 Jul 2006 07:13:44 -0400 Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k6EB9ZjQ007560 for ; Fri, 14 Jul 2006 07:09:36 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 14 Jul 2006 14:13:39 +0300 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Returned mail: see transcript for details Thread-Index: AcanNo6l0vgl5pIdQwmoIOUzq9Vj6QAAAAG0 From: "Romascanu, Dan \(Dan\)" To: X-Scanner: InterScan AntiVirus for Sendmail X-Spam-Score: 0.1 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 Subject: [Bridge-mib] Out of Office AutoReply: Returned mail: see transcript for details X-BeenThere: bridge-mib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: bridge-mib.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1976092206==" Errors-To: bridge-mib-bounces@ietf.org This is a multi-part message in MIME format. --===============1976092206== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6A736.8EA9D7D6" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6A736.8EA9D7D6 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable I am out-of-office traveling at the IETF and IEEE meetings and will be = back on July 23, 2006. I may not read and respond all e-mails during = this period. If you need to contact me urgently, please leave a voice = mail message at my office number. Regards, Dan ------_=_NextPart_001_01C6A736.8EA9D7D6 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Out of Office AutoReply: Returned mail: see transcript for = details

I am out-of-office traveling at the IETF and IEEE = meetings and will be back on July 23, 2006.  I may not read and = respond all e-mails during this period.  If you need to contact me = urgently, please leave a voice mail message at my office number.

Regards,

Dan

------_=_NextPart_001_01C6A736.8EA9D7D6-- --===============1976092206== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib --===============1976092206==-- From bridge-mib-bounces@ietf.org Mon Jul 17 08:55:48 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2SdW-00072A-U1; Mon, 17 Jul 2006 08:55:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2SdW-000725-2p for bridge-mib@ietf.org; Mon, 17 Jul 2006 08:55:46 -0400 Received: from kecgate03.infosys.com ([220.227.179.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2SdT-0005fz-8g for bridge-mib@ietf.org; Mon, 17 Jul 2006 08:55:46 -0400 Received: from indhubbhs01.ad.infosys.com ([192.168.200.81]) by Kecgate03.infosys.com with InterScan Messaging Security Suite; Mon, 17 Jul 2006 18:24:52 +0530 Received: from BLRKECMSG04.ad.infosys.com ([172.25.213.134]) by indhubbhs01.ad.infosys.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 17 Jul 2006 18:24:38 +0530 Received: from BLRKECMSG03.ad.infosys.com ([172.25.213.133]) by BLRKECMSG04.ad.infosys.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 17 Jul 2006 18:24:37 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 17 Jul 2006 18:24:37 +0530 Message-ID: <18E7158E26D93D4AA3F8A6D8D0DC6FB30FC4CA@BLRKECMSG03.ad.infosys.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: New trap Thread-Index: AcapoCkO5N4Bkt0lTC+Nmz2NLLg09w== From: "ravikumarb" To: X-OriginalArrivalTime: 17 Jul 2006 12:54:37.0776 (UTC) FILETIME=[2933CD00:01C6A9A0] X-Spam-Score: 0.0 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Cc: kenyon.c.norseth@L-3com.com Subject: [Bridge-mib] New trap X-BeenThere: bridge-mib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: bridge-mib.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: bridge-mib-bounces@ietf.org Hi, We would like to porpose a new trap for bridges so that they can detect= malfunctioning neighbour bridges. Lets call it as "neighbourUnreachable".= This trap will be generated by the bridge if it doesn't receive 5= consecutive Hello BPDUs from a port, which was receiving these messages= earlier. This trap will be useful to detect cases where the bridge and its= ports were functioning properly for some time and suddenly started= malfunctioning due to a hardware glitch or a software bug. Note that link= failure (down) trap won't be raised as the link is UP from the PHY point= of view. This is analogous to Hello messages used by Routing Protocols to= detect routing peers. This trap will be very useful for the NMS to take= appropriate actions. Note that this is very different from= "topologyChange" trap, which just tells that the port has transitioned to= Blocking State from Forwarding State. This trap tells that the bridge is= not functioning properly at all from the port's point of view. It has a= specific meaning and is detected fast. Following would be its structure: neighbourUnreachable NOTIFICATION-TYPE OBJECTS { dot1dBaseBridgeAddress dot1dBasePort dot1dBasePortIfIndex= } STATUS current DESCRIPTION "A neighbourUnreachable trap is sent by a bridge when it doesn't receive 5 consecutive Hello BPDUs. This will allow a bridge to detect malfunctions of the neighbour bridge even when the link state to the neighbour bridge is UP. It is analogous to Hello messages used by Routing Protocols to detect whether the neighbour router is functional." ::=3D { dot1dNotifications 3 } Please let us know your thoughts regarding the proposed trap. Thanks & Regards, Ravi **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended= solely for the use of the addressee(s). If you are not the intended= recipient, please notify the sender by e-mail and delete the original= message. Further, you are not to copy, disclose, or distribute this e-mail= or its contents to any other person and any such actions are unlawful.= This e-mail may contain viruses. Infosys has taken every reasonable= precaution to minimize this risk, but is not liable for any damage you may= sustain as a result of any virus in this e-mail. You should carry out your= own virus checks before opening the e-mail or attachment. Infosys reserves= the right to monitor and review the content of all messages sent to or= from this e-mail address. Messages sent to or from this e-mail address may= be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS*** _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From bridge-mib-bounces@ietf.org Mon Jul 17 10:10:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2Tnu-0006gv-6S; Mon, 17 Jul 2006 10:10:34 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2Tnt-0006gq-2c for bridge-mib@ietf.org; Mon, 17 Jul 2006 10:10:33 -0400 Received: from alnrmhc13.comcast.net ([204.127.225.93] helo=alnrmhc11.comcast.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2Tnr-00013I-OF for bridge-mib@ietf.org; Mon, 17 Jul 2006 10:10:33 -0400 Received: from harrington73653 (c-24-61-137-43.hsd1.nh.comcast.net[24.61.137.43]) by comcast.net (alnrmhc13) with SMTP id <20060717141030b1300fm1tve>; Mon, 17 Jul 2006 14:10:31 +0000 From: "David B Harrington" To: "'ravikumarb'" , Subject: RE: [Bridge-mib] New trap Date: Mon, 17 Jul 2006 10:09:15 -0400 Message-ID: <000801c6a9aa$96a09a80$0400a8c0@china.huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcapoCkO5N4Bkt0lTC+Nmz2NLLg09wACcy4Q In-Reply-To: <18E7158E26D93D4AA3F8A6D8D0DC6FB30FC4CA@BLRKECMSG03.ad.infosys.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87 Cc: kenyon.c.norseth@L-3com.com X-BeenThere: bridge-mib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: bridge-mib.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: bridge-mib-bounces@ietf.org Hi, Maintenance of the Bridge Mib modules has been taken over by the IEEE 802.1 WG. As a result, this proposal is out of scope for the Bridge MIB WG mailing list. The appropriate mailing list for IEEE 802.1 MIB module discussion is STDS-802-1-L@listserv.ieee.org. To subscribe to the STDS-802-1-L list, go to http://www.ieee802.org/1/email-pages/ To see the general information about 802,1, including how they work and how to participate, go to http://www.ieee802.org/1/ To see presentations on the technology, go to http://www.ieee802.org/1/files/public/ and look in the docs2004, docs2005, and docs2006 directories. David Harrington dharrington@huawei.com dbharrington@comcast.net ietfdbh@comcast.net co-chair, Bridge-MIB WG > -----Original Message----- > From: ravikumarb [mailto:ravikumarb@infosys.com] > Sent: Monday, July 17, 2006 8:55 AM > To: bridge-mib@ietf.org > Cc: kenyon.c.norseth@L-3com.com > Subject: [Bridge-mib] New trap > > > Hi, > > We would like to porpose a new trap for bridges so that they > can detect malfunctioning neighbour bridges. Lets call it as > "neighbourUnreachable". This trap will be generated by the > bridge if it doesn't receive 5 consecutive Hello BPDUs from a > port, which was receiving these messages earlier. This trap > will be useful to detect cases where the bridge and its ports > were functioning properly for some time and suddenly started > malfunctioning due to a hardware glitch or a software bug. > Note that link failure (down) trap won't be raised as the > link is UP from the PHY point of view. This is analogous to > Hello messages used by Routing Protocols to detect routing > peers. This trap will be very useful for the NMS to take > appropriate actions. Note that this is very different from > "topologyChange" trap, which just tells that the port has > transitioned to Blocking State from Forwarding State. This > trap tells that the bridge is not functioning properly at all > from the port's point of view. It has a specific meaning and > is detected fast. Following would be its structure: > > neighbourUnreachable NOTIFICATION-TYPE > OBJECTS { dot1dBaseBridgeAddress dot1dBasePort > dot1dBasePortIfIndex } > STATUS current > DESCRIPTION > "A neighbourUnreachable trap is sent by a bridge when it > doesn't receive 5 consecutive Hello BPDUs. This will > allow a bridge to detect malfunctions of the neighbour > bridge even when the link state to the neighbour bridge > is UP. It is analogous to Hello messages used by Routing > Protocols to detect whether the neighbour router is > functional." > ::= { dot1dNotifications 3 } > > Please let us know your thoughts regarding the proposed trap. > > Thanks & Regards, > Ravi > > > > > **************** CAUTION - Disclaimer ***************** > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION > intended solely for the use of the addressee(s). If you are > not the intended recipient, please notify the sender by > e-mail and delete the original message. Further, you are not > to copy, disclose, or distribute this e-mail or its contents > to any other person and any such actions are unlawful. This > e-mail may contain viruses. Infosys has taken every > reasonable precaution to minimize this risk, but is not > liable for any damage you may sustain as a result of any > virus in this e-mail. You should carry out your own virus > checks before opening the e-mail or attachment. Infosys > reserves the right to monitor and review the content of all > messages sent to or from this e-mail address. Messages sent > to or from this e-mail address may be stored on the Infosys > e-mail system. > ***INFOSYS******** End of Disclaimer ********INFOSYS*** > > _______________________________________________ > Bridge-mib mailing list > Bridge-mib@ietf.org > https://www1.ietf.org/mailman/listinfo/bridge-mib > _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib