IETF Logo Mail Archive

[dhcwg] Sending SOLICIT/CONFIRM/REBIND messages to a relay-agent unicast address

"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 14 June 2006 20:13 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fqbjz-0000MR-1q; Wed, 14 Jun 2006 16:13:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fqbjx-0000L9-Fa for dhcwg@ietf.org; Wed, 14 Jun 2006 16:13:25 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56] helo=stl-smtpout-01.ns.cs.boeing.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fqbjw-0005FL-81 for dhcwg@ietf.org; Wed, 14 Jun 2006 16:13:25 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216]) by stl-smtpout-01.ns.cs.boeing.com (8.13.6/8.13.6/TEST_SMTPIN) with ESMTP id k5EKDNJM009988 for <dhcwg@ietf.org>; Wed, 14 Jun 2006 15:13:23 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id k5EKDNB25249 for <dhcwg@ietf.org>; Wed, 14 Jun 2006 13:13:23 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Jun 2006 13:13:17 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 14 Jun 2006 13:12:27 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1818CCD@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB2101BE4527@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Sending SOLICIT/CONFIRM/REBIND messages to a relay-agent unicast address
Thread-Index: AcZz2jZAOPbWpR/1TU2nGHP0gKb/OQcDstUwAACEdyA=
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: dhcwg@ietf.org
X-OriginalArrivalTime: 14 Jun 2006 20:13:18.0165 (UTC) FILETIME=[F9BEB050:01C68FEE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Subject: [dhcwg] Sending SOLICIT/CONFIRM/REBIND messages to a relay-agent unicast address
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

If a DHCPv6 client is pre-configured with a list of IP addresses
of DHCPv6 relay agents on the link, and if the client knows that
there are no DHCPv6 servers on the link, can the client send
SOLICIT/CONFIRM/REBIND messages to the unicast address of one
of the relay agents?

If not, is this something that can be specified "in a document
that describes how IPv6 is carried over a specific type of link"
as suggested by ([RFC3315], Section 13)?

Fred
fred.l.templin@boeing.com  

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

v2.46.0 | Report a Bug | By Email | System Status