From owner-frnetmib@sunroof.eng.sun.com Thu Dec 7 20:39:14 2000 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA26701 for ; Thu, 7 Dec 2000 20:39:14 -0500 (EST) Received: from engmail3.Eng.Sun.COM ([129.144.170.5]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA07885; Thu, 7 Dec 2000 17:34:08 -0800 (PST) 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 RAA01122; Thu, 7 Dec 2000 17:33:39 -0800 (PST) Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.11.2.Beta1+Sun/8.11.2.Beta1) id eB81XSv11323 for frnetmib-dist; Thu, 7 Dec 2000 17:33:28 -0800 (PST) Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5]) by sunroof.eng.sun.com (8.11.2.Beta1+Sun/8.11.2.Beta1) with ESMTP id eB81XLr11316 for ; Thu, 7 Dec 2000 17:33:21 -0800 (PST) Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2]) by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA01082 for ; Thu, 7 Dec 2000 17:33:21 -0800 (PST) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA11538 for ; Thu, 7 Dec 2000 17:33:21 -0800 (PST) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id RAA16680; Thu, 7 Dec 2000 17:33:19 -0800 (PST) Message-Id: <200012080133.RAA16680@boreas.isi.edu> To: IETF-Announce: ; Subject: (FRNETMIB) RFC 3020 on MIB for FRF.16 UNI/NNI MFR Cc: rfc-ed@ISI.EDU, frnetmib@sunroof.eng.sun.com Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 07 Dec 2000 17:33:19 -0800 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 3020 Title: Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function Author(s): P. Pate, B. Lynch, K. Rehbehn Status: Standards Track Date: December 2000 Mailbox: prayson.pate@overturenetworks.com, bob.lynch@overturenetworks.com, krehbehn@megisto.com Pages: 36 Characters: 67736 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-frnetmib-mfrmib-04.txt URL: ftp://ftp.isi.edu/in-notes/rfc3020.txt 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 includes conformance and notification information. 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: <001207173120.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3020 --OtherAccess Content-Type: Message/External-body; name="rfc3020.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <001207173120.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 Fri Dec 8 10:58:21 2000 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA01952 for ; Fri, 8 Dec 2000 10:58:20 -0500 (EST) Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA04763; Fri, 8 Dec 2000 07:57:46 -0800 (PST) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA12615; Fri, 8 Dec 2000 07:56:28 -0800 (PST) Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.11.2.Beta1+Sun/8.11.2.Beta1) id eB8FuHr11867 for frnetmib-dist; Fri, 8 Dec 2000 07:56:17 -0800 (PST) Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25]) by sunroof.eng.sun.com (8.11.2.Beta1+Sun/8.11.2.Beta1) with ESMTP id eB8FuCr11860 for ; Fri, 8 Dec 2000 07:56:12 -0800 (PST) Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43]) by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA01128 for ; Fri, 8 Dec 2000 07:56:13 -0800 (PST) Received: from ha2.ntr.net (etc.ntr.net [206.112.0.11]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAB14814 for ; Fri, 8 Dec 2000 07:56:12 -0800 (PST) Received: from AMALIS.vivacenet.com (1Cust145.tnt18.sdg1.da.uu.net [63.42.247.145]) by ha2.ntr.net (8.9.3/8.9.3) with ESMTP id KAA52074477 for ; Fri, 8 Dec 2000 10:56:06 -0500 (EST) Message-Id: <4.3.2.7.2.20001208105522.030f8f80@viva.vivacenet.com> X-Sender: Andy.Malis@viva.vivacenet.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 08 Dec 2000 10:56:04 -0500 To: frnetmib@sunroof.eng.sun.com From: "Andrew G. Malis" Subject: Fwd: (FRNETMIB) RFC 3020 on MIB for FRF.16 UNI/NNI MFR 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/ I know that you all saw this already, but congrats to Prayson, Bob, and Ken on their hard work! Cheers, Andy ------- Begin of Forwarded Message ------- To: IETF-Announce: ; Subject: (FRNETMIB) RFC 3020 on MIB for FRF.16 UNI/NNI MFR Cc: rfc-ed@ISI.EDU, frnetmib@sunroof.eng.sun.com Date: Thu, 07 Dec 2000 17:33:19 -0800 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 3020 Title: Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function Author(s): P. Pate, B. Lynch, K. Rehbehn Status: Standards Track Date: December 2000 Mailbox: prayson.pate@overturenetworks.com, bob.lynch@overturenetworks.com, krehbehn@megisto.com Pages: 36 Characters: 67736 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-frnetmib-mfrmib-04.txt URL: ftp://ftp.isi.edu/in-notes/rfc3020.txt 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 includes conformance and notification information. 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: <001207173120.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3020 ------- End of Forwarded Message ------- 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 Wed Dec 13 19:43:15 2000 Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA02172 for ; Wed, 13 Dec 2000 19:43:14 -0500 (EST) Received: from engmail3.Eng.Sun.COM ([129.144.170.5]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA13074; Wed, 13 Dec 2000 16:42:37 -0800 (PST) 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 QAA27294; Wed, 13 Dec 2000 16:42:12 -0800 (PST) Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.11.2.Beta1+Sun/8.11.2.Beta1) id eBE0fxN15796 for frnetmib-dist; Wed, 13 Dec 2000 16:41:59 -0800 (PST) Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13]) by sunroof.eng.sun.com (8.11.2.Beta1+Sun/8.11.2.Beta1) with ESMTP id eBE0fsr15789 for ; Wed, 13 Dec 2000 16:41:54 -0800 (PST) Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2]) by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA18177 for ; Wed, 13 Dec 2000 16:41:55 -0800 (PST) Received: from ha2.ntr.net (etc.ntr.net [206.112.0.11]) by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA29764 for ; Wed, 13 Dec 2000 16:41:54 -0800 (PST) Received: from AMALIS.vivacenet.com (ietf.207.137.74.63.tx.verio.net [207.137.74.63]) by ha2.ntr.net (8.9.3/8.9.3) with ESMTP id TAA55760148; Wed, 13 Dec 2000 19:41:46 -0500 (EST) Message-Id: <5.0.2.1.0.20001213193626.03272168@viva.vivacenet.com> X-Sender: Andy.Malis@viva.vivacenet.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 13 Dec 2000 19:41:43 -0500 To: frnetmib@sunroof.eng.sun.com From: "Andrew G. Malis" Subject: (FRNETMIB) frnetmib draft minutes Cc: Andy.Malis@vivacenetworks.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/ I've enclosed the frnetmib draft minutes, from Ken. Many many thanks to Ken for filling in for me while I was presenting elsewhere. Please respond if you have any comments. Cheers, Andy -------- Frame Relay Service MIB WG (frnetmib) Minutes Chair: Andy Malis Guest Chair: Ken Rehbehn The frnetmib working group met Tuesday, December 12, 2000 from 1700 to 1800. AGENDA: 1. Administrivia, current WG status - The following working group documents have been published as RFCs: RFC 2954, Definitions of Managed Objects for Frame Relay Service RFC 2955, Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function RFC 3020, Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function - The working group expects to go into maintenance mode (i.e. just be the email list) once the two on-going working group documents (frmrelay-service and frsi MIBs) are complete. 2. Ken Rehbehn, quick overview of the final revisions to RFC 3020 (was draft-ietf-frnetmib-mfrmib-04.txt), Definitions of Managed Objects for Monitoring and Controlling the UNI/NNI Multilink Frame Relay Function Ken presented the major changes to the MFR MIB resulting from the IESG review prior to publication. The main changes were: o A variety of clarifications regarding MIB operation o Changed location from experimental to under mib-2 transmission o Added ranges and descriptions of the meaning of a value -1 o Changed descriptors starting with "bundleXxxx" to "mfrBundleXxx" o Eliminated intermediate nodes mfrMibScalarObjects, mfrMibBundleObjects and mfrMibBundleLinkObjects 3. Rob Steinberger and Orly Nicklass, draft-ietf-frnetmib-frmrelay-service-02.txt, Definitions of Managed Objects for Frame Relay Service Level Definitions (FRF.13) Rob reviewed the changes made since the conclusion of the Working Group Last Call and the Pittsburgh meeting. The major changes included the removal of the free running counters, the merger of the availability and data tables, the use of a consistent prefix for the MIB object names, and new ASCII figures. An additional clarification will be provided in the next version of the MIB (.03) to replace Section 3.6.2. The new text describes 2 half-duplex flows evaluated with a total of 4 reference points. Randy Presuhn recommended use of the term "uni-directional" instead of half-duplex to characterize the flow. The new draft will be published in the next several weeks. The working group consensus is to forward the draft to IETF Last Call following a short review period for the new changes. 4. Rob Steinberger and Orly Nicklass, Rob Steinberger and Orly Nicklass, draft-ietf-frnetmib-frsi-00.txt, Frame Relay Circuit Interface MIB This MIB provides the ability to generate ifEntries for frame circuits. The motivation is that neither RFC 2115 nor RFC 1604 create ifEntries for DLCIs. RMON requires an ifIndex to monitor a data source, so the RMON WG requested that we do this work during the Adelaide meeting. In addition, routing MIBs (such as the CIDR Routing Table and Net to Media table) require ifIndex to control routing. Without it, you cannot control or display the routing to or on virtual circuits in a non-proprietary manner. There is not a need to create ifIndex for every circuit, but it would be nice to have one for the interesting circuits. Rob described recent changes to the MIB. Frame relay specific terms were changed to allow application of the MIB to ATM connections. A specific ATM example was added to the MIB to illustrate usage in an ATM application. Rob will obtain new ifType codepoints from IANA for both frame relay and ATM connections. He will then publish the updated MIB. The consensus of the working group is that Working Group Last Call should begin when the updated MIB is available. 4. Open discussion There being none, the group adjourned. ________________________________________________________________________ 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 Thu Dec 21 06:52:31 2000 Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA15263 for ; Thu, 21 Dec 2000 06:52:29 -0500 (EST) Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA06234; Thu, 21 Dec 2000 03:47:21 -0800 (PST) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA19829; Thu, 21 Dec 2000 03:47:10 -0800 (PST) Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.11.2.Beta2+Sun/8.11.2.Beta2) id eBLBl2X22660 for frnetmib-dist; Thu, 21 Dec 2000 03:47:02 -0800 (PST) Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6]) by sunroof.eng.sun.com (8.11.2.Beta2+Sun/8.11.2.Beta2) with ESMTP id eBLBktH22653 for ; Thu, 21 Dec 2000 03:46:55 -0800 (PST) Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31]) by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA19815 for ; Thu, 21 Dec 2000 03:46:54 -0800 (PST) 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 EAA06790 for ; Thu, 21 Dec 2000 04:46:53 -0700 (MST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15001; Thu, 21 Dec 2000 06:45:44 -0500 (EST) Message-Id: <200012211145.GAA15001@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-frmrelay-service-03.txt Date: Thu, 21 Dec 2000 06:45:44 -0500 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 Frame Relay Service Level Definitions Author(s) : R. Steinberger, O. Nicklass Filename : draft-ietf-frnetmib-frmrelay-service-03.txt Pages : 57 Date : 20-Dec-00 This memo defines an extension of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Frame Relay Service Level Definitions. This memo does not specify a standard for the Internet community. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-frnetmib-frmrelay-service-03.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-frmrelay-service-03.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-frmrelay-service-03.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: <20001220160656.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-frnetmib-frmrelay-service-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-frnetmib-frmrelay-service-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20001220160656.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.