Return-Path: <sratliff@cisco.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
 with ESMTP id 9E93311E809C for <manet@ietfa.amsl.com>;
 Mon, 23 Jul 2012 08:33:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.482
X-Spam-Level: 
X-Spam-Status: No, score=-10.482 tagged_above=-999 required=5 tests=[AWL=0.116,
 BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jVM8l7EJqfH6 for
 <manet@ietfa.amsl.com>; Mon, 23 Jul 2012 08:33:32 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75])
 by ietfa.amsl.com (Postfix) with ESMTP id 3E07611E809B for <manet@ietf.org>;
 Mon, 23 Jul 2012 08:33:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com;
 i=sratliff@cisco.com; l=68759; q=dns/txt; s=iport; t=1343057612; x=1344267212;
 h=from:to:subject:date:message-id:references:mime-version;
 bh=70L3PtHOoC8gTd0Cr+A0EXsdw1WEZ8JEM67ET7OlwNs=;
 b=FbLjXoaRpKVL6z163APgTpKwP+hAuxqfaiR6Ttn78b3G0cf59yzQ62uk
 Aib885f+fP09vnttIQRfA/WVjLBq+dO24jXwgXzfOlRLunNITvvMY3GvH
 bINQjDYO5Jc+mHxpoXIYSOAQRgpZX+Py/VtOQVQ1s80vwnDr3hGyM9Mrq 8=; 
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAJZtDVCtJV2c/2dsb2JhbAA7AQYDuTiBB4IgAQEBAwEBAQEPAQcBTAQDAg4LAgEZAwECASABBgchBgsUBwIIAgQKBwIUDodcAwYGC50algINiUoEimZnEAEDB4MXgkFgA5N1gVSLCoMdgWaCXz6BGAIHHA
X-IronPort-AV: E=Sophos; i="4.77,639,1336348800"; d="scan'208,217";
 a="104458951"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by
 rcdn-iport-4.cisco.com with ESMTP; 23 Jul 2012 15:33:30 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82])
 by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id q6NFXUqN022694
 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for
 <manet@ietf.org>; Mon, 23 Jul 2012 15:33:30 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.20]) by xhc-rcd-x08.cisco.com
 ([173.37.183.82]) with mapi id 14.02.0298.004; Mon, 23 Jul 2012 10:33:29 -0500
From: "Stan Ratliff (sratliff)" <sratliff@cisco.com>
To: manet IETF <manet@ietf.org>
Thread-Topic: [manet] MANET Terminology Update
Thread-Index: AQHNaKCpTpyJkO77IEKicKgVvY7Vig==
Date: Mon, 23 Jul 2012 15:33:28 +0000
Message-ID: <02619309-38C0-4F60-8814-E680A4894F33@cisco.com>
References: <CAMDg9bMJUiUQM8eegJ9imeoCzt42eS-BaL2C8PkCkR9Hee0aPA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.102.54.123]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19058.005
x-tm-as-result: No--50.099700-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative;
 boundary="_000_0261930938C04F608814E680A4894F33ciscocom_"
MIME-Version: 1.0
Subject: [manet] Fwd:  MANET Terminology Update
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>,
 <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/manet>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>,
 <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 15:33:36 -0000

--_000_0261930938C04F608814E680A4894F33ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Looks like this was a "respond to me" instead of a "respond to the list". I=
'm forwarding it along.
Stan


Begin forwarded message:

From: Daniel He <drdanhe@gmail.com<mailto:drdanhe@gmail.com>>
Subject: Re: [manet] MANET Terminology Update
Date: July 23, 2012 11:01:37 AM EDT
To: "Stan Ratliff (sratliff)" <sratliff@cisco.com<mailto:sratliff@cisco.com=
>>

If we go this document, we will go a stupid work. I agree with Stan,  don't=
 support it as well.
Regards
Dan

On 23 July 2012 15:59, Stan Ratliff (sratliff) <sratliff@cisco.com<mailto:s=
ratliff@cisco.com>> wrote:
I'm going to "+1" one (and only one) sentence in this email thread:

>
> On 7/6/12, Thomas Heide Clausen <thomas@thomasclausen.org<mailto:thomas@t=
homasclausen.org>> wrote:
>> I do not see the need for this terminology document in MANET:
>

In my opinion as a working group participant, this is an unnecessary distra=
ction for the working group, and will not result in a meaningful document. =
I will not support it.

Regards,
Stan




On Jul 23, 2012, at 2:58 AM, Abdussalam Baryun wrote:

> Hi
>
> Comment inline below:
>
> On 7/6/12, Thomas Heide Clausen <thomas@thomasclausen.org<mailto:thomas@t=
homasclausen.org>> wrote:
>> I do not see the need for this terminology document in MANET:
>>
>>      o       The RFCs published by the WG all do a good job of defining =
their proper
>>              terminology and conventions in the sections, aptly named to=
 this
>>              effect -- and something which both the WG and the IESG has =
been very
>>              vigilant in ensuring.
>
> Agree
>
>>
>>      o       Extracting this terminology, to present without the context=
 of the RFC in
>>
>>              which they are introduced and used, is both futile and a so=
urce
>>              of errors and confusion.
>
> It is not extracting any thing it is locating information in easy
> location to be reached efficiently by researchers, or other WG
> participants. In another reason, for example the RFC5444 and RFC6130
> is providing a MANET standard, while any RFC in this WG is specifying
> its own terminology and message format, but the reason was to bring
> RFCs to have similar formating functions. The terminology RFCs in many
> WGs does the same. RFC2501 is doing a good job to bring understanding
> of MANET which the terminology informational RFCs are doing in each
> concept/group-charter.
>
>>
>>      o       The domain evolves, new protocols appear and introduce new =
concepts,
>>              terms. This is captured by carefully defining such in the R=
FC specifying
>>              that protocol. Any terminology document (aside from all its=
 other issues,
>>              indicated in this list) would likely be obsolete and incomp=
lete before
>> the
>>              ink with which it was written was dry.
>
> So when new concepts appear any WG needs to prepare updates I-D to
> their information/standards/experiments so that knowledge is
> consistent and concepts are updated as will (including terminology
> document can be updated). Please note that our documents in MANET are
> a source of information to any participant in IETF, so we need to
> focus to not only produce new concepts/work but we see into
> update/obsolete previous work if possible/necessary. other wise why
> did the IETF make an option possibility to *update* and *obsolete* if
> they are not needed for WGs.
>
>>
>>      o       All RFCs in MANET uses no more than a small subset of the t=
otal MANET
>>              (and Internet) terminology. A collective terminology docume=
nt would,
>>              therefore, necessarily be adding entropy to any single RFC =
and to the
>>              WG (and to implementers of the WG protocols).
>
> Please note that the bigest reason of terminology is that when WG
> participants discuss things they don't misunderstand. Please note
> there are many times in MANET WG there are misunderstood in technical
> terms (I have references on the list to many incidence if you ask), so
> if experts have this problem we need to solve it by a RFC document,
> also we need to give the protocol user a sense of the general/specific
> terminology (as we have MANET general format, MANET general
> understanding, MANET general direction).
>
>>
>>      o       Certainly, a large number of terms in this document are ent=
irely out of
>> scope
>>              (such as those pertaining to non-MANET developed concepts o=
r protocols,
>>              e.g., those developed in other parts of the IETF), are usel=
ess for the WG
>>              (such as, but not exclusively, "communication channel" and =
"communication
>>
>>              medium"), are by nature ambiguous (such as, but not exclusi=
vely, "Upper
>> Layer"
>>              and "Node"), carry a legacy that renders them difficult to =
use (such as,
>> but
>>              not exclusively, "Logical (virtual) Link", "Physical Link",=
 and "Link").
