[IPv6]Re: Reclaiming fec0::/10 (I-D Action: draft-templin-6man-mla-01.txt)

Bob Hinden <bob.hinden@gmail.com> Wed, 22 May 2024 16:18 UTC

Return-Path: <bob.hinden@gmail.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 58F0AC14F685 for <ipv6@ietfa.amsl.com>; Wed, 22 May 2024 09:18:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZlZi2hUKANIZ for <ipv6@ietfa.amsl.com>; Wed, 22 May 2024 09:18:20 -0700 (PDT)
Received: from mail-yw1-x1135.google.com (mail-yw1-x1135.google.com [IPv6:2607:f8b0:4864:20::1135]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6635DC14F618 for <ipv6@ietf.org>; Wed, 22 May 2024 09:18:20 -0700 (PDT)
Received: by mail-yw1-x1135.google.com with SMTP id 00721157ae682-61816fc256dso11591737b3.0 for <ipv6@ietf.org>; Wed, 22 May 2024 09:18:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716394699; x=1716999499; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=8LwYlCnj2GIkllq/3bSxGlRgNK2W8rBlUPCIWC8aihY=; b=I+3olBHYQFur+2Q2w9xtMoG20J+cBYtMRxFv3MwajaMEURXfbXb++st3tzsysPg9Ns lxYKgXlGxt19Pcwm/pxstsWRT8VjoNpEhrD5QA+RPK2cjWv5FYUUT8UXzqocXewykcOK OWWCshajYilHPA52n7wF670VF3zhGbbAWdH85OMv4cc12GMMPb1Gjt2CmP15WFzXZ/mf S9DiTixpyblX/IQQFgJ6zdrYBQebHXGFJzYHG98qQJmjxj/WipiG4AeROEK925F2kgen jN734dbJa+P37llR6KrhL8qTtpBT0OU5UPnXCtv+/SjXyXBl9pp/9Vb86N+Ts0/KkJm5 2DbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716394699; x=1716999499; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=8LwYlCnj2GIkllq/3bSxGlRgNK2W8rBlUPCIWC8aihY=; b=qhjG1S8G0k9vlKOp0ZZ1bw3DBCZMgYtJppSRZ5qrswdLwPuvhpSRCqnGZ1rl3s84pr hgpVTvQUere/spK2m+fZNnU4w+SHbyXpm+D0zqfXhQjyY/gfjn2xj8Nipm1YAFEAZhHI fV3BRA64vfegBGT/cfdNsbbr4pPveIimp+wQIBLq+pakTpluX6BnH1PY3Xo+NKpxRzi3 68JGK6hYmWXcH4MGv20buBXpXNzw00MSj2C3O1gAr7/a5PzgiBGacSQgjwzo4jw+r8+6 ViMwmpr1bMmG5W93yxjJQ1bPjSRmhmuh6XlvoyMong1o1WEcmtpRGsyUXMVV9rbJIVFJ oNdA==
X-Forwarded-Encrypted: i=1; AJvYcCVgQRfaE4VuVLNmtkP4jC7oWSOYNFYinsG7p8hVTZ/Be7YoFSiHwtG6jk7SderS6gB6ogeuXW/E3DWvw3PP
X-Gm-Message-State: AOJu0YwX2+UNMz8Zu8ZgfEKx45NMSpOoizlYVU7PIQSkdm2vBl1wnouQ 7j5dlgezesN5yb1tALKNQE1Z/KuYGV/bKh1RbCGjuVDPPYi893c3+Cw6WQ==
X-Google-Smtp-Source: AGHT+IG4aIvygFYKncd8y0idFtPyi/bk230lg818JkCGn3gRo2/dAVgIbWjPRVyLkBaGdKC57VBL2Q==
X-Received: by 2002:a0d:d912:0:b0:627:ddf1:1497 with SMTP id 00721157ae682-627e4880990mr24106227b3.45.1716394697674; Wed, 22 May 2024 09:18:17 -0700 (PDT)
Received: from smtpclient.apple (99-31-208-116.lightspeed.sntcca.sbcglobal.net. [99.31.208.116]) by smtp.gmail.com with ESMTPSA id 00721157ae682-6209e234816sm58902907b3.26.2024.05.22.09.18.16 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 May 2024 09:18:16 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <4789D445-A4A9-4536-9145-E7470624A02B@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1269B145-152B-43ED-A253-DA3FB45A0997"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Date: Wed, 22 May 2024 09:17:55 -0700
In-Reply-To: <BN0P110MB14201A2CC2A618BD8E74B7F6A3EBA@BN0P110MB1420.NAMP110.PROD.OUTLOOK.COM>
To: "Templin (US), Fred L" <Fred.L.Templin=40boeing.com@dmarc.ietf.org>
References: <171630613439.11714.1949409711399404691@ietfa.amsl.com> <BN0P110MB14203107BB7821B867DC8B4EA3EAA@BN0P110MB1420.NAMP110.PROD.OUTLOOK.COM> <SA2PR11MB49722049B0AB97ABDE614276A9EB2@SA2PR11MB4972.namprd11.prod.outlook.com> <BN0P110MB14201A2CC2A618BD8E74B7F6A3EBA@BN0P110MB1420.NAMP110.PROD.OUTLOOK.COM>
X-Mailer: Apple Mail (2.3774.600.62)
Message-ID-Hash: F7FMF4ZIBVWWWBD6MIASMOZLJASWDMNC
X-Message-ID-Hash: F7FMF4ZIBVWWWBD6MIASMOZLJASWDMNC
X-MailFrom: bob.hinden@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipv6.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Bob Hinden <bob.hinden@gmail.com>, "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>, IPv6 List <ipv6@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [IPv6]Re: Reclaiming fec0::/10 (I-D Action: draft-templin-6man-mla-01.txt)
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Owner: <mailto:ipv6-owner@ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Subscribe: <mailto:ipv6-join@ietf.org>
List-Unsubscribe: <mailto:ipv6-leave@ietf.org>

Fred,

Proposing a new type of scoped IPv6 addresses is fine.   IMHO, there would need to be a lot of justification to warrant that in order to build a consensus in 6MAN and the IETF.

It is extremely premature to discuss what prefix to use for it at this point.

Bob 

p.s. I note your draft has no references to any other MANET work, nor any mention of a new addressing scope.



> On May 22, 2024, at 8:41 AM, Templin (US), Fred L <Fred.L.Templin=40boeing.com@dmarc.ietf.org> wrote:
> 
> Hi Eric,
>  
> RFC3879 IANA considerations says:
>  
>    “IANA is requested to mark the FEC0::/10 prefix as "deprecated",
>    pointing to this document.  Reassignment of the prefix for any usage
>    requires justification via an IETF Standards Action [RFC2434].”
>  
> The -templin draft (now at version -02) has been re-scoped to Standards Track although
> its IANA considerations are currently NULL:
>  
> https://datatracker.ietf.org/doc/draft-templin-6man-mla/
>  
> But, the key thing to realize about this draft is that it proposes a new addressing
> scope for the IPv6 scoped addressing architecture. The addressing scopes are:
>  
> Link-local Addresses
> MANET Local Addresses (formerly site-local)
> Unique Local Addresses
> Global Unicast Addresses
>  
> And, all of these address scopes have their essential uses in the architecture.
>  
> Thank you - Fred
>  
> From: Eric Vyncke (evyncke) <evyncke=40cisco.com@dmarc.ietf.org <mailto:evyncke=40cisco.com@dmarc.ietf.org>>
> Sent: Wednesday, May 22, 2024 8:23 AM
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com <mailto:Fred.L.Templin@boeing.com>>; IPv6 List <ipv6@ietf.org <mailto:ipv6@ietf.org>>
> Subject: [EXTERNAL] Re: Reclaiming fec0::/10 (I-D Action: draft-templin-6man-mla-01.txt)
>  
> EXT email: be mindful of links/attachments.
> 
>  
> Fred
>  
> As an individual contributor (and neither a positive not negative opinion on the draft itself), I think it is rather IANA job to do this kind of allocation.
>  
> -éric
>  
> From: Templin (US), Fred L <Fred.L.Templin=40boeing.com@dmarc.ietf.org <mailto:Fred.L.Templin=40boeing.com@dmarc.ietf.org>>
> Date: Tuesday, 21 May 2024 at 17:52
> To: IPv6 List <ipv6@ietf.org <mailto:ipv6@ietf.org>>
> Subject: [IPv6]Reclaiming fec0::/10 (I-D Action: draft-templin-6man-mla-01.txt)
> 
> Hi, regarding this debate about the various IPv6 prefixes that may or may not be used
> for IPv6 MANET Local Addresses (MLAs), a simple and obvious answer is why not just
> reclaim the prefix fec0::/10 (formerly site-local and deprecated by RFC3879)?
> 
> This new draft version therefore requests reinstatement of fec0::/10 in a new role
> as the top-level prefix for IPv6 MLAs while rendering RFC3879 obsolete.
> 
> Fred
> 
> -----Original Message-----
> From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> <internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>>
> Sent: Tuesday, May 21, 2024 8:42 AM
> To: i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>
> Subject: I-D Action: draft-templin-6man-mla-01.txt
> 
> Internet-Draft draft-templin-6man-mla-01.txt is now available.
> 
>    Title:   IPv6 MANET Local Addresses (MLAs)
>    Author:  Fred L. Templin
>    Name:    draft-templin-6man-mla-01.txt
>    Pages:   7
>    Dates:   2024-05-21
> 
> Abstract:
> 
>    Mobile Ad-hoc NETworks (MANETs) present an interesting challenge for
>    IPv6 addressing due to the indeterminant neighborhood properties of
>    MANET interfaces.  MANET routers must assign an IPv6 address to each
>    MANET interface that is both unique and routable within the MANET but
>    must not be forwarded to other networks.  MANET routers must be able
>    to assign self-generated addresses when there is no infrastructure
>    present on the link that can delegate topology-relative IPv6
>    addresses or prefixes.  This document therefore specifies a means for
>    MANET routers to generate and assign MANET Local Addresses (MLAs).
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-templin-6man-mla/
> 
> There is also an HTMLized version available at:
> https://datatracker.ietf.org/doc/html/draft-templin-6man-mla-01
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-templin-6man-mla-01
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org <http://rsync.ietf.org/>::internet-drafts
> 
> 
> _______________________________________________
> I-D-Announce mailing list -- i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>
> To unsubscribe send an email to i-d-announce-leave@ietf.org <mailto:i-d-announce-leave@ietf.org>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org <mailto:ipv6@ietf.org>
> Administrative Requests:
> --------------------------------------------------------------------
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org <mailto:ipv6@ietf.org>
> Administrative Requests:
> --------------------------------------------------------------------