From owner-frnetmib@sunroof.Eng.Sun.COM  Mon Feb  1 12:02:51 1999
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.8.5/8.8.7a) with SMTP id MAA24270
	for <frnetmib-archive@lists.ietf.org>; Mon, 1 Feb 1999 12:02:49 -0500 (EST)
Received: from Eng.Sun.COM (engmail2 [129.146.1.25]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id IAA19270; Mon, 1 Feb 1999 08:55:32 -0800
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with ESMTP id IAA12508;
	Mon, 1 Feb 1999 08:55:30 -0800
Received: by sunroof.eng.sun.com (8.9.3.Beta0+Sun/8.9.3.Beta0) id IAA08188
	for frnetmib-dist; Mon, 1 Feb 1999 08:55:19 -0800 (PST)
Received: from Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.9.3.Beta0+Sun/8.9.3.Beta0) with SMTP id IAA08175
	for <frnetmib@sunroof>; Mon, 1 Feb 1999 08:55:10 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id IAA20698
	for <frnetmib@sunroof.Eng.Sun.COM>; Mon, 1 Feb 1999 08:55:10 -0800
Received: from mail.visualnetworks.com ([208.22.72.43])
	by earth.sun.com (8.9.1/8.9.1) with SMTP id IAA13578
	for <frnetmib@sunroof.Eng.Sun.COM>; Mon, 1 Feb 1999 08:55:08 -0800 (PST)
Received: from shemp by mail.visualnetworks.com
          via smtpd (for earth.Sun.COM [192.9.25.3]) with SMTP; 1 Feb 1999 17:00:16 UT
Received: by shemp.visualnetworks.com with Internet Mail Service (5.0.1458.49)
	id <D957PMP0>; Mon, 1 Feb 1999 12:04:13 -0500
Message-ID: <0F9AE864A5ECD011B3100060977F354AD57B61@shemp.visualnetworks.com>
From: "Rehbehn, Kenneth" <Krehbehn@VisualNetworks.com>
To: frnetmib@sunroof.Eng.Sun.COM
Subject: (FRNETMIB) File Comparison for FRS MIB changes from ver 02 to 03
Date: Mon, 1 Feb 1999 12:04:11 -0500
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1458.49)
Content-Type: text/plain
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/

Andy is planning a last call on the Frame Relay Service MIB on Feb 5.
To aid in your review of the draft, I have created a file comparison
between draft-ietf-frnetmib-frs-mib-02.txt and
draft-ietf-frnetmib-frs-mib-03.txt.  It is Word output packaged in a PDF
file.  Download from:

ftp://ftp.visualnetworks.com/Pub/IETF/draft-ietf-frnetmib-frs-mib-03-dif
f.pdf

Enjoy!
Ken

---------------------------------------------------------------
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


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 Feb  5 11:35:20 1999
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.8.5/8.8.7a) with SMTP id LAA04074
	for <frnetmib-archive@lists.ietf.org>; Fri, 5 Feb 1999 11:35:20 -0500 (EST)
Received: from Eng.Sun.COM (engmail1 [129.146.1.13]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id IAA18686; Fri, 5 Feb 1999 08:28:26 -0800
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with ESMTP id IAA02052;
	Fri, 5 Feb 1999 08:28:22 -0800
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id IAA12585
	for frnetmib-dist; Fri, 5 Feb 1999 08:28:07 -0800 (PST)
Received: from Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id IAA12578
	for <frnetmib@sunroof>; Fri, 5 Feb 1999 08:27:58 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id IAA01999
	for <frnetmib@sunroof.eng.sun.com>; Fri, 5 Feb 1999 08:27:57 -0800
Received: from alpo.casc.com (alpo.casc.com [152.148.10.6])
	by earth.sun.com (8.9.1/8.9.1) with ESMTP id IAA17416
	for <frnetmib@sunroof.eng.sun.com>; Fri, 5 Feb 1999 08:27:56 -0800 (PST)
Received: from spice.casc.com (spice [152.148.12.52])
	by alpo.casc.com (8.9.1a/8.9.1) with ESMTP id LAA15776;
	Fri, 5 Feb 1999 11:25:19 -0500 (EST)
Received: from localhost by spice.casc.com (8.8.8+Sun/SMI-SVR4)
	id LAA01962; Fri, 5 Feb 1999 11:25:18 -0500 (EST)
Date: Fri, 5 Feb 1999 11:25:18 -0500 (EST)
From: "Andrew G. Malis" <amalis@casc.com>
X-Sender: amalis@spice
To: frnetmib@sunroof.Eng.Sun.COM, Thomas Narten <narten@raleigh.ibm.com>,
        Jeffrey Burgan <burgan@home.net>, scoya@ietf.org
cc: "Andrew G. Malis" <malis@casc.com>
Subject: (FRNETMIB) Ending one WG last call and beginning another
Message-ID: <Pine.SO4.4.04.9902051116280.1930-100000@spice>
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/

This completes working group last call on
draft-ietf-frnetmib-spvc-02.txt, with no comments received.  This is
being submitted to the IESG to be published as a Proposed Standard RFC.

This message also begins working group last call on
draft-ieft-frnetmib-frs-mib-03.txt.  Ken Rehbehn, earlier this week,
posted a diff file between version -02 and -03.  To refresh your
memories, the diff file is at:

ftp://ftp.visualnetworks.com/Pub/IETF/draft-ietf-frnetmib-frs-mib-03-diff.pdf

This last call concludes in two weeks, on February 19. Please review
and send comments to the list.

Thanks,
Andy
________________________________________________________________________
Andrew G. Malis  malis@ascend.com  phone:978 952-7414   fax:978 392-2074
Ascend Communications, Inc.        1 Robbins Road     Westford, MA 01886

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 Feb  5 18:56:35 1999
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.8.5/8.8.7a) with SMTP id SAA13660
	for <frnetmib-archive@lists.ietf.org>; Fri, 5 Feb 1999 18:56:34 -0500 (EST)
Received: from Eng.Sun.COM (engmail3 [129.144.170.5]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id PAA09264; Fri, 5 Feb 1999 15:50:02 -0800
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with ESMTP id PAA13127;
	Fri, 5 Feb 1999 15:49:58 -0800
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id PAA13078
	for frnetmib-dist; Fri, 5 Feb 1999 15:49:15 -0800 (PST)
Received: from Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id PAA13068
	for <frnetmib@sunroof>; Fri, 5 Feb 1999 15:49:08 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id PAA16356
	for <frnetmib@sunroof.eng.sun.com>; Fri, 5 Feb 1999 15:49:05 -0800
Received: from nsi_mtl_nt.nsicomm.com ([207.139.134.90])
	by earth.sun.com (8.9.1/8.9.1) with ESMTP id PAA22419
	for <frnetmib@sunroof.eng.sun.com>; Fri, 5 Feb 1999 15:49:05 -0800 (PST)
Received: from zyu ([207.139.134.105]) by nsi_mtl_nt.nsicomm.com
          (Netscape Messaging Server 3.5)  with SMTP id 300;
          Fri, 5 Feb 1999 18:46:04 -0500
Reply-To: "Zhongde Yu" <zyu@nsicomm.com>
From: "Zhongde Yu" <zyu@nsicomm.com>
To: <frnetmib@sunroof.Eng.Sun.COM>
Cc: <amalis@casc.com>, <malis@ascend.com>, <Krehbehn@VisualNetworks.com>,
        <davef@newbridge.com>
Subject: (FRNETMIB) Comments on Internet Draft (draft-ietf-frnetmib-frs-mib-03.txt)
Date: Fri, 5 Feb 1999 18:49:30 -0500
Message-ID: <01be5162$2c882f80$69868bcf@zyu.nsicomm.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0065_01BE5138.43B22780"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.71.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3
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/

This is a multi-part message in MIME format.

------=_NextPart_000_0065_01BE5138.43B22780
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Dear Sir/Madam:

Attached please find our comments on the Internet Draft
(draft-ietf-frnetmib-frs-mib-03.txt)
regarding the possibility of adding PVC priority objects to frame relay MIB.

Regards,

Zhongde Yu
NSI Communications, Inc.

----------------------------------------------------------------------------
---------------------
PS: Thanks a lot for the following replies from Mr. Kenneth Rehbehn and
Mr. Andrew G. Malis.


No suggestions have been made to add a priority object.  Given the
consideration of the Frame Transfer Priority capability in Study Group
7, there very well may be support for adding it.
The draft is starting Working Group last call.  I am not sure how much
change is allowed at that stage.

Ken


As Ken noted, the draft is in an advanced state of development, and the
ease of adding any new objects such as you mentioned above would depend
on whether or not you already had concrete objects you wished to
propose, and how long this would delay the work.  The MIB just entered
working group last call, which is the final two-week period for
technical comments.  It is usually meant to correct errors in the MIB,
but new objects could be considered if the working group agreed.  I
will go ahead and add you to the list, and re-send the last call
announcement to you.  You should send your comments, as detailed as
possible, to the working group's email list
(frnetmib@sunroof.eng.sun.com).
Regards,

Andy
FRNETMIB working group chair


------=_NextPart_000_0065_01BE5138.43B22780
Content-Type: text/plain;
	name="comments_on_ draft-ietf-frnetmib-frs-mib-03.txt"
Content-Disposition: attachment;
	filename="comments_on_ draft-ietf-frnetmib-frs-mib-03.txt"
Content-Transfer-Encoding: quoted-printable

Comments on Internet Draft (draft-ietf-frnetmib-frs-mib-03.txt)

(Note: The comments are typed bewteen double ********************* =
lines.)



-- The Frame Relay Service Logical Port Group
--  the Frame Relay Logical Port Group

          frLportTable OBJECT-TYPE
              SYNTAX  SEQUENCE OF FrLportEntry
              MAX-ACCESS  not-accessible
              STATUS  current
              DESCRIPTION
                      "The Frame Relay Logical Port Information table."
              ::=3D { frnetservObjects 1 }

          frLportEntry OBJECT-TYPE
              SYNTAX  FrLportEntry
              MAX-ACCESS  not-accessible
              STATUS  current
              DESCRIPTION
                      "An entry in the Frame Relay Logical Port
                      Information table."
              INDEX   { ifIndex }
              ::=3D { frLportTable 1 }

          FrLportEntry ::=3D
              SEQUENCE {
                  frLportNumPlan            INTEGER,
                  frLportContact            DisplayString,
                  frLportLocation           DisplayString,
                  frLportType               INTEGER,
                  frLportAddrDLCILen        INTEGER,
                  frLportVCSigProtocol      INTEGER,
                  frLportVCSigPointer       OBJECT IDENTIFIER,
                  frLportDLCIIndexValue     Integer32,
                  frLportTypeRW             INTEGER,
                  frLportVCSigProtocolRW    INTEGER,
                  frLportVCSigPointerRW     OBJECT IDENTIFIER,
                  frLportFragControl        INTEGER,
                  frLportFragSize           Integer32,
	-- ***********************************************************
  		  frLportNumPriority	    INTEGER
	-- ***********************************************************
          }

	-- ***********************************************************=20
	    frLportNumPriority OBJECT-TYPE
              SYNTAX  INTEGER (1..8)
              MAX-ACCESS  read-only
              STATUS  current
              DESCRIPTION
                      "The value of this object is the number of=20
		      priority assigned to each logical port. It is
		      a read-only object with a default value of 1."
              DEFVAL { 1 }
              ::=3D { frLportEntry 14 }
	-- ***********************************************************=20



-- The PVC End-Point Group
-- The Frame Relay PVC End-point Table

          frPVCEndptTable OBJECT-TYPE
              SYNTAX  SEQUENCE OF FrPVCEndptEntry
              MAX-ACCESS  not-accessible
              STATUS  current
              DESCRIPTION
                      "The Frame Relay PVC End-Point table.  This table
                      is used to model a PVC end-point.  This table
                      contains the traffic parameters and statistics for
                      a PVC end-point."
              ::=3D { frnetservObjects 3 }

          frPVCEndptEntry OBJECT-TYPE
              SYNTAX  FrPVCEndptEntry
              MAX-ACCESS  not-accessible
              STATUS  current
              DESCRIPTION
                      "An entry in the Frame Relay PVC Endpoint table."
              INDEX   { ifIndex, frPVCEndptDLCIIndex }
              ::=3D { frPVCEndptTable 1 }

          FrPVCEndptEntry ::=3D
              SEQUENCE {
                  frPVCEndptDLCIIndex            Integer32,
                  frPVCEndptInMaxFrameSize       Integer32,
                  frPVCEndptInBc                 Integer32,
                  frPVCEndptInBe                 Integer32,
                  frPVCEndptInCIR                Integer32,
                  frPVCEndptOutMaxFrameSize      Integer32,
                  frPVCEndptOutBc                Integer32,
                  frPVCEndptOutBe                Integer32,
                  frPVCEndptOutCIR               Integer32,
		  frPVCEndptConnectIdentifier    Integer32,
                  frPVCEndptRowStatus            RowStatus,
                  frPVCEndptRcvdSigStatus        INTEGER,
                  frPVCEndptInFrames             Counter32,
                  frPVCEndptOutFrames            Counter32,
                  frPVCEndptInDEFrames           Counter32,
                  frPVCEndptInExcessFrames       Counter32,
                  frPVCEndptOutExcessFrames      Counter32,
                  frPVCEndptInDiscards           Counter32,
                  frPVCEndptInOctets             Counter32,
                  frPVCEndptOutOctets            Counter32,
                  frPVCEndptInDiscardsDESet      Counter32,
                  frPVCEndptInFramesFECNSet      Counter32,
                  frPVCEndptOutFramesFECNSet     Counter32,
                  frPVCEndptInFramesBECNSet      Counter32,
                  frPVCEndptOutFramesBECNSet     Counter32,
                  frPVCEndptInCongDiscards       Counter32,
                  frPVCEndptInDECongDiscards     Counter32,
                  frPVCEndptOutCongDiscards      Counter32,
                  frPVCEndptOutDECongDiscards    Counter32,
                  frPVCEndptOutDEFrames          Counter32,
	-- ***********************************************************=20
  		  frPVCEndptOutPriority		 INTEGER
	-- ***********************************************************=20
              }

	-- *********************************************************** 	=20
	    frPVCEndptOutPriority OBJECT-TYPE

              SYNTAX  INTEGER (1.. frLportNumPriority)
              MAX-ACCESS  read-write
              STATUS  current
              DESCRIPTION
                      "The priority assigned to each PVC End Point in
		      the egress direction. It=92s a read-write object.
		      Its range is from 1 to frLportNumPriority with=20
		      a default value of 1. There is no corresponding
		      object in the ingress direction as the inbound=20
		      frames are switched in the FCFS order."
		  DEFVAL { 1 }
              ::=3D { frPVCEndptEntry 31 }
	-- ***********************************************************=20












------=_NextPart_000_0065_01BE5138.43B22780--

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  Mon Feb  8 12:15:47 1999
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.8.5/8.8.7a) with SMTP id MAA23377
	for <frnetmib-archive@lists.ietf.org>; Mon, 8 Feb 1999 12:15:46 -0500 (EST)
