draft-ietf-softwire-dslite-yang-16.txt   draft-ietf-softwire-dslite-yang-17.txt 
Network Working Group M. Boucadair Network Working Group M. Boucadair
Internet-Draft C. Jacquenet Internet-Draft C. Jacquenet
Intended status: Standards Track Orange Intended status: Standards Track Orange
Expires: November 25, 2018 S. Sivakumar Expires: November 30, 2018 S. Sivakumar
Cisco Systems Cisco Systems
May 24, 2018 May 29, 2018
A YANG Data Module for Dual-Stack Lite (DS-Lite) A YANG Data Model for Dual-Stack Lite (DS-Lite)
draft-ietf-softwire-dslite-yang-16 draft-ietf-softwire-dslite-yang-17
Abstract Abstract
This document defines a YANG module for the DS-Lite Address Family This document defines a YANG module for the DS-Lite Address Family
Transition Router (AFTR) and Basic Bridging BroadBand (B4) elements. Transition Router (AFTR) and Basic Bridging BroadBand (B4) elements.
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
be assigned to this document: be assigned to this document:
o "This version of this YANG module is part of RFC XXXX;" o "This version of this YANG module is part of RFC XXXX;"
o "RFC XXXX: A YANG Data Module for Dual-Stack Lite (DS-Lite)"; o "RFC XXXX: A YANG Data Model for Dual-Stack Lite (DS-Lite)";
o "reference: RFC XXXX" o "reference: RFC XXXX"
Please update the "revision" date of the YANG module. Please update the "revision" date of the YANG module.
Also, update this sentence with the RFC number to be assigned to I- Also, update this sentence with the RFC number to be assigned to I-
D.ietf-opsawg-nat-yang: D.ietf-opsawg-nat-yang:
o "RFC YYYY: A YANG Module for Network Address Translation (NAT) and o "RFC YYYY: A YANG Module for Network Address Translation (NAT) and
Network Prefix Translation (NPT)" Network Prefix Translation (NPT)"
skipping to change at page 2, line 7 skipping to change at page 2, line 7
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 November 25, 2018. This Internet-Draft will expire on November 30, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 4, line 16 skipping to change at page 4, line 16
This document follows the guidelines of [RFC6087], uses the common This document follows the guidelines of [RFC6087], uses the common
YANG types defined in [RFC6991], and adopts the Network Management YANG types defined in [RFC6991], and adopts the Network Management
Datastore Architecture (NMDA). Datastore Architecture (NMDA).
1.1. Terminology 1.1. Terminology
This document makes use of the terms defined in Section 3 of This document makes use of the terms defined in Section 3 of
[RFC6333]. [RFC6333].
The terminology for describing YANG data modules is defined in The terminology for describing YANG data models is defined in
[RFC7950]. [RFC7950].
The meaning of the symbols in tree diagrams is defined in [RFC8340]. The meaning of the symbols in tree diagrams is defined in [RFC8340].
2. DS-Lite YANG Module: An Overview 2. DS-Lite YANG Module: An Overview
As shown in Figure 1: As shown in Figure 1:
o The AFTR element is a combination of an IPv4-in-IPv6 tunnel and a o The AFTR element is a combination of an IPv4-in-IPv6 tunnel and a
NAPT function (Section 2.2 of [RFC3022]). NAPT function (Section 2.2 of [RFC3022]).
skipping to change at page 5, line 20 skipping to change at page 5, line 20
(policy, in particular) with the following: (policy, in particular) with the following:
o A policy to limit the number of DS-Lite softwires per subscriber o A policy to limit the number of DS-Lite softwires per subscriber
(max-softwire-per-subscriber). (max-softwire-per-subscriber).
o A policy to instruct the AFTR whether a state can be automatically o A policy to instruct the AFTR whether a state can be automatically
migrated (state-migrate). migrated (state-migrate).
o Further, in order to prevent a denial-of-service by frequently o Further, in order to prevent a denial-of-service by frequently
changing the source IPv6 address, 'b4-address-change-limit' is changing the source IPv6 address, 'b4-address-change-limit' is
used to rate-lmite such changes. used to rate-limit such changes.
o An instruction to rewrite the TCP Maximum Segment Size (MSS) o An instruction to rewrite the TCP Maximum Segment Size (MSS)
option (mss-clamping) to avoid TCP fragmentation. option (mss-clamping) to avoid TCP fragmentation.
Given that the NAPT table of the AFTR element is extended to include Given that the NAPT table of the AFTR element is extended to include
the source IPv6 address of incoming packets, the DS-Lite YANG module the source IPv6 address of incoming packets, the DS-Lite YANG module
augments the NAPT44 mapping-entry with the following: augments the NAPT44 mapping-entry with the following:
o b4-ipv6-address which is used to record the source IPv6 address of o b4-ipv6-address which is used to record the source IPv6 address of
a packet received from a B4 element. This IPv6 address is a packet received from a B4 element. This IPv6 address is
skipping to change at page 8, line 30 skipping to change at page 8, line 30
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 2018-02-26 { revision 2018-02-26 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Module for Dual-Stack Lite (DS-Lite)"; "RFC XXXX: A YANG Data Model for Dual-Stack Lite (DS-Lite)";
} }
/* /*
* Features * Features
*/ */
feature b4 { feature b4 {
description description
"The B4 element is a function implemented on a dual-stack-capable "The B4 element is a function implemented on a dual-stack-capable
node, either a directly connected device or a CPE, that creates node, either a directly connected device or a CPE, that creates
skipping to change at page 10, line 28 skipping to change at page 10, line 28
reference reference
"RFC 6908: Deployment Considerations for Dual-Stack Lite"; "RFC 6908: Deployment Considerations for Dual-Stack Lite";
} }
leaf v6-v4-dscp-preservation { leaf v6-v4-dscp-preservation {
type boolean; type boolean;
description description
"Copies the DSCP value from the IPv6 header and vice versa. "Copies the DSCP value from the IPv6 header and vice versa.
According to Section 2.10 of [RFC6908], operators should According to Section 2.10 of [RFC6908], operators should
use this model by provisioning the network such that the use the uniform model by provisioning the network such
AFTR/B4 copies the DSCP value in the IPv4 header to that the AFTR/B4 copies the DSCP value in the IPv4 header
the Traffic Class field in the IPv6 header, after the to the Traffic Class field in the IPv6 header, after the
IPv4-in-IPv6 encapsulation."; IPv4-in-IPv6 encapsulation.";
reference reference
"Section 2.10 of RFC 6908."; "Section 2.10 of RFC 6908.";
} }
} }
augment "/nat:nat/nat:instances/nat:instance/nat:policy" { augment "/nat:nat/nat:instances/nat:instance/nat:policy" {
when "derived-from-or-self(/nat:nat/nat:instances/nat:instance/" + when "derived-from-or-self(/nat:nat/nat:instances/nat:instance/" +
"nat:type, 'nat:napt44')" + "nat:type, 'nat:napt44')" +
" and /nat:nat/nat:instances/nat:instance/" + " and /nat:nat/nat:instances/nat:instance/" +
 End of changes. 9 change blocks. 
12 lines changed or deleted 12 lines changed or added

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