Skip to main content

464XLAT Customer-side Translator (CLAT): Node Behavior and Recommendations
draft-ietf-v6ops-claton-16

Revision differences

Document history

Date Rev. By Action
2026-10-19
16 (System) RPC status changed to In Progress (First Edit) from Awaiting First editor
2026-08-13
16 (System) RPC status changed to Awaiting First editor from Awaiting Editor Assignment
2026-06-15
16 (System) RPC status changed to Awaiting Editor Assignment from ref_checker
2026-06-12
16 (System) RPC status changed to ref_checker from formatting
2026-06-09
16 (System) RPC status changed to formatting from blocked: Author Input Required
2026-06-09
16 (System) RFC Editor state changed to In Progress from Blocked
2026-05-22
16 (System) RPC status changed to blocked: Author Input Required from formatting
2026-05-22
16 (System) RFC Editor state changed to Blocked from In Progress
2026-05-22
16 (System) RPC status changed to formatting from Awaiting Editor Assignment
2026-05-20
16 (System) RPC status changed to Awaiting Editor Assignment
2026-05-20
16 (System) RFC Editor state changed to In Progress from MISSREF
2026-03-10
16 (System) IANA Action state changed to No IANA Actions from In Progress
2026-03-09
16 (System) RFC Editor state changed to MISSREF
2026-03-09
16 (System) IESG state changed to RFC Ed Queue from Approved-announcement sent
2026-03-09
16 (System) Announcement was received by RFC Editor
2026-03-06
16 (System) IANA Action state changed to In Progress
2026-03-06
16 Morgan Condie IESG state changed to Approved-announcement sent from Approved-announcement to be sent
2026-03-06
16 Morgan Condie IESG has approved the document
2026-03-06
16 Morgan Condie Closed "Approve" ballot
2026-03-06
16 Morgan Condie Ballot approval text was generated
2026-03-05
16 (System) Removed all action holders (IESG state changed)
2026-03-05
16 Mohamed Boucadair IESG state changed to Approved-announcement to be sent from IESG Evaluation::AD Followup
2026-03-05
16 Jen Linkova New version available: draft-ietf-v6ops-claton-16.txt
2026-03-05
16 Jen Linkova New version approved
2026-03-05
16 (System) Request for posting confirmation emailed to previous authors: Jen Linkova , Lorenzo Colitti , Tommy Jensen
2026-03-05
16 Jen Linkova Uploaded new revision
2026-03-04
15 Éric Vyncke
[Ballot comment]
Thanks for the important work done and for the discussion in addressing my previous blocking DISCUSS ballot
(https://mailarchive.ietf.org/arch/msg/v6ops/9gcmPIGcy6mzKzweov6FUbqdb28/).

I am trusting …
[Ballot comment]
Thanks for the important work done and for the discussion in addressing my previous blocking DISCUSS ballot
(https://mailarchive.ietf.org/arch/msg/v6ops/9gcmPIGcy6mzKzweov6FUbqdb28/).

I am trusting the authors and the responsible AD to fix the two remaining issues:

- RFC 8415 (DHCPv6) is now obsoleted by RFC 9915
- The PvD reference should probably rather be RFC 8801

Regards
2026-03-04
15 Éric Vyncke [Ballot Position Update] Position for Éric Vyncke has been changed to Yes from Discuss
2026-03-01
15 (System) Changed action holders to Mohamed Boucadair (IESG state changed)
2026-03-01
15 (System) Sub state has been changed to AD Followup from Revised I-D Needed
2026-03-01
15 Jen Linkova New version available: draft-ietf-v6ops-claton-15.txt
2026-03-01
15 Jen Linkova New version accepted (logged-in submitter: Jen Linkova)
2026-03-01
15 Jen Linkova Uploaded new revision
2026-01-27
14 (System) Changed action holders to Lorenzo Colitti, Jen Linkova, Tommy Jensen (IESG state changed)
2026-01-27
14 Mohamed Boucadair IESG state changed to IESG Evaluation::Revised I-D Needed from IESG Evaluation::AD Followup
2025-12-18
14 Mohamed Boucadair Request closed, assignment withdrawn: Michael Jones IETF Last Call SECDIR review
2025-12-18
14 Mohamed Boucadair Closed request for IETF Last Call review by SECDIR with state 'Withdrawn': The document went to the IESG Telechat 18/12. Thanks.
2025-12-18
14 Morgan Condie IESG state changed to IESG Evaluation::AD Followup from IESG Evaluation
2025-12-18
14 (System) IANA Review state changed to Version Changed - Review Needed from IANA OK - No Actions Needed
2025-12-18
14 Jen Linkova New version available: draft-ietf-v6ops-claton-14.txt
2025-12-18
14 Jen Linkova New version accepted (logged-in submitter: Jen Linkova)
2025-12-18
14 Jen Linkova Uploaded new revision
2025-12-17
13 Deb Cooley [Ballot Position Update] New position, No Objection, has been recorded for Deb Cooley
2025-12-17
13 Gunter Van de Velde [Ballot Position Update] New position, No Objection, has been recorded for Gunter Van de Velde
2025-12-16
13 Orie Steele [Ballot Position Update] New position, No Objection, has been recorded for Orie Steele
2025-12-16
13 Roman Danyliw [Ballot comment]
Thank you to Robert Sparks for the GENART review.
2025-12-16
13 Roman Danyliw [Ballot Position Update] New position, No Objection, has been recorded for Roman Danyliw
2025-12-16
13 Éric Vyncke
[Ballot discuss]

# Éric Vyncke INT AD comments for draft-ietf-v6ops-claton-13
CC @evyncke

Thank you for the work put into this document. While my current ballot …
[Ballot discuss]

# Éric Vyncke INT AD comments for draft-ietf-v6ops-claton-13
CC @evyncke

Thank you for the work put into this document. While my current ballot is a blocking DISCUSS, I am a big supporter of this work, so, take the length list of the points below as a way to help the authors improving their document.

Please find below some blocking DISCUSS points, some non-blocking COMMENT points/nits (replies would be appreciated even if only for my own education).

Special thanks to Michael Richardson for the shepherd's detailed write-up including the WG consensus *and* the justification of the intended status.

Other thanks to Nicolai Leymann, the DNS directorate reviewer, and Nicolai confirmed that all its comments were implemented by the authors.

I hope that this review helps to improve the document,

Regards,

-éric

Note: this ballot comments follow the Markdown syntax of https://github.com/mnot/ietf-comments/tree/main, i.e., they can be processed by a tool to create github issues.

## DISCUSS (blocking)

As noted in https://datatracker.ietf.org/doc/statement-iesg-handling-ballot-positions-20220121/, a DISCUSS ballot is a request to have a discussion on the points below; I really think that the document would be improved with a change here, but can be convinced otherwise.

### Section 6.1

In which case does the SHOULD not apply in `A node providing CLAT functions to local applications SHOULD use IPv4 addresses from the dedicated 192.0.0.0/29 range [RFC7335]` ? I.e., why not a MUST

### Section 6.2.2

I have also seen mcast IP over ucast layer-2, so, the text in the second bullet should really qualify ucast and mcast by the layer.

### Section 7

Please explain why PvDs (RFC 8801) do not help in this case.

### Section 8

Why not a MUST in `the CLAT instance SHOULD present IPv4-only applications with an IPv4 MTU which is 28 bytes smaller` ? If SHOULD is kept, then follow the IESG guidance at https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-the-use-of-bcp-14-key-words/
2025-12-16
13 Éric Vyncke
[Ballot comment]

## COMMENTS (non-blocking)


### Section 1

While I understand why the I-D means by `which require IPv4 would fail`, the wording seems a …
[Ballot comment]

## COMMENTS (non-blocking)


### Section 1

While I understand why the I-D means by `which require IPv4 would fail`, the wording seems a little 'fuzzy', perhaps adding '(e.g., having a remote peer hardcoded IPv4 addresses preventing the use of DNS64/NAT64)' could help (even if the sentence is heavier) ?

I may perhaps be too strict about the use of "host" vs. "node" in `CLAT functions are performed by the host itself` because the host can be used for tethering 'downstream' devices, i.e., not really a 'host' anymore. I.e., suggest s/host/node/. Later in the I-D, "node" seems to be used more often than "host", so, let's be consistent.

s/compl*i*ments/compl*e*ments/ ;-)

### Section 3

I find the definition of `IPv6-only network` a little confusing with the use of 2 similar but not identical sentences.

About the `native IPv4`, why not using "IPv4-only network" even if only for symmetry with "IPv6-only network" ?

### Section 4

Why not a "MUST" in `Therefore an IPv6-only node SHOULD enable CLAT `? Even if the "MUST" is conditioned with "Therefore an IPv6-only node with CLAT features MUST enable CLAT as soon as it receives a PREF64 option from the network and if local policy allows it." or something similar. Nevertheless I appreciate the "Discussion" as it matches https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-the-use-of-bcp-14-key-words/

About the multi-interface with CLAT on, should this specific use case be more detailed ? E.g., by explaining how the selection of the default IPv4 route should work ? (I note that there is text about using "ipv4only.arpa" in multi-interface, which is good).

s/the node is allowed to use other mechanisms/the node *MAY* use other mechanisms/ ?

I fear that `Unless configured otherwise, the node MUST enable CLAT if the node has not already obtained a non-link-local IPv4 address by the time it discovers the NAT64 prefix.` is probably too aggressive as DHCPv4 is typically slower (as it relayed and requires a permanent storage write operation) than IPv6 RA by a local router. I.e., CLAT could end up being enabled 10 msec before DHCPv4 especially with text later saying `If native IPv4 connectivity becomes available later for a given interface, the node SHOULD disable CLAT for that interface `. Should there be a minimum delay before enable CLAT ?

`If native IPv4 connectivity becomes available later for a given interface, the node SHOULD disable CLAT for that interface ` while the next section has a "MUST" (although with a "unless"). This reads weird.

### Section 6.1

`on the wire` in a Wi-Fi world looks strange ;-)