Received: from Eng.Sun.COM (engmail2 [129.146.1.25]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id JAA03957; Mon, 8 Feb 1999 09:06:52 -0800
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with ESMTP id JAA26315;
	Mon, 8 Feb 1999 09:06:48 -0800
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id JAA14282
	for frnetmib-dist; Mon, 8 Feb 1999 09:06:33 -0800 (PST)
Received: from Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id JAA14275
	for <frnetmib@sunroof>; Mon, 8 Feb 1999 09:06:28 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id JAA24526
	for <frnetmib@sunroof.eng.sun.com>; Mon, 8 Feb 1999 09:06:27 -0800
Received: from mail.visualnetworks.com ([208.22.72.43])
	by earth.sun.com (8.9.1/8.9.1) with SMTP id JAA25538
	for <frnetmib@sunroof.eng.sun.com>; Mon, 8 Feb 1999 09:06:24 -0800 (PST)
Received: from shemp by mail.visualnetworks.com
          via smtpd (for earth.Sun.COM [192.9.25.3]) with SMTP; 8 Feb 1999 17:11:31 UT
Received: by shemp.visualnetworks.com with Internet Mail Service (5.0.1458.49)
	id <D957PYP6>; Mon, 8 Feb 1999 12:15:52 -0500
Message-ID: <0F9AE864A5ECD011B3100060977F354AD57B95@shemp.visualnetworks.com>
From: "Rehbehn, Kenneth" <Krehbehn@VisualNetworks.com>
To: "'frnetmib@sunroof.eng.sun.com'" <frnetmib@sunroof.Eng.Sun.COM>
Cc: "'Zhongde Yu'" <zyu@nsicomm.com>
Subject: (FRNETMIB) Adding a Priority Object to (draft-ietf-frnetmib-frs-mib-03.txt
Date: Mon, 8 Feb 1999 12:15:52 -0500
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1458.49)
Content-Type: text/plain;
	charset="ISO-8859-1"
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 was a bit surprised by the proposal.  It is targeted at the port and
not the connection!  I was expecting an entry in the frPVCEndptTable to
associate a priority with a particular PVC.

Assuming that we change the object to fit into the PVC End-point Table,
we need to consider some issues.

Many implementations provide for priority using proprietary mechanisms.
The priority range may be more than 1 to 8 (I think I have heard of one
implementation supporting 24 levels of priority).  

A second issue is that priority may be asymmetric (low in one direction
and high in the other).  As an example, the proposed X.36 Frame Transfer
Priority specifies two priority fields in a new signaling information
element:  "Outgoing transfer priority index" and "Incoming transfer
priority index".  The possible priority range is 0 to 15.  The X.36
Frame Transfer Priority IE is not in the standard yet and could change,
though that is unlikely.

If we want to add priority support at this time, I suggest we follow the
ITU-T work and model the priority object as an abstract indication of
priority. Each implementation can take the MIB setting for priority (say
15 for high) and map the index into an internal implementation value for
priority.  Here is my cut at the objects:

          frPVCEndptInPriorityIndex OBJECT-TYPE
              SYNTAX  Unsigned32(0..15)
              MAX-ACCESS  read-create
              STATUS  current
              DESCRIPTION
                   "The transfer priority index value for frames
received
                    by the network (ingress).
                    
                    The transfer priority index identifies a level of
                    service where PVCs provisioned with higher values
                    receive better frame relay service than PVCs
                    provisioned with lower values. The characteristics
                    of the priority index values are implementation
                    specific and not standardized. The value serves as
                    an index from 0 (low) to 15 (high) into the
                    implementation-specific priority levels.
                    Implementations MUST support all 16 index values.

                    If a request is made using a transfer priority
                    index value that cannot be supported by the
                    network due to resource constraints, the request
                    will fail with badValue"
              DEFVAL {0}
              ::= { frPVCEndptEntry xxx }

          frPVCEndptOutPriorityIndex OBJECT-TYPE
              SYNTAX  Unsigned32(0..15)
              MAX-ACCESS  read-create
              STATUS  current
              DESCRIPTION
                   "The transfer priority index value for frames sent
                    by the network (egress).
                    
                    Refer to frPVCEndptInPriorityIndex object for a
                    description of the transfer priority index."
              DEFVAL {0}
              ::= { frPVCEndptEntry xxx }
    
Do we want to add such objects at this time?  Do we really understand
all the issues with having priority go into the MIB during Working Group
Last Call?

Ken

---------------------------------------------------------------
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





> -----Original Message-----
> From: Zhongde Yu [mailto:zyu@nsicomm.com]
> Sent: Friday, February 05, 1999 6:50 PM
> To: frnetmib@sunroof.Eng.Sun.COM
> Cc: amalis@casc.com; malis@ascend.com; Krehbehn@VisualNetworks.com;
> davef@newbridge.com
> Subject: (FRNETMIB) Comments on Internet Draft
> (draft-ietf-frnetmib-frs-mib-03.txt)
> 
> 
> Dear Sir/Madam:
> 
> Attached please find our comments on the Internet Draft
> (draft-ietf-frnetmib-frs-mib-03.txt)
> regarding the possibility of adding PVC priority objects to 
> frame relay MIB.
> 
> Regards,
> 
> Zhongde Yu
> NSI Communications, Inc.
> 
> --------------------------------------------------------------
> --------------
> ---------------------
> PS: Thanks a lot for the following replies from Mr. Kenneth 
> Rehbehn and
> Mr. Andrew G. Malis.
> 
> 
> No suggestions have been made to add a priority object.  Given the
> consideration of the Frame Transfer Priority capability in Study Group
> 7, there very well may be support for adding it.
> The draft is starting Working Group last call.  I am not sure how much
> change is allowed at that stage.
> 
> Ken
> 
> 
> As Ken noted, the draft is in an advanced state of 
> development, and the
> ease of adding any new objects such as you mentioned above 
> would depend
> on whether or not you already had concrete objects you wished to
> propose, and how long this would delay the work.  The MIB just entered
> working group last call, which is the final two-week period for
> technical comments.  It is usually meant to correct errors in the MIB,
> but new objects could be considered if the working group agreed.  I
> will go ahead and add you to the list, and re-send the last call
> announcement to you.  You should send your comments, as detailed as
> possible, to the working group's email list
> (frnetmib@sunroof.eng.sun.com).
> Regards,
> 
> Andy
> FRNETMIB working group chair
> 
> 
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  Mon Feb  8 12:54:49 1999
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.8.5/8.8.7a) with SMTP id MAA24937
	for <frnetmib-archive@lists.ietf.org>; Mon, 8 Feb 1999 12:54:48 -0500 (EST)
Received: from Eng.Sun.COM (engmail1 [129.146.1.13]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id JAA22027; Mon, 8 Feb 1999 09:48:14 -0800
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with ESMTP id JAA11958;
	Mon, 8 Feb 1999 09:48:10 -0800
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id JAA14331
	for frnetmib-dist; Mon, 8 Feb 1999 09:47:36 -0800 (PST)
Received: from Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id JAA14324
	for <frnetmib@sunroof>; Mon, 8 Feb 1999 09:47:30 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id JAA02272
	for <frnetmib@sunroof.Eng.Sun.COM>; Mon, 8 Feb 1999 09:47:29 -0800
Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67])
	by earth.sun.com (8.9.1/8.9.1) with ESMTP id JAA26077
	for <frnetmib@sunroof.Eng.Sun.COM>; Mon, 8 Feb 1999 09:47:28 -0800 (PST)
Received: (from smtpd@localhost) by ns.newbridge.com (8.8.8/8.6.12) id MAA08040 for frnetmib@sunroof.Eng.Sun.COM; Mon, 8 Feb 1999 12:47:22 -0500 (EST)
Received: from kanata-gw1.newbridge.com(192.75.23.72), claiming to be "kanata-gw1.ca.newbridge.com"
 via SMTP by ns.newbridge.com, id smtpdZAAa07134; Mon Feb  8 12:47:16 1999
Received: from popmail.ca.newbridge.com by kanata-mh1.ca.newbridge.com with ESMTP; Mon, 8 Feb 1999 12:47:15 -0500
Received: from newbridge.com (macdavef.ca.newbridge.com [138.120.55.103])
	by popmail.ca.newbridge.com. (8.8.8+Sun/8.8.8) with ESMTP id MAA09631;
	Mon, 8 Feb 1999 12:47:14 -0500 (EST)
Message-Id: <36BF2319.12CEE427@newbridge.com>
Date: Mon, 08 Feb 1999 12:47:31 -0500
From: David Fowler <davef@newbridge.com>
X-Mailer: Mozilla 4.5 (Macintosh; U; PPC)
X-Accept-Language: en
MIME-Version: 1.0
To: "Rehbehn, Kenneth" <Krehbehn@VisualNetworks.com>
CC: "'frnetmib@sunroof.eng.sun.com'" <frnetmib@sunroof.Eng.Sun.COM>,
        "'Zhongde Yu'" <zyu@nsicomm.com>
