. "Status : DEPRECATED" . . . "The name of the interface.\n\nA server implementation MAY map this leaf to the ifName\nMIB object. Such an implementation needs to use some\nmechanism to handle the differences in size and characters\nallowed between this leaf and ifName. The definition of\nsuch a mechanism is outside the scope of this document." . "The name of the interface.\n\nA device MAY restrict the allowed values for this leaf,\npossibly depending on the type of the interface.\nFor system-controlled interfaces, this leaf is the\ndevice-specific name of the interface.\n\nIf a client tries to create configuration for a\nsystem-controlled interface that is not present in the\noperational state, the server MAY reject the request if\nthe implementation does not support pre-provisioning of\ninterfaces or if the name refers to an interface that can\nnever exist in the system. A Network Configuration\nProtocol (NETCONF) server MUST reply with an rpc-error\nwith the error-tag 'invalid-value' in this case.\n\nIf the device supports pre-provisioning of interface\nconfiguration, the 'pre-provisioning' feature is\nadvertised.\n\nIf the device allows arbitrarily named user-controlled\ninterfaces, the 'arbitrary-names' feature is advertised.\nWhen a configured user-controlled interface is created by\nthe system, it is instantiated with the same name in the\noperational state.\n\nA server implementation MAY map this leaf to the ifName\nMIB object. Such an implementation needs to use some\nmechanism to handle the differences in size and characters\nallowed between this leaf and ifName. The definition of\nsuch a mechanism is outside the scope of this document." . "Reference : RFC 2863: The Interfaces Group MIB - ifName" . .