draft-ietf-v6ops-rfc7084-bis-00.txt   draft-ietf-v6ops-rfc7084-bis-01.txt 
IPv6 Operations (v6ops) J. Palet Martinez IPv6 Operations (v6ops) J. Palet Martinez
Internet-Draft Consulintel, S.L. Internet-Draft Consulintel, S.L.
Obsoletes: 7084 (if approved) April 5, 2017 Obsoletes: 7084 (if approved) April 10, 2017
Intended status: Informational Intended status: Informational
Expires: October 7, 2017 Expires: October 12, 2017
Basic Requirements for IPv6 Customer Edge Routers Basic Requirements for IPv6 Customer Edge Routers
draft-ietf-v6ops-rfc7084-bis-00 draft-ietf-v6ops-rfc7084-bis-01
Abstract Abstract
This document specifies requirements for an IPv6 Customer Edge (CE) This document specifies requirements for an IPv6 Customer Edge (CE)
router. Specifically, the current version of this document focuses router. Specifically, the current version of this document focuses
on the basic provisioning of an IPv6 CE router and the provisioning on the basic provisioning of an IPv6 CE router and the provisioning
of IPv6 hosts attached to it. The document also covers several of IPv6 hosts attached to it. The document also covers several
transition technologies, as required in a world where IPv4 addresses transition technologies, as required in a world where IPv4 addresses
are no longer available, so hosts in the customer LANs with IPv4-only are no longer available, so hosts in the customer LANs with IPv4-only
or IPv6-only applications or devices, requiring to communicate with or IPv6-only applications or devices, requiring to communicate with
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 October 7, 2017. This Internet-Draft will expire on October 12, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
skipping to change at page 2, line 26 skipping to change at page 2, line 26
4. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Architecture . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Current IPv4 End-User Network Architecture . . . . . . . 6 4.1. Current IPv4 End-User Network Architecture . . . . . . . 6
4.2. IPv6 End-User Network Architecture . . . . . . . . . . . 6 4.2. IPv6 End-User Network Architecture . . . . . . . . . . . 6
4.2.1. Local Communication . . . . . . . . . . . . . . . . . 8 4.2.1. Local Communication . . . . . . . . . . . . . . . . . 8
5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 8 5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 8
5.1. General Requirements . . . . . . . . . . . . . . . . . . 8 5.1. General Requirements . . . . . . . . . . . . . . . . . . 8
5.2. WAN-Side Configuration . . . . . . . . . . . . . . . . . 9 5.2. WAN-Side Configuration . . . . . . . . . . . . . . . . . 9
5.3. LAN-Side Configuration . . . . . . . . . . . . . . . . . 13 5.3. LAN-Side Configuration . . . . . . . . . . . . . . . . . 13
5.4. Transition Technologies Support . . . . . . . . . . . . . 15 5.4. Transition Technologies Support . . . . . . . . . . . . . 15
5.4.1. 464XLAT . . . . . . . . . . . . . . . . . . . . . . . 15 5.4.1. 464XLAT . . . . . . . . . . . . . . . . . . . . . . . 15
5.4.2. 6in4 . . . . . . . . . . . . . . . . . . . . . . . . 16 5.4.2. 6in4 . . . . . . . . . . . . . . . . . . . . . . . . 15
5.4.3. 6rd . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.4.3. 6rd . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.4.4. Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . . . 18 5.4.4. Dual-Stack Lite (DS-Lite) . . . . . . . . . . . . . . 18
5.4.5. Lightweight 4over6 (lw4o6) . . . . . . . . . . . . . 19 5.4.5. Lightweight 4over6 (lw4o6) . . . . . . . . . . . . . 19
5.4.6. MAP-E . . . . . . . . . . . . . . . . . . . . . . . . 19 5.4.6. MAP-E . . . . . . . . . . . . . . . . . . . . . . . . 19
5.4.7. MAP-T . . . . . . . . . . . . . . . . . . . . . . . . 20 5.4.7. MAP-T . . . . . . . . . . . . . . . . . . . . . . . . 20
5.5. IPv4 Multicast Support . . . . . . . . . . . . . . . . . 20 5.5. IPv4 Multicast Support . . . . . . . . . . . . . . . . . 20
5.6. Security Considerations . . . . . . . . . . . . . . . . . 21 5.6. Security Considerations . . . . . . . . . . . . . . . . . 21
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22
8. ANNEX A: Code Considerations . . . . . . . . . . . . . . . . 22 8. ANNEX A: Code Considerations . . . . . . . . . . . . . . . . 22
9. ANNEX B: Changes from RFC7084 . . . . . . . . . . . . . . . . 23 9. ANNEX B: Changes from RFC7084 . . . . . . . . . . . . . . . . 23
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 10. ANNEX C: Changes from RFC7084-bis-00 . . . . . . . . . . . . 23
10.1. Normative References . . . . . . . . . . . . . . . . . . 23 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.2. Informative References . . . . . . . . . . . . . . . . . 28 11.1. Normative References . . . . . . . . . . . . . . . . . . 24
11.2. Informative References . . . . . . . . . . . . . . . . . 29
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 29 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 29
1. Introduction 1. Introduction
This document defines basic IPv6 features for a residential or small- This document defines basic IPv6 features for a residential or small-
office router, referred to as an "IPv6 CE router", in order to office router, referred to as an "IPv6 CE router", in order to
establish an industry baseline for features to be implemented on such establish an industry baseline for features to be implemented on such
a router. a router.
These routers typically also support IPv4, at least in the LAN side. These routers typically also support IPv4, at least in the LAN side.
skipping to change at page 14, line 45 skipping to change at page 14, line 45
IA_NA option, it SHOULD set the M flag to zero and the O flag IA_NA option, it SHOULD set the M flag to zero and the O flag
to 1 in its Router Advertisement messages [RFC4861]. to 1 in its Router Advertisement messages [RFC4861].
L-10: The IPv6 CE router MUST support providing DNS information in L-10: The IPv6 CE router MUST support providing DNS information in
the DHCPv6 DNS_SERVERS and DOMAIN_LIST options [RFC3646]. the DHCPv6 DNS_SERVERS and DOMAIN_LIST options [RFC3646].
L-11: The IPv6 CE router MUST support providing DNS information in L-11: The IPv6 CE router MUST support providing DNS information in
the Router Advertisement Recursive DNS Server (RDNSS) and DNS the Router Advertisement Recursive DNS Server (RDNSS) and DNS
Search List options. Both options are specified in [RFC6106]. Search List options. Both options are specified in [RFC6106].
L-12: The IPv6 CE router SHOULD make available a subset of DHCPv6 L-12: The IPv6 CE router SHOULD implement a DNS proxy as described
in [RFC5625].
L-13: The IPv6 CE router SHOULD make available a subset of DHCPv6
options (as listed in Section 5.3 of [RFC3736]) received from options (as listed in Section 5.3 of [RFC3736]) received from
the DHCPv6 client on its WAN interface to its LAN-side DHCPv6 the DHCPv6 client on its WAN interface to its LAN-side DHCPv6
server. server.
L-13: If the delegated prefix changes, i.e., the current prefix is L-14: If the delegated prefix changes, i.e., the current prefix is
replaced with a new prefix without any overlapping time replaced with a new prefix without any overlapping time
period, then the IPv6 CE router MUST immediately advertise the period, then the IPv6 CE router MUST immediately advertise the
old prefix with a Preferred Lifetime of zero and a Valid old prefix with a Preferred Lifetime of zero and a Valid
Lifetime of either a) zero or b) the lower of the current Lifetime of either a) zero or b) the lower of the current
Valid Lifetime and two hours (which must be decremented in Valid Lifetime and two hours (which must be decremented in
real time) in a Router Advertisement message as described in real time) in a Router Advertisement message as described in
Section 5.5.3, (e) of [RFC4862]. Section 5.5.3, (e) of [RFC4862].
L-14: The IPv6 CE router MUST send an ICMPv6 Destination Unreachable L-15: The IPv6 CE router MUST send an ICMPv6 Destination Unreachable
message, code 5 (Source address failed ingress/egress policy) message, code 5 (Source address failed ingress/egress policy)
for packets forwarded to it that use an address from a prefix for packets forwarded to it that use an address from a prefix
that has been invalidated. that has been invalidated.
L-15: The IPv6 CE router SHOULD provide HNCP (Home Networking L-16: The IPv6 CE router SHOULD provide HNCP (Home Networking
Control Protocol) services, as specified in [RFC7788]. Control Protocol) services, as specified in [RFC7788].
5.4. Transition Technologies Support 5.4. Transition Technologies Support
5.4.1. 464XLAT 5.4.1. 464XLAT
464XLAT [RFC6877] is a technique to provide IPv4 access service to 464XLAT [RFC6877] is a technique to provide IPv4 access service to
IPv6-only edge networks without encapsulation. IPv6-only edge networks without encapsulation.
The CE router SHOULD support CLAT functionality. If 464XLAT is The CE router SHOULD support CLAT functionality. If 464XLAT is
skipping to change at page 15, line 44 skipping to change at page 15, line 48
using DHCPv6-PD [RFC3633]. using DHCPv6-PD [RFC3633].
464XLAT-2: The CE router MUST implement [RFC7050] in order to 464XLAT-2: The CE router MUST implement [RFC7050] in order to
discover the PLAT-side translation IPv4 and IPv6 discover the PLAT-side translation IPv4 and IPv6
prefix(es)/suffix(es). In environments with PCP support, prefix(es)/suffix(es). In environments with PCP support,
the CE SHOULD follow [RFC7225] to learn the PLAT-side the CE SHOULD follow [RFC7225] to learn the PLAT-side
translation IPv4 and IPv6 prefix(es)/suffix(es) used by translation IPv4 and IPv6 prefix(es)/suffix(es) used by
an upstream PCP-controlled NAT64 device. Alternatively an upstream PCP-controlled NAT64 device. Alternatively
SHOULD support draft-li-intarea-nat64-prefix-dhcp-option. SHOULD support draft-li-intarea-nat64-prefix-dhcp-option.
464XLAT-3: The CE router MUST implement a DNS proxy as described in
[RFC5625].
464XLAT-4: The CE router MUST support the DHCPv4-over-DHCPv6 (DHCP
4o6) transport described in [RFC7341].
5.4.2. 6in4 5.4.2. 6in4
6in4 [RFC4213] specifies a tunneling mechanism to allow end-users to 6in4 [RFC4213] specifies a tunneling mechanism to allow end-users to
manually configure IPv6 support via a service provider's IPv4 network manually configure IPv6 support via a service provider's IPv4 network
infrastructure. infrastructure.
The CE router MAY support 6in4 functionality. If 6rd is implemented, The CE router MAY support 6in4 functionality. If 6rd is implemented,
6in4 MUST be supported as well. If 6in4 is supported, it MUST be 6in4 MUST be supported as well. If 6in4 is supported, it MUST be
implemented according to [RFC4213]. The following CE Requirements implemented according to [RFC4213]. The following CE Requirements
also apply: also apply:
skipping to change at page 18, line 47 skipping to change at page 18, line 41
DS-Lite requirements: DS-Lite requirements:
DSLITE-1: The CE router MUST support configuration of DS-Lite via DSLITE-1: The CE router MUST support configuration of DS-Lite via
the DS-Lite DHCPv6 option [RFC6334]. The IPv6 CE router the DS-Lite DHCPv6 option [RFC6334]. The IPv6 CE router
MAY use other mechanisms to configure DS-Lite parameters. MAY use other mechanisms to configure DS-Lite parameters.
Such mechanisms are outside the scope of this document. Such mechanisms are outside the scope of this document.
DSLITE-2: The CE router MUST support the DHCPv6 S46 priority option DSLITE-2: The CE router MUST support the DHCPv6 S46 priority option
described in [RFC8026]. described in [RFC8026].
DSLITE-3: The CE router MUST support the DHCPv4-over-DHCPv6 (DHCP DSLITE-3: The IPv6 CE router MUST NOT perform IPv4 Network Address
4o6) transport described in [RFC7341].
DSLITE-4: The IPv6 CE router MUST NOT perform IPv4 Network Address
Translation (NAT) on IPv4 traffic encapsulated using DS- Translation (NAT) on IPv4 traffic encapsulated using DS-
Lite. Lite.
DSLITE-5: If the IPv6 CE router is configured with an IPv4 address DSLITE-4: If the IPv6 CE router is configured with an IPv4 address
on its WAN interface, then the IPv6 CE router SHOULD on its WAN interface, then the IPv6 CE router SHOULD
disable the DS-Lite Basic Bridging BroadBand (B4) element. disable the DS-Lite Basic Bridging BroadBand (B4) element.
5.4.5. Lightweight 4over6 (lw4o6) 5.4.5. Lightweight 4over6 (lw4o6)
Lw4o6 [RFC7596] specifies an extension to DS-Lite, which moves the Lw4o6 [RFC7596] specifies an extension to DS-Lite, which moves the
NAPT function from the DS-Lite tunnel concentrator to the tunnel NAPT function from the DS-Lite tunnel concentrator to the tunnel
client located in the IPv6 CE router, removing the requirement for a client located in the IPv6 CE router, removing the requirement for a
CGN function in the tunnel concentrator and reducing the amount of CGN function in the tunnel concentrator and reducing the amount of
centralized state. centralized state.
skipping to change at page 19, line 36 skipping to change at page 19, line 32
lw4o6 DHCPv6 options [RFC7598]. The IPv6 CE router MAY use lw4o6 DHCPv6 options [RFC7598]. The IPv6 CE router MAY use
other mechanisms to configure lw4o6 parameters. Such other mechanisms to configure lw4o6 parameters. Such
mechanisms are outside the scope of this document. mechanisms are outside the scope of this document.
LW4O6-2: The CE router MUST support the DHCPv6 S46 priority option LW4O6-2: The CE router MUST support the DHCPv6 S46 priority option
described in [RFC8026]. described in [RFC8026].
LW4O6-3: The CE router MUST support the DHCPv4-over-DHCPv6 (DHCP LW4O6-3: The CE router MUST support the DHCPv4-over-DHCPv6 (DHCP
4o6) transport described in [RFC7341]. 4o6) transport described in [RFC7341].
LW4O6-4: The IPv6 CE router MUST perform IPv4 Network Address LW4O6-4: The CE router MAY support Dynamic Allocation of Shared IPv4
Translation (NAT) on IPv4 traffic encapsulated using lw4o6. Addresses as described in [RFC7618].
LW4O6-5: If the IPv6 CE router is configured with an IPv4 address on LW4O6-5: The IPv6 CE router MUST perform port-restricted IPv4
Network Address Translation (NAT) on IPv4 traffic
encapsulated using lw4o6.
LW4O6-6: If the IPv6 CE router is configured with an IPv4 address on
its WAN interface, then the IPv6 CE router SHOULD disable its WAN interface, then the IPv6 CE router SHOULD disable
the Lightweight Basic Bridging BroadBand (B4) element. the Lightweight Basic Bridging BroadBand (B4) element.
5.4.6. MAP-E 5.4.6. MAP-E
MAP-E [RFC7597] is a mechanism for transporting IPv4 packets across MAP-E [RFC7597] is a mechanism for transporting IPv4 packets across
an IPv6 network using IP encapsulation, including a generic mechanism an IPv6 network using IP encapsulation, including a generic mechanism
for mapping between IPv6 addresses and IPv4 addresses as well as for mapping between IPv6 addresses and IPv4 addresses as well as
transport-layer ports. transport-layer ports.
skipping to change at page 20, line 15 skipping to change at page 20, line 15
MAP-E requirements: MAP-E requirements:
MAPE-1: The CE router MUST support configuration of MAP-E via the MAPE-1: The CE router MUST support configuration of MAP-E via the
MAP-E DHCPv6 options [RFC7598]. The IPv6 CE router MAY use MAP-E DHCPv6 options [RFC7598]. The IPv6 CE router MAY use
other mechanisms to configure MAP-E parameters. Such other mechanisms to configure MAP-E parameters. Such
mechanisms are outside the scope of this document. mechanisms are outside the scope of this document.
MAPE-2: The CE router MUST support the DHCPv6 S46 priority option MAPE-2: The CE router MUST support the DHCPv6 S46 priority option
described in [RFC8026]. described in [RFC8026].
MAPE-3: The CE router MUST support the DHCPv4-over-DHCPv6 (DHCP 4o6) MAPE-3: The IPv6 CE router MUST perform port-restricted IPv4 Network
transport described in [RFC7341]. Address Translation (NAT) on IPv4 traffic encapsulated using
MAP-E.
MAPE-4: The IPv6 CE router MUST perform IPv4 Network Address
Translation (NAT) on IPv4 traffic encapsulated using MAP-E.
5.4.7. MAP-T 5.4.7. MAP-T
MAP-T [RFC7599] is a mechanism similar to MAP-E, differing from it in MAP-T [RFC7599] is a mechanism similar to MAP-E, differing from it in
that MAP-T uses IPv4-IPv6 translation, rather than encapsulation, as that MAP-T uses IPv4-IPv6 translation, rather than encapsulation, as
the form of IPv6 domain transport. the form of IPv6 domain transport.
The CE router SHOULD support MAP-T functionality. If MAP-T is The CE router SHOULD support MAP-T functionality. If MAP-T is
supported, it MUST be implemented according to [RFC7599]. The supported, it MUST be implemented according to [RFC7599]. The
following CE Requirements also apply: following CE Requirements also apply:
skipping to change at page 20, line 41 skipping to change at page 20, line 39
MAP-T requirements: MAP-T requirements:
MAPT-1: The CE router MUST support configuration of MAP-T via the MAPT-1: The CE router MUST support configuration of MAP-T via the
MAP-E DHCPv6 options [RFC7598]. The IPv6 CE router MAY use MAP-E DHCPv6 options [RFC7598]. The IPv6 CE router MAY use
other mechanisms to configure MAP-E parameters. Such other mechanisms to configure MAP-E parameters. Such
mechanisms are outside the scope of this document. mechanisms are outside the scope of this document.
MAPT-2: The CE router MUST support the DHCPv6 S46 priority option MAPT-2: The CE router MUST support the DHCPv6 S46 priority option
described in [RFC8026]. described in [RFC8026].
MAPT-3: The CE router MUST support the DHCPv4-over-DHCPv6 (DHCP 4o6) MAPT-3: The IPv6 CE router MUST perform port-restricted IPv4 Network
transport described in [RFC7341]. Address Translation (NAT) on IPv4 traffic translated using
MAP-T.
MAPT-4: The IPv6 CE router MUST perform IPv4 Network Address
Translation (NAT) on IPv4 traffic translated using MAP-T.
5.5. IPv4 Multicast Support 5.5. IPv4 Multicast Support
Actual deployments support IPv4 multicast for services such as IPTV. Actual deployments support IPv4 multicast for services such as IPTV.
In the transition phase it is expected that multicast services will In the transition phase it is expected that multicast services will
still be provided using IPv4 to the customer LANs. still be provided using IPv4 to the customer LANs.
In order to support the delivery of IPv4 multicast services to IPv4 In order to support the delivery of IPv4 multicast services to IPv4
clients over an IPv6 multicast network, the CE router SHOULD support clients over an IPv6 multicast network, the CE router SHOULD support
[RFC8114] and [RFC8115]. [RFC8114] and [RFC8115].
skipping to change at page 21, line 40 skipping to change at page 21, line 36
was downgraded from a MUST from RFC 6204 due to the difficulty was downgraded from a MUST from RFC 6204 due to the difficulty
of implementation in the CE router and the feature's redundancy of implementation in the CE router and the feature's redundancy
with upstream router ingress filtering. with upstream router ingress filtering.
S-3: If the IPv6 CE router firewall is configured to filter incoming S-3: If the IPv6 CE router firewall is configured to filter incoming
tunneled data, the firewall SHOULD provide the capability to tunneled data, the firewall SHOULD provide the capability to
filter decapsulated packets from a tunnel. filter decapsulated packets from a tunnel.
6. Acknowledgements 6. Acknowledgements
Thanks to Mohamed Boucadair for his review and comments. Thanks to Mohamed Boucadair, Masanobu Kawashima and Mikael
Abrahamsson for their review and comments.
This document is an update of RFC7084, whose original authors were: This document is an update of RFC7084, whose original authors were:
Hemant Singh, Wes Beebee, Chris Donley and Barbara Stark. The rest Hemant Singh, Wes Beebee, Chris Donley and Barbara Stark. The rest
of the text on this section and the Contributors section, are the of the text on this section and the Contributors section, are the
original acknowledgements and Contributors sections of the earlier original acknowledgements and Contributors sections of the earlier
version of this document. version of this document.
Thanks to the following people (in alphabetical order) for their Thanks to the following people (in alphabetical order) for their
guidance and feedback: guidance and feedback:
skipping to change at page 23, line 13 skipping to change at page 23, line 12
the development cost is negligent, and only integration and testing the development cost is negligent, and only integration and testing
cost may become a minor issue. cost may become a minor issue.
9. ANNEX B: Changes from RFC7084 9. ANNEX B: Changes from RFC7084
The -bis version of this document has some minor text edits here and The -bis version of this document has some minor text edits here and
there. Significant updates are: there. Significant updates are:
1. New section "Usage Scenarios". 1. New section "Usage Scenarios".
2. Added support of HNCP ([RFC7788]) in LAN (L-15). 2. Added support of HNCP ([RFC7788]) in LAN (L-16).
3. Added support of 464XLAT ([RFC6877]). 3. Added support of 464XLAT ([RFC6877]).
4. Added support of lw4o6 ([RFC7596]). 4. Added support of lw4o6 ([RFC7596]).
5. Added support of MAP-E ([RFC7597]) and MAP-T ([RFC7599]). 5. Added support of MAP-E ([RFC7597]) and MAP-T ([RFC7599]).
6. As the main scope of this document is the IPv6-only CE (IPv6-only 6. As the main scope of this document is the IPv6-only CE (IPv6-only
in the WAN link), the support of 6rd ([RFC5969]) has been changed in the WAN link), the support of 6rd ([RFC5969]) has been changed
to MAY. 6in4 ([RFC4213]) support has been included as well in to MAY. 6in4 ([RFC4213]) support has been included as well in
case 6rd is supported, as it doesn't require additional code. case 6rd is supported, as it doesn't require additional code.
7. New section "IPv4 Multicast Support". 7. New section "IPv4 Multicast Support".
10. References 8. Added support for DNS proxy [RFC5625] as general LAN requirement.
10.1. Normative References 10. ANNEX C: Changes from RFC7084-bis-00
Section to be removed for WGLC. Significant updates are:
1. LW4O6-5 changed to port-restricted to conform with [RFC7596].
2. MAPE-3 changed to port-restricted to conform with [RFC7597].
3. MAPT-3 changed to port-restricted to conform with [RFC7599].
4. [RFC7341] removed from 464XLAT, DS-LITE, MAP-E and MAP-T
requirements.
5. [RFC5625] removed from 464XLAT, and included as general LAN
requirement.
6. [RFC7618] included as MAY for lw4o6.
11. References
11.1. Normative References
[RFC1122] Braden, R., Ed., "Requirements for Internet Hosts - [RFC1122] Braden, R., Ed., "Requirements for Internet Hosts -
Communication Layers", STD 3, RFC 1122, Communication Layers", STD 3, RFC 1122,
DOI 10.17487/RFC1122, October 1989, DOI 10.17487/RFC1122, October 1989,
<http://www.rfc-editor.org/info/rfc1122>. <http://www.rfc-editor.org/info/rfc1122>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 28, line 10 skipping to change at page 28, line 27
W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for
Configuration of Softwire Address and Port-Mapped Configuration of Softwire Address and Port-Mapped
Clients", RFC 7598, DOI 10.17487/RFC7598, July 2015, Clients", RFC 7598, DOI 10.17487/RFC7598, July 2015,
<http://www.rfc-editor.org/info/rfc7598>. <http://www.rfc-editor.org/info/rfc7598>.
[RFC7599] Li, X., Bao, C., Dec, W., Ed., Troan, O., Matsushima, S., [RFC7599] Li, X., Bao, C., Dec, W., Ed., Troan, O., Matsushima, S.,
and T. Murakami, "Mapping of Address and Port using and T. Murakami, "Mapping of Address and Port using
Translation (MAP-T)", RFC 7599, DOI 10.17487/RFC7599, July Translation (MAP-T)", RFC 7599, DOI 10.17487/RFC7599, July
2015, <http://www.rfc-editor.org/info/rfc7599>. 2015, <http://www.rfc-editor.org/info/rfc7599>.
[RFC7618] Cui, Y., Sun, Q., Farrer, I., Lee, Y., Sun, Q., and M.
Boucadair, "Dynamic Allocation of Shared IPv4 Addresses",
RFC 7618, DOI 10.17487/RFC7618, August 2015,
<http://www.rfc-editor.org/info/rfc7618>.
[RFC7788] Stenberg, M., Barth, S., and P. Pfister, "Home Networking [RFC7788] Stenberg, M., Barth, S., and P. Pfister, "Home Networking
Control Protocol", RFC 7788, DOI 10.17487/RFC7788, April Control Protocol", RFC 7788, DOI 10.17487/RFC7788, April
2016, <http://www.rfc-editor.org/info/rfc7788>. 2016, <http://www.rfc-editor.org/info/rfc7788>.
[RFC8026] Boucadair, M. and I. Farrer, "Unified IPv4-in-IPv6 [RFC8026] Boucadair, M. and I. Farrer, "Unified IPv4-in-IPv6
Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Softwire Customer Premises Equipment (CPE): A DHCPv6-Based
Prioritization Mechanism", RFC 8026, DOI 10.17487/RFC8026, Prioritization Mechanism", RFC 8026, DOI 10.17487/RFC8026,
November 2016, <http://www.rfc-editor.org/info/rfc8026>. November 2016, <http://www.rfc-editor.org/info/rfc8026>.
[RFC8114] Boucadair, M., Qin, C., Jacquenet, C., Lee, Y., and Q. [RFC8114] Boucadair, M., Qin, C., Jacquenet, C., Lee, Y., and Q.
Wang, "Delivery of IPv4 Multicast Services to IPv4 Clients Wang, "Delivery of IPv4 Multicast Services to IPv4 Clients
over an IPv6 Multicast Network", RFC 8114, over an IPv6 Multicast Network", RFC 8114,
DOI 10.17487/RFC8114, March 2017, DOI 10.17487/RFC8114, March 2017,
<http://www.rfc-editor.org/info/rfc8114>. <http://www.rfc-editor.org/info/rfc8114>.
[RFC8115] Boucadair, M., Qin, J., Tsou, T., and X. Deng, "DHCPv6 [RFC8115] Boucadair, M., Qin, J., Tsou, T., and X. Deng, "DHCPv6
Option for IPv4-Embedded Multicast and Unicast IPv6 Option for IPv4-Embedded Multicast and Unicast IPv6
Prefixes", RFC 8115, DOI 10.17487/RFC8115, March 2017, Prefixes", RFC 8115, DOI 10.17487/RFC8115, March 2017,
<http://www.rfc-editor.org/info/rfc8115>. <http://www.rfc-editor.org/info/rfc8115>.
10.2. Informative References 11.2. Informative References
[RFC6144] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for [RFC6144] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for
IPv4/IPv6 Translation", RFC 6144, DOI 10.17487/RFC6144, IPv4/IPv6 Translation", RFC 6144, DOI 10.17487/RFC6144,
April 2011, <http://www.rfc-editor.org/info/rfc6144>. April 2011, <http://www.rfc-editor.org/info/rfc6144>.
[RFC7157] Troan, O., Ed., Miles, D., Matsushima, S., Okimoto, T., [RFC7157] Troan, O., Ed., Miles, D., Matsushima, S., Okimoto, T.,
and D. Wing, "IPv6 Multihoming without Network Address and D. Wing, "IPv6 Multihoming without Network Address
Translation", RFC 7157, DOI 10.17487/RFC7157, March 2014, Translation", RFC 7157, DOI 10.17487/RFC7157, March 2014,
<http://www.rfc-editor.org/info/rfc7157>. <http://www.rfc-editor.org/info/rfc7157>.
 End of changes. 23 change blocks. 
41 lines changed or deleted 61 lines changed or added

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