IETF Logo Mail Archive

RE: L=0 [was draft-pioxfolks-6man-pio-exclusive-bit-02.txt]

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 01 February 2018 16:29 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C31A112EB42 for <ipv6@ietfa.amsl.com>; Thu, 1 Feb 2018 08:29:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 WLE18iymYgw3 for <ipv6@ietfa.amsl.com>; Thu, 1 Feb 2018 08:29:52 -0800 (PST)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7335E12EC04 for <ipv6@ietf.org>; Thu, 1 Feb 2018 08:29:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id w11GTp0X053981; Thu, 1 Feb 2018 09:29:51 -0700
Received: from XCH15-06-10.nw.nos.boeing.com (xch15-06-10.nw.nos.boeing.com [137.136.239.219]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id w11GToPd053966 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 1 Feb 2018 09:29:50 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-10.nw.nos.boeing.com (2002:8988:efdb::8988:efdb) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Thu, 1 Feb 2018 08:29:49 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1347.000; Thu, 1 Feb 2018 08:29:49 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, Lorenzo Colitti <lorenzo@google.com>
CC: 6man WG <ipv6@ietf.org>
Subject: RE: L=0 [was draft-pioxfolks-6man-pio-exclusive-bit-02.txt]
Thread-Topic: L=0 [was draft-pioxfolks-6man-pio-exclusive-bit-02.txt]
Thread-Index: AQHTmzqNkuf0FCoeaU2KIGEqD3UNlqOP2TwAgAAPNwD//9LbIA==
Date: Thu, 01 Feb 2018 16:29:49 +0000
Message-ID: <658076313dd5488080a596717d00c19b@XCH15-06-08.nw.nos.boeing.com>
References: <91953634-9B4A-405B-AB36-FBB2079A0A40@gmail.com> <CAO42Z2worXnmmTEx7_g_R1kuoywc40O0Yo7b6Bf4cdLJ70=rFA@mail.gmail.com> <alpine.DEB.2.20.1801300611070.8884@uplift.swm.pp.se> <CAO42Z2ydjfsvL0ita9TW8Hgrqfd30E6BSPAf0DmLn0cZaCt3tg@mail.gmail.com> <alpine.DEB.2.20.1801311042240.8884@uplift.swm.pp.se> <alpine.DEB.2.20.1801311125400.8884@uplift.swm.pp.se> <91E4B0D5-BB27-4961-883B-0774729F1A83@employees.org> <CAKD1Yr23G+rz7woT1K504UEb2=sQGJd2p_CcQogLA5BbmTomZA@mail.gmail.com> <32FB86D8-235A-434F-A20C-6624FB7C3CE2@employees.org> <CAKD1Yr1oTmBOQR7YJnJV3S9_NG54sA-+phzRMwPT5qQcF1nKPA@mail.gmail.com> <alpine.DEB.2.20.1801311327410.8884@uplift.swm.pp.se> <CAKD1Yr04NV0+r1V1XnOo9XUu2GF_RiVPN6pqM0pJ0a68=mC9Zw@mail.gmail.com> <alpine.DEB.2.20.1801311402350.8884@uplift.swm.pp.se> <CAKD1Yr2cTdK+kkojHa5qPOO4VyT=jW1pmJmf=uXSrdif404iQQ@mail.gmail.com> <alpine.DEB.2.20.1802010954270.8884@uplift.swm.pp.se> <CAKD1Yr28iU=jCBv7dy4D8gyeL=uB5hFu-YhGOKPiih9sykZ1GQ@mail.gmail.com> <alpine.DEB.2.20.1802011138010.8884@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.20.1802011138010.8884@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/jV-XYXPLkAzt81Lo43mUjMACsfU>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Feb 2018 16:29:55 -0000

Hi,

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Mikael Abrahamsson
> Sent: Thursday, February 01, 2018 3:04 AM
> To: Lorenzo Colitti <lorenzo@google.com>
> Cc: 6man WG <ipv6@ietf.org>
> Subject: Re: L=0 [was draft-pioxfolks-6man-pio-exclusive-bit-02.txt]
> 
> On Thu, 1 Feb 2018, Lorenzo Colitti wrote:
> 
> > Are you talking about something that's not standardized? All the SAVI
> > RFCs that I have seen track individual addresses.
> 
> You're right, it seems work was started but never finished:
> 
> https://www.ietf.org/proceedings/77/slides/savi-1.pdf
> 
> I thought this was completed. Pity.
> 
> https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipv6_fhsec/configuration/15-s/ip6f-15-s-book/ip6-src-guard.html
> 
> It looks like Cisco has support for DHCPv6-PD source guard, but it looks
> like this was never standardized in the IETF (SAVI). I'm sure other
> vendors have this functionality as well, as this is an obvious requirement
> from potential customers with the need of these first-hop security
> features.
> 
> It's similar to the fact that DHCPv6 relay snooping and route installation
> for PD was never standardized, but most vendors have this functionality
> anyway.

DHCPv6 relay snooping and route installation does not need to be
standardized, as they are implementation details. As you say, most
vendors have figured out how to do it in their own implementation
specific fashions. For example, on linux "ip route add" works fine.

If we wanted something standardized, it would be Relay Agent
Assignment Notification (RAAN):

https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-agentopt-delegate/

But, efforts to get that standardized fizzled on multiple occasions simply
because there was no perceived need for it.

Thanks - Fred
 
> I have several times in the past few years brought up SAVI and that we
> should take this into account when we design protocols, but I have been
> met with no interest what so ever so far. I still haven't given up hope
> that this will change, because I think it's an important functionality to
> have, even if some people think it's a protocol layer violation (which is
> one of the arguments I have been met with before).
> 
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email