draft-ietf-dime-mip6-integrated-02.txt   draft-ietf-dime-mip6-integrated-03.txt 
Diameter Maintenance and J. Korhonen (ed.) Diameter Maintenance and J. Korhonen (ed.)
Extensions (DIME) TeliaSonera Extensions (DIME) TeliaSonera
Internet-Draft J. Bournelle Internet-Draft J. Bournelle
Intended status: Standards Track France Telecom R&D Intended status: Standards Track France Telecom R&D
Expires: July 27, 2007 H. Tschofenig Expires: August 16, 2007 H. Tschofenig
Siemens Networks GmbH & Co KG Siemens Networks GmbH & Co KG
C. Perkins C. Perkins
Nokia Research Center Nokia Research Center
K. Chowdhury K. Chowdhury
Starent Networks Starent Networks
January 23, 2007 February 12, 2007
Diameter Mobile IPv6: NAS <-> HAAA Support Diameter Mobile IPv6: NAS <-> HAAA Support
draft-ietf-dime-mip6-integrated-02.txt draft-ietf-dime-mip6-integrated-03.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 27, 2007. This Internet-Draft will expire on August 16, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
A Mobile IPv6 node requires a Home Agent address, a home address, and A Mobile IPv6 node requires a Home Agent address, a home address, and
a security association with its Home Agent before it can start a security association with its Home Agent before it can start
utilizing Mobile IPv6. RFC 3775 requires that some or all of these utilizing Mobile IPv6. RFC 3775 requires that some or all of these
skipping to change at page 3, line 40 skipping to change at page 3, line 40
6.2. Integrated scenario and HA allocation in MSP . . . . . . . 16 6.2. Integrated scenario and HA allocation in MSP . . . . . . . 16
6.3. Integrated scenario and HA allocation in ASP . . . . . . . 18 6.3. Integrated scenario and HA allocation in ASP . . . . . . . 18
7. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 19 7. AVP Occurrence Tables . . . . . . . . . . . . . . . . . . . . 19
7.1. DER and DEA Commands AVP Table . . . . . . . . . . . . . . 19 7.1. DER and DEA Commands AVP Table . . . . . . . . . . . . . . 19
7.2. AAR and AAA Commands AVP Table . . . . . . . . . . . . . . 20 7.2. AAR and AAA Commands AVP Table . . . . . . . . . . . . . . 20
8. MIPv6 Bootstrapping NAS - HAAA Interface AVPs . . . . . . . . 21 8. MIPv6 Bootstrapping NAS - HAAA Interface AVPs . . . . . . . . 21
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
10. Security Considerations . . . . . . . . . . . . . . . . . . . 22 10. Security Considerations . . . . . . . . . . . . . . . . . . . 22
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22
12. Revision history . . . . . . . . . . . . . . . . . . . . . . . 23 12. Revision history . . . . . . . . . . . . . . . . . . . . . . . 23
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24
13.1. Normative References . . . . . . . . . . . . . . . . . . . 23 13.1. Normative References . . . . . . . . . . . . . . . . . . . 24
13.2. Informative References . . . . . . . . . . . . . . . . . . 24 13.2. Informative References . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25
Intellectual Property and Copyright Statements . . . . . . . . . . 27 Intellectual Property and Copyright Statements . . . . . . . . . . 27
1. Introduction 1. Introduction
The Mobile IPv6 (MIPv6) specification [RFC3775] requires a Mobile The Mobile IPv6 (MIPv6) specification [RFC3775] requires a Mobile
Node (MN) to perform registration with a Home Agent (HA) with Node (MN) to perform registration with a Home Agent (HA) with
information about its current point of attachment (Care-of Address). information about its current point of attachment (Care-of Address).
The HA creates and maintains binding between the MN's Home Address The HA creates and maintains binding between the MN's Home Address
skipping to change at page 20, line 27 skipping to change at page 20, line 27
[a] Either MIP6-Home-Agent-Address or MIP6-Home-Agent-FQDN [a] Either MIP6-Home-Agent-Address or MIP6-Home-Agent-FQDN
MAY appear in DER or DEA Commands. MAY appear in DER or DEA Commands.
[b] If the Diameter server accepts the NAS suggestion for [b] If the Diameter server accepts the NAS suggestion for
the HA, then the Diameter server MUST also include the the HA, then the Diameter server MUST also include the
values received in these AVPs in the DEA Command. values received in these AVPs in the DEA Command.
[c] Either MIP6-Home-Link-Prefix or MIP6-Home-Address MAY [c] Either MIP6-Home-Link-Prefix or MIP6-Home-Address MAY
appear in DER or DEA Commands. appear in DER or DEA Commands.
[d] If either MIP6-Home-Agent-Address or MIP6-Home-Agent-FQDN [d] If either MIP6-Home-Address or MIP6-Home-Link-Prefix are
are present in DER Command then this AVP MUST also be present in the DER Command then the corresponding AVP MUST
included in the corresponding DER Command. If the Diameter also be included in the DEA Command. If the Diameter server
server accepts the NAS suggestion for the HA then the accepts the NAS suggestion for the HoA or for the Prefix
Diameter server MUST also include the value received in then the Diameter server MUST also include values received
this AVP in the DEA Command. in these AVPs in the DEA Command.
Figure 9: DER and DEA Commands AVP Table Figure 9: DER and DEA Commands AVP Table
7.2. AAR and AAA Commands AVP Table 7.2. AAR and AAA Commands AVP Table
The following table lists the additional MIPv6 bootstrapping NAS - The following table lists the additional MIPv6 bootstrapping NAS -
HAAA interface AVPs that may optionally be present in the AAR and AAA HAAA interface AVPs that may optionally be present in the AAR and AAA
Commands, as defined in this document and in [RFC4005]. Commands, as defined in this document and in [RFC4005].
+---------------+ +---------------+
skipping to change at page 21, line 27 skipping to change at page 21, line 27
[a] Either MIP6-Home-Agent-Address or MIP6-Home-Agent-FQDN [a] Either MIP6-Home-Agent-Address or MIP6-Home-Agent-FQDN
MAY appear in AAR or AAA Commands. MAY appear in AAR or AAA Commands.
[b] If the Diameter server accepts the NAS suggestion for [b] If the Diameter server accepts the NAS suggestion for
the HA, then the Diameter server MUST also include the the HA, then the Diameter server MUST also include the
values received in these AVPs in the AAA Command. values received in these AVPs in the AAA Command.
[c] Either MIP6-Home-Link-Prefix or MIP6-Home-Address MAY [c] Either MIP6-Home-Link-Prefix or MIP6-Home-Address MAY
appear in AAR or AAA Commands. appear in AAR or AAA Commands.
[d] If either MIP6-Home-Agent-Address or MIP6-Home-Agent-FQDN [d] If either MIP6-Home-Address or MIP6-Home-Link-Prefix are
are present in AAR Command then this AVP MUST also be present in the AAR Command then the corresponding AVP MUST
included in the corresponding AAR Command. If the Diameter also be included in the AAA Command. If the Diameter server
server accepts the NAS suggestion for the HA then the accepts the NAS suggestion for the HoA or for the Prefix
Diameter server MUST also include the value received in then the Diameter server MUST also include values received
this AVP in the AAA Command. in these AVPs in the AAA Command.
Figure 10: AAR and AAA Commands AVP Table Figure 10: AAR and AAA Commands AVP Table
8. MIPv6 Bootstrapping NAS - HAAA Interface AVPs 8. MIPv6 Bootstrapping NAS - HAAA Interface AVPs
This section defines the AVPs that are specific to Diameter MIPv6 This section defines the AVPs that are specific to Diameter MIPv6
bootstrapping NAS - HAAA interface and MAY be included in the bootstrapping NAS - HAAA interface and MAY be included in the
Diameter EAP [RFC4072] and the NASREQ [RFC4005] applications messages Diameter EAP [RFC4072] and the NASREQ [RFC4005] applications messages
listed in Section 4 of this document. The Diameter AVP rules are listed in Section 4 of this document. The Diameter AVP rules are
defined in the Diameter Base [RFC3588], Section 4. These AVP rules defined in the Diameter Base [RFC3588], Section 4. These AVP rules
skipping to change at page 23, line 43 skipping to change at page 23, line 43
o Section 7 NAS - HAAA Interface AVPs flags were corrected. 'M' o Section 7 NAS - HAAA Interface AVPs flags were corrected. 'M'
flag was listed as MUST even if it should have been MUST NOT. flag was listed as MUST even if it should have been MUST NOT.
o General shortening of the text. o General shortening of the text.
o Addition of the MIP6-Home-Address AVP. o Addition of the MIP6-Home-Address AVP.
o Checked against draft-ietf-mip6-radius-01. o Checked against draft-ietf-mip6-radius-01.
o Addition of noted & constrains to AVP tables. o Addition of noted & constrains to AVP tables.
o Miscellaneous corrections like Mobile IPv6 -> MIPv6. o Miscellaneous corrections like Mobile IPv6 -> MIPv6.
o Added signaling examples for HA assignment from MSP, and local HA o Added signaling examples for HA assignment from MSP, and local HA
assignment. assignment.
The following changes were made to the -03 version of the draft:
o Section 7.1 corrected case [d] mixed AVPs.
o Section 7.2 corrected case [d] mixed AVPs.
13. References 13. References
13.1. Normative References 13.1. Normative References
[I-D.ietf-mip6-aaa-ha-goals] [I-D.ietf-mip6-aaa-ha-goals]
Giaretta, G., "AAA Goals for Mobile IPv6", Giaretta, G., "AAA Goals for Mobile IPv6",
draft-ietf-mip6-aaa-ha-goals-03 (work in progress), draft-ietf-mip6-aaa-ha-goals-03 (work in progress),
September 2006. September 2006.
[I-D.ietf-mip6-bootstrapping-integrated-dhc] [I-D.ietf-mip6-bootstrapping-integrated-dhc]
Chowdhury, K. and A. Yegin, "MIP6-bootstrapping via DHCPv6 Chowdhury, K. and A. Yegin, "MIP6-bootstrapping for the
for the Integrated Scenario", Integrated Scenario",
draft-ietf-mip6-bootstrapping-integrated-dhc-01 (work in draft-ietf-mip6-bootstrapping-integrated-dhc-02 (work in
progress), June 2006. progress), February 2007.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", March 1997. Requirement Levels", March 1997.
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support [RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
in IPv6", RFC 3775, June 2004. in IPv6", RFC 3775, June 2004.
 End of changes. 9 change blocks. 
22 lines changed or deleted 27 lines changed or added

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