[v6ops] Re: Call For Adoption: draft-link-v6ops-6mops

[tom petch <[e-mail]>]

From: Ron Bonica <rbonica=[e-mail]>
Sent: 05 August 2024 14:21

Friends,

This message begins a Call For Adoption for draft-link-v6ops-6mops. Please read the draft and send your comments in response to this email.

The call for adoption will close on August 19, 2024.

<tp>
Not an easy read because of the terminology and style e.g..

NAT44 I do not see defined in the IETF abbreviation list

" pure IPv6-only networks remain uncommon
   outside of the mobile carrier space.  This dual-stack approach is ..."
Eh?  I expect the second sentence to follow on from the subject, the main clause of the previous one.  Here they seem to be contradictory.

"two additional key elements:
   *  The network provides NAT64 ([RFC6146] ) functionality ([RFC6146]),
      enabling IPv6-only clients to communicate with IPv4-only
      destinations.
   *  The DHCPv4 infrastructure processing DHCPv4 Option 108 as per
      [RFC8925]."
The first bullet I understand. The second is a clause seemingly floating in  space - I do not understand

"The term "IPv6-only capable endpoint""
Sometimes capitalised, sometimes not.  If this is a technical term, then I think capitalisation is needed throughout.

I also note that it is not defined as a term in the way that 
   *  IPv4-Only Endpoint: 
   *  Dual-Stack Endpoint
are.

"Dual-Stack Endpoint (Not IPv6-Only Capable)"
At ths point, "Not IPv6-Capable has not been defined  It would be easier to follow if it were.

"Dual-Stack Endpoint (Not IPv6-Only Capable)"
Is there a technical term in here which needs defining? or two thereof?

And so on...

Like I say not an easy read.  I suspect that if I read and took on board all 19 pages at once it would be clear to me but my memory wants things in bite-size chunks, a page or two at a time, leading on from one chunk to another to the conclusion.

Tom Petch



                                                              Ron




Juniper Business Use Only