draft-ietf-dime-4over6-provisioning-03.txt   draft-ietf-dime-4over6-provisioning-04.txt 
Internet Engineering Task Force C. Zhou Internet Engineering Task Force C. Zhou
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Standards Track T. Taylor Intended status: Standards Track T. Taylor
Expires: December 25, 2015 PT Taylor Consulting Expires: January 21, 2016 PT Taylor Consulting
Q. Sun Q. Sun
China Telecom China Telecom
M. Boucadair M. Boucadair
France Telecom France Telecom
June 23, 2015 July 20, 2015
Attribute-Value Pairs For Provisioning Customer Equipment Supporting Attribute-Value Pairs For Provisioning Customer Equipment Supporting
IPv4-Over-IPv6 Transitional Solutions IPv4-Over-IPv6 Transitional Solutions
draft-ietf-dime-4over6-provisioning-03 draft-ietf-dime-4over6-provisioning-04
Abstract Abstract
During the transition from IPv4 to IPv6, customer equipment may have During the transition from IPv4 to IPv6, customer equipment may have
to support one of the various transition methods that have been to support one of the various transition methods that have been
defined for carrying IPv4 packets over IPv6. This document defined for carrying IPv4 packets over IPv6. This document
enumerates the information that needs to be provisioned on a customer enumerates the information that needs to be provisioned on a customer
edge router to support a list of transition techniques based on edge router to support a list of transition techniques based on
tunneling IPv4 in IPv6, with a view to defining reusable components tunneling IPv4 in IPv6, with a view to defining reusable components
for a reasonable transition path between these techniques. To the for a reasonable transition path between these techniques. To the
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 25, 2015. This Internet-Draft will expire on January 21, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 27 skipping to change at page 2, line 27
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
2. Description of the Parameters Required By Each Transition 2. Description of the Parameters Required By Each Transition
Method . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Method . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Parameters For Dual-Stack Lite (DS-Lite) . . . . . . . . 5 2.1. Parameters For Dual-Stack Lite (DS-Lite) . . . . . . . . 5
2.2. Lightweight IPv4 Over IPv6 (LW4over6) . . . . . . . . . . 5 2.2. Lightweight 4over6 (lw4o6) . . . . . . . . . . . . . . . 5
2.3. Port Set Specification . . . . . . . . . . . . . . . . . 6 2.3. Port Set Specification . . . . . . . . . . . . . . . . . 6
2.4. Mapping of Address and Port with Encapsulation (MAP-E) . 6 2.4. Mapping of Address and Port with Encapsulation (MAP-E) . 6
2.5. Parameters For Multicast . . . . . . . . . . . . . . . . 7 2.5. Parameters For Multicast . . . . . . . . . . . . . . . . 7
2.6. Summary and Discussion . . . . . . . . . . . . . . . . . 8 2.6. Summary and Discussion . . . . . . . . . . . . . . . . . 8
3. Attribute-Value Pair Definitions . . . . . . . . . . . . . . 8 3. Attribute-Value Pair Definitions . . . . . . . . . . . . . . 8
3.1. IP-Prefix-Length AVP . . . . . . . . . . . . . . . . . . 9 3.1. IP-Prefix-Length AVP . . . . . . . . . . . . . . . . . . 9
3.2. Border-Router-Name AVP . . . . . . . . . . . . . . . . . 9 3.2. Border-Router-Name AVP . . . . . . . . . . . . . . . . . 9
3.3. 64-Multicast-Attributes AVP . . . . . . . . . . . . . . . 9 3.3. 64-Multicast-Attributes AVP . . . . . . . . . . . . . . . 9
3.3.1. ASM-mPrefix64 AVP . . . . . . . . . . . . . . . . . . 10 3.3.1. ASM-mPrefix64 AVP . . . . . . . . . . . . . . . . . . 9
3.3.2. SSM-mPrefix64 AVP . . . . . . . . . . . . . . . . . . 10 3.3.2. SSM-mPrefix64 AVP . . . . . . . . . . . . . . . . . . 10
3.3.3. Delegated-IPv6-Prefix AVP As uPrefix64 . . . . . . . 11 3.3.3. Delegated-IPv6-Prefix AVP As uPrefix64 . . . . . . . 11
3.4. Tunnel-Source-Pref-Or-Addr AVP . . . . . . . . . . . . . 11 3.4. Tunnel-Source-Pref-Or-Addr AVP . . . . . . . . . . . . . 11
3.4.1. Delegated-IPv6-Prefix As the IPv6 Binding Prefix . . 11 3.4.1. Delegated-IPv6-Prefix As the IPv6 Binding Prefix . . 11
3.4.2. Tunnel-Source-IPv6-Address AVP . . . . . . . . . . . 12 3.4.2. Tunnel-Source-IPv6-Address AVP . . . . . . . . . . . 11
3.5. Port-Set-Identifier . . . . . . . . . . . . . . . . . . . 12 3.5. Port-Set-Identifier . . . . . . . . . . . . . . . . . . . 12
3.6. LW4over6-Binding AVP . . . . . . . . . . . . . . . . . . 12 3.6. Lw4o6-Binding AVP . . . . . . . . . . . . . . . . . . . . 12
3.6.1. LW4over6-External-IPv4-Addr AVP . . . . . . . . . . . 13 3.6.1. Lw4o6-External-IPv4-Addr AVP . . . . . . . . . . . . 13
3.7. MAP-E-Attributes . . . . . . . . . . . . . . . . . . . . 13 3.7. MAP-E-Attributes . . . . . . . . . . . . . . . . . . . . 13
3.8. MAP-Mesh-Mode . . . . . . . . . . . . . . . . . . . . . . 14 3.8. MAP-Mesh-Mode . . . . . . . . . . . . . . . . . . . . . . 14
3.9. MAP-Mapping-Rule . . . . . . . . . . . . . . . . . . . . 14 3.9. MAP-Mapping-Rule . . . . . . . . . . . . . . . . . . . . 14
3.9.1. Rule-IPv4-Addr-Or-Prefix AVP . . . . . . . . . . . . 15 3.9.1. Rule-IPv4-Addr-Or-Prefix AVP . . . . . . . . . . . . 15
3.9.2. Rule-IPv6-Prefix AVP . . . . . . . . . . . . . . . . 15 3.9.2. Rule-IPv6-Prefix AVP . . . . . . . . . . . . . . . . 15
3.9.3. EA-Field-Length AVP . . . . . . . . . . . . . . . . . 16 3.9.3. EA-Field-Length AVP . . . . . . . . . . . . . . . . . 16
4. Attribute Value Pair flag rules . . . . . . . . . . . . . . . 16 4. Attribute Value Pair Flag Rules . . . . . . . . . . . . . . . 16
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18
7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 6.1. Man-In-The-Middle (MITM) Attacks . . . . . . . . . . . . 18
6.2. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 19
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.1. Normative References . . . . . . . . . . . . . . . . . . 19 8.1. Normative References . . . . . . . . . . . . . . . . . . 19
8.2. Informative References . . . . . . . . . . . . . . . . . 20 8.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
A number of transition techniques have been defined to allow IPv4 A number of transition techniques have been defined to allow IPv4
packets to pass between hosts and IPv4 networks over an intervening packets to pass between hosts and IPv4 networks over an intervening
IPv6 network while minimizing the number of public IPv4 addresses IPv6 network while minimizing the number of public IPv4 addresses
that need to be consumed by the hosts. Different operators will that need to be consumed by the hosts. Different operators will
deploy different technologies, and sometimes one operator will use deploy different technologies, and sometimes one operator will use
more than one technology, depending on what is supported by the more than one technology, depending on what is supported by the
available equipment and upon other factors both technical and available equipment and upon other factors both technical and
skipping to change at page 3, line 31 skipping to change at page 3, line 33
Each technique requires the provisioning of some subscriber-specific Each technique requires the provisioning of some subscriber-specific
information on the customer edge device. The provisioning may be by information on the customer edge device. The provisioning may be by
DHCPv6 [RFC3315] or by some other method. This document is DHCPv6 [RFC3315] or by some other method. This document is
indifferent to the specific provisioning technique used, but assumes indifferent to the specific provisioning technique used, but assumes
a deployment in which that information is managed by AAA a deployment in which that information is managed by AAA
(Authentication, Authorization, and Accounting) servers. It further (Authentication, Authorization, and Accounting) servers. It further
assumes that this information is delivered to intermediate network assumes that this information is delivered to intermediate network
nodes for onward provisioning using the Diameter protocol [RFC6733]. nodes for onward provisioning using the Diameter protocol [RFC6733].
As described below, in the particular case where the Lightweight IPv4 As described below, in the particular case where the Lightweight
Over IPv6 (Lw4o6) [I-D.ietf-softwire-lw4over6] transition method has 4over6 (lw4o6) [I-D.ietf-softwire-lw4over6] transition method has
been deployed, per-subscriber-site information almost identical to been deployed, per-subscriber-site information almost identical to
that passed to the subscriber site [I-D.ietf-softwire-map-dhcp] also that passed to the subscriber site [I-D.ietf-softwire-map-dhcp] also
needs to be delivered to the border router serving that site. The needs to be delivered to the border router serving that site. The
Diameter protocol may be used for this purpose too. Diameter protocol may be used for this purpose too.
This document analyzes the information required to configure the This document analyzes the information required to configure the
customer edge equipment for the following set of transition methods: customer edge equipment for the following set of transition methods:
o Dual-Stack Lite (DS-Lite) [RFC6333], o Dual-Stack Lite (DS-Lite) [RFC6333],
o Lightweight IPv4 Over IPv6 (LW4over6) o Lightweight 4over6 (lw4o6) [I-D.ietf-softwire-lw4over6], and
[I-D.ietf-softwire-lw4over6], and
o Mapping of Address and Port with Encapsulation (MAP-E) o Mapping of Address and Port with Encapsulation (MAP-E)
[I-D.ietf-softwire-map]. [I-D.ietf-softwire-map].
[I-D.ietf-softwire-dslite-multicast] specifies a generic solution for [I-D.ietf-softwire-dslite-multicast] specifies a generic solution for
delivery of IPv4 multicast services to IPv4 clients over an IPv6 delivery of IPv4 multicast services to IPv4 clients over an IPv6
multicast network. The solution was developed with DS-Lite in mind multicast network. The solution was developed with DS-Lite in mind
but it is however not limited to DS-Lite. As such, it applies also but it is however not limited to DS-Lite. As such, it applies also
for LW4over6 and MAP-E. This document analyzes the information for lw4o6 and MAP-E. This document analyzes the information required
required to configure the customer edge equipment for the support of to configure the customer edge equipment for the support of multicast
multicast in the context of DS-Lite, MAP, and LW4over6 in particular. in the context of DS-Lite, MAP-E, and Lightweight 4over6 in
particular.
On the basis of those analyses it specifies a number of attribute- On the basis of those analyses it specifies a number of attribute-
value pairs (AVPs) to allow the necessary subscriber-site-specific value pairs (AVPs) to allow the necessary subscriber-site-specific
configuration information to be carried in Diameter. configuration information to be carried in Diameter.
This document doesn't specify any new commands or Application-Ids and This document doesn't specify any new commands or Application-Ids.
that the AVPs could be used for any Diameter application suitable for The specified AVPs could be used for any Diameter application
provisioning. suitable for provisioning.
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
The abbreviation "CE" denotes the equipment at the customer edge that The abbreviation "CE" denotes the equipment at the customer edge that
terminates the customer end of an IPv6 transitional tunnel. This terminates the customer end of an IPv6 transitional tunnel. This
will usually be a router, but could be a host directly connected to will usually be a router, but could be a host directly connected to
the network. the network.
The term "tunnel source address" is used to denote the IPv6 source The term "tunnel source address" is used to denote the IPv6 source
address used in the outer header of packets sent from the CE through address used in the outer header of packets sent from the CE through
an LW4over6 transitional tunnel to the border router. an lw4o6 transitional tunnel to the border router.
2. Description of the Parameters Required By Each Transition Method 2. Description of the Parameters Required By Each Transition Method
This section reviews the parameters that need to be provisioned for This section reviews the parameters that need to be provisioned for
each of the transition methods listed above. This enumeration each of the transition methods listed above. This enumeration
provides the justification for the AVPs defined in the next section. provides the justification for the AVPs defined in the next section.
A means is required to indicate which transition method(s) a given A means is required to indicate which transition method(s) a given
subscriber is allowed to use. The approach taken in this document is subscriber wants to use. The approach taken in this document is to
to specify Grouped AVPs specific to LW4over6 and MAP-E. The operator specify Grouped AVPs specific to lw4o6 and MAP-E. The operator can
can control which of these two transition methods a given subscriber control which of these two transition methods a given subscriber uses
uses by ensuring that AAA passes only the Grouped AVP relevant to by ensuring that AAA passes only the Grouped AVP relevant to that
that method. A Grouped AVP is unnecessary for Dual-Stack Lite, since method. A Grouped AVP is unnecessary for Dual-Stack Lite, since AAA
AAA has only to provide the Fully Qualified Domain Name (FQDN) of the has only to provide the Fully Qualified Domain Name (FQDN) of the DS-
DS-Lite Address Family Transition Router (AFTR) (see Section 2.1). Lite Address Family Transition Router (AFTR) (see Section 2.1).
Hence when no Grouped AVP is provided either for LW4over6 or MAP-E Hence when no Grouped AVP is provided either for lw4o6 or MAP-E and
and only the AFTR's FQDN is present, this indicates that the only the AFTR's FQDN is present, this indicates that the subscriber
subscriber equipment will use the Dual-Stack Lite transition method. equipment will use the Dual-Stack Lite transition method.
Provisioning of multicast is an orthogonal activity, since it is Provisioning of multicast is an orthogonal activity, since it is
independent of the transition method. independent of the transition method.
2.1. Parameters For Dual-Stack Lite (DS-Lite) 2.1. Parameters For Dual-Stack Lite (DS-Lite)
DS-Lite is documented in [RFC6333]. The Basic Bridging BroadBand DS-Lite is documented in [RFC6333]. The Basic Bridging BroadBand
(B4) element at the customer premises needs to discover the IPv6 (B4) element at the customer premises needs to discover the IPv6
address of the AFTR (border router). For the reasons discussed in address of the AFTR (border router). For the reasons discussed in
Section 3.2, the AAA server provision the B4 element with the AFTR's Section 3.2, the AAA server provision the B4 element with the AFTR's
Fully Qualified Domain Name (FQDN) that is passed to a B4's IP Fully Qualified Domain Name (FQDN) that is passed to a B4's IP
skipping to change at page 5, line 24 skipping to change at page 5, line 27
The B4 element could also be configured with the IPv4 address of the The B4 element could also be configured with the IPv4 address of the
B4 interface facing the tunnel, with valid values from 192.0.0.2 to B4 interface facing the tunnel, with valid values from 192.0.0.2 to
192.0.0.7 and the default value of 192.0.0.2 in the absence of 192.0.0.7 and the default value of 192.0.0.2 in the absence of
provisioning. Provisioning such information through AAA is provisioning. Provisioning such information through AAA is
problematic because it is most likely used in a case where multiple problematic because it is most likely used in a case where multiple
B4 instances occupy the same device. This document therefore assumes B4 instances occupy the same device. This document therefore assumes
that the B4 interface address is determined by other means than AAA that the B4 interface address is determined by other means than AAA
(implementation-dependent or static assignment). (implementation-dependent or static assignment).
2.2. Lightweight IPv4 Over IPv6 (LW4over6) 2.2. Lightweight 4over6 (lw4o6)
Light Weight IPv4 Over IPv6 (LW4over6) is documented in Lightweight 4over6 (lw4o6) is documented in
[I-D.ietf-softwire-lw4over6]. LW4over6 requires four items to be [I-D.ietf-softwire-lw4over6]. Lw4o6 requires four items to be
provisioned to the customer equipment: provisioned to the customer equipment:
o IPv6 address of the border router. o IPv6 address of the border router.
o IPv6 prefix used by the CE to construct the tunnel source address. o IPv6 prefix used by the CE to construct the tunnel source address.
In the terminology of [I-D.ietf-softwire-lw4over6], this is the In the terminology of [I-D.ietf-softwire-lw4over6], this is the
IPv6 Binding Prefix. IPv6 Binding Prefix.
o an IPv4 address to be used on the external side of the CE; and o an IPv4 address to be used on the external side of the CE; and
o if the IPv4 address is shared, a specification of the port set the o if the IPv4 address is shared, a specification of the port set the
subscriber site is allowed to use. Please see the description in subscriber site is allowed to use. Please see the description in
Section 2.3. For LW4over6, all three of the parameters 'a', 'k', Section 2.3. For lw4o6, all three of the parameters 'a', 'k', and
and PSID described in that section are required. The default PSID described in that section are required. The default value of
value of the offset parameter 'a' is 0. the offset parameter 'a' is 0.
As discussed in Section 4 of [I-D.ietf-softwire-lw4over6], it is As discussed in Section 4 of [I-D.ietf-softwire-lw4over6], it is
necessary to synchronize this configuration with corresponding per- necessary to synchronize this configuration with corresponding per-
subscriber configuration at the border router. The border router subscriber configuration at the border router. The border router
information consists of the same public IPv4 address and port set information consists of the same public IPv4 address and port set
parameters that are passed to the CE, bound together with the full parameters that are passed to the CE, bound together with the full
/128 IPv6 address (not just the Binding Prefix) configured as the /128 IPv6 address (not just the Binding Prefix) configured as the
tunnel source address at the CE. tunnel source address at the CE.
2.3. Port Set Specification 2.3. Port Set Specification
When an external IPv4 address is shared, LW4over6 and MAP-E restrict When an external IPv4 address is shared, lw4o6 and MAP-E restrict the
the CE to use of a subset of all available ports on the external CE to use of a subset of all available ports on the external side.
side. Both transition methods use the algorithm defined in Both transition methods use the algorithm defined in Appendix B of
Appendix B of [I-D.ietf-softwire-map] to derive the values of the [I-D.ietf-softwire-map] to derive the values of the port numbers in
port numbers in the port set. This algorithm features three the port set. This algorithm features three parameters, describing
parameters, describing the positioning and value of the Port Set the positioning and value of the Port Set Identifier (PSID) within
Identifier (PSID) within each port number of the generated set: each port number of the generated set:
o an offset 'a' from the beginning of the port number to the first o an offset 'a' from the beginning of the port number to the first
bit of the PSID; bit of the PSID;
o the length 'k' of the PSID within the port number, in bits; and o the length 'k' of the PSID within the port number, in bits; and
o the value of the PSID itself. o the value of the PSID itself.
2.4. Mapping of Address and Port with Encapsulation (MAP-E) 2.4. Mapping of Address and Port with Encapsulation (MAP-E)
Mapping of Address and Port with Encapsulation (MAP-E) is described Mapping of Address and Port with Encapsulation (MAP-E) is described
in [I-D.ietf-softwire-map]. MAP-E requires the provisioning of the in [I-D.ietf-softwire-map]. MAP-E requires the provisioning of the
following per-subscriber information at the customer edge device: following per-subscriber information at the customer edge device:
o the IPv6 address of one or more border routers, or in MAP-E o the IPv6 address of one or more border routers, or in MAP-E
terminology, MAP border relays. terminology, MAP-E border relays.
o the unique End-user IPv6 prefix for the customer edge device. o the unique End-user IPv6 prefix for the customer edge device.
This may be provided by AAA or acquired by other means. This may be provided by AAA or acquired by other means.
o the Basic Mapping Rule for the customer edge device. This o the Basic Mapping Rule for the customer edge device. This
includes the following parameters: includes the following parameters:
* the rule IPv6 prefix and length; * the rule IPv6 prefix and length;
* the rule IPv4 prefix and length. A prefix length of 0 * the rule IPv4 prefix and length. A prefix length of 0
skipping to change at page 7, line 12 skipping to change at page 7, line 14
default value 6. The parameters 'k' and PSID are needed if default value 6. The parameters 'k' and PSID are needed if
they cannot be derived from the mapping rule information and they cannot be derived from the mapping rule information and
the EA bits (final case of Section 5.2 of the EA bits (final case of Section 5.2 of
[I-D.ietf-softwire-map]). [I-D.ietf-softwire-map]).
o whether the device is to operate in mesh or hub-and-spoke mode; o whether the device is to operate in mesh or hub-and-spoke mode;
o in mesh mode only, zero or more Forwarding Mapping Rules, o in mesh mode only, zero or more Forwarding Mapping Rules,
described by the same set of parameters as the Basic Mapping Rule; described by the same set of parameters as the Basic Mapping Rule;
As indicated in Section 5, bullet 1 of the MAP-E document, a MAP CE As indicated in Section 5, bullet 1 of [I-D.ietf-softwire-map], a MAP
can be provisioned with multiple End-user IPv6 prefixes, each CE can be provisioned with multiple End-user IPv6 prefixes, each
associated with its own Basic Mapping Rule. This does not change the associated with its own Basic Mapping Rule. This does not change the
basic requirement for representation of the corresponding information basic requirement for representation of the corresponding information
in the form of Diameter AVPs, but adds a potential requirement for in the form of Diameter AVPs, but adds a potential requirement for
multiple instances of this information to be present in the Diameter multiple instances of this information to be present in the Diameter
message, differing in the value of the End-user IPv6 prefix (in message, differing in the value of the End-user IPv6 prefix (in
contrast to the Forward Mapping Rule instances). contrast to the Forward Mapping Rule instances).
The border router needs to be configured with the superset of the The border router needs to be configured with the superset of the
Mapping Rules passed to the customer sites it serves. Since this Mapping Rules passed to the customer sites it serves. Since this
requirement does not require direct coordination with CE requirement does not require direct coordination with CE
configuration in the way LW4over6 does, it is out of scope of the configuration in the way lw4o6 does, it is out of scope of the
present document. However, the AVPs defined here may be useful if a present document. However, the AVPs defined here may be useful if a
separate Diameter application is used to configure the border router. separate Diameter application is used to configure the border router.
2.5. Parameters For Multicast 2.5. Parameters For Multicast
[I-D.ietf-softwire-dslite-multicast] specifies a generic solution for [I-D.ietf-softwire-dslite-multicast] specifies a generic solution for
delivery of IPv4 multicast services to IPv4 clients over an IPv6 delivery of IPv4 multicast services to IPv4 clients over an IPv6
multicast network. The solution can be in particular deployed in a multicast network. The solution can be in particular deployed in a
DS-Lite context, but is also adaptable to LW4over6 and MAP-E. For DS-Lite context, but is also adaptable to lw4o6 and MAP-E. For
example, [I-D.ietf-softwire-multicast-prefix-option] specifies how example, [I-D.ietf-softwire-multicast-prefix-option] specifies how
DHCPv6 [RFC3315] can be used to provision multicast-related DHCPv6 [RFC3315] can be used to provision multicast-related
information. The following lists the multicast-related information information. The following lists the multicast-related information
that needs to be provisioned: that needs to be provisioned:
o ASM-mPrefix64: the IPv6 multicast prefix to be used to synthesize o ASM-mPrefix64: the IPv6 multicast prefix to be used to synthesize
the IPv4-embedded IPv6 addresses of the multicast groups in the the IPv4-embedded IPv6 addresses of the multicast groups in the
Any-Source Multicast (ASM) mode. This is achieved by Any-Source Multicast (ASM) mode. This is achieved by
concatenating the ASM-mPrefix64 and a IPv4 multicast address; the concatenating the ASM-mPrefix64 and a IPv4 multicast address; the
Pv4 multicast address is inserted in the last 32 bits of the IPv4 multicast address is inserted in the last 32 bits of the
IPv4-embedded IPv6 multicast address. IPv4-embedded IPv6 multicast address.
o SSM-mPrefix64: the IPv6 multicast prefix to be used to synthesize o SSM-mPrefix64: the IPv6 multicast prefix to be used to synthesize
the IPv4-embedded IPv6 addresses of the multicast groups in the the IPv4-embedded IPv6 addresses of the multicast groups in the
Source-Specific Multicast (SSM, [RFC4607]) mode. This is achieved Source-Specific Multicast (SSM, [RFC4607]) mode. This is achieved
by concatenating the SSM-mPrefix64 and a IPv4 multicast address; by concatenating the SSM-mPrefix64 and a IPv4 multicast address;
the Pv4 multicast address is inserted in the last 32 bits of the the Pv4 multicast address is inserted in the last 32 bits of the
IPv4-embedded IPv6 multicast address. IPv4-embedded IPv6 multicast address.
o uPrefix64: the IPv6 unicast prefix to be used in SSM mode for o uPrefix64: the IPv6 unicast prefix to be used in SSM mode for
constructing the IPv4-embedded IPv6 addresses representing the constructing the IPv4-embedded IPv6 addresses representing the
IPv4 multicast sources in the IPv6 domain. uPrefix64 may also be IPv4 multicast sources in the IPv6 domain. uPrefix64 may also be
used to extract the IPv4 address from the received multicast data used to extract the IPv4 address from the received multicast data
flows. The address mapping follows the guidelines documented in flows. The address mapping follows the guidelines documented in
[RFC6052]. [RFC6052].
2.6. Summary and Discussion 2.6. Summary and Discussion
It appears that two items are common to the different transition There are two items that are common to the different transition
methods and the corresponding AVPs to carry them can be reused: methods, and the corresponding AVPs to carry them can be reused:
o a representation of the IPv6 address of a border router; o a representation of the IPv6 address of a border router;
o A set of prefixes for delivery of multicast services to IPv4 o A set of prefixes for delivery of multicast services to IPv4
clients over an IPv6 multicast network. clients over an IPv6 multicast network.
[RFC6519] sets a precedent for representation of the IPv6 address of [RFC6519] sets a precedent for representation of the IPv6 address of
a border router as an FQDN. This can be dereferenced to one or more a border router as an FQDN. This can be dereferenced to one or more
IP addresses by the provisioning system before being passed to the IP addresses by the provisioning system before being passed to the
customer equipment, or left as an FQDN as it as in [RFC6334]. customer equipment, or left as an FQDN as it as in [RFC6334].
The remaining requirements are transition-method-specific: The remaining requirements are transition-method-specific:
o for LW4over6, a representation of a binding between (1) either the o for lw4o6, a representation of a binding between (1) either the
IPv6 Binding Prefix or a full /128 IPv6 address, (2) a public IPv4 IPv6 Binding Prefix or a full /128 IPv6 address, (2) a public IPv4
address, and (3) (if the IPv4 address is shared) a port set address, and (3) (if the IPv4 address is shared) a port set
identifier; identifier;
o for MAP-E, a representation of the unique End-user IPv6 prefix for o for MAP-E, a representation of the unique End-user IPv6 prefix for
the CE, if not provided by other means; the CE, if not provided by other means;
o for MAP-E, a representation of a Mapping Rule; o for MAP-E, a representation of a Mapping Rule;
o for MAP-E, an indication of whether mesh mode or hub-and-spoke o for MAP-E, an indication of whether mesh mode or hub-and-spoke
mode is to be used. mode is to be used.
3. Attribute-Value Pair Definitions 3. Attribute-Value Pair Definitions
This section provides the specifications for the AVPs needed to meet This section provides the specifications for the AVPs needed to meet
the requirements summarized in Section 2.6. Within the context of the requirements summarized in Section 2.6.
their usage, all of these AVPs MUST have the M bit set and the V bit
cleared.
3.1. IP-Prefix-Length AVP 3.1. IP-Prefix-Length AVP
The IP-Prefix-Length AVP (AVP code TBD00) is of type Unsigned32. It The IP-Prefix-Length AVP (AVP code TBD00) is of type Unsigned32. It
provides the length of an IPv4 or IPv6 prefix. Valid values are from provides the length of an IPv4 or IPv6 prefix. Valid values are from
0 to 32 for IPv4, and from 0 to 128 for IPv6. Tighter limits are 0 to 32 for IPv4, and from 0 to 128 for IPv6. Tighter limits are
given below for particular contexts of use of this AVP. given below for particular contexts of use of this AVP.
NOTE: The IP-Prefix-Length AVP is only relevant when associated NOTE: The IP-Prefix-Length AVP is only relevant when associated
with an IP-Address AVP in a Grouped AVP. with an IP-Address AVP in a Grouped AVP.
skipping to change at page 9, line 27 skipping to change at page 9, line 27
Following on the precedent set by [RFC6334] and [RFC6519], this Following on the precedent set by [RFC6334] and [RFC6519], this
document identifies a border router using an FQDN rather than an document identifies a border router using an FQDN rather than an
address. The Border-Router-Name AVP (AVP Code TBD01) is of type address. The Border-Router-Name AVP (AVP Code TBD01) is of type
OctetString. The FQDN encoding MUST follow the Name Syntax defined OctetString. The FQDN encoding MUST follow the Name Syntax defined
in [RFC1035][RFC1123][RFC2181] and are represented in ASCII form. in [RFC1035][RFC1123][RFC2181] and are represented in ASCII form.
3.3. 64-Multicast-Attributes AVP 3.3. 64-Multicast-Attributes AVP
The 64-Multicast-Attributes AVP (AVP Code TBD02) is of type Grouped. The 64-Multicast-Attributes AVP (AVP Code TBD02) is of type Grouped.
It contains the multicast-related IPv6 prefixes needed for providing It contains the multicast-related IPv6 prefixes needed for providing
IPv4 multicast over IPv6 using DS-Lite, MAP-E, or LW4over6, as IPv4 multicast over IPv6 using DS-Lite, MAP-E, or lw4o6, as mentioned
mentioned in Section 2.5. in Section 2.5.
The syntax is shown in Figure 1. The syntax is shown in Figure 1.
64-Multicast-Attributes ::= < AVP Header: TBD02 > 64-Multicast-Attributes ::= < AVP Header: TBD02 >
[ ASM-mPrefix64 ] [ ASM-mPrefix64 ]
[ SSM-mPrefix64 ] [ SSM-mPrefix64 ]
[ Delegated-IPv6-Prefix ] [ Delegated-IPv6-Prefix ]
*[ AVP ] *[ AVP ]
Figure 1: 64-Multicast-Attributes AVP Figure 1: 64-Multicast-Attributes AVP
64-Multicast-Attributes AVP MUST include at least the ASM-mPrefix64 64-Multicast-Attributes AVP MUST include the ASM-mPrefix64 AVP or the
AVP or the SSM-mPrefix64 AVP. SSM-mPrefix64 AVP, and it MAY include both.
Both the ASM-mPrefix64 AVP and the SSM-mPrefix64 AVP MAY be present.
The Delegated-IPv6-Prefix AVP MUST be present when the SSM-mPrefix64 The Delegated-IPv6-Prefix AVP MUST be present when the SSM-mPrefix64
AVP is present. The Delegated-IPv6-Prefix AVP MAY be present when AVP is present. The Delegated-IPv6-Prefix AVP MAY be present when
the ASM-mPrefix64 AVP is present. the ASM-mPrefix64 AVP is present.
3.3.1. ASM-mPrefix64 AVP 3.3.1. ASM-mPrefix64 AVP
The ASM-mPrefix64 AVP (AVP Code TBD03) conveys the value of The ASM-mPrefix64 AVP (AVP Code TBD03) conveys the value of
ASM_mPrefix64 as mentioned in Section 2.5. The ASM-mPrefix64 AVP is ASM_mPrefix64 as mentioned in Section 2.5. The ASM-mPrefix64 AVP is
of type Grouped, as shown in Figure 2. of type Grouped, as shown in Figure 2.
ASM-mPrefix64 ::= < AVP Header: TBD03 > ASM-mPrefix64 ::= < AVP Header: TBD03 >
{ IP-Address } { IP-Address }
{ IP-Prefix-Length } { IP-Prefix-Length }
*[ AVP ] *[ AVP ]
Figure 2: ASM-mPrefix64 AVP Figure 2: ASM-mPrefix64 AVP
IP-Address (AVP code 518) is defined in [RFC5777] and is of type IP-Address (AVP code 518) is defined in [RFC5777] and is of type
Address. Within the ASM-mPrefix64 AVP, it provides the value of an Address. Within the ASM-mPrefix64 AVP, it provides the value of an
IPv6 prefix. The AddressType field in IP-Address MUST have value 2 IPv6 prefix. The AddressType field in IP-Address MUST have value 2
(IPv6). The conveyed multicast IPv6 prefix MUST belong to the ASM (IPv6). The conveyed multicast IPv6 prefix MUST belong to the ASM
range. Unused bits in IP-Address beyond the actual prefix MUST be range. Unused bits in IP-Address beyond the actual prefix MUST be
set to zeroes by the sender and ignored by the receiver. set to zeroes by the sender and ignored by the receiver.
skipping to change at page 10, line 37 skipping to change at page 10, line 31
mPrefix64 AVP, valid values of the IP-Prefix-Length AVP are from 24 mPrefix64 AVP, valid values of the IP-Prefix-Length AVP are from 24
to 96. to 96.
3.3.2. SSM-mPrefix64 AVP 3.3.2. SSM-mPrefix64 AVP
The SSM-mPrefix64 AVP (AVP Code TBD04) conveys the value of The SSM-mPrefix64 AVP (AVP Code TBD04) conveys the value of
SSM_mPrefix64 as mentioned in Section 2.5. The SSM-mPrefix64 AVP is SSM_mPrefix64 as mentioned in Section 2.5. The SSM-mPrefix64 AVP is
of type Grouped, as shown in Figure 3. of type Grouped, as shown in Figure 3.
SSM-mPrefix64 ::= < AVP Header: TBD04 > SSM-mPrefix64 ::= < AVP Header: TBD04 >
{ IP-Address } { IP-Address }
{ IP-Prefix-Length } { IP-Prefix-Length }
*[ AVP ] *[ AVP ]
Figure 3: SSM-mPrefix64 AVP Figure 3: SSM-mPrefix64 AVP
IP-Address (AVP code 518) provides the value of an IPv6 prefix. The IP-Address (AVP code 518) provides the value of an IPv6 prefix. The
AddressType field in IP-Address MUST have value 2 (IPv6). The AddressType field in IP-Address MUST have value 2 (IPv6). The
conveyed multicast IPv6 prefix MUST belong to the SSM range. Unused conveyed multicast IPv6 prefix MUST belong to the SSM range. Unused
bits in IP-Address beyond the actual prefix MUST be set to zeroes by bits in IP-Address beyond the actual prefix MUST be set to zeroes by
the sender and ignored by the receiver. the sender and ignored by the receiver.
The IP-Prefix-Length AVP (AVP code TBD00) provides the actual length The IP-Prefix-Length AVP (AVP code TBD00) provides the actual length
skipping to change at page 11, line 27 skipping to change at page 11, line 22
3.4. Tunnel-Source-Pref-Or-Addr AVP 3.4. Tunnel-Source-Pref-Or-Addr AVP
The Tunnel-Source-Pref-Or-Addr AVP (AVP Code TBD05) conveys either The Tunnel-Source-Pref-Or-Addr AVP (AVP Code TBD05) conveys either
the IPv6 Binding Prefix or the tunnel source address on the CE, as the IPv6 Binding Prefix or the tunnel source address on the CE, as
described in Section 2.2. The Tunnel-Source-Pref-Or-Addr AVP is of described in Section 2.2. The Tunnel-Source-Pref-Or-Addr AVP is of
type Grouped, with syntax as shown in Figure 4. The Tunnel-Source- type Grouped, with syntax as shown in Figure 4. The Tunnel-Source-
Pref-Or-Addr AVP MUST contain either the Delegated-IPv6-Prefix AVP or Pref-Or-Addr AVP MUST contain either the Delegated-IPv6-Prefix AVP or
the Tunnel-Source-IPv6-Address AVP, not both. the Tunnel-Source-IPv6-Address AVP, not both.
Tunnel-Source-Pref-Or-Addr ::= < AVP Header: TBD05 > Tunnel-Source-Pref-Or-Addr ::= < AVP Header: TBD05 >
[ Delegated-IPv6-Prefix ] [ Delegated-IPv6-Prefix ]
[ Tunnel-Source-IPv6-Address ] [ Tunnel-Source-IPv6-Address ]
*[ AVP ] *[ AVP ]
Figure 4: Tunnel-Source-Pref-Or-Addr AVP Figure 4: Tunnel-Source-Pref-Or-Addr AVP
This AVP is defined separately from the LW4over6-Binding AVP (which This AVP is defined separately from the lw4o6-Binding AVP (which
includes it) to provide flexibility in the transport of the tunnel includes it) to provide flexibility in the transport of the tunnel
source address from the provisioning system to AAA while also source address from the provisioning system to AAA while also
supporting the provision of a complete binding to the LW4over6 border supporting the provision of a complete binding to the lw4o6 border
router. router.
3.4.1. Delegated-IPv6-Prefix As the IPv6 Binding Prefix 3.4.1. Delegated-IPv6-Prefix As the IPv6 Binding Prefix
The Delegated-IPv6-Prefix AVP (AVP code 123) is of type Octetstring, The Delegated-IPv6-Prefix AVP (AVP code 123) is of type Octetstring,
and is defined in [RFC4818]. Within the Tunnel-Source-Pref-Or-Addr and is defined in [RFC4818]. Within the Tunnel-Source-Pref-Or-Addr
AVP, it conveys the IPv6 Binding Prefix assigned to the CE. Valid AVP, it conveys the IPv6 Binding Prefix assigned to the CE. Valid
values in the Prefix-Length field are from 0 to 128 (full address), values in the Prefix-Length field are from 0 to 128 (full address),
although a more restricted range is obviously more reasonable. although a more restricted range is obviously more reasonable.
3.4.2. Tunnel-Source-IPv6-Address AVP 3.4.2. Tunnel-Source-IPv6-Address AVP
The Tunnel-Source-IPv6-Address AVP (AVP code TBD06) is of type The Tunnel-Source-IPv6-Address AVP (AVP code TBD06) is of type
Address. It provides the address that the CE has assigned to its end Address. It provides the address that the CE has assigned to its end
of an LW4over6 tunnel. The AddressType field in this AVP MUST be set of an lw4o6 tunnel. The AddressType field in this AVP MUST be set to
to 2 (IPv6). 2 (IPv6).
3.5. Port-Set-Identifier 3.5. Port-Set-Identifier
The Port-Set-Identifier AVP (AVP Code TBD07) is a structured The Port-Set-Identifier AVP (AVP Code TBD07) is a structured
OctetString with four octets of data, hence a total AVP length of 12. OctetString with four octets of data, hence a total AVP length of 12.
The description of the structure which follows refers to refers to The description of the structure which follows refers to refers to
the parameters described in Section 2.3. the parameters described in Section 2.3 (see Figure 5).
o The first (high-order) octet is the Offset field. It is o The first (high-order) octet is the Offset field. It is
interpreted as an 8-bit unsigned integer giving the offset 'a' interpreted as an 8-bit unsigned integer giving the offset 'a'
from the beginning of a port number to the beginning of the port from the beginning of a port number to the beginning of the port
set identifier (PSID) to which that port belongs. Valid values set identifier (PSID) to which that port belongs. Valid values
are from 0 to 15. are from 0 to 15.
o The next octet, the PSIDLength, is also interpreted as an 8-bit o The next octet, the PSIDLength, is also interpreted as an 8-bit
unsigned integer and gives the length 'k' in bits of the port set unsigned integer and gives the length 'k' in bits of the port set
identifier (PSID). Valid values are from 0 to (16 - a). A value identifier (PSID). Valid values are from 0 to (16 - a). A value
skipping to change at page 12, line 42 skipping to change at page 12, line 35
value of the PSID itself, right-justified within the field. That value of the PSID itself, right-justified within the field. That
is, the value of the PSID occupies the 'k' lowest-order bits of is, the value of the PSID occupies the 'k' lowest-order bits of
the PSIDValue field. the PSIDValue field.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Offset | Length | PSID Value | | Offset | Length | PSID Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.6. LW4over6-Binding AVP Figure 5: Port Set
The LW4over6-Binding AVP (AVP Code TBD08) is of type Grouped. It 3.6. Lw4o6-Binding AVP
The Lw4o6-Binding AVP (AVP Code TBD08) is of type Grouped. It
contains the elements of configuration that constitute the binding contains the elements of configuration that constitute the binding
between an LW4over6 tunnel and IPv4 packets sent through that tunnel, between an lw4o6 tunnel and IPv4 packets sent through that tunnel, as
as described in Section 2.2. described in Section 2.2.
LW4over6-Binding ::= < AVP Header: TBD08 > Lw4o6-Binding ::= < AVP Header: TBD08 >
{ Tunnel-Source-Pref-Or-Addr } { Tunnel-Source-Pref-Or-Addr }
{ LW4over6-External-IPv4-Addr } { Lw4o6-External-IPv4-Addr }
[ Port-Set-Identifier ] [ Port-Set-Identifier ]
*[ AVP ] *[ AVP ]
Figure 5 Figure 6: Lw4o6-Binding AVP
The Tunnel-Source-Pref-Or-Addr AVP is defined in Section 3.4 and The Tunnel-Source-Pref-Or-Addr AVP is defined in Section 3.4 and
provides either the Binding Prefix or the full IPv6 tunnel source provides either the Binding Prefix or the full IPv6 tunnel source
address. address.
The LW4over6-External-IPv4-Addr AVP is defined in Section 3.6.1. The Lw4o6-External-IPv4-Addr AVP is defined in Section 3.6.1.
The Port-Set-Identifier AVP is defined in Section 3.5. It identifies The Port-Set-Identifier AVP is defined in Section 3.5. It identifies
the specific set of ports assigned to the LW4over6 tunnel, when the the specific set of ports assigned to the lw4o6 tunnel, when the IPv4
IPv4 address is being shared. address is being shared.
3.6.1. LW4over6-External-IPv4-Addr AVP 3.6.1. Lw4o6-External-IPv4-Addr AVP
The LW4over6-External-IPv4-Addr AVP (AVP Code TBD09) uses the Address The Lw4o6-External-IPv4-Addr AVP (AVP Code TBD09) uses the Address
derived data format defined in Section 4.3.1 of [RFC6733]. It derived data format defined in Section 4.3.1 of [RFC6733]. It
provides the CE's external IPv4 address within the LW4over6 tunnel provides the CE's external IPv4 address within the lw4o6 tunnel
associated with the given binding. The AddressType field MUST be set associated with the given binding. The AddressType field MUST be set
to 1 (IPv4), and the total length of the AVP MUST be 14 octets. to 1 (IPv4), and the total length of the AVP MUST be 14 octets.
3.7. MAP-E-Attributes 3.7. MAP-E-Attributes
The MAP-E-Attributes AVP (AVP Code TBD10) is of type Grouped. It The MAP-E-Attributes AVP (AVP Code TBD10) is of type Grouped. It
contains the configuration data identified in Section 2.4 for all of contains the configuration data identified in Section 2.4 for all of
the mapping rules (Basic and Forwarding) in a single MAP domain. the mapping rules (Basic and Forwarding) in a single MAP domain.
Multiple instances of this AVP will be present if the CE belongs to Multiple instances of this AVP will be present if the CE belongs to
multiple MAP domains. multiple MAP domains.
MAP-E-Attributes ::= < AVP Header: TBD06 > MAP-E-Attributes ::= < AVP Header: TBD06 >
1*{ Border-Router-Name } 1*{ Border-Router-Name }
1*{ MAP-Mapping-Rule } 1*{ MAP-Mapping-Rule }
[ MAP-Mesh-Mode ] [ MAP-Mesh-Mode ]
[ Delegated-IPv6-Prefix ] [ Delegated-IPv6-Prefix ]
*[ AVP ] *[ AVP ]
Figure 6 Figure 7: MAP-E-Attributes AVP
The Border-Router-Name AVP is defined in Section 3.2. It provides The Border-Router-Name AVP is defined in Section 3.2. It provides
the FQDN of a MAP border relay at the edge of the MAP domain to which the FQDN of a MAP border relay at the edge of the MAP domain to which
the containing MAP-E-Attributes AVP relates. At least one instance the containing MAP-E-Attributes AVP relates. At least one instance
of this AVP MUST be present. of this AVP MUST be present.
The MAP-Mapping-Rule AVP is defined in Section 3.9. At least one The MAP-Mapping-Rule AVP is defined in Section 3.9. At least one
instance of this AVP MUST be present. If the MAP-E domain supports instance of this AVP MUST be present. If the MAP-E domain supports
mesh mode (indicated by the presence of the MAP-Mesh-Mode AVP), mesh mode (indicated by the presence of the MAP-Mesh-Mode AVP),
additional MAP-Mapping-Rule instances MAY be present. If the MAP-E additional MAP-Mapping-Rule instances MAY be present. If the MAP-E
skipping to change at page 15, line 6 skipping to change at page 14, line 45
The MAP-Mapping-Rule AVP (AVP Code TBD12) is of type Grouped, and is The MAP-Mapping-Rule AVP (AVP Code TBD12) is of type Grouped, and is
used only in conjunction with MAP-based transition methods. Mapping used only in conjunction with MAP-based transition methods. Mapping
rules are required both by the MAP border relay and by the CE. The rules are required both by the MAP border relay and by the CE. The
components of the MAP-Mapping-Rule AVP provide the contents of a components of the MAP-Mapping-Rule AVP provide the contents of a
mapping rule as described in Section 2.4. mapping rule as described in Section 2.4.
The syntax of the MAP-Mapping-Rule AVP is as follows: The syntax of the MAP-Mapping-Rule AVP is as follows:
MAP-Mapping-Rule ::= < AVP Header: TBD12 > MAP-Mapping-Rule ::= < AVP Header: TBD12 >
{ Rule-IPv4-Addr-Or-Prefix } { Rule-IPv4-Addr-Or-Prefix }
{ Rule-IPv6-Prefix } { Rule-IPv6-Prefix }
{ EA-Field-Length } { EA-Field-Length }
{ Port-Set-Identifier } { Port-Set-Identifier }
*[ AVP ] *[ AVP ]
Figure 7 Figure 8: MAP-Mapping-Rule AVP
The Rule-IPv4-Addr-Or-Prefix, Rule-IPv6-Prefix, EA-Field-Length, and The Rule-IPv4-Addr-Or-Prefix, Rule-IPv6-Prefix, EA-Field-Length, and
Port-Set-Identifier AVPs MUST all be present. Port-Set-Identifier AVPs MUST all be present.
The Port-Set-Identifier AVP provides information to identify the The Port-Set-Identifier AVP provides information to identify the
specific set of ports assigned to the CE. For more information see specific set of ports assigned to the CE. For more information see
Section 2.4 and Section 2.3. The Port-Set-Identifier AVP is defined Section 2.4 and Section 2.3. The Port-Set-Identifier AVP is defined
in Section 3.5. in Section 3.5.
3.9.1. Rule-IPv4-Addr-Or-Prefix AVP 3.9.1. Rule-IPv4-Addr-Or-Prefix AVP
The Rule-IPv4-Addr-Or-Prefix AVP (AVP Code TBD13) conveys the rule The Rule-IPv4-Addr-Or-Prefix AVP (AVP Code TBD13) conveys the rule
IPv4 prefix and length as described in Section 2.4. The Rule-IPv4- IPv4 prefix and length as described in Section 2.4. The Rule-IPv4-
Addr-Or-Prefix AVP is of type Grouped, as shown in Figure 8. Addr-Or-Prefix AVP is of type Grouped, as shown in Figure 9.
Rule-IPv4-Addr-Or-Prefix ::= < AVP Header: TBD13 > Rule-IPv4-Addr-Or-Prefix ::= < AVP Header: TBD13 >
{ IP-Address } { IP-Address }
{ IP-Prefix-Length } { IP-Prefix-Length }
*[ AVP ] *[ AVP ]
Figure 8: Rule-IPv4-Addr-Or-Prefix AVP Figure 9: Rule-IPv4-Addr-Or-Prefix AVP
IP-Address (AVP code 518) is defined in [RFC5777] and is of type IP-Address (AVP code 518) is defined in [RFC5777] and is of type
Address. Within the Rule-IPv4-Addr-Or-Prefix AVP, it provides the Address. Within the Rule-IPv4-Addr-Or-Prefix AVP, it provides the
value of a unicast IPv4 address or prefix. The AddressType field in value of a unicast IPv4 address or prefix. The AddressType field in
IP-Address MUST have value 1 (IPv4). Unused bits in IP-Address IP-Address MUST have value 1 (IPv4). Unused bits in IP-Address
beyond the actual prefix MUST be set to zeroes by the sender and beyond the actual prefix MUST be set to zeroes by the sender and
ignored by the receiver. ignored by the receiver.
The IP-Prefix-Length AVP (AVP code TBD00) provides the actual length The IP-Prefix-Length AVP (AVP code TBD00) provides the actual length
of the prefix contained in the IP-Address AVP. Within the Rule-IPv4- of the prefix contained in the IP-Address AVP. Within the Rule-IPv4-
Addr-Or-Prefix AVP, valid values of the IP-Prefix-Length AVP are from Addr-Or-Prefix AVP, valid values of the IP-Prefix-Length AVP are from
0 to 32 (full address), based on the different cases identified in 0 to 32 (full address), based on the different cases identified in
Section 5.2 of [I-D.ietf-softwire-map]. Section 5.2 of [I-D.ietf-softwire-map].
3.9.2. Rule-IPv6-Prefix AVP 3.9.2. Rule-IPv6-Prefix AVP
The Rule-IPv6-Prefix AVP (AVP Code TBD14) conveys the rule IPv6 The Rule-IPv6-Prefix AVP (AVP Code TBD14) conveys the rule IPv6
prefix and length as described in Section 2.4. The Rule-IPv6-Prefix prefix and length as described in Section 2.4. The Rule-IPv6-Prefix
AVP is of type Grouped, as shown in Figure 9. AVP is of type Grouped, as shown in Figure 10.
Rule-IPv6-Prefix ::= < AVP Header: TBD14 > Rule-IPv6-Prefix ::= < AVP Header: TBD14 >
{ IP-Address } { IP-Address }
{ IP-Prefix-Length } { IP-Prefix-Length }
*[ AVP ] *[ AVP ]
Figure 9: Rule-IPv6-Prefix AVP Figure 10: Rule-IPv6-Prefix AVP
IP-Address (AVP code 518) is defined in [RFC5777] and is of type IP-Address (AVP code 518) is defined in [RFC5777] and is of type
Address. Within the Rule-IPv6-Prefix AVP, it provides the value of a Address. Within the Rule-IPv6-Prefix AVP, it provides the value of a
unicast IPv6 prefix. The AddressType field in IP- Address MUST have unicast IPv6 prefix. The AddressType field in IP- Address MUST have
value 2 (IPv6). Unused bits in IP-Address beyond the actual prefix value 2 (IPv6). Unused bits in IP-Address beyond the actual prefix
MUST be set to zeroes by the sender and ignored by the receiver. MUST be set to zeroes by the sender and ignored by the receiver.
The IP-Prefix-Length AVP (AVP code TBD00) provides the actual length The IP-Prefix-Length AVP (AVP code TBD00) provides the actual length
of the prefix contained in the IP-Address AVP. Within the Rule- of the prefix contained in the IP-Address AVP. Within the Rule-
IPv6-Prefix AVP, the minimum valid prefix length is 0. The maximum IPv6-Prefix AVP, the minimum valid prefix length is 0. The maximum
skipping to change at page 16, line 33 skipping to change at page 16, line 26
IPv6-Prefix AVP in the enclosing MAP-E-Attributes AVP. Otherwise the IPv6-Prefix AVP in the enclosing MAP-E-Attributes AVP. Otherwise the
maximum value is 128. maximum value is 128.
3.9.3. EA-Field-Length AVP 3.9.3. EA-Field-Length AVP
The EA-Field-Length AVP (AVP Code TBD15) is of type Unsigned32. The EA-Field-Length AVP (AVP Code TBD15) is of type Unsigned32.
Valid values range from 0 to 48. See Section 5.2 of Valid values range from 0 to 48. See Section 5.2 of
[I-D.ietf-softwire-map] for a description of the use of this [I-D.ietf-softwire-map] for a description of the use of this
parameter in deriving IPv4 address and port number configuration. parameter in deriving IPv4 address and port number configuration.
4. Attribute Value Pair flag rules 4. Attribute Value Pair Flag Rules
+---------+ +---------+
|AVP flag | |AVP flag |
|rules | |rules |
+----+----+ +----+----+
AVP Section | |MUST| AVP Section | |MUST|
Attribute Name Code Defined Value Type |MUST| NOT| Attribute Name Code Defined Value Type |MUST| NOT|
+-------------------------------------------------------+----+----+ +-------------------------------------------------------+----+----+
|IP-Prefix-Length TBD00 3.1 Unsigned32 | | V | |IP-Prefix-Length TBD00 3.1 Unsigned32 | | V |
+-------------------------------------------------------+----+----+ +-------------------------------------------------------+----+----+
|Border-Router-Name TBD01 3.2 OctetString | | V | |Border-Router-Name TBD01 3.2 OctetString | | V |
skipping to change at page 17, line 27 skipping to change at page 17, line 27
|ASM-mPrefix64 TBD03 3.3.1 Grouped | | V | |ASM-mPrefix64 TBD03 3.3.1 Grouped | | V |
+-------------------------------------------------------+----+----+ +-------------------------------------------------------+----+----+
|SSM-mPrefix64 TBD04 3.3.2 Grouped | | V | |SSM-mPrefix64 TBD04 3.3.2 Grouped | | V |
+-------------------------------------------------------+----+----+ +-------------------------------------------------------+----+----+
|Tunnel-Source-Pref-Or-Addr TBD05 3.4 Grouped | | V | |Tunnel-Source-Pref-Or-Addr TBD05 3.4 Grouped | | V |
+-------------------------------------------------------+----+----+ +-------------------------------------------------------+----+----+
|Tunnel-Source-IPv6-Address TBD06 3.4.2 Address | | V | |Tunnel-Source-IPv6-Address TBD06 3.4.2 Address | | V |
+-------------------------------------------------------+----+----+ +-------------------------------------------------------+----+----+
|Port-Set-Identifier TBD07 3.5 OctetString | | V | |Port-Set-Identifier TBD07 3.5 OctetString | | V |
+-------------------------------------------------------+----+----+ +-------------------------------------------------------+----+----+
|LW4over6-Binding TBD08 3.6 Grouped | | V | |Lw4o6-Binding TBD08 3.6 Grouped | | V |
+-------------------------------------------------------+----+----+ +-------------------------------------------------------+----+----+
|LW4over6-External-IPv4-Addr TBD09 3.6.1 Address | | V | |Lw4o6-External-IPv4-Addr TBD09 3.6.1 Address | | V |
+-------------------------------------------------------+----+----+ +-------------------------------------------------------+----+----+
|MAP-E-Attributes TBD10 3.7 Grouped | | V | |MAP-E-Attributes TBD10 3.7 Grouped | | V |
+-------------------------------------------------------+----+----+ +-------------------------------------------------------+----+----+
|MAP-Mesh-Mode TBD11 3.8 Enumerated | | V | |MAP-Mesh-Mode TBD11 3.8 Enumerated | | V |
+-------------------------------------------------------+----+----+ +-------------------------------------------------------+----+----+
|MAP-Mapping-Rule TBD12 3.9 Grouped | | V | |MAP-Mapping-Rule TBD12 3.9 Grouped | | V |
+-------------------------------------------------------+----+----+ +-------------------------------------------------------+----+----+
|Rule-IPv4-Addr-Or-Prefix TBD13 3.9.1 Grouped | | V | |Rule-IPv4-Addr-Or-Prefix TBD13 3.9.1 Grouped | | V |
+-------------------------------------------------------+----+----+ +-------------------------------------------------------+----+----+
|Rule-IPv6-Prefix TBD14 3.9.2 Grouped | | V | |Rule-IPv6-Prefix TBD14 3.9.2 Grouped | | V |
+-------------------------------------------------------+----+----+ +-------------------------------------------------------+----+----+
|EA-Field-Length TBD15 3.9.3 Unsigned32 | | V | |EA-Field-Length TBD15 3.9.3 Unsigned32 | | V |
+-------------------------------------------------------+----+----+ +-------------------------------------------------------+----+----+
As described in the Diameter base protocol [RFC6733], the M-bit usage As described in the Diameter base protocol [RFC6733], the M-bit usage
for a given AVP in a given command may be defined by the application. for a given AVP in a given command may be defined by the application.
5. Acknowledgements 5. IANA Considerations
Huawei Technologies funded Tom Taylor's work on earlier versions of
this document.
Special thanks to Lionel Morand for the detailed review.
6. IANA Considerations
This memo requests to IANA to register the following Diameter AVP This memo requests to IANA to register the following Diameter AVP
codes: codes:
+-------+-----------------------------+---------------+ +-------+----------------------------+---------------+
| Code | Attribute Name | Reference | | Code | Attribute Name | Reference |
+-------+-----------------------------+---------------+ +-------+----------------------------+---------------+
| TBD00 | IP-Prefix-Length | This document | | TBD00 | IP-Prefix-Length | This document |
| TBD01 | Border-Router-Name | This document | | TBD01 | Border-Router-Name | This document |
| TBD02 | 64-Multicast-Attributes | This document | | TBD02 | 64-Multicast-Attributes | This document |
| TBD03 | ASM-mPrefix64 | This document | | TBD03 | ASM-mPrefix64 | This document |
| TBD04 | SSM-mPrefix64 | This document | | TBD04 | SSM-mPrefix64 | This document |
| TBD05 | Tunnel-Source-Pref-Or-Addr | This document | | TBD05 | Tunnel-Source-Pref-Or-Addr | This document |
| TBD06 | Tunnel-Source-IPv6-Address | This document | | TBD06 | Tunnel-Source-IPv6-Address | This document |
| TBD07 | Port-Set-Identifier | This document | | TBD07 | Port-Set-Identifier | This document |
| TBD08 | LW4over6-Binding | This document | | TBD08 | Lw4o6-Binding | This document |
| TBD09 | LW4over6-External-IPv4-Addr | This document | | TBD09 | Lw4o6-External-IPv4-Addr | This document |
| TBD10 | MAP-E-Attributes | This document | | TBD10 | MAP-E-Attributes | This document |
| TBD11 | MAP-Mesh-Mode | This document | | TBD11 | MAP-Mesh-Mode | This document |
| TBD12 | MAP-Mapping-Rule | This document | | TBD12 | MAP-Mapping-Rule | This document |
| TBD13 | Rule-IPv4-Addr-Or-Prefix | This document | | TBD13 | Rule-IPv4-Addr-Or-Prefix | This document |
| TBD14 | Rule-IPv6-Prefix | This document | | TBD14 | Rule-IPv6-Prefix | This document |
| TBD15 | EA-Field-Length | This document | | TBD15 | EA-Field-Length | This document |
+-------+-----------------------------+---------------+ +-------+----------------------------+---------------+
Table 1 Table 1
7. Security Considerations 6. Security Considerations
6.1. Man-In-The-Middle (MITM) Attacks
The AVPs defined in this document face two threats, both dependent on The AVPs defined in this document face two threats, both dependent on
man-in-the-middle attacks on the Diameter delivery path. The more man-in-the-middle (MITM) attacks on the Diameter delivery path. The
serious threat is denial of service through modification of the AVP first threat is denial-of-service (DoS) through modification of the
contents leading to misconfiguration. The lesser threat is AVP contents leading to misconfiguration (e.g., a subscriber may fail
disclosure of subscriber addresses allowing the attacker to track to access its connectivity service if an invalid IP address was
subscriber activity. configured, the subscriber's traffic can be intercepted by a
misbehaving node if a fake Border Node has been configured, etc.).
The second one is related to privacy (see Section 6.2).
Diameter security is currently provided on a hop-by-hop basis (see Diameter security is currently provided on a hop-by-hop basis (see
Section 2.2 of [RFC6733]). The Diameter end-to-end security problem Section 2.2 of [RFC6733]). The Diameter end-to-end security problem
has not been solved, so man-in-the-middle attacks on Diameter peers has not been solved, so MITM attacks on Diameter peers along the path
along the path are possible. The present document does not propose are possible. The present document does not propose to solve that
to solve that general problem, but simply warn that it exists. general problem, but simply warn that it exists.
Diameter-related security considerations are discussed in Section 13
of [RFC6733].
6.2. Privacy
The AVPs defined in this document reveal privacy-related information
(e.g., subscriber addresses) that can be used for tracking proposes.
Considerations discussed in Section 13.3 of [RFC6733] MUST be
followed.
7. Acknowledgements
Huawei Technologies funded Tom Taylor's work on earlier versions of
this document.
Special thanks to Lionel Morand for the detailed review.
Many thanks to Russ Housley for the review and comments.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-softwire-lw4over6] [I-D.ietf-softwire-lw4over6]
Cui, Y., Sun, Q., Boucadair, M., Tsou, T., Lee, Y., and I. Cui, Y., Qiong, Q., Boucadair, M., Tsou, T., Lee, Y., and
Farrer, "Lightweight 4over6: An Extension to the DS-Lite I. Farrer, "Lightweight 4over6: An Extension to the DS-
Architecture (work in progress)", March 2014. Lite Architecture", draft-ietf-softwire-lw4over6-13 (work
in progress), November 2014.
[I-D.ietf-softwire-map] [I-D.ietf-softwire-map]
Troan, O., Dec, W., Li, X., Bao, C., Matsushima, S., Troan, O., Dec, W., Li, X., Bao, C., Matsushima, S.,
Murakami, T., and T. Taylor, "Mapping of Address and Port Murakami, T., and T. Taylor, "Mapping of Address and Port
with Encapsulation (MAP) (work in progress)", January with Encapsulation (MAP)", draft-ietf-softwire-map-13
2014. (work in progress), March 2015.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987. specification", STD 13, RFC 1035, November 1987.
[RFC1123] Braden, R., "Requirements for Internet Hosts - Application [RFC1123] Braden, R., "Requirements for Internet Hosts - Application
and Support", STD 3, RFC 1123, October 1989. and Support", STD 3, RFC 1123, October 1989.
[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, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
skipping to change at page 20, line 14 skipping to change at page 20, line 32
8.2. Informative References 8.2. Informative References
[I-D.ietf-softwire-dslite-multicast] [I-D.ietf-softwire-dslite-multicast]
Qin, J., Boucadair, M., Jacquenet, C., Lee, Y., and Q. Qin, J., Boucadair, M., 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", draft-ietf-softwire- over an IPv6 Multicast Network", draft-ietf-softwire-
dslite-multicast-09 (work in progress), March 2015. dslite-multicast-09 (work in progress), March 2015.
[I-D.ietf-softwire-map-dhcp] [I-D.ietf-softwire-map-dhcp]
Mrugalski, T., Troan, O., Farrer, I., Perrault, S., Dec, Mrugalski, T., Troan, O., Farrer, I., Perreault, S., Dec,
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 Clients configuration of Softwire Address and Port Mapped
(Work in progress)", March 2014. Clients", draft-ietf-softwire-map-dhcp-12 (work in
progress), March 2015.
[I-D.ietf-softwire-multicast-prefix-option] [I-D.ietf-softwire-multicast-prefix-option]
Boucadair, M., Qin, J., Tsou, T., and X. Deng, "DHCPv6 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", draft-ietf-softwire-multicast-prefix-option-08 Prefixes", draft-ietf-softwire-multicast-prefix-option-08
(work in progress), March 2015. (work in progress), March 2015.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
 End of changes. 70 change blocks. 
171 lines changed or deleted 190 lines changed or added

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