Re: [atn] Embedding IP information in an IPv6 address (OMNI)

Bob Hinden <> Tue, 20 October 2020 17:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 18CA43A11B0; Tue, 20 Oct 2020 10:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 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, 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 Lm5u36bUzaL4; Tue, 20 Oct 2020 10:05:05 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::433]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 110973A11A9; Tue, 20 Oct 2020 10:05:05 -0700 (PDT)
Received: by with SMTP id b8so3095636wrn.0; Tue, 20 Oct 2020 10:05:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=zxcumxUozZfIWcwdQD+iV/rOT373MsaWyfJELFwEIXc=; b=GhwTyJ3kOe+trYC5jil1T/jTmogV5pStXRWYfVbkLx+RdslC0x4z4+1S1YFLA7JGBt 2n7lRptQ3ELqDJ0WEeVv2kMTC9Ia/xcVR9rPSvZuZrp+mV6cBWFzvMfj16Cv7fz/tIhB hSspmzLIILT1dtvcA6eR/OiEHJh+un3hnS0gCY07gGAqiP6ekEdM8ANb4R7TxX5wX5BI F6cHUUQs1mz60a+j27IwUwXEqyMHABbLjkAP1JZUBr/Er/UZRhXIkm0lSx3M3ejdZLmt WLiaHbqhLklYkLma4f/ZRv5G2ezvEkd3+wiw3+5SD9S3TmOet7xy8WXEmdERG4EvNIIQ bOsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=zxcumxUozZfIWcwdQD+iV/rOT373MsaWyfJELFwEIXc=; b=nFk62dlqX7fQEeiAJmhtzujcgZ2xnOcmI6KP1c9n+D1BQAg++ytBxpheyUKmI56Ppc vpDdlpQ2KDKBVkuhAP4+jcDRTFmGaYYCdvTf2MyFyGbyZ44h0UBats8XDp2KxR0/H3xl cgO6pfXzeeA3Bjm1oLW4FAITYR66w3yfmFm+uTX9c0gcWqJDY2HGwC7fk/fagd2O7Cz6 nLB+k2shE3qGdNITtqL8Zrdq1qFb3SxZdAsKfDJt57DMHKpVaiklgcQQWyPlXmkBVXPM r+9E8XejGjC3jK67SoBagFQub268ic6dmQOeBvjcc8yZyyg97yKQekfzeUupsxZ76c0b n1mw==
X-Gm-Message-State: AOAM532kZsxFS/rMrnkv5skofJZ0TrQ4B9GqGBOvyHWsKX+UKC/3bupU 1lBw9mq1wO2DsGdLmSLPSLEqD9mj1Ik=
X-Google-Smtp-Source: ABdhPJwbGcUS4OUfAnmdxbRdQSU5u3LGuz4+Yma6sknXP7Zf/Yl8xmVoUejEiFUpTy+I3hzfnVubQg==
X-Received: by 2002:adf:f1cd:: with SMTP id z13mr4609137wro.197.1603213503454; Tue, 20 Oct 2020 10:05:03 -0700 (PDT)
Received: from [] ( []) by with ESMTPSA id t7sm3799811wrx.42.2020. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Oct 2020 10:05:02 -0700 (PDT)
From: Bob Hinden <>
Message-Id: <>
Content-Type: multipart/signed; boundary="Apple-Mail=_AF3BC031-A749-4400-9D2B-38E8A2E9163C"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Subject: Re: [atn] Embedding IP information in an IPv6 address (OMNI)
Date: Tue, 20 Oct 2020 10:04:58 -0700
In-Reply-To: <8671.1603129044@localhost>
Cc: Bob Hinden <>, IPv6 List <>, "" <>
To: Michael Richardson <>
References: <> <> <> <8671.1603129044@localhost>
X-Mailer: Apple Mail (2.3445.104.17)
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: Tue, 20 Oct 2020 17:05:07 -0000


> On Oct 19, 2020, at 10:37 AM, Michael Richardson <> wrote:
> Signed PGP part
> Bob Hinden <> wrote:
>> I think most people read SLA as Site-Local Address, especially since
>> you are proposing to use the prefix defined in RFC3513:
> Yes, I keep saying to Fred, that overloading SLA is a recipe for
> misunderstanding.   I think Fred has fixated on those three letters though.

I agree.

> Bob, can you file away all the historical objections to SLA, and can we just
> use another name.

It’s all written down in RFC 3879.

> Fred needs a /10 with some new name and new semantics.
>     Reusing FEC0::/10 is ONE option, given that it's just sitting there rotting.
>     Allocating another prefix that satisfies the needs of OMNI is another.

Trying to reuse the site-local prefix is IMHO not going to have a good outcome, and I don’t think it is necessary.

If OMNI needs its own prefix, it can request that.   The length of that prefix will have to be justified.

Also, I would like to see if Fred can solve the “OMNI” problem using existing addresses, like Global Unicast and ULAs without anything new.   The networks that OMNI is proposing to use could easily get their own provider allocations.