Connected: An Internet Encyclopedia
RFC 1661 - 5.2. Configure-Ack

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1661
Up: 5. LCP Packet Formats
Prev: 5.1. Configure-Request
Next: 5.3. Configure-Nak

### 5.2. Configure-Ack

Description

  If every Configuration Option received in a Configure-Request is recognizable and all values are acceptable, then the implementation MUST transmit a Configure-Ack. The acknowledged Configuration Options MUST NOT be reordered or modified in any way.

  On reception of a Configure-Ack, the Identifier field MUST match that of the last transmitted Configure-Request. Additionally, the Configuration Options in a Configure-Ack MUST exactly match those of the last transmitted Configure-Request. Invalid packets are silently discarded.

A summary of the Configure-Ack 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             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       | Options ...
       +-+-+-+-+

Code

  2 for Configure-Ack.

Identifier

  The Identifier field is a copy of the Identifier field of the Configure-Request which caused this Configure-Ack.

Options

  The Options field is variable in length, and contains the list of zero or more Configuration Options that the sender is acknowledging. All Configuration Options are always acknowledged simultaneously.

Next: 5.3. Configure-Nak

Connected: An Internet Encyclopedia
RFC 1661 - 5.2. Configure-Ack