One document matched: draft-xia-mext-ha-init-flow-binding-00.txt
Network Working Group F. Xia
Internet-Draft B. Sarikaya
Expires: October 24, 2009 Huawei USA
April 22, 2009
Home Agent Initiated Flow Binding for Mobile IPv6
draft-xia-mext-ha-init-flow-binding-00
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 24, 2009.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Xia & Sarikaya Expires October 24, 2009 [Page 1]
Internet-Draft HA Initiated Flow Binding for Mobile IPv6 April 2009
Abstract
This document defines two new Mobility Headers for a home agent to
control flow binding in a mobile node.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Default Flow Binding Provisioning . . . . . . . . . . . . 3
3.2. Flow Binding Revocation . . . . . . . . . . . . . . . . . 4
3.3. Inter-Interface Flow Binding Movement . . . . . . . . . . 4
4. Protocol Operation . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Adding flow bindings . . . . . . . . . . . . . . . . . . . 4
4.2. Deleting flow bindings . . . . . . . . . . . . . . . . . . 5
4.3. Modifying flow bindings . . . . . . . . . . . . . . . . . 5
4.4. Refreshing flow bindings . . . . . . . . . . . . . . . . . 5
4.5. Moving flow bindings . . . . . . . . . . . . . . . . . . . 5
4.6. Switching flow bindings . . . . . . . . . . . . . . . . . 5
4.7. Acknowledging flow bindings . . . . . . . . . . . . . . . 6
5. Flow Binding messages and options . . . . . . . . . . . . . . 6
5.1. Mobility Header . . . . . . . . . . . . . . . . . . . . . 6
5.1.1. Flow Binding Indication . . . . . . . . . . . . . . . 6
5.1.2. Flow Binding Acknowledgement . . . . . . . . . . . . . 8
5.2. New Options . . . . . . . . . . . . . . . . . . . . . . . 9
5.2.1. Flow Attribute option . . . . . . . . . . . . . . . . 9
5.2.2. Alternate Home Agent sub-option . . . . . . . . . . . 11
5.2.3. Target Care-of-Address sub-option . . . . . . . . . . 11
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12
7. IANA considerations . . . . . . . . . . . . . . . . . . . . . 12
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Normative References . . . . . . . . . . . . . . . . . . . 13
9.2. Informative References . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
Xia & Sarikaya Expires October 24, 2009 [Page 2]
Internet-Draft HA Initiated Flow Binding for Mobile IPv6 April 2009
1. Introduction
[I-D.ietf-mext-flow-binding] allows a mobile node to bind a
particular flow to a care-of address without affecting other flows
using the same home address. Binding Update (BU)/Binding
Acknowledgement(BA) messages are extended to enable the mobile node
to add, modify, remove and refresh flow binding in a home agent. The
operations are always initiated by the mobile node.
In some cases, the home agent would like to initiate flow binding
operations. E.g, the home agent revokes a flow binding because of
accounting insufficiency of the mobile node; for the mobile equipped
with multiple interfaces, the home agent moves a flow binding from
one interface to another based on network resource availability; the
home agent provisions default flow binding rules to the mobile node
based on the mobile node's default profile.
This document defines two new Mobility Headers for the home agent to
control flow binding in the mobile node.
2. Terminology
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 [RFC2119].
The terminology in this document is based on the definitions in
[RFC3775] and [I-D.ietf-mext-flow-binding].
3. Use Cases
3.1. Default Flow Binding Provisioning
Michael purchases a dual mode phone equipped with both 3GPP and WiFi
interfaces. He also signs a Service Level Agreement(SLA) with an
operator including the following information:
o 3GPP access takes priority of WiFi when providing VoIP service.
That is, the 3GPP network is always used when Michael makes a call
if the network is accessible.
o WiFi access is primarily selected to serve IPTV service.
o Peer-to-peer (p2p) download is only allowed through WiFi access.
Michael's default profile can be downloaded from AAA server through
the home agent to its mobile node when registering.
Xia & Sarikaya Expires October 24, 2009 [Page 3]
Internet-Draft HA Initiated Flow Binding for Mobile IPv6 April 2009
3.2. Flow Binding Revocation
The operator also provides a package to Michael, for example,
unlimited call and 8 hours free Video-on-Demand (VoD). Michael is a
movie fan, and every month he uses up all the 8 hours. The operator
has no choice but cutting his ongoing VoD while still providing
unlimited call service.
3.3. Inter-Interface Flow Binding Movement
Michael stays home using WLAN access for voice call and downloading.
However, it happens that the operator is carrying on a routine
maintenance of its WiFi devices. The operator then moves all the
call and downloading to its 3GPP interface. Once the maintenance is
finished, the operator then moves the service back to WiFi interface.
4. Protocol Operation
[I-D.ietf-mext-flow-binding] makes use of Binding Update (BU)
/Binding Acknowledgement(BA) signalling to add, modify, remove and
refresh flow binding in a home agent. That is, flow binding
operations are always initiated from the mobile node. The mechanism
specified in this document is complementary to the method described
in [I-D.ietf-mext-flow-binding]. It is assumed that the home agent
has already created Binding Cache entries for the mobile node before
launching flow binding operations.
In this document, two new Mobility Headers are defined, that is, Flow
Binding Indication(FBI) Section 5.1.1 and Flow Binding
Acknowledgement(FBA)Section 5.1.2. FBI is used by the home agent to
initiate flow binding operations, while FBA is used for acknowledging
FBI.
4.1. Adding flow bindings
Adding the flow binding implies associating a flow with a particular
care-of address for the mobile node. The care-of address concerned
with the flow binding is present in the destination address of the
packet or the alternate care-of address option. Alternatively, the
care-of address may be indicated by the BID (Binding Identification
number) described in [I-D.ietf-monami6-multiplecoa] which is pointing
to an existing care-of address, and the BID is included in the
Binding Reference sub-option of the Flow Attribute option defined in
Section 5.2.1.
When adding a new flow binding, the home agent sends a FBI with a
Flow Attribute option to the mobile node. The Flow Attribute option
Xia & Sarikaya Expires October 24, 2009 [Page 4]
Internet-Draft HA Initiated Flow Binding for Mobile IPv6 April 2009
includes a unique FID. The PRO field of the option MUST indicate an
Adding operation. The FID needs only be unique for the receiver of
the adding message, i.e. the same FID can be used across different
receivers of adding messages. A lifetime value is included to
indicate the remaining lifetime of the flow binding.
4.2. Deleting flow bindings
When removing a flow binding, the home agent sends a FBI with a Flow
Attribute option in which PRO field indicates Deleting operation.
The Flow Attribute option includes a unique FID for the mobile node
to locate the flow binding and remove it.
4.3. Modifying flow bindings
When modifying a flow binding (either the care-of address or other
attributes of the flow), the home agent sends the mobile node a FBI
message with Flow Attribute option. The option includes the FID for
the binding being modified. A flow description option may come with
the Flow Attribute option to contain the new attributes needed to
classify the flow. Hence, flow modification is essentially a process
where an existing flow definition is removed and a new flow (included
in the option) is added and given the same FID as the flow that was
removed.
4.4. Refreshing flow bindings
A flow binding is refreshed by simply including the Flow Attribute
option with Refreshing PRO field in the FBI message. The message
should be sent before the expiration of the flow binding. The
message updates existing bindings with new information. Hence, all
information previously sent in the last refreshing message need to be
resent, otherwise such information will be lost.
4.5. Moving flow bindings
The home agent can move a flow associated to one interface of the
multi-interfaced mobile node to another by sending a FBI message to
the mobile node. A Flow Attribute option in which PRO field is set
to Moving is included. The address of the target interface is also
included in the Flow Attribute option.
4.6. Switching flow bindings
Here are some example scenarios where a home agent signals to the
mobile node that it should acquire a new home agent for some specific
flows:
Xia & Sarikaya Expires October 24, 2009 [Page 5]
Internet-Draft HA Initiated Flow Binding for Mobile IPv6 April 2009
o The home agent is overloaded.
o An operator may wish to balance the load among home agents.
o Operators do periodic maintenance in order to maintain reliability
o ... ...
The home agent sends the mobile node a FBI with Flow Attribute option
to indicate that the mobile node should bind a flow to a new home
agent. The alternative home agent addresses are included for the
mobile node to initiate the flow binding to a new home agent.
4.7. Acknowledging flow bindings
The mobile node sends FBA message to acknowledge the reception of
Adding, Deleting, Modifying, Refreshing, Moving, or Switching of a
flow binding. On receiving messages with the Flow Attribute
option(s), the mobile node should copy each Flow Attribute to the
Flow Binding Acknowledgement(FBA) messages.
5. Flow Binding messages and options
5.1. Mobility Header
The messages described below follow the Mobility Header format
specified in Section 6.1 of [RFC3775]:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Payload Proto | Header Len | MH Type | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Checksum | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| |
. .
. Message Data .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5.1.1. Flow Binding Indication
The Flow Binding Indication messages are used by the home agent to
initiate flow binding operations to the mobile node. The Flow
Binding Indication messages use the MH Type value (IANA-TBD1), and
the format of the Message Data field in the Mobility Header is as
follows:
Xia & Sarikaya Expires October 24, 2009 [Page 6]
Internet-Draft HA Initiated Flow Binding for Mobile IPv6 April 2009
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Trigger |A| Reserved | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
. .
. Mobility options .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sequence #
A 16-bit unsigned integer used by the home agent to match a returned
Flow Binding Acknowledgement with this Flow Binding Indication. It
could be a random number.
Trigger
8-bit unsigned integer indicating the event which triggered the
home agent to send the Flow Binding Indication message. The following
Revocation Trigger values are currently defined:
0 Reserved
1 Unspecified
2 Administrative Reason
3 Possible Out-of Sync BCE State
250-255 Reserved For Testing Purposes only
All other values are Reserved
Acknowledge (A)
The Acknowledge (A) bit is set by the home agent to request a Flow Binding
Acknowledgement be returned upon receipt of the Flow Binding Indication.
Reserved
These fields are unused. They MUST be initialized to zero by the
sender and MUST be ignored by the receiver.
Mobility Options
Variable-length field of such length that the complete Mobility
Header is an integer multiple of 8 octets long. Flow Attribute
options defined in this document are included in this field.
Xia & Sarikaya Expires October 24, 2009 [Page 7]
Internet-Draft HA Initiated Flow Binding for Mobile IPv6 April 2009
5.1.2. Flow Binding Acknowledgement
The Flow Binding Acknowledgement is used to acknowledge receipt of a
Flow Binding Indication. The Flow Binding Acknowledgement has the MH
Type value (IANA-TBD2). When this value is indicated in the MH Type
field, the format of the Message Data field in the Mobility Header is
as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence # |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status | Reserved | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
. .
. Mobility options .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sequence #
The sequence number in the Flow Binding Acknowledgement is
copied from the Sequence Number field in the Flow Binding Indication.
Status
8-bit unsigned integer indicating the result of processing the
Flow Binding Indication message by the receiving mobile node.
Values of the Status field less than 128 indicate that
the Flow Binding Indication was processed successfully by
the receiving node. Values greater than or equal to 128 indicate
that the Flow Binding Indication was rejected by the receiving node.
The following status values are currently defined:
0 success
1 partial success
128 Binding Does NOT Exist
All other values are Reserved
Mobility Options
Variable-length field of such length that the complete Mobility
Header is an integer multiple of 8 octets long. This field
contains zero or more TLV-encoded mobility options. Flow Attribute
options defined in this document are included in this field.
Xia & Sarikaya Expires October 24, 2009 [Page 8]
Internet-Draft HA Initiated Flow Binding for Mobile IPv6 April 2009
5.2. New Options
5.2.1. Flow Attribute option
This is a Mobility option.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Option Len | PRO | PRI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FID | Status | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Lifetime | Sub-options |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flow Description ... ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option Type
TBD
Option Len
Length of option in 8-octet units
PRO
This is a 4-bit field that describes the required processing
for the option. It can be assigned one of the following values:
0 Reserved
1 Adding a binding flow
2 Deleting a binding flow
3 Modifying a binding flow
4 Refreshing a binding flow
5 Moving a binding flow
6 Switch a binding flow to alternative home agents
All other values are reserved
PRI
This is a 8-bit priority field to indicate the priority of a
particular option. This field is needed in cases where two
different flow descriptions in two different options overlap.
The priority field decides which policy should apply in those
cases. A lower number in this field indicates a higher
Xia & Sarikaya Expires October 24, 2009 [Page 9]
Internet-Draft HA Initiated Flow Binding for Mobile IPv6 April 2009
priority.
FID
The Flow Identifier field is an 16-bit unsigned integer that
includes the identifier for the flow binding. This field is
used to refer to an existing binding or to create a new
binding.
Status
This field indicates the success or failure of the flow binding
operation for the particular flow in the option. Values from 0
to 127 indicate success; Values of 128 and higher indicate failure.
This field is only relevant when included in the Flow Binding
Acknowledgement message and must be ignored in the Flow Binding
Indication message.
Reserved
This field is unused. It MUST be initialized to zero by the
sender and MUST be ignored by the receiver.
Lifetime
16-bit unsigned integer. One time unit is 4 seconds. Except Deleting
and Switching processing where the lifetime field is ignored, the
lifetime in other PROs has the following meanings:
Adding, the time remaining before the flow binding expired
Modifying, the lifetime of the modified flow binding
Refreshing, the lifetime of the refreshed flow binding
Moving, the lifetime of the moved flow binding
Sub-options
One or more sub-options may be included. These variable length
options are defined in later sections.
Flow Description
Variable length field including attributes defining a flow.
Xia & Sarikaya Expires October 24, 2009 [Page 10]
Internet-Draft HA Initiated Flow Binding for Mobile IPv6 April 2009
5.2.2. Alternate Home Agent sub-option
This section introduces the Alternate Home Agent sub-option, which
may be included in the Flow Attribute option. This sub-option is
used to indicate the mobile node to switch a flow binding from one
home agent to another.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Option Len | # of Addresses| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Home Agent Addresses |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option Type
TBD
Option Len
Length of option in 8-octet units
# of Addresses
The number of home agent addresses in this option.
Reserved
This field is unused. It MUST be initialized to zero by the
sender and MUST be ignored by the receiver.
Home Agent Addresses
Alternative home agent addresses to which the mobile node
is going to switch its flow bindings.
5.2.3. Target Care-of-Address sub-option
This section introduces the Target Care-of-Address, which may be
included in the Flow Attribute option. This sub-option is used to
indicate the mobile node to move a flow binding from one interface to
another.
Xia & Sarikaya Expires October 24, 2009 [Page 11]
Internet-Draft HA Initiated Flow Binding for Mobile IPv6 April 2009
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Option Len | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Target Care-of-Address |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Option Type
TBD
Option Len
Length of option in 8-octet units
Reserved
This field is unused. It MUST be initialized to zero by the
sender and MUST be ignored by the receiver.
Target Care-of-Address
The address of an interface that the flow is moved to.
6. Security Considerations
TBD.
7. IANA considerations
TBD.
8. Acknowledgements
TBD.
9. References
Xia & Sarikaya Expires October 24, 2009 [Page 12]
Internet-Draft HA Initiated Flow Binding for Mobile IPv6 April 2009
9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5213] Gundavelli, S., Leung, K., Devarapalli, V., Chowdhury, K.,
and B. Patil, "Proxy Mobile IPv6", RFC 5213, August 2008.
[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
in IPv6", RFC 3775, June 2004.
[RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
Address Autoconfiguration", RFC 4862, September 2007.
[RFC0792] Postel, J., "Internet Control Message Protocol", STD 5,
RFC 792, September 1981.
[RFC4443] Conta, A., Deering, S., and M. Gupta, "Internet Control
Message Protocol (ICMPv6) for the Internet Protocol
Version 6 (IPv6) Specification", RFC 4443, March 2006.
9.2. Informative References
[I-D.ietf-mext-flow-binding]
Soliman, H., Montavont, N., Fikouras, N., and K.
Kuladinithi, "Flow Bindings in Mobile IPv6 and Nemo Basic
Support", draft-ietf-mext-flow-binding-01 (work in
progress), February 2009.
[I-D.ietf-mext-generic-signaling-message]
Haley, B. and S. Gundavelli, "Mobile IPv6 Generic
Signaling Message",
draft-ietf-mext-generic-signaling-message-00 (work in
progress), August 2008.
[I-D.ietf-mext-binding-revocation]
Muhanna, A., Khalil, M., Gundavelli, S., Chowdhury, K.,
and P. Yegani, "Binding Revocation for IPv6 Mobility",
draft-ietf-mext-binding-revocation-05 (work in progress),
March 2009.
[I-D.ietf-mext-nemo-v4traversal]
Soliman, H., "Mobile IPv6 Support for Dual Stack Hosts and
Routers", draft-ietf-mext-nemo-v4traversal-10 (work in
progress), April 2009.
[I-D.ietf-monami6-multiplecoa]
Wakikawa, R., Devarapalli, V., Tsirtsis, G., Ernst, T.,
Xia & Sarikaya Expires October 24, 2009 [Page 13]
Internet-Draft HA Initiated Flow Binding for Mobile IPv6 April 2009
and K. Nagami, "Multiple Care-of Addresses Registration",
draft-ietf-monami6-multiplecoa-13 (work in progress),
April 2009.
[I-D.larsson-mext-flow-distribution-rules]
Larsson, C., Eriksson, M., Mitsuya, K., Tasaka, K., and R.
Kuntz, "Flow Distribution Rule Language for Multi-Access
Nodes", draft-larsson-mext-flow-distribution-rules-02
(work in progress), February 2009.
Xia & Sarikaya Expires October 24, 2009 [Page 14]
Internet-Draft HA Initiated Flow Binding for Mobile IPv6 April 2009
Authors' Addresses
Frank Xia
Huawei USA
1700 Alma Dr. Suite 500
Plano, TX 75075
Phone: +1 972-509-5599
Email: xiayangsong@huawei.com
Behcet Sarikaya
Huawei USA
1700 Alma Dr. Suite 500
Plano, TX 75075
Phone: +1 972-509-5599
Email: sarikaya@ieee.org
Xia & Sarikaya Expires October 24, 2009 [Page 15]
| PAFTECH AB 2003-2026 | 2026-04-24 05:30:02 |