CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 04:06:23 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=vmStcbtf3UjhLLRZnFuuWI.IZz2AkyO9VQjt4wAOorc-1760069183-1.0.1.1-UqDS5jzmEXCQe7X9TA8EXQrGuc_7HjBgtZZEeBUqO6T4mMJztI.3RRu2qaYNdTBkIes9UBcq.pnxeaYOn7nERMFw7NOCAd_yvA51wMcYJfg; path=/; expires=Fri, 10-Oct-25 04:36:23 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c33ea77d5fa9c3-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 6098 » RFC Editor
Search RFCs
RFC 6098
Generic Notification Message for Mobile IPv4, April 2012
- File formats:
- Status:
- PROPOSED STANDARD
- Authors:
- H. Deng
H. Levkowetz
V. Devarapalli
S. Gundavelli
B. Haley - Stream:
- IETF
- Source:
- mip4 (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6098
Discuss this RFC: Send questions or comments to the mailing list mip4@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6098
Abstract
This document specifies protocol enhancements that allow Mobile IPv4 entities to send and receive explicit notification messages using a Mobile IPv4 message type designed for this purpose. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us