No row in the public ledger

RFC 905 - ISO Transport Protocol Specification (ISO DP 8073)

Every requirement this repository extracted from RFC 905, 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 ways72.7%8 of 11 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 reason0.0%0 of 11 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 11 gated MUSTs

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

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

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

No test at all0.0%0 of 11 gated MUSTs

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

Proven by a recorded break79.3%23 of 29 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 MUSTs11of 11 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 scope3of 11 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 applicable27.3%3 of 11 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 11 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 11 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

The 8 shares marked as a part above are the whole of the 11 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	ok	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
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	No row in the public ledger
Enrolment	Enrolled
Requirements	11
Gated MUST-level	11
Not applicable, so out of scope	3
Declared gaps	0
Declared gaps a test demonstrates	0
Gated with no test	0
Nightly-only evidence	0
Test tags	29
Tagged units	29
Recorded audit verdicts	8
Discrimination records	23
Summary	`rfc/short/rfc905.md`
Requirement shard	`rfc/requirements/rfc905.md`
RFC text	`rfc/full/rfc905.txt`

Enrolment

Enrolled: ISO Transport Protocol: nine MUST-level requirements. The six that ze realizes are the Annex B Fletcher checksum (mod-255 arithmetic, two-pass generation, verify-both-sums-zero, OSPF LSA checksum excluding LS Age, encode+decode vectors) -- x-1,x-2,x-3,x-4,x-6,x-7 -- each bound with positive+negative tags on the IS-IS (internal/plugins/isis/packet/checksum.go) and OSPF (internal/plugins/ospf/types/checksum.go, ospf/packet/checksum.go) checksum tests. The three ISO Transport TPDU MUSTs (6.17.3-1 generation, 6.17.3-2 receive/verify-and-discard, 13.2.3.1-1 0xC3 checksum parameter) are {not-applicable}: ze has no ISO Transport TPDU sender/receiver and no 0xC3 transport-checksum-parameter code path.

What the public ledger says

No row in the public ledger, so its summary declares `| Support | - |` and docs/features/rfc-status.md carries no row for RFC 905.

Coverage

Bucket	Count	What it counts
Positive and negative tests	8	one part of the gated population
Annotated (including scoped evidence)	3	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	11	every gated MUST falls in exactly one bucket above

Positive and negative tests (8): RFC905-x-1, RFC905-x-2, RFC905-x-3, RFC905-x-4, RFC905-B.3.1-1, RFC905-B.3.2-1, RFC905-B.3.5-1, RFC905-B.4.2-1

Annotated (including scoped evidence) (3): RFC905-6.17.3-1, RFC905-6.17.3-2, RFC905-13.2.3.1-1

Requirements

Requirement	Level	Section	Tests
`RFC905-6.17.3-1`	The sending transport entity shall transmit TPDUs with the checksum parameter set such that the following formulas are satisfied: SUM(from i=1 to i=L) OF a[i] EQUALS <zero> (module 255) SUM(from i=1 to i=L) OF i*a[i] EQUALS <zero> (module 255) (§6.17.3)
	MUST	6.17.3	positive`no test`no positive test negative`no test`no negative test {not-applicable}: ze implements the RFC 905 Annex B Fletcher checksum (reused by IS-IS at internal/plugins/isis/packet/checksum.go and OSPF at internal/plugins/ospf/types/checksum.go) but has no ISO Transport Protocol TPDU generator that sets a transport checksum parameter (grep for TPDU/TP4/0xC3 across internal/ is empty)
`RFC905-6.17.3-2`	A transport entity which receives a TPDU for a transport connection for which the use of checksum has been agreed and which does not satisfy the above formulas shall discard the TPDU (§6.17.3)
	MUST	6.17.3	positive`no test`no positive test negative`no test`no negative test {not-applicable}: ze implements the RFC 905 Annex B Fletcher checksum (reused by IS-IS at internal/plugins/isis/packet/checksum.go and OSPF at internal/plugins/ospf/types/checksum.go) but has no ISO Transport Protocol TPDU receiver that verifies and discards a transport TPDU (grep for TPDU/TP4/0xC3 across internal/ is empty)
`RFC905-x-1`	Addition is performed in one of the two following modes: a) modulo 255 arithmetic; b) one's complement arithmetic in which if any of the variables has the value minus zero (i.e. 255) it shall be regarded as though it was plus zero (i.e. 0). (§B.2)
	MUST	B.2	positive`unit/verifyTestISISChecksumFixedVector` positive`unit/verifyTestISISChecksumModulus` positive`unit/verifyTestRFC905MinusZeroReadAsZero` negative`unit/verifyTestRFC905FaultySenderChecksumRefused`
`RFC905-x-2`	Process each octet sequentially from i = 1 to L by: a) adding the value of the octet to C0; then b) adding the value of C0 to C1. (§B.3)
	MUST	B.3	positive`unit/verifyTestISISChecksumVectors` negative`unit/verifyTestRFC905FaultySenderChecksumRefused`
`RFC905-x-3`	Calculate X and Y such that X = -C1 + (L-n).CO Y = C1 - (L-n+1).C0 (§B.3)
	MUST	B.3	positive`unit/verifyTestFletcherGenerateMatchesClosedForm` positive`unit/verifyTestFletcherRFC905Vectors` positive`unit/verifyTestISISChecksumFixedVector` positive`unit/verifyTestISISChecksumMatchesClosedForm` positive`unit/verifyTestISISChecksumVectors` positive`unit/verifyTestOSPFLSAChecksum` negative`unit/verifyTestFletcherGenerateRefusesMisplacedXY` negative`unit/verifyTestISISChecksumRefusesMisplacedXY`
`RFC905-x-4`	If, when all the octets have been processed, either or both of C0 and C1 does not have the value zero, the checksum formulas in 6.17 have not been satisfied. (§B.4)
	MUST	B.4	positive`unit/verifyTestFletcherVerifyRequiresBothSumsZero` positive`unit/verifyTestISISChecksumVectors` positive`unit/verifyTestISISVerifyRequiresBothSumsZero` negative`unit/verifyTestFletcherVerifyRequiresBothSumsZero` negative`unit/verifyTestISISChecksumDetectsCorruption` negative`unit/verifyTestISISVerifyRequiresBothSumsZero` negative`unit/verifyTestOSPFLSAChecksumExcludesAge`
`RFC905-B.3.1-1`	Set up the complete TPDU with the value of the checksum parameter field set to zero. (§B.3.1)
	MUST	B.3.1	positive`unit/verifyTestRFC905GeneratorZeroesTheFieldFirst` negative`unit/verifyTestRFC905SenderThatKeptTheFieldRefused`
`RFC905-B.3.2-1`	Initialize C0 and C1 to zero. (§B.3.2)
	MUST	B.3.2	positive`unit/verifyTestRFC905GeneratorStartsFromZeroSums` negative`unit/verifyTestRFC905SenderWithSeededSumsRefused`
`RFC905-B.3.5-1`	Place the values X and Y in octets n and (n + 1) respectively. (§B.3.5)
	MUST	B.3.5	positive`unit/verifyTestRFC905LSPPlacesXAtNAndYAtNPlus1` negative`unit/verifyTestRFC905LSPWithSwappedXYRefused`
`RFC905-B.4.2-1`	Process each octet of the TPDU sequentially from i = 1 to L by: a) adding the value of the octet to C0; then b) adding the value of C0 to C1. (§B.4.2)
	MUST	B.4.2	positive`unit/verifyTestRFC905VerifierAcceptsEveryPlacement` negative`unit/verifyTestRFC905VerifierReadsTheFirstAndLastOctet`
`RFC905-13.2.3.1-1`	Parameter Code: 1100 0011 Parameter Length: 2 Parameter Value: Result of checksum algorithm. This algorithm is specified in 6.17. (§13.2.3.1)
	MUST	13.2.3.1	positive`no test`no positive test negative`no test`no negative test {not-applicable}: ze implements the RFC 905 Annex B Fletcher checksum (reused by IS-IS at internal/plugins/isis/packet/checksum.go and OSPF at internal/plugins/ospf/types/checksum.go) but has no ISO Transport Protocol code path that encodes the 0xC3 transport checksum parameter (grep for TPDU/TP4/0xC3 across internal/ is empty)

Gaps and untested MUSTs

