EDNS0 OWNER Option
draft-cheshire-edns0-owner-option-01

Document Type Active Internet-Draft (individual)
Last updated 2017-07-03
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)
Network Working Group                                        S. Cheshire
Internet-Draft                                               M. Krochmal
Intended status: Standards Track                              Apple Inc.
Expires: January 3, 2018                                    July 2, 2017

                           EDNS0 OWNER Option
                draft-cheshire-edns0-owner-option-01.txt

Abstract

   The DNS-SD Sleep Proxy Service uses a message format identical to
   that used by standard DNS Update, with two additional pieces of
   information: the identity of the sleeping server to which the records
   belong, and the Wake-on-LAN Magic Packet bit pattern which should be
   used to wake the sleeping server.  This document specifies the EDNS0
   option used to carry that additional information.

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

   This Internet-Draft will expire on January 3, 2018.

Copyright Notice

   Copyright (c) 2017 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

Cheshire & Krochmal      Expires January 3, 2018                [Page 1]
Internet-Draft             EDNS0 OWNER Option                  July 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

1.  Introduction

   The EDNS0 'Owner' Option is used by the DNS-SD Sleep Proxy Service.
   The DNS-SD Sleep Proxy Service [RFC6762] [RFC6763] uses a message
   format identical to that used by standard DNS Update [RFC2136]
   [RFC3007], with two additional pieces of information: the identity of
   the sleeping server to which the records belong, and the Wake-on-LAN
   Magic Packet [WoL] bit pattern which should be used to wake the
   sleeping server.  This document specifies the EDNS0 option [RFC2671]
   used to carry that additional information.

   The EDNS0 'Owner' Option is specified here with reference to the
   DNS-SD Sleep Proxy Service, but could also be used for other purposes
   not related to the Sleep Proxy Service.

2.  Conventions and Terminology Used in this Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   "Key words for use in RFCs to Indicate Requirement Levels" [RFC2119].

3.  EDNS0 'Owner' Option

   When a server that supports the DNS-SD Sleep Proxy protocol goes to
   sleep, it communicates relevant DNS records, which describe its role
   on the network, to the Sleep Proxy, in one or more DNS Update
   messages [RFC2136] [RFC3007].  Typically these record registrations
   with the Sleep Proxy do not last forever; they have a finite
   lifetime, communicated using EDNS0 option 2 "DNS Update Lease"
   [DNS-UL].

   When the Sleep Proxy observes traffic on the network which warrants
   waking the sleeping server, it does so by sending a Wake-on-LAN
   "Magic Packet" [WoL].

   A Wake-on-LAN "Magic Packet" consists of the following bit-pattern:

   o  Sync sequence: 48 binary 1s (i.e. 6 bytes of 0xFF)

   o  Sixteen repetitions of the 48-bit MAC address of the sleeping
      server's network interface

   o  Optional 32-bit or 48-bit 'password'

Cheshire & Krochmal      Expires January 3, 2018                [Page 2]
Internet-Draft             EDNS0 OWNER Option                  July 2017

   When the Sleep Proxy determines that the sleeping server has awoken,
   it can cease proxying for that server.

   The Sleep Proxy needs to know the 48-bit MAC address (and possibly
   32-bit or 48-bit 'password') to use to wake the sleeping server.

   It also needs a way to determine when the sleeping server has awoken.
   Because, when a sleeping server wakes it may be attached to the
   network via a different interface (e.g. 802.11 wireless instead of
   Ethernet), merely observing the source MAC address in the packets it
Show full document text