Impending publication: draft-iab-dns-choices-05
The IAB is ready to ask the RFC-Editor to publish Design Choices When Expanding DNS draft-iab-dns-choices-05 as an Informational RFC. This document provides a number of considerations to assist application and protocol designers in choosing a mechanism to store and retrieve data in the DNS. It treats, among other things the pros and cons of using TXT records, and of adding prefixes or suffixes to owner names. It argues that adding an new Resource Record is the best solution to add new data to the DNS and that the use of TXT Resource Records is the worst. The IAB solicits comments by February 23, 2008. Please send comments to the IAB ([EMAIL PROTECTED]), or to [EMAIL PROTECTED] The document can be found at http://www.ietf.org/internet-drafts/draft-iab-dns-choices-03.txt From the Abstract: This note discusses how to extend the DNS with new data for a new application. DNS extension discussions too often focus on reuse of the TXT Resource Record Type. This document lists different mechanisms to extend the DNS, and concludes that the use of a new DNS Resource Record Type is the best solution. Olaf Kolkman, For the IAB. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: draft-ietf-hokey-emsk-hierarchy (Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK)) to Proposed Standard
The IESG has received a request from the Handover Keying WG (hokey) to consider the following document: - 'Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK) ' draft-ietf-hokey-emsk-hierarchy-04.txt as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the [EMAIL PROTECTED] mailing lists by 2008-03-21. Exceptionally, comments may be sent to [EMAIL PROTECTED] instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hokey-emsk-hierarchy-04.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=15627rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 5098 on Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs)
A new Request for Comments is now available in online RFC libraries. RFC 5098 Title: Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs) Author: G. Beacham, S. Kumar, S. Channabasappa Status: Standards Track Date: February 2008 Mailbox:[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Pages: 79 Characters: 159415 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-ipcdn-pktc-signaling-15.txt URL:http://www.rfc-editor.org/rfc/rfc5098.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices. [STANDARDS TRACK] This document is a product of the IP over Cable Data Network Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: 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 [EMAIL PROTECTED] Requests to be added to or deleted from the RFC-DIST distribution list should be sent to [EMAIL PROTECTED] Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to [EMAIL PROTECTED] with the message body help: ways_to_get_rfcs. For example: To: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to [EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