Requirement	State	Reason
`RFC905-6.17.3-1` The sending transport entity shall transmit TPDUs with the checksum parameter set such that the following formulas are satisfied: SUM(from i=1 to i=L) OF a[i] EQUALS <zero> (module 255) SUM(from i=1 to i=L) OF i*a[i] EQUALS <zero> (module 255) (§6.17.3)	no test	no test carries this requirement id; annotated {not-applicable}: ze implements the RFC 905 Annex B Fletcher checksum (reused by IS-IS at internal/plugins/isis/packet/checksum.go and OSPF at internal/plugins/ospf/types/checksum.go) but has no ISO Transport Protocol TPDU generator that sets a transport checksum parameter (grep for TPDU/TP4/0xC3 across internal/ is empty)
`RFC905-6.17.3-2` A transport entity which receives a TPDU for a transport connection for which the use of checksum has been agreed and which does not satisfy the above formulas shall discard the TPDU (§6.17.3)	no test	no test carries this requirement id; annotated {not-applicable}: ze implements the RFC 905 Annex B Fletcher checksum (reused by IS-IS at internal/plugins/isis/packet/checksum.go and OSPF at internal/plugins/ospf/types/checksum.go) but has no ISO Transport Protocol TPDU receiver that verifies and discards a transport TPDU (grep for TPDU/TP4/0xC3 across internal/ is empty)
`RFC905-13.2.3.1-1` Parameter Code: 1100 0011 Parameter Length: 2 Parameter Value: Result of checksum algorithm. This algorithm is specified in 6.17. (§13.2.3.1)	no test	no test carries this requirement id; annotated {not-applicable}: ze implements the RFC 905 Annex B Fletcher checksum (reused by IS-IS at internal/plugins/isis/packet/checksum.go and OSPF at internal/plugins/ospf/types/checksum.go) but has no ISO Transport Protocol code path that encodes the 0xC3 transport checksum parameter (grep for TPDU/TP4/0xC3 across internal/ is empty)

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.

`RFC905-6.17.3-1`

The sending transport entity shall transmit TPDUs with the checksum parameter set such that the following formulas are satisfied: SUM(from i=1 to i=L) OF a[i] EQUALS <zero> (module 255) SUM(from i=1 to i=L) OF i*a[i] EQUALS <zero> (module 255) (§6.17.3)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC905-6.17.3-1, so no unit is bound to it.

`RFC905-6.17.3-2`

A transport entity which receives a TPDU for a transport connection for which the use of checksum has been agreed and which does not satisfy the above formulas shall discard the TPDU (§6.17.3)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC905-6.17.3-2, so no unit is bound to it.

`RFC905-x-1`

Addition is performed in one of the two following modes: a) modulo 255 arithmetic; b) one's complement arithmetic in which if any of the variables has the value minus zero (i.e. 255) it shall be regarded as though it was plus zero (i.e. 0). (§B.2)

Audit verdict: enforced (the tests do what the requirement demands), fresh. B.2: addition modulo 255, or one's complement with 255 read as 0. Positive TestRFC905MinusZeroReadAsZero: VerifyChecksum accepts five 0xFF octets (mod 256, or one's complement keeping 255 distinct, leaves C0 non-zero and goes red) and every seed region where Checksum stored 255 for a computed zero. Negative TestRFC905FaultySenderChecksumRefused/modulo-256: the X,Y closed form solves mod 256 too, so a mod-256 verifier would accept the mod-256 sender's checksum and refuse the compliant one; the test requires the opposite, and its guard (faulty != Checksum's) goes red on a mod-256 Checksum. TestISISChecksumFixedVector pins 0x0b,0xed. The old single-octet-flip negative (not an arithmetic violation) was untagged. Recorded red on VerifyChecksum.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC905FaultySenderChecksumRefused`	unit/verify	revert, verified
positive	`TestRFC905MinusZeroReadAsZero`	unit/verify	revert, verified
positive	`TestISISChecksumFixedVector`	unit/verify	revert, verified
positive	`TestISISChecksumModulus`	unit/verify	revert, verified

`RFC905-x-2`

Process each octet sequentially from i = 1 to L by: a) adding the value of the octet to C0; then b) adding the value of C0 to C1. (§B.3)

Audit verdict: enforced (the tests do what the requirement demands), fresh. Re-judged 2026-09-30 under R-C1: row text and tagged units unchanged; the Annex B steps around it now carry their own rows (B.3.1-1, B.3.2-1, B.3.5-1, B.4.2-1). B.3.3 order binds the generator: TestISISChecksumVectors round-trips Checksum through VerifyChecksum, a C1-first Checksum goes red; negative TestRFC905FaultySenderChecksumRefused/c1-before-c0 refuses a pair built with the steps swapped. The verification-side sequence is B.4.2-1's.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC905FaultySenderChecksumRefused`	unit/verify	revert, verified
positive	`TestISISChecksumVectors`	unit/verify	revert, verified

`RFC905-x-3`

Calculate X and Y such that X = -C1 + (L-n).CO Y = C1 - (L-n+1).C0 (§B.3)

Audit verdict: enforced (the tests do what the requirement demands), fresh. Re-judged 2026-09-30 under R-C1: row text and tagged units (IS-IS and OSPF) unchanged. Positive: TestISISChecksumMatchesClosedForm and TestFletcherGenerateMatchesClosedForm compare the producer at every field offset against an independent B.3.4 derivation in L-n notation; fixed vectors pin values. Negative: TestISISChecksumRefusesMisplacedXY and TestFletcherGenerateRefusesMisplacedXY refuse the pair swapped or shifted one octet early. The B.3.5 placement obligation is now its own row, RFC905-B.3.5-1.

Polarity	Test	Kind and tier	Proof state
negative	`TestISISChecksumRefusesMisplacedXY`	unit/verify	revert, verified
negative	`TestFletcherGenerateRefusesMisplacedXY`	unit/verify	revert, verified
positive	`TestISISChecksumMatchesClosedForm`	unit/verify	revert, verified
positive	`TestISISChecksumFixedVector`	unit/verify	unproven
positive	`TestISISChecksumVectors`	unit/verify	unproven
positive	`TestOSPFLSAChecksum`	unit/verify	unproven
positive	`TestFletcherRFC905Vectors`	unit/verify	unproven
positive	`TestFletcherGenerateMatchesClosedForm`	unit/verify	revert, verified

`RFC905-x-4`

If, when all the octets have been processed, either or both of C0 and C1 does not have the value zero, the checksum formulas in 6.17 have not been satisfied. (§B.4)

Audit verdict: enforced (the tests do what the requirement demands), fresh. Re-judged 2026-09-30 under R-C1: row text and tagged units unchanged. TestISISVerifyRequiresBothSumsZero and TestFletcherVerifyRequiresBothSumsZero refuse a region with C0 zero and C1 non-zero and one with C1 zero and C0 non-zero, and accept the generated region; the both-non-zero case stays covered by the single-octet flips of TestISISChecksumDetectsCorruption and TestOSPFLSAChecksumExcludesAge.

Polarity	Test	Kind and tier	Proof state
negative	`TestISISVerifyRequiresBothSumsZero`	unit/verify	mutant, verified
negative	`TestISISChecksumDetectsCorruption`	unit/verify	revert, verified
negative	`TestOSPFLSAChecksumExcludesAge`	unit/verify	unproven
negative	`TestFletcherVerifyRequiresBothSumsZero`	unit/verify	mutant, verified
positive	`TestISISVerifyRequiresBothSumsZero`	unit/verify	revert, verified
positive	`TestISISChecksumVectors`	unit/verify	unproven
positive	`TestFletcherVerifyRequiresBothSumsZero`	unit/verify	revert, verified

`RFC905-B.3.1-1`

Set up the complete TPDU with the value of the checksum parameter field set to zero. (§B.3.1)

Audit verdict: enforced (the tests do what the requirement demands), fresh. Judged 2026-09-30. Positive TestRFC905GeneratorZeroesTheFieldFirst: Checksum over a region whose field holds stale 0x5A,0xC3 returns the same X,Y as over the zeroed region, equal to the independent closed form, and the pair verifies. Negative TestRFC905SenderThatKeptTheFieldRefused: a sender that summed the stale field octets produces a pair (guarded to differ from Checksum's) that VerifyChecksum refuses, while the compliant pair is accepted (receive-side refusal, R1(a)). Records on checksum.go::Checksum and VerifyChecksum, observed red.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC905SenderThatKeptTheFieldRefused`	unit/verify	revert, verified
positive	`TestRFC905GeneratorZeroesTheFieldFirst`	unit/verify	revert, verified

`RFC905-B.3.2-1`

Initialize C0 and C1 to zero. (§B.3.2)

Audit verdict: enforced (the tests do what the requirement demands), fresh. Judged 2026-09-30. Positive TestRFC905GeneratorStartsFromZeroSums: an all-zero 24-octet region yields 0xFF,0xFF at every field offset (sums that start at zero stay zero), and a non-zero region equals the derivation that starts C0 and C1 at zero. Negative TestRFC905SenderWithSeededSumsRefused: pairs from C0 or C1 seeded with 1 (guarded to differ) are refused by VerifyChecksum, the compliant pair accepted. Records observed red.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC905SenderWithSeededSumsRefused`	unit/verify	revert, verified
positive	`TestRFC905GeneratorStartsFromZeroSums`	unit/verify	revert, verified

`RFC905-B.3.5-1`

Place the values X and Y in octets n and (n + 1) respectively. (§B.3.5)

Audit verdict: enforced (the tests do what the requirement demands), fresh. Judged 2026-09-30. Positive TestRFC905LSPPlacesXAtNAndYAtNPlus1: LSP.WriteTo stores the independently derived X at octet n and Y at n+1 (X != Y guarded, so a swap cannot pass) and the decoded LSP verifies. Negative TestRFC905LSPWithSwappedXYRefused: the same LSP with the two octets swapped is refused by LSP.VerifyChecksum, the check the flooding path runs, while the unswapped one is accepted. Records on lsp.go::WriteTo and VerifyChecksum, observed red.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC905LSPWithSwappedXYRefused`	unit/verify	revert, verified
positive	`TestRFC905LSPPlacesXAtNAndYAtNPlus1`	unit/verify	revert, verified

`RFC905-B.4.2-1`

Process each octet of the TPDU sequentially from i = 1 to L by: a) adding the value of the octet to C0; then b) adding the value of C0 to C1. (§B.4.2)

Audit verdict: enforced (the tests do what the requirement demands), fresh. Judged 2026-09-30. Positive TestRFC905VerifierAcceptsEveryPlacement: VerifyChecksum accepts correct X,Y at every field offset 0..L-2 of 4, 9, 24 and 41-octet regions, so a verifier with the a)/b) steps out of order or a wrong range refuses some case. Negative TestRFC905VerifierReadsTheFirstAndLastOctet: a region whose first or last octet changed 0->1 is refused, with a guard proving that sums skipping that octet would end at zero, so a receiver not running i = 1 to L accepts it. Records on VerifyChecksum, observed red.

Polarity	Test	Kind and tier	Proof state
negative	`TestRFC905VerifierReadsTheFirstAndLastOctet`	unit/verify	revert, verified
positive	`TestRFC905VerifierAcceptsEveryPlacement`	unit/verify	revert, verified

`RFC905-13.2.3.1-1`

Parameter Code: 1100 0011 Parameter Length: 2 Parameter Value: Result of checksum algorithm. This algorithm is specified in 6.17. (§13.2.3.1)

Audit verdict: not audited: no reader has judged these tests

No test carries RFC905-13.2.3.1-1, so no unit is bound to it.

Extraction sign-off

Field	Value
Reviewer	claude
Signed off	2026-09-26
Register	prose
Source	rfc/full/rfc905.txt
Source fingerprint	d47560796f50e3dd
Record	rfc/extraction/rfc905.json
Mapped sentences	3
Declined as scope	254
Relocated to a spec, which Ze OWES	0
Unclassified	0

Sections

