IETF

The October 8 approval gives the DNS-SD working group a concrete list for discovery across one or more links, while keeping changes to general DNS outside its remit.

The IESG approved NETCONF charter 21 on 9 October. Its group history now records two 31 December targets for submitting YANG-Push and List Pagination drafts to the IESG for publication as Proposed Standards. Those are work-plan dates, not promises of approval or deployment.

The IESG approved Agentproto’s charter on 8 October, setting December 2026 as the first target for adopting an informational use-cases draft. A document updated on 15 October is already visible in the IETF’s related-drafts list, but its own record still calls it an individual Internet-Draft. The distinction is the first test of the new work plan: a fresh upload is not the same act as working-group adoption.

The 2026–2027 IETF Nominating Committee has moved the deadline for accepting nominations by two weeks. Its public home page still shows the earlier close, slate and interview dates, leaving candidates with two unreconciled versions of the calendar.

By the time BGP appeared in an RFC, Cisco routers and NSFNET’s Nodal Switching Systems already had implementations. The June 1989 document captured a protocol still taking shape; a year later, its successor was a proposed standard that openly invited deployment experience to change it.

The RFC Editor queue showed a clean YANG validation for revision 44, but the proposed RFC was still in final review with two author approvals unrecorded and a possible cluster hold.

A common RADIUS attribute can carry a user-group label into an access-control system. RFC 10065 still leaves group definition and the mapping to packet fields to each deployment.

The IESG has approved the charter that PROCON put forward for review in September. Its new schedule sets November targets for two process-document submissions and December for work on the IETF Chair’s authorities; the decision assigns work, but changes no rule yet.

The IETF’s “hum” could make a room’s direction audible, but it was never meant to settle a technical question by volume. RFC 7282 turned that distinction into a practical account of rough consensus: surface objections, examine them, and explain the chair’s judgment before work moves on.

Usenet needed a compact way to distinguish a moderator’s decision from an ordinary reader’s submission. The `Approved:` header supplied that signal; it did not authenticate the person named in it. The difference mattered because the same marker sat at the boundary between discussion, network distribution and commands that could change the newsgroup structure itself.

Usenet needed a compact way to distinguish a moderator’s decision from an ordinary reader’s submission. The `Approved:` header supplied that signal; it did not authenticate the person named in it. The difference mattered because the same marker sat at the boundary between discussion, network distribution and commands that could change the newsgroup structure itself.

In 1981, IPv4 gained a small field for recording where a packet had been processed and when. Its design resembles a route diary, but it cannot be read as a synchronized stopwatch for network delay.

A 16-bit field made room for two different zeros: one was a computed checksum, the other a signal that no checksum had been sent. The distinction began in UDP’s 1980 specification and later met stricter rules in IPv6.

A 1989 standard made multicast membership visible to neighboring routers with a deliberately economical signal: one host report could speak for a whole local group, while silence after departure had to age out.

Three authoritative DNS names on a zone did not create three independent ways to reach it. In 1997, BCP 16 made location and network topology part of the redundancy decision.

In 1995, engineers wanted DNS to steer requests toward a less-loaded machine without changing the protocol or breaking the installed base. The compromise could rank addresses before a reply went out. It could not make every resolver or application obey that ranking.

Internet Relay Chat moved from an unreliable feature on OuluBox to a network of independently run servers before RFC 1459 described its operating rules in 1993.

The two October 1989 Host Requirements standards did not invent the Internet’s protocols. They gave vendors and implementers a shared account of what a working host needed to do, after a long effort that ranked interoperability above architectural neatness.