From owner-frnetmib@sunroof.eng.sun.com Tue Oct 10 07:00:24 2000 Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31]) by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA01073; Tue, 10 Oct 2000 07:00:24 -0400 (EDT) Received: from engmail3.Eng.Sun.COM ([129.144.170.5]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA03548; Tue, 10 Oct 2000 04:58:10 -0600 (MDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA09438; Tue, 10 Oct 2000 03:53:26 -0700 (PDT) Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9AAeAk01031 for frnetmib-dist; Tue, 10 Oct 2000 03:40:10 -0700 (PDT) Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5]) by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9AAdj301024 for ; Tue, 10 Oct 2000 03:39:52 -0700 (PDT) Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31]) by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA08589 for ; Tue, 10 Oct 2000 03:39:37 -0700 (PDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA28742 for ; Tue, 10 Oct 2000 04:39:36 -0600 (MDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00646; Tue, 10 Oct 2000 06:39:34 -0400 (EDT) Message-Id: <200010101039.GAA00646@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: frnetmib@sunroof.eng.sun.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: (FRNETMIB) I-D ACTION:draft-ietf-frnetmib-mfrmib-04.txt Date: Tue, 10 Oct 2000 06:39:34 -0400 Sender: owner-frnetmib@sunroof.eng.sun.com Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Frame Relay Service MIB Working Group of the IETF. Title : Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function Author(s) : P. Pate, B. Lynch, K. Rehbehn Filename : draft-ietf-frnetmib-mfrmib-04.txt Pages : 39 Date : 09-Oct-00 This memo defines a Management Information Base (MIB) for monitoring and controlling a UNI/NNI Multilink Frame Relay Function as defined in Frame Relay Forum FRF.16. This MIB also include conformance and notification information. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-frnetmib-mfrmib-04.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-frnetmib-mfrmib-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-frnetmib-mfrmib-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. 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: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20001009132234.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-frnetmib-mfrmib-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-frnetmib-mfrmib-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20001009132234.I-D@ietf.org> --OtherAccess-- --NextPart-- X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message. From owner-frnetmib@sunroof.eng.sun.com Tue Oct 17 20:03:56 2000 Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23165; Tue, 17 Oct 2000 20:03:56 -0400 (EDT) Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA19119; Tue, 17 Oct 2000 18:03:18 -0600 (MDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA16418; Tue, 17 Oct 2000 17:02:54 -0700 (PDT) Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9I02Zi10456 for frnetmib-dist; Tue, 17 Oct 2000 17:02:35 -0700 (PDT) Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5]) by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9I02S310449 for ; Tue, 17 Oct 2000 17:02:28 -0700 (PDT) Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31]) by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA02662 for ; Tue, 17 Oct 2000 17:02:28 -0700 (PDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA18733 for ; Tue, 17 Oct 2000 18:02:26 -0600 (MDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id RAA02532; Tue, 17 Oct 2000 17:02:21 -0700 (PDT) Message-Id: <200010180002.RAA02532@boreas.isi.edu> To: IETF-Announce: ; Subject: (FRNETMIB) RFC 2954 on Frame Relay Service MIB Cc: rfc-ed@ISI.EDU, frnetmib@sunroof.eng.sun.com Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 17 Oct 2000 17:02:21 -0700 From: RFC Editor Sender: owner-frnetmib@sunroof.eng.sun.com Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ --NextPart A new Request for Comments is now available in online RFC libraries. RFC 2954 Title: Definitions of Managed Objects for Frame Relay Service Author(s): K. Rehbehn, D. Fowler Status: Proposed Standard Date: October 2000 Mailbox: krehbehn@megisto.com, fowler@syndesis.com Pages: 76 Characters: 164217 Obsoletes: 1604 I-D Tag: draft-ietf-frnetmib-frs-mib-12.txt URL: ftp://ftp.isi.edu/in-notes/rfc2954.txt This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in Transmission Control Protocol/Internet Protocol-based (TCP/IP) internets. In particular, it defines objects for managing the frame relay service. This document is a product of the Frame Relay Service MIB Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <001017170013.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2954 --OtherAccess Content-Type: Message/External-body; name="rfc2954.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <001017170013.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message. From owner-frnetmib@sunroof.eng.sun.com Tue Oct 17 20:05:32 2000 Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23234; Tue, 17 Oct 2000 20:05:32 -0400 (EDT) Received: from engmail1.Eng.Sun.COM ([129.146.1.13]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA19779; Tue, 17 Oct 2000 18:05:09 -0600 (MDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA13835; Tue, 17 Oct 2000 17:05:01 -0700 (PDT) Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9I04qY10478 for frnetmib-dist; Tue, 17 Oct 2000 17:04:52 -0700 (PDT) Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13]) by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9I04i310471 for ; Tue, 17 Oct 2000 17:04:44 -0700 (PDT) Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5]) by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA13757 for ; Tue, 17 Oct 2000 17:04:45 -0700 (PDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA11987 for ; Tue, 17 Oct 2000 17:04:44 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id RAA03110; Tue, 17 Oct 2000 17:04:40 -0700 (PDT) Message-Id: <200010180004.RAA03110@boreas.isi.edu> To: IETF-Announce: ; Subject: (FRNETMIB) RFC 2955 on FR to ATM Service Interworking MIB Cc: rfc-ed@ISI.EDU, frnetmib@sunroof.eng.sun.com Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Tue, 17 Oct 2000 17:04:40 -0700 From: RFC Editor Sender: owner-frnetmib@sunroof.eng.sun.com Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ --NextPart A new Request for Comments is now available in online RFC libraries. RFC 2955 Title: Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function Author(s): K. Rehbehn, O. Nicklass, G. Mouradian Status: Proposed Standard Date: October 2000 Mailbox: krehbehn@megisto.com, orly_n@rad.co.il, gvm@att.com Pages: 38 Characters: 83281 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-frnetmib-atm-06.txt URL: ftp://ftp.isi.edu/in-notes/rfc2955.txt This memo defines a Management Information Base (MIB) to configure, monitor, and control a service interworking function (IWF) for Permanent Virtual Connections (PVC) between Frame Relay and Asynchronous Transfer Mode (ATM) technologies. This document is a product of the Frame Relay Service MIB Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <001017170247.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2955 --OtherAccess Content-Type: Message/External-body; name="rfc2955.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <001017170247.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message. From owner-frnetmib@sunroof.eng.sun.com Tue Oct 17 22:16:47 2000 Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31]) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA26168; Tue, 17 Oct 2000 22:16:46 -0400 (EDT) Received: from engmail3.Eng.Sun.COM ([129.144.170.5]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA00850; Tue, 17 Oct 2000 20:16:36 -0600 (MDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id TAA23793; Tue, 17 Oct 2000 19:16:28 -0700 (PDT) Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9I2GKe10578 for frnetmib-dist; Tue, 17 Oct 2000 19:16:20 -0700 (PDT) Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25]) by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9I2GF310570 for ; Tue, 17 Oct 2000 19:16:15 -0700 (PDT) Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5]) by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id TAA07470 for ; Tue, 17 Oct 2000 19:16:15 -0700 (PDT) Received: from viva.vivacenet.com (w005.z208036016.sjc-ca.dsl.cnc.net [208.36.16.5]) by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA06226 for ; Tue, 17 Oct 2000 19:16:14 -0700 (PDT) Received: from AMALIS.vivacenetworks.com [10.2.1.96] by viva.vivacenet.com with ESMTP (SMTPD32-5.05) id A7F78C1C03D6; Tue, 17 Oct 2000 19:16:23 -0700 Message-Id: <4.3.2.7.2.20001017221436.02db4458@10.2.0.5> X-Sender: Andy.Malis@10.2.0.5 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 17 Oct 2000 22:16:03 -0400 To: frnetmib@sunroof.eng.sun.com From: "Andrew G. Malis" Subject: Fwd: (FRNETMIB) RFC 2955 on FR to ATM Service Interworking MIB Cc: Andy.Malis@vivacenetworks.com, krehbehn@megisto.com, orly_n@rad.co.il, gvm@att.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-frnetmib@sunroof.eng.sun.com Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ Many thanks to Ken, Orly, and George (who first started this a long time ago) for their hard work. Cheers, Andy ------- Begin of Forwarded Message ------- To: IETF-Announce: ; Subject: (FRNETMIB) RFC 2955 on FR to ATM Service Interworking MIB Cc: rfc-ed@ISI.EDU, frnetmib@sunroof.eng.sun.com Date: Tue, 17 Oct 2000 17:04:40 -0700 From: RFC Editor Sender: owner-frnetmib@sunroof.eng.sun.com X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ X-RCPT-TO: A new Request for Comments is now available in online RFC libraries. RFC 2955 Title: Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function Author(s): K. Rehbehn, O. Nicklass, G. Mouradian Status: Proposed Standard Date: October 2000 Mailbox: krehbehn@megisto.com, orly_n@rad.co.il, gvm@att.com Pages: 38 Characters: 83281 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-frnetmib-atm-06.txt URL: ftp://ftp.isi.edu/in-notes/rfc2955.txt This memo defines a Management Information Base (MIB) to configure, monitor, and control a service interworking function (IWF) for Permanent Virtual Connections (PVC) between Frame Relay and Asynchronous Transfer Mode (ATM) technologies. This document is a product of the Frame Relay Service MIB Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. Content-Type: text/plain Content-ID: <001017170247.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2955 ------- End of Forwarded Message ------- ________________________________________________________________________ Andrew G. Malis Andy.Malis@vivacenetworks.com phone:408-383-7223 Vivace Networks/2730 Orchard Parkway/San Jose, CA 95134/fax:408-904-4748 http://www.vivacenetworks.com X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message. From owner-frnetmib@sunroof.eng.sun.com Tue Oct 17 22:16:50 2000 Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31]) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA26181; Tue, 17 Oct 2000 22:16:49 -0400 (EDT) Received: from engmail3.Eng.Sun.COM ([129.144.170.5]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA00445; Tue, 17 Oct 2000 20:14:54 -0600 (MDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id TAA23634; Tue, 17 Oct 2000 19:14:39 -0700 (PDT) Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9I2EUW10555 for frnetmib-dist; Tue, 17 Oct 2000 19:14:30 -0700 (PDT) Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5]) by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9I2EP310548 for ; Tue, 17 Oct 2000 19:14:25 -0700 (PDT) Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5]) by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id TAA23605 for ; Tue, 17 Oct 2000 19:14:25 -0700 (PDT) Received: from viva.vivacenet.com (w005.z208036016.sjc-ca.dsl.cnc.net [208.36.16.5]) by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA05600 for ; Tue, 17 Oct 2000 19:14:24 -0700 (PDT) Received: from AMALIS.vivacenetworks.com [10.2.1.96] by viva.vivacenet.com with ESMTP (SMTPD32-5.05) id A78D8BC303D6; Tue, 17 Oct 2000 19:14:37 -0700 Message-Id: <4.3.2.7.2.20001017221032.030f1a70@10.2.0.5> X-Sender: Andy.Malis@10.2.0.5 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 17 Oct 2000 22:12:00 -0400 To: frnetmib@sunroof.eng.sun.com From: "Andrew G. Malis" Subject: Fwd: (FRNETMIB) RFC 2954 on Frame Relay Service MIB Cc: Andy.Malis@vivacenetworks.com, krehbehn@megisto.com, fowler@syndesis.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-frnetmib@sunroof.eng.sun.com Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ Congratulations and thanks to Ken and Dave!!! Andy ------- Begin of Forwarded Message ------- To: IETF-Announce: ; Subject: (FRNETMIB) RFC 2954 on Frame Relay Service MIB Cc: rfc-ed@ISI.EDU, frnetmib@sunroof.eng.sun.com Date: Tue, 17 Oct 2000 17:02:21 -0700 From: RFC Editor Sender: owner-frnetmib@sunroof.eng.sun.com X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ X-RCPT-TO: A new Request for Comments is now available in online RFC libraries. RFC 2954 Title: Definitions of Managed Objects for Frame Relay Service Author(s): K. Rehbehn, D. Fowler Status: Proposed Standard Date: October 2000 Mailbox: krehbehn@megisto.com, fowler@syndesis.com Pages: 76 Characters: 164217 Obsoletes: 1604 I-D Tag: draft-ietf-frnetmib-frs-mib-12.txt URL: ftp://ftp.isi.edu/in-notes/rfc2954.txt This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in Transmission Control Protocol/Internet Protocol-based (TCP/IP) internets. In particular, it defines objects for managing the frame relay service. This document is a product of the Frame Relay Service MIB Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. Content-Type: text/plain Content-ID: <001017170013.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2954 ------- End of Forwarded Message ------- ________________________________________________________________________ Andrew G. Malis Andy.Malis@vivacenetworks.com phone:408-383-7223 Vivace Networks/2730 Orchard Parkway/San Jose, CA 95134/fax:408-904-4748 http://www.vivacenetworks.com X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message. From owner-frnetmib@sunroof.eng.sun.com Fri Oct 27 12:49:52 2000 Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA25553; Fri, 27 Oct 2000 12:49:52 -0400 (EDT) Received: from engmail1.Eng.Sun.COM ([129.146.1.13]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA03951; Fri, 27 Oct 2000 10:46:58 -0600 (MDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA26584; Fri, 27 Oct 2000 09:42:51 -0700 (PDT) Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) id e9RGgea19410 for frnetmib-dist; Fri, 27 Oct 2000 09:42:40 -0700 (PDT) Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5]) by sunroof.eng.sun.com (8.11.1+Sun/8.11.1) with ESMTP id e9RGgW319403 for ; Fri, 27 Oct 2000 09:42:32 -0700 (PDT) Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5]) by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA29175 for ; Fri, 27 Oct 2000 09:42:32 -0700 (PDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA21254 for ; Fri, 27 Oct 2000 09:42:31 -0700 (PDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23075; Fri, 27 Oct 2000 12:42:18 -0400 (EDT) Message-Id: <200010271642.MAA23075@ietf.org> To: IETF-Announce: ; Cc: RFC Editor , IANA Cc: Internet Architecture Board Cc: frnetmib@sunroof.eng.sun.com From: The IESG Subject: (FRNETMIB) Protocol Action: Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function to Proposed Standard Date: Fri, 27 Oct 2000 12:42:18 -0400 Sender: owner-frnetmib@sunroof.eng.sun.com Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ The IESG has approved the Internet-Draft 'Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function' as a Proposed Standard. This document is the product of the Frame Relay Service MIB Working Group. The IESG contact persons are Erik Nordmark and Thomas Narten. Technical Summary The document defines a Management Information Base (MIB) for monitoring and controlling a UNI/NNI Multilink Frame Relay Function as defined in Frame Relay Forum FRF.16. This MIB also include conformance and notification information. Working Group Summary There was consensus in thw WG to advance this document. Protocol Quality The specification has been revied for the IESG by Dan Romascanu, Bert Wijnen, and Erik Nordmark. X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message.