Subject: Re: (FRNETMIB) Adding a Priority Object to (draft-ietf-frnetmib-frs-mib-03.txt
References: <0F9AE864A5ECD011B3100060977F354AD57B95@shemp.visualnetworks.com>
Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353"
Content-Transfer-Encoding: 7bit
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/

There are 2 types of priority that can be applied to a connection.  One is
the type of priority that Ken described below.  But, in addition, there is
a priority for the connection itself within the network.  This could be
used as follows:

When the PVC is being provisioned in the network, the priority can be used
to indicate how important the PVC is compared to other PVCs in the
network.  If there is insufficient bandwidth in the network to set up a
connection then A PVC with higher priority could, in some implementations,
supplant a PVC of lower priority in order to make room for itself.

In any case, I feel this object warrants to much discussion at this date
and I suggest that it is tabled for the next round.

David

"Rehbehn, Kenneth" wrote:

> I was a bit surprised by the proposal.  It is targeted at the port and
> not the connection!  I was expecting an entry in the frPVCEndptTable to
> associate a priority with a particular PVC.
>
> Assuming that we change the object to fit into the PVC End-point Table,
> we need to consider some issues.
>
> Many implementations provide for priority using proprietary mechanisms.
> The priority range may be more than 1 to 8 (I think I have heard of one
> implementation supporting 24 levels of priority).
>
> A second issue is that priority may be asymmetric (low in one direction
> and high in the other).  As an example, the proposed X.36 Frame Transfer
> Priority specifies two priority fields in a new signaling information
> element:  "Outgoing transfer priority index" and "Incoming transfer
> priority index".  The possible priority range is 0 to 15.  The X.36
> Frame Transfer Priority IE is not in the standard yet and could change,
> though that is unlikely.
>
> If we want to add priority support at this time, I suggest we follow the
> ITU-T work and model the priority object as an abstract indication of
> priority. Each implementation can take the MIB setting for priority (say
> 15 for high) and map the index into an internal implementation value for
> priority.  Here is my cut at the objects:
>
>           frPVCEndptInPriorityIndex OBJECT-TYPE
>               SYNTAX  Unsigned32(0..15)
>               MAX-ACCESS  read-create
>               STATUS  current
>               DESCRIPTION
>                    "The transfer priority index value for frames
> received
>                     by the network (ingress).
>
>                     The transfer priority index identifies a level of
>                     service where PVCs provisioned with higher values
>                     receive better frame relay service than PVCs
>                     provisioned with lower values. The characteristics
>                     of the priority index values are implementation
>                     specific and not standardized. The value serves as
>                     an index from 0 (low) to 15 (high) into the
>                     implementation-specific priority levels.
>                     Implementations MUST support all 16 index values.
>
>                     If a request is made using a transfer priority
>                     index value that cannot be supported by the
>                     network due to resource constraints, the request
>                     will fail with badValue"
>               DEFVAL {0}
>               ::= { frPVCEndptEntry xxx }
>
>           frPVCEndptOutPriorityIndex OBJECT-TYPE
>               SYNTAX  Unsigned32(0..15)
>               MAX-ACCESS  read-create
>               STATUS  current
>               DESCRIPTION
>                    "The transfer priority index value for frames sent
>                     by the network (egress).
>
>                     Refer to frPVCEndptInPriorityIndex object for a
>                     description of the transfer priority index."
>               DEFVAL {0}
>               ::= { frPVCEndptEntry xxx }
>
> Do we want to add such objects at this time?  Do we really understand
> all the issues with having priority go into the MIB during Working Group
> Last Call?
>
> Ken
>
> ---------------------------------------------------------------
> 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
>
> > -----Original Message-----
> > From: Zhongde Yu [mailto:zyu@nsicomm.com]
> > Sent: Friday, February 05, 1999 6:50 PM
> > To: frnetmib@sunroof.Eng.Sun.COM
> > Cc: amalis@casc.com; malis@ascend.com; Krehbehn@VisualNetworks.com;
> > davef@newbridge.com
> > Subject: (FRNETMIB) Comments on Internet Draft
> > (draft-ietf-frnetmib-frs-mib-03.txt)
> >
> >
> > Dear Sir/Madam:
> >
> > Attached please find our comments on the Internet Draft
> > (draft-ietf-frnetmib-frs-mib-03.txt)
> > regarding the possibility of adding PVC priority objects to
> > frame relay MIB.
> >
> > Regards,
> >
> > Zhongde Yu
> > NSI Communications, Inc.
> >
> > --------------------------------------------------------------
> > --------------
> > ---------------------
> > PS: Thanks a lot for the following replies from Mr. Kenneth
> > Rehbehn and
> > Mr. Andrew G. Malis.
> >
> >
> > No suggestions have been made to add a priority object.  Given the
> > consideration of the Frame Transfer Priority capability in Study Group
> > 7, there very well may be support for adding it.
> > The draft is starting Working Group last call.  I am not sure how much
> > change is allowed at that stage.
> >
> > Ken
> >
> >
> > As Ken noted, the draft is in an advanced state of
> > development, and the
> > ease of adding any new objects such as you mentioned above
> > would depend
> > on whether or not you already had concrete objects you wished to
> > propose, and how long this would delay the work.  The MIB just entered
> > working group last call, which is the final two-week period for
> > technical comments.  It is usually meant to correct errors in the MIB,
> > but new objects could be considered if the working group agreed.  I
> > will go ahead and add you to the list, and re-send the last call
> > announcement to you.  You should send your comments, as detailed as
> > possible, to the working group's email list
> > (frnetmib@sunroof.eng.sun.com).
> > Regards,
> >
> > Andy
> > FRNETMIB working group chair
> >
> >
> X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with
> X-Info: 'unsubscribe frnetmib' in the body of the 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  Mon Feb  8 14:05:31 1999
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.8.5/8.8.7a) with SMTP id OAA27009
	for <frnetmib-archive@lists.ietf.org>; Mon, 8 Feb 1999 14:05:31 -0500 (EST)
Received: from Eng.Sun.COM (engmail2 [129.146.1.25]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id KAA23153; Mon, 8 Feb 1999 10:59:25 -0800
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with ESMTP id KAA21473;
	Mon, 8 Feb 1999 10:59:18 -0800
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id KAA14404
	for frnetmib-dist; Mon, 8 Feb 1999 10:58:46 -0800 (PST)
Received: from Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id KAA14397
	for <frnetmib@sunroof>; Mon, 8 Feb 1999 10:58:41 -0800 (PST)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id KAA21283
	for <frnetmib@sunroof.Eng.Sun.COM>; Mon, 8 Feb 1999 10:58:34 -0800
Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67])
	by saturn.sun.com (8.9.1/8.9.1) with ESMTP id KAA02051
	for <frnetmib@sunroof.Eng.Sun.COM>; Mon, 8 Feb 1999 10:58:34 -0800 (PST)
Received: (from smtpd@localhost) by ns.newbridge.com (8.8.8/8.6.12) id NAA22737 for frnetmib@sunroof.Eng.Sun.COM; Mon, 8 Feb 1999 13:57:17 -0500 (EST)
Received: from kanata-gw1.newbridge.com(192.75.23.72), claiming to be "kanata-gw1.ca.newbridge.com"
 via SMTP by ns.newbridge.com, id smtpdYAAa21366; Mon Feb  8 13:57:09 1999
Received: from popmail.ca.newbridge.com by kanata-mh1.ca.newbridge.com with ESMTP; Mon, 8 Feb 1999 13:57:07 -0500
Received: from newbridge.com (macdavef.ca.newbridge.com [138.120.55.103])
	by popmail.ca.newbridge.com. (8.8.8+Sun/8.8.8) with ESMTP id NAA12770;
	Mon, 8 Feb 1999 13:57:06 -0500 (EST)
Message-Id: <36BF3371.3FFED41A@newbridge.com>
Date: Mon, 08 Feb 1999 13:57:22 -0500
From: David Fowler <davef@newbridge.com>
X-Mailer: Mozilla 4.5 (Macintosh; U; PPC)
X-Accept-Language: en
MIME-Version: 1.0
To: "Rehbehn, Kenneth" <Krehbehn@VisualNetworks.com>,
        "'frnetmib@sunroof.eng.sun.com'" <frnetmib@sunroof.Eng.Sun.COM>,
        "'Zhongde Yu'" <zyu@nsicomm.com>
Subject: Re: (FRNETMIB) Adding a Priority Object to (draft-ietf-frnetmib-frs-mib-03.txt
References: <0F9AE864A5ECD011B3100060977F354AD57B95@shemp.visualnetworks.com> <36BF2319.12CEE427@newbridge.com>
Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353"
Content-Transfer-Encoding: 7bit
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/

Someone reminded me that the word tabled is ambiguous (Thanks, Randy).

What I meant is we should put forward the current I-D without adding a
priority object and discuss a priority object if/when the WG re-activates.

Regards,
David

David Fowler wrote:

> There are 2 types of priority that can be applied to a connection.  One is
> the type of priority that Ken described below.  But, in addition, there is
> a priority for the connection itself within the network.  This could be
> used as follows:
>
> When the PVC is being provisioned in the network, the priority can be used
> to indicate how important the PVC is compared to other PVCs in the
> network.  If there is insufficient bandwidth in the network to set up a
> connection then A PVC with higher priority could, in some implementations,
> supplant a PVC of lower priority in order to make room for itself.
>
> In any case, I feel this object warrants to much discussion at this date
> and I suggest that it is tabled for the next round.
>
> David
>
> "Rehbehn, Kenneth" wrote:
>
> > I was a bit surprised by the proposal.  It is targeted at the port and
> > not the connection!  I was expecting an entry in the frPVCEndptTable to
> > associate a priority with a particular PVC.
> >
> > Assuming that we change the object to fit into the PVC End-point Table,
> > we need to consider some issues.
> >
> > Many implementations provide for priority using proprietary mechanisms.
> > The priority range may be more than 1 to 8 (I think I have heard of one
> > implementation supporting 24 levels of priority).
> >
> > A second issue is that priority may be asymmetric (low in one direction
> > and high in the other).  As an example, the proposed X.36 Frame Transfer
> > Priority specifies two priority fields in a new signaling information
> > element:  "Outgoing transfer priority index" and "Incoming transfer
> > priority index".  The possible priority range is 0 to 15.  The X.36
> > Frame Transfer Priority IE is not in the standard yet and could change,
> > though that is unlikely.
> >
> > If we want to add priority support at this time, I suggest we follow the
> > ITU-T work and model the priority object as an abstract indication of
> > priority. Each implementation can take the MIB setting for priority (say
> > 15 for high) and map the index into an internal implementation value for
> > priority.  Here is my cut at the objects:
> >
> >           frPVCEndptInPriorityIndex OBJECT-TYPE
> >               SYNTAX  Unsigned32(0..15)
> >               MAX-ACCESS  read-create
> >               STATUS  current
> >               DESCRIPTION
> >                    "The transfer priority index value for frames
> > received
> >                     by the network (ingress).
> >
> >                     The transfer priority index identifies a level of
> >                     service where PVCs provisioned with higher values
> >                     receive better frame relay service than PVCs
> >                     provisioned with lower values. The characteristics
> >                     of the priority index values are implementation
> >                     specific and not standardized. The value serves as
> >                     an index from 0 (low) to 15 (high) into the
> >                     implementation-specific priority levels.
> >                     Implementations MUST support all 16 index values.
> >
> >                     If a request is made using a transfer priority
> >                     index value that cannot be supported by the
> >                     network due to resource constraints, the request
> >                     will fail with badValue"
> >               DEFVAL {0}
> >               ::= { frPVCEndptEntry xxx }
> >
> >           frPVCEndptOutPriorityIndex OBJECT-TYPE
> >               SYNTAX  Unsigned32(0..15)
> >               MAX-ACCESS  read-create
> >               STATUS  current
> >               DESCRIPTION
> >                    "The transfer priority index value for frames sent
> >                     by the network (egress).
> >
> >                     Refer to frPVCEndptInPriorityIndex object for a
> >                     description of the transfer priority index."
> >               DEFVAL {0}
> >               ::= { frPVCEndptEntry xxx }
> >
> > Do we want to add such objects at this time?  Do we really understand
> > all the issues with having priority go into the MIB during Working Group
> > Last Call?
> >
> > Ken
> >
> > ---------------------------------------------------------------
> > 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
> >
> > > -----Original Message-----
> > > From: Zhongde Yu [mailto:zyu@nsicomm.com]
> > > Sent: Friday, February 05, 1999 6:50 PM
> > > To: frnetmib@sunroof.Eng.Sun.COM
> > > Cc: amalis@casc.com; malis@ascend.com; Krehbehn@VisualNetworks.com;
> > > davef@newbridge.com
> > > Subject: (FRNETMIB) Comments on Internet Draft
> > > (draft-ietf-frnetmib-frs-mib-03.txt)
> > >
> > >
> > > Dear Sir/Madam:
> > >
> > > Attached please find our comments on the Internet Draft
> > > (draft-ietf-frnetmib-frs-mib-03.txt)
> > > regarding the possibility of adding PVC priority objects to
> > > frame relay MIB.
> > >
> > > Regards,
> > >
> > > Zhongde Yu
> > > NSI Communications, Inc.
> > >
> > > --------------------------------------------------------------
> > > --------------
> > > ---------------------
> > > PS: Thanks a lot for the following replies from Mr. Kenneth
> > > Rehbehn and
> > > Mr. Andrew G. Malis.
> > >
> > >
> > > No suggestions have been made to add a priority object.  Given the
> > > consideration of the Frame Transfer Priority capability in Study Group
> > > 7, there very well may be support for adding it.
> > > The draft is starting Working Group last call.  I am not sure how much
> > > change is allowed at that stage.
> > >
> > > Ken
> > >
> > >
> > > As Ken noted, the draft is in an advanced state of
> > > development, and the
> > > ease of adding any new objects such as you mentioned above
> > > would depend
> > > on whether or not you already had concrete objects you wished to
> > > propose, and how long this would delay the work.  The MIB just entered
> > > working group last call, which is the final two-week period for
> > > technical comments.  It is usually meant to correct errors in the MIB,
> > > but new objects could be considered if the working group agreed.  I
> > > will go ahead and add you to the list, and re-send the last call
> > > announcement to you.  You should send your comments, as detailed as
> > > possible, to the working group's email list
> > > (frnetmib@sunroof.eng.sun.com).
> > > Regards,
> > >
> > > Andy
> > > FRNETMIB working group chair
> > >
> > >
> > X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with
> > X-Info: 'unsubscribe frnetmib' in the body of the message.
>
> X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with
> X-Info: 'unsubscribe frnetmib' in the body of the 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  Sun Feb 14 14:55:15 1999
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.8.5/8.8.7a) with SMTP id OAA03496
	for <frnetmib-archive@lists.ietf.org>; Sun, 14 Feb 1999 14:55:14 -0500 (EST)
