One document matched: draft-korhonen-dime-mip6-feature-bits-01.xml
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type='text/xsl' href='http://xml.resource.org/authoring/rfc2629.xslt' ?>
<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc compact="yes" ?>
<?rfc sortrefs="yes" ?>
<?rfc strict="yes" ?>
<?rfc linkmailto="yes" ?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
<!ENTITY RFC3588 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3588.xml'>
<!ENTITY RFC3775 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3775.xml'>
<!ENTITY RFC4004 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4004.xml'>
<!ENTITY RFC4005 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4005.xml'>
<!ENTITY RFC4072 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4072.xml'>
<!ENTITY RFC4283 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4283.xml'>
<!ENTITY RFC4306 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4306.xml'>
<!ENTITY RFC4372 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4372.xml'>
<!ENTITY RFC4640 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4640.xml'>
<!ENTITY RFC4877 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4877.xml'>
<!ENTITY RFC5026 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5026.xml'>
<!ENTITY RFC5149 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5149.xml'>
<!ENTITY RFC5142 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5142.xml'>
<!ENTITY RFC5226 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml'>
<!ENTITY RFC5447 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5447.xml'>
<!ENTITY I-D.ietf-dime-mip6-split PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-dime-mip6-split.xml'>
<!ENTITY I-D.ietf-monami6-multiplecoa PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-monami6-multiplecoa.xml'>
]>
<rfc category="info" ipr="trust200902" docName="draft-korhonen-dime-mip6-feature-bits-01.txt">
<front>
<title abbrev="Diameter MIP6 Feature Vector Bits">Diameter MIP6 Feature Vector Additional Bit Allocations</title>
<author initials="J" surname="Korhonen" fullname="Jouni Korhonen">
<organization>Nokia Siemens Networks</organization>
<address>
<postal>
<street>Linnoitustie 6</street>
<city>Espoo</city>
<code>FIN-02600</code>
<country>Finland</country>
</postal>
<email>jouni.nospam@gmail.com</email>
</address>
</author>
<date year="2009"/>
<area>Operations and Management Area</area>
<workgroup>Diameter Maintenance and Extensions (DIME)</workgroup>
<keyword>Internet-Draft</keyword>
<abstract>
<t>During the Mobile IPv6 Split Scenario bootstrapping the Mobile IPv6 Home
Agent and the Authentication, Authorization, and Accounting server may
exchange a set of authorized mobility capabilities. This document defines
new mobility capability flags that are used to authorize per Mobile Node
route optimization, Multiple Care-of Address and user plane traffic
encryption support. Furthermore, this document also defines a capability
flag of indicating whether the Home Agent is authorized to act as a
stand alone Virtual Private Network gateway.
</t>
</abstract>
</front>
<middle>
<!-- ====================================================================== -->
<section anchor="introduction" title="Introduction">
<t>During the Mobile IPv6 <xref target="RFC3775"/> Split Scenario
bootstrapping <xref target="RFC5026"/> the Mobile IPv6 Home
Agent (HA) and the Authentication, Authorization, and Accounting (AAA)
server MAY exchange a set of capabilities
as defined in <xref target="I-D.ietf-dime-mip6-split"/>. This
document defines additional capability flag bits that are used
to authorize per Mobile Node (MN) route optimization,
Multiple Care-of Address (MCoA) <xref target="I-D.ietf-monami6-multiplecoa"/>
and user plane traffic encryption support. Furthermore, this document
also defines a capability flag bit of indicating whether the HA is
authorized to act as a stand alone IPsec Virtual Private Network (VPN)
gateway for remote VPN clients. These new capability flag bits allow
Mobility Service Provider (MSP) to control the supported services on
the HA.
</t>
</section>
<!-- ====================================================================== -->
<section anchor="terminology" title="Terminology">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <xref target="RFC2119"/>.
</t>
</section>
<!-- ====================================================================== -->
<!-- ====================================================================== -->
<section title="Flag definitions for the MIP6-Feature-Vector AVP">
<t>The MIP6-Feature-Vector AVP is defined in <xref target="RFC5447"/>.
The new capability bits defined in this document are intended to be
used between the HA and the AAA server during the Mobile IPv6 Split
Scenario bootstrapping
Diameter interactions <xref target="I-D.ietf-dime-mip6-split"/>. However,
the defined flag bits MAY also be used in other scenarios and deployments
outside the Mobile IPv6 Split Scenario.
</t>
<section title="Route Optimization Support">
<t>Route optimization support is indicated by using the
RO_SUPPORTED (value 0x0000000200000000) capability flag bit.
When the HA sets
this bit, it indicates support for the route optimization.
If this bit is unset in the returned
MIP6-Feature-Vector
AVP, the AAA server does not authorize route optimization for
the MN.
</t>
</section>
<section title="Multiple Care-of Addresses Support">
<t>Multiple Care-of Addresses (MCoA) <xref
target="I-D.ietf-monami6-multiplecoa"/> support is indicated
by using the MCOA_SUPPORTED (value 0x0000001000000000)
capability flag bit. When the HA sets
this bit, it indicates support for the MCoA.
If this bit is unset in the returned
MIP6-Feature-Vector
AVP, the AAA server does not authorize the use of MCoA for
the MN.
</t>
</section>
<section title="User Traffic Encryption Support">
<t>User plane traffic encryption support is indicated
by using the USER_TRAFFIC_ENCRYPTION (value 0x0000000400000000)
capability flag bit. When the HA
sets this bit, it indicates support for the user plane traffic
encryption between the MN and the HA. If this bit is
unset in the returned MIP6-Feature-Vector
AVP, the AAA server does not authorize user plane traffic encryption
because of subscription or operator policy.
</t>
</section>
<section title="VPN Gateway Mode Support">
<t>The HA MAY act as a IPsec VPN gateway for the user and
the support is indicated by the VPN_GW_MODE (value 0x0000000800000000)
capability flag bit. When the HA
sets this bit, it indicates support for acting as
a standalone IPsec VPN gateway. If this bit is unset in
the returned MIP6-Feature-Vector AVP, the AAA server does not
authorize the HA to act as a standalone IPsec
VPN gateway for the MN because of subscription or
operator policy.
</t>
</section>
</section>
<!-- ====================================================================== -->
<section title="IANA Considerations">
<t>This document defines new values to the "Mobility
Capability" registry (see <xref target="RFC5447"/>)
for use with the MIP6-Feature-Vector AVP:
<figure><artwork><![CDATA[
Token | Value | Description
---------------------------------+----------------------+------------
RO_SUPPORTED | 0x0000000200000000 | RFC TBD
USER_TRAFFIC_ENCRYPTION | 0x0000000400000000 | RFC TBD
VPN_GW_MODE | 0x0000000800000000 | RFC TBD
MCOA_SUPPORTED | 0x0000001000000000 | RFC TBD
]]></artwork></figure>
</t>
</section>
<!-- ====================================================================== -->
<section anchor="SecurityConsiderations" title="Security Considerations">
<t>This document has no additional security consideration to those
already described for the Mobile IPv6 Integrated Scenario Diameter
interactions <xref target="RFC5447"/> and
Mobile IPv6 Split Scenario Diameter interactions
<xref target="I-D.ietf-dime-mip6-split"/>.
</t>
</section>
</middle>
<!-- ====================================================================== -->
<back>
<references title="Normative References">
&RFC2119;
&RFC5447;
</references>
<references title="Informative References">
&I-D.ietf-dime-mip6-split;
&I-D.ietf-monami6-multiplecoa;
&RFC3775;
&RFC5026;
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 08:55:19 |