I AM NOT SHURE THAT MY PREVIOUS MAIL HAVE BEEN DELIVERED,
SO I FEEL FREE TO REPOST IT AGAIN. APOLOGY FOR ANY POSSIBLE
INCOVENIENCE.


After I have been lurker for some time in this mailing list,
I would like to add some comments regarding modem statistic
group.

Chris Rosmans idea to merge incoming and ougoing abnormal
termination is not reasonable to me. Also, looks that nobody
knows what abnormal termination could be! At the moment I can
think of only three events in that category:

	a) disconnection during or after some number of
	unsuccessefull retrains (ref. V58),

	b) disconnection during or immediately after fallback,

	c) disconnection during or immediately after fallforward.

All this means that objects should stay in the group.

Following Steven Walbusser note that
	failures + successes = requests
I would like to rename - mdmStatsOutgoingConnectionsRequests -to
			 mdmStatsOutgoingConnectionsAccepted
and to propose NEW object
			 mdmStatsUnsuccesseefullDialAttempts

mdmStatsUnsuccessefullDialAttempts OBJECT-TYPE
	SYNTAX		Counter
	ACCESS		read-only
	STATUS		current
	DESCRIPTION
		"This object reflects count of performed dials
		failed because modem didn't go off hook, there
		is no dialtone or there is error in dialing
		stored number from NVRAM"
	::= { mdmStats xxx }

This way, we can split connection process failure statistic in to
three stages:
	a) early stage where connection is hardware dependable,
	and where RingsNoAnswer/DTERingsNoAnswer are covering 
	incoming connection and object above outgoing connection,

	b) handshake,sync stage through exisiting objects,
	mdmStatIncomingConnectionsFailures and
	mdmStatOutgoingConnectionsFailures and,

	c) late stage through abnormal termination object.

The number of successefull connections can be calculated from
above objects as
	incomingSuccess = incomingAccepted - incomingAbnormalTerminations
and same for outgoing connections.

Comments are welcome.