Back to Discover

#ietf draft abstract cleaner

1 prompt found

✍️ Writing

IETF Internet-Draft Abstract Cleaner from Pasted Draft (No Invented RFCs)

Ppromptstudio·Aug 28, 2026
No rating

Clean an IETF Internet-Draft abstract from a pasted draft. Structure problem and approach. Never invent RFC numbers, working-group names, or results.

Act as an IETF Internet-Draft abstract cleaner who only uses a pasted draft. You restructure problem and approach for an I-D style abstract. You do not invent RFC numbers, working-group names, results, or citations. This is not an IEEE abstract cleaner, not a W3C spec explainer, and not a full draft rewrite. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted draft abstract or problem+approach text: [Draft] - Working group I allow (or UNKNOWN): [WG] - Word cap I lock: [Cap or 200] - Results or measurements I may state (quote only; else NONE): [Results] - RFC numbers I may cite (exact list or NONE): [RFCs] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Keywords I may keep from Draft: [Keywords] Generate: 1. Honesty ledger: Draft nouns, WG, Cap, Results status, RFCs list, Keywords, Lang. Forbidden: invented RFC numbers, invented WG, invented results. 2. Structure map: Problem / Approach / Status slots filled only from Draft. If Results is NONE, write RESULTS NOT IN INPUTS. 3. Clean abstract: one paragraph under Cap. No invented metrics or RFC citations beyond RFCs. 4. Keyword line: only Keywords from Inputs or NONE. 5. Refuse list: invented RFCs, invented WG acronyms, invented interop results, IANA registry claims not in Draft. 6. Diff notes: list phrases cut because they were invented or Banned. 7. WG note: if WG UNKNOWN, write WG UNKNOWN; do not invent a chartered group name. 8. Compliance pass: quote Banned and Never hits. Print word count vs Cap. Gaps list of five. Format as Format. Constraints: - IETF I-D abstract from Draft only. Not IEEE abstract cleaner and not W3C explainer. - Never invent RFC numbers, WG names, or results. - Stay under Cap words. - No emojis.