search

hstenn / ietf-ntp-extended-information-ef

IETF NTP Extension Field proposal: Extended-Information
1 stars 0 forks source link

Remove versioning #2

Open samuelweiler opened 5 years ago

samuelweiler commented 5 years ago

Only ask for a single extension field code point. Otherwise, you're assuming an EF type field structure that differs from 7822 - and this document will get bogged down waiting for an EF cleanup that might or might not ever happen.

(And, if you were to keep the subtyping, the doc needs specific instructions re: what to do with unknown/higher version numbers - and even what to do differently when 0x0009 is used v. 0x0109. (hint: I suspect you intend no difference between 0x0009 and 0x0109 - so just use one of them!))

hstenn commented 5 years ago

Doing what you suggest will cause us to burn thru these and complicate future implementations.

I was not planning to allow 0x0009, unless we did not use 0x0109, saving 0x0109 for the next revision.