>>
>
> I disagree that thoes terms are out of scope of the I-D of the MANETs
> context terminology, because those terms you mentioned were used in
> one/some MANET RFCs, so they need to be explained to bring all terms
> together to make overall knowledge to internet community. Your
> argument is right only if we are not specifying network-protocols, so
> because we are doing a type of network, then our documents for it
> SHOULD be *connected* by some combined meaning/knowledge *words*, so
> other (i.e. all internet community) can understand, without any
> possibility of misunderstanding (there are many examples I can give if
> you want).
>
> I thank you for your comments, and I will prepare a new version for the I=
-D,
>
> Best Regards
>
> Abdussalam Baryun
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>> On Jul 3, 2012, at 1:24 PM, Abdussalam Baryun wrote:
>>>>
>>>>> Dear All
>>>>>
>>>>> I completed the first version of draft on terminology and submited th=
e
>>>>> draft yesterday (with getting some techniq problem), but needed to
>>>>> post to know the community feedback and advise. There are other terms
>>>>> that was not yet included which will need some advise from you.
>>>>> Thanking you,
>>>>>
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>> Abbreviations Used in The submitted Document
>>>>>
>>>>> AH   Authentication Header
>>>>> DAD  Duplicate Address Detection
>>>>> DPD  Duplicate Packet Detection
>>>>> DoS  Denial of Service
>>>>> ESP  Encapsulating Security Payload
>>>>> IP   IPv4 or IPv6
>>>>> ICMP Internet Control Message Protocol
>>>>> IIB  Interface Information Base
>>>>> ETX  Estimated Expected number of Transmission
>>>>> FIB  Forwarding Information Base
>>>>> LQI  Link Quality Indicator
>>>>> L2   Data Link Layer (i.e. 2nd layer in ISO model)
>>>>> L3   Internet Layer (i.e. 3rd layer in ISO model)
>>>>> LLN  Low power and Lossy Network
>>>>> MAC  Mediam Access Control
>>>>> MIB  Management Information Base
>>>>> MTU  Maximum Transmission Unit
>>>>> NBMA Non-Broadcast Multi-Access link
>>>>> NHDP Neighborhood Discovery Protocol
>>>>> ND   IP Neighbor Discovery
>>>>> OSPF Open Shortest Path First
>>>>> RIB  Routing Information Base
>>>>> SMF  Simplified Multicast Forwarding
>>>>> TCP  Transmission Control Protocol
>>>>> UDP  User Datagram Protocol
>>>>>
>>>>> 2.3 Definitions for MANET Terms
>>>>>
>>>>> 2.3.1 Terms Definition of MANET Communication:
>>>>>
>>>>> Communications=92 Technology or Facility:
>>>>> The means employed by two or more devices/subsystems to transfer
>>>>> and/or receive information between them in one way or two way
>>>>> communication.  MANET communications often uses the wireless
>>>>> transmission medium(s) and MAY use some wired mediums (e.g. free
>>>>> space, air, water, antenna, coaxial cables, etc.)
>>>>>
>>>>> Communication Medium:
>>>>> The transceiver system (e.g. such as L2 systems, IEEE802.11 systems,
>>>>> satellite system, etc.) that the routing device uses to communicates
>>>>> through the transmission medium(s), by providing connectionless and/o=
r
>>>>> connection services that MAY be established. The system medium
>>>>> includes MAC layer and MAY include the physical Layer.
>>>>>
>>>>> Communication Channel:
>>>>> A subdivision of the physical communication medium (i.e. radio carrie=
r
>>>>> signal bandwidth, or the system bandwidth) allowing possibly shared
>>>>> independent uses of the medium. Channels may be made available by
>>>>> subdividing the medium into; distinct time slots, distinct spectral
>>>>> bands, or coding sequence, etc.
>>>>>
>>>>> MANET Protocol:
>>>>> The communication system/subsystem that operates and maintains the
>>>>> ad hoc communication technology or facility within MANET. MANET routi=
ng
>>>>> Protocols often apply distributed algorithms/techniques to disseminat=
e
>>>>> or forward routing messages within a MANET routing domain.
>>>>>
>>>>> Topology:
>>>>> An abstract representation of a network (physical or logical), as a
>>>>> graph (G) whose topology is defined by a set of routers/bridges (V)
>>>>> that
>>>>> communicate through set of links (E), where the G =3D (V, E).
>>>>>
>>>>> Physical-level Topology:
>>>>> A topology of the communication medium networks consists of routing
>>>>> devices and physical links. This topology information is updated by
>>>>> devices=92 technology in the L2 information Base.
>>>>>
>>>>> Network-level Topology:
>>>>> A topology of the communication system networks consists of routers a=
nd
>>>>> links. This topology information is updated by routers in its RIB.
>>>>>
>>>>> Multihop MANET:
>>>>> A MANET that its node(s) MAY need(s) more than one IP hop to reach th=
e
>>>>> destination.
>>>>>
>>>>> Reactive Routing:
>>>>> An on-demand based routing protocol that operates route discover and
>>>>> maintainance the route(s), to reach the demanded destination(s).
>>>>>
>>>>> Proactive Routing:
>>>>> A topology RIB based routing protocol that operates routes and
>>>>> maintains
>>>>> the network topology, to reach its known destination(s). Each router
>>>>> maintains routes to all reachable destinations at all times, whether =
or
>>>>> not there is currently any demand to deliver packets to those
>>>>> destinations.
>>>>>
>>>>> Upper Layer:
>>>>> a protocol layer above IP layer (e.g. as TCP, UDP, OSPF).
>>>>>
>>>>> MANET Domain: TBD
>>>>>
>>>>> MANET Signaling:
>>>>> Sending and exchanging some MANET messages/information.
>>>>>
>>>>> 2.3.2 Terms Definition of MANET Elements
>>>>>
>>>>> Node:
>>>>> A device/subsystem that MUST implement IP and SHOULD participate in
>>>>> MANET signaling. It either runs a MANET routing protocol or participa=
te
>>>>> in MANET signaling.
>>>>>
>>>>> Router:
>>>>> A MANET node that MUST implement a MANET routing protocol and forward=
s
>>>>> IP packets not explicitly addressed to itself.
>>>>>
>>>>> Host:
>>>>> A node that is not a router. All destinations in MANET that receive
>>>>> delivered data are hosts.
>>>>>
>>>>> Link:
>>>>> A link between two node interfaces. This link may be Logical
>>>>> (i.e. virtual) link or physical link. Logical links are between two
>>>>> logical interfaces and physical links are between two physical
>>>>> interfaces. Links are either unidirectional or bidirectional
>>>>> (links may be on-link and off-link: see RFC4861).
>>>>>
>>>>>
>>>>> Physical Link:
>>>>> a communication facility or medium over which the nodes can
>>>>> communicate at the link layer, i.e., the layer immediately below
>>>>> IP. Physical interfaces are the nodes=92 attachment to physical links=
.
>>>>> Physical Link types are point-to-point, NBMA, multicast capable,
>>>>> and shared-media, etc (see link types in ND [RFC4861]).
>>>>>
>>>>> Logical (virtual) Link:
>>>>> a communication facility (at L3, or upper-layer) over which nodes can
>>>>> communicate. This logical link is between two MANET interfaces exists
>>>>> if either can be heard by the other.
>>>>>
>>>>> Link MTU:
>>>>> the maximum transmission unit (i.e. maximum unit size in octets), tha=
t
>>>>> can be conveyed in one transmission unit over the link.
>>>>>
>>>>>
>>>>> Node Interface:
>>>>> A node's point of attachment to a link. Each node MUST have at least
>>>>> one
>>>>> interface that SHOULD be assigned an IP address. If there is/are more
>>>>> than one interface(s) per node then the additional interface(s) MAY b=
e
>>>>> assigned an IP address. If an interface is not assigned to an IP
>>>>> address
>>>>> it MUST be identified by the MANET routing protocol. An interface MAY
>>>>> be
>>>>> assigned one or more addresses.
>>>>>
>>>>> MANET Interface:
>>>>> A node interface that participate in; exchange MANET information used
>>>>> in
>>>>> MANET routing or exchange information in MANET neighbor node discover=
y
>>>>> (e.g as the term used in RFC6130). A MANET interface MUST be assigned
>>>>> to
>>>>> least one  address to communicate. A router interface MUST be
>>>>> assigned a routable address which is the main address for the
>>>>> interface.
>>>>>
>>>>>
>>>>> 2.3.3 Terms Definition of MANET Identifications:
>>>>>
>>>>> An interface MAY be assigned one or more addresses. If the interface =
is
>>>>> a logical interface it MAY be assigned to only logical addresses, but
>>>>> if
>>>>> it is a physical interface MAY be assigned with physical address
>>>>> (e.g. MAC address) and/or logical address(es) (e.g. IP addresses,
>>>>> MANET addresses).
>>>>>
>>>>>
>>>>> MANET Address
>>>>> A MANET-subnet, node, or interface address. Node and interface
>>>>> addresses
>>>>> are either IP addresses or RFC5444 addresses. All subnet addresses ar=
e
>>>>> unicast IP addresses.
>>>>>
>>>>> Address Block and TLV: as specified in RFC5444
>>>>>
>>>>> Routable address:
>>>>> A subnet address which can be a destination address. A router MUST be
>>>>> able to distinguish a routable address from a non-routable address.
>>>>> Broadcast, and multicast addresses, limited in scope to less than the
>>>>> entire MANET, MUST NOT be considered as routable addresses. Anycast
>>>>> addresses MAY be considered as routable addresses.
>>>>>
>>>>> Main address
>>>>> A routable address (MANET address) that is assigned to one router's
>>>>> MANET interface.
>>>>>
>>>>> Originator address:
>>>>> A node address of the node that originated a MANET message (this
>>>>> message
>>>>> MUST include the originator address). It MAY be a routable or an
>>>>> unroutable address.
>>>>>
>>>>> subnet prefix
>>>>> A bit string that consists of some number of initial bits of an IP
>>>>> address.
>>>>>
>>>>> Interface identifier
>>>>> the remaining low-order bits in the node's IP address after the subne=
t
>>>>> prefix. A number used to identify a node's interface on a link.
>>>>>
>>>>> 2.3.4 Terms Definition of MANET exchange information formats:
>>>>>
>>>>> Packet:
>>>>> A MANET packet of a header plus payload. These packets are either
>>>>> IP packets or RFC5444 packets. RFC5444 packet MUST be encapsulated
>>>>> in IP packet. Packets are generated by nodes to be sent to
>>>>> destination(s) through MANET or through the Internet. RFC5444 packets
>>>>> information MAY not be used only by MANET routers.
>>>>>
>>>>> Message:
>>>>> A MANET data message or routing control message. Routing control
>>>>> messages are either MANET routing protocol messages or/and RFC5444
>>>>> messages.
>>>>>
>>>>> Type Length Value coding (TLV):
>>>>> A generic way to represent MANET information (as in [RFC5444] and
>>>>> [RFC5497]).
>>>>>
>>>>> Frame:
>>>>> A L2 protocol TLV with a header and payload. In some technologies the
>>>>> L2
>>>>> operates a MANET routing protocol as a local area networking system.
>>>>> Frames MAY encapsulate MANET packets to be tunneled through a
>>>>> telecommunication network.
>>>>>
>>>>> Route Request Message (RREQ)
>>>>> A message is used to discover a valid route to a particular
>>>>> destination address, called the RREQ Target Node. When a router
>>>>> processes a RREQ it learns routing information on how to Originator
>>>>> Node.
>>>>>
>>>>> Route Reply Message (RREP)
>>>>> A message is used to disseminate routing information about
>>>>> the RREP Target Node to the RREQ Originator Node and the intermediate
>>>>> routers.
>>>>>
>>>>> Route Error Message (RERR)
>>>>> A message is used to disseminate the information that a route is
>>>>> not available for one or more particular addresses. A RERR message is
>>>>> used to indicate that a router does not have a forwarding route
>>>>> to one or more particular addresses.
>>>>>
>>>>> 2.3.5 Terms Definition Related to MANET Protocol Operation:
>>>>>
>>>>> Hop-by-hop Routing: (TBD)
>>>>> A dynamic routing that routes to destination by routing table.
>>>>>
>>>>> Source Routing: (TBD)
>>>>> A dynamic routing that its route path is provided in the IP packet.
>>>>>
>>>>> Route Discovery: TBD
>>>>>
>>>>> Route Maintenance: TBD
>>>>>
>>>>> Neighbor discovery: (TBD)
>>>>> A node discovers neighbors only if the node receives from it's
>>>>> neighbors.
>>>>>
>>>>>
>>>>> Multipoint relay (MPR): (TBD)
>>>>> A router X1 is an MPR for a router Y1, if router Y1 has indicated
>>>>> its selection of router X1 as an MPR in a recent HELLO message.
>>>>> Router X1 may be a flooding MPR for Y1 if it is indicated to
>>>>> participate in the flooding process of messages received from
>>>>> router Y1, or it may be a routing MPR for Y1, if it is indicated to
>>>>> declare link-state information for the link from X1 to Y1. It may
>>>>> also be both at the same time.
>>>>>
>>>>> MPR selector:
>>>>> A router, Y, is a flooding/routing MPR selector of router X if
>>>>> router Y has selected router X as a flooding/routing MPR.
>>>>>
>>>>> Router Parameters:
>>>>> boolean or numerical values, specified for each router, and not
>>>>> specific to an interface. A router MAY change router parameter
>>>>> values at any time, subject to some MANET constraints.
>>>>>
>>>>> MANET Routing Metric:
>>>>> A MANET routing cost that is governed by specific rules and propertie=
s
>>>>> defined by the MANET routing protocol which captures specific link or
>>>>> node characteristics. Examples of basic metrics are hop-count, ETX,
>>>>> LQI,
>>>>> etc.
>>>>>
>>>>> Distance Vector Metric
>>>>> A metric class related to rules of the MANET interface and MANET path
>>>>> distance. The metric can be calculated by the distance vector routing
>>>>> algorithm class used by the MANET routing protocol. A metric of the
>>>>> distance a message or piece of information has traversed. The minimum
>>>>> value of distance is the number of IP hops traversed.
>>>>>
>>>>> Link State Metric
>>>>> A metric type related to the MANET network-topology status and logica=
l
>>>>> links' states. This metric is calculated by the link state routing
>>>>> algorithm class used by the MANET routing protocol. A metric type may=
be
>>>>> EXT, LQL, etc.
>>>>>
>>>>> Link Metric: TBD
>>>>>
>>>>> Neighbor Metric: TBD
>>>>>
>>>>> Path accumulated:
>>>>> The RREQ message accumulates intermediate routers that are in path to
>>>>> destination(s).
>>>>>
>>>>> Protocol Sequence Number:
>>>>> A Sequence Number related to a MANET protocol that maintained by each
>>>>> protocol subsystem process. This sequence number is used by other
>>>>> subsystems to identify the temporal order of protocol information
>>>>> generated.
>>>>>
>>>>> Router Sequence Number:
>>>>> A router sequence number is maintained by each router process. The
>>>>> sequence number is used by other routers to identify the temporal
>>>>> order of routing information generated and ensure loop-free routes.
>>>>>
>>>>> MANET Information Base:
>>>>> A collection of information (in Table or Cache structure) maintained
>>>>> by MANET protocols and which is to be made available to MANET routing
>>>>> protocols. An Information Base may be associated with a MANET router
>>>>> or with MANET interface (e.g. route request table, IIB, RIB, FIB, MIB=
).
>>>>>
>>>>> RIB Entry:
>>>>> The RIB entry is a conceptual data structure. Implementations may use
>>>>> any internal representation that conforms to the semantics of a route
>>>>> as specified in the router specification.
>>>>>
>>>>> 3. IP Considerations and Terminology
>>>>>
>>>>> All MANET nodes MUST implement IP and all MANET routers MUST
>>>>> run/implement  at least one MANET routing protocol. The
>>>>> terminologies described in this document can be used for
>>>>> IPv4-MANET and IPv6-MANET. The IPv4 addresses MAY be used in IPv6
>>>>> packets but IPv6 addresses MUST not be in IPv4 packets.
>>>>>
>>>>> IP address:
>>>>> IPv4 addresses or IPv6 addresses.
>>>>>
>>>>> IP Packet:
>>>>> The packet header plus payload as specified in [RFC791] and [RFC2460]
>>>>> for IPv4 and IPv6 respectively. It can encapsulate RFC5444 packets as
>>>>> specified by RFC5498.
>>>>>
>>>>> Mobile IP considerations:
>>>>> Mobile IP terms are provided in [RFC6275], and this technology
>>>>> assists nodes while connected through the Internet domain(s). MANET
>>>>> is an infrastructure-less network that is able to communicate with
>>>>> the Internet (i.e. an IP infrastructure network).
>>>>>
>>>>> 4. Security Consideration and Terminology
>>>>>
>>>>> It is RECOMMENDED that MANET routing protocols consider security
>>>>> issues because the MANET's transmission medium is wireless which make
>>>>> it vulnerable to attacks [ANJUM][RFC4593]. In some situations the
>>>>> routing information while traversing the MANET MAY be used by an
>>>>> intruder node, to obtain MANET data traffic or/and attack the MANET
>>>>> [HERBERG]. Forwarding protocols that use DPD techniques MAY be
>>>>> vulnerable to DoS attacks such as [RFC6621]. MANETs MAY be secured
>>>>> by using IPsec, AH, DAD, and ESP techniques, and other. However,
>>>>> it is RECOMMENDED that MANET detects attackers and possible threats.
>>>>>
>>>>> The following are some terminology related to MANET threats and
>>>>> security.
>>>>>
>>>>> Attacker: A node, present in the network and which intentionally seek=
s
>>>>> to compromise information based in MANET router(s). The Attacker MAY =
be
>>>>> a compromised MANET router if obtained MANET identity or routing
>>>>> information.
>>>>>
>>>>> Compromised MANET Router: An attacker router, present in MANET and
>>>>> which generates syntactically correct routing control messages. Contr=
ol
>>>>> messages emitted by compromised router(s) may contain additional
>>>>> information, or omit information, as compared to a control message
>>>>> generated by a non-compromised router located in the same MANET
>>>>> topological position.
>>>>>
>>>>> Legitimate MANET Router: A MANET router, which is not a Compromised
>>>>> MANET Router.
>>>>>
>>>>> Jamming Attack:
>>>>> The attacker transmits massive amounts of interfering radio traffic,
>>>>> which will prevent legitimate traffic (e.g., routing and data traffic=
)
>>>>> on all or part of the MANET. Indirect jamming attacks MAY occur by
>>>>> influencing Legitimate MANET Router to transmit unnecessary
>>>>> information.
>>>>>
>>>>> Eavesdropping:
>>>>> Obtaining a copy by the attacker of the transmitted MANET routing
>>>>> information or the transmitted data information from its neighbor's
>>>>> transmitted radio packet. Attacker=92s processes MANY be used by atta=
cker
>>>>> to mislead routing. Eavesdropping does not pose a direct threat to th=
e
>>>>> MANET or to its routing.
>>>>>
>>>>> Identity Spoofing:
>>>>> Attacker sends routing messages, pretending to have the MANET identit=
y
>>>>> of another node.
>>>>>
>>>>> Link Spoofing:
>>>>> Compromised MANET router sends routing messages to neighbor node(s)
>>>>> providing incorrect set of link information.
>>>>>
>>>>> Replay Attack:
>>>>> A Compromised router in one MANET region records control traffic
>>>>> information and replays the recorded information in a different MANET
>>>>> region (this type of attack is also called the Wormhole attack).
>>>>>
>>>>> Broadcast Storm:
>>>>> Compromised MANET router may attack the MANET by attempting to change
>>>>> the MANET flooding algorithm(s) to increase routing overheads or/and =
to
>>>>> increase the route discovery delay. Broadcast storm degrades the data
>>>>> traffic delivery and MANET performance.
>>>>>
>>>>> Falsification in MANET:
>>>>> The compromised MANET router sends false routing information into
>>>>> MANET.
>>>>> False routing information received in MANET, MAY create unrealistic
>>>>> information bases.
>>>>>
>>>>> ICMP Attacks:
>>>>> The generation of ICMPv6 error messages may be used by compromised
>>>>> MANET
>>>>> router to attempt DoS attacks by sending an error-causing source
>>>>> routing
>>>>> header in back-to-back datagrams. As the ICMP messages are passed to
>>>>> the
>>>>> upper-layer processes, it is possible to perform attacks on the upper
>>>>> layer protocols (e.g., UDP, TCP). Protocols at the upper layers are
>>>>> RECOMMENDED to perform some form of validation to ICMP messages (usin=
g
>>>>> the information contained in the payload of the ICMP message) before
>>>>> acting upon them.
>>>>>
>>>>> Source Routing Attacks: TBD
>>>>>
>>>>> Acknowledgments:
>>>>>
>>>>> This work has used/modified terms of the following documents: RFC2462=
,
>>>>> RFC2501, RFC3561, RFC3626, RFC3753, RFC4728, RFC4861, RFC5444,
>>>>> RFC6130,  RFC6621, [AODVv2], [OLSRv2], and [HERBERG],
>>>>> Gratefully acknowledge to the IETF community and all contributions.
>>>>>
>>>>> Reference:
>>>>> [HERBERG] Herberg, U., Yi, J., Clausen, T.,"Security Threats for
>>>>>           NHDP", Work in progress, March, 2012.
>>>>> [ANJUM]   Anjum, F. and Mouchtaris, P. "Security for Wireless Ad Hoc
>>>>>           Networks", John Wiley & Sons, March 2007.
>>>>>           ISBN: 978-0-471-75688-0.
>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>
>>>>> I hope to get some advise from the Internet community to make the
>>>>> definitions more suitable/accurate, because I MAY misunderstood.
>>>>> Thanking you,
>>>>>
>>>>> Best Regards
>>>>>
>>>>> Abdussalam Baryun
>>>>> University of Glamorgan, UK
>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> _______________________________________________
> manet mailing list
> manet@ietf.org<mailto:manet@ietf.org>
> https://www.ietf.org/mailman/listinfo/manet