Received: from Eng.Sun.COM (engmail3 [129.144.170.5]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id LAA02802; Sun, 14 Feb 1999 11:48:41 -0800
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with ESMTP id LAA20732;
	Sun, 14 Feb 1999 11:48:36 -0800
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id LAA29166
	for frnetmib-dist; Sun, 14 Feb 1999 11:47:33 -0800 (PST)
Received: from Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id LAA29159
	for <frnetmib@sunroof>; Sun, 14 Feb 1999 11:47:14 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id LAA03415
	for <frnetmib@sunroof.eng.sun.com>; Sun, 14 Feb 1999 11:46:57 -0800
Received: from services.paradyne.com (services.paradyne.com [135.90.253.90])
	by earth.sun.com (8.9.1/8.9.1) with ESMTP id LAA04948
	for <frnetmib@sunroof.eng.sun.com>; Sun, 14 Feb 1999 11:46:53 -0800 (PST)
Received: from hermes.eng.paradyne.com ([135.26.1.14])
          by services.paradyne.com (Netscape Messaging Server 3.6)
           with ESMTP id AAA6F61 for <frnetmib@sunroof.eng.sun.com>;
          Sun, 14 Feb 1999 14:46:51 -0500
Received: from eng.paradyne.com (graysnapper.eng.paradyne.com [135.26.4.35]) by hermes.eng.paradyne.com (8.7.5/8.7.3) with ESMTP id OAA03591 for <frnetmib@sunroof.eng.sun.com>; Sun, 14 Feb 1999 14:46:48 -0500 (EST)
Message-ID: <36C7282A.D64B0313@eng.paradyne.com>
Date: Sun, 14 Feb 1999 14:46:50 -0500
From: Rob Steinberger <ras@eng.paradyne.com>
Organization: Paradyne Corporation
X-Mailer: Mozilla 4.05 [en] (X11; U; SunOS 5.5.1 sun4u)
MIME-Version: 1.0
To: frnetmib@sunroof.Eng.Sun.COM
Subject: (FRNETMIB) Comments on Frame Relay Services MIB
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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 have the following comments concerning the new version of the MIB:

1)   The "Service Level Agreement Counters" (in the Changes from RFC
1604 section) should be renamed "Congestion Counters". This may be a
trivial issue, but Service Level Agreement directs me to FRF.13.  In
that these counters neither fully relate to FRF.13 nor is there a
complete set of Service Level Agreement counters in the MIB, I would
prefer not to even suggest it to the reader.

2) If we are heading down the path of FRF.13 support for Service Level
Agreements, we need more actual Service Level Agreement variables.

2a) On a per end point basis, I think that it would be good to have an
Unavailable Seconds counter and possibly some FDR / DDR counters both
as frames and octets.  It may also be nice to have the aggregate
counters on a per logical port basis.

2b) We are also missing a frame transfer delay object.  Some have
stated that this object can be found elsewhere in the MIBs.  My
feelings are that this object should both relate to Frame Relay and be
generic enough to simply report the delay and not imply any mechanism
used to actually calculate the delay.  This allows the user to utilize
either some ping type mechanism or proprietary mechanism without
having to further extend their MIB view.

2c) We need both frame and octet counts within and/or in excess of
CIR.  Right now, we only have frame counts for the excess frames and
FRF.13 requires both octets and frames.

3) In that we are now controlling fragmentation in this MIB, we now
also need fragmentation counters on a per end point basis.  I think
that we will find the need to know how many fragmentation failures
actually occurred in that a network can appear to run in the normal
range but never get data through due to fragmentation failures. This
information may also suggest the need for the total number of
fragments and the total number of successful reassembles.  A complete
set would include the number of segments, the number of segment
octets, and the number of reassembly errors.  These are important in
that when fragmentation is enabled, the fragment information will feed
the FDR and DDR counters.

Thanks for any comments.

Rob Steinberger
MTS
Paradyne Corporation
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  Mon Feb 15 10:31:39 1999
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.8.5/8.8.7a) with SMTP id KAA19400
	for <frnetmib-archive@lists.ietf.org>; Mon, 15 Feb 1999 10:31:38 -0500 (EST)
Received: from Eng.Sun.COM (engmail1 [129.146.1.13]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id HAA27031; Mon, 15 Feb 1999 07:24:06 -0800
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with ESMTP id HAA16290;
	Mon, 15 Feb 1999 07:23:53 -0800
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id HAA29562
	for frnetmib-dist; Mon, 15 Feb 1999 07:22:46 -0800 (PST)
Received: from Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id HAA29555
	for <frnetmib@sunroof>; Mon, 15 Feb 1999 07:22:39 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id HAA05104
	for <frnetmib@sunroof.Eng.Sun.COM>; Mon, 15 Feb 1999 07:22:36 -0800
Received: from mail.visualnetworks.com ([208.22.72.43])
	by earth.sun.com (8.9.1/8.9.1) with SMTP id HAA00231
	for <frnetmib@sunroof.Eng.Sun.COM>; Mon, 15 Feb 1999 07:22:37 -0800 (PST)
Received: from shemp by mail.visualnetworks.com
          via smtpd (for earth.Sun.COM [192.9.25.3]) with SMTP; 15 Feb 1999 15:28:04 UT
Received: by shemp.visualnetworks.com with Internet Mail Service (5.0.1458.49)
	id <174WLR0P>; Mon, 15 Feb 1999 10:32:49 -0500
Message-ID: <0F9AE864A5ECD011B3100060977F354AD57BB0@shemp.visualnetworks.com>
From: "Rehbehn, Kenneth" <Krehbehn@VisualNetworks.com>
To: "'frnetmib@sunroof.Eng.Sun.COM'" <frnetmib@sunroof.Eng.Sun.COM>
Cc: "'Rob Steinberger'" <ras@eng.paradyne.com>
Subject: RE: (FRNETMIB) Comments on Frame Relay Services MIB
Date: Mon, 15 Feb 1999 10:32:48 -0500
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1458.49)
Content-Type: text/plain;
	charset="ISO-8859-1"
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/

Some good ideas!  My comments below:

> -----Original Message-----
> From: Rob Steinberger [mailto:ras@eng.paradyne.com]
> Sent: Sunday, February 14, 1999 2:47 PM
> To: frnetmib@sunroof.Eng.Sun.COM
> Subject: (FRNETMIB) Comments on Frame Relay Services MIB
> 
> 
> I have the following comments concerning the new version of the MIB:
> 
> 1)   The "Service Level Agreement Counters" (in the Changes from RFC
> 1604 section) should be renamed "Congestion Counters". This may be a
> trivial issue, but Service Level Agreement directs me to FRF.13.  In
> that these counters neither fully relate to FRF.13 nor is there a
> complete set of Service Level Agreement counters in the MIB, I would
> prefer not to even suggest it to the reader.
> 

I think this is an excellent idea.  The objects have generic utility
that goes beyond SLA verification.  Unless there are good arguments to
the contrary, I'll change the comment.


> 2) If we are heading down the path of FRF.13 support for Service Level
> Agreements, we need more actual Service Level Agreement variables.
> 
> 2a) On a per end point basis, I think that it would be good to have an
> Unavailable Seconds counter and possibly some FDR / DDR counters both
> as frames and octets.  It may also be nice to have the aggregate
> counters on a per logical port basis.
> 
> 2b) We are also missing a frame transfer delay object.  Some have
> stated that this object can be found elsewhere in the MIBs.  My
> feelings are that this object should both relate to Frame Relay and be
> generic enough to simply report the delay and not imply any mechanism
> used to actually calculate the delay.  This allows the user to utilize
> either some ping type mechanism or proprietary mechanism without
> having to further extend their MIB view.
> 
> 2c) We need both frame and octet counts within and/or in excess of
> CIR.  Right now, we only have frame counts for the excess frames and
> FRF.13 requires both octets and frames.

Rob is saying that the current MIB objects were not designed with
FRF.13-based Service Level Agreements in mind.  Other than the
congestion discard counts cited above, this is true.  However, the
addition of a number of new objects (and protocol, in the case of some
new delay measure) is probably a working group task that goes beyond
"last call" fixing of I-D problems.  If sufficient interest exists,
let's defer this for a follow-on RFC - perhaps one focused on FR SLA.

> 
> 3) In that we are now controlling fragmentation in this MIB, we now
> also need fragmentation counters on a per end point basis.  I think
> that we will find the need to know how many fragmentation failures
> actually occurred in that a network can appear to run in the normal
> range but never get data through due to fragmentation failures. This
> information may also suggest the need for the total number of
> fragments and the total number of successful reassembles.  A complete
> set would include the number of segments, the number of segment
> octets, and the number of reassembly errors.  These are important in
> that when fragmentation is enabled, the fragment information will feed
> the FDR and DDR counters.

I could see an object to track fragmentation failure events as an aid to
trouble shooting a mis-matched configuration.  I don't see the value in
more granularity (number of segments, number of segment octets, total
number of fragments, total number of successful reassemblies).
Specifically, the fragment information does not feed into FDR and DDR.
Those counts are based on actual full frames.  A fragmentation error
means that the frame never shows up!  The "failure to appear" means that
a bench warrent is issued and FDR/DDR reflects poor delivery quality.

> 
> Thanks for any comments.
> 
> Rob Steinberger
> MTS
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  Mon Feb 15 17:44:53 1999
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.8.5/8.8.7a) with SMTP id RAA10961
	for <frnetmib-archive@lists.ietf.org>; Mon, 15 Feb 1999 17:44:52 -0500 (EST)
Received: from Eng.Sun.COM (engmail1 [129.146.1.13]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id OAA28417; Mon, 15 Feb 1999 14:38:16 -0800
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with ESMTP id OAA15486;
	Mon, 15 Feb 1999 14:37:46 -0800
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id OAA29799
	for frnetmib-dist; Mon, 15 Feb 1999 14:33:44 -0800 (PST)
Received: from Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id OAA29792
	for <frnetmib@sunroof>; Mon, 15 Feb 1999 14:33:39 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id OAA19742
	for <frnetmib@sunroof.Eng.Sun.COM>; Mon, 15 Feb 1999 14:33:38 -0800
Received: from mail.visualnetworks.com ([208.22.72.43])
	by earth.sun.com (8.9.1/8.9.1) with SMTP id OAA19666
	for <frnetmib@sunroof.Eng.Sun.COM>; Mon, 15 Feb 1999 14:33:27 -0800 (PST)
Received: from shemp by mail.visualnetworks.com
          via smtpd (for earth.Sun.COM [192.9.25.3]) with SMTP; 15 Feb 1999 22:38:55 UT
Received: by shemp.visualnetworks.com with Internet Mail Service (5.0.1458.49)
	id <174WLT28>; Mon, 15 Feb 1999 17:43:45 -0500
Message-ID: <0F9AE864A5ECD011B3100060977F354AD57BBC@shemp.visualnetworks.com>
From: "Rehbehn, Kenneth" <Krehbehn@VisualNetworks.com>
To: "'frnetmib@sunroof.Eng.Sun.COM'" <frnetmib@sunroof.Eng.Sun.COM>
Subject: (FRNETMIB) Frame Relay Service MIB Trap Prefix Missing
Date: Mon, 15 Feb 1999 17:43:42 -0500
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1458.49)
Content-Type: text/plain
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/

