From mailman-owner@ietf.org Thu Feb 1 05:04:02 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA22651 for ; Thu, 1 Feb 2001 05:04:02 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA03120 for ; Thu, 1 Feb 2001 05:04:02 -0500 (EST) Date: Thu, 1 Feb 2001 05:04:02 -0500 (EST) Message-Id: <200102011004.FAA03120@optimus.ietf.org> From: mailman-owner@ietf.org Subject: ietf.org mailing list memberships reminder To: bridge-mib-web-archive@ns.ietf.org X-No-Archive: yes Precedence: bulk X-Mailman-Version: 1.0 Precedence: bulk List-Id: Diffserv Discussion List 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, bridge-mib-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! Passwords for bridge-mib-web-archive@optimus.ietf.org: List Password // URL ---- -------- bridge-mib@ietf.org cCGJ http://www.ietf.org/mailman/options/bridge-mib/bridge-mib-web-archive@optimus.ietf.org From bbnt9@building.com Wed Feb 7 03:14:06 2001 Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA26464 for ; Wed, 7 Feb 2001 03:14:05 -0500 (EST) Received: from sj-msg-av-3.cisco.com (sj-msg-av-3.cisco.com [171.69.2.19]) by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id XAA02786 for ; Tue, 6 Feb 2001 23:40:48 -0800 (PST) Received: from proxy3.cisco.com (localhost [127.0.0.1]) by sj-msg-av-3.cisco.com (8.10.1/8.10.1) with ESMTP id f177eY525129 for ; Tue, 6 Feb 2001 23:40:34 -0800 (PST) Received: from mailsvr.insuworld.co.kr (mailsvr.dongyangfire.co.kr [210.124.51.4] (may be forged)) by proxy3.cisco.com (8.11.2/8.11.2) with SMTP id f177eY617641 for ; Tue, 6 Feb 2001 23:40:34 -0800 (PST) Received: from host (unverified [38.26.242.194]) by mailsvr.insuworld.co.kr (EMWAC SMTPRS 0.83) with SMTP id ; Wed, 07 Feb 2001 16:25:33 +0900 Message-ID: From: "Craig Heroux" Subject: Your Request #4656 To: on398d@cisco.com X-Mailer: Microsoft Outlook Express 4.72.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE VÐßD.1712.3 Mime-Version: 1.0 Date: Tue, 06 Feb 2001 21:35:10 -0500 Content-Type: multipart/mixed; boundary="----=_NextPart_000_007F_01BDF6C7.FABAC1B0" This is a MIME Message ------=_NextPart_000_007F_01BDF6C7.FABAC1B0 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0080_01BDF6C7.FABAC1B0" ------=_NextPart_001_0080_01BDF6C7.FABAC1B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ***** This is an HTML Message ! ***** ------=_NextPart_001_0080_01BDF6C7.FABAC1B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Candidate,

You have been selected as a potential candidate= for a free listing in
the 2001 Edition of the International Executiv= e Guild Registry=2E

Please accept our congratulations for this cove= ted honor=2E

As this edition is so important in view of the new millennium, the
International Executive Guild Registry will be= published in two different
formats; the searchable CD-ROM and the Online Registry=2E

Since inclusion can be considered recognition of your career position
and professionalism, each candidate is evaluat= ed in keeping with high
standards of individual achievement=2E In ligh= t of this, the International Executive
Guild thinks that you may make an interesting biographical subject=2E

We look forward to your inclusion and appearanc= e in the International
Executive Guild's Registry=2E Best wishes for = your continued success=2E

International Executive Guild
Listing Dept=2E

If you wish to be removed from our list, please submit your request
at= the bottom of this email=2E



*International Execut= ive Guild* Registration Form (US and Canada Only)
Please fill out this form if you would like to be included in The International Executive Guild's Registry=2E For accuracy and publication purposes, pleas= e complete and send this form at the earliest opportunity=2E There is no charge or obligation to be listed in The International Exe= cutive Guild's Registry=2E

Your Name
Your Company
Title
Address
City
State or Province
Country
ZIP/Postal Code
Day Time Telephone
Home Phone	(Not To Be Published)
Email

TO HELP US IN CONSIDERING YOUR APPLICATION, PLEASE TELL US A LITTLE ABOUT YOURSELF=2E=2E=2E


