--o41d8xLWOaLD8vYh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 07, 2002 at 04:10:31PM -0700, Chris Jones wrote:

> On Mon, Jan 07, 2002 at 02:49:53PM -0800, Dennis Ferguson wrote:
>=20
> > > Sometimes, the DHCPOFFER message needs to be sent broadcast back to
> > > the client.  In other words, the dest IP address is 0xffffffff, and
> > > the dest MAC address is the client's.  I don't think you can do this
> > > with UDP.
> >=20
> > I'd challenge you to quote the text in RFC 2131 which requires this.
> > This is such a huge layering and semantic violation that I don't think
> > anyone would even dare to write it down, let alone have it remain in
> > the document all the way to draft standard status, even if it could
> > otherwise be widely implemented.

Hmm.  I see; you're asserting that the message should either be
unicast to both MAC and IP addresses, or it should be broadcast to
both.  (Please excuse the sloppy terminology.)  That certainly makes
sense, and I haven't read the RFC closely enough to have an opinion
either way on that.

Chris

--=20
---------------------------------------------------- chris@cjones.org
Chris Jones                                          Mad scientist at large
  www.netbsd.org www.postgresql.org www.schemers.org www.python.org

--o41d8xLWOaLD8vYh
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (NetBSD)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjw6Kz4ACgkQDPY2T8RzaD8aQgCffMOYtRA1qAxmzI7P5QsIjGlJ
bgEAn11updGoMM3zXc8Iwx6W4mKlWUgc
=iCz7
-----END PGP SIGNATURE-----

--o41d8xLWOaLD8vYh--