MIME-Version: 1.0
References: <171656605305.48682.1088678194134276372@ietfa.amsl.com>
 <CAFU7BAQGyuEJ1iLSEyKQE__kmihV_TgEOmPyepdt08yEFTuh1Q@mail.gmail.com>
 <C5F7334E-7146-419D-9701-3C3E81EF3F1F@consulintel.es>
 <CAFU7BASYWz6Op3xo5kkcoJoLgFCFwgivefeMZ9hm5b3P8PZ-BA@mail.gmail.com>
 <8DB094F1-037B-40D0-9970-7B2A792CAA8C@consulintel.es>
In-Reply-To: <8DB094F1-037B-40D0-9970-7B2A792CAA8C@consulintel.es>
From: Jen Linkova <furry13@gmail.com>
Date: Fri, 5 Jul 2024 19:24:11 +1000
Message-ID: 
 <CAFU7BATQV3-L79mQVMvEG9=Nf+x3a+7QUxVmu_Phfpscgi=AFg@mail.gmail.com>
To: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: M7PNWF37XES6U53LADMTJTA4OG5TXUTU
CC: V6 Ops List <v6ops@ietf.org>
Precedence: list
Subject: =?utf-8?q?=5Bv6ops=5D_Re=3A_New_Version_Notification_for_draft-link-v6ops-cl?=
	=?utf-8?q?aton-03=2Etxt?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/v6ops/oDpkPCVq_pLhvcAuO4FQC6Fsl9E>

Hi Jordi,

On Mon, Jul 1, 2024 at 7:43=E2=80=AFAM jordi.palet@consulintel.es
<jordi.palet@consulintel.es> wrote:
> >> Then, instead ensure that is well understood that the CLAT can be also=
 in a CE:
> >>   *  CLAT is performed by the host itself.
> >> So:
> >>   *  CLAT is performed by the host itself or a CE.
> >> or
> >>   *  CLAT is performed by the node (host or router).
> >
> > This paragraph is describing the =E2=80=9CWireless=E2=80=9D mode (CLAT =
on a host)
> > outside of 3GPP - in Wi-Fi hotspots, enterprise networks etc. So in
> > this scenario it=E2=80=99s important that CLAT is performed by a host, =
not a
> > CE router.
>
> The point is that there are UEs that are CE. For example, a well known ca=
se is T-Mobile that provided a CE with 464XLAT for broadband provisioning, =
as they don=E2=80=99t have GPON, etc.

How about we say ' CLAT is performed by the UE'?

> >> May be we need to consider defining a maximum delay instead of "The de=
lay is implementation specific=E2=80=9D.
> >
> > If we want to do this, I=E2=80=99d rather specify the default value and=
 let
> > implementations choose whether they want to use it or not. I guess the
> > delay shall be comparable with an RTT between the client and the DHCP
> > server(s) - but I do not know what value to choose here. Any
> > suggestions?
>
> The reason why we needed HE was because the fallback delay from IPv6 to I=
Pv4 was not predefined =E2=80=A6 I think we should avoid those type of situ=
ations.
>The problem is that the RTT to DHCP servers can vary a lot in different co=
ntexts.

Exactly. So, for example, why shall we prevent the node from
remembering the median RTT for previous connections to the given
network, and using it as a timeout value?

If we are going to define that maximum delay, what do you think it should b=
e?

--=20
Cheers, Jen Linkova