Re: [dhcwg] DHCPv6 RAAN options
"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 08 August 2014 16:07 UTC
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03B8E1B2B54 for <dhcwg@ietfa.amsl.com>; Fri, 8 Aug 2014 09:07:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hFZt6_OqB_cM for <dhcwg@ietfa.amsl.com>; Fri, 8 Aug 2014 09:07:00 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AF741B2B6C for <dhcwg@ietf.org>; Fri, 8 Aug 2014 09:07:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s78G70Ma005845; Fri, 8 Aug 2014 09:07:00 -0700
Received: from XCH-PHX-512.sw.nos.boeing.com (xch-phx-512.sw.nos.boeing.com [10.57.37.29]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s78G6qFV005329 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 8 Aug 2014 09:06:52 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.6]) by XCH-PHX-512.sw.nos.boeing.com ([169.254.12.132]) with mapi id 14.03.0181.006; Fri, 8 Aug 2014 09:06:52 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ralph Droms <rdroms.ietf@gmail.com>, Ted Lemon <ted.lemon@nominum.com>
Thread-Topic: [dhcwg] DHCPv6 RAAN options
Thread-Index: Ac+yf+stS7sJIaihTkKQdnTDfuT8QwAPkPgAAA579MD//5LdgIAAdPIw//+RDACAAHTV8IAA4dxQ//67BgD//2x8wAAnctNw///+rmA=
Date: Fri, 08 Aug 2014 16:06:51 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832CED559@XCH-BLV-504.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D9831832CECA61@XCH-BLV-504.nw.nos.boeing.com> <83E91E35-3F30-4659-B4AE-58DD11E74DB6@nominum.com> <2134F8430051B64F815C691A62D9831832CECB68@XCH-BLV-504.nw.nos.boeing.com> <075FB3EE-EA09-4CBD-AFE9-CF14E77ED007@nominum.com> <2134F8430051B64F815C691A62D9831832CECBF5@XCH-BLV-504.nw.nos.boeing.com> <9C369D15-88ED-4E1E-8138-A538760C6FDE@nominum.com> <2134F8430051B64F815C691A62D9831832CECC7B@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831832CECD1A@XCH-BLV-504.nw.nos.boeing.com> <35F4F6CF-7CBC-4935-9E9F-2EC946D7EBB7@nominum.com> <2134F8430051B64F815C691A62D9831832CED2CD@XCH-BLV-504.nw.nos.boeing.com> <65C2A9BF-B153-4BD0-89EF-6D7D8FE459B3@nominum.com> <E5A9495C-DC3F-4CA3-8448-F6F510DA587E@gmail.com>
In-Reply-To: <E5A9495C-DC3F-4CA3-8448-F6F510DA587E@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/xTfwOMYDdNi8roLfsK9FEvbblNM
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] DHCPv6 RAAN options
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Aug 2014 16:07:03 -0000
Hi Ralph, > -----Original Message----- > From: Ralph Droms [mailto:rdroms.ietf@gmail.com] > Sent: Friday, August 08, 2014 8:57 AM > To: Ted Lemon > Cc: Templin, Fred L; dhcwg@ietf.org > Subject: Re: [dhcwg] DHCPv6 RAAN options > > > On Aug 8, 2014, at 10:53 AM 8/8/14, Ted Lemon <ted.lemon@nominum.com> wrote: > > > On Aug 8, 2014, at 10:44 AM, Templin, Fred L <Fred.L.Templin@boeing.com> wrote: > >> Write a little draft that (if approved) updates RFC3315? > > > > That's the right process, if you can't get this into the 3315bis effort. But it would have to go > through the working group. I seem to be talking a lot on this topic, but I'm only one working group > participant, and not an active participant in the 3315bis effort. Have any of the 3315bis people > been following this discussion? Do you have thoughts on the matter? > > If I recall correctly, draft-ietf-dhc-dhcpv6-agentopt-delegate-04 was not published by the working > group because of message transport and ordering concerns: no guarantees that... > > ...messages containing RAAN options will be delivered in order so that the relay agent takes actions > in the correct order > ...transactions containing RAAN options will be forwarded through the correct relay agent; e.g., the > transaction delegating prefix P to device D might be forwarded through relay agent R1, causing R1 to > take action based on that delegation, while the subsequent transaction releasing P might be forwarded > through relay agent R2, which has no knowledge of the original delegation I have a case where the Client can steer its DHCPv6 messaging through a specific relay agent or agents by mapping All_DHCP_Relay_Agents_and_Servers to a unicast L2 address. I think there would probably also be real-world use cases where there is only one relay agent on the link - otherwise, I think PD might have problems in some environments. But, perhaps others would know better. Thanks - Fred fred.l.templin@boeing.com > - Ralph > > PS I'm working from memory w/o bothering to research the mailing list... > > > > _______________________________________________ > > dhcwg mailing list > > dhcwg@ietf.org > > https://www.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] DHCPv6 RAAN options Templin, Fred L
- Re: [dhcwg] DHCPv6 RAAN options Ted Lemon
- Re: [dhcwg] DHCPv6 RAAN options Templin, Fred L
- Re: [dhcwg] DHCPv6 RAAN options Ted Lemon
- Re: [dhcwg] DHCPv6 RAAN options Templin, Fred L
- Re: [dhcwg] DHCPv6 RAAN options Ted Lemon
- Re: [dhcwg] DHCPv6 RAAN options Templin, Fred L
- Re: [dhcwg] DHCPv6 RAAN options Templin, Fred L
- Re: [dhcwg] DHCPv6 RAAN options Ted Lemon
- Re: [dhcwg] DHCPv6 RAAN options Templin, Fred L
- Re: [dhcwg] DHCPv6 RAAN options Ted Lemon
- Re: [dhcwg] DHCPv6 RAAN options Ralph Droms
- Re: [dhcwg] DHCPv6 RAAN options Templin, Fred L
- Re: [dhcwg] DHCPv6 RAAN options Ted Lemon
- Re: [dhcwg] DHCPv6 RAAN options Templin, Fred L
- Re: [dhcwg] DHCPv6 RAAN options Ted Lemon
- Re: [dhcwg] DHCPv6 RAAN options Templin, Fred L
- Re: [dhcwg] DHCPv6 RAAN options Ted Lemon
- Re: [dhcwg] DHCPv6 RAAN options Ralph Droms
- Re: [dhcwg] DHCPv6 RAAN options Templin, Fred L
- [dhcwg] RFC3315(bis) comment Templin, Fred L
- Re: [dhcwg] RFC3315(bis) comment Ted Lemon
- Re: [dhcwg] RFC3315(bis) comment Ted Lemon
- Re: [dhcwg] RFC3315(bis) comment Ralph Droms
- Re: [dhcwg] RFC3315(bis) comment Templin, Fred L
- Re: [dhcwg] RFC3315(bis) comment Ralph Droms
- Re: [dhcwg] RFC3315(bis) comment Templin, Fred L
- Re: [dhcwg] DHCPv6 RAAN options Bernie Volz (volz)
- Re: [dhcwg] DHCPv6 RAAN options Templin, Fred L
- Re: [dhcwg] RFC3315(bis) comment Bernie Volz (volz)
- Re: [dhcwg] RFC3315(bis) comment Templin, Fred L