One document matched: draft-ietf-fax-feature-schema-05.txt

Differences from draft-ietf-fax-feature-schema-04.txt

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


        RFC 2531: 

        Title:	    Content Feature Schema for Internet Fax
	Author(s):  G. Klyne, L. McIntyre
	Status:     Proposed Standard
	Date:       March 1999
        Mailbox:    GK@ACM.ORG, Lloyd.McIntyre@pahv.xerox.com
	Pages:      51
        Characters: 88295
        Updates/Obsoletes/See Also: None
        I-D Tag:    draft-ietf-fax-feature-schema-05.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2531.txt


This document defines a content feature schema that is a profile of
the media feature registration mechanisms for use in performing
capability identification between extended Internet fax systems.

This document is a product of the Internet Fax Working Group of the
IETF.
 
This is now a Proposed Standard Protocol.
 
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 IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

        To: rfc-info@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@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute