draft-ietf-netmod-iana-if-type-09.txt   draft-ietf-netmod-iana-if-type-10.txt 
Network Working Group M. Bjorklund Network Working Group M. Bjorklund
Internet-Draft Tail-f Systems Internet-Draft Tail-f Systems
Intended status: Standards Track December 7, 2013 Intended status: Standards Track January 15, 2014
Expires: June 10, 2014 Expires: July 19, 2014
IANA Interface Type YANG Module IANA Interface Type YANG Module
draft-ietf-netmod-iana-if-type-09 draft-ietf-netmod-iana-if-type-10
Abstract Abstract
This document defines the initial version of the iana-if-type YANG This document defines the initial version of the iana-if-type YANG
module. module.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 10, 2014. This Internet-Draft will expire on July 19, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. IANA Maintained Interface Type YANG Module . . . . . . . . . . 4 2. IANA Maintained Interface Type YANG Module . . . . . . . . . . 4
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
3.1. URI Registrations . . . . . . . . . . . . . . . . . . . . 36 3.1. URI Registrations . . . . . . . . . . . . . . . . . . . . 37
3.2. YANG Module Registrations . . . . . . . . . . . . . . . . 37 3.2. YANG Module Registrations . . . . . . . . . . . . . . . . 37
4. Security Considerations . . . . . . . . . . . . . . . . . . . 38 4. Security Considerations . . . . . . . . . . . . . . . . . . . 38
5. Normative References . . . . . . . . . . . . . . . . . . . . . 39 5. Normative References . . . . . . . . . . . . . . . . . . . . . 39
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 40 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 40
1. Introduction 1. Introduction
This document defines the initial version of the iana-if-type YANG This document defines the initial version of the iana-if-type YANG
module for interface type definitions. module for interface type definitions.
The iana-if-type module reflects IANA's existing "ifType definitions" The iana-if-type module reflects IANA's existing "ifType definitions"
registry. The latest revision of the module can be obtained from the registry [IFTYPE-IANA-REGISTRY]. The latest revision of the module
IANA web site. can be obtained from the IANA web site.
Whenever a new interface type is added to the "ifType definitions" Whenever a new interface type is added to the "ifType definitions"
registry, the IANAifType-MIB and the iana-if-type YANG module are registry, the IANAifType-MIB and the iana-if-type YANG module are
updated by IANA. updated by IANA.
2. IANA Maintained Interface Type YANG Module 2. IANA Maintained Interface Type YANG Module
This YANG module imports the "interface-type" identity from This YANG module imports the "interface-type" identity from
[I-D.ietf-netmod-interfaces-cfg]. [I-D.ietf-netmod-interfaces-cfg].
skipping to change at page 5, line 4 skipping to change at page 5, line 4
Copyright (c) 2013 IETF Trust and the persons identified as Copyright (c) 2013 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see The initial version of this YANG module is part of RFC XXXX;
the RFC itself for full legal notices."; see the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this // RFC Ed.: replace XXXX with actual RFC number and remove this
// note. // note.
reference reference
"IANA ifType definitions registry. "IANA ifType definitions registry.
<http://www.iana.org/assignments/smi-numbers>"; <http://www.iana.org/assignments/smi-numbers>";
// RFC Ed.: update the date below with the date of RFC publication // RFC Ed.: update the date below with the date of RFC publication
// and remove this note. // and remove this note.
revision 2013-12-07 { revision 2014-01-15 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: IANA Interface Type YANG Module"; "RFC XXXX: IANA Interface Type YANG Module";
} }
identity iana-interface-type { identity iana-interface-type {
base if:interface-type; base if:interface-type;
description description
"This identity is used as a base for all interface types "This identity is used as a base for all interface types
skipping to change at page 7, line 29 skipping to change at page 7, line 29
status obsolete; status obsolete;
description description
"Obsolete see DS1-MIB"; "Obsolete see DS1-MIB";
reference reference
"RFC 4805 - Definitions of Managed Objects for the "RFC 4805 - Definitions of Managed Objects for the
DS1, J1, E1, DS2, and E2 Interface Types"; DS1, J1, E1, DS2, and E2 Interface Types";
} }
identity basicISDN { identity basicISDN {
base iana-interface-type; base iana-interface-type;
description description
"see also RFC2127"; "no longer used.
see also RFC2127";
} }
identity primaryISDN { identity primaryISDN {
base iana-interface-type; base iana-interface-type;
description
"no longer used.
see also RFC2127";
} }
identity propPointToPointSerial { identity propPointToPointSerial {
base iana-interface-type; base iana-interface-type;
description description
"proprietary serial"; "proprietary serial";
} }
identity ppp { identity ppp {
base iana-interface-type; base iana-interface-type;
} }
identity softwareLoopback { identity softwareLoopback {
skipping to change at page 36, line 10 skipping to change at page 36, line 10
} }
<CODE ENDS> <CODE ENDS>
3. IANA Considerations 3. IANA Considerations
This document defines the initial version of the IANA-maintained This document defines the initial version of the IANA-maintained
iana-if-type YANG module. iana-if-type YANG module.
The iana-if-type module is intended to reflect the "ifType The iana-if-type YANG module is intended to reflect the "ifType
definitions" registry. When an interface type is added to this definitions" registry [IFTYPE-IANA-REGISTRY], exactly like the
registry, a new "identity" statement must be added to the module. IANAifType-MIB MIB module [IANAifType-MIB] reflects the "ifType
The name of the "identity" is the same as the corresponding definitions" registry.
IANA is requested to add this new Note to the iana-if-type YANG
module registry:
Interface types must not be directly added to the iana-if-type YANG
module, they must instead be added to the "ifType definitions"
registry.
When an interface type is added to the "ifType definitions" registry,
a new "identity" statement must be added to the iana-if-type YANG
module. The name of the "identity" is the same as the corresponding
enumeration in the IANAifType-MIB. The following substatements to enumeration in the IANAifType-MIB. The following substatements to
the "identity" statement should be defined: the "identity" statement should be defined:
"base": Contains the value "iana-interface-type". "base": Contains the value "iana-interface-type".
"status": Include only if a registration has been deprecated (use "status": Include only if a registration has been deprecated (use
the value "deprecated") or obsoleted (use the value the value "deprecated") or obsoleted (use the value
"obsolete"). "obsolete").
"description": Replicate the description from the registry, if any. "description": Replicate the description from the registry, if any.
Insert line breaks as needed so that the line does
not exceed 72 characters.
"reference": Replicate the reference from the registry, if any, and "reference": Replicate the reference from the registry, if any, and
add the title of the document. add the title of the document.
Unassigned or reserved values are not present in the module. Unassigned or reserved values are not present in the module.
When the iana-if-type YANG module is updated, a new "revision" When the iana-if-type YANG module is updated, a new "revision"
statement must be added. statement must be added in front of the existing revision statements.
IANA is requested to add this new Note to the "ifType definitions" IANA is requested to add this new Note to the "ifType definitions"
registry: registry:
When this registry is modified, the YANG module iana-if-type When this registry is modified, the YANG module iana-if-type
must be updated as defined in RFC XXXX. must be updated as defined in RFC XXXX.
The Reference text in the "ifType definitions" registry needs to be The Reference text in the "ifType definitions" registry needs to be
updated as: updated as:
skipping to change at page 39, line 12 skipping to change at page 39, line 12
there are no security issues to be considered for this document there are no security issues to be considered for this document
itself. itself.
5. Normative References 5. Normative References
[I-D.ietf-netmod-interfaces-cfg] [I-D.ietf-netmod-interfaces-cfg]
Bjorklund, M., "A YANG Data Model for Interface Bjorklund, M., "A YANG Data Model for Interface
Management", draft-ietf-netmod-interfaces-cfg-14 (work in Management", draft-ietf-netmod-interfaces-cfg-14 (work in
progress), December 2013. progress), December 2013.
[IANAifType-MIB]
Internet Assigned Numbers Authority, "IANAifType Textual
Convention definitions",
<http://www.iana.org/assignments/ianaiftype-mib>.
[IFTYPE-IANA-REGISTRY]
Internet Assigned Numbers Authority, "ifType Definitions",
<http://www.iana.org/assignments/smi-numbers/
smi-numbers.xhtml#smi-numbers-5>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
Network Configuration Protocol (NETCONF)", RFC 6020, Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. October 2010.
Author's Address Author's Address
Martin Bjorklund Martin Bjorklund
 End of changes. 14 change blocks. 
17 lines changed or deleted 44 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/