Research paper — per-model detail

- **NFS + TLS support (kTLS Technology Preview)** – NFS traffic can now be encrypted using kernel TLS. This adds confidentiality and integrity for RPCs; it may increase CPU usage but protects data in transit and aligns NFS with modern security requirements. [Jira RHEL‑74415]

- **IPv6 URL parsing fix for `nfs://` schemes in ReaR** – ReaR now correctly handles IPv6 addresses enclosed in brackets in `nfs://` (and `sshfs://`) URLs. The previous bug caused backup/restore jobs that used NFS over IPv6 to abort. Fix restores reliable NFS‑based backups on IPv6 networks.

- **Increased default `rsize`/`wsize` limits to 1 MiB** – RHEL 10 sets the maximum read and write size for NFS mounts to 1,048,576 bytes on both client and server (up from earlier, lower defaults). Larger I/O chunks reduce the number of RPC calls, improving throughput and overall NFS performance.

- **Client‑side NFS caching via FS‑Cache** – FS‑Cache support is now documented and enabled through the `cachefilesd` daemon. When an NFS mount is created with the appropriate cache option, read requests can be satisfied from a local persistent cache (XFS, ext3/4), lowering network traffic and server load and speeding up repeated reads (with the trade‑off of local cache overhead).

- **NFS with TLS support added (RHEL 10.0)**: NFS now supports TLS encryption for RPC traffic, enhancing security. Relies on kernel TLS (kTLS), which is a Technology Preview.
- **NFS client supports larger rsize/wsize (RHEL 10.0)**: Maximum read/write buffer size increased to 1,048,576 bytes, improving NFS client performance.
- **IPv6 address support in nfs:// URLs fixed (RHEL 10.0)**: ReaR now correctly parses IPv6 addresses in `nfs://` URLs without requiring workarounds, enabling proper backup/restore over NFS with IPv6.
- **FS-Cache client-side caching documented (RHEL 10.0)**: NFS performance can be improved using FS-Cache with `cachefilesd`, reducing server load and network usage by caching data locally.

- **NFS with TLS support added (RHEL 10.0)**: NFS now supports TLS encryption for RPC traffic, enhancing security. Relies on kernel TLS (kTLS), which is a Technology Preview.
- **NFS client supports larger rsize/wsize (RHEL 10.0)**: Maximum read/write buffer size increased to 1,048,576 bytes, improving NFS client performance.
- **IPv6 address support fixed in NFS URLs (RHEL 10.0)**: ReaR now correctly parses IPv6 addresses in `nfs://` URLs when enclosed in square brackets, fixing a parsing bug.
- **FS-Cache client-side caching documented (RHEL 10.0)**: NFS performance can be improved using FS-Cache with the `cachefilesd` service, reducing server load and network usage.

- **NFS with TLS support added (RHEL 10.0)** – TLS is now fully supported for NFS, encrypting RPC traffic between clients and servers via kernel TLS (kTLS). Improves security without requiring application changes; kTLS itself remains a Technology Preview.

- **NFS client supports larger rsize/wsize (up to 1MB) (RHEL 10.0)** – Maximum read/write transfer size increased to 1,048,576 bytes for both client and server. Enhances NFS performance by allowing larger data transfers per operation.

- **IPv6 address support fixed in nfs:// URLs for ReaR (RHEL 10.0)** – Square brackets around IPv6 addresses in `nfs://` URLs are no longer misinterpreted as shell metacharacters. Enables correct use of IPv6 NFS URLs in backup/restore configurations.

- **FS-Cache client-side caching documentation updated (RHEL 10.0)** – Clarifies use of `cachefiles` and `cachefilesd` for NFS caching, including supported backends (XFS, ext3, ext4) and behavior with partial caching. Helps optimize NFS client performance and reduce server load through local caching.

- **NFS with TLS support (RHEL 10.0)** – RPC traffic for NFS is now encrypted using Transport Layer Security.  The feature is fully supported (via kernel TLS technology preview) and allows administrators to secure NFS mounts without changing client or server configuration beyond enabling TLS.  This improves confidentiality and integrity of NFS traffic, especially over untrusted networks.  

- **IPv6 address parsing bug fix for `nfs://` URLs (RHEL 10.0)** – Square‑bracketed IPv6 addresses are now correctly interpreted in `nfs://` and `sshfs://` URLs used by tools such as ReaR.  The previous bug caused ReaR to abort with “Invalid scheme” errors when an IPv6 address was enclosed in brackets.  The fix restores proper URL handling, enabling reliable use of IPv6 NFS endpoints in backup and restore workflows.  

