Partial

RFC 3162 - RADIUS and IPv6

Every requirement this repository extracted from RFC 3162, the tests bound to it, and what a reader has verified about them. This summary is enrolled and gated by ./le rfc check.

Overview

Positive

what Ze has

Tested both ways0.0%0 of 6 gated MUSTs

a positive test proves Ze does what the requirement demands and a negative one proves it refuses what the requirement forbids

One polarity plus reason50.0%3 of 6 gated MUSTs

the requirement admits no counter-case, so one polarity plus a recorded reason is the whole proof available for it

One polarity, unexcused0.0%0 of 6 gated MUSTs

one direction is tested, the other is neither tested nor excused, and nothing states which

Partial proof; remaining gap0.0%0 of 6 gated MUSTs

scoped tests exist; the remaining obligation is unmet or unproven, with zero whole-requirement credit

Proven by a recorded break100.0%3 of 3 tagged units

a red was observed once under a recorded procedure, and the unit, the claim and the producer it rested on still hash to what was recorded. The break is not re-run. A test pair is not a proof until one has been observed

Neutral

measures that are neither good news nor bad

Gated MUSTs6of 13 this summary declares

MUST-level requirements the gate HOLDS. A population, not a result: the shares beside it are what says how Ze stands

Out of scope0of 6 gated MUSTs

an obligation that does not bind Ze. A {not-applicable} annotation says it never bound; a {feature-declined} annotation says its condition is an optional feature Ze does not offer, and quotes the RFC sentence that makes it optional. Scope, not coverage: it stays in the denominator every share on this page is taken over

Not applicable0.0%0 of 6 gated MUSTs

a {not-applicable} annotation says the obligation does not bind Ze, so no test is owed for it. It stays in the denominator every share here is taken over

Met below Ze0.0%0 of 6 gated MUSTs

a {lower-layer} annotation says a layer under Ze performs the behavior, on state Ze installs into that layer, and names the producer that installs it. The obligation binds Ze and is met; Ze proves none of it, because its own boundary carries no value the behavior reads

Optional feature declined0.0%0 of 6 gated MUSTs

a {feature-declined} annotation says the obligation is conditional on a feature the RFC makes optional and Ze does not offer, and it quotes the sentence that makes it optional. The condition is false, so nothing is owed and nothing is missing. It stays in the denominator every share here is taken over

Linux cannot do this0.0%0 of 6 gated MUSTs

Linux cannot provide the primitive this requirement needs. The obligation still binds Ze and remains unmet; it stays in every denominator and earns no proof credit

Negative

what Ze owes

No test at all50.0%3 of 6 gated MUSTs

no test carries the requirement id, whether or not a gap states why

The 9 shares marked as a part above are the whole of the 6 gated MUSTs: they add to 100%. Proven by a recorded break is a share of TAGGED UNITS, a different population, so it is not one of them.

How to read the colors

A color names what the measure MEANS, not how well Ze scores on it. Green is a good outcome at any value, red is a bad one, and neither a population nor a scope count is an outcome, so both take no color. The number under the label is what says how far Ze has got.

Card	Tone here	Why that color
Gated MUSTs	neutral	no color: a population is a scale, and a larger one is neither good news nor bad. It is the accounting total
Out of scope	neutral	no color: an obligation that never bound Ze is neither an achievement nor a failure, and counting it either way would be a claim
Tested both ways	ok	green at every value: a test pair is the outcome this gate exists to produce, and the share under the label is what says how far Ze has got
One polarity plus reason	ok	green at every value: where no counter-case exists, one polarity IS the complete answer, and a recorded reason is what the gate demands beside it
One polarity, unexcused	ok	green at zero, RED above it: half a proof with no reason for the other half
Partial proof; remaining gap	ok	green at zero, RED above it: a tested clause cannot prove the whole requirement
No test at all	bad	green at zero, RED above it: a binding obligation nothing exercises is a claim with nothing behind it, whether or not a reason is stated
Not applicable	neutral	no color: an obligation that never bound Ze is neither an achievement nor a failure, and counting it either way would be a claim
Met below Ze	neutral	no color: an obligation met below Ze is neither a test Ze wrote nor work Ze owes, and the two green shares above are what says how much Ze proves itself
Optional feature declined	neutral	no color: an obligation whose condition Ze never meets is neither an achievement nor a failure. The absent FEATURE is disclosed on the RFC's own status row, as an implementation gap a later scope decision can revisit
Linux cannot do this	neutral	neutral at every value: an evidenced platform limit is neither a proof nor a scope exemption
Proven by a recorded break	ok	green at every value: an observed break is the outcome the discrimination gate exists to produce. The denominator is TAGGED UNITS, not obligations, so this share is not one of the parts above
Audit verdicts	warn	RED on the first weak, wrong or unimplemented verdict, amber while a verdict is no longer current or a gated MUST is unjudged, green when every one is judged sound and current

At a glance

Field	Value
Public status	Partial
Enrolment	Enrolled
Requirements	13
Gated MUST-level	6
Not applicable, so out of scope	0
Declared gaps	3
Declared gaps a test demonstrates	0
Gated with no test	0
Nightly-only evidence	0
Test tags	3
Tagged units	3
Recorded audit verdicts	0
Discrimination records	3
Summary	`rfc/short/rfc3162.md`
Requirement shard	`rfc/requirements/rfc3162.md`
RFC text	`rfc/full/rfc3162.txt`

Enrolment

Enrolled: Ze is a RADIUS NAS for L2TP subscribers (internal/component/l2tp/plugins/authradius) and so the client this document addresses. Walked site by site on 2026-10-26 (rfc/extraction/rfc3162.json). Every MUST is classified: RFC3162-2.1-1, RFC3162-2.5-1 and RFC3162-2.6-1 are met by the producers they name and owe tests; RFC3162-3.2-1 (no Framed-Interface-Id in a re-authentication Access-Request), RFC3162-2.3-1 (no Framed-IPv6-Prefix encoding) and RFC3162-5-1 (no zero-length secret over IPsec ESP) are gaps owned by plan/release/fixes/spec-radius-rfc3162-ipv6-attributes.md, because no owner ruling names those features unwanted (ai/META-DECISIONS.md, Goal and scope).

What the public ledger says

Status: Partial

What the ledger says is covered

Framed-IPv6-Route (99) is read from the Access-Accept and installed as a subscriber route (authradius/extract.go extractFramedRoutes). An Access-Request from an IPv6-only NAS carries a NAS-Identifier (authradius/nasidentity.go appendNASIdentity). Framed-IPv6-Pool (100) is ignored, as a NAS without prefix pools must. CoA recognises NAS-IPv6-Address, Framed-Interface-Id and Framed-IPv6-Prefix as identifiers (authradius/coa.go).

What the ledger says remains

NAS-IPv6-Address is never sent; Framed-Interface-Id, Framed-IPv6-Prefix and Login-IPv6-Host in an Access-Accept are ignored, so a RADIUS server cannot assign a subscriber's IPv6 prefix or interface identifier.

Three MUST rows are gaps: no Framed-Interface-Id in a re-authentication Access-Request after IPv6CP (RFC3162-3.2-1), no Framed-IPv6-Prefix encoding (RFC3162-2.3-1), no zero-length secret for RADIUS over IPsec ESP (RFC3162-5-1). RFC3162-2.1-1, RFC3162-2.5-1 and RFC3162-2.6-1 carry tagged tests with recorded discrimination (rfc/discrimination/rfc3162).

Coverage

Bucket	Count	What it counts
Positive and negative tests	0	one part of the gated population
Annotated (including scoped evidence)	6	one part of the gated population
One polarity only	0	one part of the gated population
No test and no annotation	0	one part of the gated population
Partial proof; remaining gap (subset of annotated; zero whole-requirement credit)	0	an overlay: each of these is also counted by the part it falls in
Evidence that runs nightly only	0	an overlay: each of these is also counted by the part it falls in
Derived from other rows	0	outside the gated population: each asserts nothing and derives its state from the rows it names, which the parts above already count
Gated MUST-level requirements	6	every gated MUST falls in exactly one bucket above

