{"as_of":"2026-08-17T09:14:00Z","caps":{"database_statements":6,"inbound":100,"outbound":100},"context_digest":"sha256:71ad0451dfbba05de68d27ca6175734d34e785f38a11b340c293c7c9ff7e2e21","coverage":[{"denominator":58,"lane":"reference_resolution","note":"Typed states for the displayed outbound observations.","records_observed":58,"source":"paper_references, paper_reference_links","source_observed_at":"2026-08-16T10:30:35.024270Z","state":"measured"},{"denominator":59,"lane":"standing_notices","note":"One-hop event checks from named stored sources.","records_observed":59,"source":"scholarly_work_events, retraction_status_cache","source_observed_at":"2026-08-17T06:30:58.91139+00:00","state":"measured"},{"denominator":1,"lane":"inbound_itemization","note":"Pith citing papers itemized under the disclosed page cap.","records_observed":1,"source":"paper_references, paper_reference_links","source_observed_at":"2026-08-12T17:10:55.639191Z","state":"measured"},{"denominator":1,"lane":"external_citation_measurements","note":"A source-named dated measurement, never combined with another source.","records_observed":0,"source":"pith","source_observed_at":"2026-08-12T17:10:55.692003Z","state":"measured"}],"external_citation_measurements":[],"inbound":[{"citation":{"cited_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"cited_work":{"arxiv_id":"2504.18050","doi":null,"metadata_source":"pith","pith_arxiv_id":"2504.18050","snapshot_observed_at":"2026-08-12T17:10:55.692003Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","venue":"cs.SE","work_id":"2b5778a4-e1ce-495c-9066-60087f0fcc67","year":2025},"citing_paper":{"arxiv_id":"2411.12882","last_updated":"2025-06-06T05:27:10Z","snapshot_observed_at":"2026-08-15T15:30:04.308785Z","submitted_at":"2024-11-19T22:00:01Z","title":"ProSec: Fortifying Code LLMs with Proactive Security Alignment","version":3},"reference_index":75,"source":"arxiv_source","source_observed_at":"2026-08-12T17:10:55.639191Z"},"links":{"cited_paper":"/paper/2504.18050","citing_paper":"/paper/2411.12882"},"observation_digest":"sha256:bd5b02a875aa79b8f85f2034320c2c2e28ade6403662f77215a481209d4ba4dc","observation_id":"42378c20-25d7-4e37-a5e6-fee996dc43bc","resolution":{"observed_at":"2026-08-12T17:10:55.697789Z","resolver_source":"local_arxiv","status":"verified_exact"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}}],"links":{"evidence":"/evidence","html":"/paper/2504.18050/citation-record","integrity":"/paper/2504.18050/integrity","json":"/paper/2504.18050/citation-record.json","paper":"/paper/2504.18050"},"outbound":[{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.547270Z","title":"RFC 793 - Transmission Control Protocol","venue":null,"work_id":"1e82c4a5-571d-460f-9737-88c26be5965f","year":1981},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":1,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.818776Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:51fcd7ce59a856739220a1bbd3675a678d1f006da017fdc0fe39682ec905da38","observation_id":"1a54d8cb-cc26-4471-8051-21746c75ecac","resolution":{"observed_at":"2026-08-16T10:30:36.550805Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.537025Z","title":"Go Networking","venue":null,"work_id":"9dc40646-91d7-46b3-9726-85c72ba99fdf","year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":2,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.823119Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:d2547c4c37944c1106e7070b6b845a735d1e6fb9906e1e36870dc4f9e2fb7800","observation_id":"37aaa5a4-23ca-4f49-8b7c-01a05dcc2517","resolution":{"observed_at":"2026-08-16T10:30:36.540348Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.526668Z","title":"IETF DataTracker","venue":null,"work_id":"72966724-218f-4054-8633-482b79b32633","year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":3,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.826710Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:95c9c811576d19c3ed6714d2c89e59ad1473300e750a15b4578175e2eeac2ec2","observation_id":"e5ad3519-7d1a-4bfc-b6be-2baab3fcabe5","resolution":{"observed_at":"2026-08-16T10:30:36.530226Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.515784Z","title":"Impacket","venue":null,"work_id":"1bc56eec-5c8f-404c-8f5c-d64614c55d96","year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":4,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.830596Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:11298d6bafeb9bca15af9a07c0be0bca96c997672f9edee5b5836f9fc3eab7dc","observation_id":"c9eadd48-5dee-440f-ae5f-9fca5018a1cf","resolution":{"observed_at":"2026-08-16T10:30:36.519713Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.504182Z","title":"Internet Standard","venue":null,"work_id":"01551bb8-91da-40c4-a4b0-b455f74793fb","year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":5,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.834267Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:84a6982def0ae58d3799e311cc5c6f364680c5e73e1e3bd36b4c8327fe67ca3e","observation_id":"c48ee981-bfbd-4e7d-80a9-24c6c3f5fc99","resolution":{"observed_at":"2026-08-16T10:30:36.508571Z","resolver_source":"raw_fallback","status":"verified_fuzzy"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.494037Z","title":null,"venue":null,"work_id":"b52c0cd2-9df4-43f0-ab59-f074a4e24d22","year":2023},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":6,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.837902Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:baa1a183f4f293145a6c31c0325374be4cb890e0d1df0ef0b90b3ab03e008c9f","observation_id":"7d09a8cc-9af6-4b93-b528-422f37ad9840","resolution":{"observed_at":"2026-08-16T10:30:36.497400Z","resolver_source":"raw_fallback","status":"unresolved"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":"10.1007/978-3-031-80889-0_17","metadata_source":"doi_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:35.178175Z","title":null,"venue":null,"work_id":"c358e82a-c8da-4ca1-9327-e6baa222def3","year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":7,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.841598Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:20f052f1da024441deaada877242558200889738c713dd494a3f29d13481c818","observation_id":"e0397205-19dd-4b2c-b13e-b2968a1de67d","resolution":{"observed_at":"2026-08-16T10:30:35.181756Z","resolver_source":"doi","status":"verified_exact"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.483757Z","title":null,"venue":null,"work_id":"6f982be1-542f-4c96-a624-5c24f56d7c6e","year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":8,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.845178Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:412010363cebccca8d489a34842809bf7c11ca5269d2f66abf85d9fa723c0482","observation_id":"d03be1eb-84ce-4ef3-9250-3ad857fee98b","resolution":{"observed_at":"2026-08-16T10:30:36.487042Z","resolver_source":"raw_fallback","status":"unresolved"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.473933Z","title":null,"venue":null,"work_id":"ab467b9b-a003-4c37-b924-c88a6616d584","year":2008},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":9,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.848741Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:0c4c2f9e95cec5c99ba2ec076f31c3783bb006ae134843848c3efdb1232673f3","observation_id":"1c40bc8a-d5ad-4177-b93f-f745b65ac038","resolution":{"observed_at":"2026-08-16T10:30:36.477312Z","resolver_source":"raw_fallback","status":"unresolved"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":{"arxiv_id":"2003.12012","last_updated":"2020-03-24T15:06:05Z","snapshot_observed_at":"2026-08-10T05:50:45.445846Z","submitted_at":"2020-03-24T15:06:05Z","title":"TRACER: A Framework for Facilitating Accurate and Interpretable Analytics for High Stakes Applications","version":1},"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":"2003.12012","snapshot_observed_at":"2026-08-16T10:30:34.852322Z","title":"Clarke, Alex Groce, Somesh Jha, and Helmut Veith","venue":null,"work_id":null,"year":2003},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":10,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.852322Z"},"links":{"cited_paper":"/paper/2003.12012","citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:75837fcc22050a8b46b57f47dcaf553b36c22ea3ffb1fdc91ca1149f821e0781","observation_id":"1b70c476-7e34-464b-9d1e-162ae4296b90","resolution":{"observed_at":"2026-08-16T10:30:34.852322Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":"10.1109/sp.2017.40","metadata_source":"doi_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:35.165515Z","title":"Endadul Hoque, Huangyi Ge, Aniket Kate, Cristina Nita-Rotaru, and Ninghui Li","venue":null,"work_id":"59031bb4-1777-4f15-a130-b4d6e56ab068","year":2017},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":11,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.855886Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:6586086f0c9249591c095f67c40f5465097904a87c274fdad9a3a6e45eec2a69","observation_id":"8bc25122-8c85-4ecf-a7cc-a022c4432b36","resolution":{"observed_at":"2026-08-16T10:30:35.170333Z","resolver_source":"doi","status":"verified_exact"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.463970Z","title":null,"venue":null,"work_id":"f51c82e4-3b81-4f96-b984-b243f2f7783d","year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":12,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.859442Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:a5f01c09f25c699fa99b7810d676ccd222e06275e7d7c1441dc6cc5b9ce2fff9","observation_id":"34b4ae25-1136-47e0-b17b-72332eddc0f9","resolution":{"observed_at":"2026-08-16T10:30:36.467377Z","resolver_source":"raw_fallback","status":"unresolved"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.866511Z","title":null,"venue":null,"work_id":null,"year":2023},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":14,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.866511Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:35c7bdff298dc44366b67bc86ca50fb366fc8f8ccae9a6b3dca4b931f4405b61","observation_id":"af0a3704-c0c4-4cab-8597-95ccaa5aeb28","resolution":{"observed_at":"2026-08-16T10:30:34.866511Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":"7900.96806","doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.249457Z","title":null,"venue":null,"work_id":"54e0b9cf-1903-4ed4-bf94-43e32f9664e3","year":2004},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":15,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.869772Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:056282909a1cfa0c61aa254b93d89fb9c7c9ae9e9f8d7aa5b5405f35c97f485a","observation_id":"a66ba9cc-a661-4def-afbf-abf6a2c5e381","resolution":{"observed_at":"2026-08-16T10:30:36.257155Z","resolver_source":"raw_fallback","status":"metadata_mismatch"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.873179Z","title":null,"venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":16,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.873179Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:d05f9b8d95b0a5cde25ab6c39c0563bbb1416fbfbad331066cdd90779be4e6ce","observation_id":"821d9803-af27-4540-afc2-e07b13dba682","resolution":{"observed_at":"2026-08-16T10:30:34.873179Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.876459Z","title":null,"venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":17,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.876459Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:5a279eec74899ba73e079d1173d65d1e4e8934873cf7240937eaef445c0279ad","observation_id":"1fd92c8f-761e-435b-ad63-b8b387b35625","resolution":{"observed_at":"2026-08-16T10:30:34.876459Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.879689Z","title":null,"venue":null,"work_id":null,"year":null},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":18,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.879689Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:6f53a4b256e4292c3e9e5840fc6fa8f28e15a7f06c60290b69aca0ffb5150027","observation_id":"91c0cb2f-7441-469f-9f57-3b3434d6d54c","resolution":{"observed_at":"2026-08-16T10:30:34.879689Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.886535Z","title":null,"venue":null,"work_id":null,"year":2012},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":19,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.886535Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:c238c0d6a22924106844ec1a0b102c4dc9602a30cdfbbb512beee88b9ff4f313","observation_id":"d4444e24-212a-4d3d-a3a7-495a8111ec23","resolution":{"observed_at":"2026-08-16T10:30:34.886535Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":{"arxiv_id":"2501.18160","last_updated":"2025-05-29T22:08:26Z","snapshot_observed_at":"2026-08-16T10:46:03.673514Z","submitted_at":"2025-01-30T05:56:30Z","title":"RepoAudit: An Autonomous LLM-Agent for Repository-Level Code Auditing","version":3},"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":"2501.18160","snapshot_observed_at":"2026-08-16T10:30:34.889567Z","title":null,"venue":null,"work_id":null,"year":2025},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":20,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.889567Z"},"links":{"cited_paper":"/paper/2501.18160","citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:08ea95514eabea25ee17ff80307587ae69909135956f0fc79e93f50aa956e903","observation_id":"dc286582-63a6-4242-b8dd-e9533310b682","resolution":{"observed_at":"2026-08-16T10:30:34.889567Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.899248Z","title":null,"venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":23,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.899248Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:bf2cd3faf8415464f3bf868a09d4c35e78f1d17c834cb53eafec3baacbf6a1e3","observation_id":"475afb52-99a7-4471-bcdb-d60aa0d12e52","resolution":{"observed_at":"2026-08-16T10:30:34.899248Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":{"arxiv_id":"2504.11711","last_updated":"2025-05-31T06:47:58Z","snapshot_observed_at":"2026-08-16T12:40:39.027062Z","submitted_at":"2025-04-16T02:17:06Z","title":"The Hitchhiker's Guide to Program Analysis, Part II: Deep Thoughts by LLMs","version":3},"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":"2504.11711","snapshot_observed_at":"2026-08-16T10:30:34.902399Z","title":null,"venue":null,"work_id":null,"year":2025},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":24,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.902399Z"},"links":{"cited_paper":"/paper/2504.11711","citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:e8682cc175bbc775a3f4ea7d11c835be79be9ea1b2cbbb0844c2eadc244703c1","observation_id":"07e176bf-6188-42d3-ab3a-c23ffdcfcf1e","resolution":{"observed_at":"2026-08-16T10:30:34.902399Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.905932Z","title":null,"venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":25,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.905932Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:448cb9c7858fb8de714b78684641c29339df7039e58c612a73bb10decda41d73","observation_id":"d23479ad-697b-4b68-8f24-c3106632e127","resolution":{"observed_at":"2026-08-16T10:30:34.905932Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.909415Z","title":null,"venue":null,"work_id":null,"year":2023},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":26,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.909415Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:c58e253d242536bfd0475a6355e61b64bd0d56934484ab8a40087dd70f5d1b22","observation_id":"b3e6ce81-8a8c-4e25-b378-9c468bf052e7","resolution":{"observed_at":"2026-08-16T10:30:34.909415Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.446622Z","title":null,"venue":null,"work_id":"efca0098-9180-4fa1-9c51-88217856fd52","year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":27,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.912883Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:7e87a9b4fde4d1af42feb00c1835611dd59d3b2439c3a03a3f35b852bf6a5773","observation_id":"7ceee53c-a61b-42c4-869c-6da7353c32bc","resolution":{"observed_at":"2026-08-16T10:30:36.450129Z","resolver_source":"raw_fallback","status":"unresolved"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.915918Z","title":"Mosthaf and Andrzej Wasowski","venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":28,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.915918Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:57c1167d2485c1f2dca6b5b345b8fc92a3b23bc6736b10db25f51691490bbc63","observation_id":"5040585e-8478-40e1-bf9a-c9e68a2e0294","resolution":{"observed_at":"2026-08-16T10:30:34.915918Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.436375Z","title":null,"venue":null,"work_id":"abd35322-b205-4311-829b-7eb0035f6abc","year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":29,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.919004Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:6d453c6e7c1308aa20aedda02f4161d74656f20d2d3c0f1cec423eeb99cc0ba7","observation_id":"889c2195-4aab-495a-a842-f27e712f5ec2","resolution":{"observed_at":"2026-08-16T10:30:36.440123Z","resolver_source":"raw_fallback","status":"unresolved"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.922088Z","title":null,"venue":null,"work_id":null,"year":2021},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":30,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.922088Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:38d71ccc7beab57468de33eab42bf27e3401c1e65d0c1bde20ad0c6dd73c8a7d","observation_id":"65b1cfe1-9202-4671-933c-5a37e9f0191e","resolution":{"observed_at":"2026-08-16T10:30:34.922088Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.925208Z","title":null,"venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":31,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.925208Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:1991b8e0b0c413bcf53fe8bf75ca4af320647b18972a0f452890ad1d6e199440","observation_id":"9d492b06-34aa-46c0-8847-4562814c6ed2","resolution":{"observed_at":"2026-08-16T10:30:34.925208Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.425706Z","title":null,"venue":null,"work_id":"2ed26a51-b3e3-4b7c-bdcf-6852ea651fa5","year":2022},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":32,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.928648Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:7525a72377c05ffa1d32f1a4aec8ab69c533f11312259a2830a570dd9f1611e5","observation_id":"4e44c684-3347-4939-bd64-3f8597f9622a","resolution":{"observed_at":"2026-08-16T10:30:36.429050Z","resolver_source":"raw_fallback","status":"unresolved"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.415279Z","title":null,"venue":null,"work_id":"522fcfd3-5492-4016-a809-ed4cad167054","year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":33,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.932748Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:133bbaadcab3a8050229256ffa1f0719ca791ad1c82ddee58902b88bb7fe07be","observation_id":"8c537db1-4672-46e9-9f03-592511bfc742","resolution":{"observed_at":"2026-08-16T10:30:36.418777Z","resolver_source":"raw_fallback","status":"unresolved"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.404541Z","title":null,"venue":null,"work_id":"4326568e-67cd-444e-86b4-e587c6368598","year":2004},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":34,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.936119Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:9b10889d944c6eafcf879d5962db9b4dfad47ceae20f7effa0da5988802770d5","observation_id":"822ad99b-0161-4cb1-9702-bbc0a3cac67e","resolution":{"observed_at":"2026-08-16T10:30:36.408077Z","resolver_source":"raw_fallback","status":"unresolved"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.939455Z","title":null,"venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":35,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.939455Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:6a9f840a6267c89d8cac4ae6f2e4e840af6ca8afc3fe10a0e99974f0a2e1d127","observation_id":"5a7618e2-f5dc-4395-b38b-465affb68896","resolution":{"observed_at":"2026-08-16T10:30:34.939455Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.386495Z","title":null,"venue":null,"work_id":"f4580af8-0913-4212-b395-2354133d7e30","year":2023},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":36,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.942924Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:8f2d406dde011aca07d98b62ce15f1312145abc84c75aa0081e7dc5cb9e7133f","observation_id":"f6469bb9-1f5f-4d5a-813b-2b730b46eab6","resolution":{"observed_at":"2026-08-16T10:30:36.390650Z","resolver_source":"raw_fallback","status":"unresolved"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.374504Z","title":null,"venue":null,"work_id":"f212621d-48b3-4ded-a176-7c7aab344cc0","year":2019},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":37,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.946182Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:f26eb106fae21d1a734d2a59f7b004530576223d03cc4c9f152dd4313e6135ff","observation_id":"18c1af33-729a-4bf4-84b7-579ac115e3b4","resolution":{"observed_at":"2026-08-16T10:30:36.378292Z","resolver_source":"raw_fallback","status":"unresolved"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.949514Z","title":null,"venue":null,"work_id":null,"year":2020},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":38,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.949514Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:c8d298e9a8a6fcb0413dad33e8a9ba4ad47121c593b9f4022edbbe0d7b9b13a7","observation_id":"2959b446-7ec4-4be4-b9a7-524463519dd4","resolution":{"observed_at":"2026-08-16T10:30:34.949514Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.363910Z","title":null,"venue":null,"work_id":"417e6cf5-288e-44d6-a203-23fa0583ca9d","year":2020},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":39,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.952727Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:96bf006677435ac04d2447991382f8df1dcbc20ea0bed13d558730557d5d840c","observation_id":"28db4f10-da65-4955-9906-b465da82a374","resolution":{"observed_at":"2026-08-16T10:30:36.367546Z","resolver_source":"raw_fallback","status":"unresolved"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.956019Z","title":null,"venue":null,"work_id":null,"year":2022},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":40,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.956019Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:2261c201a6a9b269d3db6766ef6d3da73effe83bd3c63535879ed0462eccb6f7","observation_id":"cb0aa704-b7b8-4388-b4e8-31709fcb53e6","resolution":{"observed_at":"2026-08-16T10:30:34.956019Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.959401Z","title":null,"venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":41,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.959401Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:03357dcf08bed320c3b77d1ca7936f1e87d32e9d21f642af4fe589e7cb413b6b","observation_id":"9e289ca9-1f31-48b6-b400-c7bbfc3ffd50","resolution":{"observed_at":"2026-08-16T10:30:34.959401Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.962716Z","title":null,"venue":null,"work_id":null,"year":2023},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":42,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.962716Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:f1e87e0ddbb38ad43fe50a17f514f4986599f387f6cc03f697159c6e7f38abba","observation_id":"4b53b592-8ccd-443b-9c57-aaa76fd01b4c","resolution":{"observed_at":"2026-08-16T10:30:34.962716Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.966073Z","title":null,"venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":43,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.966073Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:3c0836cae631595a8c49b799b85b3ee6d0e52b9e08a1aaa6244fdfddc828db9c","observation_id":"fa679b74-d752-4d71-a808-4072fbc4c460","resolution":{"observed_at":"2026-08-16T10:30:34.966073Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.969403Z","title":null,"venue":null,"work_id":null,"year":2023},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":44,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.969403Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:0e1db61f528dbd286ae090971c64cf1b650f69945b1dc4e06220e88a8010457e","observation_id":"62750304-b277-4189-91c2-4a317d7c30ee","resolution":{"observed_at":"2026-08-16T10:30:34.969403Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.972625Z","title":null,"venue":null,"work_id":null,"year":2022},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":45,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.972625Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:8668259ded0891c1a306a029314124660ec878dcc0848271795eb9fb3d66f47b","observation_id":"5d876210-712e-47d1-b8eb-0ba4b34c5033","resolution":{"observed_at":"2026-08-16T10:30:34.972625Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.352252Z","title":null,"venue":null,"work_id":"0744bd44-d8fe-47cb-87d1-d26a6698829f","year":2006},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":46,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.975793Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:92f7726e523a0b9593e54e1ba44533d798258bfde1685f163f97f78777f84355","observation_id":"85917c9a-b212-47b5-98fc-90178258345f","resolution":{"observed_at":"2026-08-16T10:30:36.356202Z","resolver_source":"raw_fallback","status":"unresolved"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":"10.1145/3660816","metadata_source":"doi_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:35.100748Z","title":null,"venue":null,"work_id":"1c237813-7af2-4c2a-ae7a-e52b398d6599","year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":47,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.978982Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:a2bfa1eb8ef9e1ea2c75029611aacb451144bbff136e69d5c037a904fafa8707","observation_id":"cf5dd2ef-dd5d-4292-a1de-d316c711a919","resolution":{"observed_at":"2026-08-16T10:30:35.104965Z","resolver_source":"doi","status":"verified_exact"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.341164Z","title":null,"venue":null,"work_id":"c45dac54-a2fd-4ba5-ae29-ad57e434740a","year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":48,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.982377Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:eb7cff4956898b91c492a8fd267bf78e5af5b56af621ec9d59e63ca9d6368394","observation_id":"0a6086ad-bcfa-405d-902b-51799f78b9ac","resolution":{"observed_at":"2026-08-16T10:30:36.344554Z","resolver_source":"raw_fallback","status":"unresolved"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.985792Z","title":null,"venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":49,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.985792Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:70ecd3a443821d29e4b1fd58cf1e2d32b0b1b5af367fd325b265f937cdae7cea","observation_id":"d483e8a1-5936-4276-a0e7-bbe3d904f2b4","resolution":{"observed_at":"2026-08-16T10:30:34.985792Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.989331Z","title":null,"venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":50,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.989331Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:ad601f52e74d149601f4f2ff1c74eeb20e43a206ec53910afab5e929bc9a15a5","observation_id":"e5fa47f8-e40a-4a6f-85fd-3d7564aaf619","resolution":{"observed_at":"2026-08-16T10:30:34.989331Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.992805Z","title":null,"venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":51,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.992805Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:c47798dfe0b8842393a445c25b63c8cbd42a9853075c81b1ec43e089190b456e","observation_id":"a0323d24-5a3e-4ae2-a2bd-c68c9622a181","resolution":{"observed_at":"2026-08-16T10:30:34.992805Z","resolver_source":null,"status":"malformed_identifier"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.996132Z","title":null,"venue":null,"work_id":null,"year":2023},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":52,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.996132Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:ff7c2567acffc1bc56f3bf3532dbb1fe74f4d6730a176ff88f20d82dbd4a148e","observation_id":"2b8a0d2c-2b98-4df6-9237-638e629bf228","resolution":{"observed_at":"2026-08-16T10:30:34.996132Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:34.999350Z","title":null,"venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":53,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.999350Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:7647d9ceb1ff2590c651649224527227b0cc807982380e3bd393e3ba04cb5659","observation_id":"ffacd51b-4b03-422b-91a3-6b7ea6e8ebcd","resolution":{"observed_at":"2026-08-16T10:30:34.999350Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":{"arxiv_id":"2306.03324","last_updated":"2025-02-09T21:28:58Z","snapshot_observed_at":"2026-08-16T15:26:20.719452Z","submitted_at":"2023-06-06T00:28:39Z","title":"How Effective are Large Language Models in Generating Software Specifications?","version":3},"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":"2306.03324","snapshot_observed_at":"2026-08-16T10:30:35.002840Z","title":null,"venue":null,"work_id":null,"year":2023},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":54,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:35.002840Z"},"links":{"cited_paper":"/paper/2306.03324","citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:bca75fc4ab81faa09714ea39a470f1f6021024726349bcd781bb04e9f89fee1e","observation_id":"93fc367d-a499-4a37-87bc-38d4360c95c7","resolution":{"observed_at":"2026-08-16T10:30:35.002840Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":"raw_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:36.330663Z","title":null,"venue":null,"work_id":"8b9fddb8-5e7b-4745-a2ad-88d103e10e8d","year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":55,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:35.006538Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:f0b171c2a1144297bd3cfd1c133bd1edabc2b0a4bca7fb2469f95f4410ba117c","observation_id":"ec2c703c-49b7-4dec-b860-cbad14eb4b76","resolution":{"observed_at":"2026-08-16T10:30:36.334140Z","resolver_source":"raw_fallback","status":"malformed_identifier"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":"10.1007/s13042-024-02527-3","metadata_source":"doi_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:35.072769Z","title":null,"venue":null,"work_id":"f2134243-0b2c-4845-9209-4d6214c63f32","year":2025},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":56,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:35.009900Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:34e9193ad0ffd604b9f7b7c54fb8e9a945670ebf112c7cc21645f4d92ae2a05d","observation_id":"94dd2816-80a9-4a32-ad73-b8fae78f56a8","resolution":{"observed_at":"2026-08-16T10:30:35.076587Z","resolver_source":"doi","status":"verified_exact"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:35.013302Z","title":null,"venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":57,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:35.013302Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:af4bdea91f567e884dc87276c535b9ca530be32840178eadc4f63893bb46e0d6","observation_id":"225fcbf5-d8a2-4466-a584-2616c8d22e73","resolution":{"observed_at":"2026-08-16T10:30:35.013302Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":"10.1145/3649854","metadata_source":"doi_reference","pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:35.060791Z","title":null,"venue":null,"work_id":"ab461dd6-f310-4ee4-a922-46dc52156280","year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":58,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:35.017049Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:e53f9f29924d970c2b46466be948a2a03e37552ca47b3157ac218631f71a61c6","observation_id":"703d9395-adfd-4963-9319-53f75db0ff88","resolution":{"observed_at":"2026-08-16T10:30:35.065262Z","resolver_source":"doi","status":"verified_exact"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-17T06:30:58.91139+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-08-16T10:30:35.020700Z","title":null,"venue":null,"work_id":null,"year":2021},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":59,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:35.020700Z"},"links":{"citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:b7af8667542ce2bda4f389deaa4f7673e084ebde82f9e400b5bc171e764d1ee3","observation_id":"6bd70577-edeb-4bd9-b903-6747ccd5c307","resolution":{"observed_at":"2026-08-16T10:30:35.020700Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":{"arxiv_id":"2406.11931","last_updated":"2024-06-17T13:51:35Z","snapshot_observed_at":"2026-08-14T04:42:19.578053Z","submitted_at":"2024-06-17T13:51:35Z","title":"DeepSeek-Coder-V2: Breaking the Barrier of Closed-Source Models in Code Intelligence","version":1},"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":"2406.11931","snapshot_observed_at":"2026-08-16T10:30:35.024270Z","title":null,"venue":null,"work_id":null,"year":2024},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":60,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:35.024270Z"},"links":{"cited_paper":"/paper/2406.11931","citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:8cbd43be5e902802d884a4dd6cc9d286ea5ffb4f27d36422497519183e45eefd","observation_id":"8b89d5bd-dba9-4463-b168-8e43f28bf152","resolution":{"observed_at":"2026-08-16T10:30:35.024270Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":{"arxiv_id":"2304.11384","last_updated":"2023-06-14T06:33:10Z","snapshot_observed_at":"2026-08-16T15:38:31.796935Z","submitted_at":"2023-04-22T12:26:24Z","title":"Large Language Models are Few-Shot Summarizers: Multi-Intent Comment Generation via In-Context Learning","version":3},"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":"2304.11384","snapshot_observed_at":"2026-08-16T10:30:34.882900Z","title":"arXiv preprint arXiv:2304.11384 (2023)","venue":null,"work_id":null,"year":2023},"citing_paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation","version":1},"reference_index":2023,"source":"pdf_text","source_observed_at":"2026-08-16T10:30:34.882900Z"},"links":{"cited_paper":"/paper/2304.11384","citing_paper":"/paper/2504.18050"},"observation_digest":"sha256:1164bd04f7fc7ffb80b8b10ab093da69939d8740802bcb0ed2e2a19d20c83291","observation_id":"55aac7e0-a5c4-4f79-8f34-6d1ae0a40abb","resolution":{"observed_at":"2026-08-16T10:30:34.882900Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}}],"paper":{"arxiv_id":"2504.18050","last_updated":"2025-04-25T03:39:19Z","latest_version":1,"primary_category":"cs.SE","snapshot_observed_at":"2026-08-16T10:23:30.062165Z","submitted_at":"2025-04-25T03:39:19Z","title":"Validating Network Protocol Parsers with Traceable RFC Document Interpretation"},"reference_resolution":{"displayed":58,"state_counts":{"malformed_identifier":2,"metadata_mismatch":1,"parse_uncertain":0,"unresolved":45,"verified_exact":5,"verified_fuzzy":5},"total_outbound_references":58},"refusal":"A citation records a reference. It does not transfer a finding from one paper to another.","schema":"pith.paper-citation-record.v1","standing_sources":[{"observed_at":"2026-08-17T06:30:58.91139+00:00","source":"crossref"},{"observed_at":"2026-08-17T06:30:54.323127+00:00","source":"retraction_watch"}],"thesis":"As of 17 August 2026, this Paper Citation Record lists 58 of 58 outbound references and 1 inbound Pith citation observation for arXiv:2504.18050."}