One document matched: draft-bertin-hints-params-00.txt
DNA Network Working Group P. Bertin
Internet Draft France Telecom R&D
Document: draft-bertin-hints-params-00.txt T. Noel
Expires: February 2004 N. Montavont
LSIIT
August 2003
Parameters for Link Hints
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
Link hints are going to be standardized to enhance interactions
between link and network layers, allowing a given node to integrate
and efficiently manage one or even several network interfaces.
Parameters conveyed in Link Hints shall provide the necessary
abstraction level to be mapped on several technologies. This
document provides a first list of parameters to be transported in
Link Hints but the way to transport them is out of the scope of
this document.
Two sets of parameters are proposed: the MN set gathers information
available at the Mobile Node whereas the AR set is relevant for the
Access Router side. In each set, parameters are grouped into three
distinct categories: static parameters are related to the hardware
implementation of the interface, configuration parameters are
manageable through interface configuration, status parameters are
highly varying as they provide the current link environment of the
interface.
Table of Contents
Bertin Expires Feb. 2004 [Page 1]
Internet Draft Parameters for Link Hints August 2003
1. Introduction...............................................2
2. Conventions used in this document..........................3
3. Parameters sets and categories.............................3
4. MN parameters set..........................................4
4.1. MN static parameters.......................................4
4.2. MN configuration parameters................................4
4.3. MN link status parameters..................................5
4.3.1. MN interface status parameters.............................5
4.3.2. MN available attachments status............................6
5. AR parameters set..........................................7
5.1. AR static parameters.......................................7
5.2. AR configuration parameters................................7
5.3. AR link status parameters..................................8
5.3.1. AR interface status parameters.............................8
5.3.2. AR attached MN status parameters...........................8
6. Acknowledgements...........................................9
7. References.................................................9
8. Author's Addresses.........................................9
Annex A...........................................................11
1. Introduction
Due to the developpment of new protocols to manage host mobility
[1][2][3][4], Link hints are going to be standardized to enhance
interaction between the link layer and the network layer. This
interaction would allow to optimize network layer operations
(anticipation, choice of the attachment point, new link detectioną).
Link hints are expected to provide notifications when changes occur
in link environment such as the detection of a new point of
attachment, or the start/end of a handover procedure for a MN, or the
new attachment of a MN for an AP. As Mobile Nodes are able to
integrate several link layer interfaces with heterogeneous
technologies, it is expected in the near future that link hints will
provide the necessary framework to efficiently manage several
interfaces in a given Mobile Node. At the network side, a stronger
interaction between layers 2 and 3 would allow a better host mobility
control from the network. Hence, it becomes necessary to define
information elements to be transported in Link Hints and having the
necessary abstraction level to be mapped on several technologies.
The goal of this document is to define a list of link layer
parameters to be transported in link hints. It assumes that link
hints will be implemented in both sides of the link: in the Mobile
Node (MN) between the link layer module and the MN IP layer; in the
network side between the radio Access Point (AP) or Base Station (BS)
and the Access Router (AR). The way hints transport parameters
between the link and the network layer, either in the MN or in the
AR, is out of the scope of this document. This document is intended
to serve as a basis for discussions in the Detecting Network
Bertin Expires Feb. 2004 [Page 2]
Internet Draft Parameters for Link Hints August 2003
Attachment (DNA) group and does not intend to be fully exhaustive. In
particular, it shall be refined accordingly to hints identified for
each link layer technology considered in the working group.
Section 3 introduces notions of parameters sets and categories;
section 4 and 5 defines parameters relevant at the MN and AR side
respectively. In Annex A, tables illustrate examples on how
parameters can be used with different technologies (802.11,
Bluetooth, GPRS).
2. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [1].
3. Parameters sets and categories
Two sets of parameters are defined: the MN set contains parameters
made available by the MN link layer to the MN IP layer; the AR set
comprises parameters made available by the AR radio interface (or AP)
to the AR IP layer.
In each set (MN and AR sets), parameters are classified into three
categories: static parameters, configuration parameters and link
status parameters. Static parameters refer to physical parameters
depending on the interface nature (such as the technology, the
hardware MAC addressą), their values are static. Configuration
parameters are defined through configuration of the link layer (e.g.
network name, security levelą), their values are dynamic but the
frequency of change is very low as it occurs on changes in
configuration that may be managed for example by the network
administrator or the user. Link status parameters characterise the
current communication environment (e.g. available bandwidth, current
load, radio quality measurementą), their values are dynamic and
subject to frequent changes as radio link quality is highly variable
especially in mobile environments.
Link status parameters are also divided into two subsets: the first
subset contains parameters available locally to the link layer
interface whereas the second one contains parameters learnt from the
peer entity (either the MN or the AR/AP) at L2.
Depending on the link layer technology and its configuration, only a
subset of the listed parameters will be available in a given MN or
AR. By default, each parameter must be set to NULL.
Bertin Expires Feb. 2004 [Page 3]
Internet Draft Parameters for Link Hints August 2003
4. MN parameters set
This section lists parameters available at the MN side, grouped by
categories. For examples on how to use these parameters with
different technologies, please refer to annex A.
4.1. MN static parameters
MN Interface type list
The MN interface type indicates the supported link technologies.
The complete set of technologies and the corresponding are to be
defined. It has to be noted that some links support more than
one technology; this is for example the case of dual-mode radio
cards. Hence, a given interface can be able to provide more than
one interface type to the network layer.
MN interface type options
The MN interface type options indicate options implemented for
the given interface type.
MN hardware identifier
The MN hardware identifier identifies uniquely the hardware
module. The used identifier depends on the MN interface type.
4.2. MN configuration parameters
MN current interface type
The MN current interface type indicates the current used type
when several technologies are supported by the same device.
MN default network identifier
The MN default network identifier indicates the MN default
network identifier value to be used for link-layer attachment.
The type of identifier depends on MN interface type.
MN security level
The MN security level parameter identifies the current security
scheme selected through configuration.
MN fragmentation threshold
This parameter indicates the fragmentation threshold of the L2
interface, i.e. the maximum size of MTU in L2 frames.
MN data rate
The MN data rate indicates the configured rate to be used for
the interface. Depending on the Interface type and its
configuration, either one or several data rate can be permitted.
MN maximum transmission power
Bertin Expires Feb. 2004 [Page 4]
Internet Draft Parameters for Link Hints August 2003
The MN maximum transmission power indicates the configured max
transmission power to be applied for the link layer interface.
4.3. MN link status parameters
MN link status parameters are split into two sub-categories:
. MN interface status sub-category includes parameters that
are known locally to the MN link layer. Their aim is to
give information on the current MN capabilities;
. MN available attachments status sub-category includes
parameters that are learned from the available point of
attachments through the L2 air interface. Their aim is to
give information on the capabilities of the available
attachment points connected to ARs.
4.3.1. MN interface status parameters
MN current network identifier
The MN current network identifier indicates the current network
identifier used at link layer for MN attachment to the network.
The type of identifier depends on MN interface type.
MN current attachment identifier
The MN current attachment identifier indicates the current radio
attachment point for the MN.
MN power mode
The MN power mode indicates in which power mode the link layer
interface is currently operating.
MN measured bandwidth
The MN measured bandwidth indicates the current available
bandwidth measured by the MN over the link.
MN bit error rate
The MN bit error rate indicates the current measured bit error
rate.
MN packet error rate
The MN packet error rate indicates the current measured packet
error rate.
MN current data rate
The MN current data rate indicates the current rate at which the
MN link layer is transmitting/receiving packets.
MN current transmit power
The MN current transmit power indicates the current power at
which the interface transmits packets.
Bertin Expires Feb. 2004 [Page 5]
Internet Draft Parameters for Link Hints August 2003
MN current radio link quality
The MN current radio link quality indicates the current quality
as measured by the interface.
MN available radio link quality
The MN available radio link quality lists quality measurements
on available radio attachment points other than the current one.
MN interface status
The MN interface status can be ON or OFF. If the MN interface
status is ON, the interface is present into the MN, and the
interface is activated.
MN L2 handover status
The MN L2 handover status indicates the status of L2 handover
when it occurs. This parameter can be one of the following
states:
. L2 handover in progress: the network interface is performing
a L2 handover
. No L2 handover: the network interface is not performing a L2
handover
MN interface Load
It represents the interface load in terms of number of packets
sent and/or received by/through the interface.
MN noise level
The MN noise level indicates the noise intensity measured in the
received packets.
4.3.2. MN available attachments status
MN other network identifiers
The MN other network identifiers lists the available network
identifiers detected at the link layer when several networks are
available.
MN available attachments identifiers
The MN available attachments identifiers list the identifiers of
detected radio attachments point available in the MN
neighbourhood.
MN network advertisement frequency
The MN network advertisement frequency represents the frequency
of the periodic control message(s) sent by the point of
attachment of the MN.
MN network configured data rates
The MN network configured data rates gives the available data
rate(s) on the point of attachment of the MN. The available data
Bertin Expires Feb. 2004 [Page 6]
Internet Draft Parameters for Link Hints August 2003
rate(s) represent(s) rate that the point of attachment might use
at a given time.
5. AR parameters set
As already introduced, some parameters are common to MN and AR sets.
In the following, we list parameters available at the AR side with
reference to the ones described in the previous section for common
parameters or with more detailed description for parameters relevant
at the AR side only.
Any AR may control one or several link-layer interfaces integrated in
the AR such as hardware interfaces or remotely available through APs
connected to a fixed AR. The connection between APs and AR can use a
LAN (that is a typical deployment case for 802.11 networks) or
specific architecture and protocols such as a dedicated cellular
access network (that is the case for GPRS). Depending on the
connection types and protocols between APs and AR, only a subset of
the following parameters will be available. For examples
illustrating the way to use these parameters with various link-layer
technologies, please see annex A.
5.1. AR static parameters
AR interface type list
See MN interface type definition in section 4.1.
AR interface type options
See MN section interface type options definition in section 4.1.
AR hardware identifier
The AR hardware identifier identifies uniquely the hardware module
for the link layer interface. The type of identifier depends on the
interface type.
5.2. AR configuration parameters
AR current interface type
See MN current interface type definition in section 4.2.
AR network identifiers
The AR network identifiers lists the supported network
identifiers by the radio interface.
AR maximum transmission power
See MN maximum transmission power definition in section 4.2.
Data rate
See MN Data rate definition in section 4.2.
Bertin Expires Feb. 2004 [Page 7]
Internet Draft Parameters for Link Hints August 2003
AR security level
See MN Security level definition in section 4.2.
AR radio channel
The AR radio channel parameters indicates the radio channel used
at the link layer interface.
AR max packet retransmission
The AR max packet retransmission parameter indicates the maximum
number of retransmissions applied to any data packet over the
link.
AR beacon period
The AR beacon period parameter indicates the period at which
beacons are transmitted. This parameter is applicable to
IEEE802.11 interface type only.
AR fragmentation threshold
See MN fragmentation threshold definition in section 4.2.
5.3. AR link status parameters
AR link status parameters are split into two sub-categories:
. AR interface status sub-category contains parameters that
are known locally to the AR radio link layer;
. AR attached MN status sub-category contains parameters that
are learned from the attached MN through the L2 air
interface.
5.3.1. AR interface status parameters
AR bit error rate
See MN bit error rate definition in section 0.
AR packet error rate
The MN packet error rate definition in section 0.
5.3.2. AR attached MN status parameters
AR number of attached nodes
The AR number of attached nodes indicates the number of attached
MNs nodes to the link layer interface.
AR attached MN status
The AR attached MN status parameter lists indicates the current
radio status for a given MN by listing its following parameters:
MN hardware identifier, MN current network identifier, MN
interface load, MN power mode, MN current data rate, MN bit
error rate, MN packet error rate, MN radio link quality.
Bertin Expires Feb. 2004 [Page 8]
Internet Draft Parameters for Link Hints August 2003
6. Acknowledgements
The authors would like to thank the members of the French RNRT
Cyberte project (France Telecom R&D, Cisco System, ENST Bretagne,
IRISA, and LSIIT) for their valuable feedback.
7. References
[1] Johnson, D. Perkins, C. and Arko, J. "Mobility Support in IPv6",
draft-ietf-mobileip-ipv6-24.txt, June 30, 2003.
[2] Perkins, C., "IP Mobility Support for IPv4", RFC3344, August
2002.
[3] Soliman, H. Castelluccia, C. El-Malki, K. Bellier, L.
"Hierarchical Mobile IPv6 mobility management (HMIPv6)", draft-
ietf-mobileip-hmipv6-08.txt, June, 2003 (work in progress).
[4] Koodli, R. "Fast Handovers for Mobile IPv6", draft-ietf-mobileip-
fast-mipv6-06.txt, 1 March 2003 (work in progress).
8. Author's Addresses
Philippe Bertin
France Telecom R&D
4, Rue du Clos Courtel
35512 CESSON SEVIGNE
FRANCE
Phone: +33 2 99 12 41 57
Email: philippe.bertin@francetelecom.com
Thomas Noel
LSIIT - University Louis Pasteur
Ple API, bureau C444
Boulevard Sbastien Brant
Illkirch 67400
FRANCE
Phone: (33) 3 90 24 45 92
Email: noel@dpt-info.u-strasbg.fr
URI: http://www-r2.u-strasbg.fr/~noel/
Nicolas Montavont
LSIIT - University Louis Pasteur
Ple API, bureau C444
Boulevard Sbastien Brant
Illkirch 67400
Bertin Expires Feb. 2004 [Page 9]
Internet Draft Parameters for Link Hints August 2003
FRANCE
Phone: (33) 3 90 24 45 87
Email: montavont@dpt-info.u-strasbg.fr
URI: http://www-r2.u-strasbg.fr/~montavont
Bertin Expires Feb. 2004 [Page 10]
Internet Draft Parameters for Link Hints August 2003
Annex A
The link hints listed in this document aim to be generic and not
specific to a technology. However, the listed fields are designed to
represent the parameters of each heterogeneous technology. In this
annex, we propose a way to illustrate them.
Table 1: examples of MN parameters
-------------------------------------------------------------------
| | IEEE 802.11 | Bluetooth | GPRS |
|-------------------------------------------------------------------|
| MN static parameters |
|-------------------------------------------------------------------|
|MN interface Type List |802.11g,a |Bluetooth |GPRS |
|MN interface type options|802.11i |BNEP ū RFCOM | - |
|MN hardware ID |H.MAC addr |H.MAC addr | IMEI |
|-------------------------------------------------------------------|
| MN configuration parameters |
|-------------------------------------------------------------------|
|MN current interface type|IEEE 802.11a |Bluetooth | GPRS |
|MN default network ID |SSID | X | PLMN |
|MN maximum Tx power |50mW |1mW |2W |
|MN data rate |6, 12, 24Mbps |1Mbps |30kbps |
|MN security level |EAP TTLS |Authentication|SIM auth. |
|MN frag. Threshold |max MTU |max MTU |max MTU |
|-------------------------------------------------------------------|
| MN link environment parameters / MN interface status |
|-------------------------------------------------------------------|
|MN current network ID |SSID | X |PLMN |
|MN current attach.ID |BSSID |H.M.addr of AP|cell-id |
|MN power mode |PSP |park/hold/... | ready |
|MN measured bandwidth |x Mbps |x Kbps |x Kbps |
|MN Bit error rate |probability |probability |probability|
|MN packet error rate |probability |probability |probability|
|MN current data rate |x Mbps |x Kbps |x Kbps |
|MN curr. transmit power |x mW |x mW |x mW |
|MN curr. radio link qual.|x dBm |x dBm |x dBm |
|MN interface status |ON || OFF |ON || OFF |ON || OFF |
|MN L2 handover status |YES || NO |YES || NO |YES||NO |
|MN interface load |x packets |x packets |x packets |
|MN noise level |x dBm |x dBm |xdBm |
|-------------------------------------------------------------------|
| MN link environment parameters / MN available attachment status |
|-------------------------------------------------------------------|
|MN other network ID |SSIDs in range| X |PLMN(s) |
|MN available attach. IDs |BSSIDsin range|H.M.addr of AP|cell-id |
|MN net. adv. Frequency |beacon period | X | X |
|MN net. config. data rate|6, 12 Mbps |1Mbps |30 Kbps |
|MN avail. radio link qual|x',x''... dBm |x',x''..dBm |x',x''..dBm|
-------------------------------------------------------------------
Bertin Expires Feb. 2004 [Page 11]
Internet Draft Parameters for Link Hints August 2003
Table 2: examples of AR parameters
-------------------------------------------------------------------
| | IEEE 802.11 | Bluetooth | GPRS |
|-------------------------------------------------------------------|
| AR static parameters |
|-------------------------------------------------------------------|
|AR interface type list |802.11g,a |Bluetooth |GPRS |
|AR interface type option |IEEE 802.11i |BNEP ū RFCOM | X |
|AR hardware ID |H.MAC addr |H.MAC addr | X |
|-------------------------------------------------------------------|
| AR configuration parameters |
|-------------------------------------------------------------------|
|AR current interface type|IEEE 802.11a |Bluetooth | GPRS |
|AR network IDs |SSID(s) | X | PLMN |
|AR maximum Tx power |50mW |1mW | 5W |
|AR data rate |6, 12, 24Mbps |1Mbps | 30kbps |
|AR security level | EAP TTLS |Authentication|SIM auth |
|AR radio channel |channel(s) | X | X |
|AR beacon period |beacon period | X | X |
|AR frag. Threshold |max MTU |max MTU |max MTU |
|-------------------------------------------------------------------|
| AR link status parameters / AR interface status parameters |
|-------------------------------------------------------------------|
|AR bit error rate |probability |probability |probability|
|AR packet error rate |probability |probability |probability|
|-------------------------------------------------------------------|
| AR link status parameters / AR attached MN status parameters |
|-------------------------------------------------------------------|
|AR nb of attached Nodes |x nodes |x nodes |x node |
|AR attached MN status (1)|MN1 ID/netID/load/power/rate/BER/PER/qual|
|AR attached MN status (2)|MN2 ID/netID/load/power/rate/BER/PER/qual|
| ..... | ...... |
|AR attached MN status (n)|MNn ID/netID/load/power/rate/BER/PER/qual|
-------------------------------------------------------------------
Full Copyright Statement
"Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
Bertin Expires Feb. 2004 [Page 12]
Internet Draft Parameters for Link Hints August 2003
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS 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.
Bertin Expires Feb. 2004 [Page 13]
| PAFTECH AB 2003-2026 | 2026-04-22 03:35:45 |