While reviewing the Frame Rleay Service MIB I noticed that the trap is
defined as follows:

          frnetservTraps    OBJECT IDENTIFIER ::= { frnetservMIB 2 }

          frPVCConnectStatusChange  NOTIFICATION-TYPE
              OBJECTS { frPVCConnectIndex,
                        frPVCConnectLowIfIndex,
                        frPVCConnectLowDLCIIndex,
                        frPVCConnectHighIfIndex,
                        frPVCConnectHighDLCIIndex,
                        frPVCConnectL2hOperStatus,
                        frPVCConnectH2lOperStatus,
                        frPVCEndptRcvdSigStatus }
              STATUS  current
              DESCRIPTION
                      "This trap indicates that the indicated PVC has
                      changed state.  This trap is not sent if an FR-UNI
                      changes state; a linkDown or linkUp trap should be
                      sent instead.  The first instance of
                      frPVCEndptRcvdSigStatus is for the endpoint with
                      LowIfIndex, LowDLCIIndex.  The second instance of
                      frPVCEndptRcvdSigStatus is for the endpoint with
                      HighIfIndex, HighDLCIIndex"
              ::= { frnetservTraps 1 }

I think we need to add the SMI V2 prefix of "0" to aid in conversion to
SNMP V1 MIBs.  I propose to add the following:

          frnetservTraps    OBJECT IDENTIFIER ::= { frnetservMIB 2 }
          frnetservTrapsV2  OBJECT IDENTIFIER ::= { frnetservTraps 0 }

          frPVCConnectStatusChange  NOTIFICATION-TYPE
              OBJECTS { frPVCConnectIndex,
                        frPVCConnectLowIfIndex,
                        frPVCConnectLowDLCIIndex,
                        frPVCConnectHighIfIndex,
                        frPVCConnectHighDLCIIndex,
                        frPVCConnectL2hOperStatus,
                        frPVCConnectH2lOperStatus,
                        frPVCEndptRcvdSigStatus }
              STATUS  current
              DESCRIPTION
                      "This trap indicates that the indicated PVC has
                      changed state.  This trap is not sent if an FR-UNI
                      changes state; a linkDown or linkUp trap should be
                      sent instead.  The first instance of
                      frPVCEndptRcvdSigStatus is for the endpoint with
                      LowIfIndex, LowDLCIIndex.  The second instance of
                      frPVCEndptRcvdSigStatus is for the endpoint with
                      HighIfIndex, HighDLCIIndex"
              ::= { frnetservTrapsV2 1 }

Should this change be made?

Ken

---------------------------------------------------------------
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


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 Feb 16 11:31:40 1999
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.8.5/8.8.7a) with SMTP id LAA02486
	for <frnetmib-archive@lists.ietf.org>; Tue, 16 Feb 1999 11:31:39 -0500 (EST)
Received: from Eng.Sun.COM (engmail4 [129.144.134.6]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id IAA09739; Tue, 16 Feb 1999 08:25:28 -0800
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with ESMTP id IAA08062;
	Tue, 16 Feb 1999 08:25:18 -0800
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id IAA00441
	for frnetmib-dist; Tue, 16 Feb 1999 08:21:10 -0800 (PST)
Received: from Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id IAA00434
	for <frnetmib@sunroof>; Tue, 16 Feb 1999 08:21:00 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id IAA07258
	for <frnetmib@sunroof.Eng.Sun.COM>; Tue, 16 Feb 1999 08:20:59 -0800
Received: from services.paradyne.com (services.paradyne.com [135.90.253.90])
	by earth.sun.com (8.9.1/8.9.1) with ESMTP id IAA23426
	for <frnetmib@sunroof.Eng.Sun.COM>; Tue, 16 Feb 1999 08:20:58 -0800 (PST)
Received: from hermes.eng.paradyne.com ([135.26.1.14])
          by services.paradyne.com (Netscape Messaging Server 3.6)
           with ESMTP id AAA157; Tue, 16 Feb 1999 11:20:43 -0500
Received: from eng.paradyne.com (graysnapper.eng.paradyne.com [135.26.4.35]) by hermes.eng.paradyne.com (8.7.5/8.7.3) with ESMTP id LAA16872; Tue, 16 Feb 1999 11:20:35 -0500 (EST)
Message-ID: <36C99ACE.5E490ECE@eng.paradyne.com>
Date: Tue, 16 Feb 1999 11:20:32 -0500
From: Rob Steinberger <ras@eng.paradyne.com>
Organization: Paradyne Corporation
X-Mailer: Mozilla 4.05 [en] (X11; U; SunOS 5.5.1 sun4u)
MIME-Version: 1.0
To: "Rehbehn, Kenneth" <Krehbehn@VisualNetworks.com>
CC: "'frnetmib@sunroof.Eng.Sun.COM'" <frnetmib@sunroof.Eng.Sun.COM>
Subject: Re: (FRNETMIB) Comments on Frame Relay Services MIB
References: <0F9AE864A5ECD011B3100060977F354AD57BB0@shemp.visualnetworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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 agree that we may want to hold off on the complete set SLA statistics
until the group decides that it is appropriate to add them.  Maybe we
should discuss adding this as a work item at the meeting in March.

As for fragmentation statistics, I feel that the user needs more
information. In the case of end-to-end fragmentation, or in the case of a
probe doing SLA measurements at the FRF12 fragmentation layer, (or
Multilink fragmentation layer), simply counting octets and frames at only
one of the layers does not yield a good picture of network performance. If
SLA measurements are made at the re-assembled frame-layer and not the
fragmentation layer, small values of loss in the network may result in
large values at the frame-level, thus making the network appear much worse
than it is. Conversely, making the measurements at only the fragmentation
layer would properly reflect the network's performance, but would not
address the reason that the user isn't getting any data across. In order to
allow an NMS to properly assess fault and give a complete picture of the
network performance, I think we need a more robust set of statistics.

If it is the case that we do not have time to discuss the statistics at
this point, maybe this should be added as an action item as well and we
should withhold the ability to configure fragmentation until we can
properly track its effects on the network.

Rehbehn, Kenneth wrote:

> Some good ideas!  My comments below:
>
> > -----Original Message-----
> > From: Rob Steinberger [mailto:ras@eng.paradyne.com]
> > Sent: Sunday, February 14, 1999 2:47 PM
> > To: frnetmib@sunroof.Eng.Sun.COM
> > Subject: (FRNETMIB) Comments on Frame Relay Services MIB
> >
> >
> > I have the following comments concerning the new version of the MIB:
> >
> > 1)   The "Service Level Agreement Counters" (in the Changes from RFC
> > 1604 section) should be renamed "Congestion Counters". This may be a
> > trivial issue, but Service Level Agreement directs me to FRF.13.  In
> > that these counters neither fully relate to FRF.13 nor is there a
> > complete set of Service Level Agreement counters in the MIB, I would
> > prefer not to even suggest it to the reader.
> >
>
> I think this is an excellent idea.  The objects have generic utility
> that goes beyond SLA verification.  Unless there are good arguments to
> the contrary, I'll change the comment.
>
> > 2) If we are heading down the path of FRF.13 support for Service Level
> > Agreements, we need more actual Service Level Agreement variables.
> >
> > 2a) On a per end point basis, I think that it would be good to have an
> > Unavailable Seconds counter and possibly some FDR / DDR counters both
> > as frames and octets.  It may also be nice to have the aggregate
> > counters on a per logical port basis.
> >
> > 2b) We are also missing a frame transfer delay object.  Some have
> > stated that this object can be found elsewhere in the MIBs.  My
> > feelings are that this object should both relate to Frame Relay and be
> > generic enough to simply report the delay and not imply any mechanism
> > used to actually calculate the delay.  This allows the user to utilize
> > either some ping type mechanism or proprietary mechanism without
> > having to further extend their MIB view.
> >
> > 2c) We need both frame and octet counts within and/or in excess of
> > CIR.  Right now, we only have frame counts for the excess frames and
> > FRF.13 requires both octets and frames.
>
> Rob is saying that the current MIB objects were not designed with
> FRF.13-based Service Level Agreements in mind.  Other than the
> congestion discard counts cited above, this is true.  However, the
> addition of a number of new objects (and protocol, in the case of some
> new delay measure) is probably a working group task that goes beyond
> "last call" fixing of I-D problems.  If sufficient interest exists,
> let's defer this for a follow-on RFC - perhaps one focused on FR SLA.
>
> >
> > 3) In that we are now controlling fragmentation in this MIB, we now
> > also need fragmentation counters on a per end point basis.  I think
> > that we will find the need to know how many fragmentation failures
> > actually occurred in that a network can appear to run in the normal
> > range but never get data through due to fragmentation failures. This
> > information may also suggest the need for the total number of
> > fragments and the total number of successful reassembles.  A complete
> > set would include the number of segments, the number of segment
> > octets, and the number of reassembly errors.  These are important in
> > that when fragmentation is enabled, the fragment information will feed
> > the FDR and DDR counters.
>
> I could see an object to track fragmentation failure events as an aid to
> trouble shooting a mis-matched configuration.  I don't see the value in
> more granularity (number of segments, number of segment octets, total
> number of fragments, total number of successful reassemblies).
> Specifically, the fragment information does not feed into FDR and DDR.
> Those counts are based on actual full frames.  A fragmentation error
> means that the frame never shows up!  The "failure to appear" means that
> a bench warrent is issued and FDR/DDR reflects poor delivery quality.
>
> >
> > Thanks for any comments.
> >
> > Rob Steinberger
> > MTS



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 Feb 16 11:40:18 1999
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.8.5/8.8.7a) with SMTP id LAA02837
	for <frnetmib-archive@lists.ietf.org>; Tue, 16 Feb 1999 11:40:18 -0500 (EST)
Received: from Eng.Sun.COM (engmail3 [129.144.170.5]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id IAA12860; Tue, 16 Feb 1999 08:33:30 -0800
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with ESMTP id IAA20579;
	Tue, 16 Feb 1999 08:33:25 -0800
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id IAA00494
	for frnetmib-dist; Tue, 16 Feb 1999 08:32:26 -0800 (PST)
Received: from Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id IAA00484
	for <frnetmib@sunroof>; Tue, 16 Feb 1999 08:32:17 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id IAA10005
	for <frnetmib@sunroof.Eng.Sun.COM>; Tue, 16 Feb 1999 08:32:16 -0800
Received: from mail.visualnetworks.com ([208.22.72.43])
	by earth.sun.com (8.9.1/8.9.1) with SMTP id IAA29789
	for <frnetmib@sunroof.Eng.Sun.COM>; Tue, 16 Feb 1999 08:31:55 -0800 (PST)
Received: from shemp by mail.visualnetworks.com
          via smtpd (for earth.Sun.COM [192.9.25.3]) with SMTP; 16 Feb 1999 16:37:24 UT
Received: by shemp.visualnetworks.com with Internet Mail Service (5.0.1458.49)
	id <174WL4MV>; Tue, 16 Feb 1999 11:42:10 -0500
Message-ID: <0F9AE864A5ECD011B3100060977F354AD57BC1@shemp.visualnetworks.com>
From: "Rehbehn, Kenneth" <Krehbehn@VisualNetworks.com>
To: "'Rob Steinberger'" <ras@eng.paradyne.com>
Cc: "'frnetmib@sunroof.Eng.Sun.COM'" <frnetmib@sunroof.Eng.Sun.COM>
Subject: RE: (FRNETMIB) Comments on Frame Relay Services MIB
Date: Tue, 16 Feb 1999 11:42:08 -0500
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1458.49)
Content-Type: text/plain;
	charset="ISO-8859-1"
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/

Rob -

The fragmentation objects in the MIB apply ONLY to the interface and not
end-to-end.  There is no impact on network performance apart from the
load on the physical link supporting fragmentation.  One physical
segment of a connection path is not typically the target of a service
level agreement.

When fragmentation is configured for the port, I think the only
statistic needed is a reassembly failure count to trouble shoot
configuration problems.  

The impact of such failures on service level gets reflected in the
resulting drop of a frame.  That loss is noticed when service level is
monitored on an end-to-end basis.

Regards,
Ken

