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


a method to negotiate the

authenticate itself before allowing network-layer protocol packets

to be exchanged.

This Configuration Option provides a method to negotiate the use

of a specific protocol for authentication. By default,

authentication is not required.

An implementation MUST NOT include multiple Authentication-

Protocol Configuration Options in its Configure-Request packets.

Instead, it SHOULD attempt to configure the most desirable

protocol first. If that protocol is Configure-Nak'd, then the

implementation SHOULD attempt the next most desirable protocol in

the next Configure-Request.

The implementation sending the Configure-Request is indicating

that it expects authentication from its peer. If an

implementation sends a Configure-Ack, then it is agreeing to

authenticate with the specified protocol. An implementation

receiving a Configure-Ack SHOULD expect the peer to authenticate

with the acknowledged protocol.

There is no requirement that authentication be full-duplex or that

the same protocol be used in both directions. It is perfectly

acceptable for different protocols to be used in each direction.

This will, of course, depend on the specific protocols negotiated.

A summary of the Authentication-Protocol Configuration Option 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


| Type | Length | Authentication-Protocol |


| Data ...




Simpson [Page 42]

RFC 1661 Point-to-Point Protocol July 1994


>= 4


The Authentication-Protocol field is two octets, and indicates the

authentication protocol desired. Values for this field are always

the same as the PPP Protocol field values for that same

authentication protocol.

Up-to-date values of the Authentication-Protocol field are

specified in the most recent "Assigned Numbers" RFC [2].

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