Subject: RFCyyyy on Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation HDSL and Single-Pair High-Speed Digital Subscriber Line SHDSL Lines

From: [email-masked]
Date: Tue, 20 Dec 2005 17:09:18 -0800

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

This does not apply to this document, but if it were part of a
sub-series, the sub-series number would get listed here also.  For 
example, if this were also bcp NNN, it would be listed as

        BCP NNN
        RFCyyyy

        Title:      Definitions of Managed Objects for 
                    High Bit-Rate DSL - 2nd generation 
                    HDSL and Single-Pair High-Speed Digital Subscriber 
                    Line SHDSL Lines 
        Author:     yyyyyyyyyy
        Status:     Experimental
        Date:       May 2005
        Mailbox:    [email-masked]
        Pages:      
        Characters: 
        Obsoletes:  RFCxxxx
        Updates:    RFCpppp
        See-also:   BCPnnnn

        I-D Tag:    draftyyy-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfcRFCyyyy.txt

This document is a product of the Audio/Video Transport Working Group of the IETF.

EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community.It does not specify an Internet standard of any kind.  Discussion and suggestions for improvement are requested.  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-masked].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email-masked].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email-masked] with the message body 

help: ways_to_get_rfcs. For example:

        To: [email-masked]
        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-masked].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[email-masked].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

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

...

Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="add_draft.pl"

_______________________________________________
IETF-Announce mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ietf-announce