Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

#80 closed defect (fixed)

Change "IP Link" to "IP Domain"

Reported by: kempf@… Owned by: kempf@…
Priority: major Milestone:
Component: nohost-ps Severity:
Keywords: PS draft Cc: netlmm@…


Fred Templin suggests:

6) Section 1.1, the term "IP link" is confusing even if it is defined only within the scope of this document. From the definitions in RFC2461 and RFC3753, the term "link" is well understood and clearly refers to something that occurs below the IP layer. (IP-in-IP tunnels can be "links", but that doesn't seem like what you are trying to capture here.)

Suggest using a different term such as "IP domain" defined as:

"IP domain

A set of routers, mobile nodes, and wireless access points connected by links that share the same IP subnet prefixes. This definition covers one or more access points connected by one or more links under one or more access routers."

Suggest also changing the term "IP Link" to "IP Domain" throughout the rest of the document. Alternative would be to call it a "localized mobility management domain", since the meaning is the same and this terminolgy is used elsewhere in the document.

and later: 9) Section 1.1, definition for "Intra-Link Mobility", suggest

changing this term to "Intra-Domain Mobility" (see also 6) above) defined as:

"Intra-Domain Mobility

mobility between wireless access points and/or access routers within an IP domain. Typically, movement between access points only involves Layer 2 mechanisms, but may also involve IP signaling for movement between access points attached to different links. No IP configuration change is required upon movement within an IP domain since the IP prefixes do not change, but some IP signaling may be required for the mobile node to confirm whether the change in access point also resulted in a change of IP domain."

10) Section 2.0, in figure 1 and the two paragraphs that immediately follow, change "local mobility" to "intra-domain mobility". (See also 6) and 9) above).

Change History (4)

comment:1 Changed 13 years ago by kempf@…

  • Status changed from new to assigned

"Domain" in IETF documents typically refers to a broader area than is covered by a set of last hop IPv6 subnet prefixes. For example, a DNS domain (since DNS stands for Domain Name System). DNS domains don't cover just one link typically. A DHCP domain is defined in RFC 3315 to cover multiple links (Section 4.2). What the IP link definintion in PS is intended to capture is the last hop link covered in IPv6 by multiple subnet prefixes but which only consists of non-routing nodes or mobile routers that are mobility-managed as nodes. In IPv4 there would be no confusion, because a link is always only covered by a single subnet prefix, so the term "subnet" could be used. The definition is not intended to cover the entire topological graph managed by the NETLMM mobility anchor. That is a "LMM domain" or "NETLMM domain" because in that case, the usage of the word "domain" more closely matches the traditional IETF usage, multiple links managed somehow by a single protocol or system.

That said, the current definition is heavily premised on the functional equivalent of broadcast, which includes NBMA networks such as ATM. It would rule out point to point networks, and that is probably not such a good idea because some wireless link protocols, like the cellular protocols, do in fact operate much like point to point links.

Looking through the uses of the term "IP link" in the document, it seems as if the usage could be replaced by the standard term of "link" in most cases and in others, where the term "IP link" is used as an adjective, with the appropriate term, either "IP" or "link".

Recommendation is to remove the definition of "IP Link" from Section 1.1 and substitute "link" or "IP" where appropriate throughout the document.

comment:2 Changed 13 years ago by kempf@…

  • version changed from 1.0 to 2.0

comment:3 Changed 13 years ago by kempf@…

  • Resolution set to fixed
  • Status changed from assigned to closed

comment:4 Changed 12 years ago by anonymous

  • Milestone milestone2 deleted

Milestone milestone2 deleted

Note: See TracTickets for help on using tickets.