Feature #4853
closed
Rewrite syntax specifications using IETF ABNF
Added by Junxiao Shi about 5 years ago.
Updated over 4 years ago.
Description
NDN Packet Format spec, along with several other specs, uses a variant of Backus-Naur form to specify its syntaxes. However, it's unclear exactly which variant is followed. This can lead to ambiguity and hinder protocol standardization.
This issue is to choose a BNF variant and rewrite projections accordingly.
Future protocol revisions should be checked against this variant.
- Status changed from New to Resolved
- Assignee set to Junxiao Shi
- Start date deleted (
02/24/2019)
- % Done changed from 0 to 60
If everyone agrees, I can rewrite the whole spec with IETF's ABNF as defined in RFC5234.
As discussed on 20190227 call, I'm to provide a preview of how the documents look like in IETF ABNF. It's now in Change 5280 patchset2. I only updated name.rst data.rst. Other files will be updated after these are reviewed.
- Subject changed from Clarify BNF variant to Rewrite syntax specifications using IETF ABNF
- Description updated (diff)
- % Done changed from 60 to 100
- Estimated time set to 4.50 h
- Status changed from Resolved to Code review
- Status changed from Code review to Closed
What about the syntax specifications in NDNLPv2? Can you convert those too?
What about the syntax specifications in NDNLPv2?
This belongs to #4927.
Also available in: Atom
PDF
Updated by 
Updated by