Re: [netlmm] #25: MN-AR interface specifying REDIRECT behavior

#25: MN-AR interface specifying REDIRECT behavior
-----------------------------------------+----------------------------------
  Reporter:  julien.ietf@laposte.net     |       Owner:  julien.ietf@laposte.net
      Type:  defect                      |      Status:  closed                 
  Priority:  major                       |   Milestone:                         
 Component:  draft-ietf-netlmm-mn-ar-if  |     Version:                         
Resolution:  fixed                       |    Keywords:                         
-----------------------------------------+----------------------------------
Changes (by julien.ietf@laposte.net):

  * cc:  netlmm@ngnet.it => netlmm@ietf.org
  * resolution:  => fixed
  * status:  reopened => closed

Comment:

 Fred Templin wrote:
  One attribute of a multi-link subnet (which I
  think should be agreed that NETLMM is an example) is that
  MNs in the same IP prefix may be attached to different links.
  Moreover, MNs that were formerly attached to the same link may
  move to different links during the course of communication
  sessions.

  So, I can see reason for the MN-AR interface spec to supercede
  the normative reference but only if it gives a specific reason
  for doing so, e.g.,

    "An AR SHOULD NOT send a redirect message ([RFC2461], Section
  8.2) unless it can determine that the sending node and better
  first-hop node reside on the same link and will remain on the same
  link."

 Resolution: Adopt the text above.

-- 
Ticket URL: <http://www1.tools.ietf.org/wg/netlmm/trac/ticket/25>
netlmm <http://tools.ietf.org/wg/netlmm/>

_______________________________________________
netlmm mailing list
netlmm@ietf.org
https://www1.ietf.org/mailman/listinfo/netlmm