Intended status: Standards Track
draft-eromenko-ipff-arp-01

Document Type Active Internet-Draft (individual)
Last updated 2016-09-29
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
INTERNET-DRAFT
"Internet Protocol Five Fields - Address Resolution Protocol", 
Alexey Eromenko, 2016-09-29, 
<draft-eromenko-ipff-arp-01.txt>
expiration date: 2017-03-29

Intended status: Standards Track

                                                              A.Eromenko
                                                          September 2016

                    Address Resolution Protocol
                  for Internet Protocol version 5
                       on Ethernet Networks
                ===================================
                  (aka ARP-FF for IP "Five Fields")

Abstract

   Address Resolution Protocol in IPv5 is basically the same as in IPv4,
   and it is intended to resolve Data Link Layer Ethernet addresses to 
   Network Layer IP-FF addresses,  in addition to Duplicate Address 
   Detection (DAD), includes optional duplicate MAC address detection.
   This spec was written for IEEE 802.3 Ethernet links or compatible.
   Separate specifications may be required for other link types.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

Copyright Notice

   Copyright (c) 2016 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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. ARPv5 header
   2. ARP Replies
   3. Booting IPFF stack
   4. Mapping of Multicast addresses
   Acknowledgments
   Authors' Contacts

1. ARPv5 header

    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  4|  Hardware Type = 1 (Ethernet) | Protocol Type = 0x9500 (IPFF) |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  8|  H.Len = 6    | P.Len = 14    |          Operation            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 12|                   Sender Hardware Address                     |
   +                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 16|                               |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               +
 20|                   Sender IP-FF Address                        |
   +   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 24|   |                                                           |
   +-+-+                                                           +
 28|                  Sender IP-FF Session ID (62-bit)             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 32|                   Target Hardware Address                     |
   +                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 36|                               |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               +
 40|                   Target IP-FF Address                        |
   +   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 44|   |                                                           |
   +-+-+                                                           +
 48|                           Reserved (62-bit)                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
(bytes)

        16-bit: (ar$hrd) Hardware address space (e.g., Ethernet,
                         Packet Radio Net.)
        16-bit: (ar$pro) Protocol address space.  For IP-FF over Ethernet
                         hardware, this equals to Ethertype of IP-FF.

                         (0x9500 for experimental IP-FF, TBD later)

         8-bit: (ar$hln) Hardware address length, in bytes. = 6 bytes.
                         (for Ethernet MAC)
Show full document text