Re: I-D Action: draft-templin-duid-ipv6-01.txt

"Templin (US), Fred L" <> Fri, 15 January 2021 20:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1D9CD3A11A9; Fri, 15 Jan 2021 12:54:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.117
X-Spam-Status: No, score=-2.117 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_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Z2nQxwK5OMpL; Fri, 15 Jan 2021 12:54:02 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 377D23A11A8; Fri, 15 Jan 2021 12:54:02 -0800 (PST)
Received: from localhost (localhost []) by (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 10FKrvOM012459; Fri, 15 Jan 2021 15:54:00 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=boeing-s1912; t=1610744040; bh=Kkv9y1vlsxri6ycOUvCW7NQ7QhBewiWOUGaVpS7A3QE=; h=From:To:CC:Subject:Date:From; b=mPI70WB8pCa4U+ygfF4fKTtxbQs41kCZTFiOUyipGwG9fu/n9qj4PaN7anp1H1dZD HJoX9R6MS+AXzvY91IZIleqxCS+YCyx6XESbbozVJZ3vDUwpPsBwgCSRTBuIXGw9A7 8VtOKJbzQgYMFgaGuapd7qEGAFbZZTnKxmnpJWcjFjKaOw8l4Q1oPyKQbobqB0aiJV VmIvh4vlpwklA/1hhU4bD0tx64C6wndjf82bXgxHhQm+7FR8IC45q+vDIN5XbG2RO5 jDgnbKey1e2lN0aqsT+QFpBsfYC0nakjuX+221/jQusFIf/zh/PHpQPjSI6t6EhGq9 osWyX0b+PkCiQ==
Received: from ( []) by (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 10FKrpa9012402 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Fri, 15 Jan 2021 15:53:51 -0500
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Fri, 15 Jan 2021 12:53:50 -0800
Received: from ([fe80::1522:f068:5766:53b5]) by ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2044.004; Fri, 15 Jan 2021 12:53:50 -0800
From: "Templin (US), Fred L" <>
To: Ted Lemon <>
CC: "Bernie Volz (volz)" <>, Bob Hinden <>, dhcwg <>, IPv6 List <>, "Dickson (US), Sean M" <>
Subject: Re: I-D Action: draft-templin-duid-ipv6-01.txt
Thread-Topic: I-D Action: draft-templin-duid-ipv6-01.txt
Thread-Index: AdbrfttkOSxT/RteQveHQZFWn6tS6w==
Date: Fri, 15 Jan 2021 20:53:50 +0000
Message-ID: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
x-tm-snts-smtp: 57C00B2F70F82C8D865A63B8BAADC42C0CD99E531B59E82B181ABA712DF2DC002000:8
Content-Type: multipart/alternative; boundary="_000_934f21434d854a9babcfc04c2699968bboeingcom_"
MIME-Version: 1.0
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 15 Jan 2021 20:54:04 -0000

Ted, the allocation policy for the Private Enterprise Number (PEN) code for users
of DUID-EN is not Standards Track; anyone and their brother can easily obtain a
PEN code by filling out a simple form:

I did one for “LinkUp Networks”, but that is not in any way tied to a Standards
Track RFC. IANA did not even ask me any questions; they simply allocated the
code for free. So, as far as standards status goes, an arbitrary PEN code has no
standing while the global IPv6 unicast address space has full Internet standards
status according to RFCs 4291 and 8200. I would therefore see it as a major
DOWNREF to entrust the entire IPv6 address space to any random person
who decided to register a PEN code.

That, plus I don’t want to carry around the extra 4 bytes for a PEN code…


From: Ted Lemon []
Sent: Friday, January 15, 2021 12:31 PM
To: Templin (US), Fred L <>
Cc: Bernie Volz (volz) <>; Bob Hinden <>; dhcwg <>; IPv6 List <>; Dickson (US), Sean M <>
Subject: [EXTERNAL] Re: I-D Action: draft-templin-duid-ipv6-01.txt

On Jan 15, 2021, at 3:25 PM, Templin (US), Fred L <<>> wrote:
using DUID-EN with some
arbitrary PEN code to encode the entire global IPv6 unicast address space would
IMHO be an unacceptable DOWNREF.

You said this before. I don’t understand what this means. DUID-EN is in a standards track RFC. How is this a DOWNREF? And why use an arbitrary enterprise number?