Re: [v6ops] link types for both RA and DHCP 'was: control and security of DHCP)

"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 13 January 2014 16:23 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35DED1AE115 for <v6ops@ietfa.amsl.com>; Mon, 13 Jan 2014 08:23:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.739
X-Spam-Level:
X-Spam-Status: No, score=-4.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, 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 Jj4Yyo1n6iLg for <v6ops@ietfa.amsl.com>; Mon, 13 Jan 2014 08:23:11 -0800 (PST)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id E9A761ADFDD for <v6ops@ietf.org>; Mon, 13 Jan 2014 08:23:10 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s0DGN0UG010430; Mon, 13 Jan 2014 08:23:00 -0800
Received: from XCH-PHX-411.sw.nos.boeing.com (xch-phx-411.sw.nos.boeing.com [10.57.37.42]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s0DGMseU009878 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 13 Jan 2014 08:22:54 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.203]) by XCH-PHX-411.sw.nos.boeing.com ([169.254.11.54]) with mapi id 14.03.0158.001; Mon, 13 Jan 2014 08:22:54 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] link types for both RA and DHCP 'was: control and security of DHCP)
Thread-Index: AQHPDrbsGksE3iLXw02DzecWSXac+ZqC2aKg
Date: Mon, 13 Jan 2014 16:22:53 +0000
Message-ID: <2134F8430051B64F815C691A62D98318198549@XCH-BLV-504.nw.nos.boeing.com>
References: <1808340F7EC362469DDFFB112B37E2FCDA31A30EB1@SRVHKE02.rdm.cz> <52CFB8D5.70900@gmail.com> <B54D5283-8880-434A-A3C0-9BFF0081E13B@gmail.com> <20140110.124610.74672987.sthaug@nethelp.no> <60C5513D-B8DA-48D6-82D3-53E148F9F7BA@gmail.com> <52D0157D.6040009@foobar.org> <alpine.DEB.2.02.1401101651580.20074@uplift.swm.pp.se> <52D0180D.6030505@foobar.org> <2134F8430051B64F815C691A62D98318196839@XCH-BLV-504.nw.nos.boeing.com> <52D11B22.2070603@gmail.com>
In-Reply-To: <52D11B22.2070603@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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Subject: Re: [v6ops] link types for both RA and DHCP 'was: control and security of DHCP)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 16:23:13 -0000

Alex,

> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Alexandru Petrescu
> Sent: Saturday, January 11, 2014 2:21 AM
> To: v6ops@ietf.org
> Subject: Re: [v6ops] link types for both RA and DHCP 'was: control and security of DHCP)
> 
> Le 10/01/2014 18:13, Templin, Fred L a écrit :
> > Hi, I am just beginning to get the flavor for this discussion but
> > what I am finding lacking is a consideration for the _different link
> > types_ for which DHCPv6 vs RS/RA would apply. For example, AERO
> > links are link-local only and there is actually very little useful
> > information that could be gotten from an RS/RA exchange that could
> > not just as easily be gotten from NS/NA. There, DHCPv6-PD may be all
> > that is needed.
> >
> > Similarly, on managed network links DHCPv6 gives a central
> > administrative control point for coordinating all of the managed
> > links.
> >
> > So, what are the link types where we would expect to see RS/RA?
> > Unmanaged edge links where visiting nodes come and go at random
> > times? Others?
> 
> Fred,
> 
> The use of DHCP and ND would apply supposedly to the as many links as
> possible.
> 
> The links I am concerned with are: cellular 1G, 2G, 3G, 4G and in the
> future 5G, 869MHZ 'Alarm' IoT/M2M networks, 5.9GHz 802.11p, WiFi, wired
> Ethernet, Fiber to the RSU, satellite, and more.
> 
> The additional links I have heard about here are: wired Ethernet in
> Enterprise, virtual links between virtual machines ('virtual' by name
> but transmitting real packets), and more.
> 
> Yes, some of these links would be termed unmanaged links where visiting
> nodes come and go at random times.  On some of them it would be better
> to just use RA (e.g. WiFi handovers on IPv6 hotspots), on others just
> DHCP (e.g. on constrained links of machine-class devices), and yet on
> others both ND and DHCP (e.g. some visitor networks in Enterprise).
> 
> Sorry if this reads too generic, but I couldnt synthesize it better than
> that.

I think we are seeing it the same way. Thanks for confirming.

Fred
fred.l.templin@boeing.com

> Alex
> 
> >
> > Thanks - Fred fred.l.templin@boeing.com
> > _______________________________________________ v6ops mailing list
> > v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
> >
> >
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops