host
Click on the red underlined text to get to the source
...
Modern access technologies are faced with several conflicting goals.
It is desirable to connect multiple hosts at a remote site through
the same customer premise access device. It is also a goal to
...
... PPP. In many access technologies, the most
cost effective method to attach multiple hosts to the customer
premise access device, is via Ethernet ...
... PPPoE) provides the ability to connect a network
of hosts over a simple bridging access device to a remote Access
Concentrator. With this model, each host ...
... hosts over a simple bridging access device to a remote Access
Concentrator. With this model, each host utilizes it's own PPP stack
and the user is presented with a familiar user interface ...
... PPP
Session stage. When a Host wishes to initiate a PPPoE session, it
must first perform Discovery to identify the Ethernet ...
... peer-to-peer relationship, Discovery is inherently a client-server
relationship. In the Discovery process, a Host (the client)
discovers an Access Concentrator (the server). Based on the network
topology ...
... discovers an Access Concentrator (the server). Based on the network
topology, there may be more than one Access Concentrator that the
Host can communicate with. The Discovery stage allows the Host to
discover all Access Concentrators and then select one. When
...
... network
topology, there may be more than one Access Concentrator that the
Host can communicate with. The Discovery stage allows the Host to
discover all Access Concentrators and then select one. When
Discovery completes successfully, both the Host ...
... Host to
discover all Access Concentrators and then select one. When
Discovery completes successfully, both the Host and the selected
Access Concentrator have the information they will use to build their
point-to-point connection ...
... established. Once a PPP session is established, both the Host and
the Access Concentrator MUST allocate the resources for a PPP virtual
...
... which together define the PPPoE session uniquely. The steps consist
of the Host broadcasting an Initiation packet, one or more Access
Concentrators sending Offer packets, the Host ...
... Host broadcasting an Initiation packet, one or more Access
Concentrators sending Offer packets, the Host sending a unicast
Session Request packet and the selected Access Concentrator sending a
Confirmation packet. When the Host ...
... Host sending a unicast
Session Request packet and the selected Access Concentrator sending a
Confirmation packet. When the Host receives the Confirmation packet,
it may proceed to the PPP Session ...
... Service-
Name, indicating the service the Host is requesting, and any number
of other TAG types. An entire PADI ...
... DESTINATION_ADDR is the
unicast address of the Host that sent the PADI. The CODE field is
set to 0x07 and the SESSION ...
... Host may receive more than one
PADO. The Host looks through the PADO packets it receives and
chooses one. The choice can be based on the AC ...
... AC-Name or the Services
offered. The Host then sends one PADR packet to the Access
Concentrator that it has chosen. The DESTINATION ...
... Service-
Name, indicating the service the Host is requesting, and any number
of other TAG types.
...
... session. It generates a unique SESSION_ID for the PPPoE
session and replies to the Host with a PADS packet. The
DESTINATION ...
... unicast Ethernet address of the Host
that sent the PADR. The CODE field is set to 0x65 and the SESSION ...
... indicate that a PPPoE session has been terminated. It may be sent by
either the Host or the Access Concentrator. The DESTINATION_ADDR
field is a unicast ...
... It is RECOMMENDED that the Access Concentrator ocassionally send
Echo-Request packets to the Host to determine the state of the
session ...
... state of the
session. Otherwise, if the Host terminates a session without sending
a Terminate-Request packet, the Access Concentrator will not be able
...
...
When LCP terminates, the Host and Access concentrator MUST stop using
that PPPoE session. If the Host ...
... Host and Access concentrator MUST stop using
that PPPoE session. If the Host wishes to start another PPP session ...
...
When a host does not receive a PADO packet within a specified amount
of time, it SHOULD resend it's PADI ...
... of time, it SHOULD resend it's PADI packet and double the waiting
period. This is repeated as many times as desired. If the Host is
waiting to receive a PADS packet, a similar timeout mechanism SHOULD
...
... waiting to receive a PADS packet, a similar timeout mechanism SHOULD
be used, with the Host re-sending the PADR. After a specified number
of retries, the Host ...
... Host re-sending the PADR. After a specified number
of retries, the Host SHOULD then resend a PADI packet.
...
... HMAC [3] over the
Host MAC address using a key known only to the Access > Concentrator.
While the AC ...
...
This TAG is used by a Host to uniquely associate an Access
Concentrator response (PADO or PADS ...
... TAG_VALUE is binary data of any value and
length that the Host chooses. It is not interpreted by the Access
Concentrator. The Host MAY include a Host ...
... length that the Host chooses. It is not interpreted by the Access
Concentrator. The Host MAY include a Host-Uniq TAG in a PADI ...
... Host chooses. It is not interpreted by the Access
Concentrator. The Host MAY include a Host-Uniq TAG in a PADI or
...
... Concentrator MAY include this TAG in a PADO packet. If a Host
receives this TAG, it MUST return the TAG ...
... TAG_VALUE is binary data of any value and
length and is not interpreted by the Host.
0x0105 Vendor-Specific ...
... TAG_VALUE is opaque to both
the Host and the Access Concentrator. If either the Host or
Access Concentrator receives this TAG ...
... opaque to both
the Host and the Access Concentrator. If either the Host or
Access Concentrator receives this TAG they MUST include it
...
... This TAG indicates that the Access Concentrator experienced some
error in performing the Host request. (For example insufficient
resources to create a virtual circuit ...
... | 0xffffffff |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0xffff | Host_mac_addr |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Host ...
... Host_mac_addr |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Host_mac_addr (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ETHER_TYPE = 0x8863 | v = 1 | t = 1 | CODE = 0x09 |
...
... 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Host_mac_addr |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Host ...
... Host_mac_addr |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Host_mac_addr (cont) | Access_Concentrator_mac_addr |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access_Concentrator_mac_addr (cont) |
...
... PPP payload is left to the reader. This is a packet from the Host to
the Access Concentrator.
...
... | Access_Concentrator_mac_addr |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Access_Concentrator_mac_addr(c)| Host_mac_addr |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Host ...
... Host_mac_addr |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Host_mac_addr (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ETHER_TYPE = 0x8864 | v = 1 | t = 1 | CODE = 0x00 |
...