And I failed to include a relevant point:

On Wed, Oct 14, 2015 at 04:35:37PM -0400, Jeffrey Haas wrote:
> The protocol standardizes the message contents over this stream.
> 
> The protocol by default suggests TCP.  But as overly flippantly noted in the
> security considerations, you can use something stronger if you desire either
> integrity or privacy.
> 
> While I feel your particular pain and anger over the general state of
> things, my suggestion is we should work on clarifying the text in the above
> fashion: If you want a secured transport, you can use one.  We can even
> recommend one.  Making anything other than stock TCP mandatory will result
> in implementor torches and pitchforks at this point because we have shipping
> code and customers use it. :-)

It's also important to understand that in routing infrastructure,
*operators* have some power to control the security of inter-router traffic.
They may choose to tunnel traffic between two routers over a secure
transport.  Their link layers may provide security.  A separate management
plane may be used for for the protocol.

-- Jeff

_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow

Reply via email to