A SIPP system discovery question

DEC NoS <grehan@ozrock.enet.dec.com> Wed, 27 April 1994 22:10 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12606; 27 Apr 94 18:10 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa12602; 27 Apr 94 18:10 EDT
Received: from Sun.COM by CNRI.Reston.VA.US id aa16703; 27 Apr 94 18:10 EDT
Received: from Eng.Sun.COM (zigzag.Eng.Sun.COM) by Sun.COM (sun-barr.Sun.COM) id AA20590; Wed, 27 Apr 94 15:03:57 PDT
Received: from sunroof2.Eng.Sun.COM by Eng.Sun.COM (4.1/SMI-4.1) id AA13931; Wed, 27 Apr 94 15:02:55 PDT
Received: by sunroof2.Eng.Sun.COM (4.1/SMI-4.1) id AA04193; Wed, 27 Apr 94 15:03:51 PDT
Received: from Eng.Sun.COM (engmail1) by sunroof2.Eng.Sun.COM (4.1/SMI-4.1) id AA04187; Wed, 27 Apr 94 15:03:50 PDT
Received: from Sun.COM (sun-barr) by Eng.Sun.COM (4.1(1/24/94)/SMI-4.1) id AA11296; Wed, 27 Apr 94 15:02:23 PDT
Received: from inet-gw-2.pa.dec.com by Sun.COM (sun-barr.Sun.COM) id AA10442; Tue, 26 Apr 94 23:18:02 PDT
Received: from us3rmc.bb.dec.com by inet-gw-2.pa.dec.com (5.65/21Mar94) id AA23578; Tue, 26 Apr 94 23:14:39 -0700
Received: from ozrock.enet by us3rmc.bb.dec.com (5.65/rmc-22feb94) id AA24921; Tue, 26 Apr 94 23:14:19 -0700
Message-Id: <9404270614.AA24921@us3rmc.bb.dec.com>
Received: from ozrock.enet; by us3rmc.enet; Tue, 26 Apr 94 23:14:20 PDT
Date: Tue, 26 Apr 94 23:14:20 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: DEC NoS <grehan@ozrock.enet.dec.com>
To: sipp@sunroof2.eng.sun.com
Apparently-To: sipp@sunroof2.eng.sun.com
Subject: A SIPP system discovery question
X-Orig-Sender: sipp-request@sunroof.eng.sun.com

 I have a query on the system discovery draft that maybe Bill Simpson
or others could answer.

 Since solicitation messages do not contain a lifetime, what sort of
lifetime should be attached to the Media-Access extension contained
in these messages ?

 Section 2.1.4. implies that the Media-Access extension in the
solicitation packets should be used to update the end-node cache
to avoid another solicitation/advertisement exchange. If this
is the case (and I think that it should be), should the solicitation
messages contain all of the information and extensions that an
advertisement has (such as a lifetime), rather than just the 
Media-Access extension ?

 And if this could then the case, do the solicitation/advertisement
messages essentially become the same, with the only difference 
being that one contains a multicast destination while the other
contains a unicast destination (with router messages being a 
slightly special case) ?