Address Resolution Protocol (ARP) for the Identifier-Locator Network Protocol for IPv4 (ILNPv4)
RFC 6747
|
Document |
Type |
|
RFC - Experimental
(November 2012; No errata)
|
|
Authors |
|
R. Atkinson
,
Bhatti Sn
|
|
Last updated |
|
2015-10-14
|
|
Stream |
|
IRTF
|
|
Formats |
|
plain text
html
pdf
htmlized
bibtex
|
Stream |
IRTF state
|
|
(None)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Document shepherd |
|
No shepherd assigned
|
IESG |
IESG state |
|
RFC 6747 (Experimental)
|
|
Telechat date |
|
|
|
Responsible AD |
|
Ralph Droms
|
|
IESG note |
|
Tony Li (tony.li@tony.li) is the document shepherd.
|
|
Send notices to |
|
tony.li@tony.li
|
Internet Research Task Force (IRTF) RJ Atkinson
Request for Comments: 6747 Consultant
Category: Experimental SN Bhatti
ISSN: 2070-1721 U. St Andrews
November 2012
Address Resolution Protocol (ARP)
for the Identifier-Locator Network Protocol for IPv4 (ILNPv4)
Abstract
This document defines an Address Resolution Protocol (ARP) extension
to support the Identifier-Locator Network Protocol for IPv4 (ILNPv4).
ILNP is an experimental, evolutionary enhancement to IP. This
document is a product of the IRTF Routing Research Group.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for examination, experimental implementation, and
evaluation.
This document defines an Experimental Protocol for the Internet
community. This document is a product of the Internet Research Task
Force (IRTF). The IRTF publishes the results of Internet-related
research and development activities. These results might not be
suitable for deployment. This RFC represents the individual
opinion(s) of one or more members of the Routing Research Group of
the Internet Research Task Force (IRTF). Documents approved for
publication by the IRSG are not a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6747.
Atkinson & Bhatti Experimental [Page 1]
RFC 6747 ILNPv4 ARP November 2012
Copyright Notice
Copyright (c) 2012 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
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
This document may not be modified, and derivative works of it may not
be created, except to format it for publication as an RFC or to
translate it into languages other than English.
Table of Contents
1. Introduction ....................................................3
1.1. ILNP Document Roadmap ......................................3
1.2. Terminology ................................................5
2. ARP Extensions for ILNPv4 .......................................5
2.1. ILNPv4 ARP Request Packet Format ...........................5
2.2. ILNPv4 ARP Reply Packet Format .............................7
2.3. Operation and Implementation of ARP for ILNPv4 .............8
3. Security Considerations .........................................9
4. IANA Considerations .............................................9
5. References .....................................................10
5.1. Normative References ......................................10
5.2. Informative References ....................................11
6. Acknowledgements ...............................................11
Atkinson & Bhatti Experimental [Page 2]
RFC 6747 ILNPv4 ARP November 2012
1. Introduction
This document is part of the ILNP document set, which has had
extensive review within the IRTF Routing RG. ILNP
is one of the recommendations made by the RG Chairs. Separately,
various refereed research papers on ILNP have also been published
during this decade. So, the ideas contained herein have had much
broader review than the IRTF Routing RG. The views in this
document were considered controversial by the Routing RG, but the
RG reached a consensus that the document still should be
published. The Routing RG has had remarkably little consensus on
anything, so virtually all Routing RG outputs are considered
controversial.
At present, the Internet research and development community are
exploring various approaches to evolving the Internet
Architecture to solve a variety of issues including, but not
limited to, scalability of inter-domain routing [RFC4984]. A wide
range of other issues (e.g., site multihoming, node multihoming,
site/subnet mobility, node mobility) are also active concerns at
present. Several different classes of evolution are being
considered by the Internet research and development community. One
class is often called "Map and Encapsulate", where traffic would
be mapped and then tunnelled through the inter-domain core of the
Show full document text