Reply to routingInformation and routedUA

Kevin Jordan <> Tue, 17 January 1995 18:28 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa05444; 17 Jan 95 13:28 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa05440; 17 Jan 95 13:28 EST
Received: from by CNRI.Reston.VA.US id aa10430; 17 Jan 95 13:28 EST
Received: by; Tue, 17 Jan 95 12:28:07 -0600
X-From: Tue Jan 17 12:28 CST 1995
Received: from localhost by; Tue, 17 Jan 95 12:28:04 -0600
To: MHS Mail <>
cc: MHSDS list <>
Subject: Reply to routingInformation and routedUA
In-reply-to: Your message of "Tue, 17 Jan 95 17:14:42 +0700" <9501171614.AA24310@karl.wtk.suresnes>
Date: Tue, 17 Jan 95 12:28:02 -0600
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Kevin Jordan <>
Message-Id: <>

> I am currently working on the MHSDS draft dated May 1995.

I assume you are referencing the draft dated November 1994, which -expires-
in May 1995.  This draft has been progressed onto the Experimental Internet
Standard track and should be assigned an RFC number very soon.

> I have a question regarding the routingInformation and
> routedUA object class definition. The attribute
> nonDeliveryInformation is defined in both classes and the
> routedUA is a sub class of the routingInformation object
> class. Where is the mistake : should this attribute be defined
> in routingInformation or only in routedUA object class.

It may have been redundant to define nonDeliveryInformation in the
routedUA class, but this is not a serious error.  Subclass definitions may
contain attributes which are also defined in their superclasses.