_______________________________________________
manet mailing list
manet@ietf.org<mailto:manet@ietf.org>
https://www.ietf.org/mailman/listinfo/manet



--
Dan He
---------------------
Tel: +44-788-686-3428



--_000_0261930938C04F608814E680A4894F33ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <58ADB34B284E594DBFBC5E1B99302515@cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
Looks like this was a &quot;respond to me&quot; instead of a &quot;respond =
to the list&quot;. I'm forwarding it along.
<div>Stan</div>
<div><br>
<div><br>
<div>Begin forwarded message:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;">
<span style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, =
0, 1.0);"><b>From:
</b></span><span style=3D"font-family:'Helvetica'; font-size:medium;">Danie=
l He &lt;<a href=3D"mailto:drdanhe@gmail.com">drdanhe@gmail.com</a>&gt;<br>
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;">
<span style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, =
0, 1.0);"><b>Subject:
</b></span><span style=3D"font-family:'Helvetica'; font-size:medium;"><b>Re=
: [manet] MANET Terminology Update</b><br>
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;">
<span style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, =
0, 1.0);"><b>Date:
</b></span><span style=3D"font-family:'Helvetica'; font-size:medium;">July =
23, 2012 11:01:37 AM EDT<br>
</span></div>
<div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margi=
n-left: 0px;">
<span style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, =
0, 1.0);"><b>To:
</b></span><span style=3D"font-family:'Helvetica'; font-size:medium;">&quot=
;Stan Ratliff (sratliff)&quot; &lt;<a href=3D"mailto:sratliff@cisco.com">sr=
atliff@cisco.com</a>&gt;<br>
</span></div>
<br>
<div>If we go this document, we will go a stupid work. I agree with Stan,&n=
bsp; don't support it as well.</div>
<div>Regards</div>
<div>Dan<br>
<br>
</div>
<div class=3D"gmail_quote">On 23 July 2012 15:59, Stan Ratliff (sratliff) <=
span dir=3D"ltr">
&lt;<a href=3D"mailto:sratliff@cisco.com" target=3D"_blank">sratliff@cisco.=
com</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">
I'm going to &quot;&#43;1&quot; one (and only one) sentence in this email t=
hread:<br>
<br>
&gt;<br>
&gt; On 7/6/12, Thomas Heide Clausen &lt;<a href=3D"mailto:thomas@thomascla=
usen.org">thomas@thomasclausen.org</a>&gt; wrote:<br>
&gt;&gt; I do not see the need for this terminology document in MANET:<br>
&gt;<br>
<br>
In my opinion as a working group participant, this is an unnecessary distra=
ction for the working group, and will not result in a meaningful document. =
I will not support it.<br>
<br>
Regards,<br>
Stan<br>
<br>
<br>
<br>
<br>
On Jul 23, 2012, at 2:58 AM, Abdussalam Baryun wrote:<br>
<br>
&gt; Hi<br>
&gt;<br>
&gt; Comment inline below:<br>
&gt;<br>
&gt; On 7/6/12, Thomas Heide Clausen &lt;<a href=3D"mailto:thomas@thomascla=
usen.org">thomas@thomasclausen.org</a>&gt; wrote:<br>
&gt;&gt; I do not see the need for this terminology document in MANET:<br>
&gt;&gt;<br>
&gt;&gt; &nbsp; &nbsp; &nbsp;o &nbsp; &nbsp; &nbsp; The RFCs published by t=
he WG all do a good job of defining their proper<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;terminology and co=
nventions in the sections, aptly named to this<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;effect -- and some=
thing which both the WG and the IESG has been very<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;vigilant in ensuri=
ng.<br>
&gt;<br>
&gt; Agree<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; &nbsp; &nbsp; &nbsp;o &nbsp; &nbsp; &nbsp; Extracting this termino=
logy, to present without the context of the RFC in<br>
&gt;&gt;<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;which they are int=
roduced and used, is both futile and a source<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;of errors and conf=
usion.<br>
&gt;<br>
&gt; It is not extracting any thing it is locating information in easy<br>
&gt; location to be reached efficiently by researchers, or other WG<br>
&gt; participants. In another reason, for example the RFC5444 and RFC6130<b=
r>
&gt; is providing a MANET standard, while any RFC in this WG is specifying<=
br>
&gt; its own terminology and message format, but the reason was to bring<br=
>
&gt; RFCs to have similar formating functions. The terminology RFCs in many=
<br>
&gt; WGs does the same. RFC2501 is doing a good job to bring understanding<=
br>
&gt; of MANET which the terminology informational RFCs are doing in each<br=
>
&gt; concept/group-charter.<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; &nbsp; &nbsp; &nbsp;o &nbsp; &nbsp; &nbsp; The domain evolves, new=
 protocols appear and introduce new concepts,<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;terms. This is cap=
