organization
"IETF Routing Area (rtgwg) Working Group";
contact
- "WG Web: <https://datatracker.ietf.org/wg/rtgwg>
+ "WG Web: <http://tools.ietf.org/wg/rtgwg/>
WG List: <mailto:rtgwg@ietf.org>
-
Author: Lou Berger
<mailto:lberger@labn.net>
Author: Christian Hopps
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.
-
Copyright (c) 2019 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 Simplified 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 8529; see
the RFC itself for full legal notices.";
"Add a node for the identification of the network
instance associated with the information configured
on a interface.
-
Note that a standard error will be returned if the
identified leafref isn't present. If an interface cannot
be assigned for any other reason, the operation SHALL fail
"Add a node for the identification of the network
instance associated with the information configured
on an IPv4 interface.
-
Note that a standard error will be returned if the
identified leafref isn't present. If an interface cannot
be assigned for any other reason, the operation SHALL fail
"Add a node for the identification of the network
instance associated with the information configured
on an IPv6 interface.
-
Note that a standard error will be returned if the
identified leafref isn't present. If an interface cannot
be assigned for any other reason, the operation SHALL fail
"Indicates an error in the association of an interface to an
NI. Only generated after success is initially returned when
bind-ni-name is set.
-
Note: Some errors may need to be reported for multiple
associations, e.g., a single error may need to be reported
for an IPv4 and an IPv6 bind-ni-name.
-
At least one container with a bind-ni-name leaf MUST be
included in this notification.";
leaf name {
failure.";
}
}
-}
\ No newline at end of file
+}