Re: IESG Review: draft-ietf-seamoby-mobility-terminology (Re: ID Tracker State Update Notice)

Thierry Ernst <[email protected]> Fri, 21 Nov 2003 15:24:12 +0900

Newsgroups	gmane.ietf.seamoby
Organization	Keio University
Message-ID	<[email protected]>

Hi,

A few more minor comments, if it's not too late:

- I would add "HoA" next to the term "Home Address" as this is done in
Care-of Address (CoA).

- a question concerning the term "link" was left unanswered. I attach
the mail. I also had interest into clarifying.

- a definition about what a subnet is may be useful since the term is
used in many places in the document.

- Mobile Node (MN)
       An IP node capable of changing its point of attachment to the
       network. A Mobile Node may or may not have forwarding
       functionality.

  -> I would add "MR" and "MH" in it:       

      An IP node capable of changing its point of attachment to the     
      network. A Mobile Node may either be a Mobile Host (no forwarding
      functionality) or a Mobile Router (forwarding functionality).

      or mention something about forwarding functionality in defs of MH and MR.

- Mobile Host (MH) 
  "....  A Mobile host..." -> capitalize Host.

- Mobile Router (MR)    

  In the middle paragraph, I would recommend to move the sentence about
"ingress interface" and the one about "egress interfaces" as standalones
definitions. Those 2 terms are extensively used in NEMO WG. The last
paragraph shall be kept under the definition of MR.

- Network mobility
  -> I would add something similar to first sentence of "host mobility"

  refers to the function of allowing an entire network to change its    
 point of attachment to the network, and thus its reachability in the
topology, without interrupting IP packet delivery to/from that mobile network.

And, as long as we are using the term "function" into the definition of
either "host mobility" or "network mobility", it would make sense to add
the word "support" to both terms:

-> replace "Host Mobility" with "Host Mobility Support" and "Network
Mobility" with "Network Mobility Support".

E.g: I don't have any support function on my laptop, so by doing host
mobility I cannot maintain sessions. It's the fact that I do have "host
mobility support" abilities that my sessions do not break.


Thierry.

link-definition.txt (text/plain, 3.5 KB)

Message-ID: <[email protected]>
Date: Thu, 04 Sep 2003 22:28:44 +0900
From: Nicolas Montavont <[email protected]>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030727 Thunderbird/0.1
MIME-Version: 1.0
To: [email protected]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Seamoby] Question on link definition
Sender: [email protected]
Errors-To: [email protected]
Precedence: bulk

Hi,

I have a question about the definition of "link" in

draft-ietf-seamoby-mobility-terminology-04.txt

It is said:

"A communication facility or physical medium that can sustain data
communications between multiple network nodes, such as an
Ethernet (simple or bridged). A link is the layer immediately
below IP."

As I undestand, the definition of link is not directly related to an 
IPv6 link.
For example, consider the following example:

One ethernet link where a router advertises a single IPv6 prefix, and an 
802.11b access point connected to this ethernet link as illustrated here:

         AR
   ____ |__________________
                |                         |
             AP                     Fixed node
                         MN2
 MN1          

In this situation, is it right to say that :
    - there are 2 links
and
    - there is one IPv6 link
?

Thanks

Regards,
Nicolas

_______________________________________________
Seamoby mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/seamoby