Re: [dhcwg] Sending SOLICIT/CONFIRM/REBIND messages to a relay-agentunicast address
Thomas Narten <narten@us.ibm.com> Thu, 15 June 2006 02:15 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FqhOA-00059Z-Bf; Wed, 14 Jun 2006 22:15:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FqhO9-00059U-NJ for dhcwg@ietf.org; Wed, 14 Jun 2006 22:15:17 -0400
Received: from e2.ny.us.ibm.com ([32.97.182.142]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FqhO7-0003dM-Dk for dhcwg@ietf.org; Wed, 14 Jun 2006 22:15:17 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e2.ny.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k5F2FFqI027316 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <dhcwg@ietf.org>; Wed, 14 Jun 2006 22:15:15 -0400
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay02.pok.ibm.com (8.13.6/NCO/VER7.0) with ESMTP id k5F2FEll242396 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dhcwg@ietf.org>; Wed, 14 Jun 2006 22:15:14 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k5F2FEYM018857 for <dhcwg@ietf.org>; Wed, 14 Jun 2006 22:15:14 -0400
Received: from cichlid.raleigh.ibm.com (sig-9-76-131-84.mts.ibm.com [9.76.131.84]) by d01av02.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k5F2FDJj018809; Wed, 14 Jun 2006 22:15:14 -0400
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.13.6/8.12.5) with ESMTP id k5F2FScb010536; Wed, 14 Jun 2006 22:15:30 -0400
Message-Id: <200606150215.k5F2FScb010536@cichlid.raleigh.ibm.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: [dhcwg] Sending SOLICIT/CONFIRM/REBIND messages to a relay-agentunicast address
In-reply-to: <39C363776A4E8C4A94691D2BD9D1C9A1818CD0@XCH-NW-7V2.nw.nos.boeing.com>
References: <39C363776A4E8C4A94691D2BD9D1C9A1818CD0@XCH-NW-7V2.nw.nos.boeing.com>
Comments: In-reply-to "Templin, Fred L" <Fred.L.Templin@boeing.com> message dated "Wed, 14 Jun 2006 15:58:37 -0700."
Date: Wed, 14 Jun 2006 22:15:28 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: dhcwg@ietf.org
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
Fred, What problem are you trying to solve? You seem to be asking a narrow "legalistic" question about whether something is technically legal according to the RFC. I would much prefer understanding what you are trying to do (and why) before answering whether what you are asking is legal. (I.e., maybe it is technically legal, but shouldn't be, or maybe it's technically not legal, but given the problem at hand, could be made legal.) In particular: > If a DHCPv6 client is pre-configured with a list of IP addresses > of DHCPv6 relay agents on the link, This statement alone gives me heartburn because the whole point of DHC is to not have to hardwire in something like the addresses of the relay agents. I.e., the hardwired part is the multicast addresses already used in the base DHC protocol. > 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)? Perhaps. But could you please describe the problem and your proposed solution, so we have context for answering your specific questions? Thomas _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- RE: [dhcwg] dhc wg last call on "DHCP Relay Agent… Bernie Volz (volz)
- RE: [dhcwg] dhc wg last call on "DHCP Relay Agent… Bernie Volz (volz)
- Re: [dhcwg] dhc wg last call on "DHCP Relay Agent… David W. Hankins
- RE: [dhcwg] dhc wg last call on "DHCP Relay Agent… Bernie Volz (volz)
- Re: [dhcwg] dhc wg last call on "DHCP Relay Agent… Ted Lemon
- [dhcwg] Sending SOLICIT/CONFIRM/REBIND messages t… Templin, Fred L
- RE: [dhcwg] dhc wg last call on "DHCP Relay Agent… Bernie Volz (volz)
- RE: [dhcwg] Sending SOLICIT/CONFIRM/REBIND messag… Templin, Fred L
- RE: [dhcwg] Sending SOLICIT/CONFIRM/REBIND messag… Templin, Fred L
- Re: [dhcwg] Sending SOLICIT/CONFIRM/REBIND messag… Thomas Narten
- Re: [dhcwg] dhc wg last call on "DHCP Relay Agent… Thomas Narten
- Re: [dhcwg] dhc wg last call on "DHCP Relay Agent… Ted Lemon
- RE: [dhcwg] Sending SOLICIT/CONFIRM/REBIND messag… Templin, Fred L
- Re: [dhcwg] Sending SOLICIT/CONFIRM/REBIND messag… David W. Hankins
- RE: [dhcwg] Sending SOLICIT/CONFIRM/REBIND messag… Templin, Fred L
- Re: [dhcwg] dhc wg last call on "DHCP Relay Agent… Ralph Droms