Your Business	(Fi= nancial Svcs, Banking, Computer Hardware, Software, Professional Svcs, Chemicals, Apparel, Aerospace, Food, Government, Utility, etc=2E)
Type of Organization	(Mf= g, Dist/Wholesaler, Retailer, Law Firm, Investment Bank, Commercial Bank, University, Financial Consultants, Ad Agency, Contractor, Broker, etc=2E)
Your Business Expertise	(Co= rp=2EMgmt, Marketing, Civil Engineering, Tax Law, Nuclear Physics, Database Development, Operations, Pathologist, Mortg= age Banking, etc=2E)
Major Product Line	(In= tegrated Circuits, Commercial Aircraft, Adhesives, Cosmetics, Plastic Components, Snack Foods, etc=2E)

Note: Submitting this form = will be made by email, not by use of www=2E Confirmation of its del= ivery is made by browsing your outgoing mail=2E

Thank you for filling in this form, we will contact you with more information=2E=

List Removal
Click Here ------=_NextPart_001_0080_01BDF6C7.FABAC1B0-- ------=_NextPart_000_007F_01BDF6C7.FABAC1B0-- From bridge-mib-admin@ietf.org Fri Feb 16 16:21:52 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA09941 for ; Fri, 16 Feb 2001 16:21:52 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22555; Fri, 16 Feb 2001 16:21:49 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22526 for ; Fri, 16 Feb 2001 16:21:48 -0500 (EST) Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA09937 for ; Fri, 16 Feb 2001 16:21:44 -0500 (EST) Received: from ihemail2.firewall.lucent.com (localhost [127.0.0.1]) by ihemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id QAA29549 for ; Fri, 16 Feb 2001 16:21:46 -0500 (EST) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id QAA29534 for ; Fri, 16 Feb 2001 16:21:45 -0500 (EST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2650.21) id ; Fri, 16 Feb 2001 22:21:42 +0100 Message-ID: <2413FED0DFE6D111B3F90008C7FA61FB0B429812@nl0006exch002u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: BridgeMIB Cc: Randy Bush Date: Fri, 16 Feb 2001 22:21:41 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Subject: [Bridge-mib] New WG chair Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org Hello Bridge-MIBers, Keith has indicated that he will not have time to stay on as a Bridge MIB WG chair. There are two options: - shut down the WG - find a new WG chair and see what work needs to be done. Les Bell has volunteered to become WG chair. I have been discussing a possible new WG charter with him. Les will post it to the list soon... so that the WG can decide if they indeed want to subscribe to this work and then come up with volunteers to actually DO that work. Bert _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org http://www.ietf.org/mailman/listinfo/bridge-mib From bridge-mib-admin@ietf.org Mon Feb 19 11:45:04 2001 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA08754 for ; Mon, 19 Feb 2001 11:45:03 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA22815; Mon, 19 Feb 2001 11:44:55 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA22784 for ; Mon, 19 Feb 2001 11:44:54 -0500 (EST) Received: from columba.eur.3com.com (columba.EUR.3Com.COM [161.71.169.13]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA08750 for ; Mon, 19 Feb 2001 11:44:51 -0500 (EST) Received: from toucana.eur.3com.com (eurelay.eur.3com.com [140.204.220.50]) by columba.eur.3com.com (8.9.3/8.9.3) with ESMTP id QAA21719 for ; Mon, 19 Feb 2001 16:42:36 GMT Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206]) by toucana.eur.3com.com (8.9.3/8.9.3) with SMTP id QAA22511 for ; Mon, 19 Feb 2001 16:37:35 GMT Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 802569F8.005BFCA5 ; Mon, 19 Feb 2001 16:44:44 +0000 X-Lotus-FromDomain: 3COM From: "Les Bell" To: bridge-mib@ietf.org Message-ID: <802569F8.005BF989.00@notesmta.eur.3com.com> Date: Mon, 19 Feb 2001 16:44:29 +0000 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Bridge-mib] Proposed re-charter for the Bridge MIB WG Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org Hi folks, The IEEE 802.1 working group is in the final stages of approval for a number of proposed new standards. 802.1t, 802.1u, 802.1v and 802.1w are extensions to the 802.1D and 802.1Q standards that we are all familiar with, and manage through the MIBs in RFC 1493, RFC 1525 and RFC 2674. I think that these standards have reached the stage where it is appropriate to develop a standard MIB, or MIBs, to manage the new features. The extent of the new features is much less dramatic than the last set of features we did for VLANs, Priorities, and Multicast Filtering, in RFC 2674. We also need to progress the current MIBs, which includes translating RFC 1493 and RFC 1525 to SMIv2 format and determing the current level of implementation support for them, and also for RFC 2674. The first thing I need to do, as the new WG chair, is to determine if there is sufficient interest in supporting and helping to develop this work. If there is enough interest, we can begin work on the new MIBs and book timeslots at upcoming IETF meetings to discuss it. We will not have enough work prepared for the Minnesota meeting in March, so I hope to get an I-D ready to discuss at the August meeting, in London. I am particularly keen to hear from anyone who can help with contributions and act as Editor(s) for the proposed new MIB(s). The proposed re-charter for the Bridge MIB WG is at the end of this email. Thanks, Les Bell (Bridge MIB WG chair) -------- Status: Proposed Recharter (with new WG chair) Bridge MIB (bridge) Last Modified: 18-Feb-01 Chair(s): Les Bell Operations and Management Area Director(s): Randy Bush Bert Wijnen Operations and Management Area Advisor: Bert Wijnen Mailing Lists: General Discussion: bridge-mib@ietf.org To Subscribe: bridge-mib-request@ietf.org In Body: subscribe your_email_address Archive: ftp://ftp.ietf.org/ietf-mail-archive/bridge/ Description of Working Group: The Bridge MIB Working Group is chartered to define a set of managed objects that instrument devices that conform to the IEEE 802.1 standards for MAC-layer bridges. This set of objects should be largely compliant with (and even draw from) those objects defined within each of the IEEE 802.1 standards, although there is no requirement that any specific object be present or absent. The set of objects should not duplicate, nor conflict with any MIB object definitions defined by the IEEE 802.1 standards themselves. The MIB object definitions produced will be for use by SNMP and will be consistent with other SNMP objects, standards, and conventions. Goals and Milestones: Done Publish initial proposal. Done Submit an Internet-Draft. Done Submit draft for RFC publication. Done Publish a draft SNMP MIB that instruments functions specific to source routed bridges as Internet-Draft. Done Publish a draft revision to RFC 1286 that reflects implementation experience and the result of alignments with IEEE work as an Internet-Draft. Done Submit draft MIB for source routing bridge functions to IESG for consideration as a Proposed Standard. Done Submit a new MIB document with support for recently developed 802.1p and 802.1Q specifications to the IESG for consideration as a Proposed Standard. Jul 01 Submit new I-D for RFC 1493 in SMIv2 format. Jul 01 Submit new I-D for RFC 1525 in SMIv2 format. Aug 01 Evaluate status of RFC 1493 and the SMIv2 version and get WG consensus if it should be recycled at Draft or can be elevated to Full Standard. Aug 01 Evaluate status of RFC 1525 and the SMIv2 version and get WG consensus if it should be recycled at Draft or can be elevated to Full Standard. Aug 01 Evaluate status of RFC 2674 and and get WG consensus if it should be recycled at Proposed or can be elevated to Draft Standard. Aug 01 Submit an Internet-Draft (or drafts) with MIB support for extensions to the Bridge standards defined in 802.1t, 802.1u, 802.1v and 802.1w. Sep 01 Submit SMIv2 version of RFC 1493 to IESG for consideration as Full Standard. Sep 01 Submit SMIv2 version of RFC 1523 to IESG for consideration as Full Standard. Sep 01 Submit RFC 2674 (or new I-D if clarifications had to be made) to IESG for consideration as Draft Standard. Dec 01 Revise the Internet-Draft(s) with MIB support for extensions to the Bridge standards defined in 802.1t, 802.1u, 802.1v and 802.1w. Mar 02 Submit completed draft(s) with MIB support for extensions to the Bridge standards defined in 802.1t, 802.1u, 802.1v and 802.1w to the IESG, for consideration as a Proposed Standard. No Current Internet-Drafts Request For Comments: Definitions of Managed Objects for Bridges (RFC 1493) (74493 bytes) Definitions of Managed Objects for Source Routing Bridges (RFC 1525) (38100 bytes) Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions (RFC 2674) (159971 bytes) _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org http://www.ietf.org/mailman/listinfo/bridge-mib