RFC 3977

E827892

RFC 3977 is the Internet standard that defines the Network News Transfer Protocol (NNTP), updating and replacing the earlier specification in RFC 977.

Try in SPARQL Jump to: Statements Referenced by

Statements (46)

Predicate Object
instanceOf Internet standard
Request for Comments
abbrev NNTP NERFINISHED
area Applications Area
category Standards Track
defines article retrieval mechanisms for NNTP
authentication framework for NNTP
capability negotiation for NNTP
client-server protocol for reading and posting Usenet articles
commands for NNTP
error codes for NNTP
group selection mechanisms for NNTP
message formats for NNTP
responses for NNTP
streaming extensions for NNTP
definesConformanceRequirementsFor NNTP implementations
definesProtocol Network News Transfer Protocol NERFINISHED
documentType Standards-track protocol specification
intendedAudience implementers of NNTP clients
implementers of NNTP servers
language English
obsoletes RFC 977
obsoletesSpecification Network News Transfer Protocol as defined in RFC 977
partOf NNTP standards family
portNumber 119
publishedBy Internet Engineering Task Force
surface form: IETF

Internet Engineering Task Force
publishedInSeries Request for Comments NERFINISHED
relatedTo Internet messaging
Usenet NERFINISHED
email-like protocols
replaces original NNTP specification
rfcNumber 3977
securePortNumber 563
specifies article numbering and message identifiers in NNTP
capability discovery via CAPABILITIES command
error handling rules for NNTP
group status and article range reporting in NNTP
minimum feature set for compliant NNTP clients
minimum feature set for compliant NNTP servers
use of UTF-8 in certain NNTP contexts
standardizes NNTP over TCP NERFINISHED
status Proposed Standard
title Network News Transfer Protocol (NNTP) NERFINISHED
updatesSpecificationOf Network News Transfer Protocol NERFINISHED
usesTransportProtocol TCP NERFINISHED

Referenced by (1)

Full triples — surface form annotated when it differs from this entity's canonical label.

RFC 977 supersededBy RFC 3977