Re: 64share v2

Ca By <cb.list6@gmail.com> Tue, 10 November 2020 23:37 UTC

Return-Path: <cb.list6@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 F28833A11F8 for <ipv6@ietfa.amsl.com>; Tue, 10 Nov 2020 15:37:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.847
X-Spam-Level:
X-Spam-Status: No, score=-0.847 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 LXXJujmD_BQf for <ipv6@ietfa.amsl.com>; Tue, 10 Nov 2020 15:37:35 -0800 (PST)
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 744D33A1208 for <ipv6@ietf.org>; Tue, 10 Nov 2020 15:37:30 -0800 (PST)
Received: by mail-io1-xd36.google.com with SMTP id r12so308439iot.4 for <ipv6@ietf.org>; Tue, 10 Nov 2020 15:37:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kpj10OMqtaMIL3m+Q4XhILTNXkBxeMWLVjxBG4cugHc=; b=I9+C3LahHRZcCx7/k8vY1mLpp/t/w5c2TdezcbLlRnBvVMi8VDOJIlN0mXJagXjM6n 3J2E++6AVAi0f0CAp9mwyfQEltJY5V5KqevLJv84w52VZ2QcxE0+gjmo8W+RyJD7iDVT 2Fn/qSaURfbS/kYenyjtXCXPO/iu/nF5/K+3lxdYyFKonFHJotDcsuyji1oPuo2AxdUV bh2uh5yjrf//FF4ZCLdLkAOULzf/mP4MaMH3Na4SxWTs+BsQhhUCDKIAOTq93I8RdRX1 PliqOjhn+U+0G3ZUgrkuxVv0ofhWP6j95jpAUt42Rd+t7inQw0fS/4+tgcRG/YZnIchd WdFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kpj10OMqtaMIL3m+Q4XhILTNXkBxeMWLVjxBG4cugHc=; b=BCgkuyy7A8iOvyQvLY9JqtrcEYiphEvFMRDgFcYvYZ0gJrXeDXoDM1GgEUoqdOQcij 1WoHKB1VBzxZfOO6BAKfNO0SLlCtjFCYdk07Mhz6abP/5W9NjlLFrKjgZk+5aBAjYsWJ hBY7Tv46CYboRsMat2fSdf/FKDtFWOMeU0IrB89v20FU/+bhwiP1lQXmVfzhwqEUptol 6hxCg0g941k8WNAAfoelnP2COJ3rw3PuCF/3V09OxntdXVDBt+pMQruhTW91sHRhvXa0 7mxlbXxU/3VxSpvekGuhk46h2y/xtcYZm1SabQWKaZ2/fZFWduZtAGznCgR09g746se2 RexA==
X-Gm-Message-State: AOAM531z8rqEmceeF/iW4sdm4wWnFHBEHmnxMnTnEo0YhPrh+bm5gi0j wCiehR+wVDvXXAKiingzvmYahzDKExb7knmn2/0=
X-Google-Smtp-Source: ABdhPJwF+55y7CQD3vpGO8BCm5GuRTjZ/WvLy1WEgFd3NiacDCgVi7bwtJrXESLGXXLNAtgdhVlnTO5jM/k2K3bEHSw=
X-Received: by 2002:a02:7f16:: with SMTP id r22mr17063056jac.19.1605051449675; Tue, 10 Nov 2020 15:37:29 -0800 (PST)
MIME-Version: 1.0
References: <CAD6AjGR-NE_sJ_jp7nAT6OvNkcdE9qoWuGEiiVW7r9YtsQvbbw@mail.gmail.com> <43ebd660-3df6-bc9c-2ef3-bbfd72a64229@gmail.com> <CAD6AjGQRyDDhVtunyCrWDBABG576oi=5xd1Lmz5=QicOJ6YsNA@mail.gmail.com> <d591a034-b629-cf6a-8211-b9243528db79@gmail.com>
In-Reply-To: <d591a034-b629-cf6a-8211-b9243528db79@gmail.com>
From: Ca By <cb.list6@gmail.com>
Date: Tue, 10 Nov 2020 15:37:18 -0800
Message-ID: <CAD6AjGQaMCS+T-6pV=c7M_DL=qCYSdqrsemE8vUYYyqm5Rv32A@mail.gmail.com>
Subject: Re: 64share v2
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: 6man <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000081136f05b3c929b0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/j81F6jzPCRQaf_jgxhfxaRIkW8w>
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: Tue, 10 Nov 2020 23:37:37 -0000

On Tue, Nov 10, 2020 at 3:06 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 11-Nov-20 11:03, Ca By wrote:
> >
> >
> > On Tue, Nov 10, 2020 at 1:49 PM Brian E Carpenter <
> brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> >
> >     On 10-Nov-20 21:10, Ca By wrote:
> >     > Folks,
> >     >
> >     > In an effort to progress the conversation, i created a simple and
> rough pre-00 i-d (as ietf is not accepting submissions now) for your review
> and comment
> >     >
> >     > https://pastebin.com/duyYRkzG
> >
> >     I'm having difficulty reconciling that with what I read at:
> >
> https://mailarchive.ietf.org/arch/msg/v6ops/0d7lSiP_78td3vWBlMnVvmp7UAo/
> >
> >
> >     If that email is correct, the 3GPP model is tightly bound to
> >     the /64 boundary and to the notion of giving a single address
> >     and predefined Interface ID to the UE.
> >
> >
> >
> > This is not a correct summary. I believe rfc6459 describes it clearly.
> The ue receives an off-link  /64, the iid is simply a hint and typically
> not used. This is why rfc7278 works.
>
> Thanks for the clarification.
>
> >
> >     Also, since /64
> >     is still fixed by the addressing architecture, and RA PIOs
> >     are constrained by that architecture, I don't understand how
> >     a UE can be "given a prefix such as a /56 using RA".
> >
> >
> > The i-d is to requests the 3gpp to make a change to allow < 64 via RA
>
> RFC 6459 says "The 3GPP network allocates each default bearer a
> unique /64 prefix" but doesn't seem to explain how that prefix is
> conveyed to the UE. It does say that the suggested IID is conveyed
> by "layer-2 signaling". If the allocated prefix is only conveyed
> by an RA/PIO there is something unconventional going on, i.e. the
> UE is allowed to deduce *from the RA* that it owns the entire /64,
> which is not all what applies on a conventional LAN. (Yes, I do see
> how that enables RFC 7278, but this unconventional semantic is
> not all obvious from RFC 6459.)
>

Yes, it is conveyed only using RA

On the wire(less), it looks like this (image of pcap)

https://imgur.com/a/p6dBy3d


> So if that's right, I think we do have a problem. If we (=IETF+3GPP)
> decide to allow <64 prefixes in RA/PIO during the establishment of
> a PDP context, that seems to be not only an unconventional use
> of RA but also one that directly contravenes the /64 rule in the
> addressing architecture.
>
> I'm not against either of those things, but I think some very
> explicit wording is needed to explain what's going on and how it
> is different from a conventional LAN.
>
>    Brian
>
> >
> >
> >
> >     Perhaps someone familiar with 3GPP internals, e.g. the authors
> >     of RFC6459, can comment?
> >
> >     Regards
> >         Brian
> >
>
>