Section	Name	Sites	Disposition	Reason
`front`	not stated	4	walked	not stated
`1`	not stated	0	walked	not stated
`1.1`	not stated	0	walked	not stated
`1.2`	not stated	0	walked	not stated
`1.3`	not stated	0	walked	not stated
`1.4`	not stated	0	walked	not stated
`2`	not stated	0	walked	not stated
`3`	not stated	0	walked	not stated
`3.1`	not stated	0	walked	not stated
`3.2`	not stated	0	walked	not stated
`3.2.1`	not stated	0	walked	not stated
`3.2.2`	not stated	0	walked	not stated
`3.2.3`	not stated	0	walked	not stated
`3.2.4`	not stated	0	walked	not stated
`3.2.5`	not stated	0	walked	not stated
`3.2.6`	not stated	0	walked	not stated
`3.2.7`	not stated	0	walked	not stated
`3.2.8`	not stated	0	walked	not stated
`3.2.9`	not stated	0	walked	not stated
`3.2.10`	not stated	0	walked	not stated
`3.2.11`	not stated	0	walked	not stated
`3.2.12`	not stated	0	walked	not stated
`3.2.13`	not stated	0	walked	not stated
`3.2.14`	not stated	0	walked	not stated
`3.2.15`	not stated	0	walked	not stated
`3.2.16`	not stated	0	walked	not stated
`3.2.17`	not stated	0	walked	not stated
`3.2.18`	not stated	0	walked	not stated
`3.2.19`	not stated	0	walked	not stated
`3.2.20`	not stated	0	walked	not stated
`3.2.21`	not stated	0	walked	not stated
`3.2.22`	not stated	0	walked	not stated
`3.2.23`	not stated	0	walked	not stated
`3.2.24`	not stated	0	walked	not stated
`3.2.25`	not stated	0	walked	not stated
`3.2.26`	not stated	0	walked	not stated
`3.2.27`	not stated	0	walked	not stated
`3.2.28`	not stated	0	walked	not stated
`3.2.29`	not stated	0	walked	not stated
`4`	not stated	0	walked	not stated
`4.1`	not stated	0	walked	not stated
`4.2`	not stated	0	walked	not stated
`4.3`	not stated	0	walked	not stated
`4.4`	not stated	0	walked	not stated
`4.5`	not stated	0	walked	not stated
`5`	not stated	0	walked	not stated
`5.1`	not stated	0	walked	not stated
`5.2`	not stated	0	walked	not stated
`5.3`	not stated	0	walked	not stated
`5.3.1`	not stated	0	walked	not stated
`5.3.1.1`	not stated	0	walked	not stated
`5.3.1.2`	not stated	1	walked	not stated
`5.3.1.3`	not stated	0	walked	not stated
`5.3.1.4`	not stated	0	walked	not stated
`5.4`	not stated	0	walked	not stated
`5.4.1`	not stated	0	walked	not stated
`5.4.2`	not stated	1	walked	not stated
`5.4.3`	not stated	0	walked	not stated
`5.4.4`	not stated	0	walked	not stated
`5.4.5`	not stated	0	walked	not stated
`5.4.6`	not stated	0	walked	not stated
`5.4.6.1`	not stated	0	walked	not stated
`5.4.6.2`	not stated	0	walked	not stated
`5.4.6.3`	not stated	1	walked	not stated
`5.4.7`	not stated	0	walked	not stated
`5.4.8`	not stated	0	walked	not stated
`5.5`	not stated	0	walked	not stated
`6`	not stated	1	walked	not stated
`6.1`	not stated	0	walked	not stated
`6.1.1`	not stated	0	walked	not stated
`6.1.2`	not stated	0	walked	not stated
`6.1.3`	not stated	2	walked	not stated
`6.2`	not stated	0	walked	not stated
`6.2.1`	not stated	0	walked	not stated
`6.2.2`	not stated	0	walked	not stated
`6.2.3`	not stated	3	walked	not stated
`6.3`	not stated	0	walked	not stated
`6.3.1`	not stated	0	walked	not stated
`6.3.2`	not stated	0	walked	not stated
`6.3.3`	not stated	4	walked	not stated
`6.4`	not stated	0	walked	not stated
`6.4.1`	not stated	0	walked	not stated
`6.4.2`	not stated	1	walked	not stated
`6.5`	not stated	0	walked	not stated
`6.5.1`	not stated	0	walked	not stated
`6.5.2`	not stated	0	walked	not stated
`6.5.3`	not stated	0	walked	not stated
`6.5.4`	not stated	11	walked	not stated
`6.6`	not stated	0	walked	not stated
`6.6.1`	not stated	0	walked	not stated
`6.6.2`	not stated	0	walked	not stated
`6.6.3`	not stated	6	walked	not stated
`6.7`	not stated	0	walked	not stated
`6.7.1`	not stated	0	walked	not stated
`6.7.2`	not stated	0	walked	not stated
`6.7.3`	not stated	0	walked	not stated
`6.7.4`	not stated	0	walked	not stated
`6.7.5`	not stated	6	walked	not stated
`6.8`	not stated	0	walked	not stated
`6.8.1`	not stated	0	walked	not stated
`6.8.2`	not stated	0	walked	not stated
`6.8.3`	not stated	1	walked	not stated
`6.9`	not stated	0	walked	not stated
`6.9.1`	not stated	0	walked	not stated
`6.9.2`	not stated	0	walked	not stated
`6.9.3`	not stated	0	walked	not stated
`6.9.4`	not stated	0	walked	not stated
`6.9.4.1`	not stated	2	walked	not stated
`6.9.4.2`	not stated	1	walked	not stated
`6.10`	not stated	0	walked	not stated
`6.10.1`	not stated	0	walked	not stated
`6.10.2`	not stated	0	walked	not stated
`6.10.3`	not stated	4	walked	not stated
`6.11`	not stated	0	walked	not stated
`6.11.1`	not stated	0	walked	not stated
`6.11.2`	not stated	0	walked	not stated
`6.11.3`	not stated	0	walked	not stated
`6.11.4`	not stated	3	walked	not stated
`6.12`	not stated	0	walked	not stated
`6.12.1`	not stated	0	walked	not stated
`6.12.2`	not stated	0	walked	not stated
`6.12.3`	not stated	3	walked	not stated
`6.12.4`	not stated	4	walked	not stated
`6.13`	not stated	0	walked	not stated
`6.13.1`	not stated	0	walked	not stated
`6.13.2`	not stated	0	walked	not stated
`6.13.3`	not stated	0	walked	not stated
`6.13.4`	not stated	2	walked	not stated
`6.14`	not stated	0	walked	not stated
`6.14.1`	not stated	0	walked	not stated
`6.14.2`	not stated	0	walked	not stated
`6.14.3`	not stated	0	walked	not stated
`6.14.4`	not stated	1	walked	not stated
`6.14.4.1`	not stated	5	walked	not stated
`6.14.4.2`	not stated	8	walked	not stated
`6.14.4.3`	not stated	5	walked	not stated
`6.15`	not stated	0	walked	not stated
`6.15.1`	not stated	0	walked	not stated
`6.15.2`	not stated	0	walked	not stated
`6.15.3`	not stated	1	walked	not stated
`6.16`	not stated	0	walked	not stated
`6.16.1`	not stated	0	walked	not stated
`6.16.2`	not stated	0	walked	not stated
`6.16.3`	not stated	0	walked	not stated
`6.17`	not stated	0	walked	not stated
`6.17.1`	not stated	0	walked	not stated
`6.17.2`	not stated	0	walked	not stated
`6.17.3`	not stated	2	walked	not stated
`6.18`	not stated	0	walked	not stated
`6.18.1`	not stated	0	walked	not stated
`6.18.2`	not stated	2	walked	not stated
`6.18.2.1`	not stated	0	walked	not stated
`6.18.2.2`	not stated	1	walked	not stated
`6.18.2.3`	not stated	0	walked	not stated
`6.19`	not stated	0	walked	not stated
`6.19.1`	not stated	0	walked	not stated
`6.19.2`	not stated	0	walked	not stated
`6.19.3`	not stated	0	walked	not stated
`6.20`	not stated	0	walked	not stated
`6.20.1`	not stated	0	walked	not stated
`6.20.2`	not stated	0	walked	not stated
`6.20.3`	not stated	0	walked	not stated
`6.21`	not stated	0	walked	not stated
`6.21.1`	not stated	0	walked	not stated
`6.21.2`	not stated	0	walked	not stated
`6.22`	not stated	0	walked	not stated
`6.22.1`	not stated	0	walked	not stated
`6.22.2`	not stated	0	walked	not stated
`6.22.3`	not stated	3	walked	not stated
`6.23`	not stated	0	walked	not stated
`6.23.1`	not stated	0	walked	not stated
`6.23.2`	not stated	0	walked	not stated
`7`	not stated	0	walked	not stated
`8`	not stated	0	walked	not stated
`8.1`	not stated	0	walked	not stated
`8.2`	not stated	0	walked	not stated
`8.2.1`	not stated	1	walked	not stated
`8.2.2`	not stated	3	walked	not stated
`8.2.3`	not stated	1	walked	not stated
`8.2.4`	not stated	1	walked	not stated
`9`	not stated	0	walked	not stated
`9.1`	not stated	0	walked	not stated
`9.2`	not stated	0	walked	not stated
`9.2.1`	not stated	2	walked	not stated
`9.2.2`	not stated	1	walked	not stated
`9.2.3`	not stated	0	walked	not stated
`9.2.3.1`	not stated	2	walked	not stated
`9.2.3.2`	not stated	3	walked	not stated
`9.2.4`	not stated	1	walked	not stated
`10`	not stated	0	walked	not stated
`10.1`	not stated	0	walked	not stated
`10.2`	not stated	0	walked	not stated
`10.2.1`	not stated	1	walked	not stated
`10.2.2`	not stated	1	walked	not stated
`10.2.3`	not stated	1	walked	not stated
`10.2.4`	not stated	0	walked	not stated
`10.2.4.1`	not stated	4	walked	not stated
`10.2.4.2`	not stated	9	walked	not stated
`10.2.4.3`	not stated	1	walked	not stated
`10.2.5`	not stated	1	walked	not stated
`11`	not stated	0	walked	not stated
`11.1`	not stated	0	walked	not stated
`11.2`	not stated	0	walked	not stated
`11.2.1`	not stated	1	walked	not stated
`11.2.2`	not stated	1	walked	not stated
`11.2.3`	not stated	0	walked	not stated
`11.2.3.1`	not stated	4	walked	not stated
`11.2.3.2`	not stated	4	walked	not stated
`11.2.3.3`	not stated	3	walked	not stated
`11.2.3.4`	not stated	4	walked	not stated
`11.2.4`	not stated	1	walked	not stated
`12`	not stated	0	walked	not stated
`12.1`	not stated	1	walked	not stated
`12.2`	not stated	0	walked	not stated
`12.2.1`	not stated	0	walked	not stated
`12.2.1.1`	not stated	2	walked	not stated
`12.2.1.1.1`	not stated	0	walked	not stated
`12.2.1.1.2`	not stated	0	walked	not stated
`12.2.1.1.3`	not stated	0	walked	not stated
`12.2.1.1.4`	not stated	0	walked	not stated
`12.2.1.1.5`	not stated	0	walked	not stated
`12.2.1.1.6`	not stated	1	walked	not stated
`12.2.1.2`	not stated	1	walked	not stated
`12.2.2`	not stated	0	walked	not stated
`12.2.2.1`	not stated	0	walked	not stated
`12.2.2.2`	not stated	6	walked	not stated
`12.2.3`	not stated	0	walked	not stated
`12.2.3.1`	not stated	1	walked	not stated
`12.2.3.2`	not stated	3	walked	not stated
`12.2.3.3`	not stated	2	walked	not stated
`12.2.3.4`	not stated	9	walked	not stated
`12.2.3.5`	not stated	6	walked	not stated
`12.2.3.6`	not stated	5	walked	not stated
`12.2.3.7`	not stated	4	walked	not stated
`12.2.3.8`	not stated	0	walked	not stated
`12.2.3.8.1`	not stated	2	walked	not stated
`12.2.3.8.2`	not stated	3	walked	not stated
`12.2.3.8.3`	not stated	3	walked	not stated
`12.2.3.8.4`	not stated	4	walked	not stated
`12.2.3.9`	not stated	1	walked	not stated
`12.2.4`	not stated	0	walked	not stated
`12.2.4.1`	not stated	0	walked	not stated
`12.2.4.2`	not stated	1	walked	not stated
`13`	not stated	0	walked	not stated
`13.1`	not stated	0	walked	not stated
`13.2`	not stated	2	walked	not stated
`13.2.1`	not stated	1	walked	not stated
`13.2.2`	not stated	0	walked	not stated
`13.2.2.1`	not stated	0	walked	not stated
`13.2.2.2`	not stated	0	walked	not stated
`13.2.3`	not stated	7	walked	not stated
`13.2.3.1`	not stated	1	walked	not stated
`13.2.4`	not stated	0	walked	not stated
`13.3`	not stated	1	walked	not stated
`13.3.1`	not stated	1	walked	not stated
`13.3.2`	not stated	0	walked	not stated
`13.3.3`	not stated	3	walked	not stated
`13.3.4`	not stated	1	walked	not stated
`13.3.5`	not stated	0	walked	not stated
`13.4`	not stated	0	walked	not stated
`13.4.1`	not stated	1	walked	not stated
`13.4.2`	not stated	0	walked	not stated
`13.4.3`	not stated	1	walked	not stated
`13.4.4`	not stated	1	walked	not stated
`13.4.5`	not stated	0	walked	not stated
`13.5`	not stated	0	walked	not stated
`13.5.1`	not stated	1	walked	not stated
`13.5.2`	not stated	0	walked	not stated
`13.5.3`	not stated	2	walked	not stated
`13.5.4`	not stated	0	walked	not stated
`13.5.5`	not stated	2	walked	not stated
`13.6`	not stated	1	walked	not stated
`13.6.1`	not stated	1	walked	not stated
`13.6.2`	not stated	0	walked	not stated
`13.6.3`	not stated	1	walked	not stated
`13.6.4`	not stated	1	walked	not stated
`13.7`	not stated	0	walked	not stated
`13.7.1`	not stated	1	walked	not stated
`13.7.2`	not stated	0	walked	not stated
`13.7.3`	not stated	1	walked	not stated
`13.7.4`	not stated	1	walked	not stated
`13.7.5`	not stated	0	walked	not stated
`13.8`	not stated	1	walked	not stated
`13.8.1`	not stated	1	walked	not stated
`13.8.2`	not stated	0	walked	not stated
`13.8.3`	not stated	2	walked	not stated
`13.8.4`	not stated	1	walked	not stated
`13.8.5`	not stated	0	walked	not stated
`13.9`	not stated	1	walked	not stated
`13.9.1`	not stated	1	walked	not stated
`13.9.2`	not stated	0	walked	not stated
`13.9.3`	not stated	3	walked	not stated
`13.9.4`	not stated	0	walked	not stated
`13.10`	not stated	1	walked	not stated
`13.10.1`	not stated	1	walked	not stated
`13.10.2`	not stated	0	walked	not stated
`13.10.3`	not stated	3	walked	not stated
`13.10.4`	not stated	0	walked	not stated
`13.11`	not stated	1	walked	not stated
`13.11.1`	not stated	1	walked	not stated
`13.11.2`	not stated	0	walked	not stated
`13.11.3`	not stated	3	walked	not stated
`13.11.4`	not stated	0	walked	not stated
`13.12`	not stated	0	walked	not stated
`13.12.1`	not stated	0	walked	not stated
`13.12.2`	not stated	0	walked	not stated
`13.12.3`	not stated	1	walked	not stated
`13.12.4`	not stated	1	walked	not stated
`14`	not stated	0	walked	not stated
`14.1`	not stated	1	walked	not stated
`14.2`	not stated	1	walked	not stated
`14.3`	not stated	1	walked	not stated
`14.4`	not stated	1	walked	not stated
`14.5`	not stated	1	walked	not stated
`14.6`	not stated	2	walked	not stated
`A`	not stated	0	walked	not stated
`B`	not stated	0	walked	not stated
`B.1`	not stated	0	walked	not stated
`B.2`	not stated	1	walked	not stated
`B.3`	not stated	0	walked	not stated
`B.3.1`	not stated	0	walked	not stated
`B.3.2`	not stated	0	walked	not stated
`B.3.3`	not stated	0	walked	not stated
`B.3.4`	not stated	0	walked	not stated
`B.3.5`	not stated	0	walked	not stated
`B.4`	not stated	0	walked	not stated
`B.4.1`	not stated	0	walked	not stated
`B.4.2`	not stated	0	walked	not stated
`B.4.3`	not stated	0	walked	not stated

