Tom,
This is quite a comprehensive list.
Please consider the changes suggested below.
Lloyd
1. Add draft-ietf-fax-tiff-fx-09.txt, which obsoletes RFC 2301 on route to
issuing TIFF-FX as Draft Standard
http://www.ietf.org/internet-drafts/draft-ietf-fax-tiff-fx-09.txt
2. Add draft-ietf-fax-tiff-fx-extension1-00.txt, which introduces the first
set of extensions to TIFF-FX for higher spatial resolutions, JBIG2 encoding
and others
http://www.ietf.org/internet-drafts/draft-ietf-fax-tiff-fx-extension1-00.txt
3. Add draft-ietf-fax-tiff-regbis-02.txt, which obsoletes RFC 2302 on route
to issuing Registration as Best Common Practice
http://www.ietf.org/internet-drafts/draft-ietf-fax-tiff-regbis-02.txt
4. Add draft-ietf-fax-minaddr-v2-02.txt, which obsoletes RFC 2303 on route
to issuing TIFF-FX as Draft Standard
http://www.ietf.org/internet-drafts/draft-ietf-fax-minaddr-v2-02.txt
5. draft-ietf-fax-faxaddr-v2-02.txt, which obsoletes RFC 2304 on route to
issuing TIFF-FX as Draft Standard
http://www.ietf.org/internet-drafts/draft-ietf-fax-faxaddr-v2-02.txt
6. Delete RFC 2306, this is Information and only a subset of RFC 2301 with
no further value.
7. Delete RFC 2880 - Internet Fax T.30 Feature Mapping, this provides
information with regard to translating T.30 fax DIS/DCS frame bits to schema
representation
> -----Original Message-----
> From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com]
> Sent: Saturday, December 02, 2000 12:57 AM
> To: IPP FAX DL (E-mail)
> Subject: IFX> All Internet FAX RFCs down loaded into a .zip and
> abstracts of ea ch put into a single file
>
>
> As we decide what to make REQUIRED, RECOMMENDED, and OPTIONAL
> for IPP FAX,
> we should do so in terms of features in Internet FAX. So we
> need to study
> their documents more. To that end, I've down loaded a .zip
> file that has
> all of the current Internet FAX RFCs (up through RFC 2938) into:
>
> ftp://ftp.pwg.org/pub/pwg/QUALDOCS/rfcs/internet-fax-rfcs-001201.zip
>
> I've also created a file that has all of their titles, dates,
> Abstracts and
> any updating or obsolescing and down loaded it in the same directory:
>
> ftp://ftp.pwg.org/pub/pwg/QUALDOCS/rfcs/internet-fax-rfc-abstr
> acts-001201.do
> c
> ftp://ftp.pwg.org/pub/pwg/QUALDOCS/rfcs/internet-fax-rfc-abstr
> acts-001201.pd
> f
>
> Here is a cut and paste of the abstracts:
>
> Internet FAX RFC Abstracts
> Date: 12/01/00
> File:
> ftp://ftp.pwg.org/pub/pwg/QUALDOCS/rfcs/internet-fax-rfc-abstr
> acts-001201.do
> c
>
> RFC 2301 - File Format for Internet Fax, March 1998
> This document describes the TIFF (Tag Image File Format)
> representation of image data specified by the ITU-T Recommendations
> for black-and-white and color facsimile. This file format
> specification is commonly known as TIFF-FX. It formally defines
> minimal, extended and lossless JBIG modes (Profiles S, F, J) for
> black-and-white fax, and base JPEG, lossless JBIG and Mixed Raster
> Content modes (Profiles C, L, M) for color and grayscale fax. These
> modes or profiles correspond to the content of the applicable ITU-T
> Recommendations. Files formatted according to this
> specification use
> the image/tiff MIME Content Type.
> RFC 2302 - Tag Image File Format (TIFF) - image/tiff MIME Sub-type
> Registration, March 1998
> This document describes the registration of the MIME sub-type
> image/tiff. The baseline encoding is defined by [TIFF]. This
> document refines an earlier sub-type registration in RFC 1528
> [TPC.INT].
> RFC 2303 - Minimal PSTN address format in Internet Mail, March 1998
> This memo describes the MINIMAL addressing method to encode PSTN
> addresses into e-mail addresses and the standard extension
> mechanism
> to allow definition of further standard elements. The opposite
> problem, i.e. to allow a traditional numeric-only PSTN
> device user to
> access the e-mail transport service, is not discussed here.
> RFC 2304 - Minimal FAX address format in Internet Mail, March 1998
> This memo describes the MINIMAL addressing method and standard
> extensions to encode FAX addresses in e-mail addresses, as required
> in reference [13]. The opposite problem, i.e. to allow a
> traditional
> numeric-only fax device user to access the e-mail
> transport service,
> is not discussed here.
> RFC 2305 - A Simple Mode of Facsimile Using Internet Mail, March 1998
> This specification provides for "simple mode" carriage of facsimile
> data over the Internet. Extensions to this document will follow.
> The current specification employs standard protocols and
> file formats
> such as TCP/IP, Internet mail protocols [1, 2, 3], MIME
> [4, 16, 17],
> and TIFF for Facsimile [5,6,19]. It can send images not only to
> other Internet-aware facsimile devices but also to Internet-native
> systems, such as PCs with common email readers which can
> handle MIME
> mail and TIFF for Facsimile data. The specification facilitates
> communication among existing facsimile devices, Internet
> mail agents,
> and the gateways which connect them.
> RFC 2306 - Tag Image File Format (TIFF) - F Profile for
> Facsimile, March
> 1998
> This document describes in detail the definition of TIFF-F that is
> used to store facsimile images. The TIFF-F encoding has been
> folklore with no standard reference definition before this
> document.
> RFC 2426 - vCard MIME Directory Profile - September 1998
> This memo defines the profile of the MIME Content-Type
> [MIME-DIR] for
> directory information for a white-pages person object, based on a
> vCard electronic business card. The profile definition is
> independent
> of any particular directory service or protocol. The profile is
> defined for representing and exchanging a variety of information
> about an individual (e.g., formatted and structured name
> and delivery
> addresses, email address, multiple telephone numbers, photograph,
> logo, audio clips, etc.). The directory information used by this
> profile is based on the attributes for the person object defined in
> the X.520 and X.521 directory services recommendations. The profile
> also provides the method for including a [VCARD]
> representation of a
> white-pages directory entry within the MIME Content-Type defined by
> the [MIME-DIR] document.
> RFC 2506 - Media Feature Tag Registration Procedure, March 1999
> Recent Internet applications, such as the World Wide Web, tie
> together a great diversity in data formats, client and server
> platforms, and communities. This has created a need for media
> feature descriptions and negotiation mechanisms in order
> to identify
> and reconcile the form of information to the capabilities and
> preferences of the parties involved.
>
> Extensible media feature identification and negotiation mechanisms
> require a common vocabulary in order to positively identify media
> features. A registration process and authority for media
> features is
> defined with the intent of sharing this vocabulary between
> communicating parties. In addition, a URI tree is defined to enable
> sharing of media feature definitions without registration.
>
> This document defines a registration procedure which uses the
> Internet Assigned Numbers Authority (IANA) as a central
> registry for
> the media feature vocabulary.
>
> Please send comments to the CONNEG working group at <ietf-
> medfree@imc.org>. Discussions of the working group are archived at
> <URL: http://www.imc.org/ietf-medfree/>.
> RFC 2530 - Indicating Supported Media Features Using
> Extensions to DSN and
> MDN, March 1999
> There is a need in Internet mail and Internet fax for a
> recipient to
> indicate the media features it supports so that messages can be
> generated by senders without exceeding the recipient's abilities.
>
> This memo describes a format for generating Message Disposition
> Notifications [RFC2298] and Delivery Status Notifications [RFC1894]
> which contain such information. This information can be used by
> senders to avoid exceeding the recipient's capabilities
> when sending
> subsequent messages.
> RFC 2531 - Content Feature Schema for Internet Fax, March 1999
> Obsoleted by RFC 2879
> This document defines a content feature schema that is a profile of
> the media feature registration mechanisms [1,2,3] for use in
> performing capability identification between extended Internet fax
> systems [5].
>
> This document does not describe any specific mechanisms for
> communicating capability information, but does presume
> that any such
> mechanisms will transfer textual values. It specifies a textual
> format to be used for describing Internet fax capability
> information.
> RFC 2532 - Extended Facsimile Using Internet Mail, March 1999
> This document describes extensions to "Simple Mode of
> Facsimile Using
> Internet Mail" [RFC2305] and describes additional
> features, including
> transmission of enhanced document characteristics (higher
> resolution,
> color) and confirmation of delivery and processing.
>
> These additional features are designed to provide the highest level
> of interoperability with the existing and future
> standards-compliant
> email infrastructure and mail user agents, while providing
> a level of
> service that approximates the level currently enjoyed by fax users.
>
> The IETF has been notified of intellectual property rights
> claimed in
> regard to some or all of the specification contained in this
> document. For more information consult the online list of claimed
> rights in <http://www.ietf.org/ipr.html>.
> RFC 2533 - A Syntax for Describing Media Feature Sets, March 1999
> Updated by RFC 2738 and by RFC 2938
> A number of Internet application protocols have a need to provide
> content negotiation for the resources with which they interact [1].
> A framework for such negotiation is described in [2], part of which
> is a way to describe the range of media features which can
> be handled
> by the sender, recipient or document transmission format of a
> message. A format for a vocabulary of individual media
> features and
> procedures for feature registration are presented in [3].
>
> This document introduces and describes a syntax that can be used to
> define feature sets which are formed from combinations and
> relations
> involving individual media features. Such feature sets are used to
> describe the media feature handling capabilities of
> message senders,
> recipients and file formats.
>
> An algorithm for feature set matching is also described here.
> RFC 2534 - Media Features for Display, Print, and Fax, March 1999
> This specification defines some common media features for
> describing
> image resolution, size, color, and image representation
> methods that
> are common to web browsing, printing, and facsimile applications.
> These features are registered for use within the framework
> of [REG].
> RFC 2542 - Terminology and Goals for Internet Fax, March 1999
> This document defines a number of terms useful for the
> discussion of
> Internet Fax. In addition, it describes the goals of the
> Internet Fax
> working group and establishes a baseline of desired functionality
> against which protocols for Internet Fax can be judged. It
> encompasses the goals for all modes of facsimile delivery,
> including
> 'real-time', 'session', and 'store and forward'.
> Different levels of
> desirability are indicated throughout the document.
> RFC 2703 - Protocol-independent Content Negotiation
> Framework, September
> 1999
> A number of Internet application protocols have a need to provide
> content negotiation for the resources with which they
> interact. MIME
> media types [1,2] provide a standard method for handling one major
> axis of variation, but resources also vary in ways which cannot be
> expressed using currently available MIME headers.
>
> This memo sets out terminology, an abstract framework and goals for
> protocol-independent content negotiation, and identifies some
> technical issues which may need to be addressed.
>
> The abstract framework does not attempt to specify the content
> negotiation process, but gives an indication of the
> anticipated scope
> and form of any such specification. The goals set out the desired
> properties of a content negotiation mechanism.
> RFC 2738 - Corrections to "A Syntax for Describing Media
> Feature Sets", Dec
> 1999
> Updates 2533
> In RFC 2533, "A Syntax for Describing Media Feature Sets", an
> expression format is presented for describing media feature
> capabilities using simple media feature tags.
>
> This memo contains two corrections to that specification:
> one fixes
> an error in the formal syntax specification, and the other fixes an
> error in the rules for reducing feature comparison predicates.
> RFC 2879 - Content Feature Schema for Internet Fax (V2), August 2000
> Obsoletes RFC 2531
> This document defines a content media feature schema for Internet
> fax.
>
> It is a profile of the media feature registration
> mechanisms [1,2,3]
> for use in performing capability identification between extended
> Internet fax systems [5]. It replaces and updates the
> feature schema
> defined in RFC 2531.
> RFC 2880 - Internet Fax T.30 Feature Mapping, August 2000
> This document describes how to map Group 3 fax capability
> identification bits, described in ITU T.30 [6], into the
> Internet fax
> feature schema described in "Content feature schema for
> Internet fax"
> [4].
>
> This is a companion to the fax feature schema document [4], which
> itself defines a profile of the media feature registration
> mechanisms
> [1,2,3], for use in performing capability identification between
> extended Internet fax systems [5].
> RFC 2912 - Indicating Media Features for MIME Content, September 2000
> In "A Syntax for Describing Media Feature Sets", an
> expression format
> is presented for describing media feature capabilities using simple
> media feature tags.
>
> This memo defines a Multipurpose Internet Mail Extensions (MIME)
> 'Content-features:' header that can be used to annotate a MIME
> message part using this expression format, and indicates
> some ways it
> might be used.
> RFC 2913 - MIME Content Types in Media Feature Expressions,
> September 2000
> In "A Syntax for Describing Media Feature Sets", an
> expression format
> is presented for describing media feature capabilities using simple
> media feature tags.
>
> This memo defines a media feature tag whose value is a Multipurpose
> Internet Mail Extensions (MIME) content type. This allows the
> construction of feature expressions that take account of the MIME
> content type of the corresponding data.
> RFC 2938 - Identifying Composite Media Features, September 2000
> Updates 2533
> In RFC 2533, an expression format is presented for describing media
> feature capabilities as a combination of simple media feature tags.
>
> This document describes an abbreviated format for a composite media
> feature set, based upon a hash of the feature expression describing
> that composite.
>
>
>
>
This archive was generated by hypermail 2b29 : Tue Dec 05 2000 - 02:37:54 EST