The Routing Over Large Clouds Mailing List Archive by date

[gardo@vnet.ibm.com]

An NHS can cache "Source Address" information from either a
Registration Request or Resolution Request.  However,
the MTU from a Registration Request can be cached, and
the MTU in a Resolution Request is not used...
Therefore, responding with cached information gleaned from a
Resolution Request would only allow an MTU of zero (which has a
specific pre-defined meaning) to be returned.

I suggest that the MTU be used in the Resolution Request packet and be
associated with the "Source Address" information (like we do in the
Registration Request).  This way an MTU will always accompany "Source
Address" information in a Request (Resolution & Registration).


Also, I suggest rewording the Registration packet's MTU description:
  The description in the Registration Request says the MTU is
  for the Next Hop information in the mandatory part of the packet.
  Maybe it would be clearer to say that the MTU is for the "Source
  Address" information in the Registration Request packet, since
  there is no field in the Registration Request called "Next Hop".

-- Russell