### Section 6.2.1

Please note that RFC8415 will soon be RFC9915 (it is in AUTH48) so using the I-D draft-ietf-dhc-rfc8415bis rather RFC 8415 will ensure that the RFC editor picks up the right RFC for DHCPv6.

You may add that the examples are using the Well-Known Prefix for NAT64.

Should there be some text confirming that the CLAT node can obtain *two* IPv6 addresses by DHCPv6 and use one for CLAT ? Of course at the expense of checksum recomputation (it would be nice to have an DHCPv6 option to request a checksum neutral IPv6 address...)

Really unsure what is meant by `If a protocol uses the standard IP checksum,` as there is no checksum in any IP header ;-) and is there any TCP or UDP protocols not using the standard checksum ?

### Section 6.2.2

Should there be another term instead of `native IPv6 addresses`, e.g., "non-CLAT addresses" or simply "their other IPv6 addresses" ?

Hummm, the 1st paragraph clearly (and rightfully) states that all IPv6 addresses (CLAT & non-CLAT) MUST have the same behavior, then the bulleted list only specifies the CLAT behavior, e.g., allow non-DAD for some addresses as long as CLAT addresses do DAD... This is not correct, I suggest removing the CLAT-specific text in the bulleted list.

About the DHCP registration, like written above, what if the other addresses are not registered ?

