From owner-frnetmib@sunroof.eng.sun.com Mon May 24 00:25:34 1999 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14366; Mon, 24 May 1999 00:25:33 -0400 (EDT) Received: from engmail2.Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id VAA29724; Sun, 23 May 1999 21:25:24 -0700 (PDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id VAA23342; Sun, 23 May 1999 21:25:23 -0700 (PDT) Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id VAA09298 for frnetmib-dist; Sun, 23 May 1999 21:25:08 -0700 (PDT) Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6]) by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id VAA09291 for ; Sun, 23 May 1999 21:25:03 -0700 (PDT) Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5]) by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id VAA16436 for ; Sun, 23 May 1999 21:25:04 -0700 (PDT) Received: from mail.visualnetworks.com ([208.22.72.43]) by venus.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id VAA13482 for ; Sun, 23 May 1999 21:25:03 -0700 (PDT) Received: from shemp by mail.visualnetworks.com via smtpd (for venus.Sun.COM [192.9.25.5]) with SMTP; 24 May 1999 04:32:34 UT Received: from kenr (KENR.visualnetworks.com [208.22.74.191]) by shemp.visualnetworks.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id L2J2H37J; Mon, 24 May 1999 00:27:58 -0400 Reply-To: From: "Ken Rehbehn" To: Subject: (FRNETMIB) A Cross-Connect Model for the FR/ATM PVC Service IWF MIB Date: Mon, 24 May 1999 00:22:23 -0400 Message-ID: <000201bea59d$06a556a0$bf4a16d0@kenr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal 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/ Content-Transfer-Encoding: 7bit The next draft is being prepared for the FR/ATM PVC IWF MIB. In this draft, we must deal with the open issue of how this cross-connect MIB is utilized by the RFC 1604 and RFC 2515 technology-specific MIBs (TSM). This is a proposal Orly and I have produced for dealing with the problem. Each TSM has a table of PVC endpoints (indexed by ifIndex and logical link address (DLCI or VPI/VCI). Typically, two endpoints are cross-connected via a technology-specific cross connect table. The introduction of the FR/ATM MIB creates the need to have multiple cross-connect tables. As an example, an ATM PVC endpoint might be connected to either: 1) another ATM PVC endpoint via the atmVcCrossConnectTable, or 2) a frame relay PVC endpoint via the frAtmIwfConnectionTable. This issue is not restricted to the case of frame relay to ATM interworking. An implementation supporting the ATM Forum Circuit Emulation Service (CES) is another example of an ATM VPI/VCI that is not cross-connected via the atmVcCrossConnectTable. Currently, the implicit assumption is made that all PVC endpoints are cross-connected via a single cross-connect table. To change this restriction, one new object is required for each PVC endpoint rows, in both the ATM and Frame Relay Service MIBs. The object (named xxxIwfKind, where xxx == atmVcl or frPVC) serves to identify the cross-connect table associated with the PVC endpoint. I propose that use of an OID value that matches the OID of the IWF MIB cross-connect table that applies (e.g., (1.3.6.1.2.1.10.45.1.2) for the FR/ATM IWF MIB frAtmIwfConnectionTable (assumes the FR/ATM PVC IWF MIB will be planted at { transmission 45 }). A value of zero (or noSuchObject) indicates cross-connection via the technology-specific cross-connect table. Such an approach readily supports standards-based and vendor-specific cross-connects. Each TSM contains an existing object that contains an index into the cross-connect table. In the case of the ATM MIB, the cross-connect index might point into one of several cross-connect tables. I propose we use these existing cross-connect objects to contain the index into the FR/ATM MIB cross-connect table. The ATM MIB has an object called AtmConnKind. It enumerates a number of different connection cases and, as a side-effect, points to the correct cross-connection table. We should consider adding an enumeration to this list for generic IWF cross-connection where the actual cross-connection table is identified in the atmVclIwfKind object. The example at the end of this email shows how a frame relay PVC endpoint is cross-connected to an ATM PVC endpoint. The AtmConnKind object is ignored in this example. Review and comments are needed. Cheers, Ken Rehbehn --------------------------------------------------------------- Ken Rehbehn Phone: +1-301-296-2325 Visual Networks Fax: +1-301-296-2302 2092 Gaither Rd EMail: krehbehn@visualnetworks.com Rockville, MD 20850 http://www.visualnetworks.com == == == == == == == == == == == == == == == == == == == == == == Example Cross-Connect using the FR/ATM PVC IWF MIB -------------------------------------------------- ASSUMPTIONS: o Frame Relay PVC is DLCI 16 on ifIndex 123 o ATM PVC is VPI.VCI 45.98 on ifIndex 987 o The FR/ATM IWF MIB OID root is assigned by IANA to { transmission 45} o All xxxAdminStatus objects reflect an "up" status o No errors in activation for any PVC segment so that xxxOperStatus can reflect an "active" status Step 1 - Create the frame relay PVC endpoint a) Agent receives management request to create a row in frPVCEndptTable for the frame side b) system creates the row in frPVCEndptTable with the following defaults: - initialize frPVCEndptConnectIdentifier to zero - initialize frPVCIWFKind to 0.0 - initialize the remaining columns as needed for DLCI 16 on ifIndex 123 Step 2 - Create the ATM PVC endpoint a) agent receives management request to create a row in atmVclTable for the ATM side b) system creates the row in atmVclTable with the following defaults: - initialize atmVclCrossConnectIdentifier to zero - initialize atmVclIWFKind to 0.0 - initialize the remaining columns as needed for VPI.VCI 45.98 on ifIndex 987 Step 3 - Create the FR/ATM cross-connect a) manager requests a new cross-connect index value by reading frAtmIwfConnectionIndexNext from the agent b) agent receives GET request for frAtmIwfConnectionIndexNext and responds with the next available value (9901 - Hey, its a big switch) c) manager requests a new cross-connect row entry using the value 9901 as the index d) agent receives SET request to create the frAtmIwfConnectionTable row entry (note: the frame relay and ATM PVC endpoints MUST exist and be specified as part of the index fields for the row) e) system creates a row in frAtmIwfConnectionTable for the following indices: - frAtmIwfConnectionIndex of 9901 - frAtmIwfConnAtmPort of 987 - frAtmIwfConnVpi of 45 - frAtmIwfConnVci of 98 - frAtmIwfConnFrPort of 123 - frAtmIwfConnDlci of 16 f) system establishes the appropriate connection descriptor for the IWF (specified by manager in the SET for the row) and assigns it to frAtmIwfcOnnectionDescriptorIdx Step 4 - Point the frame relay PVC endpoint row to the FR/ATM cross-connect row (Note: The system may perform these actions as a side-effect of Step 3) a) system sets frPVCEndptConnectIdentifier to 9901 b) system sets frPVCIWFKind to (1.3.6.1.2.1.10.45.1.2) to point to the FR/ATM PVC IWF cross-connect table Step 5 - Point the ATM PVC endpoint row to the FR/ATM cross-connect row (Note: The system may perform these actions as a side-effect of Step 3) a) system sets atmVclCrossConnectIdentifier to 9901 b) system sets atmVclIWFKind to (1.3.6.1.2.1.10.45.1.2) Step 6 - Manager signals activation by issuing a SET for the frAtmIwfConnAdminStatus object using the value of "up" Step 7 - Agent receives SET request for frAtmIwfConnAdminStatus and executes internal system mechanisms to activate each PVC segment and the IWF cross-connect. The successful activation permits the agent to respond with "active" when a GET request is received for the following fields: - frAtmIwfConnAtm2FrOperStatus - frAtmIwfConnFr2AtmOperStatus - atmVclOperStatus (Note: there is no comparable FRS MIB object) 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 May 28 15:01:23 1999 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00314; Fri, 28 May 1999 15:01:22 -0400 (EDT) Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA01795; Fri, 28 May 1999 12:01:20 -0700 (PDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id MAA16225; Fri, 28 May 1999 12:01:18 -0700 (PDT) Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id MAA14432 for frnetmib-dist; Fri, 28 May 1999 12:00:07 -0700 (PDT) Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25]) by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA14425 for ; Fri, 28 May 1999 12:00:01 -0700 (PDT) Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31]) by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id LAA18255 for ; Fri, 28 May 1999 11:59:58 -0700 (PDT) Received: from alpo.casc.com (alpo.casc.com [152.148.10.6]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA28009 for ; Fri, 28 May 1999 12:59:57 -0600 (MDT) Received: from apollo13.casc.com (apollo13 [152.148.10.13]) by alpo.casc.com (8.9.1a/8.9.1) with ESMTP id OAA24723; Fri, 28 May 1999 14:59:53 -0400 (EDT) Received: from localhost by apollo13.casc.com (8.8.8+Sun/SMI-SVR4) id OAA16240; Fri, 28 May 1999 14:59:52 -0400 (EDT) Date: Fri, 28 May 1999 14:59:52 -0400 (EDT) From: "Andrew G. Malis" X-Sender: amalis@apollo13 To: frnetmib@sunroof.eng.sun.com cc: "Andrew G. Malis" Subject: (FRNETMIB) 45th IETF-OSLO, NORWAY: FRNETMIB (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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/ Please send me any requests for agenda slots in Oslo. Thanks, Andy ---------- Forwarded message ---------- Date: Fri, 28 May 1999 14:56:11 -0400 From: Marcia Beaulieu To: Andrew G. Malis Cc: Thomas Narten , Erik Nordmark Subject: 45th IETF-OSLO, NORWAY: FRNETMIB FRNETMIB is tentatively scheduled as follows: Tuesday, July 13 at 1700-1800 other groups scheduled at that time: nat, policy Please submit an agenda for this meeting as soon as possible to agenda@ietf.org The deadline for submitting an agenda is July 1 at 1200 ET. Thanks, Marcia X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message.