draft-ietf-netmod-iana-if-type-04.txt   draft-ietf-netmod-iana-if-type-05.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 June 5, 2012 Intended status: Standards Track April 17, 2013
Expires: December 7, 2012 Expires: October 19, 2013
IANA Interface Type and Address Family YANG Modules IANA Interface Type and Address Family YANG Modules
draft-ietf-netmod-iana-if-type-04 draft-ietf-netmod-iana-if-type-05
Abstract Abstract
This document defines the initial versions of the iana-if-type and This document defines the initial versions of the iana-if-type and
iana-afn-safi YANG modules. iana-afn-safi YANG modules.
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 December 7, 2012. This Internet-Draft will expire on October 19, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 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
skipping to change at page 4, line 50 skipping to change at page 4, line 50
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 This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; 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.
// 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 2012-06-05 { revision 2013-04-17 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: TITLE"; "RFC XXXX: TITLE";
} }
typedef iana-if-type { typedef iana-if-type {
type enumeration { type enumeration {
enum "other" { enum "other" {
skipping to change at page 21, line 29 skipping to change at page 21, line 29
"ATM Virtual Interface"; "ATM Virtual Interface";
} }
enum "mplsTunnel" { enum "mplsTunnel" {
value 150; value 150;
description description
"MPLS Tunnel Virtual Interface"; "MPLS Tunnel Virtual Interface";
} }
enum "srp" { enum "srp" {
value 151; value 151;
description description
"Spatial Reuse Protocol "; "Spatial Reuse Protocol";
} }
enum "voiceOverAtm" { enum "voiceOverAtm" {
value 152; value 152;
description description
"Voice Over ATM"; "Voice Over ATM";
} }
enum "voiceOverFrameRelay" { enum "voiceOverFrameRelay" {
value 153; value 153;
description description
"Voice Over Frame Relay"; "Voice Over Frame Relay";
skipping to change at page 36, line 52 skipping to change at page 36, line 52
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 This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; 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.
// 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 2012-06-04 { revision 2013-04-17 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: TITLE"; "RFC XXXX: TITLE";
} }
typedef address-family { typedef address-family {
type enumeration { type enumeration {
enum other { enum other {
value "0"; value "0";
skipping to change at page 45, line 18 skipping to change at page 45, line 18
iana-if-type and iana-afn-safi YANG modules. iana-if-type and iana-afn-safi YANG modules.
The iana-if-type module is intended to reflect the "ifType The iana-if-type module is intended to reflect the "ifType
definitions" registry. When an interface type is added to this definitions" registry. When an interface type is added to this
registry, a new "enum" statement must be added to the "iana-if-type" registry, a new "enum" statement must be added to the "iana-if-type"
typedef, with the same name and value as the corresponding typedef, with the same name and value as the corresponding
enumeration in IANAifType-MIB. If the new interface type has a enumeration in IANAifType-MIB. If the new interface type has a
reference, a new "reference" statement should be added to the new reference, a new "reference" statement should be added to the new
"enum" statement. If an interface type is deprecated in the "ifType "enum" statement. If an interface type is deprecated in the "ifType
definitions" registry, the corresponding "enum" statement must be definitions" registry, the corresponding "enum" statement must be
updated with a "status" statement with the value "deprecated". updated with a "status" statement with the value "deprecated". If an
interface type is marked as "reserved" in the "ifType definitions"
registry, no "enum" statement is added to the "iana-if-type" typedef.
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.
The iana-afn-safi module is intended to reflect the "Address Familiy The iana-afn-safi module is intended to reflect the "Address Family
Numbers" and "Subsequent Address Familiy Identifiers" registries. Numbers" and "Subsequent Address Family Identifiers" registries.
When an AFN or SAFI is added to these registries, a new "enum" When an AFN or SAFI is added to these registries, a new "enum"
statement must be added to the "address-family" or statement must be added to the "address-family" or
"subsequent-address-family" typedefs. If the new parameter has a "subsequent-address-family" typedefs. If the new parameter has a
reference, a new "reference" statement should be added to the new reference, a new "reference" statement should be added to the new
"enum" statement. If a parameter gets deprecated in the registry, "enum" statement. If a parameter gets deprecated in these
the corresponding "enum" statement must be updated with a "status" registries, the corresponding "enum" statement must be updated with a
statement with the value "deprecated". "status" statement with the value "deprecated". If a parameter is
marked as "reserved" in these registries, no "enum" statement is
added to the corresponding typedef.
When the iana-afn-safi YANG module is updated, a new "revision" When the iana-afn-safi YANG module is updated, a new "revision"
statement must be added. statement must be added.
This document registers two URIs in the IETF XML registry [RFC3688]. This document registers two URIs in the IETF XML registry [RFC3688].
Following the format in RFC 3688, the following registrations are Following the format in RFC 3688, the following registrations are
requested to be made. requested to be made.
URI: urn:ietf:params:xml:ns:yang:iana-if-types URI: urn:ietf:params:xml:ns:yang:iana-if-types
 End of changes. 10 change blocks. 
14 lines changed or deleted 18 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/