### Section 7

A small but nice graphics would help some readers who are not aware of the issue.

### Section 9.2

I was expecting a MAY rather than `SHOULD implement [RFC7050] ("Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis")` as this document clearly prefers (rightfully) the RA method.

`The router SHOULD have a configuration knob to disable DHCP Option 108 processing.` has little to do with 464XLAT though and more about IPv6-mostly.

### Section 10

`For non-mobile environments, ... the operational considerations are documented in [I-D.ietf-v6ops-6mops].` is rather succint as having 2 IPv6 addresses (and the whole discussion of multi-prefixes) really belongs to this document IMHO.

### Section 11

The link to I-D.ietf-pquip-pqc-engineers does not bring a lot as the discussion about ""Harvest Now, Decrypt Later" as it is not specific to this I-D. Consider removing this part, else a LOT of I-D will end-up referring to this PQC draft.
2025-12-16
13 Éric Vyncke [Ballot Position Update] New position, Discuss, has been recorded for Éric Vyncke
2025-12-16
13 Gorry Fairhurst [Ballot comment]
Thank you for this document, and the update provided to the TSVART review by Wes Eddy.
2025-12-16
13 Gorry Fairhurst [Ballot Position Update] New position, No Objection, has been recorded for Gorry Fairhurst
2025-12-15
13 Paul Wouters [Ballot Position Update] New position, No Objection, has been recorded for Paul Wouters
2025-12-15
13 Mahesh Jethanandani [Ballot Position Update] New position, No Objection, has been recorded for Mahesh Jethanandani
2025-12-12
13 (System) IANA Review state changed to IANA OK - No Actions Needed from Version Changed - Review Needed
2025-12-12
13 Ketan Talaulikar [Ballot Position Update] New position, No Objection, has been recorded for Ketan Talaulikar
2025-12-09
13 Jim Guichard [Ballot Position Update] New position, No Objection, has been recorded for Jim Guichard
2025-12-08
13 Andy Newton [Ballot Position Update] New position, No Objection, has been recorded for Andy Newton
2025-12-08
13 Nicolai Leymann Request for Telechat review by DNSDIR Completed: Ready. Reviewer: Nicolai Leymann. Sent review to list.
2025-11-29
13 Michael Richardson
Document Shepherd Write-Up for Group Documents
This version is dated 4 July 2022.

DOCUMENT: draft-ietf-v6ops-claton-13
DATE of THIS WRITEUP: 2025-11-29.

>Document History
>Does the working …
Document Shepherd Write-Up for Group Documents
This version is dated 4 July 2022.

DOCUMENT: draft-ietf-v6ops-claton-13
DATE of THIS WRITEUP: 2025-11-29.

>Document History
>Does the working group (WG) consensus represent the strong concurrence of a
>few individuals, with others being silent, or did it reach broad agreement?

The WG had much participation during the WGLC.

> Was there controversy about particular points, or were there decisions where
> the consensus was particularly rough?

No.

> Has anyone threatened an appeal or otherwise indicated extreme discontent?

No.

> For protocol documents, are there existing implementations of the contents of
> the document? Have a significant number of potential implementers indicated
> plans to implement? Are any existing implementations reported somewhere,
> either in the document itself (as RFC 7942 recommends) or elsewhere
> (where)?

This is an update on operational considerations for RFC6877, and provides
updates to it based upon deployment/implementation experiences.

> Additional Reviews
> Do the contents of this document closely interact with technologies in other
> IETF working groups or external organizations, and would it therefore benefit
> from their review? Have those reviews occurred? If yes, describe which
> reviews took place.

No additional reviews required.

> Describe how the document meets any required formal expert review criteria,
> such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

N/A.

> If the document contains a YANG module, has the final version of the module

N/A.

> Describe reviews and automated checks performed to validate sections of the
> final version of the document written in a formal language, such as XML code,
> BNF rules, MIB definitions, CBOR's CDDL, etc.

N/A.

>Document Shepherd Checks
>Based on the shepherd's review of the document, is it their opinion that this
>document is needed, clearly written, complete, correctly designed, and ready
>to be handed off to the responsible Area Director?

Yes.

>What type of RFC publication is being requested on the IETF stream (Best
>Current Practice, Proposed Standard, Internet Standard,
>Informational, Experimental or Historic)? Why is this the proper type
>of RFC? Do all Datatracker state attributes correctly reflect this intent?

Although the reference architecture was published as Informational, the
intended status for this specification is justified. Specifically, the
document specifies normative behavior for CLAT nodes for deterministic,
consistent, and interoperable implementations."

The updates to RFC8585 are included in this document rather than offloading
them to a separate document to help implementers/operators easily find latest
CLAT node clarifications in a self-contained document.

>Have reasonable efforts been made to remind all authors of the intellectual
>property rights (IPR) disclosure obligations described in BCP 79? To

Yes.

>Has each author, editor, and contributor shown their willingness to be
>listed as such? If the total number of authors and editors on the front page
>is greater than five, please provide a justification.

Yes. < 5.

>Document any remaining I-D nits in this document. Simply running the idnits
>tool is not enough; please review the "Content Guidelines" on
>authors.ietf.org. (Also note that the current idnits tool generates
>some incorrect warnings; a rewrite is underway.)

None.

>Should any informative references be normative or vice-versa? See the IESG
>Statement on Normative and Informative References.

The split seems fine.

>List any normative references that are not freely available to anyone. Did
>the community have sufficient access to review any such normative
>references?

None.

>Are there any normative downward references (see RFC 3967 and BCP
>97) that are not already listed in the DOWNREF registry? If so,
>list them.

