RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 4640, "Problem Statement for bootstrapping Mobile IPv6 (MIPv6)", September 2006

Source of RFC: mip6 (int)

Errata ID: 36

Status: Verified
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2006-11-01
Verifier Name: Brian Haberman
Date Verified: 2012-05-11

Section 12 says:

   [RFC3776]     Galvin, J., "IAB and IESG Selection, Confirmation, and
                 Recall Process: Operation of the Nominating and Recall
                 Committees", BCP 10, RFC 3777, June 2004.

It should say:

   [RFC3776]     Arkko, J., Devarapalli, V., and F. Dupont, "Using IPsec to 
                 Protect Mobile IPv6 Signaling Between Mobile Nodes and Home 
                 Agents", RFC 3776, June 2004.

Notes:

In Section 12, near the bottom of page 20, a strange accident must
have hit the Ref. tagged [RFC3776]. This indeed should be a citation of the Mobile IP related RFC 3776, but it is a citiation of the unrelated RFC 3777.

Status: Held for Document Update (1)

RFC 4640, "Problem Statement for bootstrapping Mobile IPv6 (MIPv6)", September 2006

Source of RFC: mip6 (int)

Errata ID: 811

Status: Held for Document Update
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2006-11-01
Held for Document Update by: Brian Haberman

 


(1)  typo/grammar

On page 3 of RFC 4640, the seconf paragraph of Section 1.2 says:

   Typically, bootstrapping happens when a mobile node does not have all
   the information it needs to set up the Mobile IPv6 service.  This
   includes, but is not limited to, situations in which the mobile node
   does not having any information when it boots up for the first time
   (out of the box), or does not retain any information during reboots.

It should say:

   Typically, bootstrapping happens when a mobile node does not have all
   the information it needs to set up the Mobile IPv6 service.  This
   includes, but is not limited to, situations in which the mobile node
|  does not have any information when it boots up for the first time
   (out of the box), or does not retain any information during reboots.


(2)  missing line break

Near the end of Section 1.3, on page 5, there should be an additional
blank line above the term "Home Mobility Service Provider".


(3)  typo

On page 6, the last sub-bullet of the first bulleted list in Section 3
says:

      *  IPsec Security Association (SA) between MN and HA, Intenet Key
         Exchange Protocol (IKE) pre-shared secret between MN and HA

It should say:
                                                                v
|     *  IPsec Security Association (SA) between MN and HA, Internet Key
         Exchange Protocol (IKE) pre-shared secret between MN and HA


(4)  grammar (singluar/plural mismatch)

The first sentence of Section 5.1.3, on page 9, says:
                                                      vv
|  The home agent discovery protocol does not support an "opportunistic"
|  or local discovery mechanisms in an ASP's local access network.  [..]
                               ^
It either should say:

   The home agent discovery protocol does not support an "opportunistic"
|  or local discovery mechanism in an ASP's local access network.  [..]

or it should say:

|  The home agent discovery protocol does not support "opportunistic" or
   local discovery mechanisms in an ASP's local access network.  [..]

Please decide what was intended.


(5)  missing articles

The last paragraph of Section 5.3.1, on page 11, says:

   Bootstrapping does not explicitly try to solve this problem of home
   network renumbering when MN is in dormant mode.  If the MN can
   configure itself after it 'comes back on' by reinitiating the
   bootstrapping process, then network renumbering problem is fixed as a
   side effect.

It should better say:

   Bootstrapping does not explicitly try to solve this problem of home
|  network renumbering when the MN is in dormant mode.  If the MN can
   configure itself after it 'comes back on' by reinitiating the
|  bootstrapping process, then the network renumbering problem is fixed
   as a side effect.


(6)  missing article

The second paragraph of Section 7, on page 13, says:

   For each scenario, the underlying assumptions are described.  The
   basic assumption is that there is a trust relationship between mobile
   user and the MSA.  Typically, [...]

It should better say:

   For each scenario, the underlying assumptions are described.  The
|  basic assumption is that there is a trust relationship between the
   mobile user and the MSA.  Typically, [...]


(7)  missing article

The second paragraph of Section 7.2, on page 14, says:

   Figure 1 describes an AAA design example for integrated ASP scenario.

It should better say:

   Figure 1 describes an AAA design example for the integrated ASP
   scenario.


(8)  flawed artwork

Figure 2, on page 15,

                +--------------+   +--------+
                |              |   |Serving |
                | ASP          |   | MSP    |
   +----+    +-----+           |   | +----+ |
   | MN |--- | NAS |           |   | | HA | |  +-------------------+
   +----+    +-----+           |===| +----+ |  | MSA               |
                | \            |   |    \   || (e.g., corporate NW)|
                |  \ +------+  |   |     \     | +-------+         |
                |   -|AAA-NA|  |   |      -------|AAA-MIP|         |
                |    +------+  |   |        |  | +-------+         |
                +------------  +   +--------+  +-------------------+

should perhaps be corrected/improved to:

                +--------------+   +--------+
                |              |   |Serving |
                | ASP          |   | MSP    |
   +----+    +-----+           |   | +----+ |
   | MN |--- | NAS |           |   | | HA | |  +-------------------+
   +----+    +-----+           |===| +----+ |  | MSA (e.g.,        |
                | \            |   |    \   |  |      corporate NW)|
                |  \ +------+  |   |     \  |  | +-------+         |
                |   -|AAA-NA|  |   |      -------|AAA-MIP|         |
                |    +------+  |   |        |  | +-------+         |
                +------------  +   +--------+  +-------------------+

[ Note: I intentionally have refrained from horizontally extending
  the box on the rigth side of the figure, which would have been
  possible while still conforming to RFC formatting rules. ]



(9)  word omissions

Within the large first paragraph of Section 9.1, at the bottom of
page 17, there are two word omissions:

In the 2nd line of the paragraph, replace

	  ... between the home agent and mobile node
by:
          ... between the home agent and the mobile node

and in the 5th line from the bottom of the page, insert "be", changing

                                   [...].  The best way to minimize the
   probability of such a compromise is to have the cryptographic
   material only known or calculable by the two end nodes that share the
   SA -- in this case, the home agent and mobile node.  [...]

to:
                                   [...].  The best way to minimize the
   probability of such a compromise is to have the cryptographic
|  material only be known or calculable by the two end nodes that share
   the SA -- in this case, the home agent and mobile node.  [...]


(10) [[posted separately.]]

Notes:

from pending

Report New Errata



Search RFCs
Advanced Search
×