ietf-softwire-ce

This document defines a YANG module for the configuration and management of A+P Softwire Customer Premises Equipment (CEs). It c...

  • Version: 2019-11-16

    ietf-softwire-ce@2019-11-16


    
      module ietf-softwire-ce {
    
        yang-version 1.1;
    
        namespace
          "urn:ietf:params:xml:ns:yang:ietf-softwire-ce";
    
        prefix softwire-ce;
    
        import ietf-inet-types {
          prefix inet;
          reference
            "RFC 6991: Common YANG Data Types, Section 4";
    
    
        }
        import ietf-interfaces {
          prefix if;
          reference
            "RFC 8343: A YANG Data Model for Interface Management";
    
    
        }
        import ietf-softwire-common {
          prefix softwire-common;
          reference
            "RFC 8676: YANG Modules for IPv4-in-IPv6 Address plus Port
            Softwires";
    
    
        }
        import iana-tunnel-type {
          prefix iana-tunnel-type;
          reference
            "RFC 8675: A YANG Data Model for Tunnel Interface Types";
    
    
        }
    
        organization
          "IETF Softwire Working Group";
    
        contact
          "WG Web:   <https://datatracker.ietf.org/wg/softwire/>
         WG List:  <mailto:softwire@ietf.org>
    
         Author:  Qi Sun
                  <mailto:sunqi.ietf@gmail.com>
    
         Author:  Linhui Sun
                  <mailto:lh.sunlinh@gmail.com>
    
         Author:  Yong Cui
                  <mailto:yong@csnet1.cs.tsinghua.edu.cn>
    
         Editor:  Ian Farrer
                  <mailto:ian.farrer@telekom.de>
    
         Author:  Sladjana Zoric
                  <mailto:sladjana.zoric@telekom.de>
    
         Editor:  Mohamed Boucadair
                  <mailto:mohamed.boucadair@orange.com>
    
         Author:  Rajiv Asati
                   <mailto:rajiva@cisco.com>";
    
        description
          "This document defines a YANG module for the configuration and
         management of A+P Softwire Customer Premises Equipment (CEs).
         It covers Lightweight 4over6, MAP-E, and MAP-T mechanisms.
    
         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
         (http://trustee.ietf.org/license-info).
    
         This version of this YANG module is part of RFC 8676; see
         the RFC itself for full legal notices.";
    
        revision "2019-11-16" {
          description "Initial revision.";
          reference
            "RFC 8676: YANG Modules for IPv4-in-IPv6 Address plus Port
            (A+P) Softwires";
    
        }
    
    
        feature binding-mode {
          description
            "Binding is used for configuring the Lightweight 4over6
           mechanism.
    
           Binding-based softwire mechanisms are IPv4-over-IPv6 tunneling
           transition mechanisms specifically intended for complete
           independence between the IPv6 subnet prefix (and IPv6 address)
           and IPv4 address, with or without IPv4 address sharing.
    
           This is accomplished by maintaining state for each softwire
           (per-subscriber state) in the central Border Relay (BR) and
           using a hub-and-spoke forwarding architecture.  In order to
           delegate the NAPT function and achieve IPv4 address sharing,
           port-restricted IPv4 addresses needs to be allocated to CEs.
    
           This feature indicates that the network element can function
           as one or more binding-based softwire instances.";
          reference
            "RFC 7596: Lightweight 4over6: An Extension to the Dual-Stack
            Lite Architecture
             RFC 7597: Mapping of Address and Port with Encapsulation
            (MAP-E)
             RFC 7599: Mapping of Address and Port using Translation
            (MAP-T)";
    
        }
    
        feature map-e {
          description
            "MAP-E is an IPv6 transition mechanism for transporting IPv4
           packets across an IPv6 network using IP encapsulation.  MAP-E
           allows for a reduction of the amount of centralized state
           using rules to express IPv4/IPv6 address mappings.  This
           introduces an algorithmic relationship between the IPv6
           subnet and IPv4 address.
    
           This feature indicates that the network element can function
           as one or more MAP-E softwire instances.";
          reference
            "RFC 7597: Mapping of Address and Port with
            Encapsulation (MAP-E)";
    
        }
    
        feature map-t {
          description
            "MAP-T is an IPv6 transition mechanism for transporting IPv4
           packets across an IPv6 network using IP translation.  It
           leverages a double stateless NAT64-based solution as well as
           the stateless algorithmic address and transport layer port
           mapping algorithm defined for MAP-E.
    
           This feature indicates that the network element can function
           as one or more MAP-T softwire instances.";
          reference
            "RFC 7599: Mapping of Address and Port using Translation
            (MAP-T)";
    
        }
    
        notification softwire-ce-event {
          if-feature binding-mode;
          description "CE notification";
          leaf ce-binding-ipv6-addr-change {
            type inet:ipv6-address;
            mandatory true;
            description
              "This notification is generated whenever the CE's binding
             IPv6 address changes for any reason.";
          }
        }  // notification softwire-ce-event
      }  // module ietf-softwire-ce
    

© 2023 YumaWorks, Inc. All rights reserved.