A.11 Network-initiated removal of an access network from a PDN connection
24.3033GPPMobility management based on Dual-Stack Mobile IPv6Release 17Stage 3TS
A.11.1 Binding Revocation Indication Message
The network-initiated DSMIPv6 removal of an access network from a PDN connection procedure is described in subclause 5.9 and the fields of a BRI message used for this procedure are depicted in table A.11.1-1.
The network-initiated DSMIPv6 removal of an access network from a PDN connection procedure is described in subclause 5.9 and the Mobility Options in a BRI message used for this procedure are depicted in table A.11.1-2.
Table A.11.1-1: Fields of a BRI message for the network-initiated DSMIPv6 removal of an access network from a PDN connection procedure
Fields |
Fields Description |
Reference |
B.R. Type |
Set to "1" to indicate BRI. |
IETF RFC 5846 [19] |
Sequence Number |
Set to a monotonically increasing value and is used to match with the returned Binding Revocation Acknowledge |
IETF RFC 5846 [19] |
Revocation Trigger |
Set to "1" |
IETF RFC 5846 [19] |
Proxy Binding (P) |
Set to "0" |
IETF RFC 5846 [19] |
Global (G) |
Set to "0" |
IETF RFC 5846 [19] |
IPv4 HoA Binding Only (V) |
Set to "0" |
IETF RFC 5846 [19] |
Table A.11.1-2: Mobility Options in a BRI message for the network-initiated DSMIPv6 removal of an access network from a PDN connection procedure
Mobility Option |
Cat. |
Mobility Option Description |
Reference |
Binding Identifier mobility option |
O |
The BID and BID-PRI are set to the corresponding entry that the UE wants to remove. |
IETF RFC 5648 [31], IETF RFC 6089 [32] |
A.11.2 Binding Revocation Acknowledgement
The network-initiated DSMIPv6 removal of an access network from a PDN connection procedure is described in subclause 5.9 and the fields of a BRA message used for this procedure are depicted in table A.11.2-1.
The network-initiated DSMIPv6 removal of an access network from a PDN connection procedure is described in subclause 5.9 and the Mobility Options in a BRA message used for this procedure are depicted in table A.11.2-2.
Table A.11.2-1: Fields of a BRA message for the network-initiated DSMIPv6 removal of an access network from a PDN connection procedure
Fields |
Fields Description |
Reference |
B.R. Type |
Set to "2" to indicate BRA. |
IETF RFC 5846 [19] |
Sequence Number |
Set to the value received in the corresponding BRI. |
IETF RFC 5846 [19] |
Status |
Indicates the result of the BRI. |
IETF RFC 5846 [19] |
Proxy Registration Flag (P) |
Set to "0" to indicate that the Binding Revocation Acknowledgment is NOT for a proxy MIPv6 binding entry. |
IETF RFC 5846 [19] |
Global (G) |
Set to "0"; the same value as for the BRI. |
IETF RFC 5846 [19] |
IPv4 HoA Binding Only (V) |
Set to "0" |
IETF RFC 5846 [19] |
Table A.11.2-2: Mobility Options in a BRA message for the network-initiated DSMIPv6 removal of an access network from a PDN connection procedure
Mobility Option |
Cat. |
Mobility Option Description |
Reference |
Binding Identifier mobility option |
C |
This option may be included to indicate the specific BID that failded the revocation procedure. The BID and BID-PRI are set to the value indicated in the BID mobility option of the received Binding Revocation Indication. |
IETF RFC 5648 [31], IETF RFC 6089 [32] |
Annex B (normative):
Extensions specific to the present document
B.1 PDN Identifier notify payload
The format of the PDN Identifier notify payload is shown in figure B-1-1.
The PDN Identifier notify payload type is 40960. The length of the PDN Identifier notify payload is 21 octets. The IPv6 Home Network Prefix contains the IPv6 prefix of a PDN connection. The Prefix Length field indicates the length of the prefix contained in IPv6 Home Network Prefix field.
The other fields are defined by IETF RFC 5996 [14].
Bits |
||||||||
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Octets |
Protocol ID |
1 |
|||||||
SPI Size |
2 |
|||||||
Notify Message Type |
3-4 |
|||||||
IPv6 Home Network Prefix |
5 – 20 |
|||||||
Prefix Length |
21 |
Figure B.1-1: PDN Identifier notify payload format
NOTE: As the notify payload notifies information relating an IKE_SA, SPI Size field is set to 0 and there is no Security Parameter Index field.
B.2 IFOM Capability notify payload
The format of the IFOM Capability notify payload is shown in figure B.2-1.
The IFOM Capability notify payload type is 16428. The length of the IFOM Capability notify payload is 4 octets. The IFOM Capability notify payload is used to indicate the IFOM capability.
The other fields are defined by IETF RFC 5996 [14].
Bits |
||||||||
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
Octets |
Protocol ID |
1 |
|||||||
SPI Size |
2 |
|||||||
Notify Message Type |
3-4 |
Figure B.2-1: IFOM Capability notify payload format
NOTE: As the notify payload notifies information relating to an IKE_SA, SPI Size field is set to 0 and there is no Security Parameter Index field.
Annex C (informative):
Change history
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
---|---|---|---|---|---|---|---|
01-2008 |
Version 0.0.0 Editor’s internal draft |
0.0.0 |
|||||
02-2008 |
CT1 #51 |
Includes the following contributions agreed in CT1 #51: C1-080436, C1-080437 |
0.0.0 |
0.1.0 |
|||
02-2008 |
CT1 #51bis |
Includes the following contributions agreed in CT1 #51bis: C1-080770, C1-080776, C1-080791. |
0.1.0 |
0.2.0 |
|||
02-2008 |
Email-review |
Editorial/style corrections in the clean version |
0.2.0 |
0.2.1 |
|||
04-2008 |
CT1 #52 |
Includes the following contributions agreed in CT1 #52: C1-080954, C1-080959, C1-080960, C1-081213, C1-081232, C1-081398, C1-081399, C1-081400, C1-081401, C1-081402, C1-081419 |
0.2.1 |
0.3.0 |
|||
04-2008 |
Email-review |
Editorial/style corrections in the clean version |
0.3.0 |
0.3.1 |
|||
05-2008 |
CT1 #53 |
Includes the following contributions agreed in CT1 #53: C1-081590, C1-081594, C1-081693, C1-082079, C1-082080, C1-082082, C1-082083, C1-082084, C1-082063 |
0.3.1 |
0.4.0 |
|||
05-2008 |
Email-review |
Editorial clean-up |
0.4.0 |
0.4.1 |
|||
05-2008 |
Version 1.0.0 to be presented to CT-40 created by MCC |
0.4.1 |
1.0.0 |
||||
07-2008 |
CT1 #54 |
Includes the following contributions agreed in CT1 #54: C1-082122, C1-082364, C1-082368, C1-082693, C1-082694, C1-082698, C1-082699, C1-082700 and C1-082808 |
1.0.0 |
1.1.0 |
|||
08-2008 |
CT1 #55 |
Includes the following contributions agreed in CT1 #55: C1-082827, C1-082828, C1-082989, C1-083003, C1-083004, C1-083486, C1-083488, C1-083524 and C1-083601 |
1.1.0 |
1.2.0 |
|||
10-2008 |
CT1 #55bis |
Includes the following contributions agreed in CT1 #55bis: C1-083858, C1-083861, C1-084384, C1-084454, C1-084455, C1-084457, C1-084458, C1-084460, C1-084461, C1-084553, C1-084563, C1-084564, C1-084565 |
1.2.0 |
1.3.0 |
|||
11-2008 |
CT1 #56 |
Includes the following contributions agreed in CT1 #56: C1-084692, C1-084693, C1-085379, C1-085517 |
1.3.0 |
1.4.0 |
|||
11-2008 |
E-mail review |
Editorial clean-up |
1.4.0 |
1.4.1 |
|||
11-2008 |
E-mail review |
Editorial clean-up |
1.4.1 |
1.4.2 |
|||
11-2008 |
E-mail review |
Editorial clean-up |
1.4.2 |
1.4.3 |
|||
11-2008 |
Version 2.0.0 created for presentation to CT#42 for approval |
1.4.3 |
2.0.0 |
||||
12-2008 |
Version 8.0.0 created after approval in CT#42 |
2.0.0 |
8.0.0 |
||||
03-2009 |
CT-43 |
CP-090126 |
0001 |
1 |
Binding Update Optimization |
8.0.0 |
8.1.0 |
03-2009 |
CT-43 |
CP-090126 |
0003 |
BRI error correction |
8.0.0 |
8.1.0 |
|
03-2009 |
CT-43 |
CP-090129 |
0005 |
1 |
Missing HA Initiated Multiple PDN Detach |
8.0.0 |
8.1.0 |
03-2009 |
CT-43 |
CP-090129 |
0007 |
IPv4 HoA release |
8.0.0 |
8.1.0 |
|
03-2009 |
CT-43 |
CP-090125 |
0008 |
1 |
Align with latest version of internet draft |
8.0.0 |
8.1.0 |
03-2009 |
CT-43 |
Editorial cleanup by MCC |
8.0.0 |
8.1.0 |
|||
06-2009 |
CT-44 |
CP-090413 |
0004 |
3 |
Discovery of the Home Agent address |
8.1.0 |
8.2.0 |
06-2009 |
CT-44 |
CP-090413 |
0011 |
1 |
HA discovery via DHCPv6 |
8.1.0 |
8.2.0 |
06-2009 |
CT-44 |
CP-090413 |
0012 |
Nemo Binding Acknowledgement Status value clarification |
8.1.0 |
8.2.0 |
|
06-2009 |
CT-44 |
CP-090413 |
0013 |
Alternate Care-of Address correction |
8.1.0 |
8.2.0 |
|
06-2009 |
CT-44 |
CP-090413 |
0014 |
TLV Header Format flag references |
8.1.0 |
8.2.0 |
|
06-2009 |
CT-44 |
CP-090413 |
0016 |
Update to the Binding Revocation Indication Message |
8.1.0 |
8.2.0 |
|
06-2009 |
CT-44 |
CP-090413 |
0017 |
Clarification of routing header usage |
8.1.0 |
8.2.0 |
|
06-2009 |
CT-44 |
CP-090324 |
0018 |
3 |
HA reallocation procedure and Home Address request |
8.1.0 |
8.2.0 |
09-2009 |
CT-45 |
CP-090655 |
0019 |
DNS lookup at HA discovery based on DHCPv6 |
8.2.0 |
8.3.0 |
|
09-2009 |
CT-45 |
CP-090655 |
0021 |
1 |
Clarification of IPv4 Home Address request |
8.2.0 |
8.3.0 |
09-2009 |
CT-45 |
CP-090655 |
0023 |
1 |
Update of TS after DS-MIPv6 RFC availability |
8.2.0 |
8.3.0 |
09-2009 |
CT-45 |
CP-090655 |
0024 |
1 |
Remove the static HNP configured in LTE capable UE |
8.2.0 |
8.3.0 |
09-2009 |
CT-45 |
CP-090655 |
0025 |
IPv4 address acknowledgement option type |
8.2.0 |
8.3.0 |
|
09-2009 |
CT-45 |
CP-090655 |
0027 |
Deletion of SA to the initial HA during HA reallocation procedure |
8.2.0 |
8.3.0 |
|
12-2009 |
CT-46 |
CP-090901 |
0028 |
RFC5555 missing reference |
8.3.0 |
8.4.0 |
|
12-2009 |
CT-46 |
CP-090901 |
0030 |
A bit in BRI message |
8.3.0 |
8.4.0 |
|
12-2009 |
CT-46 |
CP-090901 |
0031 |
1 |
UE procedures at BRI reception |
8.3.0 |
8.4.0 |
12-2009 |
CT-46 |
CP-090901 |
0029 |
2 |
Clarification of Binding Error message |
8.4.0 |
9.0.0 |
03-2010 |
CT-47 |
CP-100107 |
0035 |
1 |
Multiple PDN connections |
9.0.0 |
9.1.0 |
03-2010 |
CT-47 |
CP-100107 |
0037 |
1 |
PDN connections |
9.0.0 |
9.1.0 |
03-2010 |
CT-47 |
CP-100107 |
0039 |
Reference to redirect RFC |
9.0.0 |
9.1.0 |
|
06-2010 |
CT-48 |
CP-100339 |
0042 |
Reference Updates |
9.1.0 |
9.2.0 |
|
06-2010 |
CT-48 |
CP-100339 |
0044 |
2 |
Usage of PDN prefix information with multiple PDNs to the same APN |
9.1.0 |
9.2.0 |
09-2010 |
CT-49 |
CP-100485 |
0048 |
3 |
Usage of PDN Identifier notify payload |
9.2.0 |
9.3.0 |
09-2010 |
CT-49 |
CP-100513 |
0049 |
4 |
IFOM Reference and Definitions |
9.3.0 |
10.0.0 |
09-2010 |
CT-49 |
CP-100513 |
0050 |
6 |
UE behaviour with multiple PDN connection for IFOM |
9.3.0 |
10.0.0 |
09-2010 |
CT-49 |
CP-100513 |
0053 |
3 |
Attach to additional access – general |
9.3.0 |
10.0.0 |
09-2010 |
CT-49 |
CP-100513 |
0054 |
5 |
Dual Stack Mobile IPv6 inter-access flow mobility |
9.3.0 |
10.0.0 |
09-2010 |
CT-49 |
CP-100513 |
0055 |
2 |
Attach to additional access acting as home link – UE behaviour |
9.3.0 |
10.0.0 |
09-2010 |
CT-49 |
CP-100513 |
0056 |
2 |
Attach to additional access acting as visted link – UE behaviour |
9.3.0 |
10.0.0 |
09-2010 |
CT-49 |
CP-100513 |
0057 |
2 |
Attach to additional access acting as home link – HA behaviour |
9.3.0 |
10.0.0 |
09-2010 |
CT-49 |
CP-100513 |
0058 |
1 |
Attach to additional access acting as visited link – HA behavior |
9.3.0 |
10.0.0 |
09-2010 |
CT-49 |
CP-100513 |
0059 |
2 |
Access removal – general |
9.3.0 |
10.0.0 |
09-2010 |
CT-49 |
CP-100513 |
0060 |
Home link access removal – UE behavior |
9.3.0 |
10.0.0 |
|
09-2010 |
CT-49 |
CP-100513 |
0061 |
2 |
Visited link access removal – UE behavior |
9.3.0 |
10.0.0 |
09-2010 |
CT-49 |
CP-100513 |
0062 |
Removal of an access acting as home link – HA procedures |
9.3.0 |
10.0.0 |
|
09-2010 |
CT-49 |
CP-100513 |
0063 |
2 |
Visited link access removal – HA behavior |
9.3.0 |
10.0.0 |
09-2010 |
CT-49 |
CP-100513 |
0064 |
1 |
IFOM initial attachment |
9.3.0 |
10.0.0 |
09-2010 |
CT-49 |
CP-100513 |
0065 |
1 |
Message format for IP flow mobility |
9.3.0 |
10.0.0 |
09-2010 |
CT-49 |
CP-100520 |
0066 |
2 |
Support of IPv6 Prefix Delegation on S2c |
9.3.0 |
10.0.0 |
09-2010 |
CT-49 |
CP-100518 |
0067 |
1 |
Usage of IP version for Care-of Address selection |
9.3.0 |
10.0.0 |
12-2010 |
CT-50 |
CP-100754 |
0069 |
2 |
IFOM Attach to additional access procedure |
10.0.0 |
10.1.0 |
12-2010 |
CT-50 |
CP-100754 |
0070 |
2 |
IFOM flow mobility procedure |
10.0.0 |
10.1.0 |
12-2010 |
CT-50 |
CP-100754 |
0071 |
1 |
IFOM Remove a link – general |
10.0.0 |
10.1.0 |
12-2010 |
CT-50 |
CP-100754 |
0075 |
3 |
Additional message format for IP flow mobility |
10.0.0 |
10.1.0 |
12-2010 |
CT-50 |
CP-100754 |
0077 |
1 |
Clarification on Dual Stack Mobile IPv6 re-registration |
10.0.0 |
10.1.0 |
12-2010 |
CT-50 |
CP-100754 |
0078 |
3 |
Network-initiated detach in multiple Care-of addresses use case |
10.0.0 |
10.1.0 |
12-2010 |
CT-50 |
CP-100763 |
0079 |
1 |
Delegated Prefix in HA |
10.0.0 |
10.1.0 |
12-2010 |
CT-50 |
CP-100763 |
0080 |
1 |
UE behaviour of DHCPv6 prefix delegation |
10.0.0 |
10.1.0 |
12-2010 |
CT-50 |
CP-100754 |
0082 |
2 |
Clarification on IFOM capability |
10.0.0 |
10.1.0 |
12-2010 |
CT-50 |
CP-100754 |
0083 |
1 |
Corrections and clarifications on IFOM procedures |
10.0.0 |
10.1.0 |
12-2010 |
CT-50 |
CP-100754 |
0084 |
5 |
Access removal from PDN |
10.0.0 |
10.1.0 |
12-2010 |
CT-50 |
CP-100763 |
0087 |
Assigned HNP in BA message |
10.0.0 |
10.1.0 |
|
12-2010 |
CT-50 |
CP-100754 |
0088 |
1 |
IFOM Capability Discovery |
10.0.0 |
10.1.0 |
12-2010 |
CT-50 |
CP-100754 |
0089 |
2 |
Error conditions for IFOM |
10.0.0 |
10.1.0 |
03-2011 |
CT-51 |
CP-110185 |
0093 |
1 |
IFOM capability discovery through ISRP |
10.1.0 |
10.2.0 |
03-2011 |
CT-51 |
CP-110185 |
0094 |
3 |
IFOM condition for binding acknowledge |
10.1.0 |
10.2.0 |
03-2011 |
CT-51 |
CP-110185 |
0095 |
IFOM error condition |
10.1.0 |
10.2.0 |
|
03-2011 |
CT-51 |
CP-110185 |
0096 |
1 |
IFOM correction on attach to additional access procedure |
10.1.0 |
10.2.0 |
03-2011 |
CT-51 |
CP-110185 |
0098 |
1 |
Network-initiated removal of an access |
10.1.0 |
10.2.0 |
03-2011 |
CT-51 |
CP-110185 |
0100 |
3 |
Revision to Network-initiated Removal of Foreign Link from a PDN Connection |
10.1.0 |
10.2.0 |
03-2011 |
CT-51 |
CP-110185 |
0101 |
Modification of UE-initiated Removal of an Access Network from a PDN Connection |
10.1.0 |
10.2.0 |
|
03-2011 |
CT-51 |
CP-110185 |
0102 |
1 |
Correction to pointer to TS 24.302 for IFOM procedure |
10.1.0 |
10.2.0 |
03-2011 |
CT-51 |
CP-110185 |
0103 |
IFOM extensions for handover |
10.1.0 |
10.2.0 |
|
03-2011 |
CT-51 |
CP-110185 |
0104 |
IFOM capability discovery – PCO usage correction |
10.1.0 |
10.2.0 |
|
03-2011 |
CT-51 |
CP-110185 |
0105 |
Correction on ‘O’ flag |
10.1.0 |
10.2.0 |
|
03-2011 |
CT-51 |
CP-110185 |
0106 |
1 |
Protocol type definition for IFOM capability IKE-v2 payload |
10.1.0 |
10.2.0 |
03-2011 |
CT-51 |
CP-110185 |
0107 |
2 |
Routing of packets for IFOM |
10.1.0 |
10.2.0 |
03-2011 |
CT-51 |
CP-110185 |
0108 |
Removal of editor’s note |
10.1.0 |
10.2.0 |
|
03-2011 |
CT-51 |
CP-110197 |
0109 |
2 |
S2c data integrity protection |
10.1.0 |
10.2.0 |
06-2011 |
CT-52 |
CP-110478 |
0110 |
1 |
References to RFC |
10.2.0 |
10.3.0 |
09-2011 |
CT-53 |
CP-110682 |
0111 |
1 |
S2c data integrity protection over trusted non-3GPP access |
10.3.0 |
10.4.0 |
09-2011 |
CT-53 |
CP-110660 |
0115 |
2 |
Correction of Home Agent discovery via DHCPv6 |
10.3.0 |
10.4.0 |
09-2011 |
CT-53 |
CP-110682 |
0117 |
1 |
Correction to S2c data integrity protection – UE procedures |
10.3.0 |
10.4.0 |
09-2011 |
CT-53 |
CP-110690 |
0112 |
1 |
Correction of security related reference |
10.4.0 |
11.0.0 |
09-2011 |
CT-53 |
CP-110690 |
0116 |
1 |
Rejection of IKEv2 SA request |
10.4.0 |
11.0.0 |
09-2011 |
CT-53 |
CP-110690 |
0120 |
1 |
Correction to references |
10.4.0 |
11.0.0 |
12-2011 |
CT-54 |
CP-110874 |
0121 |
2 |
Correction to S2c data integrity protection – HA procedures |
11.0.0 |
11.1.0 |
06-2012 |
CT-56 |
CP-120300 |
0123 |
IETF reference update |
11.1.0 |
11.2.0 |
|
06-2012 |
CT-56 |
CP-120293 |
0125 |
4 |
Correction to HA discovery based on DHCPv6 |
11.1.0 |
11.2.0 |
06-2012 |
CT-56 |
CP-120309 |
0126 |
1 |
Generalize handover procedure to include also Care-of Address change independent of handover |
11.1.0 |
11.2.0 |
06-2012 |
CT-56 |
CP-120309 |
0127 |
1 |
Corrections with references |
11.1.0 |
11.2.0 |
06-2013 |
CT-60 |
CP-130237 |
0129 |
1 |
Specification of IFOM Capability notify payload type |
11.2.0 |
11.3.0 |
09-2014 |
CT-65 |
Upgrade to Rel-12 |
11.3.0 |
12.0.0 |
|||
12-2015 |
CT-70 |
Upgrade to Rel-13 |
12.0.0 |
13.0.0 |
Change history |
|||||||
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
2017-03 |
CT-75 |
Upgrade to Rel-14 |
14.0.0 |
||||
2018-06 |
SA-80 |
– |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
2020-07 |
SA-88e |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
2022-03 |
CT-95e |
Update to Rel-17 version (MCC) |
17.0.0 |