ietf-rift

Organization:

IETF RIFT (Routing In Fat Trees) Working Group

Module:

ietf-rift

Version:

2025-04-04

File:

ietf-rift@2025-04-04.yang

Abstract:

This YANG module defines the generic configuration and operational state for the RIFT protocol common to all vendor implementati...

Contact:

WG Web: <https://datatracker.ietf.org/wg/rift/>
WG List: <mailto:rift@ietf.org>

Author: Zheng (Sandy) Zhang
<mailto:zhang.zheng@zte.com.cn>

Author: Yuehua Wei
<mailto:wei.yuehua@zte.com.cn>

Author: Shaowen Ma
<mailto:mashaowen@gmail.com>

Author: Xufeng Liu
<mailto:xufeng.liu.ietf@gmail.com>

Author: Bruno Rijsman
<mailto:brunorijsman@gmail.com>

Check for an additional details:

YANG Catalog

Description:

This YANG module defines the generic configuration and
operational state for the RIFT protocol common to all
vendor implementations. It is intended that the module
will be extended by vendors to define vendor-specific
RIFT configuration parameters and policies --
for example, route maps or route policies.

Copyright (c) 2025 IETF Trust and the persons identified as
authors of the code. All rights reserved.

Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to
the license terms contained in, the Revised BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).

This version of this YANG module is part of RFC 9719
(https://www.rfc-editor.org/info/rfc9719); see the RFC itself
for full legal notices.

The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here.