tured by carefully defining such in the RFC specifying<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;that protocol. Any=
 terminology document (aside from all its other issues,<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;indicated in this =
list) would likely be obsolete and incomplete before<br>
&gt;&gt; the<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;ink with which it =
was written was dry.<br>
&gt;<br>
&gt; So when new concepts appear any WG needs to prepare updates I-D to<br>
&gt; their information/standards/experiments so that knowledge is<br>
&gt; consistent and concepts are updated as will (including terminology<br>
&gt; document can be updated). Please note that our documents in MANET are<=
br>
&gt; a source of information to any participant in IETF, so we need to<br>
&gt; focus to not only produce new concepts/work but we see into<br>
&gt; update/obsolete previous work if possible/necessary. other wise why<br=
>
&gt; did the IETF make an option possibility to *update* and *obsolete* if<=
br>
&gt; they are not needed for WGs.<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; &nbsp; &nbsp; &nbsp;o &nbsp; &nbsp; &nbsp; All RFCs in MANET uses =
no more than a small subset of the total MANET<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(and Internet) ter=
minology. A collective terminology document would,<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;therefore, necessa=
rily be adding entropy to any single RFC and to the<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;WG (and to impleme=
nters of the WG protocols).<br>
&gt;<br>
&gt; Please note that the bigest reason of terminology is that when WG<br>
&gt; participants discuss things they don't misunderstand. Please note<br>
&gt; there are many times in MANET WG there are misunderstood in technical<=
br>
&gt; terms (I have references on the list to many incidence if you ask), so=
<br>
&gt; if experts have this problem we need to solve it by a RFC document,<br=
>
&gt; also we need to give the protocol user a sense of the general/specific=
<br>
&gt; terminology (as we have MANET general format, MANET general<br>
&gt; understanding, MANET general direction).<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; &nbsp; &nbsp; &nbsp;o &nbsp; &nbsp; &nbsp; Certainly, a large numb=
er of terms in this document are entirely out of<br>
&gt;&gt; scope<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(such as those per=
taining to non-MANET developed concepts or protocols,<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;e.g., those develo=
ped in other parts of the IETF), are useless for the WG<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(such as, but not =
exclusively, &quot;communication channel&quot; and &quot;communication<br>
&gt;&gt;<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;medium&quot;), are=
 by nature ambiguous (such as, but not exclusively, &quot;Upper<br>
&gt;&gt; Layer&quot;<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;and &quot;Node&quo=
t;), carry a legacy that renders them difficult to use (such as,<br>
&gt;&gt; but<br>
&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;not exclusively, &=
quot;Logical (virtual) Link&quot;, &quot;Physical Link&quot;, and &quot;Lin=
k&quot;).<br>
&gt;&gt;<br>
&gt;<br>
&gt; I disagree that thoes terms are out of scope of the I-D of the MANETs<=
br>
&gt; context terminology, because those terms you mentioned were used in<br=
>
&gt; one/some MANET RFCs, so they need to be explained to bring all terms<b=
r>
&gt; together to make overall knowledge to internet community. Your<br>
&gt; argument is right only if we are not specifying network-protocols, so<=
br>
&gt; because we are doing a type of network, then our documents for it<br>
&gt; SHOULD be *connected* by some combined meaning/knowledge *words*, so<b=
r>
&gt; other (i.e. all internet community) can understand, without any<br>
&gt; possibility of misunderstanding (there are many examples I can give if=
<br>
&gt; you want).<br>
&gt;<br>
&gt; I thank you for your comments, and I will prepare a new version for th=
e I-D,<br>
&gt;<br>
&gt; Best Regards<br>
&gt;<br>
&gt; Abdussalam Baryun<br>
&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
&gt;&gt;&gt;&gt; On Jul 3, 2012, at 1:24 PM, Abdussalam Baryun wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Dear All<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; I completed the first version of draft on terminology =
and submited the<br>
&gt;&gt;&gt;&gt;&gt; draft yesterday (with getting some techniq problem), b=
ut needed to<br>
&gt;&gt;&gt;&gt;&gt; post to know the community feedback and advise. There =
are other terms<br>
&gt;&gt;&gt;&gt;&gt; that was not yet included which will need some advise =
from you.<br>
&gt;&gt;&gt;&gt;&gt; Thanking you,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; &#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43=
;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43=
;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43=
;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43=
;&#43;&#43;<br>
&gt;&gt;&gt;&gt;&gt; Abbreviations Used in The submitted Document<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; AH &nbsp; Authentication Header<br>
&gt;&gt;&gt;&gt;&gt; DAD &nbsp;Duplicate Address Detection<br>
&gt;&gt;&gt;&gt;&gt; DPD &nbsp;Duplicate Packet Detection<br>
&gt;&gt;&gt;&gt;&gt; DoS &nbsp;Denial of Service<br>
&gt;&gt;&gt;&gt;&gt; ESP &nbsp;Encapsulating Security Payload<br>
&gt;&gt;&gt;&gt;&gt; IP &nbsp; IPv4 or IPv6<br>
&gt;&gt;&gt;&gt;&gt; ICMP Internet Control Message Protocol<br>
&gt;&gt;&gt;&gt;&gt; IIB &nbsp;Interface Information Base<br>
&gt;&gt;&gt;&gt;&gt; ETX &nbsp;Estimated Expected number of Transmission<br=
>
&gt;&gt;&gt;&gt;&gt; FIB &nbsp;Forwarding Information Base<br>
&gt;&gt;&gt;&gt;&gt; LQI &nbsp;Link Quality Indicator<br>
&gt;&gt;&gt;&gt;&gt; L2 &nbsp; Data Link Layer (i.e. 2nd layer in ISO model=
)<br>
&gt;&gt;&gt;&gt;&gt; L3 &nbsp; Internet Layer (i.e. 3rd layer in ISO model)=
<br>
&gt;&gt;&gt;&gt;&gt; LLN &nbsp;Low power and Lossy Network<br>
&gt;&gt;&gt;&gt;&gt; MAC &nbsp;Mediam Access Control<br>
&gt;&gt;&gt;&gt;&gt; MIB &nbsp;Management Information Base<br>
&gt;&gt;&gt;&gt;&gt; MTU &nbsp;Maximum Transmission Unit<br>
&gt;&gt;&gt;&gt;&gt; NBMA Non-Broadcast Multi-Access link<br>
&gt;&gt;&gt;&gt;&gt; NHDP Neighborhood Discovery Protocol<br>
&gt;&gt;&gt;&gt;&gt; ND &nbsp; IP Neighbor Discovery<br>
&gt;&gt;&gt;&gt;&gt; OSPF Open Shortest Path First<br>
&gt;&gt;&gt;&gt;&gt; RIB &nbsp;Routing Information Base<br>
&gt;&gt;&gt;&gt;&gt; SMF &nbsp;Simplified Multicast Forwarding<br>
&gt;&gt;&gt;&gt;&gt; TCP &nbsp;Transmission Control Protocol<br>
&gt;&gt;&gt;&gt;&gt; UDP &nbsp;User Datagram Protocol<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; 2.3 Definitions for MANET Terms<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; 2.3.1 Terms Definition of MANET Communication:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Communications=92 Technology or Facility:<br>
&gt;&gt;&gt;&gt;&gt; The means employed by two or more devices/subsystems t=
o transfer<br>
&gt;&gt;&gt;&gt;&gt; and/or receive information between them in one way or =
two way<br>
&gt;&gt;&gt;&gt;&gt; communication. &nbsp;MANET communications often uses t=
he wireless<br>
&gt;&gt;&gt;&gt;&gt; transmission medium(s) and MAY use some wired mediums =
(e.g. free<br>
&gt;&gt;&gt;&gt;&gt; space, air, water, antenna, coaxial cables, etc.)<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Communication Medium:<br>
&gt;&gt;&gt;&gt;&gt; The transceiver system (e.g. such as L2 systems, IEEE8=
02.11 systems,<br>
&gt;&gt;&gt;&gt;&gt; satellite system, etc.) that the routing device uses t=
o communicates<br>
&gt;&gt;&gt;&gt;&gt; through the transmission medium(s), by providing conne=
ctionless and/or<br>
&gt;&gt;&gt;&gt;&gt; connection services that MAY be established. The syste=
m medium<br>
&gt;&gt;&gt;&gt;&gt; includes MAC layer and MAY include the physical Layer.=
<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Communication Channel:<br>
&gt;&gt;&gt;&gt;&gt; A subdivision of the physical communication medium (i.=
e. radio carrier<br>
&gt;&gt;&gt;&gt;&gt; signal bandwidth, or the system bandwidth) allowing po=
ssibly shared<br>
&gt;&gt;&gt;&gt;&gt; independent uses of the medium. Channels may be made a=
vailable by<br>
&gt;&gt;&gt;&gt;&gt; subdividing the medium into; distinct time slots, dist=
inct spectral<br>
&gt;&gt;&gt;&gt;&gt; bands, or coding sequence, etc.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; MANET Protocol:<br>
&gt;&gt;&gt;&gt;&gt; The communication system/subsystem that operates and m=
aintains the<br>
&gt;&gt;&gt;&gt;&gt; ad hoc communication technology or facility within MAN=
ET. MANET routing<br>
&gt;&gt;&gt;&gt;&gt; Protocols often apply distributed algorithms/technique=
s to disseminate<br>
&gt;&gt;&gt;&gt;&gt; or forward routing messages within a MANET routing dom=
ain.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Topology:<br>
&gt;&gt;&gt;&gt;&gt; An abstract representation of a network (physical or l=
ogical), as a<br>
&gt;&gt;&gt;&gt;&gt; graph (G) whose topology is defined by a set of router=
s/bridges (V)<br>
&gt;&gt;&gt;&gt;&gt; that<br>
&gt;&gt;&gt;&gt;&gt; communicate through set of links (E), where the G =3D =
(V, E).<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Physical-level Topology:<br>
&gt;&gt;&gt;&gt;&gt; A topology of the communication medium networks consis=
ts of routing<br>
&gt;&gt;&gt;&gt;&gt; devices and physical links. This topology information =
is updated by<br>
&gt;&gt;&gt;&gt;&gt; devices=92 technology in the L2 information Base.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Network-level Topology:<br>
&gt;&gt;&gt;&gt;&gt; A topology of the communication system networks consis=
ts of routers and<br>
&gt;&gt;&gt;&gt;&gt; links. This topology information is updated by routers=
 in its RIB.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Multihop MANET:<br>
&gt;&gt;&gt;&gt;&gt; A MANET that its node(s) MAY need(s) more than one IP =
hop to reach the<br>
&gt;&gt;&gt;&gt;&gt; destination.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Reactive Routing:<br>
&gt;&gt;&gt;&gt;&gt; An on-demand based routing protocol that operates rout=
e discover and<br>
&gt;&gt;&gt;&gt;&gt; maintainance the route(s), to reach the demanded desti=
nation(s).<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Proactive Routing:<br>
&gt;&gt;&gt;&gt;&gt; A topology RIB based routing protocol that operates ro=
utes and<br>
&gt;&gt;&gt;&gt;&gt; maintains<br>
&gt;&gt;&gt;&gt;&gt; the network topology, to reach its known destination(s=
). Each router<br>
&gt;&gt;&gt;&gt;&gt; maintains routes to all reachable destinations at all =
times, whether or<br>
&gt;&gt;&gt;&gt;&gt; not there is currently any demand to deliver packets t=
o those<br>
&gt;&gt;&gt;&gt;&gt; destinations.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Upper Layer:<br>
&gt;&gt;&gt;&gt;&gt; a protocol layer above IP layer (e.g. as TCP, UDP, OSP=
F).<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; MANET Domain: TBD<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; MANET Signaling:<br>
&gt;&gt;&gt;&gt;&gt; Sending and exchanging some MANET messages/information=
.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; 2.3.2 Terms Definition of MANET Elements<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Node:<br>
&gt;&gt;&gt;&gt;&gt; A device/subsystem that MUST implement IP and SHOULD p=
articipate in<br>
&gt;&gt;&gt;&gt;&gt; MANET signaling. It either runs a MANET routing protoc=
ol or participate<br>
&gt;&gt;&gt;&gt;&gt; in MANET signaling.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Router:<br>
&gt;&gt;&gt;&gt;&gt; A MANET node that MUST implement a MANET routing proto=
col and forwards<br>
&gt;&gt;&gt;&gt;&gt; IP packets not explicitly addressed to itself.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Host:<br>
&gt;&gt;&gt;&gt;&gt; A node that is not a router. All destinations in MANET=
 that receive<br>
&gt;&gt;&gt;&gt;&gt; delivered data are hosts.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Link:<br>
&gt;&gt;&gt;&gt;&gt; A link between two node interfaces. This link may be L=
ogical<br>
&gt;&gt;&gt;&gt;&gt; (i.e. virtual) link or physical link. Logical links ar=
e between two<br>
&gt;&gt;&gt;&gt;&gt; logical interfaces and physical links are between two =
physical<br>
&gt;&gt;&gt;&gt;&gt; interfaces. Links are either unidirectional or bidirec=
tional<br>
&gt;&gt;&gt;&gt;&gt; (links may be on-link and off-link: see RFC4861).<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Physical Link:<br>
&gt;&gt;&gt;&gt;&gt; a communication facility or medium over which the node=
s can<br>
&gt;&gt;&gt;&gt;&gt; communicate at the link layer, i.e., the layer immedia=
tely below<br>
&gt;&gt;&gt;&gt;&gt; IP. Physical interfaces are the nodes=92 attachment to=
 physical links.<br>
&gt;&gt;&gt;&gt;&gt; Physical Link types are point-to-point, NBMA, multicas=
t capable,<br>
&gt;&gt;&gt;&gt;&gt; and shared-media, etc (see link types in ND [RFC4861])=
.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Logical (virtual) Link:<br>
&gt;&gt;&gt;&gt;&gt; a communication facility (at L3, or upper-layer) over =
which nodes can<br>
&gt;&gt;&gt;&gt;&gt; communicate. This logical link is between two MANET in=
terfaces exists<br>
&gt;&gt;&gt;&gt;&gt; if either can be heard by the other.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Link MTU:<br>
&gt;&gt;&gt;&gt;&gt; the maximum transmission unit (i.e. maximum unit size =
in octets), that<br>
&gt;&gt;&gt;&gt;&gt; can be conveyed in one transmission unit over the link=
.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Node Interface:<br>
&gt;&gt;&gt;&gt;&gt; A node's point of attachment to a link. Each node MUST=
 have at least<br>
&gt;&gt;&gt;&gt;&gt; one<br>
&gt;&gt;&gt;&gt;&gt; interface that SHOULD be assigned an IP address. If th=
ere is/are more<br>
&gt;&gt;&gt;&gt;&gt; than one interface(s) per node then the additional int=
erface(s) MAY be<br>
&gt;&gt;&gt;&gt;&gt; assigned an IP address. If an interface is not assigne=
d to an IP<br>
&gt;&gt;&gt;&gt;&gt; address<br>
&gt;&gt;&gt;&gt;&gt; it MUST be identified by the MANET routing protocol. A=
n interface MAY<br>
&gt;&gt;&gt;&gt;&gt; be<br>
&gt;&gt;&gt;&gt;&gt; assigned one or more addresses.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; MANET Interface:<br>
&gt;&gt;&gt;&gt;&gt; A node interface that participate in; exchange MANET i=
nformation used<br>
&gt;&gt;&gt;&gt;&gt; in<br>
&gt;&gt;&gt;&gt;&gt; MANET routing or exchange information in MANET neighbo=
r node discovery<br>
&gt;&gt;&gt;&gt;&gt; (e.g as the term used in RFC6130). A MANET interface M=
UST be assigned<br>
&gt;&gt;&gt;&gt;&gt; to<br>
&gt;&gt;&gt;&gt;&gt; least one &nbsp;address to communicate. A router inter=
face MUST be<br>
&gt;&gt;&gt;&gt;&gt; assigned a routable address which is the main address =
for the<br>
&gt;&gt;&gt;&gt;&gt; interface.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; 2.3.3 Terms Definition of MANET Identifications:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; An interface MAY be assigned one or more addresses. If=
 the interface is<br>
&gt;&gt;&gt;&gt;&gt; a logical interface it MAY be assigned to only logical=
 addresses, but<br>
&gt;&gt;&gt;&gt;&gt; if<br>
&gt;&gt;&gt;&gt;&gt; it is a physical interface MAY be assigned with physic=
al address<br>
&gt;&gt;&gt;&gt;&gt; (e.g. MAC address) and/or logical address(es) (e.g. IP=
 addresses,<br>
&gt;&gt;&gt;&gt;&gt; MANET addresses).<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; MANET Address<br>
&gt;&gt;&gt;&gt;&gt; A MANET-subnet, node, or interface address. Node and i=
nterface<br>
&gt;&gt;&gt;&gt;&gt; addresses<br>
&gt;&gt;&gt;&gt;&gt; are either IP addresses or RFC5444 addresses. All subn=
et addresses are<br>
&gt;&gt;&gt;&gt;&gt; unicast IP addresses.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Address Block and TLV: as specified in RFC5444<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Routable address:<br>
&gt;&gt;&gt;&gt;&gt; A subnet address which can be a destination address. A=
 router MUST be<br>
&gt;&gt;&gt;&gt;&gt; able to distinguish a routable address from a non-rout=
able address.<br>
&gt;&gt;&gt;&gt;&gt; Broadcast, and multicast addresses, limited in scope t=
o less than the<br>
&gt;&gt;&gt;&gt;&gt; entire MANET, MUST NOT be considered as routable addre=
sses. Anycast<br>
&gt;&gt;&gt;&gt;&gt; addresses MAY be considered as routable addresses.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Main address<br>
&gt;&gt;&gt;&gt;&gt; A routable address (MANET address) that is assigned to=
 one router's<br>
&gt;&gt;&gt;&gt;&gt; MANET interface.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Originator address:<br>
&gt;&gt;&gt;&gt;&gt; A node address of the node that originated a MANET mes=
sage (this<br>
&gt;&gt;&gt;&gt;&gt; message<br>
&gt;&gt;&gt;&gt;&gt; MUST include the originator address). It MAY be a rout=
able or an<br>
&gt;&gt;&gt;&gt;&gt; unroutable address.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; subnet prefix<br>
&gt;&gt;&gt;&gt;&gt; A bit string that consists of some number of initial b=
its of an IP<br>
&gt;&gt;&gt;&gt;&gt; address.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Interface identifier<br>
&gt;&gt;&gt;&gt;&gt; the remaining low-order bits in the node's IP address =
after the subnet<br>
&gt;&gt;&gt;&gt;&gt; prefix. A number used to identify a node's interface o=
n a link.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; 2.3.4 Terms Definition of MANET exchange information f=
ormats:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Packet:<br>
&gt;&gt;&gt;&gt;&gt; A MANET packet of a header plus payload. These packets=
 are either<br>
