From mailman-bounces@ietf.org Mon Nov 1 06:44:13 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 GAA19928 for ; Mon, 1 Nov 2004 06:44:13 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COaqZ-00052g-2b for rtg-bfd-archive@ietf.org; Mon, 01 Nov 2004 06:59:39 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COZRO-0001cA-8w for rtg-bfd-archive@ietf.org; Mon, 01 Nov 2004 05:29:34 -0500 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: Mon, 01 Nov 2004 05:10:59 -0500 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 Mon Nov 1 09:14:18 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 JAA05489 for ; Mon, 1 Nov 2004 09:14:18 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COdBp-0007yC-Vk for rtg-bfd-web-archive@ietf.org; Mon, 01 Nov 2004 09:29:46 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COZmd-0003GQ-Mx for rtg-bfd-web-archive@ietf.org; Mon, 01 Nov 2004 05:51:31 -0500 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: Mon, 01 Nov 2004 05:19:56 -0500 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 Tue Nov 9 17:34:02 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 RAA22156; Tue, 9 Nov 2004 17:34:02 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CReZk-0000QH-W4; Tue, 09 Nov 2004 17:34:57 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CReHc-0007Pu-Ig; Tue, 09 Nov 2004 17:16:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CReC0-0006Bu-Mc; Tue, 09 Nov 2004 17:10:24 -0500 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 RAA19663; Tue, 9 Nov 2004 17:10:22 -0500 (EST) Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CReCo-0008Ew-An; Tue, 09 Nov 2004 17:11:16 -0500 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-2.cisco.com with ESMTP; 09 Nov 2004 17:09:52 -0500 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iA9M9nR5004780; Tue, 9 Nov 2004 17:09:49 -0500 (EST) Received: from [130.129.139.226] (rtp-vpn1-86.cisco.com [10.82.224.86]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMX58798; Tue, 9 Nov 2004 17:09:47 -0500 (EST) In-Reply-To: <6FAB860EC6AE3C4EB327204DEC33A528E541AD@wombat.seabridge.co.il> References: <6FAB860EC6AE3C4EB327204DEC33A528E541AD@wombat.seabridge.co.il> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <0FC68842-329C-11D9-AF25-000D93AD480A@cisco.com> Content-Transfer-Encoding: 7bit From: "Thomas D. Nadeau" Date: Tue, 9 Nov 2004 17:09:44 -0500 To: "Nurit Sprecher" X-Mailer: Apple Mail (2.619) X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org, rtg-bfd@ietf.org Subject: Re: [mpls] BFD For MPLS LSPs 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: c1c65599517f9ac32519d043c37c5336 Content-Transfer-Encoding: 7bit On Nov 9, 2004, at 4:35 PM, Nurit Sprecher wrote: > I have some questions about the BFD's draft on BFD for MPLS LSPs. > 1. I think that this should be an MPLS work. It is a specific > mechanism for the MPLS. It was decided to do it in BFD. I don't think it matters much where it is done. > 2. It looks like being companion to the ITU-T OAM mechanism defined > for the MPLS. Which ITU OAM mechanism are you referring to? > Is it? What is the attitude of the MPLS guys for this draft? Which "MPLS guys" are you referring to? > 3. What is the status of this draft? (there was no BFD session this > week). It is almost ready for last call. There are some security concerns with the baseline BFD draft, so we are waiting to make changes to align with any changes there. > 4. Is it compliant to the requirements for the MPLS OAM? Yes, I think so. Many of the same authors worked on both. > 5. Is it a reasonable solution? I think so. 8) --Tom > > Thanks, > > Nurit, > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls