TH71927A - A peer to peer name conversion protocol in wired networks and a data structure of the text format for use in the protocol. - Google Patents

Abstract

DC60 (09/11/60) provides an extensible data structure for protocol messages. Peer-to-peer name conversion The data structure of this message uses a number of fields, each containing text. That should be The first field is the header. A message that contains protocol information and identifies the message type. Each component of Text has a number of different fields. The fields that make up the text are those that define the type of text, the length fields, and the body or body. Message component information One example of invention is The message is at least Ten species are made to perform the appropriate actions in the name conversion protocol. Peer to Peer Name Resolution Protocol, PNRP, the different types of messages are RESOLVE, RESPONSE, SOLICIT, ADVERTISE, REQUEST, FLOOD, INQUIRE, AUTHORITY, ACK, and REPAIR messages -----. -09/11/2017 ------ (OCR) page 1 of the number 1 page summary of invention Provides extensible data structures for protocol messages. Peer-to-Peer Name Conversions The data structure of this text uses a number of fields, each containing text. That should be The first field is the header. A message that contains protocol information and identifies the message type. Each component of Text has a number of different fields. The fields that make up the text are those that define the type of text, the length fields, and the body or body. Message component information One example of invention is The message is at least Ten species were made to perform various actions. Properly in the name conversion protocol. Peer to Peer Name Resolution Protocol, PNRP, the different types of messages are RESOLVE, RESPONSE, SOLICIT, ADVERTISE, REQUEST, FLOOD, INQUIRE, AUTHORITY, ACK, and REPAIR messages ------. ------ Provides extensible data structures for messages in the protocol Convert peer-to-peer names The data structure of this message uses a number of fields, each containing text. That should be The first field is the message header with. Protocol information and indicates the type of message. Each element of the message has a number. The fields that make up these messages are Fields that tell The type of text, the length field, and the body or part of the section. Make up of text In one example of an invention, there are at least ten types of text created. To perform appropriate operations in Peer to Peer Name Resolution Protocol (PNRP) protocols where the message types are RESOLVE, RESPONSE, SOLICIT, ADVERTISE, REQUEST, FLOOD, INQUIRE, AUTHORITY, ACK, and REPAIR

Claims (1)

: DC60 (09/11/60) has introduced a scalable data structure for protocol messages. Peer-to-peer name conversion The data structure of this message uses a number of fields, each containing text. That should be The first field is the header. A message that contains protocol information and identifies the message type. Each component of Text has a number of different fields. The fields that make up the text are those that define the type of text, the length fields, and the body or body. Message component information One example of invention is The message is at least Ten species are made to perform the appropriate actions in the name conversion protocol. Peer to Peer Name Resolution Protocol, PNRP, the different types of messages are RESOLVE, RESPONSE, SOLICIT, ADVERTISE, REQUEST, FLOOD, INQUIRE, AUTHORITY, ACK, and REPAIR messages -----. -09/11/2017 ------ (OCR) page 1 of the number 1 page summary of invention Provides extensible data structures for protocol messages. Peer-to-Peer Name Conversions The data structure of this text uses a number of fields, each containing text. That should be The first field is the header. A message that contains protocol information and identifies the message type. Each component of Text has a number of different fields. The fields that make up the text are those that define the type of text, the length fields, and the body or body. Message component information One example of invention is The message is at least Ten species were made to perform various actions. Properly in the name conversion protocol. Peer to Peer Name Resolution Protocol, PNRP, the different types of messages are RESOLVE, RESPONSE, SOLICIT, ADVERTISE, REQUEST, FLOOD, INQUIRE, AUTHORITY, ACK, and REPAIR messages ------. ------ Provides extensible data structures for messages in the protocol Convert peer-to-peer names The data structure of this message uses a number of fields, each containing text. That should be The first field is the message header with. Protocol information and indicates the type of message. Each element of the message has a number. The fields that make up these messages are Fields that tell The type of text, the length field, and the body or part of the section. Make up of text In one example of an invention is at least ten types of text that have been created. To perform appropriate operations in Peer to Peer Name Resolution Protocol (PNRP) protocols, where the message types are RESOLVE, RESPONSE, SOLICIT, ADVERTISE, REQUEST, FLOOD, INQUIRE, AUTHORITY, ACK, and REPAIR rights. (Section one) which will appear on the advertisement page: ------ 09/11/2017 ------ (OCR) Page 1 of the number 19 pages. 1. A method for generating and sending peer-to-peer protocol messages for messages that They are suitable for use in Peer to Peer Name Resolution Protocol (PNRP) protocols. Creating a scalable data structure that includes the first field consists of sections. The head of the peer-to-peer name conversion protocol (PNRP), which is tagged: