rfc2879.txt

RFC 的详细文档！

      high resolution documents.  (The available 300dpi document
      codings here are MMR and JBIG, and the receiver capabilities are
      MH, MR and JBIG.)

   o  The low-resolution version of the document can be sent with
      either MH or MR coding as the receiver can deal with either of
      these for low resolution documents.

   o  The high resolution variant of the document is available only for
      A4, so that is the paper-size used in that case.  Similarly the
      low resolution version is sent for B4 paper.

   o  Even though the sender may not understand the 'ua-media' feature
      tag, and does not mention it, the matching rules preserve the



Klyne & McIntyre            Standards Track                    [Page 20]

RFC 2879      Content Feature Schema for Internet Fax (V2)   August 2000


      constraint that the B4 document is rendered with
     '(ua-media=continuous)', and the A4 document may be rendered with
     '(ua-media=[stationery,transparency])'.

   Finally, note that when matching an MRC document description, the
   description of each component sub-image must match the capabilities
   of the intended receiver.

5. IANA Considerations

   Appendix A of this document repeats the descriptions of feature tags
   introduced by RFC 2531 [22], with some small revisions.  These have
   been registered in the "IETF tree", according to the procedure
   described in section 3.1.1 of "Media Feature Tag Registration
   Procedure" [1] (i.e. these feature tags are subject to the "IETF
   Consensus" policies described in RFC 2434 [21]).

   Appendix section A.5 introduces one new feature tag (color-
   illuminant) to be registered according to the same procedure.  An
   ASN.1 identifier should be assigned for this new tag and replaced in
   the body of the registration.

6. Security Considerations

   The points raised below are in addition to the general security
   considerations for extended Internet fax [5], and others discussed in
   [2,8,11,12,13]

6.1 Capability descriptions and mechanisms

   Negotiation mechanisms reveal information about one party to other
   parties.  This may raise privacy concerns, and may allow a malicious
   party to make better guesses about the presence of specific security
   holes.

   Most of these concerns pertain to capability information getting into
   the hands of someone who may abuse it.  This document specifies
   capabilities that help a sender to determine what image
   characteristics can be processed by the recipient, not mechanisms for
   their publication.  Implementers and users should take care that the
   mechanisms employed ensure that capabilities are revealed only to
   appropriate persons, systems and agents.

6.2 Specific threats

   1. Unsolicited bulk mail:  if it is known that a recipient can
      process certain types of images, they may be targeted by bulk
      mailers that want to send such images.



Klyne & McIntyre            Standards Track                    [Page 21]

RFC 2879      Content Feature Schema for Internet Fax (V2)   August 2000


7. Acknowledgements

   The authors gratefully acknowledge the contributions of the following
   persons who commented on earlier versions of this memo:  James
   Rafferty, Dan Wing, Robert Buckley, Mr Ryuji Iwazaki.  The following
   contributed ideas upon which some of the features described here have
   been based:  Larry Masinter, Al Gilman, Koen Holtman.

8. References

   [1]  Holtman, K., Mutz, A. and T. Hardie, "Media Feature Tag
        Registration Procedure", RFC 2506, March 1999.

   [2]  Klyne, G., "A syntax for describing media feature sets", RFC
        2533, March 1999.

   [3]  Masinter, L., Holtman, K., Mutz, A. and D. Wing, "Media Features
        for Display, Print, and Fax", RFC 2534, March 1999.

   [4]  McIntyre, L. and G. Klyne, "Internet Fax T.30 Feature Mapping",
        RFC 2880, July 2000.

   [5]  Masinter, L. and D. Wing, RFC 2532, "Extended Facsimile Using
        Internet Mail", RFC 2532, March 1999.

   [6]  "Procedures for document facsimile transmission in the general
        switched telephone network", ITU-T Recommendation T.30 (1999),
        International Telecommunications Union, March 1999

   [7]  McIntyre, L., Buckley, R., Venable, D., Zilles, S., Parsons, G.
        and J. Rafferty, "File format for Internet fax", RFC 2301, March
        1998.

   [8]  Toyoda, K., Ohno, H., Murai, J. and D. Wing, "A Simple Mode of
        Facsimile Using Internet Mail", RFC 2305, March 1998.

   [9]  "Continuous-tone color representation method for facsimile"
        ITU-T Recommendation T.42 (1996) International
        Telecommunications Union (Covers custom illuminant, gamut)

   [10] "Colour and gray-scale image representation using lossless
        coding scheme for facsimile" ITU-T Recommendation T.43 (1997)
        International Telecommunications Union.  (Covers JBIG for
        colour/grey images)

   [12] Klyne, G., "Protocol-independent Content Negotiation Framework",
        RFC 2703, September 1999.




Klyne & McIntyre            Standards Track                    [Page 22]

RFC 2879      Content Feature Schema for Internet Fax (V2)   August 2000


   [13] "Standardization of Group 3 facsimile terminals for document
        transmission", ITU-T Recommendation T.4 (1999), International
        Telecommunications Union, (Covers basic fax coding formats: MH,
        MR)

   [14] "Facsimile coding schemes and coding control functions for Group
        4 facsimile apparatus", ITU Recommendation T.6, International
        Telecommunications Union,  (Commonly referred to as the MMR
        standard; covers extended 2-D fax coding format).

   [15] "Mixed Raster Content (MRC)", ITU-T Recommendation T.44,
        International Telecommunications Union.

   [16] "Information technology - Digital compression and coding of
        continuous-tone still image - Requirements and guidelines" ITU-T
        Recommendation T.81 (1992) | ISO/IEC 10918-1:1993 International
        Telecommunications Union, (Commonly referred to as JPEG
        standard)

   [17] "Information technology - Coded representation of picture and
        audio information - Progressive bi-level image compression"
        ITU-T Recommendation T.82 (1993) | ISO/IEC 11544:1993
        International Telecommunications Union (Commonly referred to as
        JBIG1 standard)

   [18] "Application profile for Recommendation T.82 - Progressive bi-
        level image compression (JBIG1 coding scheme for facsimile
        apparatus)", ITU-T Recommendation T.85 (1995),International
        Telecommunications Union, (Covers bi-level JBIG).

   [19] "Colorimeter, 2nd ed.", CIE Publication No. 15.2, 1986. (Defines
        CIELAB color space;  use with fax is further constrained by T.42
        [9].)

   [20] Tag Image File Format, Revision 6.0 Adobe Developers Association
        <ftp://ftp.adobe.com/pub/adobe/devrelations/devtechnotes/pdffiles
        /tiff6.pdf> June 1992

   [21] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
        Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.

   [22] Klyne, G. and L. McIntyre, "Content feature schema for Internet
        fax", RFC 2531, March 1999.








Klyne & McIntyre            Standards Track                    [Page 23]

RFC 2879      Content Feature Schema for Internet Fax (V2)   August 2000


9. Authors' Addresses

   Graham Klyne
   Content Technologies Ltd.
   1220 Parkview,
   Arlington Business Park
   Theale
   Reading, RG7 4SA
   United Kingdom.

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]


   Lloyd McIntyre
   Xerox Corporation
   Mailstop PAHV-121
   3400 Hillview Ave.
   Palo Alto, CA 94304 USA

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]



























Klyne & McIntyre            Standards Track                    [Page 24]

RFC 2879      Content Feature Schema for Internet Fax (V2)   August 2000


Appendix A: Feature registrations

A.1 Image size

   -  Media Feature tag name(s):

        size-x
        size-y

   -  ASN.1 identifiers associated with these feature tags:

        size-x:      1.3.6.1.8.1.7
        size-y:      1.3.6.1.8.1.8

   -  Summary of the media features indicated:

        These feature tags indicate the size of a displayed, printed
        or otherwise rendered document image;  they indicate
        horizontal (size-x) and vertical (size-y) dimensions.

        The unit of measure is inches (to be consistent with the
        measure of resolution defined by the feature tag 'dpi').

        Where the actual size is available in millimetres, a
        conversion factor of 10/254 may be applied to yield an exact
        inch-based value.

   -  Values appropriate for use with these feature tags:

        Rational (>0)

   -  The feature tag is intended primarily for use in the following
      applications, protocols, services, or negotiation mechanisms:

        Print and display applications where different media choices
        will be made depending on the size of the recipient device.

   -  Examples of typical use:

        This example describes the maximum scanned image width and
        height for Group 3 fax: 215x297 mm (8.46x11.69 inches):

        (size-x<=2150/254)
        (size-y<=2970/254)







Klyne & McIntyre            Standards Track                    [Page 25]

RFC 2879      Content Feature Schema for Internet Fax (V2)   August 2000


   -  Related standards or documents:

        The memo "Media Features for Display, Print, and Fax" [3]
        describes features (pix-x, pix-y) for measuring document size
        in pixels.

        Fax applications should declare physical dimensions using the
        features defined here.

   -  Considerations particular to use in individual applications,
      protocols, services, or negotiation mechanisms:

        Where no physical size is known or available, but a pixel size
        is known, a notional size should be declared based upon known
        pixel dimensions and a notional resolution of (say) 100dpi

        For example, to describe a 640x480 pixel display:

           (& (size-x<=640/100) (size-y<=480/100) (dpi=100) )

        The notional 100dpi resolution is used as it represents a
        fairly typical resolution for a pixel-limited display.
        Reducing the rational numbers to canonical form gives the
        following equivalent expression:

           (& (size-x<=32/5) (size-y<=24/5) (dpi=100) )

   -  Interoperability considerations:

        For interoperability with other (non-fax) applications that
        use only pixel-based measurements, pixel dimensions (pix-x,
        pix-y) may be declared in addition to physical measurements.

   -  Related feature tags:

        pix-x                 [3]
        pix-y                 [3]
        dpi                   [3]
        dpi-xyratio           [this document]

   -  Intended usage:

        Common








Klyne & McIntyre            Standards Track                    [Page 26]

RFC 2879      Content Feature Schema for Internet Fax (V2)   August 2000


   -  Author/Change controller:

        IETF

A.2 Resolution aspect ratio

   -  Media Feature tag name(s):

        dpi-xyratio