- **Client‑side caching of NFS content via FS‑Cache (RHEL 10.0)** – RHEL 10 introduces the `cachefilesd` daemon and `cachefiles` kernel module to provide FS‑Cache support for NFS mounts.  When enabled, the client can cache read data locally on a block‑based filesystem (XFS, ext3, ext4) with extended attributes, reducing network traffic and server load while improving read performance for frequently accessed files.  Administrators can configure the cache backend and size through `/etc/cachefilesd.conf`.

- **NFS with TLS support** – RHEL 10 now fully supports Transport Layer Security (TLS) for NFS RPC traffic.  The kernel TLS (kTLS) technology preview is required, but the feature enables end‑to‑end encryption of NFS data, improving security and compliance for NFS clients and servers.  

- **IPv6 address parsing bug fix for `nfs://` URLs** – Previously, square brackets around an IPv6 address were treated as shell metacharacters, causing ReaR (and other tools) to abort when an `nfs://[2001:db8::1]/path` URL was used.  The fix now correctly interprets brackets, allowing IPv6 NFS URLs to be used in backup and output URLs without error.  

- **FS‑Cache client‑side caching for NFS** – RHEL 10 introduces the `cachefilesd` daemon and FS‑Cache integration for NFS mounts.  When the `cachefiles` option is enabled, the client can persistently cache NFS data on a local block‑based filesystem (ext3, ext4, or XFS).  This reduces network traffic, lowers server load, and speeds up read operations by serving data from local cache.

- **NFS with TLS support (new feature)** – RHEL 10 now allows NFS RPC traffic to be encrypted with Transport Layer Security.  The kernel TLS (kTLS) technology preview is required, but the feature is fully supported in the NFS server and client configuration.  This change improves data confidentiality and integrity for NFS traffic, especially over untrusted networks, without requiring separate VPN or IPsec tunnels.

- **IPv6 address parsing bug fix for `nfs://` URLs** – Previously, ReaR (and other tools that parse `nfs://` URLs) incorrectly treated square brackets around an IPv6 address as shell metacharacters, causing the backup or output URL to be rejected.  The fix now correctly ignores the brackets, allowing `nfs://[2001:db8:ca2:6::101]/path` to be used directly.  This eliminates a common configuration error and enables reliable use of IPv6 NFS endpoints in backup scripts and other automation.

- **Client‑side caching of NFS content via FS‑Cache (new feature)** – RHEL 10 introduces full FS‑Cache support for NFS mounts.  The `cachefiles` kernel module and `cachefilesd` daemon provide a persistent local cache backed by a block‑based filesystem (XFS, ext3, or ext4).  When an NFS share is mounted with the appropriate option, read requests are served from the local cache whenever possible, reducing network traffic, lowering server load, and improving client‑side read performance.  The feature is transparent to users and can be enabled or disabled per‑mount, giving administrators fine‑grained control over performance trade‑offs.

- **NFS with TLS support added** – NFS traffic can now be encrypted using TLS (via kernel TLS/kTLS), improving security for RPC communication between clients and servers.
- **IPv6 support in NFS URLs fixed** – ReaR now correctly parses IPv6 addresses in `nfs://` URLs (e.g., `nfs://[2001:db8::1]/path`), enabling proper backup/restore over IPv6 NFS shares.
- **Default `rsize`/`wsize` increased to 1,048,576 bytes** – NFS client and server now use a larger default block size for read/write operations, improving throughput and performance.
- **FS-Cache (client-side caching) for NFS enabled** – Introduces `cachefiles` and `cachefilesd` to cache NFS content locally, reducing network load and improving read performance (requires XFS/ext3/ext4 as cache backend).
- **FS-Cache coherency and transparency** – Ensures cached data stays consistent with server state; handles partial caching and hides cache I/O errors from applications.

*   **NFS with TLS support**: RHEL 10 fully supports NFS with Transport Layer Security (TLS) to encrypt RPC traffic between clients and servers. This matters for security, though it relies on kernel TLS (kTLS), which is currently a Technology Preview.
*   **ReaR NFS URL parsing fix**: The ReaR backup tool now correctly interprets square brackets in IPv6 addresses within `nfs://` URLs (e.g., `nfs://[::1]/...`). Previously, these brackets were treated as shell metacharacters, causing premature aborts; this fix ensures reliable backup configurations using IPv6 NFS targets.
*   **Increased default rsize/wsize limits**: The maximum supported value for NFS read (`rsize`) and write (`wsize`) operations is now 1,048,576 bytes (1 MB) for both client and server. This allows for larger data transfers per operation, potentially improving throughput for compatible workloads.
*   **FS-Cache for NFS performance**: RHEL 10 documentation highlights the use of FS-Cache (via the `cachefiles` backend) to cache NFS content locally. This improves performance by satisfying read requests from local storage, reducing network bandwidth usage and server load, though it may introduce slight latency overhead on the client side.

*   **NFS with TLS support**: RHEL 10 fully supports NFS with Transport Layer Security (TLS) to encrypt RPC traffic between clients and servers. This matters for security, though it relies on kernel TLS (kTLS), which is currently a Technology Preview.
*   **ReaR NFS URL parsing fix**: The ReaR backup tool now correctly interprets square brackets in IPv6 addresses within `nfs://` URLs (e.g., `nfs://[::1]/...`). Previously, these brackets were treated as shell metacharacters, causing premature aborts; this fix ensures reliable backup configurations using IPv6 NFS targets.
*   **Increased default rsize/wsize limits**: The maximum supported value for NFS read (`rsize`) and write (`wsize`) operations is now 1,048,576 bytes (1 MB) for both client and server. This allows for larger data transfers per operation, potentially improving throughput for compatible workloads.
*   **FS-Cache for NFS performance**: RHEL 10 documentation highlights the use of FS-Cache (via the `cachefiles` backend) to cache NFS content locally. This improves performance by satisfying read requests from local storage, reducing network bandwidth usage and server load, though it may introduce slight latency overhead on the client side.

*   **NFS with TLS support**: RHEL 10 fully supports NFS with Transport Layer Security (TLS) to encrypt RPC traffic between clients and servers. This matters for security, though it relies on kernel TLS (kTLS), which is currently a Technology Preview.
*   **ReaR NFS URL parsing fix**: The ReaR backup tool now correctly interprets square brackets in `nfs://` URLs containing IPv6 addresses (e.g., `nfs://[2001:db8::1]/share`). Previously, these brackets were misinterpreted as shell metacharacters, causing premature aborts; this fix ensures reliable backup configurations using IPv6 NFS targets.
*   **Increased default rsize/wsize limits**: The maximum supported value for NFS read (`rsize`) and write (`wsize`) operations is now 1,048,576 bytes (1 MB) on both client and server. This allows for larger single-operation transfers, potentially improving throughput for large file operations compared to previous defaults.
*   **FS-Cache for NFS performance**: RHEL 10 documentation highlights the use of FS-Cache (via `cachefiles`) to cache NFS content locally. This improves performance by satisfying read requests from local storage, reducing network bandwidth usage and server load, though it may introduce slight latency overhead for cache management.

*   **NFS with TLS support is fully supported**: NFS now supports Transport Layer Security (TLS) for RPC traffic, ensuring encrypted communication between clients and servers. This matters for enhancing security, though it relies on kernel TLS (kTLS), which is currently a Technology Preview.
*   **ReaR correctly parses IPv6 addresses in NFS URLs**: The ReaR tool no longer misinterprets square brackets in IPv6 addresses within `nfs://` URLs, allowing users to specify IPv6 addresses for NFS backup/output URLs without manual escaping workarounds.
*   **FS-Cache enables client-side caching for NFS**: The integration of FS-Cache with the `cachefiles` backend allows NFS clients to cache data locally, which improves performance by reducing network traffic and server load, although it may introduce some client-side latency.

*   **NFS with TLS support is fully supported**: NFS now supports Transport Layer Security (TLS) for RPC traffic, ensuring encrypted communication between clients and servers. This matters for enhancing security, though it relies on kernel TLS (kTLS), which is currently a Technology Preview.
*   **ReaR correctly parses IPv6 addresses in NFS URLs**: The ReaR tool no longer misinterprets square brackets in IPv6 addresses within `nfs://` URLs, allowing users to specify IPv6 addresses for NFS backup/output URLs without manual escaping workarounds.
*   **FS-Cache enables client-side caching for NFS**: The integration of FS-Cache with the `cachefiles` backend allows NFS clients to cache data locally, which improves performance by reducing network traffic and server load, although it may introduce some client-side latency.

