RE: [v6ops] New Version Notification for draft-naveen-slaac-prefix-management-00.txt

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Wed, 21 November 2018 16:15 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 D4A85130DF1; Wed, 21 Nov 2018 08:15:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level:
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 0foev7sVvEnd; Wed, 21 Nov 2018 08:15:21 -0800 (PST)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 4C240130DFA; Wed, 21 Nov 2018 08:15:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id wALGFJig046072; Wed, 21 Nov 2018 09:15:19 -0700
Received: from XCH15-06-10.nw.nos.boeing.com (xch15-06-10.nw.nos.boeing.com [137.136.239.219]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id wALGFGkc046045 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 21 Nov 2018 09:15:16 -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.1367.3; Wed, 21 Nov 2018 08:15:15 -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.1367.000; Wed, 21 Nov 2018 08:15:15 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
CC: Naveen Kottapalli <naveen.sarma@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man WG <ipv6@ietf.org>, v6ops list <v6ops@ietf.org>
Subject: RE: [v6ops] New Version Notification for draft-naveen-slaac-prefix-management-00.txt
Thread-Topic: [v6ops] New Version Notification for draft-naveen-slaac-prefix-management-00.txt
Thread-Index: AQHUemuywmmsBQddKEW1fr9sznfAQqVMbZjAgAFwigCAAAgHoIAAmmKA//+EguCAAIuKgP//emnAgACWtgD//4eZIABeBgcLAACJLRAA/OXD0wABCqwgADFvgoAABxla8AAFLlgAABC539A=
Date: Wed, 21 Nov 2018 16:15:15 +0000
Message-ID: <51084397aa90410684c599a2cb1953d0@XCH15-06-08.nw.nos.boeing.com>
References: <154155148848.30897.17784898234776136208.idtracker@ietfa.amsl.com> <a446f89d19954278a8ff09ac9850acd7@XCH15-06-08.nw.nos.boeing.com> <90b22d50-6100-a45c-1663-da80fede8126@gmail.com> <8d3cab11459e4276825c644154fd1b0e@XCH15-06-08.nw.nos.boeing.com> <c31171cd-8de1-d613-60fb-7b4c5d63c831@gmail.com> <CANFmOtmpNjxfpPF-2JL1QMEo2Dkh1owpVtgRxWtgve8-SmxT2A@mail.gmail.com> <7cfcb7b21b1f498e880d00d11b0adfad@XCH15-06-08.nw.nos.boeing.com> <79f505f6-94e6-4570-0e77-d21e0d7c77e1@gmail.com> <CANFmOtmu6jsSx6z3mZRTkM95D-c6i=D7OJTDKgYCuA76-N9qXQ@mail.gmail.com> <995ff903-1df6-225a-8aaa-813db45d1dd2@gmail.com> <CANFmOt=VYMgPTL1SH6hsBCDEtZBAL9v_1k5a2QW0M7A-TRaXPA@mail.gmail.com> <50c10934-6ca8-00d0-73bd-cc6cf19ed213@gmail.com> <CANFmOt=DSi0Y=jBoNJFtFaJHDzFJ+61ZAN0L2a94efnfMBMh1w@mail.gmail.com> <430c94b29f3a49bd9fed24d8d78c6624@XCH15-06-08.nw.nos.boeing.com> <alpine.DEB.2.20.1811211109340.14216@uplift.swm.pp.se> <7ba4a7429e374385856002e361e0324e@XCH15-06-08.nw.nos.boeing.com> <alpine.DEB.2.20.1811211708220.14216@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.20.1811211708220.14216@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.137.12.6]
x-tm-snts-smtp: FB3833028F2DB6CEC81D3C9A75F2A9917F0F8578BAABF9CBB50789C95121FE0B2000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/GQbh_CkDwAkDi6DxuLyZVBJWOtQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 21 Nov 2018 16:15:23 -0000

Hi Mikael,

> -----Original Message-----
> From: Mikael Abrahamsson [mailto:swmike@swm.pp.se]
> Sent: Wednesday, November 21, 2018 8:12 AM
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> Cc: Naveen Kottapalli <naveen.sarma@gmail.com>; Brian E Carpenter <brian.e.carpenter@gmail.com>; 6man WG <ipv6@ietf.org>;
> v6ops list <v6ops@ietf.org>
> Subject: RE: [v6ops] New Version Notification for draft-naveen-slaac-prefix-management-00.txt
> 
> On Wed, 21 Nov 2018, Templin (US), Fred L wrote:
> 
> >> So this proposal has that "built in" (zero lifetime) the same way we do
> >> everything else in ND, whereas DHCPv6 would need extra code for this not
> >> currently existing.
> >
> > I can't understand from this what you are talking about. The DHCPv6-ND
> > approach inherits all of IPv6ND - not only just the features of DHCPv6.
> 
> The subject is about draft-naveen-slaac-prefix-management which is what I
> am commenting on. I am not commenting on your document. I do not like the
> idea to tunnel DHCPv6 messages unchanged in ND/RA.

Sorry you don’t like the idea, but please don’t call it "tunneling" because
that is not what DHCPv6ND is about. It is about a unified service that
combines the best elements of the two services.

> > I don’t understand this either. Anything new that would be brought into
> > IPv6ND would simply be re-creating what DHCPv6 already does.
> 
> Yes.

Good. Then we stick with DHCPv6.

Thanks - Fred

> > That is why 'draft-templin-6man-dhcpv6-ndopt' advocates a unified
> > service of DHCPv6-ND.
> 
> Ok.