Справочник по сетевым протоколам


RFC1661 - часть 29

6 for Terminate-Ack.


On transmission, the Identifier field MUST be changed whenever the

content of the Data field changes, and whenever a valid reply has

been received for a previous request. For retransmissions, the

Identifier MAY remain unchanged.

On reception, the Identifier field of the Terminate-Request is

copied into the Identifier field of the Terminate-Ack packet.

Simpson [Page 33]

RFC 1661 Point-to-Point Protocol July 1994


The Data field is zero or more octets, and contains uninterpreted

data for use by the sender. The data may consist of any binary

value. The end of the field is indicated by the Length.

5.6. Code-Reject


Reception of a LCP packet with an unknown Code indicates that the

peer is operating with a different version. This MUST be reported

back to the sender of the unknown Code by transmitting a Code-


Upon reception of the Code-Reject of a code which is fundamental

to this version of the protocol, the implementation SHOULD report

the problem and drop the connection, since it is unlikely that the

situation can be rectified automatically.

A summary of the Code-Reject packet format is shown below. The

fields are transmitted from left to right.

0 1 2 3

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1


| Code | Identifier | Length |


| Rejected-Packet ...



7 for Code-Reject.


The Identifier field MUST be changed for each Code-Reject sent.


The Rejected-Packet field contains a copy of the LCP packet which

is being rejected. It begins with the Information field, and does

not include any Data Link Layer headers nor an FCS. The

Rejected-Packet MUST be truncated to comply with the peer's

Simpson [Page 34]

RFC 1661 Point-to-Point Protocol July 1994

established MRU.

5.7. Protocol-Reject


Содержание  Назад  Вперед