- **NFS with TLS support added**: RHEL 10 now fully supports Transport Layer Security (TLS) for NFS RPC traffic, enabling encrypted communication between clients and servers; this matters for enhancing security, though it relies on kernel TLS (kTLS), which is currently a Technology Preview.
- **IPv6 address handling in NFS URLs fixed**: ReaR (Relax-and-Recover) now correctly interprets IPv6 addresses enclosed in square brackets (e.g., `nfs://[::1]/path`) in `BACKUP_URL` or `OUTPUT_URL` without requiring manual escaping; this matters because it prevents premature aborts during backup/restore operations when using IPv6 NFS targets.
- **NFS client-side caching via FS-Cache documented**: RHEL 10 supports using FS-Cache with NFS to improve performance by caching data locally, reducing server load and network bandwidth usage; this matters for optimizing read-heavy workloads, though it may introduce slight client-side overhead and requires a supported cache backend (XFS, ext3, ext4).
- **NFS mount options `rsize` and `wsize` defaults clarified**: The maximum transfer size for NFS read/write operations is now explicitly defined as 1,048,576 bytes (1 MiB) for both client and server in RHEL 10; this matters for performance tuning, as larger sizes can improve throughput for large file transfers.
- **NFS `port` option behavior clarified for NFSv4**: For NFSv4 mounts, if the `port` option is not specified, the client now uses the standard TCP port 2049 instead of querying `rpcbind`; this matters for simplifying firewall configurations and reducing dependency on `rpcbind` in NFSv4 environments.

- **NFS with TLS support added**: RHEL 10 now fully supports Transport Layer Security (TLS) for NFS RPC traffic, enabling encrypted communication between clients and servers; this matters for enhancing security, though it relies on kernel TLS (kTLS), which is currently a Technology Preview.
- **IPv6 address handling in NFS URLs fixed**: ReaR (Relax-and-Recover) now correctly interprets IPv6 addresses enclosed in square brackets (e.g., `nfs://[::1]/path`) in `BACKUP_URL` or `OUTPUT_URL` without requiring manual escaping; this matters because it prevents premature aborts during backup/restore operations when using IPv6 NFS targets.
- **NFS client-side caching via FS-Cache documented**: RHEL 10 supports using FS-Cache with NFS to improve performance by caching data locally, reducing server load and network bandwidth usage; this matters for optimizing read-heavy workloads, though it may introduce slight client-side overhead and requires a supported cache backend (XFS, ext3, ext4).
- **NFS mount options `rsize` and `wsize` defaults clarified**: The maximum transfer size for NFS read/write operations is now explicitly defined as 1,048,576 bytes (1 MiB) for both client and server in RHEL 10; this matters for performance tuning, as larger sizes can improve throughput for large file transfers.
- **NFS `port` option behavior clarified for NFSv4**: For NFSv4 mounts, if the `port` option is not specified, the client now uses the standard TCP port 2049 instead of querying `rpcbind`; this matters for simplifying firewall configurations and reducing dependency on `rpcbind` in NFSv4 environments.

- **NFS with TLS support added**: RHEL 10 now fully supports Transport Layer Security (TLS) for NFS RPC traffic, enabling encrypted communication between clients and servers; this matters for enhancing security, though it relies on kernel TLS (kTLS), which is currently a Technology Preview.
- **IPv6 address handling in NFS URLs fixed**: ReaR (Relax-and-Recover) now correctly interprets IPv6 addresses enclosed in square brackets (e.g., `nfs://[::1]/path`) in `BACKUP_URL` or `OUTPUT_URL` without requiring manual escaping; this matters because it prevents premature aborts during backup/restore operations when using IPv6 NFS targets.
- **NFS client-side caching via FS-Cache documented**: RHEL 10 supports using FS-Cache with NFS to improve performance by caching data locally, reducing server load and network bandwidth usage; this matters for optimizing read-heavy workloads, though it may introduce slight client-side overhead and requires a supported cache backend (XFS, ext3, ext4).
- **NFS mount options `rsize` and `wsize` defaults clarified**: The maximum transfer size for NFS read/write operations is now explicitly defined as 1,048,576 bytes (1 MiB) for both client and server in RHEL 10; this matters for performance tuning, as larger sizes can improve throughput for large file transfers.
- **NFS `port` option behavior clarified for NFSv4**: For NFSv4 mounts, if the `port` option is not specified, the client now uses the standard TCP port 2049 instead of querying `rpcbind`; this matters for simplifying firewall configurations and reducing dependency on `rpcbind` in NFSv4 environments.

- **NFS with TLS support added (Technology Preview)**  
  *Changed:* RHEL 10 now supports NFS over TLS for encrypted RPC traffic.  
  *Why it matters:* Enhances security by enabling encrypted communication between NFS clients and servers, though kTLS is still a preview feature.