Annotated (including scoped evidence) (6): RFC3162-2.1-1, RFC3162-3.2-1, RFC3162-2.3-1, RFC3162-2.5-1, RFC3162-2.6-1, RFC3162-5-1

Attainable ceiling

Mandatory ceiling: 6 of 6 (100.0%). Optional ceiling: 7 of 7 (100.0%). Every RFC shown with measured rows can reach 100% under current classifications. Lowest mandatory ceiling: rfc3162 6 of 6 (100.0%). Lowest optional ceiling: rfc3162 7 of 7 (100.0%). Ceilings describe current classifications, not an immutable Linux maximum. Not-applicable and feature-declined classifications can be revisited. Every gap remains work Ze owes.

Requirements

Requirement	Level	Section	Tests
`RFC3162-2.1-1`	NAS-IPv6- Address and/or NAS-IP-Address MAY be present in an Access-Request packet; however, if neither attribute is present then NAS- Identifier MUST be present. (§2.1)
	MUST	2.1 - NAS-IPv6-Address	positive`unit/verifyTestRFC3162AccessRequestFromAnIPv6SourceNamesTheNAS` negative`no test`no negative test {single-polarity}: the fallback is an addition to the packet, so its other direction, a configured NAS-IP-Address making the NAS-Identifier optional, is RFC 2865 Section 4.1 behaviour proven by TestRFC2866AcctNASIdentityFallbackIsNarrow under RFC2866-4.1-3, not a separate obligation of this sentence
`RFC3162-3.2-1`	If the Interface-Identifier IPv6CP option [11] has been successfully negotiated, this Attribute MUST be included in an Access-Request packet as a hint by the NAS to the server that it would prefer that value. (§3.2)
	MUST	3.2	positive`no test`no positive test negative`no test`no negative test {gap}: Ze never sends Framed-Interface-Id: internal/component/l2tp/plugins/authradius/handler.go::buildAccessRequestAttrs writes no such attribute, and with authentication reauth-interval set, internal/component/l2tp/ppp/session_run.go runs runAuthPhase again on an established CHAP session, so a re-authentication Access-Request leaves after IPv6CP negotiated an Interface-Identifier and omits it; no owner ruling names this feature unwanted (ai/META-DECISIONS.md, Goal and scope)
`RFC3162-2.3-1`	This field, which is reserved and MUST be present, is always set to zero. (§2.3)
	MUST	2.3 - Framed-IPv6-Prefix	positive`no test`no positive test negative`no test`no negative test {gap}: Ze implements no Framed-IPv6-Prefix encoding: internal/component/l2tp/plugins/authradius/handler.go::buildAccessRequestAttrs and internal/component/l2tp/plugins/authradius/acct.go::buildAcctPacket write none, so no Reserved field is ever written; no owner ruling names this feature unwanted (ai/META-DECISIONS.md, Goal and scope)
`RFC3162-2.5-1`	It is intended to be human readable and MUST NOT affect operation of the protocol. (§2.5)
	MUST NOT	2.5 - Framed-IPv6-Route	positive`no test`no positive test negative`unit/verifyTestRFC3162FramedIPv6RouteTextDoesNotStopTheAccept` {single-polarity}: the obligation is that the text affects nothing outside its own route, and no well-formed or malformed text exists for which stopping the Access-Accept would be correct
`RFC3162-2.6-1`	If a NAS does not support multiple prefix pools, the NAS MUST ignore this Attribute. (§2.6)
	MUST	2.6 - Framed-IPv6-Pool	positive`unit/verifyTestRFC3162FramedIPv6PoolIsIgnored` negative`no test`no negative test {single-polarity}: ze supports no prefix pools in any configuration, so the attribute is ignored unconditionally and there is no case in which acting on it would be correct
`RFC3162-5-1`	In this case, a shared secret of zero length MUST be assumed. (§5)
	MUST	5 - Security Considerations	positive`no test`no positive test negative`no test`no negative test {gap}: internal/component/radius/client.go::Exchange refuses an empty shared secret (RFC 2865 Section 3), so RADIUS run over IPsec ESP with no configured secret is refused rather than run with a zero-length secret; no owner ruling names this feature unwanted (ai/META-DECISIONS.md, Goal and scope)
