# Witness Protocol Feature - Detailed Design Document

## 1. Overview

The SMB Witness Protocol enables rapid notification of resource changes in a clustered file server environment. It provides fast failover capabilities by allowing clients to register for notifications about server node availability, share movement, and other critical cluster events.

## 2. Protocol Specification Reference

- **MS-SWN**: Service Witness Protocol Specification

        final Smb2TransformHeader header = new Smb2TransformHeader();

        // Check protocol ID
        final int protocolId = SMBUtil.readInt4(buffer, bufferIndex);
        if (protocolId != TRANSFORM_PROTOCOL_ID) {
            throw new IllegalArgumentException("Invalid transform header protocol ID: 0x" + Integer.toHexString(protocolId));
        }
        bufferIndex += 4;

        // Read signature

            }
        } else {
            failedValidations.incrementAndGet();
            log.warn("Invalid SMB protocol ID: 0x{}", Integer.toHexString(protocolId));
            throw new SmbException("Invalid SMB protocol identifier");
        }

        // Validate command is in valid range
        if (command < 0 || command > 255) {
            failedValidations.incrementAndGet();

 */
package jcifs.internal.util;

import jcifs.SmbConstants;

/**
 * SMB protocol utility class providing low-level data encoding and decoding operations.
 * Contains methods for reading and writing various data types (integers, strings, timestamps)
 * in SMB protocol format, handling endianness and data type conversions.
 *
 * @author mbechler
 */
public class SMBUtil {

    /**

- Delete deprecated `service.beta.kubernetes.io/azure-load-balancer-mixed-protocols` mixed procotol annotation in favor of the MixedProtocolLBService feature ([#97096](https://github.com/kubernetes/kubernetes/pull/97096), [@nilo19](https://github.com/nilo19)) [SIG Cloud Provider]

- GCE does not support LoadBalancer Services with ports with different protocols (TCP and UDP) ([#115966](https://github.com/kubernetes/kubernetes/pull/115966), [@aojea](https://github.com/aojea)) [SIG Apps and Cloud Provider]

## Origen

Un origen es la combinación de protocolo (`http`, `https`), dominio (`myapp.com`, `localhost`, `localhost.tiangolo.com`) y puerto (`80`, `443`, `8080`).

Así que, todos estos son orígenes diferentes:

* `http://localhost`
* `https://localhost`
* `http://localhost:8080`

Aunque todos están en `localhost`, usan protocolos o puertos diferentes, por lo tanto, son "orígenes" diferentes.

## Pasos

## Origem

Uma origem é a combinação de protocolo (`http`, `https`), domínio (`myapp.com`, `localhost`, `localhost.tiangolo.com`), e porta (`80`, `443`, `8080`).

Então, todos estes são origens diferentes:

* `http://localhost`
* `https://localhost`
* `http://localhost:8080`

Mesmo se todos estiverem em `localhost`, eles usam diferentes protocolos e portas, portanto, são "origens" diferentes.

## Passos

- Fixes high CPU usage in kubectl drain ([#95260](https://github.com/kubernetes/kubernetes/pull/95260), [@amandahla](https://github.com/amandahla)) [SIG CLI]
- Kube-apiserver: multiple comma-separated protocols in a single X-Stream-Protocol-Version header are now recognized, in addition to multiple headers, complying with RFC2616 ([#89857](https://github.com/kubernetes/kubernetes/pull/89857), [@tedyu](https://github.com/tedyu)) [SIG API Machinery]

- To ensure the code be strong,  add unit test for GetAddressAndDialer ([#93180](https://github.com/kubernetes/kubernetes/pull/93180), [@FreeZhang61](https://github.com/FreeZhang61)) [SIG Node]
- UDP and SCTP protocols can left stale connections that need to be cleared to avoid services disruption, but they can cause problems that are hard to debug.