Using NTP Extension Fields without Authentication
draft-ietf-ntp-extension-field-01

The information below is for an old version of the document
Document Type Active Internet-Draft (ntp WG)
Last updated 2014-06-25
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd Karen O'Donoghue
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
NTP Working Group                                             T. Mizrahi
Internet Draft                                                   Marvell
Intended status: Standards Track                                D. Mayer
Updates: 5905                                    Network Time Foundation
Expires: December 2014                                     June 26, 2014

             Using NTP Extension Fields without Authentication
                   draft-ietf-ntp-extension-field-01.txt

Abstract

   The Network Time Protocol Version 4 (NTPv4) defines the optional
   usage of extension fields. An extension field is an optional field
   that resides at the end of the NTP header, and can be used to add
   optional capabilities or additional information that is not conveyed
   in the standard NTP header. The current definition of extension
   fields in NTPv4 is somewhat ambiguous regarding the connection
   between extension fields and the presence of a Message Authentication
   Code (MAC). This draft clarifies the usage of extension fields in the
   presence and in the absence of a MAC, while maintaining
   interoperability with existing implementations.

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on December 26, 2014.

Mizrahi, Mayer        Expires December 26, 2014               [Page 1]
Internet-Draft           NTP Extension Field                 June 2014

Copyright Notice

   Copyright (c) 2014 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. Introduction ................................................. 3
   2. Conventions Used in this Document ............................ 4
      2.1. Terminology ............................................. 4
      2.2. Terms & Abbreviations ................................... 4
   3. NTP Extension Fields with and without a MAC - Clarifications . 4
      3.1. Extension Field Format .................................. 4
      3.2. Extension Fields in the Absence of a MAC ................ 4
      3.3. Unknown Extension Fields ................................ 5
      3.4. Interoperability with Current Implementations ........... 5
   4. NTP Extension Field Usage with and without a MAC - Extensions  5
      4.1. Extension Fields in the Presence of a MAC ............... 5
      4.2. Extension Fields in the Absence of a MAC ................ 5
      4.3. Multiple Extension fields in an NTP packet .............. 6
      4.4. MAC in the absence of an Extension field ................ 6
   5. Security Considerations ...................................... 6
   6. IANA Considerations .......................................... 6
   7. Acknowledgments .............................................. 6
   8. References ................................................... 6
      8.1. Normative References .................................... 6
      8.2. Informative References .................................. 7
   Appendix A. Requirements from NTPv4 and Autokey ................. 7
      A.1. NTP Extension Field for Future Extensions ............... 7
      A.2. NTP Extension Field in the Presence of a MAC ............ 7
      A.3. The NTP Extension Field Format .......................... 7
      A.4. NTP Extension Field in Autokey .......................... 8

Mizrahi, Mayer        Expires December 26, 2014               [Page 2]
Internet-Draft           NTP Extension Field                 June 2014

1. Introduction

   The NTP header format consists of a set of fixed fields that may be
Show full document text