> -----Original Message-----
> From: Rob Steinberger [mailto:ras@eng.paradyne.com]
> Sent: Tuesday, February 16, 1999 11:21 AM
> To: Rehbehn, Kenneth
> Cc: 'frnetmib@sunroof.Eng.Sun.COM'
> Subject: Re: (FRNETMIB) Comments on Frame Relay Services MIB
> 
> 
> I agree that we may want to hold off on the complete set SLA 
> statistics
> until the group decides that it is appropriate to add them.  Maybe we
> should discuss adding this as a work item at the meeting in March.
> 
> As for fragmentation statistics, I feel that the user needs more
> information. In the case of end-to-end fragmentation, or in 
> the case of a
> probe doing SLA measurements at the FRF12 fragmentation layer, (or
> Multilink fragmentation layer), simply counting octets and 
> frames at only
> one of the layers does not yield a good picture of network 
> performance. If
> SLA measurements are made at the re-assembled frame-layer and not the
> fragmentation layer, small values of loss in the network may result in
> large values at the frame-level, thus making the network 
> appear much worse
> than it is. Conversely, making the measurements at only the 
> fragmentation
> layer would properly reflect the network's performance, but would not
> address the reason that the user isn't getting any data 
> across. In order to
> allow an NMS to properly assess fault and give a complete 
> picture of the
> network performance, I think we need a more robust set of statistics.
> 
> If it is the case that we do not have time to discuss the 
> statistics at
> this point, maybe this should be added as an action item as 
> well and we
> should withhold the ability to configure fragmentation until we can
> properly track its effects on the network.
> 
> Rehbehn, Kenneth wrote:
> 
> > Some good ideas!  My comments below:
> >
> > > -----Original Message-----
> > > From: Rob Steinberger [mailto:ras@eng.paradyne.com]
> > > Sent: Sunday, February 14, 1999 2:47 PM
> > > To: frnetmib@sunroof.Eng.Sun.COM
> > > Subject: (FRNETMIB) Comments on Frame Relay Services MIB
> > >
> > >
> > > I have the following comments concerning the new version 
> of the MIB:
> > >
> > > 1)   The "Service Level Agreement Counters" (in the 
> Changes from RFC
> > > 1604 section) should be renamed "Congestion Counters". 
> This may be a
> > > trivial issue, but Service Level Agreement directs me to 
> FRF.13.  In
> > > that these counters neither fully relate to FRF.13 nor is there a
> > > complete set of Service Level Agreement counters in the 
> MIB, I would
> > > prefer not to even suggest it to the reader.
> > >
> >
> > I think this is an excellent idea.  The objects have generic utility
> > that goes beyond SLA verification.  Unless there are good 
> arguments to
> > the contrary, I'll change the comment.
> >
> > > 2) If we are heading down the path of FRF.13 support for 
> Service Level
> > > Agreements, we need more actual Service Level Agreement variables.
> > >
> > > 2a) On a per end point basis, I think that it would be 
> good to have an
> > > Unavailable Seconds counter and possibly some FDR / DDR 
> counters both
> > > as frames and octets.  It may also be nice to have the aggregate
> > > counters on a per logical port basis.
> > >
> > > 2b) We are also missing a frame transfer delay object.  Some have
> > > stated that this object can be found elsewhere in the MIBs.  My
> > > feelings are that this object should both relate to Frame 
> Relay and be
> > > generic enough to simply report the delay and not imply 
> any mechanism
> > > used to actually calculate the delay.  This allows the 
> user to utilize
> > > either some ping type mechanism or proprietary mechanism without
> > > having to further extend their MIB view.
> > >
> > > 2c) We need both frame and octet counts within and/or in excess of
> > > CIR.  Right now, we only have frame counts for the excess 
> frames and
> > > FRF.13 requires both octets and frames.
> >
> > Rob is saying that the current MIB objects were not designed with
> > FRF.13-based Service Level Agreements in mind.  Other than the
> > congestion discard counts cited above, this is true.  However, the
> > addition of a number of new objects (and protocol, in the 
> case of some
> > new delay measure) is probably a working group task that goes beyond
> > "last call" fixing of I-D problems.  If sufficient interest exists,
> > let's defer this for a follow-on RFC - perhaps one focused 
> on FR SLA.
> >
> > >
> > > 3) In that we are now controlling fragmentation in this 
> MIB, we now
> > > also need fragmentation counters on a per end point 
> basis.  I think
> > > that we will find the need to know how many fragmentation failures
> > > actually occurred in that a network can appear to run in 
> the normal
> > > range but never get data through due to fragmentation 
> failures. This
> > > information may also suggest the need for the total number of
> > > fragments and the total number of successful reassembles. 
>  A complete
> > > set would include the number of segments, the number of segment
> > > octets, and the number of reassembly errors.  These are 
> important in
> > > that when fragmentation is enabled, the fragment 
> information will feed
> > > the FDR and DDR counters.
> >
> > I could see an object to track fragmentation failure events 
> as an aid to
> > trouble shooting a mis-matched configuration.  I don't see 
> the value in
> > more granularity (number of segments, number of segment 
> octets, total
> > number of fragments, total number of successful reassemblies).
> > Specifically, the fragment information does not feed into 
> FDR and DDR.
> > Those counts are based on actual full frames.  A fragmentation error
> > means that the frame never shows up!  The "failure to 
> appear" means that
> > a bench warrent is issued and FDR/DDR reflects poor 
> delivery quality.
> >
> > >
> > > Thanks for any comments.
> > >
> > > Rob Steinberger
> > > MTS
> 
> 
> 
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 Feb 26 16:41:49 1999
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA27991
	for <frnetmib-archive@lists.ietf.org>; Fri, 26 Feb 1999 16:41:48 -0500 (EST)
