RE: [dhcwg] dhcpv6-24: sending Information-request via multicast
"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Wed, 08 May 2002 16:22 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15577 for <dhcwg-archive@odin.ietf.org>; Wed, 8 May 2002 12:22:00 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id MAA12163 for dhcwg-archive@odin.ietf.org; Wed, 8 May 2002 12:22:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA12074; Wed, 8 May 2002 12:20:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA12057 for <dhcwg@optimus.ietf.org>; Wed, 8 May 2002 12:20:17 -0400 (EDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15442 for <dhcwg@ietf.org>; Wed, 8 May 2002 12:20:10 -0400 (EDT)
Received: from mr7.exu.ericsson.se (mr7att.ericy.com [138.85.224.158]) by imr2.ericy.com (8.11.3/8.11.3) with ESMTP id g48GJli17747 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:19:47 -0500 (CDT)
Received: from eamrcnt747.exu.ericsson.se (eamrcnt747.exu.ericsson.se [138.85.133.37]) by mr7.exu.ericsson.se (8.11.3/8.11.3) with SMTP id g48GJkE29712 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:19:46 -0500 (CDT)
Received: FROM eamrcnt761.exu.ericsson.se BY eamrcnt747.exu.ericsson.se ; Wed May 08 11:19:43 2002 -0500
Received: by eamrcnt761.exu.ericsson.se with Internet Mail Service (5.5.2653.19) id <KQMFNJ46>; Wed, 8 May 2002 11:19:43 -0500
Message-ID: <66F66129A77AD411B76200508B65AC69B4D3C0@EAMBUNT705>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: 'Thomas Narten' <narten@us.ibm.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] dhcpv6-24: sending Information-request via multicast
Date: Wed, 08 May 2002 11:19:40 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1F6AC.2785EA20"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Yes, this same issue has given us some concern in 3G standardization. Link-local multicast is always safe to use (but does require a Relay). The general multicast issue for non-link local still haven't been fully resolved (at least to my understanding), so using a site scoped multicast address is potentially a problem until general multicast support is wide-spread. I'd recommend we require the use of the link-local multicast and remove the ability to send the Information-Request to the site scoped multicast. - Bernie -----Original Message----- From: Thomas Narten [mailto:narten@us.ibm.com] Sent: Wednesday, May 08, 2002 11:08 AM To: dhcwg@ietf.org Subject: [dhcwg] dhcpv6-24: sending Information-request via multicast > If the client has an IPv6 address of sufficient scope, the > client MAY choose to send the Information-request message to the > All_DHCP_Servers multicast address. This MAY leaves things very ambiguous. When should they do this? When not? It would be much better to have a clear algorithm the client always follows. Otherwise, you'll get different implementations doing different things, which is probably not good for interoperability. Thomas _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] dhcpv6-24: sending Information-request vi… Thomas Narten
- RE: [dhcwg] dhcpv6-24: sending Information-reques… Bernie Volz (EUD)
- RE: [dhcwg] dhcpv6-24: sending Information-reques… Ralph Droms