[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: addition of TLV to locator ID or locator ID set
Brian E Carpenter wrote:
I meant to send this to the list and accidentally
sent it only to Jason some days ago:
Jason Schiller (firstname.lastname@example.org) wrote:
Summary: support for an additional TLV is required in order to allow
a destination (sink) to signal to a source which links should be
to carry traffic inbound to the destination (sink).
Jason, I understand your goal here and it is very reasonable.
However, I would like to ask whether this policy-like information
signalled in-band with the locator set (which is host to host) or
whether it should be signalled out of band as a policy mechanism, and in
that case signalled site to site. I'm assuming that the real requirement
is to apply site to site preferences.
This is a good discussion. Some of the design alternatives here
include placing the information in DNS, having the routers do
it, having the hosts do it, or some combination of these. I
would actually prefer seeing a rather host oriented approach
in terms of actually using this information. However, its very
clear that the hosts won't have the full network picture, can
not be configured with the necessary policy information and
have other problems in dealing with the whole problem. However,
it would seem that some kind of router control/advice
combined with host behaviour would be a good tradeoff.