idnits says;
  ** Downref: Normative reference to an Informational RFC: RFC 6877
  ** Downref: Normative reference to an Informational RFC: RFC 8585
  ** Downref: Normative reference to an Informational RFC: RFC 9872

None of these are on the downref list, and will need to be added.

>Are there normative references to documents that are not ready to be
>submitted to the IESG for publication or are otherwise in an unclear state?
>If so, what is the plan for their completion?

6man-rfc6724-update is a normative reference, but is in the RFC-editor Q.

> Will publication of this document change the status of any existing RFCs?

No.

> Describe the document shepherd's review of the IANA considerations section,

No IANA considerations.

2025-11-28
13 Erik Kline [Ballot Position Update] New position, Yes, has been recorded for Erik Kline
2025-11-26
13 Jim Reid Request for Telechat review by DNSDIR is assigned to Nicolai Leymann
2025-11-25
13 Mohamed Boucadair Placed on agenda for telechat - 2025-12-18
2025-11-25
13 Mohamed Boucadair Ballot has been issued
2025-11-25
13 Mohamed Boucadair [Ballot Position Update] New position, Yes, has been recorded for Mohamed Boucadair
2025-11-25
13 Mohamed Boucadair Created "Approve" ballot
2025-11-25
13 Mohamed Boucadair IESG state changed to IESG Evaluation from Waiting for AD Go-Ahead::AD Followup
2025-11-25
13 Mohamed Boucadair Ballot writeup was changed
2025-11-25
13 (System) Changed action holders to Mohamed Boucadair (IESG state changed)
2025-11-25
13 (System) Sub state has been changed to AD Followup from Revised I-D Needed
2025-11-25
13 (System) IANA Review state changed to Version Changed - Review Needed from IANA OK - No Actions Needed
2025-11-25
13 Jen Linkova New version available: draft-ietf-v6ops-claton-13.txt
2025-11-25
13 Jen Linkova New version accepted (logged-in submitter: Jen Linkova)
2025-11-25
13 Jen Linkova Uploaded new revision
2025-11-22
12 Menachem Dodge Request for IETF Last Call review by OPSDIR Completed: Has Nits. Reviewer: Menachem Dodge. Sent review to list.
2025-11-22
12 (System) Changed action holders to Lorenzo Colitti, Jen Linkova, Tommy Jensen (IESG state changed)
2025-11-22
12 Mohamed Boucadair IESG state changed to Waiting for AD Go-Ahead::Revised I-D Needed from Waiting for AD Go-Ahead
2025-11-21
12 (System) IESG state changed to Waiting for AD Go-Ahead from In Last Call
2025-11-21
12 Tero Kivinen Request for IETF Last Call review by SECDIR is assigned to Michael Jones
2025-11-19
12 Wesley Eddy Request for IETF Last Call review by TSVART Completed: Ready with Nits. Reviewer: Wesley Eddy. Sent review to list.
2025-11-14
12 Robert Sparks Request for IETF Last Call review by GENART Completed: Ready with Nits. Reviewer: Robert Sparks. Sent review to list.
2025-11-14
12 David Dong
IESG/Authors/WG Chairs:

IANA has completed its review of draft-ietf-v6ops-claton-12, which is currently in Last Call, and has the following comments:

We understand that this …
IESG/Authors/WG Chairs:

IANA has completed its review of draft-ietf-v6ops-claton-12, which is currently in Last Call, and has the following comments:

We understand that this document doesn't require any registry actions.

While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object.

If this assessment is not accurate, please respond as soon as possible.

For definitions of IANA review states, please see:

https://datatracker.ietf.org/help/state/draft/iana-review

Thank you,

David Dong
IANA Services Sr. Specialist
2025-11-14
12 (System) IANA Review state changed to IANA OK - No Actions Needed from IANA - Review Needed
2025-11-14
12 Nicolai Leymann Request for IETF Last Call review by DNSDIR Completed: Ready with Nits. Reviewer: Nicolai Leymann. Sent review to list.
2025-11-14
12 Magnus Westerlund Request for IETF Last Call review by TSVART is assigned to Wesley Eddy
2025-11-13
12 Dave Thaler Request for IETF Last Call review by INTDIR Completed: Ready with Issues. Reviewer: Dave Thaler. Sent review to list.
2025-11-11
12 Jean Mahoney Request for IETF Last Call review by GENART is assigned to Robert Sparks
2025-11-11
12 Daniele Ceccarelli Request for IETF Last Call review by OPSDIR is assigned to Menachem Dodge
2025-11-10
12 Tim Chown Request for IETF Last Call review by INTDIR is assigned to Dave Thaler
2025-11-08
12 Jim Reid Request for IETF Last Call review by DNSDIR is assigned to Nicolai Leymann
2025-11-07
12 Mohamed Boucadair Requested IETF Last Call review by OPSDIR
2025-11-07
12 Mohamed Boucadair Requested IETF Last Call review by INTDIR
2025-11-07
12 Morgan Condie IANA Review state changed to IANA - Review Needed
2025-11-07
12 Morgan Condie
The following Last Call announcement was sent out (ends 2025-11-21):

From: The IESG
To: IETF-Announce
CC: draft-ietf-v6ops-claton@ietf.org, mcr@sandelman.ca, mohamed.boucadair@orange.com, v6ops-chairs@ietf.org, v6ops@ietf.org …
The following Last Call announcement was sent out (ends 2025-11-21):

From: The IESG
To: IETF-Announce
CC: draft-ietf-v6ops-claton@ietf.org, mcr@sandelman.ca, mohamed.boucadair@orange.com, v6ops-chairs@ietf.org, v6ops@ietf.org
Reply-To: last-call@ietf.org
Sender:
Subject: Last Call:  (464XLAT Customer-side Translator (CLAT): Node Behavior and Recommendations) to Proposed Standard


