{ "schema": "varexis-index-free-publication-preview/1", "catalogue_version": "pub-9-tranche-59-v1", "route_id": "agentic_reviewed_rar_invalid_fields", "record_id": "VXI-EXT-PROCUREMENT-RAR-INVALID-FIELDS-01-v1", "question": "May an OAuth RAR server silently ignore unknown fields in a known authorization-details type?", "answer": "RFC 9396 requires rejection with invalid_authorization_details for unknown types, invalid fields or values, and missing required fields. A type definition can expressly permit extension fields, so not every unfamiliar field is automatically invalid. Validation must use the supported type definition rather than silently accepting malformed authority terms.", "records": [ { "record_id": "VXI-EXT-PROCUREMENT-RAR-INVALID-FIELDS-01-v1", "url": "/varexis-index/records/rar-invalid-fields.json", "content_sha256": "7f9147577261ebc7d969a5cc99b2582737d0b091cb2bca23f350d5c91059e626", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-25T20:55:19.974986+00:00", "record_id": "VXI-EXT-PROCUREMENT-RAR-INVALID-FIELDS-01-v1", "record_kind": "external_reference", "title": "OAuth RAR invalid authorization details", "system": "IETF RFC 9396", "evidence_family": "vendor_evidence_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "May an OAuth RAR server silently ignore unknown fields in a known authorization-details type?", "near_questions": [ "What happens when an OAuth RAR type is unsupported?", "Can an authorization server ignore an invalid RAR field?", "Are extension fields always forbidden in authorization_details?", "Which error identifies malformed detailed authorization?" ], "supported_claims": [ { "claim": "RFC 9396 requires rejection with invalid_authorization_details for unknown types, invalid fields or values, and missing required fields. A type definition can expressly permit extension fields, so not every unfamiliar field is automatically invalid. Validation must use the supported type definition rather than silently accepting malformed authority terms.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "The applicable type definition determines which fields are known. Do not reject legitimate type-defined extensions merely because they are not common RFC fields, or claim deployed enforcement was tested.", "Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.", "No expanded capabilities or licences for existing INDEX executables." ], "public_summary": "RFC 9396 requires rejection with invalid_authorization_details for unknown types, invalid fields or values, and missing required fields. A type definition can expressly permit extension fields, so not every unfamiliar field is automatically invalid. Validation must use the supported type definition rather than silently accepting malformed authority terms.", "related_record_ids": [], "source_review": { "source_type": "official_external_documentation", "source_title": "IETF RFC 9396", "source_url": "https://www.rfc-editor.org/rfc/rfc9396.txt", "checked_on": "2026-10-25", "candidate_record_id": "VXI-EXT-PROCUREMENT-RAR-INVALID-FIELDS-01-v1", "candidate_record_sha256": "b4ec5326c51bed89c616a9358e7dd902225bdb9ae7915fab0e92f42d0030102c", "method": "Primary documentation reviewed for the published bounded statement.", "deployment_tested_by_varexis": false, "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research." }, "answer_policy": { "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY", "bounded_answer": "RFC 9396 requires rejection with invalid_authorization_details for unknown types, invalid fields or values, and missing required fields. A type definition can expressly permit extension fields, so not every unfamiliar field is automatically invalid. Validation must use the supported type definition rather than silently accepting malformed authority terms.", "required_buyer_context": "Supported RAR type versions; Required fields and extension policy; Actual validation response. Buyer deployment not inspected.", "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state." }, "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.", "decision_profile": { "schema": "varexis-vendor-evidence-review/1", "review_status": "documentation_review_only", "checked_on": "2026-10-25", "claim_to_check": "May an OAuth RAR server silently ignore unknown fields in a known authorization-details type?", "documented_statement": { "status": "documented", "statement": "RFC 9396 requires rejection with invalid_authorization_details for unknown types, invalid fields or values, and missing required fields. A type definition can expressly permit extension fields, so not every unfamiliar field is automatically invalid. Validation must use the supported type definition rather than silently accepting malformed authority terms.", "source_ids": [ "rfc9396" ] }, "review_inference": { "status": "review_inference", "statement": "Fail closed on malformed or unrecognized fine-grained authority descriptions. This is a documentation-review judgment, not an observed deployment outcome.", "source_ids": [ "rfc9396" ] }, "buyer_evidence_required": [ "Supported RAR type versions", "Required fields and extension policy", "Actual validation response" ], "review_condition": { "status": "varexis_review_policy", "statement": "Refuse buyer-specific assurance from documentation alone. The applicable type definition determines which fields are known. Do not reject legitimate type-defined extensions merely because they are not common RFC fields, or claim deployed enforcement was tested." }, "unknowns": "The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.", "unknown_finding": { "status": "unknown", "statement": "The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected." }, "evidence_sources": [ { "source_id": "rfc9396", "url": "https://www.rfc-editor.org/rfc/rfc9396.txt", "final_url": "https://www.rfc-editor.org/rfc/rfc9396.txt", "status": 200, "captured_at_utc": "2026-10-25T20:04:28.371Z", "sha256": "d6a8f032d8a585daae1c33a8c7b6e539d199f886ec8cc1c7898436f7f2eed29c", "bytes": 65926, "title": "IETF RFC 9396", "hash_basis": "SHA-256 of unmodified HTTP response body bytes", "rights_review": "Original factual paraphrase of the cited IETF RFC; IETF Trust and contributor rights remain applicable. No RFC text, code component or modified standard is redistributed.", "checked_on": "2026-10-25", "capture_status": 200, "claim_review_completed": true, "reviewed_sections": [ "Sections 3, 7 and 7.1", "Section 2.2", "Section 6.1", "Section 3.1", "Section 3.2", "Section 5", "Section 12" ], "version_context": "Fixed IETF RFC 9396 publication; later applicable updates and actual implementation conformance require separate review." } ], "observed_deployment": false, "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.", "paid_value": { "decision_context": "Fail closed on malformed or unrecognized fine-grained authority descriptions.", "free": "Complete review, practical questions, sources and limitations; may be saved locally.", "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.", "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.", "excluded": [ "Fresh vendor research", "Continuous monitoring or change alerts", "Testing the buyer configuration", "Private evidence or vendor certification" ], "integrity": "Hashes identify content versions; they do not prove truth or provide a signature." }, "revalidation": { "trigger": "A saved purchase does not recheck the source or buyer configuration.", "specific_watch": "Recheck Section 5 in IETF RFC 9396 when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval." }, "buyer_relevance": "Fail closed on malformed or unrecognized fine-grained authority descriptions.", "refusal_conditions": [ "Refuse buyer-specific assurance from documentation alone. The applicable type definition determines which fields are known. Do not reject legitimate type-defined extensions merely because they are not common RFC fields, or claim deployed enforcement was tested." ] }, "niche": { "niche_id": "agent-authority-action-evidence", "label": "Agent Authority & Action Evidence", "classification_id": "governance", "classification_label": "Agent Governance & Policy Boundaries", "topic_id": "governance", "buyer_intent": "Fail closed on malformed or unrecognized fine-grained authority descriptions.", "comparison_role": "supplementary_discovery" }, "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.", "service_route": { "request_guide": "/varexis-index/request.html", "request_workflow": "/varexis-index/request-workflow.json", "service_id": "single_request", "service_routes_url": "/varexis-index/service-routes.json", "payment_required": true, "availability_endpoint": "/api/index/capabilities", "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED", "checkout_url": "/index-access" }, "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.", "human_page": "/varexis-index/catalog.html#rar-invalid-fields", "machine_readable_record": "/varexis-index/records/rar-invalid-fields.json" } } ], "access": { "mode": "exact_http_only", "payment_required": false, "purchase_url": null, "mcp_preview_available": false, "paid_saved_retrieval_available": false, "natural_language_search_qualified": false }, "boundary": "Catalogue additions are available free through the exact HTTP JSON links below. Enhanced natural-language discovery is not yet qualified for these records. They are outside MCP search, MCP preview and paid saved retrieval. No search qualification, executable capability or entitlement is added.", "content_sha256": "e2d58bc4bf098674ec499b28fa9393365f081370450c9522adde25bd38aeda98" }