draft-ietf-dna-link-information-05.txt   draft-ietf-dna-link-information-06.txt 
Network Working Group S. Krishnan, Ed. Network Working Group S. Krishnan, Ed.
Internet-Draft Ericsson Research Internet-Draft Ericsson Research
Expires: May 9, 2007 N. Montavont Intended status: Informational N. Montavont
LSIIT - University Louis Pasteur Expires: August 19, 2007 LSIIT - University Louis Pasteur
E. Njedjou E. Njedjou
France Telecom France Telecom
S. Veerepalli S. Veerepalli
Qualcomm Qualcomm
A. Yegin, Ed. A. Yegin, Ed.
Samsung AIT Samsung AIT
November 5, 2006 February 15, 2007
Link-layer Event Notifications for Detecting Network Attachments Link-layer Event Notifications for Detecting Network Attachments
draft-ietf-dna-link-information-05 draft-ietf-dna-link-information-06
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 41 skipping to change at page 1, line 41
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 9, 2007. This Internet-Draft will expire on August 19, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
Certain network access technologies are capable of providing various Certain network access technologies are capable of providing various
types of link-layer status information to IP. Link-layer event types of link-layer status information to IP. Link-layer event
notifications can help IP expeditiously detect configuration changes. notifications can help IP expeditiously detect configuration changes.
This document provides a non-exhaustive catalogue of information This document provides a non-exhaustive catalogue of information
available from well-known access technologies. available from well-known access technologies.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Requirements notation . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Link-Layer Event Notifications . . . . . . . . . . . . . . . . 5 3. Link-Layer Event Notifications . . . . . . . . . . . . . . . . 6
2.1 GPRS/3GPP . . . . . . . . . . . . . . . . . . . . . . . . 6 3.1. GPRS/3GPP . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 cdma2000/3GPP2 . . . . . . . . . . . . . . . . . . . . . . 7 3.2. cdma2000/3GPP2 . . . . . . . . . . . . . . . . . . . . . . 8
2.3 IEEE 802.11/WiFi . . . . . . . . . . . . . . . . . . . . . 8 3.3. IEEE 802.11/WiFi . . . . . . . . . . . . . . . . . . . . . 9
2.4 IEEE 802.3 CSMA/CD . . . . . . . . . . . . . . . . . . . . 9 3.4. IEEE 802.3 CSMA/CD . . . . . . . . . . . . . . . . . . . . 10
2.4.1 Link Integrity Tests in 802.3 Networks . . . . . . . . 10 3.4.1. Link Integrity Tests in 802.3 Networks . . . . . . . . 11
2.4.2 IEEE 802.1D Bridging and Its Effects on Link-layer 3.4.2. IEEE 802.1D Bridging and Its Effects on Link-layer
Event Notifications . . . . . . . . . . . . . . . . . 10 Event Notifications . . . . . . . . . . . . . . . . . 11
2.4.3 802.1AB Link-Layer Discovery Protocol . . . . . . . . 12 3.4.3. 802.1AB Link-Layer Discovery Protocol . . . . . . . . 13
2.4.4 Summary . . . . . . . . . . . . . . . . . . . . . . . 13 3.4.4. Other heuristics . . . . . . . . . . . . . . . . . . . 13
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 3.4.5. Summary . . . . . . . . . . . . . . . . . . . . . . . 13
4. Security Considerations . . . . . . . . . . . . . . . . . . . 15 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 16 5. Security Considerations . . . . . . . . . . . . . . . . . . . 16
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 17
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18
7.1 Normative References . . . . . . . . . . . . . . . . . . . 18 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.2 Informative References . . . . . . . . . . . . . . . . . . 19 8.1. Normative References . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 20 8.2. Informative References . . . . . . . . . . . . . . . . . . 21
A. Change History . . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
Intellectual Property and Copyright Statements . . . . . . . . 23 Intellectual Property and Copyright Statements . . . . . . . . . . 24
1. Introduction 1. Introduction
It is not an uncommon occurrence for a node to change its point-of It is not an uncommon occurrence for a node to change its point of
attachment to the network. This can happen due to mobile usage attachment to the network. This can happen due to mobile usage
(e.g., a mobile phone moving among base stations) or nomadic usage (e.g., a mobile phone moving among base stations) or nomadic usage
(e.g., road-warrior case). (e.g., road-warrior case).
A node changing its point-of attachment to the network may end up A node changing its point of attachment to the network may end up
changing its IP subnet and therefore require re-configuration of IP- changing its IP subnet and therefore require re-configuration of IP-
layer parameters, such as IP address, default gateway information, layer parameters, such as IP address, default gateway information,
and DNS server address. Detecting the subnet change can usually use and DNS server address. Detecting the subnet change can usually use
network-layer indications (such as a change in the advertised network-layer indications (such as a change in the advertised
prefixes for IPv6). But generally reliance on such indications does prefixes for IPv6). But such indications may not be always available
not yield rapid detection, since these indications are not readily (e.g. DNAv6) to the node upon changing its point of attachment.
available upon node changing its point of attachment.
Additional information can be conveyed along with the event, such as Additional information can be conveyed along with the event, such as
the identifier of the network attachment point (e.g., IEEE 802.11 the identifier of the network attachment point (e.g., IEEE 802.11
BSSID and SSID), or network-layer configuration parameters obtained BSSID and SSID), or network-layer configuration parameters obtained
via the link-layer attachment process if available. It is envisaged via the link-layer attachment process if available. It is envisaged
that such event notifications can in certain circumstances be used to that such event notifications can in certain circumstances be used to
expedite the inter-subnet movement detection and reconfiguration expedite the inter-subnet movement detection and reconfiguration
process. For example, the notification indicating that the node has process. For example, the notification indicating that the node has
established a new link-layer connection MAY be used for immediately established a new link-layer connection may be used for immediately
probing the network for a possible configuration change. In the probing the network for a possible configuration change. In the
absence of such a notification from the link-layer, IP has to wait absence of such a notification from the link layer, IP has to wait
for indications that are not immediately available, such as receipt for indications that are not immediately available, such as receipt
of next scheduled router advertisement, unreachability of the default of next scheduled router advertisement, unreachability of the default
gateway, etc. gateway, etc.
It should be noted that a link-layer event notification does not It should be noted that a link-layer event notification does not
always translate into a subnet change. Even if the node has torn always translate into a subnet change. Even if the node has torn
down a link-layer connection with one attachment point and down a link-layer connection with one attachment point and
established a new connection with another, it may still be attached established a new connection with another, it may still be attached
to the same IP subnet. For example, several IEEE 802.11 access to the same IP subnet. For example, several IEEE 802.11 access
points can be attached to the same IP subnet. Moving among these points can be attached to the same IP subnet. Moving among these
skipping to change at page 4, line 9 skipping to change at page 4, line 7
events and notifications in various architectures. While this events and notifications in various architectures. While this
document mentions the utility of this information for detecting document mentions the utility of this information for detecting
change of subnet (or, detecting network attachment - DNA), the change of subnet (or, detecting network attachment - DNA), the
detailed usage is left to other documents, namely DNA solution detailed usage is left to other documents, namely DNA solution
specifications. specifications.
The document limits itself to the minimum set of information that is The document limits itself to the minimum set of information that is
necessary for solving the DNA problem [RFC4135]. A broader set of necessary for solving the DNA problem [RFC4135]. A broader set of
information (e.g., signal strength, packet loss, etc.) and events information (e.g., signal strength, packet loss, etc.) and events
(e.g. link down) may be used for other problem spaces, such as (e.g. link down) may be used for other problem spaces, such as
anticipation-based Mobile IP fast handovers [I-D.ietf-mobileip- anticipation-based Mobile IP fast handovers
lowlatency-handoffs-v4] [I-D.ietf-mobileip-lowlatency-handoffs-v4],
[I-D.ietf-mipshop-fast-mipv6]. Separate documents that are backward- [I-D.ietf-mipshop-fast-mipv6] etc.
compatible with this one can be generated to discuss further
enhancements.
These event notifications are considered with hosts in mind, although These event notifications are considered with hosts in mind, although
they may also be available on the network side (e.g., on the access they may also be available on the network side (e.g., on the access
points and routers). An API or protocol-based standard interface may points and routers). An API or protocol-based standard interface may
be defined between the link-layer and IP for conveying this be defined between the link layer and IP for conveying this
information. That activity is beyond the scope of this document. information. That activity is beyond the scope of this document.
1.1 Requirements notation 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", Link: is a communication facility or medium over which network nodes
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this can communicate. Each link is associated with a minimum of two
document are to be interpreted as described in [RFC2119]. endpoints. An "attachment point" is the link endpoint on the link to
which the node is currently connected, such as an access point, a
base station, or a wired switch.
2. Link-Layer Event Notifications Link up: is an event provided by the link layer that signifies a
state change associated with the interface becoming capable of
communicating data packets. This event is associated with a link-
layer connection between the node and an attachment point.
BSSID: Basic Service Set Identification
DNA: Detecting Network Attachment
GPRS: GSM Packet Radio System
PDP: Packet Data Protocol
SSID: Service Set Identifier
3. Link-Layer Event Notifications
Link-layer event notifications are considered to be one of the inputs Link-layer event notifications are considered to be one of the inputs
to the DNA process. A DNA process is likely to take other inputs to the DNA process. A DNA process is likely to take other inputs
(e.g., presence of advertised prefixes, reachability of default (e.g., presence of advertised prefixes, reachability of default
gateways) before determining whether IP-layer configuration must be gateways) before determining whether IP-layer configuration must be
updated. It is expected that the DNA process can take advantage of updated. It is expected that the DNA process can take advantage of
link-layer notifications when they are made available to IP. While link-layer notifications when they are made available to IP. While
by itself a link-layer notification may not constitute all the input by itself a link-layer notification may not constitute all the input
DNA needs, it can at least be useful for prompting the DNA process to DNA needs, it can at least be useful for prompting the DNA process to
collect further information (i.e., other inputs to the process). For collect further information (i.e., other inputs to the process). For
example, the node may send a router solicitation as soon as it learns example, the node may send a router solicitation as soon as it learns
that a new link-layer connection is established. that a new link-layer connection is established.
The link-layer event that is considered most useful to DNA process is The link-layer event that is considered most useful to DNA process is
the link up event. The associated notifications can be provided to the link up event. The associated notifications can be provided to
the IP-layer after the event concludes successfully. The link up the IP-layer after the event concludes successfully. The link up
events and notifications are associated with a network interface on events and notifications are associated with a network interface on
the node. The IP module may receive simultaneous independent the node. The IP module may receive simultaneous independent
notifications from each one of the network interfaces on the node. notifications from each one of the network interfaces on the node.
"Link" is a communication facility or medium over which network nodes The actual event is managed by the link layer of the node through
can communicate. Each link is associated with a minimum of two
endpoints. An "attachment point" is the link endpoint on the link to
which the node is currently connected, such as an access point, a
base station, or a wired switch.
"Link up" is an event provided by the link-layer that signifies a
state change associated with the interface becoming capable of
communicating data packets. This event is associated with a link-
layer connection between the node and an attachment point.
The actual event is managed by the link-layer of the node through
execution of link-layer protocols and mechanisms. Once the event execution of link-layer protocols and mechanisms. Once the event
successfully completes within the link-layer, its notification MUST successfully completes within the link layer, its notification must
be delivered to the IP-layer. By the time the notification is be delivered to the IP-layer. By the time the notification is
delivered, the link-layer of the node MUST be ready to accept IP delivered, the link layer of the node must be ready to accept IP
packets from the IP and the physical-layers. Each time an interface packets from the IP and the physical-layers. Each time an interface
changes its point of attachment, a link up event SHOULD be generated. changes its point of attachment, a link up event should be generated.
There is a non-deterministic usage of link up notification to There is a non-deterministic usage of the link up notification to
accomodate implementations that desire to indicate the link is up but accomodate implementations that desire to indicate the link is up but
the data transmission may be blocked in the network (see IEEE 802.3 the data transmission may be blocked in the network (see IEEE 802.3
discussion). A link up notification MAY be generated with an discussion). A link up notification may be generated with an
appropriate attribute (e.g., "risk" indicated by R-flag) to convey appropriate attribute, conveying its non-deterministic nature, to
the event. Alternatively, the link-layer implementation MAY choose convey the event. Alternatively, the link-layer implementation may
to delay the link up notification until the risk conditions cease to choose to delay the link up notification until the risk conditions
exist. cease to exist.
If a link up with the R-flag set was generated, another link up MUST If a non-deterministic link up was generated, another link up must
follow up as soon as the link-layer is capable of generating a follow as soon as the link layer is capable of generating a
deterministic notification. The event attributes MUST indicate deterministic notification. The event attributes may indicate
whether the packets transmitted since the previous notification were whether the packets transmitted since the previous notification were
presumed to be blocked (B-flag) or allowed (A-flag) by the network if presumed to be blocked or allowed by the network, if the link layer
the link-layer could determine the exact conditions. If the link- could determine the exact conditions.
layer cannot make a determination about the fate of these packets, it
MUST generate a link up without any additional indications (no flags The deterministic link up event following a non-deterministic link up
set). event can be treated differently by consumers of the link up event.
e.g. The second link up event need not trigger a confirmation
process, if the first one already did.
A node may have to change its IP-layer configuration even when the A node may have to change its IP-layer configuration even when the
link-layer connection stays the same. An example scenario is the link-layer connection stays the same. An example scenario is the
IPv6 subnet renumbering [RFC2461]. Therefore, there exist cases IPv6 subnet renumbering [RFC2461]. Therefore, there exist cases
where IP-layer configuration may have to change even without the IP- where IP-layer configuration may have to change even without the IP
layer receiving a link up notification. Therefore, a link-layer layer receiving a link up notification. Therefore, a link-layer
notification is not a mandatory indication of a subnet change. notification is not a mandatory indication of a subnet change.
A link up notification may optionally deliver information relating to A link up notification may optionally deliver information relating to
the attachment point. Such auxiliary information may include the attachment point. Such auxiliary information may include the
identity of the attachment point (e.g., base station identifier), or identity of the attachment point (e.g., base station identifier), or
the IP-layer configuration parameters associated with the attached the IP-layer configuration parameters associated with the attached
subnet (e.g., subnet prefix, default gateway address, etc.). While subnet (e.g., subnet prefix, default gateway address, etc.). While
merely knowing that a new link-layer connection is established may merely knowing that a new link-layer connection is established may
prompt DNA process to immediately seek other clues for detecting prompt the DNA process to immediately seek other clues for detecting
network configuration change, auxiliary information may constitute a network configuration change, auxiliary information may constitute
further clues (and even the final answers sometimes). In cases where further clues (and even the final answers sometimes). In cases where
there is a one-to-one mapping between the attachment point there is a one-to-one mapping between the attachment point
identifiers and the IP-layer configurations, learning the former can identifiers and the IP-layer configurations, learning the former can
reveal the latter. Furthermore, IP-layer configuration parameters reveal the latter. Furthermore, IP-layer configuration parameters
obtained during link-layer connection may be exactly what the DNA obtained during the link-layer connection may be exactly what the DNA
process is trying to discover (e.g., IP address configured during PPP process is trying to discover.
link establishment).
The link-layer process leading to a link up event depends on the link The link-layer process leading to a link up event depends on the link
technology. While a link-layer notification MUST always indicate technology. While a link-layer notification must always indicate
that the link up event occurred, the availability and types of that the link up event occurred, the availability and types of
auxiliary information on the attachment point depends on the link- auxiliary information on the attachment point depends on the link-
layer technology as well. The following subsections examine four layer technology as well. The following subsections examine four
link-layer technologies and describe when a link-layer notification link-layer technologies and describe when a link-layer notification
must be generated and what information must be included in it. must be generated and what information must be included in it.
2.1 GPRS/3GPP 3.1. GPRS/3GPP
GSM Packet Radio System (GPRS) provides packet switched data GSM Packet Radio System (GPRS) provides packet switched data
transmission over a cellular network[GPRS][GPRS-LINK]. transmission over a cellular network[GPRS][GPRS-LINK].
The GPRS architecture consists of a Radio Access Network and a packet The GPRS architecture consists of a Radio Access Network and a packet
domain Core Network. domain Core Network.
- The GPRS Radio Access Network is composed of Mobile Terminals (MT), - The GPRS Radio Access Network is composed of Mobile Terminals (MT),
a Base Station Subsystem and Serving GPRS Support Nodes (SGSN). a Base Station Subsystem and Serving GPRS Support Nodes (SGSN).
- An IP Core Network that acts as the transport backbone of user - An IP Core Network that acts as the transport backbone of user
datagrams between SGSNs and Gateway GPRS Support Nodes (GGSN). The datagrams between SGSNs and Gateway GPRS Support Nodes (GGSN). The
GGSN ensures the GPRS IP core network connectivity with external GGSN ensures the GPRS IP core network connectivity with external
networks, such as Internet or Local Area Networks. GGSN acts as the networks, such as the Internet or Local Area Networks. The GGSN acts
default IP gateway for the MT. as the default IP gateway for the MT.
A GPRS MT that wants to establish IP connectivity establishes first a A GPRS MT that wants to establish IP connectivity establishes first a
connection to the GPRS network and one or more PDP Context connection to the GPRS network and one or more PDP Context
associations between the MT and the GGSN. It is only after the PDP associations between the MT and the GGSN. It is only after the PDP
Context has been established, address autoconfiguration and tunneling Context has been established, address autoconfiguration and tunneling
mechanism have taken place that the MT's IP packets can be forwarded mechanism have taken place that the MT's IP packets can be forwarded
to and from its remote IP peers. The aim of PDP Context to and from its remote IP peers. The aim of PDP Context
establishment is also to provide IP-level configuration on top of the establishment is also to provide IP-level configuration on top of the
GPRS link-layer attachment. GPRS link-layer attachment.
Successful establishment of a PDP Context on a GPRS link signifies Successful establishment of a PDP Context on a GPRS link signifies
the availability of IP service to the MT. Therefore, this link-layer the availability of IP service to the MT. Therefore, this link-layer
event MUST generate a link up event notification sent to IP-layer. event must generate a link up event notification sent to the IP
layer.
An MT has the possibility to establish a secondary PDP Context while An MT has the possibility to establish a secondary PDP Context while
re-using the IP configuration acquired from a previously established re-using the IP configuration acquired from a previously established
and active PDP Context. Such a secondary PDP Context does not and active PDP Context. Such a secondary PDP Context does not
provide additional information to IP-layer and only allows another provide additional information to the IP layer and only allows
QoS profile to be used. The activiation of a such secondary PDP another QoS profile to be used. The activation of such a secondary
Context MUST NOT generate another link up event notification. PDP context does not usually generate a link up event since it does
However, other additional PDP Context activiations are to be treated not require new IP parameters. However, other additional PDP Context
as indicated earlier. activiations are to be treated as indicated earlier.
With IPv4, the auxiliary information carried along with this With IPv4, the auxiliary information carried along with this
notification MUST be the IPv4 address of the MT which is obtained as notification must be the IPv4 address of the MT which is obtained as
part of the PDP Context. With IPv6, the PDP Context activation part of the PDP Context. With IPv6, the PDP Context activation
response does not come along with a usable IPv6 address. response does not come along with a usable IPv6 address.
Effectively, the IPv6 address received from the GGSN in the PDP Effectively, the IPv6 address received from the GGSN in the PDP
address field of the message does not contain a valid prefix. The MN address field of the message does not contain a valid prefix. The MN
actually only uses the interface-identifier extracted from that field actually only uses the interface-identifier extracted from that field
to form a link-local address, that it uses afterwards to obtain a to form a link-local address, that it uses afterwards to obtain a
valid prefix (e.g., by stateless [RFC2462][GPRS-CN] or stateful valid prefix (e.g., by stateless [RFC2462][GPRS-CN] or stateful
[RFC3315] [GPRS-GSSA] address configuration). Therefore no IPv6- [RFC3315] [GPRS-GSSA] address configuration). Therefore no IPv6-
related auxiliary information is provided to IP-layer. related auxiliary information is provided to the IP layer.
2.2 cdma2000/3GPP2 3.2. cdma2000/3GPP2
cdma2000-based 3GPP2 packet data services provide mobile users wide cdma2000-based 3GPP2 packet data services provide mobile users wide
area high-speed access to packet switched networks [CDMA2K]. Some of area high-speed access to packet switched networks [CDMA2K]. Some of
the major components of the 3GPP2 packet network architecture consist the major components of the 3GPP2 packet network architecture consist
of: of:
- Mobile Station (MS), which allows mobile access to packet-switched - Mobile Station (MS), which allows mobile access to packet-switched
networks over a wireless connection. networks over a wireless connection.
- Radio Access Network, which consists of the Base Station - Radio Access Network, which consists of the Base Station
Transceivers, Base Station Controllers, and the Packet Control Transceivers, Base Station Controllers, and the Packet Control
Function. Function.
- Network Access Server known as the Packet Data Switching Node - Network Access Server known as the Packet Data Switching Node
(PDSN). The PDSN also serves as default IP gateway for the IP MS. (PDSN). The PDSN also serves as default IP gateway for the IP MS.
3GPP2 networks use the Point-to-Point Protocol (PPP [RFC1661]) as the 3GPP2 networks use the Point-to-Point Protocol (PPP [RFC1661]) as the
link-layer protocol between the MS and the PDSN. Before any IP link-layer protocol between the MS and the PDSN. Before any IP
packets may be sent or received, PPP MUST reach the Network-Layer packets may be sent or received, PPP must reach the Network-Layer
Protocol phase, and the IP Control Protocol (IPCP [RFC1332], IPV6CP Protocol phase, and the IP Control Protocol (IPCP [RFC1332], IPV6CP
[RFC2472]) reach the Opened state. When these states are reached in [RFC2472]) reach the Opened state. When these states are reached in
PPP, a link up event notification MUST be delivered to the IP-layer. PPP, a link up event notification must be delivered to the IP layer.
When the PPP is used for 3GPP2 Simple (i.e., non-Mobile) IPv4 When the PPP is used for 3GPP2 Simple (i.e., non-Mobile) IPv4
Service, IPCP enables configuration of IPv4 address on the MS. This Service, IPCP enables configuration of an IPv4 address on the MS.
IPv4 address MUST be provided as the auxiliary information along with This IPv4 address must be provided as the auxiliary information along
the link up notification. IPV6CP used for Simple IPv6 service does with the link up notification. IPV6CP used for Simple IPv6 service
not provide an IPv6 address, but the interface-identifiers for local does not provide an IPv6 address, but the interface identifiers for
and remote end-points of the PPP link. Since there is no standards- local and remote endpoints of the PPP link. Since there is no
mandated correlation between the interface-identifier and other IP- standards-mandated correlation between the interface identifier and
layer configuration parameters, this information is deemed not useful other IP-layer configuration parameters, this information is deemed
for DNA (nevertheless it MAY be provided as auxiliary information for not useful for DNA (nevertheless it may be provided as auxiliary
other uses). information for other uses).
2.3 IEEE 802.11/WiFi 3.3. IEEE 802.11/WiFi
IEEE 802.11-based WiFi networks are the wireless extension of the IEEE 802.11-based WiFi networks are the wireless extension of the
Local Area Networks. Currently available standards are IEEE 802.11b Local Area Networks. Currently available standards are IEEE 802.11b
[IEEE-802.11b], IEEE 802.11g [IEEE-802.11g], and IEEE 802.11a [IEEE- [IEEE-802.11b], IEEE 802.11g [IEEE-802.11g], and IEEE 802.11a
802.11a]. The specifications define both the MAC-layer and the [IEEE-802.11a]. The specifications define both the MAC-layer and the
physical-layer. The MAC layer is the same for all these physical-layer. The MAC layer is the same for all these
technologies. technologies.
Two operating modes are available in the IEEE 802.11 series, either Two operating modes are available in the IEEE 802.11 series, either
infrastructure mode or ad-hoc mode. In infrastructure mode, all infrastructure mode or ad-hoc mode. In infrastructure mode, all
link-layer frames are transmitted to an access point (AP) which then link-layer frames are transmitted to an access point (AP) which then
forwards them to the final receiver. A station (STA) establishes a forwards them to the final receiver. A station (STA) establishes an
IEEE 802.11 association with an AP in order to send and receive IP IEEE 802.11 association with an AP in order to send and receive IP
packets. In a WiFi network that uses Robust Secure Network (RSN packets. In a WiFi network that uses Robust Secure Network (RSN
[IEEE-802.11i]), successful completion of the 4-way handshake between [IEEE-802.11i]), successful completion of the 4-way handshake between
the STA and AP commences the availability of IP service. The link up the STA and AP commences the availability of IP service. The link up
event notification MUST be generated upon this event. In non-RSN- event notification must be generated upon this event. In non-RSN-
based networks, successful association or re-association events on based networks, successful association or re-association events on
the link-layer MUST cause a link up notification sent to the IP- the link layer must cause a link up notification sent to the IP-
layer. layer.
As part of the link establishment, Basic Service Set Identification As part of the link establishment, the STA learns the Basic Service
(BSSID) and Service Set Identifier (SSID) associated with the AP is Set Identification (BSSID) and Service Set Identifier (SSID)
learned by the STA. BSSID is a unique identifier of the AP, usually associated with the AP. The BSSID is a unique identifier of the AP,
set to the MAC address of the wireless interface of the AP. SSID usually set to the MAC address of the wireless interface of the AP.
carries the identifier of the Extended Service Set (ESS) - the set The SSID carries the identifier of the Extended Service Set (ESS) -
composed of APs and associated STAs that share a common distribution the set composed of APs and associated STAs that share a common
system. BSSID and SSID MAY be provided as auxiliary information distribution system. BSSID and SSID may be provided as auxiliary
along with the link up notification. Unfortunately this information information along with the link up notification. Unfortunately this
does not provide a deterministic indication of whether the IP-layer information does not provide a deterministic indication of whether
configuration MUST be changed upon movement. There is no standards- the IP-layer configuration must be changed upon movement. There is
mandated one-to-one relation between the BSSID/SSID pairs and IP no standards-mandated one-to-one relation between the BSSID/SSID
subnets. An AP with a given BSSID can connect a STA to any one of pairs and IP subnets. An AP with a given BSSID can connect a STA to
multiple IP subnets. Similarly, an ESS with the given SSID may span any one of multiple IP subnets. Similarly, an ESS with the given
multiple IP subnets. And finally, the SSIDs are not globally unique. SSID may span multiple IP subnets. And finally, the SSIDs are not
The same SSID may be used by multiple independent ESSs. See Appendix globally unique. The same SSID may be used by multiple independent
A of [DNA4] for a detailed discussion. Nevertheless, BSSID/SSID ESSs. Nevertheless, BSSID/SSID information may be used in a
information may be used in a probabilistic way by the DNA process, probabilistic way by the DNA process, hence it is provided with the
hence it is provided with the link up event notification. link up event notification.
In ad-hoc mode, mobile stations (STA) in range may directly In ad-hoc mode, mobile stations (STA) in range may directly
communicate with each other, i.e., without any infrastructure or communicate with each other, i.e., without any infrastructure or
intermediate hop. The set of communicating STAs is called IBSS for intermediate hop. The set of communicating STAs is called IBSS for
Independent Basic Service Set. In an IBSS, only STA services are Independent Basic Service Set. In an IBSS, only STA services are
available, i.e. authentication, deauthentication, privacy and MSDU available, i.e. authentication, deauthentication, privacy and MSDU
delivery. STAs do not associate with each other, and therefore may delivery. STAs do not associate with each other, and therefore may
exchange data frames in state 2 (authenticated and not associated) or exchange data frames in state 2 (authenticated and not associated) or
even in state 1 (unauthenticated and unassociated) if the even in state 1 (unauthenticated and unassociated) if the
Distribution System is not used (i.e., "To DS" and "From DS" bits are Distribution System is not used (i.e., "To DS" and "From DS" bits are
clear). If authentication is performed, a link up indication can be clear). If authentication is performed, a link up indication can be
generated upon authentication. Concerning the link layer generated upon authentication. Concerning the link layer
identification, both the BSSID (which is a random MAC address chosen identification, both the BSSID (which is a random MAC address chosen
by a STA of the IBSS) and SSID may be used to identify a link, but by a STA of the IBSS) and SSID may be used to identify a link, but
not to make any assumptions on the IP network configuration. not to make any assumptions on the IP network configuration.
2.4 IEEE 802.3 CSMA/CD 3.4. IEEE 802.3 CSMA/CD
IEEE 802.3 CSMA/CD (commonly referred to as Ethernet) is the most IEEE 802.3 CSMA/CD (commonly referred to as Ethernet) is the most
commonly deployed Local Area Network technology in use today. As commonly deployed Local Area Network technology in use today. As
deployed today, it is specified by a physical layer/medium access deployed today, it is specified by a physical layer/medium access
control (MAC) layer specification [IEEE-802.3]. In order to provide control (MAC) layer specification [IEEE-802.3]. In order to provide
connection of different LANs together into a larger network, 802.3 connection of different LANs together into a larger network, 802.3
LANs are often bridged together [IEEE-802.1D]. LANs are often bridged together [IEEE-802.1D].
In this section, the terms 802.3 and Ethernet are used In this section, the terms 802.3 and Ethernet are used
interchangeably. This section describes some issues in providing interchangeably. This section describes some issues in providing
skipping to change at page 10, line 21 skipping to change at page 11, line 14
In order to determine whether the physical medium is ready for frame In order to determine whether the physical medium is ready for frame
transfer, IEEE 802.3 Ethernet specifies its own link monitoring transfer, IEEE 802.3 Ethernet specifies its own link monitoring
mechanism, which is defined for some, but not all classes of media. mechanism, which is defined for some, but not all classes of media.
Where available, this Link Integrity Test operation is used to Where available, this Link Integrity Test operation is used to
identify when packets are able to be received on an Ethernet segment. identify when packets are able to be received on an Ethernet segment.
It is applicable to both wired and optical physical layers, although It is applicable to both wired and optical physical layers, although
details vary between technologies (link pulses in twisted pair details vary between technologies (link pulses in twisted pair
copper, light levels in fibre). copper, light levels in fibre).
2.4.1 Link Integrity Tests in 802.3 Networks 3.4.1. Link Integrity Tests in 802.3 Networks
Link Integrity Tests in 802.3 networks typically occur at initial Link Integrity Tests in 802.3 networks typically occur at initial
physical connection time (for example, at the auto-negotiation physical connection time (for example, at the auto-negotiation
stage), and periodically afterwards. It makes use of physical-layer stage), and periodically afterwards. It makes use of physical-layer
specific operations to determine if a medium is able to support link- specific operations to determine if a medium is able to support link-
layer frames [IEEE-802.3]. layer frames [IEEE-802.3].
The status of the link as determined by the Link Integrity Test is The status of the link as determined by the Link Integrity Test is
stored in the variable 'link_status'. Changes to the value of stored in the variable 'link_status'. Changes to the value of
link_status (for example due to Link Integrity Test failure) will link_status (for example due to Link Integrity Test failure) will
skipping to change at page 10, line 43 skipping to change at page 11, line 36
implemented on an Ethernet device [IEEE-802.3]. implemented on an Ethernet device [IEEE-802.3].
The link_status has possible values of FAIL, READY and OK. When an The link_status has possible values of FAIL, READY and OK. When an
interface is in FAIL state, Link Integrity Tests have failed. Where interface is in FAIL state, Link Integrity Tests have failed. Where
status is READY, the link segment has passed integrity tests, but status is READY, the link segment has passed integrity tests, but
autonegotiation has not completed. OK state indicates that the autonegotiation has not completed. OK state indicates that the
medium is able to send and receive packets. medium is able to send and receive packets.
Upon transition to a particular state the Physical Medium Attachment Upon transition to a particular state the Physical Medium Attachment
subsystems generates a PMA_LINK.indicate(link_status). Indications subsystems generates a PMA_LINK.indicate(link_status). Indications
of OK state MAY be used to generate a link up event notification. of OK state may be used to generate a link up event notification.
This indication do not definitively ensure that packets will be able These indications do not definitively ensure that packets will be
to be received through the bridge domain, though [see the next able to be received through the bridge domain, though [see the next
section]. Such operations are governed by bridging. section]. Such operations are governed by bridging.
2.4.2 IEEE 802.1D Bridging and Its Effects on Link-layer Event 3.4.2. IEEE 802.1D Bridging and Its Effects on Link-layer Event
Notifications Notifications
Ethernet networks commonly consist of LANs joined together by Ethernet networks commonly consist of LANs joined together by
transparent bridges (usually implemented as switches). Transparent transparent bridges (usually implemented as switches). Transparent
bridges require the active topology to be loop free. This is bridges require the active topology to be loop free. This is
achieved through the Spanning Tree Protocol (STP) or the Rapid achieved through the Spanning Tree Protocol (STP) or the Rapid
Spanning Tree Protocol (RSTP). These protocols exchange Bridge Spanning Tree Protocol (RSTP). These protocols exchange Bridge
Protocol Data Units (BPDUs), as defined in [IEEE-802.1D], which leads Protocol Data Units (BPDUs), as defined in [IEEE-802.1D], which leads
to, where required, the blocking of ports (i.e., not forwarding). to, where required, the blocking of ports (i.e., not forwarding).
By default, the spanning tree protocol does not know whether a By default, the spanning tree protocol does not know whether a
particular newly connected piece of Ethernet will cause a loop. particular newly connected piece of Ethernet will cause a loop.
Therefore it will block all traffic from and to newly connected ports Therefore it will block all traffic from and to newly connected ports
with the exception of some unbridged management frames. The STP will with the exception of some unbridged management frames. The STP will
determine if the port can be connected to the network in a loop-free determine if the port can be connected to the network in a loop-free
manner. manner.
For these technologies, even though the link-layer appears available, For these technologies, even though the link layer appears available,
no data packet forwarding will occur until it is determined that the no data packet forwarding will occur until it is determined that the
port can be connected to the network in a loop-free environment. port can be connected to the network in a loop-free environment.
For hosts which are providing indications to upper layer protocols, For hosts which are providing indications to upper layer protocols,
even if the host itself does not implement bridging or STP, packet even if the host itself does not implement bridging or STP, packet
delivery across the network can be affected by the presence of delivery across the network can be affected by the presence of
bridges. bridges.
Where the host is not running STP itself, no explicit indication that A host connected to a bridge port does not receive any explicit
forwarding has begun is sent from a bridge. Therefore, a host may indication that the bridge has started forwarding packets.
not know when STP operations have completed, and when it is safe to Therefore, a host may not know when STP operations have completed,
inform upper layers to transmit packets. and when it is safe to inform upper layers to transmit packets.
Where it is not known that forwarding operations are available, a Where it is not known that forwarding operations are available, a
host SHOULD assume that RSTP or STP is being performed. Hosts MAY host should assume that RSTP or STP is being performed. Hosts may
listen to STP/RSTP and 802.1AB messages to gain further information listen to STP/RSTP and 802.1AB messages to gain further information
about the timing of full connectivity on the link, for example, to about the timing of full connectivity on the link, for example, to
override an existing indication. override an existing indication.
Notably, though, it is not easy for a host to distinguish between Notably, though, it is not easy for a host to distinguish between
Disabled bridge ports and non-bridge ports with no active Disabled bridge ports and non-bridge ports with no active
transmitters on them, as Disabled ports will have no traffic on them, transmitters on them, as Disabled ports will have no traffic on them,
and incur 100% sender loss. and incur 100% sender loss.
If no bridge configuration messages are received within the If no bridge configuration messages are received within the
Bridge_Max_Age interval (default 20s), then it is likely that there Bridge_Max_Age interval (default 20s), then it is likely that there
is no visible bridge whose port is enabled for bridging (S8.4.5 of is no visible bridge whose port is enabled for bridging (S8.4.5 of
[IEEE-802.1D]), since at least two BPDU hello messages would have [IEEE-802.1D]), since at least two BPDU hello messages would have
been lost. Upon this timeout, a link up notification MUST be been lost. Upon this timeout, a link up notification must be
generated, if one has not been already. generated, if one has not been already.
If a BPDU is received, and the adjacent bridge is running the If a BPDU is received, and the adjacent bridge is running the
original Spanning Tree Protocol, then a host cannot successfully send original Spanning Tree Protocol, then a host cannot successfully send
packets until at least twice the ForwardDelay value in the received packets until at least twice the ForwardDelay value in the received
BPDU has elapsed. After this time, a link up notification MUST be BPDU has elapsed. After this time, a link up notification must be
generated. If the previous link up notification had the R-flag set, generated. If the previous link up notification was non-
then the B-flag) MUST be set in this notification. The B-flag deterministic, then this notification includes an attribute
signifies that the packets sent within the prior interval were lost. signifying that the packets sent within the prior interval were lost.
If the bridge is identified as performing Rapid Spanning Tree If the bridge is identified as performing Rapid Spanning Tree
Protocol (RSTP), it instead waits Bridge_Max_Age after packet Protocol (RSTP), it instead waits Bridge_Max_Age after packet
reception (advertised in the BPDU's Max Age field), before reception (advertised in the BPDU's Max Age field), before
forwarding. For ports which are known to be point-to-point through forwarding. For ports which are known to be point-to-point through
autonegotiation, this delay is abbreviated to 3 seconds after autonegotiation, this delay is abbreviated to 3 seconds after
autonegotiation completes [IEEE-802.1D]. autonegotiation completes [IEEE-802.1D].
2.4.3 802.1AB Link-Layer Discovery Protocol 3.4.3. 802.1AB Link-Layer Discovery Protocol
The recently defined 802.1AB Link-Layer Discovery Protocol (LLDP) The recently defined 802.1AB Link-Layer Discovery Protocol (LLDP)
provides information to devices which are directly adjacent to them provides information to devices which are directly adjacent to them
on the local LAN [IEEE-802.1ab]. on the local LAN [IEEE-802.1ab].
LLDP sends information periodically, and at link status change time LLDP sends information periodically, and at link status change time
to indicate the configuration parameters of the device. Devices may to indicate the configuration parameters of the device. Devices may
either send or receive these messages, or both. either send or receive these messages, or both.
The LLDP message may contain a System Capabilities TLV, which The LLDP message may contain a System Capabilities TLV, which
describes the MAC and IP layer functions which a device is currently describes the MAC and IP layer functions which a device is currently
using. Where a host receives the Systems Capabilities TLV which using. Where a host receives the Systems Capabilities TLV which
indicate that no Bridging or Repeating is occurring on the LLDP indicate that no Bridging is occurring on the LLDP transmitter, no
transmitter, then no delays for STP calculation will be applied to delays for STP calculation will be applied to packets sent through
packets sent through this transmitter, if the host does not perform this transmitter. This would allow the generation of a link up
STP itself. This would allow the generation of a link up
notification. notification.
Additionally, if a host receives a Systems Capabilities TLV which Additionally, if a host receives a Systems Capabilities TLV which
indicates that the LLDP transmitter is a bridge, the host's indicates that the LLDP transmitter is a bridge, the host's
advertisement that it is an (end-host) Station-Only, may tell the advertisement that it is an (end-host) Station-Only, may tell the
bridge not to run STP, and immediately allow forwarding. bridge not to run STP, and immediately allow forwarding.
Proprietary extensions may also indicate that data forwarding is Proprietary extensions may also indicate that data forwarding is
already available on such a port. Discussion of such optimizations already available on such a port. Discussion of such optimizations
is out-of-scope for this document. is out of scope for this document.
Due to the protocol's newness and lack of deployment, it is unclear Because the protocol is new and not widely deployed, it is unclear
how this protocol will eventually affect DNA in IPv4 or IPv6 how this protocol will eventually affect DNA in IPv4 or IPv6
networks. networks.
2.4.4 Summary 3.4.4. Other heuristics
In 802.3 networks, NICs are often capable of returning a speed and
duplex indication to the host, and that changes in these
characteristics may indicate a connection to a new layer 2 network.
3.4.5. Summary
Link-Layer indications in Ethernet-like networks are complicated by Link-Layer indications in Ethernet-like networks are complicated by
additional unadvertised delays due to Spanning Tree calculations. additional unadvertised delays due to Spanning Tree calculations.
This may cause re-indication (link up with A-flag) or retraction This may cause re-indication or retraction of indications previously
(link up with B-flag) of indications previously sent to upper layer sent to upper layer protocols.
protocols.
3. IANA Considerations 4. IANA Considerations
This document has no actions for IANA. This document has no actions for IANA.
4. Security Considerations 5. Security Considerations
Attackers may spoof various indications at the link-layer, or Attackers may spoof various indications at the link layer, or
manipulate the physical medium directly in an effort to confuse the manipulate the physical medium directly in an effort to confuse the
host about the state of the link-layer. For instance, attackers may host about the state of the link layer. For instance, attackers may
spoof error messages or disturb the wireless medium to cause the host spoof error messages or disturb the wireless medium to cause the host
to move its connection elsewhere or to even disconnect. Attackers to move its connection elsewhere or to even disconnect. Attackers
may also spoof information to make the host believe it has a may also spoof information to make the host believe it has a
connection when, in reality, it does not. connection when, in reality, it does not. In addition, wireless
networks such as 802.11 are susceptible to an attack called the "Evil
These attacks may cause use of non-preferred networks or even denial- Twin" attack where an attacker sets up an Access Point with the same
of-service. SSID as a legitimate one and gets the use to connect to the fake
access point instead of the real one. These attacks may cause use of
non-preferred networks or even denial of service.
This specification does not provide any protection of its own for the This specification does not provide any protection of its own for the
the indications from the lower layers. But the vulnerabilities can indications from the lower layers. But the vulnerabilities can be
be mitigated through the use of techniques in other parts of the mitigated through the use of techniques in other parts of the
protocol stack. In particular, it is RECOMMENDED that protocol stack. In particular, it is recommended that
authentication, replay and integrity protection of link-layer authentication, replay and integrity protection of link-layer
management messages is enabled when available. Additionally, the management messages is enabled when available. e.g. The IEEE 802.1ae
protocol stack may also use some network layer mechanisms to achieve standard [IEEE-802.1ae] defines such mechanisms for IEEE 802
partial protection. For instance, SEND [RFC 3971] could be used to compliant MAC layers. Additionally, the protocol stack may also use
confirm secure reachability with a router. However, network layer some network layer mechanisms to achieve partial protection. For
mechanisms are unable to deal with all problems, such as with instance, SEND [RFC3971] could be used to confirm secure reachability
insecure lower layer notifications that lead to the link not with a router. However, network layer mechanisms are unable to deal
functioning properly with all problems, such as with insecure lower layer notifications
that lead to the link not functioning properly.
5. Contributors 6. Contributors
In addition to the people listed in the author list, text for the In addition to the people listed in the author list, text for the
specific link-layer technologies covered by this document was specific link-layer technologies covered by this document was
contributed by Thomas Noel (IEEE 802.11b), and Greg Daley (IEEE contributed by Thomas Noel (IEEE 802.11b), and Greg Daley (IEEE
802.3). The authors would like to thank them for their efforts in 802.3). The authors would like to thank them for their efforts in
bringing this document to fruition. bringing this document to fruition.
6. Acknowledgements 7. Acknowledgements
The authors would like to acknowledge Bernard Aboba, Sanjeev Athalye, The authors would like to acknowledge Bernard Aboba, Sanjeev Athalye,
JinHyeock Choi, John Loughney, Pekka Nikander, Brett Pentland, Tom JinHyeock Choi, John Loughney, Pekka Nikander, Brett Pentland, Tom
Petch, Dan Romascanu, Pekka Savola, and Muhammad Mukarram bin Tariq Petch, Dan Romascanu, Pekka Savola, Steve Bellovin, Thomas Narten,
for their useful comments and suggestions. Matt Mathis, Alfred Hoenes and Muhammad Mukarram bin Tariq for their
useful comments and suggestions.
7. References 8. References
7.1 Normative References 8.1. Normative References
[CDMA2K] "IS-835 - cdma2000 Wireless IP Network Standard", . [CDMA2K] "IS-835 - cdma2000 Wireless IP Network Standard", .
[GPRS] "Digital cellular telecommunications system (Phase 2+); [GPRS] "Digital cellular telecommunications system (Phase 2+);
General Packet Radio Service (GPRS) Service description; General Packet Radio Service (GPRS) Service description;
Stage 2", 3GPP 3GPP TS 03.60 version 7.9.0 Release 98. Stage 2", 3GPP TS 03.60 version 7.9.0 Release 98.
[GPRS-LINK] [GPRS-LINK]
"Digital cellular telecommunications system (Phase 2+); "Digital cellular telecommunications system (Phase 2+);
Radio subsystem link control", 3GPP GSM 03.05 version Radio subsystem link control", 3GPP GSM 03.05 version
7.0.0 Release 98. 7.0.0 Release 98.
[IEEE-802.11a] [IEEE-802.11a]
Institute of Electrical and Electronics Engineers, "IEEE Institute of Electrical and Electronics Engineers, "IEEE
Std 802.11a-1999, supplement to IEEE Std 802.11-1999, Part Std 802.11a-1999, supplement to IEEE Std 802.11-1999, Part
11: Wireless MAN Medium Access Control (MAC) and Physical 11: Wireless MAN Medium Access Control (MAC) and Physical
skipping to change at page 19, line 8 skipping to change at page 20, line 8
"Supplement to STANDARD FOR Telecommunications and "Supplement to STANDARD FOR Telecommunications and
Information Exchange between Systems - LAN/MAN Specific Information Exchange between Systems - LAN/MAN Specific
Requirements - Part 11: Wireless Medium Access Control Requirements - Part 11: Wireless Medium Access Control
(MAC) and physical layer (PHY) specifications: (MAC) and physical layer (PHY) specifications:
Specification for Enhanced Security", IEEE IEEE 802.11i, Specification for Enhanced Security", IEEE IEEE 802.11i,
December 2004. December 2004.
[IEEE-802.1D] [IEEE-802.1D]
Institute of Electrical and Electronics Engineers, "IEEE Institute of Electrical and Electronics Engineers, "IEEE
standard for local and metropolitan area networks - common standard for local and metropolitan area networks - common
specific ations - Media access control (MAC) Bridges", specifications - Media access control (MAC) Bridges", ISO/
ISO/IEC IEEE Std 802.1D, 2004. IEC IEEE Std 802.1D, 2004.
[IEEE-802.1ab] [IEEE-802.1ab]
Institute of Electrical and Electronics Engineers, "Draft Institute of Electrical and Electronics Engineers, "Draft
Standard for Local and Metropolitan Networks: Station and Standard for Local and Metropolitan Networks: Station and
Media Access Control Connectivity Discovery (Draft 13)", Media Access Control Connectivity Discovery (Draft 13)",
IEEE draft Std 802.1AB, 2004. IEEE draft Std 802.1AB, 2004.
[IEEE-802.1ae]
Institute of Electrical and Electronics Engineers, "IEEE
Std 802.1AE, Local and Metropolitan Area Networks - Media
Access Control (MAC) Security", IEEE Standard 802.1ae,
June 2006.
[IEEE-802.3] [IEEE-802.3]
Institute of Electrical and Electronics Engineers, "IEEE Institute of Electrical and Electronics Engineers, "IEEE
standard for local and metropolitan area networks - standard for local and metropolitan area networks -
Specific Require ments, Part 3: Carrier Sense Multiple Specific Require ments, Part 3: Carrier Sense Multiple
Access with Collision Detection (CSMA/CD) Access Method Access with Collision Detection (CSMA/CD) Access Method
and Physical Layer Specifications", ISO/IEC IEEE and Physical Layer Specifications", ISO/IEC IEEE
Std 802.3, 2002. Std 802.3, 2002.
[RFC1332] McGregor, G., "The PPP Internet Protocol Control Protocol [RFC1332] McGregor, G., "The PPP Internet Protocol Control Protocol
(IPCP)", RFC 1332, May 1992. (IPCP)", RFC 1332, May 1992.
[RFC1661] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51, [RFC1661] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51,
RFC 1661, July 1994. RFC 1661, July 1994.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2462] Thomson, S. and T. Narten, "IPv6 Stateless Address [RFC2462] Thomson, S. and T. Narten, "IPv6 Stateless Address
Autoconfiguration", RFC 2462, December 1998. Autoconfiguration", RFC 2462, December 1998.
[RFC2472] Haskin, D. and E. Allen, "IP Version 6 over PPP", [RFC2472] Haskin, D. and E. Allen, "IP Version 6 over PPP",
RFC 2472, December 1998. RFC 2472, December 1998.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC3971] Arkko, J., Kempf, J., Zill, B., and P. Nikander, "SEcure
Neighbor Discovery (SEND)", RFC 3971, March 2005.
[RFC4135] Choi, JH. and G. Daley, "Goals of Detecting Network [RFC4135] Choi, JH. and G. Daley, "Goals of Detecting Network
Attachment in IPv6", RFC 4135, August 2005. Attachment in IPv6", RFC 4135, August 2005.
7.2 Informative References 8.2. Informative References
[GPRS-CN] "Technical Specification Group Core Network; [GPRS-CN] "Technical Specification Group Core Network;
Internetworking between the Public Land Mobile Network Internetworking between the Public Land Mobile Network
(PLMN) supporting packet based services and Packet Data (PLMN) supporting packet based services and Packet Data
Networks (PDN) (Release 6)", 3GPP 3GPP TS 29.061 version Networks (PDN) (Release 6)", 3GPP TS 29.061 version 6.1.0
6.1.0 2004-06. 2004-06.
[GPRS-GSSA] [GPRS-GSSA]
"Technical Specification Group Services and System Aspect; "Technical Specification Group Services and System Aspect;
General Packet Radio Service (GPRS) Service description; General Packet Radio Service (GPRS) Service description;
Stage 2 (Release 6)", 3GPP 3GPP TS 23.060 version 6.5.0 Stage 2 (Release 6)", 3GPP TS 23.060 version 6.5.0
2004-06. 2004-06.
[I-D.ietf-mipshop-fast-mipv6] [I-D.ietf-mipshop-fast-mipv6]
Koodli, R., "Fast Handovers for Mobile IPv6", Koodli, R., "Fast Handovers for Mobile IPv6",
draft-ietf-mipshop-fast-mipv6-03 (work in progress), draft-ietf-mipshop-fast-mipv6-03 (work in progress),
October 2004. October 2004.
[I-D.ietf-mobileip-lowlatency-handoffs-v4] [I-D.ietf-mobileip-lowlatency-handoffs-v4]
Malki, K., "Low Latency Handoffs in Mobile IPv4", Malki, K., "Low Latency Handoffs in Mobile IPv4",
draft-ietf-mobileip-lowlatency-handoffs-v4-11 (work in draft-ietf-mobileip-lowlatency-handoffs-v4-11 (work in
skipping to change at page 21, line 4 skipping to change at page 22, line 24
Nicolas Montavont Nicolas Montavont
LSIIT - University Louis Pasteur LSIIT - University Louis Pasteur
Pole API, bureau C428 Pole API, bureau C428
Boulevard Sebastien Brant Boulevard Sebastien Brant
Illkirch 67400 Illkirch 67400
France France
Phone: +33 390 244 587 Phone: +33 390 244 587
Email: montavont@dpt-info.u-strasbg.fr Email: montavont@dpt-info.u-strasbg.fr
Eric Njedjou Eric Njedjou
France Telecom France Telecom
4, Rue du Clos Courtel BP 91226 4, Rue du Clos Courtel BP 91226
Cesson Sevigne 35512 Cesson Sevigne 35512
France France
Phone: +33 299124202 Phone: +33 299124202
Email: eric.njedjou@france-telecom.com Email: eric.njedjou@orange-ftgroup.com
Siva Veerepalli Siva Veerepalli
Qualcomm Qualcomm
5775 Morehouse Drive 5775 Morehouse Drive
San Diego, CA 92131 San Diego, CA 92131
USA USA
Phone: +1 858 658 4628 Phone: +1 858 658 4628
Email: sivav@qualcomm.com Email: sivav@qualcomm.com
Alper E. Yegin (editor) Alper E. Yegin (editor)
Samsung Advanced Institute of Technology Samsung Advanced Institute of Technology
75 West Plumeria Drive 75 West Plumeria Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Phone: +1 408 544 5656 Phone: +1 408 544 5656
Email: alper01.yegin@partner.samsung.com Email: alper01.yegin@partner.samsung.com
Appendix A. Change History Full Copyright Statement
The following changes were made on draft version 00:
- IEEE 802.11 ad-hoc mode discussion added.
- IPv6 address configuration over 3GPP networks clarified.
The following changes were made on draft version 01:
- Text for IEEE 802.3 added.
- Multiple 3GPP PDP Contexts scenario clarified.
The following change was made on draft version 02:
- Editorial fixes as suggested by WG last call feedback.
The following change was made on draft version 03: Copyright (C) The IETF Trust (2007).
Link down events were removed since they are not relevant to DNA This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
References updated This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Statement Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 23, line 29 skipping to change at page 24, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 90 change blocks. 
230 lines changed or deleted 226 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/