&gt;&gt;&gt;&gt;&gt; IP packets or RFC5444 packets. RFC5444 packet MUST be =
encapsulated<br>
&gt;&gt;&gt;&gt;&gt; in IP packet. Packets are generated by nodes to be sen=
t to<br>
&gt;&gt;&gt;&gt;&gt; destination(s) through MANET or through the Internet. =
RFC5444 packets<br>
&gt;&gt;&gt;&gt;&gt; information MAY not be used only by MANET routers.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Message:<br>
&gt;&gt;&gt;&gt;&gt; A MANET data message or routing control message. Routi=
ng control<br>
&gt;&gt;&gt;&gt;&gt; messages are either MANET routing protocol messages or=
/and RFC5444<br>
&gt;&gt;&gt;&gt;&gt; messages.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Type Length Value coding (TLV):<br>
&gt;&gt;&gt;&gt;&gt; A generic way to represent MANET information (as in [R=
FC5444] and<br>
&gt;&gt;&gt;&gt;&gt; [RFC5497]).<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Frame:<br>
&gt;&gt;&gt;&gt;&gt; A L2 protocol TLV with a header and payload. In some t=
echnologies the<br>
&gt;&gt;&gt;&gt;&gt; L2<br>
&gt;&gt;&gt;&gt;&gt; operates a MANET routing protocol as a local area netw=
orking system.<br>
&gt;&gt;&gt;&gt;&gt; Frames MAY encapsulate MANET packets to be tunneled th=
rough a<br>
&gt;&gt;&gt;&gt;&gt; telecommunication network.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Route Request Message (RREQ)<br>
&gt;&gt;&gt;&gt;&gt; A message is used to discover a valid route to a parti=
cular<br>
&gt;&gt;&gt;&gt;&gt; destination address, called the RREQ Target Node. When=
 a router<br>
&gt;&gt;&gt;&gt;&gt; processes a RREQ it learns routing information on how =
to Originator<br>
&gt;&gt;&gt;&gt;&gt; Node.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Route Reply Message (RREP)<br>
&gt;&gt;&gt;&gt;&gt; A message is used to disseminate routing information a=
bout<br>
&gt;&gt;&gt;&gt;&gt; the RREP Target Node to the RREQ Originator Node and t=
he intermediate<br>
&gt;&gt;&gt;&gt;&gt; routers.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Route Error Message (RERR)<br>
&gt;&gt;&gt;&gt;&gt; A message is used to disseminate the information that =
a route is<br>
&gt;&gt;&gt;&gt;&gt; not available for one or more particular addresses. A =
RERR message is<br>
&gt;&gt;&gt;&gt;&gt; used to indicate that a router does not have a forward=
ing route<br>
&gt;&gt;&gt;&gt;&gt; to one or more particular addresses.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; 2.3.5 Terms Definition Related to MANET Protocol Opera=
tion:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Hop-by-hop Routing: (TBD)<br>
&gt;&gt;&gt;&gt;&gt; A dynamic routing that routes to destination by routin=
g table.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Source Routing: (TBD)<br>
&gt;&gt;&gt;&gt;&gt; A dynamic routing that its route path is provided in t=
he IP packet.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Route Discovery: TBD<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Route Maintenance: TBD<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Neighbor discovery: (TBD)<br>
&gt;&gt;&gt;&gt;&gt; A node discovers neighbors only if the node receives f=
rom it's<br>
&gt;&gt;&gt;&gt;&gt; neighbors.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Multipoint relay (MPR): (TBD)<br>
&gt;&gt;&gt;&gt;&gt; A router X1 is an MPR for a router Y1, if router Y1 ha=
s indicated<br>
&gt;&gt;&gt;&gt;&gt; its selection of router X1 as an MPR in a recent HELLO=
 message.<br>
&gt;&gt;&gt;&gt;&gt; Router X1 may be a flooding MPR for Y1 if it is indica=
ted to<br>
&gt;&gt;&gt;&gt;&gt; participate in the flooding process of messages receiv=
ed from<br>
&gt;&gt;&gt;&gt;&gt; router Y1, or it may be a routing MPR for Y1, if it is=
 indicated to<br>
&gt;&gt;&gt;&gt;&gt; declare link-state information for the link from X1 to=
 Y1. It may<br>
&gt;&gt;&gt;&gt;&gt; also be both at the same time.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; MPR selector:<br>
&gt;&gt;&gt;&gt;&gt; A router, Y, is a flooding/routing MPR selector of rou=
ter X if<br>
&gt;&gt;&gt;&gt;&gt; router Y has selected router X as a flooding/routing M=
PR.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Router Parameters:<br>
&gt;&gt;&gt;&gt;&gt; boolean or numerical values, specified for each router=
, and not<br>
&gt;&gt;&gt;&gt;&gt; specific to an interface. A router MAY change router p=
arameter<br>
&gt;&gt;&gt;&gt;&gt; values at any time, subject to some MANET constraints.=
<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; MANET Routing Metric:<br>
&gt;&gt;&gt;&gt;&gt; A MANET routing cost that is governed by specific rule=
s and properties<br>
&gt;&gt;&gt;&gt;&gt; defined by the MANET routing protocol which captures s=
pecific link or<br>
&gt;&gt;&gt;&gt;&gt; node characteristics. Examples of basic metrics are ho=
p-count, ETX,<br>
&gt;&gt;&gt;&gt;&gt; LQI,<br>
&gt;&gt;&gt;&gt;&gt; etc.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Distance Vector Metric<br>
&gt;&gt;&gt;&gt;&gt; A metric class related to rules of the MANET interface=
 and MANET path<br>
&gt;&gt;&gt;&gt;&gt; distance. The metric can be calculated by the distance=
 vector routing<br>
&gt;&gt;&gt;&gt;&gt; algorithm class used by the MANET routing protocol. A =
metric of the<br>
&gt;&gt;&gt;&gt;&gt; distance a message or piece of information has travers=
ed. The minimum<br>
&gt;&gt;&gt;&gt;&gt; value of distance is the number of IP hops traversed.<=
br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Link State Metric<br>
&gt;&gt;&gt;&gt;&gt; A metric type related to the MANET network-topology st=
atus and logical<br>
&gt;&gt;&gt;&gt;&gt; links' states. This metric is calculated by the link s=
tate routing<br>
&gt;&gt;&gt;&gt;&gt; algorithm class used by the MANET routing protocol. A =
metric type maybe<br>
&gt;&gt;&gt;&gt;&gt; EXT, LQL, etc.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Link Metric: TBD<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Neighbor Metric: TBD<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Path accumulated:<br>
&gt;&gt;&gt;&gt;&gt; The RREQ message accumulates intermediate routers that=
 are in path to<br>