The IESG has received a request from the IPv6 Operations WG (v6ops) to
consider the following document: - '464XLAT Customer-side Translator (CLAT):
Node Behavior and
  Recommendations'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2025-11-21. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


  464XLAT defines an architecture for providing IPv4 connectivity
  across an IPv6-only network.  The solution involves two functional
  elements: provider-side translator (PLAT) and customer-side
  translator (CLAT).  This document updates the 464XLAT specification
  (RFC6877) and Requirements for IPv6 Customer Edge Routers (RFC8585)
  by further defining CLAT node behavior and IPv6 Customer Edge Routers
  to Support IPv4-as-a-Service by providing recommendations for the
  node developers on enabling and disabling CLAT.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-v6ops-claton/



No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information:
    rfc6877: 464XLAT: Combination of Stateful and Stateless Translation (Informational - Internet Engineering Task Force (IETF) stream)
    rfc8585: Requirements for IPv6 Customer Edge Routers to Support IPv4-as-a-Service (Informational - Internet Engineering Task Force (IETF) stream)
    rfc9872: Recommendations for Discovering IPv6 Prefix Used for IPv6 Address Synthesis (Informational - Internet Engineering Task Force (IETF) stream)



2025-11-07
12 Morgan Condie IESG state changed to In Last Call from Last Call Requested
2025-11-07
12 Mohamed Boucadair Last call was requested
2025-11-07
12 Mohamed Boucadair Last call announcement was generated
2025-11-07
12 Mohamed Boucadair Ballot approval text was generated
2025-11-07
12 Mohamed Boucadair Ballot writeup was generated
2025-11-07
12 Mohamed Boucadair IESG state changed to Last Call Requested from Publication Requested
2025-11-07
12 Nick Buraglio
Document Shepherd Write-Up for Group Documents
This version is dated 4 July 2022.

DOCUMENT: draft-ietf-v6ops-claton-11
DATE of THIS WRITEUP: 2025-11-05.

>Document History
>Does the working …
Document Shepherd Write-Up for Group Documents
This version is dated 4 July 2022.

DOCUMENT: draft-ietf-v6ops-claton-11
DATE of THIS WRITEUP: 2025-11-05.

>Document History
>Does the working group (WG) consensus represent the strong concurrence of a
>few individuals, with others being silent, or did it reach broad agreement?

Concurrence of a few individuals, mostly silence.

> Was there controversy about particular points, or were there decisions where
> the consensus was particularly rough?

No.

> Has anyone threatened an appeal or otherwise indicated extreme discontent?

No.

> For protocol documents, are there existing implementations of the contents of
> the document? Have a significant number of potential implementers indicated
> plans to implement? Are any existing implementations reported somewhere,
> either in the document itself (as RFC 7942 recommends) or elsewhere
> (where)?

This is an update on operational considerations for RFC6877, and provides
updates to it based upon deployment/implementation experiences.

> Additional Reviews
> Do the contents of this document closely interact with technologies in other
> IETF working groups or external organizations, and would it therefore benefit
> from their review? Have those reviews occurred? If yes, describe which
> reviews took place.

No additional reviews required.

> Describe how the document meets any required formal expert review criteria,
> such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

N/A.

> If the document contains a YANG module, has the final version of the module

N/A.

> Describe reviews and automated checks performed to validate sections of the
> final version of the document written in a formal language, such as XML code,
> BNF rules, MIB definitions, CBOR's CDDL, etc.

N/A.

>Document Shepherd Checks
>Based on the shepherd's review of the document, is it their opinion that this
>document is needed, clearly written, complete, correctly designed, and ready
>to be handed off to the responsible Area Director?

Yes.

>What type of RFC publication is being requested on the IETF stream (Best
>Current Practice, Proposed Standard, Internet Standard,
>Informational, Experimental or Historic)? Why is this the proper type
>of RFC? Do all Datatracker state attributes correctly reflect this intent?

Although the reference architecture was published as Informational, the
intended status for this specification is justified. Specifically, the
document specifies normative behavior for CLAT nodes for deterministic,
consistent, and interoperable implementations."

The updates to RFC8585 are included in this document rather than offloading
them to a separate document to help implementers/operators easily find latest
CLAT node clarifications in a self-contained document.


>Have reasonable efforts been made to remind all authors of the intellectual
>property rights (IPR) disclosure obligations described in BCP 79? To

Yes.

>Has each author, editor, and contributor shown their willingness to be
>listed as such? If the total number of authors and editors on the front page
>is greater than five, please provide a justification.

Yes. < 5.

>Document any remaining I-D nits in this document. Simply running the idnits
>tool is not enough; please review the "Content Guidelines" on
>authors.ietf.org. (Also note that the current idnits tool generates
>some incorrect warnings; a rewrite is underway.)



>Should any informative references be normative or vice-versa? See the IESG
>Statement on Normative and Informative References.

The split seems fine.

>List any normative references that are not freely available to anyone. Did
>the community have sufficient access to review any such normative
>references?

None.

>Are there any normative downward references (see RFC 3967 and BCP
>97) that are not already listed in the DOWNREF registry? If so,
>list them.

idnits says;
  ** Downref: Normative reference to an Informational RFC: RFC 6877
  ** Downref: Normative reference to an Informational RFC: RFC 8585
  ** Downref: Normative reference to an Informational RFC: RFC 9872

None of these are on the downref list.

>Are there normative references to documents that are not ready to be
>submitted to the IESG for publication or are otherwise in an unclear state?
>If so, what is the plan for their completion?

6man-rfc6724-update is a normative reference, but is in the RFC-editor Q.

> Will publication of this document change the status of any existing RFCs?

No.

