Re: Restart/Entity Domain usage/specification?

"Steven L. Waldbusser" <sw0l+@andrew.cmu.edu> Wed, 04 November 1992 08:59 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00551; 4 Nov 92 3:59 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa00547; 4 Nov 92 3:59 EST
Received: from thumper.bellcore.com by CNRI.Reston.VA.US id aa01659; 4 Nov 92 4:00 EST
Received: by thumper.bellcore.com (4.1/4.7) id <AA23743> for ietf-archive@nri.reston.va.us; Wed, 4 Nov 92 04:00:13 EST
Received: from andrew.cmu.edu by thumper.bellcore.com (4.1/4.7) id <AA23736> for /usr/lib/sendmail -oi -fowner-snmp2 X-snmp2; Wed, 4 Nov 92 04:00:12 EST
Received: by andrew.cmu.edu (5.54/3.15) id <AA21663@X> for snmp2@thumper.bellcore.com; Wed, 4 Nov 92 04:00:06 EST
Received: via switchmail; Wed, 4 Nov 1992 04:00:05 -0500 (EST)
Received: from zeus.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/service/mailqs/q002/QF.8ext3X600WAr80Uu0e>; Wed, 4 Nov 1992 03:59:16 -0500 (EST)
Received: from zeus.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/usr5/sw0l/.Outgoing/QF.Aext3Va00WArImxKAd>; Wed, 4 Nov 1992 03:59:13 -0500 (EST)
Received: from Messages.7.15.N.CUILIB.3.45.SNAP.NOT.LINKED.zeus.andrew.cmu.edu.sun4c.411 via MS.5.6.zeus.andrew.cmu.edu.sun4c_411; Wed, 4 Nov 1992 03:59:13 -0500 (EST)
Message-Id: <kext3VS00WArEmxK0R@andrew.cmu.edu>
Date: Wed, 4 Nov 1992 03:59:13 -0500 (EST)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Steven L. Waldbusser" <sw0l+@andrew.cmu.edu>
To: snmp2@thumper.bellcore.com, mlk%bir.UUCP@mathcs.emory.edu
Subject: Re: Restart/Entity Domain usage/specification?
In-Reply-To: <0D15DDF1.hpcsot@bir.bir.com>
References: <0D15DDF1.hpcsot@bir.bir.com>

Excerpts from mail: 3-Nov-92 Restart/Entity Domain usage.. Michael L.
Kornegay@math (203)

> These two optional domains need to be defined more specifically.

> Maybe some examples.

> They do not have a serialization encoding.

There is no serialization encoding for these domains.  One will always
communicate to them over a network through a proxy party with a
serialization encoding (UDP, IPX, AppleTalk, OSI, ...).

I can think of a couple of things that will make this text more clear on
the first reading.  I'll propose some additional text.


Steve