About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section

[dns-wg] FYI

  • From: Jaap Akkerhuis <
    >
  • Date: Tue, 30 Aug 2005 00:17:42 +0200

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@localhost
        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@localhost.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@localhost.

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

        To: rfc-info@localhost
        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@localhost.  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@localhost.  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@localhost"

Content-Type: text/plain
Content-ID: <050829145515.RFC@localhost

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@localhost


--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@localhost
https://www1.ietf.org/mailman/listinfo/ietf-announce

--NextPart--




 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | © RIPE Community. All rights reserved.
RIPE.NET Homepage LIR Portal RIPE Community