idnits 2.17.1 draft-cohen-fp-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 91 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** There are 3 instances of too long lines in the document, the longest one being 10 characters in excess of 72. ** There are 15 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 8 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Fred Cohen 2 Internet Engineering Task Force 4 FP 5 draft-cohen-fp-00.txt 7 Status of this Memo 9 This document is an Internet-Draft and is subject to all provisions of 10 Section 10 of RFC2026. 12 Internet-Drafts are working documents of the Internet Engineering Task 13 Force (IETF), its areas, and its working groups. Note that other groups 14 may also distribute working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six months 17 and may be updated, replaced, or obsoleted by other documents at any 18 time. It is inappropriate to use Internet- Drafts as reference material 19 or to cite them other than as "work in progress." 21 The list of current Internet-Drafts can be accessed at 22 http://www.ietf.org/1id-abstracts.html 24 The list of Internet-Draft Shadow Directories can be accessed at 25 http://www.ietf.org/shadow.html 27 Abstract 29 This is a new protocol now being used to communicate within a local area 30 network. It is called "FP" (rumored to stand for Frame Protocol) and is 31 intended for use by communicating parties on the same LAN segment. 33 "FP" (rumored to stand for Frame Protocol) uses an Ethernet or similar 34 LAN technology to communicate short burst traffic between communicating 35 parties. 37 Ethernet byte sequences starting with a first octet (byte) of 'FC' are 38 used in an Ethernet-level protocol for communication between computers 39 on the same LAN segment. Subprotocols are defined by the second octet 40 (byte). Current subcodes are: 42 00 Reserved - never to be used 43 01 Start of session 44 02 Data in session 45 03 End of session 47 Further codes are anticipated over time. 49 FP Ethernet packet: 50 +----+----+----+----+- 51 | FC | Op | Content... 52 +----+----+----+----+- 54 FP Ethernet Start of session packet: 55 +----+----+----+----+----+----+----+----+----+----+----+----+----+----+ 56 | FC | 01 | Session Idendity | Timestamp | 57 +----+----+----+----+----+----+----+----+----+----+----+----+----+----+ 59 FP Ethernet Data in session packet: 61 +----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+ 62 | FC | 02 | Session Idendity | Timestamp |Content... 63 +----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+ 65 FP Ethernet End of session packet: 66 +----+----+----+----+----+----+----+----+----+----+----+----+----+----+ 67 | FC | 03 | Session Idendity | Timestamp | 68 +----+----+----+----+----+----+----+----+----+----+----+----+----+----+ 70 Contact Information: 72 Fred Cohen 73 fc@all.net