From Sandeep.Bishnoi@alcatel-lucent.com Thu Apr 16 14:31:24 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 C86C03A6F74 for ; Thu, 16 Apr 2009 14:31:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.394 X-Spam-Level: X-Spam-Status: No, score=-1.394 tagged_above=-999 required=5 tests=[AWL=1.205, 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 PRfTaknKUrpA for ; Thu, 16 Apr 2009 14:31:24 -0700 (PDT) Received: from audl751.usa.alcatel.com (audl751.usa.alcatel.com [143.209.238.164]) by core3.amsl.com (Postfix) with ESMTP id 0EB673A6DD9 for ; Thu, 16 Apr 2009 14:31:24 -0700 (PDT) Received: from usdalsbhs01.ad3.ad.alcatel.com (usdalsbhs01.usa.alcatel.com [172.22.216.19]) by audl751.usa.alcatel.com (ALCANET) with ESMTP id n3GLWTPk004488 for ; Thu, 16 Apr 2009 16:32:36 -0500 Received: from USDALSMBS01.ad3.ad.alcatel.com ([172.22.216.10]) by usdalsbhs01.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 16 Apr 2009 16:32:35 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: BFD multipoint comments Date: Thu, 16 Apr 2009 16:32:36 -0500 Message-ID: <4E816EC104822245BA3C86149A7158150B1BD5A2@USDALSMBS01.ad3.ad.alcatel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: BFD multipoint comments Thread-Index: Acm5N/c3epzv+PCITY2sxX27P9z9fQDSamnAAJYlI5A= From: "BISHNOI Sandeep" To: X-OriginalArrivalTime: 16 Apr 2009 21:32:35.0973 (UTC) FILETIME=[DBFD5350:01C9BEDA] X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34 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, 16 Apr 2009 21:31:24 -0000 Hi Dave/Dave, WRT section 4.8 - To identify a BFD session on a tail node for a particular multipoint tree, the source address and MyDiscr must be used. IMO - This has a limited application and may need some revamp like the bootstrap mechanism in MPLS LSP BFD (you could piggyback BFD TLV on P2MP OAM). Otherwise an operator would be forced to pick a MyDiscr for each BFD session and multipoint tree combination and configure it on both head and tail node. "4.8. Discriminators and Packet Demultiplexing The use of Discriminators is somewhat different in Multipoint BFD than in Point-to-point BFD. The head sends Multipoint BFD Control packets over the MultipointHead session with My Discr set to a value bound to the multipoint tree, and with Your Discr set to zero. The tails MUST demultiplex these packets based on a combination of the source address and My Discr, which together uniquely identify the head and the multipoint tree." Thanks, Sandeep From Sandeep.Bishnoi@alcatel-lucent.com Wed Apr 22 15:31: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 9C8A33A6B4A for ; Wed, 22 Apr 2009 15:31:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.996 X-Spam-Level: X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[AWL=0.603, 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 XXNbN30hmzTX for ; Wed, 22 Apr 2009 15:31:37 -0700 (PDT) Received: from audl952.usa.alcatel.com (audl952.usa.alcatel.com [143.209.238.159]) by core3.amsl.com (Postfix) with ESMTP id 3C65E3A68BD for ; Wed, 22 Apr 2009 15:30:42 -0700 (PDT) Received: from usdalsbhs02.ad3.ad.alcatel.com (usdalsbhs02.usa.alcatel.com [172.22.216.13]) by audl952.usa.alcatel.com (ALCANET) with ESMTP id n3MMVw5O031606 for ; Wed, 22 Apr 2009 17:31:59 -0500 Received: from USDALSMBS01.ad3.ad.alcatel.com ([172.22.216.10]) by usdalsbhs02.ad3.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 22 Apr 2009 17:31:58 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: BFD multipoint comments Date: Wed, 22 Apr 2009 17:31:58 -0500 Message-ID: <4E816EC104822245BA3C86149A7158150B215630@USDALSMBS01.ad3.ad.alcatel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: BFD multipoint comments Thread-Index: Acm5N/c3epzv+PCITY2sxX27P9z9fQDSamnAAJYlI5ABL/TpgA== From: "BISHNOI Sandeep" To: X-OriginalArrivalTime: 22 Apr 2009 22:31:58.0771 (UTC) FILETIME=[260FA830:01C9C39A] X-Scanned-By: MIMEDefang 2.64 on 143.209.238.34 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, 22 Apr 2009 22:31:38 -0000 Any comments??? Hi Dave/Dave, WRT section 4.8 - To identify a BFD session on a tail node for a particular multipoint tree, the source address and MyDiscr must be used. IMO - This has a limited application and may need some revamp like the bootstrap mechanism in MPLS LSP BFD (you could piggyback BFD TLV on P2MP OAM). Otherwise an operator would be forced to pick a MyDiscr for each BFD session and multipoint tree combination and configure it on both head and tail node. "4.8. Discriminators and Packet Demultiplexing The use of Discriminators is somewhat different in Multipoint BFD than in Point-to-point BFD. The head sends Multipoint BFD Control packets over the MultipointHead session with My Discr set to a value bound to the multipoint tree, and with Your Discr set to zero. The tails MUST demultiplex these packets based on a combination of the source address and My Discr, which together uniquely identify the head and the multipoint tree." Thanks, Sandeep From root@core3.amsl.com Sun Apr 26 19:30:01 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 0) id 619833A69A7; Sun, 26 Apr 2009 19:30:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Subject: I-D Action:draft-ietf-bfd-mib-07.txt Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090427023001.619833A69A7@core3.amsl.com> Date: Sun, 26 Apr 2009 19:30:01 -0700 (PDT) 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: Mon, 27 Apr 2009 02:30:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Bidirectional Forwarding Detection Working Group of the IETF. Title : BFD Management Information Base Author(s) : T. Nadeau, et al. Filename : draft-ietf-bfd-mib-07.txt Pages : 31 Date : 2009-04-26 This draft defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling Bidirectional Forwarding Detection (BFD) protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-bfd-mib-07.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-bfd-mib-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-04-26192603.I-D@ietf.org> --NextPart--