- **Improved NFS client-side caching with FS-Cache**  
  *Changed:* FS-Cache integration with NFS allows client-side caching using the `cachefilesd` service.  
  *Why it matters:* Reduces server load and network bandwidth usage by caching frequently accessed files locally.

- **Fixed IPv6 address handling in NFS URLs**  
  *Changed:* ReaR now correctly parses NFS URLs with IPv6 addresses enclosed in square brackets.  
  *Why it matters:* Enables proper use of IPv6-based NFS mounts in backup tools like ReaR without workarounds.

- **New mount options for NFS performance tuning**  
  *Changed:* Options like `rsize`, `wsize`, `retrans`, `timeo`, and `sec=` are documented for fine-tuning NFS performance and security.  
  *Why it matters:* Allows administrators to optimize NFS performance and security based on network conditions and use cases.

- **NFS client-side caching back end support (ext3, ext4, XFS)**  
  *Changed:* FS-Cache supports specific file systems for caching back ends.  
  *Why it matters:* Provides reliable local caching infrastructure for NFS traffic, improving read performance and reducing server load.

- **NFS with TLS support** (Technology Preview in RHEL 10):
  - NFS now supports encrypted communication between clients and servers using TLS.
  - Requires kernel TLS (kTLS) support, which is also a Technology Preview.
  - Why it matters: Enhances NFS security by preventing traffic sniffing and ensuring encrypted RPC communication, though it may introduce performance overhead due to encryption.

- **NFS mount option fixes and IPv6 support** (RHEL 10):
  - `vers` option added for compatibility with `nfsvers`.
  - Fixed incorrect handling of square brackets in IPv6 addresses when using `nfs://` or `sshfs://` URLs (e.g., `nfs://[::1]/path`).
  - Why it matters: Ensures correct parsing of IPv6 addresses in NFS/sshfs URLs and improves compatibility with older NFS configurations.

- **NFS client-side caching (FS-Cache) improvements** (RHEL 10):
  - NFS shares can now be mounted with FS-Cache enabled for better performance and reduced server load.
  - Caching is transparent and does not require changes to the NFS share itself.
  - Supports partial caching of files (no need to read entire files upfront).
  - Cache errors are hidden from the client.
  - Requires a cache back end (ext3, ext4, or XFS) mounted at `/var/cache/fscache/` with extended attributes enabled.
  - Why it matters: Reduces network latency, improves performance for frequently accessed files, and decreases server load by caching data locally.

- **NFS mount options for performance tuning** (RHEL 10):
  - `rsize=num` and `wsize=num`: Set maximum bytes per read/write operation (default: 1,048,576 bytes).
  - `retrans=num`: Configures NFS client retry count for requests (default: 3 for UDP, 2 for TCP).
  - `timeo=num`: Sets timeout (in tenths of a second) before retrying requests (default: 600 for TCP).
  - `port=num`: Specifies NFS server port (default: 0 queries `rpcbind` for NFSv3, standard port 2049 for NFSv4).
  - `noacl`: Disables ACL processing for compatibility with older NFS servers.
  - `noexec`: Prevents execution of binaries (useful for non-Linux file systems).
  - `nosuid`: Disables `setuid`/`setgid` bits to prevent privilege escalation.
  - Why it matters: These options allow fine-tuning of NFS performance and security based on server/client capabilities and network conditions.

- **NFS security options (`sec=options`)** (RHEL 10):
  - `sec=sys`: Uses local UNIX UIDs/GIDs (default, least secure).
  - `sec=krb5`: Uses Kerberos V5 for authentication (more secure).
  - `sec=krb5i`: Adds integrity checking to Kerberos V5 (prevents tampering).
  - `sec=krb5p`: Encrypts NFS traffic (most secure, highest performance overhead).
  - Why it matters: Provides flexibility to balance security and performance needs.

- **Fixed NFS-related bugs** (RHEL 10):
  - `fstrim` now enabled by default on LUKS2 root in ostree-based installations (prevents unresponsive systems or broken file chooser dialogs).
  - Why it matters: Ensures proper discard handling for encrypted storage, improving system responsiveness.

- **NFS with TLS support** (Technology Preview in RHEL 10):
  - NFS now supports TLS for RPC traffic to encrypt communication between clients and servers.
  - Why it matters: Enhances NFS security by preventing traffic sniffing, though it may introduce performance overhead due to encryption.