Received: from Eng.Sun.COM (engmail1 [129.146.1.13]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id NAA16244; Fri, 26 Feb 1999 13:35:34 -0800
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (8.8.8+Sun/SMI-5.3) with ESMTP id NAA16021;
	Fri, 26 Feb 1999 13:35:08 -0800 (PST)
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id NAA15548
	for frnetmib-dist; Fri, 26 Feb 1999 13:34:35 -0800 (PST)
Received: from Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA15541
	for <frnetmib@sunroof>; Fri, 26 Feb 1999 13:34:25 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by Eng.Sun.COM (8.8.8+Sun/SMI-5.3) with ESMTP id NAA02762
	for <frnetmib@sunroof.eng.sun.com>; Fri, 26 Feb 1999 13:34:22 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by earth.sun.com (8.9.1/8.9.1) with ESMTP id NAA17561
	for <frnetmib@sunroof.eng.sun.com>; Fri, 26 Feb 1999 13:34:22 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27764;
	Fri, 26 Feb 1999 16:34:15 -0500 (EST)
Message-Id: <199902262134.QAA27764@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;;
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-atmiwf-01.txt
Date: Fri, 26 Feb 1999 16:34:15 -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 Monitoring 
                          and Controlling the Frame Relay/ATM PVC 
                          Service Interworking Function
	Author(s)	: K. Rehbehn, O. Nicklass, G. Mouradian
	Filename	: draft-ietf-frnetmib-atmiwf-01.txt
	Pages		: 31
	Date		: 25-Feb-99
	
   This memo defines a Management Information Base (MIB) for monitoring
   and controlling a service interworking function (IWF) for Permanent
   Virtual Connections (PVC) between Frame Relay and Asynchronous
   Transfer Mode (ATM) technologies.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-frnetmib-atmiwf-01.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-atmiwf-01.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-atmiwf-01.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:	<19990225150354.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-frnetmib-atmiwf-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-frnetmib-atmiwf-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990225150354.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  Fri Feb 26 23:38:30 1999
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA26627
	for <frnetmib-archive@lists.ietf.org>; Fri, 26 Feb 1999 23:38:29 -0500 (EST)
Received: from Eng.Sun.COM (engmail2 [129.146.1.25]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id UAA27515; Fri, 26 Feb 1999 20:32:56 -0800
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (8.8.8+Sun/SMI-5.3) with ESMTP id UAA00991;
	Fri, 26 Feb 1999 20:32:49 -0800 (PST)
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id UAA15975
	for frnetmib-dist; Fri, 26 Feb 1999 20:31:55 -0800 (PST)
Received: from Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id UAA15968
	for <frnetmib@sunroof>; Fri, 26 Feb 1999 20:31:47 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by Eng.Sun.COM (8.8.8+Sun/SMI-5.3) with ESMTP id UAA17903
	for <frnetmib@sunroof.eng.sun.com>; Fri, 26 Feb 1999 20:31:46 -0800 (PST)
Received: from delcluster2.vsnl.net.in (delcluster2.vsnl.net.in [202.54.96.2])
	by earth.sun.com (8.9.1/8.9.1) with ESMTP id UAA02012
	for <frnetmib@sunroof.eng.sun.com>; Fri, 26 Feb 1999 20:31:43 -0800 (PST)
Received: from mailserver ([202.54.106.227])
	by delcluster2.vsnl.net.in (8.9.2/8.9.2) with SMTP id KAA20253
	for <frnetmib@sunroof.eng.sun.com>; Sat, 27 Feb 1999 10:01:54 -0500 (GMT)
Received: by mailserver with XtraMail-SMTP/POP3-Server (v1.10 58210006074) for <frnetmib@sunroof.eng.sun.com> at Sat, 27 Feb 99  09:56:29 +0530
Received: from proxy1.ba.best.com (root@proxy1.ba.best.com [206.184.139.12])
	by fpage1.ba.best.com (8.9.2/8.9.2/best.sh) with ESMTP id OAA15538
	for <ravibaid+XRCPT.61616c6f6b4042495351554152452e434f4d@fpage1.ba.best.com>; Fri, 26 Feb 1999 14:03:40 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by proxy1.ba.best.com (8.9.3/8.9.2/best.in) with ESMTP id OAA13605;
	Fri, 26 Feb 1999 14:00:46 -0800 (PST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA28619
	for ietf-123-outbound.02@ietf.org; Fri, 26 Feb 1999 16:55:01 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27764;
	Fri, 26 Feb 1999 16:34:15 -0500 (EST)
Message-Id: <199902262134.QAA27764@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;;;;@bisquare.com;@Eng.Sun.COM;;;
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-atmiwf-01.txt
Date: Fri, 26 Feb 1999 16:34:15 -0500
X-Rcpt-To: aalok@bisquare.com
X-UIDL: 7987ef81696c929f4254fcd7f8ac29ac
Status: U
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 Frame Relay/ATM PVC 
                          Service Interworking Function
	Author(s)	: K. Rehbehn, O. Nicklass, G. Mouradian
	Filename	: draft-ietf-frnetmib-atmiwf-01.txt
	Pages		: 31
	Date		: 25-Feb-99
	
   This memo defines a Management Information Base (MIB) for monitoring
   and controlling a service interworking function (IWF) for Permanent
   Virtual Connections (PVC) between Frame Relay and Asynchronous
   Transfer Mode (ATM) technologies.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-frnetmib-atmiwf-01.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-atmiwf-01.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-atmiwf-01.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:	<19990225150354.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-frnetmib-atmiwf-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-frnetmib-atmiwf-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<19990225150354.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 Mar  2 10:50:37 1999
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA03564
	for <frnetmib-archive@lists.ietf.org>; Tue, 2 Mar 1999 10:50:36 -0500 (EST)
Received: from Eng.Sun.COM (engmail3 [129.144.170.5]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id HAA00858; Tue, 2 Mar 1999 07:40:57 -0800
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (8.8.8+Sun/SMI-5.3) with ESMTP id HAA16330;
	Tue, 2 Mar 1999 07:40:48 -0800 (PST)
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id HAA18926
	for frnetmib-dist; Tue, 2 Mar 1999 07:40:20 -0800 (PST)
Received: from Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA18911
	for <frnetmib@sunroof>; Tue, 2 Mar 1999 07:40:10 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by Eng.Sun.COM (8.8.8+Sun/SMI-5.3) with ESMTP id HAA26756
	for <frnetmib@sunroof.eng.sun.com>; Tue, 2 Mar 1999 07:40:07 -0800 (PST)
Received: from alpo.casc.com (alpo.casc.com [152.148.10.6])
	by earth.sun.com (8.9.1/8.9.1) with ESMTP id HAA18240
	for <frnetmib@sunroof.eng.sun.com>; Tue, 2 Mar 1999 07:40:08 -0800 (PST)
Received: from amalis (amalis [152.148.13.74])
	by alpo.casc.com (8.9.1a/8.9.1) with SMTP id KAA26295;
	Tue, 2 Mar 1999 10:40:07 -0500 (EST)
Message-Id: <4.1.19990302101933.01a6ad70@alpo.casc.com>
X-Sender: amalis@alpo.casc.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Tue, 02 Mar 1999 10:40:03 -0500
To: frnetmib@sunroof.Eng.Sun.COM
From: "Andrew G. Malis" <malis@casc.com>
Subject: (FRNETMIB) A bunch of frnetmib WG business
Cc: "Andrew G. Malis" <malis@casc.com>
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/

I've put a bunch of frnetmib WG business into one email.

1. Our session in Minneapolis has been moved slightly; instead of Tuesday 9 
AM to 10 AM, we are now Tuesday 10:15 to 11:15.  This was done at the 
request of our co-area directors.

2. This ends the WG last call for draft-ietf-frnetmib-frs-mib-03.txt (about 
a week late - sorry about that).  We had good comments on the list; here is 
their resolution:

- The priority object(s) requested by Zhongde Yu will be deferred to a
  follow-on extension to the MIB.
- Rob Steinberger's suggestions regarding SLA and fragmentation counters 
  have been partially accepted for this MIB and partially deferred to
  follow-on work, as per the discussion on the list.
- The missing trap prefix will be corrected.

Ken will put out a -04 based upon this resolution.  Given the I-D freeze,
Ken can email it to the WG list as well as the Internet-drafts editor.  It
will be forwarded to the IESG as soon as the I-D freeze is lifted.

3. We have one other current WG draft to discuss in Minneapolis:

draft-ieft-frnetmib-atmiwf-01.txt
Definitions of Managed Objects for Monitoring and Controlling
the Frame Relay/ATM PVC Service Interworking Function

Is there anything else people would like to put on the agenda?  If so,
please let me know.

Thanks,
Andy

________________________________________________________________________
Andrew G. Malis  malis@ascend.com  phone:978 952-7414   fax:978 392-2074
Ascend Communications, Inc.        1 Robbins Road     Westford, MA 01886
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  Mon Mar  8 14:08:16 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 OAA07239;
	Mon, 8 Mar 1999 14:08:15 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA07970;
	Mon, 8 Mar 1999 11:07:28 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8) with ESMTP id LAA04281;
	Mon, 8 Mar 1999 11:07:24 -0800 (PST)
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id LAA26454
	for frnetmib-dist; Mon, 8 Mar 1999 11:06:55 -0800 (PST)
Received: from Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA26441
	for <frnetmib@sunroof>; Mon, 8 Mar 1999 11:06:41 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by Eng.Sun.COM (8.8.8+Sun/SMI-5.3) with ESMTP id LAA07798
	for <frnetmib@sunroof.eng.sun.com>; Mon, 8 Mar 1999 11:06:40 -0800 (PST)
Received: from alpo.casc.com (alpo.casc.com [152.148.10.6])
	by earth.sun.com (8.9.1/8.9.1) with ESMTP id LAA07793
	for <frnetmib@sunroof.eng.sun.com>; Mon, 8 Mar 1999 11:06:39 -0800 (PST)
Received: from amalis (amalis [152.148.13.74])
	by alpo.casc.com (8.9.1a/8.9.1) with SMTP id OAA07682;
	Mon, 8 Mar 1999 14:06:37 -0500 (EST)
Message-Id: <4.1.19990308135816.01abe980@alpo.casc.com>
X-Sender: amalis@alpo.casc.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Mon, 08 Mar 1999 14:05:40 -0500
To: frnetmib@sunroof.eng.sun.com
From: "Andrew G. Malis" <malis@casc.com>
Subject: (FRNETMIB) Draft frnetmib agenda
Cc: "Andrew G. Malis" <malis@casc.com>
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/

Let me know ASAP if there's anyone else who would like to be added.  We can
also adjust the agenda at the meeting.

Andy

-------

Frame Relay Service MIB WG (frnetmib)

Tuesday, March 16, 1015 - 1115
==============================

Chair: Andy Malis <malis@ascend.com>

AGENDA:

1. Administrivia, current documents status

2. draft-ietf-frnetmib-frs-mib-03.txt
   Definitions of Managed Objects for Frame Relay Service

3. draft-ieft-frnetmib-atmiwf-01.txt,
   Definitions of Managed Objects for Monitoring and Controlling
   the Frame Relay/ATM PVC Service Interworking Function

4. Open discussion

________________________________________________________________________
Andrew G. Malis  malis@ascend.com  phone:978 952-7414   fax:978 392-2074
Ascend Communications, Inc.        1 Robbins Road     Westford, MA 01886
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 Mar  9 16:33:24 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 QAA19640;
	Tue, 9 Mar 1999 16:33:23 -0500 (EST)
Received: from Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA19742;
	Tue, 9 Mar 1999 13:33:15 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (8.8.8+Sun/SMI-5.3) with ESMTP id NAA19427;
	Tue, 9 Mar 1999 13:32:52 -0800 (PST)
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id NAA27811
	for frnetmib-dist; Tue, 9 Mar 1999 13:30:04 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA27804
	for <frnetmib@sunroof.Eng.Sun.COM>; Tue, 9 Mar 1999 13:29:48 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by engmail1.Eng.Sun.COM (8.8.8+Sun/8.8.8) with ESMTP id NAA06927
	for <frnetmib@sunroof.Eng.Sun.COM>; Tue, 9 Mar 1999 13:29:47 -0800 (PST)
Received: from mail.visualnetworks.com ([208.22.72.43])
	by earth.sun.com (8.9.1/8.9.1) with SMTP id NAA28020
	for <frnetmib@sunroof.Eng.Sun.COM>; Tue, 9 Mar 1999 13:29:47 -0800 (PST)
Received: from shemp by mail.visualnetworks.com
          via smtpd (for earth.Sun.COM [192.9.25.3]) with SMTP; 9 Mar 1999 21:35:40 UT
Received: by shemp.visualnetworks.com with Internet Mail Service (5.0.1458.49)
	id <GR3QKPQQ>; Tue, 9 Mar 1999 16:27:16 -0500
Message-ID: <0F9AE864A5ECD011B3100060977F354AD57C1B@shemp.visualnetworks.com>
From: "Rehbehn, Kenneth" <Krehbehn@VisualNetworks.com>
To: frnetmib@sunroof.Eng.Sun.COM
Subject: (FRNETMIB) draft-ietf-frnetmib-frs-mib-04.txt
Date: Tue, 9 Mar 1999 16:27:14 -0500
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1458.49)
Content-Type: text/plain
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 have incorporated the changes following the working group last call
period.  The MIB and a difference file (PDF) are available from: 

ftp://ftp.visualnetworks.com/Pub/IETF/draft-ietf-frnetmib-frs-mib-04.txt
ftp://ftp.visualnetworks.com/Pub/IETF/draft-ietf-frnetmib-frs-mib-04-dif
f.pdf

The draft will be forwarded to the I-D Editor for posting following the
I-D freeze.

See you in Minneapolis!
Ken

---------------------------------------------------------------
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


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 Mar 10 09:28:46 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 JAA10926;
	Wed, 10 Mar 1999 09:28:45 -0500 (EST)
Received: from Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA23783;
	Wed, 10 Mar 1999 06:28:14 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by Eng.Sun.COM (8.8.8+Sun/SMI-5.3) with ESMTP id GAA28650;
	Wed, 10 Mar 1999 06:28:01 -0800 (PST)
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id GAA28387
	for frnetmib-dist; Wed, 10 Mar 1999 06:21:11 -0800 (PST)
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 GAA28380
	for <frnetmib@sunroof.eng.sun.com>; Wed, 10 Mar 1999 06:20:56 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8) with ESMTP id GAA13085
	for <frnetmib@sunroof.eng.sun.com>; Wed, 10 Mar 1999 06:20:53 -0800 (PST)
Received: from alpo.casc.com (alpo.casc.com [152.148.10.6])
	by earth.sun.com (8.9.1/8.9.1) with ESMTP id GAA21060
	for <frnetmib@sunroof.eng.sun.com>; Wed, 10 Mar 1999 06:20:55 -0800 (PST)
Received: from amalis (amalis [152.148.13.74])
	by alpo.casc.com (8.9.1a/8.9.1) with SMTP id JAA23548;
	Wed, 10 Mar 1999 09:20:22 -0500 (EST)
Message-Id: <4.1.19990310091649.01abd230@alpo.casc.com>
X-Sender: amalis@alpo.casc.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 10 Mar 1999 09:20:15 -0500
To: agenda@ietf.org
From: "Andrew G. Malis" <malis@casc.com>
Subject: (FRNETMIB) FRNETMIB Minneapolis agenda
Cc: frnetmib@sunroof.Eng.Sun.COM, "Andrew G. Malis" <malis@casc.com>
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/

Frame Relay Service MIB WG (frnetmib)

Tuesday, March 16, 1015 - 1115
==============================

Chair: Andy Malis <malis@ascend.com>

AGENDA:

1. Administrivia, current documents status

2. draft-ietf-frnetmib-frs-mib-04.txt
   Definitions of Managed Objects for Frame Relay Service

3. draft-ieft-frnetmib-atmiwf-01.txt,
   Definitions of Managed Objects for Monitoring and Controlling
   the Frame Relay/ATM PVC Service Interworking Function

4. Open discussion

________________________________________________________________________
Andrew G. Malis  malis@ascend.com  phone:978 952-7414   fax:978 392-2074
Ascend Communications, Inc.        1 Robbins Road     Westford, MA 01886
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 Mar 19 09:19:41 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 JAA14262;
	Fri, 19 Mar 1999 09:19:41 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA13694;
	Fri, 19 Mar 1999 06:19:35 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with ESMTP id GAA24620;
	Fri, 19 Mar 1999 06:19:29 -0800 (PST)
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id GAA07519
	for frnetmib-dist; Fri, 19 Mar 1999 06:18:58 -0800 (PST)
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 GAA07512
	for <frnetmib@sunroof.eng.sun.com>; Fri, 19 Mar 1999 06:18:46 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by engmail4.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with ESMTP id GAA00969
	for <frnetmib@sunroof.eng.sun.com>; Fri, 19 Mar 1999 06:18:44 -0800 (PST)
Received: from alpo.casc.com (alpo.casc.com [152.148.10.6])
	by earth.sun.com (8.9.1/8.9.1) with ESMTP id GAA26785
	for <frnetmib@sunroof.eng.sun.com>; Fri, 19 Mar 1999 06:18:41 -0800 (PST)
Received: from amalis ([152.148.171.94])
	by alpo.casc.com (8.9.1a/8.9.1) with SMTP id JAA07639;
	Fri, 19 Mar 1999 09:18:32 -0500 (EST)
Message-Id: <4.1.19990319090832.01c27d50@alpo.casc.com>
X-Sender: amalis@alpo.casc.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Fri, 19 Mar 1999 09:09:17 -0500
To: frnetmib@sunroof.eng.sun.com
From: "Andrew G. Malis" <malis@casc.com>
Subject: (FRNETMIB) Draft frnetmib minutes
Cc: "Andrew G. Malis" <malis@casc.com>
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/

These are the draft frnetmib minutes.  Please send comments to the list.

Thanks,
Andy

-------

Frame Relay Service MIB (frnetmib) Working Group Minutes
IETF-44, Minneapolis (March 15-19, 1999)

Date: Tuesday, March 16, 1015-1115

Chair: Andrew Malis, Ascend Communications, malis@ascend.com

Minutes recorded by Andrew Malis

Mailing List Information:
Discussion: frnetmib@sunroof.eng.sun.com
E-Mail-Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/
(un)subscribe requests to: majordomo@sunroof.eng.sun.com

Agenda:

1. Administrivia, current documents status

2. Definitions of Managed Objects for Frame Relay Service
   draft-ietf-frnetmib-frs-mib-04.txt

3. Definitions of Managed Objects for Monitoring and Controlling
   the Frame Relay/ATM PVC Service Interworking Function
   draft-ietf-frnetmib-atmiwf-01.txt

4. Open discussion


Agenda Item 1: Administrivia, current document status

Andy Malis presented the agenda. There were no request for
changes or additional agenda items.

Following the review of the agenda, Andy presented on overview of
the status of work in the frnetmib group.

The following drafts are in progress:
- draft-ietf-frnetmib-frs-mib-04.txt, Definitions of Managed
  Objects for Frame Relay Service, Ken Rehbehn, Dave Fowler
  We heard about this draft later in the meeting.
- draft-ietf-frnetmib-spvc-02.txt, Frame Relay Switched PVC MIB,
  Bill Coutts
  This was forwarded to IESG for publication as Proposed Standard
  RFC, and last week comments were returned from the IESG.  Bill
  will update the draft based upon the comments.
- draft-ietf-frnetmib-atmiwf-01.txt, Definitions of Managed
  Objects for Monitoring and Controlling the Frame Relay/ATM PVC
  Service Interworking, Ken Rehbehn, Orly Nicklass, George
  Mouradian
  We heard about this draft later in the meeting.
- draft-ietf-frnetmib-dte-svc-00.txt, Don Cochrane
  Don had indicated that he was still interested in pursuing this
  draft.  Andy will contact him to determine his current
  intentions.
- draft-ietf-frnetmib-dcp-02.txt, Moji Kashef, Jaime Colom
  Rob Steinberger will contact Jaime to determine his intentions.


Agenda Item 2: Definitions of Managed Objects for Frame Relay
Service, draft-ietf-frnetmib-frs-mib-04.txt

Ken Rehbehn presented the changes since the last meeting.  He
updated the boilerplate, added fragmentation objects, changed
notification prefix for SMIv1 compiles, removed text citing
service level agreements, and got a clean compile with smicng.

He plans to revise the MIB based upon comments he has received
from Bert Wijnen, including apply to both this MIB and the SPVC
MIB.


Agenda Item 3:  Definitions of Managed Objects for Monitoring and
Controlling the Frame Relay/ATM PVC Service Interworking
Function, draft-ietf-frnetmib-atmiwf-01.txt

Ken Rehbehn also presented this MIB.  He began by describing the
MIB's structure.  During the structure discussion, some open
issues came up that Ken had also listed later in his
presentation.  Changes from the previous version included
boilerplate, additional connection indices and descriptors,
changed TimeTicks to TimeStamp, updated the compliance statement,
updated to SMIv2, and compiled cleanly with smicng.

There are still a number of open issues, including the
relationships with other MIBs, saving the last failed translation
packet header, security boilerplate, connection entry DESCRIPTION
text needs to clarify system behavior, "Big Picture" descriptive
text is needed, it needs text describing creation/destruction of
IWF connections or components, explicit point-to-multipoint text
is needed (both when supported and when not), and an IANA MIB
leaf is required.

David Perkins asked if there extra objects in the
frAtmIwfConnStatusChange notification.  Ken will update the
notification based upon the discussion.  Rob Steinberger
suggested that Ken remove the comment that this will lead to an
SVC MIB, which Ken will do.

Ken's plan is to continue to work with Orly Nicklass and put out
a new draft in the May time frame.  Randy Presuhn asked about the
MIB's persistance characteristics over reboots - will table
entries remain over device reboots?  This was discused in the
meeting, but no conclusions were reached.  This will be further
discussed on the list.


Agenda Item 4: Open Discussion

Rob and Orly are going to think about working on an SLA MIB based
on FRF.13.

No additional items were brought up, and the group adjourned.

________________________________________________________________________
Andrew G. Malis  malis@ascend.com  phone:978 952-7414   fax:978 392-2074
Ascend Communications, Inc.        1 Robbins Road     Westford, MA 01886
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 Mar 25 09:34:27 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 JAA26748;
	Thu, 25 Mar 1999 09:34:26 -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 GAA03553;
	Thu, 25 Mar 1999 06:34:30 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with ESMTP id GAA06797;
	Thu, 25 Mar 1999 06:34:24 -0800 (PST)
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id GAA13903
	for frnetmib-dist; Thu, 25 Mar 1999 06:34:07 -0800 (PST)
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 GAA13896
	for <frnetmib@sunroof.eng.sun.com>; Thu, 25 Mar 1999 06:34:01 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with ESMTP id GAA21726
	for <frnetmib@sunroof.eng.sun.com>; Thu, 25 Mar 1999 06:33:58 -0800 (PST)
Received: from alpo.casc.com (alpo.casc.com [152.148.10.6])
	by earth.sun.com (8.9.1/8.9.1) with ESMTP id GAA21539
	for <frnetmib@sunroof.eng.sun.com>; Thu, 25 Mar 1999 06:33:57 -0800 (PST)
Received: from apollo13.casc.com (apollo13 [152.148.10.13])
	by alpo.casc.com (8.9.1a/8.9.1) with ESMTP id JAA13440;
	Thu, 25 Mar 1999 09:33:55 -0500 (EST)
Received: from localhost by apollo13.casc.com (8.8.8+Sun/SMI-SVR4)
	id JAA27812; Thu, 25 Mar 1999 09:33:54 -0500 (EST)
Date: Thu, 25 Mar 1999 09:33:54 -0500 (EST)
From: "Andrew G. Malis" <amalis@casc.com>
X-Sender: amalis@apollo13
To: frnetmib@sunroof.eng.sun.com
cc: "Andrew G. Malis" <malis@casc.com>
Subject: (FRNETMIB) New technical advisor for FRNETMIB WG (fwd)
Message-ID: <Pine.GSO.4.10.9903250929410.27764-100000@apollo13>
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/

For your information.

Welcome aboard to Bob, and many thanks to Fred for his past
contributions.

Andy

---------- Forwarded message ----------
Date: Wed, 24 Mar 99 00:16:50 CET
From: Bert Wijnen <WIJNEN@vnet.ibm.com>
To: scoya@ietf.org, malis@ascend.com
Cc: fred@cisco.com, bstewart@cisco.com, narten@raleigh.ibm.com,
     nordmark@eng.sun.com
Subject: Technical advisor for FRNETMIB WG

Steve, Andy,

Fred Baker has asked me to try and find another Technical Advisor for
your WG who is well versed in SNMP and SMI.

Bob Stewart has offered to play that role. So any questions on SNMP or
SMI can be posted to Bob. Bob can also do a pre-review of the MIBs
before they go to WG last call.

Hope this helps to get the WG to do their work faster/better.

Steve, can you update the WG charter page.

Bert - co-AD for Operations and Management

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 Mar 26 16:30:16 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 QAA02318;
	Fri, 26 Mar 1999 16:30:16 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA01454;
	Fri, 26 Mar 1999 13:29:52 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with ESMTP id NAA16772;
	Fri, 26 Mar 1999 13:29:39 -0800 (PST)
Received: by sunroof.eng.sun.com (8.9.3+Sun/8.9.3) id NAA15430
	for frnetmib-dist; Fri, 26 Mar 1999 13:29:22 -0800 (PST)
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 NAA15423
	for <frnetmib@sunroof.eng.sun.com>; Fri, 26 Mar 1999 13:29:17 -0800 (PST)
Received: from earth.sun.com (earth.EBay.Sun.COM [129.150.69.3])
	by engmail4.Eng.Sun.COM (8.8.8+Sun/8.8.8/ENS_USDOMAIN,v%I%) with ESMTP id NAA21246
	for <frnetmib@sunroof.eng.sun.com>; Fri, 26 Mar 1999 13:29:15 -0800 (PST)
Received: from alpo.casc.com (alpo.casc.com [152.148.10.6])
	by earth.sun.com (8.9.1/8.9.1) with ESMTP id NAA02448
	for <frnetmib@sunroof.eng.sun.com>; Fri, 26 Mar 1999 13:29:14 -0800 (PST)
Received: from apollo13.casc.com (apollo13 [152.148.10.13])
	by alpo.casc.com (8.9.1a/8.9.1) with ESMTP id QAA18733;
	Fri, 26 Mar 1999 16:29:07 -0500 (EST)
Received: from localhost by apollo13.casc.com (8.8.8+Sun/SMI-SVR4)
	id QAA03424; Fri, 26 Mar 1999 16:29:06 -0500 (EST)
Date: Fri, 26 Mar 1999 16:29:06 -0500 (EST)
From: "Andrew G. Malis" <amalis@casc.com>
X-Sender: amalis@apollo13
To: minutes@ietf.org
cc: "Andrew G. Malis" <malis@casc.com>, frnetmib@sunroof.eng.sun.com
Subject: (FRNETMIB) Final frnetmib minutes
Message-ID: <Pine.GSO.4.10.9903261628100.29546-100000@apollo13>
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/

Frame Relay Service MIB (frnetmib) Working Group Minutes
IETF-44, Minneapolis (March 15-19, 1999)

Date: Tuesday, March 16, 1015-1115

Chair: Andrew Malis, Ascend Communications, malis@ascend.com

Minutes recorded by Andrew Malis

Mailing List Information:
Discussion: frnetmib@sunroof.eng.sun.com
E-Mail-Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/
(un)subscribe requests to: majordomo@sunroof.eng.sun.com

Agenda:

1. Administrivia, current documents status

2. Definitions of Managed Objects for Frame Relay Service
   draft-ietf-frnetmib-frs-mib-04.txt

3. Definitions of Managed Objects for Monitoring and Controlling
   the Frame Relay/ATM PVC Service Interworking Function
   draft-ietf-frnetmib-atmiwf-01.txt

4. Open discussion


Agenda Item 1: Administrivia, current document status

Andy Malis presented the agenda. There were no request for
changes or additional agenda items.

Following the review of the agenda, Andy presented on overview of
the status of work in the frnetmib group.

The following drafts are in progress:
- draft-ietf-frnetmib-frs-mib-04.txt, Definitions of Managed
  Objects for Frame Relay Service, Ken Rehbehn, Dave Fowler
  We heard about this draft later in the meeting.
- draft-ietf-frnetmib-spvc-02.txt, Frame Relay Switched PVC MIB,
  Bill Coutts
  This was forwarded to IESG for publication as Proposed Standard
  RFC, and last week comments were returned from the IESG.  Bill
  will update the draft based upon the comments.
- draft-ietf-frnetmib-atmiwf-01.txt, Definitions of Managed
  Objects for Monitoring and Controlling the Frame Relay/ATM PVC
  Service Interworking, Ken Rehbehn, Orly Nicklass, George
  Mouradian
  We heard about this draft later in the meeting.
- draft-ietf-frnetmib-dte-svc-00.txt, Don Cochrane
  Don had indicated that he was still interested in pursuing this
  draft.  Andy will contact him to determine his current
  intentions.
- draft-ietf-frnetmib-dcp-02.txt, Moji Kashef, Jaime Colom
  Rob Steinberger will contact Jaime to determine his intentions.


Agenda Item 2: Definitions of Managed Objects for Frame Relay
Service, draft-ietf-frnetmib-frs-mib-04.txt

Ken Rehbehn presented the changes since the last meeting.  He
updated the boilerplate, added fragmentation objects, changed
notification prefix for SMIv1 compiles, removed text citing
service level agreements, and got a clean compile with smicng.

He plans to revise the MIB based upon comments he has received
from Bert Wijnen, including apply to both this MIB and the SPVC
MIB.


Agenda Item 3:  Definitions of Managed Objects for Monitoring and
Controlling the Frame Relay/ATM PVC Service Interworking
Function, draft-ietf-frnetmib-atmiwf-01.txt

Ken Rehbehn also presented this MIB.  He began by describing the
MIB's structure.  During the structure discussion, some open
issues came up that Ken had also listed later in his
presentation.  Changes from the previous version included
boilerplate, additional connection indices and descriptors,
changed TimeTicks to TimeStamp, updated the compliance statement,
updated to SMIv2, and compiled cleanly with smicng.

There are still a number of open issues, including the
relationships with other MIBs, saving the last failed translation
packet header, security boilerplate, connection entry DESCRIPTION
text needs to clarify system behavior, "Big Picture" descriptive
text is needed, it needs text describing creation/destruction of
IWF connections or components, explicit point-to-multipoint text
is needed (both when supported and when not), and an IANA MIB
leaf is required.

David Perkins asked if there extra objects in the
frAtmIwfConnStatusChange notification.  Ken will update the
notification based upon the discussion.  Rob Steinberger
suggested that Ken remove the comment that this will lead to an
SVC MIB, which Ken will do.

Ken's plan is to continue to work with Orly Nicklass and put out
a new draft in the May time frame.  Randy Presuhn asked about the
MIB's persistance characteristics over reboots - will table
entries remain over device reboots?  This was discused in the
meeting, but no conclusions were reached.  This will be further
discussed on the list.


Agenda Item 4: Open Discussion

Rob and Orly are going to think about working on an SLA MIB based
on FRF.13.

No additional items were brought up, and the group adjourned.

________________________________________________________________________
Andrew G. Malis  malis@ascend.com  phone:978 952-7414   fax:978 392-2074
Ascend Communications, Inc.        1 Robbins Road     Westford, MA 01886

X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with
X-Info: 'unsubscribe frnetmib' in the body of the message.


