search

IETF-OPSAWG-WG / draft-ietf-opsawg-pcap

PCAP next generation file format specification
Other
264 stars 59 forks source link

Fix wording based on Jim Young's email #36

Closed hadrielk closed 9 years ago

hadrielk commented 9 years ago

See: http://www.winpcap.org/pipermail/pcap-ng-format/2015-September/000320.html

alagoutte commented 9 years ago

Oups... comment after the merge..

Do you have check other RFC about using bytes/octets (There is a rules ?)

hadrielk commented 9 years ago

I don't know if there's a hard and fast rule really, but yes in my experience IETF RFC's generally use the term "octet" for on-the-wire encoding stuff.

-hadriel

On Thu, Sep 3, 2015 at 4:38 PM, Alexis La Goutte notifications@github.com wrote:

Oups... comment after the merge..

Do you have check other RFC about using bytes/octets (There is a rules ?)

— Reply to this email directly or view it on GitHub https://github.com/pcapng/pcapng/pull/36#issuecomment-137567862.

guyharris commented 9 years ago

I don't know if there's a hard and fast rule really, but yes in my experience IETF RFC's generally use the term "octet" for on-the-wire encoding stuff.

For what it's worth, RFC 7322, the RFC Style Guide doesn't say anything about it, and neither does the "Table of decisions on consistent usage in RFCs".