> Describe the document shepherd's review of the IANA considerations section,

No IANA considerations.

2025-11-07
12 Nick Buraglio IETF WG state changed to Submitted to IESG for Publication from WG Consensus: Waiting for Write-Up
2025-11-07
12 Nick Buraglio IESG state changed to Publication Requested from I-D Exists
2025-11-07
12 (System) Changed action holders to Mohamed Boucadair (IESG state changed)
2025-11-07
12 Nick Buraglio Responsible AD changed to Mohamed Boucadair
2025-11-07
12 Nick Buraglio Document is now in IESG state Publication Requested
2025-11-06
12 Jen Linkova New version available: draft-ietf-v6ops-claton-12.txt
2025-11-06
12 Jen Linkova New version accepted (logged-in submitter: Jen Linkova)
2025-11-06
12 Jen Linkova Uploaded new revision
2025-11-05
11 Michael Richardson
Document Shepherd Write-Up for Group Documents
This version is dated 4 July 2022.

DOCUMENT: draft-ietf-v6ops-claton-11
DATE of THIS WRITEUP: 2025-11-05.

>Document History
>Does the working …
Document Shepherd Write-Up for Group Documents
This version is dated 4 July 2022.

DOCUMENT: draft-ietf-v6ops-claton-11
DATE of THIS WRITEUP: 2025-11-05.

>Document History
>Does the working group (WG) consensus represent the strong concurrence of a
>few individuals, with others being silent, or did it reach broad agreement?

Concurrence of a few individuals, mostly silence.

> Was there controversy about particular points, or were there decisions where
> the consensus was particularly rough?

No.

> Has anyone threatened an appeal or otherwise indicated extreme discontent?

No.

> For protocol documents, are there existing implementations of the contents of
> the document? Have a significant number of potential implementers indicated
> plans to implement? Are any existing implementations reported somewhere,
> either in the document itself (as RFC 7942 recommends) or elsewhere
> (where)?

This is an update on operational considerations for RFC6877, and provides
updates to it based upon deployment/implementation experiences.

> Additional Reviews
> Do the contents of this document closely interact with technologies in other
> IETF working groups or external organizations, and would it therefore benefit
> from their review? Have those reviews occurred? If yes, describe which
> reviews took place.

No additional reviews required.

> Describe how the document meets any required formal expert review criteria,
> such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

N/A.

> If the document contains a YANG module, has the final version of the module

N/A.

> Describe reviews and automated checks performed to validate sections of the
> final version of the document written in a formal language, such as XML code,
> BNF rules, MIB definitions, CBOR's CDDL, etc.

N/A.

>Document Shepherd Checks
>Based on the shepherd's review of the document, is it their opinion that this
>document is needed, clearly written, complete, correctly designed, and ready
>to be handed off to the responsible Area Director?

Yes.

>What type of RFC publication is being requested on the IETF stream (Best
>Current Practice, Proposed Standard, Internet Standard,
>Informational, Experimental or Historic)? Why is this the proper type
>of RFC? Do all Datatracker state attributes correctly reflect this intent?

Although the reference architecture was published as Informational, the
intended status for this specification is justified. Specifically, the
document specifies normative behavior for CLAT nodes for deterministic,
consistent, and interoperable implementations."

The updates to RFC8585 are included in this document rather than offloading
them to a separate document to help implementers/operators easily find latest
CLAT node clarifications in a self-contained document.


>Have reasonable efforts been made to remind all authors of the intellectual
>property rights (IPR) disclosure obligations described in BCP 79? To

Yes.

>Has each author, editor, and contributor shown their willingness to be
>listed as such? If the total number of authors and editors on the front page
>is greater than five, please provide a justification.

Yes. < 5.

>Document any remaining I-D nits in this document. Simply running the idnits
>tool is not enough; please review the "Content Guidelines" on
>authors.ietf.org. (Also note that the current idnits tool generates
>some incorrect warnings; a rewrite is underway.)



>Should any informative references be normative or vice-versa? See the IESG
>Statement on Normative and Informative References.

The split seems fine.

>List any normative references that are not freely available to anyone. Did
>the community have sufficient access to review any such normative
>references?

None.

>Are there any normative downward references (see RFC 3967 and BCP
>97) that are not already listed in the DOWNREF registry? If so,
>list them.

idnits says;
  ** Downref: Normative reference to an Informational RFC: RFC 6877
  ** Downref: Normative reference to an Informational RFC: RFC 8585
  ** Downref: Normative reference to an Informational RFC: RFC 9872

None of these are on the downref list.

>Are there normative references to documents that are not ready to be
>submitted to the IESG for publication or are otherwise in an unclear state?
>If so, what is the plan for their completion?

6man-rfc6724-update is a normative reference, but is in the RFC-editor Q.

> Will publication of this document change the status of any existing RFCs?

No.

> Describe the document shepherd's review of the IANA considerations section,

No IANA considerations.

2025-11-05
11 Mohamed Boucadair Almost all comments in the AD review were adequately addressed. There are some very few points to clarify.
2025-11-04
11 Jen Linkova New version available: draft-ietf-v6ops-claton-11.txt
2025-11-04
11 Jen Linkova New version accepted (logged-in submitter: Jen Linkova)
2025-11-04
11 Jen Linkova Uploaded new revision
2025-11-04
10 Michael Richardson
Document Shepherd Write-Up for Group Documents
This version is dated 4 July 2022.

DOCUMENT: draft-ietf-v6ops-claton-10
DATE of THIS WRITEUP: 2025-11-04.

>Document History
>Does the working …
Document Shepherd Write-Up for Group Documents
This version is dated 4 July 2022.

DOCUMENT: draft-ietf-v6ops-claton-10
DATE of THIS WRITEUP: 2025-11-04.