Excluded sentences

Site	Excluded kind	Reason	Quote
`front:1`	`not-a-requirement` never bound Ze the sentence states a fact or describes another document, and directs no implementation	a table-of-contents line; the words "Claims of Conformance Shall State" are the title of clause 14.6 reproduced in the contents list, not an obligation	14.2 ................................................. 145 14.3 ................................................. 145 14.4 ................................................. 145 14.5 ................................................. 146 14.6 Claims of Conformance Shall State................ 146
`front:2`	`not-a-requirement` never bound Ze the sentence states a fact or describes another document, and directs no implementation	a descriptive sentence about what the OSI series of standards covers; "required" qualifies the services the series describes, not an act any implementation must perform	The set of standards covers the services and protocols required to achieve such interconnection.
`front:3`	`not-a-requirement` never bound Ze the sentence states a fact or describes another document, and directs no implementation	a descriptive sentence about how the protocol classes relate to quality of service; it states a property of the class set, not an obligation	The classes are selectable with respect to the Transport and Network Services in providing the required quality of service for the interconnection of two session entities (note that each class provides a different set of functions for enhancement of service qualities).
`front:4`	`not-a-requirement` never bound Ze the sentence states a fact or describes another document, and directs no implementation	advice to the reader of the standard about how to cite it; it obliges no behavior of any transport entity	It is important, therefore, to qualify all references to this International Standard with statements of the options provided or required or with statements of the intended purpose of provision or use.
`5.3.1.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The following functions of the transport layer during this phase must match the TS-users' requested quality of service with the services offered by the network layer:
`5.4.2:1`	`not-a-requirement` never bound Ze the sentence states a fact or describes another document, and directs no implementation	a list item naming one input to the class-selection decision, the user required service versus cost ratio; the keyword qualifies the ratio, not an act	c) the user required service versus cost ratio acceptable to the TS-user.
`5.4.6.3:1`	`not-a-requirement` never bound Ze the sentence states a fact or describes another document, and directs no implementation	a descriptive sentence about when an option would typically be used; the keyword describes multiplexing that is absent, not an obligation	The option would typically be used for unsophisticated terminals, and when no multiplexing onto network connections is required.
`6:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Transport entities shall accept and respond to any TPDU received in a valid NSDU and may issue TPDUs initiating specific elements of procedure specified in this clause.
`6.1.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Each transport connection shall be assigned to a network connection.
`6.1.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The initiator shall not assign or reassign the transport connection to an existing network connection if the protocol class(es) proposed or the class in use for the transport connection are incompatible with the current usage of the network connection with respect to multiplexing (see Note 2).
`6.2.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	When the network expedited variant has been selected for class 1, the transport entities shall transmit and receive ED and EA TPDUs as NS-user data parameters of N-EXPEDITED DATA primitives.
`6.2.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	In all other cases, transport entities shall transmit and receive TPDUs as NS-user data parameters of N-DATA primitives.
`6.2.3:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	When a TPDU is put into an NS-user data parameter, the significance of the bits within an octet and the order of octets within a TPDU shall be as defined in 13.2.
`6.3.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A transport entity shall map a TSDU on to an ordered sequence of one or more DT TPDUs.
`6.3.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	This sequence shall not be interrupted by other DT TPDUs on the same transport connection.
`6.3.3:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	All DT TPDUs except the last DT TPDU in a sequence greater than one shall have a length of data greater than zero.
`6.3.3:4`	`not-a-requirement` never bound Ze the sentence states a fact or describes another document, and directs no implementation	the sentence explicitly DENIES a requirement: "There is no requirement that the DT TPDUs shall be of the maximum length selected during connection establishment."	There is no requirement that the DT TPDUs shall be of the maximum length selected during connection establishment.
`6.4.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	b) no more than one TPDU from the following list: CR, DR, CC, DT, ED TPDUs; if this TPDU is present, it shall be placed last in the set of concatenated TPDUs.
`6.5.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	During this exchange, all information and parameters needed for the transport entities to operate shall be exchanged or negotiated.
`6.5.4:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	After receiving the CC TPDU for a class which includes the procedure for retention until acknowledgement of TPDUs the initiator shall acknowledge the CC TPDU as defined in table 5 (see 6.13).
`6.5.4:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	When the network expedited variant of the expedited data transfer (see 6.11) has been agreed (possible in class 1 only), the responder shall not send an ED TPDU before the CC TPDU is acknowledged.
`6.5.4:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	1) it shall not already be in use or frozen (see 6.18),
`6.5.4:5`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	2) it shall not be zero.
`6.5.4:6`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The initiator shall propose a preferred class and may propose any number of alternative class which permit a valid response as defined in table 3.
`6.5.4:7`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The initiator should assume when it sends the CR TPDU that its preferred class will be agreed to, and commence the procedures associated with that class, except that if class 0 or class 1 is an alternative class, multiplexing shall not commence until a CC TPDU selecting the use of classes 2, 3 or 4 has been received.
`6.5.4:8`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The responder shall select one class defined in table 3 as a valid response corresponding to the preferred class and to the class(es), if any, contained in the alternative class parameter of the CR TPDU.
`6.5.4:9`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	It shall indicate the selected class in the CC TPDU and shall follow the procedures for the selected class.
`6.5.4:10`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If the preferred class is not selected, then on receipt of the CC TPDU the initiator shall adjust its operation according the procedures of the selected class.
`6.5.4:11`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	In class 2, whenever a transport entity requests or agrees to the transport expedited data transfer service or to the use of extended formats, it shall also request or agree (respectively) to the use of explicit flow control.
`6.6.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If a transport connection cannot be accepted, the responder shall respond to the CR TPDU with a DR TPDU.
`6.6.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The reason shall indicate why the connection was not accepted.
`6.6.3:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The source reference field in the DR TPDU shall be set to zero to indicate an unassigned reference.
`6.6.3:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If a DR TPDU is received the initiator shall regard the connection as released.
`6.6.3:5`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The responder shall respond to an invalid CR TPDU by sending an ER or DR TPDU.
`6.6.3:6`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If an ER TPDU is received in response to a CR TPDU, the initiator shall regard the connection as released.
`6.7.5:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	a) if it has previously sent or received a CC TPDU (see note 1), shall send a DR TPDU.
`6.7.5:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	It shall ignore all subsequently received TPDUs other than a DR or DC TPDU.
`6.7.5:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	On receipt of a DR or DC TPDU it shall consider the transport connection released;
`6.7.5:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	b) in other cases it shall:
`6.7.5:5`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	1) For classes other than class 4 wait for the acknowledgement of the outstanding CR TPDU; if it receives a CC TPDU, it shall follow the procedures in 6.7.5.a.
`6.7.5:6`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A transport entity that receives a DR TPDU shall
`6.8.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	When, on the network connection to which a transport connection is assigned, an N-DISCONNECT or N-RESET indication is received, both transport entities shall consider that the transport connection is released and so inform the TS-users.
`6.9.4.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If the received NSDU or Expedited NSDU cannot be decoded (i.e. does not contain one or more correct TPDUs) or is corrupted (i.e. contains a TPDU with a wrong checksum) then the transport entity shall:
`6.9.4.1:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If the NSDU can be decoded and is not corrupted, the transport entity shall:
`6.9.4.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	a) if the DST-REF is not allocated to a transport connection, the transport entity shall respond on the same network connection with a DR TPDU if the TPDU is a CC TPDU, with a DC TPDU if the TPDU is a DR TPDU and shall ignore the TPDU if neither a DR TPDU nor CC TPDU.
`6.10.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A Transport entity shall allocate the sequence number zero to the TPDU-NR of the first DT TPDU which it transmits for a transport connection.
`6.10.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	For subsequent DT TPDUs sent on the same transport connection, the transport entity shall allocate a sequence number one greater than the previous one.
`6.10.3:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	When a DT TPDU is retransmitted, the TPDU-NR parameter shall have the same value as in the first transmission of that DT TPDU.
`6.10.3:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Modulo 27 arithmetic shall be used when normal formats have been selected and modulo 231 arithmetic shall be used when extended formats have been selected.
`6.11.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The TS-user data parameter of each T-EXPEDITED DATA request shall be conveyed as the data field of an Expedited Data (ED) TPDU.
`6.11.4:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Each ED TPDU received shall be acknowledged by an Expedited Acknowledge (EA) TPDU.
`6.11.4:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	No more than one ED TPDU shall remain unacknowledged at any time for each direction of a transport connection.
`6.12.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	When an N-DISCONNECT indication is received from the network connection to which a transport connection is assigned, the initiator shall apply one of the following alternatives:
`6.12.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The responder shall start its TWR timer if not already started.
`6.12.3:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The TWR timer is stopped and the responder shall continue with resynchronization (see 6.14).
`6.12.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Its value shall not exceed two minutes minus the sum of the maximum disconnect propagation delay and the transit delay of the network connections (see note 1).
`6.12.4:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If the reassignment time parameter is present in the CR TPDU, the TWR timer value shall be greater than the sum of the TTR timer plus the maximum disconnect propagation delay plus the transit delay of the network connections.
`6.12.4:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If the reassignment time parameter is not present in the CR TPDU, a default value of 2 minutes shall be used for the TWR timer.
`6.12.4:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Provided that the required quality of service is met, TTR may be set to zero (i.e. no assignment).
`6.13.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Copies of the following TPDUs shall be retained upon transmission to permit their later retransmission:
`6.13.4:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	In the confirmation of receipt variant, applicable only in Class 1, transport entities receiving N-DATA indications which convey DT TPDUs and have the confirmation request field set shall issue an N-DATA ACKNOWLEDGE request (see notes 1 and 2).
`6.14.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A transport entity which is notified of the occurence of an N- RESET or which is performing 'reassignment after failure' according to 6.12 shall carry out the active resynchronization procedure (see 6.14.4.1) unless any of the following hold:
`6.14.4.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The Transport entity shall carry out one of the following actions:
`6.14.4.1:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	b) otherwise, the TTR timer shall be started (unless it is already running) and the first applicable of the following actions shall be taken:
`6.14.4.1:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	1) if a CR TPDU is unacknowledged, then the transport entity shall retransmit it;
`6.14.4.1:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	2) if a DR TPDU is unacknowledged, then the transport entity shall retransmit it;
`6.14.4.1:5`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	3) otherwise, the transport entity shall carry out the data resynchronization procedures (6.14.4.3).
`6.14.4.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entity shall not send any TPDUs until a TPDU has been received.
`6.14.4.2:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entity shall start its TWR timer if it was not already started (due to a previous N-DISCONNECT or N- RESET indication).
`6.14.4.2:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	When a valid TPDU is received the transport entity shall stop its TWR timer and carry out the appropriate one of the following actions, depending on the TPDU:
`6.14.4.2:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	a) if it is a DR TPDU, then the transport entity shall send a DC TPDU;
`6.14.4.2:5`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	b) if it is a repeated CR TPDU (see note 1) then the transport entity shall carry out the appropriate action from the following:
`6.14.4.2:6`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	c) if it is an RJ or ED TPDU then one of the following actions shall be taken:
`6.14.4.2:7`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	1) if a DR TPDU is unacknowledged, then the transport entity shall retransmit it;
`6.14.4.2:8`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	2) otherwise, the transport entity shall carry out the data resynchronization procedures (6.14.4.3).
`6.14.4.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entity shall carry out the following actions in the following order:
`6.14.4.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	c) wait for the next TPDU from the other transport entity, unless an RJ or DR TPDU has already been received; if a DR TPDU is received the transport entity shall send a DC, freeze the reference, inform the TS-user of the disconnection and take no further action (i.e. it shall not follow the procedures in 6.14.4.3.d).
`6.14.4.3:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If an RJ TPDU is received, the procedure of 6.14.4.3.d shall be followed.
`6.14.4.3:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If an ED TPDU is received the procedures as described in 6.11 shall be followed.
`6.14.4.3:5`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If it is a duplicated ED-TPDU the transport entity shall acknowledge it, with an EA TPDU, discard the duplicated ED TPDU and wait again for the next TPDU.
`6.15.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall be able to send and receive on the same network connection TPDUs belonging to different transport connections.
`6.18.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	When a transport entity determines that a particular connection is released it shall place the reference which it has allocated to the connection in a frozen state according to the procedures of the class.
`6.18.2:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	While frozen, the reference shall not be re-used.
`6.18.2.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The period of time for which the reference remains frozen shall be greater than the TWR time.
`6.22.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A transport entity that receives a TPDU that can be associated to a transport connection and is invalid or constitutes a protocol error (see 3.2.16 and 3.2.17) shall take one of the following actions so as not to jeopardize any other transport connections not assigned to that network connection:
`6.22.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If an ER TPDU is sent in Class 0 it shall contain the octets of the invalid TPDU up to and including the octet where the error was detected (see notes 3, 4 and 5).
`6.22.3:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If the timer expires, the transport entity shall initiate the release procedures appropriate to the class.
`8.2.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use the following procedures:
`8.2.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use the following procedures:
`8.2.2:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	c) the CR and CC TPDUs shall contain no parameter field other than those for TSAP-ID and maximum TPDU size;
`8.2.2:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	d) the CR and CC TPDUs shall not contain a data field.
`8.2.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use the segmenting and reassembling procedure (see 6.3).
`8.2.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use the implicit variant of the normal release procedure (see 6.7).
`9.2.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use the following procedures:
`9.2.1:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	g) retention until acknowledgement of TPDU (see 6.13); the variant used, AK or confirmation of receipt, shall be as selected during connection establishment (see notes);
`9.2.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use the following procedures:
`9.2.3.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The sending transport entity shall use the following procedures;
`9.2.3.1:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The receiving transport entity shall use the following procedures;
`9.2.3.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use either the network normal data or the network expedited variants of the expedited data transfer procedure (see 6.11) if their use has been selected during connection establishment (see note 1).
`9.2.3.2:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The sending transport entity shall not allocate the same ED- TPDU-NR to successive ED TPDUs (see notes 2 and 3).
`9.2.3.2:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	When acknowledging an ED TPDU by sending and EA TPDU the transport entity shall put into the YR-EDTU-NR parameter of the EA TPDU the value received in the ED-TPDU-NR parameter of the ED TPDU.
`9.2.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use the explicit variant of the release procedure (see 6.7).
`10.2.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use the following procedures
`10.2.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use the following procedures:
`10.2.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If this option has been selected as a result of the connection establishment, the transport entities shall use the segmenting procedure (see 6.3).
`10.2.4.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The sending transport entity shall use the following procedures:
`10.2.4.1:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The receiving transport entity shall use the following procedures:
`10.2.4.1:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	c) DT TPDU numbering (see 6.10); if a DT TPDU is received which is out of sequence it shall be treated as a protocol error; then
`10.2.4.1:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The variant of the DT TPDU numbering which is used by both transport entities shall be that which was agreed at connection establishment.
`10.2.4.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall send an initial credit (which may be zero) in the CDT field of the CR or CC TPDU.
`10.2.4.2:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entity that receives the CR or the CC TPDU shall consider its lower window edge as zero, and its upper window edge as the value of the CDT field in the received TPDU.
`10.2.4.2:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	a) the YR-TU-NR parameter shall be at most one greater than the TPDU-NR field of the last received DT TPDU or shall be zero if no DT TPDU has been received;
`10.2.4.2:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	b) if an AK TPDU has previously been sent the value of the YR-TU-NR parameter shall not be lower than that in the previously sent AK TPDU.
`10.2.4.2:5`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	c) the sum of the YR-TU-NR and CDT fields shall not be less than the upper window edge allocated to the remote entity (see note 1).
`10.2.4.2:6`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A transport entity which receives an AK TPDU shall consider the YR-TU-NR field as its new lower window edge, and the sum of YR- TU-NR and CDT as its new upper window edge.
`10.2.4.2:7`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If either of these have been reduced or if the lower window edge has become more than one greater than the TPDU-NR of the last transmitted DT TPDU, this shall be treated as a protocol error (see 6.22).
`10.2.4.2:8`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A transport entity shall not send a DT TPDU with a TPDU-NR outside of the transmit window (see notes 2 and 3).
`10.2.4.2:9`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	This means that a transport entity is required to stop sending if the TPDU-NR field of the next DT TPDU which would be sent would be the upper window edge.
`10.2.4.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall follow the network normal variant of the expedited data transfer procedure in 6.11 if its use has been agreed during connection establishment.
`10.2.5:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use the explicit variant of the release procedure in 6.7.
`11.2.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use the following procedures:
`11.2.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use the following procedures;
`11.2.3.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The sending transport entity shall use the following procedures:
`11.2.3.1:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The receiving transport entity shall use the following procedures:
`11.2.3.1:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	c) DT TPDU numbering (see 6.10); the TPDU-NR field of each received DT TPDU shall be treated as a protocol error if it exceeds the greatest such value received in a previous DT TPDU by more than one (see note); then
`11.2.3.1:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	d) reassembling (see 6.3); duplicated TPDUs shall be eliminated before reassembling is performed.
`11.2.3.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	When an RJ TPDU is sent, the following constraints shall be respected:
`11.2.3.2:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	a) the YR-TU-NR parameter shall be at most one greater than the greatest such value received in a previous DT TPDU, or shall be zero if no DT TPDU has yet been received (see note 2);
`11.2.3.2:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	b) if an AK or RJ TPDU has previously been sent the YR-TU-NR parameter shall not be lower than that in the previously sent AK or RJ TPDU or lower than zero if no AK or RJ TPDU.
`11.2.3.2:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	c) the next DT TPDU to be transmitted, or retransmitted, shall be that for which the value of the TPDU-NR parameter is equal to the value of the YR-TU-NR parameter of the RJ TPDU;
`11.2.3.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The procedures shall be as defined in 10.2.4.2, except that:
`11.2.3.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	This shall not be treated as a protocol error;
`11.2.3.3:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	b) receipt of an AK TPDU which sets the lower window edge more than one greater than the TPDU-NR of the last transmitted DT TPDU shall not be treated as a protocol error, provided that all acknowledged DT TPDUs have been previously transmitted (see notes 1 and 2).
`11.2.3.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall follow the network normal data variant of expedited data transfer procedure in 6.11 if its use has been agreed during connection establishment.
`11.2.3.4:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The sending transport entity shall not allocate the same ED- TPDU-NR to successive ED TPDUs.
`11.2.3.4:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The receiving transport entity shall transmit an EA TPDU with the same value in its YR-EDTU-NR parameter.
`11.2.3.4:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If, and only if, this number is different from that of the previously received ED TPDU shall it generate a T-EXPEDITED DATA indication to convey the data to the TS-user (see note 2).
`11.2.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use the explicit variant of the release procedure in 6.7.
`12.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The use of the checksum mechanism must be available but its use or its non-use is subject to negotiation.
`12.2.1.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The values should be chosen so that the required quality of service can be provided, given the known characteristics of the network.
`12.2.1.1:2`	`not-a-requirement` never bound Ze the sentence states a fact or describes another document, and directs no implementation	an ASCII table of timer names and their meanings reproduced as one block; the keywords sit inside the table's descriptive cells	+----------------------------------------------------------------+ \| T1 \|Local retrans- \| A bound for the maximum time that \| \| \|mission time \| the local transport entity will \| \| \| \| wait for acknowledgement before re-\| \| \| \| transmitting a TPDU. \| \| \| \| \| \| R \|Persistence time \| A bound for the maximum time the \| \| \| \| the local transport entity will \| \| \| \| continue to transmit a TPDU that \| \| \| \| requires acknowledgement. \| \| \| \| \| \| N \|Maximum number of \| A bound for the maximum number of \| \| \|transmissions \| times which the local transport \| \| \| \| entity will continue to transmit a \| \| \| \| TPDU that requires acknowledgement.\| \| \| \| \| \| L \|Bound on references \| A bound for the maximum time \| \| \|and sequence \| between the transmission of a TPDU \| \| \|numbers \| and the receipt of any acknow- \| \| \| \| ledgement relating to it. \| \| \| \| \| \| I \|Inactivity time \| A bound for the time after which \| \| \| \| a transport entity will, if it \| \| \| \| does not receive a TPDU, initiate \| \| \| \| the release procedure to terminate \| \| \| \| the transport connection. \| \| \| \| \| \| \| \| NOTE - This parameter is required \| \| \| \| for protection against unsignalled \| \| \| \| breaks in the network connection. \| \| \| \| \| \| W \|Window time \| A bound for the maximum time a \| \| \| \| transport entity will wait before \| \| \| \| retransmitting up to date window \| \| \| \| information. \| +----------------------------------------------------------------+
`12.2.1.1.6:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A smaller value may therefore be used where this still allows the required quality of service to be provided.
`12.2.1.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entity shall use the following procedures:
`12.2.2.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use the following procedures:
`12.2.2.2:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The sender of a CR TPDU shall respond to the corresponding CC TPDU by immediately sending a DT, ED, DR or AK TPDU;
`12.2.2.2:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If the receiving transport entity is in the data transfer phase, having completed the 3-way TPDU exchange procedure, or is waiting for the T-CONNECT response from the TS-user, the receiving transport entity shall ignore such a TPDU.
`12.2.2.2:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Otherwise a CC TPDU shall be transmitted;
`12.2.2.2:5`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The receiving transport entity shall only acknowledge the duplicate CC TPDU according to the procedure in 12.2.2.2.b.1.
`12.2.2.2:6`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The response to such a TPDU shall be a DR TPDU;
`12.2.3.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The interval must be greater than E.
`12.2.3.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall use the following procedures:
`12.2.3.2:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The sending transport entity shall use the following procedures in the following order:
`12.2.3.2:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The receiving transport entity shall use the following procedures in the following order:
`12.2.3.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If the interval of the inactivity timer I expires without receipt of some TPDU, the transport entity shall initiate the release procedures.
`12.2.3.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	To prevent expiration of the remote transport entity's inactivity timer when no data is being sent, the local transport entity must send AK TPDUs at suitable intervals in the absence of data, having regard to the probability of TPDU loss.
`12.2.3.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall follow the network normal data variant of the expedited data transfer procedures (see 6.11), if the use of transport expedited service option has been agreed during connection establishment.
`12.2.3.4:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The ED TPDU shall have a TPDU-NR which is allocated from a separate sequence space from that of the DT TPDUs.
`12.2.3.4:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A transport entity shall allocate the sequence number zero to the ED TPDU-NR of the first ED TPDU which it transmits for a
`12.2.3.4:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	For subsequent ED TPDU sent on the same transport connection, the transport entity shall allocate a sequence number one greater than the previous one.
`12.2.3.4:5`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Modulo 27 arithmetic shall be used when normal formats have been selected and modulo 231 arithmetic shall be used when extended formats have been selected.
`12.2.3.4:6`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The receiving transport entity shall transmit an EA TPDU with the same sequence number in its YR-ETDU-NR field.
`12.2.3.4:7`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If this number is one greater than in the previously in sequence received ED TPDU, the receiving transport entity shall transfer the data in the ED TPDU to the TS-user.
`12.2.3.4:8`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If a transport entity does not receive an EA TPDU in acknowledgement to an ED TPDU it shall follow the retransmission procedures (see note and 12.2.1.2).
`12.2.3.4:9`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The sender of an ED TPDU shall not send any new DT TPDU with higher TPDU-NR until it receives the EA TPDU.
`12.2.3.5:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The receiving transport entity shall deliver all DT TPDUs to the TS-user in the order specified by the sequence number field.
`12.2.3.5:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	DT TPDUs received out-of-sequence but within the transmit window shall not be delivered to the TS-user until all in-sequence TPDUs have been received.
`12.2.3.5:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	DT TPDU received out-of-sequence and outside the transmit window shall be discarded.
`12.2.3.5:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Sequence numbers shall not be reused for the period L after their previous use.
`12.2.3.5:5`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Duplicated DT TPDUs shall be acknowledged, since the duplicated TPDU may be the result of a retransmission resulting from the loss of an AK TPDU.
`12.2.3.5:6`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The data contained in a duplicated DT TPDU shall be ignored.
`12.2.3.6:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entities shall send an initial credit (which may take the value 0) in the CDT field of the CR TPDU or CC TPDU.
`12.2.3.6:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entity which receives the CR TPDU or CC TPDU shall consider its lower window edge as zero and its upper window edge as the value in the CDT field in the received TPDU.
`12.2.3.6:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The sequence number of an AK TPDU shall not exceed the sequence number of the next expected DT TPDU, i.e. it shall not be greater than the highest sequence number of a received DT TPDU, plus one.
`12.2.3.6:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A transport entity which receives an AK TPDU shall consider the value of the YR-TU-NR field as its new lower window edge if it is greater than any previously received in a YR-TU-NR field, and the sum of YR-TU-NR and CDT as its new upper window edge subject to the procedures for sequencing AK TPDUs (see 12.2.3.8).
`12.2.3.6:5`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A transport entity shall not transmit or retransmit a DT TPDU with a sequence number outside the transmit window.
`12.2.3.7:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	For the purpose of determining the correct sequence of AK TPDUs, the absence of the subsequence parameter shall be equivalent to the value of the parameter set to zero.
`12.2.3.7:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A transport entity is not required to include the subsequence number in its AK TPDUs.
`12.2.3.7:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If a transport entity chooses not to recognize the subsequence parameter it shall still sequence received AK TPDUs according to 12.2.3.7.a.
`12.2.3.7:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	When the receiving transport entity recognizes an out of sequence AK TPDU it shall ignore it.
`12.2.3.8.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A transport entity shall not allow an interval W to pass without the transmission of an AK TPDU. if the transport entity is not using the procedure following setting CDT to zero (see 12.2.3.8.3) or reduction of the upper window edge (see 12.2.3.8.4), and does not have to acknowledge receipt of any DT TPDU, then it shall achieve this by retransmission of the most recent AK TPDU, with up-to-date window information.
`12.2.3.8.1:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	However, if these procedures are not used then W must be set to ensure enough retransmissions of the AK TPDU so that release of TC is avoided.
`12.2.3.8.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The value of the subsequence parameter, if used, shall be zero (either explicitly or by absence of the parameter) if the sequence number is greater than the field in previous AK TPDUs, sent by the transport entity.
`12.2.3.8.2:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If the sequence number is the same as the previous AK TPDU sent and the CDT field is equal to or greater than the CDT field in the previous AK TPDU sent then the subsequence parameter, if used, shall be equal to that in the previously sent AK TPDU.
`12.2.3.8.2:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	and the CDT field is less than the value of the CDT field in the previous AK TPDU sent than the subsequence parameter, if used, shall be one greater than the value in the previous AK TPDU..
`12.2.3.8.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	In this case the transport entity shall continue to transmit the AK TPDU at an interval of W.
`12.2.3.8.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	An AK TPDU which is subject to the retransmission procedure shall not contain the flow control confirmation parameter.
`12.2.3.8.3:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If it is required to transmit this parameter concurrently, an additional AK TPDU shall be transmitted having the same values in the sequence, subsequence (if applicable) and credit fields.
`12.2.3.8.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	This retransmission procedure for any particular AK TPDU shall terminate when:
`12.2.3.8.4:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	In this case the transport entity shall continue to transmit the AK TPDU at an interval of W.
`12.2.3.8.4:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	An AK TPDU which is subject to the retransmission procedure shall not contain the flow control confirmation parameter.
`12.2.3.8.4:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If it is required to transmit this parameter concurrently, an additional AK TPDU shall be transmitted having the same values in the sequence, subsequence (if applicable) and credit fields.
`12.2.3.9:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The lower window edge, your subsequence and your credit fields shall be set to the same values as the corresponding fields in the most recently received in sequence AK TPDU.
`12.2.4.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The transport entity shall use the explicit variant of normal release (see 6.7).
`13.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	All the transport protocol data units (TPDUs) shall contain an integral number of octets.
`13.2:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	TPDUs shall contain, in the following order:
`13.2.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The length indicated shall be the header length in octets including parameters, but excluding the length indicator field and user data, if any.
`13.2.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If the variable part is present, it shall contain one or more parameters.
`13.2.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	For example, in the case of a single parameter contained within the variable part, two octets are required for the parameter code and the parameter length indication itself.
`13.2.3:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If any parameter is duplicated then the later value shall be used.
`13.2.3:4`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A parameter not defined in this International Standard shall be treated as a protocol error in any received TPDU except a CR TPDU; in a CR TPDU it shall be ignored.
`13.2.3:5`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If the responding transport entity selects a class for which a parameter of the CR TPDU is not defined, it may ignore this parameter, except the class and option, and alternative protocol class parameters which shall always be interpreted.
`13.2.3:6`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A parameter defined in this International Standard but having an invalid value shall be treated as a protocol error in any received TPDU except a CR TPDU.
`13.2.3:7`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	In a CR TPDU it shall be treated as a protocol error if it is either the class and option parameter or the alternative class parameter or the additional option parameter; otherwise it shall be either ignored or treated as a protocol error.
`13.2.3.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	This parameter shall be present in a CR TPDU and shall be present in all other TPDUs except when the non use of checksum option is selected.
`13.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The length of the CR TPDU shall not exceed 128 octets.
`13.3.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The structure of the CR TPDU shall be as follows:
`13.3.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The structure of this part shall contain:
`13.3.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	This field shall take one of the following values:
`13.3.3:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Second and subsequent choices are listed in the variable part if required.
`13.3.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	This parameter shall always be present in a CR TPDU requesting Class 4, even if the checksum selection parameter is used to request non-use of the checksum facility.
`13.4.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The structure of the CC TPDU shall be as follows:
`13.4.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The fixed part shall contain:
`13.4.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Parameters ruled out by selection of an alternative class and option shall not be present.
`13.5.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The structure of the DR TPDU shall be as follows:
`13.5.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The fixed part shall contain:
`13.5.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	This field shall take one of the following values:
`13.5.5:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	This field shall not exceed 64 octets and is used to carry TS- user data.
`13.5.5:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	When a DR TPDU is used in Class 0 it shall not contain this field.
`13.6:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	This TPDU shall not be used in Class 0.
`13.6.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The structure of DC TPDU shall be as follows:
`13.6.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The fixed part shall contain:
`13.6.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The variable part shall contain the checksum parameter if the condition in (see 13.2.3.1) applies.
`13.7.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Depending on the class and the option the DT TPDU shall have one of the following structures.
`13.7.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The fixed part shall contain:
`13.7.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The variable part shall contain the checksum parameter if the condition in see 13.2.3.1 applies.
`13.8:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The ED TPDU shall not be used in Class 0 or in Class 2 when the no explicit flow control option is selected or when the expedited data transfer service has not been selected for the connection.
`13.8.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Depending on the format negotiated at connection establishment the ED TPDU shall have one of the following structures:
`13.8.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The fixed part shall contain:
`13.8.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	NOTE - Depending on the format the fixed part shall be either octets 2 to 5 or 2 to 8.
`13.8.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The variable part shall contain the checksum parameter if the condition defined in 13.2.3.1 applies.
`13.9:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	This TPDU shall not be used for Class 0 and Class 2 when the "no explicit flow control" option is selected, and for Class 1 when the network receipt confirmation option is selected.
`13.9.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Depending on the class and option agreed the AK TPDU shall have one of the following structures:
`13.9.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The fixed part shall contain (in octet 2 to 5 when normal format is used, 2 to 10 otherwise) the following parameters:
`13.9.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	and shall take the value 0.
`13.9.3:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	For extended formats, octets 5, 6 and 7 together with bits 7-1 of octet 8; bit 8 of octet 8 is not significant and shall take the value 0.
`13.10:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	This TPDU shall not be used for Class 0 and Class 2 when the no explicit flow control option is selected.
`13.10.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	Depending on the option (normal or extended format) the TPDU structure shall be:
`13.10.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The fixed part shall contain (in octets 2 to 5 when normal format is used, in octets 2 to 8 otherwise):
`13.10.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	For normal formats bits 7-1 of octet 5; bit 8 of octet 5 is not significant and shall take the value 0.
`13.10.3:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	For extended formats, octets 5,6 and 7 together with bits 7-1 of octet 8; bit 8 of octet 8 is not significant and shall take the value 0.
`13.11:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The RJ TPDU shall not be used in Classes 0, 2 and 4.
`13.11.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The RJ TPDU shall have one of the following formats:
`13.11.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The fixed part shall contain (in octets 2 to 5 when normal format is used, in octets 2 to 10 otherwise):
`13.11.3:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	For normal formats, bits 7-1 of octet 5; bit 8 of octet 5 is not significant and shall take the value 0.
`13.11.3:3`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	For extended formats, octets 5,6 and 7 together with bits 7-1 of octet 8; bit 8 of octet 8 is not significant and shall take the value 0.
`13.12.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The fixed part shall contain:
`13.12.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	This parameter shall be present if the condition in 13.2.3.1 applies.
`14.1:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	A system claiming to implement the procedures specified in this standard shall comply with the requirements in 14.2 - 14.5.
`14.2:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	The system shall implement Class 0 or Class 2 or both.
`14.3:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If the system implements Class 3 or Class 4, it shall also implement Class 2.
`14.4:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	If the system implements Class 1, it shall also implement Class 0.
`14.5:1`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	For each class which the system claims to implement, the system shall be capable of:
`14.6:1`	`not-a-requirement` never bound Ze the sentence states a fact or describes another document, and directs no implementation	the clause heading "14.6 Claims of Conformance Shall State", a title rather than a sentence	Claims of Conformance Shall State
`14.6:2`	`feature-out-of-scope` never bound Ze the RFC makes a feature OPTIONAL, Ze decided not to offer it, and this obligation is conditional on offering it	the obligation binds a transport entity running one of the ISO 8073 transport classes, and ze implements no ISO Transport Protocol: it has no TPDU sender, no TPDU receiver and no transport connection. The standard binds only "A system claiming to implement the procedures" specified in it, and ze makes no such claim. ze reuses one part of this document, the Annex B Fletcher checksum, at internal/plugins/isis/packet/checksum.go and internal/plugins/ospf/types/checksum.go. The scope decision is recorded in the Enrolment reason and Scope rows of rfc/short/rfc905.md, which put the three ISO Transport TPDU requirements out of reach on the same ground.	d) the maximum size of TPDU implemented; the value shall be chosen from the following list and all values in the list which are less than this maximum shall be implemented:

Superseded

No document obsoletes RFC 905, so its obligations are stated where they were written.