Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

#86 closed defect (wontfix)

DHCP is a mobility management protocol too (for Gap analysis)

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


Fred Templin says:

5) Section 9, "DHCP + IP forwarding table manipulation" should be listed as another item for the gap analysis, but I don't see a detailed analysis coming within the time remaining between now and Friday. Suggest adding a very short subsection such as:

"9.6 DHCP + IP forwarding table manipulation"

It has been suggested that using DHCP on mobile nodes, access routers and localized mobility agents can provide a framework for localized mobility management when the DHCP exchanges are also tied to IP forwarding table manipulations on routers. This method requires further investigation before a gap analysis can be determined. In one alternative, DHCP could be seen as an access method for the eventual NETLMM protocol design."

Then (since the gap analysis is not complete) there should be no entry for this alternative under the "Summary" section.

Change History (2)

comment:1 Changed 13 years ago by kempf@…

  • Resolution set to wontfix
  • Status changed from new to closed

The gap analysis is supposed to be for protocols that a) have in the past (i.e. not as part of the current NETLMM effort) been proposed for localized mobility management in IETF and b) there is was an existing (i.e. not currently ongoing) implementation and study of the protocol when the NETLMM effort started.

From my browsing of draft-templin-autoconf-netlmm-dhcp-01.txt, it does not sound as if this solution can be accomplished without modifying the forwarding code on the access routers, and developing a new code for the LMA. So I don't see a gap analysis of this solution being relevant to this document.

In addition, the gap analysis has become secondary to the purpose of this document, which is to define the goals of the NETLMM protocol. So I don't think adding additional material on other protocols will really help advance the primary purpose of the document. Finally, as noted by the suggestor, a complete gap analysis has not been done on this solution, so any text added now would probably not do justice to the technical details in any event.

Recommendation: not to add any text on this.

comment:2 Changed 12 years ago by anonymous

  • Milestone milestone2 deleted

Milestone milestone2 deleted

Note: See TracTickets for help on using tickets.