>Document History
>Does the working group (WG) consensus represent the strong concurrence of a
>few individuals, with others being silent, or did it reach broad agreement?

Concurrence of a few individuals, mostly silence.

> Was there controversy about particular points, or were there decisions where
> the consensus was particularly rough?

No.

> Has anyone threatened an appeal or otherwise indicated extreme discontent?

No.

> For protocol documents, are there existing implementations of the contents of
> the document? Have a significant number of potential implementers indicated
> plans to implement? Are any existing implementations reported somewhere,
> either in the document itself (as RFC 7942 recommends) or elsewhere
> (where)?

This is an update on operational considerations for RFC6877, and provides
updates to it based upon deployment/implementation experiences.

> Additional Reviews
> Do the contents of this document closely interact with technologies in other
> IETF working groups or external organizations, and would it therefore benefit
> from their review? Have those reviews occurred? If yes, describe which
> reviews took place.

No additional reviews required.

> Describe how the document meets any required formal expert review criteria,
> such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

N/A.

> If the document contains a YANG module, has the final version of the module

N/A.

> Describe reviews and automated checks performed to validate sections of the
> final version of the document written in a formal language, such as XML code,
> BNF rules, MIB definitions, CBOR's CDDL, etc.

N/A.

>Document Shepherd Checks
>Based on the shepherd's review of the document, is it their opinion that this
>document is needed, clearly written, complete, correctly designed, and ready
>to be handed off to the responsible Area Director?

Yes.

>What type of RFC publication is being requested on the IETF stream (Best
>Current Practice, Proposed Standard, Internet Standard,
>Informational, Experimental or Historic)? Why is this the proper type
>of RFC? Do all Datatracker state attributes correctly reflect this intent?

Yes, standards track.

>Have reasonable efforts been made to remind all authors of the intellectual
>property rights (IPR) disclosure obligations described in BCP 79? To

Yes.

>Has each author, editor, and contributor shown their willingness to be
>listed as such? If the total number of authors and editors on the front page
>is greater than five, please provide a justification.

Yes. < 5.

>Document any remaining I-D nits in this document. Simply running the idnits
>tool is not enough; please review the "Content Guidelines" on
>authors.ietf.org. (Also note that the current idnits tool generates
>some incorrect warnings; a rewrite is underway.)



>Should any informative references be normative or vice-versa? See the IESG
>Statement on Normative and Informative References.

The split seems fine.

>List any normative references that are not freely available to anyone. Did
>the community have sufficient access to review any such normative
>references?

None.

>Are there any normative downward references (see RFC 3967 and BCP
>97) that are not already listed in the DOWNREF registry? If so,
>list them.

idnits says;
  ** Downref: Normative reference to an Informational RFC: RFC 6877
  ** Downref: Normative reference to an Informational RFC: RFC 8585
  ** Downref: Normative reference to an Informational RFC: RFC 9872

None of these are on the downref list.

>Are there normative references to documents that are not ready to be
>submitted to the IESG for publication or are otherwise in an unclear state?
>If so, what is the plan for their completion?

6man-rfc6724-update is a normative reference, but is in the RFC-editor Q.

> Will publication of this document change the status of any existing RFCs?

No.

> Describe the document shepherd's review of the IANA considerations section,

No IANA considerations.

2025-11-04
10 Nick Buraglio Changed consensus to Yes from Unknown
2025-11-04
10 Nick Buraglio Intended Status changed to Proposed Standard from None
2025-10-30
10 Michael Richardson
Document Shepherd Write-Up for Group Documents
This version is dated 4 July 2022.

DOCUMENT: draft-ietf-v6ops-claton-10
DATE of THIS WRITEUP: 2025-10-30.

>Document History
>Does the working …
Document Shepherd Write-Up for Group Documents
This version is dated 4 July 2022.

DOCUMENT: draft-ietf-v6ops-claton-10
DATE of THIS WRITEUP: 2025-10-30.

>Document History
>Does the working group (WG) consensus represent the strong concurrence of a
>few individuals, with others being silent, or did it reach broad agreement?

Concurrence of a few individuals, mostly silence.

> Was there controversy about particular points, or were there decisions where
> the consensus was particularly rough?

No.

> Has anyone threatened an appeal or otherwise indicated extreme discontent?

No.

> For protocol documents, are there existing implementations of the contents of
> the document? Have a significant number of potential implementers indicated
> plans to implement? Are any existing implementations reported somewhere,
> either in the document itself (as RFC 7942 recommends) or elsewhere
> (where)?

This is an update on operational considerations for RFC6877, and provides
updates to it based upon deployment/implementation experiences.

> Additional Reviews
> Do the contents of this document closely interact with technologies in other
> IETF working groups or external organizations, and would it therefore benefit
> from their review? Have those reviews occurred? If yes, describe which
> reviews took place.

No additional reviews required.

> Describe how the document meets any required formal expert review criteria,
A> such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

N/A.

> If the document contains a YANG module, has the final version of the module

N/A.

> Describe reviews and automated checks performed to validate sections of the
> final version of the document written in a formal language, such as XML code,
> BNF rules, MIB definitions, CBOR's CDDL, etc.

N/A.

>Document Shepherd Checks
>Based on the shepherd's review of the document, is it their opinion that this
>document is needed, clearly written, complete, correctly designed, and ready
>to be handed off to the responsible Area Director?

Yes.

>What type of RFC publication is being requested on the IETF stream (Best
>Current Practice, Proposed Standard, Internet Standard,
>Informational, Experimental or Historic)? Why is this the proper type
>of RFC? Do all Datatracker state attributes correctly reflect this intent?

Not yet.

