< draft-ietf-softwire-iftunnel-03.txt   draft-ietf-softwire-iftunnel-04.txt >
Softwire Working Group M. Boucadair Softwire Working Group M. Boucadair
Internet-Draft Orange Internet-Draft Orange
Intended status: Standards Track I. Farrer Intended status: Standards Track I. Farrer
Expires: July 31, 2019 Deutsche Telekom AG Expires: October 5, 2019 Deutsche Telekom AG
R. Asati R. Asati
Cisco Systems, Inc. Cisco Systems, Inc.
January 27, 2019 April 3, 2019
Tunnel Interface Types YANG Module Tunnel Interface Types YANG Module
draft-ietf-softwire-iftunnel-03 draft-ietf-softwire-iftunnel-04
Abstract Abstract
This document specifies a YANG module containing a collection of IANA This document specifies a YANG module containing a collection of IANA
maintained YANG identities, used as interface types for tunnel maintained YANG identities, used as interface types for tunnel
interfaces. interfaces.
Editorial Note (To be removed by RFC Editor) Editorial Note (To be removed by RFC Editor)
Please update these statements in the document with the RFC number to Please update these statements in the document with the RFC number to
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 July 31, 2019. This Internet-Draft will expire on October 5, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 3, line 21 skipping to change at page 3, line 21
[RFC8340]. [RFC8340].
2. IANA Tunnel Type YANG Module 2. IANA Tunnel Type YANG Module
The iana-tunnel-type module imports the 'iana-if-type' module defined The iana-tunnel-type module imports the 'iana-if-type' module defined
in [RFC7224]. in [RFC7224].
The initial version of the module includes tunnels types defined in The initial version of the module includes tunnels types defined in
[RFC4087], [RFC7856], [RFC7870], and [RFC6346]. [RFC4087], [RFC7856], [RFC7870], and [RFC6346].
<CODE BEGINS> file "iana-tunnel-type@2019-01-10.yang" <CODE BEGINS> file "iana-tunnel-type@2019-04-04.yang"
module iana-tunnel-type { module iana-tunnel-type {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:iana-tunnel-type"; namespace "urn:ietf:params:xml:ns:yang:iana-tunnel-type";
prefix iana-tunnel-type; prefix iana-tunnel-type;
import iana-if-type { import iana-if-type {
prefix ift; prefix ift;
reference reference
"RFC 7224: IANA Interface Type YANG Module"; "RFC 7224: IANA Interface Type YANG Module";
skipping to change at page 4, line 15 skipping to change at page 4, line 15
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 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.";
revision 2019-01-10 { revision 2019-04-04 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Tunnel Interface Types YANG Module"; "RFC XXXX: Tunnel Interface Types YANG Module";
} }
identity other { identity other {
base ift:tunnel; base ift:tunnel;
description description
"None of the following values."; "None of the following values.";
reference reference
skipping to change at page 8, line 9 skipping to change at page 8, line 9
subregistry within the "IETF XML Registry" [RFC3688]: subregistry within the "IETF XML Registry" [RFC3688]:
URI: urn:ietf:params:xml:ns:yang:iana-tunnel-type URI: urn:ietf:params:xml:ns:yang:iana-tunnel-type
Registrant Contact: IANA. Registrant Contact: IANA.
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
This document requests IANA to register the following following YANG This document requests IANA to register the following following YANG
module in the "YANG Module Names" subregistry [RFC7950] within the module in the "YANG Module Names" subregistry [RFC7950] within the
"YANG Parameters" registry. "YANG Parameters" registry.
name: iana-tunnel-type Name: iana-tunnel-type
namespace: urn:ietf:params:xml:ns:yang:iana-tunnel-type Namespace: urn:ietf:params:xml:ns:yang:iana-tunnel-type
prefix: iana-tunnel-type Prefix: iana-tunnel-type
reference: RFC XXXX Reference: RFC XXXX
This document defines the initial version of the IANA-maintained This document defines the initial version of the IANA-maintained
iana-tunnel-type YANG module. IANA is requested to add this note: iana-tunnel-type YANG module. IANA is requested to add this note:
Tunnel type values must not be directly added to the iana-tunnel- Tunnel type values must not be directly added to the iana-tunnel-
type YANG module. They must instead be respectively added to the type YANG module. They must instead be respectively added to the
"tunnelType" sub-registry (under the "ifType definitions" "tunnelType" sub-registry (under the "ifType definitions"
registry). registry).
When a tunnel type is added to the "tunnelType" sub-registry, a new When a tunnel type is added to the "tunnelType" sub-registry, a new
skipping to change at page 10, line 5 skipping to change at page 9, line 51
13 isatap ISATAP encapsulation [RFC5214] 13 isatap ISATAP encapsulation [RFC5214]
14 teredo Teredo encapsulation [RFC4380] 14 teredo Teredo encapsulation [RFC4380]
16 softwireMesh softwire mesh tunnel [RFC5565] 16 softwireMesh softwire mesh tunnel [RFC5565]
17 dsLite DS-Lite tunnel [RFC6333] 17 dsLite DS-Lite tunnel [RFC6333]
5. Acknowledgements 5. Acknowledgements
Special thanks to Tom Petch and Martin Bjorklund for the detailed Special thanks to Tom Petch and Martin Bjorklund for the detailed
review and suggestions. review and suggestions.
Thanks to Andy Bierman for the Yangdoctors review.
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
skipping to change at page 11, line 10 skipping to change at page 11, line 10
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
6.2. Informative References 6.2. Informative References
[I-D.ietf-softwire-yang] [I-D.ietf-softwire-yang]
Farrer, I. and M. Boucadair, "YANG Modules for IPv4-in- Farrer, I. and M. Boucadair, "YANG Modules for IPv4-in-
IPv6 Address plus Port (A+P) Softwires", draft-ietf- IPv6 Address plus Port (A+P) Softwires", draft-ietf-
softwire-yang-15 (work in progress), January 2019. softwire-yang-16 (work in progress), January 2019.
[RFC1701] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic [RFC1701] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic
Routing Encapsulation (GRE)", RFC 1701, Routing Encapsulation (GRE)", RFC 1701,
DOI 10.17487/RFC1701, October 1994, DOI 10.17487/RFC1701, October 1994,
<https://www.rfc-editor.org/info/rfc1701>. <https://www.rfc-editor.org/info/rfc1701>.
[RFC1702] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic [RFC1702] Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic
Routing Encapsulation over IPv4 networks", RFC 1702, Routing Encapsulation over IPv4 networks", RFC 1702,
DOI 10.17487/RFC1702, October 1994, DOI 10.17487/RFC1702, October 1994,
<https://www.rfc-editor.org/info/rfc1702>. <https://www.rfc-editor.org/info/rfc1702>.
skipping to change at page 13, line 40 skipping to change at page 13, line 40
Definitions", <https://www.iana.org/assignments/smi- Definitions", <https://www.iana.org/assignments/smi-
numbers/smi-numbers.xhtml#smi-numbers-6>. numbers/smi-numbers.xhtml#smi-numbers-6>.
Appendix A. Example Usage Appendix A. Example Usage
The following example illustrates how the Interface YANG module can The following example illustrates how the Interface YANG module can
be augmented with tunnel-specific paramters. In this example, the be augmented with tunnel-specific paramters. In this example, the
module is augmented with a 'remote-endpoint' for the tunnel. A tree module is augmented with a 'remote-endpoint' for the tunnel. A tree
structure is provided below: structure is provided below:
module: ietf-extension-example module: example-iftunnel-extension
augment /if:interfaces/if:interface: augment /if:interfaces/if:interface:
+--rw remote-endpoint? inet:ipv6-address +--rw remote-endpoint? inet:ipv6-address
The 'extension-example' module imports the modules defined in The 'extension-example' module imports the modules defined in
[RFC6991] and [RFC8343] in addition to the "iana-tunnel-type" module [RFC6991] and [RFC8343] in addition to the "iana-tunnel-type" module
defined in this document. defined in this document.
<CODE BEGINS> file "ietf-extension-example@2019-01-10.yang" module example-iftunnel-extension {
module ietf-extension-example {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-extension-example"; namespace "urn:ietf:params:xml:ns:yang:ietf-extension-example";
prefix example; prefix example;
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
"Section 4 of RFC 6991"; "Section 4 of RFC 6991";
} }
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference reference
"RFC 8343: A YANG Data Model for Interface Management"; "RFC 8343: A YANG Data Model for Interface Management";
skipping to change at page 15, line 5 skipping to change at page 14, line 50
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 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.";
revision 2019-01-10 { revision 2019-04-04 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: Tunnel Interface Types YANG Module"; "RFC XXXX: Tunnel Interface Types YANG Module";
} }
augment "/if:interfaces/if:interface" { augment "/if:interfaces/if:interface" {
when "derived-from(if:type, 'iana-tunnel-type:gre')"; when "derived-from(if:type, 'iana-tunnel-type:gre')";
description description
"Augments Interface module with specific tunnel parameters."; "Augments Interface module with specific tunnel parameters.";
leaf remote-endpoint { leaf remote-endpoint {
type inet:ipv6-address; type inet:ipv6-address;
description description
"IPv6 address of the local GRE endpoint."; "IPv6 address of the local GRE endpoint.";
} }
} }
} }
<CODE ENDS>
Authors' Addresses Authors' Addresses
Mohamed Boucadair Mohamed Boucadair
Orange Orange
Rennes 35000 Rennes 35000
France France
Email: mohamed.boucadair@orange.com Email: mohamed.boucadair@orange.com
 End of changes. 15 change blocks. 
18 lines changed or deleted 17 lines changed or added

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