`RFC3162-2.1-2`	This Attribute indicates the identifying IPv6 Address of the NAS which is requesting authentication of the user, and SHOULD be unique to the NAS within the scope of the RADIUS server. (§2.1)
	SHOULD	2.1 - NAS-IPv6-Address	positive`no test`no positive test negative`no test`no negative test
`RFC3162-2.5-2`	Whenever the gateway address is the IPv6 unspecified address the IP address of the user SHOULD be used as the gateway address. (§2.5)
	SHOULD	2.5 - Framed-IPv6-Route	positive`no test`no positive test negative`no test`no negative test
`RFC3162-2.6-2`	This Attribute contains the name of an assigned pool that SHOULD be used to assign an IPv6 prefix for the user. (§2.6)
	SHOULD	2.6 - Framed-IPv6-Pool	positive`no test`no positive test negative`no test`no negative test
`RFC3162-3.2-2`	It MAY be used in Access-Accept packets. (§3.2)
	MAY	3.2	positive`no test`no positive test negative`no test`no negative test
`RFC3162-2.3-2`	It MAY be used in Access-Accept packets, and can appear multiple times. (§2.3)
	MAY	2.3 - Framed-IPv6-Prefix	positive`no test`no positive test negative`no test`no negative test
`RFC3162-2.3-3`	It MAY be used in an Access-Request packet as a hint by the NAS to the server that it would prefer these prefix(es), but the server is not required to honor the hint. (§2.3)
	MAY	2.3 - Framed-IPv6-Prefix	positive`no test`no positive test negative`no test`no negative test
`RFC3162-2.4-1`	It MAY be used in an Access- Request packet as a hint to the server that the NAS would prefer to use that host, but the server is not required to honor the hint. (§2.4)
	MAY	2.4 - Login-IPv6-Host	positive`no test`no positive test negative`no test`no negative test

Gaps and untested MUSTs

Requirement	State	Reason
`RFC3162-3.2-1` If the Interface-Identifier IPv6CP option [11] has been successfully negotiated, this Attribute MUST be included in an Access-Request packet as a hint by the NAS to the server that it would prefer that value. (§3.2)	{gap}, no test	Ze never sends Framed-Interface-Id: internal/component/l2tp/plugins/authradius/handler.go::buildAccessRequestAttrs writes no such attribute, and with authentication reauth-interval set, internal/component/l2tp/ppp/session_run.go runs runAuthPhase again on an established CHAP session, so a re-authentication Access-Request leaves after IPv6CP negotiated an Interface-Identifier and omits it; no owner ruling names this feature unwanted (ai/META-DECISIONS.md, Goal and scope)
`RFC3162-2.3-1` This field, which is reserved and MUST be present, is always set to zero. (§2.3)	{gap}, no test	Ze implements no Framed-IPv6-Prefix encoding: internal/component/l2tp/plugins/authradius/handler.go::buildAccessRequestAttrs and internal/component/l2tp/plugins/authradius/acct.go::buildAcctPacket write none, so no Reserved field is ever written; no owner ruling names this feature unwanted (ai/META-DECISIONS.md, Goal and scope)
`RFC3162-5-1` In this case, a shared secret of zero length MUST be assumed. (§5)	{gap}, no test	internal/component/radius/client.go::Exchange refuses an empty shared secret (RFC 2865 Section 3), so RADIUS run over IPsec ESP with no configured secret is refused rather than run with a zero-length secret; no owner ruling names this feature unwanted (ai/META-DECISIONS.md, Goal and scope)

Proof state

A tagged unit reads unproven where no discrimination record exists for it: nothing in this tree has been observed to break it, so the claim its tag makes is unproven.

`RFC3162-2.1-1`

NAS-IPv6- Address and/or NAS-IP-Address MAY be present in an Access-Request packet; however, if neither attribute is present then NAS- Identifier MUST be present. (§2.1)