>Have reasonable efforts been made to remind all authors of the intellectual
>property rights (IPR) disclosure obligations described in BCP 79? To

Yes.

>Has each author, editor, and contributor shown their willingness to be
>listed as such? If the total number of authors and editors on the front page
>is greater than five, please provide a justification.

Yes. < 5.

>Document any remaining I-D nits in this document. Simply running the idnits
>tool is not enough; please review the "Content Guidelines" on
>authors.ietf.org. (Also note that the current idnits tool generates
>some incorrect warnings; a rewrite is underway.)



>Should any informative references be normative or vice-versa? See the IESG
>Statement on Normative and Informative References.

The split seems fine.

>List any normative references that are not freely available to anyone. Did
>the community have sufficient access to review any such normative
>references?

None.

>Are there any normative downward references (see RFC 3967 and BCP
>97) that are not already listed in the DOWNREF registry? If so,
>list them.

idnits says;
  ** Downref: Normative reference to an Informational RFC: RFC 6877
  ** Downref: Normative reference to an Informational RFC: RFC 8585
  ** Downref: Normative reference to an Informational RFC: RFC 9872

None of these are on the downref list.

>Are there normative references to documents that are not ready to be
>submitted to the IESG for publication or are otherwise in an unclear state?
>If so, what is the plan for their completion?

6man-rfc6724-update is a normative reference, but is in the RFC-editor Q.

> Will publication of this document change the status of any existing RFCs?

No.

> Describe the document shepherd's review of the IANA considerations section,

No IANA considerations.

2025-10-18
10 Jen Linkova New version available: draft-ietf-v6ops-claton-10.txt
2025-10-18
10 Jen Linkova New version accepted (logged-in submitter: Jen Linkova)
2025-10-18
10 Jen Linkova Uploaded new revision
2025-10-11
09 Mohamed Boucadair AD Review: https://mailarchive.ietf.org/arch/msg/v6ops/JYY5IkPguwyEggnL1irzS1qjK8I/
2025-10-08
09 Nick Buraglio Notification list changed to mcr@sandelman.ca because the document shepherd was set
2025-10-08
09 Nick Buraglio Document shepherd changed to Michael Richardson
2025-10-07
09 Jen Linkova New version available: draft-ietf-v6ops-claton-09.txt
2025-10-07
09 Jen Linkova New version accepted (logged-in submitter: Jen Linkova)
2025-10-07
09 Jen Linkova Uploaded new revision
2025-10-07
08 Nick Buraglio The WG chairs believe that there is rough consensus to advance this document to the IESG.
2025-10-07
08 Nick Buraglio IETF WG state changed to WG Consensus: Waiting for Write-Up from In WG Last Call
2025-09-26
08 Nick Buraglio Tag Revised I-D Needed - Issue raised by WGLC cleared.
2025-09-17
08 Jen Linkova New version available: draft-ietf-v6ops-claton-08.txt
2025-09-17
08 Jen Linkova New version accepted (logged-in submitter: Jen Linkova)
2025-09-17
08 Jen Linkova Uploaded new revision
2025-09-11
07 Nick Buraglio WGLC was extended for 2 weeks
2025-09-11
07 Nick Buraglio Tag Revised I-D Needed - Issue raised by WGLC set.
2025-08-25
07 Jen Linkova New version available: draft-ietf-v6ops-claton-07.txt
2025-08-25
07 Jen Linkova New version accepted (logged-in submitter: Jen Linkova)
2025-08-25
07 Jen Linkova Uploaded new revision
2025-07-30
06 Nick Buraglio IETF WG state changed to In WG Last Call from WG Document
2025-07-25
06 Jen Linkova New version available: draft-ietf-v6ops-claton-06.txt
2025-07-25
06 Jen Linkova New version accepted (logged-in submitter: Jen Linkova)
2025-07-25
06 Jen Linkova Uploaded new revision
2025-07-17
05 Nick Buraglio Added to session: IETF-123: v6ops  Mon-1500
2025-07-06
05 Jen Linkova New version available: draft-ietf-v6ops-claton-05.txt
2025-07-06
05 Jen Linkova New version accepted (logged-in submitter: Jen Linkova)
2025-07-06
05 Jen Linkova Uploaded new revision
2025-03-17
04 Jen Linkova New version available: draft-ietf-v6ops-claton-04.txt
2025-03-17
04 Jen Linkova New version accepted (logged-in submitter: Jen Linkova)
2025-03-17
04 Jen Linkova Uploaded new revision
2025-02-23
03 Jen Linkova New version available: draft-ietf-v6ops-claton-03.txt
2025-02-23
03 Jen Linkova New version accepted (logged-in submitter: Jen Linkova)
2025-02-23
03 Jen Linkova Uploaded new revision
2024-10-21
02 Jen Linkova New version available: draft-ietf-v6ops-claton-02.txt
2024-10-21
02 Jen Linkova New version accepted (logged-in submitter: Jen Linkova)
2024-10-21
02 Jen Linkova Uploaded new revision
2024-10-14
01 Jen Linkova New version available: draft-ietf-v6ops-claton-01.txt
2024-10-14
01 Jen Linkova New version accepted (logged-in submitter: Jen Linkova)
2024-10-14
01 Jen Linkova Uploaded new revision
2024-07-09
00 Nick Buraglio This document now replaces draft-link-v6ops-claton instead of None
2024-07-09
00 Jen Linkova New version available: draft-ietf-v6ops-claton-00.txt
2024-07-09
00 Nick Buraglio WG -00 approved
2024-07-08
00 Jen Linkova Set submitter to "Jen Linkova ", replaces to draft-link-v6ops-claton and sent approval email to group chairs: v6ops-chairs@ietf.org
2024-07-08
00 Jen Linkova Uploaded new revision