Opened 13 years ago

Closed 12 years ago

#23 closed defect (invalid)

Multicast IPv6 ND triggers cause many ARs to send UPDATEs when there are many ARs on the link.

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

Description

The protocol implies that all of the possibly many ARs should send an UPDATE to the MAP when the MN sends the NS(DAD). Some might view this as being OK, i.e., that it is good to have the extra state in the MAP for the purpose of fault tolerance. But others might view it that having multiple entries for the same MN in the MAP and the extra control traffic represent unnecessary overhead.

Proposed Resolution: No text change yet. The issue of which AR updates the MAP, or how to arbitrate between many ARs updating the MAP has to be dealt with in the NetLMM backbone protocol. If the way this is done in the backbone requires coordination with the MN-AR interface, this will be sorted out once the backbone protocol specification is available.

Change History (6)

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

  • Cc netlmm@… added

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

  • Status changed from new to assigned
  • Type set to defect

comment:4 Changed 13 years ago by henrik@…

  • Cc netlmm@… added; netlmm@… removed

comment:5 Changed 12 years ago by anonymous

  • Milestone milestone1 deleted

Milestone milestone1 deleted

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

  • Cc netlmm@… removed
  • Resolution set to invalid
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.