CARVIEW |
Select Language
HTTP/2 200
date: Fri, 01 Aug 2025 15:49:56 GMT
content-type: text/html; charset=utf-8
content-security-policy: default-src 'self' 'unsafe-inline' data: https://datatracker.ietf.org/ https://www.ietf.org/ https://ietf.org/ https://analytics.ietf.org https://static.ietf.org; frame-ancestors 'self' ietf.org *.ietf.org meetecho.com *.meetecho.com
cross-origin-opener-policy: unsafe-none
referrer-policy: strict-origin-when-cross-origin
strict-transport-security: max-age=3600; includeSubDomains
vary: Cookie, Accept-Encoding
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
cf-cache-status: MISS
expires: Fri, 01 Aug 2025 19:49:56 GMT
cache-control: public, max-age=14400
set-cookie: __cf_bm=1BW4HWRUdnWxWLxhz0apZErsKE9FSrxSOys2foAWhkk-1754063396-1.0.1.1-upkjqEfR_zhWfJTZrKORPi6mAxYtLNdySEvEVeOvQJUn1lSjTrvFSLUYkefbYJevLORPjQgbngKU.Sn9Y42oLjGxM09gA4Zp9bjFqxHv1qo; path=/; expires=Fri, 01-Aug-25 16:19:56 GMT; domain=.ietf.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 96867cff6d56a403-BLR
content-encoding: gzip
alt-svc: h3=":443"; ma=86400
TCP Client Identity Protocol (ident)
Skip to main content
Concluded WG TCP Client Identity Protocol (ident)
Note: The data for concluded WGs is occasionally incorrect.
WG | Name | TCP Client Identity Protocol | |
---|---|---|---|
Acronym | ident | ||
Area | Security Area (sec) | ||
State | Concluded | ||
Charter | charter-ietf-ident-01 Approved | ||
Document dependencies |
Document dependencies
Loading...
|
||
Personnel | Chair | Michael StJohns | |
Mailing list | Address | ident@nri.reston.va.us | |
To subscribe | ident-request@nri.reston.va.us | ||
Archive | cnri.reston.va.us:~/ietf.mailing.lists/ident/* |
Final Charter for Working Group
The TCP Client Identity Protocol Working Group is chartered to define
a protocol for returning the identity of the user initiating a TCP
connection. When a client on host A initiates a TCP connection to
host B, host B may query a server on host A to determine the identity
of the client on host A. The primary purpose of this protocol is to
record the identity of requesters initiating a connection.
This work is a clarification and standardization of the Experimental
Protocol currently published as RFC 931.
Done milestones
Date | Milestone | Associated documents |
---|---|---|
Done | Review implementations, and resolve outstanding issues in preparation for Draft Standard. | |
Done | Submit the Identity Server Protocol to the IESG for consideration as a Proposed Standard. | |
Done | Post an Internet-Draft of the revised RFC 931 Identity Server Protocol. |