This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/
[dns-wg] FYI
- Previous message (by thread): [dns-wg] Ripe NCC DNSSEC Deployment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jaap Akkerhuis
jaap at NLnetLabs.nl
Tue Aug 30 00:17:42 CEST 2005
A new Request for Comments is now available in online RFC libraries.
BCP 109
RFC 4159
Title: Deprecation of "ip6.int"
Author(s): G. Huston
Status: Best Current Practice
Date: August 2005
Mailbox: gih at apnic.net
Pages: 3
Characters: 5353
SeeAlso: BCP0109
I-D Tag: draft-huston-ip6-int-03.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc4159.txt
This document advises of the deprecation of the use of "ip6.int" for
Standards Conformant IPv6 implementations.
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. 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 at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at 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 at 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 at 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.
--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"
--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
server="RFC-INFO at RFC-EDITOR.ORG"
Content-Type: text/plain
Content-ID: <050829145515.RFC at RFC-EDITOR.ORG>
RETRIEVE: rfc
DOC-ID: rfc4159
--OtherAccess
Content-Type: Message/External-body; name="rfc4159.txt"; site="ftp.isi.edu";
access-type="anon-ftp"; directory="in-notes"
Content-Type: text/plain
Content-ID: <050829145515.RFC at RFC-EDITOR.ORG>
--OtherAccess--
--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
--NextPart--
- Previous message (by thread): [dns-wg] Ripe NCC DNSSEC Deployment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]