idnits 2.17.1 draft-ietf-dhc-pktc-kerb-tckt-03.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3594 5 Title: PacketCable Security Ticket Control Sub-Option 6 for the DHCP CableLabs Client Configuration (CCC) 7 Option 8 Author(s): P. Duffy 9 Status: Standards Track 10 Date: September 2003 11 Mailbox: paduffy@cisco.com 12 Pages: 7 13 Characters: 12521 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-dhc-pktc-kerb-tckt-03.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3594.txt 20 This document defines a new sub-option for the DHCP CableLabs 21 Client Configuration (CCC) Option. This new sub-option will be 22 used to direct CableLabs Client Devices (CCDs) to invalidate 23 security tickets stored in CCD non volatile memory (i.e., locally 24 persisted security tickets). 26 This document is a product of the Dynamic Host Configuration Working 27 Group of the IETF. 29 This is now a Proposed Standard Protocol. 31 This document specifies an Internet standards track protocol for 32 the Internet community, and requests discussion and suggestions 33 for improvements. Please refer to the current edition of the 34 "Internet Official Protocol Standards" (STD 1) for the 35 standardization state and status of this protocol. Distribution 36 of this memo is unlimited. 38 This announcement is sent to the IETF list and the RFC-DIST list. 39 Requests to be added to or deleted from the IETF distribution list 40 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 41 added to or deleted from the RFC-DIST distribution list should 42 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 44 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 45 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 46 help: ways_to_get_rfcs. For example: 48 To: rfc-info@RFC-EDITOR.ORG 49 Subject: getting rfcs 51 help: ways_to_get_rfcs 53 Requests for special distribution should be addressed to either the 54 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 55 specifically noted otherwise on the RFC itself, all RFCs are for 56 unlimited distribution.echo 57 Submissions for Requests for Comments should be sent to 58 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 59 Authors, for further information.