RFC 4075 on Simple Network Time Protocol (SNTP) ConfigurationOption for DHCPv6

rfc-editor@rfc-editor.org Mon, 23 May 2005 22:32 UTC

Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DaLTc-0007ZI-WD; Mon, 23 May 2005 18:32:49 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DaLTR-0007W2-3N; Mon, 23 May 2005 18:32:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05733; Mon, 23 May 2005 18:32:34 -0400 (EDT)
From: rfc-editor@rfc-editor.org
Received: from cityhall.ci.sugar-land.tx.us ([] helo=mail.ci.sugar-land.tx.us) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DaLlU-0006Pn-El; Mon, 23 May 2005 18:51:16 -0400
Received: from svrpd14 ([]) by mail.ci.sugar-land.tx.us; Mon, 23 May 2005 17:31:43 -0500
MIME-Version: 1.0
Date: Mon, 23 May 2005 17:31:42 -0500
X-Priority: 3 (Normal)
To: ietf-announce@ietf.org, dhcwg@ietf.org, rfc-editor@rfc-editor.org
X-Mailer: GWAVA Archive Mailer
Content-Type: multipart/mixed; boundary="----=_NextPart_ff1_6426_b4fd4bd8.311414b5_.MIX"
Message-ID: <CHILKAT-MID-fb8d5125-d4ec-419a-bdd5-616ff4714f89@svrpd14>
X-Spam-Score: 0.4 (/)
X-Scan-Signature: a3f7094ccc62748c06b21fcf44c073ee
Subject: RFC 4075 on Simple Network Time Protocol (SNTP) ConfigurationOption for DHCPv6
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.

        RFC 4075

        Title:      Simple Network Time Protocol (SNTP)
                    Configuration Option for DHCPv6
        Author(s):  V. Kalusivalingam
        Status:     Standards Track
        Date:       May 2005
        Mailbox:    vibhaska@cisco.com
        Pages:      5
        Characters: 9424
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-dhc-dhcpv6-opt-sntp-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4075.txt

This document describes a new DHCPv6 option for passing a list of
Simple Network Time Protocol (SNTP) server addresses to a client.

This document is a product of the Dynamic Host Configuration Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
IETF-Announce mailing list