RE: [EXTERNAL] Re: DHCPv6-PD is fine

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Mon, 09 November 2020 19:52 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 AA8953A12EF for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 11:52:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.com
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 jv-i4o5ZM4wR for <ipv6@ietfa.amsl.com>; Mon, 9 Nov 2020 11:52:13 -0800 (PST)
Received: from ewa-mbsout-01.mbs.boeing.net (ewa-mbsout-01.mbs.boeing.net [130.76.20.194]) (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 957413A08C0 for <ipv6@ietf.org>; Mon, 9 Nov 2020 11:52:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ewa-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 0A9Jq7QB029492; Mon, 9 Nov 2020 11:52:11 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1604951531; bh=ZQbq/FifQtPPZGV3AJsqRb0++C12o+iEAfonicpHlTc=; h=From:To:Subject:Date:References:In-Reply-To:From; b=C4zutwtnHK0BsdJcPVNYmu7rsyQZrzS4ncap+jiMu2StGnDMcy7x8tvrqefOtq+ci gYYC3UN+Oej/Qy/u+iYI8TlV9Sa6YiCU2N1BM97ePwbI0tINqcIQz05DQuKka7Pdmx XxXF7U6H986AwR2YK/iX2lyM8gDGkcmwvnipyrOp1nBaKesWexRrm+4LQ1gMe+8TAv YqddkBH3S61Dt+OR5gHe/P74d8vfBK/U5aofrHEwlPNa5+kGceiF8073cA0VjQ+hR0 8gJjnj5DiGk1v2AqJtn7+db4u/iUgjGM6Ky4YulRWRCcIOj4p75sgfsoRAkVhoM36l avVZJiP1opG8A==
Received: from XCH16-07-08.nos.boeing.com (xch16-07-08.nos.boeing.com [144.115.66.110]) by ewa-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 0A9JprRB028728 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Mon, 9 Nov 2020 11:51:54 -0800
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-08.nos.boeing.com (144.115.66.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Mon, 9 Nov 2020 11:51:52 -0800
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2044.004; Mon, 9 Nov 2020 11:51:52 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "tony.whyman" <tony.whyman@mccallumwhyman.com>, Alexandre Petrescu <alexandre.petrescu@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: [EXTERNAL] Re: DHCPv6-PD is fine
Thread-Topic: [EXTERNAL] Re: DHCPv6-PD is fine
Thread-Index: AQHWtszylCA25DTCRH2QjN3TcGyuS6nAMvvw
Date: Mon, 09 Nov 2020 19:51:52 +0000
Message-ID: <f540eeeb97e74c7782f7faa41317bfa8@boeing.com>
References: <350919b2-fe50-a3b8-3f15-4ce32124d495@gmail.com> <202011091916.0A9JGjZg039270@mail2.mwassocs.co.uk>
In-Reply-To: <202011091916.0A9JGjZg039270@mail2.mwassocs.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 002AD38794FAFBDB66A51562B82BAC54062A43812ADC5A60682816E345C9732B2000:8
Content-Type: multipart/alternative; boundary="_000_f540eeeb97e74c7782f7faa41317bfa8boeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/wcPJ9Gi9eFRWkqe75i_XsGN82qQ>
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: Mon, 09 Nov 2020 19:52:22 -0000

Tony,

>We should clarify that while OMNI may include DHCPv6 PD, that is for general use.
>Civil Aviation is using static MNP assignment and is only interested in MNP confirmation
>using the LLA convention.

Yes, that is a very good point and I tried to highlight that in my initial message
when I said: “In OMNI in particular, we have two modes of prefix registration
for mobiles:  1) Static configuration, 2) DHCPv6-PD”. What you are saying above
fits with option 1) Static configuration, and for Civil Aviation where the aircraft
has a uniquely-assigned MNP you are right that this will be the method used.
However, for non-aircraft users that do not have a pre-assigned MNP option
2) DHCPv6-PD may be the only option.

So, you are correct in what you are saying, yes – but I believe a complete
solution needs to support both options.

Fred


From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of tony.whyman
Sent: Monday, November 09, 2020 11:17 AM
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>; ipv6@ietf.org
Subject: Re: DHCPv6-PD is fine

Fred,

We should clarify that while OMNI may include DHCPv6 PD, that is for general use. Civil Aviation is using static MNP assignment and is only interested in MNP confirmation using the LLA convention.

Tony



Sent from my Samsung Galaxy smartphone.


-------- Original message --------
From: Alexandre Petrescu <alexandre.petrescu@gmail.com<mailto:alexandre.petrescu@gmail.com>>
Date: 09/11/2020 16:41 (GMT+00:00)
To: ipv6@ietf.org<mailto:ipv6@ietf.org>
Subject: Re: DHCPv6-PD is fine



Le 09/11/2020 à 17:32, Templin (US), Fred L a écrit :
> DHCPv6-PD is fine - especially for mobiles - so, please stop spreading FUD.
> In OMNI in particular, we have two modes of prefix registration for mobiles:
> 1) Static configuration, 2) DHCPv6-PD - with both methods being driven by
> RS/RA. We have used both methods for many years for prefixes lengths
> in the /56 to /64 range, and I see no reason to get dragged into arguments
> about longer lengths which is a completely different discussion.

Fred, maybe people in the aviation can deploy their own ground networks
to accomodate planes with OMNI interfaces.  At that point it is easy to
say DHCPv6-PD is fine.

But in other places, automobiles for example, one must use the existing
cellular networks.  DHCPv6-PD is not fine there.  It's not FUD.

This discussion has become so complicated that it seems to me impossibly
complex to come up with something that satisfies even a minority.

OMNI and DHCPv6-PD, Ethernet P2P, Variable SLAAC, 464XLAT, Mobile IPv6
with NEMO extensions, and others - are each a potential solution to some
environment.

Alex

>
> Fred
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org<mailto:ipv6@ietf.org>
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org<mailto:ipv6@ietf.org>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------