Well parsing is easier if it is not omitted. It a matter of conditionally expecting end-of-line or not at that point. If it is to be omitted it needs to be documented as being optional in the presentation format. Remember the presentation format is also a interchange format. The parser needs to know if it should error out or not. Different implementations should produce the same presentation format from the same wire input. -- Mark Andrews > On 9 Jul 2019, at 23:49, Ben Schwartz <bemasc@google.com> wrote: > > > >> On Tue, Jul 9, 2019 at 2:21 AM Mark Andrews <marka@isc.org> wrote: >> Introductory Example: The example record >> >> example.com. 2H IN HTTPSSVC 0 0 svc.example.net. >> >> does not match the description of the record (missing last field). It should be: >> >> example.com. 7200 IN HTTPSSVC 0 0 svc.example.net. “” > > I think the idea was to omit the SvcFieldValue field from the text representation in mode 0, where it's unused/disallowed. Do you think that's too inconvenient for zone file parsing code? To me, it seems more natural for humans.
Received on Tuesday, 9 July 2019 21:21:44 UTC