Hello Jen That's great. I realize that I'm asking you to state the perfectly obvious for someone who designs a phone in 2020. Still that context scopes the applicability of the draft, which is a lot more than that. Ideally that definition would indicate that the IPv6 only mode may include: 1) accessing IPv4 services via a fully transparent mapping system such as NAT64 2) translating or tunneling IPv4 traffic to traverse the v6-only network such as 464XLAT This way we can say later in the spec that -if the transition mechanism is not fully transparent to the host then the server MUST NOT place the option, - the mechanism is compatible with solutions based on NAT64, DNA64 and XLAT, and also any other fully transparent mechanism. The goal is to be prepared for that future where another mechanism becomes prevalent that requires host attention. Take care, Pascal > -----Original Message----- > From: Jen Linkova <furry13@xxxxxxxxx> > Sent: mercredi 24 juin 2020 02:20 > To: Pascal Thubert (pthubert) <pthubert@xxxxxxxxx> > Cc: iot-directorate@xxxxxxxx; draft-ietf-dhc-v6only.all@xxxxxxxx; > dhcwg@xxxxxxxx; last-call@xxxxxxxx > Subject: Re: [dhcwg] Iotdir last call review of draft-ietf-dhc-v6only-03 > > Hi Pascal, > > Thank you for reviewing the document. > I believe Lorenzo explained why the draft supports NAT64 only. > > Re: the terminology comment: > On Tue, Jun 23, 2020 at 7:55 PM Pascal Thubert via Datatracker > <noreply@xxxxxxxx> wrote: > > " > > ... IPv6-only mode (either > > because the OS and all applications are IPv6-only capable or because > > the host has some form of 464XLAT [RFC6877] deployed), > > " > > Do we have a good reference of what we mean by the v6-only mode of a > host > > - or an interface for that matter ? > > > > Else it would help to define it before we use it. Note, the terminology > > defines a "IPv6-only capable host" but not the "mode". > > I'll update the Terminology section with the following definition: > IPv6-only mode as 'a mode of operation when a host acts as IPv6-only capable > and does not have IPv4 addresses assigned (except for IPv4 link-local > address [RFC3927]). > > Would it address your comment? > > -- > SY, Jen Linkova aka Furry -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
