Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

#24 closed defect (fixed)

Setting MN/AR/MAP as DHCPv6 client/relay/server fixes issues #22 and #23

Reported by: julien.ietf@… Owned by: julien.ietf@…
Priority: trivial Milestone:
Component: draft-ietf-netlmm-mn-ar-if Severity:
Keywords: Cc: netlmm@…

Description

We are already assuming that the MAP needs to carefully keep state information for each MN that registers with it. With DHCP, the MN would use the AR as a relay to the MAP acting as a DHCP server. The MN would then receive positive confirmation that its proposed address was unique within the NETLMM domain and was successfully registered with the MAP.

Proposed Resolution: RFC4294 (IPv6 Node Requirements) says:

  • Stateless Address Autoconfiguration (RFC2462) is a MUST
  • Neighbor Discovery (RFC2461) is a MUST
  • Stateful Address Configuration (DHCPv6) is a MAY

Thus, to be consistent with that, it seems that we too MUST support stateless autoconf, and we MAY support DHCP. That means that we might add text saying that when DHCP is used then MN/AR/MAP are DHCPv6 client/relay/server

Change History (9)

comment:1 Changed 13 years ago by julien.ietf@…

  • Cc netlmm@… added

comment:2 Changed 13 years ago by anonymous

  • Priority changed from major to trivial

MUST for stateless autoconfig and MAY for DHCPv6 may be a significant departure from IPv4 where the reverse is true. The deployment with MAP and ARs screams for DHCPv6 usage, and netlmm's need to maintain same address per visiting MN may too.

comment:5 Changed 13 years ago by julien.ietf@…

  • Status changed from new to assigned

comment:6 Changed 13 years ago by julien.ietf@…

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

comment:7 Changed 13 years ago by julien.ietf@…

  • Resolution fixed deleted
  • Status changed from closed to reopened

comment:8 Changed 13 years ago by julien.ietf@…

  • Cc netlmm@… added; netlmm@… removed
  • Resolution set to fixed
  • Status changed from reopened to closed

comment:9 Changed 12 years ago by anonymous

  • Milestone milestone1 deleted

Milestone milestone1 deleted

Note: See TracTickets for help on using tickets.