&gt;&gt;&gt;&gt;&gt; destination(s).<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Protocol Sequence Number:<br>
&gt;&gt;&gt;&gt;&gt; A Sequence Number related to a MANET protocol that mai=
ntained by each<br>
&gt;&gt;&gt;&gt;&gt; protocol subsystem process. This sequence number is us=
ed by other<br>
&gt;&gt;&gt;&gt;&gt; subsystems to identify the temporal order of protocol =
information<br>
&gt;&gt;&gt;&gt;&gt; generated.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Router Sequence Number:<br>
&gt;&gt;&gt;&gt;&gt; A router sequence number is maintained by each router =
process. The<br>
&gt;&gt;&gt;&gt;&gt; sequence number is used by other routers to identify t=
he temporal<br>
&gt;&gt;&gt;&gt;&gt; order of routing information generated and ensure loop=
-free routes.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; MANET Information Base:<br>
&gt;&gt;&gt;&gt;&gt; A collection of information (in Table or Cache structu=
re) maintained<br>
&gt;&gt;&gt;&gt;&gt; by MANET protocols and which is to be made available t=
o MANET routing<br>
&gt;&gt;&gt;&gt;&gt; protocols. An Information Base may be associated with =
a MANET router<br>
&gt;&gt;&gt;&gt;&gt; or with MANET interface (e.g. route request table, IIB=
, RIB, FIB, MIB).<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; RIB Entry:<br>
&gt;&gt;&gt;&gt;&gt; The RIB entry is a conceptual data structure. Implemen=
tations may use<br>
&gt;&gt;&gt;&gt;&gt; any internal representation that conforms to the seman=
tics of a route<br>
&gt;&gt;&gt;&gt;&gt; as specified in the router specification.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; 3. IP Considerations and Terminology<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; All MANET nodes MUST implement IP and all MANET router=
s MUST<br>
&gt;&gt;&gt;&gt;&gt; run/implement &nbsp;at least one MANET routing protoco=
l. The<br>
&gt;&gt;&gt;&gt;&gt; terminologies described in this document can be used f=
or<br>
&gt;&gt;&gt;&gt;&gt; IPv4-MANET and IPv6-MANET. The IPv4 addresses MAY be u=
sed in IPv6<br>
&gt;&gt;&gt;&gt;&gt; packets but IPv6 addresses MUST not be in IPv4 packets=
.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; IP address:<br>
&gt;&gt;&gt;&gt;&gt; IPv4 addresses or IPv6 addresses.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; IP Packet:<br>
&gt;&gt;&gt;&gt;&gt; The packet header plus payload as specified in [RFC791=
] and [RFC2460]<br>
&gt;&gt;&gt;&gt;&gt; for IPv4 and IPv6 respectively. It can encapsulate RFC=
5444 packets as<br>
&gt;&gt;&gt;&gt;&gt; specified by RFC5498.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Mobile IP considerations:<br>
&gt;&gt;&gt;&gt;&gt; Mobile IP terms are provided in [RFC6275], and this te=
chnology<br>
&gt;&gt;&gt;&gt;&gt; assists nodes while connected through the Internet dom=
ain(s). MANET<br>
&gt;&gt;&gt;&gt;&gt; is an infrastructure-less network that is able to comm=
unicate with<br>
&gt;&gt;&gt;&gt;&gt; the Internet (i.e. an IP infrastructure network).<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; 4. Security Consideration and Terminology<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; It is RECOMMENDED that MANET routing protocols conside=
r security<br>
&gt;&gt;&gt;&gt;&gt; issues because the MANET's transmission medium is wire=
less which make<br>
&gt;&gt;&gt;&gt;&gt; it vulnerable to attacks [ANJUM][RFC4593]. In some sit=
uations the<br>
&gt;&gt;&gt;&gt;&gt; routing information while traversing the MANET MAY be =
used by an<br>
&gt;&gt;&gt;&gt;&gt; intruder node, to obtain MANET data traffic or/and att=
ack the MANET<br>
&gt;&gt;&gt;&gt;&gt; [HERBERG]. Forwarding protocols that use DPD technique=
s MAY be<br>
&gt;&gt;&gt;&gt;&gt; vulnerable to DoS attacks such as [RFC6621]. MANETs MA=
Y be secured<br>
&gt;&gt;&gt;&gt;&gt; by using IPsec, AH, DAD, and ESP techniques, and other=
. However,<br>
&gt;&gt;&gt;&gt;&gt; it is RECOMMENDED that MANET detects attackers and pos=
sible threats.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; The following are some terminology related to MANET th=
reats and<br>
&gt;&gt;&gt;&gt;&gt; security.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Attacker: A node, present in the network and which int=
entionally seeks<br>
&gt;&gt;&gt;&gt;&gt; to compromise information based in MANET router(s). Th=
e Attacker MAY be<br>
&gt;&gt;&gt;&gt;&gt; a compromised MANET router if obtained MANET identity =
or routing<br>
&gt;&gt;&gt;&gt;&gt; information.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Compromised MANET Router: An attacker router, present =
in MANET and<br>
&gt;&gt;&gt;&gt;&gt; which generates syntactically correct routing control =
messages. Control<br>
&gt;&gt;&gt;&gt;&gt; messages emitted by compromised router(s) may contain =
additional<br>
&gt;&gt;&gt;&gt;&gt; information, or omit information, as compared to a con=
trol message<br>
&gt;&gt;&gt;&gt;&gt; generated by a non-compromised router located in the s=
ame MANET<br>
&gt;&gt;&gt;&gt;&gt; topological position.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Legitimate MANET Router: A MANET router, which is not =
a Compromised<br>
&gt;&gt;&gt;&gt;&gt; MANET Router.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Jamming Attack:<br>
&gt;&gt;&gt;&gt;&gt; The attacker transmits massive amounts of interfering =
radio traffic,<br>
&gt;&gt;&gt;&gt;&gt; which will prevent legitimate traffic (e.g., routing a=
nd data traffic)<br>
&gt;&gt;&gt;&gt;&gt; on all or part of the MANET. Indirect jamming attacks =
MAY occur by<br>
&gt;&gt;&gt;&gt;&gt; influencing Legitimate MANET Router to transmit unnece=
ssary<br>
&gt;&gt;&gt;&gt;&gt; information.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Eavesdropping:<br>
&gt;&gt;&gt;&gt;&gt; Obtaining a copy by the attacker of the transmitted MA=
NET routing<br>
&gt;&gt;&gt;&gt;&gt; information or the transmitted data information from i=
ts neighbor's<br>
&gt;&gt;&gt;&gt;&gt; transmitted radio packet. Attacker=92s processes MANY =
be used by attacker<br>
&gt;&gt;&gt;&gt;&gt; to mislead routing. Eavesdropping does not pose a dire=
ct threat to the<br>
&gt;&gt;&gt;&gt;&gt; MANET or to its routing.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Identity Spoofing:<br>
&gt;&gt;&gt;&gt;&gt; Attacker sends routing messages, pretending to have th=
e MANET identity<br>
&gt;&gt;&gt;&gt;&gt; of another node.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Link Spoofing:<br>
&gt;&gt;&gt;&gt;&gt; Compromised MANET router sends routing messages to nei=
ghbor node(s)<br>
&gt;&gt;&gt;&gt;&gt; providing incorrect set of link information.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Replay Attack:<br>
&gt;&gt;&gt;&gt;&gt; A Compromised router in one MANET region records contr=
ol traffic<br>
&gt;&gt;&gt;&gt;&gt; information and replays the recorded information in a =
different MANET<br>
&gt;&gt;&gt;&gt;&gt; region (this type of attack is also called the Wormhol=
e attack).<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Broadcast Storm:<br>
&gt;&gt;&gt;&gt;&gt; Compromised MANET router may attack the MANET by attem=
pting to change<br>
&gt;&gt;&gt;&gt;&gt; the MANET flooding algorithm(s) to increase routing ov=
erheads or/and to<br>
&gt;&gt;&gt;&gt;&gt; increase the route discovery delay. Broadcast storm de=
grades the data<br>
&gt;&gt;&gt;&gt;&gt; traffic delivery and MANET performance.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Falsification in MANET:<br>
&gt;&gt;&gt;&gt;&gt; The compromised MANET router sends false routing infor=
mation into<br>
&gt;&gt;&gt;&gt;&gt; MANET.<br>
&gt;&gt;&gt;&gt;&gt; False routing information received in MANET, MAY creat=
e unrealistic<br>
&gt;&gt;&gt;&gt;&gt; information bases.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; ICMP Attacks:<br>
&gt;&gt;&gt;&gt;&gt; The generation of ICMPv6 error messages may be used by=
 compromised<br>
&gt;&gt;&gt;&gt;&gt; MANET<br>
&gt;&gt;&gt;&gt;&gt; router to attempt DoS attacks by sending an error-caus=
ing source<br>
&gt;&gt;&gt;&gt;&gt; routing<br>
&gt;&gt;&gt;&gt;&gt; header in back-to-back datagrams. As the ICMP messages=
 are passed to<br>
&gt;&gt;&gt;&gt;&gt; the<br>
&gt;&gt;&gt;&gt;&gt; upper-layer processes, it is possible to perform attac=
ks on the upper<br>
&gt;&gt;&gt;&gt;&gt; layer protocols (e.g., UDP, TCP). Protocols at the upp=
er layers are<br>
&gt;&gt;&gt;&gt;&gt; RECOMMENDED to perform some form of validation to ICMP=
 messages (using<br>
&gt;&gt;&gt;&gt;&gt; the information contained in the payload of the ICMP m=
essage) before<br>
&gt;&gt;&gt;&gt;&gt; acting upon them.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Source Routing Attacks: TBD<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Acknowledgments:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; This work has used/modified terms of the following doc=
uments: RFC2462,<br>
&gt;&gt;&gt;&gt;&gt; RFC2501, RFC3561, RFC3626, RFC3753, RFC4728, RFC4861, =
RFC5444,<br>
&gt;&gt;&gt;&gt;&gt; RFC6130, &nbsp;RFC6621, [AODVv2], [OLSRv2], and [HERBE=
RG],<br>
&gt;&gt;&gt;&gt;&gt; Gratefully acknowledge to the IETF community and all c=
ontributions.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Reference:<br>
&gt;&gt;&gt;&gt;&gt; [HERBERG] Herberg, U., Yi, J., Clausen, T.,&quot;Secur=
ity Threats for<br>
&gt;&gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; NHDP&quot;, Work in=
 progress, March, 2012.<br>
&gt;&gt;&gt;&gt;&gt; [ANJUM] &nbsp; Anjum, F. and Mouchtaris, P. &quot;Secu=
rity for Wireless Ad Hoc<br>
&gt;&gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Networks&quot;, Joh=
n Wiley &amp; Sons, March 2007.<br>
&gt;&gt;&gt;&gt;&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ISBN: 978-0-471-756=
88-0.<br>
&gt;&gt;&gt;&gt;&gt; &#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43=
;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43=
;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43=
;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43;&#43=
;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; I hope to get some advise from the Internet community =
to make the<br>
&gt;&gt;&gt;&gt;&gt; definitions more suitable/accurate, because I MAY misu=
nderstood.<br>
&gt;&gt;&gt;&gt;&gt; Thanking you,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Best Regards<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Abdussalam Baryun<br>
&gt;&gt;&gt;&gt;&gt; University of Glamorgan, UK<br>
&gt;&gt;&gt;&gt;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br>
&gt; _______________________________________________<br>
&gt; manet mailing list<br>
&gt; <a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/manet</a><br>
<br>
_______________________________________________<br>
manet mailing list<br>
<a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/manet</a><br>
</blockquote>
</div>
<br>
<br clear=3D"all">
<br>
-- <br>
Dan He<br>
---------------------<br>
Tel: &#43;44-788-686-3428<br>
<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>

--_000_0261930938C04F608814E680A4894F33ciscocom_--
