Comments on X.25 MIB, 12 June, 1992

goldthorpe@ses6a.bt.co.uk Tue, 16 June 1992 09:40 UTC

Received: from nri.reston.va.us by ietf.NRI.Reston.VA.US id aa05616; 16 Jun 92 5:40 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa01958; 16 Jun 92 5:40 EDT
Received: from dg-rtp.rtp.dg.com by NRI.Reston.VA.US id aa01951; 16 Jun 92 5:40 EDT
Received: from [132.146.5.1] by dg-rtp.dg.com (5.4/dg-rtp-proto) id AA01329; Tue, 16 Jun 1992 03:49:37 -0400
Message-Id: <9206160749.AA01329@dg-rtp.dg.com>
Received: from ses6a.bt.co.uk by zaphod.axion.bt.co.uk via DECnet inbound channel id <16479-0@zaphod.axion.bt.co.uk>; Tue, 16 Jun 1992 08:49:12 +0100
X-Vms-To: R11F::DG-RTP.DG.COM::X25MIB
To: x25mib@dg-rtp.dg.com
From: goldthorpe@ses6a.bt.co.uk
Subject: Comments on X.25 MIB, 12 June, 1992
Date: Tue, 16 Jun 1992 08:49:12 +0100

From:	NAME: Andy Goldthorpe               
	FUNC: DAS23                           
	TEL: 0473 227164                      <GOLDTHORPE AT A1 AT SES6A>
To:	x25mib@dg-rtp.dg.com@r11f@mrgate


Comments on X.25 Packet Layer MIB


Comment  : #1
Location : Page 2, clause 1.1
Type     : Question
Question : Why has the x121Address been extended to 17 digits?  There is no
	   change to X.121 in the 1988 X.25 standard.

Comment  : #2
Location : Page 9, clause 5.3
Type     : Major technical
Rationale: Reference is made to the ISO work on X.25 management and the
	   Committee Draft of 10733.  It should be noted that this work has
	   advanced cosiderably, particularly in light of CCITT comments on
	   X.25 management.
Proposal : ISO SC6 is meeting in July to consider the DIS ballot of 10733.
	   CCITT has submitted a considerable input to this meeting.  The
	   results of this meeting (which may be an IS) should be
	   considered and referenced, and the MIB aligned.

Comment  : #3 (ref #1)
Location : Page 13, clause 6
Type	 : Major technical
Rationale: X.121 addresses are a maximum of 14 digits in length.  They may
	   be preceeded by an escape code (1 digit) or TOA/NPI (2 digits).
	   In neither case does the total equal 17 digits.
Proposal : Reduce the length to 14 digits unless there is a good answer to
	   comment #1.

Comment  : #4
Location : Page 16, x25AdmnMaxActiveCircuits OBJECT-TYPE
Type	 : Major technical
Rationale: The maximum number of active circuits is limited to 4095: Logical
	   Channel 0 is used for network signalling.
Proposal : Change SYNTAX INTEGER TO (0..4095).

Comment	 : #5 (as for #4)
Location : Page 24, x25OperMaxActiveCircuits OBJECT-TYPE

Comment	 : #6
Location : Page 20, x25AdmnNumberPVCs OBJECT-TYPE
Type	 : Major technical
Rationale: Logical Channels are numbered from 0 to 4095.  LC0 is used for
	   network signalling: LC1 to LC4095 are available for PVCs.
Proposal : Change SYNTAX INTEGER to (1..4095).

Comment	 : #7 (as for #6)
Location : Page 28, x25OperNumberPVCs OBJECT-TYPE

Comment	 : #8
Location : Page 34, x25StatInInterrupts OBJECT-TYPE
Type	 : Question
Question : How is the method of counting determined - per PLE or per PVC/VC?
	   How is the method indicated?

Comment	 : #9 (as for #8)
Location : Page 35, x25StatOutInterrupts OBJECT-TYPE

Comment	 : #10
Location : Pages 39-40, x25Channelxxx
Type	 : Major technical
Rationale: Logical Channels are nymbered from 0 to 4095.  LC0 is used for
	   network signalling: LC1 to LC4095 are available.
Proposal : Change SYNTAX INTEGER to (1..4095).

Comment	 : #11
Location : Pages 39-40, x25Channelxxx
Type	 : Question
Question : How is conformance to Logical Channel Assignment rules achieved?
	   Is this implementation dependent?  For example, how is range
	   overlap avoided?

Comment	 : #12 (as for #10)
Location : Page 42, x25CircuitChannel OBJECT-TYPE

Comment	 : #13 (as for #10)
Location : Page 52, x25ClearedCircuitChannel OBJECT-TYPE