Intended status: Standards Track
draft-eromenko-ipff-dhcp-02

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 - Dynamic Host Configuration Protocol",
Alexey Eromenko, 2016-09-29, 
<draft-eromenko-ipff-dhcp-02.txt>
expiration date: 2017-03-29

Intended status: Standards Track

                                                              A.Eromenko
                                                          September 2016

                  Dynamic Host Configuration Protocol
                 -------------------------------------
                      Required modifications for
                    Internet Protocol "Five Fields"
                     PROTOCOL SPECIFICATION draft

Abstract

   This document describes the changes needed from DHCPv4, as defined in
   RFC-2131, to bring DHCP to IP-FF.

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) 2015 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.

Introduction

   DHCP in IPv4 works remarkably well, and so a good idea is to keep it 
   almost unchanged in IP-FF. Instead of publishing a full RFC, I focus
   only on changes required from DHCPv4.

Table of Contents

   1. Format of a DHCP-FF message
   2. Changes from DHCPv4, as defined in RFC-2131
   3. Booting IP-FF via DHCP
   4. Throttling / Delayed replies on High usage

1. Format of a DHCP-FF message

    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|Version|  Hops |     op        |   htype       |   hlen        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  8|               Transaction ID - xid (4)                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 12|         secs              |      ciaddr                       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+                                   +
 16|                        client IP address                      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 20|         flags             |      yiaddr                       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+                                   +
 24|                'your' (client) IP address                     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 28|        Reserved           |      siaddr                       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+                                   +
 32|          IP address of next server to use in bootstrap        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 36|        Reserved           |      giaddr                       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+                                   +
 40|                    Relay agent IP address                     |
   +---------------------------------------------------------------+
   |                                                               |
   |                          chaddr  (16-bytes)                   |
   |                    Client hardware address                    |
   |                                                               |
   +---------------------------------------------------------------+
   |                                                               |
   |                     servername   (up to 128-bytes)            |
   +---------------------------------------------------------------+
   |                                                               |
   |                       bootfile   (up to 255-bytes)            |
   +---------------------------------------------------------------+
Show full document text