- **NFS client IPv6 address handling** (Fixed in ReaR):
  - IPv6 addresses in NFS URLs (e.g., `nfs://[2001:db8:ca2:6::101]/root/REAR`) are now correctly parsed without errors.
  - Why it matters: Enables seamless use of IPv6 addresses in NFS configurations, avoiding premature termination or workarounds.

- **NFS mount options (`rsize`, `wsize`)**:
  - Default and maximum values for `rsize` and `wsize` increased to **1,048,576 bytes** (1 MiB) in RHEL 10.
  - Why it matters: Larger read/write sizes improve NFS performance by reducing the number of operations needed for data transfer.

- **NFS client-side caching with FS-Cache**:
  - NFS shares can now be mounted with **FS-Cache enabled** to cache data locally, reducing server load and improving performance.
  - Why it matters: Transparently improves NFS performance for repeated reads by serving data from local cache instead of the network.

- **Cache backends for FS-Cache**:
  - Supported cache backends are **XFS**, **ext3**, and **ext4** (must support block mapping and extended attributes).
  - Why it matters: Ensures compatibility with common local file systems for caching NFS content.

- **`cachefilesd` service configuration**:
  - The `cachefilesd` daemon manages client-side caching for NFS via FS-Cache.
  - Why it matters: Proper configuration is essential for enabling and optimizing NFS caching performance.

- **NFS with TLS support** (Technology Preview in RHEL 10):
  - NFS now supports TLS for RPC traffic to encrypt communication between clients and servers.
  - Why it matters: Enhances NFS security by preventing traffic sniffing, though it may introduce performance overhead due to encryption.

- **NFS client IPv6 address handling** (Fixed in ReaR):
  - IPv6 addresses in NFS URLs (e.g., `nfs://[2001:db8:ca2:6::101]/root/REAR`) are now correctly parsed without errors.
  - Why it matters: Enables seamless use of IPv6 addresses in NFS configurations, avoiding premature termination or workarounds.

- **NFS mount options (`rsize`, `wsize`)**:
  - Default and maximum values for `rsize` and `wsize` increased to **1,048,576 bytes** (1 MiB) in RHEL 10.
  - Why it matters: Larger read/write sizes improve NFS performance by reducing the number of operations needed for data transfer.

- **NFS client-side caching with FS-Cache**:
  - NFS shares can now be mounted with **FS-Cache enabled** to cache data locally, reducing server load and improving performance.
  - Why it matters: Transparently improves NFS performance for repeated reads by serving data from local cache instead of the network.

- **Cache backends for FS-Cache**:
  - Supported cache backends are **XFS**, **ext3**, and **ext4** (must support block mapping and extended attributes).
  - Why it matters: Ensures compatibility with common local file systems for caching NFS content.

- **`cachefilesd` service configuration**:
  - The `cachefilesd` daemon manages client-side caching for NFS via FS-Cache.
  - Why it matters: Proper configuration is essential for enabling and optimizing NFS caching performance.

- **NFS with TLS support**: RHEL 10 offers NFS with Transport Layer Security (TLS), enhancing security by enabling encrypted communication between clients and servers. This feature relies on kernel TLS (kTLS), provided as a Technology Preview.
- **IPv6 address parsing fix**: A bug affecting the use of IPv6 addresses in sshfs:// and nfs:// URLs has been fixed. Now, square brackets around IPv6 addresses are correctly interpreted, allowing their use in these URL schemes.
- **NFS client-side caching**: RHEL 10 introduces client-side caching for NFS using FS-Cache, which can improve performance, reduce server load, and enable efficient local data retrieval. FS-Cache requires a compatible cache back-end file system (XFS, ext3, or ext4) and can be configured using the`/etc/cachefilesd.conf` file.<|END_OF_TURN_TOKEN|>

- **NFS with TLS support**: RHEL 10 offers NFS with Transport Layer Security (TLS), enhancing security by enabling encrypted communication between clients and servers. This feature relies on kernel TLS (kTLS), provided as a Technology Preview.
- **IPv6 address parsing fix**: A bug affecting the use of IPv6 addresses in sshfs:// and nfs:// URLs has been fixed. Now, square brackets around IPv6 addresses are correctly interpreted, allowing their use in these URL schemes.
- **NFS client-side caching**: RHEL 10 introduces client-side caching for NFS using FS-Cache, which can improve performance, reduce server load, and enable efficient local data retrieval. FS-Cache requires a compatible cache back-end file system (XFS, ext3, or ext4) and can be configured using the`/etc/cachefilesd.conf` file.<|END_OF_TURN_TOKEN|>